Existing adjacency candidate data in db is not deleted if a device's CDP cache or LLDP remote table becomes empty
Bug #1447999 reported by
Morten Brekkevold
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Network Administration Visualized |
Fix Released
|
High
|
Morten Brekkevold | ||
Bug Description
If a device's CDP cache table goes from having entries to being empty, ipdevpoll will not delete the corresponding AdjacencyCandidate records.
This is because the sentinel that tells the AdjacencyManager that CDP has been processed is only posted by the ipdevpoll CDP plugin if the CDP cache table had any entries.
This may cause stale topology data to remain in NAV indefinitely, even when the corresponding interfaces are shutdown.
This may also be the case for LLDP; the LLDP plugin should also be examined.
Revision history for this message
| Morten Brekkevold (mbrekkevold) wrote | #1 |
| summary: |
- Existing CDP data in db is not deleted if a device's CDP cache table - becomes empty + Existing adjacency candidate data in db is not deleted if a device's CDP + cache or LLDP remote table becomes empty |
Revision history for this message
| Morten Brekkevold (mbrekkevold) wrote | #2 |
| Changed in nav: | |
| status: | In Progress → Fix Committed |
| Changed in nav: | |
| milestone: | 4.2.7 → 4.3.0 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
confirmed to be a problem for LLDP too.