Auto Discovery

Device42 provides a number of different auto-discovery tools. Some of these tools are internal to Device42 and some run externally as discussed below.

You can run the autodiscovery tools in any order and all can be setup to run on a regular schedule. This enables you to automate a significant portion of your network documentation.

We recommend running network discovery first, because it brings in the subnets that will contain discovered IP addresses and the VLANs that contain MAC addresses. However, this is not a requirement. If IPs are discovered before adding subnets, IPs will end up in a “catch-all” subnet named “undefined”. You can then manually add subnets before re-running the discovery.

WARNING: Please do not set up an auto-discovery / scan using critical production account credentials!

Depending on permissions granted & your configured password policies, account lock-out could result in an otherwise completely avoidable outage. You, the customer, are responsible for any such behavior that might result if you choose to ignore this requirement.

Blade Systems device discovery

HP & IBM Blade System (or Blade Center) chassis and blade details can be discovered using SNMP. This is discussed in more detail at: https://docs.device42.com/auto-discovery/hp-bladesystem-auto-discovery/

Cisco UCS Manager is supported as well. You can grab chassis, blades and service profiles information. More details at: https://docs.device42.com/auto-discovery/cisco-ucs-auto-discovery/

Cloud Discovery

You can connect to Amazon AWS, Microsoft Azure, Digital Ocean, Linode, Openstack, Outscale and CloudStack from the cloud discovey under Tools > Auto-discovery > Cloud. More details here: https://docs.device42.com/auto-discovery/cloud-auto-discovery/

DNS auto-discovery

Run from device42 appliance portal : Tools > Auto-discovery > DNS.

DNS auto-discovery is built-in into device42 and you can run/schedule it to do zone transfer from your DNS server(s).

Get node’s data from Chef and Puppet

Send Ohai node data from Chef server to Device42: Sync node data from Chef
Sync puppet facts to Device42: Script to sync Puppet nodes information

Another Puppet integration script is available on API Autodisc repo that reads the yaml facter files and populates inventory details in device42 using the REST API.

IPMI auto-discovery

Discover iLO, iDrac or ocher IPMI/BMC boards with basic hardware info and BMC IP and MAC address for a given IP range. If the server has already been discovered by OS level discovery methods, BMC IP and MAC address show up in device properties.

Discussed here in detail: https://docs.device42.com/auto-discovery/ipmi-auto-discovery/

Network / SNMP auto-discovery

Run from the device42 appliance portal : Discovery > Networking.

Using SNMP v1/v2c/v3 discovery for network devices, you can automate discovery of:

  • Network device inventory
  • Subnets/VLANs
  • IP to MAC associations
  • MAC to switch port associations
  • Switch port status and remote port associations.

This topic is discussed in more detail at : https://docs.device42.com/auto-discovery/setup-network-auto-discovery/

Ping sweep utility

The .net based, open source Ping Sweep client uses nmap in the background for a ping sweep on selected network(s) and uploads IP/MAC/reverse DNS info to device42 using the REST API.

Also, Discovery > Ping Sweep is another option within Device42 UI (the UI based option, may, in the future, be depreciated – Also note the standalone tool is much faster).

Remote Collector (RC)

The Device42 remote collector is a lightweight VM appliance that can be quickly deployed in, for example, secure network segments and tasked to run auto discovery jobs. A deployed Remote Collector (RC) can be assigned a given auto discovery job during that job’s configuration. Simply choose the desired RC from the “Remote Collector” dropdown when initially setting up a new auto discovery job, or editing an existing auto discovery job.

Most auto discovery jobs that can be launched from the Device42 Menu (Tools > Auto-discovery) support running from a deployed RC.

For more information, and full RC documentation, head to the dedicated Remote Collector page

Scripts for Linux, Solaris, Windows and Mac

If you don’t want to use the .Net discovery tool linked above, you can alternatively used our opensourced scripts on github.

For mac, linux and solaris auto-discovery, you can use this repo: https://github.com/device42/nix_bsd_mac_inventory

Windows discovery scripts here: device42 github repository.

Windows scripts use powershell 2.0/iPython to get individual windows details or windows machines from AD. Details are sent to device42 appliance using the REST API.

Linux, solaris and mac script is connecting to remote servers using ssh, collect inventory data and send data back to Device42 using REST API.

Using REST APIs

You can automate inventory management with other programs using the device42 RESTful APIs as discussed at : device42 apis.

VMware / Citrix XenServer / oVirt / Redhat Virtualization / KVM

Run from device42 appliance portal : Discovery > vServer.

This discovery tool can connect to vCenter server(s), ESX server(s), Citrix XenServer, oVirt or Redhat Virtualization Servers and get:
host inventory details and virtual machine details.

Discussed more at : https://docs.device42.com/auto-discovery/vmware-auto-discovery/

Windows and Linux auto-discovery

The Device42 Auto-Discovery Tool is a .NET based software application that runs externally on any windows machine and gathers:

  • Windows machines inventory details using WMI.
  • Linux machines inventory details using SSH.
  • Hyper-V Server and VM details using WMI.
  • SCCM information using WMI.

The Auto-Discovery tool allows you to build auto-discovery jobs for your environment with flexible options and scheduling. Please see our Device42 Auto-Discovery Tool Documentation for more information.