Device42 FAQs

We are excited to announce the general availability of Device42 v16.04.03, which includes the following:

Cloud Recommendation Engine (CRE) enhancements

The Cloud Recommendation Engine (CRE) now includes a default option to Ignore Hypervisors when you run a CRE report. For more information about the CRE, see our documentation site: https://docs.device42.com/reports/cloud-recommendation-engine/.

The CRE page now also includes updated command buttons (Send to Cloud and Analyze DataandDownload Device Inventory) that more clearly explain what you use the commands for.

In response to customer requests, the CRE report recommendation spreadsheet now highlights any devices that use a Windows desktop OS (Windows 7, 8, 8.1, 10, etc.) as there may be additional cost considerations or restrictions with the use of Windows desktop OS.

Warranty Sync Discovery compatible with updated Dell API

Warranty Sync discovery jobs for Dell devices are now compatible with the new Dell API v5 to ensure the accuracy of your Dell warranty data for start and end dates and device purchase orders.

*nix and Windows Discovery returns CPU Hyperthreading Data

*nix and Windows discovery jobs now return the following device CPU hyperthreading information:

Total CPUs = Total number of sockets

Cores/CPU = Number of cores per socket

Threads/Core = Number of threads per core

Bug fixes

Windows and Linux Ping Sweep discovery creates discovery scores, discovers IP addresses, and operates as expected.

You will need to configure the following: Create a new application secret Subscription ID- you can get from:1. Log on to the Azure portal.2. In the left navigation panel, clickSubscriptions.The list of your subscriptions is displayed along with the subscription ID.Then, create an Application in Azure - instructions from Microsoft here: Create an Azure Active Directory Application.After creating the application, you can getClient IDandTenant IDfrom here: Values for Signing In.ForClient Secret -Finally, prior to running the discovery, you will need to Assign reader role to the application.1. In the left pane of the Azure portal menu, select Subscriptions.2. Select your subscription.3. Select the Access Control (IAM)tab.4. Select Add role assignment.5. Assign the Readerrole to the application.Example here:

You should now be able to run Discovery and see your Azure resources.

We are excited to announce the general availability of Device42 v16.04.02, which includes the following:

CRE 95th and 98th Percentile RU Calculation Options (and more)

The Cloud Recommendation Engine (CRE) page now includes options for 95th and 98th percentile resource utilization calculations for CPU, memory, disk, and network recommendations for all supported cloud platforms.

CRE now also provides disk and network IO recommendations for Google Cloud, and returns instance recommendations for devices with more than 100 cores for all platforms.

Ping Sweep Discovery

Ping Sweep discovery now provides frequent progress status updates and provides a discovery score record for each IP scanned and whether the scan was successful or failed. You can now also cancel a Ping Sweep job.

Bug fixes

Cluster devices and members properties not updating.Fixed

Agent-based Linux discovery not detecting last login.Fixed

