Discovery Manager

Discovery Options

There are two concurrent discovery queues.

• High Priority Queue - For devices in the high priority discovery queue, SevOne NMS first discovers the device that was most recently queued with the high priority followed by the other devices in the high priority queue in the last in first out sequence.

• Low Priority Queue - For devices in the low priority discovery queue, SevOne NMS first discovers the device that has been in the low priority queue the longest in the first in first out sequence.

There are two discovery processes.

• Manual Discovery - The Manual Discovery process runs every two minutes to discover objects such as interfaces, CPUs, and their indicators on the devices you manually mark for discovery on the Device Manager. Typically the Manual Discovery process runs in the high priority queue but you can choose to decrease the Manual Discovery process to the low priority queue.

• Automatic Discovery - The Automatic Discovery process runs as you schedule it to occur on the Cluster Manager > Peer Settings tab to discover interfaces, CPUs, etc. on all devices in SevOne NMS even if you do not mark the device for discovery. Automatic Discovery runs in the low priority discovery queue.

Manage Discovery

The Discovery Queue tab displays the following information. Select the check box for each device on which to stop discovery and click Cancel Selected to stop discovery.

• Device Name - Displays the device name.

• Queue - Displays Low for the low discovery queue or displays High for the high discovery queue.

• Last Start Time - Displays the time the discovery process started.

• Peer – Displays the name of the peer that performs the discovery and polls the device.

• Core - Displays the identification of the core discovery process. A core discovery process spawns multiple discovery threads. Threads with the same Core ID are created by the same process.

• Thread - Displays the identification of the thread that is currently performing the discovery action. A thread only discovers one device and then the thread is destroyed.

• CPU % - Displays the percentage of CPU usage when the device is discovered.

• Mem % - Displays the percentage of memory that the discovery action consumes. Discoveries with abnormally high memory usage may indicate a problem with the polled device. The discovery thread terminates when it consumes too much memory.

Manage Subnets

The Watched Subnets tab enables you to create any number of subnet blocks and IP address ranges to scan your network on a regular schedule for items that can be pinged.

• Click Cancel Scan to cancel all scans that are currently in progress or select the check box for specific subnets and click Cancel Scan.

• Click Scan Now to start a scan of all subnets or select the check box for specific subnets and click Scan Now.

Perform the following steps to manage subnets scans.

1. Click Add Subnet or click to display the Add/Edit Subnet pop-up.

2. In the Subnet Name field, enter the name of the subnet block or IP address range.

3. Click the Peer drop-down and select the peer that is to send out the ping commands to the network segment.

4. Click the Action drop-down.

   • Select Add Device to add everything that is able to be pinged to the Device Manager for object discovery and data polling.

   • Select Add Candidate to display everything that is able to be pinged on the Candidates tab where you can select specific candidates to add to the for object discovery and data polling. No metrics are collected from candidates.

5. Select the Check SNMP check box to check for SNMP on all devices being scanned.

6. Click Schedule to display the Scan Time pop-up. If you do not schedule the subnet scan, the scan occurs only when you click Scan Now.
   

   1. Click the Days tabs to scan the network on the dates that appear with a darker shade. Click Weekends to scan on weekend and/or click Weekdays to scan on weekdays.

   2. Click the Start Time drop-down and select the time to start the scan.

   3. Click the Time Zone drop-down and select a time zone.

   4. Click Add to add the scan time to the Selected list.

   5. Repeat these steps to add additional scan times. Each scan time must be unique.

   6. Click Save to save the scan times.

7. Select one of the following options:
   

   • Select IP Address Range to create an IP address range and perform the following steps.

     1. In the Start IP Address field, enter the low end of the IP address range.

     2. In the End IP Address field, enter the high end of the IP address range.

   • Select Subnet Block to create a subnet block and perform the following steps.

     1. In the IP Address field, enter an IP address.

     2. In the Subnet Mask field, enter a subnet mask.

8. Select the Create Device Group for Subnet check box to create a device group for the devices you add to SevOne NMS as a result of the scan for the subnet.

