3/11/2020 1:33 PM

6/25/2025 5:05 PM

Most common issues:

• NCM inventory job creating performance issues on the server and taking a long time to finish a task
• NCM inventory job will not start and hangs with the status "starting Job"
• Some nodes are taking a long time to complete inventory jobs
• Some nodes are failing to provide information or authentication on part of the inventory
• NCM inventory fails with some errors
• The polling engine does not show on the job log and inventory is not being run on that engine
• Device OIDs authentication failure
• Location of real time inventory job logs.
• Inventory is not performing DNS resolution

Network Configuration Manager

Most common issue

Avoid polling any Route Tables. Uncheck them, because nodes can have very large tables and this could delay completion for the Inventory job.

Please review the Inventory Settings and only select what you really need to poll from the nodes. (See the following steps.)

Troubleshot and isolate the inventory job issue

Create a brand new NCM inventory job. Add only 2 - 5 Cisco Nodes in the job, and select only the ARP option to poll:

If the issue is on a specific polling engine

• Does manual config download work for this polling engine?
• Does the Config Download Job work for these nodes on this polling engine?
• Does a ping test work between the main polling engine and this problematic polling engine?
• Do firewall rules block something? Could we turn off the firewall and see if the job works? (This might not be possible.)

Check the logs and monitor resources

Run the inventory job, and then check the general logs and job logs here:

C:\ProgramData\Solarwinds\Logs\Orion\NCM\Logging

Now add more nodes in the same job and check the results and outcome.

Track CPU and memory usage on the SolarWinds Platform server to make sure there are no resource constraints.

Also try disabling Windows Defender, because this can cause significant delays in writing the job logs and configs to the database.

Nightly Network Inventory failed with some errors

20-6-2019 14:39:59 - Inventory - 10.11.255.253 InventoryNode.SNMPReply: Error: Timeout

20-6-2019 14:39:59 - Inventory - ---------------------------ActiveNodes.InventoryFailure xxxxxxxxxxxxxxxx-192.168.1.1 Failure reason: Does not respond to SNMP queries using 'SNMP_COMMUNITY' Remaining nodes: 40

20-6-2019 14:39:59 - Inventory - 10.11.232.88 InventoryNode.SNMPReply: proceed reply for ,{A57292D6-8797-4CF5-9CE9-FD7DAD71217B},NCM_Entity_Physical,AssetID

20-6-2019 14:39:59 - Inventory - 10.11.232.88 InventoryNode.SNMPReply: OID: 1.3.6.1.2.1.47.1.1.1.1.15.6461 NCM_Entity_Physical:AssetID.6461=

Logs show the following for the inventory job:

 Job Engine: NCM

1-6-2019 23:00:09 : Started Nightly Network Inventory : JobDescription_10024d4c-9963-41d3-9f9a-fe271ab81f19

Disable this job, create a new job, and add only one node (for example, a Cisco node).

Deselect any Inventory Settings options that are not applicable.

Run this new inventory job, and determine if you still get the same error.

Add more nodes into the same job and keep checking the logs.

A device is sending Authentication Failure messages while Inventory Jobs are running

Is this node configured with SNMPV3?

SNMPv3 allows you to set up and assign groups and access with differing levels of security. Object IDs are associated with various levels of permissions, and a single view can be assigned to multiple objects. The figure below shows how access for groups and users are associated with these different permission levels. The SNMPV3 user might not be configured to access all of the OIDs for inventory. Therefore it is rejected by the device.

SNMPv3 Group Access with Different Permission Levels

Change the node to SNMPV2 and run the Inventory Job again and verify if you still have the same Authentication Failure Errors.

Run SNMPWALK and make sure the OIDs are actually present on the device.

Inventory not performing DNS resolution

NCM Inventory will not send ICMPO and DNS requests if this feature is disabled.

To turn it back on:

1. Go to Settings > All Settings > Product Specific Settings > NCM Settings > NCM Node Management > Node Inventory.
2. At the bottom of the page, select Disable inventory lookup.
   

NCM inventory polls IP addresses other than the polling IP address

Adjust the inventory settings. Increase the number of devices that should be inventoried concurrently as per the article: https://documentation.solarwinds.com/en/success_center/ncm/content/ncm-inventory.htm

If you still have the same issue after following all of the previous steps, open a SolarWinds Support ticket. See Tips and Tricks on opening a Support Ticket with SolarWinds.