Enhanced custom fields, console server auto-discovery, support for variable width devices and devices outside the rack in v7.1.0

We are excited to announce availability of v7.1.0 with changes around rack elevations, custom fields and power module. We will discuss power related changes in the next blog post and all other changes are discussed below.

Security Fix – The export cipher suites have been disabled in OpenSSL

We updated openssl for Ubuntu Security Notice USN-2624-1

Enhanced Custom Fields


We have 3 new types for custom fields – Related Field, Boolean and URL.

With Related field, you can choose an existing data category like Building, Asset, Device, IP Address and you can then select an existing object for a custom field.

With Boolean (Yes/No) field, you will get to choose “Yes/No” for that custom field.

With URL, it is a simple URL field, which basically becomes clickable on the object view page.

Variable width devices in a rack


You can now add hardware models with variable width (upto 1/10th). With this you can easily represent 1/2 width or 1/4 width devices side by side in the rack. With easy drag and drop in the rack, you can perfectly align these devices as in real life.

There are some more changes around adding devices/assets/PDUs to the rack. On the left hand side bar, you can search by hardware model and drag a new device to its new place. Similarly, you can add a new asset and PDU,

Add devices and Assets around the rack

If you have devices/assets that are around the rack, you can visualize those as well. Default is still “Rack Mounted”, but you can choose to add these on left, right, top or bottom.

What If Scenarios


You can now run What If Simulations for adding devices to racks. You can choose what type of devices you are adding and it will go through selected building, room or racks and give you before and after snapshot of the selected racks.

This is available under Tools > Templates & Bulk Operations > What if.

For power check, you need to have power monitoring module and iPDUs in the racks to estimate power usage.

Auto-Discover Console Server

You can now auto-discover OpenGear and Avocent ACS Console Server with ports. This is done via Tools > Auto-discovery > Other SNMP devices.

Load Certificates from a file


When adding a new certificate, you can now load an existing file (.pfx. .crt).

Parts assignment to a storage racks

If the parts are being stored in a rack, you can now document that as well.

Add a note to login page


From Tools > Settings > Global Settings, you can now upload a text file (Markdown), which will be shown on the login page. If you have some instructions for your users logging into the system or other notes, you can add those here (along with links).

Bring your logo to the Device42 App


Similar to the instructions, you can also upload a logo from global settings. The logo will show up in login page and also throughout the app on the menu bar next to the username.

Network Device and Blade Host properties carry over from hardware model to device


We have added option to mark hardware model as Network Device. If a hardware model is network device and/or Blade Host/Chassis, that property is automatically carried over to any newly created device.

Added "First added" to Devices, IPs etc.

Categories like devices, IPs, MAC address, VLAN and few more get a new field to record First added (in D42) date. For users with existing data, we went with the last updated date (or time of update, if that is missing). But, as you add any new data, you will have correct First added date.

API Changes

Following API changes in this release:

  • Added auto_delete to a DNS auto-discovery job.
  • added first_added_lt & first_added_gt filtering to get api for devices, ips, macs and parts
  • name, room and building filters for racks get API.
  • Added is_it_switch to hardware model API
  • Added where to the API call when mounting devices or assets to a rack.
  • related_field, url and boolean added as type for a custom field.

Bug Fixes

  • Adding new “Software in use” from the form was erroring out. Now Fixed.
  • device_id for Device PUT API call was not working. Now fixed.
  • AD login failed with special character in password. Now fixed.


Share this post

About the author