Sending again...Not sure whether my first one reached or not.
Hi Guys,
Does quagga IS-IS support leaking of level 1 IP routes to level 2. I tried
but its not working. I am using quagga-1.2.1 release. Latest one.
Any help will be appreciated. Thanks in advance.
I have simple three node topology. R1- R2 are in same area connected via L1
adjacency. R2 and R3 are in different areas, connected via L2 adjacency.
-----------------------------------------------------------------------------
L1 ----------------------------- ------------------------------
------------------------------------- L2 ----------------------------------
|
|
|
R1 (Area: 49.0001, SysId: 63b5.0001.0000.00-00 ) ----LAN(10.1.1.0/24)-----
R2 (Area 49.0001, SYSId: 0010.0100.1001.00-00) ---LAN(12.1.1.0/24)-------
R3 (Area: 49.0005, SysId: 0020.0200.2002.00-00 )
R1 is publishing IPV4 routes(192.168.(1-10).0/24) which can be seen at R2
but those routes are not seen in R3.
I checked ISIS neighbor ships is correctly formed.
At R3 I can see R2 is not sending those routes in its LSP packet.
Below given is the output of show isis database detail cmd at R2
Area 1:
IS-IS Level-1 link-state database:
LSP ID PduLen SeqNumber Chksum Holdtime ATT/P/OL
0010.0100.1001.00-00 * 96 0x0000031b 0xe304 887 0/0/0
Area Address: 49.0000
NLPID : 0xCC
IPv4 Address: 1.1.1.2
Metric : 10 IS : 63b5.0001.0000.01
Metric : 10 IPv4-Internal : 10.1.1.0 255.255.255.0
Metric : 10 IPv4-Internal : 12.1.1.0 255.255.255.0
Metric : 0 IPv4-External : 23.1.1.1 255.255.255.255
63b5.0001.0000.00-00 206 0x00000016 0x9388 1167 1/0/0
Area Address: 49.0000
NLPID : 0xCC
NLPID : unknown
NLPID : 0x8E
IPv4 Address: 10.1.1.2
Metric : 10 IS : 63b5.0001.0000.01
Metric : 10 IPv4-Internal : 10.1.1.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.1.0 255.255.255.0
>>>>>>>>>>> Published routes from R1
Metric : 0 IPv4-Internal : 192.168.2.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.3.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.4.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.5.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.6.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.7.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.8.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.9.0 255.255.255.0
Metric : 0 IPv4-Internal : 192.168.10.0 255.255.255.0
63b5.0001.0000.01-00 52 0x00000011 0xdb94 643 1/0/0
Metric : 0 IS : 63b5.0001.0000.00
Metric : 0 IS : 0010.0100.1001.00
3 LSPs
IS-IS Level-2 link-state database:
LSP ID PduLen SeqNumber Chksum Holdtime ATT/P/OL
0010.0100.1001.00-00 * 96 0x00000320 0x814c 882 0/0/0
Area Address: 49.0000
NLPID : 0xCC
IPv4 Address: 1.1.1.2
Metric : 10 IS : 0010.0100.1001.0c
Metric : 10 IPv4-Internal : 10.1.1.0 255.255.255.0
Metric : 10 IPv4-Internal : 12.1.1.0 255.255.255.0
Metric : 0 IPv4-External : 23.1.1.1 255.255.255.255
>>>
Those published routes are missing here from Level 2 LSP
0010.0100.1001.0c-00 * 52 0x00000006 0x1633 900 0/0/0
Metric : 0 IS : 0010.0100.1001.00
Metric : 0 IS : 0020.0200.2002.00
0020.0200.2002.00-00 70 0x0000028c 0xfd08 514 0/0/0
Area Address: 49.0005
NLPID : 0xCC
IPv4 Address: 2.2.2.2
Metric : 10 IS : 0010.0100.1001.0c
Metric : 10 IPv4-Internal : 12.1.1.0 255.255.255.0
3 LSPs
Below given is the output of show isis database detail cmd at R3
IS-IS Level-2 link-state database:
LSP ID PduLen SeqNumber Chksum Holdtime ATT/P/OL
0010.0100.1001.00-00 96 0x00000320 0x814c 844 0/0/0
Area Address: 49.0000
NLPID : 0xCC
IPv4 Address: 1.1.1.2
Metric : 10 IS : 0010.0100.1001.0c
Metric : 10 IPv4-Internal : 10.1.1.0 255.255.255.0
Metric : 10 IPv4-Internal : 12.1.1.0 255.255.255.0
Metric : 0 IPv4-External : 23.1.1.1 255.255.255.255 >>>
Those published routes are missing here from Level 2 LSP from R2
0010.0100.1001.0c-00 52 0x00000006 0x1633 862 0/0/0
Metric : 0 IS : 0010.0100.1001.00
Metric : 0 IS : 0020.0200.2002.00
0020.0200.2002.00-00 * 70 0x0000028c 0xfd08 477 0/0/0
Area Address: 49.0005
NLPID : 0xCC
IPv4 Address: 2.2.2.2
Metric : 10 IS : 0010.0100.1001.0c
Metric : 10 IPv4-Internal : 12.1.1.0 255.255.255.0
3 LSPs
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
