We are super excited to announce Cloud Inventory Management starting with v5.6. Device42 now supports Amazon AWS and Microsoft Azure instances. Device42 will auto-discover your cloud virtual machines, databases, and storage as devices. You can then work with your cloud devices just like other devices. You can define application components, store passwords, create custom keys, and so on, just like you do for physical or virtual devices. More details and other changes in v5.6.0 are discussed below
Cloud devices auto-discovery
The Tools > Auto-Discovery menu now has an option for Cloud instances. The list page shows your existing cloud auto-discovery jobs. You’ll typically have one job per account. As with other types of auto-discovery jobs, cloud jobs can be run immediately and/or scheduled. Click the Add Cloud Autodiscovery button to create a new job.
Auto-Discovery for Amazon AWS Instances
To create an AWS autodiscovery job, you will need to:
– Enter an arbitrary name for this job
– Choose the Cloud Type (currently, the two choices are Microsoft Azure and Amazon AWS but more will be added in the future)
– Enter your Amazon Account ID
– Add your Amazon Secret Key for this account. To do this, click the magnifying glass and then click Add Password. Here you can store the Secret Key encrypted and, if you’d like setup users and groups who can access this Secret Key.
– Choose one or more Amazon regions to search
Optionally, you can also:
– Choose the vendor
– Choose a VRF Group that the IPs will belong to (e.g. if you have overlapping IPs between your private and cloud IPs)
You can also run the job immediately or save it or save it have it run on a regular schedule.
If you check “Remove unfound instances from Device42”, then each time this auto-discovery job is run, any devices that were previously created for this account but were not found by the auto-discovery job will be deleted. By checking this box, you can ensure that Device42 will remain in sync with Amazon. If you leave it unchecked, then you may end up with Device42 Cloud Instances (cloud devices) that no longer exist in Amazon AWS.
Auto-Discovery for Microsoft Azure Instances
Microsoft Azure Discovery is similar to Amazon, you will need to:
– Enter an arbitrary name for the job
– Enter the subscription ID
– Generate a new management cert to add to your Azure console and then add the generated cert to your Azure console and run the discovery. To do this, click the “Re-generate management cert…” link. Then, log onto your Azure Management Console and click Settings. Click “Management Certificates”. Click the Upload button and browse to the file you just downloaded from Device42. That’s it! Azure will now recognize the Device42 instance as secure client that is authorized to interact with your Azure account.
Device > Virtual Device will now show cloud devices as well. The Vendor shows up as the Device Host for these devices. There is a new filter on the right hand side filter bar.
Cloud Instance Info
The Device view and edit pages will now show “Cloud Instance Information” under the Properties tab.
- The Device Add/Update API now has a new field available named ‘virtual_subtype. This field is only active if the device ‘type’ is ‘virtual’. The accepted values for this field are:
private: for an Internal VM. This is default behavior if nothing is passed.
ec2: for an Amazon EC2 instance
azure_vm: for a Microsoft hosted instance
azure_sql: for a Microsoft hosted sql server
azure_sql: for Microsoft hosted storage
other: for any other public cloud service
- For the application components API, if the appcomp_depends_on doesn’t exist already, new application is created automatically.
More verbose Reporting with Ping Sweep Discovery
Ping sweep discovery gets more verbose logging for each network with better success and error messages.
Better log history handling when an administrator(user) is deleted
In earlier version, if an Administrator was deleted, all the log history went with it. Starting with this release, the username is changed to username plus the epoch time (that is number of seconds elapsed from 1970) for user is “effectively” deleted. So you will still see the log history and will be able to add a future user with same username.
Cloning permission groups
You can now clone Permission groups using “Save as new” option. This will make it easier if you want to start from the System generated groups and add your own permissions to create groups.
Device PDU Mapping visual improvements
To map serial #, IPs, purchase info etc., you can map a PDU to a device (type other/PDU). We have added a visual representation to the PDU(linked) on the device page. Also, on the PDU page, we have taken the expand/collapse option out and made it expanded by default.
- Ping sweep discovery was failing in certain cases – which has now been fixed and verbose logging has been added.
- Switch port auto-discovery was ignoring ports with description of more than 32 characters – this is now fixed.
- Rack and Room in Device Report Columns now output just the rack name and just the room name.