[Xorp-users] RIB does not seem to import routes from OSPF

Aidan Walton aidan at wires3.net
Wed Jul 19 04:01:21 PDT 2006


Hi Folks,

I like to say first, I'm a newbie to the group in terms of mailing in,
but thankyou for your efforts with XORP, it's just a great piece of
code.

I do however have the following situation occurring, I have seen this
occur several times over the past couple of months, typically after a
neighbour has been repeatedly connected and disconnected. Unless I'm
mistaken, which is quite possible :), this does not seem correct. I'm
running XORP over wireless links and after the wireless link has bounced
a couple of times the following problem occurs. I have an OSPF neighbour
that becomes locked in the init state. It refused to go any further
until I enabled traceoptions, as soon as I did this the neighbour
exchanged as follows and moved to 'full'. I have attached the log.  Note
the gap between the timestamps 9.17am and 10.56am represent the period
while the OSPF neighbours got locked in 'init':

Back in xorpsh the situation looks like this:



root at testnode# run show route table ipv4 unicast final
0.0.0.0/0       [static(1)/30]
                > to 10.0.0.1 via eth0/eth0
10.0.0.0/24     [connected(0)/0]
                > via eth0/eth0
192.168.0.0/30  [connected(0)/0]
                > via ath0/ath0
192.168.255.251/32      [connected(0)/0]
                > via lo/lo
root at testnode# run show ospf4 database
   OSPF link state database, Area 0.0.0.0
Type       ID               Adv Rtr           Seq      Age  Opt  Cksum
Len
Router  *192.168.255.251  192.168.255.251  0x8000002d   850  0x2  0xbe35
60
ASExt-2 *0.0.0.0          192.168.255.251  0x80000019  1431  0x2  0x68c3
36
Router   192.168.255.253  192.168.255.253  0x8000008d   846  0x2  0xe4c1
48
Network *192.168.0.1      192.168.255.251  0x80000004   851  0x2  0x2895
32
Network  192.168.0.2      192.168.255.253  0x80000001   851  0x2  0x209d
32
ASExt-2  172.16.0.0       192.168.255.253  0x80000037   258  0x2  0x50c
36
root at testnode# run show ospf4 neighbor
  Address         Interface             State      ID              Pri
Dead
192.168.0.2      ath0/ath0              Full      192.168.255.253  128
33


As you can see the OSPF LSDB has routes that should make it to the RIB
but they don't seem to. I have also attached the detailed lsdb output.
Do you think there is a problem?

After disabling and enabling the interface under ospf the neighbour
comes up exchanges and the route table and detailed lsdb is fully
populated, as below:


root at testnode# run show route table ipv4 unicast final
0.0.0.0/0       [static(1)/30]
                > to 10.0.0.1 via eth0/eth0
10.0.0.0/24     [connected(0)/0]
                > via eth0/eth0
172.16.0.0/24   [ospf(110)/2]
                > to 192.168.0.2 via ath0/ath0
192.168.0.0/30  [connected(0)/0]
                > via ath0/ath0
192.168.255.251/32      [connected(0)/0]
                > via lo/lo
192.168.255.253/32      [ospf(110)/2]
                > to 192.168.0.2 via ath0/ath0

root at testnode# run show ospf4 database
   OSPF link state database, Area 0.0.0.0
 Type       ID               Adv Rtr           Seq      Age  Opt  Cksum
Len
Router  *192.168.255.251  192.168.255.251  0x80000030   378  0x2  0xc22d
60
ASExt-2 *0.0.0.0          192.168.255.251  0x8000001b   553  0x2  0x64c5
36
Router   192.168.255.253  192.168.255.253  0x80000090   374  0x2  0xdec4
48
Network  192.168.0.2      192.168.255.253  0x80000003   374  0x2  0x1c9f
32
ASExt-2  172.16.0.0       192.168.255.253  0x80000038  1179  0x2  0x30d
36




The log file has had this appended:


[ 2006/07/19 11:48:45  WARNING xorp_ospfv2:5666 OSPF +1529 peer.cc
event_neighbour_change ] Unexpected state Down
[ 2006/07/19 11:48:45  WARNING xorp_ospfv2:5666 OSPF +314 peer.cc
receive ] Packet arrived while peer is not running
[ 2006/07/19 11:48:45  WARNING xorp_ospfv2:5666 OSPF +314 peer.cc
receive ] Packet arrived while peer is not running
[ 2006/07/19 11:49:40  INFO xorp_ospfv2:5666 OSPF +4042 peer.cc
link_state_update_received ] Same LSA
Network-LSA:
LS age 3600 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x2 Link
State ID 192.168.0.2 Advertising Router 192.168.255.253 LS sequence
number 0x80000002 LS checksum 0x1e9e length 32
        Network Mask 0xfffffffc
        Attached Router 192.168.255.251
        Attached Router 192.168.255.253
Network-LSA:
LS age    6 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x2 Link
State ID 192.168.0.2 Advertising Router 192.168.255.253 LS sequence
number 0x80000003 LS checksum 0x1c9f length 32
        Network Mask 0xfffffffc
        Attached Router 192.168.255.251
        Attached Router 192.168.255.253



