OSPF neighborship is up but there is no route in the routing table

OSPF neighborship is up but there is no route in the routing table

52064
Created On 09/26/18 13:49 PM - Last Modified 06/09/23 09:06 AM


Resolution


Sometimes OSPF neighborship is up and exchanged routes are present in the OSPF LSDB but routes are not injected into the routing table. If the network type is mismatched on both sides then this may occur. To resolve this issue, change the network type.

 

Network Type.png

 

On one side the network type might be broadcast but another side might be point-to-point.

 

In the following example, OSPF is configured on ethernet 1/1 (192.168.73.0/24) route, from the neighbor, for network 1.1.1.0/24, which is not present in the routing table but the OSPF neighbor ship is up and the route is present in the LSDB.

 

PA> show routing route

 

flags: A:active, ?:loose, C:connect, H:host, S:static, ~:internal, R:rip, O:ospf, B:bgp,

 

      Oi:ospf intra-area, Oo:ospf inter-area, O1:ospf ext-type-1, O2:ospf ext-type-2

 

VIRTUAL ROUTER: default (id 1)

 

  ==========

 

destination                                 nexthop                                 metric flags      age   interface          next-AS

 

10.1.12.0/24                                192.168.73.2                            10     A S              ethernet1/1

 

12.0.0.1/32                                 0.0.0.0                                 0      A H

 

192.168.73.0/24                             0.0.0.0                                 10       Oi       548   ethernet1/1

 

192.168.73.0/24                             192.168.73.12                           0      A C              ethernet1/1

 

192.168.73.12/32                            0.0.0.0                                 0      A H

 

total routes shown: 5

 

PA> show routing protocol ospf neighbor virtual-router default

 

  Options: 0x80:reserved, O:Opaq-LSA capability, DC:demand circuits, EA:Ext-Attr LSA capability,

           N/P:NSSA option, MC:multicase, E:AS external LSA capability, T:TOS capability

 

  ==========

virtual router:                default

  neighbor address:              192.168.73.11

  local address binding:         0.0.0.0

  type:                          dynamic

  status:                        full

  neighbor router ID:            1.1.1.1

    area id:                       0.0.0.0

  neighbor priority:             1

  lifetime remain:               34

  messages pending:              0

  LSA request pending:           0

  options:                       0x52: O EA E

  hello suppressed:              no

  restart helper status:         not helping

restart helper time remaining: 0

restart helper exit reason:    none

 

PA> show routing protocol ospf lsdb virtual-router default

 

VIRTUAL ROUTER: default (id 1)

  ==========

VR Area ID         Orig RTR ID     LS ID              LSA Type             Seq Number CheckSum     Age  Size

 

  1 0.0.0.0         1.1.1.1         1.1.1.1            type-1 (Router)      0x80000002 0x000050D8   434    60

    1 0.0.0.0         192.68.72.12    192.68.72.12       type-1 (Router)      0x80000006 0x0000707B   429    48 

    1 0.0.0.0         192.68.72.12    192.168.73.12/24   type-2 (Network)     0x80000001 0x0000F7EC   434    32

 



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClrHCAS&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Choose Language