Project

General

Profile

Actions

Bug #2785

closed

NamePrefixTableEntry loses origin router

Added by Vince Lehman almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
Start date:
05/04/2015
Due date:
% Done:

100%

Estimated time:

Description

John has reported an issue where other routers are losing the name prefix of certain routers. When looking through the logs for the NamePrefixTable, I saw that the problem name prefixes did not have an origin router associated with them. When the routing table calculation is performed, since the name prefix does not have an origin router associated with it, no next hop is installed for the name prefix.

The issue appears to happen when a router receives an update for an old LSA, installs the LSA, the LSA immediately expires, and the removal causes an incomplete deletion of the NamePrefixTableEntry. When the up to date Name LSA is received, the origin router is not added to the existing NamePrefixTableEntry and so the name prefix is never installed with next hops.

Actions #1

Updated by Vince Lehman almost 9 years ago

  • Status changed from New to Code review
  • Assignee set to Vince Lehman
  • % Done changed from 0 to 90
Actions #2

Updated by Vince Lehman almost 9 years ago

  • Target version set to v0.2.1
Actions #3

Updated by Vince Lehman almost 9 years ago

  • Status changed from Code review to Closed
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF