Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ISIS: The L1-2 router cannot advertise L1 routes into L2. #12793

Open
MintLife619 opened this issue Feb 11, 2023 · 8 comments
Open

ISIS: The L1-2 router cannot advertise L1 routes into L2. #12793

MintLife619 opened this issue Feb 11, 2023 · 8 comments
Assignees
@riw777
Labels
isis

Comments

@MintLife619
Copy link

ISIS L1-2 router with FRR installed cannot advertise the route from Level-1 to Level-2

[√] Did you check if this is a duplicate issue?
[√] Did you test it on the latest FRRouting/frr master branch?

To Reproduce
Steps to reproduce the behavior:

  1. Virtual bridges are used to connect containers with frr to form a network.
  2. Open the ISIS daemon in the container (router) where the ISIS protocol needs to be deployed.
  3. Configure the protocol. The interface connected with L1 domain is set as "isis circuit-type level-1" and the interface connected with L2 domain is set as "isis circuit-type level-2".
  4. Perform connectivity test.

Expected behavior
Different ISIS regions should be able to connect with each other.

Versions

  • OS Version: Ubuntu 20.04 LTS
  • LXD/LXC Version: 5.10. Routers are Linux containers running FRR.
  • Kernel: 5.4.0-135-generic
  • FRR Version: 8.4.2

Additional context
The Network topology diagram:
AR1(L1) --- AR2(L1/2) --- AR3(L2) --- AR4(L1/2) --- AR5(L1)

image

logs and captures
show running-config:
AR1:

AR1# show running-config 
Building configuration...

Current configuration:
!
frr version 8.4.2
frr defaults traditional
hostname AR1
log syslog informational
no ipv6 forwarding
service integrated-vtysh-config
!
interface lo
 ip address 1.1.1.1/32
 ip router isis AA
exit
!
interface eth0
 ip router isis AA
exit
!
router isis AA
 is-type level-1
 net 49.0002.0000.0000.1111.00
exit
!
end

AR2:

AR2# show running-config 
Building configuration...

Current configuration:
!
frr version 8.4.2
frr defaults traditional
hostname AR2
log syslog informational
no ipv6 forwarding
service integrated-vtysh-config
!
interface lo
 ip address 2.2.2.2/32
 ip router isis AA
exit
!
interface eth0
 ip router isis AA
 isis circuit-type level-1
exit
!
interface eth1
 ip router isis AA
 isis circuit-type level-2-only
exit
!
interface loo
exit
!
router isis AA
 net 49.0002.0000.0000.2222.00
 net 49.0001.0000.0000.2222.00
exit
!
end

AR3:

AR3# show running-config 
Building configuration...

Current configuration:
!
frr version 8.4.2
frr defaults traditional
hostname AR3
log syslog informational
no ipv6 forwarding
service integrated-vtysh-config
!
interface lo
 ip address 3.3.3.3/32
 ip router isis AA
exit
!
interface eth0
 ip router isis AA
exit
!
interface eth1
 ip router isis AA
exit
!
router isis AA
 is-type level-2-only
 net 49.0001.0000.0000.3333.00
exit
!
end

AR4 and AR5 are similar to AR1 and AR2.

show isis databases:
AR1 database:

AR1# show isis database detail 
Area AA:
IS-IS Level-1 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
AR1.00-00            *     92   0x00000022  0x04fe     366    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0002
  Hostname: AR1
  TE Router ID: 1.1.1.1
  Router Capability: 1.1.1.1 , D:0, S:0
  Extended Reachability: 0000.0000.2222.46 (Metric: 10)
  IPv4 Interface Address: 1.1.1.1
  Extended IP Reachability: 12.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 1.1.1.1/32 (Metric: 10)

AR2.00-00                 104   0x00000022  0x4fe1    1051    1/0/0
  Protocols Supported: IPv4
  Area Address: 49.0002
  Area Address: 49.0001
  Hostname: AR2
  TE Router ID: 2.2.2.2
  Router Capability: 2.2.2.2 , D:0, S:0
  Extended Reachability: 0000.0000.2222.46 (Metric: 10)
  IPv4 Interface Address: 2.2.2.2
  Extended IP Reachability: 12.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 23.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 2.2.2.2/32 (Metric: 10)

