I’m not talking about the D-Link! I’m talking about the MikroTik. You’ve created 18 different VLAN interfaces. The only reason you would ever want to do this is if the MikroTik switch needs 18 IP addresses, one on each VLAN. Does the MikroTik switch need 18 IP addresses??? It is a simple yes or no answer. Do not answer with “The Dlink is on VLAN 60”.
I see a problem in your MSTP configuration above. The region name and region revision should exactly match on all switches on your network (Cisco, Dlink, MikroTik)
On the D-Link you have configured an MSTP region name of D-Link-07 with a revision of 1 and on the MikroTik you’ve configured a region name of “vlan1” with a revision of 1. This won’t work because the region names don’t match. You have to change the MST region name of all of the D-Links to “D-Link-07” and the Ciscos also to “D-Link-07” and the MikroTik to “D-Link-07”. If you want “D-Link-07” to be your region name for the entire company, it has to be set the same on all switches, and you have to make sure they are all set for revision 1.
Thanks for your messages, I changed the MSTI. Name “CORE”, revision “1”.
I also changed bridge->vlans to different ones.
Also changed everything to the standard bridge.
I created vlan interfaces because I thought it was necessary, and so I use only vlan 60 to log in to mikrotik. If they are not needed for routing, I can delete them.
That configuration is much better.
If this is intended to be a layer 2 switch (access layer), there is generally not a good reason to give the switch an IP on other VLANs besides the one that will be used for management of the switch, and in that case the extra VLAN interfaces are unnecessary.
If this is intended to be a layer 3 switch (distribution layer), meaning it will perform inter-VLAN routing between your VLANs, then of course this will need a VLAN interface for each VLAN, except for your native VLAN (normally VLAN 1). However, this will not result in satisfactory performance unless you are running RouterOS v7 which can do hardware offloaded layer 3 switching. On RouterOS v6 this will be handled by the very weak CPU of the device and it will easily become overwhelmed.
If VLAN 1 is your native VLAN on Cisco and D-Link, you should delete the Bridge->VLANs entry for VLAN 1. You will find once you delete it, you get a dynamically created VLAN 1 entry in its place due to the PVID setting for both the bridge and the bridge ports.
Also, you should only need to have “bridge” as a tagged port for those VLANs that have VLAN interfaces added. Adding “bridge” itself as tagged is how you tell the router “I want to connect this bridge vlan with the VLAN interface matching the same ID”. On Cisco this connection between VLANs and VLAN interfaces is automatic, on MikroTik you add bridge as tagged for the VLANs that need to be connected up to certain VLAN interfaces. Again on a layer 2 switch scenario, you will generally only need one VLAN interface (for your management VLAN) and therefore only that bridge->VLAN needs to have “bridge” itself as a tagged port.
You should also add your D-Link ports (sfp-D-link-xx) as tagged probably for those VLANs and then you should find that you have proper traffic passing from Cisco<–>MikroTik<–>Dlink as long as your MST region name and region revision number are matching on all devices.
This switch will not route, so it would probably be correct to say that it will work for access.
According to the last paragraph, should I do this? for each vlan.
I’m sorry I didn’t really understand paragraph 4, correct it if it’s not. I need to do as shown in the screenshot above for L2 switch.
I already had it set up like this, it still doesn’t work. Sorry.
Yes, except for one thing. Under “tagged” you have “bridge” as a port. This is necessary for VLAN 60 on which the device will have an IP, but should be avoided on all other VLANs. Having “bridge” itself as “tagged” for a VLAN means that it creates a pathway from that VLAN to the router CPU, and this pathway is only needed for access to the IP (i.e. the VLAN interface). Having “bridge” added as a “tagged” port for VLANs that do not need it increases the chances of some kind of packet storm (like a broadcast storm) overwhelming the router CPU as you are creating a pathway to the CPU for VLANs that do not require this pathway if the device doesn’t have an IP on that VLAN.
Also you should delete the bridge->VLANs entry for VLAN 1 as it will be created dynamically with the correct settings anyway (if you haven’t already deleted it).
If you do all of this and it still doesn’t work, the issue is almost certainly on the Cisco or Dlink side and not the MikroTik. If you do an /export hide-sensitive from the command line and paste the result in here we can look at the entire configuration in some case some weird setting was changed somewhere, but I doubt this will be the case.
Unfortunately, it didn’t work, I tried to reboot and so on. Previously, I just had connections from cisco to D-Link. And it worked, but we were not satisfied with the speed up to D-Link, for scanning OS images, because of this we bought Mikrotik. If everything is fine here, I will go to the D-Link forum. I think it’s still something with D-Link.
jan/20/2022 07:30:38 by RouterOS 6.49.2
software id = JJ57-1PR5
model = CRS326-24S+2Q+
serial number = D84E0F08A6E8
/interface ethernet
set [ find default-name=sfp-sfpplus1 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-01
set [ find default-name=sfp-sfpplus2 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-02
set [ find default-name=sfp-sfpplus3 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-03
set [ find default-name=sfp-sfpplus4 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-04
set [ find default-name=sfp-sfpplus5 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-05
set [ find default-name=sfp-sfpplus6 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-06
set [ find default-name=sfp-sfpplus7 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-07
set [ find default-name=sfp-sfpplus8 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-08
set [ find default-name=sfp-sfpplus9 ] advertise=“10M-half,10M-full,100M-half,
100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
disabled=yes l2mtu=9198 name=sfp-D-link-09
set [ find default-name=sfp-sfpplus23 ] advertise=“10M-half,10M-full,100M-half
,100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
l2mtu=9198
set [ find default-name=sfp-sfpplus24 ] advertise=“10M-half,10M-full,100M-half
,100M-full,1000M-half,1000M-full,2500M-full,5000M-full,10000M-full”
l2mtu=9198
set [ find default-name=qsfpplus1-1 ] disabled=yes name=zqsfpplus1-1
set [ find default-name=qsfpplus1-2 ] disabled=yes name=zqsfpplus1-2
set [ find default-name=qsfpplus1-3 ] disabled=yes name=zqsfpplus1-3
set [ find default-name=qsfpplus1-4 ] disabled=yes name=zqsfpplus1-4
set [ find default-name=qsfpplus2-1 ] disabled=yes name=zqsfpplus2-1
set [ find default-name=qsfpplus2-2 ] disabled=yes name=zqsfpplus2-2
set [ find default-name=qsfpplus2-3 ] disabled=yes name=zqsfpplus2-3
set [ find default-name=qsfpplus2-4 ] disabled=yes name=zqsfpplus2-4
set [ find default-name=sfp-sfpplus10 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus10
set [ find default-name=sfp-sfpplus11 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus11
set [ find default-name=sfp-sfpplus12 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus12
set [ find default-name=sfp-sfpplus13 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus13
set [ find default-name=sfp-sfpplus14 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus14
set [ find default-name=sfp-sfpplus15 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus15
set [ find default-name=sfp-sfpplus16 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus16
set [ find default-name=sfp-sfpplus17 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus17
set [ find default-name=sfp-sfpplus18 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus18
set [ find default-name=sfp-sfpplus19 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus19
set [ find default-name=sfp-sfpplus20 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus20
set [ find default-name=sfp-sfpplus21 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus21
set [ find default-name=sfp-sfpplus22 ] disabled=yes l2mtu=9198 name=
zsfp-sfpplus22
/interface bridge
add admin-mac=DC:2C:6E:4D:FD:FA auto-mac=no comment=defconf name=bridge
priority=0x9000 protocol-mode=mstp region-name=CORE region-revision=1
vlan-filtering=yes
add name=bridge-eth
/interface vlan
add interface=bridge name=VLAN-60 vlan-id=60
/interface bonding
add mode=802.3ad name=bonding-cisco slaves=sfp-sfpplus24,sfp-sfpplus23
/interface list
add name=WAN
add name=LAN
/interface bridge msti
add bridge=bridge identifier=1 priority=0x9000 vlan-mapping=
1,5,11-13,21-23,31-33,41-43,60,172,200,300
/interface bridge port
add bridge=bridge-eth comment=defconf interface=ether1
add bridge=bridge interface=bonding-cisco
add bridge=bridge interface=sfp-D-link-01
add bridge=bridge interface=sfp-D-link-02
add bridge=bridge interface=sfp-D-link-03
add bridge=bridge interface=sfp-D-link-04
add bridge=bridge interface=sfp-D-link-05
add bridge=bridge interface=sfp-D-link-06
add bridge=bridge interface=sfp-D-link-07
add bridge=bridge interface=sfp-D-link-08
add bridge=bridge interface=sfp-D-link-09
/interface bridge vlan
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=5
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=11
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=12
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=13
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=21
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=22
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=23
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=31
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=32
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=33
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=41
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=42
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=43
add bridge=bridge tagged=“bonding-cisco,bridge,sfp-D-link-01,sfp-D-link-02,sfp
-D-link-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-l
ink-08,sfp-D-link-09” vlan-ids=60
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=172
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=200
add bridge=bridge tagged=“bonding-cisco,sfp-D-link-01,sfp-D-link-02,sfp-D-link
-03,sfp-D-link-04,sfp-D-link-05,sfp-D-link-06,sfp-D-link-07,sfp-D-link-08,
sfp-D-link-09” vlan-ids=300
/interface list member
add interface=ether1 list=WAN
add interface=sfp-D-link-01 list=LAN
add interface=sfp-D-link-02 list=LAN
add interface=sfp-D-link-03 list=LAN
add interface=sfp-D-link-04 list=LAN
add interface=sfp-D-link-05 list=LAN
add interface=sfp-D-link-06 list=LAN
add interface=sfp-D-link-07 list=LAN
add interface=sfp-D-link-08 list=LAN
add interface=sfp-D-link-09 list=LAN
add interface=zsfp-sfpplus10 list=LAN
add interface=zsfp-sfpplus11 list=LAN
add interface=zsfp-sfpplus12 list=LAN
add interface=zsfp-sfpplus13 list=LAN
add interface=zsfp-sfpplus14 list=LAN
add interface=zsfp-sfpplus15 list=LAN
add interface=zsfp-sfpplus16 list=LAN
add interface=zsfp-sfpplus17 list=LAN
add interface=zsfp-sfpplus18 list=LAN
add interface=zsfp-sfpplus19 list=LAN
add interface=zsfp-sfpplus20 list=LAN
add interface=zsfp-sfpplus21 list=LAN
add interface=zsfp-sfpplus22 list=LAN
add interface=sfp-sfpplus23 list=LAN
add interface=sfp-sfpplus24 list=LAN
add list=LAN
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge-eth network=
192.168.88.0
add address=10.60.60.253/24 interface=VLAN-60 network=10.60.60.0
/ip dns
set servers=10.14.206.251
/ip ipsec policy
set 0 disabled=yes
/ip route
add distance=1 gateway=10.60.60.254
/ip service
set telnet disabled=yes
set ftp disabled=yes
set winbox disabled=yes
/system clock
set time-zone-name=Asia/Yekaterinburg
/system routerboard settings
set baud-rate=9600 boot-os=router-os
/system swos
set address-acquisition-mode=static allow-from-ports=“p1,p2,p3,p4,p5,p6,p7,p8,
p9,p10,p11,p12,p13,p14,p15,p16,p17,p18,p19,p20,p21,p22,p23,p24,p25,p26,p27
,p28,p29,p30,p31,p32” allow-from-vlan=1 identity=it-ktk-sw-port-0
static-ip-address=10.50.50.6
Everything is correct and standard with that configuration. To troubleshoot further at this point, I would try doing ping tests on VLAN 60 to the Cisco and Dlink from the MikroTik to help narrow down where the problem is.
I’ll start with the fact that now the traffic goes directly from Cisco to D-Link. And when the interfaces from Mikrotik to D-Link are disabled, the ping goes.
But as soon as I turn off the traffic from Cisco to D-Link, and turn on the interfaces on Mikrotik, even restarting them, D-Link does not connect and there is no traffic.
I have suspicions that the D-Link interface is not working correctly, or the sfp module.