Getting Started with Power and Environmental Monitoring

To access the functionality described in this section, you must have licensed one of the optional Power Modules. Most of the power and environmental monitoring capabilities are present in the base power monitoring option. To turn outlets on and off, you will need the power control option in addition. See the Device42 power pricing page for more details.

Note to Power Monitoring / Control Users: The Standalone Power Appliance is being depreciated, and all related functionality is now available in Remote Collectors (RC’s). Please utilize RC’s for power / environmental monitoring or control going forward. See the Remote Collector page for setup details and for information on obtaining a Remote Collector going forward!

The actual monitoring occurs in a separate virtual appliance from the main Device42 appliance. Please note that you can optionally monitor power using Device42 Remote Collectors from v14.0.0 forward, as well as the dedicated power appliance. This is done for three reasons:

  1. First, continuous monitoring is fairly resource intensive and would interfere with the primary Device42 functionality if run on the same appliance.
  2. Second, you have the flexibility to place the monitoring appliance in a separate network segment.
  3. Third, you can deploy multiple monitoring appliances that all talk to the same main Device42 appliance. This gives you the ability to locate monitoring appliances in sensitive network segments and open the minimal number of ports.


The installation process for one or more monitoring appliances is similar to installation of the Device42 main appliance. If you would like to set up power monitoring using a Remote Collector (RC), see the instructions for setting up an RC.

Refer to the appropriate link(s) below for installation on your selected virtualization platform:
VMWare Player
Virtual Box
Citrix Xen Server
Microsoft Hyper V
vCenter Server

Follow the steps for your selected virtualization platform to:
– Download the virtual appliance zip file.
– Use 7 zip to unzip the downloaded file.
– Open or Import the virtual appliance into vmware player
– Once the import is finished, power on the new virtual appliance.
– Login to console as ubuntu/default (you can change the password with option 10)
– On the console, configure the IP [Please use a STATIC IP for all production Device42 Installations to avoid connection losses] and choose your settings.
– Optional: Create DNS entry for the new IP address for the new virtual appliance.

Please note, however, that the default monitoring appliance username/password is ubuntu/default (this is different than the main appliance default password. Please be sure to change the password after you login.

Monitoring Appliance IP

Monitoring Appliance IP

Instead of loading the url into a browser (like you did when you loaded the main Device42 virtual machine), you will go to the main Device42 appliance via your browser, navigate to Tools>>Settings>>Monitoring Appliances. If you have two monitoring appliances deployed, the list view screen would show…

Though you are limited by the Device42 license to deploying a single production main appliance, you can deploy an unlimited number of monitoring appliances under that same license. To add a monitoring appliance, click add and you will see…

You will enter the url of each monitoring appliance here. After clicking “Save and continue editing”, you can test the connection to the monitoring appliance by clicking the Test Connection button.

You can also enter one or more email addresses of people who should receive email notifications if the main Device42 appliance detects that the monitoring appliance is down.

You can setup multiple monitoring appliances by entering multiple screens like the one above.

Please also read this section of the documentation concerning maintaining the IP’s on the monitoring appliance.

Capacity Considerations

Monitoring is a fairly resource-intensive process and as a result, each individual monitoring appliance is limited in the number of pdus, infeeds, and outlets it can handle. When you set up each autodiscovery job (see below), you will choose a polling interval. The primary resource limitation is the number of snmp polls that can be done in the selected polling. So, if you select a 5-minute polling intervals, you monitor 5x the number of pdu’s in one monitoring appliance as you can if you select 1-minute polling intervals.

At 5-minute intervals (default), Device42 recommends that you have one monitoring appliance per 200 pdu’s. At 1-minute intervals, assume 40 pdu’s. If your network is at all sluggish, reduce the number of pdu’s per monitoring appliance. Remember, you can deploy as many monitoring appliances as you need with no additional license cost.

Power Unit Autodiscovery

PDU Autodiscovery

Autodiscovery of power-enabled pdu’s is very similar to Device42 Network Autodiscovery. Navigate to Tools>>Autodiscovery>>SNMP. You will enter an IP address range, a port, and SNMP information. Before you can do this, you must have setup the monitoring appliance as described above. There is a Test Connection that will test the connection to the monitoring appliance. NOTE that you will not see the Power (SNMP) discovery option in the TOOLS –> Auto-Discovery menu if a power appliance is not registered. Once an appliance is registered in Device42, the option will be visible.

You can also set the polling interval for this set of pdu’s by entering a value in the Polling Interval field. This value causes the monitoring to poll each pdu with the frequency defined by this field.

NOTE: Checking the “Delete Ports” Checkbox will force deletion of all ports that do not match was is currently discovered. If you have power units that show more ports than they should, selecting this option should remedy it:

Delete Ports Checkbox

Environmental Monitoring

The Autodiscovery job just described will also find any environmental sensors attached to the pdu (by the vendor) such as heat, temperature, and humidity sensors.

Environmental sensors from RFCode will be discovered. Set up RFCode discovery by navigating to Tools>>Autodiscovery>>RFCode.

The required data to be entered for each RF Code Zone Manager is:

Zone Manager Name : The Zone Manager name
Zone Manager IP Address : The Zone Manager IP address
D42 Monitoring Appliance : Choose which D42 monitoring appliance to use.
Polling Interval : See Polling Interval for PDU’s above.
Username : Login username for the Zone Manager
Password : Password for the Zone Manager

RF Code autodiscovery jobs can be scheduled just like PDU autodiscovery jobs (see above).

There is also a Location Data Pattern Section (see below). This section is optional. Fill it in only if you want Device42 to parse the location descriptor to get the location of each sensor.

You can define up to 5 segments in the RF Code location description field. For each segment, choose the type of object being identified by the segment (see red box above). You can also add a Segment End Delimiter for each segment. For example, if the segments are separated by a semicolon, then you would put just a semicolon in each of the Segment n End Delimiter boxes.


Note: It is recommended that you place RF Code sensor monitoring in a separate monitoring appliance that is not also monitoring PDU’s. Just as with PDU’s, you can have multiple monitoring appliances for RF Code sensors.

When sensors are discovered, they are created with Asset records in Device42. If you navigate to Devices>>Assets>>PDU Sensors, you will see a list of all pdu-attached sensors discovered. If you navigate to Devices>>Assets>>RFCode Sensors, you will see a list of all RFCode sensors discovered.