AR2.46-00                  51   0x00000017  0xf8c7     950    1/0/0
  Extended Reachability: 0000.0000.2222.00 (Metric: 0)
  Extended Reachability: 0000.0000.1111.00 (Metric: 0)

    3 LSPs

AR2 database:

AR2# show isis database detail 
Area AA:
IS-IS Level-1 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
AR1.00-00                  92   0x00000023  0x02ff    1120    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0002
  Hostname: AR1
  TE Router ID: 1.1.1.1
  Router Capability: 1.1.1.1 , D:0, S:0
  Extended Reachability: 0000.0000.2222.46 (Metric: 10)
  IPv4 Interface Address: 1.1.1.1
  Extended IP Reachability: 12.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 1.1.1.1/32 (Metric: 10)

AR2.00-00            *    104   0x00000022  0x4fe1     942    1/0/0
  Protocols Supported: IPv4
  Area Address: 49.0002
  Area Address: 49.0001
  Hostname: AR2
  TE Router ID: 2.2.2.2
  Router Capability: 2.2.2.2 , D:0, S:0
  Extended Reachability: 0000.0000.2222.46 (Metric: 10)
  IPv4 Interface Address: 2.2.2.2
  Extended IP Reachability: 12.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 23.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 2.2.2.2/32 (Metric: 10)

AR2.46-00            *     51   0x00000017  0xf8c7     841    1/0/0
  Extended Reachability: 0000.0000.2222.00 (Metric: 0)
  Extended Reachability: 0000.0000.1111.00 (Metric: 0)

    3 LSPs

IS-IS Level-2 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
AR2.00-00            *    104   0x00000021  0x32e1     869    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0002
  Area Address: 49.0001
  Hostname: AR2
  TE Router ID: 2.2.2.2
  Router Capability: 2.2.2.2 , D:0, S:0
  Extended Reachability: 0000.0000.3333.4a (Metric: 10)
  IPv4 Interface Address: 2.2.2.2
  Extended IP Reachability: 12.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 23.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 2.2.2.2/32 (Metric: 10)

AR3.00-00                 111   0x0000001d  0xc66e    1044    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0001
  Hostname: AR3
  TE Router ID: 3.3.3.3
  Router Capability: 3.3.3.3 , D:0, S:0
  Extended Reachability: 0000.0000.3333.4a (Metric: 10)
  Extended Reachability: 0000.0000.4444.4e (Metric: 10)
  IPv4 Interface Address: 3.3.3.3
  Extended IP Reachability: 23.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 34.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 3.3.3.3/32 (Metric: 10)

AR3.4a-00                  51   0x00000016  0x70ee    1033    0/0/0
  Extended Reachability: 0000.0000.3333.00 (Metric: 0)
  Extended Reachability: 0000.0000.2222.00 (Metric: 0)

AR4.00-00                 104   0x0000001c  0x95c9    1050    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0003
  Area Address: 49.0001
  Hostname: AR4
  TE Router ID: 4.4.4.4
  Router Capability: 4.4.4.4 , D:0, S:0
  Extended Reachability: 0000.0000.4444.4e (Metric: 10)
  IPv4 Interface Address: 4.4.4.4
  Extended IP Reachability: 34.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 45.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 4.4.4.4/32 (Metric: 10)

AR4.4e-00                  51   0x00000016  0xed07    1096    0/0/0
  Extended Reachability: 0000.0000.4444.00 (Metric: 0)
  Extended Reachability: 0000.0000.3333.00 (Metric: 0)

    5 LSPs

AR3 database:

AR3# show isis database detail 
Area AA:
IS-IS Level-2 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
AR2.00-00                 104   0x0000001e  0x38de     520    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0002
  Area Address: 49.0001
  Hostname: AR2
  TE Router ID: 2.2.2.2
  Router Capability: 2.2.2.2 , D:0, S:0
  Extended Reachability: 0000.0000.3333.4a (Metric: 10)
  IPv4 Interface Address: 2.2.2.2
  Extended IP Reachability: 12.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 23.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 2.2.2.2/32 (Metric: 10)

