Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Running an NPM Network Discovery Scan in NPM displays elements outside the subnet range

Running an NPM Network Discovery Scan in NPM displays elements outside the subnet range

Updated October 31, 2018

Overview

When you run a Network Discovery Scan in NPM using a subnet range, the scanned results include elements that are outside the assigned subnet range. 

Environment

  • NPM 12.x

Cause

The Hop Count option is set to > 0 in the Discovery Settings step. This causes the scan to go beyond its initial range, depending on the number of hops.

Resolution

  1. Edit the Discovery Profile and click Next until the DIscovery Settings page displays.
  2. In the Hop Count slider, verify that the value is set to '0' (zero).
  3. Click Next.
  4. Re-run the scan.

 

Last modified

Tags

Classifications

Public