9. Click Add to add the block or range to the list to watch.

10. Repeat the previous steps to create additional ranges.

11. If you do not schedule the subnet to scan on a regular basis, select the check box for the subnet and click Scan Now. If you schedule the subnet to scan on a regular basis, the subnet is scanned on the schedule you define until you remove the subnet.

Candidates List Filters

Perform the following steps to filter the candidates that display in the list.

1. Select the check box for each candidate to manage, click , and select the following options.

   • Select Block to prevent the candidate from being promoted to as device in SevOne NMS.

   • Select Unblock to enable users to promote the candidate to a device in SevOne NMS.

   • Select Remove to remove the candidate/device from the list. The candidate/device can reappear in the list the next time a scheduled scan occurs.

2. Click Hide Devices to remove the devices SevOne NMS currently monitors and polls from the display or click Show Devices to display the devices that are in SevOne NMS in the list.

3. Click Hide Blocked to remove the candidates you block from the list or click Show Blocked to display the candidates you block in the list.

4. Select the check box for each candidate you want to promote to a device in SevOne NMS and click Add Devices to add the candidates as devices in SevOne NMS. When the device is in SevOne NMS, its objects are discovered and metrics are polled for reports and alerts. When the Status column displays In SevOne NMS you cannot re-add the device.

Candidate List

Candidates are grouped by the subnet scan that found the candidate and enable you to contract or expand each subnet group section. Click on a row to display additional information. The Edit Device topic describes this additional information. For a candidate, the additional information section enables you to add the candidate as a device and to edit the SNMP settings to attempt to detect SNMP availability. If you choose to add a candidate to SevOne NMS, you can change these settings on the Edit Device page.

• Candidate Name – Displays the candidate/device name.

• IP Address – Displays the candidate/device IP address.

• Pingable – Displays when SevOne NMS can ping the candidate/device or displays when SevOne NMS cannot ping the candidate/device.

• SNMP – Displays when you enable the candidate/device to send SNMP data to SevOne NMS or displays when SevOne NMS cannot detect SNMP availability on the candidate/device. For details, please refer to section Enable SNMP in SevOne NMS System Administration Guide.

• Peer – Displays the name of the peer that would discover and poll the device if you were to add the candidate to SevOne NMS.

• Status – Displays one of the following.

  • Candidate – Black normal font indicates this is a candidate. No objects are discovered and no metrics are polled for reports or alerts from a candidate. You must add the candidate as a device to SevOne NMS if you want to poll the objects on the device for metrics to include in reports and alerts.

  • In Progress – This candidate is being added as a device to SevOne NMS but no objects have been discovered on the device and no poll metrics are available for reports or alerts.

  • In SevOne NMS – Blue italic font indicates the device is in SevOne NMS and data is being polled and monitored for reports and alerts. The Device Manager displays all devices in SevOne NMS.

  • Blocked – Red italic font indicates a candidate is blocked and you cannot add the candidate as a device to SevOne NMS.

• Click next to a candidate to edit the IP Address and Peer columns and to display additional information.

• The additional information section on the right displays the settings that would be used in the device configuration should you choose to add the candidate as a device in SevOne NMS. The additional information provides the following buttons.

  • Click Add Device to add the candidate as a device in SevOne NMS. You can then edit these configuration settings on the Edit Device page.

  • Click Edit SNMP Settings to edit the candidate SNMP settings.

Add Candidates

Perform the following steps to add a single candidate to the list. See the Import Multiple Candidates section below to import multiple candidates via a .csv import wizard.

1. Click Add Candidate to display the Add Candidate pop-up.

2. In the IP Address field, enter the IP address of the candidate.

3. In the Candidate Name field, enter the name of the candidate.

4. Click the Peer drop-down and select the peer to scan for the candidate and to monitor the candidate if you add the candidate to SevOne NMS as a device.

