Smarts IP/AM: "FirstDiscoveredAt" dates for previously discovered devices in topology change to today's date; Receive flood of "Interface Down" alarms from all routers in Smarts IP domain

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:




FirstDiscoveredAt dates for previously discovered devices in Smarts IP topology change to today's date
FirstDiscoveredAt dates for each device in a Smarts IP topology change to today's date, even though the devices had previously been discovered by Smarts at an earlier date

All the FirstDiscoveredAt dates for each device in a Smarts IP topology change to the date on which the discovery is run, even though the devices had been previously discovered by Smarts at an earlier date

Receive flood of Interface Down alarms from all routers in Smarts IP domain

Following a full Smarts IP discovery, there is a flood of alarms (200+) from devices in the IP topology

Environment

VMware Smart Assurance - SMARTS

Cause

This issue occurs when the Smarts IP domain is re-started and the --clean-topology flag is set. With the --clean-topology flag set, the repository file is not read from disk into memory, so Smarts will discover the devices with an empty new repository, and all interfaces which are administratively down will generate alarms.

Resolution

To prevent this issue, do not use the --clean-topology flag unless you want Smarts not to read your existing topology into memory.