Smarts NCM: Unable to create discovery job for network, so no new devices can be discovered into that network

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Cannot create an auto-discovery job created for a particular network in Smarts NCM environment, so no new devices can be discovered into that network.


The following conditions, events or system behaviors may be observed with this issue:

• Receive an error message when trying to create any auto-discovery job in Smarts NCM
• Receive error message trying to add, edit, or access auto-discovery jobs in Smarts NCM
• Receive network not found error message when trying to discover devices in Smarts NCM

Environment

VMware Smart Assurance - NCM

Cause

This issue can be caused by outdated records in the cm_net_deviceserver_assoc table. Outdated records in this table may be caused by trying to remove a device server from Smarts NCM that is not 100% successful. The above issue will occur if outdated records in this table are associating a valid network with an invalid device server.

Resolution

To address this issue, verify the entries in the cm_net_deviceserver_assoc table in the database. This can be done as follows:

1. Connect and login to the Postgresql database (see Notes).
2. Run the following query to retrieve and review all records in the cm_net_deviceserver_assoc table:

select 

device_server_name as DS_NAME,

device_server_idx as DS_IDX,

encode(NDA.device_server_id,'hex') as Device_Server_ID, 

encode(NDA.net_ds_assoc_id,'hex') as Network_ID,

network_name

from cm_net_deviceserver_assoc as NDA

join cm_device_server on (NDA.device_server_id = cm_device_server.device_server_id)

join cm_network on (NDA.network_id = cm_network.network_id);

Additional Information

If you do not know how to log into the Smarts NCM postgresql database, see the following EMC article:

Smarts NCM or VoyenceControl: How do I log in to the PostgreSQL (Postgres) Control Database?