AR3.00-00            *    111   0x0000001a  0xcc6b     610    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0001
  Hostname: AR3
  TE Router ID: 3.3.3.3
  Router Capability: 3.3.3.3 , D:0, S:0
  Extended Reachability: 0000.0000.3333.4a (Metric: 10)
  Extended Reachability: 0000.0000.4444.4e (Metric: 10)
  IPv4 Interface Address: 3.3.3.3
  Extended IP Reachability: 23.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 34.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 3.3.3.3/32 (Metric: 10)

AR3.4a-00            *     51   0x00000013  0x76eb     656    0/0/0
  Extended Reachability: 0000.0000.3333.00 (Metric: 0)
  Extended Reachability: 0000.0000.2222.00 (Metric: 0)

AR4.00-00                 104   0x00000019  0x9bc6     661    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0003
  Area Address: 49.0001
  Hostname: AR4
  TE Router ID: 4.4.4.4
  Router Capability: 4.4.4.4 , D:0, S:0
  Extended Reachability: 0000.0000.4444.4e (Metric: 10)
  IPv4 Interface Address: 4.4.4.4
  Extended IP Reachability: 34.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 45.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 4.4.4.4/32 (Metric: 10)

AR4.4e-00                  51   0x00000013  0xf304     682    0/0/0
  Extended Reachability: 0000.0000.4444.00 (Metric: 0)
  Extended Reachability: 0000.0000.3333.00 (Metric: 0)

    5 LSPs

AR4 database:

AR4# show isis database detail 
Area AA:
IS-IS Level-1 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
AR4.00-00            *    104   0x00000019  0xf562     507    1/0/0
  Protocols Supported: IPv4
  Area Address: 49.0003
  Area Address: 49.0001
  Hostname: AR4
  TE Router ID: 4.4.4.4
  Router Capability: 4.4.4.4 , D:0, S:0
  Extended Reachability: 0000.0000.4444.50 (Metric: 10)
  IPv4 Interface Address: 4.4.4.4
  Extended IP Reachability: 34.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 45.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 4.4.4.4/32 (Metric: 10)

AR4.50-00            *     51   0x00000013  0x2188     462    1/0/0
  Extended Reachability: 0000.0000.4444.00 (Metric: 0)
  Extended Reachability: 0000.0000.5555.00 (Metric: 0)

AR5.00-00                  92   0x00000017  0xaa26     457    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0003
  Hostname: AR5
  TE Router ID: 5.5.5.5
  Router Capability: 5.5.5.5 , D:0, S:0
  Extended Reachability: 0000.0000.4444.50 (Metric: 10)
  IPv4 Interface Address: 5.5.5.5
  Extended IP Reachability: 45.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 5.5.5.5/32 (Metric: 10)

    3 LSPs

IS-IS Level-2 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
AR2.00-00                 104   0x0000001e  0x38de     330    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0002
  Area Address: 49.0001
  Hostname: AR2
  TE Router ID: 2.2.2.2
  Router Capability: 2.2.2.2 , D:0, S:0
  Extended Reachability: 0000.0000.3333.4a (Metric: 10)
  IPv4 Interface Address: 2.2.2.2
  Extended IP Reachability: 12.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 23.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 2.2.2.2/32 (Metric: 10)

AR3.00-00                 111   0x0000001a  0xcc6b     420    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0001
  Hostname: AR3
  TE Router ID: 3.3.3.3
  Router Capability: 3.3.3.3 , D:0, S:0
  Extended Reachability: 0000.0000.3333.4a (Metric: 10)
  Extended Reachability: 0000.0000.4444.4e (Metric: 10)
  IPv4 Interface Address: 3.3.3.3
  Extended IP Reachability: 23.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 34.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 3.3.3.3/32 (Metric: 10)

AR3.4a-00                  51   0x00000013  0x76eb     466    0/0/0
  Extended Reachability: 0000.0000.3333.00 (Metric: 0)
  Extended Reachability: 0000.0000.2222.00 (Metric: 0)

