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.

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

FRR which acts as L1L2 ISIS Router doesn't append L1 routes to L2 database #6966

Open
static33rus opened this issue Aug 21, 2020 · 2 comments
Labels
isis triage Needs further investigation

Comments

@static33rus
Copy link

FRR version: 7.4
Scheme:
FRR1(L1) --- FRR2(L1L2) ---- FRR3(L2)
FRR1 advertises network 192.168.4.0/24, this network appeared in FRR2 RIB, but not in FRR3

FRR2 database:

FRR2# show isis database detail FRR1
Area 1:
IS-IS Level-1 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
FRR1.00-00                 98   0x00000007  0xa5dd     698    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0001
  MT Router Info: ipv4-unicast
  MT Router Info: ipv6-unicast
  Hostname: FRR1
  TE Router ID: 192.168.4.1
  Router Capability: 192.168.4.1 , D:0, S:0
  Extended Reachability: 0000.0000.0002.02 (Metric: 10)
  IPv4 Interface Address: 192.168.4.1
  Extended IP Reachability: 192.168.2.0/24 (Metric: 10)
  Extended IP Reachability: 192.168.4.0/24 (Metric: 10)


FRR2# show isis database detail FRR2
Area 1:
IS-IS Level-1 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
FRR2.00-00           *     98   0x00000006  0x0b7d     759    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0001
  MT Router Info: ipv4-unicast
  MT Router Info: ipv6-unicast
  Hostname: FRR2
  TE Router ID: 192.168.3.1
  Router Capability: 192.168.3.1 , D:0, S:0
      Algorithm: 0: SPF 0: SPF
  Extended Reachability: 0000.0000.0002.02 (Metric: 10)
  IPv4 Interface Address: 192.168.3.1
  Extended IP Reachability: 192.168.2.0/24 (Metric: 10)
  Extended IP Reachability: 192.168.3.0/24 (Metric: 10)

IS-IS Level-2 link-state database:
LSP ID                  PduLen  SeqNumber   Chksum  Holdtime  ATT/P/OL
FRR2.00-00           *     98   0x00000006  0xe1a5     761    0/0/0
  Protocols Supported: IPv4
  Area Address: 49.0001
  MT Router Info: ipv4-unicast
  MT Router Info: ipv6-unicast
  Hostname: FRR2
  TE Router ID: 192.168.3.1
  Router Capability: 192.168.3.1 , D:0, S:0
      Algorithm: 0: SPF 0: SPF
  Extended Reachability: 0000.0000.0001.02 (Metric: 10)
  IPv4 Interface Address: 192.168.3.1
  Extended IP Reachability: 192.168.2.0/24 (Metric: 10)
  Extended IP Reachability: 192.168.3.0/24 (Metric: 10)

As you can see on output above, FRR2 received route 192.168.4.0/24 from FRR1 in L1 LSP, but didn't append this route to L2 database and as a result FRR3 didn't receive this route

@static33rus static33rus added the triage Needs further investigation label Aug 21, 2020
@qlyoung qlyoung added the isis label Dec 16, 2020
@winyannainghtut
Copy link

Is there any update about this issue ? I'm facing the same problem with the FRR v8.2.2

@kyrielucy
Copy link

I also encountered the problem that the l1l2 border router did not convert the l1 route to l2 lsp. Is there a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
isis triage Needs further investigation
Projects
None yet
Development

No branches or pull requests

4 participants