Hypervisor/*nix alerts are visible but not available for adding as new alerts.Fixed

You can modify the individual server auto-discovery scripts to get the data dump and then import that data into device42 using APIs or excel import.

Individual scripts for solaris, windows and linux can be found under device42 support forum topic auto-discovery.

Going from v2011.09.30 to v2.0.2 is a major upgrade as it brings some changes to the database and the virtual appliance. Applying this requires 2 updates. First one is a minor and gets it ready for the major change. You would need to reboot the appliance after both updates.

One major change is introduction of switch level VLANs which could be L2 or L3 vlans and "VLAN" for releases 2011.09.30 and 2011.07.04 is called subnet now. You can define VLANs, associate it with multiple switches and do subnetting as per your design. Due to this change, MAC Address would now belong to VLAN instead of subnet(as in previous release). So this upgrade would create VLAN for all the subnets that have MAC addresses defined under them. For example, if MAC 20111234aabb is assigned to subnet CRMdbservers, we would create a new corresponding VLAN and assign that MAC to new VLAN automatically during the upgrade. If current subnet(that has MAC addresses under it) doesn't have a number or has a word as a number, corresponding VLAN # for new VLAN would be 1. You can later go in and change VLAN properties.

Another change is better IP import functionality. Software calculates automatically what subnet an IP belongs to if none is given in the spreadsheet and if it can't find one, it adds that IP to "undefined" subnet. With this we are getting rid of GlobaVLANv4 and GlobalVLANv6 subnets(you would have them if you did IP Import previously without VLAN field). So all IPs in these 2 subnets would be transferred to "undefined" subnet.

Highly Recommended: Take a snapshot of the virtual appliance.

This way if there is any issue with upgrade you can revert back and get in touch with support to perform upgrade.

Apply update-20110930P1.zip first.

Go to Tools > Update and Apply update-20110930P1.zip. This is a fairly light update and would be very quick.

Varify the P1 for 2011.09.30.

If you go back to home page and come back to update page, you should see the new version with P1 in the end. On Hyper-V image, if browser still keeps showing in wait state after a minute, go to home page and back to update page and if you see the P1 in version number, proceed with next step.

Reboot virtual appliance.

Go to console, choose option 3 to reboot the appliance. Say y when prompted.

and when it comes back you would see option 5 as shown above.

Apply update-202.zip

Go to device42 web portal -> Tools > Update and Apply update-202.zip. (Called update202from0930P1-HyperV.zip for Hyper-V image)This is a larger file and might take some time. Once its done, you would see a message that says go the console to apply the update.

Once the update is applied, you would see above message: "Hit any key to return to the menu...". Now do a reboot again using option 3 and that should bring you to following menu.

Menu after the reboot.

You should see this new menu on the console once the reboot is done.

Confirm the new version.

You can see new version from Tools > Update from the device42 web portal. And you would see all the additional menu items as well.

Confirming the data and deleting the snapshot.

Once you confirm the functionality and data is intact, you can go ahead and delete the snapshot created in step 1.

v2.5.0 has a new underlying OS (ubuntu 12.04 LTS 32 bit) and there is no direct upgrade path to this release.

Please download the new appliance from the download section on device42 website. In this section, we would discuss steps to have your existing data populated on the new appliance.

Prerequisite

v2.5.0 can restore from v2.4.2 and v2.4.3 appliances.

(If you are running a previous version, please send us a email to support@device42 with your current version and we would send you the link to upgrade to v2.4.2).

What is not restored

Not all the settings would be restored the new appliance. We apologize for the inconvenience. Improving this list is on our road-map for future releases.

Backup pass phrase.

Password pass phrase.

Active Directory Settings (Just the settings for the server, all administrators and permissions would be restored)

Time zone and NTP settings

HTTPS certificates.

Backup schedule and mail server settings.

Appliance manager login info.

Login to the appliance manager

Installation guides for the device42 appliance

Device42 Appliance manager can be accessed at http://your-ip-address-or-FQDN:4242 (Port 4242, http for your appliance IP).

Default username and password, if you haven't changed it: d42admin/default

Generate the backup file

Backup > Run. You would need to set the pass phrase if you haven't already and make sure to keep that in safe place.

Setup the new appliance

Please refer to to setup your new appliance.

Login to the appliance manager on the new appliance

Device42 Appliance manager can be accessed at http://your-ip-address-or-FQDN:4242 (Port 4242, http for your appliance IP).

Default username and password, if you haven't changed it: d42admin/default

Do the restore

NOTE: If you are using active directory solely, you would have to manually add active directory settings prior to the restore.

Backup >Restore.

You would need the pass phrase used to do the backup.

Restart application, check everything and bring your settings back

Restart Application.

Log back in to the main webconsole, check everything and bring your settings back.

You can power off the older appliance and leave it there for few days(to make sure all is working well) as you start work on the new appliance.

Settings quick cheat sheet

Settings that would not be restored, can be set from these menu prompts:

Password passphrase : Tools > Options > Password Security

Active Directory Settings: Tools > Active Directory Settings

Time Zone/NTP: Tools > Options > Time Settings and also option 7 on vm console

HTTP certificates: Tools > Options > HTTPs cert

And backup settings in appliance manager.

Blade servers can be added to a blade chassis in device42 as discussed below.

Adding a blade chassis device

device create/update APIs doc

Add a physical device with Blade chassis checked.

You can either choose an existing hardware model for the device or add a new one using the lookup icon next to hardware input field.

Once you save this, you would be able to add blade servers to this chassis.

Adding blade servers

When adding a new device, choose type as blade and click "save and continue editing" to go to next screen.

Here you can choose/add the hardware model (type blade) and choose which chassis the blade server belongs to. Later in this article, we would discuss how to do this in bulk using excel and API calls to save you these multiple steps.

Location display on the list view

Devices > All devices would show location for the blade server as the blade chassis name - Slot #.

Listing all the blade servers in a chassis

From the device chassis view page, you can see all the modules in that chassis by clicking on the "modules list" as highlighted above.

Blade servers visual representation

We introduced better web based rack layouts in v4.2.0 for blade visualization. You can view list of all the blades/modules in a chassis when you hover over the device in the rack layout view.

Adding/editing blade servers in bulk using excel imports

If you head over to Tools > Import > Devices, you can download the sample excel file. You can either edit existing devices or add new devices using this. To focus on blade server/chassis relationship we have kind of hidden other columns here.

As you can see in the image, in first row, we are adding a device type "physical" with "Is it modular Chassis?" . Then in subsequent rows we are adding blade servers as Type "blade" and choosing the Blade Host and the slot #.

Adding/editing blade servers in bulk using RESTful APIs

You can also create/edit the blade chassis and servers using RESTful APIs in device42. All the arguments are listed on device42 documentation site under .

There is no direct GUI call to clone a device in device42, but RESTful APIs provide an easy way to clone a device. We have added a script under D42_Misc_Python_Scripts repository to do the same.

The script is briefly discussed below.

Script to clone a device

clone_device.py

Python script will take a device name as input and you can create new devices based on an existing device.

You just need to change those lines to match your environment.

ORIGINAL_DEVICE_NAME is the device to be cloned.

NEW_DEVICE_NAMES is the list of names of new devices to be created as clone of original device.

By default type and service level are cloned. You can choose to clone hardware, OS and CPU/Memory properties.

Once you modify lines 22-30, you can excecute the script to created the cloned devices.

Here is summary of steps to migrate from 32 bit Device42 appliance to 64 bit:

1. Make sure 32 bit image is same version as 64 bit version.

2. Install the 64 bit.

Linux Console credentials: device42/adm!nd42

Web console credentials: admin/adm!nd42

appliance manager credentials: d42admin/default

3. Do a backup from 32 bit image and check "Meta data backup" while doing the backup.

4. Do a restore on 64 bit image.

5. Make sure to change your IP/DNS settings on 64 image and shutdown the 32 bit image(because you might have 2 machines running scheduled jobs).

6. Optional: Base 64 image comes pre-configured with 4 GB of RAM and 2 vcpu. You can increase the memory and CPU as per your environment.

Check compatibility

You can check the versions from Tools > Update from the main app. Or you can compatibility from appliance manager restore section.

Installation

Installation steps are same as discussed here: http://docs.device42.com/getstarted/installation/

Linux console credentials are different: device42/adm!nd42

and the size of VM is different as well. By default: 2 GB RAM, 2 vCPUs and 50 GB of HDD.

Backup from 32 bit

Make sure to backup meta data when taking the backup from 32 bit appliance.

Restore to 64 bit appliance

Do the restore on new appliance and make sure restore meta data is checked.

IP settings for 64 bit and shutdown 32 bit

Do the IP settings for 64 bit as per your environment (static IPs/DNS etc.) and make sure to shutdown 32 bit appliance.

Configuring vCPUs and Memory for the new VM

4 GB RAM and 2 vCPUs are good for upto 2500 devices. If you have lot more devices and are running lot of auto-discovery jobs, you can add additional CPUs/cores and memory.

In order for windows based auto-discovery tool to collect information from windows servers it needs to connect to remote machines using WMI/WinRM.

We have an older article that helps with some of the error messages: https://device42.zendesk.com/entries/27009367-D42AutoDisc-Client-Windows-or-Hyper-V-auto-discovery-error-messages

If that doesn't help and you still have problems connecting, please use the following steps to troubleshoot:

The WMI Diagnosis Utility

This is a utility to help system administrators diagnose and repair problems with the WMI service. Please run this to see if you can connect to the remote computer.

Link: https://www.microsoft.com/en-us/download/details.aspx?id=7684

How to article for this: http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx

Quick step to enable winrm

Run following on the remote machine:

```winrm quickconfig```

Some steps for firewalls

```netsh advfirewall set service RemoteAdmin enable```

or

```

netsh firewall set service RemoteAdmin enable

```

Advanced firewall commands

```netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes

netsh advfirewall firewall add rule dir=in name ="WMI" program=%systemroot%\system32\svchost.exe service=winmgmt action = allow protocol=TCP localport=any

netsh advfirewall firewall add rule dir=in name ="UnsecApp" program=%systemroot%\system32\wbem\unsecapp.exe action=allow

netsh advfirewall firewall add rule dir=out name ="WMI_OUT" program=%systemroot%\system32\svchost.exe service=winmgmt action=allow protocol=TCP localport=any```

Windows auto-discovery

For .net auto-discovery tool to work, the WMI diagnostic utility must be able to connect to the remote machine. If you are able to connect via that utility and still having issues with auto-discovery tool, please contact us at support at device42.com

We are excited to announce general availability of v14.2.0 with the following changes:

Warranty Sync for Dell, HP, IBM and Lenovo

We have added the ability to discover Warranty Information for Dell, HP, IBM and Lenovo devices that have serial numbers in Device42. Warranty checks can be configured and scheduled to run on a regular basis fromTOOLS>Auto-Discovery>Warranty Sync. Warranty information is imported as a purchase orders. Note that some vendors may require some API access keys to be able to pull information from their APIs, namely, HP and Dell.

After running discovery, you will see detailed information on new purchase orders.

Multi-password and complex server range support

We have made Hypervisor/*nix/win AutoDiscovery Jobs more flexible so that you can discover a greater number of devices with fewer jobs.

You are now able to select multiple passwords to utilize while running auto-discovery. While configuring a job, you may click the lookup icon multiple times and keep adding more passwords to the discovery. Device42 will attempt each password in the list until the one is successful for each IP.

If you are creating a *nix discovery you may also select to use an alternate sudo password to run certain discovery commands.

In addition, you can now enter complex server ranges. This lets you target a wider range of devices or a more targeted set of non-sequential IP addresses. The Server(s) field has been upgraded to a multi-line edit field where you may enter:

Single FQDN

Single IP

IP ranges (e.g. 10.10.42.50-10.10.42.86)

CIDR(e.g. 10.10.42.0/24)

Any combination of the above, each comma separated, space separated, or line separated.

You may also utilize the same pattern described above to exclude servers from being discovered:

Auto-Discovery options in Device42

We have made Auto-Discovery options in Device42 feature-compatible with the external Windows Based Auto Discovery Tool. These options can be set inTOOLS>Settings>Global Settingsand include

Use Global Ignore Services File

Use Global Ignore Software File

Use Global Ignore Software Pattern File

Exclude Windows Listening Ports

Exclude Windows Remote Ports

Exclude *nix Listening Ports

Exclude *nix Remote Ports

Exclude Remote IP Addresses

Remote Collector Disk Space Warning and Stats

We have added a warning message to Device42 home page to alert you if one of your Remote Collectors disk space has reached 50% utilization.

In addition, we have added Remote collector statistics to thehealthstatsAPI ( https://d42:4343/healthstats/ )

Legacy Power Monitor jobs

Starting with 14.2, we have finished migrating the Power Monitor functionality to Remote Collector and are disabling the use of Power Monitors in new discovery jobs. Existing Power Monitor jobs may continue to run but you will not be able to add additional ones.

SSL version in Certificate Discovery

We are now collecting SSL version during Certificate Discoveries and displaying that information on the certificate pages.

VMWare Auto-Discovery enhancements

We are now collecting some additional information about virtual machines and host machines to make it easier to track which clusters virtual machines are on and what vCenter instance is managing those clusters.

For all VMWare virtual machines, you should be able to see two fields under the Other tab:

Datastores: a comma separated list of all the datastores for the VM

Host Cluster: If the virtual machines host is part of a VMWare cluster, then you will see the name of that cluster. In addition, a Cluster device is created in Device42 for this VMWare cluster and all the VM hosts are associated with this cluster. You may click on the cluster name to inspect the cluster itself.

For all discovered VM Hosts, if the device is part of a cluster, it will be associated with the Cluster Device and in the Other tab you will see the following fields:

Data Center: The datacenter the VM host is associated with

VM Manager: The device that is currently running vCenter, if it has been previously created into Device42

Bug Fixes

SNMP discovery of Juniper SRX550 failed to return data. Fixed

Excel Reports may fail if report name contains Unicode characters. Fixed

Linux-based discovery tool may crash while discovering some Docker instances. Fixed

TrendPoint PDU discovery may fail. Fixed

Changing a subnets customer does not modify child subnets. Fixed

VM hosts being discovered with domain suffix while Ignore Suffix is enabled. Fixed

SAML authentication always redirecting to home page after authentication. Fixed

Some discoveries may fail to use the sudo command if sudo returns warnings. Fixed

IP address may get duplicated while updating VRF group via API. Fixed

Mount point may not be discovered in some cases. Fixed

Unable to access appliance manager with browser that block RC4 cipher. Fixed

SAML authentication may fail if using passphrase. Fixed

Unable to discover certificates for RDP servers via port 3389. Fixed

Calling parts API with invalid device was returning all parts. Fixed

Link to our blog: https://www.device42.com/blog/2017/11/warranty-sync-and-mutli-password-support-in-v14-2-0/

For monitoring purpose we suggest three options:

Nagios monitoring integration

Device42 offers a Nagios plugin for Device42 which can be downloaded from this link Plugin Download, and allows easy monitoring of the health status of your Device42 appliance. Data returned includes:

Device42 Database Size

Appliance Disk space usage

Memory usage

CPU usage

Zabbix Integration which can be downloaded from this link Zabbix Download

API call to check the health status of the CPU/RAM, DB size and the status of recent backups

curl https://yourdevice42ipaddress:4343/healthstats/ /4242 port can be used if the SSL is disabled on Device42/

{

"backup_status": [

{

"id": 1,

"job_name": "Demo Backup",

"status": "Backup not run since last reboot. Please check."

}

],

"cpu_used_percent": "2.51904",

"dbsize": "84 MB",

"disk_used_percent": "8",

"memory_in_MB": {

"buffers": 92,

"cached": 254,

"memfree": 1728,

"memtotal": 3948,

"swapfree": 8187,

"swaptotal": 8187

}

This article will guide you in getting Device42 deployed on your Microsft Azure platform.

Device42 can be retrieved from the Azure Marketplace.

Go to the Azure Marketplace [Device42 - Visualize Your Entire IT Infrastructure] and click on Get it now.

Azure VM Configuration

Fill in virtual machine details. You will need to specify the following:

Resource group

Virtual machine name

Size of VM - please note that you should choose something with at least 8 GB RAM and 2 vCPU (recommended 16GB RAM 4 vCPU) or else you will get out of memory errors.

Administrator account - choose Authentication Typeas Password and just put in some random values. This field has no bearing on Device42 deployment.

Networking

Disks

Click on Review & Create. After validation, deployment should start.

The Azure deployment creates the following resources by default:

Microsoft.Network/networkInterfaces

Microsoft.Network/publicIpAddresses

Microsoft.Network/networkSecurityGroups

Microsoft.Compute/virtualMachines

You can add a ICMP Inbound allowed rule in. You should now be able to ping your Device42 instance.

You should also be able to access the Web GUI by navigating to the public IP address. Please also make sure your network security groups allow the following inbound ports:

404 - ssh access

443 - Web GUI and API access

4343 - appliance manager SSL port

VM serial console should also be enabled in your VM settings.

You will set a password for the default superuser admin account in the next steps.

Device42 Configuration

Get your Device42 Azure VMs instance ID by running the following command in Azure Shell

az vm show --name <VM Name> --resource-group <resource group name>

Need value from vmId.

Go to the serial console of your Device42 Azure VM or use ssh port 404 to login with username device42and the password as the vmIdvalue from previous step.

You will be prompted to set adminpassword and appliance manager d42adminpassword.

Once this is set, you can change the device42console user password to something of your own choosing by selecting option 10from the console or keeping it as is.

You should now have a fully functioning Device42 Main Appliance hosted on Microsoft Azure. You can run updates on this instance to get it to the latest version. You will have to supply your license to get full functionality.

The Oracle cloud discovery requires a user with enabled API access.

Required keys and OCIDs to set it up described here, https://docs.cloud.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm.

The user's API private key and public key fingerprint should be added as secrets to device42 and assigned inthe oracle cloud discovery job properties.

It is also required to supply the tenancy and user OCIDs, https://docs.cloud.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm#Other

User's OCID should be added as a secret and the tenancy OCID in place to the 'Tenant ID' field.

Secrets user names can be just descriptive. The discovery picks up OCID, fingerprint and key from password value and attached key file correspondingly.

We are excited to announce the general availability of Device42 v16.04.00, which includes the following:

Upgrade cut off release

Due to the size of our current upgrade package, we are making 16.04.00 a cut off upgrade. This release will be a required upgrade before any future upgrades. In addition, this cut off will apply to Remote Collectors as well. This is a necessary step in order for us to reduce our upgrade size, and we appreciate your understanding.

Oracle Database Discovery

Device42 v16.04.00 now supports Oracle database discovery for both Windows and *nix OS environments. Enable database discovery by simply checking theCollect database server informationcheckbox on any Window Discovery job. Add valid database credentials to the job and as Oracle databases are detected, discovery will import a list of all instances, databases, and connection details!

Device42 License Expiration Alert

Device42 v16.04.00 now displays an alert on the Device42 dashboard 30 days prior to the expiration of your Device42 license.

You can also add your own Device42 license alert with custom rules for when you want to be notified. Go toReports > Setup Alertsand selectDevice42 license.

Cisco Meraki Warranty Check enhancement

Device42 v16.04.00 now includes warranty check discovery for Cisco Meraki in addition to vendors such as Dell, HP, and IBM to check for warranty information and license expiration. Go to Discovery > Warranty Sync > Add Warranty Check to add a check for Meraki.

Device42 also updates our external version of Warranty Check; its available in github at https://github.com/device42/warranty_check/releases.

CyberPower PDU Discovery enhancement

Device42 v16.04.00 now supports discovery for CyberPower PDUs through SNMP discovery to create CyberPower device and power mappings in Device42.

Kubernetes Discovery

Device42 v16.04.00 includes an early preview of Kubernetes discovery for both cloud platforms and in standalone mode. Kubernetes discovery is the ideal way to see your containerized applications and their structure across the cloud. Discover and collect Kubernetes cluster, pod, and container data and see the information quickly and easily in visual physical and logical views. You can select Kubernetes cloud discovery for MS Azure, AWS, and Google Cloud or for a standalone platform.

Notes

We auto-create VRF groups to capture internal K8s IPs.

In AWS, some K8s nodes may not match due to naming differences between K8s node names and vendor VM instance names. Manual merging needs to take place to rectify this discrepancy. After merging, future discoveries should see both devices as the same.

Currently, if you have permission to see the new Configuration Resource items, you can see the whole physical and logical diagrams regardless of multi-tenancy permissions. However, you will not be able to drill down into the device if you do not have rights to see it based on security permissions or multi-tenancy permissions.

Currently, we are not allowing any modifications or deletions of Configuration Resources. We will enhance this functionality in the near future to empower you to do more with it.

Bug fixes

Solaris OS being returned as generic_virtual rather than Solaris.Fixed.

AD LDAP sync doesnt work with PosixGroups.Fixed.

Windows Ignore IPv6 is still creating IPv6 details.Fixed.

port_name_prefix_to_ignore_macs is not working with SNMP job creation through API.Fixed.

asset_number_profile page encoding/decoding error for some languages.Fixed.

Openldap sync fails if no credentials supplied in the LDAP settings.Fixed.

Rack layout and Multiple Rack Connections displays blank page if components are placed on the Shelf.Fixed.

We can add two or more devices on the same rack unit by creating the corresponding hardware model with appropriate width ratio and using the "X" position parameter to identify the position of the device on the rack unit.

For example if you have three devices which need to be added on the same rack unit, first we need to create a corresponding hardware model:

Here we used the width ratio 1/3 because we have three devices, for two devices we need 1/2 and so on.

Then we need to identify the position for each device, for this we need to use the default value which is equal to 2520 and divide this value on the number of devices needed, in this case we divide this value on three:

2520/3=840

0 will be the position of the first devices (on the left)

840 the position for the middle device

1680 the position for the third one

The same steps need for 2 devices 2520/2 and for four etc.

To mount all these devices, go to the rack page, then under "Devices in this rack" tab mount them by identifying the corresponding "Position" value

Finally we will get all these devices displayed on the same rack unit on the rack layout page

We are excited to announce the general availability of Device42 v16.03.00, which includes the following:

Cloud Recommendation Engine Enhancements

The Cloud Recommendation Engine (CRE) was upgraded in v16.03.00, and now factors resource utilization (RU) information and configuration details for both NICs and disks(HDDs)into the generated cloud instance recommendations.

New data includes disk IOPS(both read and write), NIC speeds, transfer rates, monthly networking & storage costs, and more, and can be found across all recommendation tabs that include RU data. You can preview some of the new columns in the sample data image below:

New disk and NIC details are factored in to recommendations across all four supported cloud platforms, and additionally, these new details can be output to a file you can download. With these enhancements you can be confident that the workloads youre moving are right for the cloud, that the instance sizes you are choosing will support them, and that the cloud platformyou'vechosen offers the best value!

Discovery Enhancements

Introducing last login for Linux

Complementing the recently introduced Last Login for Windows discoveries, this release extends this same functionality to Linux-based operating systems. Note that this doesnot includeUNIX-based OSs (BDS, Solaris, AIX, etc.) at this time.

JBoss application components

Device42 v16.03.00 introduces discovery and Application Component support for JBoss installations. The newJBoss Application Componentgroups all discovered JBoss services together, and also captures important JBoss configuration information including run variables, version, and more.

Configuration details from application components

Configuration details can now also easily be viewed via the action menu while viewing Application Components. Previously visible only on Topology diagrams, this update makes it easier to quickly view configuration details. This new action button is available across all Application Components for which configuration information is discovered.

New UCS discovery options

This release adds new options to UCS discovery jobs. You can now set a service level for decommissioned servers, and can also set theIn-Serviceflag to auto-toggle depending on if the server is powered on or off. The new options are highlighted below:

DOQL, API, and Other Updates

Customer added to cloud discovery API

This release adds API support for querying thecustomer_idfrom the Cloud Discovery jobs API endpoint(/api/1.0/auto_discovery/cloudaccount/). This column was also added to the export sample file and can be exported via the current data export. Export files can be found inTools -> Imports/Exports(.xls).

Database discovery options via API

Device42 now supports specifying database discovery via the API, as well as selecting which passwords to use while creating or modifying a discovery job via the endpoint(/api/1.0/auto_discovery/vserver/)and the valuescollect_db_info, db_username, db_password.Alternately,to send ids of existing secrets, users can utilizedb_password_idordb_password_ids.

Database discovery data added to DOQL

Support for discovery of Microsoft SQL Server was introduced recently in v16.02.00, but that new information wasnt immediately available via DOQL. This release adds the relevant DOQL endpoints, which also enables users to leverage SQL data in Advanced Reporting.

The following new views were added to support this:

view_database_v2

view_databaseconnection_v2

view_databaseinstance_v2

view_databasesize_v2

Known issues

Google Cloud Platform (GCP) support for the Cloud Recommendation Engine (CRE) is still a work in progress as of v16.03.00 and GCP cost data is known to be un-reliable at this time. CRE recommendations for GCP should not be relied upon until further notice.

Bug fixes

LDAP sync could miss users in certain PosixGroups. Fixed.

Last login for Windows discovery was not reporting all domain user logins. Fixed.

Login prompts could be sized very small on certain high-resolution screens. Fixed.

CRE with target AWS region Asia/PAC was not matching instances properly. Fixed.

End-user information containing Unicode characters was not displayed correctly after an LDAP sync. Fixed.

We are excited to announce the general availability of Device42 v16.02.01, which includes the following:

Cloud Recommendation Engine enhancements

This release includes enhancements to Cloud Recommendation Engine that will better account for different CPU configurations, speeds, and current utilization. With these new changes you should find that our Cloud Recommendation will provide the best possible match based on the data we collect and monitor.

Advanced Reporting updates

In this version, the Advanced Reporting framework was updated to take advantage of some significant performance improvements(and bug fixes)available in the latest release. In addition, several of the pre-built advanced reports were also updated, while data elements were expanded for various existing reports.

New reports are as follows:

Discovery_Status_by_Device: Detailed discovery status for easier troubleshooting

Discovery_Status_by_Job: Detailed job status for increased discovery visibility

Load_Balancers: Shows VIPs, Pools, Member Server and Service relationship

System_Profiles_Summary: Overview of discovered systems by count

Discovery enhancements

SNMP discovery performance improvements

Device42 v16.02.01 includes SNMP discovery enhancements that should significantly boost discovery performance against large IP ranges. These improvements allot more resources to the port check portion of the discovery, which in the past could take significant time to run against large network segments.

With the introduction of v16.02.01, port check can now take advantage of all available resources on the discovery appliance.

Internal testing showed that these enhancements resulted in both a net reduction in retries and a drastic performance improvement. Were looking forward to hearing about your results, as well!

SNMP support for IBM tape libraries

This release also adds support for IBM tape library discovery via SNMP.

Oracle OVM cluster support

The v16.02.01 release of Device42 also introduces Oracle OVM discovery support. Create and schedule a new Oracle OVM discovery job from the Device42 main menu, Discovery Hypervisor/*nix/Windows, then simply select Oracle OVM in theplatformfield to begin retrieving and storing cluster information from devices on the Oracle OVM platform.

Simply browse to your OVM hosts device detail page and open the Virtuals tab to see the names of discovered virtual machines that are part of the cluster:

Redfish discovery Serial number options

v16.02.01 introduces a new option to retrieve serial numbers during Redfish discovery. You can now simply selectService Tagas your option forSerial To Usewhen defining a discovery job to utilize this new value. The new option can be previewed in the screenshot to the right.

New zone support for Google Cloud discovery

Google Cloud discovery jobs now include support for all recently added regions in Google Cloud platform.

DOQL, API, and other updates

Custom field APIs

The custom fields APIs(e.g. /api/1.0/custom_fields/building/ as an example)were enhanced and now support adding items to picklist custom fields via the newly added parameteradd_to_picklist.

This new parameter expects a comma separated list of picklist items. Note that existing pick list items will be ignored, however, so if in doubt, all list values can be re-sent when updating as opposed to only new items, and duplicates will be filtered automatically.

Last login DOQL access

v16.01.00 introduced Last Login functionality for Windows discoveries, and this release follows up with the necessary DOQL view to support this new data:view_devicelastlogin_v1. With this addition, last login details can now be included in reports, and of course accessed directly via DOQL.

Periodic jobs DOQL access

This release also adds the Periodic Jobs data that is currently visible inReports > Periodic Jobsto DOQL, as well, through the newly added view_periodicjob_v1 view. In addition, you can report on this data via Advanced Reporting as well.

LDAP connection timeout control

A new LDAP configuration that allows easy customization of the LDAP connection timeout was added. The default is 10 seconds, and can of course be customized based on what makes sense for your specific network environment. Find the setting in the Device42 main menu,Settings LDAP.

Bug fixes

Sample hardware model import file would error when re-imported. Fixed.

Switch VLAN ports were inversely related to parent physical ports. Fixed.

IP addresses on VLAN ports were being assigned to the physical port rather than VLAN port. Fixed.

Standby appliances were incorrectly requiring license re-registration after restoration of a backup. Fixed.

Adding a new Asset Tag profile could fail if the asset Start Number was >32,767. Fixed.

MICROSOFT SQL SERVER DISCOVERY, BUSINESS APPLICATION ENHANCEMENTS IN V16.02.00

We are excited to announce the general availability of Device42 v16.02.00, which includes the following enhancements:

Database discovery Microsoft SQL Server

This release adds a powerful new feature to Windows discovery jobs: database discovery! Initially supporting Microsoft SQL Server databases(aka MSSQL), discovery for other popular DB platforms will be added in future releases as this feature continues to grow.

Enable database discovery by simply checking theCollect database server informationcheckbox on any Window Discovery job. Simply add valid database credentials to the job[separate fields, highlighted above], and as MSSQL databases are detected, discovery will import a list of all instances, databases, and connection details!

Business Applications enhancements

This release includes a few tweaks that should make Business Applications even better:

Easily export Business Applications as SVG images:View externally, and easily import them into other software, e.g. Visio.

Search right from the Business Application list page:Quickly find your Business App by typing the first few letters of its name, or even by the name of a device in the app!

Quickly see all Business Apps a device belongs to with the new Application tab:Device view pages now include a list of all the Business Applications each device plays a role in.

Customer auto-assignment for cloud discovery

New in v16.02.00, Device42 can automatically assign a customer to discovered cloud-based devices. Simply specify the relevant customer when configuring your cloud discovery job and each discovered instance will be automatically tagged.

Agent based discovery auto-updates

Users who leverage any of Device42s agent-based discovery tools will appreciate that using these tools just got a whole lot easier: The same auto-update capabilities that you enjoy across the agentless tools now supports agents, too including both the Netflow and packet-capture tools. Enabling this functionality will of course require a final manual update, and going forward all of your Device42 tools will self-update!

SSH-based discovery enhancements

Device42s SSH based discovery has been tweaked to improve connection stability while reducing the number of connections made between remote collectors and discovery targets. From the workflow and functionality perspective, this change should be invisible. Sysadmins, however, should appreciate it.

Bug fixes

SNMP discovery of certain switches with imported SFP modules may fail if duplication is found. Fixed.

Solaris discovery may not properly discover domain name. Fixed.

CPU counts were not always reported properly with certain server configurations. Fixed.

The rack layout page might not render power units mounted above/below a rack when operating in non-English language mode. Fixed.

Attempting to delete a Job Score could result in a server error message. Fixed.

Users were unable to specify a Reporter Name when creating a Jira Cloud ticket from the Device42 UI. Fixed.

Remote Collectors couldnt be removed from Device42 if any completed jobs that used it existed. Fixed.

Link to our official blog: https://www.device42.com/blog/2019/09/microsoft-sql-server-discovery-business-application-enhancements-in-v16-02-00/

Devices can be converted into assets by using re-importable exports or by using the Device42 API. Please note that due to the differences between device and asset fields, not every property will be converted.

1. Export the devices you wish to convert by selecting them and using the re importable export option:

https://api.device42.com/#create-assets

2. Navigate to Tools > Imports/Exports and download the sample file for "Create Assets":

3. Open the exported device file and copy the API details from the asset sample file in rows 1 and 2:

4. Remove fields from the device file that are not compatible for assets. A "Type" field must also be provided for an asset which differs from the device type. Our API documentation displays the fields that are valid for assets -:

5. Import the updated file from Tools > Imports/Exports. You will see a list of the imported rows along with any errors if fields are missing:

6. Browse for the newly created asset:

7. After the asset has been validated you can then search for and delete the original device record.

Follow these steps to upgrade your Device42 main appliance via the UI (using appliance manager):

1. Perform a backup

https://device42.com/update/

a) Head over to http://your-device42-IP-or-FQDN:4343 and take a backup before doing the upgrade. If you want to include users and settings, check "Backup Meta Data" as well; otherwise, leave the default.

Optionally, you can (also) take a virtual machine snapshot from your virtualization platform.

The default username and password for the Appliance manager is [ d42admin / default ] if they were not already changed; Please, however, ensure you change these to your own secure credentials!

2. Download and apply the update file.

a) To download the update file, head Tools > Update, or browse to

b) Once you've downloaded the update file, head back to the appliance manager. You can reach appliance manager via the link in the main Device42 UI under Tools > Update.

c) Select "Application" from the left-side menu in appliance manager, and then "Update Software":

c) Browse to the update (.enc) file you downloaded, and select "Upload". You should see the following message:

3. Login to the console to apply the update

You can login to console one of 2 ways:

1. Go to the VM console from your virtual platform.2. Or, ssh to port 404 on D42 IP. (or port 442 on power appliance)

For AWS deployments you won't have access to a VM console, you'll need to SSH and the menu below will come up in your SSH session. SSH as the device42 user:

WEB UI - u: admin p: AWS_INSTANCE_IDAPP MGR - u: d42admin p: AWS_INSTANCE_IDMAIN APP SSH: u: device42 p: AWS-KEYFILE

AWS Default PORTS:404 ssh, 4242 appmgr-http, 4343 appmgr-https, 443 https

The default credentials for the Device42 appliance console are:Username: device42Password: adm!nd42

You can (and should!) change the default console credentials via option 10.

Apply the update.

Choose option 3 from console. Press y when asked and then any key to reboot as shown below.

Reboot if required

After applying the update, the console will present the above screen; press any key (literally any key on the keyboard) to continue with the post-update reboot.

There is a possibility the update will not require a reboot; If that is the case, you will be presented an option to instead press any key to return to main menu.

3. Clear your browser cache.

This is a must - To ensure you are not using a cached UI, clear your browser history. This will ensure that the Device42 web portal works correctly!

4. You're done! Verify the update via Tools -> Update

You're all set! Confirm the new, updated version of Device42 from Tools menu > Update:

5. Note that updates to the Device42 main appliance (D42 MA) include updates for any Remote Collectors (RCs) and or WDS service instance you may have deployed. Where applicable, Operating System (OS) updates for the underlying (CentOS) Linux-based operating system(s) are included, all of which are applied automatically!

The front of the racks are angled and the backs are flat.

D42AutoDisc client common error messages and resolutions are discussed below.

Also, the executable should be run as an administrator.

Exception Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

http://stackoverflow.com/questions/11330874/get-wmiobject-the-rpc-server-is-unavailable-exception-from-hresult-0x800706?rq=1

If you see following message:

Exception = Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Please make sure the service is running under a domain account and not local system account.

Exception The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

In addition to above, please check this stackoverflow resource:

Cannot post device detail to D42. Check URL/Credentials or License.

For message: Cannot post device detail to D42. Check URL/Credentials or License. Please check you can connect to device42 instance from the browser. Otherwise, see if your license count has exceeded the number of licensed devices.

Due to certain properties assigned to devices based on the type, it is not possible to simply change the device type once assigned.

Quickest way will be to :

1. export the device records from actions menu by doing a "re-importable export for selected devices".

2. After you export the info, you can bulk delete devices from action menu.

3. Change the excel file to reflect blade devices and new hardware model(if applicable)

4. And then re-import it from Tools > Imports/Exports.

Upgrade steps to upgrade from v2.1.1 or v2.0.2 to v2.2.0P1. Same applies from upgrade from v2.0.2/2.1.1 to 2.3.2.

1. Download and Apply the update file.

Tools > Update to add the update file. Then go to console to apply the update.( You should see following message.)

2. Apply the update.

Choose option 3 from console. Press y when asked and then any key to reboot as shown below. And after it comes up, you should see the new menu option for NTP Client(as shown in image below).

3. Clear browser cache.

This is a must as well. Some of the css and js files have changed and you have to clear browser history for web portal to work correctly.

This is it! Enjoy assigning permissions to users and add active directory users!

You can confirm the new version from Tools > Update.

Steps for installing device42 appliance on Xen or KVM based platforms, if import disk image option is missing. Otherwise, refer to device42 xen/kvm install docs.

Download and bunzip2

Raw image for Xen/KVM has been compressed using bzip2. Once you get the file on kvm host, you can issue bunzip2 <filename> to uncompress the file.

Install

Once you unzip the downloaded raw image, create a new virtual machine. Choose Network Boot(we would add disk later). Please make sure you don't have some sort of automated network boot enabled for this machine. You would not see option to Import existing disk image.

Choosing OS and version

Choose Linux & Ubuntu 12.04 for Operating system type and version. If you don't see the option for 12.04, choose the latest version avaialble(as shown above).

Choose 512MB RAM and 1 vCPU.

Choose disk(bunzipped file)

Choose your virtualization type from Advanced options and i686 as architecture and you are ready to go.

Disable network boot

Details > Boot Options > Uncheck Network(PXE).

Setting up the appliance and logging in.

Power on, if not already on.

On the console, configure IP and choose the settings you desire.

Optional: Create DNS entry for the new IP address for new virtual appliance.

Point your browser to http://FQDN(Fully Qualified Domain Name) or IP address and you are ready to go.

Default username is admin and password is adm!nd42, please change that as soon as you login.

Above steps in images:

Configure Networking.

default username/password is admin/adm!nd42

Make sure to change it after you login.

Enjoy!

To clear rack allocation for a device but not delete the device, use the rack edit page to deleted the racked device. This would clear the rack allocation.

Robe based access is explained in device42 documentation here: http://docs.device42.com/tools/role-based-access-explained/

Following is a quick outline of adding users other than admin.

Use admin groups

http://docs.device42.com/tools/add-active-directory-useror-administrator/

You can do permissions either by assigning permissions on group level or on individual user level. It is better to do it on group level, that way work is less when you add more users with same permission set.

Head over to Tools > Admins & Permissions > Admin Groups > Add group.

Give it a name, filter and choose the permissions you need.

Save the group.

Add user

From Tools > Admins & Permissions > Administrators, you can add local or AD/LDAP user.

Once you choose the user/pass for user and save, you can assign the group as shown below.

Active directory integration is discussed here:

Once you save, this new user will have read-only permissions.

High level overview on how to run Device42 on your local machine using VirtualBox

Download VirtualBox

https://www.virtualbox.org/wiki/Downloads

Install VirtualBox

Go through all the appropriate next steps to install on your local Windows environment

Request Device42 Trial Download

Http://www.device42.com

Click on "Free Trial Now"

Fill out form

Fill out your name and your email then click on "Start Your Free Trial"

Go to your email

Click on "here" in your email to download the device42 virtual appliance

Select your virtual environment

Oracle Virtual Box/VMware Player

Use 7zip File Manager

Extract the file with 7zip file manager. The 7zip extraction will extract a ".vmdk" file

http://www.7-zip.org/

Importing into VirtualBox as New VM

1 Choose any name you want to give this appliance. 2. Choose Linux as OS. 3. Choose Ubuntu (64-bit) as version. 4. Next

Memory

Give the vm at least 1gb of ram

Choose existing Harddisk and browse to unzipped VMDK

Use existing harddisk and browse to folder where you extracted device42-14.x.x-player.zip. And choose the vmdk file. Click Create

Finish

Dont power on after Finish

Enable PAE

Go To setting of the new appliance you just added. Go to System > Processor Enable PAE Click OK

Configure Network Card

Enable Adapter 1. Choose Bridged Adapter (or NAT if you want) for network access. Choose the Physical NIC you would be using. Click OK.

Setup and Go

Power on Virtual appliance. (Ignore audio driver warning if you get any)

Login with default username and password : device42/adm!nd42 (Option 10 to change the password)

Network Setup

Option 1 to configure networking. Choose DHCP or give static IP.

Login!

Default credentials:

Username: admin Password: adm!nd42

Enjoy!

Whenever you see an error related to:

.dll could not be found (example attached) if you are trying to edit, schedule or create an advanced report

You need to reboot Device42 (the virtual machine) and the missing .dll file will be generated and the problem will be solved.

****Please reach out to Support before applyingthis update*****

v16.00.00 Major Update Prerequisites & Cautions

Upgrade Notice: Please note that along with many new features and improvements, the major changes in v16 break some backwards compatibility! The following will be affected when the v16 update is applied:

Services-related API endpoints; reference the breaking changes document for a complete list and new v2 API endpoints.

Services-related DOQL views are affected; reference the breaking changes document for a list of affected views.

Advanced Reporting: Any reports utilizing views listed in the breaking changes document will need to be updated.

The following tools and integrations MUST be updated along with the upgrade to v16:

Netflow users must update their NetFlow collector to support collection of new statistics see Statistics section of this document for details.

The following integrations must also be upgraded to function with this release:

Jira (self-hosted)

ServiceNow (available shortly; release still under review)

Cherwell

For full details around affected API endpoints and DOQL views, please refer to our breaking changes document. Expect a prolonged upgrade time for databases with large volumes of Service instances [see the end of this post for estimates].

Whats new in v16.00.00?

Now that weve gotten the backwards compatibility announcement out of the way (you read the important info above, right!?), were very excited to announce the release of Device42 v16.00.00 for general availability A milestone release chock-full of new features!

v16 Affinity Groups with timelines

To prepare for v16, Device42 developers gathered everything theyd learned over the years and popped the hood on the Services and Application Dependency Mapping (ADM) functionalities to determine how to best develop these features going forward.

In doing so, it was clear that it was time to re-architect the modules a major undertaking! Device42 v16 therefore marks an important milestone, introducing an all-new ADM and Services feature-set that will both better meet customers immediate needs and at the same time lays a better foundation to support future growth.

Change highlights include:

All-new, simplified approach to Services

Affinity Groups Enhancements

A variety of UX Improvements

Packet Capture A new discovery method!

Simplified Services

Device42s approach to Services was overhauled in v16, better aligning the module and its workflows to the way customers are using services in the real world. The net effects of these changes should equate to less duplicated data and better overall information. Working with Services should be easier, too.

Simplified Services Objects & Consolidated Service Instances

Prior to v16, duplicate service instances were common due to variations in startup command line parameters (frequently seen with java-based applications). Device42 now applies new intelligence to the discovery of services, merging services that fall into this category together and storing any historical command line parameter variations within the details view.

Going forward, there will be just one Service record for each service, representing all instances of a given service. Take Java as an example: prior to v16, you might see hundreds of java services on each of your servers; going forward, you will have only one instance (per server).

Additionally, the display name of each service is now customizable (e.g. you might want to rename several instances of java to MyCustomApplication). Discovery will of course seamlessly match against your new name, prioritizing it for the import of the service instances command line arguments.

Introducing Service Listening Ports & Service Communication records

Device42 v16 merges both Service Ports and Service Port IPs into a single object: Service Listening Ports. This combined object now holds only listener information and information about clients connected to each listener. Service objects are no longer created to represent applications and/or services doing client-only communication (e.g. internet explorer and similar).

This information, however, is still captured and can still be seen in the newly introduced Service Communication records, which contain end-to-end information about client-to-service connections. Service Communication records have their own main menu item, which you can navigate to for details about both sides of the conversation regardless of whether both sides have been discovered!

Undiscovered Listeners

Starting with v16, Device42 identifies and surfaces undiscovered listeners that previously blended into service port data. Prior releases captured communications between servers known to D42 and unknown (undiscovered) receiving listeners, but those details were not displayed.

Device42 now automatically creates an Undiscovered Listener to track these communications, and they are now also included in topology charts as a placeholder until subsequent discovery jobs discover them. After upgrading, you may notice that numerous Undiscovered Listeners were created from the historical data already in your system.

Scheduled tasks

Device42 now separates scheduled tasks from services. Scheduled tasks are no longer directly related to services, and now have their own top-level menu item. Scheduled tasks also now have their own APIs and DOQL and are no longer tied to service instances.

Affinity Group Enhancements

Affinity Groups received two important new UI features that should make them even more powerful than they already were: An all-new Visual Timeline, and Affinity Group Calculation views (more info on that below).

Affinity Groups picked up a new Configuration button that makes it easy for users to customize Affinity Group processing, only generating Impact Groups for those users thatdon'tcare to utilize dependency groups. Reference the screenshot to Preview the Affinity Groups Configuration!

Brand-new Visual Timeline

While viewing Affinity Groups, Device42 now displays timestamps, clearly showing when each Affinity Group was changed (both at the device or the service level). This clearly displays when devices and/or services were added or removed from each Affinity Group. The timeline makes it easy to see and quickly navigate to those specific dates when changes occurred, making it easy to see how an Affinity Group changed over time.

This is one feature youll want to play around with!

Affinity Group Calculations

Prior releases offered pre-packaged views into the calculation of affinity groups, namely, the Affinity Group view. This release expands on available views, offering an exploratory view into the calculations. You can explore any device and can look in detail at its dependent and impacted servers (based on the Affinity Group Calculation).

By default, Device42 will only show first-level connections, but you can easily expand each level to go deeper, inspecting 2nd, 3rd, and so-on levels deep. Note that the new visual timeline functionality is not available in exploratory mode; there are too many possibilities to calculate them all. Users can easily, however, utilize the effective date to view a specific dates historical data.

Multiple Application Components for Services

Prior to v16 a given service instance could only be part of a single application component. This limitation often conflicted with real life use cases, where services often play a part across several different applications. This was commonly seen with load balancers, where a given backend server might be answering for multiple front-end application endpoints.

This release alleviates these restrictions and includes updated visuals in support of these architectural changes. Application components will no longer be rendered as container boxes but are now rather displayed as stand-alone nodes; dotted line(s) connect them to associated services and devices. These changes apply across the whole Device42 system.

Note: Due to the required API and DOQL view modifications that support these changes, there will be some backwards-compatibility breakage as a result of these updates. See the breaking changes document for complete details.

Better Statistics

Statistics were restructured to include sample counts as well as information about the number of times a connection was active for netstats. For Netflow, Device42 now includes details both about the time-span a given communication between two endpoints was active (and/or inactive). These statistics provide a clear picture of how consistently a given group of endpoints communicate.

As a side effect of these drastic statistics changes (and to ensure displayed numbers accurately reflect counts going forward), as part of this update, running statistics must be reset; they are not, however, lost The old numbers are preserved in what is now called the classic values view so that they can be referenced if needed. Additionally, we are now only keeping track of statistics from listener perspective, as those have proven to be the most useful (and most accurate) stats.

Netflow collector users MUST update their NetFlow collector when they upgrade to v16 to support these restructured statistics!

Packet Capture A new discovery method

Device42 v16 debuts a brand-new way to gather connectivity data: Packet Capture. This new utility is currently compatible with any Windows or *nix-based machines, and can be customized to filter specific packets of interest.

Device42 users can download the packet capture utility from device42.com and can run it on any supported device to capture detailed communication information flowing both in and out of the targeted network interface.

Keep an eye out for a follow-up post discussing Packet Capture & Device42!

v16 Upgrade time estimates

Expect a longer than usual upgrade time when deploying v16. Users with many service instances (reference chart below) might consider temporarily allocating extra RAM to their Device42 MA instance, which may help speed up the upgrades data migrations. PostgreSQL (Device42s main data-store) loves RAM and will make use of all that is available within reason.

Ensure you have reviewed the upgrade pre-requisites listed at the beginning of this post. V16 includes changes that break backwards compatibility!

The following test data can serve as guidance when for upgrade planning; keep in mind, however, that your mileage may vary depending on the types of data stored in your specific instance & resources available to your MA not all data is processed in the same way!

Service Instances Service Port Remote IPs Tested Time

213,593 1,282,673 0:10:47

336,610 641,479 0:24:01

2,1898 12,744,147 1:48:52

Customers with large DBs (>5GB; check your DB size in Appliance Manager -> System -> Usage/Network Info) may want to contact support to schedule an assisted upgrade email [email protected].

Link to our Blog - https://www.device42.com/blog/2019/08/better-services-management-packet-capture-and-more-in-milestone-release-v16-00-00/

We are excited to announce the general availability of Device42 v15.20.1 with the following changes:

Cloud Recommendation Engine

This release includes the following Cloud Recommendation Engine enhancements, which should make the user experience a bit more intuitive:

Users are no longer required to select the No Tag checkbox if not filtering on tags.

The default selections for the Operating System (OS) filters have been updated so that if the filter is not utilized, all results will be returned by default.

The Cloud Recommendation Engines error messaging for network-related connectivity issues have been improved for greater clarity.

Bug fixes

When utilizing the new tag functionality, virtual machines discovery was only tagging virtual hosts, but not virtual machines. Fixed.

Link to our blog: https://www.device42.com/blog/2019/07/cloud-recommendation-engine-enhancements-in-v15-20-01/

Any non-IP based objects can be added as assets in device42. Few differences from a device object:

Assets don't have unique name constraint. Actually, it doesn't have a name constraint at all. You can add one without assigning a name(not recommended).

Assets don't count towards licensing.

Here is a quick video on how to quickly add such assets to the rack.

Patch panel management aka Structured cable management is discussed more in details as the device42 documentation site: http://docs.device42.com/patch-panels/

We are excited to announce the general availability of Device42 v15.20.00 with the following changes:

Oracle Cloud support added to Cloud Recommendation Engine

This release adds Oracle Cloud support to Device42s Cloud Recommendation Engine (CRE). Users can now get instance recommendations on the Oracle Cloud in addition to recommendations on AWS, Azure, and the Google Cloud platform.

Delete corresponding records on job deletion

Prior to v15.20, deleting a discovery job didnt automatically delete all corresponding records created by that job. Real-world experience made it clear that deleting associated quality score data, queues, etc. when a given job is deleted is a better default behavior. Deleting a discovery job now removes this data automatically, whether the deletion is manual or via the API.

Tag discovered devices

This release adds the ability to configure a discovery job with one or more tags that are then added to all devices discovered by that job. These tags make it simple to figure out exactly which discovery job created or updated a given device CI, to deduce if a given device was created manually, and to simply associate relevant information to subsequently discovered devices.

In support of this new tagging feature, the API now includes thetagsandtags_removedparameters on discovery-job related endpoints.

Bug fixes

Classic reporting could send multiple emails for a single scheduled report. Fixed.

Discovery of virtual F5 appliances could result in an error while updating type and hardware information. Fixed.

Attempts to upload backup files >1GB could fail with a connection reset error. Fixed.

Link to our blog: https://www.device42.com/blog/2019/07/oracle-cloud-support-added-in-v15-20-00/

Device42v15.11.04has been released and is available for download with the following enhancements:

Bug fixes

AS400 discovery was not associating discovered listening ports with services. Fixed.

AS400 discovery was not returning discovered IP addresses. Fixed.

In certain circumstances, a remote discovery agent could overwrite its settings file. Fixed.

VMware discovery could incorrectly calculate thehddsizevalue. Fixed.

Link to the full blog article: https://www.device42.com/blog/2018/11/bug-fixes-in-v15-11-04/

Version 13.4.2

New Features

API: Added tags_remove to the IP Post call to clear the comma separated tags from that IP (/api/1.0/ips/)

Bugfixes:

Fixed clear_all = yes for IP API post call to clear all the tags for that IP, if any.

The Power and Certificate Report Excel Export from the UI was not returning data. Fixed.

SFTP auto-restore was failing in the appliance manager (standby mode). Fixed.

Adding SNMPv3 jobs via API was failing. Fixed.

Link to our blog: http://www.device42.com/blog/2017/06/api-changes-and-bug-fixes-in-v13-4-2/

Version: 13.0.0

Agentless remote collector

Details: http://www.device42.com/blog/2017/03/agentless-remote-collector-with-v13/

Version: 7.3.0

Checkpoint network device support and international language support for Dutch, Japanese, Korean and Portuguese in v7.3.0

Checkpoint network device support

International language support for Dutch, Japanese, Korean and Portuguese

Part list on part model page is hidden for now

Bug fixes

Some wording fixes for Russian and French locales based on user feedback.

Multiple rack deletes from action menu was failing. Now fixed.

Fixed localization on subnet tree page.

With Auto-discovery PDU job specs permissions users were not able to see the menu. Now fixed.

Reports were an hour delayed for time zones ahead of GMT. Now fixed.

Details: http://blog.device42.com/2015/08/checkpoint-network-device-support-and-international-language-support-for-dutch-japanese-korean-and-portuguese-in-v7-3-0/

v315 introduces a robust webserver, hardware and enduser import and better power estimations for easier data center management.

Nginx/uwsgi replace apache/mod_wsgi for webserver

Nginx has more predictable behavior under heavy load and we are replacing apache2 webserver with nginx/uwsgi combination. This means you can now enable CDP for large networks in snmp network discovery as web server can now handle large requests smoothly.

Excel import for hardware models for easier data population

download

Introducing excel import for hardware models so that you can quickly build your hardware library to use in device42. This would work well in conjunction with auto-discovery client and external scripts, where you can add new or modify discovered hardware properties using an excel sheet.

Better estimated Power calculation for racks

As per suggestions from Alex M, we have introduced a PSU redundancy checkbox in hardware model. So no more double calculation for hardware PSU wattage in the rack display. We are simply dividing the # total power supplies by 2 for better estimation. This means, if a hardware model has 2 power supplies which are redundant, only 1 is calculated towards 80% of PSU wattage total and if a hardware model has 5 power supplies, factor of 2.5 is used to calculate towards the 80% of PSU wattage total.

Excel import for end users

Import end users' information using excel sheet.

Option to enable HTTP

As per feedback, we have added an option (in appliance manager) to enable http as well. We don't recommend this setting and if you are using password management module(or planning on using it), you should leave this disabled.

Simpler HTTPS certificate import

HTTPS certificate tab moves out to appliance manager(so you can apply the cert and restart the application from the appliance manager itself).

We are not asking for the CA file anymore, you would just need the cert and key file to apply the cert.(Assuming your browser already has the CA cert installed. Please let us know if you would like to see an option to add the CA cert as well.)

vm console menu option to Apply HTTPS certificate has been taken out.

Other/Cosmetic Enhancements

Added asset # in physical and blade device view.

Help external links now open in new tab/window.

SNMP network discovery task when finished always displayed success if it completed(regarless whether it failed or worked). Message now changed to reflect that task is finished. Debug Info has better status for the discovery.

Added search by location for assets, device type- other and end users.

Options and Settings menu tabs under Tools have been merged into Settings tab.

Bug Fixes

Search button in asset view was broken. Now fixed.

Report > Device report was ignoring the service level. Now fixed.

Asset Type allowed addition for same name with different casing. The validation check is case insensitive now.

Update Link

Current customers can get the update file from device42 update page. We are uploading the new images for trial. Please the v313P1 image and apply this update for your 30 day free trial.

We have redone the spare parts management module in v5.7.0. In this post, we will discuss the changes along with the thought process behind the changes and also answers some questions.

Parts Grouped and Parts Individual

Adding Parts Models

Adding and Tracking Parts

Master Parts List

Parts associated with a Device

Part History

Question: What happens to my current data?

Question: What happens to my current APIs?

Question: What else is cooking for this module?

Purchases Update

Search Improvements

Details available here: http://blog.device42.com/2014/02/better-spare-parts-tracking-with-updated-module-in-v5-7-0-2/

We are excited to announce general availability of v14.2.1 with the following changes:

Backup LDAP/Active Directory Server

We have added the ability to specify a Backup Server for your Active Directory/LDAP Settings. This backup server will be used when the primary server fails to sync.

Devices associated with a password via API

We have added the list of device ids associated with a password to/api/1.0/passwords/. The device ids will be returned in a new array field called device_ids.

Devices API returns module slot number

Module slot numbers have been added to the/api/1.0/devices/id/api if the device is a blade chassis and you are using the follow=yes query parameter.

Assign Software Suite to Software via API

You can now manage your Softwares Software Suite viaapi/1.0/software/. Two new parameters have been added, namely, software_suite_id and software_suite_name to specify the software suite that your software should be associated with. Note that if software_suite_id is used, the name parameter will be ignored.

Port Aliases on Port Reports

You can now add the columnPort Aliaseson a Port Report and additionally choose to display each Alias on a separate line.

Device Part Slots

You can now see the slot a part is on in the Device page > Parts tab.

Ability to Limit Audit Logging / History

You can now turn off audit logging by Model / CI category. Simply select a category to exclude, and audit logs will no longer be generated for that Model / CI type. You can find this feature under REPORTS > History (Audit Log) Exclusions:

Bug Fixes

Not able to change circuit type via API. Fixed

Blade Slot # column is sorted alphabetically rather than numerically. Fixed

Racking a monitored PDU disables monitoring for PDU. Fixed

Issues importing Ping Sweep via XLS or API. Fixed

Known Issues

Windows and Unix Auto-discovery jobs scheduled to run with Service Port Only option enabled do not work but theydon'thave any impact nor do they affect other discoveries.

Link to our blog: https://www.device42.com/blog/2017/11/ability-to-set-backup-ldap-server-in-v14-2-1/

Version: 12.0.0

DOQL: DB views

Port Changes

Support for worldwide numbers (WWN) and fiber switches

Part and Ports

SNMP auto-discovery jobs merged

Part Model Merge

Option to Disable TLSv1.0

Multiple NTP servers

Custom fields for Parts Models and VLANs

Backup Execution time in confirmation email

Port Speed, MTU, and type supported in discovery

API Changes

Bug Fixes

DNS TXT fields type records had a limited size issue which has been fixed.

Details: http://www.device42.com/blog/2017/02/device42-object-query-language-and-major-port-changes-with-v12-0-0/

We are excited to announce general availability of v14.7.0 with the following changes:

TCP Port Scans:

We have added TCP Port Scans to Device42 to facilitate the creation and maintenance of *nix and Windows Auto-Discovery jobs. TCP Port Scan jobs can be created inTools Auto-Discovery TCP Port Scan. These new scans will inspect a range(s) of IPs, determining which have open ports that can be used for Auto-Discovery and whether they are *nix or Windows. Once the scan is complete, Device42 will utilize these results to either create or update an Auto-Discovery job for the qualifying IPs.

This significantly speeds up the existing *nix and Windows auto-discoveries because they no longer perform extensive tests against non-existing IPs or IPs that are not applicable to a particular auto-discovery type. This is especially true for IP ranges containing a random mix of platforms.

While creating a new TCP Port Scan, you may provide the servers range in any supported format and specify which remote collector you want to run the scan on. In addition, you may provide all the settings you want the *nix or Windows auto-discovery job to be created with. This will create the appropriate auto-discovery job for you with the provided naming template and specified settings, and will continue to maintain the list of servers based on the results of each TCP port scan run.

TCP Port Scans can be schedule similarly to all other Auto-Discovery jobs.

Auto-discovery scores:

We have added column with auto-discovery job name (AD Job) to the list of results in auto-discovery scores. In addition, when viewing individual results, we have split the old Issuesfield into Application discovery issues and Container discovery issues. Auto-discovery scores can be found inReports Auto-Discovery Scores

SNMP autodiscovery VLANs to ignore:

We have added additional flexibility to the VLANs to ignorefield to support ranges in addition to comma delimited values.

Bug Fixes:

Auto-discovery creating duplicate devices for EMC Isilon device. Fixed.

Openstack discovery could fail with Index Out of Range Error. Fixed.

Unable to remove an auto-discovery schedule. Fixed

Object category options were not applied to cluster device on VMWare auto-discovery. Fixed.

Lenovo warranty sync could import wrong date for a device. Fixed.

Customer view displays incomplete Subnet list. Fixed.

Version: 8.1.0

Physical connectivity layout improvements in v8.1.0

Direct Patch panel port to patch panel ports connections with drag and drop

Network device ports showing in the module slots

FEX modules with correct ports

Support for alpha-numeric slot #s for blades/modules

Search option in impact charts

Software license management enhancements

Bug fixes

Fixed issue with Export to Excel when report not saved

Fixed issue with localization xls and csv output, use verbose column names

Fixed alert rules

Fixed contracts report

Added patch panel ID to the full path for some patch panel fixes

Details: http://blog.device42.com/2015/09/physical-connectivity-layout-improvements-in-v8-1-0/

Following bugs were fixed in v9.5.3

Some network devices were being discovered with Chassis setting set to checked. It is now fixed, but it will not change previously discovered switches/routers automatically.

Password edit page with custom field was throwing an error. Now fixed.

We are excited to announce the following enhancements in Device42 v14.5.0:

DOQL access for non-super users

Non-super users can now run DOQL queries. Object access is limited by their functional permissions (and further restricted by multi-tenancy).

Performance enhancements for multi-tenancy

This comes with a big backend change to process multi-tenancy rules faster.

Dont propagate option for buildings and rooms

If you are using multi-tenancy, you can select an option to not propagate permissions down to child objects from the building or the room level.

SVG export for racks (which can be imported into Visio)

You can now SVG export your rack images. Check out this post to learn how to import your exported SVG files into Visio.

View password event now available in webhooks

If you want to monitor who viewed a password in an external system, you can now enable the view webhook type to do just that.

Auto-discovery enhancements

Instance name added to AWS autodiscovery. It can be found in the cloud info section. If you have a different hostname than the instance tag name in the AWS console, it will now capture that.

Added service level and customer selection to all hypervisor related auto-discovery jobs

API Changes

Added aliases_remove to devices POST call that takes a CSV (comma separated values) of aliases to be removed from that device.

Added outlet_name to GET and POST calls to power_units API calls.

Added API calls for TAP ports and model changes.

Bug Fixes

Unicode characters in the server field in auto-discovery jobs were creating issues in some edge cases. Now fixed.

Link to our blog: https://www.device42.com/blog/2017/12/doql-access-for-non-super-users-and-api-changes-in-v14-5-0/

Version: 9.8.0

Uninterrupted power supply and automated transfer switch management

Enhancements for telco circuits

VMWare auto-discovery enhancements

API Changes

Additions for Lifecycle events

Cosmetic Changes

Bug Fixes

Network job export/import issues

if rack_id is not valid it adds a new rack instead of failing. Fixed

Fixed localization issue with impact/dependency charts

Added fixes to calculate total available Us in a rack as it was failing in certain cases.

Auto-restore feature asks for registration on backup instance again and again. Fixed.

return correct manufacturer for API GET call /operatingsysytems/

PDU on layout page is now based on size and not # of ports

re-importable export fixed for power circuits

x_pos is now respected in rack dev api call

re-importable part issue fixed. part_id instead of partmodel_id.

vm cpu count issue fixed in vmware auto-discovery.

show multiple PDUs on the PDU map in a rack

Bulk IP operations issue where IP could not be made available when editing is now fixed

Bottom cutoff fixed when exporting image for rack layout page

Merge tags option was missing for 64 bit OS. Now fixed.

Uninterrupted datacenter power management with Device42 now!

Details: http://blog.device42.com/2016/05/track-ups-and-ats-for-better-data-center-power-management-with-v9-8-0/

Version: 12.1.5

Better performance for device topology charts

Bug Fixes

GET api call for operating systems was failing. Fixed.

Patch panel ports re-importable exports was broken. Fixed.

Details: http://www.device42.com/blog/2017/03/better-performance-for-service-dependency-mapping-topology-in-v12-1-5/

Occasionally we need to access your appliance in a remote session. This is for health check and troubleshooting purposes. Being that Device42 is an on-premise appliance we do not have access to your data or settings.

When there is an issue we need to be able to perform certain tasks in a guided live session with the customer. For these instances we have a hidden option 18 in the VM console so we can use our Secure OTP process to gain access and check your appliance in a live session.

Citrix Xen Virtualization auto-discovery is now available in device in v5.1.1! This version also brings enhancements to the subnet tree and some bug fixes as discussed below.

Citrix Xen Virtualization Support

http://www.device42.com/update/

You can now connect to a Citrix Xen server and auto-discover the following information:

For Hosts: Host name, serial #, hardware model, OS version and build #, CPU info, IP and/or MAC address info.

For VMs: VM name, UUID, MAC address(es), CPU/memory info and power state(in service).

The Citrix Xen auto-discovery capabilities can be found under Tools > Auto-Discovery > vCenter where you can choose between vmware and Citrix Xen discovery.

Enhanced subnet tree

As per this feature request from Hugh Davie on the device42 support portal, we have added IP address labels to the subnet tree. Also, the subnet and IP are now clickable. A click causes a view page to appear in a popup window.

Bug fixes

We have addressed following bugs/issues with v5.1.1:

DNS record import failed if a record type was not recognized. Now the auto-discovery ignores that single record, logs it, and continues the import process.

View password was not showing a complete password if the password had either a '<' or a '>' in the password string.

A performance issue with lots of passwords has been fixed.

A room drag/drop issue was fixed where users were able to drag certain objects on top of existing objects.

A device energy/power utilization chart time range issue was fixed.

DCIM software download

Device42 DCIM software v5.1.1 is now available for download at: http://www.device42.com/download/

Current customers can grab the latest update file from: