Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Before you begin:
The first time you discover your network, SolarWinds recommends adding a limited number of edge routers or switches, firewalls and load balancers (if you have them), and critical physical or virtual servers and hosts.
Add nodes with high latency one at a time.
As you scale your implementation, you can use the following scanning options.
|IP Ranges|| |
Use this option when you want Orion to scan one or more IP ranges.
If you have many IP ranges to scan, consider adding multiple discovery jobs rather than including all ranges in a single job.
Use this option to scan every IP address in a subnet. SolarWinds recommends scanning at most a /23 subnet (512 addresses max).
Scanning a subnet returns everything that responds to ping, so we recommend only scanning subnets where the majority of devices are objects you want to monitor.
|IP Addresses|| |
Use this option for a limited number of IP addresses that do not fall in a range.
Since a network discovery job can take a long time to complete, SolarWinds recommends using this option when you are first starting out.
|Active Directory|| |
Use this option to scan an Active Directory Domain Controller.
Using Active Directory for discovery is particularly useful for adding large subnets because Orion can use the devices specified in Active Directory instead of scanning every IP address.
This setting ensures that any agents you deploy, including the one on your Orion server, are up-to-date. If there are no nodes using agents, you can leave this option unchecked.
If you do not add the host credentials, Orion still discovers the virtual machines (VMs) on the host. However, you will not be able to see the relationships mapped between the VMs and hosts.
SolarWinds recommends that you monitor Windows devices with WMI instead of SNMP.
When you scale monitoring, you can configure discovery to automatically start monitoring objects it finds.
Discovery can take anywhere from a few minutes to a few hours, depending on the number of network elements the system discovers.