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."