OpenNMS

No nodeid found for next hop ip/0.0.0.0

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: 1.8.5
  • Fix Version/s: 1.9.92
  • Component/s: Maps/Linkd
  • Security Level: Default (Default Security Scheme)
  • Labels:
    None
  • Environment:
    Operating System: Linux
    Platform: PC
  • Bugzilla Id:
    4166

Description

1.8-head as of approx. 0:00 oct 13. link.log gets filled with :
[LinkdScheduler-5 Pool-fiber3] DbEventWriter: store: No nodeid found for next hop ip/0.0.0.0 Skipping ip route interface add to Linkable Snmp Node

None of my nodes has a default gw. Don't think that is the problem. The problem appears to be that (at least) cisco routers got an entry in the route table for connected interfaces, which points at 0.0.0.0.

Like this:
.iso.org.dod.internet.mgmt.mib-2.ip.ipForward.ipCidrRouteTable.ipCidrRouteEntry.ipCidrRouteNextHop.10.1.3.0.255.255.255.0.0.0.0.0.0 = IpAddress: 0.0.0.0
.iso.org.dod.internet.mgmt.mib-2.ip.ipForward.ipCidrRouteTable.ipCidrRouteEntry.ipCidrRouteNextHop.10.1.4.0.255.255.255.0.0.0.0.0.0 = IpAddress: 0.0.0.0
.iso.org.dod.internet.mgmt.mib-2.ip.ipForward.ipCidrRouteTable.ipCidrRouteEntry.ipCidrRouteNextHop.10.1.5.0.255.255.255.0.0.0.0.0.0 = IpAddress: 0.0.0.0

Activity

Hide
Permalink
Matt Brozowski added a comment -

Is the log message the only concern? or is there some other symptom that you are seeing. Please reopen with the additional information

Show
Matt Brozowski added a comment - Is the log message the only concern? or is there some other symptom that you are seeing. Please reopen with the additional information

People

  • Assignee:
    Donald Desloge
    Reporter:
    Dag Bakke
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: