Problem with CRS317 using RSTP

RouterOS General
1

Hi,

I’m having a trouble with CRS317, this message appears 1 minute / 1 minute in log. The RSTP protocol is enabled in switchs.

19:02:09 interface,warning sfp-sfpplus1: bridge port received packet with own address as source address (b8:69:f4:7f:b1:2a), probably loop
19:03:09 interface,warning sfp-sfpplus1: bridge port received packet with own address as source address (b8:69:f4:7f:b1:2a), probably loop
19:04:09 interface,warning sfp-sfpplus1: bridge port received packet with own address as source address (b8:69:f4:7f:b1:2a), probably loop
19:05:09 interface,warning sfp-sfpplus1: bridge port received packet with own address as source address (b8:69:f4:7f:b1:2a), probably loop

I read the documentation from Mikrotik wiki and not identified any problem in configuration.

Anyone have an idea what is causing this warning message? No occurs forwarding problem but the CRS317-C is slow and not responding various SNMP and ICMP requests, causing fails on monitoring systems.

The network topology is attached to the post.

Below is the configuration from equipments.

\

CRS317-A

RouterOS 6.44

/interface bridge
add name=bridge-core-a priority=0x1000 vlan-filtering=yes
/interface bonding
add mode=802.3ad mtu=2000 name=bonding1 slaves=sfp-sfpplus3,sfp-sfpplus5
/interface bridge port
add bridge=bridge-core-a interface=sfp-sfpplus8
add bridge=bridge-core-a interface=sfp-sfpplus7
add bridge=bridge-core-a interface=sfp-sfpplus4
add bridge=bridge-core-a interface=sfp-sfpplus2
add bridge=bridge-core-a interface=sfp-sfpplus6
add bridge=bridge-core-a interface=bonding1 path-cost=5
add bridge=bridge-core-a interface=sfp-sfpplus9
add bridge=bridge-core-a interface=sfp-sfpplus10
add bridge=bridge-core-a interface=sfp-sfpplus11

\

CRS317-B

RouterOS 6.44

/interface bridge
add name=bridge-core-a priority=0x4000 vlan-filtering=yes
/interface bonding
add mode=802.3ad mtu=2000 name=bonding1 slaves=sfp-sfpplus1,sfp-sfpplus3
/interface bridge port
add bridge=bridge-core-a interface=sfp-sfpplus5 path-cost=25
add bridge=bridge-core-a interface=sfp-sfpplus7 path-cost=25
add bridge=bridge-core-a interface=sfp-sfpplus15
add bridge=bridge-core-a interface=sfp-sfpplus16
add bridge=bridge-core-a interface=bonding1 path-cost=5
add bridge=bridge-core-a interface=sfp-sfpplus9 path-cost=25

\

CRS317-C

RouterOS 6.44

/interface bridge
add name=bridge-core-a priority=0x4000 vlan-filtering=yes
/interface bridge port
add bridge=bridge-core-a interface=sfp-sfpplus1 path-cost=5
add bridge=bridge-core-a interface=sfp-sfpplus3 path-cost=25
add bridge=bridge-core-a interface=sfp-sfpplus16


\

CCR1036

RouterOS 6.42.1

/interface bridge
add name=bridge-core-a
/interface bridge port
add bridge=bridge-core-a interface=sfp-sfpplus1
add bridge=bridge-core-a interface=sfp-sfpplus2 path-cost=25
CORE.jpg

2

As no one seems to have an idea, run /interface bridge monitor bridge-core-a on all machines and watch whether the information is stable on all four and whether it is consistent (all machines have chosen the same root bridge, the root ports are the expected ones). Look for any bridge filter rules and interface ethernet switch rules which might interfere with stp operation.

Also run /tool profile on the slowly reacting CRS, it may show you which process group takes the most CPU. /log print follow-only may also yield something useful.

Other than that, just a small chance: 6.42.1 on the CCR whereas the rest is running 6.44 and no vlan-filtering there. Normally absence of vlan-filtering should not affect RSTP operation but things sometimes happen, and I hazily remember seeing some complaints about looped packets here on the forum when 6.42 was young.

3

All information appears as expected in /interface monitor bridge, as below. I believe the problem is related with RouterOS. After I upgraded the CCR to 6.44.3, the message started in equipment too :confused: , but the Changelog no refers to this problem, so I don’t know which version upgrade/downgrade. Any idea or suggestion?

CRS-A

/interface bridge monitor bridge-core-a duration=60 interval=2 without-paging
state: enabled
current-mac-address: B8:69:F4:72:E2:6A
root-bridge: yes
root-bridge-id: 0x1000.B8:69:F4:72:E2:6A
root-path-cost: 0
root-port: none
port-count: 10
designated-port-count: 10
fast-forward: no

CRS-B

/interface bridge monitor bridge-core-a duration=60 interval=2 without-paging
state: enabled
current-mac-address: B8:69:F4:72:BA:81
root-bridge: no
root-bridge-id: 0x1000.B8:69:F4:72:E2:6A
root-path-cost: 5
root-port: bonding-century
port-count: 6
designated-port-count: 5
fast-forward: no

CRS-C

/interface bridge monitor bridge-core-a duration=60 interval=2 without-paging
state: enabled
current-mac-address: B8:69:F4:7F:B1:2A
root-bridge: no
root-bridge-id: 0x1000.B8:69:F4:72:E2:6A
root-path-cost: 5
root-port: sfp-sfpplus1
port-count: 4
designated-port-count: 2
fast-forward: no

CCR1036

/interface bridge monitor bridge-core-a duration=60 interval=2 without-paging
state: enabled
current-mac-address: 64:D1:54:3B:34:A0
root-bridge: no
root-bridge-id: 0x1000.B8:69:F4:72:E2:6A
root-path-cost: 10
root-port: sfp-sfpplus1
port-count: 2
designated-port-count: 0
fast-forward: no