Community discussions

MikroTik App
 
chmotry
just joined
Topic Author
Posts: 3
Joined: Tue Feb 14, 2023 8:11 am

flapping interface up/down

Tue May 30, 2023 11:29 am

hi guys.

i have a switch 2960s-48ts-s that connected to rb912uag mikrotik. in other side the rb connected to router 2811 .
in both sides the ether port between cisco devices and mikrotik devices is upped and downed alternately .

The port turns off and on irregularly at different times. the logging show the below data:

in switch:

int g0/2
switchport access vlan 10
switchport mode access

-------------

:06:43.113: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:07:01.191: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:07:02.192: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:16:18.174: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:16:19.175: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:16:56.274: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:16:57.275: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:25:36.089: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:25:37.091: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:26:14.158: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:26:15.159: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:26:19.569: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:26:20.570: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:26:38.212: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:26:39.219: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:27:03.834: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:27:04.836: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:27:21.744: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:27:22.745: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:27:44.734: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:27:45.735: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:28:22.934: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:28:25.078: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:28:43.161: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:28:44.162: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:28:46.411: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:28:47.413: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 15:29:05.726: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 15:29:06.727: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 16:14:01.998: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 16:14:03.004: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 16:14:40.805: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 16:14:41.807: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 16:15:11.681: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 16:15:12.682: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 16:15:29.276: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 16:15:30.277: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
*Jan 7 17:05:41.148: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jan 7 17:05:42.149: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jan 7 17:06:19.049: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jan 7 17:06:20.050: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up



sh int g0/2
GigabitEthernet0/2 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is .....

MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:27, output 00:00:00, output hang never
Last clearing of "show interface" counters 1w2d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 271964
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 79000 bits/sec, 44 packets/sec
5 minute output rate 355000 bits/sec, 46 packets/sec
31144613 packets input, 5008047060 bytes, 0 no buffer
Received 477574 broadcasts (449047 multicasts)
0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 449047 multicast, 0 pause input
0 input packets with dribble condition detected
46577778 packets output, 56331511698 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

--------------

in router 2811:

int f0/1

ip add 192.168.1.1 255.255.255.0

sh int f0/1
FastEthernet0/1 is up, line protocol is up
Hardware is .... Ethernet, address is .....
Internet address is
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 2/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 807000 bits/sec, 82 packets/sec
5 minute output rate 86000 bits/sec, 68 packets/sec
59659829 packets input, 1164540056 bytes
Received 115434 broadcasts, 0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 1 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
38795709 packets output, 1119407562 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
104 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

-------

The interesting thing that is shown is the large amount of Total output drops in switch 2960s. why this feauture is big amount?

my poe and cable and mikrotik rb are new .how i resolve this problem ?
is this problem is hardware type?
 
jesyyie14
just joined
Posts: 1
Joined: Thu Jun 01, 2023 8:43 am

Re: flapping interface up/down

Thu Jun 01, 2023 8:49 am

The interface is put into the errdisabled state if it flaps more than five times in 10 seconds. The common cause of link flap is a Layer 1 issue such as a bad cable, duplex mismatch, or bad Gigabit Interface Converter (GBIC) card.

Who is online

Users browsing this forum: infabo and 39 guests