Strange entries in OSPF LSADB
Hi! I'm use OSPF network statement networks { 10.32.0.0/12; } And when I look at show ospf lsadb I see entry 0003 10.47.255.255 10.0.0.0 237 80000001 809e I discover, that for some networks LSADB entries looks strange: In bird.conf: networks { 10.32.0.0/12; 10.48.0.0/12; 10.64.0.0/12; 10.80.0.0/12; 10.96.0.0/12; 10.112.0.0/12; 10.128.0.0/12; 10.144.0.0/12; 10.160.0.0/12; 10.176.0.0/12; 10.192.0.0/12; 10.208.0.0/12; 10.224.0.0/12; 10.240.0.0/12; }; bird> show ospf lsadb 0001 10.0.0.0 10.0.0.0 174 8000011b 43b4 0003 10.47.255.255 10.0.0.0 237 80000001 809e 0003 10.48.0.0 10.0.0.0 68 80000001 74a9 0003 10.79.255.255 10.0.0.0 62 80000001 feff 0003 10.80.0.0 10.0.0.0 62 80000001 f20b 0003 10.111.255.255 10.0.0.0 56 80000001 7d61 0003 10.112.0.0 10.0.0.0 50 80000001 716c 0003 10.143.255.255 10.0.0.0 44 80000001 fbc2 0003 10.144.0.0 10.0.0.0 44 80000001 efcd 0003 10.175.255.255 10.0.0.0 38 80000001 7a24 0003 10.176.0.0 10.0.0.0 32 80000001 6e2f 0003 10.207.255.255 10.0.0.0 26 80000001 f885 0003 10.208.0.0 10.0.0.0 20 80000001 ec90 0003 10.239.255.255 10.0.0.0 20 80000001 77e6 0003 10.240.0.0 10.0.0.0 14 80000001 6bf1 Is it normal?
On Fri, Jun 27, 2014 at 12:10:11PM +0400, 1 ????? wrote:
bird> show ospf lsadb
0001 10.0.0.0 10.0.0.0 174 8000011b 43b4 0003 10.47.255.255 10.0.0.0 237 80000001 809e 0003 10.48.0.0 10.0.0.0 68 80000001 74a9 0003 10.79.255.255 10.0.0.0 62 80000001 feff 0003 10.80.0.0 10.0.0.0 62 80000001 f20b 0003 10.111.255.255 10.0.0.0 56 80000001 7d61 0003 10.112.0.0 10.0.0.0 50 80000001 716c 0003 10.143.255.255 10.0.0.0 44 80000001 fbc2 0003 10.144.0.0 10.0.0.0 44 80000001 efcd 0003 10.175.255.255 10.0.0.0 38 80000001 7a24 0003 10.176.0.0 10.0.0.0 32 80000001 6e2f 0003 10.207.255.255 10.0.0.0 26 80000001 f885 0003 10.208.0.0 10.0.0.0 20 80000001 ec90 0003 10.239.255.255 10.0.0.0 20 80000001 77e6 0003 10.240.0.0 10.0.0.0 14 80000001 6bf1
Is it normal?
Yes, it is. LSA IDs could be any value from the network prefix and BIRD assigns them in a way that prevents collisions in the case that networks are nested. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hello, I advertise default gateway 0/0 from 2 juniper routers into servers with bird. On one router (.14) advertise with metric 30 on second router (.9) with metric 70. I see LSA from both routers but bird always select metric 70 as better.. Beside metrics rest configuration are identical.. bird> show route 0.0.0.0/0 0.0.0.0/0 via 1.1.1.9 on bond0 [MyOSPF 00:11:12] * E2 (150/10/70) [1.1.1.9] when i turn off router with higher metric: bird> show route 0.0.0.0/0 0.0.0.0/0 via 1.1.1.14 on bond0 [MyOSPF 00:39:45] * E2 (150/10/30) [1.1.1.14] and when i turn on again router, bird choose metric 70 as better: bird> show route 0.0.0.0/0 0.0.0.0/0 via 1.1.1.9 on bond0 [MyOSPF 00:40:55] * E2 (150/10/70) [1.1.1.9] bird> show ospf neighbors MyOSPF: Router ID Pri State DTime Interface Router IP 1.1.1.14 128 full/other 00:40 bond0 1.1.1.14 1.1.1.9 128 full/dr 00:38 bond0 1.1.1.9 bird> show ospf lsadb Global Type LS ID Router Age Sequence Checksum 0005 0.0.0.0 11.1.1.9 1395 800000bc ce57 0005 0.0.0.0 11.1.1.14 1698 800000c0 52a6 protocol ospf MyOSPF { tick 2; # debug { states, routes, interfaces }; import filter ospf_import; export filter ospf_export; rfc1583compat yes; area 112 { interface "bond0" { authentication none; hello 10; poll 30; type nonbroadcast; neighbors { 1.1.1.9 eligible; 1.1.1.14 eligible; }; }; }; }; thanks for help, Peter
On Fri, Jul 11, 2014 at 01:01:43AM +0200, Piotr wrote:
Hello,
I advertise default gateway 0/0 from 2 juniper routers into servers with bird. On one router (.14) advertise with metric 30 on second router (.9) with metric 70. I see LSA from both routers but bird always select metric 70 as better.. Beside metrics rest configuration are identical..
Interesting. Which BIRD version do you use? Could you send output of 'show ospf state'? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
W dniu 2014-07-11 02:22, Ondrej Zajicek pisze:
On Fri, Jul 11, 2014 at 01:01:43AM +0200, Piotr wrote:
Hello,
I advertise default gateway 0/0 from 2 juniper routers into servers with bird. On one router (.14) advertise with metric 30 on second router (.9) with metric 70. I see LSA from both routers but bird always select metric 70 as better.. Beside metrics rest configuration are identical..
Interesting. Which BIRD version do you use? Could you send output of 'show ospf state'?
router 1.1.1.5 it's server with bird router 1.1.1.9 it's juniper with metric 70 router 1.1.1.14 it's juniper with metric 30 # birdc BIRD 1.4.3 ready. bird> show ospf state area 0.0.0.112 router 1.1.1.5 distance 0 network 1.1.1.0/28 metric 10 stubnet 192.168.20.0/25 metric 10 router 1.1.1.9 distance 10 network 1.1.1.0/28 metric 1 stubnet 192.168.20.0/25 metric 1 external 0.0.0.0/0 metric2 70 network 1.1.1.0/28 dr 1.1.1.9 distance 10 router 1.1.1.9 router 1.1.1.5
On Fri, Jul 11, 2014 at 08:53:32AM +0200, Piotr wrote:
router 1.1.1.5 it's server with bird router 1.1.1.9 it's juniper with metric 70 router 1.1.1.14 it's juniper with metric 30
network 1.1.1.0/28 dr 1.1.1.9 distance 10 router 1.1.1.9 router 1.1.1.5
This seems like NBMA related problem - perhaps 1.1.1.9 and 1.1.1.14 are not configured as neighbors to each other (not in BIRD but in their configurations). Therefore 1.1.1.9 does not include 1.1.1.14 as a neighbor in Net-LSA, and 1.1.1.14 is not reachable. When 1.1.1.9 is removed, another router (probably 1.1.1.14) is elected as DR and 1.1.1.14 became reachable. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
W dniu 2014-07-11 10:22, Ondrej Zajicek pisze:
On Fri, Jul 11, 2014 at 08:53:32AM +0200, Piotr wrote:
router 1.1.1.5 it's server with bird router 1.1.1.9 it's juniper with metric 70 router 1.1.1.14 it's juniper with metric 30
network 1.1.1.0/28 dr 1.1.1.9 distance 10 router 1.1.1.9 router 1.1.1.5
This seems like NBMA related problem - perhaps 1.1.1.9 and 1.1.1.14 are not configured as neighbors to each other (not in BIRD but in their configurations). Therefore 1.1.1.9 does not include 1.1.1.14 as a neighbor in Net-LSA, and 1.1.1.14 is not reachable. When 1.1.1.9 is removed, another router (probably 1.1.1.14) is elected as DR and 1.1.1.14 became reachable.
Yes, You are right, i forgot, in nbma type, configure junipers routers each other. It works now. Thanks for help! Peter
participants (3)
-
1 Игорь -
Ondrej Zajicek -
Piotr