1. Home
  2. OmniCenter Reference
  3. Device Autodiscovery

Device Autodiscovery

OmniCenter’s autodiscover feature periodically scans your network for the addition of new devices (roughly every hour). Any new devices discovered during a scan that respond to SNMP or WMI and are not currently managed by OmniCenter will be automatically added and have the “Default” device template applied to them. The range of time during which OmniCenter performs its scans are controlled by a scheduling system. By default, OmniCenter is scheduled to scan for new devices 24 hours per day, every day. However, this schedule can easily be changed by an administrator.

Any subnet that is part of an RFC-1918 private address range (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) with a subnet mask of /22 (255.255.252.0) or longer will be automatically enabled for autodiscovery scanning. Larger subnets (or those with public addresses) will need to be manually enabled before OmniCenter will scan them. To prevent OmniCenter from attempting to scan the Internet, the subnet scanner won’t attempt to scan any subnets larger than class B.

Caution

Be sure you only enable autodiscovery scanning for subnets which you control or own. Scanning subnets on the Internet may be considered abusive behavior by your ISP and result in you being sanctioned or even disconnected.

OmniCenter runs its subnet scanner to look for new devices roughly every hour, within the scheduled autodiscovery times. As it discovers devices that are candidates to be monitored, it test communicates with these devices (via SNMP and Windows networking) using all of the credentials provided in the Device Discovery Wizard and any device templates that contain them, in the order in which they are provided. If any of the credentials work for a given device, and OmniCenter can identify that device as a type of device that is manageable, the device is added to OmniCenter and automatically configured (using autoconfiguration rules and device templates). If OmniCenter is not able to successfully authenticate with a device, that device is not added to OmniCenter. Devices that are not added wait in a queue to be rechecked every 5 minutes. If credentials become available that work, any applicable devices are then added to OmniCenter as above. (Devices running non-server operating systems will not be automatically added to OmniCenter. These kinds of devices may be added to OmniCenter manually, if desired, by using the device addition Manual Add tab. See the Add a Device Page.)

Any devices that OmniCenter is able to successfully discover and begin monitoring have an action group called “Default Email Alerts” added to their “Host Alert Contacts” list. This group is configured with the contact information provided in the “Default Host Alert Contact” section of the Device Discovery Wizard. This allows the provided contact to be alerted by email in the case of host failures, even if no other action groups are configured.

If you did not configure a default contact in the Device Discovery Wizard, downed-host alerts will not be sent unless you explicitly configure them for each device.

You can also provide OmniCenter with the IP address and credentials for a hypervisor server from which to discover your virtual environment. The current options allow you to select from either a vCenter or Hyper-V hypervisor type. OmniCenter uses the provided server to discover virtual hosts, guests and datastores which it can then automatically configure and monitor. Hypervisors can be added in the Device Discovery Wizard or on the Virtualization Administration page.

Updated on April 9, 2020

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Leave a Reply