Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

No nodeid found for next hop ip/0.0.0.0

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

Environment

Operating System: Linux Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Matt Brozowski September 20, 2011 at 4:05 PM

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

Incomplete

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created October 13, 2010 at 9:38 AM
Updated January 27, 2017 at 4:21 PM
Resolved September 20, 2011 at 4:05 PM

Flag notifications