ISIS and ECMP?

Hello,

I got this:


Well, both B1-Distribution-1 and B1-Distribution-2 announce 192.168.0.0/24 since one is 192.168.0.2/24 and the other is 192.168.0.3/24 (planning to do VRRP here later).
From my understanding B1-Core should get two LSPs (one from each neighbor) and both of those should have 192.168.0.0/24, so B1-Core should use ECMP to reach the 192.168.0.0/24 subnet. What am I missing, because that's not working.

B1-Core:

/routing/isis/export
# 2026-04-03 18:51:41 by RouterOS 7.22
# system id = NdEfA9bvPSL
#
/routing isis instance
add areas=49.0002 disabled=no l1.originate-default=always name=B1 system-id=0255.0255.0003
/routing isis interface-template
add instance=B1 interfaces=lo levels=l2 passive
add instance=B1 interfaces=ether2 levels=l1 ptp
add instance=B1 interfaces=ether1 levels=l1,l2 ptp
add instance=B1 interfaces=ether3 levels=l1 ptp

/ip/address/print
Columns: ADDRESS, NETWORK, INTERFACE, VRF
# ADDRESS          NETWORK       INTERFACE  VRF
0 10.255.255.3/32  10.255.255.3  lo         main
1 10.0.0.6/30      10.0.0.4      ether1     main
2 10.1.0.1/30      10.1.0.0      ether2     main
3 10.50.0.1/30     10.50.0.0     ether3     main

/ip/route/print
Flags: D - DYNAMIC; A - ACTIVE; c - CONNECT, i - IS-IS
Columns: DST-ADDRESS, GATEWAY, ROUTING-TABLE, DISTANCE
    DST-ADDRESS      GATEWAY           ROUTING-TABLE  DISTANCE
DAi 10.0.0.0/30      10.0.0.5%ether1   main                115
DAc 10.0.0.4/30      ether1            main                  0
D i 10.0.0.4/30      10.0.0.5%ether1   main                115
DAc 10.1.0.0/30      ether2            main                  0
D i 10.1.0.0/30      10.1.0.2%ether2   main                115
DAi 10.20.0.0/30     10.1.0.2%ether2   main                115
DAc 10.50.0.0/30     ether3            main                  0
D i 10.50.0.0/30     10.50.0.2%ether3  main                115
DAi 10.255.255.1/32  10.0.0.5%ether1   main                115
DAi 10.255.255.2/32  10.0.0.5%ether1   main                115
DAc 10.255.255.3/32  lo                main                  0
DAi 10.255.255.4/32  10.1.0.2%ether2   main                115
DAi 10.255.255.5/32  10.50.0.2%ether3  main                115
DAi 192.168.0.0/24   10.1.0.2%ether2   main                115

# Revealing LSPs (a ton here, so no reason to paste them all I guess
 1 D instance=B1 level=l1 lsp-id="0255.0255.0004.00-00" age=598 checksum=0xCBFE sequence=0x1A body=
       areas: 4902
       nlpid: IP
       is-reach:
           0255.0255.0005.00 20
           0255.0255.0003.00 20
       ip-reach:
           10.255.255.4 0
           10.20.0.0/30 20
           192.168.0.0/24 0
           10.1.0.0/30 20
       is-reach-ext:
           0255.0255.0005.00 20
           0255.0255.0003.00 20
       ip-reach-ext:
           10.255.255.4 0
           10.20.0.0/30 20
           192.168.0.0/24 0
           10.1.0.0/30 20

 2 D instance=B1 level=l1 lsp-id="0255.0255.0005.00-00" age=565 checksum=0x84EF sequence=0xD body=
       areas: 4902
       nlpid: IP
       is-reach:
           0255.0255.0004.00 20
           0255.0255.0003.00 20
       ip-reach:
           10.20.0.0/30 20
           10.50.0.0/30 20
           10.255.255.5 0
           192.168.0.0/24 0
       is-reach-ext:
           0255.0255.0004.00 20
           0255.0255.0003.00 20
       ip-reach-ext:
           10.20.0.0/30 20
           10.50.0.0/30 20
           10.255.255.5 0
           192.168.0.0/24 0

B1-Distribution-1:

/routing isis instance
add areas=49.0002 disabled=no name=B1 system-id=0255.0255.0004
/routing isis interface-template
add instance=B1 interfaces=lo levels=l1 passive
add instance=B1 interfaces=ether1 levels=l1 ptp
add instance=B1 interfaces=ether2 levels=l1 ptp
add instance=B1 interfaces=ether8 levels=l1 passive

/ip/address/print
Columns: ADDRESS, NETWORK, INTERFACE, VRF
# ADDRESS          NETWORK       INTERFACE  VRF
0 10.1.0.2/30      10.1.0.0      ether1     main
1 10.255.255.4/32  10.255.255.4  lo         main
2 10.20.0.1/30     10.20.0.0     ether2     main
3 192.168.0.2/24   192.168.0.0   ether8     main

B1-Distribution-2:

/routing isis instance
add areas=49.0002 name=B1 system-id=0255.0255.0005
/routing isis interface-template
add instance=B1 interfaces=lo levels=l1 passive
add instance=B1 interfaces=ether2 levels=l1 ptp
add instance=B1 interfaces=ether1 levels=l1 ptp
add instance=B1 interfaces=ether8 levels=l1 passive

/ip/address/print
Columns: ADDRESS, NETWORK, INTERFACE, VRF
# ADDRESS          NETWORK       INTERFACE  VRF
0 10.255.255.5/32  10.255.255.5  lo         main
1 10.20.0.2/30     10.20.0.0     ether2     main
2 10.50.0.2/30     10.50.0.0     ether1     main
3 192.168.0.3/24   192.168.0.0   ether8     main

Does anyone know what am I doing wrong?

Currently, ISIS does not create ECMP routes; it will be addressed in the future.

If I may, this can't be completely true: If the switch is replaced with another Router, and that router announces via IS-IS it's subnet, B1-D-1 and B1-D-2 will announce to B1-Core two routes, and both get installed. So it works, at times, I guess...?!

He is running RouterOS v7.22, but I noticed the following entry in the RouterOS changelog:

7.24rc3 Testing (2026-Jul-28)
fixed ECMP route removal

To me, this suggests that ECMP is now supported.

Can anyone confirm whether ECMP is currently supported for IS-IS in MikroTik RouterOS?

I'm just starting to deploy IS-IS in my network, and ECMP support is an important requirement for my design.