Adding a PDU
Add a new PDU by heading to the Device42 main menu: DataCenter > Power Units > Power Units. Relevant PDU-related fields are listed & defined below.
Note that PDUs (like almost all D42 CI) can also be added and/or manipulated via the API.
PDU Field descriptions
PDU field: description – required [yes/no]
Name: Name your PDU – required
Type: PDU, UPS, or ATS – required
Power Unit Model: Choose the PDU model – Must be defined if the PDU is rack mounted and/or to track individual ports on the PDU
Serial #: Name your PDU – required
Is monitoring enabled: Name your PDU – required
Storage Room: Name your PDU – required
Bootstrap Power: Name your PDU – required
Rated Power: Name your PDU – required
First Added: Name your PDU – required
Last updated: Name your PDU – required
Object Category: Name your PDU – required
Tags: Name your PDU – required
Notes: Name your PDU – required
Device Mapping section
Device Mapping Section – PDU:
Device: Associating your PDU with a device is required only if you want to track IP address, life cycle, or other asset information for the PDU; IP and asset info is tracked via the chosen device – optional.
- Serial #: If PDU is mapped to a device, the serial number of the mapped device is shown here.
- Asset #: If PDU is mapped to a device, the asset number of the mapped device is shown here.
Gateway PDU Mapping Section:
Gateway PDU: If this PDU is plugged into another PDU [aka daisy chained], identify the “Gateway PDU” it is plugged in to, if any. – optional.
Infeeds: Power infeed information will display here – n/a; auto-discovered.
Custom Fields: any custom fields you have created for PDUs will display here. Custom fields are optional.
Upon saving your new PDU, Device42 will automatically add ports based on the selected PDU model.
Note that ports can only be added at the time of PDU creation and cannot be altered later!
Automatically created Ports
When a new PDU is created via the click of the “Save” button, PDU ports are created automatically based on the port layout defined on the chosen PDU model. For information on defining your PDU model(s), see the Defining PDU Models section of the Device42 Docs.
Mapping PDU’s to a Device
To track details about a PDU, e.g.: The PDU serial #, asset #, PUD IP address, purchase information, life-cycle management, etc., the PDU can be mapped to a device. To create a device for the purpose of PDU mapping, simply do the following:
- Create a new Device, setting its Device Type = Other (see image above). It is recommended (but not required) that the device be named the same as the PDU that you will be mapping it to better organize.
- Set the new device’s Device Subtype to PDU (see the above image). There is no need to define hardware, and all other fields are optional.
- Save the new device.
- Head back to the PDU ci that will be linked to the device you just created. Edit the PDU by clicking the “edit” button, and click the magnifying glass on the Device Mapping option (see the image below). Choose the device you created in steps 1-3 by clicking on its name in the “Select Device” popup.
Save the changes to the PDU
Viewing & navigating between a mapped PDU and Device
Jumping from a device to the PDU it’s plugged in to, or from a PDU to the device page of a device that’s plugged into it is simple:
Above image – PDU mapping page, with a link to the device’s details page.
Below image- Device mapping page, links back to the PDU detail page.