Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Volumes of existing nodes are not processed in the importing process of network discovery

Volumes of existing nodes are not processed in the importing process of network discovery

Table of contents

Updated April 28th, 2016


The import process of the Network Discovery finds the nodes, but fails to import the new volumes found during the discovery process.

Import Status: not processed.


New volumes found are not imported as the Parent Nodes already exist in Orion.


Setting up a Discovery Profile with only the Windows credentials should discover the volumes for existing WMI or new WMI nodes.

  1. Click Web Console > Settings > Network Sonar Discovery.
  2. Click Add New Discovery.
  3. Delete the SNMP credentials in step 1, and click Next.
  4. For the WMI credentials in step 3, click Add New Credentials.
  5. Click Add after entering the details of the new windows credentials.
  6. Click Next.
  7. Provide the IP range of the Network, and then click Next.
  8. Change the Discovery Settings to the desired value, and then click Next.
  9. Choose the option No, don't run now for the Discover Scheduling.
  10. Click Save.
  11. Click Discover Now to verify if the volumes are added.
Last modified