Clearing the next IDX number on the Device Server

Products

• VMware Smart Assurance

Issue/Introduction

When DB restoration happens, there are chances that IDX gets corrupted and needs IDX queue clear in NCM DS (Device Server).

This IDX corruption will cause overwrite of device in NCM meaning all newly discovered devices will be assigned with old IDX/existing IDX. 

Environment

NCM - 10.1.x

Resolution

• In UI :

  • Check and make sure there are no running jobs

• In DS:

  • Log into the CLI on the Device Servers with 'root' access.
  • source /etc/voyence.conf
  • Delete ad_nextIdx and ad_numIdxIHave from $VOYENCE_HOME/data/devserver/configuration directory.
  • Restart vcmaster service.

Additional Information

In certain use case, AS infraDB needs correction.

• Login to NCM AS (Application Server) with 'root' access.
• source /etc/voyence.conf
• Navigate to $VOYENCE_HOME/cgi-bin
• Run ./cflist.cgi > AS.txt
• Remove entry of devices which are overwritten in NCM due to IDX corruption.