Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > User Device Tracker (UDT) > UDT Administrator Guide > Discover and add network devices > Add multiple devices (Network Sonar Discovery)

Add multiple devices (Network Sonar Discovery)

Table of contents
No headers
Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Jan 17, 2017

Views: 78 Votes: 0 Revisions: 2

SolarWinds products employ the easy-to-use Network Sonar Discovery Wizard to direct you in the discovery of devices on your network. Before using Network Sonar Discovery, consider the following points about network discovery in SolarWinds UDT:

  • The Network Sonar Discovery Wizard recognizes network devices that are already in your Orion Platform database and prevents you from importing duplicate devices.
  • CPU and Memory Utilization charts are automatically enabled for your Windows, Cisco Systems, VMware, and Foundry Networks devices.
  • The community strings you provide in the Network Sonar Discovery Wizard are only used for SNMP GET requests, so read-only strings are sufficient.

The following procedure is done to discover devices on your network using the Network Sonar Discovery Wizard.

  1. If the Network Sonar Discovery Wizard is not already open, click Start > All Pograms > SolarWinds Orion > Configuration and Auto-Discover > Network Discovery.
  2. If you want to create a new discovery, click Add New Discovery.
  3. If you have already defined a network discovery, a number of options are available on the Network Sonar Discovery tab. Select one of the following:
    • If you want to edit an existing discovery before using it, select the discovery you want to edit, and then click Edit.
    • If you want to use an existing discover to rediscover your network, select the discovery you want to use, click Discover Now, and then complete the Network Sonar Results Wizard after discovery completes.
    • If you want to import some or all devices found in a defined discovery that you may not have already imported for monitoring, select a currently defined discovery, and then click Import All Results.
    • If you want to import any newly enabled devices matching a defined discovery profile, select a currently defined discovery, and then click Import New Results.
    • If you want to delete an existing discovery profile, select a currently defined discovery, and then click Delete.
  4. If the devices on your network do not require community strings other than the default strings public and private provided by SolarWinds UDT, click Next on the SNMP Credentials view.
  5. If any of your network devices require community strings other than public and private or if you want to use an SNMPv3 credential, complete the following steps to add the required SNMP credential.

    Repeat the following procedure for each new community string. To speed up discovery, highlight the most commonly used community strings on your network, and then use the arrows to move them to the top of the list.

    1. Click Add New Credential and then select the SNMP Version of your new credential.
    2. If you are adding an SNMPv1 or SNMPv2 ccredential, provide the new SNMP Community String.
    3. If you are adding an SNMPv3 credential, provide the following information for the new credential:
      • User name
      • Content
      • Authentication Method
      • Authentication Password/Key
      • Privacy/Encryption Method
      • Password/Key (if required)
  6. Click add, and then click Next on the SNMP Credentials view.
  7. If you want to discover any VMware or ESX Servers on your network, confirm that Poll for VMware is checked, and then complete the following steps to add or edit required VMware credentials.

    Repeat the following procedure for each new credential. To speed up discovery, use the arrows to move the most commonly used credentials on your network to the top of the list.

    1. Click Add vCenter or ESX Credential.
    2. If you are using an existing VMware credential, select the appropriate credential from the Choose Credential dropdown menu.
    3. If you are adding a new VMware credential, select <New Credential> in the Choose Credential drop-down menu, and then provide a new credential name in the Credential Name field.

      SolarWinds recommends against using non-alphanumeric characters in VMware credential names.

    4. Add or edit the credential User Name and Password.
    5. Confirm the password, and then click Add.
  8. Click Next on the Local vCenter or ESX Credentials for VMware view.
  9. If you want to discover devices located on your network within a specific range of IP addressed, complete the following procedure.

    Only one selection method may be used per defined discovery.

    1. Click IP Ranges in the Selection Method menu, and then, for each IP range, provide both a Start address and an End address.

      Scheduled discovery profiles should not use IP address ranges that include nodes with dynamically assigned IP addresses (DHCP).

    2. If you want to add another range, click Add More, and then repeat the previous step.

      If you have multiple ranges, click X to delete an incorrect range.

    3. If you have added all the IP ranges you want to poll, click Next.
  10. If you want to discover devices connected to a specific router or on a specific subnet of your network, complete the following procedure:

    Only one selection method may be used per defined discovery.

    1. Click Subnets in the Selection Method menu.
    2. If you want to discover on a specific subnet, click Add a New Subnet, provide both a Subnet Address and a Subnet Mask for the desired subnet, and then click Add.

      Repeat this step for each additional subnet you want to poll.

    3. If you want to discover devices using a seed router, click Add a Seed Router, provide the IP address of the Router, and then click Add.

       

      • Repeat this step for each additional seed router you want to use.
      • Network Sonar reads the routing table of the designated router and offers to discover nodes on the Class A network (255.0.0.0 mask) containing the seed router and, if you are discovering devices for an SolarWinds NPM installation, the Class C networks (255.255.255.0 mask) containing all interfaces on the seed router, using the SNMP version chosen previously on the SNMP Credentials page.
      • Networks connected through the seed router are NOT automatically selected for discovery.
    4. Confirm that all networks on which you want to conduct your network discovery are checked, and then click Next.
  11. If you already know the IP addresses or host names of the devices you want to discover and include in the Orion Platform database, complete the following procedure:
    1. Click Specific Nodes in the Selection Method menu.
    2. Enter or paste in the IP addresses or host names of the devices you want to discover for monitoring into the provided field.

      Type only one IP address or host name per line. For more information on using a seed file, see Import a list of nodes using a seed File. For information on using the discovery Ignore List, see Use the discovery ignore list.

    3. Click Validate to confirm that the provided IP addresses and host names are assigned to SNMP-enabled devices.
    4. If you have provided all the IPaddresses and host names you want to discover> click Next.
  12. Configure the options on the Discovery Settings view, as detailed in the following steps.
    1. Provide a Name and Description to distinguish the current discovery profile from other profiles you may use to discover other network areas.

      This Description displays next to the Name in the list of available network discovery configurations on the Network Sonar view.

    2. Position the slider or type a value, in ms, to set the SNMP Timeout.

      If you are encountering numerous SNMP timeouts during Network Discovery, increase the value for this setting. The SNMP Timeout should be at least a little more than double the time it takes a packet to travel the longest route between devices on your network.

    3. Position the slider or type a value, in ms, to set the Search Timeout.

      The Search Timeout is the amount of time Network Sonar Discovery waits to determine if a given IP address has a network device assigned to it.

    4. Position the slider or type a value to set the number of SNMP Retries.

      This value is the number of times Network Sonar Discovery will retry a failed SNMP request, defined as any SNMP request that does not receive a response within the SNMP Timeout defined above.

    5. Position the slider or type a value to set the Hop Count.

      If the Hop Count is greater than zero, Network Sonar Discovery searches for devices connected to any discovered device. Each connection to a discovered device counts as a hop.

    6. Position the slider or type a value to set the Discovery Timeout.

      The Discovery Timeout is the amount of time, in minutes, Network Sonar Discovery is allowed to complete a network discovery. If a discovery takes longer than the Discovery Timeout, the discovery is terminated.

    7. If you only want to use SNMP to discover devices on your network, check Use SNMP only.

      By default, Network Sonar uses ICMP ping requests to locate devices. Most information about monitored network objects is obtained using SNMP queries.

  13. If multiple Orion polling engines are available in your environment, select the Polling Engine you want to use for this discovery.

    For nodes already being monitored within UDT, if you want to change the polling engine with which a node is associated, see Change polling engine node assignments.

  14. Click Next.
  15. If you want the discovery you are currently defining to run on a regular schedule, select either Custom or Daily as the discovery Frequency, as shown in the following steps:
    • Scheduled discovery profiles should not use IP address ranges that include nodes with dynamically assigned IP addresses (DHCP).
    • Default Discovery Scheduling settings execute a single discovery of your network that starts immediately, after you click Discover
    • Results of scheduled discoveries are maintained on the Scheduled Discovery Results tab of Network Discovery. For more information about managing scheduled discovery results, see Manage scheduled discovery results
    1. If you want to define a custom discovery schedule to perform the currently defined discovery repeatedly in the future, select Custom and then provide the period of time, in hours, between discoveries.
    2. If you want your scheduled discovery to run once daily, select Daily, and then provide the time at which you want your discovery to run every day, using the format HH:MM AM/PM.
  16. If you do not want to run your network discovery at this time, select No, don't run now, and then click Save or Schedule, depending on whether you have configured the discovery to run once or on a schedule, respectively.
  17. If you want your Network Sonar discovery to run now, click Discover to start your network discovery.

    Because some devices may serve as both routers and switches, the total number of Nodes Discovered may be less than the sum of reported Routers Discovered plus reported Switches Discovered.

After the Network Sonar Discovery Wizard completes the node discovery and imports results, if you click FINISH, you are taken directly to Discovery Central.

 
Last modified

Tags

Classifications

Public