AR4.00-00            *    104   0x00000019  0x9bc6     471    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0003
  Area Address: 49.0001
  Hostname: AR4
  TE Router ID: 4.4.4.4
  Router Capability: 4.4.4.4 , D:0, S:0
  Extended Reachability: 0000.0000.4444.4e (Metric: 10)
  IPv4 Interface Address: 4.4.4.4
  Extended IP Reachability: 34.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 45.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 4.4.4.4/32 (Metric: 10)

AR4.4e-00            *     51   0x00000013  0xf304     492    0/0/0
  Extended Reachability: 0000.0000.4444.00 (Metric: 0)
  Extended Reachability: 0000.0000.3333.00 (Metric: 0)

    5 LSPs

AR5 database:

AR5# show isis database detail 
Area AA:
IS-IS Level-1 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
AR4.00-00                 104   0x00000019  0xf562     663    1/0/0
  Protocols Supported: IPv4
  Area Address: 49.0003
  Area Address: 49.0001
  Hostname: AR4
  TE Router ID: 4.4.4.4
  Router Capability: 4.4.4.4 , D:0, S:0
  Extended Reachability: 0000.0000.4444.50 (Metric: 10)
  IPv4 Interface Address: 4.4.4.4
  Extended IP Reachability: 34.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 45.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 4.4.4.4/32 (Metric: 10)

AR4.50-00                  51   0x00000013  0x2188     618    1/0/0
  Extended Reachability: 0000.0000.4444.00 (Metric: 0)
  Extended Reachability: 0000.0000.5555.00 (Metric: 0)

AR5.00-00            *     92   0x00000017  0xaa26     613    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0003
  Hostname: AR5
  TE Router ID: 5.5.5.5
  Router Capability: 5.5.5.5 , D:0, S:0
  Extended Reachability: 0000.0000.4444.50 (Metric: 10)
  IPv4 Interface Address: 5.5.5.5
  Extended IP Reachability: 45.1.1.0/24 (Metric: 10)
  Extended IP Reachability: 5.5.5.5/32 (Metric: 10)

    3 LSPs

Problem:

  1. As we can see, AR2 receives the loopback address 1.1.1.1/32 from AR1 in the L1 LSP, but does not add the route to the L2 database, so AR3 does not receive the route. Similarly, AR3 has not learned the route 5.5.5.5/32 of AR5.
  2. It turns out that AR1 can ping AR2, AR3 and AR4, but can't connect AR5, and AR3 can't connect AR1 and AR5.
  3. If a new L1 device is added to the left of AR1, it will not be able to connect the three devices of AR3-AR5.
@MintLife619 MintLife619 added the triage Needs further investigation label Feb 11, 2023
@MintLife619
Copy link
Author

MintLife619 commented Feb 16, 2023 •
edited

Supplement:
After adding L1 devices, except for loopback address, the interface address also cannot be announced to L2.
Basically, if all routers are configured with L1-2 or L2, they can be connected.

@riw777
Copy link
Member

riw777 commented Feb 28, 2023

Can you capture the routing table for each of the routers?

@MintLife619
Copy link
Author

Of course, the following is the routing table of all routers:

AR1:

AR1# show ip route 
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

I>* 0.0.0.0/0 [115/10] via 12.1.1.2, eth0, weight 1, 00:08:03
C>* 1.1.1.1/32 is directly connected, lo, 00:08:34
I>* 2.2.2.2/32 [115/20] via 12.1.1.2, eth0, weight 1, 00:08:03
I   12.1.1.0/24 [115/20] via 12.1.1.2, eth0 inactive, weight 1, 00:08:03
C>* 12.1.1.0/24 is directly connected, eth0, 00:08:36
I>* 23.1.1.0/24 [115/20] via 12.1.1.2, eth0, weight 1, 00:08:03

AR2:

AR2# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

I>* 1.1.1.1/32 [115/20] via 12.1.1.1, eth0, weight 1, 00:09:07
C>* 2.2.2.2/32 is directly connected, lo, 00:09:37
I>* 3.3.3.3/32 [115/20] via 23.1.1.2, eth1, weight 1, 00:09:07
I>* 4.4.4.4/32 [115/30] via 23.1.1.2, eth1, weight 1, 00:09:06
I   12.1.1.0/24 [115/20] via 12.1.1.1, eth0 inactive, weight 1, 00:09:07
C>* 12.1.1.0/24 is directly connected, eth0, 00:09:38
C>* 23.1.1.0/24 is directly connected, eth1, 00:09:38
I>* 34.1.1.0/24 [115/20] via 23.1.1.2, eth1, weight 1, 00:09:07
I>* 45.1.1.0/24 [115/30] via 23.1.1.2, eth1, weight 1, 00:09:06