I have attached also the detailed lsdb ouput after the interface has
come back up. All seems ok again!


Any help would be appreciated.

Thanks
Aidan 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xorp_log_19th_July_06.log
Type: text/x-log
Size: 10222 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20060719/8156df33/attachment.bin 
-------------- next part --------------
root at testnode# run show ospf4 database detail
   OSPF link state database, Area 0.0.0.0
Router-LSA:
LS age  407 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x1 Link State ID 192.168.255.251 Advertising Router 192.168.255.251 LS sequence number 0x8000002e LS checksum 0xbc36 length 60
        Nt-bit false
        V-bit false
        E-bit true
        B-bit false
        Type 2 Transit network IP address of Designated router 192.168.0.1 Routers interface address 192.168.0.1 Metric 1
        Type 3 Stub network Subnet number 10.0.0.0 Mask 255.255.255.0 Metric 1
        Type 3 Stub network Subnet number 192.168.255.251 Mask 255.255.255.255 Metric 1
As-External-LSA:
LS age  988 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x5 Link State ID 0.0.0.0 Advertising Router 192.168.255.251 LS sequence number 0x8000001a LS checksum 0x66c4 length 36
        Network Mask 0
        E-bit true
        Metric 30 0x1e
        Forwarding address 10.0.0.1
        External Route Tag 0
Router-LSA:
LS age  408 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x1 Link State ID 192.168.255.253 Advertising Router 192.168.255.253 LS sequence number 0x8000008e LS checksum 0xe2c2 length 48
        Nt-bit false
        V-bit false
        E-bit true
        B-bit false
        Type 2 Transit network IP address of Designated router 192.168.0.2 Routers interface address 192.168.0.2 Metric 1
        Type 3 Stub network Subnet number 192.168.255.253 Mask 255.255.255.255 Metric 1
Network-LSA:
LS age  407 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x2 Link State ID 192.168.0.1 Advertising Router 192.168.255.251 LS sequence number 0x80000005 LS checksum 0x2696 length 32
        Network Mask 0xfffffffc
        Attached Router 192.168.255.253
        Attached Router 192.168.255.251
Network-LSA:
LS age  408 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x2 Link State ID 192.168.0.2 Advertising Router 192.168.255.253 LS sequence number 0x80000002 LS checksum 0x1e9e length 32
        Network Mask 0xfffffffc
        Attached Router 192.168.255.251
        Attached Router 192.168.255.253
As-External-LSA:
LS age 1614 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x5 Link State ID 172.16.0.0 Advertising Router 192.168.255.253 LS sequence number 0x80000037 LS checksum 0x50c length 36
        Network Mask 0xffffff00
        E-bit true
        Metric 0 0
        Forwarding address 192.168.255.253
        External Route Tag 0
-------------- next part --------------
root at testnode# run show ospf4 database detail
   OSPF link state database, Area 0.0.0.0
Router-LSA:
LS age  273 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x1 Link State ID 192.168.255.251 Advertising Router 192.168.255.251 LS sequence number 0x80000030 LS checksum 0xc22d length 60
        Nt-bit false
        V-bit false
        E-bit true
        B-bit false
        Type 2 Transit network IP address of Designated router 192.168.0.2 Routers interface address 192.168.0.1 Metric 1
        Type 3 Stub network Subnet number 10.0.0.0 Mask 255.255.255.0 Metric 1
        Type 3 Stub network Subnet number 192.168.255.251 Mask 255.255.255.255 Metric 1
As-External-LSA:
LS age  448 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x5 Link State ID 0.0.0.0 Advertising Router 192.168.255.251 LS sequence number 0x8000001b LS checksum 0x64c5 length 36
        Network Mask 0
        E-bit true
        Metric 30 0x1e
        Forwarding address 10.0.0.1
        External Route Tag 0
Router-LSA:
LS age  269 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x1 Link State ID 192.168.255.253 Advertising Router 192.168.255.253 LS sequence number 0x80000090 LS checksum 0xdec4 length 48
        Nt-bit false
        V-bit false
        E-bit true
        B-bit false
        Type 2 Transit network IP address of Designated router 192.168.0.2 Routers interface address 192.168.0.2 Metric 1
        Type 3 Stub network Subnet number 192.168.255.253 Mask 255.255.255.255 Metric 1
Network-LSA:
LS age  269 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x2 Link State ID 192.168.0.2 Advertising Router 192.168.255.253 LS sequence number 0x80000003 LS checksum 0x1c9f length 32
        Network Mask 0xfffffffc
        Attached Router 192.168.255.251
        Attached Router 192.168.255.253
As-External-LSA:
LS age 1074 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x5 Link State ID 172.16.0.0 Advertising Router 192.168.255.253 LS sequence number 0x80000038 LS checksum 0x30d length 36
        Network Mask 0xffffff00
        E-bit true
        Metric 0 0
        Forwarding address 192.168.255.253
        External Route Tag 0


More information about the Xorp-users mailing list