Bug #2785
closedNamePrefixTableEntry loses origin router
100%
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.