5. Click the SNMP Version drop-down and select the SNMP version the candidate uses.

   • For SNMPv1 and SNMPv2, in the SNMP Read Community String field, enter the SNMP read community string for SevOne NMS to use to monitor the candidate should you choose to add the candidate as a device.

   • For SNMPv3, perform the following steps.

     1. In the SNMP Username field, enter the user name SevOne NMS needs to authenticate onto the device.

     2. Click the SNMP Authentication Type drop-down.

        • Select None (usmNoAuthProtocol) to not use an authentication method to send or receive messages.

        • Select MD5 (usmHMACMD5AuthProtocol) to use MD5 authentication protocol for messages.

        • Select SHA (usmHMACSHAAuthProtocol) to use SHA authentication protocol for messages.

     3. If you select MD5 or SHA in the previous step, in the SNMP Password field, enter the password SevOne NMS needs to authenticate onto the device.

     4. Click the SNMP Encryption Type drop-down.

        • Select None to not use encryption to send or receive messages.

        • Select AES to use the Advanced Encryption Standard encryption method.

        • Select DES to use the Data Encryption Standard encryption method.

     5. If you select AES or DES in the previous step, in the SNMP Encryption Key field, enter the localized key the authentication protocol on the device requires to authenticate messages.

     6. In the SNMP Context Name - (Optional) Enter the SNMP context name which defines a collection of management information that is accessible to an SNMP entity. Context can be a physical or logical system, a collection of multiple systems, or even a subset of a system.

6. Click Save.

Import Multiple Devices and Candidates

The Import CSV wizard enables you to import multiple devices and candidates. On the Candidates tab click Import CSV to display the Import CSV wizard.

You must use the Previous and Next buttons on this wizard to navigate the pages sequentially.

Notes List Filters

The Filters section enables you to define the notes to appear in the list. You must select a device and click Apply Filter to display notes. After you select a device, all other filters are optional and cumulative.

If a device has more than 3500 notes that meet your filter criteria, notes are exported to an .html format file.

1. Click Filters to expand the Filters section.

2. Click the Filter by drop-down and select an option to filter by Device or Device Group.

   1. Device

      • Click the Device drop-down and select one or more devices.

   2. Device Group

      • Click the Device Group drop-down and select one or more device groups.

3. All other filters are optional and cumulative.
   

   • Click the Severities drop-down and select each note severity level to display. The default Cluster Manager > Cluster Settings tab creates discovery notes for all severities except the Debug level.

   • Click the Time Span drop-down and select a time span.

   • Click the Time Zone drop-down and select a time zone.

   • In the Search field, enter the keywords to search on.

   • Select the Display Notes Added by Users check box to display notes users add for the device.

   • Select the Display notes added by discovery check box to display notes discovery creates.

   • Select the Display Object Configuration Changes Created During Discovery check box to display notes the object generates that pertain to configuration changes that occur during discovery.

4. Click Apply Filter.

Notes List

The notes list displays the notes that meet your filter criteria, color coded by severity. Notes can have eight severity levels and the Cluster Manager > Cluster Settings tab enables you to define which severity levels are to create notes.

• Device Name - Displays the device name.

• Severity – Displays the note severity.

• Time – Displays the note creation time.

• Message – Displays the note content.

• Actions - Click on to view the entire message when the note exceeds the allotted space.

Manage Notes

You can export the list of device notes to an .html format or to a .csv format.

• Click Export HTML to export the notes to an .html file. When there are more than 3500 notes that meet your filter criteria, notes export even if you do not click this.

• Click Export CSV to export the notes to a .csv file.

Perform the following steps to add a note. Notes you add have the Notice severity level.

1. Click Add Note to display the Add Note pop-up.

   Add Note is only available for a single device selection.

2. Enter the note text.

3. Click Save.

   The (manually added) Message in the Notes section can be viewed, edited, or deleted.

Install QoS Discovery Hooks

To install QoS Discovery Hooks, from the command line interface (CLI), execute the following command from any SevOne NMS peer.

View Installed QoS Discovery Hooks

To view the installed QoS Discovery Hooks, execute the following command.

Uninstall / Disable QoS Discovery Hooks

To uninstall or to disable the QoS Discovery Hooks, execute the following commands.