Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4696
  • Last Modified:

OSPF: Cannot see ourself in hello, state INIT

Hi All,

I have three Cisco routers (1 x 1841 2 x 877) running ina DMVPN / Multipoint tunnel config as suggested in the Cisco text http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a008019d6f7.shtml

The Tunnels are up, and I have no problems pinging to either side (my Internal addresses are 172.16.0.1/24 for the master and 172.16.0.2-3/24 for the branch offices).

I have configured OSPF on the router at our head office and ahve been able to peer both 877's in hte brances using ospf as well. I am using Area 0 for all the Head office subnets and Areas 2+3 for the branches.

On the surface everything looks really good, however at random intravals when viewing a "debug ip ospf adj", I see the error OSPF: Cannot see ourself in hello from 210.23.138.41 on Tunnel1, state INIT

this causes the routers to regnotiate their ospf relationship which is causing all sorts of problems because for a few moments my routing tables are missing the learned routes.

Can anyone shed any light on this error?
0
mgordon-spi
Asked:
mgordon-spi
  • 2
1 Solution
 
Istvan KalmarCommented:
Hi,

Did you configured correctly the hello times?

If the hello interval command is configured at the interface configuration level, then use the interface configured value, else

If the hello interval command is configured at the area configuration level, then use the area configured value, else

If the hello interval command is configured at the router ospf configuration level, then use the router ospf configured value, else

0
 
mgordon-spiAuthor Commented:

I havent changed default hello times, however I understand that if routers have two different timer settings then ospf will not allow them to form an adjacency.

 I have tested this and found it to be the case, so I can confirm that both routers are operating with the same hello timers.
0
 
mgordon-spiAuthor Commented:
Discovered that I was required to MAP multicast traffic as well as unicast traffic using NHRP. Issue Resolved.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now