Submit a ticketCall us

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.

 

 

 

 

Home > Success Center > Server & Application Monitor (SAM) > Server & Application Monitor Getting Started Guide > Discover > Discover your servers and applications

Discover your servers and applications

Table of contents
No headers
Created by Chris.Moyer, last modified by Anthony.Rinaldi on Aug 23, 2016

Views: 2 Votes: 1 Revisions: 6
 

Discovery is a term used to describe the process SolarWinds Orion uses to identify application servers and applications. Before you begin:

The first time you run discovery, SolarWinds recommends adding a limited number of application servers, including Exchange, IIS, SQL, Linux, and Unix. The examples in this guide focus on monitoring IIS and the operating system of your application server, but the same steps are applicable to monitoring any application.

After discovery, if the status of a node is Unknown, you may need to check a few settings in SolarWinds SAM. See Troubleshoot Unknown Nodes for more information.

  1. If the Discovery Wizard does not start automatically after configuration, click Settings > Network Discovery.
  2. Click Add New Discovery, and then click Start.
  3. On the Network panel, if this is your first discovery, add a limited number of IP addresses.

    As you scale your implementation, you can use the following scanning options.

    Option Description
    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.

    Subnets

    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.

    File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/030/020/IP_Range.png

  4. The Agents panel appears. The QoE agent monitors packet-level traffic. If there are any nodes using agents, select the Check all existing nodes.

    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.

  5. On the Virtualization panel, to discover VMware vCenter or ESX hosts on your network, enter the credentials, and click Next.
  6. On the SNMP panel, to monitor an SNMP-enabled device, enter the credentials, and click Next.
  7. On the Windows panel, to discover WMI or RPC-enabled Windows devices, click Add New Credential and provide the required information.

    SolarWinds recommends that you monitor Windows devices with WMI instead of SNMP.

    File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/030/020/WMI.png

  8. On the Monitoring Settings panel, SolarWinds recommends manually setting up monitoring the first time you run discovery. This allows you to review the list of discovered objects and select the ones you want to monitor.

    When you scale monitoring, you can configure discovery to automatically start monitoring objects it finds.

    File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/030/020/MonitorSettings.png

  9. On the Discovery Settings panel, click Next.
  10. Accept the default frequency and run the discovery immediately.

    File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/030/020/DiscoveryScheduling.png

    Discovery can take anywhere from a few minutes to a few hours, depending on the number of application servers the system discovers.

    File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/030/020/DiscoveryStatus.png

 
Last modified
15:42, 23 Aug 2016

Tags

Classifications

Public