Support Center > Search Results > SecureKnowledge Details
Following cluster failover, RouteD daemon sends OSPF "Hello" packets with no DR/BDR
Symptoms
  • Following cluster failover, RouteD daemon sends OSPF "Hello" packets with no DR/BDR.

    Example from RouteD traces::

    Sep  1 16:00:56 OSPFv2: SENT 192.168.144.30 -> 224.0.0.5 Hello length 48 (48)
                    rtrid 192.168.144.30 area 0.0.4.100 csum 0 authtype Md5
                    ASE mask 255.255.255.224 hello 2 pri 1 dead 8
                    dr 0.0.0.0 bdr 0.0.0.0 nbrs 4.10.1
    
  • Although OSPF adjacencies are in "FULL" state, and there are OSPF routes installed in the routing table of the cluster member, traffic that relies on OSPF does not pass.

  • RouteD traces show that the route was not added to the kernel due to being unreachable.

    Example from RouteD traces:

    Jul 17 12:52:40 KERNEL ADD    10.54           prefix 21 1 nexthops:   [IP Address]
    Jul 17 12:52:40 krt_action(1467): deleting krt_rt_static_update_timer
    Jul 17 12:52:40 krt_action(1479): creating krt_rt_static_update_timer
    Jul 17 12:52:40 KRT SENT(failed-nlmsgerr) NewRoute(24) len 44 pid 0 seq 71216 flags c05 family INET dst_len 21 src_len 0 tos 0 table MAIN proto ROUTED scope UNIVERSE type UNICAST flags  10.54/21 nhtype DIRECT via [IP Address] <DST, len 8> <GATEWAY, len 8>
    KRT SEND ADD    10.54           mask 255.255.248     router  [IP Address] : Network is unreachable
    
  • Output of "netstat -rnv" command shows that the directly connected routes are missing.

Solution
Note: To view this solution you need to Sign In .