SMARTS NCM 9.2.2.a: Job Failed with error UNKNOWN ENGINEID when attempting to rediscover swapped hardware; SNMPv3 credentials cached, causing invalid engineID errors when replacing a device

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


SNMPv3 engineID's cached preventing autodiscovery of devices where the actual hardware had been swapped out.


The issue is resulting when the cached engine ID is different from what is defined on device. Code has been modified to refresh the cache whenever there is a change in device engine ID.

Smarts NCM caches SNMPv3 engineID for the devices in question. If the hardware is swapped out, the cached engineID is incorrect for the new hardware so the autodiscovery fails with the errors:

Job Failed with error UNKNOWN ENGINEID;
Valid Credentials Found, but could not determine driver;

Environment

VMware Smart Assurance - NCM

Resolution

Permanent fix:

This is a bug in the Smarts NCM 9.2.2.a code and has been resolved in Smarts NCM version 9.2.2.a.2 or later.

The code has been modified to refresh the cache whenever there is a change in device engine ID.

Workaround (For Smarts NCM 9.2.2.a):

A restart of the relevant Smarts NCM Device Server (DS) will resolve the issue using the command:

service voyence restart