Adding a new interface to a device but Change Detection (CD) failed to detect it.
This required manually selecting "Update Metric Families" to get the new interface added to the view.
DX NetOps CAPM Release : 20.2 or later
If the following conditions are met, we will disable change detection (CD) on that specific metric family (MF) on that specific device.
When update MF runs (either manually or via change detection schedule), we first discover what VC to use.
We will read the OIDs needed for component discovery.
If we determine that the VC(s) supported changed on the metric family, we kick off a FIRST_VC_Verify stage that runs in 5 minutes from the initial read.
After we get back the OIDs needed for component discovery, we compare them to the existing components.
If we determine this will result in Not Present items being created, we do a SECOND_VC_VERIFY stage that runs in 5 minutes from the first verify.
To prevent a situation where critical devices are not being updated by change detection, you can check a REST endpoint on the DA to monitor and correct any devices that are disabled:
Replace YOUR-DA with the name of your DA.
<FilterSelect xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="filter.xsd">
<Select use="exclude" isa="exclude">
This should return something similar to:
<Name>device A name</Name>