[Xorp-hackers] OSPF problem with keep-alive messages.

[Ben Greear]

I notice something weird in my 30-node setup.

28 of my routers are up and functioning and in 'FULL' state.  One had to
be restarted because it had port conflicts with another.  Now, the restarted
one is not able to sync with it's peers.  It seems to me that the problem
is that during 'Loading' state, there is too much traffic and it crowds out
the hello messages  (I am running this over an emulated lower bandwidth and
high latency link.)

Should we consider an LS Update to be as good as a Hello message
when trying to determine the 'Alive' status of a neighbor?

Here is a snippet of a tshark dump for one of the interfaces on
this router:

  0.090164     10.2.3.2 -> 224.0.0.5    OSPF LS Update
   0.090211     10.2.3.2 -> 224.0.0.5    OSPF LS Update
   0.090261     10.2.3.2 -> 224.0.0.5    OSPF LS Update
   0.100697     10.2.3.3 -> 10.2.3.2     OSPF LS Acknowledge
   0.109600     10.2.3.3 -> 224.0.0.5    OSPF LS Update
   0.136957     10.2.3.3 -> 224.0.0.5    OSPF LS Update
   0.140972     10.2.3.3 -> 224.0.0.5    OSPF LS Update
   0.143208     10.2.3.3 -> 224.0.0.5    OSPF LS Update
   0.179049     10.2.3.3 -> 224.0.0.5    OSPF LS Update
   0.182767     10.2.3.3 -> 224.0.0.5    OSPF LS Update
   0.216704     10.2.3.3 -> 224.0.0.5    OSPF LS Update
   0.229887     10.2.3.2 -> 224.0.0.5    OSPF LS Acknowledge
   0.229942     10.2.3.2 -> 224.0.0.5    OSPF LS Update
   0.229992     10.2.3.2 -> 224.0.0.5    OSPF LS Update
   0.230042     10.2.3.2 -> 224.0.0.5    OSPF LS Update
   0.230087     10.2.3.2 -> 224.0.0.5    OSPF LS Update
   0.230132     10.2.3.2 -> 224.0.0.5    OSPF LS Acknowledge
   0.230175     10.2.3.2 -> 10.2.3.3     OSPF LS Acknowledge
   0.230223     10.2.3.2 -> 224.0.0.5    OSPF LS Update
   0.230269     10.2.3.2 -> 224.0.0.5    OSPF LS Update

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com