Idea Details

Retain historical data after devices/components/history go inactive

Last activity 10-17-2017 09:17 AM
scottbossi's profile image
08-03-2017 05:24 PM



I've run into a fair number of situations where engineers or mgrs want to look at historical data for devices or elements that have gone inactive or retired.  For example, if an interface is flapping, turned down, and then replaced, people want to see a comparison of performance of the new vs. the old.  In current CAPM, this is not possible.  I'd like to see some ability to retain historical data for "retired" devices and elements.


10-17-2017 09:17 AM

Thank you for the idea, Scott.


A couple questions:

1) Are these inactive interfaces usually "not-present" meaning they are no longer represented in the ifTable with their previous ifIndex?

2) When an interface is replaced on a device, does the new interface have have a different ifIndex than the old interface it replaced?  If so, I assume CAPM doesn't correlate the new interface to the old one - is that correct?