AR3:

AR3# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

I>* 2.2.2.2/32 [115/20] via 23.1.1.1, eth0, weight 1, 00:10:10
C>* 3.3.3.3/32 is directly connected, lo, 00:10:41
I>* 4.4.4.4/32 [115/20] via 34.1.1.2, eth1, weight 1, 00:10:10
I>* 12.1.1.0/24 [115/20] via 23.1.1.1, eth0, weight 1, 00:10:10
I   23.1.1.0/24 [115/20] via 23.1.1.1, eth0 inactive, weight 1, 00:10:10
C>* 23.1.1.0/24 is directly connected, eth0, 00:10:42
I   34.1.1.0/24 [115/20] via 34.1.1.2, eth1 inactive, weight 1, 00:10:10
C>* 34.1.1.0/24 is directly connected, eth1, 00:10:42
I>* 45.1.1.0/24 [115/20] via 34.1.1.2, eth1, weight 1, 00:10:10

AR4:

AR4# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

I>* 2.2.2.2/32 [115/30] via 34.1.1.1, eth0, weight 1, 00:10:43
I>* 3.3.3.3/32 [115/20] via 34.1.1.1, eth0, weight 1, 00:10:43
C>* 4.4.4.4/32 is directly connected, lo, 00:11:14
I>* 5.5.5.5/32 [115/20] via 45.1.1.2, eth1, weight 1, 00:10:43
I>* 12.1.1.0/24 [115/30] via 34.1.1.1, eth0, weight 1, 00:10:43
I>* 23.1.1.0/24 [115/20] via 34.1.1.1, eth0, weight 1, 00:10:43
C>* 34.1.1.0/24 is directly connected, eth0, 00:11:16
I   45.1.1.0/24 [115/20] via 45.1.1.2, eth1 inactive, weight 1, 00:10:43
C>* 45.1.1.0/24 is directly connected, eth1, 00:11:16

AR5:

AR5# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

I>* 0.0.0.0/0 [115/10] via 45.1.1.1, eth0, weight 1, 00:11:14
I>* 4.4.4.4/32 [115/20] via 45.1.1.1, eth0, weight 1, 00:11:15
C>* 5.5.5.5/32 is directly connected, lo, 00:11:45
I>* 34.1.1.0/24 [115/20] via 45.1.1.1, eth0, weight 1, 00:11:15
I   45.1.1.0/24 [115/20] via 45.1.1.1, eth0 inactive, weight 1, 00:11:15
C>* 45.1.1.0/24 is directly connected, eth0, 00:11:47

@odd22
Copy link
Member

odd22 commented Apr 4, 2023

Hi,

I'm not sure that IS-IS within FRR supports this configuration i.e. L1 to L2 redistribution and vis versa even if it is possible as per RFCs.

Olivier

@MintLife619
Copy link
Author

Hi, thanks for the reply. I don't seem to find the instructions for the isis protocol redistribution in the official documentation, but this is available on other vendors' devices such as Cisco.

@odd22 odd22 added isis and removed triage Needs further investigation labels Jun 13, 2023
@mykiimike
Copy link

Same issue & same comments

@Cheeze-It
Copy link

I have seen this too. Duplicated the issue of L1 PDU information not being imported into L2 PDUs. Here's the link under VyOS showing the topology. In there we have an end user showing it, and my own testing in my own lab showing it too.

https://forum.vyos.io/t/is-is-no-network-migration-from-level-1-to-level-2-database/11990

@fett0
Copy link

fett0 commented Sep 4, 2023

here there is another case related this wrong behavior :

#6966

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@riw777 riw777

Labels
isis
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@riw777 @mykiimike @odd22 @Cheeze-It @fett0 @MintLife619