There is also a ping sweep tool built in to Device42. The open source, standalone ping sweep tool uses NMAP in the background to run ping sweeps against the selected network(s), uploading discovered IP, MAC, & reverse DNS details via Device42's the RESTful APIs the tool is written in. To run an SNMP v1/v2c/v3 discovery against any SNMP-compatible endpoint, see the SNMP section of the SNMP/Network Discovery DOCS page. UPS, ATS, and other SNMP-compatible network-connected hardware Many environmental sensors also support SNMP discovery/polling. SNMP discoveries can also be used to discover many other types of devices: Power devices are usually discovered using SNMP, e.g. 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 Īnother Puppet integration script is available on API Autodisc repo that reads the YAML factor files and populates inventory details in Device42 using the RESTful API. SNMP Network discovery is covered in more detail at: discovery/network-auto-discovery.mdx Node data from Chef and Puppet Switch port status and remote port associations.Using SNMP v1/v2c/v3 discovery for network devices, you can automate discovery of: VMWare hypervisor host and guest VM details are discovered using appropriate APIs SNMP. ![]() Linux machines inventory details are discovered via SSH.Windows-based machine inventory details are discovered with WMI.Hypervisors, Windows & Linux/UNIX discovery jobs can all be created using the main menu, Discovery -> HyperVisors / *nix / Windows. Hypervisor / *nix / Windows Autodiscovery It can be run and/or scheduled from the Device42 web UI: Discovery > DNS Zone Sync (One way). Cloud discovery details can be found here: Cloud Platforms Autodiscovery DNS Autodiscovery ĭNS autodiscovery is built into Device42, and can do zone transfer(s) from your DNS server(s). Details can be found at: cisco-ucs-auto-discovery Cloud Platform Discovery Ĭonnect to Amazon AWS, Alibaba Cloud, Microsoft Azure, Digital Ocean, Google Cloud, Linode, and Openstack from the cloud discovery under Discovery > Cloud. You can grab chassis, blade, service profile information, and more. This is discussed in more detail at: Blade Systems Autodiscovery. HP & IBM Blade System (or Blade Center) chassis and blade details can be discovered using SNMP. Whether remote collectors can’t be deployed or policy simply doesn’t allow it, we've got the solution: See the Device42 Offline Agent-based discovery page here, or simply click here to download the Offline Discovery Data Processing Tool / Agent Log Upload Utility. There are some edge cases where discovery is desired but the network (or lack of network!) doesn’t allow communication back to the main Device42 appliance (for a variety of reasons). Agent-based Offline Discovery & Upload Tool Learn more on the Device42 Agent-based discovery docs page. There exist special situations in which an agent simply makes more sense, and for that reason, we over optional autodiscovery agents for many platforms. Click the ellipse menu in edit mode and then click Clone Job.Įnter a New Name for the cloned job and click Create. Click on a discovery Job Name in a View listing to select the job you want to clone and then click Edit. ![]() You can then modify the cloned job for your specific purposes. You can now clone an autodiscovery job while editing it to create a copy of the job with all its settings, which lets you replicate the job without having to manually re-enter all the job details. You, the customer, are responsible for any such behavior that might result if you choose to ignore this requirement. WARNING: Please do not set up an autodiscovery / 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. In this case, you can simply manually add relevant subnets before re-running the discovery. Note that this is not a requirement, but that if IPs are discovered before adding subnets, those IPs will end up in a "catch-all" subnet named "undefined". By discovering your network first, you bring in the in-use subnets that will contain all of the to-be-discovered IP addresses and construct the layer 2 framework by discovering VLANs with live MAC addresses. ![]() Running network discovery first is recommended, and is important because it lays the framework for rest of your discoveries. You may run the autodiscovery tools in any combination and/or order that makes sense for your environment, and all can be run on a regular schedule, thus enabling the automation of a significant portion of your network documentation. Autodiscovery Device42 Autodiscovery jobs ĭevice42 offers a number of different autodiscovery tools, some of which are internal to Device42 while some run externally, as discussed below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |