PX-Series PDU User Guide | PX2, PX3, PXO,
PXCCopyright © 2023 Raritan
PDU-G2-UG-B1-4.1.0
August 2023
Release 4.1.0

Contents
Introduction to Xerus Technology Platform PDUs - PX-Series User Guide
13
Raritan PDU Product Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Safety Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Safety Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Package Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Zero U Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1U Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2U Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
APIPA and Link-Local Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Unpacking the Product and Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Preparing the Installation Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Checking the Branch Circuit Rating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Filling Out the Equipment Setup Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Rackmounts
21
Rack-Mounting the PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Rackmount Safety Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Mounting Zero U Models Using L-Brackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Mounting Zero U Models Using Button Mount. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Mounting Zero U Models Using Claw-Foot Brackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Mounting Zero U Models Using Two Rear Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Mounting 1U or 2U Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
PXO Rackmount Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Connecting a PX3 Locking Line Cord. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Disconnecting a PX3 Locking Line Cord. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing Cable Retention Clips on the Inlet (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Installing Cable Retention Clips on Outlets (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
SecureLock™ Outlets and Cords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Button-Type Locking Outlets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Circuit Breaker Orientation Limitation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Initial Installation and Configuration
37
Connecting the PDU to a Power Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Connecting to Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Dual Ethernet Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring the PX-Series PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

ii

Connecting a Mobile Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Saving User Credentials for PDView's Automatic Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Connecting to a Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
RJ45-to-DB9 Cable Requirements for Computer Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Bulk Configuration Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Cascading for Shared Ethernet Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Best Practices for Cascading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Power-Sharing Restrictions and Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Power Sharing Port on iX7 Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Making a Power-Sharing Connection - iX7 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Power-Sharing Configurations and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Supported Sensor Configurations for Power Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Linking Units
54
FAQs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Linking in the Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Viewing the Primary Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Options for Adding Link Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Adding a Link Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Linking Cascaded Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Primary Units Manage Link Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Releasing a Link Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Switching to a Different Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Re-linking a Link Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Viewing Link Unit Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Outlet Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Pairwise Outlet Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
OCPs Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Peripherals Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Asset Strips Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Displays for Primary and Link Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Linking in the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Linking CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Using the Hardware Features
80
Inlet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Zero U Models Relocatable Inlet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Outlets and Outlet LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
PX3-1000/PX2-1000 Series Outlets (No LEDs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
PX3-3000/PX2-3000 Series Outlets (No LEDs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
PX3-4000/PX2-4000 Series Outlets and LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

iii

PX3-5000/PX2-5000 Series Outlets and LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
PXC and PXO Switched Series Outlets and LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
PXC and PXO Metered Series Outlets (No LEDs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Connection Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
PX3-Series Connection Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
PX2-Series Connection Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
PXE Connection Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Legrand PDU, PXC, and PXO Connection Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Connection Port Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Front Panel Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Automatic and Manual Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Control Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Operating the Front Panel Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Port Overload - Reset Fuse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Alerts Notice in a Yellow or Red Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Manually Changing Zero U LCD Orientation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Showing the Firmware Upgrade Progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Reset Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Circuit Breakers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Resetting the Button-Type Circuit Breaker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Resetting the Handle-Type Circuit Breaker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Fuse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Fuse Replacement on Zero U Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Fuse Replacement on 1U Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Beeper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Replaceable Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Threaded Grounding Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Using the Web Interface
132
Supported Web Browsers and Mobile Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Login, Logout and Password Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Login and Logout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Changing Your Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Web Interface Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Quick Access to a Specific Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Sorting a List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Dashboard - PDUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

iv

Dashboard - Inlet I1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Dashboard - OCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Dashboard - Alerted Sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Dashboard - Inlet History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Dashboard - Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Internal Beeper State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Latching Relay Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Options for Outlet State on Power Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Initialization Delay Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Inrush Current and Inrush Guard Delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Trip Cause Outlet Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Time Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Setting Thresholds for Total Active Energy or Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Minimum and Maximum Values for Numeric Sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Power Supply Sensor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Inlet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Configuring a Multi-Inlet Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Outlets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Available Data of the Outlets Overview Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Threshold Bulk Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Sequence Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Load Shedding Setup: Setting Non-Critical Outlets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Load Shedding Mode: Activate or Deactivate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Individual Outlet Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Outlet Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Creating an Outlet Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Outlet Group Power Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Resetting a Group's Energy Counter and Minimum/Maximum Values. . . . . . . . . . . . . . . . . . . . . . . . . 182
Modifying an Outlet Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Deleting an Outlet Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Viewing More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
OCPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Individual OCP Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
OCP Trip-Cause Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Peripherals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Yellow- or Red-Highlighted Sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Managed vs Unmanaged Sensors/Actuators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Sensor/Actuator States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Finding the Sensor's Serial Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Identifying the Sensor Position and Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Automatic Management of Sensors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201v

Managing One Sensor or Actuator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Individual Sensor/Actuator Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Z Coordinate Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Serial Access With Dominion Serial Access Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
DSAM Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
DSAM LED Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
View DSAM Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Configure DSAM Serial Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Connect to DSAM Serial Targets in the Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
DSAM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Connect to DSAM Serial Targets via SSH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Asset Strips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Asset Strip Automatic Firmware Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
External Beeper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Power CIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Creating Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Editing or Deleting Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Creating Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Editing or Deleting Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Setting Your Preferred Measurement Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Setting Default Measurement Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Device Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Configuring Network Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Configuring Security Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Setting the Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Door Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Event Rules and Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Setting Data Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Configuring Data Push Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Monitoring Server Accessibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Front Panel Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Configuring the Serial Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Lua Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Using Prometheus and Grafana. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Requirements for Prometheus and Grafana. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Collected Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

vi

Device Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Viewing Connected Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Viewing, Pausing, Resuming or Clearing the Local Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Updating the Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Viewing Firmware Update History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Bulk Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Backup and Restore of Device Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Network Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Downloading Diagnostic Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Hardware Issue Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Rebooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Resetting All Settings to Factory Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Webcam Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Configuring Webcams and Viewing Live Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Sending Links to Snapshots or Videos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Viewing, Downloading, Deleting Locally-Saved Snapshots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Changing Storage Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
SmartLock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Door Status and Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Card Readers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Using SNMP
397
Enabling and Configuring SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
SNMPv3 Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
SNMPv2c Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Downloading SNMP MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
SNMP Gets and Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
The MIB File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
SNMP Sets and Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Configuring NTP Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Retrieving Energy Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Using the Command Line Interface
404
Logging in to CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
With HyperTerminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
With SSH or Telnet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
With an Analog Modem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Different CLI Modes and Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Closing a Local Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Logging out of CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Tips for Using the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

vii

The ? Command for Showing Available Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Querying Available Parameters for a Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Retrieving Previous Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Automatically Completing a Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Multi-Command Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Showing Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Device Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Outlet Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Outlet Group Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Inlet Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Overcurrent Protector Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Date and Time Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Default Measurement Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Environmental Sensor Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Environmental Sensor Package Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Actuator Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Outlet Sensor Threshold Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Outlet Pole Sensor Threshold Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Outlet Group Threshold Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Inlet Sensor Threshold Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Inlet Pole Sensor Threshold Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Overcurrent Protector Sensor Threshold Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Environmental Sensor Threshold Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Environmental Sensor Default Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Security Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Authentication Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Existing User Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Existing Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Load Shedding Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Serial Port Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Asset Strip Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Rack Unit Settings of an Asset Strip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Network Connections Diagnostic Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Server Reachability Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Peripheral Devices Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Command History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Reliability Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Reliability Error Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Reliability Hardware Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

viii

Clearing Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Clearing Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Clearing Diagnostic Log for Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Configuring the Device and Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Device Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Network Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Time Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Security Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Outlet Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Outlet Group Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Inlet Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Overcurrent Protector Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
User Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Role Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Authentication Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Environmental Sensor Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Configuring Environmental Sensors' Default Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Sensor Threshold Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Actuator Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Server Reachability Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Peripheral Devices Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Asset Management Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Serial Port Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Load Shedding Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Power Control Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Actuator Control Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Unblocking a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Resetting the PX-Series PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Restarting the PX-Series PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Resetting Energy Readings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Resetting to Factory Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Network Troubleshooting in Diagnostic Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Querying DNS Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Showing Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Testing the Network Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Tracing the Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Example - Ping Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Example: Ping Monitoring and SNMP Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
In-Line Monitors
564
Safety Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Flexible Cord Installation Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564

ix

Flexible Cord Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Plug Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Receptacle Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Derating a Raritan Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Wiring of 3-Phase In-Line Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
In-Line Monitor Unused Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Installing the Flexible Cord. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
In-Line Monitor's Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Dashboard Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Inlets/Outlets Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Appendices
580
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
PX3-Series PDU and Transfer Switch Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
PX2-Series Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
PXE Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
PXC/PXO Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Equipment Setup Worksheet Sample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Special Configuration and Upgrade Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Configuration or Firmware Upgrade with a USB Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Bulk Configuration or Firmware Upgrade via DHCP (TFTP/HTTPS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Raw Configuration Upload and Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Bulk Configuration, Firmware Upgrade, or Backup/Restore via SCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Cascading Solutions for Xerus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Cascading Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Cascading Procedure Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Cascading Modes Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Setting the Cascading Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Device-Cascading Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Adding, Removing or Swapping Cascaded Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Accessing Cascaded Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Identifying Cascaded Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Firmware Upgrade for Cascading Chains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Cascade Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Resetting to Factory Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Factory Default Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Using the CLI Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Using the Reset Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Models with Residual Current Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
RCM Current Sensor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
RCM State Sensor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Compliance with IEC 62020. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680

x

RCM Self-Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Web Interface Operations for RCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Front Panel Operations for RCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
RCM SNMP Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
CLI Operations for RCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Remote Authentication Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
LDAP Configuration Illustration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
RADIUS Configuration Illustration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Cisco ISE Xerus TACACS+ Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Updating the LDAP Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Returning User Group Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Setting the Registry to Permit Write Operations to the Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Creating a New Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
Adding Attributes to the Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Updating the Schema Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Editing rciusergroup Attributes for User Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Additional Xerus Information - Assorted Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Reserving IP Addresses in DHCP Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Sensor Threshold Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Default Voltage and Current Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Altitude Correction Factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Unbalanced Current Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Ways to Probe Existing User Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Role of a DNS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Installing the USB-to-Serial Driver (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Device-Specific Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
TLS Certificate Chain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
Xerus Product Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Connecting a PDU to a Dominion KVM or Serial Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Power IQ Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
dcTrack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Third Party Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Licenses - Angular. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Licenses - Bind9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
Licenses - Clish. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Licenses - Dropbear. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Licenses - FreeType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
Licenses - IW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
Licenses - JSON-C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
Licenses - LIBTIRPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
Licenses - LIBXML2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
Licenses - Mbus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773

xiLicenses - Net-SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
Licenses - Open LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Licenses - OpenSSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
Licenses - Wireless-RegDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
Licenses - WPA Supplicant and Hostapd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
Index

xii

784

Introduction to Xerus Technology Platform PDUs PX-Series User Guide
Raritan's data center power products include rack power distribution units (rack PDUs), inline meters,
transfer switches, and branch circuit monitoring systems. Leveraging Xerus Technology Platform, all
Raritan power distribution products improve uptime and availability by making power management
devices easier to deploy, control, and manage remotely across multiple locations. Natively compatible
with DCIM software, Raritan power distribution products allow you to easily scale new environmental
monitoring and access control devices as well as gather actionable insights for quicker, smarter decision
making.
The PX Intelligent Rack PDU series provides reliable power distribution for IT equipment cabinets. It
offers metering at the inlet, outlet, and PDU circuit breaker level. Support for 120 to 400V: single orthree-phase. Form factors from Zero to 3U. Plus environmental monitoring support.
The PX Inline Meter series (PX3-3000 series) is a simple way to add power and environment monitoring
to other vendors’ basic PDUs. It also monitors standalone IT equipment. Simply wire or plug the inline
meter into existing circuits. See real-time power data and check for hot spots.
This User Guide/Online Help covers all Raritan PX-Series Xerus PDUs and inline
meters except for the newest, PX4 PDU.
•

PX3

•

PX2

•

PXC

•

PXO

▶ Differences Between Models•

All Xerus Technology Platform features that are supported on PX Series PDUs are documented here.
Not all models support all features. Unique differences between models are documented with thespecific product name.

Product models

PX2

PX3

PXC / PXO

Front panel display

LED display

Dot-matrix LCD display

Dot-matrix LCD
display

Outlet latching relays*

Number of LAN ports

1

2

2

Maximum LAN rate

100 Mbps **1,000 Mbps

100 Mbps

13

Product models

PX2

PX3

PXC / PXO

Replaceable controller***

Number of USB-A ports

1

2

1

Maximum USB rate

12 Mbps

480 Mbps

480 Mbps

RS-232 port (CONSOLE/MODEM)

Male DB9
Connector

RJ-45 Connector

RJ-45 Connector

Expansion ports

SENSOR port type

14

****
RJ-12

RJ-45

RJ-45

▶ PX Series comparison in brief:
Features

Inlet power
measurement

Outlet power
measurement

OutletswitchingLoadshedding

1000 Series

2000 Series

3000 Series(Inline meters)

4000 Series

5000 Series▶ Other Xerus Products:
Are you looking for documentation on other Xerus products not listed above? Go to www.raritan.com/
support to find documentation for the following Xerus platform products:•

PX4 intelligent rack PDUs•

BCM2 Branch Circuit Monitor and Power Meters•

PX3TS Transfer Switch•

SRC Smart Rack Controller

In This Chapter
Raritan PDU Product Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Safety Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Safety Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Package Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
APIPA and Link-Local Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Raritan PDU Product Models
Raritan offers the broadest portfolio of Rack PDU configurations, with the most options for outlet
metering. With more than 1000 different models, we are sure you will find the Rack PDU that meets
your exact needs (and if you don't, let us know and we'll build it).

15

Visit the Product Selector page https://www.raritan.com/product-selector on Raritan's website, or
contact your local reseller for a list of available models.

Safety Instructions
1. Installation of this product should only be performed by a person who has knowledge andexperience with electric power.
2. Make sure the line cord is disconnected from power before physically mounting or moving thelocation of this product.
3. This product is designed to be used within an electronic equipment rack. The metal case of thisproduct is electrically bonded to the line cord ground wire. A threaded grounding point on the casemay be used as an additional means of protectively grounding this product and the rack.
4. Examine the branch circuit receptacle that will supply electric power to this product. Make sure thereceptacle’s power lines, neutral and protective earth ground pins are wired correctly and are thecorrect voltage and phase. Make sure the branch circuit receptacle is protected by a suitably rated
fuse or circuit breaker.
5. If the product is a model that contains receptacles that can be switched on/off, electric power may
still be present at a receptacle even when it is switched off.
6. The outlet (socket) shall be installed near the equipment and shall be easily accessible.
For detailed information on any PDU's overcurrent protectors' design, refer to that model's productspecification.

16

Safety Guidelines
WARNING! Before installing or operating this product, read and understand all sections in this guide.
WARNING! Connect this product to an AC power source with a voltage that is within the range specified on the
product's nameplate. Operating this product outside the nameplate voltage range may result in electric shock,fire, personal injury and death.
WARNING! Connect this product to an AC power source that is current limited by a suitably rated fuse or
circuit breaker in accordance with national and local electrical codes. Operating this product without proper
current limiting may result in electric shock, fire, personal injury and death.
WARNING! Connect this product to a protective earth ground. Never use a "ground lift adaptor" between the
product's plug and the wall receptacle. Failure to connect to a protective earth ground may result in electric
shock, fire, personal injury and death.
WARNING! This product contains no user serviceable parts. Do not open, alter or disassemble this product. All
servicing must be performed by qualified personnel. Disconnect power before servicing this product. Failure tocomply with this warning may result in electric shock, personal injury and death.
WARNING! Use this product in a dry location. Failure to use this product in a dry location may result in electric
shock, personal injury and death.
WARNING! Do not rely on this product's receptacle lamps, receptacle relay switches or any other receptacle
power on/off indicator to determine whether power is being supplied to a receptacle. Unplug a device
connected to this product before performing repair, maintenance or service on the device. Failure to unplug adevice before servicing it may result in electric shock, fire, personal injury and death.
WARNING! Only use this product to power information technology equipment that has a UL/IEC 62368-1 orequivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury anddeath.
WARNING! Do not use a product containing outlet relays to power large inductive loads such as motors orcompressors. Attempting to power a large inductive load may result in damage to the relay.
WARNING! Do not use this product to power critical patient care equipment, fire or smoke alarm systems. Useof this product to power such equipment may result in personal injury and death.

WARNING! If this product is a model that requires the assembly of the line cord or plug, the assembly must be
performed by a licensed electrician, and the line cord or plugs used must be rated based on the product's
nameplate ratings, as well as national and local electrical codes. Assembly by unlicensed electricians or failure
to use suitably rated line cords or plugs may result in electric shock, fire, personal injury or death.
WARNING! This product contains a chemical known to the State of California to cause cancer, birth defects, orother reproductive harm.

Package Contents
The following sub-topics describe the equipment and other material included in a typical product package.

Zero U Products•

One PX-Series PDU•

Screws, brackets and/or buttons for Zero U

1U Products•

One PX-Series PDU•

1U bracket pack and screws•

Cable retention clips for the inlet (for some models only)

2U Products•

One PX-Series PDU•

2U bracket pack and screws•

Cable retention clips for the inlet (for some models only)

APIPA and Link-Local Addressing
PX-Series PDU supports Automatic Private Internet Protocol Addressing (APIPA).
With APIPA, your PX-Series PDU automatically configures a link-local IP address and a link-local host namewhen it cannot obtain a valid IP address from any DHCP server in the TCP/IP network. Only IT devices
connected to the same subnet can access the PX-Series PDU using the link-local address/host name. Those in adifferent subnet cannot access it.
Exception: Port Forwarding mode does not support APIPA.
Once the PX-Series PDU can get a DHCP-assigned IP address, it stops using APIPA and the link-local address is
replaced by the DHCP-assigned address.

▶ Scenarios where APIPA applies:•

DHCP is enabled on the PX-Series PDU, but no IP address is assigned to the PX-Series PDU. This may becaused by the absence or malfunction of DHCP servers in the network. For example, connecting the PXSeries PDU to a computer using a network cable.

•

The PX-Series PDU previously obtained an IP address from the DHCP server, but the lease of this IP address
has expired, and the lease cannot be renewed, or no new IP address is available.

▶ Link-local addressing:•

IPv4 address:•

Factory default is to enable IPv4 only. The link‑local IPv4 address is 169.254.x.x/16, which ranges
between 169.254.1.0 and 169.254.254.255.
IPv6 address:•

A link-local IPv6 address is available only after IPv6 is enabled on the PX-Series PDU. See
Configuring Network Settings.
Host name - pdu.local:
You can type https://pdu.local to access the PX-Series PDU instead of typing the link‑local IP
address.

▶ Retrieval of the link-local address:•

See Device Info.

Before You Begin
Before beginning the installation, perform the following activities:•

Unpack the product and components•

Prepare the installation site•

Check the branch circuit rating•

Fill out the equipment setup worksheet

Unpacking the Product and Components
1. Remove the product and other equipment from the box in which they were shipped.
2. Compare the serial number of the equipment with the number on the packing slip located on the outsideof the box and make sure they match.
3. Inspect the equipment carefully. If any of the equipment is damaged or missing, contact Technical Support
for assistance.
4. Verify that all circuit breakers on the product are set to ON. If not, turn them ON.
Or make sure that all fuses are inserted and seated properly. If there are any fuse covers, ensure thatthey are closed.
Note: Not all models have overcurrent protectors.

Preparing the Installation Site
1. Make sure the installation area is clean and free of extreme temperatures and humidity.
Note: Check the product specification sheet for the maximum operating temperature for your model.
2. Allow sufficient space around the product for cabling and outlet connections.
3. Review Safety Instructions listed in this guide.

Checking the Branch Circuit Rating
The rating of the branch circuit supplying power to the product shall be in accordance with national and local
electrical codes.

Filling Out the Equipment Setup Worksheet
An Equipment Setup Worksheet is provided in this guide. Use this worksheet to record the model, serial
number, and use of each IT device connected.
As you add and remove devices, keep the worksheet up-to-date.

Rackmounts
In This Chapter
Rack-Mounting the PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
PXO Rackmount Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Connecting a PX3 Locking Line Cord. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing Cable Retention Clips on the Inlet (Optional). . . . . . . . . . . . . . . . . . . . . . 32
Installing Cable Retention Clips on Outlets (Optional). . . . . . . . . . . . . . . . . . . . . . . 33
SecureLock™ Outlets and Cords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Button-Type Locking Outlets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Circuit Breaker Orientation Limitation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Rack-Mounting the PDUThis section contains the most common rackmount methods. Follow the procedure suitable for yourmodel.

Rackmount Safety Guidelines•

Operating temperature in a closed rack environment may be greater than room temperature. Do
not exceed the rated maximum ambient temperature of the Power Distribution Units. See
Specifications (on page 581) in the User Guide.

•

Ensure sufficient airflow through the rack environment.

•

Mount equipment in the rack carefully to avoid uneven mechanical loading.

•Connect equipment to the supply circuit carefully to avoid overloading circuits.

•

Ground all equipment properly, especially supply connections, to the branch circuit.

21

Mounting Zero U Models Using L-Brackets▶ To mount Zero U models using L-brackets:
1. Align the baseplates on the rear of the device.
2. Secure the baseplates in place. Use the included L-shaped hex key to loosen the hex socket screws
until the baseplate is "slightly" fastened.

22

3. Align the L-brackets with the baseplates so that the five screw-holes on the baseplates line up
through the L-bracket's slots. The rackmount side of brackets should face either the left or right sideof the device.
4. Fasten the brackets in place with at least three screws (one through each slot). Use additionalscrews as desired.

5. Using rack screws, fasten the device to the rack through the L-brackets.

23

Mounting Zero U Models Using Button Mount▶ To mount Zero-U models using button mount:
1. Align the baseplates on the rear of the device. Leave at least 24 inches between the baseplates forstability.
2. Make the baseplates grasp the device lightly. Use the included L-shaped hex key to loosen the hex
socket screws until the baseplate is "slightly" fastened.
3. Screw each mounting button in the center of each baseplate. The recommended torque for the
button is 1.96 N·m (20 kgf·cm).

24

4. Align the large mounting buttons with the mounting holes in the cabinet, fixing one in place andadjusting the other.
5. Loosen the hex socket screws until the mounting buttons are secured in their position.
6. Ensure that both buttons can engage their mounting holes simultaneously.
7. Press the device forward, pushing the mounting buttons through the mounting holes, then letting
the device drop about 5/8". This secures the device in place and completes the installation.

25

Mounting Zero U Models Using Claw-Foot Brackets

26▶ To mount Zero U models using claw-foot brackets:
1. Align the baseplates on the rear of the device.
2. Secure the baseplates in place. Use the included L-shaped hex key to loosen the hex socket screws
until the baseplate is "slightly" fastened.
3. Align the claw‑foot brackets with the baseplates so that the five screw-holes on the baseplates line
up through the bracket's slots. The rackmount side of brackets should face either the left or rightside of the device.
4. Fasten the brackets in place with at least three screws (one through each slot). Use additionalscrews as desired.

5. Using rack screws, fasten the device to the rack through the claw‑foot brackets.

27

Mounting Zero U Models Using Two Rear Buttons▶ To mount Zero U models using two buttons:
1. Turn to the rear of the hardware.
2. Locate two screw holes on the rear panel: one near the bottom and the other near the top (the sideof cable gland).
3. Screw a button in the screw hole near the bottom. The recommended torque for the button is 1.96
N·m (20 kgf·cm).

28

4. Screw a button in the screw hole near the top. The recommended torque for the button is 1.96 N·m(20 kgf·cm).
5. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously.
6. Press the device forward, pushing the mounting buttons through the mounting holes, then letting
the device drop slightly. This secures the device in place and completes the installation.

Mounting 1U or 2U Models
Using the appropriate brackets and tools, fasten the 1U or 2U device to the rack or cabinet.

▶ To mount the 1U/2U device:
1. Attach a rackmount bracket to both sides of the device with the provided screws.

2. Insert the cable-support bar into rackmount brackets.

3. Secure with the provided end cap screws.

29

4. Fasten the rackmount brackets' ears to the rack using your own fasteners.

PXO Rackmount Method
You can place PXO in any appropriate location with or without fastening it. To fasten it, screw up
fasteners to screw holes on two sides of PXO.

Connecting a PX3 Locking Line Cord
PX3 PDUs are shipped with either of the following locking line cords.
•

A line cord with locking clips: A locking inlet on the PDU is required for this cord.

•

A line cord with slide release buttons: This line cord automatically locks after being connected to theinlet. A locking inlet is not required for this cord.

A locking inlet and/or locking line cord ensure that the line cord is securely fastened to the inlet.

30▶ To connect a cord with locking clips:
Make sure the line cord's locking clips fit into the locking holes at two sides of the inlet when plugging
the cord's connector into the PDU's locking inlet.

NumberItem

1

Locking holes on the inlet

2

Locking clips of the line cord

▶ To connect a cord with slide release buttons:
Plug the cord's connector into the PDU's inlet.

NumberItem

1

Slide release buttons

Disconnecting a PX3 Locking Line Cord
The ways to disconnect a locking line cord vary according to the cord type.

▶ To disconnect a line cord with locking clips:
Press both locking clips of the line cord while unplugging the cord.
Tip: You can slightly move the line cord's plug horizontally while pulling it out to facilitate thedisconnection process.

31▶ To disconnect a line cord with slide release buttons:
Push both slide release buttons toward the cord while unplugging this cord.

Installing Cable Retention Clips on the Inlet (Optional)
If your device is designed to use a cable retention clip, install the clip before connecting a power cord. A
cable retention clip prevents the connected power cord from coming loose or falling off.
The use of cable retention clips is highly recommended for regions with high seismic activities, andenvironments where shocks and vibrations are expected.

▶ To install and use a cable retention clip on the inlet:
1. Locate two tiny holes adjacent to the inlet.
2. Install the cable retention clip by inserting two ends of the clip into the tiny holes.

32

Zero U models

1U/2U models

3. Connect the power cord to the inlet, and press the clip toward the power cord until it holds the cord
firmly.
Zero U models

1U/2U models

Installing Cable Retention Clips on Outlets (Optional)
If your device is designed to use a cable retention clip, install the clip before connecting a power cord. A
cable retention clip prevents the connected power cord from coming loose or falling off.
The use of cable retention clips is highly recommended for regions with high seismic activities, andenvironments where shocks and vibrations are expected.
These optional clips come in various sizes to accommodate diverse power cords used on IT equipment,
which are connected to C13 or C19 outlets. You can request a cable retention kit containing different
sizes of clips from your reseller. Make sure you use a clip that fits the power cord snugly to facilitate theinstallation or removal operation (for servicing).

33

▶ To install and use a cable retention clip on the outlet:
1. Locate two tiny holes at two sides of an outlet.
2. Install the cable retention clip by inserting two ends of the clip into the tiny holes.

3. Plug the power cord into the outlet, and press the clip toward the power cord until it holds the cord
firmly. The clip's central part holding the plug should face downwards toward the ground, like an
inverted "U". This allows gravity to keep the clip in place.

4. Repeat the same steps to install clips and power cords on the other outlets.

SecureLock™ Outlets and Cords
SecureLock securely holds C14 or C20 plugs in place. This method requires the following two
components:

34•

PDU with SecureLock™ outlets, which have a latch slot inside either side of the outlet.

•

SecureLock™ cords, which is a power cord with a locking latch on each side of its plug.

Item

Description

A

Latches on the SecureLock™ cord's plug

If your PDU does not have this design, do NOT use the SecureLock™ cords with it. The SecureLock™
outlets can accept regular power cords for power distribution but the SecureLock™ mechanism does nottake effect.

▶ To lock a power cord using the SecureLock™ mechanism:
1. Verify that the SecureLock™ cord you purchased meets your needs.
• The cords' socket matches the power socket type (C14 or C20) on your IT equipment.
• The cord's plug matches the outlet type (C13 or C19) on your PDU.
2. Connect the SecureLock™ cord between the IT equipment and your PDU.
• Push the plug toward the outlet until you hear the click, which indicates the plug's latches aresnapped into the latch slots of the outlet.

▶ To remove a SecureLock™ power cord from the PDU:
1. Press and hold down the two latches on the cord's plug as illustrated in the diagram below, thenunplug the cord.

35

Button-Type Locking Outlets
Such outlets do not require any special power cords to achieve the locking purpose. Plug a regularpower cord into the locking outlet and the outlet automatically locks the cord.

▶ To remove a power cord from the locking outlet:
1. Press and hold down the tiny button adjacent to the outlet, then unplug. Depending on the outlet
type, the button location differs.

Circuit Breaker Orientation Limitation
Usually a PDU can be mounted in any orientation. However, when mounting a PDU with circuit
breakers, you must follow these rules:•

36

Circuit breakers CANNOT face down. For example, do not horizontally mount a Zero U PDU withcircuit breakers facing up or down.

Initial Installation and Configuration
This chapter explains how to install your device and configure network connectivity.

In This Chapter
Connecting the PDU to a Power Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Connecting to Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring the PX-Series PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Bulk Configuration Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Cascading for Shared Ethernet Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Power-Sharing Restrictions and Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Connecting the PDU to a Power Source
1. Verify that all circuit breakers on the PDU are set to ON. If not, turn them ON.
Or make sure that all fuses are inserted and seated properly. If there are any fuse covers,
ensure that they are closed.
Note: Not all models have overcurrent protectors.
2. Connect each PDU to an appropriately rated branch circuit. Refer to the label or nameplate forappropriate input ratings or range of ratings.
3. When the software has completed loading, the front panel display illuminates.

Connecting to Your Network
To remotely administer the PX-Series PDU, you must connect it to your local area network (LAN). Wiredor wireless networks are supported.
Ethernet port is enabled by default. Port layouts, labels, speeds, and number of Ethernet ports vary bymodel.

▶ To make a wired connection:
1. Connect a standard network patch cable to one or both Ethernet ports on the PDU.
• If the two Ethernet ports have different speeds, use the higher speed port for network connection.
2. Connect the other end of the cable to your LAN.
Warning: Accidentally plugging an RS-232 RJ-45 connector into the Ethernet port can cause permanent
damage(s) to the Ethernet hardware.

▶ To make a wireless connection:37

Do one of the following:• Plug a supported USB wireless LAN adapter into the USB‑A port on your PDU.
• Connect a USB hub to the USB-A port on the PDU. Then plug the supported USB wireless LAN
adapter into the appropriate USB port on the hub.

Dual Ethernet Connection
Models with two Ethernet ports may have ports supporting different speeds. Note if your Ethernet port
is marked with speed. Port layouts and labels may vary by model.
•

ETH1 or ETH2 marked 10/100/1000 supports up to 1000 Mbps.

Exception: USB-cascading chains have different requirements.

▶ Check list when connecting both ports to the networks:•

Both Ethernet interfaces are connecting to different subnets.

•

Both Ethernet interfaces have been enabled. By default both are enabled.

•

Both Ethernet interfaces are configured with proper IPv4 and/or IPv6 settings.
• It is NOT required that the two Ethernet interfaces share similar network settings. For example,
you can enable IPv4 settings in one interface but enable IPv6 settings in the other, or apply static
IP to one but DHCP IP to the other.

•

The cascading mode is disabled. By default it is disabled. Go to Device Settings > Network.

Configuring the PX-Series PDU
You can initially configure via one of the following:•

A TCP/IP network that supports DHCP•

A mobile device with PDView installed•

A computer physically connected to the PDU

Basic configuration process overviews:▶ Configuration via a DHCP-enabled network:
1. Connect the PX-Series PDU to a DHCP IPv4 network.
2. Use the front panel LCD display to retrieve the IP address.
3. Launch a web browser to configure the PX-Series PDU.

▶ Configuration via a connected mobile device:
1. Download the PDView app to your mobile device.
2. Connect the mobile device to PX-Series PDU via USB.
3. Launch PDView to configure the PX-Series PDU.

38▶ Configuration via a connected computer:1. Connect the PX-Series PDU to a computer.
2. Use the connected computer to configure via the command line or web interface.
• Command line interface: See Initial Network Configuration via CLI.
• Web interface: Launch a web browser on the computer, and enter the link-local IP address or
pdu.local.

Connecting a Mobile Device
Raritan's PDView is a free app that turns your iOS or Android mobile device into a local display for PXSeries PDU.
PDView is especially helpful when your PX-Series PDU is not connected to the network but you need tocheck status, retrieve information, or change settings.

▶ Requirements for using PDView:•

If using an Android device, it must support USB "On-The-Go" (OTG).

•

An appropriate USB cable is required.

▶ Step A: Download and install PDView
1. Visit either Apple App or Google Play Store.
• https://itunes.apple.com/app/raritan-pdview/id780382738• https://play.google.com/store/apps/details?id=com.raritan.android.pdview

2. Install PDView.

39

▶ Step B: Connect the mobile device to PX-Series PDU
1. Get an appropriate USB cable for your mobile device.
• iOS: Use the regular USB cable shipped with your iOS mobile device.
• Android: Use a USB OTG adapter cable.
2. Connect the mobile device to the appropriate USB port on the PX-Series PDU.
• iOS: USB‑A port.
• Android: USB‑B port

▶ Step C: Launch PDView
1. Launch the PDView app from your mobile device. Below illustrate iPad's PDView screens.
a. The "Disconnected" message displays first when PDView has not detected the PX-Series PDU yet.
A diagram in PDView indicates the appropriate USB port your mobile device should
connect according to your mobile operating system.

40

Note: PDView also shows the 'Disconnected' status during the firmware upgrade. If so, wait until
the firmware upgrade finishes.
b. The PDView shows the "Connected" message when it detects the connected PX-Series PDU.

2. If the factory-default login credentials remain unchanged, or if PDView has been configured withaccurate login credentials, PDView automatically logs in to the web interface.

41

If PDView can't log in automatically, the login screen displays instead and you must enter
appropriate user credentials for login.
3. The web interface opens and prompts to change the password if this is the first time login.
Tip: You can store the updated "admin" or other user credentials in PDView so that automatic login
always functions properly upon detection of the PX-Series PDU.

Saving User Credentials for PDView's Automatic Login
When PDView detects PX-Series PDU for the first time, it automatically attempts to log in with thefactory-default user credentials.
If you have modified the factory-default user credentials, PDView's automatic login fails and the login
screen displays for you to manually enter user credentials.
To make automatic login work again, you can save the modified admin credentials or any custom user
credentials in PDView. A maximum of 5 user credentials can be saved, and PDView will try these
credentials one by one until the login succeeds.
The following procedure illustrates iPad only, but the procedure applies to any iOS or Android mobile
device.

▶ To save user credentials in PDView:
1. Make sure your mobile device is NOT connected to the PX-Series PDU so that PDView does NOT
perform the automatic login feature after it is launched.
2. Launch PDView on your mobile device.

3. Tap the top-right Settings icon

42(iOS) or(Android).

4. The user credentials setup page opens.
• Per default, three administrator user credentials are pre-configured for three Legrand brands:▪ Raritan▪ Legrand▪ Server Technology

43

5. Modify existing user credentials or type new ones, and tap Save. The pre-configured admincredentials can be removed or overwritten to meet your needs.

Connecting to a Computer
The PX-Series PDU can be connected to a computer for configuration via one of the following ports.
•

Ethernet ports•

USB‑B port•

RS-232 serial port (RJ‑45)▶ Zero U models:

To use the command line interface (CLI) for configuration, establish an RS‑232 or USB connection.

44

To use a web browser for configuration, make a network connection to the computer. The following linklocal addressing is available in any network without DHCP available:•

https://169.254.x.x Use the front panel display to find the address.

•

https://pdu.local

Establish one of the following connections to a computer.

▶ Direct network connection:
1. Connect one end of a standard network patch cable to either Ethernet port of the device.
2. Connect the other end to a computer's Ethernet port.
3. On the connected computer, launch a web browser to access using either link-local addressing:
pdu.local or 169.254.x.x.

▶ USB connection:
1. A USB-to-serial driver is required in Windows®. Install this driver before connecting the USB cable.
2. Connect a USB cable between a computer's USB‑A port and the USB‑B port of the device.
3. Perform initial network configuration via CLI.

▶ Serial connection for "RJ‑45" RS‑232 connector:
1. Connect the RJ‑45 end of the RJ45-to-DB9 adapter cable to the RJ‑45 port labeled CONSOLE /MODEM on the device.
2. Connect the DB9 end to your computer's RS‑232 port (COM).
3. Perform initial network configuration via CLI.

▶ Initial network configuration via CLI sample:
These sample commands set up the ETH1 interface with static IP address, gateway, and DNS server
settings.
#config
config:# network bridge enabled false
config:# network ipv4 interface ETH1 enabled true
config:# network ipv4 interface ETH1 configMethod static
config:# network ipv4 interface ETH1 address 192.168.56.80/24
config:# network ipv4 interface ETH1 gateway 192.168.56.128
config:# network dns firstServer 1.1.1.1 secondServer 1.0.0.1
config:# network ethernet Eth1 speed 100Mbps duplexMode fullconfig:# apply

RJ45-to-DB9 Cable Requirements for Computer Connections
For devices with a console port, an RJ45‑to‑DB9 adapter/cable is required for connecting the PX-Series
PDU to a computer, if the use of a USB cable is not wanted.

45

A third party RJ45‑to‑DB9 adapter/cable needs to meet the following requirements.
•

RJ‑45 to "DB9 female"•

RX/TX and according control pins are CROSSEDThe widespread blue Cisco RJ‑45 to DB9 adapter cable is highly recommended, which has the following
pin assignments:

Note: The blue Cisco RJ‑45 to DB9 adapter cable CANNOT be used for connecting a modem.

Bulk Configuration Methods
If you have to set up multiple devices, you can use one of the following configuration methods to savetime.

▶ A bulk configuration file downloaded from PX-Series PDU:•

Requirement: All devices to configure are of the same model and firmware.

•

Procedure: First finish configuring one PX-Series PDU. Then download the bulk configuration filefrom it and copy this file to all of the other PX-Series PDU devices.
See Bulk Configuration (on page 372).

46

For the remaining methods, see Special Configuration and Upgrade Methods (on page 593).

▶ A TFTP server:•

Requirement: DHCP is enabled in your network and a TFTP server is available.

•

Procedure: Prepare special configuration files, which must include fwupdate.cfg, and copy them tothe root directory of the TFTP server. Re-boot all PX-Series PDU devices after connecting them to the
network.

▶ Curl command:•

Requirement: Two files are required -- one is a configuration file in TXT and the other is a devices list
file in CSV. See config.txt and devices.csv.

•

Procedure: Upload both files to all of PX-Series PDU devices one by one, using the appropriate curlcommand.

▶ SCP or PSCP command:•

Requirement: Two files are required -- one is a configuration file in TXT and the other is a devices list
file in CSV.

•

Procedure: Upload both files to all of PX-Series PDU devices one by one, using the appropriate SCPor PSCP command.

▶ A USB flash drive:•

Requirement: A FAT32- or superfloppy-formatted USB flash drive containing two special
configuration files and one device list file is required.

•Procedure: Plug this USB drive into the PX-Series PDU. When a happy smiley is shown on the front
panel display, press and hold one of the control buttons on the front panel until the display turns
blank.

Cascading for Shared Ethernet Connectivity
See the Cascading Solution Guide for full details on network setup, physical setup, and supported
configurations for all cascades across products. The sections documented here are a brief overview. See
Cascading Solutions for Xerus (on page 637).
You can have multiple devices share one Ethernet connection by cascading them using either the USB
interface or Ethernet interface
The first one in the cascade is the primary device and all the other devices follow it in the cascade. Only
the primary device is physically connected to the LAN -- wired or wireless.

47

Each device in the cascade is accessible over the network, with Bridging or Port-Forwarding cascading
mode activated on each device.
•

Bridging: Each device in the cascading chain is accessed with a different IP address.

•

Port Forwarding: Each device in the cascading chain is accessed with the same IP address(es) but
with a different port number assigned.

▶ Basic cascading restrictions:•All devices in the chain must run compatible firmware versions of 3.3.10 or later.

•

The cascading mode of all devices in the chain must be the same.

•

In the Bridging mode, the primary device can have only one connection to the network. DO NOT
connect both Ethernet ports to the network(s) unless your network has the R/STP protocol enabled.
Note: The Port Forwarding mode does NOT have this restriction. In this mode, you can enable two
wired and one wireless network connections.

•

Do NOT connect cascaded devices other than primary to the LAN or WLAN.

•(WIFI only) You must use Raritan's USB WIFI wireless LAN adapter instead of other WIFI adapters for
wireless network connection.

Best Practices for Cascading▶ One Ethernet connection per cabinet is better:
One Ethernet connection per cabinet is better than one Ethernet connection across cabinets because of
these advantages:•

More reliable connectivity.

•

Easier to manage or maintain one cabinet when all of the cabling and connections are located in thesame cabinet.

•

Reduces the cross‑cabinet cabling.

▶ When to establish a chain comprising 32 devices:A chain consisting of 32 devices saves the most Ethernet connections and costs, and it is recommended
only when:•

External Ethernet ports are expensive or limited.

•

Available IP addresses are limited.

▶ Ethernet cascading is recommended for supported devices with Dual Ethernet ports:
If all the devices in the intended cascade have dual Ethernet ports, cascading them via Ethernet is better
than via USB. The Ethernet interface offers the following benefits:48

•Longer cabling distance•

Lower latency•

Connection more reliable with RJ‑45 connectors

Power-Sharing Restrictions and Connection
Two devices can share power supply to their controllers via a designated port, so that when either
controller fails to receive adequate power from its inlet(s), it continues to receive backup power fromanother device which functions properly and therefore remains accessible to users.
For documentation purposes, the term "power-sharing mode" is used to describe
the status when the PDU controller is receiving power from another device.
Before making a power-sharing connection, first read Power-Sharing Configurations and Restrictions (onpage 51), and remove unsupported equipment from BOTH PDUs.
After a PDU enters power-sharing mode, some data/operations are no longer available.

▶ Unavailable data or operations in power-sharing mode:•

All outlets lose power, and enter the "disabled" state.

•

No outlet switching can be performed.

•

All internal sensors become "unavailable", including sensors of inlets, outlets, and OCPs.
Exception: Only energy data remains available.

•

Communications with relay/meter boards are lost. Therefore, firmware upgrade may fail.

▶ Available data or operations in power-sharing mode:•

Change software settings, such as customizing names, modifying network settings, configuring
thresholds, and so on.

•

Monitor the status of connected environmental sensor packages, or configure/control their settings.

•

Operate the front panel display.

▶ Events that occur when entering power-sharing mode:•

The power supply sensor enters the fault state.

49

Tip: You can set an event rule for sending a notification when this sensor enters the fault state.
•

The above event is logged in the internal event log.

▶ To check status of power-sharing mode:•

Check the state of the power supply sensor. For SNMP, the sensor type is i1smpsStatus (46).

Power Sharing Port on iX7 Controllers
Two units with iX7 controllers can be connected via their "EXPANSION" ports using standard network
cable for power sharing.

Making a Power-Sharing Connection - iX7 Example
Make sure BOTH PX-Series PDU devices comply with the configuration limitations when establishing a
power-sharing connection.
The supported maximum power-sharing distance is 2 meters.

▶ Make a power-sharing connection:
1. Connect the two PDUs with a standard network patch cable (Cat5e/6) that is up to 2 meters long,using the designated power sharing port for your model.
• Do NOT use a crossover cable.
This example shows connection of two iX7 controllers using the EXPANSION port.
• Note that the EXPANSION port location on your PX-Series PDU may differ from the following
images.

50

Power-Sharing Configurations and Restrictions
When either PDU enters power-sharing mode, BOTH PDUs support "less" external equipment thanusual. It is strongly recommended to remove specific equipment from both PDUs when making a
power-sharing connection.

▶ Configuration limitations on "both" PDUs:•

NO USB wireless LAN adapter is connected.

•

That is, you have to connect both PDUs to a "wired" network if LAN access is wanted.
For models that support asset strips: No asset management strips can be connected while power
sharing.

•

The maximum number of DX2 environmental sensor packages or door handles that can beconnected decreases. See Smart Sensor Configurations for Power Sharing.

•

After either PDU enters the power-sharing mode, you must NOT physically remove or add any
environmental sensor packages to either PDU.

51

Supported Sensor Configurations for Power Sharing
All information and restrictions described in this section apply to BOTH PDUs involved in the powersharing configuration, unless otherwise specified.
•NO changes to usual support for DX2, DPX2 and DPX3 sensors in power sharing configurations.

•

The maximum number of supported DX environmental sensor packages also remains unchanged aslong as the DPX3‑ENVHUB4 sensor hub is not used -- that is, 12 DX sensor packages. However, there
are DX restrictions when DPX3‑ENVHUB4 is used, and there are also door handle-related
restrictions.

▶ DX sensor restrictions while DPX3‑ENVHUB4 is involved:•

A maximum of one DPX3-ENVHUB4 and a maximum of 10 DX sensor packages are supported.

▶ Door handle connection restrictions (via DX2‑DH2C2 or DX‑PD2C5):•(Restriction only for DX2‑DH2C2 manufactured before 2019) DO NOT connect any "SouthCo H3‑EM
series" door handle(s) because of insufficient power supply in the power‑sharing mode.
Note: The latest generation of DX2‑DH2C2 does NOT have this restriction and can have SouthCo H3EM series connected in the power‑sharing mode.

•

A maximum of 2 door handles connected to a maximum of one DX2‑DH2C2 or one DX‑PD2C5
package are supported.

•

All of the 2 door handles must be controlled by the same PDU so that you can have "only one"handle opened at a time to avoid critical power consumption. That is, ALL door handles must beconnected to only one PDU in the power-sharing connection, NOT both PDUs.
Note: It is strongly suggested to make sure the upper limit of "powered dry contact actuators" is set
to 1 when making a power-sharing connection.

▶ Other sensor restrictions when door handles are present:
First make sure the connection of door handles complies with the above
restrictions.

52

The following restrictions apply only to the PDU that has all the door handles connected.
•

When there are 2 door handles connected to the PDU (via DX2‑DH2C2 or DX‑PD2C5), up to 10
sensor packages of DPX2/DPX3/DX2 or up to 2 additional DX sensor packages can be additionallyconnected. Raritan's sensor hubs must NOT be used.

•

When there is only 1 handle connected, up to 12 sensor packages of DPX2/DPX3/DX2 or up to 3 DX
sensor packages can be additionally connected. Sensor hubs must NOT be used.

▶ NO physical changes made to the number of connected sensor packages:•

After either PDU enters the power-sharing mode, you must NOT physically remove or add any
environmental sensor packages to BOTH PDUs.

Warning: The inrush current of a newly added sensor package may cause both PDUs to reboot.

53

Linking Units
The Linking feature allows the linking configuration of a single Primary unit to multiple link units so thatyou can view and manage them all in one place. The primary unit has full knowledge of the location of
the connected link units, as well as the power and/or environmental information of all link units. The
primary unit provides visibility and control both the primary unit and the link units from within the GUI,
SNMP, and CLI.
Communication between primary and link units happen via HTTPS. When establishing the connection
the link unit to be added must have HTTPS enabled at the default port 443. For added security,
certificates are checked. Link units must have the demo certificate, or if custom certificates are set, theCA certificate must be installed onto the primary unit. (Go to PDU > Link Units page > "TLS Certificate"button.)
All network modes are supported. Network and physical configurations must be completed before
configuring Linking.
The administrator privilege is required for all management actions (adding, configuring, releasing) of the
Linking feature. Each unit in the chain can be monitored and managed from anywhere by the network
protocols HTTP(S), SNMP, SSH, and Telnet.
All units in the linked chain must be the same model. All units must run the same firmware version,
which can be upgraded respectively for each unit in the chain.

In This Chapter
FAQs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Linking in the Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Displays for Primary and Link Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Linking in the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

FAQs

▶ What’s the difference between a "primary unit" and a "link unit"?
Primary and link units are the same model PX-Series PDU that are equal to each other, and each has its
own IP address. You designate a PX-Series PDU as the primary unit by logging into it and then adding alink unit. The first unit becomes the primary, and when the first link unit is added, the primary unit isautomatically assigned ID "1", which is reserved to identify a primary unit only, and the ID "1" cannot beedited. A connection between the primary and the link unit has now occurred and the chain is formed.
As you continue to add link units to the chain as desired (up to seven link units), you select Link ID "2"through "8" for the Link ID numbers. Note that the Link ID "2-8" is the sequential number of each link
unit that you select as you add the unit to the chain, and once selected, the Link ID cannot be edited.

54

When the chain is established with a single primary unit, and one or more link units, communication
occurs with the primary unit through its IP address. The primary unit, in turn, communicates to theother link units in the chain through their individual IP addresses, which optimizes monitoring andmanagement.

▶ Which models can be linked?
Linking is supported on various products, but all devices in the chain should be the same models,running the same firmware version.

▶ Which network setup modes are supported?
For the underlying network, the Linking feature can use the typical network setup modes:
Independent Setup: All units have their own regular IP address. They don't need to be in a physicalchain to be logically chained. You communicate only to the primary using its normal IP address.
Configure networking of the units, and then add link units using the Web GUI, CLI, or USB.
Bridged Setup: Same as Independent Setup, but the units are physically connected as a chain, either by
ethernet or USB. The configuration steps are the same as with Independent Setup.
Port Forwarding Cascade: The units are physically connected as a chain (either by Ethernet or USB).
Only the first primary unit is connected to your network with the IP address you assigned. The otherunits will get automatically-assigned private IP addresses. When a Cascading in Port Forwarding mode
configuration is detected, you can automatically convert the cascaded units into Link Units using the
GUI in the primary unit, or add link units with the other methods in the Web GUI, CLI, or USB.
See Cascading Solutions for Xerus (on page 637).

▶ Can primary units be linked together?
No. Once a unit is designated as the primary unit in a chain, it cannot be linked to a primary unit inanother chain. A primary unit can only be linked to one or more link units in a chain.

▶ How many units can be linked?
Including the primary, a full chain can include a total of eight units. The first unit added is designated as
the primary unit with the ID "1". Each unit you then add to the chain is designated as a link unit,
beginning with ID "2" and ending with ID "8".

▶ What is re-linking?
Re-linking is a required function when a link unit no longer recognizes or responds to the primary unit,
most likely caused by the link unit being reset to factory defaults. The status of the disassociated link
unit will be displayed as "Access Denied". Selecting the link unit when in this status displays the Re-linkbutton that allows reconnection of the link unit in the chain for regaining device control.
Note: Re-linking uses the same Link Unit ID and hostname, but you will need to reauthenticate withyour login credentials.

55▶ What user privileges are required for managing the Linking configuration?
Administrative privileges are required for both the primary unit and link unit. To add a link, youradministrative login account is required, but after that you only log in to the primary to manage thechain, as all link units in the chain are visible in the user interface from the primary unit view.

▶ What happens if the connection is lost between the primary and link units?
The primary unit's dashboard displays information about unreachable link units in the Link Unit Failures
section.

If the network connection is lost, these link unit functions will still work:
1. Front panel display
2. Energy accumulation and outlet states (not applicable to SRC)
and these link unit functions will stop working:
1.
2.
3.
4.

Event log entries are lost
Event rules, actions and alarms
Remote access to the link unit
Synchronization of primary settings and time when not using NTP▶ Which system areas of the primary and link units are automatically synchronized?
The primary unit periodically checks link unit reachability. You can define rules to be alerted whencommunication with a link unit fails, such as a system alarm. Some link unit settings are automaticallysynchronized with the primary:
1.
2.
3.
4.
5.

Peripheral device settings
Front panel privileges and default view
USB host port lockdown
Time and date settings
General data logging settings▶ How are firmware updates handled?
Uploaded firmware images in the GUI are automatically distributed to all link units at the same time.
Starting a firmware update requires the automatic image upload on the link units to be finished first.

56

Firmware version must match between primary units and link units to function normally. If the primary
unit is updated before the link units, for example, you will see a "Firmware version mismatch" message
in the Link Units section. When this occurs, link unit data will not display. You will not be able to switch
to the mismatched link unit. Upon update of the linked unit to the matching firmware version, normal
data displays will resume.

▶ Does Linking support mass deployment?
Yes, mass deployment has been extended to support a setup for the Linking feature (multi-IP or singleIP) via the Mass Deployment Utility, which provides the Excel spreadsheet process used for bulk
configuration. For information about using the utility, see Configuration or Firmware Upgrade with a
USB Drive.

Linking in the Web Interface
The following topics describe how to configure and use Linking in the web interface.

Viewing the Primary Unit
To view and manage Linking, log in to the unit designated as the primary unit, and go to the PDU page.
When you add a link unit, a chain is established between the primary and the new link, and the primary
becomes ID "1".

The PDU page displays the following information about the primary PDU:
1.
2.
3.
4.
5.
6.

Firmware version
Model
Serial number
MAC address
Rating
Link to Data Log

57

The ID of the primary unit is automatically assigned the ID "1", as shown in the example as "My PDU(1)". The ID cannot be edited.

Options for Adding Link Units
To start configuring the Primary Unit with Link Units, your options in the web interface depend on the
network and physical configuration of units.
•

If you configured units in Independent or Bridging Mode, where they may or may not be physicallycascaded, and each one is assigned its own IP address, you can manually add each link unit. You can
use this manual function anytime to add link units. See Adding a Link Unit (on page 58).

•

If you configured units in a Port-Forwarding Cascade Mode configuration, in which they arephysically cascaded and only the first unit is connected to the network, you can automatically link
the cascaded units. See Linking Cascaded Units (on page 60)

Adding a Link Unit
A link unit (up to seven units) can be added to a single primary unit.
On the PDU page, the Link Units section will contain all link units. The Add Link Unit button, highlighted
in green in the screen example, also displays in the Link Units section.

▶ To add a link unit:• Primary and link units must be the same model, running the same firmware versions.
1. Log in to the primary unit and go to the PDU page.
2. Click Add Link Unit. The following add box displays:58

3. The Link ID is populated as the next available ID number (2-8), assigned sequentially as each link unit
is added to the chain to identify the link unit in the user interfaces. Note: From the drop-down, you
can manually select the desired Link ID to order the link units in the chain as desired. Onceassociated with a link unit, the Link ID cannot be edited.
4. Provide the IP address of the link unit.
5. Provide the login credentials for the link unit. Note: If the link unit has factory settings, you will beprompted to set the new password.
6. Click Add.
• The link unit's firmware version is checked to ensure it matches the primary unit. If a mismatch isfound, a message appears and the link unit is not added.
7. When the firmware matches, the new link unit is added in a list in the Link Units section. All linkunits added to the chain are now managed by the single primary unit.
The PDU page displays the following information about the link unit:•

Link ID•

Host/IP address•

Communication status•

Firmware version

About the Link ID
The Link ID "1" is automated and reserved internally for the primary unit. The primary unit’s ID "1"cannot be edited.
The Link ID "2-8" is available for you to select as the ID for each of the link units you add to the chain.
From the Link ID drop-down, you can select the desired Link ID to manage the link units in the chain.
Once selected, the Link ID cannot be edited.

59

Linking Cascaded Units
When units have been configured in a physically-connected cascade in Port Forwarding mode, PX-Series
PDU can detect expansion units via the primary unit, and link these cascaded units.
While a cascaded chain supports up to 32 units, and may include different products and different
models, Linking can only accommodate a maximum of 8 units linked, and all units must the samemodels running the same firmware version.
Link units can be added by different methods, so remember that 8 total is the maximum overall.
You can link cascaded units in two ways:••

Link All Cascaded Units (Automatic method): Use this method when your cascade's 1 through 8
expansion units are same product/model/firmware, and you want that configuration simply anddirectly converted to Linking.
The automatic option will attempt to link all cascaded units, assigning each either a linklocal IPv6 address or node-index-dependent URL as it is discovered and linked. The process
begins with the first expansion unit connected to the primary, and proceeds through thecascade in order. The process ends when all 8 Link unit IDs have been filled, or when a linkattempt fails.
Custom: Use this method when you want to selectively add only some expansion units from thecascade, or otherwise customize how expansion units are linked, and in what order.
The Custom settings option requires that you to select each cascaded unit by its node
number, and map it to a Link ID manually. You must also select a hostname type for eachlink. The linking process follows your customized list and attempts to add all selected
expansion units.

▶ To link all cascaded units (Automatic method):
1. On the PDU page, click the Link Cascaded Units button. The Link Cascaded Units dialog opens.
2. Enter the administrator user name and password assigned to all designated link units. Must be thesame credentials for all units.
3. Select "Link all Cascaded Units" for automatic linking.

60

4. Select the Hostname type to be assigned to all link units:• Link-local IPv6 address: Units are assigned IPv6 addresses that are accessible from the primary unit.
• Dependent on node index: Units are assigned a URL that includes their node index number, forexample "expansion-1.pf-cascade", "expansion-2.pf-cascade", "expansion-3.pf-cascade", where thenode number indicates the expansion unit's position in the chain related to the primary unit.
5. The table shows the process that will run: Node Index indicates the expansion unit number to belinked, Link ID shows the link ID to be assigned, and Hostname shows the hostname type for all, as
specified.

6. Click Link to start the linking process. The table shows progress and then final results. In the example
below, expansion unit 1 was linked successfully. Expansion unit 2 failed--the connection may havefailed, or this result may also indicate there was no unit at that position. Expansion units 3-7 wereskipped because the process stops upon first failure.

61▶ To link cascaded units (Custom method):
1.
2.
3.
4.

On the PDU page, click the Link Cascaded Units button. The Link Cascaded Units dialog opens.
Enter the Primary Unit's administrator user name and password.
Select Custom Settings.
Click Append Node to add a row to the table, then complete each field in the row to describe how
the expansion unit should be linked. Repeat this step as needed to create a table of all nodes to link.
• Node Index: Select the node index for the expansion unit you want to add. Node index 1 indicatesthe first expansion unit connected to the primary unit, then expansion units are numbers
sequentially as you go down the cascaded chain.
• Link ID: Select the Link ID that this expansion unit will be mapped to once linked.
• Hostname: Select the hostname type to be assigned to this link unit.
▪ Link-local IPv6 address: Units are assigned IPv6 addresses that are accessible from the primaryunit.
▪ Dependent on node index: Units are assigned a URL that includes their node index number, forexample "expansion-1.pf-cascade", "expansion-2.pf-cascade", "expansion-3.pf-cascade", where
the node number indicates the expansion unit's position in the chain related to the primary
unit.

62

5. The completed table you create shows the process that will run.
6. Click Link to start the linking process. The table shows progress and then final results.

Primary Units Manage Link Units
The primary unit manages the following functions for the entire chain of linked units:63•User management and authentication – configured only on the primary.

•

Date and time – the primary synchronizes its date and time settings to link units. If NTP is not used,then the synchronization interval is every 10 minutes.

•

Device settings – only the primary device settings are configurable, except for Network Settings.
Some settings will be synced to link units. The serial port is configurable for the primary only; linkunits use the console.

•

Data model settings – such as outlet names, thresholds, peripherals, etc., are configured on the
primary and stored on link units. Features vary by model.

•

Lua scripts – Communication with link units in a Lua script is possible.

Releasing a Link Unit
Releasing a link unit means the unit is separated from the chain and the unit then becomes standalone.
The primary unit no longer has access to the released link unit.

▶ To release a link unit directly:
If you navigate to a link unit directly, in a web browser, a Release Link option is available instead of alogin option.
•

Enter the username and password, then click Release Device.

▶ To release a link unit from the Primary Unit's web interface:Note: If a release action is attempted on a link unit when the unit is an unreachable state, a warning
message displays, and the primary will not recognize the link unit.

641. From the PDU page, in the Link Units section, click a link unit to select it.
2. Click Release Link Unit.
3. A confirmation prompts to cancel or release.
If released, the link unit is removed from the page.

Switching to a Different Unit
Switching your view to a different unit is a control function noted by the Switch control in the upper left
corner of the pages that display primary and link unit information.
Displayed data in the GUI defaults to the primary unit. The Switch control allows you to switch from a
primary page to a link unit page, and back again to the primary.

▶ To switch to a different unit:
1.
2.
3.
4.

Click the Switch
control.
Select one of the link units from the drop-down list. Link number "2-8" appears in parentheses.
The page displays data for the selected link unit.
To return to the page for the primary, select the primary unit. Primary number "1" appears inparentheses.

▶ Configure load shedding on linked units
You can switch between units in the GUI and setup / activate load shedding separately for every linkunit. Activating load shedding on the primary unit will not activate load shedding for the whole cascade.

Re-linking a Link Unit
Re-link is a required function when a link unit no longer recognizes or responds to the primary unit,
most likely caused when the link unit has been reset to factory defaults. Resetting to factory defaults
causes the linked unit in the chain to be unreachable, and it would have to be removed from the chain
manually.
If reset to factory defaults, the status of the disassociated link unit will be displayed as "Access Denied",shown below.

65▶ To re-link a link unit:
1. When you select the link unit in the "Access Denied" status, the Re-link button displays, as noted
above.
2. To reconnect the link unit in the chain, and to regain full control of the unit, click Re-Link Unit.
3. Although re-linking uses the same Link Unit ID and hostname of the unreachable unit, you will needto reauthenticate with your login credentials.
4. Click the Re-link button.
5. The status of the link unit changes to "OK".

Viewing Link Unit Information
When a link unit is added to the chain, the primary unit view (through the GUI) allows full access to theoperational data of the link unit. For example, using the navigation tabs of the GUI, link unit data isdisplayed in several pages: the Dashboard, PDUs, Inlets, Outlets, Outlet Groups, Peripherals, andFeature Ports.

▶ Dashboard
The Dashboard shows inlets, OCPs, alerted sensors, and inlet history for the entire linked chain.
In this example, data for the single inlet of the primary "My PDU (1)" Inlet I1, and the inlet of the link
unit "My PDU (2)" Inlet I1, are displayed together. The OCPs for the units are also available together on
the Dashboard page.
Peripheral sensors are not shown on the dashboard by default. Only sensors (both PDU or peripheral) in
warned or critical state are displayed in the Alerted Sensors section.

66

▶ PDU Page
The PDU page displays the details and settings for the selected unit (primary or link). The Link PDUs
section is only shown when the primary unit is selected.

67▶ Inlets Page
On the Inlets page, the primary unit and link units are displayed together on the same page.
In this example, data for the single inlet of the primary "My PDU (1)" Inlet I1, and the inlet of the link
unit "My PDU (2)" Inlet I1, are shown together on the Inlets page.

▶ Outlets Page
The Outlets page defaults to display only the outlets of the primary unit, in this example 30 outlets.

68▶ Viewing Outlets for Link Units
On the Outlets page, you can switch from the primary to the link.
1. From the Outlets page drop-down, select the link unit "My PDU (2)". Note: To view outlets for a
specific link unit, the link unit must be selected by name.

All outlets of the link unit display for viewing and access exactly like the outlets of the primaryunit.

2. You can switch back to the primary unit by selecting "My PDU (1)".

69Note: The Switch control is only available when there is at least one link unit in the chain; otherwise, thepage defaults to displaying only the outlets of the primary.
3. From the Outlets page (either primary or link), select an outlet in the list to view operational details
for the specific outlet and to configure outlet settings.

Outlet Groups
An outlet group is a named collection of selected outlets. When user-defined, an outlet group cancontain outlets from different PDUs, including both primary and link units.
Outlet groups support fast and efficient outlet control actions (On, Off, Power Cycle) across multiple
PDUs, and with PDU Linking, member outlets for the primary and its link units can be collected in thesame outlet group.
Outlet groups are managed by the primary unit, and multiple outlet groups can be controlled
simultaneously. Summary and power energy readings are available per outlet group.
The Outlet Groups page displays current user-defined outlet groups along with name, outlet state,active power reading, and the page also shows the outlet labels that were selected for the group. Notein the Outlets column in this example that outlets from both primary and link units display together
within a named group. This is an example of outlet "pairwise", a function described in more detail laterin this next section.
Note: Outlet groups can contain multiple pairs of outlets; the next screen example shows only twooutlet pairs in the sample groups.

70

Click the control arrowgroup number.

to toggle the outlet group list in ascending or descending order by▶ Viewing Outlet Group Details
Click an outlet group name in the list to display operations details for the outlet group. From this page,
you can issue the outlet control actions On, Off, and Cycle (power cycling to restore the outlet) for all
member outlets in the outlet group. The page also allows editing of the outlet group members and its
outlet settings.

71▶ To add an outlet group:
1. On the Outlet Groups page, click Add Group. The New Outlet Group page displays, defaulting to theoutlets in the primary unit.

2. Type a name for the new outlet group.
3. Select individual member outlets for the primary as shown in the default page, or to select alloutlets for the primary, select My PDU (1).
4. To select individual member outlets for the link unit My PDU (2), click Add Outlets. To select alloutlets for the link unit, select My PDU (2). Note: Link units have to be selected by name to display
their outlets.
5. Click Save.

72

The following example shows the outlet group named "TEST 1" with all outlet members
selected for the primary unit and outlet members 1-6 selected for the link unit.

Controlling Outlets in Groups
1. From the Outlet Groups page, select an outlet group by name.
2. Click the desired control: On, Off, or Cycle. This example shows three outlets in status On. When Off
is clicked, a prompt appears to confirm applying the action to all outlets in the group.
3. Click the Switch button.

4. The status of the outlets in the group appears on the Outlets Group page as Off.

Pairwise Outlet Groups
The PDU Linking feature offers the "pairwise" functionality for outlet grouping. Pairwise creates autonamed pairs of outlet groups that span multiple PDUs (primary and link units) using the same outlet
label. You can automatically create multiple outlet groups, each containing one pair of outlets between
linked PDUs that can be controlled as an outlet group.

73

Example: Chain with primary and a single link unit
PDU 1 (Primary Unit)

Server LoadPDU 2 (Link Unit)

Outlet 1

Server 1

Outlet 1

Outlet 2

Server 2

Outlet 2

Outlet 3

Server 3

Outlet 3…

…

…

Outlet 20

Server 20

Outlet 20

Using the above example, to control power to a server, you would typically switch one outlet of PDU 1
and one outlet of PDU 2. With pairwise, you can auto-create an outlet group named "Outlet pair 3", andthe new group will automatically contain Outlet 3 from PDU 1 (primary) and Outlet 3 from PDU 2 (link).

Automatically Create Pairwise Outlet Groups
1. From the Outlet Groups page, from the drop-down menu

select Automatic Creation.

2. Confirm the pairwise creation.

3. Pairwise outlet groups are created and named automatically for all outlets on the primary and link
unit, such as "Outlet pair 1", "Outlet pair 2", "Outlet pair 3", etc.

74

OCPs Page
Overcurrent protectors from both primary and link PDUs are displayed together on the same OCPs
page. If sensors are present on the units, sensor data for both primary and link units will also appear on
the page.

Peripherals Page
The Peripherals Page shows peripheral devices connected to the primary or link unit.

75

Asset Strips Page
The Asset Strips page shows all rack unit information from both the primary and link units.

Displays for Primary and Link Units
Each unit in a PDU Linking chain displays its own PDU data (inlets, outlets, sensors, alerts, etc.)▶ Primary unit:
From the following example of the primary unit display, navigate the options for displaying Link PDU
identification and status, and to confirm the primary unit that is controlling the link unit in the chain.
1. Can show alarms, which may be triggered by link units.
2. PDU information shows a list of link units with host name/IP address, model, device name, serial
number, firmware version, and communication status.

76▶ Link units:
1. No display of alarms/events.
2. PDU information shows the primary IP address77

Linking in the CLI
The CLI is disabled on link units. Access to the link unit via the CLI is available only through the primary
CLI. If any link units are configured, the CLI prompt includes the currently selected unit and Link ID, suchas My Unit (1) or My Unit (2).
Some commands are not available for link units:•

Authentication settings•

Security settings (login, role-based access control, user blocking, and strong passwords.)•

Server monitor•

User management•

Data logging

Linking CLI Commands
Commands for Linking begin with pdu.

▶ List the Units in the Linked Chain
Displays the following information for each unit:

78•

Link ID•

Communication status (for link unit only)•

Device name•

Model name•

Serial number•

Firmware version

# pdu list

▶ Switch Unit
Switch between the primary and link units. The Link ID must be 1 (primary) or 2-8 (link units).
# pdu [id]▶ Add a New Link Unit
Add a link unit to a primary unit. Only available when ID 1 (primary) is selected. The command can beused to re-establish a connection to an existing link unit if the Link ID and host match exactly. The
command requires admin privileges and prompts for the user’s password.
# pdu link [id] [host] [login]•

id: New link ID (IDs 2-8)•

host: Host name or IP address•

login: Name of user with admin privileges▶ Release a Link Unit
Release a link unit from a chain until the unit becomes standalone. The primary unit does not haveaccess to a released link unit. The command is only available when ID 1 (primary) is selected. The
command requires admin privileges, and prompts for confirmation unless the “/y” is specified.
# pdu release [id] {/y}•id: Link ID of the unit to be released (IDs 2-8).

79

Using the Hardware Features
Xerus firmware runs on various hardware designs, including different sizes and controllers.

In This Chapter
Inlet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Outlets and Outlet LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Connection Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Front Panel Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Reset Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Circuit Breakers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Fuse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Beeper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Replaceable Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Threaded Grounding Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Inlet
Most of PX-Series PDU PDUs are shipped with a locking line cord, which is ready to be plugged into the
PDU's inlet and an appropriate receptacle for electricity reception. Such devices cannot be rewired by
the user. A locking line cord helps secure the cord connection.
Connect each PX-Series PDU to an appropriately rated branch circuit. Refer to the label or nameplateaffixed to your PX-Series PDU for appropriate input ratings or range of ratings.
There is no power switch on the PX-Series PDU. To power cycle the unit, unplug it from the branch
circuit, wait 10 seconds and then plug it back in.
Some models support a relocatable inlet.

Zero U Models Relocatable Inlet
On supported Zero U models, change the inlet's location, either from the side or the top.

▶ To relocate the inlet position:
1. Power OFF the unit.
2. Remove the screws at two sides of the inlet to remove the inlet module.
3. Re-install the inlet module at the desired position, replacing the same screws.

80Inlet on the side

Inlet on the top

Outlets and Outlet LEDs
The total number and type of outlets varies from model to model.
Outlets that are metered and/or switched have an LED that indicates their state.

PX3-1000/PX2-1000 Series Outlets (No LEDs)
These models are NOT outlet-switching capable so all outlets are always in the ON state.
Outlet LEDs are not available.

PX3-3000/PX2-3000 Series Outlets (No LEDs)
These models are NOT outlet-switching capable so all outlets are always in the ON state.
Outlet LEDs are not available.

PX3-4000/PX2-4000 Series Outlets and LEDs
These models are NOT outlet-switching capable so all outlets are always in the ON state.
A small LED adjacent to each outlet indicates the outlet state.

81

LED state

Outlet status

Not litPowered OFF

What it means
The outlet is turned off and no power is available.
OR the control circuitry's power supply is broken.

Red

ON and LIVELIVE power. The outlet is on and power is available.

Red flashing

ON and LIVE

Outlet overload. Current sensor is above upper warning threshold.

Red and Green flashing

ON and NOT LIVE OCP tripped. Outlet is ON.

Cycling through Red,
Green and Yellow

n/aFirmware starting up. LED color cycling does not interrupt power tooutlets.

PX3-5000/PX2-5000 Series Outlets and LEDs
These models are outlet-switching capable. A small LED adjacent to each outlet indicates the outlet or
PDU state. The PDU is shipped from the factory with all outlets turned ON.
Some units do a power-on self test process that causes the outlet LEDs to cycle through different colors.
When the software has completed loading, the outlet LEDs show a steady color and the front panel
display illuminates.
LED state

Outlet status

Not litPowered OFF

What it means
The outlet is turned off and no power is available.
OR the control circuitry's power supply is broken.

Red

ON and LIVELIVE power. The outlet is on and power is available.

Red flashing

ON and LIVE

Outlet overload. Current sensor is above upper warning threshold.

Green

OFF and LIVEThe outlet is turned off and power is available when the outlet is turnedon.

Green flashing

OFF and NOT LIVE OCP tripped. Outlet is OFF.

Red and Green flashing

ON and NOT LIVE OCP tripped. Outlet is ON.

Cycling through Red,
Green and Yellow

n/aFirmware starting up. LED color cycling does not interrupt power tooutlets.

PXC and PXO Switched Series Outlets and LEDs
These models are outlet-switching capable. A small LED is adjacent to each outlet to indicate the outlet
status.

82

LED state Outlet status

What it means

Not lit

The outlet is turned off and no power is available.

Powered OFF

LED state Outlet status

What it means
OR the control circuitry's power supply is broken.
OR the outlet's associated circuit breaker has tripped.

ON and LIVERed

ON and NOT LIVELIVE power. The outlet is on and power is available.
The outlet is turned on but power is not available.
The outlet's relay board may be damaged. Contact Technical Support for RMA service.

PXC and PXO Metered Series Outlets (No LEDs)
These models are NOT outlet-switching capable so all outlets are always in the ON state.
Outlet LEDs are not available.

Connection Ports
Connection ports vary by model.

PX3-Series Connection Ports
Depending on the model you purchased, port locations may be different from the following image. ZeroU and 1U/2U models differ.

•

CONSOLE/MODEM port x 1 (blue)•

Sensor port x 1 (yellow)•

USB-A port x 2•

USB-B port x 1•

Feature port x 1 (red)•Ethernet port x 2 (green and white)
Note: ETH1-10/100/1000 (marked in green) supports up to 1000 Mbps. ETH2-10/100 (marked inwhite) supports up to 100 Mbps. There are single and dual ethernet varieties of the iX7 controller,
and that port speed is labeled.

•

Expansion port x 1 (gray)83

PX2-Series Connection Ports
Most Zero U models have the following front panel ports:

1U and 2U models additionally may have In addition, many PX2 series 1U and 2U models are
implemented with two SENSOR ports on the back panel.

PXE Connection Ports
Raritan PXE has the following ports on the front panel:•

ETHERNET•

RS-485•SENSOR•

USB-B

Legrand PDU, PXC, and PXO Connection Ports
Legrand PDU, and Raritan PXC and PXO models have the following ports on the front panel:84•

CONSOLE port x 1 (blue)•

Sensor port x 1 (yellow)•

USB-A port x 1•

USB-B port x 1•

Ethernet port x 2 (green)Connection Port Functions
Port

Used for...

USB‑B

•

Cascading devices for sharing a network connection.

•

Establishing a USB connection with a computer for:• Using the command line interface.
• Performing disaster recovery with Technical Support.

•
USB‑A

FEATURE

Connecting to an Android mobile device.

This is a powered "host" port.
•

Connecting to an iOS mobile device.

•

Connecting a USB device, such as a Logitech® webcam or wireless LAN adapter.

•

Cascading devices for sharing a network connection.

Connection to one of the following devices:•

A Raritan access product, with the use of a power CIM.

•

An external beeper with the RJ‑45 socket.

•

An asset management strip.

Warning: This is not an RS-232 port so do NOT plug in an RS-232 device, or damages canbe caused to the device.
CONSOLE/
MODEM(RJ‑45)iX7 controllers require an RJ45 cable with DB9 adapter for serial connections. Older
controllers prior to iX7 may have a DB9 console/modem port. A null-modem cable isrequired for connecting to a computer.

SENSOR

Connection to one of the following devices:(RJ‑45)•

Environmental sensor package(s).

•Sensor hub.

85

Port

Used for...

ETH1/ETH2 Connecting to your company's network via a standard network patch cable (Cat5e/6).
There are two small LEDs adjacent to the port:

EXPANSION ••Green indicates a physical link and activity.

•

Yellow indicates communications at 10/100 BaseT speeds.
Connecting to the EXPANSION port of another unit with an EXPANSION port for power sharing
in the event of inlet failure.

Front Panel Display
The front panel display will vary by model.
The following diagram shows a sample 0U front panel display. 1U/2U displays are horizontal.

Use the front panel display to view information and even administer features on supported models. It
consists of:•

LCD display•

Four control buttons

Zero U models automatically adjust the orientation of the content shown after detecting the directionof installation. You can also manually change the orientation. 1U and 2U models do NOT adjust thecontent's orientation.
Note: All front panel display images in the User Guide are for Zero U models with the LCD front panel
display. Displays may differ slightly by model and on 1U and 2U models.

Automatic and Manual Modes
After powering on or resetting, the front panel display first shows some dots, then logo and finallyenters the automatic mode.

86▶ Automatic mode without alerts available:
In this mode, the display cycles through information as long as there are no alerts.

▶ Manual mode:
To view more information or control outlets, enter manual mode.

Press

or

to enter the manual mode, where the Main Menu is first displayed.

To return to the automatic mode, press

until you return to the main display.

▶ Alerts:•

In the automatic mode, when an alert occurs, the display stops cycling through information, andwarns you by showing the alerts notice in a yellow or red background.

To enter the manual mode, press•.
In the manual mode, both the top and bottom bars will turn yellow or red to indicate the presenceof any alert.

Control Buttons
Use the control buttons to navigate to the menu in the manual mode.
ButtonFunction
Up

Down

OK

87

Button

Function
Back-- OR -Switch between automatic and manual modes

Operating the Front Panel Display
Enter manual mode when you want to operate the front panel display.

▶ Color changes of the display's top and bottom bars:•

In manual mode, both the top and bottom bars will turn yellow or red to indicate the presence of
any alert.

•

These examples are generic model samples. Information categories vary by model.

•

Screen with yellow bars

Screen with red bars

All alerts enter the warning level only.

Partial or all alerts enter the critical level.

Both bars turn black when there are NO alerts.
Screen with black bars

88

Main Menu
Main Menu
The Main Menu commands depend on the model.
The system time and the X and O buttons and their action on each page are shown at the bottom of thedisplay.
For example, "X Auto" means you can press the X button to enter automatic mode. "Select O" means
you can press O to select an option. Always use the arrow buttons to navigate lists and options.
The currently-selected item's number and total of menu items are indicated in the top-right corner ofthe display.

AlertsSelect Alerts in the Main Menu to view a list of alerted sensors, including both internal and externalsensors.

89

•Numeric sensors in the warning or critical range of an enabled threshold.

•

Alarmed state sensors•

Tripped circuit breakers or blown fuses

If there are no alerted sensors, the display shows the message "No Alerts."▶ Alerted sensors:• The top and bottom bars on the LCD display may be yellow or red, depending on the type(s) ofavailable alerts.

Number Description
Alarm names.
The time the alarm occurred.
If the alarm occurred at least two times, then more information is shown.
•

Number of alarms•

The first occurrence time•

The last occurrence time

Alerted sensor names.

90Number Description
Sensor readings and/or states.
A numeric sensor shows both the reading and state. A state sensor or actuator shows the state
only.
Available states:•

Alarmed•Lower Critical = below lower critical•

Lower Warning = below lower warning•

Upper Warning = above upper warning•

Upper Critical = above upper critical•Open (only available for overcurrent protectors)

The 'Details' command appears for alarms only.

1. Pressor
to view additional pages. When there are multiple pages, page numbers
appear in the top-right corner of the display.
2. (Optional) If there are alarms in the Alert List, you can perform the following operations.

a. Press

to view detailed information of the alarm.

91

b. (Optional) If the alarm occurred more than one time, the numbers of current page and total
pages are shown in the top-right corner, similar to the above diagram. Press
to view the information of other occurrences.

c. To acknowledge all alarms now, press.

PDU
Depending on model, the "PDU" menu includes:•

Internal beeper states -- Active or Off•

Unit-level power and energy readings (for models with multiple inlets)•

Energy pulse output settings•

12V power supply status▶ To view or configure PDU information:

1. Select "PDU" in the Main Menu, and press.

2. The internal beeper state is shown:• Active or Off. In the Active state, the reason of turning on the beeper is indicated.

• To mute the beep sound immediately, press

92

.

or

3. For models that support the active energy pulse output. Press
page.

to enter the Energy Pulse

By default the energy pulsing is turned off. DO NOT enable this feature unless you have to use
it.
Note: This feature, once enabled, blink all outlet LEDs proportional to the energy consumption. It can beused as a simple interface in certification labs where they use an optical sensor to count the number ofpulses and compare it to the energy reading of a reference meter.

a. To change the energy pulse settings, pressfeature.

for Setup, then select to enable or disable the93Note: All outlet LEDs turn OFF after enabling the energy pulsing. You still can turn on or off
outlets during the pulsing period though outlet LEDs do not change their status.

4. Pressto show the status of the 12V power supply to the controller.

5. If your PX-Series PDU has more than one inlet, press
power (W) and total active energy (Wh).

94

to show the information of total active▶ Muting the Internal Beeper
After enabling the internal beeper's mute control function, you can choose to mute the beeper via thefront panel whenever the beeper sounds for an alarm.
By default, the beeper's mute control feature via front panel is enabled.

▶ To mute the internal beeper during an alarm:
Note that muting the beeper does not change the alarmed state.

1. Select "PDU" in the Main Menu, and press

2. Press. The Beeper Info displays

for Mute, then confirm the operation by selecting Yes.

95

3. The beeper stops, and the Beeper State shows "Active (Muted)".

Inlet
An inlet's information is divided into two pages. Page numbers are indicated in the top-right corner ofthe display.

▶ To show the inlet information:

1. Select "Inlet I1" in the Main Menu, and press.
2. The first page shows the inlet's active power (W), apparent power (VA), power factor (PF), and activeenergy (Wh).

963. To go to other page(s), use the arrow buttons.
• For a single‑phase model, the second page shows the inlet's voltage (V), frequency (Hz) and current(A).

• For a three‑phase model,all lines are shown with unbalanced current's percentage, line frequency,
and the current and voltage values of each line.

OCPs
If your model has more overcurrent protectors (OCPs) than the display can show at a time, a page
number appears in the top right corner of the display. Use the arrow buttons to scroll through thepages.

97▶ To show the overcurrent protector information:

1. Select "OCPs" in the Main Menu, and press.
2. The display shows a list of overcurrent protectors with the details:• OCP name, such as Circuit Breaker C1• Associated lines and rated current for each OCP• Current reading (A)Note: Tripped breakers will show "open" instead of a current reading.

Outlets
With the front panel display, you can:•Show each outlet's information.

•

Turn on, off or power cycle an individual outlet on models that support switching. Front panel outlet
control must be enabled in the Front Panel Settings.

Multiple outlet information can be shown on the display. Check the bottom of the display for control
buttons and their actions.

98▶ To show an outlet's information:

1. Select "Outlets" in the Main Menu, and press.
2. The list of outlets is shown with their receptacle types, current values (A), and power states which
are indicated by the colors of circles.
The currently-selected outlet number and total of outlets are indicated in the top-right corner ofthe display.
• A red circle indicates that this outlet is powered on.
• A green circle indicates that this outlet is powered off.
If so, the word "Off" replaces the current value.

3. Pressorto select an outlet, and press.
4. The selected outlet's power state, active power (W), apparent power (VA), power factor (PF) andactive energy (Wh) is shown.
Note: In the following diagrams, N represents the selected outlet's number.

99

5. Use the arrow buttons to scroll between the pages of outlet information. The next page shows theoutlet's voltage (V), frequency (Hz) and current (A).

▶ Power Control
This section applies to outlet-switching capable models only.
The front panel outlet control must be enabled for performing this power control function. The default
is to disable this function.
Available options for power control vary, based on the power state of the selected outlet.

100▶ To power on, off or cycle an outlet:

1. Select "Outlets" in the Main Menu, and press

2. Use the arrow buttons to select an outlet, and press.

.

• In the individual page for the outlet, press
for Switch to go to the power control page. In
this example, the outlet is On, so the available options are 'Switch Off' and Cycle.

101

3. Use the arrow buttons to select the desired option, and press.

• Switch Off: Turn off the outlet.
• Switch On: Turn on the outlet.
• Cycle: Power cycle the outlet. The outlet is turned off and then on.

4. A confirmation message appears. Select Yes or No, and then press
5. Verify that the selected outlet is switched on or off.

.

• Check the outlet state shown on the LCD display -- red or green circles.
• Check the outlet LED for the correct Off or On color.

▶ Outlet Groups
Only PDUs with outlet-switching and/or outlet-metering feature show this menu item.
If any outlet group has been created, the front panel then shows a list of these groups and their status.

▶ To show an outlet group's information:

1. Select "Outlet Groups" in the Main Menu, and press.
2. The LCD display shows a list of outlet groups with the information below:• The total number of outlets in the group• Power states which are indicated by the colors of circles• Each group's active power value

102

The currently-selected outlet group's number and total of outlet groups are indicated in the
top-right corner of the display, such as "1/4" in the above diagram.
• A red circle indicates that all outlets of the group are powered on.
• A green circle indicates that all outlets of the group are powered off.
• A half-red half-green circle indicates some outlets are powered on while the others of the groupare powered off.

3. Select an outlet group, and press.
4. The LCD display shows the selected outlet group's power state, active power (W), and active energy(Wh).
Note: In the following diagrams, N represents the selected outlet group's index number. The rightmost
number in the title bar represents this group's total pages.

103

5. To check the status of each member outlet of the group, pressor.

▶ Outlet Group Power Control
This section applies to outlet-switching capable models only.
The front panel outlet control must be enabled for performing this power control function. The default
is to disable this function.
Check the bottom of the display for control buttons and their actions.

104▶ To power on, off or cycle an outlet group:

1. Select "Outlet Groups" in the Main Menu, and press.

• The LCD display shows a list of outlet groups.

2. Select an outlet group, and press.

Note: In the following diagrams, N represents the selected outlet group's index number. The rightmost
number in the title bar represents this group's total pages.

105

•

Press

to go to the power control page.

1. Select the desired option, and press106.

• Switch On: Turn on the outlet group.
• Switch Off: Turn off the outlet group.
• Cycle: Power cycle the outlet group.

2. A confirmation message appears. Select Yes or No, and then press
3. Verify that the selected outlet group is switched:.

• Check the outlet group state shown on the LCD display -- red or green circles.
• Check each member outlet's LED of the group.

Peripherals
If there are no environmental sensor packages connected, the display shows the message "No managed
devices" for the "Peripherals" menu command.

▶ To show environmental sensor or actuator information:.
1. Select "Peripherals" in the Main Menu, and press
2. The display shows a list of environmental sensors/actuators.
• When the list exceeds one page, the currently-selected sensor/actuator's ID number and total ofmanaged sensors/actuators are indicated in the top-right corner of the display.
• If any sensor enters warning, critical, or alarmed state, like 'Tamper Detector 1' shown below, it ishighlighted in yellow or red.
The top and bottom bars also turn yellow or red.

107

Number Description
Sensor or actuator names.
Sensor or actuator states:•

n/a = unavailable•

Normal•Alarmed•Lower Critical = below lower critical•

Lower Warning = below lower warning•

Upper Warning = above upper warning•

Upper Critical = above upper critical

•

On

•

Off

•

Open

•

ClosedA numeric sensor shows both the reading and state. A state sensor or actuator shows thestate only.

1. To view an environmental sensor or actuator's detailed information, select it, and press
screen similar to the following is shown.

108

.A

Number Description
The ID number assigned to this sensor or actuator.
•

A sensor shows "Peripheral Sensor x" (x is the ID number)•

An actuator shows "Peripheral Actuator x"

Sensor or actuator name.

1.

The following information is listed.
•

Serial number•

Chain position, which involves the following information:•••

Port <N>: <N> is the number of the sensor port where this sensor or actuator isconnected.
Chain Pos. <n>: <n> is the sensor or actuator's position in a sensor daisy chain.
If this sensor or actuator is on a sensor package with multiple channels, its channel number
is indicated.

Depending on the sensor type, any of the following information is displayed:•

State of a state sensor: Normal, Alarmed, Open or Closed.

•State of an actuator: On or Off.

•

Reading of a numeric sensor.

X, Y, and Z coordinates which you specify for this sensor or actuator.

▶ To switch on or off an actuator:
By default peripheral actuator control is disabled. You have to enable it in the web interface.
See:Peripherals (on page 192)

109

1. Select "Peripherals" in the Main Menu, and press. Select an actuator to switch and press.

2. Pressshown.

to turn on or off the actuator. A confirmation message similar to the following is

3. Use the arrow buttons to select Yes or No, and then press
4. Verify that the actuator status shown has been changed.

110.

Assets
After connecting asset strips, information of the rack units with detected asset tags is shown.

▶ To show asset strip information:

1. Select "Assets" in the Main Menu, and press.
2. The display shows the available asset strip, and indicates how many rack units and tags are detectedon this strip.
• The number of tags includes both the tags attached to the asset strip and those attached to theblade extension strip, if any.

3. Pressto show this asset strip's details, including:• State - strip status.
• Main Tags - number of the tags attached to the asset strip.
In the following diagram, this number is 30.
• Blade Tags - number of the tags attached to the blade extension strip(s), if any.
In the following diagram, this number is 2.
Note: The 'Blade Tags' information appears only when there are tags detected on the connected
blade extension strip.
• Type - the asset strip type.
• Numbering - the numbering mode. See Asset Strip.
• Offset - the starting number of the rack unit numbering.
• Orientation - the strip's orientation.

111

4. Press

again to show a list of available tags and their information.

• When the list exceeds one page, the currently-selected main tag and total of available main tags
are indicated in the top-right corner of the display.

• If the desired tag is not visible, press

112

or

to scroll up or down.

Number Description
Two numbers are displayed for each tag.
•

Rack unit number: The number assigned to this tag based on the selected numbering
mode.

•

The index number in parentheses: The physical port number printed on the asset strip.

The asset tag's name if you have specified. This field does not show up when no name isavailable.
If the connected tag is the blade extension strip, it shows 'blade extension' and indicates how
many tags and slots are available on this extension strip.
A color box, which represents the current LED color of the tag port where this asset tag isconnected. The default is green.
•

You can customize the color.

The connected asset tag's ID number (barcode).

1. If any blade extension strip is connected to this asset strip, select it and Pressof available tags and asset IDs on this extension strip.

to view a list113

Number

Description
The information of the selected blade extension strip, including:•

Rack unit number•

Index number in parentheses•

Current LED color of the tag port where it is connected•

Extension strip's ID number (barcode)

The slot number of each asset tag
The connected asset tag's ID number (barcode).

Device Info
The display shows the device's information, network and IPv4/IPv6 settings through various pages. Page
numbers are indicated in the top-right corner of the LCD display.

▶ To show the device information:

1. Use the arrow buttons to select "Device Info" in the Main Menu, and press
2. Device information for your model displays.
• Device name.
• Firmware version, model name and serial number.
• Device ratings, including rated voltage, frequency, current and power.

3. Press114

to show the Network Common page.

.

Number

Description
DNS servers.
Default gateways.

4. Pressto show the Network Cascading page. Display shows details on your cascading mode,as shown in these examples.

115

116

Description
Cascading status, which can be one of the following:•

No Cascading: This device's cascading mode is set to None.

•

Network Bridge Enabled: This device's cascading mode is set to Bridging. Its IP address isalso displayed on this page.

•

Port Forwarding Primary: This device's cascading mode is set to Port Forwarding, and it
is a primary device.

••

Expansion unit Connected: Indicates whether the presence of a expansion unit
device is detected - yes or no.
Port Forwarding Expansion unit: This device's cascading mode is set to Port Forwarding,and it is a expansion unit device.

•

Expansion unit Connected: Indicates whether the presence of a expansion unit
device is detected - yes or no.

•

Cascade Position: Indicates the position of a expansion unit device in the Port
Forwarding mode. 1 represents Expansion unit 1, 2 represents Expansion unit
2, and so on.

•

A port forwarding expansion unit device will also display the primary device's
IP address on this page.

1. Pressto show the Ethernet pages.

There can be one or two pages: ETH1 and ETH2.

117

Number Description
Ethernet interface information, including:•

MAC address.

•

Speed.

•

Full or half duplex.

IPv4/IPv6 network information, including:•

Network configuration: DHCP (or Automatic), or Static. Static represents Static IP.

•

IP address.

•

Prefix length, such as "/24".

Note: If you disable any Ethernet interface, a message 'Interface Disabled' isshown. See Ethernet Interface Settings.
If you do not enable IPv4/IPv6 settings, an 'IPv4 (or IPv6) Disabled' message is displayed.

1. Pressto show the WIRELESS page.

• If NO supported WLAN adapter is plugged or detected, the message "No Adapter Detected" isshown.
• If a supported WLAN adapter is detected and configured properly, wireless network information isshown instead, including:▪ MAC address▪ SSID▪ IPv4/IPv6 network information

118

-- OR --Port Overload - Reset Fuse
If an overload condition is detected on an external port, an alert notification is displayed in the front
panel. The notification includes a list of ports that may have caused the overload.
This alert cannot be dismissed without resolving the overload condition and resetting the fuse.

▶ To resolve a Port Overload condition:
1. Remove all attached devices from the ports listed in the alert.
2. Press the Select button on the front panel to reset the fuse.

119

Alerts Notice in a Yellow or Red Screen
In the automatic mode, if an alert occurs, the LCD display automatically shows a yellow or red screen
which indicates the total number of alerted sensors and information on the latest transitions.
•

When all alerted sensors enter the warning levels, the screen's background turns yellow.

•

When at least one of the alerted sensors enters the critical level or there is any "alarm", the screen's
background turns red.

The following illustrates the alerts notices in red.

120

▶ When there are only alerted sensors -- NO ALARMS are present:

NumberDescription
The total of alerted sensors in critical and warning levels.
A list of alerted sensors.
The latest reading/status time related to each alerted sensor.

▶ When there is any alarm present:
The display shows the alarm(s) and the available command in the bottom-right corner is 'Actions'.

121▶ Available operations:•

For alerted sensors only, press
acknowledge alerted sensors.

•

When an alarm is present, press
option, and press

to view a list of all alerted sensors. You do not have toto view the options. Use the arrow buttons to select an.

• Show alert list: View a list of alerted sensors and alarms. You still can choose to acknowledge
alarms after viewing the list.
• Acknowledge all alarms: This option immediately acknowledges all existing alarms, without
showing the list of alarms. When you select this option, you must next select Yes to confirm.

122Manually Changing Zero U LCD Orientation
A Zero U model has a tilt sensor that can detect the orientation of its physical device to automaticallyadjust ts LCD content's orientation.
If the LCD's orientation does not meet your need, you can manually configure it.
The factory default is automatic orientation.

▶ To set up the LCD orientation:

1. Pressandsimultaneously until you see the LCD shows "Fixed Orientation".
2. If the current LCD orientation does not meet your need, repeat the above step until the orientation
you preferred is displayed.

Showing the Firmware Upgrade Progress
When upgrading the PX-Series PDU, the firmware upgrade progress will be displayed as a percentage on
the LCD display, similar to the following diagram.

123

In the end, a message appears, indicating whether the firmware upgrade succeeds or fails.

Reset Button
The reset button is located inside the small hole labeled RESET near the display panel.
Pressing this reset button restarts the Xerus software without any loss of power to outlets.

Circuit Breakers
PX-Series PDU models rated over 20A (North American) or 16A (international) contain overcurrent
protectors for outlets, which are usually branch circuit breakers. These circuit breakers automaticallytrip (disconnect power) when the current flowing through the circuit breaker exceeds its rating.
If a circuit breaker switches off power, the front panel display shows open. To find which circuit breakeris open (trips), select Alerts or OCPs in the front panel display menu. When a circuit breaker trips, power
flow ceases to all outlets connected to it. You must manually reset the circuit breaker so that affected
outlets can resume normal operation.

Resetting the Button-Type Circuit BreakerYour button-type circuit breakers may look slightly different from the images shown in this section, but
the reset procedure remains the same.

▶ To reset the button-type breakers:
1. Locate the breaker whose ON button is up, indicating that the breaker has tripped.

124

2. Examine your PX-Series PDU and the connected equipment to remove or resolve the cause that
results in the overload or short circuit. This step is required, or you cannot proceed with the nextstep.
3. Press the ON button until it is completely down.

Resetting the Handle-Type Circuit BreakerYour handle-type circuit breakers may look slightly different from the images shown in this section, but
the reset procedure remains the same.

▶ To reset the handle-type breakers:
1. Lift the hinged cover over the breaker.
2. Check if the colorful rectangle or triangle below the operating handle is GREEN, indicating that the
breaker has tripped.

3. Examine your PX-Series PDU and the connected equipment to remove or resolve the cause that
results in the overload or short circuit. This step is required, or you cannot proceed with the nextstep.
4. Pull up the operating handle until the colorful rectangle or triangle turns RED.

125

Fuse
Some devices may be implemented with fuses instead of circuit breakers. A fuse blows to protect
associated outlets if it detects overload.
If your PDU uses fuses, you must replace it with a new one when it blows or malfunctions. The rating
and type of the new fuse must be the same as the original one.
Use of inappropriately rated fuse results in damage
to the PDU and connected equipment, electric
shock, fire, personal injury or death.

Depending on the design of your PDU, the fuse replacement methods differ.

Fuse Replacement on Zero U Models
This section only applies to a Zero U PDU with "replaceable" fuses.

▶ To replace a fuse on Zero U models:
1. Lift the hinged cover over the fuse.

2. Verify the new fuse's rating against the rating specified in the fuse holder's cover.

126

3. Push the cover of the fuse holder to expose the fuse.

4. Take the fuse out of the holder.

127

5. Insert a new fuse into the holder. There is no orientation limit for fuse insertion.
6. Close the fuse holder and the hinged cover in a reverse order.

Fuse Replacement on 1U Models
On the 1U model, a fuse is installed in a fuse knob, which fits into the PDU's fuse carrier.

NumberDescription
Fuse carrier
Fuse knob where a fuse is installed▶ To replace a fuse on 1U PDUs:
1. Disconnect the PDU's power cord from the power source.
2. Remove the desired fuse from the PDU's fuse carrier using a flat screwdriver.
a. Rotate the fuse knob counterclockwise until its slot is inclined to 45 degrees.

128

b. Take this knob out of the fuse carrier.
3. Remove the original fuse from this knob, and insert either end of a new one into the knob. Make
sure the new fuse's rating is the same as the original one.

NumberDescription
Fuse knob
Fuse

4. Install this knob along with the new fuse into the fuse carrier using a flat screwdriver.
a. Have this knob's slot inclined 45 degrees when inserting the knob into the fuse carrier.

b. Gently push this knob into the fuse carrier and then rotate it clockwise until its slot is horizontal.
5. Verify whether this knob's head is aligned with the fuse carrier. If its head is higher or lower than thefuse carrier, re-install it.

129Number

Description
INAPPROPRIATE installations
Appropriate installation

6. Connect the PDU's power cord to the power source and verify that the corresponding fuse LED is lit,
indicating that the fuse works properly.

Beeper
The PX-Series PDU includes an internal beeper to issue an audible alarm for an overcurrent protector
which is open.
•

The beeper sounds an alarm within 3 seconds of a circuit breaker trip.

•

The beeper stops as soon as all circuit breakers have been reset.

You can also set the internal beeper to sound for specific events.
Tip: You can remotely check this beeper's state in the web interface on the PDU page.

Replaceable Controller
A Zero U model provides flexibility for replacement of its controller.
If the controller is broken, you can send the controller only back for repair, or purchase a new controller.
Note: PXC and PXO models DO NOT have replaceable controllers.

▶ To request a new controller:
Contact Technical Support to request a new controller.
Include these details with your request:

130•

The serial number of the PDU•

The serial number of the controller board•

The full model number of the PDU•

The firmware version that the PDU is running▶ To replace a controller:
1. PDU is NOT required to be powered off.
2. Loosen the screws at two sides of the controller, and lift it up.
Note: Loosen the screws instead of removing them.

3. Disconnect the PDU's controller cable from the controller.

4. Get a new controller and install it back into the PDU in the reverse order.

Threaded Grounding Point
Some models have a threaded grounding point. Identify it via the grounding symbol:

Wire this point to an electrical system to protectively ground the PX-Series PDU.

131

Using the Web Interface
This chapter explains how to use the product web interface for administration.

In This Chapter
Supported Web Browsers and Mobile Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Login, Logout and Password Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Web Interface Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Dashboard - PDUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
PDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Inlet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Outlets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Outlet Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
OCPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Peripherals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Serial Access With Dominion Serial Access Module. . . . . . . . . . . . . . . . . . . . . . . . 210
Asset Strips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
External Beeper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Power CIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Device Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Using Prometheus and Grafana. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Webcam Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
SmartLock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Card Readers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Supported Web Browsers and Mobile Devices•

Firefox® 100 and later•

Safari® (Mac)•

Google® Chrome® 100 and later•

Android 8.1 and later•iOS 12.5 and later•

Edge (Windows 10, 11 (chrome-based versions))

Login, Logout and Password Change
The first time you log in, use the factory default user credentials. For details, refer to the Quick Setup
Guide accompanying the product. Password change is forced upon first login.

132

Login and Logout
You must enable JavaScript in the web browser for proper operation.

▶ To log in to the web interface:
1. In a supported browser go to the IP address of your PX-Series PDU• If the link-local addressing has been enabled, you can type pdu.local instead of an IP address.

2. If any security alert message appears, accept it.
3. You can set contrast polarity by clicking on Dark and Light iconoronbottom left of the login screen.
4. Enter your user name and password, accept any security agreement displayed, and click Login.
Note: To configure the security agreement, go to Device Settings > Security > Service Agreement.
5. The web interface opens.
After finishing your tasks, you should log out to prevent others from accessing the webinterface.
• Click Logout in the top right corner, or close the tab or browser.

Changing Your Password
You need appropriate permissions to change your password or others’ passwords.

133▶ Password requirements:• Case sensitive.
• 4 to 64 characters.

▶ Password change required on first login:•

On first login, password change is forced and strong passwords are enabled by default. The new
password must be at least 8 characters and contain at least one upper case letter, one lower caseletter, and one digit.

•

Change the default password and click OK.

▶ To change your password via the Change Password command:
You must have the Change Own Password permission to change your own password.
•

Choose User Management > Change Password. Change the password and click Save.

Web Interface Overview
The web interface consists of four areas as shown below.

134Number Web interface element
Menu - Not all models support all menu options.

Data/setup page of the selected menu item.

•

Left side:- PX-Series PDU device name.
•Right side:- Displayed language, which is English (EN) by default. You can change it.
- Your login name, which you can click to view your user account settings.
- Logout button.
From top to bottom -•Your PX-Series PDU model.

•

Current firmware version.

•

Online Documentation: link to the online help.

135Number Web interface element•

Support: link to Technical Support.

•

Date and time of your user account's last login.

- Click Last Login to view your login history.
•

PX-Series PDU system time, which is converted to the time zone of your computer or mobile device.

- Click Device Time to open the Date/Time setup page.

Menu
Depending on your model and hardware configuration, your PX-Series PDU may show all or some menu
items shown below.
Menu

Information shown

Dashboard

Summary of the PX-Series PDU status, including a list of alerted sensors and alarms, if any.

PDU

Device data and settings, such as the device name and MAC address.

Inlet

Inlet status and settings, such as inlet thresholds.

Outlets

Outlet status, settings and outlet control if your model is outlet-switching capable.

Outlet Groups

Only PDUs with outlet-switching and/or outlet-metering feature show this menu item.
You can create groups of outlets.
Functions that you can perform on an outlet group vary depending on the model you purchased.
OCPs

The OCPs menu item displays only if your model is equipped with overcurrent
protectors.
OCP status and settings, such as OCP thresholds.
Peripherals

Status and settings of environmental sensor packages, if connected.

Asset Strip

Status and settings of an Asset Strip, if connected.

Webcams

The Webcams menu is available when a webcam is detected or webcam images havebeen saved locally.
Webcam live snapshots/video and webcam settings.

136

Menu

Information shown

SmartLock-- and/or --The SmartLock and Card Readers menus are available when SmartLock kit is detected.

Card Readers•

SmartLock: Configures and controls the door connected to this product via DX2‑DH2C2. This
page is not available with other door controllers.

•

Card Readers: Lists the card readers connected directly or indirectly.

User Management Data and settings of user accounts and groups, such as password change.
Device Settings

Device-related settings, including network, security, system time, event rules and more.

MaintenanceDevice information and maintenance commands, such as firmware upgrade, device backup andreset.

Quick Access to a Specific Page
If you often visit a specific page in the PX-Series PDU web interface, you can bookmark or share the URL.
This allows you to log in directly to the desired page.

Sorting a List
Hover on a column header to see if it is sortable. Click headers that appear as a blue link to sort the listin ascending or descending order based on the selected column.
The arrow is displayed adjacent to the header currently sorted.

Dashboard - PDUs•

The Dashboard page gives you an overview of your PX-Series PDU in various sections, depending on
your model.

•

Click any blue hyperlink to go to the main page for that information.

•

Not all models have overcurrent protectors.

137▶ What to look for:•All green status bars indicate performance in normal ranges.

•

Red or yellow status bars indicate alerts or alarms.

•

Check the Alerted Sensors and Alarms sections for any issues that need attention.

•

Alarms are listed if there are events that must be acknowledged according to your configurations.

•

Alerts are listed when sensor thresholds are entered according to your configurations.

▶ What can be customized on the Dashboard?
•

The Inlet History chart at the bottom of the Dashboard shows active power by default.

•

Select a different data type to change the chart view temporarily.

▶ PDU Totals•

138

For multi-inlet models or inline monitors PDU Totals sum up the total active power and activeenergy.

Dashboard - Inlet I1
8The number of phases shown in the Inlet section is model dependent.

▶ Link to the Inlet page:
To view more information or configure the inlet(s), click this section's title 'Inlet I1' to go to the Inlet
page.

▶ Left side - generic inlet power data:

139

The left side lists all or some of the following data. Available data is model dependent.
•

Active power (kW or W)•

Apparent power (kVA or VA)•

Active energy (kWh or Wh)•

Power factor•

Line frequency (Hz)•

Unbalanced current (%) - model dependent▶ Right side - inlet's current and voltage:

The right side shows the current and voltage data per phase. For a single-phase device, it shows only
one line, but for a three-phase device, it shows three lines (L1, L2 and L3).
Inlet data from top to bottom includes:•

RMS current (A) and rated current• The smaller, gray text adjacent to RMS current is the rated current.

•

A bar showing the RMS current level•

RMS voltage (V)The RMS current bars automatically change colors to indicate the current status according to yourconfigured thresholds. To configure thresholds, see Inlet (on page 161).

140

Status

Bar colors

normalabove upper warning

above upper critical

Dashboard - OCP
Availability and total number of OCPs depend on the models.

▶ Each OCP's link:
To view more information or configure individual OCPs, click the desired OCP's index number, which iseither BR1, BR2, and so on; or C1, C2 and so on, to go to its setup page.

▶ Each OCP's power data:
OCP data from top to bottom includes:

141

•

RMS current (A), and rated current• Smaller gray text adjacent to RMS current is each OCP's rated current, such as "16A" shown in
the above diagram.

•

A bar showing OCP current levels•

OCP status -- open or closed•

Associated line pair

The RMS current bars automatically change colors to indicate the current status according to yourconfigured thresholds. To configure thresholds, see OCPs (on page 186).
StatusBar colors

normalabove upper warning

above upper critical

Dashboard - Alerted Sensors
When any internal sensors or environmental sensor packages connected to the PX-Series PDU enter anabnormal state, the Alerted Sensors section in the Dashboard shows them for alerting users. Thissection also lists tripped circuit breakers or blown fuses, if available.
To view detailed information or configure each alerted sensor, click each sensor's name to go toindividual sensor pages. See Individual Sensor/Actuator Pages (on page 203).

▶ Summary in the section title:
Information in parentheses adjacent to the title is the total number of alerted sensors.

142For example:•

1 Critical: 1 sensor enters the critical or alarmed state. 1 Warned: 1 'numeric' sensor enters thewarning state.
• Numeric sensors enter warning or critical states, as their values enter the threshold ranges.
• State sensors enter an alarmed state.

See Sensor/Actuator States (on page 199) for more details.
Numeric sensors:•

Warning

Numeric sensors:•

CriticalState sensors:•

Alarmed state

Dashboard - Inlet History•

The Inlet History graph displays the history of the sensor values. Select a different data type byclicking the selector

below the diagram.

•143• To retrieve the exact data at a particular time, hover your mouse over the data line in the chart.
Both the time and data are displayed as illustrated below.

▶ Inlet selection on multi-inlet models:If your PDU is a multi-inlet model, you can have one or multiple inlets show their power charts byselecting the checkbox(es) of the desired inlet(s).

144

•

When multiple inlets are displayed in the chart, their colors differ. You can identify each inlet's dataaccording to the colors of the selected inlet checkboxes.

•

When both inlets are shown in the chart, simply hover your mouse over either inlet's data line.
Both inlets' values display simultaneously, marked with corresponding colors.

145

Dashboard - Alarms
If configuring any event rules which create or emit device alarms, the Alarms section will list any eventthat hasn't been acknowledged yet.
Note: For information on event rules, see Event Rules and Actions (on page 291).
You must have the 'Acknowledge Alarms' permission to manually acknowledge an alarm.

▶ To acknowledge an alarm:•

146

Click Acknowledge, and that alarm then disappears from the Alarms section.

This table explains each field of the alarms list.
Field

Description

Name

Custom name of the Alarm action.

ReasonShows the log message if the alarm was only triggered by one
specific event.

Reasons

Short summary if there were multiple different events.

First
Appearance

Date and time when the event indicated in the Reason column
occurred for the first time.

Last Appearance Date and time when the event indicated in the Reason column
occurred for the last time.
Count

Number of times the event indicated in the Reason column has
occurred.

Show details

This field appears only when there are multiple types of
events triggering the same alert.
If there are other types of events (that is, other reasons)
triggering the same alert, the total number of additional reasonsis displayed. You can click it to view a list of all events.

The date and time shown on the web interface are automatically converted to your computer's timezone. To avoid time confusion, it is suggested to apply the same time zone settings to your computer ormobile device.
Tip: You can also acknowledge all alarms in the front panel display.

147

PDU
Generic information and PDU settings are available on the PDU page.
To open the PDU page, click 'PDU' in the Menu.

▶ Device information shown:•

Firmware version•

Serial number•

MAC address•

Rating•Internal Beeper State•

Status of Power Supply Sensor▶ To configure global settings:
1. Click Edit Settings.

2. Now you can configure the fields.
• For time-related fields, you can also type a value manually, making sure to type in a time unit asshown in the drop-down list of values. For example, 30 s for seconds, 30 min for minutes, and soon.

In the following table, those fields marked with * are available on an outlet-switchingcapable model only.

148

Field

Function

Name

Customizes the device name.

NoteFieldFunction*Relay behavior
on power loss

Selects an operating mode to determine the See Latching Relay Behavior (on page 153).
latching relay behavior when PDU power is • PXO, PXC and Legrand PDU do not support
lost.
Latching Relays.
• Options: Non-latching and Latching•

Note

Non-latching has all relays open at thepower loss while latching has all relays
remain unchanged at the power loss.

*Outlet state on
power up

Determines the initial power state of ALL
outlets after the PX-Series PDU powers up.

(for non‑latchingmode only)••

After removing power from the PDU, you must
wait for a minimum of 10 seconds before
powering it up again. Otherwise, the default
outlet state settings may not work properly.

•

You can override the global outlet state setting
on a per-outlet basis so specific outlets behave
differently on power up. Configure this on theindividual outlet page.

•

This setting works only when 'Relay behavior on
power loss' is set to Non‑latching. This isbecause all relays keep their states unchangedin the latching mode regardless of the power
supply status.

Options: on, off, and last known
See Options for Outlet State on PowerUp (on page 154)

*OutletDetermines how long the PX-Series PDU
initialization delay waits before providing power to all outlets
on power up
after recovering from a temporary power(for non‑latching loss.

See Initialization Delay Use Cases (on page
155).
•

This setting works only when 'Relay behavior on
power loss' is set to Non‑latching. This isbecause all relays keep their states unchangedin the latching mode regardless of the power
supply status.

*Power off period Determines the power-off period after theduring power
outlet is switched OFF during a power cycle.
cycle• Range: 1 second to 1 hour•Power cycling the outlet(s) turns the outlet(s)off and then back on.

•

You can override this global power cycle setting
on a per-outlet basis so specific outlets' poweroff period is different.

*Inrush guard
delay

See Inrush Current and Inrush Guard Delay (on page
155).

mode only)•

Range: 1 second to 1 hour

Prevents a circuit breaker trip due to inrush
current when many devices connected to
the PDU are turned on.
•

Range: 100 milliseconds to 10 seconds

149

FieldFunction*Trip cause outlet If an outlet is suspected to have caused anhandling
OCP trip event, it can optionally be marked
as "Suspended" and handled differently.
•

Options: Keep outlet state unchanged,
or Suspend Outlet

Note
Suspended outlets are not turned back on when the
OCP is closed.
See Trip Cause Outlet Handling (on page 155).
Not supported on PX2, PXE, and PXO.

1. Click Save.

▶ To reset ALL energy counters:
An energy reading is a value of total accumulated energy, which is never reset, even if the power fails or
the PX-Series PDU is rebooted. However, you can manually reset this reading to restart the energy
accumulation process. Only users with the "Admin" role assigned can reset energy readings.
Note: This reset button does not reset the energy values of outlet groups. Go to the Outlet Groups page
to reset that value.
1. On the PDU page, in the Settings section, make sure Edit Settings is not clicked, or cancel out ofediting settings.
2. On the Reset all energy counters option, click Reset, then click on the confirmation message.
• All energy readings are reset to zero.
Tip: You can also reset the energy reading of an individual inlet or outlet on those pages.

▶ To reset all minimum/maximum values:
For readings that record a maximum and minimum numeric value, you can reset these values as needed
to clear the previous highs and lows.
1. On the PDU page, in the Settings section, make sure Edit Settings is not clicked, or cancel out ofediting settings.
2. On the Reset all minimum/maximum values option, click Reset, then click on the confirmation
message.
• All previously recorded maximum and minimum values are reset.

150▶ To view total energy and power on multi-inlet models:For multi-inlet models or inline monitors, a "Sensors" section show the data of total active energy andtotal active power."PDU Total" also gives the sum of active power and active energy and it is displayedon the Dashboard.Dashboard - PDUs (on page 137)
For a regular model with multiple inlets:•

Total active energy = sum of all inlets' energy values•

Total active power = sum of all inlets' active power values

For an inline monitor with multiple inlets/outlets:•

Total active energy = sum of all outlets' energy values•

Total active power = sum of all outlets' active power values▶ To configure the thresholds of total energy and power:
For a multi-inlet model or an in‑line monitor, a "Thresholds" section is also available on the PDU page.
See Setting Thresholds for Total Active Energy or Power (on page 156)

151

Internal Beeper StateThe PDU page indicates the internal beeper state.

▶ Available beeper states:
StatesDescription

Off

The beeper is turned off.

ActiveThe beeper is turned on.

Active (Muted)"Activation Reason" is displayed, indicating why the
beeper sounds an alarm.
For example, if the beeper is turned on because of a
specific event rule "X," the activation reason looks
like:
Event Action triggered by rule: X
Beeper sound will be turned off once the Mutebutton is clicked; the beeper state will show Muted.

▶ Scenarios when the beeper sounds an alarm:•

Any overcurrent protector, including fuses and circuit breakers, has tripped or blown.

•

You have set an event rule that turns on the internal beeper when a specific event occurs, and thatevent occurs now.

•

On models with residual current monitoring (RCM), the beeper also sounds when an RCM alarm isdetected.
Note that only the RCM sensor will cause the PDU to beep while RCM "DC" sensor does notcause the PDU to beep regardless of its sensor state.

152

▶ To mute the beeper:
1. Login to the PDU and click >PDU.
2. Scroll down to the Internal Beeper section.
3. Click the Mute button, then click again to confirm.
Beeper state now shows Active (Muted).

Latching Relay Behavior
Unlike non-latching relays, latching relays do NOT require power to keep their contacts closed. In
latching mode, relay status does not change on unit power failure. The load is powered immediately
when unit power is restored.
For supported models, outlet switching can be configured to operate as a true latching relay or tosimulate a non-latching relay. The operating mode determines the latching relay behavior when PDU
power is lost. Regardless of which mode is selected, relays do not consume power to keep the contacts
closed.

▶ Non-Latching Mode:•

Relay always opens when power is lost. This insures all relays are open when power is applied to the
PDU.

•

Always select this mode if the combined inrush current of the devices connected to the PDU trip
circuit breakers when power is applied to the PDU.

•This is the factory default operating mode.

153▶ Latching Mode:•

Preserve the relay state when power is lost.

•

This is the preferred operating mode ONLY if you are sure inrush current does not trip circuit
breakers when power is applied to the PDU.

•

Power to the outlet is not disrupted if a PDU internal failure occurs.

In latching mode, the following features are disabled.
On PDU page in Settings section:•

Outlet state on startup = last known•

Outlet initialization delay on device startup = 1sec

On Individual outlet page:•

State on device startup = PDU defined (last known)▶ Non-Latching Relay Behavior on Power-Up
When outlets start receiving power (be it on PDU power up after power cycle, when turning on an inlet
in a multi-inlet PDU or when a transfer switch switches back on after being off for some time), relays are
initialized to a state configurable per outlet:•

Leave outlet switched off after power-up•

Switch outlet on after power-up•

Restore outlet to last known state (default)

Note: PDU reboot, firmware update, and factory reset does not affect relay states.

Options for Outlet State on Power Up
The following are available options for initial power states of outlets after powering up the PX-Series
PDU device. This setting is used in three scenarios:•

powering up the whole PDU•

powering up a single inlet in a multi-inlet PDU (on most, but not all, multi-inlet units the outlet
boards are powered through the respective inlet)•transfer switch switches on again after being off due to e.g. internal failure
OptionFunctiononTurns on the outlet(s).

offTurns off the outlet(s).

last known Restores the outlet(s) to the previous power state(s) before the PXSeries PDU was powered off.
When configuring an individual outlet, there is one more outlet state option.

154

Additional option

Function

PDU defined (on/off/lastknown)

Follows the global outlet state setting, which is set on
the PDU page.
The value in parentheses is the currently-selected global
option.

Initialization Delay Use Cases
Apply the initialization delay in either of the following scenarios.
•

When power may not initially be stable after being restored•

When UPS batteries may be charging

Tip: When there are a large number of outlets, set the value to a smaller number toavoid a long wait before all outlets are available.

Inrush Current and Inrush Guard Delay▶ Inrush current:
When electrical devices are turned on, they can initially draw a very large current known as inrush
current. Inrush current typically lasts for 20-40 milliseconds.

▶ Inrush guard delay:
The inrush guard delay feature helps prevent a circuit breaker trip due to the combined inrush currentof many devices turned on at the same time.
For example, if the inrush guard delay is set to 100 milliseconds and two or more outlets are turned onat the same time, the PDU will sequentially turn the outlets on with a 100 millisecond delay occurring
between each one.

Trip Cause Outlet Handling
When an outlet has been suspected as the cause of a trip, the Trip Cause Outlet Handling setting allows
you to mark the outlet as Suspended.
A Suspended outlet is handled differently than usual:•once the respective OCP is closed, the outlet is not turned on again•

outlet state shows as 'suspended' in the web interface and the CLI•

warnings are shown when you attempt to turn on a suspended outlet•

for supported models, a different outlet LED color is shown

Time Units
If you choose to type a new value in the time-related fields, such as the "Idle timeout period" field, youmust add a time unit after the numeric value. For example, you can type '15 s' for 15 seconds.

155

Note that different fields have different range of valid values.

▶ Time units:
Unit

Time

ms

millisecond(s)ssecond(s)minminute(s)hhour(s)dday(s)

Setting Thresholds for Total Active Energy or PowerThis section applies only to multi‑inlet models, including in‑line monitors.
Thresholds for total active energy and total active power are disabled by default. You can enable and set
them so that you are alerted when the total active energy or total active power hits a certain level.
For a regular PX-Series PDU model with multiple inlets:•

Total active energy = sum of all inlets' active energy values•

Total active power = sum of all inlets' active power values

For an inline monitor with multiple inlets/outlets:•

Total active energy = sum of all outlets' active energy values•

Total active power = sum of all outlets' active power values▶ To configure thresholds for total active energy and/or power:
1.
2.
3.
4.

Click PDU.
Click the Thresholds title bar at the bottom of the page to display thresholds.
Click a sensor to edit the thresholds.
Make changes as needed.
• To enable any threshold, select the corresponding checkbox.
• Type a new value in the accompanying text box.

156

5. Click Save.

Minimum and Maximum Values for Numeric Sensors
You can display minimum and maximum values manually for each numerical sensor, and for groups ofmeasured values. These values are last change values before a reset and are not affected by reboots.
However, factory reset will reset to defaults which will hide these values.
Sections where min/max values are available:
Page

SectionPDU

Sensors (if numeric sensors in list)

PDU Sensor Details

Sensor

Inlet Single Phase

Single-phase sensor table

Inlet Multi Phase

Multi phase sensor table

Inlet Detail

Detailed sensor table

Inlet Sensor Details

Sensor

Inlet Residual Current

Detailed sensor table (for multiphase)

Inlet Residual Current Sensor Details

SensorOutlets

List

OutletSensors table

157

Page

SectionOutlet Sensor Details (numeric sensors only)

Sensor

Inlet/Outlet (single phase)

Single-phase sensor table

Inlet/Outlet (multi

Multi-phase sensor tablephase)
Inlet/Outlet (detailed)Detailed sensor table

Inlet/Outlet Sensor Details

Sensor(numeric sensors only)
Inlet/Outlet Residual Current Sensor

SensorDetails (numeric sensors only)
Outlet Groups

List

Outlet Group

Outlets list and Sensor table

Outlet Group Sensor Details

Sensor(numeric sensors only)
Overcurrent Protectors

List

Overcurrent Protector

Sensors table

Overcurrent Protector Sensor Details

Sensor(numeric sensors only)
Peripheral Devices

List

Peripheral Device Details (numeric sensors only) Sensor

Show and Hide Min/Max Values
You can reset the minimum/maximum values using Web UI.

▶ To configure the min/max functionality:
1. Go to the sections of the pages listed in the table of Minimum and Maximum Values for NumericSensors (on page 157).

2. Click. Minimum/maximum columns are only selectable if at least one row provides min/max
values.
3. Select the check boxes of Minimum and Maximum values.
Sensor table single-phase:158

Sensor table Multi-phase:•

By default overviews/tables where multiple numeric sensors are listed, min/max values are notdisplayed.

•

You can configure the displayed values, and make min/max values visible. Your configuration issaved and will be available when GUI is reloaded.

•

You can configure visible columns of sensor tables including min/max values and on sensor details
pages show min/max values.

159▶ To reset the min/max values:
1. Go to the sections of the pages listed in the table of Minimum and Maximum Values for NumericSensors (on page 157).
2. Click . The menu item "Reset Minimum / Maximum" is only visible (active or inactive) if at least
one row of the table has min/max values.

Power Supply Sensor
The PX-Series PDU's controller receives power from its inlet. A sensor monitors the power supply status
and indicates it on the PDU page.
This status is also available on the PDU's front panel display, or via the CLI with the command: show
pdu details.

State

Description

OK

The controller is receiving power from its own inlet.

fault

The controller cannot receive power from its own inlet because of apower failure on the inlet or a broken power supply. Instead it isreceiving power from another PX-Series PDU PDU.
See Power-Sharing Restrictions and Connection (on page 49).
After entering the fault state, this sensor is listed in the Alerted Sensors
section of the Dashboard. .

unavailable The communication with the power supply sensor is lost.

160

InletYou can view all inlet information, configure inlet-related settings, or reset the inlet active energy andmin/max sensor values on the Inlet page. To open this page, click 'Inlet' in the Menu.
Inlet thresholds help you identify when your inlet enters warning or critical level. In addition, you canhave PX-Series PDU automatically generate alert notifications for any warning or critical status. See
Event Rules and Actions (on page 291).
Note: For multi-inlet models, see Configuring a Multi-Inlet Model (on page 163).

▶ Overview:•

Inlet power overview, which is the same as Dashboard - Inlet I1 (on page 139).

▶ Sensors:•

A list of inlet sensors with more details. Available inlet sensors depends on the model.
• Sensors show both readings and states.
• Sensors in warning or critical states are highlighted in yellow or red.

•

Inlet's power chart, which is the same as Dashboard - Inlet History.

▶ Settings--Name the inlet:
Scroll down past the Sensor list to the Settings.
•

Click Edit Settings, enter a name for the inlet, then click Save. For example, name the inlet after the
power source.

•

The inlet's custom name is displayed on the Inlet or Dashboard page, followed by its label inparentheses.

▶ Settings--Reset energy counter:
The energy counter reset feature per inlet is especially useful when your PX-Series PDU has more than
one inlet. Only users with the "Admin" role assigned can reset this value.

161

•

Click Reset and then confirm in the message.
This inlet's active energy reading is then reset to zero.

Tip: To reset ALL active energy counters on the PX-Series PDU, go to the PDU page.

▶ Settings: Reset minimum/maximum:
All inlet sensors with numeric readings store their minimum and maximum recorded reading. You canreset these as desired. Only users with the "Admin" role assigned can reset this value.
Tip: To enable the display of minimum/maximum for any sensor, click theright of the Sensors lists.
•

Options icon at the top

Click Reset and then confirm in the message.
The min/max values and the "unchanged since" timestamps are reset to this moment's
sensor readings.

▶ To configure inlet thresholds:
By default, there are pre‑defined RMS voltage and current threshold values in related fields. You can
modify them to meet your needs.
1. Click the Thresholds title bar at the bottom of the page to display inlet thresholds.

2. Click the desired sensor to open the settings.
3. To enable a threshold, select the corresponding checkbox.
4. Type a new value in the accompanying text box.

162

Configuring a Multi-Inlet Model
If the PX-Series PDU has more than one inlet, the Inlets page lists all inlets.

▶ To view or configure each inlet:
1. Click the desired inlet.

2. Now you can configure the selected inlet, such as enabling thresholds or resetting its energy.
• To disable the inlet, see the following instructions.

▶ To disable one or multiple inlets:
1. On the individual inlet's data page, click Edit Settings.

163

2. Select the "Disable this inlet" checkbox.
3. Click Save.
4. The inlet status now shows "Disabled."

5. To disable additional inlets, repeat the above steps.
• If disabling an inlet will result in all inlets being disabled, a confirmation dialog appears, indicatingthat all inlets will be disabled. Then click Yes to confirm this operation or No to abort it.
After disabling any inlet, the following information or features associated with the disabled one are nolonger available:•

Sensor readings, states, warnings, alarms or event notifications associated with the disabled inlet.

•

Sensor readings, states, warnings, alarms or event notifications for all outlets and overcurrent
protectors associated with the disabled inlet.

•

The outlet-switching capability, if available, for all outlets associated with the disabled inlet.

Exception: All active energy sensors continue to accumulate data regardless of whether any inlet has
been disabled.
Warning: A disabled inlet, if remaining connected to a power source, continues to receive power fromthe connected power source and supplies power to the associated outlets and overcurrent protectors.

164

Outlets
The Outlets page shows a list of all outlets and the overview of outlet status and data. To open thispage, click 'Outlets' in the Menu.
On this page, you can:•View all outlets' status.

•

If any outlet sensor enters the alarmed state, it is highlighted in yellow or red.
Perform actions on all or multiple outlets simultaneously with setup/power-control commands on
the top-right corner.
Note that only outlet-switching capable models show the power-control buttons, and you
must have the Switch Outlet permission to perform outlet-switching operations.

•

Go to an individual outlet's data/setup page by clicking an outlet's name.

165▶ To show or hide specific columns on the outlets overview page:
1. Clickto show a list of Available Data of the Outlets Overview Page (on page 167).

2. Select those you want to show.

▶ To configure global outlet settings or perform the load-shedding command:
1. Clickto show a list of commands.
2. Select the desired command.
Note that only outlet-switching capable models have the commands marked with * in the table.
CommandRefer toThreshold Bulk Setup

Threshold Bulk Setup (on page 168)

*Sequence Setup

Sequence Setup (on page 169)

*Load Shedding Setup

Load Shedding Setup: Setting Non-Critical Outlets (onpage 171)*Activate Load Shedding

Load Shedding Mode: Activate or Deactivate (on page171)-- OR-Deactivate Load Shedding▶ To power control or reset the active energy readings of multiple outlets:
You can switch any outlet regardless of its current power state. That is, you can turn on any outlet that isalready turned on, or turn off any outlet that is already turned off.
1. Select outlets.
2. Click or select the desired button or command.

166• Power ON• Power OFF• Power Cycle: Power cycling the outlet(s) turns the outlet(s) off and then back on.
•> Reset Energy Counter: Resets active energy readings of selected outlets. Only users withthe "Admin" role assigned can reset active energy readings.

•> Reset Minimum/Maximum: Resets minimum and maximum numeric sensors values of
selected outlets. Only users with the "Admin" role assigned can do this.
3. Confirm the operation when prompted.
Tip: You can also power control an outlet or reset its active energy from Individual Outlet Pages.
When performing any outlet-switching operation, a 'Sequence running' message similar to thefollowing displays before the outlet-switching process finishes.
• It indicates how many selected outlets are NOT switched on/off or cycled yet.
• If needed, click Cancel to stop the outlet-switching operation.

Available Data of the Outlets Overview Page
To show or hide outlet data columns, click the columns icon.

167

•

Outlet status, which is marked with either icon below. This information is available on outletswitching capable models only.
Icon

Outlet status
Outlet turned on

Outlet turned off•

RMS current (A)•Active power (W)•Power factor•

Non-critical setting for indicating whether the outlet is a non-critical outlet. This information isavailable on outlet-switching capable models only.
Non-criticalsetting

Descriptiontrue

The outlet is a non-critical outlet, which will be turned OFF in theload shedding mode.

false

The outlet is a critical outlet, which will remain unchanged in theload shedding mode.

•

Lines

•

Outlet Groups: if the outlet belongs to a group, the outlet group name appears as a link.

•

Sequence order•

Sequence delay (seconds)

Threshold Bulk Setup
Outlet thresholds, if enabled, help you identify whether any outlet enters the warning or critical level.
You can also automatically generate alert notifications for any warning or critical status. Thresholds ofmultiple or all outlets can be configured simultaneously on the Outlets page. By default, there are
pre‑defined RMS voltage and current threshold values in related fields. See Default Voltage and Current
Thresholds (on page 734).
Available on models with outlet-metering.

▶ To configure thresholds-related settings for multiple outlets:
1.
2.
3.
4.

168

On the Outlets page, click> Threshold Bulk Setup.
In the "Show Outlet Sensors of Type" field, select a sensor type.
In the "For Outlets of Receptacle Type" field, select an outlet type.
Select the checkboxes of the outlets you want to configure.

5. Click the Edit Thresholds link.
6. Make changes as needed.
• To enable any threshold, select the corresponding checkbox.
• Type a new value in the accompanying text box.

7. Click Save.

Sequence Setup
By default, outlets are sequentially powered on in the ascending order from outlet 1 to the final whenturning ON or power cycling all outlets. You can change the order in which the outlets power ON. This isuseful when there is a specific order in which some IT equipment should be powered up first.
In addition, you can make a delay occur between two outlets that are turned on consecutively. For
example, if the power-on sequence is Outlet 1 through Outlet 8, and you want to wait for 5 seconds
before turning on Outlet 4, after Outlet 3 is turned on, assign a delay of 5 seconds to Outlet 3.

▶ To set the outlet power-on sequence and delay:
1. On the Outlets page, click> Sequence Setup.
2. Select one or multiple outlets by clicking them one by one in the 'Outlet' column.
3. Click the arrow buttons to change the outlet positions.
4. Click the 'Delay' column of the outlet that requires a wait after it is turned on.
5. Type a new value in seconds.
6. Click Save.

169

To change the order of outlets in the sequence, select the outlet and then click the up or down arrow
buttons to reorder them as needed. If you need to reset the order click on Restore sequence.

170

Load Shedding Setup: Setting Non-Critical Outlets
Outlets that are turned off when load shedding is activated are called non-critical outlets. Outlets thatare not affected by load shedding are called critical outlets.
Per default, all outlets are configured as critical.

▶ To determine critical and non-critical outlets:
1. On the Outlets page, click> Load Shedding Setup.
2. To set non-critical outlets, select the checkboxes of those you want. Or, select the Non-CriticalOutlets checkbox to set all outlets as non-critical.
3. To turn non-critical outlets into critical ones, deselect their checkboxes.
4. Click Save.

Load Shedding Mode: Activate or Deactivate
Load Shedding is not supported on all models
When a UPS supplying power to PX-Series PDU switches into battery backup operation, it may bedesirable to switch off non-critical outlets to conserve UPS battery life. This feature is known as load
shedding.
Outlets that are turned off when load shedding is activated are called non-critical outlets. Outlets thatare not affected by load shedding are called critical outlets. By default, all outlets are critical.
When load shedding is activated, the PX-Series PDU turns off all non-critical outlets. When load
shedding is deactivated, the PX-Series PDU turns back on all non-critical outlets that were ON before
entering the load shedding mode.
Exception: If you once manually perform switch-off operation on any non-critical outlets during the load
shedding mode, those outlets will NOT be turned back on when exiting the load shedding mode.

171

Activation of load shedding can be accomplished using the web interface, SNMP or CLI, or triggered by
the contact closure sensors.
Tip: It is better to check non-critical outlets prior to manually entering the load shedding mode. The
non-critical information can be retrieved from the Outlets page.
You must have one of the following permissions to perform the load shedding commands.
•'Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration'•'Switch Outlet' permission for all non-critical outlets•

Administrative privileges▶ To activate load shedding mode:
1. On the Outlets page, click> Activate Load Shedding.

Note: If the command is not available, check your permissions, especially whether you have the Switch
Outlet permission for ALL noncritical outlets.
2. Click Activate on the confirmation message.

In the load shedding mode:• You CANNOT power on any "non-critical" outlets. Note the Lock icon displays for these outlets.

172• The lock icon appears for "non-critical" outlets that WILL be automatically powered on whendeactivating the load shedding mode.
• The off icon appears for outlets, critical or non-critical, that WILL NOT be automatically powered onwhen deactivating the load shedding mode.
Tip: If you manually perform any power operations on non-critical outlets during the load shedding
mode, the icons vary. See Off and Lock Icons for Outlets (on page 174).
• The message "Load shedding active" appears next to the 'Outlets' title.
• If the Non-Critical column was hidden, it automatically is shown when load shedding mode isactivated.

▶ To deactivate load shedding mode:
1. On the Outlets page, click> Deactivate Load Shedding.
2. Click Deactivate on the confirmation message.
Now you can turn on/off any outlets.

▶ TIP -- automatic load shedding via contact closure sensors:
If you have connected a contact closure sensor, you can set up an event rule in a manner that thissensor's status change automatically activates or deactivates the load shedding mode. See Sample
Environmental-Sensor-Level Event Rule (on page 341).

173

Off and Lock Icons for Outlets
This section further explains the following two icons for outlets, which display in the load shedding
mode.
•

Lock icon: It means the outlet WILL be automatically powered on after deactivating the load
shedding mode.

•

Off iconmode.

: It means the outlet will remain powered OFF when deactivating the load shedding▶ Which outlets show the lock icon:•

Non-critical outlets that were powered ON prior to the load shedding mode•

Non-critical outlets that you manually switch on during the load shedding mode
Note: The switching-on operation does not power on the selected non-critical outlets while the load
shedding mode is active, but will cause those outlets to be automatically turned on after disabling
the load shedding mode.

▶ Which outlets show the Off icon:•

Any outlets, critical or non-critical, that were powered OFF prior to the load shedding mode•

Any outlets, critical or non-critical, that you manually switch off during the load shedding mode

Individual Outlet Pages
An outlet's data/setup page is opened after clicking the outlet's name on the Outlets overview page.

174

The individual outlet's page shows this outlet's detailed information. See Detailed Information on Outlet
Pages (on page 178).

▶ To control power:
On outlet-switching capable models, you can control power on the individual outlet page using power
control buttons just like the main Outlets page. You must have the Switch Outlet permission to performoutlet-switching operations.

▶ To configure this outlet:
1. Click Edit Settings.

2. Configure available fields. Note that the fields marked with * are only available on outlet-switchingcapable models.
Field

Description

Name

Type an outlet name up to 64 characters long.

*State on
devicestartup

Click this field to select this outlet's initial power state.

*Power off
periodduringpower cycle

Select an option to determine how long this outlet is turned off
before turning back on.

•

Options: on, off, last known and PDU defined.

•

Note that any option other than "PDU defined" will override theglobal outlet state setting on this particular outlet.

•

Options: PDU defined or customized time. See Power-Off Period
Options for Individual Outlets (on page 179).

•

Note that any time setting other than "PDU defined" will override
the global power-off period setting on this particular outlet.

175

FieldDescription*Non-critical Select this checkbox only when you want this outlet to turn off in theload shedding mode. See Load Shedding Mode: Activate or
Deactivate (on page 171).

1. Click Save.
2. The outlet's custom name, if available, is displayed in the outlets list, following by its label inparentheses.
Note for 'State on device startup': This setting works only when 'Relay behavior on power loss' is set toNon‑latching. This is because all relays keep their states unchanged in the latching mode regardless ofthe power supply status.

▶ To reset this outlet's energy counter or minimum/maximum values:
Energy counter is stored for each outlet. All outlet sensors with numeric readings store their minimum
and maximum recorded reading. You can reset these values for an individual outlet as desired. Only
users with the "Admin" role assigned can reset these readings.
1. On the individual outlet page, scroll down to Settings.
2. Click the Reset button to either "Reset energy counter" or Reset minimum/maximum.
3. Click to confirm the reset.

▶ To view this outlet's Outlet History power chart:
By default this outlet's active power data within the past two hours is shown in the power chart.
•

176

Click the selector under the chart to view any other power sensor reading for this outlet.

• To retrieve the exact data at a particular time, hover your mouse over the data line in the chart.
Both the time and data are displayed.

▶ To configure this outlet's threshold settings:
Per default, there are predefined RMS voltage and current threshold values in related fields. See Default
Voltage and Current Thresholds. You can modify the defaults as needed.
These threshold settings apply to a single outlet. You can also configure thresholds for multiple outlets
at once. See Threshold Bulk Setup (on page 168).
1. If the outlet's threshold data is invisible, click the Thresholds title bar to display it.

177

2. Click the desired sensor to edit.
3. Make changes as needed.
• To enable any threshold, select the corresponding checkbox.
• Type a new value in the accompanying text box.

4. Click Save.

Detailed Information on Outlet Pages
Each outlet's data page has the Details section for showing general outlet information and Sensors
section for showing the outlet sensor status.

▶ Details section:
Field

Description

Label

The physical outlet number

Outlet status

This information is only available on outlet-switchingcapable models.
On or Off178

Receptacle typeThis outlet's receptacle type

Lines

Lines associated with this outlet

FieldDescription

Inlet

This information is useful when there are multiple inlets
on your PDU.
Inlet associated with this outlet
Overcurrent
protector

This information is available only when your PX-Series
PDU has overcurrent protectors.
Overcurrent protector associated with this outlet▶ Sensors section:•

RMS current (A)•RMS voltage (V)•Active power (W)•Active energy (Wh)•Apparent power (VA)•

Power factor•

Line frequency (Hz) -- model dependent

Power-Off Period Options for Individual Outlets
There are two options for setting the power-off period during the power cycle on each individual
outlet's page.
OptionFunction

PDU defined(configured value)

Follows the global power-off period setting, which is set on
the PDU page. The value in parentheses is the current global
value.

Customized time•

Select an existing time option, or type a new value with anappropriate time unit added, such as s for seconds.

Outlet Groups
Only PDUs with outlet-switching and/or outlet-metering feature show this menu item.
Choose Outlet Groups in the Menu.

179

▶ Required permissions:
You must have one of the permissions below to be able to operate all or some of the outlet groupfeatures.
•

Administrator Privileges -- all operations•

Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration -- creating, editing and deletingoutlet groups•

Switch Outlet Group -- powering on, off or cycle outlet groups▶ Outlet group data:
The Outlet Groups page will list all outlet groups you create.

•

For each group, you can view the following data on the Outlet Groups page:• Group number• Name: the outlet group name displays as a link. Click to go to the details page for the group.
• Status: number of outlets with status ON, number of outlets with status OFF.
• Active Power: The active power for the group. A sum of all member outlets' active power values.
• Maximum Active Power: Hidden by default. Click the columns icon to add this data. The highest
recorded active power for the group.
• Outlets: A list of the outlet numbers who are members of the group. The PDU(s) of the outlets
displays as links.

Creating an Outlet GroupYou can create an outlet group if you often have to perform the same action on the same outlets at aregular interval.
For example, create an outlet group when you need to:•Power cycle specific outlets every week.

•

Sum up and track specific outlets' active power values every month.

•

Sum up the increased values of specific outlet's active energy values every month.

Note that an outlet can be a member of one or multiple groups.

180

To create an outlet group, you must have either permission below.
•

Administrator Privileges•

Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration▶ To create an outlet group:
1. In the Outlet Groups page, click Add Group.
2. Enter a Group name.
Tip: Outlet group names do not have to be unique. Different groups with the same group name can be
identified through their unique index numbers.

3. Click Save.

Outlet Group Power Control
You must have either permission below to power control any outlet groups.
•

Administrator Privileges•

Switch Outlet GroupThe power control commands are available on the Outlet Groups main page, where you can select one
or more groups to control AND on the individual outlet groups page, where you can control that grouponly while viewing details.

▶ To switch one or multiple groups on the Outlet Groups page:
1. On the Outlet Groups page, select the group or groups you want to control.
2. The power control commands appear in the top right corner.
3. Click a power control command.

181

• On: Power ON• Off: Power OFF• Cycle: Power cycle turns outlet OFF then back ON
4. Confirm the operation when prompted.

▶ To switch one group on a specific outlet group's page:
1. In the Outlet Groups page, click a group name to go to its details page.
2. Click a power control command on the top-right corner.

3. Confirm the operation when prompted.

If Switchable Outlet Groups are Limited
For the Switch Outlet Group permission, if you assign a role to any user, which permits the user toswitch only "specific" outlet groups instead of all outlet groups, the following switching issue may
appear.

▶ Issue:•

When an outlet group that the user originally can switch is deleted, and then re-created with thesame group name, the user will not be able to switch the "new" outlet group with the same groupname.

▶ Solution:
1. Edit the role assigned to the user. See Editing or Deleting Users (on page 230).
2. Find the Switch Outlet Group permission, and re‑select that newly-created outlet group in its outlet
group list.
Note: The above issue does not occur for any role which has "All Outlet Groups" selected for its Switch
Outlet Group permission.

Resetting a Group's Energy Counter and Minimum/Maximum
ValuesAn outlet group's active energy is the sum of increments of all member outlets' active energy values.

182

Note: A group's active energy is NOT the sum of all member outlets' active energy values.
•

You can reset the energy counter and minimum/maximum values of other readings for one or more
outlet groups at a time on the Outlet Groups page.

•

To reset these values for a single outlet group, there are two methods -- either Outlet Groups pageor individual group page.

•

Resetting an outlet group's energy counter has NO impact on any member outlet's energy counter.

You must have the Administrator Privileges to reset these values.
Available on models with outlet-metering▶ To reset values on the Outlet Groups page:
1. On the Outlet Groups page, select one or more outlet groups to reset.
2. Click> Reset Energy Counter, or Reset Minimum/Maximum, then confirm the operation when
prompted.

▶ To reset values on a specific outlet group's page:
1.
2.
3.
4.

On the Outlet Groups page, click a group name to open its page
Scroll down to the Settings section.
Click the Reset button to either "Reset energy counter" or Reset minimum/maximum.
Click to confirm the reset.

Modifying an Outlet GroupTo modify an outlet group, you must have either permission below.
•

Administrator Privileges•

Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration▶ To modify the member outlets:
1.
2.
3.
4.

On the Outlet Groups page, click a group name to go to its details page.
Click Edit Members.
Add or remove outlets of this group by selecting or clearing checkboxes.
Click Save.

▶ To change the group name:
1. Scroll down to the Settings section, then click Edit Settings.
2. Type a new name.
3. Click Save.

183

▶ To configure the thresholds of group sensors:
1. Click the Thresholds title bar at the bottom of the page to display thresholds.
2. Click the desired sensor (required), and then click Edit Thresholds.
3. Make changes as needed.
• To enable any threshold, select the corresponding checkbox.
• Type a new value in the accompanying text box.
4. Click Save.

Deleting an Outlet GroupTo delete an outlet group, you must have either permission below.
•

Administrator Privileges•

Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration

You can delete one or multiple outlet groups at a time.
To delete a single outlet group only, there are two methods -- either Outlet Groups page or individual
group page.

▶ To delete one or multiple groups on the Outlet Groups page:
1. On the Outlet Groups page, select one or more outlet groups.
2. Click> Delete, then confirm the operation when prompted.

▶ To delete a group on a specific outlet group's page:
1. Open a specific outlet group's page by clicking on its name.
2. Click> Delete, then confirm the operation when prompted.

Viewing More Information
On the individual outlet group page, you can view more information by doing the following.

▶ To observe an outlet group's active power chart:•

184

The chart of an outlet group's active power history will be shown for you to have an overview of its
overall changes in the past tens of minutes.

• To retrieve the exact data at a particular time, hover your mouse over the data line in the chart.
Both the time and data are displayed as illustrated below.

▶ To visit a member outlet's page from the current page:•

On an outlet group's individual page, you can go to a member outlet's page easily. Just click theoutlet links in the Outlets section.

185

▶ To visit a different outlet group's page from the current page:•

On an outlet group's individual page, you can go to another outlet group's page easily. Just click theoutlet selector

on the top-left corner.

OCPs
The OCPs page is available only when your model has overcurrent protectors, such as circuit breakers.
The OCPs page lists all overcurrent protectors as well as their status. If any OCP trips or its current level
enters the alarmed state, it is highlighted in red or yellow.
To open the OCPs page, click 'OCPs' in the Menu.
You can go to each OCP's data/setup page by clicking its name on this page. OCPs may be numbered C1,
C2, and so on, or BR1, BR2 and so on.

186▶ Overcurrent protector overview:•

OCP status - open (tripped) or closed•

Current drawn, rated current and current bar• The smaller, gray text adjacent to "current drawn" is the rated current of each OCP.
• The RMS current bars change colors to indicate the status if the OCP thresholds have been
configured and enabled.
StatusBar colors

normalabove upper warning

above upper critical

Note: The "below lower warning" and "below lower critical" states also show yellow and redcolors respectively. However, it is not meaningful to enable the two thresholds for current levels.
•

Protected outlets, which are indicated with outlet numbers•

Associated lines▶ To configure current thresholds for multiple overcurrent protectors:
OCP thresholds, when enabled, help you identify the OCP whose RMS current enters the warning or
critical level with the yellow or red color. In addition, you can automatically generate alert notifications
for any warning or critical status.
Note: By default, upper thresholds of an OCP's RMS current have been configured. You can modify themas needed.

187

1.
2.
3.
4.

Click
> Threshold Bulk Setup.
Select one or multiple OCPs.
Click Edit Thresholds.
Make changes as needed.
• To enable any threshold, select the corresponding checkbox.
• Type a new value in the accompanying text box.

5. Click Save.

Individual OCP Pages
An OCP's data/setup page is opened after clicking any OCP's name on the OCPs or Dashboard page.

▶ General OCP information:
Field

Description

Label

This OCP's physical number.

Status•C1, C2, C3...

•

BR1, BR2, BR3...

open or closed.

If a trip cause has been detected, the details are linked
here with the Open status.

188

Type

This OCP's type.

RatingThis OCP's rated current.

Lines

Lines associated with this OCP.

Protected
outlets

Outlets associated with this OCP.

FieldDescription

Inlet

Inlet associated with this OCP.

Useful when your PDU has multiple inlets.
RMS current

This OCP's current state and readings, including current drawn
and current remaining.

▶ To customize this OCP's name:
1. Click Edit Settings.
2. Type a name.
3. Click Save.

▶ To view this OCP's RMS current chart:
This OCP's data chart is shown in the Overcurrent Protector History section.

•

To retrieve the exact data at a particular time, hover your mouse over the data line in the chart.
Both the time and data are displayed as illustrated below.

189▶ To configure this OCP's threshold settings:
By default, upper thresholds of an OCP's RMS current have been configured. You can modify them as
needed.
1. Click the Thresholds title bar at the bottom of the page to display the threshold data.

2. Click the RMS current sensor, then make changes as needed.
• To enable any threshold, select the corresponding checkbox.
• Type a new value in the accompanying text box.

3. Click Save.

190▶ Other operations:•

Go to another OCP's data/setup page by clicking the OCP selector•

Go to the associated Inlet's data page by clicking the Inlet link in the Details section.

on the top-left corner.

OCP Trip-Cause Detection
Not supported on all models.
When the outlet that most likely caused a trip can be detected, this information displays in the webinterface, front panel display, and command line interface (CLI).

▶ Web interface:•On the page of a tripped OCP, the Status field indicates the outlet number that may cause the OCPtripped event.

191

▶ Front panel display:
The 'Likely trip cause' message will be displayed for an "open" OCP, indicating which outlet may cause
the OCP-tripped event.

▶ CLI:•

Perform the show ocp command in the CLI. If any OCP has tripped, then the outlet that may cause
this event is shown in parentheses in the State field of the tripped OCP.

Peripherals
If there are environmental sensor packages connected, they are listed on the Peripherals page.
An environmental sensor package may contain:•

Numeric sensors: Detectors that show both readings and states, such as temperature sensors.

•

State sensors: Detectors that show states only, such as contact closure sensors.

•

Actuators: An actuator controls a system or mechanism so it shows states only.

PX-Series PDU communicates with managed sensors/actuators only and retrieves their data. One PXSeries PDU can manage a maximum of 64 sensors/actuators.

192

Open the Peripheral Devices page by clicking Peripherals in the Menu. Then you can:•Perform actions on multiple sensors/actuators by using the control/action icons on the top-rightcorner.

•Go to an individual sensor's or actuator's data/setup page by clicking its name.

▶ Sensor/actuator overview on this page:
If any sensor enters an alarmed state, it is highlighted in yellow or red. An actuator is never highlighted.
ColumnDescription

Name

By default, the name assigned contains:•

Sensor/actuator type, such as "Temperature" or "Dry Contact."•

Sequential number of the same sensor/actuator type, like 1, 2,
3 and so on.
You can customize the name. Customize names on theindividual sensor page.

Reading

Numeric sensors, such as temperature and humidity, show thereading.

Maximum

Maximum reading of all previously seen values since last reset.

Minimum

Minimum reading of all previously seen values since last reset.

State

Available for all sensors and actuators. Sensor/Actuator States (onpage 199)

Type

Sensor or actuator type.

SerialNumberThis is the serial number printed on the sensor package's label.

Position

Position indicates where this sensor or actuator is located in thesensor chain.
Identifying the Sensor Position and Channel (on page 201)

Actuator

Indicates whether this sensor package is an actuator or not. If yes,
the checkmark symbol

is shown.

▶ To release or manage sensors/actuators:
You can multi-select sensors to release or manage them. Releasing is necessary when the maximum
number of managed sensors are in use, and you need to make a change, such as replacing old sensors
with new ones, or making space by removing an unneeded type and adding a different type. When you
manage sensors individually, you can manually select ID numbers--this allows you to simultaneously193release an old sensor if you select to reuse its assigned ID: Managing One Sensor or Actuator (on page201). When you manage multiple sensors at once, ID numbers are automatically assigned, and nothingelse is changed or released.
1. Select the sensors/actuators that you want to manage/release from management.
2. Clickto view options and select Manage or Release.

• Release: The items are automatically released, and you return to the list. Newly released sensors
show at the end of the list as "Manage Device" if they are still physically connected, otherwise they
disappear.
• Manage: "Manage Peripheral Device" dialog opens. Click Manage to accept automatic sensor
numbers. If a single item was selected, you can choose the ID number by selecting "Manually selecta sensor number." Click Manage and you return to the list. Newly managed sensors appear and willshow a status in the State column. They can now be renamed and configured.

194

▶ To configure sensor/actuator-related settings:
1. Click> Peripheral Device Setup.

Field

Function

Peripheral device Options to describe the vertical locations (Zcoordinates) of environmental sensor
Z coordinate
packages.
format•Rack units or Free-form

NoteEvery sensor has a Z Coordinate field. The format
setting specifies whether those coordinates are
required to be rack unit numbers or can contain
arbitrary text.

See Z Coordinate Format (on page 208).

Peripheral device Enables or disables the automaticmanagement feature for Raritan
auto
environmental sensor packages.
management•

Default is Enabled.

Mute other door
handle•If selected, one door handle will becompletely powered down (including any
attached card reader or keypad) before
opening the other lock of the same DX2DH2C2.

AltitudeSpecify the altitude of PX-Series PDU above
sea level when a differential air pressure
sensor is attached.
•Range: -425 to 3000 meters (-1394 to
9842 feet)•

Negative numbers indicate locations
below sea level.

Automatic Management of Sensors (on page
201)•

This option helps to avoid overload in
power-limited setups with two door
handles.

•

The device's altitude is associated with thealtitude correction factor.

•

The default altitude measurement unit ismeter.

•Your user preference for measurements willtake effect here.

195

FieldFunction

Note

Active powered
dry contact limit

Determines the maximum number of "active"
powered dry contact actuators that ispermitted concurrently.

•

An "active" actuator is turned ON, or, for adoor handle, door is OPENED.

•

This setting only applies to "powered dry
contact" (PD) actuators rather than normal"dry contact" actuators.

•

You need either 'Change Peripheral Device
Configuration' privilege or 'Administrator
Privileges' to change the setting.

•Range: 0 to 24•

Default: 1

1. Click Save.

▶ To configure default threshold settings:
Note that default threshold settings affect all sensors already being managed, and establish the initial
settings for any sensor added from now on. To customize the threshold settings on a per-sensor basis,go to Individual Sensor/Actuator Pages (on page 203).

1. Click> Default Threshold Setup.
2. Click a sensor to open the threshold settings.
3. Make changes as needed.
• To enable any threshold, select the corresponding checkbox.
• Type a new value in the accompanying text box.

196

4. Deassertion hysteresis: An alarm is cleared when the sensor reading normalizes the specified
amount away from the threshold. In the screenshot example above, if temperature normalizes bymore than 1 degree of the threshold, the alarm is cleared. When the reading is within 1°C from thethreshold, the alarm will remain active. For example: A warning is raised when the temperature
exceeds 30°C. It has to drop to 29°C to clear the warning.
5. Assertion timeout: An alarm is raised when the sensor reading exceeds a threshold for more than
the specified number of samples. In the screenshot example above, timeout is set to Zero. An alarm
would be raised immediately when the reading exceeds the threshold. If the timeout were set for
20, the sensor reading would have to persist in exceeding a threshold for 20 data samples before an
alarm would be raised.
6. Click Save.

▶ To turn on or off any actuator:
1. Select one or multiple actuators . This activates the power buttons at the top right corner in the webinterface.
2. Click On or Off. For Door Handles, click Open or Close.
Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered dry
contact" actuator can be turned on at the same time. Change this setting in
Setup.

> Peripheral Device

3. Confirm the operation when prompted.

Yellow- or Red-Highlighted Sensors
The PX-Series PDU highlights those sensors that enter the abnormal state with a yellow or red color.
Note that numeric sensors can change colors when thresholds are enabled.
Tip: When an actuator is turned ON, it is also highlighted in red for drawing attention.

197

In the following table, "R" represents any numeric sensor's reading. The symbol <= means "smallerthan" or "equal to."Sensor status Color States shown in the interface

Description

Unknown

unavailable

Sensor state or readings cannot be detected.

unmanaged

Sensors are not being managed.

normal•NormalNumeric or state sensors are within the normal range.
-- OR --•
Warning

No thresholds have been enabled for numeric sensors.

above upper warning

Upper Warning threshold < "R" <= Upper Critical threshold

below lower warning

Lower Critical threshold <= "R" < Lower Warning threshold

above upper critical

Upper Critical threshold < "R"

below lower critical"R" < Lower Critical threshold

AlarmedalarmedState sensors enter the abnormal state.

OCP alarm

Open•

CriticalCircuit breaker trips.
-- OR --•

Fuse blown.

Managed vs Unmanaged Sensors/Actuators▶ Managed sensors/actuators:

198•

PX-Series PDU communicates with managed sensors/actuators and retrieves their data.

•

Managed sensors/actuators are always listed on the Peripheral Devices page whether they arephysically connected or not.

•

They show one of the managed states.

•

For managed 'numeric' sensors, their readings are retrieved and displayed. If any numeric sensor is
disconnected or its reading cannot be retrieved, it shows "unavailable" for its reading.

▶ Unmanaged sensors/actuators:•

PX-Series PDU does NOT communicate with unmanaged sensors/actuators.

•

Unmanaged sensors/actuators are listed only when they are physically connected to PX-Series PDU.

•

They disappear from the web interface when they are no longer connected.
They do not have an ID number.

•

They show the "unmanaged" state.

Sensor/Actuator States
An environmental sensor or actuator shows its real-time state after being managed.
Available sensor states depend on the sensor type -- numeric or state sensors. For example, a contact
closure sensor is a state sensor so it switches between three states only -- unavailable, alarmed andnormal.
Sensors will be highlighted in yellow or red when they enter abnormal states.
An actuator's state is marked in red when it is turned on.

▶ Managed sensor states:
In the following table, "R" represents any numeric sensor's reading. The symbol <= means "smallerthan" or "equal to."State

Description

normal•For numeric sensors, it means the readings are within thenormal range.

•

For state sensors, it means they enter the normal state.

below lower critical "R" < Lower Critical threshold
below lower
warning

Lower Critical threshold <= "R" < Lower Warning threshold

199

StateDescription

above upper
warning

Upper Warning threshold < "R" <= Upper Critical threshold

above upper critical Upper Critical threshold < "R"
alarmedThe state sensor enters the abnormal state.

unavailable•

Communication with the managed sensor is lost.
-- OR --•

Sensor packages are upgrading their sensor firmware.

Note that for a contact closure sensor, the normal state depends on the normal setting you haveconfigured.

▶ Managed actuator states:
State

Descriptionon

The actuator is turned on.

off

The actuator is turned off.

unavailable•

Communication with the managed actuator is lost.
-- OR --•

Sensor packages are upgrading their sensor firmware.

▶ Unmanaged sensor/actuator states:
State

Description

unmanaged Sensors or actuators are physically connected to the PX-Series PDU
but not managed yet.

Note: Unmanaged sensors or actuators will disappear from the web interface after they are no longer
physically connected.

Finding the Sensor's Serial Number
A sensor package has a serial number tag attached to its rear side.
The serial number for each sensor or actuator appears listed in the web interface when it is detected.
Match the serial number from the tag to those listed in the sensor table.

200

Identifying the Sensor Position and Channel
The Peripheral Devices page shows where each sensor or actuator is connected.

•

The position information includes the port name and the sensor's position in a sensor chain.

•

For example: Port 'Sensor', Chain Position 3
If a sensor hub is involved, the hub port information is also indicated for most sensors.

•

For example: Port 'Sensor', Hub port 2, Chain Position 3
If a sensor/actuator contains channels, such as a contact closure sensor or dry contact actuator, thechannel information is included.
For example, Port 'Sensor', Hub port 2, Chain Position 3, Channel 1

Automatic Management of Sensors
To configure automatic management, go to Peripherals >> Peripheral Device Setup.

▶ After enabling the automatic management function:
When the maximum number of sensors are not yet managed, newly-connected environmental sensors
and actuators are automatically managed upon detection.

▶ After disabling the automatic management function:
You must manually manage all sensors to start communications. Until you do this, they will not have ID
numbers or show sensor readings or states.

Managing One Sensor or Actuator
If you are managing only one sensor or actuator, you can assign the desired ID number to it. Whenmanaging multiple sensors/actuators at a time, the IDs are automatically assigned.

201

Tip: When the total of managed sensors/actuators reaches the maximum value, you cannot manage
additional ones. The only way to manage any sensor/actuator is to release or replace the managed
ones. To replace a managed one, assign an ID number to it by following the procedure below.

▶ To manage only one sensor/actuator:
1. Click Peripherals in the Menu.
2. Unmanaged sensors/actuators appear at the end of the list as "Manage Device". You can identify
the sensor/actuator by the Type, Serial Number, and Position columns.

3. Click the Manage Device link, and the Manage Peripheral Device dialog appears.

• Select "Automatically assign a sensor number" to assign an unused ID number. This method does
not release any managed sensor or actuator.
• Select "Manually select a sensor number" to select a desired ID number from the list. Selecting an
ID already in use will release the sensor currently managed with that ID. IDs already in use show
the sensor package's serial number. Available IDs show "unused."
4. Click Manage.

▶ Special note for Legrand humidity sensors:
A Legrand humidity sensor is able to provide three measurements - relative and absolute, and humidity
values.

202

•A relative humidity value is measured in percentage (%).

•

An absolute humidity value is measured in grams per cubic meter (g/m3).

•

A dew point is measured in degree celsius (°c).

However, only relative humidity sensors are "automatically" managed if the automatic management
function is enabled. You must "manually" manage absolute humidity sensors as needed.
Note: Relative and absolute values of the same humidity sensor do NOT share the same ID number
though they share the same serial number and position.

Individual Sensor/Actuator Pages
A sensor's or actuator's data/setup page is opened after clicking any sensor or actuator name on the
Peripheral Devices page.
Note that only a numeric sensor has threshold settings, while a state sensor or actuator has nothresholds.
Threshold settings, if enabled, help you identify whether any numeric sensor enters the warning or
critical level. In addition, you can have PX-Series PDU automatically generate alert notifications for any
warning or critical status.

▶ To configure a numeric sensor's threshold settings:
1. Click Edit Thresholds.

Tip: The date and time shown on the PX-Series PDU web interface are automatically converted to yourcomputer's time zone. To avoid time confusion, it is suggested to apply the same time zone to yourcomputer or mobile device.
2. Select or deselect 'Use default thresholds' according to your needs.

203• To have this sensor follow the default threshold settings configured for its own sensor type, selectthe 'Use default thresholds' checkbox.
The default threshold settings are configured on the page of Peripherals.
• To customize the threshold settings for this particular sensor, deselect the 'Use default thresholds'
checkbox, and then modify the threshold fields below it.
Note: For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor
Threshold Settings (on page 727).
3. Click Save.

▶ To set up a sensor's or actuator's physical location and additional settings:
1. Click Edit Settings.

204

2. Make changes to available fields, and then click Save.
FieldsDescription

Name

A name for the sensor or actuator.

Description

Any descriptive text you want.

Location (X, Y
and Z)

Describe the sensor's or actuator's location in the data center by typing alphanumeric values for the
X, Y and Z coordinates. See Sensor/Actuator Location Example: X, Y, Z Coordinates (on page 208)
If the term "Rack Units" appears in parentheses in the Z location, you must type an integer number.
The Z coordinate's format is determined on the page of Peripherals.

Alarmed toNormal Delay

This field is available for the DX2‑PIR presence detector only.
It determines the wait time before the PX-Series PDU announces that the presence detector is backto normal after it already returns to normal.
Adjust the value in seconds.

Binary Sensor
SubtypeThis field is available for any Raritan contact closure sensor except for DX2‑DH2C2's
contact closure sensors.
Determine the sensor type of your contact closure detector.
•

Contact Closure detects the door lock or door open/closed status.

•

Smoke Detection detects the appearance of smoke.

•

Water Detection detects the appearance of water on the floor.

•

Vibration detects the vibration of the floor.

205

Fields

Description

Sensor Polarity

This field is available for DX2‑CC2 contact closure sensors only.
Determine the normal state of your DX2‑CC2.
•

Normal Open: The open status of the connected detector/switch is considered normal. An alarmis triggered when the detector/switch turns closed.

•

Normal Closed: The closed status of the connected detector/switch is considered normal. An
alarm is triggered when the detector/switch turns opened.

▶ To view a numeric sensor's chart
This sensor's data within the past tens of minutes is shown in the chart. Note that only a numeric sensor
has this diagram. State sensors and actuators do not have such data.

•206

To retrieve the exact data at a particular time, hover your mouse over the data line in the chart.
Both the time and data are displayed as illustrated below.

▶ To turn on or off an actuator:
1. Click the desired control button.

: Turn ON.
: Turn OFF.
2. Confirm the operation on the confirmation message.
Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered
dry contact" actuator can be turned on at the same time. To change this limitation of "powered dry
contact" actuators, modify the active powered dry contact setting on the Peripherals page.

207

▶ Other operations:
You can go to another sensor's or actuator's data/setup page by clicking the selector
left corner.

on the top-

Z Coordinate Format
Z coordinates refer to vertical locations of environmental sensor packages. You can use either thenumber of rack units or a descriptive text to describe Z coordinates.

▶ To configure Z coordinates:
1. Determine the Z coordinate format in the main Peripheral Device Setup page. Available Z coordinate
formats include:• Rack Units: Measurement of the height is in standard rack units. Number from 0-60.
• Free-form: Enter any alphanumeric string to describe the Z coordinate. Up to 24 characters.
Example, "Top of Rack", "Bottom of Rack".
2. Enter the Z coordinates in the individual sensor settings.

Sensor/Actuator Location Example: X, Y, Z Coordinates
Use the X, Y and Z coordinates to describe each sensor's or actuator's physical location in the data
center.
The X, Y and Z values act as additional attributes and are not tied to any specific measurement scheme.
Therefore, you can use non-measurement values.

208

▶ Example:
X = Brown Cabinet Row
Y = Third Rack
Z = Top of Cabinet▶ Values of the X, Y and Z coordinates:•

X and Y: They can be any alphanumeric values comprising 0 to 24 characters.

•

Z: When the Z coordinate format is set to Rack units, it can be any number ranging from 0 to 60.
When its format is set to Free-form, it can be any alphanumeric value comprising 0 to 24 characters.

209

Serial Access With Dominion Serial Access Module

Connecting a PX-Series PDU and a Dominion Serial Access Module (DSAM) provides access to devices
such as LAN switches and routers that have a RS-232 serial port.
The DSAM is a 2- or 4 port serial module that derives power from the PX-Series PDU.
Connect a maximum of 2 DSAM modules to the PX-Series PDU using USB cables. DSAM can be mounted
in a 0U configuration.

In This Chapter
DSAM Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
DSAM LED Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
View DSAM Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Configure DSAM Serial Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Connect to DSAM Serial Targets in the Web Interface. . . . . . . . . . . . . . . . . . . . . . 214
DSAM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Connect to DSAM Serial Targets via SSH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

DSAM Connection▶ To connect DSAM to PX-Series PDU:

210•

Connect the DSAM unit's USB cable to the PX-Series PDU USB-A ports. No USB Hubs are supported•

Connect the serial devices to the serial ports on the DSAM unit.

•

The serial access ports of DSAM can operate in DTE (Data Terminal Equipment) or DCE (Data Circuit
Terminating Equipment) mode

DSAM LED Operation
The DSAM unit has one LED for status, and 2 LEDs on each port.

▶ Status LED:
The Status LED is labeled on the unit front. Light is on back. The Status LED gives information at bootup
and upgrade.
•

Green LED - Slow blink: DSAM booting up but not controlled by PX-Series PDU.

•

Blue LED - Slow blink: DSAM controlled by PX-Series PDU.

•

Blue LED - Fast blink: Firmware upgrade in progress.

▶ USB Port LEDs:
Each USB port has a left Green LED and a right Yellow LED.
•

Green LED: Port is set as DCE•

Yellow LED: Port is set as DTE•

LEDs off: Port is set as AUTO

View DSAM Serial Ports
When a DSAM unit is connected to the PX-Series PDU, a DSAM Serial Ports page is available.

211▶ To view DSAM serial ports:
Click DSAM Serial Port Access. You can access and configure serial ports from this page.
•

Ports are listed by physical USB position on the DSAM unit.

•# column indicates which PX-Series PDU USB port DSAM is plugged into.

•

Type column indicates port's DTE/DCE setting.

•Status and Availability columns show current activity.

Configure DSAM Serial Ports
You can rename serial ports and configure their settings.

▶ To configure DSAM serial ports:
1. Click DSAM Serial Port Access, then click the name of the port for the port you want to configure.

212

2. In the General section:• Enter a Name for the port.
• Check the Current State of the port. Status and Availability are listed.
3. In the Serial Settings section, check or change the following settings:

213

Connect to DSAM Serial Targets in the Web Interface▶ To connect to DSAM serial targets in the web interface:
1. Click DSAM Serial Port Access to view the list of ports.
2. Click Connect button of the port you want to connect to.
HSC launches in a new window.

214

DSAM CLI Commands•

show• show sxport [<sxportid>]
Shows serial access port parameters• sxportid Serial access port id (or 'all') (1.1/1.2/all) [all]Shows DSAM serial port parameters

Example:# show sxport 1.1
Port ID: 1.1
Name: DSAM 1 - Port 1
Device connected: No
Device interface type: Automatic
Baud rate: 9600
Parity: None
Data bits: 8
Stop bits: 1
Flow control: None
BREAK duration: 300 ms
SSH DPA port enabled: No
SSH DPA port: 10101
Allow shared access: No
Status: Available•

connect:
Connect to a DSAM serial port
▪ connect [<sxportid>]

Note: You have write access to this port215

During connecting to target, Pressing the escape sequence (CONTROL-]) the following
target port CLI command can be reached:clientlist Display all users on the port
close Close this target connection
getwrite Get write access for the port
resetport Reset port
return Return to the target session
sendbreak Send a break to the connected target
writelock Lock write access to this port
writeunlock Unlock write access to this port
Pressing ? will provide help
• config
You can configure only connected DSAMs ports▪ config:# sxport
sxport <sxportid> [name <name>] [devinterfacetype <deviftype>] [baudrate <baudrate>][parity <parity>] [stopbits <stopbits>] [flowcontrol <flowcontrol>] [breakduration<breakduration>] [sshdpaportenabled <sshdpaportenabled>] [sshdpaport <sshdpaport>][allowsharedaccess <allowsharedaccess>]
Configure serial access port settings:
sxportid Serial access port id (1.1/1.2)
name Port namedevinterfacetype Device interface type (AUTO/DTE/DCE)
baudrate Serial port speed (baud rate) in bits-per-second(1200/1800/2400/4800/9600/19200/38400/57600/115200/230400)
parity Parity type (none/odd/even)stopbits Number of stop bits (1..2)
flowcontrol Flow control type (none/hw/sw)
breakduration Duration of BREAK signal in ms (0..1000)
sshdpaportenabled Enable direct port access via Secure Shell (SSH) (true/false)
sshdpaport TCP port for direct port access via Secure Shell (SSH) (1024..49999)
allowsharedaccess Allow shared (r/o) access (true/false)

Connect to DSAM Serial Targets via SSH▶ To connect to DSAM serial targets via SSH:
1. Make sure that SSH Access is enabled in Device Settings > Network Services > SSH.
2. Connect to the port in two ways:•

Via configured SSH DPA port:
1. Type command ssh -p <SSH DPA port> user@device

216Note: Make sure SSH DPA port enabled is selected in DSAM Serial Port Access >DSAM Port #.
•Via regular TCP port:

1. Type command ssh user:1.2@device
1. After login, user will enter CLI interface.
2. Press Escape Sequence ^]3. Type commands See: DSAM CLI Commands (on page 215)
Example: show sxport 1.1
4. To exit serial target, type escape-key-sequence, default is Ctrl-], then enter port sub-menu CLIinterface.
5. Type "close", then enter main CLI interface.

Asset Strips
After connecting and detecting asset management strips (asset strips), the PX-Series PDU shows 'Asset
Strip' in the menu.
On this page, you can configure the rack units of asset strips and asset tags. A rack unit refers to a tag
port on the asset strips. The "Change Asset Strip Configuration" permission is required.

▶ To configure asset strip and rack unit settings:
1. Click Asset Strips in the menu, then click the Asset Strip you want to configure.
2. Click Edit Settings.

217

3. Make changes to the settings by directly typing a new value, or clicking that field to select a different
option.
Field

Description

Name

Name for this asset strip assembly.

Number of rackunits

The number of rack units is auto-detected for all supported
AMS, the input field is always disabled.

Numbering mode The rack unit numbering method in a rack/cabinet.
•

Top-Down: The numbering starts from the highest rack unitof a rack/cabinet.

•

Bottom-Up: The numbering starts from the lowest rack unitof a rack/cabinet.

Numbering offset The start number in the rack unit numbering.
For example, if this value is set to 3, then the first number is 3,
the second number is 4, and so on.
Color withconnected tag

Click this field to determine the LED color denoting thepresence of an asset tag.
•

Color without
connected tag

Click this field to determine the LED color denoting the absenceof an asset tag.
•

218

Default is green.

Default is red.

For color settings, there are two ways to set the color.
• Click a color in the color palette.
•

Type the hexadecimal RGB value of the color, such as #00FF00.

1. Click Ok. The rack unit numbering and LED color settings are immediately updated on the Rack Unitslist illustrated below.
•

The 'Index' number is the physical tag port number printed on the asset strip, which is notconfigurable. However, its order will change to reflect the latest rack unit position.

219

•

A blade extension strip and a programmable tag are marked with the word 'programmable' in the
Asset/ID column. You can customize their Asset IDs.

▶ To customize a single rack unit's settings:
You can make a specific rack unit's LED behave differently from the others on the asset strip, including
the LED light and color.
1. Click the desired rack unit position on the Rack Units list. The setup dialog for the selected one
appears.

220

2. Make changes to the information by typing a new value or clicking that field to select a different
option.
Field

Description

Name

Name for this rack unit.
For example, you can name it based on the associated IT device.

Operation
Mode

Determine whether this rack unit's LED behavior automaticallychanges according to the presence and absence of the asset tag.
•

Auto: The LED behavior varies, based on the asset tag's
presence.

•

Manual Override: This option differentiates this rack unit's LED
behavior.

LED ModeThis field is configurable only after the Operation Mode is set
to Manual Override.
Determine how the LED light behaves for this particular rack unit.
•

On: The LED stays lit.

•

Off: The LED stays off.

•

Slow blinking: The LED blinks slowly.

•

Fast blinking: The LED blinks quickly.

221

FieldDescription

LED Color

This field is configurable only after the Operation Mode is set
to Manual Override.
Determine what LED color is shown for this rack unit if the LED is lit.

▶ To expand a blade extension strip:
A blade extension strip, like an asset strip, has multiple tag ports. An extension strip is marked with agrayer color on the Asset Strip page, and its tag ports list is collapsed by default.
Note: If you need to temporarily disconnect the blade extension strip from the asset strip, wait at least
1 second before re-connecting it back, or the PX-Series PDU device may not detect it.
1. Locate the rack unit (tag port) where the blade extension strip is connected. Click its slot number,whose format is similar to, where N is the total number of its tag ports.

2. All tag ports of the blade extension strip are listed below it. Their port numbers are displayed in the
Slot column.

222• To hide the blade extension slots list, click.

▶ To customize asset IDs on programmable asset tags:
You can customize asset IDs only when the asset tags are "programmable" ones. Non-programmabletags do not support this feature. In addition, you can also customize the ID of a blade extension strip.
If a barcode reader is intended, connect it to the computer you use to access the PX-Series PDU.
1. Click Program Asset IDs.

223

2. In the Asset/ID column, enter the customized asset IDs by typing values or scanning the barcode.
• When using a barcode reader, first click the desired rack unit, and then scan the asset tag. Repeat
this step for all desired rack units.
• An asset ID contains up to 12 characters that comprise only numbers and/or UPPER CASE letters.
Lower case letters are NOT accepted.

224

3. Verify the correctness of customized asset IDs and modify as needed.
4. Click Apply at the bottom of the page to save changes.

Asset Strip Automatic Firmware Upgrade
After connecting the asset strip, it automatically checks its own firmware version against the version of
the asset strip firmware stored in the PX-Series PDU. If two versions are different, the asset strip
automatically starts downloading the new firmware from the PX-Series PDU to upgrade its own
firmware.
During the firmware upgrade, the following events take place:•

The asset strip is completely lit up, with the blinking LEDs cycling through diverse colors.

•

A firmware upgrade process is indicated in the web interface.

•

An SNMP trap is sent to indicate the firmware upgrade event.

External Beeper
After connecting and detecting a supported external beeper, the PX-Series PDU shows 'External Beeper'in the menu.
The External Beeper page shows an external beeper's status, including:

225

•

Number of the FEATURE port where this external beeper is connected•

Device type•

Connection status•

The beeper's state - off or active

Power CIM
After connecting and detecting a Power CIM, the PX-Series PDU shows 'Power CIM' in the menu.
The Power CIM page shows the CIM's status, including:•Number/information on the port where this CIM is connected.

•

Device type•

Connection status

User Management
User Management deals with user accounts, permissions, and preferred measurement units on a peruser basis.
PX-Series PDU is shipped with one built-in administrator account. You cannot delete this administrator
account or change its roles, but you can rename it. Besides the default administrator account, you cancreate an additional administrative user that can be disabled, renamed or removed. The Admin role isthe system-defined administrator role that includes all privileges. You can create additional users androles. User roles determine the tasks/actions a user is permitted to perform, so you must assign one or
multiple roles to each user.
If you are using remote authentication, you do not have to create users accounts locally. Settings are in
Device Settings > Security > Authentication. See Setting Up External Authentication (on page 277).

Creating Users
All local users must have a user account, containing the login name and password. Multiple users canlog in simultaneously using the same login name.
To add users, choose User Management > Users > then click the Add User icon

226.

▶ User information:
Field/setting

Description

User name

The name the user enters to log in.

•

1 to 32 characters•

Case sensitive•

Colon character :, forward slash /, and spaces are
NOT permitted.

Full name

The user's first and last names.

Password,•

4 to 64 characters

Confirm password•

Case sensitive•

Spaces are permitted.

Telephone number

The user's telephone number

Email address

The user's email address

Enable•Up to 128 characters•

Case sensitive

When selected, the user can log in.

Force password
When selected, a password change request automaticallychange on next login appears the next time the user logs in.

▶ SSH:You need to enter the SSH public key only if public key authentication for SSH is enabled.
1. Open the SSH public key with a text editor.
2. Copy and paste all content in the text editor into the SSH Public Key field.

▶ SNMPv3:
The SNMPv3 access permission is disabled by default.
Field/
setting

Description

EnableSNMPv3

Select this checkbox when intending to permit the SNMPv3 access by
this user.

Note: The SNMPv3 protocol must be enabled for SNMPv3
access.
Security level Click the field to select a preferred security level from the list:

227

Field/setting•

Description
•

None

•

Authentication: Authentication and no privacy.

•

Authentication & Privacy: Authentication protocol SHA-1, privacy
protocol AES-128. Default.

Authentication Password: This section is configurable only when 'Authentication' or 'Authentication& Privacy' is selected.
Field/setting

Description

Same as user
password

Select this checkbox if the authentication password is identicalto the user's password.
To specify a different authentication password, disable thecheckbox.

Password,
Confirm password•

Type the authentication password if the 'Same as User Password'checkbox is deselected.
The password must consist of 8 to 32 ASCII printable characters.

Privacy Password: This section is configurable only when 'Authentication & Privacy' is selected.
Field/setting

Description

Same as authentication Select this checkbox if the privacy password is identical topassword
the authentication password.
To specify a different privacy password, disable the checkbox.
Password,

Type the privacy password if the 'Same as Authentication
Password' checkbox is deselected.

Confirm password•

The password must consist of 8 to 32 ASCII printablecharacters.

Protocol: This section is configurable only when 'Authentication' or 'Authentication & Privacy' isselected.

Field/setting Description
Authentication Click this field to select the desired authentication protocol. Two
protocols are available:

228

•

MD5

•

SHA-1 (default)•

SHA-224•

SHA-256•

SHA-384•

SHA-512Field/setting Description
Privacy

Click this field to select the desired privacy protocol. Two protocols
are available:

•

DES

•

AES-128 (default)•

AES-192•

AES-256•

AES-192 (3DES key extension)•

AES-256 (3DES key extension)▶ Preferences:
This section determines the measurement units displayed in the web interface and CLI for this user. The
user can also change these in the User Management > User Preferences page. SNMP uses the defaults
set in User Management > Default Preferences.
Field

Description

Temperature unit

Preferred units for temperatures -(Fahrenheit).

(Celsius) or

Length unit

Preferred units for length or height -- Meter or Feet.

Pressure unit

Preferred units for pressure -- Pascal or Psi.
•

Pascal = one newton per square meter•

Psi = pounds per square inch

▶ Roles:
Select one or multiple roles to determine the user's permissions. A user can have a maximum of 32
roles. Note: With multiple roles selected, a user has the union of all roles' permissions.
If the built-in roles do not satisfy your needs, add new roles by clicking New Role. This newly-createdrole will be then automatically assigned to the user account currently being created.
Built-in role Description
Admin

Provide full permissions.

229

Built-in role Description
Operator

Provide frequently-used permissions, including:•Acknowledge Alarms•

Change Own Password•

Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration (ifyour model is a PDU)•

Switch Outlet (if your model supports it)•

Switch Outlet Group (if your model supports it)•

Change PMC, PMB, & PMM Configuration (if your model is a branch
circuit monitor)•

View Event Settings•

View Local Event Log

Editing or Deleting Users
To edit or delete users, choose User Management > Users to open the Users page.

In the Enabled column:•: The user is enabled.

•: The user is disabled.

•

Sort the list by clicking the header.

▶ To edit or delete a user account:
1. On the Users page, click the desired user. The Edit User page for that user opens.
• You can rename the user. This action is logged.
• To change the password, type a new password in the Password and Confirm Password fields. If thepassword field is left blank, the password remains unchanged.
• To delete this user, click230, and confirm the operation.

2. Click Save for changes.

▶ To delete multiple user accounts:
1. On the Users page, select users by clicking the checkboxes.
2. Click the Delete icon

then click to confirm.

Note: You cannot delete the original factory-default Administrator account, but you can disable it.

Creating Roles
A role is a combination of permissions. Each user must have at least one role.
The PX-Series PDU provides two built-in roles.
Built-in role Description
Admin

Provide full permissions.

231

Built-in role Description
Operator

Provide frequently-used permissions, including:•Acknowledge Alarms•

Change Own Password•

Change Pdu, Inlet, Outlet & Overcurrent Protector
Configuration•

Switch Outlet (for supported models)•

Switch Outlet Group (for supported models)•View Event Settings•

View Local Event Log

If the two roles do not satisfy your needs, add new roles. Up to 64 roles are supported.

▶ To create a role:
1. Choose User Management > Roles > New icon.

2. Assign a role name.
• 1 to 32 characters long
• Case sensitive• Spaces are permitted
3. Type a description for the role in the Description field.
4. Select the desired privilege(s).
• The 'Administrator Privileges' includes all privileges.
• The 'Unrestricted View Privileges' includes all 'View' privileges.
5. Some privileges have additional selections. These rows contain a blue hyperlink and expand arrow.
Click either to view options.
• For example, in the Switch Actuator and Switch Outlet privileges, you can specify the actuators andoutlets that users can switch on/off.

232

6. Click Save. The role is created and you can assign it to any user.

Editing or Deleting Roles
Roles cannot be renamed, but you can delete them or change their included privileges.
Choose User Management > Roles to open the Roles page, which lists all roles.
The built-in Admin role displays the lock icon

. You cannot delete it or change it.

▶ To edit a role:
1. On the Roles page, click the desired role. The Edit Role page opens.
• You can edit the description or change the privileges.
• To delete this role, click, and confirm the operation.

233

2. Click Save.

▶ To delete any roles:
1. On the Roles page, select the checkboxes for roles you want to delete.
2. Click the Delete icon

then click Delete in the confirmation message.

Setting Your Preferred Measurement Units
You can change the measurement units shown in the user interface according to your own preferences
regardless of the permissions you have.
Measurement unit changes apply to the web interface and CLI. SNMP uses the default measurement
units. See Setting Default Measurement Units (on page 235).
Setting your own preferences does not change the default measurement units.

▶ To set user preferences:
1. Choose User Management > User Preferences.
2. Make changes as needed.
Field
Temperature unit

Length unit

234

Description
Preferred units for temperatures -(Fahrenheit).

(Celsius) or

Preferred units for length or height -- Meter or Feet.

FieldDescription

Pressure unit

Preferred units for pressure -- Pascal or Psi.
•

Pascal = one newton per square meter•

Psi = pounds per square inch

1. Click Save.

Setting Default Measurement Units
User preferences apply to displays in the GUI and CLI for locally authenticated users. Default
preferences apply to the front panel and SNMP, and to remote-authenticated users.

▶ To set up default user preferences:
1. Click User Management > Default Preferences.
2. Make changes as needed.
Field

Description

Temperature unit

Preferred units for temperatures -- Celsius or Fahrenheit.

Length unit

Preferred units for length or height -- Meter or Feet.

Pressure unit

Preferred units for pressure -- Pascal or Psi.
•

Pascal = one newton per square meter•

Psi = pounds per square inch

1. Click Save.

User Interfaces Showing Default Units
Default measurement units will apply to the following user interfaces or data:•

Web interface for "newly-created" local users when they have not configured their own preferredmeasurement units.

•

Web interface for users who are remotely authenticated.

•

The sensor report triggered by the "Send Sensor Report" action.

•

Front panel LCD display.

Device Settings
Click 'Device Settings' in the Menu.

235

Network Settings
Configure wired, wireless, and Internet protocol-related settings on the Network page after connecting
the PX-Series PDU to your network.
You can enable both the wired and wireless networking so that there are multiple IP addresses -- wired
and wireless IP. For example, you can obtain one IPv4 and/or IPv6 address by enabling one Ethernet
interface, and obtain one more IPv4 and/or IPv6 address by enabling/configuring the wireless interface.
This also applies in port forwarding mode so that PX-Series PDU has more than one IPv4 or IPv6
address.
However, in the BRIDGING mode, there is only one IP address for wired networking. Wirelessnetworking is NOT supported in this mode.
Default gateways are configured per interface.
Important: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

▶ After enabling either or both Internet protocols:
After enabling IPv4 and/or IPv6, all but not limited to the following protocols will be compliant with theselected Internet protocol(s):

236

•

LDAP

•

NTP

•

SMTP

•

SSH

•

Telnet•FTP•

SSL/TLS

•

SNMP

•

SysLogNote: PX-Series PDU disables TLS 1.0 and 1.1 by default. It enables only TLS 1.2 and 1.3.

Common Network Settings
Common Network Settings are OPTIONAL, not required. Therefore, leave them unchanged if there areno specific local networking requirements.

Field

Description

Cascadingmode

Leave it to the default "None" unless you are establishing acascading chain.

DNS resolver
preference

Determine which IP address is used when the DNS resolver returns
both IPv4 and IPv6 addresses.

DNS suffixes(optional)•

Setting the Cascading Mode (on page 251)•

IPv4 address: Use the IPv4 addresses.

•

IPv6 address: Use the IPv6 addresses.

Specify a DNS suffix name if needed.

237

FieldDescription

First/Second/Third DNS server

Manually specify static DNS server(s).
•If any static DNS server is specified in these fields, it will
override the DHCP-assigned DNS server.

•

If DHCP (or Automatic) is selected for IPv4/IPv6 settings, andthere are NO static DNS servers specified, DHCP-assigned DNS
servers are used.

You can manually configure or the route information using IPv4 and IPv6 static routes. See Static RouteExamples (on page 248) and Static Route Interface Names (on page 250).

802.1x Security Overview
You can configure IEEE 802.1X authentication separately on each LAN port to give the PX-Series PDU a
secure access on your LAN or WLAN. This authentication protocol will authenticate a user's identity
based on their credentials or certificate, which will be verified by their RADIUS authentication server.
802.1X uses the uploaded certificate from the Certificate Repository to verify the user's identity.
EAP_TLS or EAP_PEAP are two authentication methods used in PX-Series PDU to exchange the secure
information. See Setting Up a TLS Certificate (on page 273) to configure and upload the proper
certificate.

Ethernet (Wired) Interface Settings
On the Network page, click the ETHERNET section if the PX-Series PDU has one port or click ETH1 andETH2 sections respectively to configure each port. By default, both ETH1 and ETH2 interfaces areenabled.

▶ Bridging Cascading mode:
If the device's cascading mode is set to 'Bridging', the BRIDGE section appears. Then you must click the
BRIDGE section for IPv4/IPv6 settings.

238

▶ IPv4 settings:
Field/setting

Description

Enable IPv4

Enable or disable the IPv4 protocol.

IP auto configuration

Select the method to configure IPv4 settings.

Preferred hostname••

DHCP: Auto-configure IPv4 settings via DHCP servers.

•

Static: Manually configure the IPv4 settings.

Enter the hostname you prefer for IPv4 connectivity

DHCP settings: Optionally specify the preferred hostname, which must meet the following
requirements:• Consists of alphanumeric characters and/or hyphens• Cannot begin or end with a hyphen• Cannot contain more than 63 characters• Cannot contain punctuation marks, spaces, and other symbols•

Static settings:• Assign a static IPv4 address, which follows this syntax "IP address/prefix length".
Example: 192.168.84.99/24• Assign a Default Gateway.

▶ IPv6 settings:
Field/setting

Description

Enable IPv6

Enable or disable the IPv6 protocol.

IP auto configuration

Select the method to configure IPv6 settings.
•

Automatic: Auto-configure IPv6 settings via DHCPv6.

•

Static: Manually configure the IPv6 settings.

239

Field/setting

Description

Preferred hostname•Enter the hostname you prefer for IPv6 connectivity•

Automatic settings: Optionally specify the preferred hostname, which must meet the above
requirements.

•

Static settings:• Assign a static IPv6 address, which follows this syntax "IP address/prefix length".
Example: fd07:2fa:6cff:1111::0/128• Assign a Default Gateway.

▶ Enable Interface:
Make sure the Ethernet interface is enabled, or all networking through this interface fails. This setting isavailable in the ETH1/ETH2 or ETHERNET section, but not available in the BRIDGE section.

▶ Other Ethernet settings:
Field

Description

Speed

Select a LAN speed.

Duplex240•

Auto: System determines the optimum LAN speed
through auto-negotiation.

•

10 MBit/s: Speed is always 10 Mbps.

•

100 MBit/s: Speed is always 100 Mbps.

•

1 GBit/s: Speed is always 1 Gbps (1000 Mbps).

Select a duplex mode.

•

Auto: Selects the optimum transmission mode throughauto-negotiation.

•

Full: Data is transmitted in both directions
simultaneously.

•

Half: Data is transmitted in one direction at a time.

Current stateShow the LAN's current status, including the current speed andduplex mode.

MTU•

Set the MTU from 1280 to 1500.

FieldDescription

Enable LLDP•

Default is enabled.

When LLDP is enabled, device discovery is possible with
LLDP management software that is often present in network
switches.
Authentication

Outer
authentication

Select an authentication method.
•

No Authentication: No authentication data is required.

•

EAP: PX-Series PDU supports 802.1X (EAP) Network
Authentication. You must have a client-side certificate tocommunicate with the authentication server. Enter required
authentication data in the fields that appear.

This field appears when 'EAP' is selected.
There are two authentication methods for EAP.

Inner
authentication•

PEAP: A TLS tunnel is established, and an inner authentication
method can be specified for this tunnel.

•

TLS: Authentication between the client and authentication
server is performed using TLS certificates.

This field appears when both 'EAP' and 'PEAP' are selected.
•

MS‑CHAPv2: Authentication based on the given password
using MS‑CHAPv2 protocol.

•

TLS: Authentication between the client and authentication
server is performed using TLS certificates.

IdentityThis field appears when 'EAP' is selected.
Type your user name.
Password

This field appears only when 'EAP', 'PEAP' and 'MS-CHAPv2'
are all selected.
Type your password.

241

FieldDescription

Client certificate,
Client private key, A client certificate is required for two scenarios: (1) EAP+TLS,
Client private key (2) EAP+PEAP+TLS .
password

PEM encoded X.509 certificate and PEM encoded private key are
required for certification-based authentication methods. Private
key password is optional.
•

Private keys in PKCS#1 and PKCS#8 formats are supported.

•

Client Private Key Password should be entered only when yourprivate key is encrypted with a password.

•

To view the uploaded certificate, click Show Client Certificate.

•

To remove the uploaded certificate and private key, click 'Clear
Key/Certificate selection'.

CA certificate

This field appears when 'EAP' is selected.
CA certificate is required when "Enable verification of TLS
certificate chain" is selected by default; and strongly recommended
RADIUSauthentication
server name

This field appears when 'EAP' is selected.
Type the name of the RADIUS server if it is present in the TLS
certificate.
•

The name must match the fully qualified domain name (FQDN)of the host shown in the certificate

Do not leave this field blank as it reduces security.

Note: Auto-negotiation is disabled after setting both the speed and duplex settings to NON-Auto values,
which may result in a duplex mismatch.
•

Available settings for the CA Certificate:

If the required certificate file is a chain of certificates, and you are not sure about the requirements of acertificate chain, see TLS Certificate Chain.
Field/setting

Description

EnableSelect this checkbox to verify the certificate of the EAP
verification of TLS authentication server. Then you must upload the certificate of theissuing CA in the next field.
certificate chain242

Field/setting

Description

Browse button

Click this button to import the certificate of the issuing CA. Then
you can:•Click Show to view the certificate's content.

•

Click Remove to delete the installed certificate if it isinappropriate.

Allow expired and •not yet valid
certificates•

Select this checkbox to make the authentication succeed
regardless of the certificate's validity period.
After deselecting this checkbox, the authentication fails
whenever any certificate in the selected certificate chain is
outdated or not valid yet.

Allow connection If powered off for a long time, the system time may be incorrect.
if system clock is When this checkbox is deselected, and if the system time isincorrect
incorrect, the installed TLS certificate is considered not valid yet
and will cause the network connection to fail.

When this checkbox is selected, it will make the network
connection successful when the system time is earlier than
the firmware build before synchronizing with any NTP
server.

Wireless Network Settings
Wireless network is not supported for Bridging mode or for Expansion units in port forwarding mode.
Wireless interface is disabled by default. Enable it to use wireless networking.
On the Network page, click the WIRELESS section to configure wireless and IPv4/IPv6 settings.

▶ Interface Settings:
Field/setting

Description

Enable interface

Enable or disable the wireless interface.
When disabled, the wireless networking fails.

Hardware state

Check this field to ensure that a wireless USB LAN adapter isdetected. If not, verify that the USB LAN adapter is firmly
connected or that it is supported.

SSID

Type the name of the wireless access point (AP).

Force AP BSSID

If the BSSID is available, select this checkbox.

BSSID

Type the MAC address of an access point.

243

Field/setting

Description

MTU

Set the Maximum Transmission Unit from 1280 to 1500.

Enable HighThroughput(802.11n)

Enable or disable 802.11n protocol.

Authentication

Select an authentication method.
•

No Authentication: No authentication data is required.

•

PSK: A Pre-Shared Key is required.

•

EAP: PX-Series PDU supports 802.1X (EAP) Network
Authentication. Enter required authentication data in thefields that appear.

Pre-Shared Key

This field appears only when PSK is selected.
Type the PSK string.
Outerauthentication

This field appears when 'EAP' is selected.
There are two authentication methods for EAP.

Inner
authentication•

PEAP: A TLS tunnel is established, and an innerauthentication method can be specified for this tunnel.

•

TLS: Authentication between the client and authentication
server is performed using TLS certificates.

This field appears when both 'EAP' and 'PEAP' are selected.
•

MS‑CHAPv2: Authentication based on the given password
using MS‑CHAPv2 protocol.

•

TLS: Authentication between the client and authentication
server is performed using TLS certificates.

IdentityThis field appears when 'EAP' is selected.
Type your user name.
Password

This field appears only when 'EAP', 'PEAP' and 'MSCHAPv2' are all selected.
Type your password.

244

Field/setting

Description

Client certificate,
Client private key,
Client private key
password

This field appears when 'EAP', 'PEAP' and 'TLS' are all
selected.
PEM encoded X.509 certificate and PEM encoded private key are
required for certification-based authentication methods. Private
key password is optional.
•

Private keys of PKCS#1 and PKCS#8 formats are supported.

•

Client Private Key Password should be entered only whenyour private key is encrypted with a password.

•

To view the uploaded certificate, click Show Client Certificate.

•

To remove the uploaded certificate and private key, click'Clear Key/Certificate selection'.

CA certificate

This field appears when 'EAP' is selected.
A third-party CA certificate may or may not be needed. If needed,follow the steps below.
RADIUSauthentication
server name

This field appears when 'EAP' is selected.
Type the name of the RADIUS server if it is present in the TLS
certificate.
••

The name must match the fully qualified domain name
(FQDN) of the host shown in the certificate.

Available settings for the CA Certificate:

If the required certificate file is a chain of certificates, and you are not sure about the requirements of acertificate chain, see TLS Certificate Chain.
Field/setting

Description

EnableSelect this checkbox for the PX-Series PDU to verify the validity ofverification of TLS the TLS certificate that will be installed.
certificate chain• For example, the certificate's validity period against thesystem time is checked.
Browse button

Click Browse to import a certificate file. Then you can:•Click Show to view the certificate's content.

•

Click Remove to delete the installed certificate if it isinappropriate.

245

Field/setting

Description

Allow expired and •not yet valid
certificates•

Allow connection
if system clock isincorrect

Select this checkbox to make the authentication succeed
regardless of the certificate's validity period.
After deselecting this checkbox, the authentication fails
whenever any certificate in the selected certificate chain is
outdated or not valid yet.

When this checkbox is deselected, and if the system time isincorrect, the installed TLS certificate is considered not valid yet
and will cause the wireless network connection to fail.
When this checkbox is selected, it will make the wireless network
connection successful when the PX-Series PDU system time isearlier than the firmware build before synchronizing with any NTP
server.

▶ IPv4 settings:
Field/setting

Description

Enable IPv4

Enable or disable the IPv4 protocol.

IP auto configuration

Select the method to configure IPv4 settings.

Preferred hostname••

DHCP: Auto-configure IPv4 settings via DHCP servers.

•

Static: Manually configure the IPv4 settings.

Enter the hostname you prefer for IPv4 connectivity

DHCP settings: Optionally specify the preferred hostname, which must meet the following
requirements:• Consists of alphanumeric characters and/or hyphens• Cannot begin or end with a hyphen• Cannot contain more than 63 characters• Cannot contain punctuation marks, spaces, and other symbols•

Static settings: Assign a static IPv4 address, which follows this syntax "IP address/prefix length".
Example: 192.168.84.99/24▶ IPv6 settings:

246

Field/setting

Description

Enable IPv6

Enable or disable the IPv6 protocol.

IP auto configuration

Select the method to configure IPv6 settings.
•

Automatic: Auto-configure IPv6 settings via DHCPv6.

•

Static: Manually configure the IPv6 settings.

Field/setting

Description

Preferred hostname•Enter the hostname you prefer for IPv6 connectivity•

Automatic settings: Optionally specify the preferred hostname, which must meet the above
requirements.

•

Static settings: Assign a static IPv6 address, which follows this syntax "IP address/prefix length".
Example: fd07:2fa:6cff:1111::0/128▶ (Optional) To view the wireless LAN diagnostic log:•

Click Show WLAN Diagnostic Log. See Diagnostic Log for Network Connections (on page 247)

Diagnostic Log for Network Connections
A diagnostic log for inspecting connection errors that occurred during the EAP authentication or thewireless network connection is provided. The information is useful for technical support.
The diagnostic log shows data only after connection errors are detected.
Each entry in the log consists of:•

ID number•

Date and time•

Description247

▶ To view the log:
1. Access the diagnostic log with either method below.
• Choose Device Settings > Network > ETH1/ETH2 > Show EAP Authentication Log.
• Choose Device Settings > Network > WIRELESS > Show WLAN Diagnostic Log.
2. The log is refreshed automatically at a regular interval of five seconds.
• To avoid any new events' interruption during data browsing, you can suspend the automatic update
by clicking Pause.
• To restore automatic update, click Resume. Those new events that have not been listed yet due tosuspension will be displayed in the log now.

▶ To clear the diagnostic log:
1. On the top-right corner of the log, click>
2. Click Clear Log on the confirmation message.

.

Static Route Examples
This section describes two static route examples: IPv4 and IPv6. Both examples assume that two
network interface controllers (NIC) have been installed in one network server, leading to two available
subnets, and IP forwarding has been enabled. All of the NICs and PX-Series PDU devices in the examples
use static IP addresses.
Most of local multiple networks are not directly reachable and require the use of a gateway. Therefore,
we will select Gateway in the following examples. If your local multiple networks are directly reachable,
you should select Interface rather than Gateway.
Note: If Interface is selected, you should select an interface name instead of entering an IP address.

▶ IPv4 example:

248•

Your PX-Series PDU: 192.168.100.64•

Two NICs: 192.168.200.75 and 192.168.100.88•

Two networks: 192.168.200.0 and 192.168.100.0•

Prefix length: 24

In this example, NIC-2 (192.168.100.88) is the next hop router for your PX-Series PDU to communicate
with any device in the other subnet 192.168.200.0.
In the IPv4 "Static Routes" section, you should enter the data as shown below. Note that the address inthe first field must be of the Classless Inter-Domain Routing (CIDR) notation.

Tip: If you have configured multiple static routes, you can click on any route and then make changes,

use

or

to re-sort the priority, or click

to delete it.

▶ IPv6 example:•

Your PX-Series PDU: fd07:2fa:6cff:2405::30•

Two NICs: fd07:2fa:6cff:1111::50 and fd07:2fa:6cff:2405::80•

Two networks: fd07:2fa:6cff:1111::0 and fd07:2fa:6cff:2405::0•

Prefix length: 64249

In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your PX-Series PDU tocommunicate with any device in the other subnet fd07:2fa:6cff:1111::0.
In the IPv6 "Static Routes" section, you should enter the data as shown below. Note that the address inthe first field must be of the Classless Inter-Domain Routing (CIDR) notation.

Tip: If you have configured multiple static routes, use the arrow buttons to sort the priority, or click
to delete it.

Static Route Interface Names
When your local multiple networks are "directly reachable", you should select Interface for static
routes. Then choose the interface where another network is connected.

250▶ Interface list:
Interfacename

Description

BRIDGE

When another wired network is connected to the Ethernet port ofyour PX-Series PDU, and your PX-Series PDU has been set to thebridging mode, select this interface name instead of the Ethernet
interface.

ETH1

When another wired network is connected to the ETH1 port of yourPX-Series PDU, select this interface name.

ETH2

When another wired network is connected to the ETH2 port of yourPX-Series PDU, select this interface name.

WIRELESS

When another wireless network is connected to your PX-Series PDU,
select this interface name.

Setting the Cascading ModeSee the Cascading Solution Guide for full details on network setup, physical setup, and supported
configurations for all cascades across products. The sections documented here are a brief overview.
The cascading mode configured on the primary device determines the Ethernet sharing method, which
is either network bridging or port forwarding. The cascading mode of all devices in the chain must be
the same.
You must have the Change Network Settings permission to configure the cascading mode.
Note: Port Forwarding mode does not support APIPA.

▶ To configure the cascading mode:
1. Choose Device Settings > Network > Common Network Settings section.
2. Select the preferred mode in the Cascading Mode field.
Mode

DescriptionNone

No cascading mode is enabled. This is the default.

Bridging

Each device in the cascading chain is accessed with a different
IP address.

Port Forwarding Each device in the cascading chain is accessed with the same
IP address(es) but with a different port number assigned.

Tip: If selecting Port Forwarding, the Device Information page will show a list of port numbers for all
cascaded devices. Choose Maintenance > Device Information > Port Forwarding.
3. For the Port Forwarding mode, you must also configure the following settings.

251

Note that if either setting below is incorrectly configured, a networking issue occurs.
Field

Description

Port forwarding role

Primary or Expansion.

(available on all cascaded
devices)This is to determine which device is the primary andwhich ones are expansion devices.

Downstream interface

USB or ETH1/ETH2.

(available on the primarydevice only)This is to determine which port on the primarydevice is connected to Expansion 1.
If ETH1 or ETH2 is selected as the downstream
interface, make sure the selected Ethernet interface
is enabled.

4. (Optional) Configure the network settings by clicking the BRIDGE, ETH1/ETH2, or WIRELESS section
on the same page.
• In the Bridging mode, each cascaded device can have different network settings. You may need toconfigure each device's network settings in the BRIDGE section.
• In the Port Forwarding mode, all cascaded devices share the primary device's network settings. You
only need to configure the primary device's network settings in the ETH1/ETH2 and/or WIRELESS
section.
Tip: You can enable/configure multiple network interfaces in the Port Forwarding mode so that thecascading chain has multiple IP addresses.
5. Click Save.

▶ Recommendations for cascade loops:
You can connect both the first and the last PDU to your network (cascade loop) under the following
conditions:•

Bridging mode only.

•

The remaining network MUST use R/STP to avoid network loops.

•

AND
Both the first and the last PDUs MUST either attach to the same switch or, if they are attached totwo separate switches, you must configure both ports of these switches so that the STP costs arehigh. This prevents the STP protocol from sending unrelated traffic through the PDU cascade, which
can cause bottlenecks that lead to connectivity issues in the whole network.

Cascading Modes Overview
The cascading mode is a network configuration setting that determines how each device in the chain isaccessed.
There are two cascading modes: Bridging and Port Forwarding.
In the following illustration, it is assumed that users enable the DHCP networking for the cascading
chain comprising four devices. In the diagrams, "P" is the primary device and "E" is an expansion device.

252

▶ "Bridging" mode:

In this mode, the DHCP server communicates with every cascaded device
respectively and assigns four different IP addresses. Each device has its own IP
address.
The way to remotely access each cascaded device is completely the same asaccessing a standalone device in the network.

253

▶ "Port Forwarding" mode:

In this mode, the DHCP server communicates with the primary device alone andassigns one IP address to the primary device. All expansion devices share the same
IP address as the primary device.
You must specify a 5XXXX port number (where X is a number) when remotely
accessing any expansion device with the shared IP address. See Port Number Syntax(on page 254), Port Number Syntax (on page 659).

▶ Comparison between cascading modes:•

The Bridging mode supports the wired network only, while the Port Forwarding mode supports both
wired and wireless networks.

•

Both cascading modes support a maximum of 32 devices in a chain.

•

Both cascading modes support both DHCP and static IP addressing.

•In the Bridging mode, each cascaded device has a unique IP address.

•

In the Port Forwarding mode, all cascaded devices share the same IP address(es) as theprimary device.
In the Bridging mode, each cascaded device has only one IP address.
In the Port Forwarding mode, each cascaded device can have multiple IP addresses as longas the primary device has multiple network interfaces enabled/configured properly.
For example:• When the primary device has two Ethernet ports (ETH1/ETH2), you can enable ETH1, ETH2 andWIRELESS interfaces so that the Port-Forwarding chain has two wired IP addresses and one
wireless IP address.

Port Number Syntax
In the Port Forwarding mode, all devices in the cascading chain share the same IP address(es). To accessany cascaded device, you must assign an appropriate port number to it.
•

Primary device: The port number is either 5NNXX or the standard TCP/UDP port.

•

Expansion device: The port number is 5NNXX.

▶ 5NNXX port number syntax:•

254

NN is a two-digit number representing the network protocol as shown below:

•Protocols

NN

HTTPS

00

HTTP

01

SSH

02

TELNET

03

SNMP

05

MODBUS

06

XX is a two-digit number representing the device position as shown below.
PositionXX

PositionXX

Primary device

00

Expansion 8

08

Expansion 1

01

Expansion 9

09

Expansion 2

02

Expansion 10

10

Expansion 3

03

Expansion 11

11

Expansion 4

04

Expansion 12

12

Expansion 5

05

Expansion 13

13

Expansion 6

06

Expansion 14

14

Expansion 7

07

Expansion 15

15

For example, to access the Expansion 4 device via Modbus/TCP, the port number is 50604.
Tip: The full list of each cascaded device's port numbers can be retrieved from the web interface.
Choose Maintenance > Device Information > Port Forwarding.

▶ Standard TCP/UDP ports:
The primary device can be also accessed through standard TCP/UDP ports as listed in the following
table.
Protocols

Port Numbers

HTTPS

443

HTTP

80

SSH

22

TELNET

23

SNMP

161

255

Protocols

Port Numbers

MODBUS

502

In the Port Forwarding mode, the cascaded device does NOT allow you to modify the standard TCP/UDP
port configuration, including HTTP, HTTPS, SSH, Telnet and Modbus/TCP.

Port Forwarding Examples
In this example, Port Forwarding mode is applied to a cascading chain comprising three devices. The IP
address is 192.168.84.77.

▶ Primary device:
Position code for the primary device is '00' so each port number is 5NN00 as listed below.
Protocols

Port numbers

HTTPS

50000

HTTP

50100

SSH

50200

TELNET

50300

SNMP

50500

MODBUS

50600

Examples using "5NN00" ports:•••

To access the primary device via HTTPS, the IP address is:https://192.168.84.77:50000/
To access the primary device via HTTP, the IP address is:
http://192.168.84.77:50100/
To access the primary device via SSH, the command is:ssh -p 50200 192.168.84.77

Examples using standard TCP/UDP ports:
•
•
•

256

To access the primary device via HTTPS, the IP address is:https://192.168.84.77:443/
To access the primary device via HTTP, the IP address is:
http://192.168.84.77:80/
To access the primary device via SSH, the command is:ssh -p 22 192.168.84.77

▶ Expansion 1 device:
Position code for Expansion 1 is '01' so each port number is 5NN01 as shown below.
Protocols

Port numbers

HTTPS

50001

HTTP

50101

SSH

50201

TELNET

50301

SNMP

50501

MODBUS

50601

Examples:•••To access Expansion 1 via HTTPS, the IP address is:https://192.168.84.77:50001/
To access Expansion 1 via HTTP, the IP address is:
http://192.168.84.77:50101/
To access Expansion 1 via SSH, the command is:ssh -p 50201 192.168.84.77▶ Expansion 2 device:
Position code for Expansion 2 is '02' so each port number is 5NN02 as shown below.
Protocols

Port numbers

HTTPS

50002

HTTP

50102

SSH

50202

TELNET

50302

SNMP

50502

MODBUS

50602

Examples:•To access Expansion 2 via HTTPS, the IP address is:•https://192.168.84.77:50002/
To access Expansion 2 via HTTP, the IP address is:

257

•

http://192.168.84.77:50102/
To access Expansion 2 via SSH, the command is:ssh -p 50202 192.168.84.77

Adding, Removing or Swapping Cascaded Devices
Change a device's cascading mode first before adding that device to a cascading chain, or before
disconnecting that device from the chain.
If you only want to change the cascading mode of an existing chain, or swap the primary and expansion
device, always start from the expansion device.
Note: If the following procedures are not followed, a networking issue occurs. When a networking issue
occurs, check the cascading connection and/or software settings of all devices in the chain.

▶ To add a device to an existing chain:
1. Connect the device you will cascade to the LAN and find its IP address, or connect it to a computer.
2. Log in to this device and set its cascading mode to be the same as the existing chain's cascadingmode.
3. (Optional) If this device will function as an expansion device, disconnect it from the LAN after
configuring the cascading mode.
4. Connect this device to the chain, using either a USB or Ethernet cable.

▶ To remove a device from the chain:
1. Log in to the desired cascaded device, and change its cascading mode to None.
Exception: If you are going to connect the removed device to another cascading chain, set its cascading
mode to be the same as the mode of another chain.
2. Now disconnect it from the cascading chain.

▶ To swap the primary and expansion device:258•

In the Bridging mode, you can swap the primary and expansion devices by disconnecting ALL
cascading cables from them, and then reconnecting cascading cables. No changes to softwaresettings are required.

•

In the Port Forwarding mode, you must follow the procedure below:

a. Access the expansion device that will replace the primary device, and set its role to'Primary', and correctly set the downstream interface.
b. Access the primary device, set its role to 'Expansion'.
c. Swap the primary and expansion device now.
▪ You must disconnect the LAN cable and ALL cascading cables connected to the two devices
first before swapping them, and then reconnecting all cables.

▶ To change the cascading mode applied to a chain:
1. Access the last expansion device, and change its cascading mode.
• If the new cascading mode is 'Port Forwarding', you must also set its role to 'Expansion'.
2. Access the second to last, third to last and so on until the first expansion device to change theircascading modes one by one.
3. Access the primary device, and change its cascading mode.
• If the new cascading mode is 'Port Forwarding', you must also set its role to 'Primary', and correctly
select the downstream interface.
The following diagram indicates the correct sequence. 'N' is the final one.
•

P = Primary device•

E = Expansion device

Configuring Network Services
PX-Series PDU supports the following network communication services.

259

HTTPS and HTTP enable the access to the web interface. Telnet and SSH enable the access to thecommand line interface.
By default, SSH is enabled, Telnet is disabled, and all TCP ports for supported services are set tostandard ports. You can change default settings if necessary.
Important: PX-Series PDU uses TLS rather than SSL.

Changing HTTP(S) Settings
HTTPS uses Transport Layer Security (TLS) technology to encrypt all traffic to and from the PX-Series
PDU so it is a more secure protocol than HTTP. PX-Series PDU disables TLS 1.0 and 1.1 by default. It
enables only TLS 1.2 and 1.3.
By default, any access to the PX-Series PDU via HTTP is automatically redirected to HTTPS. You candisable this redirection if needed.

▶ HTTP and HTTPS settings:
1. Choose Device Settings > Network Services > HTTP.
2. HTTP settings:• Enable or disable HTTP access.
• Default port is 80. You can enter a custom port.
• Enforce use of HTTPS: Select the checkbox to Redirect HTTP connections to HTTPS.
3. HTTPS settings:

260

• Enable or disable HTTPS access.
• Enable HSTS: Default is enabled.
• Default port is 443. You can enter a custom port.
Warning: Different network services cannot share the same TCP port.

▶ Special note for AES ciphers:
The PX-Series PDU device's TLS-based protocols support AES 128- and 256-bit ciphers. The exact cipher
to use is negotiated between PX-Series PDU and the client (such as a web browser), which is impacted by
the cipher priority of PX-Series PDU and the client's cipher availability/settings.
Tip: To force PX-Series PDU to use a specific AES cipher, refer to your client's user documentation for
information on configuring AES settings. For example, you can enable a cipher and disable the other inthe browser via the "about:config" command.

Regaining Access with HSTS and Expired Certificate
HSTS is enabled by default in the Device Settings > Security > HTTP settings. When HSTS is enabled, you
can only access PX-Series PDU via web browser when a valid, unexpired certificate is installed. HSTS
removes the ability for users to click through warnings about invalid certificates.
If access is lost due to HSTS restrictions, there are 2 methods to regain access.

▶ Replace the certificate locally on the PX-Series PDU:
1. Save the new key and certificate to a USB drive.
2. Use one of the USB configuration methods to upload the new certificate to the device.

▶ Replace the certificate over an insecure connection:
1. Disable the client web browser HSTS security, and then access the PX-Series PDU "insecurely."
2. Replace the certificate in Device Settings > Security > TLS Certificates, then enable the HSTS security.

Configuring SNMP Settings
You can enable or disable SNMP communication between an SNMP manager and the PX-Series PDU.
Enabling SNMP communication allows the manager to retrieve and even control the power status ofeach outlet.
You may also need to configure the SNMP destination(s) if the built-in "System SNMP Notification Rule"is enabled and the SNMP destination has not been set yet. See Event Rules and Actions (on page 291).

▶ To configure SNMP communication:
1. Choose Device Settings > Network Services > SNMP.

261

2. Enable or disable "SNMP v1 / v2c" and/or "SNMP v3" by clicking the corresponding checkbox.
• The SNMP v1/v2c read-only access is enabled by default. The default 'Read community string' is"public."• To enable read-write access, type the 'Write community string.' Usually the string is "private."
3. Enter the MIB-II system group information, if applicable.
• sysContact - the contact person in charge of the system• sysName - the name assigned to the system• sysLocation - the location of the system
4. To configure SNMP notifications:a. Select the 'Enable SNMP notifications' checkbox.
b. Select a notification type -- SNMPv2c trap, SNMPv2c inform, SNMPv3 trap, and SNMPv3 inform.
c. Specify the SNMP notification destinations and enter necessary information. For details, refer to:▪ SNMPv2c Notifications▪ SNMPv3 Notifications

262

Note: Any changes made to the 'SNMP Notifications' section on the SNMP page will update
the settings of the System SNMP Notification Action, and vice versa. To add more than three
SNMP destinations, you can create new SNMP notification actions.
5. You must download the SNMP MIB for your PX-Series PDU to use with your SNMP manager.
a. Click the Download MIBs title bar to show the download links.

b. Click the PDU2-MIB download link. See Downloading SNMP MIB.
6. Click Save.

Configuring SMTP Settings
The PX-Series PDU can be configured to send alerts or event messages to a specific administrator byemail. To send emails, you have to configure the SMTP settings and enter an IP address for your SMTP
server and a sender's email address.
If any email messages fail to be sent successfully, the failure event and reason are available in the eventlog.

▶ To set SMTP server settings:
1. Choose Device Settings > Network Services > SMTP Server.
2. Enter the information needed.
Field

Description

IP address/host name

Type the name or IP address of the mail server.

Port

Type the port number.
•

Default is 25

Sender email address

Type an email address for the sender.

Number of sending
retries

Type the number of email retries.

Time between sending
retries

Type the interval between email retries in minutes.

Server requires
authentication

Select this checkbox if your SMTP server requires password
authentication.

••

Default is 2 retries

Default is 2 minutes.

263

FieldDescription

User name,

Type a user name and password for authentication after
selecting the above checkbox.

Password

Enable SMTP over TLS(StartTLS)••

The length of user name and password ranges between
4 and 64. Case sensitive.

•

Spaces are not allowed for the user name, but allowed
for the password.

If your SMTP server supports the Transport Layer Security(TLS), select this checkbox.

Settings for the CA Certificate:
If the required certificate file is a chain of certificates, and you are not sure about therequirements of a certificate chain, see TLS Certificate Chain.

Field/setting

Description
Click this button to import a certificate file. Then you can:•Click Show to view the certificate's content.

•

Click Remove to delete the installed certificate if it isinappropriate.

Allow expired and not yet •valid certificates

Select this checkbox to make the authentication
succeed regardless of the certificate's validity period.

•

After deselecting this checkbox, the authentication
fails whenever any certificate in the selected certificate
chain is outdated or not valid yet.

1. Now that you have set the SMTP settings, you can test it to ensure it works properly.
a. Type the recipient's email address in the 'Recipient email addresses' field. Use a comma toseparate multiple email addresses.
b. Click Send Test Email.
c. Check if the recipient(s) receives the email successfully.
2. Click Save.

▶ Special note for AES ciphers:
The PX-Series PDU device's TLS-based protocols support AES 128- and 256-bit ciphers. The exact cipher
to use is negotiated between PX-Series PDU and the client (such as a web browser), which is impacted by
the cipher priority of PX-Series PDU and the client's cipher availability/settings.
Tip: To force PX-Series PDU to use a specific AES cipher, refer to your client's user documentation for
information on configuring AES settings.

Changing SSH Settings
You can enable or disable the SSH access to the command line interface, change the TCP port, or set a
password or public key for login over the SSH connection.

264

▶ To change SSH settings:
1.
2.
3.
4.

Choose Device Settings > Network Services > SSH.
To enable or disable the SSH access, select or deselect the checkbox.
To use a different port, type a port number.
Select one of the authentication methods.
• Password authentication only: Enables the password-based login only.
• Public key authentication only: Enables the public key-based login only. You must enter a valid SSH
public key for each user profile to log in over the SSH connection.

• Password and public key authentication: Enables both the password- and public key-based login.
This is the default.
5. Click Save.

Changing Telnet Settings
You can enable or disable the Telnet access to the command line interface, or change the TCP port.

▶ To change Telnet settings:
1.
2.
3.
4.

Choose Device Settings > Network Services > Telnet.
To enable the Telnet access, select the checkbox.
To use a different port, type a new port number.
Click Save.

Changing Modbus Settings
The PX-Series PDU supports both the Modbus/TCP and Modbus Gateway features. Enable either orboth Modbus features according to your needs.

▶ Modbus/TCP Access:You can enable or disable the Modbus/TCP access to PX-Series PDU, set it to the read-only mode, orchange the TCP port.
1.
2.
3.
4.

Choose Device Settings > Network Services > Modbus.
To enable the Modbus/TCP access, select the "Enable Modbus/TCP access" checkbox.
To use a different port, type a new port number.
To enable the Modbus read-only mode, select the checkbox of the "Enable read-only mode" field. To
enable the read-write mode, deselect it.

265▶ Modbus Gateway:
If connecting the Modbus RTU devices to PX-Series PDU and enabling the Modbus Gateway feature, theModbus TCP clients on your network will be able to communicate with those Modbus RTU devices
attached to PX-Series PDU.
1. To allow the Modbus TCP clients on the network to communicate with the Modbus RTU devices
connected to the PX-Series PDU, select the 'Enable Modbus gateway' checkbox.

2. Now configure the fields shown.
Field

Description

TCP port

Use the default port 503, or assign a different port. Valid range is 1 to 65535.

Note: Port 502 is the default Modbus/TCP port for PX-Series PDU, so
you cannot use that port for the Modbus Gateway.
Parity,Use the default values, or update if the Modbus RTU devices are usingLine speed different communication parameters.
Default
address

If the Modbus TCP client does not support Modbus RTU unit identifier
addressing, enter a Default Address.
If you must provide a unit identifier address:•

Only one Modbus RTU device is supported.

•

The unit identifier address you provide is applied to the Modbus RTU
device connected to PX-Series PDU.
Note that each Modbus RTU device's unit identifier address must be
unique.

Warning: If the connected Modbus RTU device's address does notmatch the address entered in this field, communications between the
Modbus TCP clients and Modbus RTU device fail.

266

Enabling Redfish Services
You can enable or disable the Redfish services to manage the device through the Redfish API. By default,
this service is enabled.
Enabling Redfish services allows you to retrieve the following details.
•

configuration details, such as thresholds, names, etc.

•

metric readings•

event polling

It also allows you to do the following actions•

power actions•

unit control, such as restart

Note: Go to the online Support page for your product to find full documentation of the Redfish API.

▶ To enable or disable Redfish:
Choose Device Settings > Network Services > Redfish.

Enabling Service Advertising
The PX-Series PDU advertises all enabled services that are reachable using the IP network. This featureuses DNS-SD (Domain Name System-Service Discovery) and MDNS (Multicast DNS). The advertised
services are discovered by clients that have implemented DNS-SD and MDNS.
The advertised services include the following:
•

HTTP

•

HTTPS

•

Telnet•

SSH•

Modbus•

JSON-RPC•

SNMP

By default, this feature is enabled.

267

Enabling this feature also enables Link-Local Multicast Name Resolution (LLMNR) and/or MDNS, which
are required for resolving APIPA host names. See APIPA and Link-Local Addressing.
The service advertisement feature supports both IPv4 and IPv6 protocols.
If you have set a preferred host name for IPv4 and/or IPv6, that host name can be used as the zeroconfiguration .local host name, that is, <preferred_host_name>.local, where <preferred_host_name> isthe preferred host name you have specified for PX-Series PDU. The IPv4 host name is the first priority. If
an IPv4 host name is not available, then use the IPv6 host name.

▶ To enable or disable service advertising:
1. Choose Device Settings > Network Services > Service Advertising.
2. To enable the service advertising, select either or both checkboxes.
• To advertise via MDNS, select the Multicast DNS checkbox.
• To advertise via LLMNR, select the Link-Local Multicast Name Resolution checkbox.
3. Click Save.

Configuring Security Settings
The PX-Series PDU provides tools to control access. You can enable the internal firewall, create firewall
rules, and set login limitations. In addition, you can create and install the certificate or set up external
authentication servers for access control. This product supports SHA‑2 TLS certificates.

268

Creating IP Access Control Rules
IP access control rules (firewall rules) determine whether to accept or discard traffic to/from the PXSeries PDU, based on the IP address of the host sending or receiving the traffic. When creating rules,
keep these principles in mind:•

Rule order is important.

•

When traffic reaches or is sent from the PX-Series PDU, the rules are executed in numericalorder. Only the first rule that matches the IP address determines whether the traffic is
accepted or discarded. Any subsequent rules matching the IP address are ignored.
Prefix length is required.
When typing the IP address, you must specify it in the CIDR notation. That is, BOTH theaddress and the prefix length are included. For example, to specify a single address withthe 24-bit prefix length, use this format:

x.x.x.x/24/24 = the prefix length.
Note: Valid IPv4 addresses range from 0.0.0.0 through 255.255.255.255.

▶ To configure IPv4 or IPv6 access control rules:
1. Choose Device Settings > Security > IP Access Control.
2. Select the 'Enable IPv4 access control' or "Enable IPv6 access control" checkboxes to enable theaccess control rules.
3. For either type, determine the default policy.
• Accept: Accepts traffic from all IPv4 OR IPv6 addresses.
• Drop: Discards traffic from all IPv4 OR IPv6 addresses, without sending any failure notification to
the source host.
• Reject: Discards traffic from all IPv4 OR IPv6 addresses, and an ICMP message is sent to the source
host for failure notification.
4. Go to the Inbound Rules section or the Outbound Rules section according to your needs.
• Inbound rules control the data sent to the PX-Series PDU.
• Outbound rules control the data sent from the PX-Series PDU.
5. Create rules.
• Click Append to add a row, then add the IP address and subnet mask. Select Policy. For each rule,
the policy affects only the specified IP address.
• Click Insert Above to add a rule above another rule.
• The system automatically numbers the rules.
• Use the arrow buttons to sort the priority order.
6. Click Save. The rules are applied. Make sure to click Save in each section if changes are made.

269

Editing or Deleting IP Access Control Rules
When an existing IP access control rule requires updates of IP address range and/or policy, modify themaccordingly. Or you can delete any unnecessary rules.

▶ To modify or delete a rule:
1. Choose Device Settings > Security > IP Access Control.
2. Go to the IPv4 or IPv6 section.
3. Select the desired rule in the list.
• Ensure the IPv4 or IPv6 checkbox has been selected, or you may not edit or delete any rule.
4. Perform the desired action.

270

• Make changes to the selected rule, and then click Save.

• Click

to remove it.

• To re-sort its order, click
5. Click Save.

or.

• IPv4 rules: Make sure you click the Save button in the IPv4 section, or the changes made to IPv4
rules are not saved.
• IPv6 rules: Make sure you click the Save button in the IPv6 section, or the changes made to IPv6
rules are not saved.

Creating Role Based Access Control Rules
Role-based access control rules are similar to IP access control rules, except that they are applied tomembers of a specific role. This enables you to grant system permissions to a specific role, based on
their IP addresses.
Same as IP access control rules, the order of role-based access control rules is important, since the rules
are executed in numerical order.

▶ To create IPv4 role-based access control rules:
1. Choose Device Settings > Security > Role Based Access Control.
2. Select the 'Enable role based access control for IPv4' checkbox to enable IPv4 access control rules.
3. Determine the IPv4 default policy.
• Accept: Accepts traffic when no matching rules are present.
• Deny: Rejects any user's login attempt when no matching rules are present.
4. Create rules. Refer to the tables below for different operations.
ADD a rule to the end of the list•

Click Append.

•

Type a starting IP address in the Start IP field.

•

Type an ending IP address in the End IP field.

•

Select a role in the Role field. This rule applies to members of this role only.

•

Select an option in the Policy field.

•

Accept: Accepts traffic from the specified IP address range when the user is a member ofthe specified role.

•

Deny: Rejects the login attempt of a user from the specified IP address range when thatuser is a member of the specified role.

INSERT a rule between two rules

271

•

Select the rule above which you want to insert a new rule. For example, to insert a rule between rules#3 and #4, select #4.

•

Click Insert Above.

•

Type a starting IP address in the Start IP field.

•

Type an ending IP address in the End IP field.

•

Select a role in the Role field. This rule applies to members of this role only.

•

Select Accept or Deny in the Policy field. Refer to the above table for details.

The system automatically numbers the rule.
1. When finished, the rules are listed on this page.

• You can select any existing rule and then clickor

to change its priority.

2. Click Save. The rules are applied.

▶ To configure IPv6 access control rules:
1. On the same page, select the 'Enable role based access control for IPv6' checkbox to enable IPv6
access control rules.
2. Follow the same procedure as the above IPv4 rule setup to create IPv6 rules.
3. Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are notsaved.

272

Editing or Deleting Role Based Access Control Rules
You can modify existing rules to update their roles/IP addresses, or delete them when they are nolonger needed.

▶ To modify a role-based access control rule:
1. Choose Device Settings > Security > Role Based Access Control.
2. Go to the IPv4 or IPv6 section.
3. Select the desired rule in the list.
• Ensure the IPv4 or IPv6 checkbox has been selected, or you may not edit or delete any rule.
4. Perform the desired action.
• Make changes to the selected rule, and then click Save.

• Click

to remove it.

• To resort its order, click
5. Click Save.

or.

• IPv4 rules: Make sure you click the Save button in the IPv4 section, or the changes made to IPv4
rules are not saved.
• IPv6 rules: Make sure you click the Save button in the IPv6 section, or the changes made to IPv6
rules are not saved.

Setting Up a TLS Certificate▶ To obtain a CA-signed certificate:
1. Create a Certificate Signing Request (CSR) in Device Settings > TLS Certificates.
2. Submit it to a certificate authority (CA). After the CA processes the information in the CSR, it
provides you with a certificate.
3. Install the CA-signed certificate onto the PX-Series PDU.
Note: If you are using a certificate that is part of a chain of certificates, each part of the chain is signed
during the validation process.

▶ A CSR is not required in either scenario below:•

Make the PX-Series PDU create a self-signed certificate.

•Appropriate, valid certificate and key files are already available, and you only need to import them.

Creating a CSR
Follow this procedure to create the CSR.

273

▶ To create a CSR:
1. Choose Device Settings > Security > TLS Certificate.
2. In the New TLS Certificate or CSR section, provide the information requested.
• Subject:
Field

Description

Country

The country where your company is located. Use the standard ISO country code, which
comprises two uppercase letters. For a list of ISO codes, google ISO 3166 country codes.

State or province

The full name of the state or province where your company is located.

Locality

The city where your company is located.

Organization

The registered name of your company.

Organizational unit The name of your department.
Common name

The fully qualified domain name (FQDN) of your PX-Series PDU.

Email address

An email address where you or another administrative user can be reached.

Warning: If you generate a CSR without values entered in the required fields, you cannot obtain
third-party certificates.
• Subject Alternative Names:
If you want a certificate to secure multiple hosts across different domains or subdomains,
you can add additional DNS host names or IP addresses of the wanted hosts to this CSR sothat a single certificate will be valid for all of them.
Click Add Name when there are more than one additional hosts to add.
▪ Examples of subject alternative names: support.raritan.com, help.raritan.com, help.raritan.net,
and 192.168.77.50.
• Key Creation Parameters:
Field

Description

Key Type/Key Length

Key type RSA requires you to select Key Length:•2048 bits•

3072 bits

Key Type/Elliptic Curve Key type ECDSA requires you to select the elliptic curve:
NIST-P-256•

NIST P-384•

NIST P-521

Self-sign

For requesting a certificate signed by the CA, ensure this checkbox is NOT selected.

Challenge,

Type a password. The password is used to protect the certificate or CSR. This
information is optional.

Confirm challenge

274•

The value should be 4 to 64 characters long. Case sensitive.

1. Click Create New TLS Key to create both the CSR and private key. This may take several minutes tocomplete.
2. Click Download Certificate Signing Request to download the CSR to your computer.
a. You are prompted to open or save the file. Click Save to save it onto your computer.
b. Submit it to a CA to obtain the digital certificate.
c. If the CSR contains incorrect data, click Delete Certificate Signing Request to remove it, and thenrepeat the above steps to re-create it.
3. To store the newly-created private key on your computer, click Download Key in the New TLS
Certificate section.
Note: The Download Key button in the Active TLS Certificate section is for downloading the private key ofthe currently-installed certificate rather than the newly-created one.
• You are prompted to open or save the file. Click Save to save it onto your computer.

Installing a CA-Signed Certificate
To get a certificate from a certificate authority (CA), first create a CSR and send it to the CA. See Creatinga CSR (on page 273).
After receiving the CA-signed certificate, install it onto the PX-Series PDU.

▶ To install the CA-signed certificate:
1. Choose Device Settings > Security > TLS Certificate.
2. Clickto navigate to the CA-signed certificate file.
3. Click Upload to install it.
4. To verify whether the certificate has been installed successfully, check the data shown in the Active
TLS Certificate section.

Creating a Self-Signed Certificate
When appropriate certificate and key files for PX-Series PDU are unavailable, the alternative, other thansubmitting a CSR to the CA, is to generate a self-signed certificate.

▶ To create and install a self-signed certificate:
1. Choose Device Settings > Security > TLS Certificate.
2. Enter information.
Field

Description

Country

The country where your company is located. Use the standard ISO country code, which
comprises two uppercase letters. For a list of ISO codes, google ISO 3166 country
codes.

State or province

The full name of the state or province where your company is located.

Locality

The city where your company is located.

275

FieldDescription

Organization

The registered name of your company.

Organizational unit

The name of your department.

Common name

The fully qualified domain name (FQDN) of your PX-Series PDU.

Email address

An email address where you or another administrative user can be reached.

Key Type/Key Length

Key type RSA requires you to select Key Length:•2048 bits•

3072 bits

Key Type/Elliptic Curve Key type ECDSA requires you to select the elliptic curve:•

NIST-P-256•

NIST P-384•

NIST P-521

Self-sign

Ensure this checkbox is selected, which indicates that you are creating a self-signed
certificate.

Validity in days

This field appears after the Self-sign checkbox is selected.
Type the number of days for which the self-signed certificate will be valid.

A password is not required for a self-signed certificate so the Challenge and Confirm Challenge
fields disappear.
1. Click Create New TLS Key to create both the self-signed certificate and private key. This may takeseveral minutes to complete.
2. Once complete, do the following:a. Double check the data shown in the New TLS Certificate section.
b. If correct, click "Install Key and Certificate" to install the self-signed certificate and private key.
Tip: To verify whether the certificate has been installed successfully, check the data shown in the
Active TLS Certificate section.
If incorrect, click "Delete Key and Certificate" to remove the self-signed certificate andprivate key, and then repeat the above steps to re-create them.
3. (Optional) To download the self-signed certificate and/or private key, click Download Certificate or
Download Key in the New TLS Certificate section.
• You are prompted to open or save the file. Click Save to save it onto your computer.
Note: The Download Key button in the Active TLS Certificate section is for downloading the private
key of the currently-installed certificate rather than the newly-created one.

Installing or Downloading Existing Certificate and Key
You can download the already-installed certificate and private key from any PX-Series PDU for backup or
file transfer. For example, you can install the files onto a replacement PX-Series PDU, add the certificate
to your browser and so on.

276

If valid certificate and private key files are already available, you can install them on the PX-Series PDU
without going through the process of creating a CSR or a self‑signed certificate.
Note: If you are using a certificate that is part of a chain of certificates, each part of the chain is signed
during the validation process.

▶ To download active key and certificate files from PX-Series PDU:
1. Choose Device Settings > Security > TLS Certificate.
2. In the Active TLS Certificate section, click Download Key and Download Certificate respectively.
Note: The Download Key button in the New TLS Certificate section, if present, is for downloading the
newly-created private key rather than the one of the currently-installed certificate.
3. You are prompted to open or save the file. Click Save to save it onto your computer.

▶ To install available key and certificate files onto PX-Series PDU:
1. Choose Device Settings > Security > TLS Certificate.
2. Select the "Upload key and certificate" checkbox at the bottom of the page.
3. The 'Key File' and 'Certificate file' buttons appear. Click each button to select the key and/or
certificate file.
4. Click Upload. The selected files are installed.
5. To verify whether the certificate has been installed successfully, check the data shown in the Active
TLS Certificate section.

Setting Up External Authentication
Important: Make sure your network infrastructure uses TLS rather than SSL.
PX-Series PDU supports the following authentication mechanisms:•

Local user database

•

LDAP

•

RADIUS•TACACS+

Local authentication is the default method. If you use this method, you only need to create user
accounts. See User Management (on page 226).
If you prefer external authentication, you must provide information about the external Authentication
and Authorization (AA) server.
If both local and external authentication is needed, create user accounts on the PX-Series PDU in
addition to providing the external AA server data.

277

When configured for external authentication, all users must have an account on the external AA server.
Local‑authentication-only users will have no access to the PX-Series PDU except for the admin, whoalways can access.
If the external authentication fails, an "Authentication failed" message is displayed. Details regarding
the authentication failure are available in the event log.
You must have the "Change Authentication Settings" permission to configure or modify theauthentication settings.

Adding LDAP/LDAPS Servers
To use LDAP authentication, enable it in the Device Settings > Authentication page, and enter the
information about the LDAP server in the LDAP page.
Note: If the PX-Series PDU clock and the LDAP server clock are out of sync, the installed TLS certificates,
if any, may be considered expired. To ensure proper synchronization, administrators should configure
the PX-Series PDU and the LDAP server to use the same NTP server(s).

▶ To add LDAP/LDAPS servers:
1. Choose Device Settings > Security > LDAP.
2. Click New.
3. Enter information.
Field/setting

Description

IP address /hostname

The IP address or hostname of your LDAP/LDAPS server.
•

Without the encryption enabled, you can type either the domain name or IP addressin this field, but you must type the fully qualified domain name if the encryption isenabled.

Copy settings from This checkbox appears only when there are existing AA server settings on the PX-Series
existing LDAPPDU. To duplicate any existing AA server's settings, refer to the duplicating procedure
serverbelow.
Type of LDAP
server

Security

Choose one of the following options:•

OpenLDAP•

Microsoft Active Directory.

Determine whether you would like to use Transport Layer Security (TLS) encryption, whichallows the PX-Series PDU to communicate securely with the LDAPS server.
Three options are available:

Port (None/
StartTLS)

278•

StartTLS

•

TLS

•

None

•

The default Port is 389. Either use the standard LDAP TCP port or specify another port.

Field/setting

Description

Port (TLS)

Configurable only when "TLS" is selected in the Security field.
The default is 636. Either use the default port or specify another one.

Enable verification Select this checkbox if it is required to validate the LDAP server's certificate by the PXof LDAP server
Series PDU prior to the connection.
certificate
If the certificate validation fails, the connection is refused.
CA certificate

Consult your AA server administrator to get the CA certificate file for the LDAPS server.
Click Browse to select and install the certificate file.
•

Click Show to view the installed certificate's content.

•

Click Remove to delete the installed certificate if it is inappropriate.

Note: If the required certificate file is a chain of certificates, and you are notsure about the requirements of a certificate chain, see TLS Certificate Chain.
Allow expired andnot yet valid
certificates•

Select this checkbox to make the authentication succeed regardless of the certificate's
validity period.

•

After deselecting this checkbox, the authentication fails whenever any certificate in
the selected certificate chain is outdated or not valid yet.

Anonymous bindUse this checkbox to enable or disable anonymous bind.

Bind DN•

To use anonymous bind, select this checkbox.

•

When a Bind DN and password are required to bind to the external LDAP/LDAPS
server, deselect this checkbox.

Required after deselecting the Anonymous Bind checkbox.
Distinguished Name (DN) of the user who is permitted to search the LDAP directory in thedefined search base.

Bind password,

Required after deselecting the Anonymous Bind checkbox.

Confirm bindpassword

Enter the Bind password.

Base DN for search Distinguished Name (DN) of the search base, which is the starting point of the LDAP
search.
•Example: ou=dev,dc=example,dc=com

Login Name
Attribute

The attribute of the LDAP user class which denotes the login name.

User entry object
class

The object class for user entries.

••

Usually it is the uid.

Usually it is inetOrgPerson.

279

Field/setting

Description

User searchsubfilter

Search criteria for finding LDAP user objects within the directory tree.

Group lookup
using memberOf
attribute•

Select this checkbox to determine group membership by consulting the user's
memberOf attribute(s).

•Deselect this checkbox to determine group membership by doing a non-recursive
search for groups containing the user's DN as member.

Group member
attribute•

Required only when "Group lookup using memberOf attribute" is not selected.

•

Required for OpenLDAP only.

Group entry object •class•

Required only when "Group lookup using memberOf attribute" is not selected.
Required for OpenLDAP only.

Group searchsubfilter•

Required only when "Group lookup using memberOf attribute" is not selected.

•

Required for OpenLDAP only.

Active Directorydomain

The name of the Active Directory Domain.
•

Example: testradius.com

1. Click Add Server. The new LDAP server is listed. To verify, click Test Connection to check whether the
PX-Series PDU can connect to the new server successfully.
2. To add more servers, repeat the same steps.
3. In the LDAP page, use the arrow buttons to arrange the servers in the order they should beaccessed, then click Save.
4. Make sure LDAP is enabled: Go to Device Settings > Security > Authentication, and select LDAP as
the Authentication Type.

280

▶ To duplicate LDAP/LDAPS server settings:
If you have added any LDAP/LDAPS server to the PX-Series PDU, and the server you will add shares
identical settings with an existing one, the most convenient way is to duplicate that LDAP/LDAPS
server's data and then revise the IP address/host name.
1. Choose Device Settings > Security > LDAP, then click New.
2. Select the "Copy settings from existing LDAP server" checkbox.
3. Select the LDAP/LDAPS server whose settings you want to copy.
4. Modify the IP Address/Hostname field.
5. Click Add Server.

Adding Radius Servers
To use Radius authentication, enable it and enter the information you have gathered.
Note: The RADIUS NAS Identifier is "DPC PDU SN:<device serial number>".

▶ To add Radius servers:
1. Choose Device Settings > Security > RADIUS.
2. Click New.
3. Enter information.
Field/setting

Description

IP address / hostname The IP address or hostname of your Radius server.
Type of RADIUS
authentication

Select an authentication protocol.
•

PAP (Password Authentication Protocol)•

CHAP (Challenge Handshake Authentication Protocol)•

MS-CHAPv2 (Microsoft Challenge Handshake Authentication Protocol)
CHAP is generally considered more secure because the user name and password
are encrypted, while in PAP they are transmitted in the clear.
MS‑CHAPv2 provides stronger security than the above two. Selecting this option
will support both MS-CHAPv1 and MS-CHAPv2.

Note: All authentication methods are insecure. It is strongly recommended
to use RADIUS only in a secure networking environment. A warning
displays for all methods.
Authentication port,

The defaults are standard ports -- 1812 and 1813.

Accounting port

To use non-standard ports, type a new port number.

Accounting Enabled?

Default is enabled.
Accounting allows you to log activity executed on the RADIUS server.
When RADIUS accounting is enabled and the RADIUS server does not support
accounting, then authentication will fail.

281

Field/setting

Description

Timeout

This sets the maximum amount of time to establish contact with the Radius server
before timing out.
Type the timeout period in seconds.

Retries

Type the number of retries.

Shared secret,The shared secret is necessary to protect communication with the Radius server.

Confirm shared secret

1.
2.
3.
4.

To verify settings, click Test Connection to check if you can connect to the new server successfully.
Click Add Server. The new Radius server is listed on the RADIUS page.
To add more servers, repeat the same steps.
In the RADIUS page, use the arrow buttons to arrange the servers in the order they should beaccessed, then click Save.
5. Make sure RADIUS is enabled: Go to Device Settings > Security > Authentication, and select RADIUS
as the Authentication Type.

Adding TACACS+ Servers
To use TACACS+ authentication, add the server information and enable TACACS+.
Note: You need to create a new custom service attribute called Xerus on the
TACACS+ server. This attribute value will match the role name (case sensitive) on
the PX-Series PDU. In the authorization request to the TACACS+ server, the PXSeries PDU will send a request for Xerus as a custom service attribute. TACACS+
server then returns the roles of the authenticated user in the Xerus: roles attribute.
Returning multiple roles separated by a slash, for example, role1/role2, is
supported. See Cisco ISE Xerus TACACS+ Authentication (on page 711) for
configuration.

▶ To add TACACS+ servers:
1. Choose Device Settings > Security > TACACS+.
2. Click New.
3. Enter information.
Field/setting

Description

IP address / hostname The IP address or hostname of your TACACS+ server.

282

Field/setting

Description

Type of TACACS+
authentication

Select an authentication protocol.
•

ASCII

•

PAP (Password Authentication Protocol)•

CHAP (Challenge Handshake Authentication Protocol)•

MS-CHAP (Microsoft Challenge Handshake Authentication Protocol)
CHAP is generally considered more secure because the user name and password
are encrypted, while in PAP they are transmitted in the clear.
MS‑CHAP provides stronger security than the other options.

Note: All authentication methods are insecure. It is strongly recommended
to use TACACS+ only in a secure networking environment. A warning
displays for all methods.
Port

The default port is 49
To use non-standard port, type a new port number.

Enable Accounting?

Default is enabled.
Accounting allows you to log activity executed on the TACACS+ server.

Timeout

Default is 10 seconds.
Maximum amount of time to establish contact with the server before timing out.
Enter the timeout period in seconds.

Retries

Default is 3.
Enter the number of retries.

Shared secret,The shared secret is necessary to protect communication with the server.

Confirm shared secret

1. Click Add Server or Test Connection to verify the settings.
2. To add more servers, repeat the same steps.
3. In the TACACS+ page, use the arrow buttons to arrange the servers in the order they should beaccessed, then click Save.
4. To begin using the configuration, make sure TACACS+ is enabled: Go to Device Settings > Security >Authentication, and select TACACS+ as the Authentication Type.

283

Configuring Login Settings
Choose Device Settings > Security > Login Settings to open the Login Settings page, where you can:•Configure the user blocking feature.
Note: The user blocking function applies only to local authentication instead of external
authentication through AA servers.

•

Determine the timeout period for any inactive user.

•

Prevent simultaneous logins using the same login name.

▶ To configure user blocking:
1. To enable the user blocking feature, select the 'Block user on login failure' checkbox.
2. In the 'Block timeout' field, select a time option. This setting determines how long the user isblocked.
• If you type a value, the value must be followed by a time unit, such as '4 min.'3. In the 'Maximum number of failed logins' field, type a number. This is the maximum number of login
failures the user is permitted before the user is blocked from accessing the PX-Series PDU.
4. Timeout for Failed Login Attempts: select a time option after which a failed attempt no longer
counts against the user. For example, if "Maximum number of failed logins" is 3, but the "Timeout
for Failed Login Attempts" has passed since the last failed attempt, the counter of failed logins
restarts.
5. Click Save.
Tip: If any user blocking event occurs, you can unblock that user manually by using the "unblock" CLI
command over a local connection. See Unblocking a User.

▶ To set limitations for login timeout and use of identical login names:
1. In the "Idle timeout period" field, type a value or click
to select a time option. This setting
determines how long users are permitted to stay idle before being forced to log out.
• If you type a value, the value must be followed by a time unit, such as '4 min.' See Time Units (onpage 155).
• Keep the idle timeout to 20 minutes or less if possible. This reduces the number of idle sessions
connected, and the number of simultaneous commands sent to the PX-Series PDU.
2. Select the 'Prevent concurrent login with same username' checkbox to prevent multiple users fromusing the same login name simultaneously.
3. Click Save.

284

Configuring Password Policy
Choose Device Settings > Security > Password Policy to open the Password Policy page, where you can:•Force users to use strong passwords.

•

Force users to change passwords at a regular interval -- that is, password aging.

▶ To configure password aging:
1. Select the 'Enabled' checkbox of Password Aging.
2. In the 'Password aging interval' field, type a value or select a time option. This setting determines
how often users are requested to change their passwords.
• If you type a value, the value must be followed by a time unit, such as '10 d.'
3. Click Save.

▶ To force users to create strong passwords:
1. Select the 'Enabled' checkbox of Strong Passwords to activate the strong password feature. The
following are the default settings:
Minimum length= 8 characters

Maximum length= 32 characters

At least one lowercase character= Required

At least one uppercase character= Required

At least one numeric character= Required

At least one special character= Required

Number of forbidden previous passwords=5

2. Make changes to the default settings as needed.
3. Click Save.

Enabling the Restricted Service Agreement
The restricted service agreement feature, if enabled, forces users to read a security agreement when
they log in to the PX-Series PDU. Users must accept the agreement, or they cannot log in. You canconfigure an event notifying you if a user has accepted or declined the agreement.

▶ To enable the service agreement:
1. Click Device Settings > Security > Service Agreement.
2. Select the 'Enforce restricted service agreement' checkbox.
3. Edit or paste the content as needed.
• A maximum of 10,000 characters can be entered.
4. Click Save.

285

▶ Login manner after enabling the service agreement:
After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on thelogin screen.

To log in when a restricted service agreement appears:•

In the web interface, select the checkbox labeled "I understand and accept the restricted service
agreement."•

In the CLI, type y when the confirmation message "I understand and accept the restricted service
agreement" is displayed.

Setting the Date and Time
Set the internal clock manually, or link to a Network Time Protocol (NTP) server.
PX-Series PDU follows the NTP server sanity check per the IETF RFC.
Note: If you are using Sunbird's® Power IQ®, you must configure Power IQ and the PX-Series PDU to havethe same date/time or NTP settings.

▶ To set the date and time:
1. Choose Device Settings > Date/Time.
2. Click the 'Time zone' field to select your time zone from the list.
3. If the daylight saving time applies to your time zone, verify the 'Automatic daylight saving time
adjustment' checkbox is selected.
4. Select the method for setting the date and time. Choose settings and click Save.

▶ Customize the date and time

286

•

Select 'User specified time'.

•

Enter the date or click the calendar icon to select a date.

•

Click 12H/24H button to toggle time formats.

•

Click the AM/PM button to toggle.

•

Enter the time or click the arrows to set it.

▶ Use the NTP server•

Select "Synchronize with NTP server."•The DHCP-assigned NTP servers are available when DHCP is enabled. The IP
address appears as Active NTP Server. To use this server, leave the primary andsecondary server fields blank.

•

To specify NTP servers, enter the primary NTP server in the "First time server"
field. A secondary NTP server is optional.
Click Check NTP Servers to verify accessibility.

287

Windows NTP Server Synchronization Solution
The NTP client on the PX-Series PDU follows the NTP RFC so the PX-Series PDU rejects any NTP servers
whose root dispersion is more than one second. An NTP server with a dispersion of more than one
second is considered an inaccurate NTP server by the PX-Series PDU.
Note: For information on NTP RFC, visit http://tools.ietf.org/html/rfc4330 - http://tools.ietf.org/html/
rfc4330 to refer to section 5.
Windows NTP servers may have a root dispersion of more than one second, and therefore cannot
synchronize with the PX-Series PDU. When the NTP synchronization issue occurs, change the dispersion
settings to resolve it.

▶ To change the Windows NTP's root dispersion settings:
1. Access the registry settings associated with the root dispersion on the Windows NTP server.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
2. AnnounceFlags must be set to 0x05 or 0x06.
• 0x05 = 0x01 (Always time server) and 0x04 (Always reliable time server)• 0x06 = 0x02 (Automatic time server) and 0x04 (Always reliable time server)
Note: Do NOT use 0x08 (Automatic reliable time server) because its dispersion starts at a high value
and then gradually decreases to one second or lower.
3. LocalClockDispersion must be set to 0.

Door Access
SmartLock enabled cabinets integrated with PowerIQ or other third party systems authorize door accessremotely. In the event that the remote authorization is not accessible, you can configure local door
access rules as a fallback method.
A door access rule can contain the following components:•

Selected door locks: must be configured in advance.

•

Authorization via card: specify which card ID and card reader must be used•

Authorization via keypad: specify the PIN and keypad that must be used•

Two-factor authorization: a timeout that requires both card and keypad conditions to be met. For
example: when a certain card is inserted, the correct PIN must be entered in the next 10 seconds.

•

Absolute time conditions: grant access for a specific date and time•

Periodic time conditions: grant access on certain days of the week and certain times▶ To create a door access rule:
1. Choose Device Settings > Door Access.
2. Click New Access Rule.

288

3. The New Door Access Rule page opens. Enter a name for the rule. 128 characters maximum.
4. Select the door locks this rule applies to in the Available Door Handle Locks list. Each selected door
lock appears in the Selected Locks section.

5. To allow authorization via card reader, select the Card Access checkbox, then select the correct Card
Reader and click Read Card to retrieve the Card ID. Card IDs are hidden for security. Click the eyeballicon to reveal and verify the Card ID.

6. To allow Authorization via Keypad, select the Keypad Access checkbox, then select the correct
keypad and enter the PIN. PINs are hidden for security. Click the eyeball icon to reveal and verify the
PIN. PIN length varies by keypad, and a minimum PIN length of 4 is required.

289

7. When both Card and Keypad authorization are required, the Two-Factor Configuration controls are
required. Enter a Timeout in seconds during which both Card and Keypad authorization must occur.

8. To allow authorization with an Absolute Time Condition, select the Absolute Time checkbox, thenuse the calendar tool to set the start and end dates, and the clock tools to set the start and end
times during which access is granted. Note: Click the 12H/24H icon to toggle between clock styles.

9. To allow authorization with a Periodic Time Condition, select the Periodic Time checkbox, thenselect the Days of Week and range of hours on which access is granted. Note: Click the 12H/24H icon
to toggle between clock styles.

10. Click Create to save the rule. All rules appear on the main Door Access Rule page.

290

Event Rules and Actions
Crete event rules and actions to notify you of or react to a change in conditions.
An event rule consists of two parts:•

Event: This is the situation where the PX-Series PDU or a device connected to it meets a certain
condition. For example, the inlet's voltage reaches the warning level.

•

Action: This is the response to the event. For example, the system administrator is notified of theevent via email.

Some actions can be scheduled at regular intervals instead of occurring in reaction to an event. For
example, you can schedule the emailing of the temperature report every hour.
You must have the Administrator Privileges to configure event rules.

▶ To create an event rule:
1. Choose Device Settings > Event Rules.
2. If the needed action is not available yet, click New Action to create it.
a. Assign a name to this action.
b. Select the desired action and configure it as needed.
c. Click Create.
3. Click New Rule to create a new rule.
a. Assign a name to this rule.
b. Make sure the Enabled checkbox is selected, to make the new rule active.
c. In the Event field, select the event to react to.
d. In the 'Available actions' field, select the desired action(s) to respond to the selected event.
e. Click Create.

▶ To create a scheduled action:
1. Click New Scheduled Action to schedule the desired action.

291

a. Assign a name to this scheduled action.
b. Make sure the Enabled checkbox is selected to make the scheduled action active.
c. Set the interval time, which ranges from every minute to yearly.
d. In the 'Available actions' field, select the desired action(s).
e. Click Create.

Built-in Rules and Rule Configuration
There are several built-in event rules, which cannot be deleted. If the built-in event rules do not satisfy
your needs, create new rules.

▶ Built-in rules:•

System Event Log Rule:
This causes ANY event occurred to the PX-Series PDU to be recorded in the internal log. It
is enabled by default.
Note: Default log messages are generated for each event.

•

System SNMP Notification Rule:•

This causes SNMP traps or informs to be sent to specified IP addresses or hosts when ANY
event occurs to the PX-Series PDU. It is disabled by default.
System Tamper Detection Alarmed:•

This causes alarm notifications if a connected tamper sensor is detected to be in an
alarmed state. It is enabled by default.
System Tamper Detection Unavailable:
This causes alarm notifications if a previously available tamper sensor is not detected. It isenabled by default.

▶ Event rule configuration illustration:
1. Choose Device Settings > Event Rules > New Rule.
2. Click the Event field to select an event type.
• <Any sub-event> means all events shown on the list.
• <Any Numeric Sensor> means all numeric sensors, including internal and environmental sensors.
<Any Numeric Sensor> is especially useful if you want to receive the notifications when any
numeric sensor's readings pass through a specific threshold.
3. In this example, the Peripheral Device Slot is selected, which is related to the environmental sensor
packages. Then a sensor ID field for this event type appears. Click this additional field to specify
which sensor should be the subject of this event.
4. In this example, sensor ID 3 (Slot 3) is selected, which is a temperature sensor. Then a new field forthis sensor appears. Click this field to specify the type of event(s) you want.
5. In this example, Numeric Sensor is selected because we want to select numeric-sensor-related
event(s). Then a field for numeric-sensor-related events appears. Click this field to select one of thenumeric-sensor-related events from the list.

292

6. In this example, 'Above upper critical threshold' is selected because we want the PX-Series PDU toreact only when the selected temperature sensor's reading enters the upper critical range. A"Trigger condition" field appears, requiring you to define the "exact" condition related to the "upper
critical" event.
7. Select the desired radio button to finish the event configuration. Refer to the following table fordifferent types of radio buttons.
• See Sample Event Rules (on page 338).
8. Add and/or remove actions to configure the rule. Select actions from the 'Available actions' list to
create the Select actions list.

▶ Radio buttons for different events:
Some events require you to configure the "Trigger condition".
Event types

Radio buttons

Numeric sensor
threshold-crossing
events, or theoccurrence of theselected event -true or false•

Asserted: action occurs only when the selected event
occurs. That is, the status of the event transits from FALSE
to TRUE.

•

Deasserted: action occurs only when the selected event
disappears or stops. That is, the status of the selected event
transits from TRUE to FALSE.

•

Both: action occurs both when the event occurs (asserts)
and when the event stops/disappears (deasserts).

•

Alarmed/Open/On: action occurs only when the chosensensor enters the alarmed, open or on state.

•

No longer alarmed/Closed/Off: action occurs only when thechosen sensor returns to the normal, closed, or off state.

•

Both: action occurs whenever the chosen sensor switches
its state.

State sensor statechange293

Event types

Radio buttons

Sensor availability•

Unavailable: action occurs only when the chosen sensor is
NOT detected and becomes unavailable.

•

Available: action occurs only when the chosen sensor is
detected and becomes available.

•

Both: action occurs both when the chosen sensor becomes
unavailable or available.

•

Link state is up: action occurs only when the network linkstate changes from down to up.

•

Link state is down: action occurs only when the network
link state changes from up to down.

•

Both: action occurs whenever the network link statechanges.

•

Enabled: action occurs only when the chosen function isenabled.

•Disabled: action occurs only when the chosen function isdisabled.

•

Both: action occurs when the chosen function is either
enabled or disabled.

•

Accepted: action occurs only when the specified user
accepts the restricted service agreement.

•

Declined: action occurs only when the specified user rejects
the restricted service agreement.

•

Both: action occurs both when the specified user accepts or
rejects the restricted service agreement.

•

Monitoring started: action occurs only when themonitoring of any specified server starts.

•

Monitoring stopped: action occurs only when themonitoring of any specified server stops.

•

Both: action occurs when the monitoring of any specified
server starts or stops.

•

Unreachable: action occurs only when any specified server
becomes inaccessible.

•

Reachable: action occurs only when any specified server
becomes accessible.

•

Both: action occurs when any specified server becomes
either inaccessible or accessible.

Network interface
link state

Function enabledor disabled

Restricted service
agreement

Server monitoring
event

Server reachability294

Event types

Radio buttons

Device connection
or disconnection,such as a
USB‑cascaded
device•Connected: action occurs only when the selected device is
physically connected to it.

•

Disconnected: action occurs only when the selected device
is physically disconnected from it.

•

Both: action occurs both when the selected device is
physically connected to it and when it is disconnected.

+12V Supply 1
StatusAvailable radio buttons include "Fault," "OK" and "Both."•Fault: action occurs only when the selected 12V power
supply to the controller enters the fault state.

•

OK: action occurs only when the selected 12V power supply
to the controller enters the OK state.

•

Both: action occurs whenever the selected 12 power
supply's status changes.

Xerus Default Log Messages for All Products
Listed here are all default messages for all Xerus events, including all supported products. Not all
products support all events, and events are marked here with the supported model type.
Event/context

Default message on event assertion

Default message on event
deassetion

Asset Management >Blade Extension
Overflow

Blade extension overflow occurred on strip[AMSNUMBER] ('[AMSNAME]').

Blade extension overflow cleared forstrip [AMSNUMBER] ('[AMSNAME]').

Asset Management >Composite Asset Strip
Composition Changed

Composition changed on composite asset
strip [AMSNUMBER] ('[AMSNAME]').

Asset Management >Device Config Changed

Config parameter '[CONFIGPARAM]' of asset
strip [AMSNUMBER] ('[AMSNAME]') changed
to '[CONFIGVALUE]' by user '[USERNAME]'.

Asset Management >Firmware Update

Firmware update for asset strip[AMSNUMBER] ('[AMSNAME]'): statuschanged to '[AMSSTATE]'.

Asset Management >Rack Unit > Blade
Extension Connected

Blade extension with ID '[AMSTAGID]'
connected at rack unit
[AMSRACKUNITPOSITION] of asset strip[AMSNUMBER] ('[AMSNAME]').

Blade extension with ID'[AMSTAGID]' disconnected at rack
unit [AMSRACKUNITPOSITION] of
asset strip [AMSNUMBER]('[AMSNAME]').

Asset Management >Rack Unit > Tag
Connected

Asset tag with ID '[AMSTAGID]' connected atrack unit [AMSRACKUNITPOSITION], slot
[AMSBLADESLOTPOSITION] of asset strip[AMSNUMBER] ('[AMSNAME]').

Asset tag with ID '[AMSTAGID]'
disconnected at rack unit
[AMSRACKUNITPOSITION], slot
[AMSBLADESLOTPOSITION] of asset
strip [AMSNUMBER] ('[AMSNAME]').

Model
Type

295

Asset Management >Rack Unit Config
ChangedConfig of rack unit [AMSRACKUNITPOSITION]
of asset strip [AMSNUMBER] ('[AMSNAME]')changed by user '[USERNAME]' to: Name'[AMSRACKUNITNAME]', LED Operation Mode'[AMSLEDOPMODE]', LED Color'[AMSLEDCOLOR]', LED Mode'[AMSLEDMODE]'

Asset Management >StateState of asset strip [AMSNUMBER]('[AMSNAME]') changed to '[AMSSTATE]'.

Card Reader
Management > Card
Reader > Card inserted

Card of type '[SMARTCARDTYPE]' inserted at
Card Reader'[FORMATTEDCARDREADERPATH]'.

Card Reader
Card of type '[SMARTCARDTYPE]' removed at
Management > Card
Card Reader
Reader > Card removed '[FORMATTEDCARDREADERPATH]'.
Card Reader
Management > Card
Reader attached

Card Reader'[FORMATTEDCARDREADERPATH]' connected.

Card Reader
Management > Card
Reader detached

Card Reader'[FORMATTEDCARDREADERPATH]'
disconnected.

Card Reader
Management > Card
Reader settingschangedSettings with name '[CARDREADERNAME]'
and description '[CARDREADERDESCRIPTION]'
set at Card Reader'[FORMATTEDCARDREADERPATH]' by user'[USERNAME]' from host '[USERIP]'.

Device > Event log
clearedEvent log cleared by user '[USERNAME]' fromhost '[USERIP]'.

Device > Bulk
configuration copied[LINKIDTAG]Bulk configuration copied by user'[USERNAME]' from host '[USERIP]'.

Device > Bulk
configuration saved[LINKIDTAG]Bulk configuration saved by user'[USERNAME]' from host '[USERIP]'.

Device > Device clockchangedThe device clock was changed from
[OLDDATETIME] to [DATETIME].

Device > Data pushfailedData push to URL [DATAPUSHURL] failed.
[ERRORDESC]

Device > Device settings [LINKIDTAG]Device settings restored by user
restored'[USERNAME]' from host '[USERIP]'.
Device > Device settings [LINKIDTAG]Device settings saved by user
saved'[USERNAME]' from host '[USERIP]'.

296

Device > Firmware
update completed[LINKIDTAG]Firmware upgraded successfully
from version '[OLDVERSION]' to version'[VERSION]' by user '[USERNAME]' from host'[USERIP]'.

Device > Firmware
update failed[LINKIDTAG]Firmware upgrade failed fromversion '[OLDVERSION]' to version '[VERSION]'
by user '[USERNAME]' from host '[USERIP]'.

Device > Firmware
update started[LINKIDTAG]Firmware upgrade started fromversion '[OLDVERSION]' to version '[VERSION]'
by user '[USERNAME]' from host '[USERIP]'.

Device > Firmware
validation failed[LINKIDTAG]Firmware validation failed by user'[USERNAME]' from host '[USERIP]'.

Device > Hardware
failure present[LINKIDTAG]Failure '[FAILURETYPESTR]'
asserted for component '[COMPONENTID]'.

Device > Device
identification changed

Config parameter '[CONFIGPARAM]' changed
to '[CONFIGVALUE]' by user '[USERNAME]'
from host '[USERIP]'.

Device > An LDAP error
occurred

An LDAP error occurred: [ERRORDESC].

Device > Network
The [IFNAME] network interface link is now
interface link state is up up.
Device > Peripheral
Device Firmware
UpdateFirmware update for peripheral device[EXTSENSORSERIAL] from [OLDVERSION] to[VERSION] [SENSORSTATENAME].

Device > A Radius error
occurredA Radius error occurred: [ERRORDESC].

Device > Raw
configuration
downloaded[LINKIDTAG]Raw configuration downloaded byuser '[USERNAME]' from host '[USERIP]'.

Device > Raw
configuration updated[LINKIDTAG]Raw configuration updated byuser '[USERNAME]' from host '[USERIP]'.

Device > Sending SMS
message failed

Sending SMS message to '[PHONENUMBER]'
failed. [ERRORDESC]

Device > Sending SMTP
message failed

Sending SMTP message to '[SMTPRECIPIENTS]'
using server '[SMTPSERVER]' failed.
[ERRORDESC][LINKIDTAG]Failure'[FAILURETYPESTR]' deasserted forcomponent '[COMPONENTID]'.

The [IFNAME] network interface link
is now down.

Device > Sending SNMP Sending SNMP inform to manager
inform failed or no[SNMPMANAGER]:[SNMPMANAGERPORT]
response
failed or no response. [ERRORDESC]

297

Sending Syslog message to server
Device > Sending Syslog [SYSLOGSERVER]:[SYSLOGPORT]
message failed([SYSLOGTRANSPORTPROTO]) failed.
[ERRORDESC]
Device > System reset[LINKIDTAG]System reset performed by user'[USERNAME]' from host '[USERIP]'.

Device > System started [LINKIDTAG]System started.
Device > A TACACS+
error occurred

A TACACS+ error occurred: [ERRORDESC].

Device > Unknown
peripheral device
attached

An unknown peripheral device with rom code'[ROMCODE]' was attached at position'[PERIPHDEVPOSITION]'.

Device > Expansion unit
Expansion unit connected.
connected
Device > Wired network The network authentication on interface
authentication result[IFNAME] [NETAUTHRESULTSTR].

298

Door Access Control >Door access denied

Door access was denied:[DOORACCESSDENIALREASON]

Door Access Control >Door access granted

Door access was granted, rule'[DOORACCESSRULENAME]'([DOORACCESSRULEID])

Door Access Control >Door access rule added

Door access rule '[DOORACCESSRULENAME]'([DOORACCESSRULEID]) was added by user'[USERNAME]' from host '[USERIP]'

Door Access Control >Door access rulechangedDoor access rule '[DOORACCESSRULENAME]'([DOORACCESSRULEID]) was changed by user'[USERNAME]' from host '[USERIP]'

Door Access Control >Door access deleted

Door access rule '[DOORACCESSRULENAME]'([DOORACCESSRULEID]) was deleted by user'[USERNAME]' from host '[USERIP]'

Door Access Control >Door Handle > (handle
name) > Door Forced
Open[LINKIDTAG]Door '[DOORSTATENAME]' was
opened without unlocking the door handle.

Door Access Control >Door Handle > (handle
name) > Mechanically
Unlocked[LINKIDTAG]Door handle'[DOORHANDLENAME]' was opened without
being electronically unlocked.

Expansion unit disconnected.

Peripheral device '[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT] asserted'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].

Peripheral device'[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT]deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Peripheral device '[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT] asserted'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].

Peripheral device'[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT]deasserted 'above upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Peripheral device '[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT] asserted'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].

Peripheral device'[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT]deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Peripheral device '[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT] asserted'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].

Peripheral device'[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT]deasserted 'below lower warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Peripheral Device Slot > Peripheral device '[EXTSENSORNAME]' in
Numeric Sensor >[FORMATTEDEXTSENSORSLOT] has become
Unavailable
unavailable.

Peripheral device'[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT] is nolonger unavailable; it is now[SENSORSTATENAME].

Peripheral Device Slot > Peripheral device '[EXTSENSORNAME]' inState Sensor / Actuator [FORMATTEDEXTSENSORSLOT] is> Alarmed[SENSORSTATENAME].

Peripheral device'[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT] is[SENSORSTATENAME].

Peripheral Device Slot >Numeric Sensor >Above upper criticalthreshold

Peripheral Device Slot >Numeric Sensor >Above upper warning
threshold

Peripheral Device Slot >Numeric Sensor >Below lower criticalthreshold

Peripheral Device Slot >Numeric Sensor >Below lower warning
threshold

Peripheral device '[EXTSENSORNAME]' in
Peripheral Device Slot >[FORMATTEDEXTSENSORSLOT] has beenState Sensor / Actuatorswitched to [SENSORSTATENAME] by user
> Switched by user'[USERNAME]' from host '[USERIP]'.
Peripheral Device Slot > Peripheral device '[EXTSENSORNAME]' inState Sensor / Actuator [FORMATTEDEXTSENSORSLOT] has become> Unavailable
unavailable.
Keypad Management >Keypad > PIN entered

Peripheral device'[EXTSENSORNAME]' in[FORMATTEDEXTSENSORSLOT] is nolonger unavailable; it is now[SENSORSTATENAME].

PIN entered at Keypad'[FORMATTEDKEYPADPATH]'.

299

300

Keypad Management >Keypad attached

Keypad '[FORMATTEDKEYPADPATH]'
connected.

Keypad Management >Keypad detached

Keypad '[FORMATTEDKEYPADPATH]'
disconnected.

Keypad Management >Keypad settingschangedSettings with name '[KEYPADNAME]' anddescription '[KEYPADDESCRIPTION]' set at
Keypad '[FORMATTEDKEYPADPATH]' by user'[USERNAME]' from host '[USERIP]'.

Linking > Link unit
added

Link unit [LINKID] ([LINKUNITHOST]) has been
added by user '[USERNAME]' from '[USERIP]'.

Linking > Link unit
communication failed

Communication with link unit [LINKID]([LINKUNITHOST]) failed.

Linking > Link unit
released

Link unit [LINKID] ([LINKUNITHOST]) has beenreleased by user '[USERNAME]' from'[USERIP]'.

Outlet Grouping >Outlet Group > Outlet
Group Modified

Outlet group '[OUTLETGROUPID]' wasmodified.

Outlet Grouping >Outlet Group > Power
control > Power cycled

Outlet group '[OUTLETGROUPID]' power cycle
initiated by user '[USERNAME]' from host'[USERIP]'.

Outlet Grouping >Outlet Group > Power
control > Powered off

Outlet group '[OUTLETGROUPID]' has been
powered off by user '[USERNAME]' from host'[USERIP]'.

Outlet Grouping >Outlet Group > Power
control > Powered on

Outlet group '[OUTLETGROUPID]' has been
powered on by user '[USERNAME]' from host'[USERIP]'.

Outlet Grouping >Outlet Group > Sensor >Above upper criticalthresholdSensor '[OUTLETGROUPSENSOR]' on outlet
group '[OUTLETGROUPID]' asserted 'above
upper critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[OUTLETGROUPSENSOR]' onoutlet group '[OUTLETGROUPID]'
deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Outlet Grouping >Outlet Group > Sensor >Above upper warning
thresholdSensor '[OUTLETGROUPSENSOR]' on outlet
group '[OUTLETGROUPID]' asserted 'above
upper warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[OUTLETGROUPSENSOR]' onoutlet group '[OUTLETGROUPID]'
deasserted 'above upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Outlet Grouping >Outlet Group > Sensor >Below lower criticalthresholdSensor '[OUTLETGROUPSENSOR]' on outlet
group '[OUTLETGROUPID]' asserted 'below
lower critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[OUTLETGROUPSENSOR]' onoutlet group '[OUTLETGROUPID]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Communication with link unit
[LINKID] ([LINKUNITHOST]) is OK.

Outlet Grouping >Outlet Group > Sensor >Below lower warning
thresholdSensor '[OUTLETGROUPSENSOR]' on outlet
group '[OUTLETGROUPID]' asserted 'below
lower warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[OUTLETGROUPSENSOR]' onoutlet group '[OUTLETGROUPID]'
deasserted 'below lower warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Outlet Grouping >Sensor '[OUTLETGROUPSENSOR]' on outlet
Outlet Group > Sensor > group '[OUTLETGROUPID]' has been reset by
Resetuser '[USERNAME]' from host '[USERIP]'.
Outlet Grouping >Sensor '[OUTLETGROUPSENSOR]' of outlet
Outlet Group > Sensor > group '[OUTLETGROUPID]' has become
Unavailable
unavailable.

Sensor '[OUTLETGROUPSENSOR]' onoutlet group '[OUTLETGROUPID]' isno longer unavailable; it is now[SENSORSTATENAME].

Outlet Grouping >Outlet Group CreatedOutlet group '[OUTLETGROUPID]' was created.

Outlet Grouping >Outlet Group Deleted

Outlet group '[OUTLETGROUPID]' was deleted.

PDU > Controller >Communication failed

Communication with PDU [PDUNUMBER]
controller '[CONTROLLER]' (board ID[BOARDID]) failed

Communication with PDU[PDUNUMBER] controller'[CONTROLLER]' (board ID[BOARDID]) restored

PDU > Controller >Firmware update

PDU [PDUNUMBER] controller'[CONTROLLER]' with board ID [BOARDID] hasstarted firmware update

PDU [PDUNUMBER] controller'[CONTROLLER]' with board ID[BOARDID] has completed firmware
updatePDU > Controller >Incompatible

PDU [PDUNUMBER] controller'[CONTROLLER]' with board ID [BOARDID] is
incompatible

PDU [PDUNUMBER] controller'[CONTROLLER]' with board ID[BOARDID] is no longer incompatible

PDU > Controller > OK

PDU [PDUNUMBER] controller'[CONTROLLER]' with board ID [BOARDID] isOK

PDU [PDUNUMBER] controller'[CONTROLLER]' with board ID[BOARDID] is no longer OK

PDU > Inlet > Dip

A dip event occurred on PDU [PDUNUMBER]
inlet '[INLET]' for [DIPSWELLDURATION] s witha minimum voltage of [DIPSWELLVOLTAGE] V.

PX4 orPRO4X

PDU > Inlet > Dip/swell
event list cleared

The dip/swell event list for PDU[PDUNUMBER] inlet '[INLET]' was cleared byuser '[USERNAME]' from host '[USERIP]'.

PX4 orPRO4X

PDU > Inlet > Enabled

PDU [PDUNUMBER] inlet '[INLET]' has beenenabled by user '[USERNAME]' from host'[USERIP]'.

PDU [PDUNUMBER] inlet '[INLET]'
has been disabled by user'[USERNAME]' from host '[USERIP]'.

301

302

Sensor '[PDULINEPAIRSENSOR]' on line
PDU > Inlet > Line Pair >'[INLETLINEPAIR]' of PDU [PDUNUMBER] inlet
Sensor > Above upper'[INLET]' asserted 'above upper critical' atcritical threshold[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDULINEPAIRSENSOR]' online '[INLETLINEPAIR]' of PDU[PDUNUMBER] inlet '[INLET]'
deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[PDULINEPAIRSENSOR]' on line
PDU > Inlet > Line Pair >'[INLETLINEPAIR]' of PDU [PDUNUMBER] inlet
Sensor > Above upper'[INLET]' asserted 'above upper warning' atwarning threshold[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDULINEPAIRSENSOR]' online '[INLETLINEPAIR]' of PDU[PDUNUMBER] inlet '[INLET]'
deasserted 'above upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[PDULINEPAIRSENSOR]' on line
PDU > Inlet > Line Pair >'[INLETLINEPAIR]' of PDU [PDUNUMBER] inlet
Sensor > Below lower'[INLET]' asserted 'below lower critical' atcritical threshold[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDULINEPAIRSENSOR]' online '[INLETLINEPAIR]' of PDU[PDUNUMBER] inlet '[INLET]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[PDULINEPAIRSENSOR]' on line
PDU > Inlet > Line Pair >'[INLETLINEPAIR]' of PDU [PDUNUMBER] inlet
Sensor > Below lower'[INLET]' asserted 'below lower warning' atwarning threshold[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDULINEPAIRSENSOR]' online '[INLETLINEPAIR]' of PDU[PDUNUMBER] inlet '[INLET]'
deasserted 'below lower warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[PDULINEPAIRSENSOR]' on line
PDU > Inlet > Line Pair >'[INLETLINEPAIR]' of PDU [PDUNUMBER] inlet
Sensor > Unavailable'[INLET]' has become unavailable.

Sensor '[PDULINEPAIRSENSOR]' online '[INLETLINEPAIR]' of PDU[PDUNUMBER] inlet '[INLET]' is nolonger unavailable; it is now[SENSORSTATENAME].

A dip event occurred on pole '[INLETPOLE]' of
PDU [PDUNUMBER] inlet '[INLET]' for
PDU > Inlet > Pole > Dip[DIPSWELLDURATION] s with a minimum
voltage of [DIPSWELLVOLTAGE] V.

PX4 orPRO4X

PDU > Inlet > Pole >Dip/swell event list
clearedThe dip/swell event list for pole '[INLETPOLE]'
of PDU [PDUNUMBER] inlet '[INLET]' wascleared by user '[USERNAME]' from host'[USERIP]'.

PX4 orPRO4X

PDU > Inlet > Pole >Sensor > Above upper
critical threshold

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' asserted 'above upper critical' at[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' deasserted 'above
upper critical' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > Above upper
warning threshold

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' asserted 'above upper warning' at[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' deasserted 'above
upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > Below lower
critical threshold

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' asserted 'below lower critical' at[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' deasserted 'below
lower critical' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > Below lower
warning threshold

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' asserted 'below lower warning' at[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' deasserted 'below
lower warning' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > CriticalSensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' entered critical state.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' exited critical state; it
is now [SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > Failed

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' entered failed state.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' exited failed state; it is
now [SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > Normal

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' entered normal state.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' exited normal state; it
is now [SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > Self-Test

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' started self test.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' finished self test; it is
now [SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > Unavailable

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' has become unavailable.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' is no longer
unavailable; it is now[SENSORSTATENAME].

PDU > Inlet > Pole >Sensor > Warning

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER] inlet'[INLET]' entered warning state.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of PDU [PDUNUMBER]
inlet '[INLET]' exited warning state; it
is now [SENSORSTATENAME].

PDU > Inlet > Pole >Swell

A swell event occurred on pole '[INLETPOLE]'
of PDU [PDUNUMBER] inlet '[INLET]' for[DIPSWELLDURATION] s with a maximum
voltage of [DIPSWELLVOLTAGE] V.

PX4 or
PRO4X

303

304

PDU > Inlet > Sensor >Above upper criticalthresholdSensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' asserted 'above
upper critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]'
deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >Above upper warning
thresholdSensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' asserted 'above
upper warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]'
deasserted 'above upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >Below lower criticalthresholdSensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' asserted 'below
lower critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >Below lower warning
thresholdSensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' asserted 'below
lower warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]'
deasserted 'below lower warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >CriticalSensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' entered criticalstate.

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' exitedcritical state; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >FailedSensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' entered failed
state.

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' exited
failed state; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >Fault

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' entered fault
state.

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' exitedfault state; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >NormalSensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' entered normal
state.

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' exited
normal state; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >OK

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' entered OK
state.

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' exited
OK state; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >Reset

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' has been resetby user '[USERNAME]' from host '[USERIP]'.

PDU > Inlet > Sensor >Self-Test

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' started self test.

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]'
finished self test; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >Unavailable

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' has become
unavailable.

Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' is nolonger unavailable; it is now[SENSORSTATENAME].

PDU > Inlet > Sensor >Warning

Sensor '[INLETSENSOR]' on PDU
Sensor '[INLETSENSOR]' on PDU[PDUNUMBER] inlet '[INLET]' exited[PDUNUMBER] inlet '[INLET]' entered warning
warning state; it is now
state.
[SENSORSTATENAME].

PDU > Inlet > Swell

A swell event occurred on PDU [PDUNUMBER]
inlet '[INLET]' for [DIPSWELLDURATION] s witha maximum voltage of [DIPSWELLVOLTAGE] V.

PDU > Load Shedding >StartedPDU [PDUNUMBER] placed in Load Shedding
Mode by user '[USERNAME]' from host'[USERIP]'.

PDU [PDUNUMBER] removed from
Load Shedding Mode by user'[USERNAME]' from host '[USERIP]'.

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU [PDUNUMBER] outlet'[OUTLET]' asserted 'above upper critical' at[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU[PDUNUMBER] outlet '[OUTLET]'
deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU [PDUNUMBER] outlet'[OUTLET]' asserted 'above upper warning' at[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU[PDUNUMBER] outlet '[OUTLET]'
deasserted 'above upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU [PDUNUMBER] outlet'[OUTLET]' asserted 'below lower critical' at[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU[PDUNUMBER] outlet '[OUTLET]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU [PDUNUMBER] outlet'[OUTLET]' asserted 'below lower warning' at[SENSORREADING] [SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU[PDUNUMBER] outlet '[OUTLET]'
deasserted 'below lower warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Outlet > Pole >Sensor > Above upper
critical threshold

PDU > Outlet > Pole >Sensor > Above upper
warning threshold

PDU > Outlet > Pole >Sensor > Below lower
critical threshold

PDU > Outlet > Pole >Sensor > Below lower
warning threshold

PX4 or
PRO4X

305

PDU > Outlet > Pole >Sensor > Unavailable

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU [PDUNUMBER] outlet'[OUTLET]' has become unavailable.

PDU > Outlet > Power
control > Power cycled

PDU [PDUNUMBER] outlet '[OUTLET]' power
cycle initiated by user '[USERNAME]' fromhost '[USERIP]'.

PDU > Outlet > Power
control > Powered off

PDU [PDUNUMBER] outlet '[OUTLET]' has
been powered off by user '[USERNAME]' fromhost '[USERIP]'.

PDU > Outlet > Power
control > Powered on

PDU [PDUNUMBER] outlet '[OUTLET]' has
been powered on by user '[USERNAME]' fromhost '[USERIP]'.

Sensor '[OUTLETSENSOR]' on PDU
PDU > Outlet > Sensor >[PDUNUMBER] outlet '[OUTLET]' asserted
Above upper critical'above upper critical' at [SENSORREADING]
threshold[SENSORREADINGUNIT].

Sensor '[OUTLETSENSOR]' on PDU[PDUNUMBER] outlet '[OUTLET]'
deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[OUTLETSENSOR]' on PDU
PDU > Outlet > Sensor >[PDUNUMBER] outlet '[OUTLET]' asserted
Above upper warning'above upper warning' at [SENSORREADING]
threshold[SENSORREADINGUNIT].

Sensor '[OUTLETSENSOR]' on PDU[PDUNUMBER] outlet '[OUTLET]'
deasserted 'above upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[OUTLETSENSOR]' on PDU
PDU > Outlet > Sensor >[PDUNUMBER] outlet '[OUTLET]' asserted
Below lower critical'below lower critical' at [SENSORREADING]
threshold[SENSORREADINGUNIT].

Sensor '[OUTLETSENSOR]' on PDU[PDUNUMBER] outlet '[OUTLET]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[OUTLETSENSOR]' on PDU
PDU > Outlet > Sensor >[PDUNUMBER] outlet '[OUTLET]' asserted
Below lower warning'below lower warning' at [SENSORREADING]
threshold[SENSORREADINGUNIT].

Sensor '[OUTLETSENSOR]' on PDU[PDUNUMBER] outlet '[OUTLET]'
deasserted 'below lower warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Outlet > Sensor > PDU [PDUNUMBER] outlet '[OUTLET]' stateOnsensor changed to on.

PDU [PDUNUMBER] outlet'[OUTLET]' state sensor is no longer
on; it is now [SENSORSTATENAME].

Sensor '[OUTLETSENSOR]' on outlet
PDU > Outlet > Sensor >'[OUTLET]' has been reset by user
Reset'[USERNAME]' from host '[USERIP]'.

306

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of PDU[PDUNUMBER] outlet '[OUTLET]' isno longer unavailable; it is now[SENSORSTATENAME].

Sensor '[OUTLETSENSOR]' on PDU
PDU > Outlet > Sensor >[PDUNUMBER] outlet '[OUTLET]' has become
Unavailable
unavailable.

Sensor '[OUTLETSENSOR]' on PDU[PDUNUMBER] outlet '[OUTLET]' isno longer unavailable; it is now[SENSORSTATENAME].

PDU > Outlet >Suspended

PDU [PDUNUMBER] outlet '[OUTLET]' wassuspended after being suspected of having
caused an OCP trip event.

PDU > Overcurrent
Protector > Sensor >Above upper criticalthresholdSensor '[OCPSENSOR]' on PDU [PDUNUMBER]
overcurrent protector '[OCP]' asserted 'above
upper critical' at [SENSORREADING][SENSORREADINGUNIT].

PDU > Overcurrent
Protector > Sensor >Above upper warning
thresholdSensor '[OCPSENSOR]' on PDU[PDUNUMBER] overcurrent
Sensor '[OCPSENSOR]' on PDU [PDUNUMBER]
protector '[OCP]' deasserted 'above
overcurrent protector '[OCP]' asserted 'above
upper warning' atupper warning' at [SENSORREADING][SENSORREADING][SENSORREADINGUNIT].
[SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Overcurrent
Protector > Sensor >Below lower criticalthresholdSensor '[OCPSENSOR]' on PDU [PDUNUMBER]
overcurrent protector '[OCP]' asserted 'below
lower critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[OCPSENSOR]' on PDU[PDUNUMBER] overcurrent
protector '[OCP]' deasserted 'below
lower critical' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Overcurrent
Protector > Sensor >Below lower warning
thresholdSensor '[OCPSENSOR]' on PDU [PDUNUMBER]
overcurrent protector '[OCP]' asserted 'below
lower warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[OCPSENSOR]' on PDU[PDUNUMBER] overcurrent
protector '[OCP]' deasserted 'below
lower warning' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Overcurrent
Protector > Sensor >CriticalSensor '[OCPSENSOR]' on PDU
Sensor '[OCPSENSOR]' on PDU [PDUNUMBER][PDUNUMBER] overcurrent
overcurrent protector '[OCP]' entered criticalprotector '[OCP]' exited critical state;state.
it is now [SENSORSTATENAME].

PDU > Overcurrent
Protector > Sensor >FailedSensor '[OCPSENSOR]' on PDU
Sensor '[OCPSENSOR]' on PDU [PDUNUMBER][PDUNUMBER] overcurrent
overcurrent protector '[OCP]' entered failed
protector '[OCP]' exited failed state;state.
it is now [SENSORSTATENAME].

PDU > Overcurrent
Protector > Sensor >NormalSensor '[OCPSENSOR]' on PDU
Sensor '[OCPSENSOR]' on PDU [PDUNUMBER] [PDUNUMBER] overcurrent
overcurrent protector '[OCP]' entered normal protector '[OCP]' exited normal
state.
state; it is now[SENSORSTATENAME].

Sensor '[OCPSENSOR]' on PDU[PDUNUMBER] overcurrent
protector '[OCP]' deasserted 'above
upper critical' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

307

308

PDU > Overcurrent
Protector > Sensor >Open

Sensor '[OCPSENSOR]' on PDU
Sensor '[OCPSENSOR]' on PDU [PDUNUMBER][PDUNUMBER] overcurrent
overcurrent protector '[OCP]' is open.
protector '[OCP]' is no longer open;[OCPTRIPCAUSEINFO]
it is now [SENSORSTATENAME].

PDU > Overcurrent
Protector > Sensor >Self-Test

Sensor '[OCPSENSOR]' on PDU
Sensor '[OCPSENSOR]' on PDU [PDUNUMBER] [PDUNUMBER] overcurrent
overcurrent protector '[OCP]' started self test. protector '[OCP]' finished self test; it
is now [SENSORSTATENAME].

PDU > Overcurrent
Protector > Sensor >Unavailable

Sensor '[OCPSENSOR]' on PDU
Sensor '[OCPSENSOR]' on PDU [PDUNUMBER] [PDUNUMBER] overcurrent
overcurrent protector '[OCP]' has become
protector '[OCP]' is no longer
unavailable.
unavailable; it is now[SENSORSTATENAME].

PDU > Overcurrent
Protector > Sensor >Warning

Sensor '[OCPSENSOR]' on PDU
Sensor '[OCPSENSOR]' on PDU [PDUNUMBER] [PDUNUMBER] overcurrent
overcurrent protector '[OCP]' entered warning protector '[OCP]' exited warningstate.
state; it is now[SENSORSTATENAME].

PDU > Sensor > Above
upper critical threshold

PDU [PDUNUMBER] sensor '[PDUSENSOR]'
asserted 'above upper critical' at[SENSORREADING] [SENSORREADINGUNIT].

PDU [PDUNUMBER] sensor'[PDUSENSOR]' deasserted 'above
upper critical' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Sensor > Above
upper warning
threshold

PDU [PDUNUMBER] sensor '[PDUSENSOR]'
asserted 'above upper warning' at[SENSORREADING] [SENSORREADINGUNIT].

PDU [PDUNUMBER] sensor'[PDUSENSOR]' deasserted 'above
upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Sensor > Below
lower critical threshold

PDU [PDUNUMBER] sensor '[PDUSENSOR]'
asserted 'below lower critical' at[SENSORREADING] [SENSORREADINGUNIT].

PDU [PDUNUMBER] sensor'[PDUSENSOR]' deasserted 'below
lower critical' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Sensor > Below
lower warning
threshold

PDU [PDUNUMBER] sensor '[PDUSENSOR]'
asserted 'below lower warning' at[SENSORREADING] [SENSORREADINGUNIT].

PDU [PDUNUMBER] sensor'[PDUSENSOR]' deasserted 'below
lower warning' at [SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

PDU > Sensor > Fault

PDU [PDUNUMBER] sensor '[PDUSENSOR]'
entered fault state.

PDU [PDUNUMBER] sensor'[PDUSENSOR]' exited fault state; it
is now [SENSORSTATENAME].

PDU > Sensor > ResetPDU [PDUNUMBER] sensor '[PDUSENSOR]'
has been reset by user '[USERNAME]' fromhost '[USERIP]'.

PDU > Sensor >Unavailable

PDU [PDUNUMBER] sensor '[PDUSENSOR]'
has become unavailable.

PDU [PDUNUMBER] sensor'[PDUSENSOR]' is no longer
unavailable; it is now[SENSORSTATENAME].

Active inlet on PDU [PDUNUMBER] transfer
PDU > Transfer Switch > switch '[TRANSFERSWITCH]' changed to
Active inlet changed'[ACTIVEINLET]' due to[TRANSFERSWITCHREASON].

Transfer
switchSensor '[TRANSFERSWITCHSENSOR]' on PDU
PDU > Transfer Switch > [PDUNUMBER] transfer switch
Sensor > Above upper'[TRANSFERSWITCH]' asserted 'above upper
critical thresholdcritical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[TRANSFERSWITCHSENSOR]'
on PDU [PDUNUMBER] transfer
switch '[TRANSFERSWITCH]'
Transferdeasserted 'above upper critical' atswitch[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[TRANSFERSWITCHSENSOR]' on PDU
PDU > Transfer Switch > [PDUNUMBER] transfer switch
Sensor > Above upper'[TRANSFERSWITCH]' asserted 'above upper
warning thresholdwarning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[TRANSFERSWITCHSENSOR]'
on PDU [PDUNUMBER] transfer
switch '[TRANSFERSWITCH]'
Transferdeasserted 'above upper warning' atswitch[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[TRANSFERSWITCHSENSOR]' on PDU
PDU > Transfer Switch > [PDUNUMBER] transfer switch
Sensor > Below lower'[TRANSFERSWITCH]' asserted 'below lower
critical thresholdcritical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[TRANSFERSWITCHSENSOR]'
on PDU [PDUNUMBER] transfer
switch '[TRANSFERSWITCH]'
Transferdeasserted 'below lower critical' atswitch[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[TRANSFERSWITCHSENSOR]' on PDU
PDU > Transfer Switch > [PDUNUMBER] transfer switch
Sensor > Below lower'[TRANSFERSWITCH]' asserted 'below lower
warning thresholdwarning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[TRANSFERSWITCHSENSOR]'
on PDU [PDUNUMBER] transfer
switch '[TRANSFERSWITCH]'
Transferdeasserted 'below lower warning' atswitch[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Sensor '[TRANSFERSWITCHSENSOR]'
Sensor '[TRANSFERSWITCHSENSOR]' on PDU
PDU > Transfer Switch >on PDU [PDUNUMBER] transfer
Transfer[PDUNUMBER] transfer switch
Sensor > Fault
switch '[TRANSFERSWITCH]' isswitch'[TRANSFERSWITCH]' is [SENSORSTATENAME].
[SENSORSTATENAME].
PDU > Transfer Switch > Operational state of PDU [PDUNUMBER]
Sensor > Nontransfer switch '[TRANSFERSWITCH]' is now
redundant
non-redundant.

Operational state of PDU[PDUNUMBER] transfer switch'[TRANSFERSWITCH]' is no longer
non-redundant; it is now[SENSORSTATENAME].

Transfer
switch309

Operational state of PDU [PDUNUMBER]
PDU > Transfer Switch >transfer switch '[TRANSFERSWITCH]' is now
Sensor > Normal
normal.

Operational state of PDU[PDUNUMBER] transfer switch'[TRANSFERSWITCH]' is no longer
normal; it is now[SENSORSTATENAME].

Transfer
switchOperational state of PDU [PDUNUMBER]
PDU > Transfer Switch >transfer switch '[TRANSFERSWITCH]' is now
Sensor > Off
off.

Operational state of PDU[PDUNUMBER] transfer switch'[TRANSFERSWITCH]' is no longer
off; it is now [SENSORSTATENAME].

Transfer
switchSensor '[TRANSFERSWITCHSENSOR]' on PDU
PDU > Transfer Switch >[PDUNUMBER] transfer switch
Sensor > Out of sync'[TRANSFERSWITCH]' is out of sync.

Sensor '[TRANSFERSWITCHSENSOR]'
on PDU [PDUNUMBER] transfer
Transfer
switch '[TRANSFERSWITCH]' is noswitchlonger out of sync; it is now[SENSORSTATENAME].

Operational state of PDU [PDUNUMBER]
PDU > Transfer Switch >transfer switch '[TRANSFERSWITCH]' is now
Sensor > Standby
standby.

Operational state of PDU[PDUNUMBER] transfer switch'[TRANSFERSWITCH]' is no longer
standby; it is now[SENSORSTATENAME].

Transfer
switchSensor '[TRANSFERSWITCHSENSOR]'
Sensor '[TRANSFERSWITCHSENSOR]' on PDU
on PDU [PDUNUMBER] transfer
PDU > Transfer Switch >Transfer[PDUNUMBER] transfer switch
switch '[TRANSFERSWITCH]' is no
Sensor > Unavailable
switch'[TRANSFERSWITCH]' has become unavailable. longer unavailable; it is now[SENSORSTATENAME].

310

Port Fuse > Tripped

Fuse of [FORMATTEDEXTPORT] is[FUSESTATENAME].

Fuse of [FORMATTEDEXTPORT] is[FUSESTATENAME].

Power Metering
Controller > Power
Meter > Circuit > Pole >Sensor > Above upper
critical threshold

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel '[POWERMETER]'
circuit '[CIRCUIT]' asserted 'above upper
critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel'[POWERMETER]' circuit '[CIRCUIT]'
deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Circuit > Pole >Sensor > Above upper
warning threshold

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel '[POWERMETER]'
circuit '[CIRCUIT]' asserted 'above upper
warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel'[POWERMETER]' circuit '[CIRCUIT]'
BCM2 /
deasserted 'above upper warning' at
PMC[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Circuit > Pole >Sensor > Below lower
critical threshold

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel '[POWERMETER]'
circuit '[CIRCUIT]' asserted 'below lower
critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel'[POWERMETER]' circuit '[CIRCUIT]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

BCM2 /PMC

BCM2 /PMC

Power Metering
Controller > Power
Meter > Circuit > Pole >Sensor > Below lower
warning threshold

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel '[POWERMETER]'
circuit '[CIRCUIT]' asserted 'below lower
warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel'[POWERMETER]' circuit '[CIRCUIT]'
BCM2 /
deasserted 'below lower warning' at
PMC[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Circuit > Pole >Sensor > Unavailable

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel '[POWERMETER]'
circuit '[CIRCUIT]' has become unavailable.

Sensor '[PDUPOLESENSOR]' on pole'[CIRCUITPOLE]' of panel'[POWERMETER]' circuit '[CIRCUIT]'
is no longer unavailable; it is now[SENSORSTATENAME].

BCM2 /
PMC

Power Metering
Controller > Power
Meter > Circuit > Sensor> Above upper criticalthresholdSensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]' asserted'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]'
deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

BCM2 /
PMC

Power Metering
Controller > Power
Meter > Circuit > Sensor> Above upper warning
thresholdSensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]' asserted'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]'
deasserted 'above upper warning' at BCM2 /[SENSORREADING]PMC[SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Circuit > Sensor> Below lower criticalthresholdSensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]' asserted'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Circuit > Sensor> Below lower warning
thresholdSensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]' asserted'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]'
deasserted 'below lower warning' at BCM2 /[SENSORREADING]PMC[SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Circuit > Sensor> ResetSensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]' has been
reset by user '[USERNAME]' from host'[USERIP]'.

BCM2 /
PMC

Power Metering
Sensor '[CIRCUITSENSOR]' on panel
Controller > Power'[POWERMETER]' circuit '[CIRCUIT]' has
Meter > Circuit > Sensor
become unavailable.
> Unavailable
Power Metering
Controller > Power
Meter > Circuit Created

Circuit '[CIRCUIT]' on panel '[POWERMETER]'
was created.

Sensor '[CIRCUITSENSOR]' on panel'[POWERMETER]' circuit '[CIRCUIT]'
is no longer unavailable; it is now[SENSORSTATENAME].

BCM2 /PMC

BCM2 /PMC

BCM2 /
PMC

311

312

Power Metering
Controller > Power
Meter > Circuit Deleted

Circuit '[CIRCUIT]' on panel '[POWERMETER]'
was deleted.

BCM2 /
PMC

Power Metering
Controller > Power
Meter > Circuit
Modified

Circuit '[CIRCUIT]' on panel '[POWERMETER]'
was modified.

BCM2 /
PMC

Power Metering
Controller > Power
Meter > Pole > Sensor >Above upper criticalthresholdSensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power meter'[POWERMETER]' asserted 'above upper
critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power
meter '[POWERMETER]' deasserted'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

BCM2 /
PMC

Power Metering
Controller > Power
Meter > Pole > Sensor >Above upper warning
thresholdSensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power meter'[POWERMETER]' asserted 'above upper
warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power
meter '[POWERMETER]' deasserted'above upper warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

BCM2 /
PMC

Power Metering
Controller > Power
Meter > Pole > Sensor >Below lower criticalthresholdSensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power meter'[POWERMETER]' asserted 'below lower
critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power
meter '[POWERMETER]' deasserted'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

BCM2 /
PMC

Power Metering
Controller > Power
Meter > Pole > Sensor >Below lower warning
thresholdSensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power meter'[POWERMETER]' asserted 'below lower
warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power
meter '[POWERMETER]' deasserted'below lower warning' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

BCM2 /
PMC

Power Metering
Sensor '[PDUPOLESENSOR]' on pole
Controller > Power'[POWERMETERPOLE]' of power meter
Meter > Pole > Sensor >'[POWERMETER]' has become unavailable.
Unavailable

Sensor '[PDUPOLESENSOR]' on pole'[POWERMETERPOLE]' of power
meter '[POWERMETER]' is no longer
unavailable; it is now[SENSORSTATENAME].

BCM2 /
PMC

Power Metering
Controller > Power
Meter > Sensor > Above
upper critical threshold

Sensor '[POWERMETERSENSOR]' on
power meter '[POWERMETER]'
deasserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

BCM2 /
PMC

Sensor '[POWERMETERSENSOR]' on power
meter '[POWERMETER]' asserted 'above
upper critical' at [SENSORREADING][SENSORREADINGUNIT].

Power Metering
Controller > Power
Meter > Sensor > Above
upper warning
thresholdSensor '[POWERMETERSENSOR]' on power
meter '[POWERMETER]' asserted 'above
upper warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[POWERMETERSENSOR]' on
power meter '[POWERMETER]'
deasserted 'above upper warning' at BCM2 /PMC[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Sensor > Below
lower critical threshold

Sensor '[POWERMETERSENSOR]' on power
meter '[POWERMETER]' asserted 'below lower
critical' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[POWERMETERSENSOR]' on
power meter '[POWERMETER]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Sensor > Below
lower warning
thresholdSensor '[POWERMETERSENSOR]' on power
meter '[POWERMETER]' asserted 'below lower
warning' at [SENSORREADING][SENSORREADINGUNIT].

Sensor '[POWERMETERSENSOR]' on
power meter '[POWERMETER]'
deasserted 'below lower warning' at BCM2 /[SENSORREADING]PMC[SENSORREADINGUNIT]; it is now[SENSORSTATENAME].

Power Metering
Controller > Power
Meter > Sensor > Reset

Sensor '[POWERMETERSENSOR]' on power
meter '[POWERMETER]' has been reset byuser '[USERNAME]' from host '[USERIP]'.

Power Metering
Controller > Power
Meter > Sensor >Unavailable

Sensor '[POWERMETERSENSOR]' on power
meter '[POWERMETER]' has become
unavailable.

Power Metering
Controller > Power
Meter CreatedPower meter '[POWERMETER]' was created.

BCM2 /
PMC

Power Metering
Controller > Power
Meter Deleted

Power meter '[POWERMETER]' was deleted.

BCM2 /
PMC

Power Metering
Controller > Power
Meter Modified

Power meter '[POWERMETER]' was modified.

BCM2 /
PMC

Server Monitoring >Error

Error monitoring server '[MONITOREDHOST]':[ERRORDESC]

BCM2 /
PMC

Server Monitoring >Monitored

Server '[MONITOREDHOST]' is now being
monitored.

Server Monitoring >Power control
completedPower control operation for'[MONITOREDHOST]' finished with result:[SERVERPOWERRESULT]BCM2 /
PMC

Server Monitoring >Power control initiatedUser '[USERNAME]' initiated a power control
operation for '[MONITOREDHOST]':[SERVERPOWEROPERATION]

BCM2 /PMC

BCM2 /PMC

BCM2 /
PMC
Sensor '[POWERMETERSENSOR]' on
power meter '[POWERMETER]' is nolonger unavailable; it is now[SENSORSTATENAME].

Server '[MONITOREDHOST]' is nolonger being monitored.

BCM2 /PMC

BCM2 /
PMC

313

Server Monitoring >Unreachable

Server '[MONITOREDHOST]' is unreachable.

Server Monitoring >Unrecoverable

Connection to server '[MONITOREDHOST]'
could not be restored.

Test > Test Event

A test event was triggered by user'[USERNAME]'.

Server '[MONITOREDHOST]' isreachable.

BCM2 /
PMC

Timer Event > Occurred Timer event '[EVENTRULENAME]' occurred.
User Activity > User
User '[USERNAME]' from host '[USERIP]'
accepted the Restrictedaccepted the Restricted Service Agreement.
Service Agreement

314

User Activity >Authentication failure

Authentication failed for user '[USERNAME]'
from host '[USERIP]'.

User Activity > Userlogon state

User '[USERNAME]' from host '[USERIP]'
logged in.

User Activity > Session
timeout

Session of user '[USERNAME]' from host'[USERIP]' timed out.

User Activity > User
blockedUser '[USERNAME]' from host '[USERIP]' wasblocked.

User Administration >Password changed

Password of user '[UMTARGETUSER]' changed
by user '[USERNAME]' from host '[USERIP]'.

User Administration >Password settingschangedPassword settings changed by user'[USERNAME]' from host '[USERIP]'.

User Administration >Role added

Role '[UMTARGETROLE]' added by user'[USERNAME]' from host '[USERIP]'.

User Administration >Role deleted

Role '[UMTARGETROLE]' deleted by user'[USERNAME]' from host '[USERIP]'.

User Administration >Role modified

Role '[UMTARGETROLE]' modified by user'[USERNAME]' from host '[USERIP]'.

User Administration >User added

User '[UMTARGETUSER]' added by user'[USERNAME]' from host '[USERIP]'.

User Administration >User deleted

User '[UMTARGETUSER]' deleted by user'[USERNAME]' from host '[USERIP]'.

User Administration >User modified

User '[UMTARGETUSER]' modified by user'[USERNAME]' from host '[USERIP]'.

User Administration >User renamed

User '[UMTARGETUSER]' renamed to'[NEWUMTARGETUSER]' by user'[USERNAME]' from host '[USERIP]'.

BCM2 /
PMC

User '[USERNAME]' from host'[USERIP]' declined the Restricted
Service Agreement.

User '[USERNAME]' from host'[USERIP]' logged out.

Webcam Management> Image upload started

A snapshot upload of webcam'[WEBCAMNAME]' to folder[WEBCAMSNAPSHOTFOLDERURL] was started.

Webcam Management> Webcam attached

Webcam '[WEBCAMNAME]'('[WEBCAMMODEL]') added to port'[WEBCAMUSBPORT]'.

Webcam Management> Webcam detached

Webcam '[WEBCAMNAME]'('[WEBCAMMODEL]') removed from port'[WEBCAMUSBPORT]'.

Webcam Management> Webcam settingschangedWebcam '[WEBCAMNAME]' settings changed
by user '[USERNAME]'

Available Actions
There are several built-in actions, which cannot be deleted. You can create additional actions forresponding to different events.
Some actions have messages that you can customize using placeholders that will populate with specificinformation when the message is generated. Custom messages with placeholders can be used in theseactions: Log event message, Send SMS, Send email (subject+body), Send webcam image (subject+body).

▶ To test an action:•

Click the Test button next to the Action. The action is triggered and you can verify it.

▶ Built-in actions:•

System Event Log Action:•

This action records the selected event in the internal log when the event occurs.
System SNMP Notification Action:
This action sends SNMP notifications to one or multiple IP addresses after the selected
event occurs.

315Note: No IP addresses are specified for this notification action by default so you must enter IP
addresses before applying this action to any event rule. Any changes made to the 'SNMP
Notifications' section on the SNMP page will update the settings of the System SNMP Notification
Action, and vice versa.
•

System Tamper Alarm:This action causes the PX-Series PDU to show the alarm for the tamper sensor, if any, on
the Dashboard page until a person acknowledges it. By default, this action has been
assigned to the built-in tamper detection event rules.

▶ Actions you can create:
1. Choose Device Settings > Event Rules > New Action.
2. Click the Action field to select an action type from the list.

3. Available actions depend on your model. See next sections for details on each action you canconfigure.
4. Click Create to save an action, then you can include it in an event rule.

Alarm
The Alarm is an action that requires users to acknowledge an alert. This helps ensure that the user isaware of the alert.
If the Alarm action has been included in a specific event rule and no one acknowledges that alert after it
occurs, the PX-Series PDU resends or regenerates an alert notification regularly until the alert isacknowledged or the maximum number of alert notifications is sent. You can acknowledge an alert in
the Dashboard.

▶ Operation:
1. Choose Device Settings > Event Rules >.
2. Select Alarm from the Action list.
3. In the Alarm Notifications list box, specify one or multiple ways to issue the alert notifications.
Available methods vary, depending on how many notification-based actions have been created.
Notification-based action types include:316

▪ External beeper▪ Syslog message▪ Send email▪ Send SMS message▪ Internal beeper
If no appropriate actions are available, create them first.
a. To select any methods, select them one by one in the Available field.
To add all available methods, simply click Select All.
b. To delete any methods, click a method's
4.
5.
6.
7.

in the Selected field.

To remove all methods, simply click Deselect All.
To enable the notification-resending feature, select the 'Enable re-scheduling of alarm notifications'checkbox.
In the 'Re-scheduling period' field, specify the time interval (in minutes) at which the alert
notification is resent or regenerated regularly.
In the 'Re-scheduling limit' field, specify the maximum number of times the alert notification isresent. Values range from 1 to infinite.
(Optional) You can instruct the PX-Series PDU to send the acknowledgment notification after thealarm is acknowledged in the 'Acknowledgment notifications' field. Available methods are identicalto those for generating alarm notifications.
a. In the Available field, select desired methods, or click Select All.
b. In the Selected field, click any method's

to remove unnecessary ones, or click Deselect All.

Action GroupYou can create an action group that performs up to 32 actions. After creating such an action group, you
can easily assign this set of actions to any event rule rather than selecting all needed actions one by one
per rule.
If the needed action is not available yet, create it first.

▶ Operation:
1.
2.
3.
4.

Choose Device Settings > Event Rules >.
Select 'Execute an action group' from the Action list.
Select the actions to include in group from the 'Available actions' list, or click Select All.
To remove any action(s) from the 'Selected actions' field, click it's X.

5. Click Create to save the action.

317

Change Load Shedding StateThe "Change load shedding state" action is available only when your PX-Series PDU is able to control
outlet power. Use this action to activate or deactivate the load shedding mode for responding to a
specific event.

▶ Operation:
1. Choose Device Settings > Event Rules >2. Select 'Change load shedding state' from the Action list.
3. In the Operation field, select either one below:.

• Start load shedding: Enters the load shedding mode when the specified event occurs.
• Stop load shedding: Quits the load shedding mode when the specified event occurs.

External Beeper
If an external beeper is connected, you can change the beeper's behavior or status to respond to acertain event.

▶ To control the connected external beeper:
1.
2.
3.
4.

Choose Device Settings > Event Rules >.
Select 'External beeper' from the Action list.
In the 'Beeper port' field, select the port where the external beeper is connected.
In the 'Beeper action' field, select an action for the external beeper to carry out.
• Alarm: Causes the external beeper to sound an alarm cycle every 20 seconds - stays on for 0.7
seconds and then off for 19.3 seconds.
• On: Turns on the external beeper so that it buzzes continuously.
• Off: Turns off the external beeper so that it stops buzzing.

318

Warning: If you create an event rule for the external beeper but disconnect it when an event causes it
to beep, the beeper no longer beeps after it is re-connected even though the event triggering the
beeping action remains asserted.

Internal Beeper
You can have the built-in beeper of the PX-Series PDU turned on or off when a certain event occurs.

▶ Operation:
1. Choose Device Settings > Event Rules >2. Select 'Internal beeper' from the Action list.
3. Select an option from the Operation field.

.

• Turn beeper on: Turns on the internal beeper to make it buzz.
• Turn beeper off: Turns off the internal beeper to make it stop buzzing.

Log an Event Message
The option 'Log event message' records the selected events in the internal log.
A default log message will be generated for each type of event, or you can create a custom log message.

▶ Operation:
1. Choose Device Settings > Event Rules > New Action.
2. Select 'Log an event message' from the Action list.
3. Select the 'Use custom log message' checkbox, and then create a custom message in the provided
text box.
• To automatically insert message placeholders, open the Custom Log Message Help section. Searchfor placeholders and click to include them in your message.
4. Click Create.

Shut down a Server and Control its PowerThe "Power control server" action is available only when your PX-Series PDU is outlet-switching capable.
You can configure the PX-Series PDU to shut down a specific server and then turn off its outlet(s), or
turn on that server's outlet(s) after a certain event occurs.
The server must be one of the servers being monitored by your PX-Series PDU and the same PX-Series
PDU supplies power to it. See Monitoring Server Accessibility (on page 350) .
Tip: If the server has multiple power cords, make sure all of its power cords are connected to the same
PX-Series PDU and you have created an outlet group for controlling all outlets simultaneously.

319

▶ Operation:
1. Choose Device Settings > Event Rules >2. Select 'Power control server' from the Action list.
3. In the Operation field, select an action for the server.

.

• Power up: Turns on the outlet or outlet group associated with the selected server.
• Graceful shutdown: Shuts down the selected server first and then turn off its associated outlet oroutlet group.
4. Select the server you want in the Server field.
• If PX-Series PDU cannot power control any server, a message 'Power control not configured' isshown in the end of the server's host name or IP address.

Push Out Sensor Readings
You can configure the PX-Series PDU to push sensor log to a remote server after a certain event occurs,
including logs of internal sensors, environmental sensors and actuators.
If you have connected asset strips, you can also configure the PX-Series PDU to push the data to aserver.
Before creating this action, make sure that you have properly defined the destination servers and thedata to be sent on the Data Push page.
Tip: To send the data at a regular interval, schedule this action. Note that the "Asset management log" isgenerated only when there are changes made to any asset strips or asset tags, such as connection or
disconnection events.

▶ Operation:
1. Choose Device Settings > Event Rules >.
2. Select 'Push out sensor readings' from the Action list.
3. Select a server or host which receives the data in the Destination field.
• If the desired destination is not available yet, go to the Data Push page to specify it.

Record Snapshots to Webcam Storage
This option allows you to define an action that starts or stops a specific webcam from taking snapshots.
Per default the snapshots are stored on the PX-Series PDU. It is recommended to specify a remote
server to store as many snapshots as possible.

320

▶ Operation:
1.
2.
3.
4.

Choose Device Settings > Event Rules >.
Select 'Record snapshots to webcam storage' from the Action list.
Select a webcam in the Webcam field.
Select the action to perform - 'Start recording' or 'Stop recording.'

If 'Start recording' is selected, adjust the values of the following:• Number of snapshots - the number of snapshots to be taken when the event occurs.
The maximum amount of snapshots that can be stored on the PX-Series PDU is 10. If you
set it for a number greater than 10 and the storage location is on the PX-Series PDU, after
the 10th snapshot is taken and stored, the oldest snapshots are overwritten. Storing
snapshots on a remote server does not have such a limitation.
• Time before first snapshot - the amount of time in seconds between when the event is triggered
and the webcam begins taking snapshots.
• Time between snapshots - the amount of time in seconds between when each snapshot is taken.
• Folder - names of the folders that will be automatically created to store webcam snapshots after
the recording action is triggered by the rule you will configure.
Note that the Folder field is available only when the selected webcam has been configured
to store its snapshots on an "FTP" server.
Folder nameoptions

Definition

Serial number /Webcam nameTwo folders will be created.
•

The parent folder's name is the serial number of PX-Series PDU.

•

The subfolder's name is the selected webcam's name.

Serial number /Webcam name / Rulename

Three folders will be created.

Serial number /Webcam name /Timestamp

Three folders will be created.

Serial number /Webcam name / Rulename / Timestamp

Four folders will be created.

•

Definitions of the parent folder and first subfolder are the same as the first row.

•

The final subfolder's name is the name of event rule that triggers this recording action.

•

Definitions of the parent folder and first subfolder are the same as the first row.

•

The final subfolder's name is the time when the recording event occurs, which is theaccumulated time in seconds since 1970/1/1.

•

Definitions of the parent folder and first subfolder are the same as the first row.

•

The second subfolder's name is the name of event rule that triggers this recording action.

•

The final subfolder's name is the time when the recording event occurs, which is theaccumulated time in seconds since 1970/1/1.

Serial number /Three folders will be created.
Webcam name /• Definitions of the parent folder and first subfolder are the same as the first row.
Formatted timestamp• The final subfolder's name is the time when the recording event occurs, which is a format
comprising year, month, date, hour, minute, second and timezone.

321

Folder nameoptions

Definition

Serial number /Webcam name / Rulename / Formatted
timestamp

Four folders will be created.
•

Definitions of the parent folder and first subfolder are the same as the first row.

•

The second subfolder's name is the name of event rule that triggers this recording action.

•

The final subfolder's name is the time when the recording event occurs, which is a format
comprising year, month, date, hour, minute, second and timezone.

The timestamp is based on the time you have configured on the PX-Series PDU.
To find the serial number of your PX-Series PDU, go to Maintenance > Device Information.

Send EmailYou can configure emails to be sent when an event occurs and can customize the message.
Messages consist of a combination of free text and placeholders. The placeholders represent
information which is pulled from the PX-Series PDU and inserted into the message.
For example:[USERNAME] logged into the device on [DATETIME]
translates toMary logged into the device on 2022-January-30 21:00▶ Operation:
1. Choose Device Settings > Event Rules >.
2. Select 'Send email' from the Action list.
3. In the 'Recipient email addresses' field, specify the email address(es) of the recipient(s). Use acomma to separate multiple email addresses.
4. By default, the SMTP server specified on the SMTP Server page will be the SMTP server for
performing this action.
To use a different SMTP server, select the 'Use custom settings' radio button.
Default messages are sent based on the event.
5. If needed, you can customize the subject and messages sent via this email.
• Select the 'Custom subject' checkbox, and enter the text you prefer as this email's subject.
• Select the 'Use custom log message' checkbox, and then create a custom message up to 1024
characters in the provided field.
• To automatically insert message placeholders, open the Custom Log Message Help section. Searchfor placeholders and click to include them in your message.
6. Click Create.

322

Send Sensor Report
You may set the PX-Series PDU so that it automatically reports the latest readings or states of one or
multiple sensors by sending a message or email or simply recording the report in a log. These sensors
can be either internal or environmental sensors listed below.
•

Inlet sensors, including RMS current, RMS voltage, active power, apparent power, power factor andactive energy.

•

Outlet sensors, including RMS current, RMS voltage, active power, apparent power, power factor,
active energy and outlet state (for outlet-switching capable PDUs only).

•

Overcurrent protector sensors, including RMS current and tripping state.

•

Peripheral device sensors, which can be any environmental sensor packages connected to the PXSeries PDU, such as temperature or humidity sensors.

SeeSend Sensor Report Example (on page 330).

▶ Operation:
1. Choose Device Settings > Event Rules >.
2. Select 'Send sensor report' from the Action list.
3. In the 'Destination actions' section, select the method(s) to report sensor readings or states. The
number of available methods varies, depending on how many messaging actions have been created.
The messaging action types include:• Log event message• Syslog message• Send email• Send SMS message
4. If no messaging actions are available, create them now.
5. In the 'Available sensors' field, select the desired target's sensor.
a. Click the firstb. Click the second

to select a target component from the list.

to select the specific sensor for the target from the list.

323

c. Clickto add the selected sensor to the Report Sensors list box.

For example, to monitor the current reading of the Inlet 1, select Inlet 1 from the left
field, and then select RMS Current from the right field.
6. To report additional sensors simultaneously, repeat the above step to add more sensors.

• To remove any sensor from the 'Report sensors' list box, select it and click
multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.

. To make7. To immediately send out the sensor report, click Send Report Now.
Tip: When intending to send a sensor report using custom messages, use the placeholder[SENSORREPORT] to report sensor readings.

Send SMS Message
You can configure SMS messages to be sent when an event occurs and can customize the message.
A supported modem, such as the Cinterion® GSM MC52i modem, must be plugged into the PX-Series
PDU in order to send SMS messages.
Note: The PX-Series PDU cannot receive SMS messages.
Only the 7-bit ASCII charset is supported for SMS messages. Messages consist of a combination of freetext and placeholders. The placeholders represent information retrieved from the device and inserted
into the message. For example:[USERNAME] logged into the device on [TIMESTAMP]

324

translates toMary logged into the device on 2012-January-30 21:00▶ Operation:
1.
2.
3.
4.

Choose Device Settings > Event Rules >.
Select 'Send SMS message' from the Action list.
In the 'Recipient phone number' field, specify the phone number of the recipient.
Select the 'Use custom log message' checkbox, and then create a custom message in the provided
text box.

• To automatically insert message placeholders, open the Custom Log Message Help section. Searchfor placeholders and click to include them in your message.
5. Click Create.

Send Snapshots via EmailThis option notifies one or multiple persons for the selected events by emailing snapshots or videos
captured by a connected Logitech® webcam.

▶ Operation:
1. Choose Device Settings > Event Rules >.
2. Select 'Send snapshots via email' from the Action list.
3. In the 'Recipient email addresses' field, specify the email address(es) of the recipient(s). Use acomma to separate multiple email addresses.
4. By default, the SMTP server specified on the SMTP Server page will be the SMTP server for
performing this action.
To use a different SMTP server, select the 'Use custom SMTP server' checkbox. The fields forcustomized SMTP settings appear.
5. Select the webcam that is capturing the images you want sent in the email.
6. Adjust the values of the following:• Number of snapshots - the number of snapshots to be taken when the event occurs. For example,
you can specify 10 images be taken once the event triggers the action.
• Snapshots per mail - the number of snapshots to be sent at one time in the email.
• Time before first snapshot - the amount of time in seconds between when the event is triggered
and the webcam begins taking snapshots.
• Time between snapshots - the amount of time in seconds between when each snapshot is taken.
7. If needed, you can customize the subject and messages sent via this email.

325

• Select the 'Custom subject' checkbox, and enter the text you prefer as this email's subject.
• Select the 'Use custom log message' checkbox, and then create a custom message up to 1024
characters in the provided field.
• To automatically insert message placeholders, open the Custom Log Message Help section. Searchfor placeholders and click to include them in your message.
8. Click Create.

Send an SNMP Notification
This option sends an SNMP notification to one or multiple SNMP destinations.

▶ Operation:
1. Choose Device Settings > Event Rules >.
2. Select 'Send SNMP notification' from the Action list.
3. Select the type of SNMP notification. See either procedure below according to your selection.

▶ To send SNMP v2c notifications:
1. In the 'Notification type' field, select 'SNMPv2c trap' or 'SNMPv2c inform.'
2. For SNMP INFORM communications, leave the resend settings at their default or do the following:a. In the Timeout field, specify the interval of time, in seconds, after which a new inform
communication is resent if the first is not received. For example, resend a new inform
communication once every 3 seconds.
b. In the 'Number of retries' field, specify the number of times you want to re‑send the inform
communication if it fails. For example, inform communications are re‑sent up to 5 times when
the initial communication fails.
3. In the Host fields, enter the IP address of the device(s) you want to access. This is the address towhich notifications are sent by the SNMP system agent.
4. In the Port fields, enter the port number used to access the device(s).
5. In the Community fields, enter the SNMP community string to access the device(s). The community
is the group representing the PX-Series PDU and all SNMP management stations.
Tip: An SNMP v2c notification action permits only a maximum of three SNMP destinations. To assign
more than three SNMP destinations to a specific rule, first create several SNMP v2c notification actions,each of which contains completely different SNMP destinations, and then add all of these SNMP v2c
notification actions to the same rule.

326

▶ To send SNMP v3 notifications:
1. In the 'Notification type' field, select 'SNMPv3 trap' or 'SNMPv3 inform.'
2. For SNMP TRAPs, the engine ID is prepopulated.
3. For SNMP INFORM communications, leave the resend settings at their default or do the following:a. In the Timeout field, specify the interval of time, in seconds, after which a new inform
communication is resent if the first is not received. For example, resend a new inform
communication once every 3 seconds.
b. In the 'Number of retries' field, specify the number of times you want to re‑send the inform
communication if it fails. For example, inform communications are re‑sent up to 5 times when
the initial communication fails.
4. For both SNMP TRAPS and INFORMS, enter the following as needed and then click OK to apply thesettings:a. Host nameb. Port number
c. User ID for accessing the host -- make sure the User ID has the SNMPv3 permission.
d. Select the host security level
Security level

Description"noAuthNoPriv" Select this if no authorization or privacy protocols areneeded.
"authNoPriv""authPriv"

Select this if authorization is required but no privacy
protocols are required.
•Select the authentication protocol - MD5 or SHA•

Enter the authentication passphrase and then confirm
the authentication passphrase

Select this if authentication and privacy protocols are
required.
•

Select the authentication protocol - MD5 or SHA•

Enter the authentication passphrase and confirm theauthentication passphrase•

Select the Privacy Protocol - DES or AES•

Enter the privacy passphrase and then confirm theprivacy passphrase

Start or Stop a Lua Script
If you have created or loaded a Lua script file into the PX-Series PDU, you can have that script
automatically run or stop in response to a specific event.
See Lua Scripts (on page 360).

327

▶ To automatically start or stop a Lua script:
1.
2.
3.
4.

Choose Device Settings > Event Rules >.
Select 'Start/stop Lua script' from the Action list.
In the Operation field, select 'Start script' or 'Stop script.'
In the Script field, select the script that you want it to be started or stopped when an event occurs.
Scripts must be pre-loaded.
5. To apply different arguments than the default, do the following. Note that the newly-added
arguments will override this script's default arguments.
a. Click Add Argument.
b. Type the key and value.

▪ To remove any existing argument, click

adjacent to it.

Switch Outlet GroupThe "Switch outlet group" action is available only when your PX-Series PDU is outlet-switching capable.
This action turns on, off or power cycles a specific outlet group.

▶ Operation:
1.
2.
3.
4.

Choose Device Settings > Event Rules >.
Select 'Switch outlet group' from the Action list.
To specify the outlet group where this action will be applied, select it from the 'Group to switch' list.
In the Operation field, select an operation for the selected outlet group.
• Turn on all outlets in group: Turns on the selected outlet group.
• Turn off all outlets in group: Turns off the selected outlet group.
• Cycle all outlets in group: Cycles power to the selected outlet group.

Switch Outlets
The "Switch outlets" action is available only when your PX-Series PDU is outlet-switching capable. Thisaction turns on, off or power cycles a specific outlet.

▶ Operation:
1. Choose Device Settings > Event Rules >.
2. Select 'Switch outlets' from the Action list.
3. In the Operation field, select an operation for the selected outlet(s).
• Turn outlet on: Turns on the selected outlet(s).
• Turn outlet off: Turns off the selected outlet(s).
• Cycle outlet: Cycles power to the selected outlet(s).

328

4. To specify the outlet(s) where this action will be applied, select them one by one from the 'Available
outlets' list.
• To add all outlets, click Select All.
5. To remove any outlets from the 'Selected outlets' field, click that outlet's.
6. If 'Turn outlet on' or 'Cycle outlet' is selected, choose to select the 'Use sequence order and delays'
checkbox so that all selected outlets will follow the power-on sequence defined on the Outlets page.

Switch Peripheral Actuator
If you have any actuator connected to the PX-Series PDU, you can set up the PX-Series PDU so it
automatically turns on or off the system controlled by the actuator when a specific event occurs.

▶ Operation:
1. Choose Device Settings > Event Rules >.
2. Select 'Switch peripheral actuator' from the Action list.
3. In the Operation field, select an operation for the selected actuator(s).
• Turn on: Turns on the selected actuator(s).
• Turn off: Turns off the selected actuator(s).
4. To select the actuator(s) where this action will be applied, select them one by one from the'Available actuators' list.
• To add all actuators, click Select All.
5. To remove any selected actuator from the 'Selected actuators' field, click that actuator's.

Syslog Message
Use this action to automatically forward event messages to the specified syslog server. Determine thesyslog transmission mechanism you prefer when setting it up - UDP, TCP or TLS over TCP.
PX-Series PDU may or may not detect the syslog message transmission failure. If yes, it will log thissyslog failure as well as the failure reason in the event log.

▶ Operation:
1.
2.
3.
4.

Choose Device Settings > Event Rules > New Action.
Select 'Syslog message' from the Action list.
In the 'Syslog server' field, specify the IP address to which the syslog is forwarded.
In the 'Transport protocol' field, select one of the syslog protocols: TCP, UDP or TCP+TLS. The default
is UDP.

Transport
protocols
UDP
TCP

Next steps•

In the 'UDP port' field, type an appropriate port number. Default is 514.

•

Select the 'Legacy BSD syslog protocol' checkbox if applicable.

NO TLS certificate is required. Type an appropriate port number in the 'TCP port' field.

329

Transport
protocols

Next steps
A TLS certificate is required. Do the following:a. Type an appropriate port number in the 'TCP port' field. Default is 6514.
b. In the 'CA certificate' field, click Browse to select a TLS certificate. After importing thecertificate, you may:
• Click Show to view its contents.
TCP+TLS• Click Remove to delete it if it is inappropriate.
c. Determine whether to select the 'Allow expired and not yet valid certificates' checkbox.
• To always send the event message to the specified syslog server as long as a TLS
certificate is available, select this checkbox.
• To prevent the event message from being sent to the specified syslog server when any
TLS certificate in the selected certificate chain is outdated or not valid yet, deselect thischeckbox.

Scheduling an Action
An action can be regularly performed at a preset time interval instead of being triggered by a specific
event. For example, you can make the PX-Series PDU report the reading or state of a specific sensor
regularly by scheduling the "Send sensor report" action.
When scheduling an action, make sure you have a minimum of 1-minute buffer between this action's
creation and first execution time. Otherwise, the scheduled action will NOT be performed at the
specified time when the buffer time is too short. For example, if you want an action to be performed at
11:00 am, you should finish scheduling it at 10:59 am or earlier.

▶ Operation:
1. Choose Device Settings > Event Rules >.
2. To select any action(s), select them one by one from the 'Available actions' list.
• To select all available actions, click Select All.
3. To remove any action(s) from the 'Selected actions' field, click that action's.

• To remove all actions, click Deselect All.
4. Select the desired frequency in the 'Execution time' field, and then specify the time interval or a
specific date and time in the field(s) that appear. Use the clock and calendar tools to choose theschedule. Use the AM/PM button to toggle time settings.

Send Sensor Report Example
To create a scheduled action for emailing a temperature sensor report hourly, it requires:

330•

A 'Send email' action•

A 'Send sensor report' action•

A timer - that is, the scheduled action▶ Steps:
1. Click
recipient(s).

to create a 'Send email' action that sends an email to the desired• In this example, this action is named Email a Sensor Report.
• The subject and content of this email can be customized.

Clickto create a 'Send sensor report' action that includes the 'Email a Sensor
Report' action as its destination action.
•

In this example, this action is named Send Temperature Sensor Readings.

•

You can specify more than one temperature sensor as needed in this action.

331

1. ClickSensor Readings' action hourly.

332

to create a timer for performing the 'Send Temperature•

In this example, the timer is named Hourly Temperature Sensor Reports.

•

To perform the specified action at 12:30 pm, 01:30 pm, 02:30 pm, and so on, select Hourly, and set
the Minute to 30.

•An email containing the specified temperature sensor readings will be sent hourly every day. If you
no longer need the report, you can disable the timer by clearing the Enabled checkbox.

Placeholders for Custom Messages
Actions that include messages allow you to customize text and include placeholders that retrieve system
information and include it in the message.
Supported actions:•

Send email•

Send snapshots via email•

Send SMS•

Log event message

The following are placeholders that can be used in custom messages. Because the placeholders employ
square brackets, you must precede with a backslash any other square brackets that must be included inyour message. For example, \[ \].
If a placeholder is used in a situation where the information cannot be retrieved, it will be shown as"unknown" in the message.
Placeholder

Definition[AMSBLADESLOTPOSITION]

The (horizontal) slot position inside a blade extension[AMSLEDCOLOR]The RGB LED color[AMSLEDMODE]

The LED indication mode

[AMSLEDOPMODE]

The LED operating mode

[AMSNAME]

The name of an asset strip[AMSNUMBER]

The numeric ID of an asset strip

333

Placeholder

Definition[AMSRACKUNITPOSITION]

The (vertical) rack unit position[AMSSTATE]

The human-readable state of an asset strip[AMSTAGID]

The asset tag ID[CARDREADERCHANNEL]

The channel number of a card reader[CARDREADERDESCRIPTION]

The custom description of a card reader[CARDREADERID]

The id of a card reader[CARDREADERMANUFACTURER] The manufacturer of a card reader

334[CARDREADERNAME]

The custom name of a card reader[CARDREADERPRODUCT]The product name of a card reader[CARDREADERSERIALNUMBER]

The serial number of a card reader[COMPONENTID]

The ID of a hardware component[CONFIGPARAM]

The name of a configuration parameter[CONFIGVALUE]

The new value of a parameter[DATETIME]

The human readable timestamp of the event occurrence[DEVICEIP]

The IP address of the device the event occurred on[DEVICENAME]

The name of the device the event occurred on[DEVICESERIAL]

The unit serial number of the device the event occurred on[DIPSWELLDURATION]

The formatted duration of the dip/swell event in seconds[DIPSWELLVOLTAGE]

The formatted minimum/maximum voltage during the dip/swell event in
volts[DOORACCESSDENIALREASON]

The reason for the door access being denied[DOORACCESSRULEID]

The id of a door access rule

[DOORACCESSRULENAME]

The name of a door access rule

[ERRORDESC]

The error message[EVENTRULENAME]

The name of the matching event rule

[EXTPORTNAME]

The name of an external port

[EXTSENSOR]

The peripheral device identifier[EXTSENSORNAME]

The name of a peripheral device[EXTSENSORSLOT]The ID of a peripheral device slot

Placeholder

Definition[FAILURETYPE]

The numeric hardware failure type

[FAILURETYPESTR]

The textual hardware failure type[FUSESTATENAME]

The human readable state of a fuse

[IFNAME]

The human readable name of a network interface[INLET]

The inlet label[INLETLINEPAIR]

The inlet line pair identifier[INLETPOLE]

The inlet power line identifier[INLETSENSOR]

The inlet sensor name

[ISASSERTED]

Boolean flag whether an event condition became true (1) or false (0)[KEYPADCHANNEL]

The channel number of a keypad[KEYPADDESCRIPTION]

The custom description of a keypad[KEYPADID]

The id of a keypad[KEYPADMANUFACTURER]

The manufacturer of a keypad[KEYPADNAME]

The custom name of a keypad[KEYPADPIN]

The PIN entered at a keypad[KEYPADPRODUCT]The product name of a keypad[KEYPADSERIALNUMBER]

The serial number of a keypad[LINKIDTAG]

Link ID prefix for link unit events, empty otherwise[LINKID]

The link ID of a link unit

[LINKUNITHOST]

The host name or IP address of a link unit

[LOGMESSAGE]The original log message[MONITOREDHOST]

The name or IP address of a monitored host

[NETAUTHRESULTSTR]

The network authentication result string ('succeeded' or 'failed')[NEWUMTARGETUSER]

The new target user of a user rename operation[OCP]

The overcurrent protector label[OCPSENSOR]

The overcurrent protector sensor name

[OCPTRIPCAUSELABEL]

The label of the outlet that likely caused the OCP trip

[OCPTRIPCURRENT]

The current flow before the trip event

335

Placeholder

Definition[OLDDATETIME]

The device date and time before a clock change[OLDVERSION]

The firmware version the device is being upgraded from[OUTLET]The outlet label[OUTLETGROUPID]

The outlet group ID[OUTLETGROUPNAME]

The outlet group name

[OUTLETGROUPSENSOR]

The outlet group sensor name

[OUTLETNAME]

The outlet nameNote: If any outlet does not have a name, neither an outlet namenor an outlet number will be shown in the custom message for it.
Therefore, it is recommended to check the availability of all outlet
names if intending to use this placeholder.

336[OUTLETPOLE]

The outlet power line identifier[OUTLETSENSOR]

The outlet sensor name

[PDULINEPAIRSENSOR]

The sensor name for a certain line pair

[PDUNUMBER]

The PDU number in a cascade[PDUPOLESENSOR]

The sensor name for a certain power line

[PDUSENSOR]

The PDU sensor name

[PERIPHDEVPOSITION]

The position of an attached peripheral device[PHONENUMBER]

The destination phone number of an outgoing SMS message[PORTID]

The label of the external port the event-triggering device is connected to[PORTTYPE]

The type of the external port (e.g. 'feature' or 'auxiliary') the eventtriggering device is connected to[RADIUSERRORDESC]

The Radius error message[ROMCODE]The romcode of an attached peripheral device[SENSORREADING]

The value of a sensor reading[SENSORREADINGUNIT]

The unit of a sensor reading[SENSORREPORT]The formatted sensor report contents[SENSORSTATENAME]

The human readable state of a sensor[SENSORTHRESHOLDNAME]

The name of the threshold being crossedPlaceholder

Definition[SENSORTHRESHOLDVALUE]

The value of the threshold being crossed[SERVERPOWEROPERATION]

The power control operation that was initiated on a server (on/off)[SERVERPOWERRESULT]The result of a power control operation[SMARTCARDID]

The id of a smart card

[SMARTCARDTYPE]

The type of a smart card

[SMTPRECIPIENTS]

The list of recipients of an outgoing mail

[SMTPSERVER]

The name or IP address of an SMTP server[SYSCONTACT]SNMP MIB-II sysContact field[SYSLOCATION]

SNMP MIB-II sysLocation field[SYSNAME]

SNMP MIB-II sysName field[TIMEREVENTID]

The id of a timer event[TIMESTAMP]

The timestamp of the event occurrence[UMTARGETROLE]

The target role of a user management operation[UMTARGETUSER]

The target user of a user management operation[USERIP]The IP address a user connected from[USERNAME]

The user who performed an operation[VERSION]

The firmware version the device is upgrading to

Editing or Deleting a Rule/Action
You can change the settings of an event rule, action or scheduled action, or delete them.
Exception: Some settings of the built-in event rules or actions are not user-configurable. You cannot
delete built-in rules and actions.

337▶ To edit or delete an event rule, action or scheduled action:
1. Choose Device Settings > Event Rules.
2. Click an item in the list of rules, actions or scheduled actions to open its page.
• To modify settings, make changes and then click Save.
• To delete it, click the Delete icon then confirm.

Sample Event Rules
Sample PDU-Level Event RuleIn this example, we want the PX-Series PDU to record the firmware upgrade failure in the internal log
when it happens.
The event rule involves:•

Event: Device > Firmware update failed•

Action: System Event Log Action▶ To create this PDU-level event rule:
1. For an event at the PDU level, select "Device" in the Event field.
2. Select "Firmware update failed" so that the PX-Series PDU responds to the event related to firmware
upgrade failure.
3. To make PX-Series PDU record the firmware update failure event in the internal log, select "System
Event Log Action" in the 'Available actions' field.

Sample Outlet-Level Event RuleIn this example, we want the PX-Series PDU to send SNMP notifications to the SNMP manager for any
sensor change event of outlet 3.

338

The event rule involves:•

Event: Outlet > Outlet 3 > Sensor > Any sub-event•

Action: System SNMP Notification Action▶ To create this outlet-level event rule:
1. For an event at the outlet level, select "Outlet" in the Event field.
2. Select "Outlet 3" because that is the desired outlet.
3. Select "Sensor" to refer to sensor-related events.
4. Select "Any sub-event" to include all events related to all sensors of this outlet and all thresholds,
such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold,lower warning threshold, and so on.
5. To make PX-Series PDU send SNMP notifications, select "System SNMP Notification Action" in the'Available actions' field.
Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for
the System SNMP Notification Action. See Enabling and Configuring SNMP.

Then the SNMP notifications are sent when:• Any numeric sensor's reading enters the warning or critical range.
• Any sensor reading or state returns to normal.
• Any sensor becomes unavailable.
• The active energy sensor is reset.
• Any state sensor changes its state.
For example, when the outlet 3's voltage exceeds the upper warning threshold, the SNMP
notifications are sent, and when the voltage drops below the upper warning threshold, the
SNMP notifications are sent again.

339

Sample Inlet-Level Event RuleIn this example, we want the PX-Series PDU to send SNMP notifications to the SNMP manager for any
sensor change event of the Inlet I1.
The event rule involves:•

Event: Inlet > Sensor > Any sub-event•

Action: System SNMP Notification Action▶ To create the above event rule:
1. For an event at the inlet level, select "Inlet" in the Event field.
2. Select "Sensor" to refer to sensor-related events.
3. Select "Any sub-event" to include all events related to all sensors of this inlet and all thresholds,
such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold,lower warning threshold, and so on.
4. To make the PX-Series PDU send SNMP notifications, select "System SNMP Notification Action" in
the 'Available actions' box.
Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for
the System SNMP Notification Action. See Enabling and Configuring SNMP.

Then the SNMP notifications are sent when:• Any numeric sensor's reading enters the warning or critical range.
• Any sensor reading or state returns to normal.
• Any sensor becomes unavailable.
• The active energy sensor is reset.
For example, when the Inlet I1's voltage exceeds the upper warning threshold, the SNMP
notifications are sent, and when the voltage drops below the upper warning threshold, the
SNMP notifications are sent again.

340

Sample Environmental-Sensor-Level Event Rule
This section applies to outlet-switching capable models only.
In this example, we want PX-Series PDU to activate the load shedding function when a contact closure
sensor enters the alarmed state. This event rule requires creating a new action before creating the rule.

▶ Step 1: create a new action for activating the load shedding
1.
2.
3.
4.

Choose Device Settings > Event Rules >.
In this illustration, assign the name "Activate Load Shedding" to the new action.
In the Action field, select "Change load shedding state."
In the Operation field, select "Start load shedding."

5. Click Create.
After the new action is created, follow the procedure below to create an event rule that triggers theload shedding mode when the contact closure sensor enters the alarmed state. This event rule involves
the following:•

Event: Peripheral Device Slot > Slot 1 > State Sensor/Actuator > Alarmed/Open/On•

Trigger condition: Alarmed•

Action: Activate Load Shedding341

▶ Step 2: create the contact closure-triggered load shedding event rule
1. Clickon the Event Rules page.
2. In this illustration, assign the name "Contact Closure Triggered Load Shedding" to the new rule.
3. In the Event field, select "Peripheral Device Slot" to indicate we are specifying an event related tothe environmental sensor package.
4. Select the ID number of the desired contact closure sensor. In this illustration, the ID number of thedesired contact closure sensor is 1, so select Slot 1.
Note: ID numbers of all sensors/actuators are available on the Peripherals page.
5. Select "State Sensor/Actuator" because the contact closure sensor is a state sensor.
6. Select "Alarmed" since we want the PX-Series PDU to respond when the selected contact closure
sensor changes its state related to the "alarmed" state.
7. In the 'Trigger condition' field, select the Alarmed/Open/On radio button so that the action is taken
only when the contact closure sensor enters the alarmed state.
8. Select "System Event log Action" from the 'Available actions' list.

A Note about Infinite Loop
You should avoid building an infinite loop when creating event rules.

342

The infinite loop refers to a condition where the PX-Series PDU keeps busy because the action or one of
the actions taken for a certain event triggers an identical or similar event which will result in an action
triggering one more event.

▶ Example 1
This example illustrates an event rule which continuously causes the PX-Series PDU to send out email
messages.
Event selected

Action included

Device > Sending SMTP message failed

Send email▶ Example 2This example illustrates an event rule which continuously causes the PX-Series PDU to send out SMTP
messages when one of the selected events listed on the Device menu occurs. Note that <Any subevent> under the Device menu includes the event "Sending SMTP message failed."
Event selected

Action included

Device > Any sub-event

Send email▶ Example 3This example illustrates a situation where two event rules combined regarding the outlet state changes
causes the PX-Series PDU to continuously power cycle outlets 1 and 2 in turn.
Event selected

Action included

Outlet > Outlet 1 > Sensor > Outlet State > On/Off >Both (trigger condition)

Cycle Outlet 2

Outlet > Outlet 2 > Sensor > Outlet State > On/Off >Both (trigger condition)

Cycle Outlet 1(Switch outlets --> Cycle Outlet --> Outlet 2)(Switch outlets --> Cycle Outlet --> Outlet 1)

A Note about Untriggered Rules
In some cases, a measurement exceeds a threshold causing an alert. The measurement then returns toa value within the threshold, but the PX-Series PDU does not generate an alert message for the
Deassertion event. Such scenarios can occur due to the hysteresis tracking the PX-Series PDU uses. See"To De-assert" and Deassertion Hysteresis.

343

Setting Data Logging
The data log stores records of each internal sensor's readings. You can configure the log capacity andthe frequency that measurements are taken and stored. The total size of the data log is limited due tomemory constraints. For example, for a PDU with 500 sensors, the effective log size cannot be morethan 200 records. A log capacity warning appears if the desired log capacity is higher than the effective
log capacity.
You can configure how often measurements are written into the data log using the Measurements Per
Log Entry field. Since the internal sensors are measured every second, specifying a value of 60, forexample, would cause measurements to be written to the data log once every minute. Whenevermeasurements are written to the log, three values for each sensor are written: the average, minimum
and maximum values. For example, if measurements are written every minute, the average of all
measurements that occurred during the preceding 60 seconds along with the minimum and maximum
measurement values are written to the log.
The device's SNMP agent must be enabled. In addition, using an NTP time server ensures accurately
time-stamped measurements.
By default, data logging is enabled. You must have the "Administrator Privileges" or "Change Pdu, Inlet,
Outlet & Overcurrent Protector Configuration" permissions to change the setting.
Important: The third-party management solutions like PowerIQ rely on the data logging feature, and thesettings should be changed only in accordance with those systems' requirements.

▶ To configure the data logging feature:
1.
2.
3.
4.
5.

Choose Device Settings > Data Logging.
To enable the data logging feature, select the "Enable" checkbox in the General Settings section.
Measurements Per Log Entry: Valid range is from 1 to 600. The default is 60.
Log capacity: Valid range varies, from 60 to 20,000.
Enable data log backup: Select this checkbox to enable an automatic USB backup of your data log.
USB stick with specially configured file required, see procedure below.
6. Verify that all sensor logging is enabled. If not, click Enable All at the bottom of the page to have allsensors selected.
7. Click Save.

344

▶ Enable Data Log Backup:
This feature allows backup of the data log on a USB drive. When the PX-Series PDU reboots, e.g becauseof a power outage, it will repopulate the data log from the backup on the USB Stick.
To Prepare USB:
Before connecting a USB drive to the PX-Series PDU, configure a file with these details:
1. Create a text file containing:• user=<admin_username>• password=<admin_user_password>• destroy_and_format_for_storage=true
2. Save the file as "fwupdate.cfg" on the USB drive.
3. Make sure the Enable Data log backup checkbox is selected in Device Settings > Data Logging.
4. Connect the USB drive to the device.

345

On the console of the PX-Series PDU, you will see the USB drive is reformatted and existing
contents are removed. Once formatting is done, data is started to be backed up on the USB.
Note: Backed up data on the USB is in encrypted form.

Configuring Data Push Settings
You can push the sensor or asset strip data to a remote server for data synchronization. The destination
and authentication for data push have to be configured properly on the PX-Series PDU.
The data will be sent in JSON format using HTTP POST requests. Each push message contains exactly one
JSON object. The data format is formally defined in IDL files, sharing several definitions from the JSONRPC data model. IDL files are available by launching JSON‑RPC online help, which is available on the
Support site for your product.
After configuring the destination and authentication settings, do either or both of the following:•

To perform the data push after the occurrence of a certain event, create the data push action andassign it to an event rule.

•

To push the data at a regular interval, schedule the data push action.

▶ To configure data push settings:
1. Choose Device Settings > Data Push.
2. To specify a destination, click
3. Set up the URL field.

.

a. Select http or https.
b. Type the URL or host name in the accompanying text box.
4. If selecting https, a CA certificate is required for making the connection. Click Browse to install it.
Then you can:• Click Show to view the certificate's content.
• Click Remove to delete the installed certificate if it is inappropriate.
5. If the destination server requires authentication, select the 'Use authentication' checkbox, and enter
the following data.
• User name comprising up to 64 characters• Password comprising up to 128 characters
6. In the 'Entry type' field, determine the data that will be transmitted.

346

• Asset management tag list: Transmit the information of the specified asset strip(s), including thegeneral status of the specified strip(s) and a list of asset tags. The asset tags list also includes thetags on blade extension strips, if any.
• Asset management tag log: Transmit the log of all asset strips, which is generated when there arechanges made to asset tags and asset strips, including asset tag connection or disconnection
events.
• Sensor log: Transmit the record of all logged sensors, including their sensor readings and/or status.
Logged sensors refer to all internal and/or environmental sensors/actuators that you have selectedon the Data Logging page.
7. If 'Asset management tag list' is selected in the above step, specify the asset strip(s) whose
information to send. Depending on your PDU model, only one strip may be available.
• To specify the asset strip(s), select them one by one from the Available AMS Ports list. Or click
Select All to add all.
• To remove the asset strip(s), click that asset strip's
in the Selected AMS Ports field. Or click
Deselect All to remove all.
8. Click Create.
9. Repeat the same steps for additional destinations. Up to 64 destinations are supported.

▶ To immediately push out the data:
1. On the Data Push page, choose the data source you want to push out.
2. Click the Push Now button.

▶ To cancel a data push:•

You can cancel the push in progress: Click Cancel.

▶ To modify or delete data push settings:
1. On the Data Push page, click the one you want in the list.
2. Perform either action below.
• To modify settings, make necessary changes and then click Save.
• To delete it, click, and then confirm it on the confirmation message.

Data Push Format Examples
Sensor Log
The root object of the message is a SensorLogPushMessage structure. It comprises a list of sensor
descriptors and a list of log rows.

▶ Sensor descriptors:
The sensor descriptor vector contains static information of all logged sensors, including:

347

•

The electrical component a sensor is associated with. For example, an inlet pole or an overcurrent
protector.

•

The sensor's type. For example, RMS current or active energy.

•

Unit and range of the sensor's readings.

▶ Log rows:
Each log row consists of a time stamp (accumulated seconds since 1/1/1970) and a list of log records -one for each logged sensor.
The length and order of the record list is the same as the sensor descriptor vector.

Sensor Descriptors for Inlet Active PowerThe following illustrates a descriptor for an inlet active power sensor.
The metadata field is relevant only to numeric sensors so the readingtype field is displayed twicein the illustration.
The comment beginning with // in each line, is added to the following illustration to help explain it.

Log Rows
The following illustrates log rows with only one sensor record shown.
The actual length and order of log rows will be the same as those of sensors descriptors.
The comment beginning with // in each line, is added to the following illustration to help explain it.

348Asset Management Tag List
The root object of the asset management tag list message is an AssetStripsMessage structure. It
contains current data about all connected asset management strips and tags, which is similar to theillustration below.

349

(Continued)

Asset Management Tag Log
The root object of the asset management log message is an AssetLogPushMessage structure. It
contains a list of tag or strip events since the last successful push.
The comment beginning with // in each line, is added to the following illustration to help explain it.

Monitoring Server Accessibility
You can monitor whether specific IT devices are alive by having the PX-Series PDU continuously pingthem. An IT device's successful response to the ping commands indicates that the IT device is still alive
and can be remotely accessed.

350

This function is especially useful when you are not located in an area with Internet connectivity.
PX-Series PDU can monitor any IT device, such as database servers, remote authentication servers,
power distribution units (PDUs), and so on. It supports monitoring a maximum of 64 IT devices.
To perform this feature, you need the Administrator Privileges.
The default ping settings may not be suitable for monitoring devices that require high connection
reliability so it is strongly recommended that you should adjust the ping settings for optimal results.
In addition, if your PX-Series PDU is outlet switching capable, you can even connect a monitored IT
device to one or multiple outlets of PX-Series PDU and then have PX-Series PDU perform the following
two actions as needed, in addition to monitoring its status:•

First shut down the monitored IT device.

•

After the IT device is shut down, power off the outlet(s) where that device is connected.

Important: Not every IT device can be shut down by PX-Series PDU so it issuggested to verify whether the device can be shut down using a shutdown
command. For example, PX-Series PDU cannot shut down a PDU with a shutdown
command.

▶ To add IT equipment for ping monitoring:
1. Choose Device Settings > Server Reachability.
2. Click.
3. By default, the "Enable ping monitoring for this server" checkbox is selected. If not, select it toenable this feature.
4. Configure the following.
Field

Description

IP address/hostname

IP address or host name of the IT equipment which you
want to monitor.

Number of successful
pings to enable feature

The number of successful pings required to declare thatthe monitored equipment is "Reachable." Valid range is
0 to 200.

Wait time after
successful ping

The wait time before sending the next ping if theprevious ping was successfully responded. Valid range
is 5 to 600 (seconds).

Wait time after
unsuccessful ping

The wait time before sending the next ping if theprevious ping was not responded. Valid range is 3 to600 (seconds).

Number of consecutive
unsuccessful pings for
failureThe number of consecutive pings without any response
before the monitored equipment is declared"Unreachable." Valid range is 1 to 100.

351

FieldDescription

Wait time before
resuming pinging after
failureThe wait time before the PX-Series PDU resumes
pinging after the monitored equipment is declared"Unreachable." Valid range is 1 to 1200 (seconds).

Number of consecutive The number of times the monitored equipment is
failures before disabling declared "Unreachable" consecutively before the PXfeature (0 = unlimited) Series PDU disables the ping monitoring feature for it
and shows "Waiting for reliable connection." Valid
range is 0 to 100.

5. On a PDU with outlet switching capability, there is one more checkbox available -- Power control
enabled.
To be able to shut down and power control the monitored IT device via the Server Reachability
page, enable this checkbox and configure related settings, which are explained in the following
table.
6. Click Create.
7. To add more IT devices, repeat the same steps.

▶ To configure the shutdown and power control settings:
Restriction: To make the power control feature work properly, the power cord(s) of the monitored IT
device must be connected to the same PDU which is monitoring the IT device.
Field

Description

Shutdown
commandThis is the command which is sent to the monitored IT device via
SSH for shutting it down after you press the Shutdown button on
PX-Series PDU.
•

GNU/Linux:

This option sends the GNU/Linux shutdown
command.
•

Windows:

This option sends the Windows shutdown
command.
•

Custom:If the monitored device's system is neither GNU/Linux nor Windows, choose this option to specify aproper shutdown command, which can comprise amaximum of 1024 ASCII characters.

352

FieldDescription

User name,Specify user credentials for logging in to the monitored device via
SSH.

Password•User name:

The name comprises up to 128 non‑empty ASCII
characters.
•

Password:

The password comprises up to 128 ASCII
characters.
SSH port

The monitored device's SSH port.
•

Default is 22.

Power target Select the outlet or outlet group that is powering the monitored
to switch
device.
Method ofchecking
successful
shutdown

This field determines when PX-Series PDU will power off theoutlet(s) that supplies power to the monitored device, after PXSeries PDU issues the shutdown command to that device.
•

Timer:•

PX-Series PDU will power off the selected outlet or outlet
group after the time specified in the 'Timer delay' field
expires.Active power drop:

PX-Series PDU will power off the selected outlet(s)after the active power value of the selected outlet
or outlet group drops below the value specified in
the 'Active power threshold' field.
Note: Number of available methods is model dependent.
The 'Active power drop' method is available only on models
with outlet metering capability.
Timer delayThis field appears for the 'Timer' method.
Valid values range between 5 and 10,000 seconds.
Active power
threshold
The field appears for the 'Active power drop' method.
Valid values range between 0 and 21,000 W.

353

FieldDescription

Timeout for
shutdown
checkThis field appears for the 'Active power drop' method.
Valid values range between 5 and 10,000 seconds.
The power-off operation is performed only when the active power
value of the selected outlet or outlet group drops below the'Active power threshold' within the period of time specified in thisfield.
If the active power value drops below the 'Active power
threshold' after the specified time expires, the power-off
operation will NOT be performed.

Server Status Checking or Power Control
Not all models supports the shutdown and power control features via the Server Reachability page.
After adding IT equipment for monitoring, all IT devices are listed on the Server Reachability page.

In the beginning, the status of the added IT equipment shows "Waiting for reliable connection," whichmeans the requested number of consecutive successful or unsuccessful pings has not reached before
PX-Series PDU can declare that the monitored device is reachable or unreachable.

▶ To check the server monitoring states and results:
1. The column labeled "Ping Enabled" indicates whether the monitoring for the corresponding IT
device is activated or not.
2. The column labeled "Status" indicates the accessibility of monitored equipment.
StatusDescription

Reachable

The monitored equipment is accessible.

Unreachable

The monitored equipment is inaccessible.

Waiting for reliable
connection

The connection between the device and the monitoredequipment is not reliably established yet.

3. If your model supports outlet switching, one more column displays -- Power Control.

354

Power control
statusDescription(disabled)

Power control is not enabled for the monitored equipment.

Server power ison

The outlet or outlet group associated with the monitoredequipment is being powered on.
•Server power isoff

In the scenario where an 'outlet group' is associated with theequipment, the message 'Server power is on' is shown as longas one of the outlets in the outlet group remains powered on.

The outlet or all outlets of the outlet group associated with themonitored equipment are being powered off.

Server is shutting The shutdown command was sent to the monitored equipment,
down
but the shutdown operation has not completed or succeeded yet.
Power state
unknown

Cannot determine the power state of the outlet(s) associatedwith the monitored device.
For example, maybe the outlet group associated with themonitored device has been deleted.

▶ To shut down a monitored device:
1.
2.
3.
4.

Select the IT device that you want to shut down.
Click Shutdown.
Confirm the operation when prompted.
Observe the Power Control status of the monitored device to make sure the shutdown operation
succeeds.

▶ To power on a monitored device:
1.
2.
3.
4.

Select the IT device that you want to turn on.
Click Power Up.
Confirm the operation when prompted.
Observe the Power Control status of the monitored device to make sure the power-on operation
succeeds.

Editing or Deleting Ping Monitoring Settings
You can edit the ping monitoring settings of any IT device or simply delete it if no longer needed.

355

▶ To modify or delete any monitored IT device:
1. Choose Device Settings > Server Reachability.
2. Click the desired one in the list.
3. Perform the desired action.
• To modify settings, make necessary changes and then click Save. To delete it, clickon the top-right corner.

Example: Ping Monitoring and SNMP Notifications
In this illustration, it is assumed that a significant PDU (IP address: 192.168.84.95) shall be monitored byyour PX-Series PDU to make sure that PDU is properly operating all the time, and the PX-Series PDU
must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or
network failure. The prerequisite for this example is that the power sources are different between yourPX-Series PDU and the monitored PDU.
This requires the following two steps.

▶ Step 1: Set up the ping monitoring for the target PDU
1. Choose Device Settings > Server Reachability.
2. Click.
3. Ensure the "Enable ping monitoring for this server" checkbox is selected.
4. Enter the data shown below.
• Enter the server's data.
Field

Data entered

IP address/hostname

192.168.84.95• To make the PX-Series PDU declare the accessibility of the monitored PDU every 15 seconds (3pings * 5 seconds) when that PDU is accessible, enter the following data.
Field

Data entered

Number of successful pings to enable feature

3

Wait time after successful ping5

• To make the PX-Series PDU declare the inaccessibility of the monitored PDU when that PDU
becomes inaccessible for around 12 seconds (4 seconds * 3 pings), enter the following data.

356

Field

Data entered

Wait time after unsuccessful ping4

FieldData entered

Number of consecutive unsuccessful pings for failure

3• To make the PX-Series PDU stop pinging the target PDU for 60 seconds (1 minute) after the PDU
inaccessibility is declared, enter the following data. After 60 seconds, the PX-Series PDU will re-ping
the target PDU,
Field

Data entered

Wait time before resuming pinging after failure

60• The "Number of consecutive failures before disabling feature (0 = unlimited)" can be set to any
value you want.
5. Click Create.

▶ Step 2: Create an event rule to send SNMP notifications for the target PDU
1. Choose Device Settings > Event Rules.
2. Click.
3. Select the Enabled checkbox to enable this new rule.
4. Configure the following.
Field/setting

Data specified

Rule nameSend SNMP notifications for PDU (192.168.84.95)
inaccessibility

Event

Choose Server Monitoring > 192.168.84.95 > Unreachable

Trigger condition Select the Unreachable radio button

This will make the PX-Series PDU react only when the target PDU becomes inaccessible.
5. Select the System SNMP Notification Action.

Front Panel Settings
You can set up the default mode of the front panel display, and front panel functions for outlet
switching, actuator control, beeper mute or RCM self-test.
Note that available front panel settings are model dependent.
•

Outlet switching -- available on outlet-switching capable models only.

•

Actuator control -- available on all models.

•Internal beeper's mute function -- available on all models•

Default front panel mode setup -- available on all models, except for the PX3-3000 series, which
does NOT provide inlet sensor information.

•

RCM self-test -- available on those models which support residual current monitoring.

357

▶ To configure the front panel settings:
1. Choose Device Settings > Front Panel.
2. Configure the following:• To configure the default view of the LCD display, select one mode below.
Note: The default view is shown in the automatic mode.
Mode

Data entered

Automaticmode

The LCD display cycles through both the inlet and overcurrent
protector information. This is the default.
Overcurrent protector information is available only when yourPX-Series PDU has overcurrent protectors.

Inlet overview

The LCD display cycles through the inlet information only.

• To enable the front panel outlet-switching function, select the 'Outlet switching' checkbox.
• To enable the front panel actuator-control function, select the 'Peripheral actuator control'
checkbox.
• The built-in beeper's mute control function is enabled per default. To disable it, deselect the 'Mute
beeper' checkbox.
• By default the front panel RCM self-test function, if available, is enabled.
3. Click Save.
If the 'Mute beeper' feature is enabled, you can operate the front panel to mute it whenever it
beeps.
Or you can turn on or off outlets/actuators by operating the front panel.

Configuring the Serial PortYou can change the bit rate of the serial port labeled CONSOLE / MODEM that is present on somemodels. The default bit rate for console and modem operation is 115200 bps.
The following devices are supported via the serial interface:•

A computer for console management.

•

A Raritan KVM product.

•

An analog modem for remote dial-in and access to the CLI.

•

A GSM modem for sending out SMS messages to a cellular phone.

Bit-rate adjustment may be necessary. Change the bit rate before connecting the supported device tothe PX-Series PDU through the serial port, or there are communication problems.
You can set diverse bit-rate settings for console and modem operations. Usually the PX-Series PDU candetect the device type, and automatically apply the preset bit rate.
The PX-Series PDU will indicate the detected device in the Port State section of the Serial Port page.

358

To configure serial port and modem settings, choose Device Settings > Serial Port.

▶ To change the serial port's baud rate settings:
1. Click the 'Connected device' field to make the serial port enter an appropriate state.
Options

Description

Automatic
detection

The PX-Series PDU automatically detects the type of the device connectedto the serial port.
Select this option unless your PX-Series PDU cannot correctly detect thedevice type.

Force console

The PX-Series PDU attempts to recognize that the connected device is set
for the console mode.

Force analog
modem

The PX-Series PDU attempts to recognize that the connected device is ananalog modem.

Force GSM modem The PX-Series PDU attempts to recognize that the connected device is a
GSM modem.

2. Click the 'Console baud rate' field to select the baud rate intended for console management.
Note: For a serial RS‑232 or USB connection between a computer and the PX-Series PDU, leave it at thedefault (115200 bps).
3. Click the 'Modem baud rate' field to select the baud rate for the modem connected to the PX-Series
PDU.
The following modem settings/fields appear in the web interface after the PX-Series PDU detects theconnection of an analog or GSM modem.

359

▶ To configure the analog modem:
1. Select the 'Answer incoming calls' checkbox to enable the remote access via a modem. Otherwise,
deselect it.
2. Type a value in the 'Number of rings before answering' field to determine the number of rings the
PX-Series PDU must wait before answering the call.

▶ To configure the GSM modem:
1. Enter the SIM PIN code.
2. Select the 'Use custom SMS center number' checkbox if a custom SMS center will be used.
• Enter the SMS center number in the 'SMS center' field.
3. If needed, click Advanced Information to view detailed information about the modem, SIM andmobile network.
4. To test whether the PX-Series PDU can successfully send out SMS messages with the modem
settings:
a. Enter the number of the recipient's phone in the Recipient Phone field.
b. Click Send SMS Test to send a test SMS message.

Lua Scripts
If you can write or obtain any Lua scripts, you can create or load them into the PX-Series PDU to control
its behaviors.
Some Lua scripts examples are provided, which you can load as needed.
Note: Not all Lua script examples can apply to your PX-Series PDU model. You should read eachexample's introduction before applying them.
You must have the Administrator Privileges to manage Lua scripts.

Writing or Loading a Lua Script
You can enter or load up to 4 scripts.

▶ To write or load a Lua script:
1. Choose Device Settings > Lua Scripts >.
2. Type a name for this script. Its length ranges between 1 to 63 characters.
The name must contain the following characters only.
• Alphanumeric characters• Underscore (_)• Minus (-)

360

Note: Spaces are NOT permitted.
3. Determine whether and when to automatically execute the loaded script.
Checkbox

Behavior when selectedStart automatically at systembootWhenever the PX-Series PDU reboots, the script is automatically
executed.

Restart after termination

The script is automatically executed each time after 10 seconds
since the script execution finishes.

4. (Optional) Determine the arguments that will be executed by default.

a. Click.

b. Type the key and value.
c. Repeat the same steps to enter more arguments as needed.

▪ To remove any existing argument, click

adjacent to it.

Note: The above default arguments will be overridden by new arguments specified with the"Start with Arguments" command or with any Lua-script-related event rule.
5. In the Source Code section, do one of the following. It is recommended to leave the Enable Syntax
Highlighting checkbox selected unless you do not need different text colors to identify diverse code
syntaxes.
• To write a Lua script, type the codes in the Source Code section.

• To load an existing Lua script file, click Load Local File.
• To use one of the default Lua script examples, click Load Example.

361

Warning: The newly-loaded script will overwrite all existing codes in the Source Code section.
Therefore, do not load a new script if the current script meets your needs.
6. If you chose to load a script or the example in the previous step, its codes are then displayed in the
Source Code section. Double check the codes. If needed, modify the codes to meet your needs.
7. Click Create.

Manually Starting or Stopping a Script
You can manually start or stop an existing Lua script at any time.
When starting a script, you can choose to start it either with its default arguments or with newarguments.
Tip: To have the PX-Series PDU automatically start or stop a script in response to an event, create an
event rule.

▶ To manually start a script:
1. Choose Device Settings > Lua Scripts. The Lua scripts list displays.

2. Click the desired script whose state is either 'Terminated' or 'New.'
3. To start with default arguments, click.

To start with new arguments, click> Start With Arguments. Newly-assigned arguments
will override default ones.
4. If you chose "Start With Arguments" in the above step, enter the key and value in the Start Lua
Script dialog.

• Click362

if needing additional arguments.

5. Click Start.
6. The script output will be shown in the Script Output section.
• If needed, click

to delete the existing output data.

▶ To manually stop a script:
1. Choose Device Settings > Lua Scripts.
2. Click the desired script whose state is either 'Running' or 'Restarting.'
3. Clickon the top-right corner.
4. Click Stop on the confirmation message.

Checking Lua Scripts States
Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state andsettings of each script.

▶ State:State

Description

New

The script is never executed since the device boot.

Running

The script is currently being executed.

363

StateDescription

Terminated The script was once executed, but stops now.
Restarting

The script will be executed. Only the scripts with the "Restart"
column set to "yes" will show this state.

▶ Autostart:
This column indicates whether the checkbox labeled "Start automatically at system boot" is enabled. .

▶ Restart:
This column indicates whether the checkbox labeled "Restart after termination" is enabled.

Modifying or Deleting a Script▶ To modify or replace a script:
1. Choose Device Settings > Lua Scripts.
2. Click the desired one in the scripts list.
3. Click> Edit Script.
4. Make changes to the information shown, except for the script's name, which cannot be revised.
• To replace the current script, click Load Local File or Load Example to select a new script.

▶ To delete a script:
1. Choose Device Settings > Lua Scripts.
2. Click the desired one in the scripts list.
3. Click> Delete.
4. Click Delete on the confirmation message.

Miscellaneous
The Miscellaneous page contains some assorted settings.

▶ Enable USB Host Ports:•

If you want to enable/disable your PX-Series PDU USB host ports, use this checkbox.

When disabled, the following features are unavailable:

364

•

Wireless networking•

USB cascading•

USB configuration and firmware update•

Webcam support•

USB card reader support•

PDView mobile app for iOS▶ Enable Crestron XiO Connection:•

If the Crestron XiO connection is part of your configuration, you can enable/disable it here.

Using Prometheus and Grafana
You can use the open-source tools Prometheus and Grafana to collect sensor data and visualize it. In
Prometheus, the sensor readings are stored locally as time series data, which can be visualized in graphs
created by Grafana or similar tools This information is displayed on dashboards, and you can create
multiple dashboards as needed.

Requirements for Prometheus and Grafana▶ Prometheus Requirements:•

Prometheus v2.0 or higher•

Install on a computer in the PX-Series PDU network.

•

Reference: https://prometheus.io/docs/introduction/first_steps/365▶ Grafana requirements:•

Grafana v8.1.5 or higher•

Install on a computer in the network of the Prometheus instance.

•

Reference: https://grafana.com/grafana/download?pg=get&plcmt=selfmanaged-box1-cta1

Collected Data
For integration into a Prometheus system, the PDU can output all measurements in a Prometheuscompatible format that can be queried in specific exposition format from the URL: 'https://<PDU_IP>/
cgi-bin/dump_prometheus.cgi'. The URL has one optional parameter, "include_names=1", to include
PDU, inlet and outlet names in the metric labels.
You can use cURL as follows to retrieve the data:
1. curl -k https://username:password@[PDU_IP]/cgi-bin/dump_prometheus.cgi
2. curl -k https://username:password@[PDU_IP]/cgi-bin/dump_prometheus.cgi?include_names=1

Maintenance
Click 'Maintenance' in the Menu to view the options.

Device Information
The Device Information page displays hardware and software information of components or connected
peripheral devices.

366

Tip: If the information shown on this page does not match the latest status, press F5 to reload it.

▶ To display device information:
1. Choose Maintenance > Device Information. Click any header to expand the information. Available
sections depend on your model.
Section title

Information shown

Information

General device information, such as model name, serial number,
firmware version, hardware revision, MIB download link(s) and so on.

Network

The network information, such as the current networking mode, IPv4
and/or IPv6 addresses and so on.
Information on cascading configurations also shows here.

Port Forwarding

If the port forwarding mode is activated, this section shows a list of
port numbers for all cascaded devices.

Outlets

Each outlet's receptacle type, operating voltage and rated current.

Overcurrent
Protectors

Each overcurrent protector's type, rated current and the outlets that it
protects.

Controllers

Each inlet or outlet controller's serial number, Device ID,Hardware ID,
Firmware Version and Status.

Peripheral Devices

Serial numbers, model names, position and firmware-related
information of connected environmental sensor packages.

Note: Serial number when clicked provides the detail
information of the peripheral device.
Asset Management Each asset strip's ID, boot version, application version and protocol
version.
Security

SSH host keys.

Viewing Connected Users
You can check which users are logged in and their status. If you have administrator privileges, you canterminate any user's connection.

▶ To view and manage connected users:
1. Choose Maintenance > Connected Users. A list of logged-in users displays.

367

Column

Description

User Name The login name of each connected user.
IP Address The IP address of each user's host.
For the login via a local connection (serial RS‑232 or USB), <local> isdisplayed instead of an IP address.
Client Type The interface through which the user is being connected to the PX-Series
PDU.
•

Web GUI: Refers to the web interface.

•

CLI: Refers to the command line interface (CLI).

The information in parentheses following "CLI" indicates
how this user is connected to the CLI.
- Serial: The local connection, such as the serial RS‑232
or USB connection.
- SSH: The SSH connection.
- Telnet: The Telnet connection.
•
Idle Time

Webcam Live Preview: Refers to the live webcam image sessions.
See below.

The length of time for which a user remains idle.

1. To disconnect any user, click the corresponding.

a. Click Disconnect on the confirmation message.
b. The disconnected user is forced to log out.

▶ If there are live webcam sessions:
All Live Preview window sessions sharing the same URL, including one Primary Standalone Live Preview
window and multiple Secondary Standalone Live Preview windows, are identified as one single"<webcam>" user in the Connected Users list. You can disconnect a "<webcam>" user to terminate allsessions sharing the same URL.

The IP address refers to the IP address of the host where the Primary Standalone Live Preview window
exists, NOT the IP address of the other two associated sessions.

368

Viewing, Pausing, Resuming or Clearing the Local Event Log
By default, certain system events are captured and saved in a local event log.
You can view over 2000 historical events in the local event log. When the log size exceeds 256KB, each
new entry overwrites the oldest one.

▶ To display the local event log:
1. Choose Maintenance > Event Log.
Each event entry consists of:• ID number of the event• Date and time of the event• Event type
• A description of the event
2. To filter the list, select the desired event type in the 'Filter event class' field, or enter keywords in the'Filter by log message' field.
3. The log is refreshed automatically at a regular interval of five seconds. To avoid any new events'
interruption during data browsing, you can suspend the automatic update by clicking Pause.
• To restore automatic update, click Resume. Those new events that have not been listed yet due tosuspension will be displayed in the log now.

▶ To Pause & Resume the local log:
1. Click Pause on the top right corner.

GUI temporarily stops displaying Event Log updates and button label shows 'Resume'.
2. Click Resume on the top right corner.
GUI continues displaying Event Log updates and shows also messages which were skipped
when paused. The Button label shows 'Pause'.
Note: After page change, Event Log list is automatically in 'Resumed' state again.

▶ To clear the local log:
1. Click Clear Log on the top-right corner.
2. Click Clear Log on the confirmation message.

369

▶ To export the log:
1. Click Export as CSV on top right corner.
2. CSV file gets downloaded to local machine.

Updating the Firmware
When performing the firmware update, the PX-Series PDU keeps each outlet's power status unchanged
so no server operation is interrupted. During and after the firmware update, outlets that have been
powered on prior to the update remain powered ON and outlets that have been powered off remain
powered OFF.
You must be the administrator or a user with the Firmware Update permission to update the firmware.
Before starting, read the release notes. If you have any questions or concerns, contact Technical Support
BEFORE updating.
On a multi-inlet PDU, all inlets must be connected to power for the PDU to successfully update its
firmware.
Note that firmware update via iOS mobile devices, such as iPad, requires the use of iCloud Drive or a file
manager app.
Firmware update can also be completed using methods other than the web interface. See Special
Configuration and Upgrade Methods (on page 593).
Warning: Do NOT perform the firmware update over a wireless network connection.

▶ To update the firmware:
1. Choose Maintenance > Update Firmware.
2. Click Browse to select an appropriate firmware file.
3. Click Upload. A progress bar appears to indicate the upload process.

370

4. Select Free memory before upload to clear up the memory.
5. Once complete, information of both installed and uploaded firmware versions as well ascompatibility and signature-checking results are displayed.
• If anything is incorrect, click Discard Upload.
6. To proceed with the update, click Update Firmware.
Warning: Do NOT power off the PX-Series PDU during the update.
7. During the firmware update:• A progress bar appears on the web interface, indicating the update status.
• The front panel display shows the firmware upgrade message.
• The outlet LEDs flash if the relay boards are being updated. If the firmware update does not include
the update of the relay board firmware, outlet LEDs do NOT flash.
• No users can log in.
• Other users' operation, if any, is forced to suspend.
8. When the update is complete, the unit resets, and the Login page re-appears.
Important: If you are using the PX-Series PDU with an SNMP manager, download
its MIB again after the firmware update to ensure your SNMP manager has thecorrect MIB for the latest release you are using.

Upgrade Guidelines for Existing Cascading Chains
There are additional concerns when upgrading devices in a cascading chain. See Firmware Upgrade for
Cascading Chains (on page 671)

A Note about Firmware Upgrade TimeThe PDU firmware upgrade time varies from unit to unit, depending on various external and internal
factors.
External factors include, but are not limited to: network throughput, firmware file size, and speed atwhich the firmware is retrieved from the storage location. Internal factors include: the necessity of
upgrading the firmware on the microcontroller and the number of microcontrollers that require
upgrade (which depends on the number of outlets). The microcontroller is upgraded only whenrequired. Therefore, the length of firmware upgrade time ranges from approximately 3 minutes(without any microcontroller updated) to almost 7 minutes (with all microcontrollers for 48 outlets
updated). Take the above factors into account when estimating the PDU's firmware upgrade time.
The time indicated in this note is for PX-Series PDU web-interface-based upgrades. Upgrades throughother management systems, such as Sunbird's Power IQ, may take additional time beyond the controlof the PDU itself. This note does not address the upgrades using other management systems.

Full Disaster Recovery
If the firmware upgrade fails, causing the PX-Series PDU to stop working, you can recover it by using a
special utility rather than returning the device.

371

Contact Raritan Technical Support for the recovery utility. You will also need an appropriate firmware
file in the recovery procedure.

Viewing Firmware Update History
The firmware upgrade history is permanently stored. It remains available even though you perform adevice reboot or any firmware update.

▶ To view the firmware update history:
1. Choose Maintenance > Firmware History.
Each firmware update event consists of:• Update date and time
• Previous firmware version• Update firmware version• Update result

Bulk Configuration
The Bulk Configuration feature lets you save generic settings of a configured PX-Series PDU device toyour computer. You can use this configuration file to copy settings to other devices of the same modeland firmware version.
A source device is the PX-Series PDU device where the configuration file is downloaded/saved. A target
device is the PX-Series PDU device that loads the configuration file.
By default the configuration file downloaded from the source device contains settings based on thebuilt-in bulk profile. The built-in bulk profile defines that all settings should be saved except for
device‑specific settings, such as IP address or environmental sensor settings. If you need to load thesedevice-specific settings, you should use the Backup/Restore feature instead.
You can decide which settings are downloaded by creating your own bulk configuration profile.
When the date and time settings are included in the bulk configuration file, exercise caution when
distributing that file to target devices located in a different time zone than the source device.
This bulk configuration method can be employed through the web interface, USB, or SCP. See Special
Configuration and Upgrade Methods (on page 593).

▶ Bulk configuration overview:
1. A built-in configuration profile is available, or you can customize your own bulk configuration profile.
2. Select and download the file from the source device.
3. Upload the file to perform the configuration on the target device.

Bulk Configuration Restrictions
Before performing bulk configuration, make sure your source and target devices are compatible devices
for sharing general settings.

372

▶ Restrictions for bulk configuration:•

The target device must be running the same firmware version as the source device.

•

The target device must be of the same model type as the source device.

•

Bulk configuration is permitted if the differences between the target and source devices are only
"mechanical" designs which are indicated in the model name's suffix.
For example, you can perform bulk configuration between PX3-4724-E2N1K2 andPX3-4724-E2N1K9 since the only difference between the two models is their chassis colors
represented by K2 (blue) and K9 (gray).

▶ Mechanical design codes in model numbers:
These mechanical designs are represented by suffixes added to the model name. In the table, x
represents a number. For example, Ax can be A1, A2, A3, and so on.
Suffix Mechanical design

ExampleAx

A20 = 3.3 meters

The line cord's length in meters

Note: For an inline monitor, it is likely two
Ax's are added to the model name forindicating the lengths of its inlets' andoutlets' line cords.
Bx

The line cord's color

B501 = bright red orange

Cx

Cord types or options

C4 = power cord withthe standard gauge

Dx

Plug types or options

D1 = IP67 watertight
plug

Ex

Outlet types or options

E2 = Locking C13 or
Locking C19

Gx

Controller options

G0 = no controller

Kx

Chassis colors

K6 = yellow

Lx

The line cord's length in centimeters

Nx

Chassis dimensions or other mechanical changes

Ox

OCP brand options

Px

Special requests for device painting or printing

Qx

Special requests for physical placement
arrangements

Rx

Custom logo373

Suffix Mechanical design
Ux

ExampleDifferent power plug brands

Customizing Bulk Configuration Profiles
A bulk profile defines which settings are downloaded/saved from the source device and which are not.
The default is to apply the built-in bulk profile, which downloads all settings from the source device
except for device-specific data.
If the built-in profile does not meet your needs, you can create your own profiles.

▶ To create new bulk configurations profiles:
1.
2.
3.
4.

Log in to the source device whose settings you want to download.
Choose Maintenance > Bulk Configuration.
Click New Profile, then enter a Profile name and Description.
To make this new profile the default one for future bulk configuration operations, select the 'Selectas default profile' checkbox.
5. Now decide which settings to include or exclude.
a. Clickof the setting which you want to configure.

b. When the pop-up menu appears, select one of the options.
Note that the two options 'Inherited' and 'Built-in' are mutually exclusive.
OptionDescription

Excluded The setting will not be downloaded.
Included The setting will be downloaded.
Inherited The setting will follow its parent setting (that is, the upper-level setting).
•

If you select 'Excluded' for its upper-level setting, this setting will be also
excluded.

•If you select 'Included' for its upper-level setting, this setting will be also
included.
The option inherited from its parent setting will be enclosed in parentheses.

374

OptionDescription

Built-inThe setting will follow the same setting of Raritan's built-in profile.
•

If 'Excluded' is selected in the built-in profile, this setting will be also excluded.

•

If 'Included' is selected in the built-in profile, this setting will be also included.
The option inherited from the built-in profile will be enclosed in parentheses.

Note: The option 'Built-in' is available in those settings whose
corresponding settings in the built in profile have been set to a noninherited option -- Excluded or Included.
1. Click Save.

Performing Bulk Configuration
To perform the bulk configuration using the web interface, first select and download the bulk
configuration file, then upload it to the target device to configure it.

▶ Step 1: Save a bulk configuration file
You must have the Administrator Privileges or "Unrestricted View Privileges" to download theconfiguration.
1.
2.
3.
4.

Log in to the source device.
Choose Maintenance > Bulk Configuration.
Select the profile of the configuration you want to use in the Bulk Profile field.
In the 'Bulk format' field select Encrypted or Cleartext, to specify the security of the file.

OptionDescription

Encrypted•

Partial content is base64 encoded.

•

Its content is encrypted using the AES-128 encryption algorithm.

•

The file is saved to the TXT format•

Content is displayed in clear text.

•

The file is saved to the TXT format.

Cleartext

1. In Encrypted mode, you can password protect the file. Select the Use Password checkbox, thenenter a password. A password will be required when the file is uploaded on the target device.
2. Click Download Bulk Configuration. The file is named "bulk_config" with the source device serial
number and a creation date/time stamp, such as "bulk_config_1BZ31B603C_20210927". Yourbrowser's file download method determines download location. Save the file so that it's available tobe uploaded to the target device.

▶ Step 2: Upload the file to configure the target
You must have the Administrator Privileges to upload the configuration.

375

1. Log in to the target device, which is of the same model and runs the same firmware as the source
device.
2. Choose Maintenance > Bulk Configuration.
3. In the Restore Bulk Configuration section, click Browse to select the configuration file.
4. Click 'Upload & Restore Bulk Configuration'.
5. Confirm the operation and enter the administrator password, then click Restore.
6. Wait until the login page reappears.

Modifying or Deleting Bulk Configuration Profiles
You can modify or delete any bulk profile except for the built-in one.
Note that a profile that has been set as the default cannot be deleted. To remove it, you have to remove
its default setting first.
Choose Maintenance > Bulk Configuration. A list of profiles displays and then do one of the following.

▶ To modify an existing profile:
1. Click on the row of the wanted profile in the list.
2. Change the settings you want.
3. Click Save.

▶ To delete profiles
1. Select one or multiple profiles, then click the Delete icon
2. Click Delete in the confirmation message.

.

Backup and Restore of Device Settings
Unlike the bulk configuration file, the backup file contains ALL device settings, including device-specificdata like device names and all network settings. To back up or restore the device settings, you should
use the Backup/Restore feature. To perform bulk configuration among multiple PX-Series PDU devices,use the Bulk Configuration feature instead.
All PX-Series PDU information is captured in the plain-TEXT-formatted backup file except for the device
logs and TLS certificate.
Backup/Restore can also be completed using other methods. See Special Configuration and Upgrade
Methods (on page 593).

376

▶ To download a backup file:
You must have the Administrator Privileges or "Unrestricted View Privileges" to download a backup file.
1. Choose Maintenance > Backup/Restore.
2. Check the 'Backup format' field. If the chosen value does not match your need, change it.
OptionDescription

Encrypted•

Partial content is base64 encoded.

•

Its content is encrypted using the AES-128 encryption algorithm.

•

The file is saved to the TXT format•

Content is displayed in clear text.

•

The file is saved to the TXT format.

Cleartext

1. Click Download Device Settings. Save the file onto your computer.

▶ To restore using a backup file:
You must have the Administrator Privileges to restore the device settings.
1. Choose Maintenance > Backup/Restore.
2. Click Browse to select the backup file.
3. Click 'Upload & Restore Device Settings' to upload the file.
• A message appears, prompting you to confirm the operation and enter an administrator password.
4. Enter the password, then click Restore.
5. Wait until the PX-Series PDU resets and the Login page re-appears, indicating that the restore iscomplete.

Network Diagnostics
PX-Series PDU provides the following tools in the web interface for diagnosing potential networking
issues.
•Ping: The tool is useful for checking whether a host is accessible through the network or Internet.

•

Trace Route: The tool lets you find out the route over the network between two hosts or systems.

•

List TCP Connections: You can use this function to display a list of TCP connections.

Tip: These network diagnostic tools are also available through the CLI.
Choose Maintenance > Network Diagnostics, and then perform any function below.

▶ Ping:
1. Type values in the following fields.

377

FieldDescription

Network host

The name or IP address of the host that you want to check.

Number of requests A number up to 20.
This determines how many packets are sent for pinging the host.

2. Click Run Ping to ping the host. The Ping results are then displayed.

▶ Trace Route:
1. Type values in the following fields.
Field/setting

Description

Hostname

The IP address or name of the host whose route you want to check.

Timeout(s)A timeout value in seconds to end the trace route operation.

Use ICMP packets To use the Internet Control Message Protocol (ICMP) packets toperform the trace route command, select this checkbox.

2. Click Run. The Trace Route results are then displayed.

▶ List TCP Connections:
1. Click the List TCP Connections title bar to show the list.

Downloading Diagnostic Information
Important: Use this function only when you are directed by Technical Support.
You can download the diagnostic file to a client machine. The file is compressed into a .tgz file andshould be sent to Technical Support.
This feature is accessible only by users with Administrative Privileges or Unrestricted View Privileges.

▶ To retrieve a diagnostic file:
1. Choose Maintenance > Download Diagnostic > Download Diagnostic.
2. The system prompts you to save or open the file. Save the file.

Hardware Issue Detection
This page lists any internal hardware issues PX-Series PDU has detected, including current events andhistorical records.
Choose Maintenance > Hardware Failures, and the page similar to either of the following diagrams
opens.
Current hardware failure events, if any, will also display on the Dashboard.

378

▶ NO hardware failures detected:379

▶ Hardware failure(s) detected:▶ Hardware failure types:
Hardware issues

Description

Network device not detected

A specific networking interface is NOT detected.

I2C Bus stuck

A specific I2C bus is stuck, which affects the communication withsensors.

Sub controller not reachable

Communication with a specific sub unit controller fails.

Sub controller malfunction

A specific sub unit controller does not work properly.

Outlet power state inconsistent The physical power state of a specific outlet is different from the chosen
power state set by the software.
Sub controller incompatible

A specific sub unit controller is incompatible with the firmware.

Rebooting
You can remotely reboot the PX-Series PDU via the web interface.
Resetting/rebooting does not interrupt the operation of connected servers because there is no loss of
power to outlets. During and after the reboot, outlets that have been powered on prior to the reboot
remain powered on, and outlets that have been powered off remain powered off.
Warning: Rebooting deletes all webcam snapshots that are saved locally. If needed, download
important snapshots before rebooting the device.

380

▶ To reboot the device:
1. Choose Maintenance > Unit Reset > Reboot Unit.

2. Click Reboot.
3. A message appears, with a countdown timer showing the remaining time of the operation. It takes
about one minute to complete.
4. When the restart is complete, the login page opens.
Tip: If you are not redirected to the login page after the restart is complete, click the text "this link" inthe countdown message.
Note: Device reset will cause CLI communications over an "USB" connection to be lost. Therefore, reconnect the USB cable after the reset is complete.

Resetting All Settings to Factory Defaults
You must have the Administrator Privileges to reset all settings to factory defaults.
Resetting to factory default can also be completed in the CLI or with a Reset button on the unit. See
Resetting to Factory Defaults (on page 676)
Important: Exercise caution before resetting to factory defaults. This erases
existing information and customized settings, such as user profiles, thresholdvalues, and so on. Only active energy data and firmware upgrade history areretained.

▶ To reset the device to factory defaults:
1. Choose Maintenance > Unit Reset > Reset to Factory Defaults.

381

2. Type your password and then click Factory Reset.
3. A message appears, with a countdown timer showing the remaining time of the operation. It takes
about two minutes to complete.
4. When the reset is complete, the login page opens.
Tip: If you are not redirected to the login page after the reset is complete, click the text "this link" in the
countdown message.
Note: Device reset will cause CLI communications over an "USB" connection to be lost. Therefore, reconnect the USB cable after the reset is complete.

Webcam Management
With a Logitech® webcam connected, you can visually monitor the environment around the PX-Series
PDU via snapshots or videos captured by the webcam.
The 'Webcams' menu item appears when there is any webcam connected to the PX-Series PDU, orwhen there are snapshots saved onto already.

382▶ Permissions required:
To do...

Permission(s) required

View snapshots and videos

Either permission below:

Configure webcam settings•

Change Webcam Configuration•

View Webcam Snapshots and Configuration

Change Webcam Configuration

Configuring Webcams and Viewing Live Images
To configure a webcam or view live snapshot/video sessions, choose Webcams in the Menu. Then click
the desired webcam to open that webcam's page.
Note that default webcam names are determined by the detection order. The one that is detected firstis named Webcam, and a second webcam detected later is named Webcam 2.

The Webcam page consists of three sections -- Live Preview, Image Controls and Settings.

▶ Live Preview:
1. By default the Live Preview section is opened, displaying the live snapshot/video session capturedby the webcam.
• The default is to show live snapshots. Interval time and capture date/time of the image aredisplayed on the top of the image. In video mode, the number of frames per second (fps) and thevideo capture date/time are displayed.

383

Tip: The date and time shown on the PX-Series PDU web interface are automatically converted toyour computer's time zone.
2. To save the current image onto PX-Series PDU or a remote server, click Save Snapshot.
• The default storage location for snapshots is the PX-Series PDU device. To save them onto a remote
server, you can change the storage settings.
• To download an image onto your computer, you can right-click it and save.
3. To have the same live session displayed in a separate window, click New Live Preview Window.
• A separate window appears, which is called the Primary Standalone Live Preview window in thisUser Guide.
• You can send out this window's URL to share the live image with others.
• Note that your browser may block the pop-up window▶ Image Controls:

1. Adjust the brightness, contrast, saturation and gain by modifying their values or adjusting thecorresponding slide bar.
• To customize the gain value, you must deselect the Auto Gain checkbox first.
• To restore all settings to this webcam's factory defaults, click Set to Webcam Defaults.

▶ Settings:
1. Click Edit Settings.
2. Enter a name for the webcam. Up to 64 ASCII printable characters are supported.
• If configured to store snapshots on a remote server, the webcam's name determines the name of
the folder where snapshots are stored.
• It is suggested to customize a webcam's name before saving snapshots on the remote server. In
case you change the webcam's name after saving any snapshots, PX-Series PDU will create a new
folder with the new webcam name while keeping the old folder with the old name.
3. Type the location information in each location field as needed. Up to 63 ASCII printable characters
are supported.
• Note that the location data you enter is not available in those snapshots stored on remote servers.
Tip: If the webcam's location is important, you can customize the webcam's name based on its
location.
4. Select a resolution for the webcam.
• If you connect two webcams to one USB-A port using a powered USB hub, set the resolution to352x288 or lower for optimal performance.
5. Select the webcam mode.

384

Mode

Description

Video

The webcam enters the video mode.
•

Set the 'Framerate' (frames per second) as needed.

Snapshot The webcam shows static images captured by the webcam at a regularinterval.
•

To determine the interval, set the 'Time Between Snapshots'(seconds).

1. Click Save. The changes made to the settings are applied to the live session in the above Live Preview
section immediately.

Sending Links to Snapshots or Videos
When opening a Primary Standalone Live Preview window, a unique URL is generated for this window
session. You can email or instant message this URL to as many people as possible as long as your system
resources permit. Recipients can then click on the provided link and view live snapshots or videos
simultaneously in the Secondary Standalone Live Preview window(s).
Tip: All Live Preview window sessions sharing the same URL, including one Primary Standalone Live
Preview window and multiple Secondary Standalone Live Preview windows, are identified as one single"<webcam>" user in the Connected Users list. You can disconnect a "<webcam>" user to terminate allsessions sharing the same URL.

▶ Best practice:
1. The sender opens the Primary Standalone Live Preview window, and sends the link to one or
multiple recipients.
2. The sender must wait until at least one recipient opens the Secondary Standalone Live Preview
window.
3. The recipient(s) should inform the sender that the link has been opened.
4. Now the sender can close the Primary Standalone Live Preview window.

▶ To send a snapshot or video link via email or instant message:
1. Choose Webcams in the Menu.
2. Click the desired webcam to open the Webcam page.
3. Click New Live Preview Window in the Live Preview section. The live snapshot or video in astandalone window opens.
4. Copy the URL from that live preview window.
a. Select the URL shown on the top of the image.

385

b. Right click to copy the URL, or press CTRL+ C.
5. Send the URL link through an email or instant message application to one or multiple persons.
6. Leave the live preview window open until the recipient(s) opens the snapshot or video via the link.

How Long a Link Remains Accessible
For documentation purposes, the one who opens and sends the URL of the Primary Standalone Live
Preview window is called User A and the two recipients of the same URL link are called User B and C.
User C is able to access the snapshot or video image via the link when the URL link remains valid, which
can be one of these scenarios:•

The Primary Standalone Live Preview window remains open on User A's computer. If so, eventhough User A logs out of the PX-Series PDU or the login session times out, the link remains
accessible.

•

User B's Secondary Standalone Live Preview window remains open. If so, even though User A
already closes the Primary Standalone Live Preview window, the link remains accessible.

•

Neither User A's Primary Standalone Live Preview window nor User B's Secondary Standalone Live
Preview window remains open, but it has not exceeded two minutes yet after the final live preview
window session was closed.

Note: The link is no longer valid after two minutes since the final live preview window is closed.

Viewing, Downloading, Deleting Locally-Saved Snapshots
This section describes the operation for snapshots saved onto the PX-Series PDU device only.
When saving a snapshot, it is stored locally on the PX-Series PDU device by default. Up to 10 snapshots
can be stored locally. The oldest snapshot is automatically overridden by the newest one when the totalof snapshots exceeds 10, if no snapshots are deleted manually.

386

When there is more than one webcam connected, then the oldest snapshot of the webcam with themost snapshots is overwritten.
Snapshots are saved as JPG files, and named with sequential numbers, such as 1.jpg, 2.jpg, 3.jpg.
Warning: Rebooting the PX-Series PDU deletes all webcam snapshots that are
saved locally. If needed, download important snapshots before rebooting thedevice.

▶ To view, refresh, download or delete saved snapshots:
1. Choose Webcams > Browse Snapshots. The Snapshots page opens.
• To view a snapshot, click the link in the list. The image, capture time and resolution is displayed on
the same page.
• To refresh the list, click the Refresh icon.
• To download an image file, click the Download icon.
• To delete an image, select the checkbox of the image and click the Delete icon.

Changing Storage Settings
Important: The PX-Series PDU web interface only lists the snapshots stored locally on the PX-Series PDU
device, but does NOT list those saved onto remote servers. You must launch appropriate third-party
applications, such as an FTP client, to access and manage the snapshots stored on remote servers.
The default is to store snapshots locally on the device, which has a limitation of 10 snapshots. Note thatany operation involving device reboot, such as firmware upgrade, will remove the locally saved
snapshots.
If you need to keep more than 10 images or need to keep them permanently, configure the settings tomove images onto a remote Samba or FTP server.

▶ To configure the storage settings:
1. Choose Webcams > Edit Settings.

387

2. Click the Storage Type field to select the desired storage location and configure as needed.
Note: When entering user credentials for remote servers, make sure the user credentials you enter havethe write permission, or NO snapshots can be successfully saved onto remote servers.
Storagelocation

Description

Local'Local' means the PX-Series PDU. This is the default.

CIFS/
Samba

•

It can store a maximum of 10 snapshots only.

•

The web interface can list and display all snapshots stored on the PXSeries PDU.

•

All snapshots are CLEARED when the PX-Series PDU is rebooted.

Snapshots are saved onto a Common Internet File System/Samba.
•

Total number of saved snapshots depends on the server's capacity.

•

Saved snapshots are not affected by reboots of the PX-Series PDU
device.

•Configure the following fields:* Server - the desired CIFS/Samba server* Share/folder - this is the share drive/folder* Username - for server access* Password - for server access
FTP

Snapshots are saved onto a FTP server.
•

Total number of saved snapshots depends on the server's capacity.

•

Saved snapshots are not affected by reboots of the PX-Series PDU.

•

Configure the following fields:* Server URL - the FTP server's path
* Username - for server access* Password - for server access
1. Click Save.
Warning: Before disconnecting or powering off any remote server where thewebcam snapshots are being stored, you must first change the storage settings, orthe connectivity issue of the remote server may degrade the performance of the
PX-Series PDU web interface. If this issue occurs, first restore the connectivity of
the remote server and then change the storage settings of the webcam snapshots.

388

▶ Tip for notifications showing the snapshots path on FTP:
If you are using SNMP to retrieve data, you can make PX-Series PDU automatically send a notification
containing the full path or URL to the snapshots saved onto FTP with this SNMP code:
webcamStorageUploadStarted.

Identifying Snapshots Folders on Remote Servers
If saving snapshots onto a remote server, you can access those snapshots via an appropriate third-party
application, such as an FTP client.
All snapshots are saved as JPEG and named according to the date and time when saving the snapshots.
Note that the date and time of the filename are based on the time zone of the PX-Series PDU rather
than that of the computer or mobile device you are operating.
Tip: To check the time zone, choose Device Settings > Date/Time.
The structure of a snapshots folder looks similar to the diagram below.

Number Folder name description
User-defined parent directory, whose name depends your server settings, such as
your FTP configuration.
Serial number of your PX-Series PDU device where the webcam is connected. For
example, PH85350018.
•

View your serial number in Device Information.

The name of the webcam that your PX-Series PDU detects first.
This is the folder where the snapshots captured by the first webcam are stored.
•

The first webcam's default name is "Webcam".

•

You can customize the webcam's name, which will change the snapshots
folder's name.

•

If the webcam's location is important, you can customize the webcam's namebased on its location when configuring PX-Series PDU to save snapshots ontoa remote server.

389

Number Folder name description
The name of the webcam that your PX-Series PDU detects later, if an additional
webcam is connected.
This is the folder where the snapshots captured by the second webcam arestored.
•The second webcam's default name is "Webcam 2".

•

Changing this webcam's name also changes the second snapshots folder's
name.

•

If the webcam's location is important, you can customize the webcam's namebased on its location when configuring PX-Series PDU to save snapshots ontoa remote server.

Note: It is suggested to customize a webcam's name "prior to" saving snapshots on the remote server.
In case you change the webcam's name after saving any snapshots, PX-Series PDU will create a new
folder with the new webcam name while keeping the old folder with the old name.

SmartLock and Card Reader
Raritan's SmartLock kits provide several cabinet access control solutions.
If you have purchased a SmartLock kit with the door handle controller "DX2-DH2C2", both menu items"SmartLock" and "Card Readers" will appear in the menu after connecting and configuring properly
DX2-DH2C2 and the door handles included in the kit.
Note that "SmartLock" appears only when your door handles are connected via DX2-DH2C2, but "Card
Readers" appears as long as any card reader is detected, whether standalone USB card reader or a card
reader integrated with the door handles.

390

SmartLock
To open the martLock page, choose SmartLock in the Menu.
The page shows information of all DX2-DH2C2 modules connected, including its serial number, position
and its door configuration. When primary units and/or link units have SmartLock controllers connected,
this page includes all door information for both.

On this page you can:•View the status of the cabinet door and card reader.
Note: Data of "external" USB card readers is shown on the Card Readers page.

•

Configure the doors connected to DX2-DH2C2. You must set this because the types of connected
door handles are not automatically detected.

•

Control the doors connected to DX2-DH2C2.

•Manage the door access.

▶ To configure the doors:
There are two door sections per DX2-DH2C2 because a DX2-DH2C2 has two door handle ports.

391

1. Click Edit Settings in the Settings section.
2. In the 'Door handle type' field, select the door handle type you are using.
• If your specific Southco H3-EM model is listed, select it. For all other supported Southco H3-EM
models, select "Southco H3-EM".

3. Make changes to the remaining fields as needed, then click Save.

392

Section

Description

Auto Relock
Time•

Specify how long the lock can remain open after someone opens
the door handle lock via smart card or remote control without thehandle being opened during that period. When the timeout
expires, the lock will be automatically closed. Default is 600
seconds (that is, 10 minutes).

Door sensor
polarity•

Choose the correct setting based on the type of contact closure
sensors used to monitor the door:•

Normally closed: The contact is closed (conducting) when thedoor is closed and open (not conducting) when the door is open.
Default.

•

Normally open: The contact is not conducting when the door isclosed and is conducting when the door is open.

•

Note: For both normally closed and normally open sensors, thereported state is "open" when the door is open and "closed"
when the door is closed.

Relock on
Handle Close•

This setting controls auto-locking. Select "Only if door closed" todelay auto-locking until "Door State" and "Door Handel State" areboth verified as "Closed". Select "Always" to relock automatically.

Connected
Device•If your door handle has a connected device, such as a keypad,
select it from the list.

▶ To manage the door access:"Managed Door Access" link provides access to "Door Access Rules" where you can create newrules.Door Access (on page 288)

Door Status and Control
After configuring the door handle type properly, you can see the Status and Card Reader sections.

393▶ To view the status of the door and card reader:
SectionDescription

StatusShows all sensor states detected by DX2‑DH2C2, including:•

Door State: States of contact closure sensors connected to DX2‑DH2C2.
Contact closure sensors detect whether the door is physically opened orclosed.

•Door Handle: States of door locks integrated with the door handles.

•

Door Lock: States of the door handle locks.
Door locks and door handle locks are interrelated so their states arechanged one after another. The door handle lock is opened first andthen the door lock.

Exception: If you manually open the door lock with the key shippedwith your door handle, the Door Lock state will enter the open state
while the Door Handle Lock state remains closed.
Card
ReaderShows the data of the smart card scanned by the internal or external card
reader accompanying each door handle connected to DX2‑DH2C2.

Tip: All sensors of the connected door handles are also listed on the Peripherals page. The same Card
Reader information is also available on the Card Reader page.

394

▶ To control the door:
Per default, only one door handle can be opened at the same time so you must close one door before
opening another. To increase the upper limit of concurrently opened doors, go to the Peripherals page.
1. Go to the proper door section, and click Open or Close.

2. Confirm the operation when prompted.
3. Now you can physically open or close the door.

▶ Door Terms:
The following terms and definitions are helpful when discussing doors, door handles, and locks. Notethat all door sensors also display in the Peripherals page.
•

SmartLock Controllers: DX2-DH2C2•

Door Handle Assembly: Door Handle and Door Lock which are connected to the SmartLock
controller 8 pin connector, for example "door handle 1".

•

Door: Door is the same as "Door Handle Assembly", but with optional contact closure sensor that isconnected to the SmartLock controller connector. The contact closure sensor status describes
whether the cabinet door is open or closed.

•

Door Handle: The small grip on the front of the Door Handle Assembly, which is used tomechanically open the door by hand if it's unlocked. Sensor status describes if the Door Handle ispulled out (open) or closed.

•

Door Lock: The small lock actuator inside of the Door Handle Assembly which locks or unlock the
Door Handle. Sensor status describes if the Door Handle is unlocked or locked.

Card Readers
To open the Card Readers page, choose Card Readers in the Menu.
This page lists all card readers connected, including:•Standalone USB card readers•

Card readers integrated with door handles

395

When a user scans a smart card with the card reader, the card's type and ID are retrieved and shown inthe corresponding Card Type and Card ID column. If no data is shown in the two columns, it means thescanned card may not be supported by the card reader.
Tip: You can use a third-party application, such as Power IQ, to retrieve the card's data to performsecurity features like cabinet access control. Refer to that application's user documentation for more
information.

▶ Door handle-integrated card readers:•This type of card reader is integrated in the door handle, which is any series below:• Emka Agent E• SouthCo H3-EM• Dirak eLine MLR 2500
Note: Not every SouthCo H3-EM door handle has a card reader integrated.

•

It is connected via the DX2-DH2C2 module.

•

The Channel column indicates which door handle port (channel) it is connected to.

•Note that the serial number displayed for this card reader is the same as DX2-DH2C2's serial
number.
Each DX2-DH2C2 module can show two card readers because they have two ports forconnecting two door handles with card readers integrated.

▶ Standalone USB card readers:396•

It is directly connected to PX-Series PDU.

•The Channel column does not show any data.

Using SNMPThis SNMP section helps you set up the PX-Series PDU for use with an SNMP manager. The PX-Series
PDU can be configured to send traps or informs to an SNMP manager, as well as receive GET and SET
commands in order to retrieve status and configure some basic settings.

In This Chapter
Enabling and Configuring SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
SNMPv3 Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
SNMPv2c Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Downloading SNMP MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
SNMP Gets and Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Enabling and Configuring SNMP
To communicate with an SNMP manager, you must enable SNMP protocols on the PX-Series PDU. By
default, SNMP is disabled.
The SNMP v3 protocol allows for encrypted communication. To take advantage of this, you must
configure the users with the SNMP v3 access permission and set Authentication Pass Phrase and Privacy
Pass Phrase, which act as shared secrets between SNMP and the PX-Series PDU.
Important: You must download the SNMP MIB for your PX-Series PDU to use withyour SNMP manager.

▶ To enable SNMP v1/v2c and/or v3 protocols:
1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Agent section, enable SNMP v1/v2c or SNMP v3, and configure related fields, such as
the community strings.
• If SNMP v3 is enabled, you must determine which users shall have the SNMP v3 access permission.

▶ To configure users for SNMP v3 access:1. Choose User Management > Users.
2. Create or modify users to enable their SNMP v3 access permission.
• If authentication and privacy is enabled, configure the SNMP password(s) in the user settings.

SNMPv3 Notifications
1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox is selected.
3. In the SNMP Notifications section, make sure the 'Enable SNMP notifications' checkbox is selected.

397

4. Select 'SNMPv3 trap' or 'SNMPv3 inform' as the notification type.
5. For SNMP TRAPs, the engine ID is prepopulated.
6. Type values in the following fields.
Field

Description

Host

The IP address of the device(s) you want to access.
This is the address to which notifications are sent by the SNMP agent.

Port

The port number used to access the device(s).

User ID

User name for accessing the device.
•

Timeout

The interval of time, in seconds, after which a new inform communication is resent if the firstis not received.
•

Number of retries

For example, resend a new inform communication once every 3 seconds.

Specify the number of times you want to resend the inform communication if it fails.
•

398

Make sure the user has the SNMP v3 access permission.

For example, inform communications are resent up to 5 times when the initialcommunication fails.

FieldDescription

Security level

Three types are available.
•

noAuthNoPriv - neither authentication nor privacy protocols are needed.

•

authNoPriv - only authentication is required.

•

authPriv - both authentication and privacy protocols are required.

Authentication
protocol,The three fields are available when the security level is set to AuthNoPriv or authPriv.

Authentication
passphrase,•

Select the authentication protocol - MD5 or SHA•

Enter the authentication passphrase

Confirm authentication
passphrase
Privacy protocol,

The three fields are available when the security level is set to authPriv.

Privacy passphrase,•

Select the Privacy Protocol - DES or AES

Confirm privacy
passphrase•

Enter the privacy passphrase and then confirm the privacy passphrase

1. Click Save.

SNMPv2c Notifications
1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox is selected.
3. In the SNMP Notifications section, make sure the 'Enable SNMP notifications' checkbox is selected.

4. Select 'SNMPv2c trap' or 'SNMPv2c inform' as the notification type.
5. Type values in the following fields.

399

FieldDescription

Timeout

The interval of time, in seconds, after which a new inform
communication is resent if the first is not received.
•

Number of
retries

The number of times you want to resend the inform communication if
it fails.
•

Host

For example, resend a new inform communication once every 3
seconds.

For example, inform communications are resent up to 5 times
when the initial communication fails.

The IP address of the device(s) you want to access. This is the address
to which notifications are sent by the SNMP agent.
You can specify up to 3 SNMP destinations.

Port

The port number used to access the device(s).

Community

The SNMP community string to access the device(s). The community
is the group representing the PX-Series PDU and all SNMP
management stations.

1. Click Save.

Downloading SNMP MIB
You must download an appropriate SNMP MIB file for successful SNMP communications. Always use thelatest SNMP MIB downloaded from the current firmware of your PX-Series PDU.
You can download the MIBs from two different pages of the web interface.

▶ MIB download via the SNMP page:
1. Choose Device Settings > Network Services > SNMP.
2. Click the Download MIBs title bar.

3. Select the desired MIB file to download.
• PDU2-MIB: The SNMP MIB file for PX-Series PDU management.
• ASSETMANAGEMENT-MIB: The SNMP MIB file for asset management.
4. Click Save to save the file onto your computer.

400

▶ MIB download via the Device Information page:
1. Choose Maintenance > Device Information.
2. In the Information section, click the desired download link:• PDU2-MIB• ASSETMANAGEMENT‑MIB
3. Click Save to save the file onto your computer.

SNMP Gets and Sets
In addition to sending notifications, the PX-Series PDU is able to receive SNMP get and set requests
from third-party SNMP managers.
•

Get requests are used to retrieve information about the PX-Series PDU, such as the system location,and the current on a specific outlet.

•

Set requests are used to configure a subset of the information, such as the SNMP system name.
Note: The SNMP system name is the PX-Series PDU device name. When you change the SNMP
system name, the device name shown in the web interface is also changed.
The PX-Series PDU does NOT support configuring IPv6-related parameters using the SNMP
set requests.

Valid objects for these requests are limited to those found in the SNMP MIB‑II System Group and thecustom PX-Series PDU MIB.

The MIB FileAn SNMP MIB file describes the SNMP functions.
Opening the MIB reveals the custom objects that describe the PX-Series PDU system at the unit level aswell as at the individual-outlet level.
As standard, these objects are first presented at the beginning of the file, listed under their parent
group. The objects then appear again individually, defined and described in detail.

401

For example, the measurementsGroup group contains objects for sensor readings of PX-Series PDU as awhole. One object listed under this group, measurementsUnitSensorValue, is described later in the MIB
as "The sensor value". pduRatedCurrent, part of the configGroup group, describes the PDU current
rating.

SNMP Sets and Thresholds
Some objects can be configured from the SNMP manager using SNMP set commands. Objects that canbe configured have a MAX-ACCESS level of "read-write" in the MIB.
These objects include threshold objects, which cause the PX-Series PDU to generate a warning and send
an SNMP notification when certain parameters are exceeded. See Sensor Threshold Settings for a
description of how thresholds work.
Note: When configuring the thresholds via SNMP set commands, ensure the value of upper criticalthreshold is higher than that of upper warning threshold.

Configuring NTP Server Settings
Using SNMP, you can change the following NTP server-related settings in the unitConfigurationTable:

402

•

Enable or disable synchronization of the device's date and time with NTP servers(synchronizeWithNTPServer)•

Enable or disable the use of DHCP‑assigned NTP servers if synchronization with NTP servers is
enabled (useDHCPProvidedNTPServer)•

Manually assign the primary NTP server if the use of DHCP‑assigned NTP servers is disabled(firstNTPServerAddressType and firstNTPServerAddress)•

Manually assign the secondary NTP server (optional) (secondNTPServerAddressType andsecondNTPServerAddress)

Tip: To specify the time zone, use the CLI or web interface instead.
When using the SNMP SET command to specify or change NTP servers, it is required that both the NTP
server's address type and address be set in the command line simultaneously.
For example, the SNMP command to change the primary NTP server's address from IPv4
(192.168.84.84) to host name looks similar to the following:
snmpset -v2c -c private 192.168.84.84 firstNTPServerAddressType = dns
firstNTPServerAddress = "angu.pep.com"

Retrieving Energy Usage
You can discover how much energy an IT device consumes by retrieving the Active Energy for the outlet
this IT device is plugged into. The Active Energy values are included in theoutletSensorMeasurementsTable, along with other outlet sensor readings.

403

Using the Command Line Interface
This section explains how to use the command line interface (CLI) to administer the PX-Series PDU.
Note that available CLI commands are model dependent.
CLI commands are case sensitive.
The CLI can be used to:
•

Reset

•

Display the device and network information, such as the device name, firmware version, IP address,
and so on•

Configure the device and network settings•

Troubleshoot network problems

You can access the interface over a local connection using a terminal emulation program such as
HyperTerminal, or via a Telnet or SSH client such as PuTTY.
Note: Telnet access is disabled by default. To enable Telnet, go to Device Settings > Network Services >Telnet.

In This Chapter
Logging in to CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Tips for Using the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Showing Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Clearing Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Configuring the Device and Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Network Troubleshooting in Diagnostic Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 559

Logging in to CLI
Logging in via HyperTerminal over a local connection is a little different than logging in using SSH or
Telnet.
If a security login agreement has been enabled, you must accept the agreement in order to complete
the login. Users are authenticated first and the security banner is checked afterwards.

With HyperTerminal
You can use any terminal emulation programs for local access to the command line interface.
This section illustrates HyperTerminal, which is part of Windows operating systems prior to Windows
Vista.

404

▶ To log in using HyperTerminal:
1. Connect your computer to the product via a local connection.
2. Launch HyperTerminal on your computer and open a console window. When the window first
opens, it is blank.
Make sure the COM port settings use this configuration:• Bits per second = 115200 (115.2Kbps)• Data bits = 8• Stop bits = 1• Parity = None
• Flow control = None
Tip: For a USB connection, you can determine the COM port by choosing Control Panel > System >Hardware > Device Manager, and locating the "Device Serial Console" under the Ports group.
3. In the communications program, press Enter to send a carriage return to the PX-Series PDU. The
Username prompt appears.
4. Type a name and press Enter. The name is case sensitive. Then you are prompted to enter apassword.
5. Type a password and press Enter. The password is case sensitive.
After properly entering the password, the PX-Series PDU name appears at the prompt.
Tip: The 'Last login' information, including the date and time, is also displayed if the same user account
was used to log in to this product's web interface or CLI.
6. You are now logged in to the command line interface and can begin using commands.

With SSH or Telnet
You can remotely log in to the command line interface (CLI) using an SSH or Telnet client, such as PuTTY.
Note: PuTTY is a free program you can download from the Internet. Refer to PuTTY's documentation for
details on configuration.

▶ To log in using SSH or Telnet:
1. Ensure SSH or Telnet has been enabled.
2. Launch an SSH or Telnet client and open a console window. A login prompt appears.

3. Type a name and press Enter. The name is case sensitive.
Note: If using the SSH client, the name must NOT exceed 25 characters. Otherwise, the login fails.

405

Then you are prompted to enter a password.

4. Type a password and press Enter. The password is case sensitive.
5. After properly entering the password, the PX-Series PDU name appears at the prompt.
Tip: The 'Last login' information, including the date and time, is also displayed if the same user account
was used to log in to this product's web interface or CLI.
6. You are now logged in to the command line interface and can begin administering this product.

With an Analog Modem
The PX-Series PDU supports remote access to the CLI via a connected analog modem. This feature isespecially useful when the LAN access is not available.

▶ To connect to the PX-Series PDU via the modem:
1. Make sure the PX-Series PDU has an analog modem connected. See Connecting an Analog Modem.
2. Make sure the computer you are using has an appropriate modem connected.
3. Launch a terminal emulation program, and configure its baud rate settings according to the baudrate set for the analog modem connected to the PX-Series PDU. See Configuring the Serial Port.
4. Type the following AT command to make a connection with the PX-Series PDU.
ATD<modem phone number>
5. The CLI login prompt appears after the connection is established successfully. Then type the username and password to log in to the CLI.

▶ To disconnect from the PX-Series PDU:
1. Return to the modem's command mode using the escape code +++.
2. After the OK prompt appears, type the following AT command to disconnect from the PX-Series PDU.
ATH

Different CLI Modes and Prompts
Depending on the login name you use and the mode you enter, the system prompt in the CLI varies. The
device name appears with the prompt.

406

•

User Mode: When you log in as a normal user, who may not have full permissions to configure the
PX-Series PDU, the > prompt appears.

•

Administrator Mode: When you log in as an administrator, who has full permissions to configure the
PX-Series PDU, the # prompt appears.

•

Configuration Mode: You can enter the configuration mode from the administrator or user mode. In
this mode, the prompt changes to config:# or config:> and you can change PX-Series PDU device andnetwork configurations. See Configuring the Device and Network (on page 438).

•

Diagnostic Mode: You can enter the diagnostic mode from the administrator or user mode. In thismode, the prompt changes to diag:# or diag:> and you can perform the network troubleshooting
commands, such as the ping command. See Network Troubleshooting in Diagnostic Mode (on page
559).

Closing a Local Connection
Close the window or terminal emulation program when you finish accessing the PX-Series PDU over the
local connection.
When accessing or upgrading multiple PX-Series PDU devices, do not transfer the local connection cablefrom one device to another without closing the local connection window first.

Logging out of CLI
After completing your tasks using the CLI, always log out of the CLI to prevent others from accessing the
CLI.

▶ To log out of the CLI:
1. Ensure you have entered administrator mode and the # prompt is displayed.
2. Type exit and press Enter.

Tips for Using the CLI

The ? Command for Showing Available Commands
When you are not familiar with CLI commands, you can press the ? key at anytime for one of thefollowing purposes.
•

Show a list of main CLI commands available in the current mode.

•

Show a list of available commands or parameters for the command you type.

▶ In the administrator mode:
#

?

407

▶ In the configuration mode:?

config:#▶ In the diagnostic mode:?

diag:#

Press Enter after pressing the ? command, and a list of main commands for the current mode isdisplayed.

Querying Available Parameters for a Command
If you are not sure what commands or parameters are available for a particular type of CLI command or
its syntax, you can have the CLI show them by adding a space and the help command (?) or list
command (ls) to the end of that command. A list of available parameters and their descriptions will be
displayed.
The following shows a few query examples.

▶ To query available parameters for the "show" command:#show ?

▶ To query available parameters for the "show user" command:#show user ?

▶ To query available role configuration parameters:
config:#role ?

▶ To query available parameters for the "role create" command:
config:#role create ?

Retrieving Previous Commands
If you would like to retrieve any command that was previously typed in the same connection session,press the Up arrow (408) on the keyboard several times until the desired command is displayed.

Automatically Completing a Command
A CLI command always consists of several words. You can easily enter a command by typing first word(s)or letter(s) and then pressing Tab or Ctrl+i instead of typing the whole command word by word.

▶ To have a command completed automatically:
1. Type initial letters or words of the desired command. Make sure the letters or words you typed are
unique so that the CLI can identify the command you want.
2. Press Tab or Ctrl+i until the complete command appears.
3. If there are more than one possible commands, a list of these commands is displayed. Then type thefull command.

▶ Examples:•

Example 1 (only one possible command):a. Type the first word and the first letter of the second word of the "reset
factorydefaults" command -- that is, reset f.
b. Then press Tab or Ctrl+i to complete the second word.

•

Example 2 (only one possible command):a. Type the first word and initial letters of the second word of the "security
strongPasswords" command -- that is, security str.
b. Then press Tab or Ctrl+i to complete the second word.

•

Example 3 (more than one possible commands):
a. Type only the first two words of the "network ipv4 gateway xxx.xxx.xxx.xxx"
command -- that is, network ipv4.
b. Then press Tab or Ctrl+i one or two times, a list of possible commands displays as shown
below.
gatewayinterfacestaticRoutes

c. Type the full command "network ipv4 gateway xxx.xxx.xxx.xxx", according
to the onscreen command list.

Multi-Command Syntax
To shorten the configuration time, you can combine various configuration commands in one command
to perform all of them at a time. All combined commands must belong to the same configuration type,such as commands prefixed with network, user modify, sensor externalsensor and so on.
A multi-command syntax looks like this:<configuration type> <setting 1> <value 1> <setting 2> <value 2><setting 3> <value 3> ...

409

▶ Example 1 - Combination of ETH1's Activation, Configuration Method and IP
The following multi-command syntax configures IPv4 address, configuration method and activation
status for ETH1's network connectivity simultaneously.
config:# network ipv4 interface eth1 enabled true configMethod static
address 192.168.84.225/24
Results:•

The ETH1 interface is enabled.

•

ETH1's configuration method is set to static IP address.

•

ETH1's IPv4 address is set to 192.168.84.225/24.

▶ Example 2 - Combination of Upper Critical and Upper Warning Settings
The following multi-command syntax simultaneously configures Upper Critical and Upper Warning
thresholds for the RMS current of the 2nd overcurrent protector.
config:#sensor ocp 2 current upperCritical disable upperWarning 15

Results:•

The Upper Critical threshold of the 2nd overcurrent protector's RMS current is disabled.

•

The Upper Warning threshold of the 2nd overcurrent protector's RMS current is set to 15A andenabled at the same time.

▶ Example 3 - Combination of SSID and PSK Parameters
This multi-command syntax configures both SSID and PSK parameters simultaneously for the wirelessfeature.
config:#network wireless SSID myssid PSK encryp_key

Results:•

The SSID value is set to myssid.

•

The PSK value is set to encryp_key.

▶ Example 4 - Combination of Upper Critical, Upper Warning and Lower Warning Settings
The following multi-command syntax configures Upper Critical, Upper Warning and Lower Warning
thresholds for the outlet 5 RMS current simultaneously.

410

config:# sensor outlet 5 current upperCritical disable upperWarning enable
lowerWarning 1.0
Results:•

The Upper Critical threshold of outlet 5 RMS current is disabled.

•

The Upper Warning threshold of outlet 5 RMS current is enabled.

•

The Lower Warning threshold of outlet 5 RMS current is set to 1.0A and enabled at the same time.

Showing Information
You can use the show commands to view current settings or the status of the PX-Series PDU device orpart of it, such as the IP address, networking mode, firmware version, states or readings of internal orexternal sensors, user profiles, and so on.
Some "show" commands have two formats: one with the parameter "details" and the other without.
The difference is that the command without the parameter "details" displays a shortened version of
information while the other displays in-depth information.
After typing a "show" command, press Enter to execute it.
Note: Depending on your login name, the # prompt may be replaced by the > prompt.

Network Configuration
This command shows all network configuration and all network interfaces' information, such as the IP
address, MAC address, the Ethernet interfaces' duplex mode, and the wireless interface's status/
settings.
#

show network

IP Configuration
This command shows the IP settings shared by all network interfaces, such as DNS and routes.
Information shown will include both IPv4 and IPv6 configuration.
#

show network ip common

To show the IP settings of a specific network interface, use the following command.
#show network ip interface <ETH>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.

411

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.
Interface Description
eth1

Show the IP-related configuration of the ETH1 interface.

eth2

Show the IP-related configuration of the ETH2 interface.

wireless

Show the IP-related configuration of the WIRELESS interface.

bridgeShow the IP-related configuration of the BRIDGE interface.

all

Show the IP-related configuration of all interfaces.

Tip: You can also type the command without adding thisoption "all" to get the same data. That is, show network ip
interface.

IPv4-Only or IPv6-Only Configuration
To show IPv4-only or IPv6-only configuration, use any of the following commands.

▶ To show IPv4 settings shared by all network interfaces, such as DNS and routes:#

show network ipv4 common▶ To show IPv6 settings shared by all network interfaces, such as DNS and routes:#

show network ipv6 common▶ To show the IPv4 configuration of a specific network interface:#show network ipv4 interface <ETH>▶ To show the IPv6 configuration of a specific network interface:#412

show network ipv6 interface <ETH>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.

Interface Description
eth1

Show the IPv4 or IPv6 configuration of the ETH1 interface.

eth2

Show the IPv4 or IPv6 configuration of the ETH2 interface.

wireless

Show the IPv4 or IPv6 configuration of the WIRELESS interface.

bridgeShow the IPv4 or IPv6 configuration of the BRIDGE interface.

all

Show the IPv4 or IPv6 configuration of all interfaces.

Tip: You can also type the command without adding thisoption "all" to get the same data. That is, show network ipv4
interface.

Network Diagnostics▶ Show network diagnostics log:
This command shows the network diagnostics (Wi-Fi/802.1x) log.
#

show network diagLog▶ Clear network diagnostics log:
This command clear the network diagnostics log.
#

clear networkDiagLog

Network Interface Settings
This command shows the specified network interface's information which is NOT related to IP
configuration. For example, the Ethernet port's LAN interface speed and duplex mode, or the wirelessinterface's SSID parameter and authentication protocol.

413

#

show network interface <ETH>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.

Interface Description
eth1

Show the ETH1 interface's non-IP settings.

eth2Show the ETH2 interface's non-IP settings.

wireless

Show the WIRELESS interface's non-IP settings.

bridgeShow the BRIDGE interface's non-IP settings.

allShow the non-IP settings of all interfaces.

Tip: You can also type the command without adding thisoption "all" to get the same data. That is, show network
interface.

Network Service Settings
This command shows the network service settings only, including the Telnet setting, TCP ports for HTTP,HTTPS, SSH and Modbus/TCP services, and SNMP settings.
#

show network services <option>

Variables:•<option> is one of the options: all, http, https, telnet, ssh, snmp, modbus and zeroconfig.

OptionDescription

all

Displays the settings of all network services, including HTTP, HTTPS,
Telnet, SSH and SNMP.

Tip: You can also type the command without adding this option"all" to get the same data.
http

414

Only displays the TCP port for the HTTP service.

OptionDescription

https

Only displays the TCP port for the HTTPS service.

telnetOnly displays the settings of the Telnet service.

ssh

Only displays the settings of the SSH service.

snmp

Only displays the SNMP settings.

modbusOnly displays the settings of the Modbus/TCP service.

redfishOnly displays the redfish service settings.

zeroconfig Only displays the settings of the zero configuration advertising.

Device Configuration
This command shows the device configuration, such as the device name, firmware version, model typeand upper limit of active powered dry contact actuators. The CLI is supported by various Xerus products.
#

show pdu

To show detailed information, add the parameter "details" to the end of the command.
#show pdu details

Note: Your Xerus product may not support all commands.

Outlet Information
This command syntax shows the outlet information.
#

show outlets <n>

To show detailed information, add the parameter "details" to the end of the command.
#show outlets <n> details

415

Variables:•<n> is one of the options: all, or a number.

OptionDescription

all

Displays the information for all outlets.

Tip: You can also type the command without adding thisoption "all" to get the same data.
A specific outlet Displays the information for the specified outlet only.
number

Displayed information:•

Without the parameter "details," only the outlet name and state are displayed.

•

With the parameter "details," more outlet information is displayed in addition to the state, such as
rated current, voltage, active power, active energy, and outlet settings.

Outlet Group Information
This command syntax shows the outlet group information.
#

show outletgroups <n>

To show detailed information, add the parameter "details" to the end of the command.
#show outletgroups <n> details

Variables:•<n> is one of the options: all, or a number.

OptionDescription

all

Displays the information for all outlet groups.

Tip: You can also type the command without adding thisoption "all" to get the same data.
A specific outlet
group number

416

Displays the information for the specified outlet group only.

Displayed information:•

Without the parameter "details," only the group's name, the group's index number, member outlets
and the group's power state (if it is a switched PDU) are displayed.

•

With the parameter "details," more inlet information is displayed in addition to the above outlet
group information, such as each member outlet's power state and the group's active energy.

Tip: PX-Series PDU allows you to assign the same name to diverse outlet groups. If this really occurs, you
still can identify different groups through their unique index numbers.

Inlet Information
This command syntax shows the inlet information.
#

show inlets <n>

To show detailed information, add the parameter "details" to the end of the command.
#show inlets <n> details

Variables:•<n> is one of the options: all, or a number.

OptionDescription

all

Displays the information for all inlets.

Tip: You can also type the command without adding thisoption "all" to get the same data.
A specificinlet number

Displays the information for the specified inlet only.
An inlet number needs to be specified only when there are morethan 1 inlet on your PDU.

Displayed information:•

Without the parameter "details," only the inlet's name and RMS current are displayed.

•

With the parameter "details," more inlet information is displayed in addition to the inlet name andRMS current, such as the inlet's RMS voltage, active power and active energy.

Overcurrent Protector Information
This command is only available for models with overcurrent protectors for protecting outlets.
This command syntax shows the overcurrent protector information, such as a circuit breaker or a fuse.

417

#

show ocp <n>

To show detailed information, add the parameter "details" to the end of the command.
#show ocp <n> details

Variables:•<n> is one of the options: all, or a number.

OptionDescription

all

Displays the information for all overcurrent protectors.

Tip: You can also type the command without adding
this option "all" to get the same data.
A specificovercurrent
protector number

Displays the information for the specified overcurrent
protector only.

Displayed information:•

Without the parameter "details," only the overcurrent protector status and name are displayed.

•

With the parameter "details," more overcurrent protector information is displayed in addition to
status, such as the rating and RMS current value.

•

For Raritan's outlet-metered models that support "outlet peak current" sensors, information
indicating which outlet MAY cause the OCP-tripped event is available with this command. See
Possible OCP-Tripped Root Cause.

Date and Time Settings
This command shows the current date and time settings on the PX-Series PDU.
#

show time

To show detailed information, add the parameter "details" to the end of the command.
#show time details

Default Measurement Units
This command shows the default measurement units applied to the PX-Series PDU web and CLIinterfaces across all users, especially those users authenticated through remote authentication servers.

418

#

show user defaultPreferences

Note: If a user has set their own preferred measurement units or the administrator has changed any
user's preferred units, the web and CLI interfaces show the preferred measurement units for that user
instead of the default ones. See Existing User Profiles (on page 431) for the preferred measurement
units for a specific user.

Environmental Sensor Information
This command syntax shows the environmental sensor's information.
#

show externalsensors <n>

To show detailed information, add the parameter "details" to the end of the command.
#show externalsensors <n> details

Variables:•<n> is one of the options: all, or a number.

OptionDescription

all

Displays the information of all environmental sensors.

Tip: You can also type the command without adding
this option "all" to get the same data.
A specificenvironmental sensor
number*

Displays the information for the specified environmental
sensor only.

419

* The environmental sensor number is the ID number assigned to the sensor, which can be found on the
Peripherals page of the PX-Series PDU web interface.
Displayed information:•

Without the parameter "details," only the sensor ID, sensor type and reading are displayed.
Note: A state sensor displays the sensor state instead of the reading.

•With the parameter "details," more information is displayed in addition to the ID number andsensor reading, such as the serial number, sensor position, and X, Y, and Z coordinates.

Environmental Sensor Package Information
Different from the "show externalsensors" commands, which show the reading, status andconfiguration of an individual environmental sensor, the following command shows the information of
all connected environmental sensor packages, each of which may contain more than one sensor or
actuator.
#show peripheralDevicePackages

Information similar to the following is displayed. Peripheral Device Package refers to an environmental
sensor package.
Peripheral Device Package 1
Serial Number: 1GE7A00022
Package Type: DX2-T1H1
Position: Port 1, Chain Position 1
Package State: operationalFirmware Version: 33.0
Peripheral Device Package 2
Serial Number: 1GE7A00021
Package Type: DX2-T3H1
Position: Port 1, Chain Position 2
Package State: operationalFirmware Version: 33.0

420

Actuator Information
This command syntax shows an actuator's information.
#

show actuators <n>

To show detailed information, add the parameter "details" to the end of the command.
#show actuators <n> details

Variables:•<n> is one of the options: all, or a number.

OptionDescription

all

Displays the information for all actuators.

Tip: You can also type the command without adding thisoption "all" to get the same data.
A specificactuator
number*

Displays the information for the specified actuator only.

* The actuator number is the ID number assigned to the actuator. The ID number can be found using
the PX-Series PDU web interface or CLI. It is an integer starting at 1.
Displayed information:•

Without the parameter "details," only the actuator ID, type and state are displayed.

•

With the parameter "details," more information is displayed in addition to the ID number andactuator state, such as the serial number and X, Y, and Z coordinates.

Outlet Sensor Threshold Information
This command syntax shows the specified outlet sensor's threshold-related information.
#

show sensor outlet <n> <sensor type>

To show detailed information, add the parameter "details" to the end of the command.
# show sensor outlet <n> <sensor type> details

421

Variables:•<n> is the number of the outlet whose sensors you want to query.

•<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

lineFrequency

Line frequency sensor

Displayed information:•

Without the parameter "details," only the sensor reading, state, threshold, deassertion hysteresis
and assertion timeout settings of the specified outlet sensor are displayed.

•

With the parameter "details," more sensor information is displayed, including resolution and range.

•

If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

Outlet Pole Sensor Threshold Information
This command is available for an in‑line monitor only, including PX2‑3000 and PX3‑3000 series.
This command syntax shows the specified outlet pole sensor's threshold-related information.
# show sensor outletpole <n> <p> <sensor type>
To show detailed information, add the parameter "details" to the end of the command.
# show sensor outletpole <n> <p> <sensor type> details
Variables:

422•<n> is the number of the outlet whose pole sensors you want to query.

•<p> is the label of the outlet pole whose sensors you want to query.
Pole

Label
<p>

Current sensor

Voltage sensor

1

L1

L1

L1 - L2

•

Pole

Label
<p>

Current sensor

Voltage sensor

2

L2

L2

L2 - L33

L3

L3

L3 - L1<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

Displayed information:•

Without the parameter "details," only the reading, state, threshold, deassertion hysteresis andassertion delay settings of the specified outlet pole sensor are displayed.

•

With the parameter "details," more sensor information is displayed, including resolution and range.

•

If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

Outlet Group Threshold Information
This command syntax shows the specified outlet group sensor's threshold-related information.
#

show sensor outletgroup <ID> <sensor type>

To show detailed information, add the parameter "details" to the end of the command.
# show sensor outletgroup <ID> <sensor type> details
Variables:•<ID> is an outlet group's index number.

•<sensor type> is one of the following sensor types:
Sensor type

Description

activePowerAn outlet group's active power sensor

activeEnergy

An outlet group's active energy sensor

For definitions on an outlet group's sensors, see Outlet Groups.

423

Displayed information:•

Without the parameter "details," only the sensor reading, state, threshold, deassertion hysteresis
and assertion timeout settings of the specified group sensor are displayed.

•

With the parameter "details," more sensor information is displayed, including resolution and range.

Inlet Sensor Threshold Information
This command is NOT available for an in‑line monitor (PX3-3000 series).
This command syntax shows the specified inlet sensor's threshold-related information.
#

show sensor inlet <n> <sensor type>

To show detailed information, add the parameter "details" to the end of the command.
# show sensor inlet <n> <sensor type> details
Variables:•<n> is the number of the inlet whose sensors you want to query. For a single-inlet PDU, <n> isalways 1.

•<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

unbalancedCurrent

Unbalanced load sensor

lineFrequency

Line frequency sensor

Displayed information:

424•

Without the parameter "details," only the reading, state, threshold, deassertion hysteresis andassertion timeout settings of the specified inlet sensor are displayed.

•

With the parameter "details," more sensor information is displayed, including resolution and range.

•

If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

▶ Additional sensors supported by specific models:Specific PX-Series PDU models support some or all of the following sensors. The CLI command(s) listed
above can be also applied to the following sensors. Note that the measurement unit of current values in
CLI is A, not mA.
Sensor type

Description

peakCurrent

Peak current sensor

reactivePower

Supported on PXC and Legrand
PDU only•

three-phase models also
support pole-level peakcurrent•

models with meteredbreakers also support
breaker-level peak current

Reactive power sensor

displacementPowerFactor Displacement power factor sensor
residualCurrent

residualDCCurrent

RCM current sensor•

For Type A, it is the sensor that detects residual
AC current.

•

For Type B, it is the sensor that detects bothresidual AC and DC current.

•

RCM DC current sensor - detects residual DC current
only.
Available only on PDUs with RCM Type B.

Note: For information on RCM Type A and B sensors, see RCM Current Sensor.

Inlet Pole Sensor Threshold Information
This command is only available for a three-phase PDU except for an in‑line monitor (PX3-3000 series).
This command syntax shows the specified inlet pole sensor's threshold-related information.
# show sensor inletpole <n> <p> <sensor type>
To show detailed information, add the parameter "details" to the end of the command.
# show sensor inletpole <n> <p> <sensor type> details
Variables:

425

•

<n> is the number of the inlet whose pole sensors you want to query. For a single-inlet PDU, <n> isalways 1.

•<p> is the label of the inlet pole whose sensors you want to query.

•

Pole

Label
<p>

Current sensor

Voltage sensor

1

L1

L1

L1 - L22

L2

L2

L2 - L33

L3

L3

L3 - L1<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

Displayed information:•

Without the parameter "details," only the reading, state, threshold, deassertion hysteresis andassertion timeout settings of the specified inlet pole sensor are displayed.

•

With the parameter "details," more sensor information is displayed, including resolution and range.

•

If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

▶ Additional sensors supported by specific models:Specific PX-Series PDU models support some or all of the following sensors. The CLI command(s) listed
above can be also applied to the following sensors. Note that the measurement unit of current values in
CLI is A, not mA.
Sensor type

Description

peakCurrent

Peak current sensor

reactivePower

426

Reactive power sensor

Supported on PXC and Legrand
PDU only•

three-phase models also
support pole-level peakcurrent•

models with meteredbreakers also support
breaker-level peak current

Sensor type

Description

displacementPowerFactor Displacement power factor sensor
residualCurrent

residualDCCurrent

RCM current sensor•

For Type A, it is the sensor that detects residual
AC current.

•

For Type B, it is the sensor that detects bothresidual AC and DC current.

•

RCM DC current sensor - detects residual DC current
only.
Available only on PDUs with RCM Type B.

Note: For information on RCM Type A and B sensors, see RCM Current Sensor.

Overcurrent Protector Sensor Threshold Information
This command is only available for models with overcurrent protectors for protecting outlets.
This command syntax shows the specified overcurrent protector sensor's threshold-related information.
#

show sensor ocp <n> <sensor type>

To show detailed information, add the parameter "details" to the end of the command.
# show sensor ocp <n> <sensor type> details
Variables:•<n> is the number of the overcurrent protector whose sensors you want to query.

•<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

Displayed information:•

Without the parameter "details," only the reading, state, threshold, deassertion hysteresis andassertion timeout settings of the specified overcurrent protector sensor are displayed.

•

With the parameter "details," more sensor information is displayed, including resolution and range.

Environmental Sensor Threshold Information
This command syntax shows the specified environmental sensor's threshold-related information.

427

#

show sensor externalsensor <n>

To show detailed information, add the parameter "details" to the end of the command.
# show sensor externalsensor <n> details

Variables:•<n> is the environmental sensor number. The environmental sensor number is the ID number
assigned to the sensor, which can be found on the Peripherals page of the PX-Series PDU web
interface.

Displayed information:•

Without the parameter "details," only the reading, threshold, deassertion hysteresis and assertion
timeout settings of the specified environmental sensor are displayed.

•

With the parameter "details," more sensor information is displayed, including resolution and range.

Note: For a state sensor, the threshold-related and accuracy-related data is NOT available.

Environmental Sensor Default Thresholds
This command syntax shows a certain sensor type's default thresholds, which are the initial thresholds
applying to the specified type of sensor.

428

#

show defaultThresholds <sensor type>

To show detailed information, add the parameter "details" to the end of the command.
# show defaultThresholds <sensor type> details
Variables:•<sensor type> is one of the following numeric sensor types:

Sensor types

Description

absoluteHumidity Absolute humidity sensors
relativeHumidity

Relative humidity sensors

temperature

Temperature sensors

airPressure

Air pressure sensors

airFlow

Air flow sensors

vibration

Vibration sensors

all

All of the above numeric sensors

Tip: You can also type the command without adding thisoption "all" to get the same data.
Displayed information:•

Without the parameter "details," only the default upper and lower thresholds, deassertion
hysteresis and assertion timeout settings of the specified sensor type are displayed.

•

With the parameter "details," the threshold range is displayed in addition to default thresholds
settings.

Security Settings
This command shows the security settings of the PX-Series PDU.
#

show security

To show detailed information, add the parameter "details" to the end of the command.
#show security details429

Displayed information:•

Without the parameter "details," the information including IP access control, role-based access
control, password policy, and HTTPS encryption is displayed.

•

With the parameter "details," more security information is displayed, such as user blocking time,user idle timeout and front panel permissions (if supported by your model).

Authentication Settings▶ General authentication settings:
This command displays the authentication settings of the PX-Series PDU, including LDAP, Radius,and
TACACS+ settings.
#

show authentication▶ One LDAP server's settings:
To show the configuration of a specific LDAP server, assign the desired LDAP server with its sequential
number in the command. To get detailed information, add "details" to the end of the command.
#show authentication ldapServer <server_num>-- OR -# show authentication ldapServer <server_num> details▶ One Radius server's settings:
To show the configuration of a specific Radius server, assign the desired Radius server with its
sequential number in the command. To get detailed information, add "details" to the end of thecommand.
# show authentication radiusServer <server_num>-- OR-# show authentication radiusServer <server_num> details

430

▶ One TACACS+ server's settings:
To show the configuration of a specific TACACS+ server, assign the desired TACACS+ server with its
sequential number in the command. To get detailed information, add "details" to the end of thecommand.
# show authentication tacplusServer <server_num>-- OR-# show authentication tacplusServer <server_num> details
Variables:•<server_num> is the sequential number of the specified authentication server on the LDAP or
Radius or TACACS+ server list.

Displayed information:•

Without specifying any server, PX-Series PDU shows the authentication type and a list of LDAP,
Radius, and TACACS+ servers that have been configured.

•

When specifying a server, only that server's configuration is displayed. For LDAP server IP address/
hostname, server type, security, and port number are displayed, whereas Radius or TACCS+ servers
show their IP address/host name Authentication type and Port/s.

With the parameter "details" added, detailed information of the specified server is displayed, such as an
LDAP server's bind DN and the login name attribute. Whereas Radius and Tacacs+ servers show
accounting, timeout, retries, and shared secret values.

Existing User Profiles
This command shows the data of one or all existing user profiles.
#

show user <user_name>To show detailed information, add the parameter "details" to the end of the command.
#show user <user_name> details

431

Variables:•<user_name> is the name of the user whose profile you want to query. The variable can be one ofthe options: all or a user's name.

OptionDescription

allThis option shows all existing user profiles.

Tip: You can also type the command without adding thisoption "all" to get the same data.
a specific user's This option shows the profile of the specified user only.
name

Displayed information:•

Without the parameter "details," only four pieces of user information are displayed: user name,user "Enabled" status, SNMP v3 access privilege, and role(s).

•With the parameter "details," more user information is displayed, such as the telephone number,e‑mail address, preferred measurement units and so on.

Existing Roles
This command shows the data of one or all existing roles.
#

show roles <role_name>

Variables:•<role_name> is the name of the role whose permissions you want to query. The variable can be oneof the following options:

OptionDescription

allThis option shows all existing roles.

Tip: You can also type the command without adding thisoption "all" to get the same data.
a specific role's
name

432

This option shows the data of the specified role only.

Displayed information:•

Role settings are displayed, including the role description and privileges.

Load Shedding Settings
This section applies to outlet-switching capable models only.
This command shows the load shedding settings.
#

show loadshedding

Displayed information:•

The load shedding state is displayed along with non‑critical outlets.

Note: The load shedding mode is associated with critical and non-critical outlets. To specify critical andnon-critical outlets through CLI, see Specifying Non-Critical Outlets (on page 442).

Serial Port Settings
This command shows the baud rate setting of the serial port labeled CONSOLE / MODEM on the PXSeries PDU.
#

show serial

Asset Strip Settings
This command shows the asset strip settings, such as the total number of rack units (tag ports), asset
strip state, numbering mode, orientation, available tags and LED color settings.
#

show assetStrip <n>Variables:•<n> is one of the options: all, or a number.

OptionDescription

all

Displays all asset strip information.

Tip: You can also type the command without adding thisoption "all" to get the same data.

433

OptionDescription

A specificasset strip
number

Displays the settings of the asset strip connected to the specified
FEATURE port number.
For the PX-Series PDU device with only one FEATURE port, thevalid number is always 1.

Rack Unit Settings of an Asset Strip
A rack unit refers to a tag port on the asset strips. This command shows the settings of a specific rack
unit or all rack units on an asset strip, such as a rack unit's LED color and LED mode.
#show rackUnit <n> <rack_unit>

Variables:•<n> is the number of the FEATURE port where the selected asset strip is physically connected. For
the PX-Series PDU device with only one FEATURE port, the number is always 1.

•<rack_unit> is one of the options: all or a specific rack unit's index number.

OptionDescription

all

Displays the settings of all rack units on the specified asset strip.

Tip: You can also type the command without adding thisoption "all" to get the same data.
A specificnumber

Displays the settings of the specified rack unit on the specified asset
strip.
Use the index number to specify the rack unit. The index number isavailable on the asset strip or the Asset Strip page of the webinterface.

Event Log
The command used to show the event log begins with show eventlog. You can add either the limit
or class parameters or both to show specific events.

▶ Show the last 30 entries:#

show eventlog▶ Show a specific number of last entries in the event log:#

434

show eventlog limit <n>▶ Show a specific type of events only:#

show eventlog class <event_type>▶ Show a specific number of last entries associated with a specific type of events only:# show eventlog limit <n> class <event_type>
Variables:••<n> is one of the options: all or a number.
OptionDescription

all

Displays all entries in the event log.

An integer
number

Displays the specified number of last entries in the event log.
The number ranges between 1 to 10,000.

<event_type> is one of the following event types.

Event type

Descriptionall

All events.

deviceDevice-related events, such as system starting or firmware
upgrade event.

userAdministration User management events, such as a new user profile or a newrole.
userActivity

User activities, such as login or logout.

sensorInternal or external sensor events, such as state changes ofany sensors.

serverMonitor

Server-monitoring records, such as a server being declared
reachable or unreachable.

assetManagement Raritan asset management events, such as asset tag
connections or disconnections.
modem

Modem-related events.

timerEvent

Scheduled action events.

webcamEvents for webcam management, if available.

cardReader

Events for card reader management, if available.

435

Network Connections Diagnostic Log
This command shows the diagnostic log for both the EAP authentication and wireless LAN connection.
#

show network diagLog

Server Reachability Information
This command shows all server reachability information with a list of monitored servers and status.
#

show serverReachability

Server Reachability Information for a Specific Server
To show the server reachability information for a certain IT device only, use the following command.
#show serverReachability server <n>

To show detailed information, add the parameter "details" to the end of the command.
# show serverReachability server <n> details
Variables:•<n> is a number representing the sequence of the IT device in the monitored server list.
You can find each IT device's sequence number using the CLI command of show
serverReachability as illustrated below.

Displayed information:•

Without the parameter "details," only the specified device's IP address, monitoring enabled/
disabled state and current status are displayed.

•

With the parameter "details," more settings for the specified device are displayed, such as numberof pings and wait time prior to the next ping.

Peripheral Devices Settings
This command shows peripheral devices settings, including Z coordinate format of external sensors,device altitude, peripheral device auto management, maximum number of concurrently active powered
dry contacts, and muting of other door handle.

436

#

show peripheralDevicesSetup

Command History
This command shows the command history for current connection session.
#

show history

Displayed information:•

A list of commands that were previously entered in the current session is displayed.

Reliability Data
This command shows the reliability data.
#

show reliability data

Reliability Error Log
This command shows the reliability error log.
#

show reliability errorlog <n>Variables:•<n> is one of the options: 0 (zero) or any other integer number.

OptionDescription0

Displays all entries in the reliability error log.

Tip: You can also type the command without adding thisoption "0" to get all data.
A specific
Displays the specified number of last entries in the reliability
integer number error log.

Reliability Hardware Failures
This command shows a list of detected hardware failures.
#show reliability hwfailures

For details, see Hardware Issue Detection.

437

Clearing Information
You can use the clear commands to remove unnecessary data.
After typing a "clear" command, press Enter to execute it.
Note: Depending on your login name, the # prompt may be replaced by the > prompt.

Clearing Event Log
This command removes all data from the event log.
#

clear eventlog-- OR -clear eventlog /y#If you entered the command without "/y," a message appears, prompting you to confirm theoperation. Type y to clear the event log or n to abort the operation.
If you type y, a message "Event log was cleared successfully" is displayed after all data in the event log isdeleted.

Clearing Diagnostic Log for Network Connections
This command removes all data from the diagnostic log for both the EAP authentication and WLAN
connection.
#clear networkDiagLog-- OR -#

clear networkDiagLog /yIf you entered the command without "/y," a message appears, prompting you to confirm theoperation. Type y to clear the log or n to abort the operation.

Configuring the Device and Network
To configure the device or network settings through the CLI, it is highly recommended to log in as theadministrator so that you have full permissions. If you enter configuration mode from user mode, you
may have limited permissions to make configuration changes.
To configure any settings, enter the configuration mode. Configuration commands are case sensitive.

438

▶ To enter configuration mode:
1. Ensure you have entered administrator mode and the # prompt is displayed.
2. Type config and press Enter.
3. The config:# prompt appears, indicating that you have entered configuration mode.

4. Now you can type any configuration command and press Enter to change the settings.
Important: To apply new configuration settings, you must issue the "apply"
command before closing the terminal emulation program. Closing the program does
not save any configuration changes.

▶ To quit the configuration mode, use either "apply" or "cancel" command:
config:#apply-- OR -config:#

cancelThe # or > prompt appears after pressing Enter, indicating that you have entered the administrator oruser mode.

Device Configuration Commands
Device configuration command begins with pdu. You can use the pdu configuration commands tochange the settings that apply to the whole device.
Configuration commands are case sensitive so ensure you capitalize them correctly.

Changing the Device Nameconfig:#pdu name "<name>"

Variables:•<name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be
enclosed in quotes when it contains spaces.

Setting the Outlet Relay Behavior
This section applies to outlet-switching capable models only.
This command syntax determines the relay behavior of all outlets on a PX-Series PDU model.

439

config:#

pdu relayBehaviorOnPowerLoss <option>

Variables:•<option> is one of the options: latching or nonLatching

Setting the Outlet Power-On SequenceThis section applies to outlet-switching capable models only.
This command sets the outlet power-on sequence when the PDU powers up.
config:#pdu outletSequence <option>

Variables:•<option> is one of the options: default, or a comma-separated list of outlet numbers.
OptionDescription

default

All outlets are switched ON in the ASCENDING order (fromoutlet 1 to the final outlet) when the PX-Series PDU powers
up.

A commaseparated list ofoutlet numbers

All outlets are switched ON in the order you specify using thecomma-separated list.
The list must include all outlets on the PDU.

Note: Power-on sequencing is disabled in the latching mode.

Setting the Outlet Power-On Sequence Delay
This section applies to outlet-switching capable models only.
This command sets the delays (in seconds) for outlets when turning on all outlets in sequence.
config:# pdu outletSequenceDelay <outlet1>:<delay1>;<outlet2>:<delay2>;<outlet3>:<delay3>;...
Separate outlet numbers and their delay settings with a colon. Outlets followed by delays are separated
with a semicolon.

440

Variables:•<outlet1>, <outlet2>, <outlet3> and the like are individual outlet numbers or a range of outlets
using a dash. For example, 3-8 represents outlets 3 to 8.

•<delay1>, <delay2>, <delay3> and the like are the delay time in seconds.

Note: Power-on sequencing is disabled in the latching mode.

Setting the PDU-Defined Default Outlet State
This section applies to outlet-switching capable models only.
This command determines the initial power condition of all outlets after powering up the PDU. Thissetting is used in three scenarios:•

powering up the whole PDU•

powering up a single inlet in a multi-inlet PDU (on most, but not all, multi-inlet units the outlet
boards are powered through the respective inlet)•transfer switch switches on again after being off due to e.g. internal failure

config:#pdu outletStateOnPowerUp <option>

Variables:•<option> is one of the options: off, on or lastKnownState.
OptionDescription

off

Switches OFF all outlets when the PX-Series PDU powers up.

on

Switches ON all outlets when the PX-Series PDU powers up.

lastKnownState Restores all outlets to the previous status before powering down
the PX-Series PDU when the PDU powers up again.

Note: This feature does NOT take effect and cannot be configured on a PX-Series PDU device after theoutlet relay is set to the "Latching" mode.

Setting the PDU-Defined Cycling Power-Off Period
This section applies to outlet-switching capable models only.
This command sets the power-off period of the power cycling operation for all outlets.

441

config:#

pdu cyclingPowerOffPeriod <timing>

Variables:•<timing> is the time of the cycling power-off period in seconds, which is an integer between 0 and
3600, or pduDefined for following the PDU-defined timing.

Setting the Inrush Guard Delay Time
This section applies to outlet-switching capable models only.
This command sets the inrush guard delay.
config:#pdu inrushGuardDelay <timing>

Variables:•<timing> is a delay time between 100 and 100000 milliseconds.

Setting the Outlet Initialization Delay
This section applies to outlet-switching capable models only.
This command determines the outlet initialization delay timing on device startup. See PDU for
information on outlet initialization delay.
config:#pdu outletInitializationDelayOnPowerUp <timing>

Variables:•<timing> is a delay time between 1 and 3600 seconds.

Note: This feature does NOT take effect and cannot be configured on a PX-Series PDU device after theoutlet relay is set to the "Latching" mode.

Specifying Non-Critical Outlets
This section applies to outlet-switching capable models only.
This command determines critical and non-critical outlets. It is associated with the load shedding mode.
See Load Shedding Mode.

442

config:#

pdu nonCriticalOutlets <outlets1>:false;<outlets2>:true

Separate outlet numbers and their settings with a colon. Separate each "false" and "true" setting with asemicolon.
Variables:••<outlets1> is one or multiple outlet numbers to be set as critical outlets. Use commas to separate
outlet numbers.
Use a dash for a range of consecutive outlets. For example, 3-8 represents outlets 3 to 8.
<outlets2> is one or multiple outlet numbers to be set as NON‑critical outlets. Use commas toseparate outlet numbers.
Use a dash for a range of consecutive outlets. For example, 3-8 represents outlets 3 to 8.

Enabling or Disabling Data Logging
This command enables or disables the data logging feature.
config:#pdu dataRetrieval <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableEnables the data logging feature.

disableDisables the data logging feature.

Setting Data Logging Measurements Per Entry
This command defines the number of measurements accumulated per log entry.
config:#pdu measurementsPerLogEntry <number>

Variables:•<number> is an integer between 1 and 600. The default is 60 samples per log entry.

Setting Log Capacity
This command defines the size of data log (records per sensor).
config:#pdu logCapacity <number>

443

Variables:•<number> is an integer between 60 and 20,000. Desired default log capacity is 120.

Enabling or Disabling data backup
This command enables or disables the data backup feature.
config:#pdu dataBackup <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableEnables the data logging feature.

disableDisables the data logging feature.

Network Configuration Commands
A network configuration command begins with network. A number of network settings can be changed
through the CLI, such as the IP address, transmission speed, duplex mode, and so on.

Configuring IPv4 Parameters
An IPv4 configuration command begins with network ipv4.

Setting the IPv4 Configuration Mode
This command determines the IP configuration mode.
config:#network ipv4 interface <ETH> configMethod <mode>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.
Interface Description
eth1

444

Determine the IPv4 configuration mode of the ETH1 interface (wired
networking).

Interface Description

•

eth2

Determine the IPv4 configuration mode of the ETH2 interface (wired
networking).

wireless

Determine the IPv4 configuration mode of the WIRELESS interface(that is, wireless networking).

bridgeDetermine the IPv4 configuration mode of the BRIDGE interface (thatis, bridging mode).

<mode> is one of the modes: dhcp or static.
Mode

Description

dhcp

The IPv4 configuration mode is set to DHCP.

staticThe IPv4 configuration mode is set to static IP address.

Setting the IPv4 Preferred Host Name
After selecting DHCP as the IPv4 configuration mode, you can specify the preferred host name, which is
optional. The following is the command:
config:#network ipv4 interface <ETH> preferredHostName <name>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.
Interface Description

•

eth1

Determine the IPv4 preferred host name of the ETH1 interface (thatis, wired networking).

eth2

Determine the IPv4 preferred host name of the ETH2 interface (thatis, wired networking).

wireless

Determine the IPv4 preferred host name of the WIRELESS interface(that is, wireless networking).

bridgeDetermine the IPv4 preferred host name of the BRIDGE interface (thatis, bridging mode).

<name> is a host name which:445

• Consists of alphanumeric characters and/or hyphens• Cannot begin or end with a hyphen• Cannot contain more than 63 characters• Cannot contain punctuation marks, spaces, and other symbols

Setting the IPv4 Address
After selecting the static IP configuration mode, you can use this command to assign a permanent IP
address to the PX-Series PDU.
config:#network ipv4 interface <ETH> address <ip address>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.
Interface Description

•

eth1

Determine the IPv4 address of the ETH1 interface (that is, wired
networking).

eth2

Determine the IPv4 address of the ETH2 interface (that is, wired
networking).

wireless

Determine the IPv4 address of the WIRELESS interface (that is,wireless networking).

bridgeDetermine the IPv4 address of the BRIDGE interface (that is, thebridging mode).

<ip address> is the IP address being assigned to your PX-Series PDU. Its format is "IP address/prefix".
For example, 192.168.84.99/24.

Setting the IPv4 Gateway
After selecting the static IP configuration mode, you can use this command to specify the gateway.
config:# network ipv4 interface eth1 gateway <ipaddress>
Variables:•446<ip address> is the IP address of the gateway. The value ranges from 0.0.0.0 to 255.255.255.255.

Interface Description
eth1

Determine the IPv4 address of the ETH1 interface (that is, wired
networking).

eth2

Determine the IPv4 address of the ETH2 interface (that is, wired
networking).

wireless

Determine the IPv4 address of the WIRELESS interface (that is,wireless networking).

bridgeDetermine the IPv4 address of the BRIDGE interface (that is, thebridging mode).

Setting IPv4 Static Routes
If the IPv4 network mode is set to static IP and your local network contains two subnets, you canconfigure static routes to enable or disable communications between the PX-Series PDU and devices in
the other subnet.
These commands are prefixed with network ipv4 staticRoutes.
Depending on whether the other network is directly reachable or not, there are two methods foradding a static route. For further information, see Static Route Examples.

▶ Method 1: add a static route when the other network is NOT directly reachable:
config:# network ipv4 staticRoutes add <dest-1> nextHop <hop>▶ Method 2: add a static route when the other network is directly reachable:
config:#network ipv4 staticRoutes add <dest-1> interface <ETH>▶ Delete an existing static route:config:#network ipv4 staticRoutes delete <route_ID>▶ Modify an existing static route:config:# network ipv4 staticRoutes modify <route_ID> dest <dest-2> nextHop<hop>-- OR --

447

config:# network ipv4 staticRoutes modify <route_ID> dest <dest-2>
interface <ETH>
Variables:•<dest-1> is a combination of the IP address and subnet mask of the other subnet. The format is IP
address/subnet mask.

•<hop> is the IP address of the next hop router.

•<ETH> is one of the interfaces: ETH1/ETH2, WIRELESS and BRIDGE. Type "bridge" only when yourPX-Series PDU is in the bridging mode.

•<route_ID> is the ID number of the route setting which you want to delete or modify.

•<dest-2> is a modified route setting that will replace the original route setting. Its format is IP
address/subnet mask. You can modify either the IP address or the subnet mask or both.

Configuring IPv6 Parameters
An IPv6 configuration command begins with network ipv6.

Setting the IPv6 Configuration Mode
This command determines the IP configuration mode.
config:#network ipv6 interface <ETH> configMethod <mode>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.
Interface Description

448

eth1

Determine the IPv6 configuration mode of the ETH1 interface (wired
networking).

eth2

Determine the IPv6 configuration mode of the ETH2 interface (wired
networking).

wireless

Determine the IPv6 configuration mode of the WIRELESS interface(that is, wireless networking).

Interface Description
bridge•Determine the IPv6 configuration mode of the BRIDGE interface (thatis, bridging mode).

<mode> is one of the modes: automatic or static.

Mode

Description

automatic*

The IPv6 configuration mode is set to automatic.

staticThe IPv6 configuration mode is set to static IP address.

*You can configure the PX-Series PDU to either "Manual" or "Automatic" IPv6 settings. In manual mode,
you must specify the device's IP address, the default router, the DNS server etc. But when Automatic
mode is selected, the behavior of the PX-Series PDU depends on the configuration of the Router
Advertisement (RA) in the network's router. If the RA contains a Prefix Information that has the"Autonomous address-configuration flag" set, the PX-Series PDU will use SLAAC and use an IPv6 address
based on that Prefix and its own MAC address. If the RA has the "otherconf" flag set, the PX-Series PDU
will also use Stateless DHCP to retrieve information like a DNS server. If the "managed" flag is set in theRA, Stateful Address Auto configuration is used via DHCPv6. Both modes (SLAAC and DHCPv6) can beused at the same time.

Setting the IPv6 Preferred Host Name
After selecting DHCP as the IPv6 configuration mode, you can specify the preferred host name, which is
optional. The following is the command:
config:#network ipv6 interface <ETH> preferredHostName <name>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.
Interface Description
eth1

Determine the IPv6 preferred host name of the ETH1 interface (wired
networking).

eth2

Determine the IPv6 preferred host name of the ETH2 interface (wired
networking).

wireless

Determine the IPv6 preferred host name of the WIRELESS interface(that is, wireless networking).

449

Interface Description
bridge•Determine the IPv6 preferred host name of the BRIDGE interface (thatis, bridging mode).

<name> is a host name which:• Consists of alphanumeric characters and/or hyphens• Cannot begin or end with a hyphen• Cannot contain more than 63 characters•

Cannot contain punctuation marks, spaces, and other symbols

Setting the IPv6 Address
After selecting the static IP configuration mode, you can use this command to assign a permanent IP
address to the PX-Series PDU.
config:# network ipv6 interface <ETH> address <ipaddress>
Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE. Note that you mustchoose/configure the bridge interface if your PX-Series PDU is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IPparameters of ETH1/ETH2 and WIRELESS interfaces do NOT function.
Interface Description

•

eth1

Determine the IPv6 address of the ETH1 interface (wired networking).

eth2

Determine the IPv6 address of the ETH2 interface (wired networking).

wireless

Determine the IPv6 address of the WIRELESS interface (that is,wireless networking).

bridgeDetermine the IPv6 address of the BRIDGE interface (that is, thebridging mode).

<ip address> is the IP address being assigned to your PX-Series PDU. This value uses the IPv6 addressformat. Note that you must add /xx, which indicates a prefix length of bits such as /64, to the end of
this IPv6 address.

Setting the IPv6 Gateway
After selecting the static IP configuration mode, you can use this command to specify the gateway.

450

config:# network ipv6 interface gateway eth1 <ipaddress>
Variables:•<ip address> is the IP address of the gateway. This value uses the IPv6 address format.
Interface Description
eth1

Determine the IPv6 address of the ETH1 interface (that is, wired
networking).

eth2

Determine the IPv6 address of the ETH2 interface (that is, wired
networking).

wireless

Determine the IPv6 address of the WIRELESS interface (that is,wireless networking).

bridgeDetermine the IPv6 address of the BRIDGE interface (that is, thebridging mode).

Setting IPv6 Static Routes
If the IPv6 network mode is set to static IP and your local network contains two subnets, you canconfigure static routes to enable or disable communications between the PX-Series PDU and devices in
the other subnet.
These commands are prefixed with network ipv6 staticRoutes.
Depending on whether the other network is directly reachable or not, there are two methods foradding a static route. For further information, see Static Route Examples.

▶ Method 1: add a static route when the other network is NOT directly reachable:
config:# network ipv6 staticRoutes add <dest-1> nextHop <hop>▶ Method 2: add a static route when the other network is directly reachable:
config:#network ipv6 staticRoutes add <dest-1> interface <ETH>▶ Delete an existing static route:config:#network ipv6 staticRoutes delete <route_ID>451

▶ Modify an existing static route:config:# network ipv6 staticRoutes modify <route_ID> dest <dest-2>
nextHop <hop>-- OR -config:# network ipv6 staticRoutes modify <route_ID> dest <dest-2>
interface <ETH>
Variables:•<dest-1> is the IP address and prefix length of the subnet where the PX-Series PDU belongs. The
format is IP address/prefix length.

•<hop> is the IP address of the next hop router.

•<ETH> is one of the interfaces: ETH1/ETH2, WIRELESS and BRIDGE. Type "bridge" only when yourPX-Series PDU is in the bridging mode.

•<route_ID> is the ID number of the route setting which you want to delete or modify.

•<dest-2> is a modified route setting that will replace the original route setting. Its format is IP
address/prefix length. You can modify either the IP address or the prefix length or both.

Configuring DNS Parameters
Use the following commands to configure static DNS-related settings.

▶ Specify the primary DNS server:
config:#network dns firstServer <ip address>▶ Specify the secondary DNS server:
config:#network dns secondServer <ip address>▶ Specify the third DNS server:
config:#network dns thirdServer <ip address>▶ Specify one or multiple optional DNS search suffixes:
config:#452

network dns searchSuffixes <suffix1>

-- OR -config:# network dns searchSuffixes<suffix1>,<suffix2>,<suffix3>,...,<suffix6>▶ Determine which IP address is used when the DNS server returns both IPv4 and IPv6 addresses:
config:#network dns resolverPreference <resolver>

Variables:•<ip address> is the IP address of the DNS server.

•<suffix1>, <suffix2>, and the like are the DNS suffixes that automatically apply when searching forany device via PX-Series PDU. For example, <suffix1> can be raritan.com, and <suffix2> can belegrand.com. You can specify up to 6 suffixes by separating them with commas.

•<resolver> is one of the options: preferV4 or preferV6.
OptionDescription

preferV4

Use the IPv4 addresses returned by the DNS server.

preferV6

Use the IPv6 addresses returned by the DNS server.

Setting LAN Interface Parameters
A LAN interface configuration command begins with network ethernet.

Enabling or Disabling the LAN Interface
This command enables or disables the LAN interface.
config:#network ethernet <ETH> enabled <option>

Variables:••<ETH> is one of the options -- eth1 or eth2.
OptionDescription

eth1

ETH1 port

eth2

ETH2 port<option> is one of the options: true or false.

453

OptionDescriptiontrue

The specified network interface is enabled.

false

The specified network interface is disabled.

Changing the LAN Interface Speed
This command determines the LAN interface speed.
config:#network ethernet <ETH> speed <option>

Variables:••<ETH> is one of the options -- eth1 or eth2.
OptionDescription

eth1

ETH1 port

eth2

ETH2 port<option> is one of the options: auto, 10Mbps, 100Mbps or 1000Mbps.
OptionDescription

auto

System determines the optimum LAN speed through auto-negotiation.

10MbpsThe LAN speed is always 10 Mbps.

100Mbps

The LAN speed is always 100 Mbps.

1000Mbps The LAN speed is always 1000 Mbps.

Changing the LAN Duplex Mode
This command determines the LAN interface duplex mode.
config:#network ethernet <ETH> duplexMode <mode>

Variables:•

454<ETH> is one of the options -- eth1 or eth2.
OptionDescription

eth1

ETH1 port•

OptionDescription

eth2

ETH2 port<mode> is one of the modes: auto, half or full.
Option Description
auto

The PX-Series PDU selects the optimum transmission mode throughauto-negotiation.

half

Half duplex:
Data is transmitted in one direction (to or from the PX-Series PDU) at a
time.

full

Full duplex:
Data is transmitted in both directions simultaneously.

Setting the LAN MTUThis command sets the MTU for the ethernet interface.
config:#network ethernet <ETH> mtu <mtu>

Variables:•<ETH> is one of the options -- eth1 or eth2.

•<mtu> is the Maximum Transfer Unit. Enter a value from 1280-1500.

Setting the Ethernet Authentication Method
PX-Series PDU supports 802.1X (EAP) Network Authentication. Enable the ethernet interface, and then
set the authentication method.
config:# network ethernet <interface> [enabled<enabled>]
The following command sets the authentication method for the selected Ethernet interface to either
none or Extensible Authentication Protocol (EAP).
config:# network ethernet <ETH> authMethod <method>
Variables:•<ETH> is one of the options -- eth1 or eth2.

455

•

OptionDescription

eth1

ETH1 port

eth2

ETH2 port<method> is one of the authentication methods: NONE or EAP.
MethodDescription

NONE

The authentication method is set to NONE.

EAPThe authentication method is set to EAP.

Setting Ethernet EAP Parameters
When the selected Ethernet interface's authentication method is set to EAP, you must configure EAP
authentication parameters, including outer authentication, inner authentication, EAP identity, clientcertificate, client private key, password, CA certificate, and RADIUS authentication server. For more
information, see Ethernet Interface Settings.

▶ Determine the outer authentication protocol:
config:# network ethernet <ETH> eapOuterAuthentication <outer_auth>▶ Determine the inner authentication protocol for authentication set to "EAP + PEAP":
config:# network ethernet <ETH> eapInnerAuthentication <inner_auth>▶ Set the EAP identity:
config:#network ethernet <ETH> eapIdentity <identity>▶ Set the EAP password:
config:#network ethernet <ETH> eapPassword

After performing the above command, the PX-Series PDU prompts you to enter the password. Thentype the password and press Enter.

456▶ Provide a client certificate for authentication set to "EAP + TLS" or "EAP + PEAP + TLS":
config:#network ethernet <ETH> eapClientCertificate

After performing any certificate or private key commands, including commands for the client certificate,client private key, and CA certificate, the system prompts you to enter the contents of the wanted
certificate or key. For an example with detailed procedure, see EAP CA Certificate Example (on page459).

▶ Provide a client private key for authentication set to "EAP + TLS" or "EAP + PEAP + TLS":
config:#network ethernet <ETH> eapClientPrivateKey▶ Provide a CA TLS certificate for EAP:
config:#network ethernet <ETH> eapCACertificate▶ Eable or disable verification of the TLS certificate chain:config:#network ethernet <ETH> enableCertVerification <option1>▶ Allow expired and not yet valid TLS certificates:
config:#network ethernet <ETH> allowOffTimeRangeCerts <option2>▶ Allow network connection with incorrect system time:
config:# network ethernet <ETH> allowConnectionWithIncorrectClock<option3>▶ Set the RADIUS authentication server for EAP:
config:#network ethernet <ETH> eapAuthServerName <FQDN>

Variables:•<ETH> is one of the options -- eth1 or eth2.

457

•

OptionDescription

eth1

ETH1 port

eth2

ETH2 port<outer_auth> is one of the options: PEAP or TLS.
Option Description

•

PEAP

Outer authentication is set to Protected Extensible Authentication
Protocol (PEAP).

TLS

Outer authentication is set to TLS.

<inner_auth> is one of the options: MS‑CHAPv2 or TLS.
OptionDescription

MSCHAPv2 Inner authentication is set to Microsoft's Challenge Authentication
Protocol Version 2 (MS‑CHAPv2).
TLS

Inner authentication is set to TLS.

•

<identity> is your user name for the EAP authentication.

•<option1> is one of the options: true or false.

•

OptionDescription

true

Enables the verification of the TLS certificate chain.

false

Disables the verification of the TLS certificate chain.

<option2> is one of the options: true or false.
Option Description

•

true

Always make the network connection successful even though the TLS
certificate chain contains any certificate which is outdated or not valid yet.

false

The network connection is NOT successfully established when the TLS
certificate chain contains any certificate which is outdated or not valid yet.

<option3> is one of the options: true or false.
Option Description
true

458

Make the network connection successful when the PX-Series PDU systemtime is earlier than the firmware build before synchronizing with the NTP
server, causing the TLS certificate to become invalid.

Option Description
false

•

The network connection is NOT successfully established when the PXSeries PDU finds that the TLS certificate is not valid due to incorrect
system time.

<FQDN> is the name of the RADIUS server if it is present in the TLS certificate. The name mustmatch the fully qualified domain name (FQDN) of the host shown in the certificate.

EAP CA Certificate Example
This section provides a CA certificate example for the Ethernet interface "ETH1". Your CA certificate
contents should be different from the contents displayed in this example.
In addition, the procedure of uploading the client certificate and client private key in CLI is similar to thefollowing example, except for the CLI command.

▶ To provide a CA certificate:
1. Make sure you have entered the configuration mode.
2. Type the following command for ETH1 and press Enter.
config:#network ethernet eth1 eapCACertificate

3. The system prompts you to enter the contents of the CA certificate.
4. Open a CA certificate using a text editor. You should see certificate contents similar to the following.

5. Select and copy the contents as illustrated below, including the starting line containing "BEGIN
CERTIFICATE" and the ending line containing "END CERTIFICATE."
6. Paste the contents in the terminal.
7. Press Enter.
8. Verify whether the system shows the following command prompt, indicating the provided CA
certificate is valid.
config:#459

Removing the Uploaded Certificate or Private Key
The procedures of removing an existing client certificate, client private key or CA certificate in CLI are
similar.
This section illustrates such a procedure for the Ethernet interface "ETH1."▶ To remove a certificate or private key for ETH1:
1. Make sure you have entered the configuration mode.
2. Type the appropriate command, depending on which file you want to remove, and press Enter.
• Client certificate:config:#network ethernet eth1 eapClientCertificate• Client private key:
config:#network ethernet eth1 eapClientPrivateKey• CA certificate:config:#network ethernet eth1 eapCACertificate

3. The system prompts you to enter the contents of the chosen certificate or private key.
4. Press Enter without typing any data.
5. Verify whether the system shows the following command prompt, indicating the existing certificate
or private key has been removed.
config:#Setting Wireless Parameters
You must configure wireless parameters, including Service Set Identifier (SSID), authentication method,
Pre-Shared Key (PSK), and Basic Service Set Identifier (BSSID) after the wireless networking mode isenabled.
A wireless configuration command begins with network wireless.
Note: If wireless networking mode is not enabled, the SSID, PSK and BSSID values are not applied until
the wireless networking mode is enabled. In addition, a message appears, indicating that the active
network interface is not wireless.

Setting the SSID
This command specifies the SSID string.
config:#network wireless SSID <ssid>

Variables:•460<ssid> is the name of the wireless access point, which consists of:

- Up to 32 ASCII characters- No spaces- ASCII codes 0x20 ~ 0x7E

Enabling or Disabling 802.11n High Throughput
This command enables or disables the 802.11n high throughput protocol.
config:#network wireless enableHT <option>

Variables:•<option> is one of the options: true or false.
OptionDescriptiontrue

802.11n is enabled.

false

802.11n is disabled.

Setting the Wireless Authentication Method
This command sets the wireless authentication method to None, PSK, or Extensible Authentication
Protocol (EAP).
config:#network wireless authMethod <method>

Variables:•<method> is one of the authentication methods: PSK or EAP.
MethodDescription

PSK

The authentication method is set to PSK.

EAPThe authentication method is set to EAP.

None

The authentication method is set to None.

Setting the PSK
If the Pre-Shared Key (PSK) authentication method is selected, you must assign a PSK passphrase byusing this command.
config:#network wireless PSK <psk>461

Variables:•<psk> is a string or passphrase that consists of:- 8 to 63 characters- No spaces- ASCII codes 0x20 ~ 0x7E

Setting Wireless EAP Parameters
When the wireless authentication method is set to EAP, you must configure EAP authentication
parameters, including outer authentication, inner authentication, EAP identity, client certificate, client
private key, password, CA certificate, and RADIUS authentication server. For more information, see
Wireless Network Settings.

▶ Determine the outer authentication protocol:
config:# network wireless eapOuterAuthentication <outer_auth>▶ Determine the inner authentication protocol for authentication set to "EAP + PEAP":
config:# network wireless eapInnerAuthentication <inner_auth>▶ Set the EAP identity:
config:#network wireless eapIdentity <identity>▶ Set the EAP password:
config:#network wireless eapPassword

After performing the above command, the PX-Series PDU prompts you to enter the password. Thentype the password and press Enter.

▶ Provide a Client Certificate for authentication set to "EAP + TLS" or "EAP + PEAP + TLS":
config:#network wireless eapClientCertificate

After performing any certificate or private key commands, including commands for the client certificate,client private key, and CA certificate, the system prompts you to enter the contents of the wanted
certificate or key. For an example with detailed procedure, see EAP CA Certificate Example (on page
459).

462

▶ Provide a Client Private Key for authentication set to "EAP + TLS" or "EAP + PEAP + TLS":
config:#network wireless eapClientPrivateKey▶ Provide a CA TLS certificate for EAP:
config:#network wireless eapCACertificate▶ Eable or disable verification of the TLS certificate chain:config:#network wireless enableCertVerification <option1>▶ Allow expired and not yet valid TLS certificates:
config:#network wireless allowOffTimeRangeCerts <option2>▶ Allow wireless network connection with incorrect system time:
config:# network wireless allowConnectionWithIncorrectClock <option3>▶ Set the RADIUS authentication server for EAP:
config:#network wireless eapAuthServerName <FQDN>

Variables:•<outer_auth> is one of the options: PEAP or TLS.
Option Description

•

PEAP

Outer authentication is set to Protected Extensible Authentication
Protocol (PEAP).

TLS

Outer authentication is set to TLS.

<inner_auth> is one of the options: MS‑CHAPv2 or TLS.

463

OptionDescription

MSCHAPv2 Inner authentication is set to Microsoft's Challenge Authentication
Protocol Version 2 (MS‑CHAPv2).
TLS

Inner authentication is set to TLS.

•

<identity> is your user name for the EAP authentication.

•<option1> is one of the options: true or false.

•

OptionDescription

true

Enables the verification of the TLS certificate chain.

false

Disables the verification of the TLS certificate chain.

<option2> is one of the options: true or false.
Option Description

•

true

Always make the network connection successful even though the TLS
certificate chain contains any certificate which is outdated or not valid yet.

false

The network connection is NOT successfully established when the TLS
certificate chain contains any certificate which is outdated or not valid yet.

<option3> is one of the options: true or false.
Option Description

•

true

Make the network connection successful when the PX-Series PDU systemtime is earlier than the firmware build before synchronizing with the NTP
server, causing the TLS certificate to become invalid.

false

The network connection is NOT successfully established when the PXSeries PDU finds that the TLS certificate is not valid due to incorrect
system time.

<FQDN> is the name of the RADIUS server if it is present in the TLS certificate. The name mustmatch the fully qualified domain name (FQDN) of the host shown in the certificate.

Setting the BSSID
This command specifies the BSSID.
config:#464

network wireless BSSID <bssid>

Variables:•<bssid> is either the MAC address of the wireless access point or none for automatic selection.

Setting the Wireless MTU
This command sets the MTU for the wireless interface.
config:#network wireless mtu<mtu>

Variables:•<mtu> is the Maximum Transfer Unit. Enter a value from 1280-1500.

Configuring the Cascading Mode
This command determines the cascading mode.
config:#network <mode> enabled <option1>

Variables:•<mode> is one of the following cascading modes.
Mode

Description

bridgeThe Bridging mode, where each cascaded device is assigned aunique IP address.

portForwarding The Port Forwarding mode, where every cascaded device in the
chain shares the same IP address, with diverse port numbers
assigned.

Important: When enabling either cascading mode, you must make sure the othercascading mode is disabled, or the preferred cascading mode may not be enabled
successfully.
•<option1> is one of the following options:
OptionDescriptiontrue

The selected cascading mode is enabled.

false

The selected cascading mode is disabled.

▶ If Port Forwarding mode is enabled, you must configure two more settings to finish theconfiguration:
On ALL cascaded devices, you must configure the 'role' setting one by one.

465

config:#

network portForwarding role <option2>

On the primary device, you must configure the 'downstream interface' setting.
config:# network portForwarding
primaryUnitDownstreamInterface <option3>
Variables:••<option2> is one of the following cascading roles:
Role

Description

primary

The device is a primary device.

expansion

The device is an expansion device.

<option3> is one of the following options:
OptionDescription

ETH1/ETH2 ETH1/ETH2 port is the port where the 1st expansion device isconnected.
Usb

USB port is the port where the 1st expansion device is connected.

Setting Network Service Parameters
A network service command begins with network services.

Setting the HTTP PortThe commands used to configure the HTTP port settings begin with network services http.

▶ Change the HTTP port:
config:#network services http port <n>▶ Enable or disable the HTTP port:
config:#network services http enabled <option>▶ Enforce redirection from HTTP to HTTPS:
config:#466

network services http enforceHttps <option>

Variables:•<n> is a TCP port number between 1 and 65535. The default HTTP port is 80.

•<option> is one of the options: true or false.

OptionDescription

true

•

The HTTP port is enabled.
- OR -

false•

HTTP redirection to HTTPS is enabled.

•

The HTTP port is disabled.
- OR -•HTTP redirection to HTTPS is disabled.

Setting the HTTPS PortThe commands used to configure the HTTPS port settings begin with network services https.

▶ Change the HTTPS port:
config:#network services https port <n>▶ Enable or disable the HTTPS access:config:#network services https enabled <option>

Variables:•<n> is a TCP port number between 1 and 65535. The default HTTPS port is 443.

•

<option> is one of the options: true or false.
Option Description
true

Forces any access to the PX-Series PDU via HTTP to be redirected to
HTTPS.

false

No HTTP access is redirected to HTTPS.

Changing the Telnet Configuration
You can enable or disable the Telnet service, or change its TCP port using the CLI commands.
A Telnet command begins with network services telnet.

▶ Enabling or Disabling Telnet
This command enables or disables the Telnet service.

467

config:#

network services telnet enabled <option>

Variables:•<option> is one of the options: true or false.
OptionDescription

true

The Telnet service is enabled.

false

The Telnet service is disabled.

▶ Changing the Telnet PortThis command changes the Telnet port.
config:#network services telnet port <n>Variables:•<n> is a TCP port number between 1 and 65535. The default Telnet port is 23.

Changing the SSH Configuration
You can enable or disable the SSH service, or change its TCP port using the CLI commands.
An SSH command begins with network services ssh.

▶ Enabling or Disabling SSH
This command enables or disables the SSH service.
config:#network services ssh enabled <option>

Variables:•

468<option> is one of the options: true or false.
OptionDescription

true

The SSH service is enabled.

OptionDescription

false

The SSH service is disabled.

▶ Changing the SSH PortThis command changes the SSH port.
config:#network services ssh port <n>Variables:•<n> is a TCP port number between 1 and 65535. The default SSH port is 22.

▶ Determining the SSH Authentication Method
This command syntax determines the SSH authentication method.
config:#network services ssh authentication <auth_method>

Variables:•<option> is one of the options: passwordOnly, publicKeyOnly or passwordOrPublicKey.
OptionDescription

passwordOnly

Enables the password-based login only.

publicKeyOnly

Enables the public key-based login only.

passwordOrPublicKey Enables both the password- and public key-based login.
This is the default.

If the public key authentication is selected, you must enter a valid SSH public key for each user profile tolog in over the SSH connection.

Setting the SNMP Configuration
You can enable or disable the SNMP v1/v2c or v3 agent, configure the read and write community
strings, or set the MIB-II parameters, such as sysContact, using the CLI commands.
An SNMP command begins with network services snmp.

▶ Enabling or Disabling SNMP v1/v2c
This command enables or disables the SNMP v1/v2c protocol.

469

config:#

network services snmp v1/v2c <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableThe SNMP v1/v2c protocol is enabled.

disableThe SNMP v1/v2c protocol is disabled.

▶ Enabling or Disabling SNMP v3
This command enables or disables the SNMP v3 protocol.
config:#network services snmp v3 <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableThe SNMP v3 protocol is enabled.

disableThe SNMP v3 protocol is disabled.

▶ Setting the SNMP Read Community
This command sets the SNMP read-only community string.
config:#network services snmp readCommunity <string>

Variables:•<string> is a string comprising 4 to 64 ASCII printable characters.

•

The string CANNOT include spaces.

▶ Setting the SNMP Write Community
This command sets the SNMP read/write community string.
config:#470

network services snmp writeCommunity <string>Variables:•<string> is a string comprising 4 to 64 ASCII printable characters.

•

The string CANNOT include spaces.

▶ Setting the sysContact Value
This command sets the SNMP MIB-II sysContact value.
config:#network services snmp sysContact <value>

Variables:•<value> is a string comprising 0 to 255 alphanumeric characters.

▶ Setting the sysName Value
This command sets the SNMP MIB-II sysName value.
config:#network services snmp sysName <value>

Variables:•<value> is a string comprising 0 to 255 alphanumeric characters.

▶ Setting the sysLocation Value
This command sets the SNMP MIB-II sysLocation value.
config:#network services snmp sysLocation <value>

Variables:<value> is a string comprising 0 to 255 alphanumeric characters.

Changing the Modbus Configuration
You can enable or disable the Modbus agent, configure its read-only capability, or change its TCP port.
A Modbus command begins with network services modbus.

▶ Enabling or Disabling Modbus
This command enables or disables the Modbus protocol.

471

config:#

network services modbus enabled <option>

Variables:•<option> is one of the options: true or false.
OptionDescription

true

The Modbus agent is enabled.

false

The Modbus agent is disabled.

▶ Enabling or Disabling the Read-Only Mode
This command enables or disables the read-only mode for the Modbus agent.
config:# network services modbus readonly <option>
Variables:•<option> is one of the options: true or false.
OptionDescription

true

The read-only mode is enabled.

false

The read-only mode is disabled.

▶ Changing the Modbus PortThis command changes the Modbus port.
config:#network services modbus port <n>Variables:•<n> is a TCP port number between 1 and 65535. The default Modbus port is 502.

Setting Redfish Service
You can enable or disable the redfish service.

▶ Enabling or Disabling Redfish service:config:# network services redfish enabled <option>

472

Variables:•<option> is one of the options: true or false.
OptionDescription

true

The redfish service is enabled.

false

The redfish service is disabled.

Enabling or Disabling Service AdvertisingThis command enables or disables the zero configuration protocol, which enables advertising or auto
discovery of network services. See Enabling Service Advertising for details.
config:#network services zeroconfig <method> <option>

Variables:••<method> is one of the options: mdns or llmnr.
OptionDescription

mdns

Service advertisement via MDNS is enabled or disabled.

llmnr

Service advertisement via LLMNR is enabled or disabled.

<option> is one of the options: enable or disable.
Option Description
enableService advertisement via the selected method (MDNS or LLMNR) is
enabled.

disableService advertisement via the selected method (MDNS or LLMNR) is
disabled.

Time Configuration Commands
A time configuration command begins with time.

▶ Determining the Time Setup Method
This command determines the method to configure the system date and time.
config:#time method <method>473

Variables:•<method> is one of the time setup options: manual or ntp.
Mode

Description

manual The date and time settings are customized.
ntp

The date and time settings synchronize with a specified NTP server.

▶ Setting NTP Parameters
A time configuration command for NTP-related parameters begins with time ntp.

▶ Specify the primary time server:
config:#time ntp firstServer <first_server>▶ Specify the secondary time server:
config:#time ntp secondServer <second_server>▶ To delete the primary time server:
config:#time ntp firstServer ""▶ To delete the secondary time server:
config:#time ntp secondServer ""Variables:•

The <first_server> is the IP address or host name of the primary NTP server.

•

The <second_server> is the IP address or host name of the secondary NTP server.

▶ Customizing the Date and TimeTo manually configure the date and time, use the following CLI commands to specify them.
Note: You shall set the time configuration method to "manual" prior to customizing the date and time.

474

▶ Assign the date:config:#time set date <yyyy‑mm‑dd>▶ Assign the time:
config:#time set time <hh:mm:ss>

Variables:
Variable

Description<yyyy‑mm‑dd> Type the date in the format of yyyy‑mm‑dd.
For example, type 2015‑11‑30 for November 30, 2015.
<hh:mm:ss>

Type the time in the format of hh:mm:ss in the 24-hour format.
For example, type 13:50:20 for 1:50:20 pm.

Setting the Time Zone
The CLI has a list of time zones to configure the date and time for PX-Series PDU.
config:#time zone

After a list of time zones is displayed, type the index number of the time zone or press Enter to cancel.

▶ To set the time zone:
1. Type the time zone command as shown below and press Enter.
config:#time zone

2. The system shows a list of time zones. Type the index number of the desired time zone and press
Enter.
3. Type apply for the selected time zone to take effect.

Setting the Automatic Daylight Savings Time
This command determines whether the daylight saving time is applied to the time settings.
config:#time autoDST <option>

Variables:•<option> is one of the options: enable or disable.

475

Mode

Description

enableDaylight savings time is enabled.

disableDaylight savings time is disabled.

Checking the Accessibility of NTP Servers
This command verifies the accessibility of NTP servers specified manually and then shows the result.
To perform this command successfully, you must:•

Own the "Change Date/Time Settings" permission.

•

Customize NTP servers.

This command is available either in the administrator/user mode or in the configuration mode.

▶ In the administrator/user mode:#

check ntp

▶ In the configuration mode:
config#check ntp

Example -Time Configuration
This section illustrates several time configuration examples.

▶ Example 1 - Time Setup Method
The following command sets the date and time settings by using the NTP servers.
config:#time method ntp▶ Example 2 - Primary NTP Server
The following command sets the primary time server to 192.168.80.66.
config:#476

time ntp firstServer 192.168.80.66

Security Configuration Commands
A security configuration command begins with security.

Firewall Control
You can manage firewall control features through the CLI. The firewall control lets you set up rules that
permit or disallow access to the PX-Series PDU from a specific or a range of IP addresses.
•

An IPv4 firewall configuration command begins with security ipAccessControl ipv4.

•

An IPv6 firewall configuration command begins with security ipAccessControl ipv6.

Modifying Firewall Control Parameters
There are different commands for modifying firewall control parameters.
•

IPv4 commands▶ Enable or disable the IPv4 firewall control feature:
config:#security ipAccessControl ipv4 enabled <option>▶ Determine the default IPv4 firewall control policy for inbound traffic:
config:#security ipAccessControl ipv4 defaultPolicyIn <policy>▶ Determine the default IPv4 firewall control policy for outbound traffic:
config:# security ipAccessControl ipv4 defaultPolicyOut <policy>•

IPv6 commands▶ Enable or disable the IPv6 firewall control feature:
config:#security ipAccessControl ipv6 enabled <option>▶ Determine the default IPv6 firewall control policy for inbound traffic:
config:#security ipAccessControl ipv6 defaultPolicyIn <policy>477

▶ Determine the default IPv6 firewall control policy for outbound traffic:
config:# security ipAccessControl ipv6 defaultPolicyOut <policy>
Variables:••<option> is one of the options: true or false.
OptionDescription

true

Enables the IP access control feature.

false

Disables the IP access control feature.

<policy> is one of the options: accept, drop or reject.
Option Description
acceptAccepts traffic from all IP addresses.

drop

Discards traffic from all IP addresses, without sending any failure
notification to the source host.

rejectDiscards traffic from all IP addresses, and an ICMP message is sent tothe source host for failure notification.

Managing Firewall Rules
You can add, delete or modify firewall rules using the CLI commands.
•

An IPv4 firewall control rule command begins with security ipAccessControl ipv4 rule.

•

An IPv6 firewall control rule command begins with security ipAccessControl ipv6 rule.

Adding a Firewall Rule
Depending on where you want to add a new firewall rule in the list, the command for adding a rulevaries.
•IPv4 commands▶ Add a new rule to the bottom of the IPv4 rules list:
config:# security ipAccessControl ipv4 rule add <direction> <ip_mask><policy>478

▶ Add a new IPv4 rule by inserting it above or below a specific rule:config:# security ipAccessControl ipv4 rule add <direction> <ip_mask><policy> <insert> <rule_number>-- OR -config:# security ipAccessControl ipv4 rule add <direction> <insert><rule_number> <ip_mask> <policy>•

IPv6 commands▶ Add a new rule to the bottom of the IPv6 rules list:
config:# security ipAccessControl ipv6 rule add <direction> <ip_mask><policy>▶ Add a new IPv6 rule by inserting it above or below a specific rule:config:# security ipAccessControl ipv6 rule add <direction> <ip_mask><policy> <insert> <rule_number>-- OR -config:# security ipAccessControl ipv6 rule add <direction> <insert><rule_number> <ip_mask> <policy>
Variables:•<direction> is one of the options: in or out.
Direction

Descriptionin

Inbound traffic.

outOutbound traffic.

•<ip_mask> is the combination of the IP address and subnet mask values (or prefix length), which areseparated with a slash. For example, an IPv4 combination looks like this: 192.168.94.222/24.

•<policy> is one of the options: accept, drop or reject.

479

Policy Description
accept Accepts traffic from/to the specified IP address(es).

•

drop

Discards traffic from/to the specified IP address(es), without sending any
failure notification to the source or destination host.

rejectDiscards traffic from/to the specified IP address(es), and an ICMP
message is sent to the source or destination host for failure notification.

<insert> is one of the options: insertAbove or insertBelow.
OptionDescription

insertAbove

Inserts the new rule above the specified rule number. Then:
new rule's number = the specified rule number

insertBelow

Inserts the new rule below the specified rule number. Then:
new rule's number = the specified rule number + 1•<rule_number> is the number of the existing rule which you want to insert the new rule above or
below.

Modifying a Firewall Rule
Depending on what to modify in an existing rule, the command varies.
•

IPv4 commands▶ Modify an IPv4 rule's IP address and/or subnet mask:
config:# security ipAccessControl ipv4 rule modify <direction><rule_number> ipMask <ip_mask>▶ Modify an IPv4 rule's policy:
config:# security ipAccessControl ipv4 rule modify <direction><rule_number> policy <policy>

480

▶ Modify all contents of an existing IPv4 rule:config:# security ipAccessControl ipv4 rule modify <direction><rule_number> ipMask <ip_mask> policy <policy>•

IPv6 commands▶ Modify an IPv6 rule's IP address and/or prefix length:
config:# security ipAccessControl ipv6 rule modify <direction><rule_number> ipMask <ip_mask>▶ Modify an IPv6 rule's policy:
config:# security ipAccessControl ipv6 rule modify <direction><rule_number> policy <policy>▶ Modify all contents of an IPv6 existing rule:config:# security ipAccessControl ipv6 rule modify <direction><rule_number> ipMask <ip_mask> policy <policy>
Variables:•<direction> is one of the options: in or out.
Direction

Descriptionin

Inbound traffic.

outOutbound traffic.

•<rule_number> is the number of the existing rule that you want to modify.

•<ip_mask> is the combination of the IP address and subnet mask values (or prefix length), which areseparated with a slash. For example, an IPv4 combination looks like this: 192.168.94.222/24.

•<policy> is one of the options: accept, drop or reject.
Option Description
acceptAccepts traffic from/to the specified IP address(es).

dropDiscards traffic from/to the specified IP address(es), without sending
any failure notification to the source or destination host.

481

Option Description
rejectDiscards traffic from/to the specified IP address(es), and an ICMP
message is sent to the source or destination host for failure notification.

Deleting a Firewall Rule
The following commands remove a specific IPv4 or IPv6 rule from the list.

▶ IPv4 commands
config:# security ipAccessControl ipv4 rule delete <direction><rule_number>▶ IPv6 commands
config:# security ipAccessControl ipv6 rule delete <direction><rule_number>
Variables:••<direction> is one of the options: in or out.
Direction

Descriptionin

Inbound traffic.

outOutbound traffic.

<rule_number> is the number of the existing rule that you want to remove.

Restricted Service Agreement
The CLI command used to set the Restricted Service Agreement feature begins with security
restrictedServiceAgreement,

Enabling or Disabling the Restricted Service Agreement
This command activates or deactivates the Restricted Service Agreement.
config:#security restrictedServiceAgreement enabled <option>

Variables:•482<option> is one of the options: true or false.

OptionDescription

true

Enables the Restricted Service Agreement feature.

false

Disables the Restricted Service Agreement feature.

After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on thelogin screen.

Do either of the following, or the login fails:•

In the web interface, select the checkbox labeled "I understand and accept the restricted service
agreement."
Tip: To select the agreement checkbox using the keyboard, first press Tab to go to the checkbox andthen Enter.

•In the CLI, type y when the confirmation message "I understand and accept the restricted service
agreement" is displayed.

Specifying the Agreement Contents
This command allows you to create or modify contents of the Restricted Service Agreement.
config:#security restrictedServiceAgreement bannerContent

After performing the above command, do the following:
1. Type the text comprising up to 10,000 ASCII characters when the CLI prompts you to enter thecontent.
2. To end the content:483

a. Press Enter.
b. Type --END-- to indicate the end of the content.
c. Press Enter again.
If the content is successfully entered, the CLI displays this message "Successfully entered Restricted
Service Agreement" followed by the total number of entered characters in parentheses.
Note: The new content of Restricted Service Agreement is saved only after typing the applycommand.

Login Limitation
The login limitation feature controls login-related limitations, such as password aging, simultaneous
logins using the same user name, and the idle time permitted before forcing a user to log out.
A login limitation command begins with security loginLimits.

Single Login Limitation
This command enables or disables the single login feature, which controls whether multiple logins using
the same login name simultaneously is permitted.
config:#security loginLimits singleLogin <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableEnables the single login feature.

disableDisables the single login feature.

Password Aging
This command enables or disables the password aging feature, which controls whether the password
should be changed at a regular interval:
config:#security loginLimits passwordAging <option>

Variables:•484<option> is one of the options: enable or disable.
OptionDescription

enableEnables the password aging feature.

OptionDescription

disableDisables the password aging feature.

Password Aging IntervalThis command determines how often the password should be changed.
config:#security loginLimits passwordAgingInterval <value>

Variables:•<value> is a numeric value in days set for the password aging interval. The interval ranges from 7 to365 days.

Idle Timeout
This command determines how long a user can remain idle before that user is forced to log out of the
PX-Series PDU web interface or CLI.
config:#security loginLimits idleTimeout <value>

Variables:•<value> is a numeric value in minutes set for the idle timeout. The timeout ranges from 1 to 1440
minutes (24 hours).

User Blocking
There are different commands for changing different user blocking parameters. These commands begin
with security userBlocking.

▶ Determine the maximum number of failed logins before blocking a user:
config:#security userBlocking maximumNumberOfFailedLogins <value1>▶ Determine how long a user is blocked:
config:#security userBlocking blockTime <value2>

485

Variables:•<value1> is an integer between 3 and 10, or unlimited, which sets no limit on the maximum numberof failed logins and thus disables the user blocking function.

•<value2> is a numeric value ranging from 1 to 1440 minutes (one day), or infinite, which blocks theuser all the time until the user is unblocked manually.

Strong Passwords
The strong password commands determine whether a strong password is required for login, and what astrong password should contain at least.
A strong password command begins with security strongPasswords.

Enabling or Disabling Strong Passwords
This command enables or disables the strong password feature.
config:#security strongPasswords enabled <option>

Variables:•<option> is one of the options: true or false.
OptionDescription

true

Enables the strong password feature.

false

Disables the strong password feature.

Minimum Password Length
This command determines the minimum length of the password.
config:#security strongPasswords minimumLength <value>

Variables:•<value> is an integer between 8 and 32.

Maximum Password Length
This command determines the maximum length of the password.
config:#486

security strongPasswords maximumLength <value>Variables:•<value> is an integer between 16 and 64.

Lowercase Character Requirement
This command determines whether a strong password includes at least a lowercase character.
config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter<option>Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableAt least one lowercase character is required.

disableNo lowercase character is required.

Uppercase Character Requirement
This command determines whether a strong password includes at least a uppercase character.
config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter<option>Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableAt least one uppercase character is required.

disableNo uppercase character is required.

Numeric Character Requirement
This command determines whether a strong password includes at least a numeric character.
config:# security strongPasswords enforceAtLeastOneNumericCharacter<option>Variables:•<option> is one of the options: enable or disable.

487

OptionDescription

enableAt least one numeric character is required.

disableNo numeric character is required.

Special Character Requirement
This command determines whether a strong password includes at least a special character.
config:# security strongPasswords enforceAtLeastOneSpecialCharacter<option>Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableAt least one special character is required.

disableNo special character is required.

Maximum Password History
This command determines the number of previous passwords that CANNOT be repeated whenchanging the password.
config:#488

security strongPasswords passwordHistoryDepth <value>Variables:•<value> is an integer between 1 and 12.

Role-Based Access Control
In addition to firewall access control based on IP addresses, you can configure other access control rulesthat are based on both IP addresses and users' roles.
•

An IPv4 role-based access control command begins with security roleBasedAccessControl ipv4.

•

An IPv6 role-based access control command begins with security roleBasedAccessControl ipv6.

Modifying Role-Based Access Control Parameters
There are different commands for modifying role-based access control parameters.
•

IPv4 commands▶ Enable or disable the IPv4 role-based access control feature:
config:#security roleBasedAccessControl ipv4 enabled <option>▶ Determine the IPv4 role-based access control policy:
config:#•security roleBasedAccessControl ipv4 defaultPolicy <policy>

IPv6 commands▶ Enable or disable the IPv6 role-based access control feature:
config:#security roleBasedAccessControl ipv6 enabled <option>▶ Determine the IPv6 role-based access control policy:
config:#security roleBasedAccessControl ipv6 defaultPolicy <policy>

Variables:•<option> is one of the options: true or false.
OptionDescription

true

Enables the role-based access control feature.

489

•

OptionDescription

false

Disables the role-based access control feature.

<policy> is one of the options: allow or deny.
PolicyDescription

allow

Accepts traffic from all IP addresses regardless of the user's role.

deny

Drops traffic from all IP addresses regardless of the user's role.

Tip: You can combine both commands to modify all role-based access control parameters at a time.

Managing Role-Based Access Control Rules
You can add, delete or modify role-based access control rules.
•

An IPv4 role-based access control command for managing rules begins with security
roleBasedAccessControl ipv4 rule.

•

An IPv6 role-based access control command for managing rules begins with security
roleBasedAccessControl ipv6 rule.

Adding a Role-Based Access Control Rule
Depending on where you want to add a new rule in the list, the command syntax for adding a rulevaries.
•IPv4 commands▶ Add a new rule to the bottom of the IPv4 rules list:
config:# security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip><role> <policy>490

▶ Add a new IPv4 rule by inserting it above or below a specific rule:config:# security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip><role><policy> <insert> <rule_number>•

IPv6 commands▶ Add a new rule to the bottom of the IPv6 rules list:
config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip><role> <policy>▶ Add a new IPv6 rule by inserting it above or below a specific rule:config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip><role><policy> <insert> <rule_number>
Variables:•<start_ip> is the starting IP address.

•<end_ip> is the ending IP address.

•<role> is the role for which you want to create an access control rule.

•<policy> is one of the options: allow or deny.
Policy Description

•

allow

Accepts traffic from the specified IP address range when the user is amember of the specified roledeny

Drops traffic from the specified IP address range when the user is amember of the specified role<insert> is one of the options: insertAbove or insertBelow.
OptionDescription

insertAbove

Inserts the new rule above the specified rule number. Then:
new rule's number = the specified rule number

insertBelow

Inserts the new rule below the specified rule number. Then:
new rule's number = the specified rule number + 1•<rule_number> is the number of the existing rule which you want to insert the new rule above or
below.

491

Modifying a Role-Based Access Control Rule
Depending on what to modify in an existing rule, the command syntax varies.
•

IPv4 commands▶ Modify a rule's IPv4 address range:
config:# security roleBasedAccessControl ipv4 rule modify <rule_number>startIpAddress <start_ip> endIpAddress <end_ip>▶ Modify an IPv4 rule's role:
config:# security roleBasedAccessControl ipv4 rule modify <rule_number>role <role>▶ Modify an IPv4 rule's policy:
config:# security roleBasedAccessControl ipv4 rule modify <rule_number>policy <policy>▶ Modify all contents of an existing IPv4 rule:config:# security roleBasedAccessControl ipv4 rule modify <rule_number>startIpAddress <start_ip> endIpAddress <end_ip> role <role>
policy <policy>•

IPv6 commands▶ Modify a rule's IPv6 address range:
config:# security roleBasedAccessControl ipv6 rule modify <rule_number>startIpAddress <start_ip> endIpAddress <end_ip>▶ Modify an IPv6 rule's role:
config:# security roleBasedAccessControl ipv6 rule modify <rule_number>role <role>492

▶ Modify an IPv6 rule's policy:
config:# security roleBasedAccessControl ipv6 rule modify <rule_number>policy <policy>▶ Modify all contents of an existing IPv6 rule:config:# security roleBasedAccessControl ipv6 rule modify <rule_number>startIpAddress <start_ip> endIpAddress <end_ip> role <role>
policy <policy>
Variables:•<rule_number> is the number of the existing rule that you want to modify.

•<start_ip> is the starting IP address.

•<end_ip> is the ending IP address.

•<role> is one of the existing roles.

•<policy> is one of the options: allow or deny.
Policy Description
allow

Accepts traffic from the specified IP address range when the user is amember of the specified roledeny

Drops traffic from the specified IP address range when the user is amember of the specified role

Deleting a Role-Based Access Control Rule
These commands remove a specific rule from the list.

▶ IPv4 commands
config:# security roleBasedAccessControl ipv4 rule delete <rule_number>▶ IPv6 commands
config:# security roleBasedAccessControl ipv6 rule delete <rule_number>493

Variables:•<rule_number> is the number of the existing rule that you want to remove.

Enabling or Disabling Front Panel Outlet SwitchingThis section applies to outlet-switching capable models only.
The following CLI commands control whether you can turn on or off an outlet by operating the front
panel display.

▶ To enable the front panel outlet control feature:
config:#security frontPanelPermissions add switchOutlet▶ To disable the front panel outlet control feature:
config:#security frontPanelPermissions remove switchOutlet

Tip: If your PX-Series PDU supports multiple front panel permissions, you can combine them into one
command by adding a semicolon (;) between different permissions. For example, the following CLI
command enables both front panel actuator control and outlet switching functions simultaneously.
security frontPanelPermissions add switchActuator;switchOutlet

Enabling or Disabling Front Panel Actuator Control
The following CLI commands control whether you can turn on or off connected actuator(s) by operating
the front panel LCD display.

▶ To enable the front panel actuator control feature:
config:#security frontPanelPermissions add switchActuator▶ To disable the front panel actuator control feature:
config:#494

security frontPanelPermissions remove switchActuatorTip: If your PX-Series PDU supports multiple front panel permissions, you can combine them into one
command by adding a semicolon (;) between different permissions. For example, the following CLI
command enables both front panel actuator control and the internal beeper-muting functions
simultaneously.
security frontPanelPermissions add switchActuator;muteBeeper

Enabling or Disabling Front Panel Beeper-Sound Control
The following CLI commands control whether you can mute the internal beeper by operating the front
panel LCD display when the beeper sounds.

▶ To enable the front panel beeper sound control feature:
config:#security frontPanelPermissions add muteBeeper▶ To disable the front panel actuator control feature:
config:#security frontPanelPermissions remove muteBeeper

Tip: If your PX-Series PDU supports multiple front panel permissions, you can combine them into one
command by adding a semicolon (;) between different permissions. For example, the following CLI
command enables both front panel actuator control and the the internal beeper-muting functions
simultaneously.
security frontPanelPermissions add switchActuator;muteBeeper

Outlet Configuration Commands
An outlet configuration command begins with outlet. Such a command allows you to configure an
individual outlet.

Changing the Outlet Name
This command names an outlet.
config:#outlet <n> name "<name>"

495

Variables:•<n> is the number of the outlet that you want to configure.

•<name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be
enclosed in quotes when it contains spaces.

Changing an Outlet's Default State
This section applies to outlet-switching capable models only.
This command determines the initial power condition of an outlet after the PX-Series PDU powers up.
config:#outlet <n> stateOnPowerUp <option>

Variables:•<n> is the number of the outlet that you want to configure.

•<option> is one of the options: off, on, lastKnownState and pduDefined.
OptionDescription

offTurn off the outlet.

onTurn on the outlet.

lastKnownState

Restore the outlet to the state prior to last PDU power down.

pduDefined

PDU-defined setting.

Note: Setting the outlet's default state to an option other than pduDefined overrides the PDU-defined
default state on that outlet.

Setting an Outlet's Cycling Power-Off Period
This section applies to outlet-switching capable models only.
This command determines the power-off period of the power cycling operation for a specific outlet.
config:#496

outlet <n> cyclingPowerOffPeriod <timing>Variables:•<n> is the number of the outlet that you want to configure.

•<timing> is the time of the cycling power-off period in seconds, which is an integer between 0 and
3600, or pduDefined for following the PDU-defined timing.

Note: This setting overrides the PDU-defined cycling power-off period on a particular outlet.

Example - Outlet Naming
The following command assigns the name "Win XP" to outlet 8.
config:#outlet 8 name "Win XP"

Outlet Group Configuration Commands
An outlet group configuration command begins with outletgroup. Such a command allows you to
configure or operate an outlet group.

Creating an Outlet Group
This command creates a new outlet group.
config:#outletgroup add "<name>" <members>

Variables:•<name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be
enclosed in quotes when it contains spaces.
Tip: PX-Series PDU allows you to assign the same name to diverse outlet groups. If this really occurs,
you still can identify different groups through their unique index numbers.

•<members> is one or multiple member outlets' index numbers separated with commas. If themember outlets are consecutive outlets, you can type a hyphen between the initial and the finalindex number instead of using commas.
For example, to assign outlets 3, 4, 5, 8 and 10 to the outlet group named "servers", youhave two choices -- either use a hyphen for consecutive outlets 3 to 5, or use commas forall of member outlets:• outletgroup add servers 3-5,8,10-- OR -• outletgroup add servers 3,4,5,8,10

Managing an Outlet GroupYou can modify an outlet group's name and member outlets, or simply remove any existing outlet
group.

497

You can modify both the name and members of an outlet group at a time by combining multiplecommands.

▶ Modify an outlet group's name:config:#outletgroup modify <ID> name "<name>"▶ Modify an outlet group's member outlets:
config:#outletgroup modify <ID> members <members>▶ Delete an outlet group:
config:#outletgroup delete <ID>

Variables:•<ID> is an outlet group's index number.

•<name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be
enclosed in quotes when it contains spaces.

•<members> is one or multiple member outlets' index numbers separated with commas. If themember outlets are consecutive outlets, you can type a hyphen between the initial and the finalindex number instead of using commas.
For example, to assign outlets 3, 4, 5, 8 and 10 to the outlet group named "servers", youhave two choices -- either use a hyphen for consecutive outlets 3 to 5, or use commas forall of member outlets:
In the following examples, it is assumed that the "servers" outlet group's index number is2.
• outletgroup modify 2 members 3-5,8,10-- OR -• outletgroup modify 2 members 3,4,5,8,10

Powering On/Off/Cycle Outlet Groups
This section applies to outlet-switching capable models only.
You must perform this operation in the administrator mode.

▶ Power on one outlet group:#498

power outletgroup <ID> on▶ Power off one outlet group:#

power outletgroup <ID> off▶ Power cycle one outlet group:#

power outletgroup <ID> cycle

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms
the operation.
For example:#

power outletgroup <ID> off /y

If you entered the command without "/y", a message appears, prompting you to confirm the operation.
Then:•

Type y to confirm the operation, OR

Type n to abort the operation
Variables:•<ID> is an outlet group's index number.

Inlet Configuration Commands
An inlet configuration command begins with inlet. You can configure an inlet by using the inlet
configuration command.

Changing the Inlet Name
This command syntax names an inlet.
config:#inlet <n> name "<name>"499

Variables:•<n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always 1.
The value is an integer between 1 and 50.

•<name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be
enclosed in quotes when it contains spaces.

Enabling or Disabling an Inlet (for Multi-Inlet PDUs)
Enabling or disabling an inlet takes effect on a multi-inlet PDU only.
This command enables or disables an inlet.
config:#inlet <n> enabled <option>

Variables:•<n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always 1.
The value is an integer between 1 and 50.

•<option> is one of the options: true or false.
OptionDescriptiontrue

The specified inlet is enabled.

false

The specified inlet is disabled.

Note: If performing this command causes all inlets to be disabled, a warning message appears,
prompting you to confirm. When this occurs, press y to confirm or n to cancel the operation.

Example - Inlet Naming
The following command assigns the name "AC source" to the inlet 1. If your PX-Series PDU contains
multiple inlets, this command names the 1st inlet.
config:#inlet 1 name "AC source"

Overcurrent Protector Configuration Commands
An overcurrent protector configuration command begins with ocp. The command configures anindividual circuit breaker or fuse which protects outlets.

Changing the Overcurrent Protector Name
This command names a circuit breaker or a fuse which protects outlets on your PX-Series PDU.

500

config:#

ocp <n> name "<name>"

Variables:•<n> is the number of the overcurrent protector that you want to configure. The value is an integer
between 1 and 50.

•<name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be
enclosed in quotes when it contains spaces.

Example - OCP Naming
The command assigns the name "Email servers CB" to the overcurrent protector labeled 2.
config:#ocp 2 name "Email servers CB"

User Configuration Commands
Most user configuration commands begin with user except for the password change command.

Creating a User Profile
This command creates a new user profile.
config:#user create <name> <option> <roles>

After performing the user creation command, the PX-Series PDU prompts you to assign a password to
the newly‑created user. Then:
1. Type the password and press Enter.
2. Re-type the same password for confirmation and press Enter.
Variables:•<name> is a string comprising up to 32 ASCII printable characters. The <name> variable CANNOT
contain spaces.

•<option> is one of the options: enable or disable.

•

OptionDescription

enableEnables the newly‑created user profile.

disableDisables the newly‑created user profile.

<roles> is a role or a list of comma-separated roles assigned to the specified user profile.

Modifying a User Profile
A user profile contains various parameters that you can modify.

501

Tip: You can combine all commands to modify the parameters of a specific user profile at a time.

Changing a User's Password
This command allows you to change an existing user's password if you have the Administrator
Privileges.
config:#user modify <name> password

After performing the above command, you are prompted to enter a new password. Then:
1. Type a new password and press Enter.
2. Re-type the new password for confirmation and press Enter.
Variables:•<name> is the name of the user whose settings you want to change.

▶ Example
The following procedure illustrates how to change the password of the user "May."
1. Verify that you have entered the configuration mode.
2. Type the following command to change the password for the user profile "May."
config:#user modify May password

3. Type a new password when prompted, and press Enter.
4. Type the same new password and press Enter.
5. If the password change is completed successfully, the config:# prompt appears.

Modifying a User's Personal Data
You can change a user's personal data, including the user's full name, telephone number, and email
address.
Various commands can be combined to modify the parameters of a specific user profile at a time.

▶ Change a user's full name:config:#user modify <name> fullName "<full_name>"▶ Change a user's telephone number:config:#502

user modify <name> telephoneNumber "<phone_number>"▶ Change a user's email address:
config:#user modify <name> eMailAddress <email_address>

Variables:•<name> is the name of the user whose settings you want to change.

•<full_name> is a string comprising up to 64 ASCII printable characters. The <full_name> variablemust be enclosed in quotes when it contains spaces.

•<phone_number> is the phone number that can reach the specified user. The <phone_number>variable must be enclosed in quotes when it contains spaces.

•<email_address> is the email address of the specified user.

Enabling or Disabling a User Profile
This command enables or disables a user profile. A user can log in to the PX-Series PDU only after thatuser's user profile is enabled.
config:#user modify <name> enabled <option>

Variables:•<name> is the name of the user whose settings you want to change.

•<option> is one of the options: true or false.
OptionDescription

true

Enables the specified user profile.

false

Disables the specified user profile.

Forcing a Password ChangeThis command determines whether the password change is forced when a user logs in to the specified
user profile next time.
config:#user modify <name> forcePasswordChangeOnNextLogin <option>

Variables:•<name> is the name of the user whose settings you want to change.

•<option> is one of the options: true or false.
OptionDescriptiontrue

A password change is forced on the user's next login.

503

OptionDescription

false

No password change is forced on the user's next login.

Modifying SNMPv3 Settings
There are different commands to modify the SNMPv3 parameters of a specific user profile. You can
combine all of the following commands to modify the SNMPv3 parameters at a time.

▶ Enable or disable the SNMP v3 access to PX-Series PDU for the specified user:
config:#user modify <name> snmpV3Access <option1>▶ Determine the security level:
config:#user modify <name> securityLevel <option2>▶ Determine whether the authentication passphrase is identical to the password:
config:# user modify <name> userPasswordAsAuthenticationPassphrase<option3>▶ Determine the authentication passphrase:
config:#user modify <name> authenticationPassPhrase

After performing the above command, the system prompts you to enter the authentication passphrase.

▶ Determine whether the privacy passphrase is identical to the authentication passphrase:
config:# user modify <name> useAuthenticationPassPhraseAsPrivacyPassPhrase<option4>▶ Determine the privacy passphrase:
config:#user modify <name> privacyPassPhrase

After performing the above command, the system prompts you to enter the privacy passphrase.

504

▶ Determine the authentication protocol:
config:#user modify <name> authenticationProtocol <option5>▶ Determine the privacy protocol:
config:#user modify <name> privacyProtocol <option6>

Variables:•<name> is the name of the user whose settings you want to change.

•<option1> is one of the options: enable or disable.

•

•

•

OptionDescription

enableEnables the SNMP v3 access permission for the specified user.

disableDisables the SNMP v3 access permission for the specified user.

<option2> is one of the options: noAuthNoPriv, authNoPriv or authPriv.
OptionDescription

noAuthNoPriv

No authentication and no privacy.

authNoPriv

Authentication and no privacy.

authPriv

Authentication and privacy.

<option3> is one of the options: true or false.
OptionDescription

trueAuthentication passphrase is identical to the password.

false

Authentication passphrase is different from the password.

<option4> is one of the options: true or false.
Option Description

•

true

Privacy passphrase is identical to the authentication passphrase.

false

Privacy passphrase is different from the authentication passphrase.

<option5> is one of the following options:

505

•

•

OptionDescription

MD5

MD5 authentication protocol is applied.

SHA‑1

SHA‑1 authentication protocol is applied.

SHA-224

SHA‑224 authentication protocol is applied.

SHA-256

SHA-256 authentication protocol is applied.

SHA-384

SHA-384 authentication protocol is applied.

SHA-512

SHA-512 authentication protocol is applied.

<option6> is one of the following options:
OptionDescription

DES

DES privacy protocol is applied.

AES‑128

AES‑128 privacy protocol is applied.

AES‑192

AES‑192 privacy protocol is applied.

AES‑256

AES‑256 privacy protocol is applied.

AES‑192 (3DES key extension)

AES‑192 privacy protocol is applied.

AES‑256 (3DES key extension)

AES‑256 privacy protocol is applied.

An authentication or privacy passphrase is a string comprising 8 to 32 ASCII printable characters.

Changing the Role(s)This command changes the role(s) of a specific user.
config:#user modify <name> roles <roles>

Variables:•<name> is the name of the user whose settings you want to change.

•<roles> is a role or a list of comma-separated roles assigned to the specified user profile.

Changing Measurement Units
You can change the measurement units displayed for temperatures, length, and pressure for a specificuser profile. Different measurement unit commands can be combined so that you can set allmeasurement units at a time.

506

Note: The measurement unit change only applies to the web interface and command line interface.

▶ Set the preferred temperature unit:
config:#user modify <name> preferredTemperatureUnit <option1>▶ Set the preferred length unit:
config:#user modify <name> preferredLengthUnit <option2>▶ Set the preferred pressure unit:
config:#user modify <name> preferredPressureUnit <option3>

Variables:•<name> is the name of the user whose settings you want to change.

•<option1> is one of the options: C or F.

••

OptionDescription

C

This option displays the temperature in Celsius.

F

This option displays the temperature in Fahrenheit.

<option2> is one of the options: meter or feet.
OptionDescription

meterThis option displays the length or height in meters.

feetThis option displays the length or height in feet.

<option3> is one of the options: pascal or psi.
OptionDescription

pascalThis option displays the pressure value in Pascals (Pa).

psiThis option displays the pressure value in psi.

Specifying the SSH Public Key
If the SSH key-based authentication is enabled, specify the SSH public key for each user profile using thefollowing procedure.

507

▶ To specify or change the SSH public key for a specific user:
1. Type the SSH public key command as shown below and press Enter.
config:#user modify <name> sshPublicKey

2. The system prompts you to enter the contents of the SSH public key. Do the following to input thecontents:
a. Open your SSH public key with a text editor.
b. Copy all contents in the text editor.
c. Paste the contents into the terminal.
d. Press Enter.

▶ To remove an existing SSH public key:
1. Type the same command as shown above.
2. When the system prompts you to input the contents, press Enter without typing or pasting anything.

▶ Example
The following procedure illustrates how to change the SSH public key for the user "assistant."
1. Verify that you have entered the configuration mode.
2. Type the following command and press Enter.
config:#user modify assistant sshPublicKey

3. You are prompted to enter a new SSH public key.
4. Type the new key and press Enter.

Deleting a User Profile
This command deletes an existing user profile.
config:#user delete <name>

Changing Your Own Password
Every user can change their own password via this command if they have the Change Own Password
privilege. Note that this command does not begin with user.
config:#password

After performing this command, the system prompts you to enter both current and new passwords
respectively.

508

Important: After the password is changed successfully, the new password iseffective immediately whether or not you type the command "apply" to save thechanges.

▶ Example
This procedure changes your own password:
1. Verify that you have entered the configuration mode.
2. Type the following command and press Enter.
config:#password

3. Type the existing password and press Enter when the following prompt appears.
Current password:
4. Type the new password and press Enter when the following prompt appears.
Enter new password:
5. Re-type the new password for confirmation and press Enter when the following prompt appears.
Re-type new password:

Setting Default Measurement Units
Default measurement units, including temperature, length, and pressure units, apply to the userinterfaces across all users except for those whose preferred measurement units are set differently bythemselves or the administrator. Diverse measurement unit commands can be combined so that you
can set all default measurement units at a time.
Note: The measurement unit change only applies to the web interface and command line interface.

▶ Set the default temperature unit:
config:# user defaultpreferences preferredTemperatureUnit <option1>▶ Set the default length unit:
config:#user defaultpreferences preferredLengthUnit <option2>▶ Set the default pressure unit:
config:#user defaultpreferences preferredPressureUnit <option3>

Variables:•<option1> is one of the options: C or F.

509

•

•

OptionDescription

C

This option displays the temperature in Celsius.

F

This option displays the temperature in Fahrenheit.

<option2> is one of the options: meter or feet.
OptionDescription

meterThis option displays the length or height in meters.

feetThis option displays the length or height in feet.

<option3> is one of the options: pascal or psi.
OptionDescription

pascalThis option displays the pressure value in Pascals (Pa).

psiThis option displays the pressure value in psi.

Role Configuration Commands
A role configuration command begins with role.

Creating a Role
This command creates a new role, with a list of semicolon‑separated privileges assigned to the role.
config:#role create <name> <privilege1>;<privilege2>;<privilege3>...

If a specific privilege contains any arguments, that privilege should be followed by a colon and theargument(s).
config:#Variables:

510

role create <name> <privilege1>:<argument1>,<argument2>...;<privilege2>:<argument1>,<argument2>...;<privilege3>:<argument1>,<argument2>...;...

•<name> is a string comprising up to 32 ASCII printable characters.

•<privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role.
Separate each privilege with a semi-colon.

•<argument1>, <argument2> and the like are arguments set for a particular privilege. Separate aprivilege and its argument(s) with a colon, and separate arguments with a comma if there are morethan one argument for a privilege.

All PrivilegesThis table lists all privileges. Note that available privileges vary according to the model you purchased.
For example, a PDU without the outlet switching function does not have the privilege "switchOutlet."Privilege

Description

acknowledgeAlarms

Acknowledge Alarms

adminPrivilege

Administrator PrivilegeschangeAssetStripConfiguration

Change Asset Strip Configuration

changeAuthSettings

Change Authentication SettingschangeDataTimeSettings

Change Date/Time SettingschangeExternalSensorsConfiguration Change Peripheral Device Configuration
changeModemConfiguration

Change Modem Configuration

changeNetworkSettings

Change Network SettingschangePassword

Change Own Password

changePduConfiguration

Change Pdu, Inlet, Outlet & Overcurrent
Protector Configuration

changeSecuritySettings

Change Security SettingschangeSnmpSettings

Change SNMP SettingschangeUserSettings

Change Local User ManagementchangeWebcamSettings

Change Webcam Configuration

clearLog

Clear Local Event Log

firmwareUpdate

Firmware Update

performReset

Reset (Warm Start)

switchActuator*

Switch ActuatorswitchOutlet**

Switch Outlet

switchOutletGroup***

Switch Outlet Group

viewAuthSettings

View Authentication Settings

511

Privilege

Description

viewEventSetup

View Event Settings

viewEverything

Unrestricted View Privileges

viewLog

View Local Event Log

viewSecuritySettings

View Security Settings

viewSnmpSettings

View SNMP Settings

viewUserSettings

View Local User Management

viewWebcamSettings

View Webcam Snapshots and Configuration* The "switchActuator" privilege requires an argument that is separated with a colon. The argument
could be:•All actuators, that is,
switchActuator:all•

An actuator's ID number. For example:
switchActuator:1
switchActuator:2
switchActuator:3•

A list of comma-separated ID numbers of different actuators. For example:
switchActuator:1,3,6
Note: The ID number of each actuator is shown in the PX-Series PDU web interface. It is an integer.

** The "switchOutlet" privilege requires an argument that is separated with a colon. The argument
could be:•All outlets, that is,
switchOutlet:all•

An outlet number. For example:
switchOutlet:1
switchOutlet:2
switchOutlet:3•

A list of comma-separated outlets. For example:
switchOutlet:1,3,5,7,8,9*** The "switchOutletGroup" privilege requires an argument that is separated with a colon. The
argument could be:•

512

All outlet groups, that is,switchOutletGroup:all•

An outlet group number. For example:
switchOutletGroup:1
switchOutletGroup:2
switchOutletGroup:3•

A list of comma-separated outlet groups. For example:
switchOutletGroup:1,3,5,7,8,9

Modifying a Role
You can modify diverse parameters of an existing role, including its privileges.

▶ Modify a role's description:
config:#role modify <name> description "<description>"▶ Add more privileges to a specific role:
config:# role modify <name> addPrivileges<privilege1>;<privilege2>;<privilege3>...
If a specific privilege contains any arguments, add a colon and the argument(s) after thatprivilege.
config:# role modify <name> addPrivileges<privilege1>:<argument1>,<argument2>...;<privilege2>:<argument1>,<argument2>...;<privilege3>:<argument1>,<argument2>...;...

▶ Remove specific privileges from a role:
config:# role modify <name> removePrivileges<privilege1>;<privilege2>;<privilege3>...
If a specific privilege contains any arguments, add a colon and the argument(s) after thatprivilege.
config:# role modify <name> removePrivileges<privilege1>:<argument1>,<argument2>...;<privilege2>:<argument1>,<argument2>...;<privilege3>:<argument1>,<argument2>...;
...

513

Note: When removing privileges from a role, make sure the specified privileges and arguments (if any)exactly match those assigned to the role. Otherwise, the command fails to remove specified privilegesthat are not available.
Variables:•<name> is a string comprising up to 32 ASCII printable characters.

•<description> is a description comprising alphanumeric characters. The <description> variable must
be enclosed in quotes when it contains spaces.

•<privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role.
Separate each privilege with a semi-colon. See All Privileges (on page ).

•<argument1>, <argument2> and the like are arguments set for a particular privilege. Separate aprivilege and its argument(s) with a colon, and separate arguments with a comma if there are morethan one argument for a privilege. For arguments syntax, see All Privileges (on page ).

Deleting a Role
This command deletes an existing role.
config:#role delete <name>Example - Creating a RoleThe following command creates a new role and assigns privileges to the role.
config:#role create tester firmwareUpdate;viewEventSetup

Results:•

A new role "tester" is created.

•

Two privileges are assigned to the role: firmwareUpdate (Firmware Update) and viewEventSetup(View Event Settings).

Authentication Commands
An authentication configuration command begins with authentication.

Determining the Authentication Method
You can choose to set the authentication type only, or both set the authentication type and determine
whether to switch to local authentication in case the remote authentication is not available.

▶ Determine the authentication type only:
config:#514

authentication type <option1>

▶ Determine the authentication type and enable/disable the option of switching to local
authentication:
config:# authentication type <option1> useLocalIfRemoteUnavailable<option2>

Note: You cannot enable or disable the option of switching to local authentication without determining
the authentication type in the CLI. Therefore, always type "authentication type <option1>" when setting
up "useLocalIfRemoteUnavailable".
Variables:••<option1> is one of the options: local , ldap or radius.
OptionDescription

local

Enable Local authentication only.

ldap

Enable LDAP authentication.

radiusEnable Radius authentication.

<option2> is one of the options: true or false.
Option Description
true

Remote authentication is the first priority. The device will switch to local
authentication when the remote authentication is not available.

false

Always stick to remote authentication regardless of the availability of
remote authentication.

LDAP Settings
All LDAP-related commands begin with authentication ldap.
If you enable LDAP authentication, you must add at least one LDAP server. Later you can modify ordelete any existing LDAP server as needed.

Adding an LDAP Server
Adding an LDAP server requires the entry of quite a lot of parameters, such as the server's IP address,
TCP port number, Base DN and so on.
You can repeat the following CLI command to add more than one LDAP server.

515

▶ Add a new LDAP server:
config:# authentication ldap add <host> <port> <ldap_type> <security><bind_type> <base_DN> <login_name_att> <user_entry_class> "Optional
Parameters"

Note: "Optional Parameters" refer to one or multiple parameters listed in the section Optional
Parameters. They are required only when your server settings need to specify these parameters. For
example, if setting the <bind_type> to "authenticatedBind", then you must add the parameter"bindDN" to this command.
When the above command is successfully performed, a list of all LDAP servers, including the newlyadded one, will be displayed, which is similar to the following diagram.

Variables:•<host> is the IP address or host name of the LDAP server.

•<port> is the port number assigned for communication with the LDAP server.

•<ldap_type> is one of the LDAP server types: openldap or activeDirectory.

•

•

Type

Description

openldap

OpenLDAP server

activeDirectory

Microsoft Active Directory<security> is one of the security options: none, startTls or tls.
Type

Descriptionnone

No security

startTls

StartTLS

tls

TLS<bind_type> is one of the bind options: anonymouseBind, or authenticatedBind.
TypeanonymousBind

Description
Enable the anonymous Bind.
Bind DN and password are NOT required.

516

Type

Description

authenticatedBind

Enable the Bind with authentication.
Bind DN and password are required.

•<base_DN> is the base DN for search.

•<login_name_att> is the login name attribute.

•<user_entry_class> is the User Entry Object Class.

Optional Parameters
You can add one or multiple "optional parameters", such as specifying the Bind DN or certificate upload,to an LDAP-server-adding command as illustrated below. If adding multiple optional parameters, youmust add them to the END of the command and separate them with a space.
•

Example 1 -- Specify an Active Directory Domain's name:config:# authentication ldap add <host> <port> <ldap_type> <security><bind_type> <base_DN> <login_name_att> <user_entry_class>adDomain <AD_domain>•

Example 2 -- Set up the bind DN:

config:# authentication ldap add <host> <port> <ldap_type> <security><bind_type> <base_DN> <login_name_att> <user_entry_class> bindDN<bind_DN>▶ "Optional Parameters" table:
Parameters

To configure

userSearchSubfilter <filter>

User search subfilter

bindDN <bind_DN>bind DN•

The system will prompt you to enter and re-confirm the bindpassword after adding this parameter to the command.

adDomain <AD_domain>

Active Directory Domain nameverifyServerCertificate<verify_cert>

Certificate verification setting

allowExpiredCertificate<allow_exp_cert>

Whether to accept expired or not valid yet certificate•

After setting to true, the system will prompt you to upload acertificate.

Variables:

517

•

<filter> is the user search subfilter you specify.

•<bind_DN> is bind DN.

•<AD_domain> is the Active Directory Domain.

•<verify_cert> is one of the options: true or false.

•

OptionDescription

true

Enable the verification of the LDAP server certificate.

false

Disable the verification of the LDAP server certificate.

<allow_exp_cert> is one of the options: true or false.
Option Description
trueCertificates that are either expired or not valid yet are all accepted.

false

Only valid certificates are accepted.

Illustrations of Adding LDAP Servers
This section shows several LDAP command examples. Those words highlighted in bold are required fortheir respective examples.

▶ An OpenLDAP server:
config:# authentication ldap add op‑ldap.raritan.com 389 openldap noneanonymousBind dc=raritan,dc=com uid inetOrgPerson▶ A Microsoft Active Directory server:
config:# authentication ldap add ac‑ldap.raritan.com 389 activeDirectory noneanonymousBind dc=raritan,dc=com sAMAccountName user adDomain
raritan.com▶ An LDAP server with a TLS certificate uploaded:a. Enter the CLI command with the following two TLS-related options set and/or added:▪ <security> is set to tls or startTls.
▪ The "verifyServerCertificate" parameter is added to the command and set to "true."518

config:# authentication ldap add ldap.raritan.com 389 openldap startTls ...
inetOrgPerson verifyServerCertificate trueb. The system now prompts you to enter the certificate's content.
c. Type or copy the certificate's content in the CLI and press Enter.
Note: Select and copy the content including the starting line containing "BEGIN CERTIFICATE" and theending line containing "END CERTIFICATE."▶ An LDAP server with the bind DN and bind password configured:a. Enter the CLI command with the "bindDN" parameter and its data added.
config:# authentication ldap add op‑ldap.raritan.com 389 openldap none
authenticatedBind cn=Manager,dc=raritan,dc=com uid inetOrgPerson bindDN
user@raritan.com

b. The system prompts you to specify the bind DN password.
c. Type the password and press Enter.
d. Re-type the same password.

Copying an Existing Authentication Server's Settings
If the server that you will add completely shares the same settings with any server that has been
configured, use the following command.

▶ Add an LDAP server by copying an existing server's settings:
config:# authentication ldap addClone <server_num> <host>
Variables:•<host> is the IP address or host name of the LDAP server.

•<server_num> is the sequential number of the specified server shown on the server list.

Modifying an Existing LDAP Server
You can modify one or multiple parameters of an existing LDAP server, such as its IP address, TCP port
number, Base DN and so on. Besides, you can also change the priority or sequence of existing LDAP
servers in the server list.

▶ Command syntax:
A command to modify an existing LDAP server's settings looks like the following:
config:#authentication ldap modify <server_num> "parameters"

519

Variables:•<server_num> is the sequential number of the specified server in the LDAP server list.

•

Replace "parameters" with one or multiple commands in the following table, depending on whichparameter(s) you want to modify.

▶ Parameters:
Parameters

Description

host <host>

Change the IP address or host name.
•port <port>

Change the TCP port number.
•serverType <ldap_type>securityType <security>

bindType <bind_type>searchBaseDN <base_DN>•<ldap_type> is the new type of the LDAP server.

•<ldap_type> values include: openldap and activeDirectory.

Change the security type.
•<security> is the new security type.

•<security> values include: none, startTls, and ssl

Change the bind type.
•<bind_type> is the new bind type.

•<bind_type> values include: anonymousBind andauthenticatedBind.

Change the base DN for search.

<login_name_att> is the new login name attribute.

Change the user entry object class.
•<user_entry_class> is the new user entry class.

userSearchSubfilter<user_search_filter>

Change the user search subfilter.

adDomain <AD_domain>

Change the Active Directory Domain name.

•

•

520

<base_DN> is the new base DN for search.

Change the login name attribute.
•

userEntryObjectClass<user_entry_class><port> is the new TCP port number.

Change the server type.

•loginNameAttribute<login_name_att><host> is the new IP address or host name.

<user_search_filter> is the new user search subfilter.

<AD_domain> is the new domain name of the Active Directory.

Parameters

Description

verifyServerCertificate<verify_cert>

Enable or disable the certificate verification.

certificate•<verify_cert> enables or disables the certificate verification feature.

•

Available values include: true, false

Re-upload a different certificate.

a. First add the "certificate" parameter to the command, and press Enter.
b. The system prompts you for the input of the certificate.
c. Type or copy the content of the certificate in the CLI and press Enter.
allowExpiredCertificate<allow_exp_cert>

bindDN <bind_DN>

Determine whether to accept a certificate which is expired or not valid yet.
•<allow_exp_cert> determines whether to accept an expired or not valid yet
certificate•<allow_exp_cert> values include: true, and false

Change the bind DN.
•

bindPassword<bind_DN> is the new bind DN.

Change the bind DN password.
a. First add the "bindPassword" parameter to the command, and press
Enter.
b. The system prompts you for the input of the password.
c. Type the password and press Enter.

sortPosition <position>

Change the priority of the server (that is, resorting).
•<position> is the new sequential number of the server in the LDAP server list.

▶ Examples:•

Change the IP address of the 1st LDAP server

config:#•Change both the IP address and TCP port of the 1st LDAP server

config:#•authentication ldap modify 1 host 192.168.3.3

authentication ldap modify 1 host 192.168.3.3 port 633

Change the IP address, TCP port and the type of the L1st DAP server

config:# authentication ldap modify 1 host 192.168.3.3 port 633
serverType activeDirectory

Removing an Existing LDAP ServerThis command removes an existing LDAP server from the server list.

521

config:#

authentication ldap delete <server_num>

Variables:•<server_num> is the sequential number of the specified server in the LDAP server list.

Radius Settings
All Radius-related commands begin with authentication radius.
If you enable Radius authentication, you must add at least one Radius server. Later you can modify ordelete any existing Radius server as needed.

Adding a Radius Server
You can repeat the following commands to add Radius servers one by one.

▶ Command syntax:
config:# authentication radius add <host> <rds_type> <auth_port><acct_port> <timeout> <retries>
Variables:•<host> is the IP address or host name of the Radius server.

•<rds_type> is one of the Radius authentication types: pap, chap, msChapV2.
Type

Description

chap

CHAP

pap

PAP

msChapV2

MSCHAP v2•<auth_port> is the authentication port number.

•<acct_port> is the accounting port number.

•<timeout> is the timeout value in seconds. It ranges between 1 to 10 seconds.

•<retries> is the number of retries. It ranges between 0 to 5.

▶ To enter the shared secret:
1. After executing the above Radius command, the system automatically prompts you to enter theshared secret.
2. Type the secret and press Enter.
3. Re-type the same secret and press Enter.

522

▶ Example:
config:#authentication radius add 192.168.7.99 chap 1812 1813 10 3

Modifying an Existing Radius Server
You can modify one or multiple parameters of an existing Radius server, or change the priority or
sequence of existing servers in the server list.

▶ Change the IP address or host name:config:#authentication radius modify <server_num> host <host>▶ Change the Radius authentication type:config:# authentication radius modify <server_num> authType <rds_type>▶ Change the authentication port:
config:# authentication radius modify <server_num> authPort <auth_port>▶ Change the accounting port:
config:# authentication radius modify <server_num> accountPort <acct_port>▶ Change the timeout value:
config:#authentication radius modify <server_num> timeout <timeout>▶ Change the number of retries:
config:#authentication radius modify <server_num> retries <retries>▶ Change the shared secret:config:#authentication radius modify <server_num> secret523

▶ Change the priority of the specified server:
config:# authentication radius modify <server_num> sortPositon <position>

Tip: You can add more than one parameters to the command. For example, "authentication
radius modify <server_num> host <host> authType <rds_type> authPort<auth_port> accountPort <acct_port> ...".
Variables:•<server_num> is the sequential number of the specified server in the Radius server list.

•<host> is the new IP address or host name of the Radius server.

•<rds_type> is one of the Radius authentication types: pap, chap, msChapV2.

•<auth_port> is the new authentication port number.

•<acct_port> is the new accounting port number.

•<timeout> is the new timeout value in seconds. It ranges between 1 to 10 seconds.

•<retries> is the new number of retries. It ranges between 0 to 5.

▶ To enter the shared secret:
1. After executing the above Radius command, the system automatically prompts you to enter theshared secret.
2. Type the secret and press Enter.
3. Re-type the same secret and press Enter.

▶ Example:
config:#authentication radius add 192.168.7.99 chap 1812 1813 10 3

Removing an Existing Radius ServerThis command removes an existing Radius server from the server list.
config:#authentication radius delete <server_num>

Variables:•<server_num> is the sequential number of the specified server in the Radius server list.

Environmental Sensor Configuration Commands
An environmental sensor configuration command begins with externalsensor. You can configure thename and location parameters of an individual environmental sensor. Actuators are configured with
their own commands.

524

Changing the Sensor Name
This command names an environmental sensor.
config:#externalsensor <n> name "<name>"

Variables:•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the web interface or using the command "show externalsensors <n>" in the
CLI. It is an integer starting at 1.

•<name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be
enclosed in quotes when it contains spaces.

Specifying the CC Sensor Type
Raritan's contact closure sensor supports the connection of diverse third-party. You must specify thetype of connected detector/switch for proper operation. Use this command when you need to specify
the sensor type.
config:# externalsensor <n> sensorSubType <sensor_type>
Variables:•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the PX-Series PDU web interface or using the command "show externalsensors<n>" in the CLI. It is an integer starting at 1.

•<sensor_type> is one of these types: contact, smokeDetection, waterDetection or vibration.
Type

Description

contact

The connected detector/switch is for detection of door lock ordoor closed/open status.

smokeDetection The connected detector/switch is for detection of the smokepresence.
waterDetection The connected detector/switch is for detection of the water
presence.
vibration

The connected detector/switch is for detection of the vibration.

Setting the X Coordinate
This command specifies the X coordinate of an environmental sensor.
config:#externalsensor <n> xlabel "<coordinate>"

525

Variables:•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the PX-Series PDU web interface or using the command "show externalsensors<n>" in the CLI. It is an integer starting at 1.

•<coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed inquotes.

Setting the Y Coordinate
This command specifies the Y coordinate of an environmental sensor.
config:#externalsensor <n> ylabel "<coordinate>"

Variables:•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the PX-Series PDU web interface or using the command "show externalsensors<n>" in the CLI. It is an integer starting at 1.

•<coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed inquotes.

Setting the Z Coordinate
This command specifies the Z coordinate of an environmental sensor.
config:#externalsensor <n> zlabel "<coordinate>"

Variables:•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the web interface or using the command "show externalsensors <n>" in the
CLI. It is an integer starting at 1.

•

Depending on the Z coordinate format you set, there are two types of values for the <coordinate>variable:Type

Description

Free form <coordinate> is a string comprising up to 24 ASCII printablecharacters, and it must be enclosed in quotes.
Rack units <coordinate> is an integer number in rack units.

Changing the Sensor Description
This command provides a description for a specific environmental sensor.

526

config:# externalsensor <n> description "<description>"
Variables:•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the web interface or using the command "show externalsensors <n>" in the
CLI. It is an integer starting at 1.

•<description> is a string comprising up to 64 ASCII printable characters, and it must be enclosed inquotes when it contains spaces.

Using Default Thresholds
This command determines whether default thresholds, including the deassertion hysteresis andassertion timeout, are applied to a specific environmental sensor.
config:#externalsensor <n> useDefaultThresholds <option>

Variables:•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the PX-Series PDU web interface or using the command "show externalsensors<n>" in the CLI. It is an integer starting at 1.

•<option> is one of the options: true or false.
Option Description
true

Default thresholds are selected as the threshold option for the specified
sensor.

false

Sensor-specific thresholds are selected as the threshold option for the
specified sensor.

Setting the Alarmed to Normal Delay for DX2-passive infrared sensor
This command determines the value of the Alarmed to Normal Delay setting for a Raritan presence
detector.
config:#externalsensor <n> alarmedToNormalDelay <time>527

Variables:•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the PX-Series PDU web interface or using the command "show externalsensors<n>" in the CLI. It is an integer starting at 1.

•<time> is an integer number in seconds, ranging between 0 and 300.

Configuring Environmental Sensors' Default Thresholds
You can set the default values of upper and lower thresholds, deassertion hysteresis and assertion
timeout on a sensor type basis, including temperature, humidity, air pressure and air flow sensors. The
default thresholds automatically apply to all environmental sensors that are newly detected or added.
A default threshold configuration command begins with defaultThresholds.
You can configure various default threshold settings for the same sensor type at a time by combining
multiple commands.

▶ Set the Default Upper Critical Threshold for a specific sensor type:config:#defaultThresholds <sensor type> upperCritical <value>▶ Set the Default Upper Warning Threshold for a specific sensor type:config:#defaultThresholds <sensor type> upperWarning <value>▶ Set the Default Lower Critical Threshold for a specific sensor type:config:#defaultThresholds <sensor type> lowerCritical <value>▶ Set the Default Lower Warning Threshold for a specific sensor type:config:#defaultThresholds <sensor type> lowerWarning <value>▶ Set the Default Deassertion Hysteresis for a specific sensor type:config:#528

defaultThresholds <sensor type> hysteresis <hy_value>▶ Set the Default Assertion Timeout for a specific sensor type:config:# defaultThresholds <sensor type> assertionTimeout <as_value>
Variables:••<sensor type> is one of the following numeric sensor types:
Sensor types

Description

absoluteHumidity

Absolute humidity sensors

relativeHumidity

Relative humidity sensors

temperature

Temperature sensors

airPressure

Air pressure sensors

airFlow

Air flow sensors

vibration

Vibration sensors<value> is the value for the specified threshold of the specified sensor type. Note that diverse
sensor types use different measurement units.
Sensor types

Measurement units

absoluteHumidity g/m^3 (that is, g/m3)
relativeHumidity%

temperature

Degrees Celsius (°C) or Fahrenheit (°F), depending on yourmeasurement unit settings.

airPressure

Pascal (Pa) or psi, depending on your measurement unit settings.

airFlowm/s

vibrationg•<hy_value> is the deassertion hysteresis value applied to the specified sensor type.

•<as_value> is the assertion timeout value applied to the specified sensor type. It ranges from 0 to
100 (samples).

529

Example - Default Upper Thresholds for Temperature
It is assumed that your preferred measurement unit for temperature is set to degrees Celsius. Then thefollowing command sets the default Upper Warning threshold to 20
24

and Upper Critical threshold tofor all temperature sensors.

config:# defaultThresholds temperature upperWarning 20
upperCritical 24

Sensor Threshold Configuration Commands
A sensor configuration command begins with sensor. You can use the commands to configure thethreshold, hysteresis and assertion timeout values for any sensor associated with the following items:•

Outlets•

Outlet groups•

Inlets•

Inlet poles (for three-phase PDUs only)•

Overcurrent protectors•

Environmental sensors

It is permitted to assign a new value to the threshold at any time regardless of whether the thresholdhas been enabled.
Note: Your Xerus product may not support all commands.

Commands for Outlet Sensors
A sensor configuration command for outlets begins with sensor outlet.
You can configure various outlet sensor threshold settings at a time by combining multiple commands.

▶ Set the Upper Critical threshold for an outlet sensor:
config:#sensor outlet <n> <sensor type> upperCritical <option>▶ Set the Upper Warning threshold for an outlet sensor:
config:#530

sensor outlet <n> <sensor type> upperWarning <option>

▶ Set the Lower Critical threshold for an outlet sensor:
config:#sensor outlet <n> <sensor type> lowerCritical <option>▶ Set the Lower Warning threshold for an outlet sensor:
config:#sensor outlet <n> <sensor type> lowerWarning <option>▶ Set the deassertion hysteresis for an outlet sensor:
config:#sensor outlet <n> <sensor type> hysteresis <hy_value>▶ Set the assertion timeout for an outlet sensor:
config:# sensor outlet <n> <sensor type> assertionTimeout <as_value>
Variables:•<n> is the number of the outlet that you want to configure.

•<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

lineFrequency

Line frequency sensor

Note: If the requested sensor type is not supported, the "Sensor is not available" message isdisplayed.
•<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for a specific outlet sensor.

531

OptionDescription

disableDisables the specified threshold for a specific outlet sensor.

A numeric value Sets a value for the specified threshold of a specific outlet
sensor and enables this threshold at the same time.

•<hy_value> is a numeric value that is assigned to the hysteresis for the specified outlet sensor. See"To De-assert" and Deassertion Hysteresis.

•<as_value> is a number in samples that is assigned to the assertion timeout for the specified outlet
sensor. See "To Assert" and Assertion Timeout.

Commands for Outlet Group Sensors
A sensor configuration command for outlets begins with sensor outletgroup.
You can configure various outlet group sensor threshold settings at a time by combining multiplecommands.

▶ Set the Upper Critical threshold for an outlet group sensor:
config:#sensor outletgroup <ID> <sensor type> upperCritical <option>▶ Set the Upper Warning threshold for an outlet group sensor:
config:#sensor outletgroup <ID> <sensor type> upperWarning <option>▶ Set the Lower Critical threshold for an outlet group sensor:
config:#sensor outletgroup <ID> <sensor type> lowerCritical <option>▶ Set the Lower Warning threshold for an outlet group sensor:
config:#sensor outletgroup <ID> <sensor type> lowerWarning <option>▶ Set the deassertion hysteresis for an outlet group sensor:
config:#532

sensor outletgroup <ID> <sensor type> hysteresis <hy_value>▶ Set the assertion timeout for an outlet group sensor:
config:# sensor outletgroup <ID> <sensor type> assertionTimeout <as_value>
Variables:•<ID> is an outlet group's index number.

•<sensor type> is one of the following sensor types:
Sensor type

Description

activePowerAn outlet group's active power sensor

activeEnergy

An outlet group's active energy sensor

For definitions on an outlet group's sensors, see Outlet Groups.
•<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for a specific group sensor of thechosen outlet group.

disableDisables the specified threshold for a specific group sensor of thechosen outlet group.

A numericvalue

Sets a value for the specified threshold of the chosen outlet
group's specific group sensor, and enables this threshold at thesame time.

•<hy_value> is a numeric value that is assigned to the hysteresis for the specified group sensor of thechosen outlet group.

•<as_value> is a number in samples that is assigned to the assertion timeout for the specified group
sensor of the chosen outlet group.

Commands for Inlet Sensors
A sensor configuration command for inlets begins with sensor inlet.
You can configure various inlet sensor threshold settings at a time by combining multiple commands.

▶ Set the Upper Critical threshold for an inlet sensor:
config:# sensor inlet <n> <sensor type> upperCritical <option>533

▶ Set the Upper Warning threshold for an inlet sensor:
config:# sensor inlet <n> <sensor type> upperWarning <option>▶ Set the Lower Critical threshold for an inlet sensor:
config:# sensor inlet <n> <sensor type> lowerCritical <option>▶ Set the Lower Warning threshold for an inlet sensor:
config:# sensor inlet <n> <sensor type> lowerWarning <option>▶ Set the deassertion hysteresis for an inlet sensor:
config:# sensor inlet <n> <sensor type> hysteresis <hy_value>▶ Set the assertion timeout for an inlet sensor:
config:# sensor inlet <n> <sensor type> assertionTimeout <as_value>
Variables:

534•<n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always 1.

•<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

unbalancedCurrent

Unbalanced load sensor

lineFrequency

Line frequency sensor

phaseAngle

Inlet phase angle sensor

Note: If the requested sensor type is not supported, the "Sensor is not available" message isdisplayed.
•<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for a specific inlet sensor.

disableDisables the specified threshold for a specific inlet sensor.

A numeric value Sets a value for the specified threshold of a specific inlet sensor
and enables this threshold at the same time.

•<hy_value> is a numeric value that is assigned to the hysteresis for the specified inlet sensor.

•<as_value> is a numeric value that is assigned to the assertion timeout for the specified inlet sensor.

Commands for Inlet Pole Sensors
A sensor configuration command for inlet poles begins with sensor inletpole. This type of command isavailable on a three-phase PDU only.
You can configure various inlet pole sensor threshold settings at a time by combining multiplecommands.

▶ Set the Upper Critical Threshold for an Inlet Pole:config:# sensor inletpole <n> <p> <sensor type> upperCritical <option>▶ Set the Upper Warning Threshold for an Inlet Pole:config:# sensor inletpole <n> <p> <sensor type> upperWarning <option>▶ Set the Lower Critical Threshold for an Inlet Pole:config:# sensor inletpole <n> <p> <sensor type> lowerCritical <option>▶ Set the Lower Warning Threshold for an Inlet Pole:config:# sensor inletpole <n> <p> <sensor type> lowerWarning <option>535

▶ Set the Inlet Pole's Deassertion Hysteresis:
config:#sensor inletpole <n> <p> <sensor type> hysteresis <hy_value>▶ Set the Inlet Pole's Assertion Timeout:config:# sensor inletpole <n> <p> <sensor type> assertionTimeout<as_value>
Variables:•<n> is the number of the inlet whose pole sensors you want to configure. For a single-inlet PDU, <n>is always 1.

•<p> is the label of the inlet pole that you want to configure.

•

Pole

Label
<p>

Current sensor

Voltage sensor

1

L1

L1

L1 - L22

L2

L2

L2 - L33

L3

L3

L3 - L1<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentEnergy

Apparent Energy sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

L-L Voltage

Voltage is measured per line

Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.
•

536<option> is one of the options: enable, disable or a numeric value.

OptionDescription

enableEnables the specified threshold for the specified inlet polesensor.

disableDisables the specified threshold for the specified inlet polesensor.

A numericvalue

Sets a value for the specified threshold of the specified inlet
pole sensor and enables this threshold at the same time.

•<hy_value> is a numeric value that is assigned to the hysteresis for the specified inlet pole sensor.

•<as_value> is a number in samples that is assigned to the assertion timeout for the specified inlet
pole sensor.

▶ Additional sensors supported by specific models:Specific models support some or all of the following sensors. The CLI command(s) listed above can bealso applied to the following sensors. Note that the measurement unit of current values in CLI is A, notmA.
Sensor type

Description

peakCurrent

Peak current sensor

reactivePower

Supported on PXC and Legrand
PDU only•

three-phase models also
support pole-level peakcurrent•

models with meteredbreakers also support
breaker-level peak current

Reactive power sensor

displacementPowerFactor Displacement power factor sensor
residualCurrent

residualDCCurrent

RCM current sensor•

For Type A, it is the sensor that detects residual AC
current.

•

For Type B, it is the sensor that detects bothresidual AC and DC current.

RCM DC current sensor - detects residual DC current
only.
Available only on PDUs with RCM Type B.

Commands for Overcurrent Protector Sensors
A sensor configuration command for overcurrent protectors begins with sensor ocp.

537

You can configure various overcurrent protector threshold settings at a time by combining multiplecommands.

▶ Set the Upper Critical threshold for an overcurrent protector:
config:#sensor ocp <n> <sensor type> upperCritical <option>▶ Set the Upper Warning threshold for an overcurrent protector:
config:#sensor ocp <n> <sensor type> upperWarning <option>▶ Set the Lower Critical threshold for an overcurrent protector:
config:#sensor ocp <n> <sensor type> lowerCritical <option>▶ Set the Lower Warning threshold for an overcurrent protector:
config:#sensor ocp <n> <sensor type> lowerWarning <option>▶ Set the deassertion hysteresis for an overcurrent protector:
config:#sensor ocp <n> <sensor type> hysteresis <hy_value>▶ Set the assertion timeout for an overcurrent protector:
config:#sensor ocp <n> <sensor type> assertionTimeout <as_value>▶ Set the residual current sensor parameters
config:# sensor ocp <n> residualCurrent|residualDCCurrent
upperCritical|upperWarning|lowerWarning|lowerCritical|
hysteresis|assertionTimeout <as_value>
Variables:

538•<n> is the number of the overcurrent protector that you want to configure.

•<sensor type> is one of the following sensor types:

Sensor type

Description

current

Current sensor

Note: If the requested sensor type is not supported, the "Sensor is not available" message isdisplayed.
•<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for the overcurrent protector
sensor.

disableDisables the specified threshold for the overcurrent protector
sensor.

A numeric value Sets a value for the specified threshold of the overcurrent
protector sensor and enables this threshold at the same time.

•<hy_value> is a numeric value that is assigned to the hysteresis for the specified overcurrent
protector sensor.

•<as_value> is a number in samples that is assigned to the assertion timeout for the specified
overcurrent protector sensor.

▶ Additional sensors supported by specific models:Specific models support OCP residual current sensors per input phase, and output branches. The CLI
command(s) listed above can be also applied to the following sensors. Note that the measurement unitof current values in CLI is A, not mA.
Sensor type

Description

residualCurrent

RCM current sensor•

For Type A, it is the sensor that detects residual AC
current.

•

For Type B, it is the sensor that detects both residual AC
and DC current.

residualDCCurrent RCM DC current sensor - detects residual DC current only.
Available only on PDUs with RCM Type B.
residualACCurrent RCM AC current sensor - detects residual AC current only.
Available only on PDUs with RCM Type A.

Commands for Environmental Sensors
A sensor threshold configuration command for environmental sensors begins with sensor
externalsensor.

539

You can configure various environmental sensor threshold settings at a time by combining multiplecommands.

▶ Set the Upper Critical threshold for an environmental sensor:
config:# sensor externalsensor <n> <sensor type> upperCritical <option>▶ Set the Upper Warning threshold for an environmental sensor:
config:# sensor externalsensor <n> <sensor type> upperWarning <option>▶ Set the Lower Critical threshold for an environmental sensor:
config:# sensor externalsensor <n> <sensor type> lowerCritical <option>▶ Set the Lower Warning threshold for an environmental sensor:
config:# sensor externalsensor <n> <sensor type> lowerWarning <option>▶ Set the deassertion hysteresis for an environmental sensor:
config:# sensor externalsensor <n> <sensor type> hysteresis <hy_value>▶ Set the assertion timeout for an environmental sensor:
config:# sensor externalsensor <n> <sensor type> assertionTimeout<as_value>
Variables:

540•<n> is the ID number of the environmental sensor that you want to configure. The ID number isavailable in the web interface or using the command "show externalsensors <n>" in the
CLI. It is an integer starting at 1.

•<sensor type> is one of the following numeric sensor types:
Sensor types

Description

absoluteHumidity

Absolute humidity sensors

Sensor types

Description

relativeHumidity

Relative humidity sensors

temperature

Temperature sensors

airPressure

Air pressure sensors

airFlow

Air flow sensors

vibration

Vibration sensors

Note: If the specified sensor type does not match the type of the specified environmental sensor, thiserror message appears: "Specified sensor type 'XXX' does not match the sensor's type(<sensortype>)," where XXX is the specified sensor type, and <sensortype> is the correct sensor type.
•<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for a specific environmental
sensor.

disableDisables the specified threshold for a specific environmental
sensor.

A numericvalue

Sets a value for the specified threshold of a specificenvironmental sensor and enables this threshold at the same
time.

•

<hy_value> is a numeric value that is assigned to the hysteresis for the specified environmental
sensor.

•<as_value> is a number in samples that is assigned to the assertion timeout for the specified
environmental sensor. It ranges between 1 and 100.

Actuator Configuration Commands
An actuator configuration command begins with actuator. You can configure the name and location
parameters of an individual actuator.
You can configure various parameters for one actuator at a time.

▶ Change the name:config:#actuator <n> name "<name>"541▶ Set the X coordinate:config:#actuator <n> xlabel "<coordinate>"▶ Set the Y coordinate:config:#actuator <n> ylabel "<coordinate>"▶ Set the Z coordinate:config:#actuator <n> zlabel "<z_label>"▶ Modify the actuator's description:
config:#actuator <n> description "<description>"

Variables:•<n> is the ID number assigned to the actuator. The ID number can be found using the web interface
or CLI. It is an integer starting at 1.

•<name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be
enclosed in quotes when it contains spaces.

•<coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed inquotes.

•There are two types of values for the <z_label> variable, depending on the Z coordinate format you
set:
Type

Description

Free form <coordinate> is a string comprising up to 24 ASCII printablecharacters, and it must be enclosed in quotes.
Rack units <coordinate> is an integer number in rack units.

•<description> is a string comprising up to 64 ASCII printable characters, and it must be enclosed inquotes when it contains spaces.

Example - Actuator Naming
The following command assigns the name "Door lock of cabinet 3" to the actuator whose ID number is9.

542

config:#

actuator 9 name "Door lock of cabinet 3"

Server Reachability Configuration Commands
You can use the CLI to add or delete an IT device, such as a server, from the server reachability list, or
modify the settings for a monitored IT device. A server reachability configuration command begins with
serverReachability.

Adding a Monitored Device
This command adds a new IT device to the server reachability list.
config:# serverReachability add <IP_host> <enable> <succ_ping><fail_ping> <succ_wait> <fail_wait> <resume> <disable_count>
Variables:•<IP_host> is the IP address or host name of the IT device that you want to add.

•<enable> is one of the options: true or false.
Option Description
true

Enables the ping monitoring feature for the newly added device.

false

Disables the ping monitoring feature for the newly added device.

•<succ_ping> is the number of successful pings for declaring the monitored device "Reachable." Valid
range is 0 to 200.

•

<fail_ping> is the number of consecutive unsuccessful pings for declaring the monitored device"Unreachable." Valid range is 1 to 100.

•

<succ_wait> is the wait time to send the next ping after a successful ping. Valid range is 5 to 600(seconds).

•<fail_wait> is the wait time to send the next ping after an unsuccessful ping. Valid range is 3 to 600(seconds).

•<resume> is the wait time before the PX-Series PDU resumes pinging after declaring the monitored
device "Unreachable." Valid range is 5 to 120 (seconds).

•<disable_count> is the number of consecutive "Unreachable" declarations before the PX-Series PDU
disables the ping monitoring feature for the monitored device and returns to the "Waiting for
reliable connection" state. Valid range is 1 to 100 or unlimited.

Deleting a Monitored Device
This command removes a monitored IT device from the server reachability list.
config:#serverReachability delete <n>543

Variables:•<n> is a number representing the sequence of the IT device in the monitored server list.
You can find each IT device's sequence number using the CLI command of show
serverReachability as illustrated below.

Modifying a Monitored Device's Settings
The command to modify a monitored IT device's settings begins with serverReachability modify.
You can modify various settings for a monitored device at a time.

▶ Modify a device's IP address or host name:config:#serverReachability modify <n> ipAddress <IP_host>▶ Enable or disable the ping monitoring feature for the device:config:# serverReachability modify <n> pingMonitoringEnabled <option>▶ Modify the number of successful pings for declaring "Reachable":
config:# serverReachability modify <n> numberOfSuccessfulPingsToEnable<succ_number>▶ Modify the number of unsuccessful pings for declaring "Unreachable":
config:# serverReachability modify <n> numberOfUnsuccessfulPingsForFailure<fail_number>▶ Modify the wait time after a successful ping:config:# serverReachability modify <n> waitTimeAfterSuccessfulPing<succ_wait>544

▶ Modify the wait time after an unsuccessful ping:config:# serverReachability modify <n> waitTimeAfterUnsuccessfulPing<fail_wait>▶ Modify the wait time before resuming pinging after declaring "Unreachable":
config:# serverReachability modify <n> waitTimeBeforeResumingPinging<resume>▶ Modify the number of consecutive "Unreachable" declarations before disabling the pingmonitoring feature:
config:# serverReachability modify <n> numberOfFailuresToDisable<disable_count>
Variables:•<n> is a number representing the sequence of the IT device in the server monitoring list.

•<IP_host> is the IP address or host name of the IT device whose settings you want to modify.

•<option> is one of the options: true or false.
OptionDescription

true

Enables the ping monitoring feature for the monitored device.

false

Disables the ping monitoring feature for the monitored device.

•<succ_number> is the number of successful pings for declaring the monitored device "Reachable."
Valid range is 0 to 200.

•

<fail_number> is the number of consecutive unsuccessful pings for declaring the monitored device"Unreachable." Valid range is 1 to 100.

•

<succ_wait> is the wait time to send the next ping after a successful ping. Valid range is 5 to 600(seconds).

•<fail_wait> is the wait time to send the next ping after an unsuccessful ping. Valid range is 3 to 600(seconds).

•<resume> is the wait time before the system resumes pinging after declaring the monitored device"Unreachable." Valid range is 5 to 120 (seconds).

•<disable_count> is the number of consecutive "Unreachable" declarations before disabling the pingmonitoring feature for the monitored device and returns to the "Waiting for reliable connection"state. Valid range is 1 to 100 or unlimited.

545

Example - Server Settings Changed
The following command modifies several ping monitoring settings for the second server in the server
reachability list.
config:# serverReachability modify 2 numberOfSuccessfulPingsToEnable 10
numberOfUnsuccessfulPingsForFailure 8
waitTimeAfterSuccessfulPing 30

Peripheral Devices Configuration Commands
You can use the CLI to set the Z Coordinate format for external sensors, set the device altitude, enable/
disable device auto management, set the active powered dry contact limit, and enable/disable the"mute other door handle" setting.
Peripheral device configuration commands begin with:config:# peripheralDevicesSetup
Field

DescriptionMore Information

externalSensorsZCoordinateFormat Keyword

Z coordinate refers to the height of sensors.

rackUnits / freeForm

rackUnits: The height of the Z coordinate is measured
in standard rack units. Type a numeric value in therack unit to describe the Z coordinate.

Enter one of thesevaluesfreeForm: Any alphanumeric string can be used forspecifying the Z coordinate.

deviceAltitude

KeywordSpecifies the altitude of your PDU above sea
level (in meters). Must be set if a differential airpressure sensor is attached because the device's
altitude is associated with the altitude
correction factor.

number1

Enter an integer
number from -425 up
to 3000 when using
Meters.

Negative numbers indicate altitude below sea
level.

peripheralDeviceAutoManagement Keyword

546

Enable or disable the automatic management
feature for sensors.

enable / disable

Enter one of thesevaluesactivePoweredDryContactLimit

Keyword

You need either 'Change Peripheral Device
Configuration' privilege or 'Administrator
Privileges'.

number2

Enter an integer
number from 0 - 24.

An "active" actuator is turned ON, or, if with adoor handle connected, is OPENED.

muteOtherDoorHandle

Keywordenable / disable

Enter one of thesevalues▶ Examples:
config:# peripheralDevicesSetup
externalSensorsZCoordinateFormat freeForm
deviceAltitude 3
peripheralDeviceAutoManagement enable
activePoweredDryContactLimit 2
muteOtherDoorHandle disable

Asset Management Commands
You can use the CLI commands to change the settings of the connected asset strip (if any) or the settingsof LEDs on the asset strip.

Asset Strip Management
An asset strip management configuration command begins with assetStrip.

Rack Unit Configuration (Tag Ports)
A rack unit refers to a tag port on the asset strips. A rack unit configuration command begins with
rackUnit.

547

Example - Asset Management
This section illustrates several asset management examples.

▶ Example 1 - Asset Strip LED Colors for Disconnected Tags
This command syntax sets the LED color for all rack units on the asset sensor #1 to BLACK (that is,
000000) to indicate the absence of a connected asset tag.
config:#assetStrip 1 LEDColorForDisconnectedTags #000000

Note: Black color causes the LEDs to stay off.

▶ Example 2 - Rack Unit Naming
The following command assigns the name "Linux server" to the rack unit whose index number is 25 on
the asset sensor#1.
config:#rackUnit 1 25 name "Linux server"

Serial Port Configuration Commands
A serial port configuration command begins with serial.

Setting the Baud Rates
The following commands set the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the
PX-Series PDU device. Change the baud rate before connecting it to the desired device, such as acomputer, a Raritan's P2CIM‑SER, or a modem, through the serial port, or there are communications
errors. If you change the baud rate dynamically after the connection has been made, you must reset the
PX-Series PDU or power cycle the connected device for proper communications.

▶ Determine the CONSOLE baud rate:
config:#serial consoleBaudRate <baud_rate>

Note: The serial port bit-rate change is required when the PX-Series PDU works in conjunction with
Raritan's Dominion LX KVM switch. Dominion LX only supports 19200 bps for communications over theserial interface.

▶ Determine the MODEM baud rate:
config:#548

serial modemBaudRate <baud_rate>

Variables:•<baud_rate> is one of the baud rate options: 1200, 2400, 4800, 9600, 19200, 38400, 57600,
115200.

Forcing the Device Detection Mode
This command forces the serial port on the PX-Series PDU to enter a specific device detection mode.
config:#serial deviceDetectionType <mode>

Variables:•<mode> is one of the detection modes: automatic, forceConsole, forceAnalogModem, orforceGsmModem.
OptionDescription

automatic

The PX-Series PDU automatically detects the type of thedevice connected to the serial port.
Select this option unless your PX-Series PDU cannot
correctly detect the device type.

forceConsole

The PX-Series PDU attempts to recognize that the connected
device is set for the console mode.

forceAnalogModem The PX-Series PDU attempts to recognize that the connected
device is an analog modem.
forceGsmModem

The PX-Series PDU attempts to recognize that the connected
device is a GSM modem.

Example - Baud Rate
The following command sets the CONSOLE baud rate of the PX-Series PDU device's serial port to 9600bps.
config:#serial consoleBaudRate 9600

Load Shedding Configuration Commands
This section applies to outlet-switching capable models only.
A load shedding configuration command begins with loadshedding.
Unlike other CLI configuration commands, the load shedding configuration command is performed in
the administrator mode rather than the configuration mode.

549

Enabling or Disabling Load SheddingThis section applies to outlet-switching capable models only.
This command determines whether to enter or exit from the load shedding mode.
#loadshedding <option>

After performing the above command, PX-Series PDU prompts you to confirm the operation. Press y toconfirm or n to abort the operation.
To skip the confirmation step, you can add the "/y" parameter to the end of the command so that theoperation is executed immediately.
#loadshedding <option> /yVariables:•<option> is one of the options: enable or disable.
OptionDescription

startEnter the load shedding mode.

stop

Quit the load shedding mode.

▶ Example
The following command has the PX-Series PDU enter the load shedding mode.
config:#loadshedding startPower Control Operations
This section applies to outlet-switching capable models only.
Outlets can be turned on or off, or power cycled through the CLI.
You can also cancel the power-on process while the system is powering on ALL outlets.
You must perform this operation in the administrator mode.

550

Turning On the Outlet(s)This section applies to outlet-switching capable models only.
This command turns on one or multiple outlets.
#

power outlets <numbers> on

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms
the operation.
#

power outlets <numbers> on /yVariables:•<numbers> is one of the options: all, an outlet number, a list or a range of outlets.
OptionDescription

all

Switches ON all outlets.

A specific outlet
number

Switches ON the specified outlet.

A comma- separated
list of outlets

Switches ON multiple, inconsecutive or consecutive
outlets.
For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and15, type:
outlets 2,4,9,11-13,15.

A range of outlets with Switches ON multiple, consecutive outlets.
a hyphen in between
For example, to specify 6 consecutive outlets -- 3, 4, 5, 6,
7, 8, type:outlets 3-8.

If you entered the command without "/y", a message appears, prompting you to confirm the operation.
Then:•

Type y to confirm the operation, OR•

Type n to abort the operation

If you have configured outlet switching sequence and/or delay, PX-Series PDU will prompt you with one
more question:

551

Should outlet sequence order and delays be used during switching?
•Type y to apply the current outlet sequence and delay settings when switching on outlets. See
Setting Outlet Power-On Sequence and Delay.

•

Type n to apply the default sequence and delays.

Turning Off the Outlet(s)This section applies to outlet-switching capable models only.
This command turns off one or multiple outlets.
#

power outlets <numbers> off

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms
the operation.
#

power outlets <numbers> off /yVariables:•<numbers> is one of the options: all, an outlet number, a list or a range of outlets.
OptionDescription

all

Switches OFF all outlets.

A specific outlet
number

Switches OFF the specified outlet.

A comma- separated
list of outlets

Switches OFF multiple, inconsecutive or consecutive
outlets.
For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and15, type:
outlets 2,4,9,11-13,15.

552

OptionDescription

A range of outlets with Switches OFF multiple, consecutive outlets.
a hyphen in between
For example, to specify 6 consecutive outlets -- 3, 4, 5, 6,
7, 8, type:outlets 3-8.

If you entered the command without "/y", a message appears, prompting you to confirm the operation.
Then:•

Type y to confirm the operation, OR•

Type n to abort the operation

Power Cycling the Outlet(s)This section applies to outlet-switching capable models only.
This command power cycles one or multiple outlets.
#

power outlets <numbers> cycle

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms
the operation.
#

power outlets <numbers> cycle /yVariables:•<numbers> is one of the options: all, an outlet number, a list or a range of outlets.
OptionDescription

allPower cycles all outlets.

A specific outlet
numberPower cycles the specified outlet.

A comma- separated
list of outlets

Power cycles multiple, inconsecutive or consecutive
outlets.
For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and15, type:
outlets 2,4,9,11-13,15.

553

OptionDescription

A range of outlets with Power cycles multiple, consecutive outlets.
a hyphen in between
For example, to specify 6 consecutive outlets -- 3, 4, 5, 6,
7, 8, type:outlets 3-8.

If you entered the command without "/y", a message appears, prompting you to confirm the operation.
Then:•

Type y to confirm the operation, OR•

Type n to abort the operation

If you have configured outlet switching sequence and/or delay, PX-Series PDU will prompt you with one
more question:
Should outlet sequence order and delays be used during switching?
•Type y to apply the current outlet sequence and delay settings when switching on outlets. See
Setting Outlet Power-On Sequence and Delay.

•

Type n to apply the default sequence and delays.

Canceling the Power-On ProcessThis section applies to outlet-switching capable models only.
After issuing the command to power on ALL outlets, you can use the following command to stop thepower-on process.
#power cancelSequence

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms
the operation.
#

power cancelSequence /yExample - Power Cycling Specific Outlets
The following command power cycles these outlets: 2, 6, 7, 8, 10, 13, 14, 15 and 16.
#554

power outlets 2,6-8,10,13-16 cycle

Actuator Control Operations
An actuator, which is connected to a dry contact signal channel of a sensor package, can control amechanism or system. You can switch on or off that mechanism or system through the actuator control
command in the CLI.
Perform these commands in the administrator or user mode.

Switching On an Actuator
This command syntax turns on one actuator.
#

control actuator <n> on

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms
the operation.
#

control actuator <n> on /yVariables:•<n> is an actuator's ID number.
The ID number is available in the PX-Series PDU web interface or using the show commandin the CLI. It is an integer starting at 1.

If you entered the command without "/y", a message appears, prompting you to confirm the operation.
Then:•

Type y to confirm the operation, OR•

Type n to abort the operation

Switching Off an Actuator
This command syntax turns off one actuator.
#

control actuator <n> off

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms
the operation.
#

control actuator <n> off /yVariables:•<n> is an actuator's ID number.

555

The ID number is available in the PX-Series PDU web interface or using the show commandin the CLI. It is an integer starting at 1.
If you entered the command without "/y", a message appears, prompting you to confirm the operation.
Then:•

Type y to confirm the operation, OR•

Type n to abort the operation

Example - Turning On a Specific Actuator
The following command turns on the actuator whose ID number is 8.
#

control actuator 8 on

Unblocking a User
If any user is blocked from accessing, you can unblock them at the local console.

▶ To unblock a user:
1. Access the CLI interface using any terminal program via a local connection.
2. When the Username prompt appears, type unblock and press Enter.

3. When the "Username to unblock" prompt appears, type the name of the blocked user and press
Enter.

4. A message appears, indicating that the specified user was unblocked successfully.

Resetting the PX-Series PDU
You can reset the PX-Series PDU to factory defaults or simply restart it using the CLI commands.

Restarting the PX-Series PDU
This command restarts the PX-Series PDU. It is not a factory default reset.

▶ To restart the PX-Series PDU:
1. Ensure you have entered administrator mode and the # prompt is displayed.
2. Type either of the following commands to restart the PX-Series PDU.
#

556

reset unit

-- OR -#reset unit /y

3. If you entered the command without "/y" in Step 2, a message appears prompting you to confirm
the operation. Type y to confirm the reset.
4. Wait until the reset is complete.
Note: Device reset will cause CLI communications over an "USB" connection to be lost. Therefore, reconnect the USB cable after the reset is complete.

Resetting Energy Readings
You can reset either one energy sensor or all energy sensors at a time to restart the energy
accumulation process.
Only users with the "Admin" role assigned can reset energy readings.

▶ To reset all energy counters:
All counters includes inlets, outlets, and PDU (for multi-inlet models).
#

reset energy pdu-- OR -#

reset energy pdu /y▶ To reset one inlet's energy readings:#

reset energy inlet <n>-- OR -#

reset energy inlet <n> /y557

▶ To reset one outlet's energy readings:#

reset energy outlet <outlet_n>-- OR -#

reset energy outlet <outlet_n> /y▶ To reset one outlet group's energy readings:#

reset energy outletgroup <ID>-- OR -#

reset energy outletgroup <ID> /y

If you entered the command without "/y", a message appears prompting you to confirm the operation.
Type y to confirm the reset or n to abort it.
Variables:•<n> is the inlet number.

•<outlet_n> is an outlet number.

•<ID> is an outlet group's index number.

Resetting to Factory Defaults
The following commands restore all settings of the PX-Series PDU to factory defaults.

558

▶ To reset PX-Series PDU settings after login, use either command:#

reset factorydefaults-- OR -#

reset factorydefaults /y▶ To reset PX-Series PDU settings before login:
Username:factorydefaults

See Using the CLI Command for details.
Note: Device reset will cause CLI communications over an "USB" connection to be lost. Therefore, reconnect the USB cable after the reset is complete.

Network Troubleshooting in Diagnostic Mode
The PX-Series PDU provides 4 diagnostic commands for troubleshooting network problems: nslookup,
netstat, ping, and traceroute. The diagnostic commands function as corresponding Linux commands
and can get corresponding Linux outputs.
The diagnostic command syntax varies from command to command.
Diagnostic commands function in the diagnostic mode only.

▶ To enter the diagnostic mode:
1. Enter either of the following modes:• Administrator mode: The # prompt is displayed.
• User mode: The > prompt is displayed.
2. Type diag and press Enter. The diag# or diag> prompt appears, indicating that you have entered
the diagnostic mode.
3. Now you can type any diagnostic commands for troubleshooting.

▶ To quit the diagnostic mode:
diag>

exit

The # or > prompt appears after pressing Enter, indicating that you have entered the administrator oruser mode.

Querying DNS Servers
This command syntax queries Internet domain name server (DNS) information of a network host.

559

diag>

nslookup <host>

Variables:•<host> is the name or IP address of the host whose DNS information you want to query.

Showing Network Connections
This command syntax displays network connections and/or status of ports.
diag>

netstat <option>

Variables:•<option> is one of the options: ports or connections.
OptionDescription

ports

Shows TCP/UDP ports.

connections

Shows network connections.

Testing the Network Connectivity
This ping command sends the ICMP ECHO_REQUEST message to a network host for checking its
network connectivity. If the output shows the host is responding properly, the network connectivity isgood. If not, either the host is shut down or it is not being properly connected to the network.
diag>ping <host>

Variables:•<host> is the host name or IP address whose networking connectivity you want to check.

Options:•

You can include any or all of additional options listed below in the ping command.
Options

Description

count <number1> Determines the number of messages to be sent. <number1>
is an integer number between 1 and 100.
size <number2>

560

Determines the packet size. <number2> is an integer number
in bytes between 1 and 65468.

Options

Description

timeout<number3>

Determines the waiting period before timeout. <number3> isan integer number in seconds ranging from 1 to 600.

The command looks like the following when it includes all options:
diag> ping <host> count <number1> size <number2> timeout <number3>

Tracing the RouteThis command syntax traces the network route between your PX-Series PDU and a network host.
diag>

traceroute <host> <useICMP> <timeout>

Variables:•<host> is the name or IP address of the host you want to trace.

•<useICMP> is optional. It has only one value -- useICMP. Type useICMP in the end of thiscommand only when you want to use ICMP packets rather than UDP packets.

•<timeout> is the maximum amount of time (in seconds) until traceroute will be terminated (1..900).

Example - Ping Command
The following command checks the network connectivity of the host 192.168.84.222 by sending the
ICMP ECHO_REQUEST message to the host for 5 times. You can also use ipv6 address to check theconnectivity.
diag> ping 192.168.84.222 count 5
ping fd07:a47c:0000:823e:3b02:0000:982b:0463
count 5

Example: Ping Monitoring and SNMP Notifications
In this illustration, it is assumed that a significant PDU (IP address: 192.168.84.95) shall be monitored byyour PX-Series PDU to make sure that PDU is properly operating all the time, and the PX-Series PDU
must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or
network failure. The prerequisite for this example is that the power sources are different between yourPX-Series PDU and the monitored PDU.
This requires the following two steps.

561

▶ Step 1: Set up the ping monitoring for the target PDU
1. Choose Device Settings > Server Reachability.
2. Click.
3. Ensure the "Enable ping monitoring for this server" checkbox is selected.
4. Enter the data shown below.
• Enter the server's data.
Field

Data entered

IP address/hostname

192.168.84.95• To make the PX-Series PDU declare the accessibility of the monitored PDU every 15 seconds (3pings * 5 seconds) when that PDU is accessible, enter the following data.
Field

Data entered

Number of successful pings to enable feature

3

Wait time after successful ping5

• To make the PX-Series PDU declare the inaccessibility of the monitored PDU when that PDU
becomes inaccessible for around 12 seconds (4 seconds * 3 pings), enter the following data.
Field

Data entered

Wait time after unsuccessful ping4

Number of consecutive unsuccessful pings for failure

3• To make the PX-Series PDU stop pinging the target PDU for 60 seconds (1 minute) after the PDU
inaccessibility is declared, enter the following data. After 60 seconds, the PX-Series PDU will re-ping
the target PDU,
Field

Data entered

Wait time before resuming pinging after failure

60• The "Number of consecutive failures before disabling feature (0 = unlimited)" can be set to any
value you want.
5. Click Create.

▶ Step 2: Create an event rule to send SNMP notifications for the target PDU
1. Choose Device Settings > Event Rules.
2. Click.
3. Select the Enabled checkbox to enable this new rule.
4. Configure the following.

562

Field/setting

Data specified

Rule nameSend SNMP notifications for PDU (192.168.84.95)
inaccessibility

Event

Choose Server Monitoring > 192.168.84.95 > Unreachable

Trigger condition Select the Unreachable radio button

This will make the PX-Series PDU react only when the target PDU becomes inaccessible.
5. Select the System SNMP Notification Action.

563

In-Line Monitors
PX3-3000 series models are in‑line monitors. An in‑line monitor is implemented with the same numberof inlets and outlets.
•

Inlets are located at the side labeled Line.

•

Outlets are located at the side labeled Load.

An inlet is connected to a power source for receiving electricity, such as electric distribution panels orbranch circuit receptacles. An outlet is connected to a device that draws power, such as a cooling or IT
device.

In This Chapter
Safety Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Flexible Cord Installation Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
In-Line Monitor's Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

Safety Instructions
1. Installation of this product should only be performed by a licensed electrician.
2. Make sure the line cord is disconnected from power before physically mounting or moving thelocation of this product.
3. This product is intended to be located in an equipment rack in an information technology room. In
the United States, installation must comply and be done in accordance with NEC (2011) Article 645
Information Technology Equipment.
4. This product is designed to be used within an electronic equipment rack. The metal case of thisproduct is electrically bonded to the line cord ground wire. A threaded grounding point on the casemay be used as an additional means of protectively grounding this product and the rack.
5. Examine the branch circuit receptacle that will supply electric power to this product. Make sure thereceptacle’s power lines, neutral and protective earth ground pins are wired correctly and are thecorrect voltage and phase. Make sure the branch circuit receptacle is protected by a suitably rated
fuse or circuit breaker.
6. If the product is a model that contains receptacles that can be switched on/off, electric power may
still be present at a receptacle even when it is switched off.

Flexible Cord Installation Instructions
The following instructions are for Raritan products manufactured to accept user-installed flexible cords.
These products are visually identified by the cable gland used to hold the flexible cord.

564

Flexible Cord Selection•

The preferred flexible cable is type SOOW, 600V, 90°C or 105°C. Consult Technical Support before
using a different flexible cable type.

•The rated ampacity of the flexible cord must be greater than or equal to the the product’s rated
ampacity marked on its nameplate. In the United States, relevant ampacity ratings for flexible cords
can be found in NEC(2011) section 400.5.

•

The number of wires in the flexible cord must match the number of terminals (including the groundterminal) inside the product. There are exceptions for 3-Phase In-Line Monitors.

•

If a plug is to be attached to the flexible cord, the length of the flexible cord must not exceed 4.5
meters - as specified in UL 60950-1 (2007) and NEC 645.5 (2011).

•

The flexible cord may be permanently connected to power subject to local regulatory agency
approval. In the United States, relevant electrical regulations can be found in NEC (2011) sections
400.7(A)(8), 400.7(B), 368.56 and table 400.4.

Plug Selection
If a plug is to be attached to the flexible cord, the plug’s rated ampacity is chosen as follows:•

In the United States, as specified in UL 60950‑1, the plug’s rated ampacity must be 125% greaterthan the Raritan product’s rated ampacity. In some Raritan products, such as 35A 3-phase delta
wired PDUs, an exactly 125% rated plug is not available. In these cases, choose the closest plug thatis more than 125%. For example, a 50A plug is the closest fit for a 35A 3-phase PDU.

•

For all other locations, subject to local regulatory agency policy, the plug’s rated ampacity is thesame as the Raritan products rated ampacity.

Receptacle Selection
For Raritan in-line monitors, any receptacle fitted to the outlet flexible cord must have identical ratings
as the plug attached to the inlet flexible cord.

565

Derating a Raritan Product
Lower rated plugs, receptacles and flexible cords may be connected to a Raritan product. This results ina derated (reduced) ampacity rating for the product.

▶ Derating guidelines:
1. Choose the plug and use its rated ampacity to determine the derated ampacity.
• In the United States, as specified in UL 60950‑1, the derated ampacity is 80% of the plug’s rated
ampacity. For example, a 30A plug would result in a derated ampacity of 24A.
• In other geographic locations, subject to local regulatory agency approval, the derated ampacity is
the plug’s rated ampacity. For example, using a 16A plug would result in a derated ampacity of 16A.
2. The derated ampacity must be marked on the Raritan product so the new reduced rating can beeasily identified.
3. For in-line monitors, the receptacles used must have the same voltage and ampacity rating as theplug chosen in step 1.
4. The flexible cord must have a rated ampacity greater than or equal to the derated ampacity. Since
the new flexible cord may be smaller diameter, a check must be performed to insure the cable glandnut, when tightened, will securely hold the flexible cord so that it cannot be twisted, pulled or
pushed in the cable gland. A sealing ring, for small diameter flexible cords, may have been included
with the Raritan product, or can be sourced from a electrical equipment supplier, to reduce theinside diameter of the cable gland.

Wiring of 3-Phase In-Line Monitors
3-phase in-line monitors contain 4-pole wiring terminal blocks (L1, L2, L3, N) to monitor 5-wire (4P+PE)
3-phase wye connections. Delta wired 4-wire (3P+PE) 3-phase connections are also permitted (no wire
connected to the terminal block neutral "N"). No additional hardware or firmware configuration isrequired to specify whether the connection is 5-wire wye or 4-wire delta.

In-Line Monitor Unused Channels
It is not necessary to wire up all channels of multi-channel in-line monitors. The inlet and outlet
openings of unused channels must be completely closed off. "Goof plugs" for this purpose may be agood choice if they are available in your country or region.

Installing the Flexible Cord
This flexible cord installation procedure can be followed for either support rack PDUs or in-line
monitors.

566

The following items are required to complete the installation:•

Flexible cord(s).

•Insulated ring terminals (one for each wire) and appropriate crimp tool.

•

Plug(s) and receptacle(s) (for in-line monitors)•

Torque screwdriver, torque nut driver and torque wrench to tighten the wiring terminal blockscrews, ground nut and cable gland nut.

▶ To install a flexible cord:
1. Open the PDU's access panel (or in-line monitor top panel) to expose the power wiring terminal
block(s).
One-channel in-line monitor

Zero U PDU

567

Make sure to locate the ground wire mounting stud(s). There is a separate ground wire
mounting stud for each terminal block. Each flexible cord MUST have its green (or green/
yellow) ground wire bonded to a ground wire mounting stud.

For in-line monitors, make sure to identify the inlet terminal blocks (rear of monitor) and outlet
terminal blocks (front of monitor). Each inlet terminal block has a corresponding outlet terminal
block.

NumberDescription
Inlets (labeled LINE)
Outlets (labeled LOAD)

2. Strip off the outer jacket of the flexible cord and remove any jute, paper or other fillers. Use thefollowing to help determine how much jacket to remove:• In the finished assembly, the outer jacket should protrude inside the Raritan product.
• The wires will have ring terminals crimped onto them.
• In the finished assembly, the wires should have some slack and not be taught.
• In the finished assembly, if the flexible cord slips in the cable gland placing a strain on the cord’s
wires, the ground wire must be the last wire to take the strain.
3. Crimp an insulated ring terminal onto each wire. A non-insulated ring terminal may be used for the
ground wire. Inspect each crimp to insure it is secure and verify no exposed wire protrudes from therear of an insulated ring terminal.
4. Loosen the cable gland nut and push the flexible cord assembly through the gland.

568

Temporarily hand tighten the gland nut and verify the cord cannot be twisted or pushed orpulled in the gland. Do not proceed if hand tightening results in a loose cord. In some models,
especially in-line monitors, the flexible cord’s diameter may be too small for the cable gland. A
sealing ring for smaller diameter line cords may have been included with the Raritan product, or
can be requested from Raritan, to reduce the inside diameter of the cable gland.

5. Fasten the ring terminal of the green (or green/yellow) ground wire to the chassis’s threaded groundstud in this order:
a. Place the lock washer on the stud.
b. Place the ground wire ring terminal on the stud.
c. Place the nut on the stud and tighten with a torque wrench. The appropriate torque settings
vary according to the nut size.
Nut size

Torque setting (N·m)

Tolerance

M3

0.49

10%

M4

1.27

8%

M5

1.96

5%

M6

2.94

3.5%

M8

4.9

2%

d. Check the ground wire connection. It should be secure and not move or rotate.

569

6. Fasten the ring terminals of all remaining wires to the terminal block and tighten each using atorque screwdriver. The appropriate torque settings vary according to the screw size.
Screw size

Torque setting (N·m)

Tolerance

M3

0.49

10%

M4

1.27

8%

M5

1.96

5%

M6

2.94

3.5%

M8

4.9

2%

Make sure each ring terminal is firmly fastened and cannot be twisted by hand. Use thefollowing guidelines to help terminal block wiring.
• In single-phase Raritan products with world-wide ratings, the terminals are labeled L1 and L2. L1 isthe phase wire. L2 is either the neutral (120/230V installations) or another phase wire (208V
installations).

570

• In all 3-phase products, L1 is phase A, L2 is phase B, L3 is phase C and N is neutral.
• If your PDU is inlet metered, such as PDU models PX2-1nnn and PX2-2nnn (where n is a number),you must pass each line cord wire through the correct CT in the correct direction. Each CT is labeled
and contains a direction arrow. Push the ring terminal end of the line cord through the CT in the
direction indicated by the arrow. For example, push the L1 line cord wire through the CT labeled L1
and then connect it to the L1 terminal block.

• For Raritan in-line monitors, where there is a one to one correspondence between plug andreceptacle, maintain the same wire colors for inlet and outlet flexible cords.
7. Make final adjustments to the cable gland and verify the jacket of the flexible cord extends into the
Raritan product. Hand tighten the gland nut and finish tightening with a torque wrench. Appropriate
torque settings vary according to the cable gland size.
Cable gland size

Torque setting (N·m)

M12x1.5

0.7 to 0.9

M16x1.5

2.0 to 3.0

M20x1.5

2.7 to 4.0

M25x1.5

5.0 to 7.5

M32x1.5

7.5 to 10.0

M40x1.5

7.5 to 10.0

M50x1.5

7.5 to 10.0

M63x1.5

7.5 to 10.0571

Note: The cable gland size is marked on the cable gland body.
After tightening, examine the flexible cord and cable gland for the following:• Make sure you can see a few remaining threads between the cable gland body and cable gland nut.
The gland nut must not bottom out on the gland body.
• Make sure the flexible cord does not move in the cable gland when it is twisted, pushed or pulled.
8. Re-install the PDU wiring access panel or in-line monitor cover plate. This completes internal wiringof the Raritan product.
9. For in-line monitors, fasten the receptacles to the outlet flexible cords following the manufacturer’s
instructions.
10. Complete the wiring of the inlet flexible cord by performing one of these steps:• Assemble the plug following the manufacturer’s instructions.
• Permanently attach and strain relief the flexible cord to a junction box following applicable
electrical codes.

In-Line Monitor's Web Interface
An in‑line monitor's web interface is similar to a regular PX3 model's web interface.

Dashboard Page
An in‑line monitor's Dashboard page looks slightly different than a typical PX-Series PDU device's
Dashboard page, and will vary depending on the model of inline-monitor.

572

Number Section
Outlet(s)Content•

Overview of each outlet's power data -- in the above diagram, there are 4 outlets.

•

A current bar per outlet, which changes colors to indicate the RMS current state -normal (green), warning (yellow) or critical (red).
This is similar to Dashboard - Inlet I1.

AlertedSensors•

When no sensors enter the alarmed state, this section shows the message "No Alerted
Sensors."•

When any sensor enters the alarmed state, this section lists all of them.
See Dashboard - Alerted Sensors.

OutletHistory

The historical chart of the first outlet's active power is displayed by default.
You can make the diagram show another outlet's or multiple outlets' active power
history or select a different data type. See instructions below.

573

Number Section

Content

AlarmsThis section can show data only after you have set event rules requiring users totake the acknowledgment action.
•

When there are no unacknowledged events, this section shows the message "No
Alarms."•When there are unacknowledged events, this section lists all of them.
See Dashboard - Alarms.

▶ To go to each outlet's setup page:
1. Locate the desired outlet section.
2. Click its title, such as Inlet/Outlet 1, Inlet/Outlet 2, and the like. The selected outlet's page opens.

▶ To view the inlet power chart:
1. To view the power chart of one or multiple outlets, select one or multiple outlet checkboxes below
the diagram.

574

• When multiple outlets are displayed in the chart, their data lines' colors differ. You can identify
their lines according to the colors of the selected outlet checkboxes as illustrated below.

2. To view a different data type, click the selector

at the bottom.

• Available data types include RMS current, RMS voltage, active power and apparent power.

575

• To retrieve the exact data at a particular time, hover your mouse over the data line in the chart.
Both the time and data are displayed as illustrated below.

• When the data of multiple outlets is shown in the chart, simply hover your mouse over any outlet's
data line. Values of all outlets display simultaneously, marked with corresponding colors.

576

Inlets/Outlets Page
On the Inlets/Outlets page, you can:•View each outlet's power data (which is also each inlet's power data)•

Configure each inlet/outlet as needed, such as customizing outlet names, setting thresholds orresetting energy.

Outlet thresholds, when enabled, help you identify whether the outlet enters the warning or criticallevel. In addition, you can have PX3 automatically generate alert notifications for any warning or criticalstatus. See Event Rules and Actions.
Number of available outlet sensors are model dependent.

▶ Operation:
1. Click Inlets/Outlets to open the Inlet(s)/Outlet(s) page.

577

2. A list of inlets/outlets is displayed. Click "Show Details" of the desired inlet/outlet.

578

3. The individual inlet/outlet page opens.
On this page, you can:• View details, such as its receptacle type
• View all of its sensors data
• Reset its active energy• View its power chart• Configure its power thresholds

579

Appendices
In This Chapter
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Equipment Setup Worksheet Sample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Special Configuration and Upgrade Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Cascading Solutions for Xerus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Resetting to Factory Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Models with Residual Current Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Remote Authentication Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Updating the LDAP Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Additional Xerus Information - Assorted Products. . . . . . . . . . . . . . . . . . . . . . . . . 725
Xerus Product Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Third Party Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748

580

Specifications

In This Chapter
PX3-Series PDU and Transfer Switch Specifications. . . . . . . . . . . . . . . . . . . . . . . . 581
PX2-Series Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
PXE Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
PXC/PXO Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

PX3-Series PDU and Transfer Switch Specifications▶ Max Ambient Operating Temperature:•

60 degrees Celsius

581▶ Serial Port Pinouts
RJ-45 Pin/signal definition
Pin No.

SignalDirection

Description

1

RTS

OutputRequest to send

2

DTR

OutputData terminal ready3

TxD

OutputTransmit data

4

GND

―

Signal ground

5

DCD

Input

Data carrier detect

6

RxD

Input

Receive data (data in)

7

DSR

Input

Data set ready

8

CTS

Input

Clear to send

▶ Sensor Port Pinouts
RJ-45 Pin/signal definition
Pin No. Signal

Direction

Description

1

+12V

―

Power (fuse protected)

2

+12V

―

Power (fuse protected)

3

GND

―

Signal Ground4

RS485_DP bi-directional Data Positive of the RS‑485 bus

5RS485_DN bi-directional Data Negative of the RS‑485 bus

6

GND

―

Signal Ground7

1‑wire―1-wire signal for Legrandenvironmental sensor packages

8

GND

―

Signal Ground

Note: A maximum of 500mA power is permitted for both pin 1 and pin 2 altogether.

582

▶ Feature Port Pinouts
RJ-45 Pin/signal definition
Pin No. Signal Direction Description
1

DTR

OutputReserved

2

GND

―

Signal Ground

3

+5V

―

Power for CIM(200mA, fuse protected)

Warning: Pin 3 is only intended for use with
Raritan devices.
4

TxD

OutputTransmit Data (Data out)

5

RxD

Input

Receive Data (Data in)

6+12V ―

Warning: Pin 6 is only intended for use with
Raritan devices. Do NOT connect.
7

GND

―

Signal Ground

8

DCD

Input

Reserved▶ Expansion Port Pinouts
RJ-45 Pin/signal definition
Pin No.

SignalDirection

Description

1

+12V

―

Power (fuse protected)

2

+12V

―

Power (fuse protected)

3

GND

―

Signal Ground4

RS485_DPbi-directional

Data Positive of the RS‑485 bus

5RS485_DN

bi-directional

Data Negative of the RS‑485 bus

6

GND

―

Signal Ground

7

NC

―

No Connection

583

RJ-45 Pin/signal definition
8

GND

―

Signal Ground

PX2-Series Specifications▶ Max Ambient Operating Temperature•

50-60 degrees Celsius

The maximum ambient operating temperature (TMA) for PX-Series PDU varies from 50 to 60 degrees
Celsius, depending on the model and certification standard (CE or UL). Check the label on your model.

▶ Serial Port Pinouts
RS-232 "DB9" Pin/signal definition

584

Pin No.

SignalDirection

Description

1

DCD

Input

Data

2

RxD

Input

Receive data (data in)

3

TxD

OutputTransmit data

4

DTR

OutputData terminal ready

5

GND

―

Signal ground

6

DSR

Input

Data set ready

7

RTS

OutputRequest to send

8

CTS

Input

Clear to send

9

RI

Input

Ring indicator▶ Sensor Port Pinouts:
RJ-12 Pin/signal definition
Pin No. Signal Direction Description
1

+12V

―

Power
(500mA, fuse protected)

2

GND

―

Signal Ground

3

―

―

―

4

―

―

―

5

GND

―

Signal Ground6

1-wire1-wire signal for external environmental
sensor packages▶ Feature Port Pinouts:
RJ-45 Pin/signal definition
Pin No. Signal Direction Description
1

DTR

OutputReserved

2

GND

―

Signal Ground

3

+5V

―

Power for CIM(200mA, fuse protected)

Warning: Pin 3 is only intended for use with
Raritan devices.
4

TxD

OutputTransmit Data (Data out)

5

RxD

Input

Receive Data (Data in)

6

N/C

N/C

No Connection

7

GND

―

Signal Ground

8

DCD

Input

Reserved

585

PXE Specifications▶ Max Ambient Operating Temperature:•586

60 degrees Celsius

▶ Sensor Port Pinouts
RJ-12 Pin/signal definition
Pin No. Signal Direction Description
1

+12V

―

Power
(500mA, fuse protected)

2

GND

―

Signal Ground

3

―

―

―

4

―

―

―

5

GND

―

Signal Ground6

1-wire1-wire signal for external environmental
sensor packages▶ RS-485 Port Pinouts
RS-485 Pin/signal definition
Pin No.

SignalDirection

Description

1

―

―

―

2

―

―

―

3

D+

bi-directional

Data +

4

―

―

―

5

―

―

―

6

D-

bi-directional

Data -

7

―

―

―

8

―

―

―

PXC/PXO Specifications▶ Max Ambient Operating Temperature:•

60 degrees Celsius

587▶ Serial Port Pinouts:
RJ-45 Pin/signal definition
Pin No.

SignalDirection

Description

1

N/A

―

No signal

2

N/A

―

No signal

3

TxD

OutputTransmit data

4

GND

―

Signal ground

5

N/A

―

No signal

6

RxD

Input

Receive data (data in)

7

N/A

―

No signal

8

N/A

―

No signal▶ Sensor Port Pinouts:
RJ-45 Pin/signal definition
Pin No. Signal

Direction

Description

1

+12V

―

Power (fuse protected)

2

+12V

―

Power (fuse protected)

3

GND

―

Signal Ground4

RS485_DP bi-directional Data Positive of the RS‑485 bus

5RS485_DN bi-directional Data Negative of the RS‑485 bus

6

GND

―

Signal Ground7

1‑wire―1-wire signal for Raritan
environmental sensor packages

8

GND

―

Signal Ground

Note: A maximum of 500mA power is permitted for both pin 1 and pin 2 altogether.

588

Equipment Setup Worksheet Sample

589

▶ PX-Series PDU Model ___________________________▶ PX-Series PDU Serial Number ___________________________

590

OUTLET 1

OUTLET 2

OUTLET 3

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 4

OUTLET 5

OUTLET 6

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 7

OUTLET 8

OUTLET 9

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 10

OUTLET 11

OUTLET 12

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 13

OUTLET 14

OUTLET 15

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 16

OUTLET 17

OUTLET 18

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 19

OUTLET 20

OUTLET 21

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 22

OUTLET 23

OUTLET 24

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

▶ Types of adapters_________________________________________________________

591

▶ Types of cables_________________________________________________________▶ Name of software program_________________________________________________________

592

Special Configuration and Upgrade Methods

In This Chapter
Configuration or Firmware Upgrade with a USB Drive. . . . . . . . . . . . . . . . . . . . . . 593
Bulk Configuration or Firmware Upgrade via DHCP (TFTP/HTTPS). . . . . . . . . . . . 605
Raw Configuration Upload and Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Bulk Configuration, Firmware Upgrade, or Backup/Restore via SCP. . . . . . . . . . . 627

Configuration or Firmware Upgrade with a USB Drive
You can accomplish the following tasks simultaneously by plugging a USB flash drive which contains
special configuration files into the device.
•

Configuration changes•

Firmware upgrade•

Diagnostic data download

Device Configuration/Upgrade ProcedureFirmware downgrade is NOT supported by default. Contact Technical Support.
You can use one USB drive to configure or upgrade multiple devices one by one as long as it contains
valid configuration files.

▶ To use a USB drive to configure or upgrade firmware:
1. Check requirements. System and USB Requirements (on page 594).
2. Prepare required configuration files. See Configuration Files (on page 594).
3. Copy required configuration files to the root directory of the USB drive.
• For firmware upgrade, an appropriate firmware binary file is also required.
4. Plug the USB drive into the USB‑A port of the device.
5. The initial message shown on the front panel display depends on the first task performed.
• If the USB contains a firmware upgrade, that task happens first. The front panel display shows an
upgrade message. When the firmware upgrade completes successfully, then a happy smileyappears.
• If no firmware upgrade task will be performed, a happy smiley is displayed after around 30
seconds.

593

6. If nothing is shown on the display and no task is performed after plugging the USB drive, check thelog file in the USB drive.
7. After the happy smiley appears, press one of the control buttons next to the display for one second
until the smiley disappears. Wait for several seconds until the device resumes normal operation,
indicated by the normal message of the display.
Tip: Once the happy smiley displays, you can safely remove the USB drive and move it to the next device
you are working on.

System and USB Requirements
You must satisfy ALL of the following requirements prior to using a USB flash drive to perform device
configuration and/or firmware upgrade.

▶ System requirements:•

There is at least one USB‑A port available on your Xerus device.

•Your Xerus device must run firmware version 2.2.13 or later.

▶ USB drive requirements:•

The drive contains either a single partition formatted as a Windows FAT32 filesystem, or NO
partition tables (that is, a superfloppy-formatted drive).

Configuration Files
There are three types of configuration files. To generate these files, use the Mass Deployment Utility.
See Creating Configuration Files via Mass Deployment Utility (on page 602).
•

fwupdate.cfg:•

This file MUST always be present for performing configuration or firmware upgrade tasks.
See fwupdate.cfg (on page 594).
config.txt:•

This file is used for configuring device settings. See config.txt (on page 598).
devices.csv:
This file is required only when there are device-specific settings to configure for multiple
devices. See devices.csv (on page 600).

fwupdate.cfg
The configuration file, fwupdate.cfg, is an ASCII text file containing key-value pairs, one per line.

594

Each value in the file must be separated by an equal sign (=), without any surrounding spaces. Keys are
not case sensitive.
Illustration:user=admin
password=admn
set_password=newpassword
logfile=log.txt
config=config.txt
device_list=devices.csv

This section explains common options in the file.

▶ user•A required option.

•

Specify the name of a user account with Administrator Privileges.

▶ password•

A required option.

•

Specify the password of the specified admin user.

Tip: You can add multiple user credentials to fwupdate.cfg. Each 'user' line must be
immediately followed by its 'password' line. Each user will be authenticated until
one of them succeeds, or until all user credentials fail.

▶ set_password•

You are required to change the default password for all units. Access to units with factory default
password settings will be denied unless this option is used.

•

Changes the password of the given user before executing any commands.

▶ logfile•Specify the name of a text file where the where log messages will be saved when interpreting theUSB drive contents.

•

If the specified file does not exist in the USB drive, it will be automatically created.

•

If this option is not set, no log messages are recorded, and there will be no feedback if there is aproblem with the USB drive contents.

595

▶ firmware•

Specify the name of a firmware file.

•

The specified firmware file must be compatible with your device.

•

The default is to NOT permit any firmware downgrade . To do this, the parameter"allow_downgrade" must be present and properly set in the fwupdate.cfg file.

▶ config•

Specify the name of the configuration file containing device settings.

•

The default filename is config.txt.

▶ device_list•

Specify the name of the configuration file listing all devices to configure and their device-specificsettings.

•

This file is required if any macros are used in the device configuration file "config.txt."•

The default filename is devices.csv.

▶ match•Specify a match condition for identifying a device in the device configuration file "devices.csv."
The option's value comprises one word and one number as explained below:• The word prior to the colon is an identification property, which is either serial for serial
number or mac for MAC address.
• The number following the colon indicates a column in the devices.csv file.
For example, mac:7 will search for the MAC address in the 7th column of the"devices.csv" file.

•

The default value is serial:1, to search for its serial number in the first column.

•

This option is used only if the "device_list" option has been set.

▶ factory_reset•

If this option is set to true, the device will be reset to factory defaults.

•

If the device configuration will be updated at the same time, the factory reset will be executed
before updating the device configuration.

▶ bulk_config_restore•

596

Specify the name of the bulk configuration file used to configure or restore.

Note: See Bulk Configuration or Firmware Upgrade via DHCP (TFTP/HTTPS) (on page 605) for
instructions on generating a bulk configuration file.
•

Additional configuration keys set via the config.txt file will be applied after performing the bulk
restore operation.

•

This option CANNOT be used with the option "full_config_restore."•

If a firmware upgrade will be performed at the same time, you must generate the bulk configuration
file based on the NEW firmware version instead of the current firmware version.

▶ full_config_restore•

Specify the name of the full configuration backup file used to restore the device.

•

Additional configuration keys set via the config.txt file will be applied after performing theconfiguration restore operation.

•

This option CANNOT be used with the option "bulk_config_restore."•

If a firmware upgrade will be performed at the same time, you must generate the full configuration
backup file based on the NEW firmware version instead of the current firmware version.

▶ collect_diag•

If this option is set to true, the diagnostic data is transmitted to the USB drive.

•

The filename of the diagnostic data written into the USB drive is:•diag_<unit‑serial>.zip
The device beeps after it finishes writing the diagnostic data to the USB drive.

▶ switch_outlets•

This feature works on outlet-switching capable models only.

•

Switch on or off specific outlets.

•

The option's value comprises outlet numbers and the setting "on" or "off" as explained below:• Each "on" or "off" setting consists of three parts: outlet numbers, a colon, and the word "on" or"off".
• Each "on" or "off" setting is separated with a semicolon.
• If all outlets will share the same "on" or "off" setting, replace the outlet numbers with the word"all".

•

Examples:• Turn on outlets 1 to 3, and 10, and turn off outlets 4 to 9.
switch_outlets=1,2,3:on;4-9:off;10:on• Turn on all outlets.

597

switch_outlets=all:on▶ tls_cert_file•

Specify the filename of the wanted TLS server certificate. The filename can contain a single
placeholder ${SERIAL} that is replaced with the serial number of the device.

•

This option should be used with tls_key_file listed below.

•

This option is NOT supported by bulk configuration or backup/restore via DHCP/TFTP.

▶ tls_key_file•

Specify the filename of the wanted TLS server key. The filename can contain a single placeholder ${SERIAL} that is replaced with the serial number of the device.

•

This option should be used with tls_cert_file listed above.

•

This option is NOT supported by bulk configuration or backup/restore via DHCP/TFTP.

▶ execute_lua_script•

Specify a Lua script file. For example:
execute_lua_script=my_script.lua•

Script output will be recorded to a log file -- <BASENAME_OF_SCRIPT>.<SERIAL_NUMBER>.log. Note
this log file's size is limited on DHCP/TFTP.

•A DHCP/TFTP-located script has a timeout of 60 seconds. After that duration the script will be
removed.

•This feature can be used to manage LuaService, such as upload, start, get output, and so on.

•

If you unplug the USB drive while the Lua script is still running, the script will be removed.

•

An exit handler can be used but the execution time is limited to three seconds. Note that this is not
implemented on DHCP/TFTP yet.

config.txt
To perform device configuration using a USB drive, you must:•

Copy the device configuration file "config.txt" to the root directory of the USB drive.

•

Reference the "config.txt" file in the config option of the "fwupdate.cfg" file.

The file, config.txt, is a text file containing a number of configuration keys and values to configure or
update.
This section only introduces the device configuration file in brief, and does not document all
configuration keys, which vary according to the firmware version and your model.
You can use the Mass Deployment Utility to create this file by yourself, or contact Technical Support toget a device configuration file specific to your model and firmware version.
Tip: You can choose to encrypt important data in the "config.txt" file so that people cannot easily
recognize it, such as the SNMP write community string. See Data Encryption in 'config.txt' (on page603) .

598

If you are using a password as auth/priv passphrases, you must set the password in the config file toensure it generates the SNMPv3 hash.

▶ Regular configuration key syntax:•

Each configuration key and value pair is in a single line as shown below:
key=value
Note: Each value in the file must be separated by an equal sign (=), without any surrounding spaces.

•

Multi-line values are supported by using the Here Document Syntax with a user-chosen delimiter.
The following illustration declares a value in two lines. You can replace the delimiter EOF
with other delimiter strings.
key<<EOF
value line 1
value line 2
EOF
Note: The line break before the closing EOF is not part of the value. If a line break is required in thevalue, insert an additional empty line before the closing EOF.

▶ Special configuration keys:
There are 3 special configuration keys that are prefixed with magic:.
•

A special key that sets a user account's password without knowing the firmware's internal
encryption/hashing algorithms is implemented.
Example:magic:users[1].cleartext_password=joshua•

Two special keys that set the SNMPv3 passphrases without knowing the firmware's internal
encryption/hashing algorithms are implemented.
Examples:magic:users[1].snmp_v3.auth_phrase=swordfish
magic:users[1].snmp_v3.priv_phrase=opensesame▶ To configure device‑specific settings:
1. Make sure the device list configuration file "devices.csv" is available in the USB drive.
2. In the "config.txt" file, refer each device-specific configuration key to a specific column in the"devices.csv" file. The syntax is: ${column}, where "column" is a column number.
Examples:net.interfaces[eth0].ipv4.static.addr_cidr.addr=${4}599

pdu.name=${16}▶ To rename the admin user:
You can rename the admin user by adding the following configuration key:users[0].name=new admin nameExample:users[0].name=May▶ To restore a specific setting to factory default:
Add "delete:" to the beginning of the key whose setting you want to remove. The custom setting will be
removed and then reset to factory default.
Example:delete:net.port_forwarding

devices.csv
If there are device-specific settings to configure, you must create a device list configuration file devices.csv, to store unique data of each device.
This file must be:•

A CSV (comma-separated values) format file exported from a spreadsheet application like Excel.

•

Copied to the root directory of USB drive.

•

Referenced in the device_list option of the "fwupdate.cfg" file. See fwupdate.cfg (on page 594).

Every device identifies its entry in the "devices.csv" file by comparing its serial number or MAC address
to one of the columns in the file.

▶ Determine the column to identify devices:•

By default, each device searches for its serial number in the 1st column of "devices.csv".

•

To override the default, set the match option in the "fwupdate.cfg" file to a different column.

▶ Syntax:•

Values containing commas, line breaks or double quotes are all supported.

•

The commas and line breaks to be included in the values must be enclosed in double quotes.

•

Every double quote to be included in the value must be escaped with another double quote.
For example:
Value‑1,"Value‑2,with,three,commas",Value‑3
Value‑1,"Value‑2,""with""three""double‑quotes",Value‑3
Value‑1,"Value‑2600

with a line break", Value‑3

Configuration Files for Linking
When Linking is enabled, the mass deployment tool will create the usual files, and multiple versions ofconfig.txt:•

config_link_unit.txt containing the configuration for all link units•

config_<serial>.txt for each primary unit containing its specific settings, including a list of link units.

▶ Commands for device Linking:
The following commands are used in the fwupdate.cfg file to configure Linking.

▶ add_link_unit
Add a new link unit. The option can be specified more than once to add multiple link units.
add_link_unit=<id>,<host>,<login>:<password>•

Parameters are: <id>: new link unit id (2..8), <host>: hostname or IP address, <login>:<password>:
credentials for admin user

▶ add_link_unit_new_password:
Change the password when adding a new link unit. Required in case the link unit still uses the factory
default password.
add_link_unit_new_password=<id>,<new_password>▶ add_cascade_link_units
Add port-forwarding expansion units as link units. The option can be specified more than once to link
multiple port-forwarding nodes with different parameters.
add_cascade_link_units=<link ids>:<nodes>:<position
dependent>:<login>:<password>
Parameters are:<link ids>: comma-separated list of new link unit ids (2..8)<nodes>: comma-separated list of port-forwarding node indices (1..31, needs to be same length as <linkids>), or the special word "all", which will link all port-forwarding nodes until an error occurs.
<position dependent>: "true" or "false": if true, use position-dependent host-names (i.e. expansion<n>.pf-cascade) or, if false, use link-local IPv6 addresses.

601

<login>:<password>: credentials for admin user on the port-forwarding node•

Example: add_cascade_link_units=2,3:1,2:false:admin:<password>

Creating Configuration Files via Mass Deployment Utility
The Mass Deployment Utility is an Excel file that lets you fill in basic information required for the three
configuration files, such as the admin account and password.
After entering required information, you can generate all configuration files with only one click,including fwupdate.cfg, config.txt and devices.csv.
Note: The firmware version of your device must match the version of the Mass Deployment Utility
spreadsheet. Do not mix versions.
New commands that have been introduced in later versions of the spreadsheet will not be effective on
devices with older firmware.

▶ To use the Mass Deployment Utility:
1. Download the Mass Deployment Utility from the support page.
• The utility is named mass_deployment-xxx (where xxx is the firmware version number).
2. Launch Excel to open this utility.
Note: Other programs, such as OpenOffice and LibreOffice, are not supported.
3. Read the instructions in the 1st worksheet of the utility, and make sure Microsoft Excel's security
level has been set to Medium or the equivalent for executing unsigned macros of this utility.
4. Enter information in the 2nd and 3rd worksheets.
• The 2nd worksheet contains information required for fwupdate.cfg and config.txt.
• The 3rd worksheet contains device-specific information for devices.csv.
5. Return to the 2nd worksheet to execute the export macro.
a. In the Target Directory field, specify the folder where to generate the configuration files. For
example, you can specify the root directory of a connected USB drive.
b. Click Export Lists to generate configuration files.

602

Verify that at least 3 configuration files are created - fwupdate.cfg, config.txt and devices.csv. You areready to configure or upgrade with these files.

Data Encryption in 'config.txt'
When intending to prevent people from identifying the values of any settings, you can encrypt them.
Encrypted data still can be properly interpreted and performed by any device running Xerus firmware
version 3.2.20 or later.

▶ Data encryption procedure:
1. Open the "config.txt" file to determine which setting(s) to encrypt.
• If an appropriate "config.txt" is not created yet, see Creating Configuration Files via Mass
Deployment Utility (on page 602).
2. Launch a terminal to log in to the CLI of the device.
3. Type the encryption command and the value of the setting you want to encrypt.
• The value cannot contain any double quotes (") or backslashes (\).
• If the value contains spaces, it must be enclosed in double quotes.
# config encrypt <value>-- OR -# config encrypt "<value with spaces>"

4. Press Enter. The CLI generates and displays the encrypted form of the typed value.
5. Go to the "config.txt" file and replace the chosen value with the encrypted one by typing or copying
the encrypted value from the CLI.
6. Add the text "encrypted:" to the beginning of the encrypted setting.
7. Repeat steps for additional settings you intend to encrypt.
8. Save the changes made to the "config.txt" file. Now you can use this file to configure other devices.

▶ Illustration:
In this example, we will encrypt the word "private", which is the value of the SNMP write community inthe "config.txt" file.

603

1. In the CLI, type the following command to encrypt "private."

2. The CLI generates and shows the encrypted form of "private."

3. In the "config.txt" file, make the following changes to the SNMP write community setting.
a. Replace the word "private" with the encrypted value that CLI shows.

b. Add "encrypted:" to the beginning of that setting.

Firmware Upgrade via USB
Firmware files are available on the product support page.
Note that if the firmware file used for firmware upgrade is the same as the firmware version running on
the PX-Series PDU, no firmware upgrade will be performed unless you have set the force_update option
to true in the "fwupdate.cfg" file.

▶ To use a USB drive to upgrade the PX-Series PDU:
1. Copy the configuration file "fwupdate.cfg" and an appropriate firmware file to the root directory of
the USB drive.
2. Reference the firmware file in the firmware option of the "fwupdate.cfg" file.
3. Plug the USB drive into the USB‑A port on the PX-Series PDU.
4. The front panel display shows the firmware upgrade progress.

604

Tip: You can remove the USB drive and plug it into another unit for firmware upgrade when the firmware
upgrade message displays.
5. It may take one to five minutes to complete the firmware upgrade, depending on your product.
6. When the firmware upgrade finishes, the front panel display indicates the firmware upgrade result.
• Happy smiley: Successful.

• Sad smiley: Failed. Check the log file in the USB drive or contact Technical Support to look into thefailure cause.

Bulk Configuration or Firmware Upgrade via DHCP (TFTP/HTTPS)
If a TFTP or HTTPS server is available, you can use it and appropriate configuration files to perform anyor all of the following tasks for a large number of devices in the same network.
•

Initial deployment•

Configuration changes•

Firmware upgrade•

Downloading diagnostic data

This feature is useful if you have hundreds or even thousands of devices to configure or upgrade.
Warning: The feature of bulk configuration or firmware upgrade via DHCP (TFTP/HTTPS)only works onstandalone devices directly connected to the network. This feature does NOT work for expansion units
in a cascading configuration.

Bulk Configuration/Upgrade ProcedureFirmware downgrade is NOT supported by default. Contact Technical Support.

605

▶ Steps of using DHCP (TFTP/HTTPS) for bulk configuration/upgrade:
1. Create configuration files specific to your PX-Series PDU models and firmware versions. Create yourown or contact Technical Support to properly prepare some or all of the following files:• fwupdate.cfg (always required)• config.txt• devices.csv
Note: Supported syntax of "fwupdate.cfg" and "config.txt" may vary based on different firmware
versions. If you have existing configuration files, it is suggested to double check with TechnicalSupport for the correctness of these files prior to using this feature.
2. Configure your TFTP or HTTPS server properly.
3. Copy ALL required configuration files into the TFTP or HTTPS root directory. If the tasks you will
perform include firmware upgrade, an appropriate firmware binary file is also required.
4. Properly configure your DHCP server so that it refers to the file "fwupdate.cfg" on the TFTP/HTTPS
server.
5. Make sure all of the desired devices use DHCP as the IP configuration method and have been
directly connected to the network.
6. Reboot these devices. The DHCP server will execute the commands in the "fwupdate.cfg" file on the
TFTP server to configure or upgrade those devices supporting DHCP in the same network.
DHCP will execute the "fwupdate.cfg" commands once for IPv4 and once for IPv6 respectively if
both IPv4 and IPv6 settings are configured properly in DHCP.
Note: If both TFTP and HTTP server options are specified, HTTP takes precedence. For HTTP, both 'http'and 'https' schemes are supported, but when using https, the certificate is not checked.

TFTP/HTTPS Requirements
To perform bulk configuration or firmware upgrade successfully, your TFTP/HTTPS server must meet thefollowing requirements:•

The server is able to work with both IPv4 and IPv6.
In Linux, remove any IPv4 or IPv6 flags from /etc/xinetd.d/tftp.
Note: DHCP will execute the "fwupdate.cfg" commands once for IPv4 and once for IPv6 respectively
if both IPv4 and IPv6 settings are configured properly in DHCP.

•

All required configuration files are available in the TFTP/HTTPS root directory. See Bulk
Configuration/Upgrade Procedure (on page ).

If you are going to upload any PX-Series PDU diagnostic file or create a log file in the TFTP server, thefirst of the following requirements is also required.
Note: The HTTPS server does not support file writes(diag data, log files etc.).

606

▶ TFTP Server:•

The TFTP server supports the write operation, including file creation and upload.

•

In Linux, provide the option "-c" for write support.
Required for uploading the diagnostic file only - the timeout for file upload is set to one minute or
longer.

DHCP IPv4 Configuration in Windows
For those PX-Series PDU devices using IPv4 addresses, follow this procedure to configure your DHCP
server. The following illustration is based on Microsoft® Windows Server 2012 system.

▶ Required Windows IPv4 settings in DHCP:
1. Add a new vendor class for PX-Series PDU under IPv4.
a. Right-click the IPv4 node in DHCP to select Define Vendor Classes.
b. Click Add to add a new vendor class.

c. Specify a unique name for this vendor class and type the binary codes of "Raritan PDU 1.0" in
the New Class dialog.
The vendor class is named "Raritan PDU" in this illustration.

607

2. Define one DHCP standard option - Vendor Class Identifier.
a. Right-click the IPv4 node in DHCP to select Set Predefined Options.
b. Select DHCP Standard Options in the "Option class" field, and Vendor Class Identifier in the"Option name" field. Leave the String field blank.

608

3. Add three options to the new vendor class "Raritan PDU" in the same dialog.
a. Select Raritan PDU in the "Option class" field.

609

b. Click Add to add the first option. Type "pdu-tftp-server" or "pdu-https-server" in the Name field,
select IP Address as the data type, and type 1 in the Code field for tftp server and type 7 in the
Code field for https server.

c. Click Add to add the second option. Type "pdu-update-control-file" in the Name field, selectString as the data type, and type 2 in the Code field.

610

d. Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as thedata type, and type 3 in the Code field.

4. Create a new policy associated with the "Raritan PDU" vendor class.
a. Right-click the Policies node under IPv4 to select New Policy.
b. Specify a policy name, and click Next.
The policy is named "PDU" in this illustration.

611

c. Click Add to add a new condition.
d. Select the vendor class "Raritan PDU" in the Value field, click Add and then Ok.

e. Click Next.
f. Select DHCP Standard Options in the "Vendor class" field, select "060 Vendor Class Identifier"from the Available Options list, and type "Raritan PDU 1.0" in the "String value" field.

612

g. Select the "Raritan PDU" in the "Vendor class" field, select "001 pdu-tftp-server" or "007 pduhttps-server" from the Available Options list, and type your TFTP/https server's IPv4 address in
the "IP address" field.

h. Select "002 pdu-update-control-file" from the Available Options list, and type the filename"fwupdate.cfg" in the "String value" field.

613

i. Select "003 pdu-update-magic" from the Available Options list, and type any string in the "Stringvalue" field. This third option/code is the magic cookie to prevent the fwupdate.cfg commands
from being executed repeatedly. It does NOT matter whether the IPv4 magic cookie is identicalto or different from the IPv6 magic cookie.
The magic cookie is a string comprising numerical and/or alphabetical digits in any
format. In the following illustration diagram, it is a combination of a date and a serial
number.
Important: The magic cookie is transmitted to and stored in PX-Series PDU at the time of
executing the "fwupdate.cfg" commands. The DHCP(TFTP/HTTPS) operation is triggered only
when there is a mismatch between the magic cookie in DHCP and the one stored in PX-Series
PDU. Therefore, you must modify the magic cookie's value in DHCP when intending to executethe "fwupdate.cfg" commands next time.

614

DHCP IPv6 Configuration in Windows
For those PX-Series PDU devices using IPv6 addresses, follow this procedure to configure your DHCP
server. The following illustration is based on Microsoft® Windows Server 2012 system.

▶ Required Windows IPv6 settings in DHCP:
1. Add a new vendor class for Raritan's PX-Series PDU under IPv6.
a. Right-click the IPv6 node in DHCP to select Define Vendor Classes.
b. Click Add to add a new vendor class.

c. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)" field, andtype the binary codes of "Raritan PDU 1.0" in the New Class dialog.
The vendor class is named "Raritan PDU 1.0" in this illustration.

615

2. Add three options to the "Raritan PDU 1.0" vendor class.
a. Right-click the IPv6 node in DHCP to select Set Predefined Options.
b. Select Raritan PDU 1.0 in the "Option class" field.

c. Click Add to add the first option. Type "pdu-tftp-server" or "pdu-https-server" in the Name field,
select IP Address as the data type, and type 1 in the Code field and type 7 in the Code field forhttps server.

616

d. Click Add to add the second option. Type "pdu-update-control-file" in the Name field, selectString as the data type, and type 2 in the Code field.

e. Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as thedata type, and type 3 in the Code field.

617

3. Configure server options associated with the "Raritan PDU 1.0" vendor class.
a. Right-click the Server Options node under IPv6 to select Configure Options.
b. Click the Advanced tab.
c. Select "Raritan PDU 1.0" in the "Vendor class" field, select "00001 pdu-tftp-server" or "00007
pdu-https-server" from the Available Options list, and type your TFTP/HTPPS server's IPv6
address in the "IPv6 address" field.

d. Select "00002 pdu-update-control-file" from the Available Options list, and type the filename"fwupdate.cfg" in the "String value" field.

618

e. Select "00003 pdu-update-magic" from the Available Options list, and type any string in the"String value" field. This third option/code is the magic cookie to prevent the fwupdate.cfg
commands from being executed repeatedly. It does NOT matter whether the IPv6 magic cookie
is identical to or different from the IPv4 magic cookie.
The magic cookie is a string comprising numerical and/or alphabetical digits in any
format. In the following illustration diagram, it is a combination of a date and a serial
number.
Important: The magic cookie is transmitted to and stored in PX-Series PDU at the time of
executing the "fwupdate.cfg" commands. The DHCP(TFTP/HTTPS) operation is triggered only
when there is a mismatch between the magic cookie in DHCP and the one stored in PX-Series
PDU. Therefore, you must modify the magic cookie's value in DHCP when intending to executethe "fwupdate.cfg" commands next time.

619

DHCP IPv4 Configuration in Linux
Modify the "dhcpd.conf" file for IPv4 settings when your DHCP server is running Linux.

▶ Required Linux IPv4 settings in DHCP:
1. Locate and open the "dhcpd.conf" file of the DHCP server.
2. The PX-Series PDU will provide the following value of the vendor‑class‑identifier option (option 60).
• vendor-class-identifier = "Raritan PDU 1.0"
Configure the same option in DHCP accordingly. The PX-Series PDU accepts theconfiguration or firmware upgrade only when this value in DHCP matches.
3. Set the following three sub‑options in the "vendor-encapsulated-options" (option 43).
• code 1 (pdu-tftp-server) = the TFTP server's IPv4 address or• code 7 (pdu-https-server) = the HTTPS server's IPv4 address• code 2 (pdu-update-control-file) = the name of the control file "fwupdate.cfg"• code 3 (pdu-update-magic) = any string
This third option/code is the magic cookie to prevent the fwupdate.cfg commands frombeing executed repeatedly. It does NOT matter whether the IPv4 magic cookie is identicalto or different from the IPv6 magic cookie.
The magic cookie is a string comprising numerical and/or alphabetical digits in any format.
In the following illustration diagram, it is a combination of a date and a serial number.
Important: The magic cookie is transmitted to and stored in PX-Series PDU at the time of executing
the "fwupdate.cfg" commands. The DHCP(TFTP/HTTPS) operation is triggered only when there is amismatch between the magic cookie in DHCP and the one stored in PX-Series PDU. Therefore, youmust modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg"
commands next time.

620

▶ IPv4 illustration example in dhcpd.conf:

DHCP IPv6 Configuration in Linux
Modify the "dhcpd6.conf" file for IPv6 settings when your DHCP server is running Linux.

▶ Required Linux IPv6 settings in DHCP:
1. Locate and open the "dhcpd6.conf" file of the DHCP server.
2. The PX-Series PDU will provide the following values to the "vendor-class" option (option 16).
Configure related settings in DHCP accordingly.
• 13742 (Raritan's IANA number)• Raritan PDU 1.0• 15 (the length of the above string "Raritan PDU 1.0")
3. Set the following three sub‑options in the "vendor-opts" (option 17).
• code 1 (pdu-tftp-server) = the TFTP server's IPv6 address or• code 7 (pdu-https-server) = the HTTPs server's IPv6 address• code 2 (pdu-update-control-file) = the name of the control file "fwupdate.cfg"• code 3 (pdu-update-magic) = any string621

This third option/code is the magic cookie to prevent the fwupdate.cfg commands frombeing executed repeatedly. It does NOT matter whether the IPv6 magic cookie is identicalto or different from the IPv4 magic cookie.
The magic cookie is a string comprising numerical and/or alphabetical digits in any format.
In the following illustration diagram, it is a combination of a date and a serial number.
Important: The magic cookie is transmitted to and stored in PX-Series PDU at the time of executing
the "fwupdate.cfg" commands. The DHCP(TFTP/HTTPS) operation is triggered only when there is amismatch between the magic cookie in DHCP and the one stored in PX-Series PDU. Therefore, youmust modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg"
commands next time.

▶ IPv6 illustration example in dhcpd6.conf:

Raw Configuration Upload and Download
You can modify any existing "config.txt", and then upload it to a specific device for modifying part or allof its settings. Both configuration download and upload operations require the Administrator Privileges.

622

There are two ways to get one "config.txt":•

You create this file by yourself, which can be facilitated using the Mass Deployment Utility. See
Configuration Files (on page 594).

•

You download the raw configuration data from the device.

The downloaded raw configuration contains almost all of current settings on your device.
Warning: When you download the raw configuration data, some configuration keys are commented out
and must remain that way. See Keys that Cannot Be Uploaded (on page 635).

Download via Web Browsers
There are two scenarios by using web browsers.

▶ URL containing login credentials:
To log in immediately while issuing the download request, type an URL containing the login credentials
in the web browser.
http(s)://<user>:<password>@<device IP>/cgi-bin/raw_config_download.cgi
Parameter

Description<user>

Any user name that has the Administrator Privileges.

<password>

The password of the specified user name.

<device IP> Hostname or IP address of the device whose raw configuration
you want to download.

•

For example:

https://admin:admn@192.168.84.114/cgi-bin/raw_config_download.cgi▶ URL without login credentials contained:
If you would like to log in after issuing the download request, type an URL without login credentials
contained in the web browser. The system will then prompt you to enter the login credentials.
http(s)://<device IP>/cgi-bin/raw_config_download.cgi•

For example:

https://192.168.84.114/cgi-bin/raw_config_download.cgi

623

Download via Curl
If you have installed curl on your computer, you can download the raw configuration from your device
by performing the curl command.

▶ To download raw configuration via curl:
1. Type the following curl command in the command line interface.
curl -k https://<user>:<password>@<device IP>/cgi-bin/
raw_config_download.cgi > config.txt
Parameter

Description<user>

Any user name that has the Administrator Privileges.

<password>

The password of the specified user name.

<device IP> Hostname or IP address of the device whose raw configuration
you want to download.

2. When the download is complete, a line indicates 100 in the first % column.

3. Go to the directory where you perform the curl command to find the "config.txt" file.
Tip: In the above curl command, you can replace the filename "config.txt" with any filename you prefer.

▶ Example:
curl -k https://admin:admn@192.168.84.114/cgi-bin/raw_config_download.cgi> config.txt

Uploading Raw Configuration
There are two upload methods:•

SCP or PSCP command: SeeRaw Configuration Upload and Download (on page 622).

•

CURL command: See Upload via Curl (on page 625).

The uploaded raw configuration file can contain only partial configuration keys that you want to modify.
Other settings that are not contained in the uploaded file will remain unchanged.

624

Authentication-related data or HTTP(S) port may be no longer the same after uploading raw
configuration. Therefore, it is suggested to double check what configuration keys will be changed in the
raw configuration file that you will upload.

Upload via CurlIf curl is available on your computer, you can upload the raw configuration to PX-Series PDU with thecurl command.
There are two scenarios with the curl upload methods.
•

When there are NO device-specific settings involved, you upload the configuration file only,
regardless of the number of PX-Series PDU devices to update.

•

When there are device-specific settings involved for updating more than one PX-Series PDU devices,
you must upload two files. including one configuration file and one device list file.

▶ To upload one configuration file only:
1. Type the following curl command in the command line interface.
curl -k -F "config_file=@<config file>" https://<user>:<password>@<device
IP>/cgi-bin/raw_config_update.cgi
Parameter

Description<user>

Any user name that has the Administrator Privileges.

<password>

The password of the specified user name.

<device IP>

Hostname or IP address of the PX-Series PDU whose raw
configuration you want to upload.

<config file> Filename of the configuration file.
•

For the syntax, see config.txt (on page ).

1. When the upload is completed successfully, the curl returns the code 0 (zero).
Note: If the upload fails and curl returns other codes, see Curl Upload Return Codes (on page ).
2. After several seconds, PX-Series PDU reboots automatically. Changed settings take effect after the
reboot process finishes.

▶ To upload both configuration and device list files:
1. Type the following curl command in the command line interface.

625

curl -k -F "config_file=@<config file>" -F "device_list_file=@<dev_list
file>" https://<user>:<password>@<device IP>/cgi-bin/raw_config_update.cgi?
match=<dev_col>Parameter

Description<user>,

Refer to the above table for explanation.

<password>,•<device IP>,<config
file>

For device-specific settings in the <config file>,refer each device-specific configuration key to a specificcolumn in the <dev_list file>. See config.txt (onpage ).

<dev_list
file>

Filename of the device list file in CSV format.

<dev_col><dev_col> comprises "serial:" or "mac:" and the numberof the column where the serial number or MAC address ofeach PX-Series PDU is in the uploaded CSV file. This is thedata based on which each device finds its device-specificsettings.

•

For the content format, see devices.csv (on page ).

For example:•

If the second column contains each device's serial
number, the parameter is then serial:2.

•

If the seventh column contains each device's MAC
address, the parameter is then mac:7.

1. PX-Series PDU will reboot after Curl shows the return code 0. For details, refer to above steps 2 to 3.

▶ Examples:•

Upload of the configuration file only:

curl -k -F "config_file=@config.txt" https://admin:admn@192.168.84.114/
cgi-bin/raw_config_download.cgi•

Upload of both configuration and device list files:

curl -k -F "config_file=@config.txt" -F "device_list_file=@devices.csv"
https://admin:admn@192.168.84.114/cgi-bin/raw_config_download.cgi

Curl Upload Return Codes
After performing raw configuration Upload via Curl (on page ), curl will return a code to indicate theresult of the file upload.

626

Code

Description

0

Operation was successful.

Code

Description

1

An internal error occurred.

2

A parameter error occurred.

3

A raw configuration update operation is already running.

4

The file is too large.

5

Invalid raw configuration file provided.

6

Invalid device list file or match provided.

7

Device list file required but missing.

8

No matching entry in device list found.

9

Macro substitution error.

10

Decrypting value failed.

11

Unknown magic line.

12

Processing magic line failed.

Bulk Configuration, Firmware Upgrade, or Backup/Restore via
SCP
You can perform a SSH File Transfer Protocol (SFTP) or Secure Copy (SCP) command to update thefirmware, do bulk configuration, or back up and restore the configuration.
Note: Because of security issues the SFTP (SSH File Transfer Protocol) should be used. SCP client innewer OpenSSH versions uses SFTP protocol by default. SCP is still supported and needs to be enabled.

Firmware Update via SCP
Same as any firmware update, all user management operations are suspended and all login attempts
fail during the SCP firmware update.
Warning: Do NOT perform the firmware upgrade over a wireless network connection.

▶ To update the firmware via SCP:
1. Type the following SCP command and press Enter.
scp <firmware file> <user name>@<device ip>:/fwupdate627

• <firmware file> is the firmware's filename. If the firmware file is not in the current directory, youmust include the path in the filename.
• <user name> is the "admin" or any user profile with the Firmware Update permission.
• <device ip> is the IP address or hostname where you want to upload the specified file.
2. Type the password when prompted, and press Enter.
3. The system transmits the specified firmware file to the device, and shows the transmission speed
and percentage.
4. When the transmission is complete, it shows the following message, indicating that the PX-Series
PDU starts to update its firmware now. Wait until the upgrade completes.
Starting firmware update. The connection will be closed now.

628▶ SCP example:
scp pdu-px2-030410-44599.bin admin@192.168.87.50:/fwupdate▶ Windows PSCP command:
PSCP in Windows works in a similar way to the SCP.
•

pscp <firmware file> <user name>@<device ip>:/fwupdate

Bulk Configuration via SCP
Like performing bulk configuration via the web interface, there are two steps with the bulk
configuration using the SCP commands:a. Save a configuration from a source device.
b. Copy the configuration file to one or multiple destination device.
Note: You can configure device-specific settings with the upload of raw configuration but not with thebulk configuration file.

▶ To save the configuration via SCP:
1. Type the following SCP command and press Enter.
scp <user name>@<device ip>:/bulk_config.txt <filename>• <user name> is any user profile with Administrator Privileges.
• <device ip> is the IP address or hostname of the device whose configuration you want to save.
• <filename> is the custom filename you assign to the "bulk_config.txt" of the source device.
2. Type the user password when prompted.
3. The system saves the configuration to a file named "bulk_config.txt."▶ To copy the configuration via SCP:
1. Type the following SCP command and press Enter.
scp bulk_config.txt <user name>@<device ip>:/bulk_restore• <user name> any user profile with Administrator Privileges• <device ip> is the IP address of the device whose configuration you want to copy.
2. Type the user password when prompted.
3. The system copies the configuration included in the file "bulk_config.txt" to another device, anddisplays the following message.
Starting restore operation. The connection will be closed now.

▶ SCP examples:•

Save operation:629

scp admin@192.168.87.50:/bulk_config.txt today_config.txt•

Copy operation:
scp today_config.txt admin@192.168.87.47:/bulk_restore▶ Windows PSCP commands:
PSCP in Windows works in a similar way to the SCP.
•

Save operation:
pscp <user name>@<device ip>:/bulk_config.txt today_config.txt•

Copy operation:
pscp today_config.txt <user name>@<device ip>:/bulk_restore

Backup and Restore via SCP
To back up ALL settings of a PX-Series PDU, including device-specific settings, you should perform the
backup operation instead of the bulk configuration.
You can restore all settings to previous ones after a backup file is available.

▶ To back up the settings via SCP:
1. Type the following SCP command and press Enter.
scp <user name>@<device ip>:/backup_settings.txt• <user name> is the "admin" or any user profile with Administrator Privileges• <device ip> is the IP address or hostname of the PX-Series PDU whose settings you want to back up.
2. Type the user password when prompted.
3. The system saves the settings from the PX-Series PDU to a file named "backup_settings.txt."▶ To restore the settings via SCP:
1. Type the following SCP command and press Enter.
scp backup_settings.txt <user name>@<device ip>:/settings_restore• <user name> is the "admin" or any user profile with Administrator Privileges• <device ip> is the IP address or hostname of the PX-Series PDU whose settings you want to restore.
2. Type the user password when prompted.
3. The system copies the configuration included in the file "backup_settings.txt" to the PX-Series PDU,
and displays the following message.
Starting restore operation. The connection will be closed now.

▶ SCP examples:•

630

Backup operation:

scp admin@192.168.87.50:/backup_settings.txt•

Restoration operation:
scp backup_settings.txt admin@192.168.87.50:/settings_restore▶ Windows PSCP commands:
PSCP in Windows works in a similar way to the SCP.
•

Backup operation:
pscp <user name>@<device ip>:/backup_settings.txt•

Restoration operation:
pscp backup_settings.txt <user name>@<device ip>:/settings_restore

Downloading Diagnostic Data via SCP
You can download the diagnostic data via SCP.

▶ To download the diagnostic data via SCP:
1. Type one of the following SCP commands and press Enter.
• <user name> is the "admin" or any user profile with Administrator Privileges or "Unrestricted View
Privileges" privileges.
• <device ip> is the IP address or hostname of the PX-Series PDU whose data you want to download.
• <port> is the current SSH/SCP port number, or the port number of a specific expansion device in
the Port-Forwarding chain.
• <filename> is the new filename of the downloaded file.
Scenario 1: Use the default SCP port and default filename•

SSH/SCP port is the default (22), and the accessed PX-Series PDU is a standalone device.

•

The diagnostic file's default filename "diag‑data.zip" is wanted. Then add a dot (.) in the end of the SCP
command as shown below.

scp <user name>@<device ip>:/diag-data.zip .

Scenario 2: Specify a different SCP port but use the default filename•

SSH/SCP port is NOT the default (22), or the accessed PX-Series PDU is a Port-Forwarding expansion
device.

•The diagnostic file's default filename "diag‑data.zip" is wanted. Then add a dot in the end of the SCP
command as shown below.

scp -P <port> <user name>@<device ip>:/diag-data.zip .

Scenario 3: Specify a new filename but use the default SCP port•

SSH/SCP port is the default (22), and the accessed PX-Series PDU is a standalone device.

•

Renaming the diagnostic file is wanted.

scp <user name>@<device ip>:/diag-data.zip <filename>631

Scenario 4: Specify a different SCP port and a new filename•

SSH/SCP port is NOT the default (22), or the accessed PX-Series PDU is a Port-Forwarding expansion
device.

•Renaming the diagnostic file is wanted.

scp -P <port> <user name>@<device ip>:/diag-data.zip <filename>

1. Type the password when prompted.
2. The system downloads the specified data from the PX-Series PDU onto your computer.
• If you do NOT specify a new filename in the command, such as Scenarios 1 or 2, the downloaded
file's default name is "diag-data.zip."• If you specify a new filename in the command, such as Scenarios 3 or 4, the downloaded file isrenamed accordingly.

632▶ SCP example:
scp admin@192.168.87.50:/diag-data.zip .

▶ Windows PSCP command:
PSCP in Windows works in a similar way to the SCP.
•

pscp -P <port> <user name>@<device ip>:/diag-data.zip <filename>

Uploading or Downloading Raw Configuration Data
You can download the raw configuration data of a specific device for review, backup or modification.
After modifying or creating any raw configuration data, you can upload it to a specific device forchanging its configuration. The uploaded raw configuration file can contain only partial configuration
keys that you want to modify. Other settings that are not contained in the uploaded file will remainunchanged.
Syntax of the raw configuration data is completely the same as the syntax in the config.txt file. Seeconfig.txt.
Warning: Some configuration keys in the downloaded raw configuration arecommented out, and those must NOT be part of the configuration that will be
uploaded to any device. See Keys that Cannot Be Uploaded (on page 635).

▶ To download raw configuration data:
1. Type one of the following SCP commands and press Enter.
Scenario 1: Use the default SCP port and default filename•

SSH/SCP port is the default (22), and the accessed device is a standalone device.

•

The raw configuration file's default filename "raw_config.txt" is wanted. Then add a dot (.) in the endof the SCP command as shown below.

scp <user name>@<device ip>:/raw_config.txt .

Scenario 2: Specify a different SCP port but use the default filename•

SSH/SCP port is NOT the default (22), or the accessed device is a Port-Forwarding expansion device.

•

The raw configuration file's default filename "raw_config.txt" is wanted. Then add a dot in the end of
the SCP command as shown below.

scp -P <port> <user name>@<device ip>:/raw_config.txt .

Scenario 3: Specify a new filename but use the default SCP port•

SSH/SCP port is the default (22), and the accessed device is a standalone device.

•

Renaming the raw configuration file is wanted.

scp <user name>@<device ip>:/raw_config.txt <filename>633

Scenario 4: Specify a different SCP port and a new filename•

SSH/SCP port is NOT the default (22), or the accessed device is a Port-Forwarding expansion device.

•

Renaming the raw configuration file is wanted.

scp -P <port> <user name>@<device ip>:/raw_config.txt <filename>•<user name> is the "admin" or any user profile with Administrator Privileges.

•<device ip> is the IP address or hostname of the device whose data you want to download.

•<port> is the current SSH/SCP port number, or the port number of a specific link unit device in the
Port-Forwarding chain.

• <filename> is the new filename of the downloaded file.
1. Type the password when prompted.
2. The system downloads the specified data from the device onto your computer.
•If you do NOT specify a new filename in the command, such as Scenarios 1 or 2, the downloaded
file's default name is "raw_config.txt."•

If you specify a new filename in the command, such as Scenarios 3 or 4, the downloaded file isrenamed accordingly.

▶ To upload raw configuration data:
1. Type one of the following SCP commands and press Enter.
Scenario 1: Only one device to configure, with the default SCP port•

SSH/SCP port is the default (22), and the accessed device is a standalone device.

•

There is only one device to configure so a CSV file for device-specific settings is NOT needed.

scp <config file> <user name>@<device ip>:/raw_config_update

Scenario 2: Only one device to configure, with a non‑default SCP port•

SSH/SCP port is NOT the default (22), or the accessed device is a Port-Forwarding expansion device.

•

There is only one device to configure so a CSV file for device-specific settings is NOT needed.

scp -P <port> <config file> <user name>@<device ip>:/raw_config_update

Scenario 3: Multiple device to configure, with the default SCP port•

SSH/SCP port is the default (22), and the accessed device is a standalone device.

•

There are multiple devices to configure so a CSV file for device-specific settings is needed during the
upload.

scp <dev_list file> <config file> <user name>@<device ip>:/
raw_config_update/match=<col>Scenario 4: Multiple device to configure, with a non‑default SCP port•

SSH/SCP port is NOT the default (22), or the accessed device is a Port-Forwarding expansion device.

•

There are multiple devices to configure so a CSV file for device-specific settings is needed during the
upload.

scp -P <port> <dev_list file> <config file> <user name>@<device ip>:/
raw_config_update/match=<dev_col>

634

•

<config file> is the filename of the custom raw configuration that you want to upload.

•<user name> is the "admin" or any user profile with Administrator Privileges.

•<device ip> is the IP address or hostname of the device where you want to upload the specified
file.

•

<port> is the current SSH/SCP port number, or the port number of a specific expansion device in
the Port-Forwarding chain.

•<dev_list file> is the name of the CSV file for configuring multiple device with devicespecific settings. For this file's format, see devices.csv.
▪ For device-specific settings in the <config file>, refer each device-specific configuration
key to a specific column in the <dev_list file>. See config.txt.

•<dev_col> comprises "serial:" or "mac:" and the number of the column where the serial
number or MAC address of each device is in the uploaded CSV file. This is the data based on which
each device finds its device-specific settings.
For example:▪ If the second column contains each device's serial number, the parameter is then serial:2.
▪ If the seventh column contains each device's MAC address, the parameter is then mac:7.

▶ SCP examples:•

Raw configuration download example -scp admin@192.168.87.50:/raw_config.txt config.txt•

Raw configuration upload example with the configuration file only -scp config.txt admin@192.168.87.50:/raw_config_update•

Raw configuration upload example with both configuration and device list files -scp devices.csv config.txt admin@192.168.87.50:/raw_config_update/match=serial:2▶ Windows PSCP commands:
PSCP in Windows works in a similar way to the SCP.
•

pscp -P <port> <user name>@<device ip>:/raw_config.txt <filename>•pscp -P <port> <CSV file> <config file> <user name>@<device ip>:/
raw_config_update/match=<col>▶ Alternative of bulk configuration via SCP:
Both methods of uploading 'bulk configuration' file or 'raw configuration' file via SCP can serve thepurpose of bulk configuration. The only difference is that you can configure device-specific settings withthe upload of raw configuration but not with the 'bulk configuration' file.

Keys that Cannot Be Uploaded
The raw configuration downloaded from any PX-Series PDU contains a few configuration keys that arecommented out with either syntax below.

635

These configuration keys cannot be part of the configuration that you will upload to any PX-Series PDU.
That is, they should be either not available or remain commented out in the configuration file you will
upload.
Comment syntax Description

636#INTERNAL#Internal use only. They are NOT user configurable settings.

#OLD/INVALID#

These keys are old or invalid ones.

Cascading Solutions for Xerus

In This Chapter
Cascading Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Cascading Procedure Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Cascading Modes Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Setting the Cascading Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Device-Cascading Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Adding, Removing or Swapping Cascaded Devices. . . . . . . . . . . . . . . . . . . . . . . . 657
Accessing Cascaded Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Identifying Cascaded Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Firmware Upgrade for Cascading Chains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Cascade Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

Cascading Solution Overview
Multiple power products can share network connectivity by cascading them through the USB or
Ethernet interface. To reduce the number of Ethernet connections or save networking costs in your data
center, you can apply this cascading solution.
You can access and administer each device in the cascading chain over the Internet from anywhere via
various protocols -- HTTP(S), SNMP, SSH, Telnet and Modbus. Each device can be upgraded respectively.

Applicable Products
The Xerus Technology platform's cascading solution is supported on the following products.

▶ Xerus requirements:•

All devices must run Xerus firmware version 3.3.10 or later. Check firmware versions before
cascading your devices and upgrade any device as needed.

•

If your cascade includes "newer" devices, such as SRC, PX4, PRO4X, and PRO3X, note that newer
devices are only supported as of their introductory firmware version. Avoid downgrading cascades.

▶ Raritan products:•

PX4 PDUs•

PX2 series PDUs•

PX3 series PDUs, including PX3‑iX7•

PX3TS transfer switches, including PX3TS‑iX7•

Branch Circuit Monitor 2 (BCM2), PMC and PMMC series, including:•BCM2‑iX7•

PMC‑iX7637

•

PXC series PDUs•

PXO series PDUs•

Smart Rack Controller (SRC)▶ Server Technology products:•

PRO4X PDUs•

PRO3X PDUs

▶ Legrand products:•

Legrand PDUs

Illustration
In a cascading chain, all PDUs are cascaded via USB or Ethernet, and only the primary device isconnected to the LAN.
The following diagrams illustrate different cascading scenarios using Zero U PDUs. Red lines in the
diagrams represent the cascading connections, which are either USB or standard network patch cables.

▶ Scenario 1: Cabinet 1 has four PDUs cascaded, sharing one Ethernet connection.

638

▶ Scenario 2: Cabinet 1 and Cabinet 2 have four PDUs respectively.
The eight PDUs are cascaded, sharing one Ethernet connection.

▶ Scenario 3: Cabinet 1 through Cabinet 4 have four PDUs respectively.
The 16 PDUs are cascaded, sharing one Ethernet connection.

639

Best Practices for Cascading▶ One Ethernet connection per cabinet is better:
One Ethernet connection per cabinet is better than one Ethernet connection across cabinets because of
these advantages:•

Easier to manage or maintain one cabinet when all of the cabling and connections are located in thesame cabinet.

•

Reduces cross‑cabinet cabling.

▶ When to establish a chain comprising 32 devices:A chain consisting of 32 devices saves the most Ethernet connections and costs, and it is recommended
only when:•

External Ethernet ports are expensive or limited.

•

Available IP addresses are limited.

▶ Ethernet cascading is recommended for PDUs/Devices with Dual Ethernet ports:
When cascading devices that have dual Ethernet ports, choose Ethernet cascading when possible
instead of USB cascading. The Ethernet interface offers the following benefits over USB.
•

Longer cabling distance•

Lower latency•

Connection more reliable with RJ‑45 connectors

Supported products with dual Ethernet ports include: Raritan's PX3‑iX7 PDUs, PX3TS‑iX7 transfer
switches, PXC PDUs, PXO PDUs, SRC, Legrand PDUs, Server Technology PRO3X and PRO4X PDUs.

When to Avoid Cascading Devices
There are two scenarios where the cascading solution is NOT recommended.

640

▶ High network reliability is required:
The cascading solution increases the number of network bridging points for cascaded
devices, which may result in network unreliability. Therefore, when high network
reliability is required, establish a separate network connection for each PDU tominimize the number of potential network failure points.

▶ High bandwidth is required:
The bandwidth among cascaded devices is limited by the USB or Ethernet interface
where they are connected. When high bandwidth is required, such as transmission of
webcam videos, it is strongly recommended to directly connect that PDU to the
network to optimize the data transfer rate.
The maximum bandwidth supported by each interface:•USB:• 12 Mbps (half duplex) when both or either side supports
full‑speed USB only.
• 480 Mbps (half duplex) when both cascaded devices support
high-speed USB.

•

Ethernet:• 100 Mbps, full duplex

Note: Effective throughput may be lower than the rate listed due toprotocol overhead.

Cascading Procedure Overview
You must follow the steps below to establish a cascading chain.
Warning: Networking issues occur if the following steps are reversed.

▶ Main cascading procedure:
1. Log in to each PDU and configure the cascading mode.
2. Cascade all devices.

Cascading Modes Overview
The cascading mode is a network configuration setting that determines how each device in the chain isaccessed.
There are two cascading modes: Bridging and Port Forwarding.
In the following illustration, it is assumed that users enable the DHCP networking for the cascading
chain comprising four devices. In the diagrams, "P" is the primary device and "E" is an expansion device.

641

▶ "Bridging" mode:

In this mode, the DHCP server communicates with every cascaded device
respectively and assigns four different IP addresses. Each device has its own IP
address.
The way to remotely access each cascaded device is completely the same asaccessing a standalone device in the network.

642

▶ "Port Forwarding" mode:

In this mode, the DHCP server communicates with the primary device alone andassigns one IP address to the primary device. All expansion devices share the same
IP address as the primary device.
You must specify a 5XXXX port number (where X is a number) when remotely
accessing any expansion device with the shared IP address. See Port Number Syntax(on page 254), Port Number Syntax (on page 659).

▶ Comparison between cascading modes:•

The Bridging mode supports the wired network only, while the Port Forwarding mode supports both
wired and wireless networks.

•

Both cascading modes support a maximum of 32 devices in a chain.

•

Both cascading modes support both DHCP and static IP addressing.

•In the Bridging mode, each cascaded device has a unique IP address.

•

In the Port Forwarding mode, all cascaded devices share the same IP address(es) as theprimary device.
In the Bridging mode, each cascaded device has only one IP address.
In the Port Forwarding mode, each cascaded device can have multiple IP addresses as longas the primary device has multiple network interfaces enabled/configured properly.
For example:• When the primary device has two Ethernet ports (ETH1/ETH2), you can enable ETH1, ETH2 andWIRELESS interfaces so that the Port-Forwarding chain has two wired IP addresses and one
wireless IP address.

Setting the Cascading Mode
Warning: The cascading mode of all devices in the chain must be the same.
Different cascading modes in a chain cause a networking failure in all subsequent
expansion devices.

643

Repeat the following procedure for each device you want to cascade until all devices share the samecascading mode.
The cascading mode can be configured via the web interface or command line interface (CLI).
You must have the Change Network Settings permission to configure the cascading mode.

▶ To set the cascade mode in the web interface:
1. Log in to the web interface of each device you intend to cascade.
2. Choose Device Settings > Network.
3. Select the preferred mode in the Cascading Mode field.
Mode

DescriptionNone

No cascading mode is enabled. This is the default.

Bridging

Each device in the cascading chain is accessed with a different
IP address.

Port
Forwarding

Each device in the cascading chain is accessed with the same
IP address(es) but with a different port number assigned.

See Port Number Syntax (on page 254), Port Number
Syntax (on page 659).

Tip: If selecting Port Forwarding, the Device Information page will show a list of port numbers for all
cascaded devices. Choose Maintenance > Device Information > Port Forwarding.
1. For the Port Forwarding mode, one to two more fields have to be configured.
Note that if either setting below is incorrectly configured, a networking issue occurs.

644

Field

Description

Port forwarding role

Primary or Expansion.

(available on all cascaded
devices)This is to determine which device is the primary andwhich ones are expansion devices.

FieldDescription

Downstream interface

USB or ETH1/ETH2.

(available on the primarydevice only)This is to determine which port on the primarydevice is connected to Expansion 1.
If ETH1 or ETH2 is selected as the downstream
interface, make sure the selected Ethernet interface
is enabled.

2. (Optional) Configure the network settings by clicking the BRIDGE, ETH1/ETH2, or WIRELESS section
on the same page.
• In the Bridging mode, each cascaded device can have different network settings. You may need toconfigure each device's network settings in the BRIDGE section.
• In the Port Forwarding mode, all cascaded devices share the primary device's network settings. You
only need to configure the primary device's network settings in the ETH1/ETH2 and/or WIRELESS
section.
Tip: You can enable/configure multiple network interfaces in the Port Forwarding mode so that thecascading chain has multiple IP addresses.
3. Click Save.

▶ To set the cascade mode in the CLI:
1. Access each device you intend to cascade via CLI.
2. Type config and press Enter to enter the configuration mode.
3. Type the following command to set the cascading mode.
config:#network <mode> enabled <option1>

Variables:•<mode> is one of the following cascading modes.
Mode

Description

bridgeThe Bridging mode, where each cascaded device is assigned aunique IP address.

portForwarding The Port Forwarding mode, where every cascaded device in the
chain shares the same IP address, with diverse port numbers
assigned.

Important: When enabling either cascading mode, you must make sure the othercascading mode is disabled, or the preferred cascading mode may not be enabled
successfully.
•<option1> is one of the following options:

645

OptionDescriptiontrue

The selected cascading mode is enabled.

false

The selected cascading mode is disabled.

▶ If Port Forwarding mode is enabled, you must configure two more settings to finish theconfiguration:
On ALL cascaded devices, you must configure the 'role' setting one by one.
config:#network portForwarding role <option2>

On the primary device, you must configure the 'downstream interface' setting.
config:# network portForwarding
primaryUnitDownstreamInterface <option3>
Variables:••<option2> is one of the following cascading roles:
Role

Description

primary

The device is a primary device.

expansion

The device is a expansion device.

<option3> is one of the following options:
OptionDescription

ETH1/ETH2 port is the port where the 1st expansion device is connected.

646

OptionDescription

Usb

USB port is the port where the 1st expansion device is connected.

Device-Cascading Methods
There are two cascading methods.
•

USB cascading: All devices in the chain are cascaded via USB ports. All products described in thisguide support this cascading method.

•

Extended cascading: Devices in the chain are cascaded via either USB or Ethernet ports, as needed.
Only devices with dual Ethernet ports can be cascaded in this way. Supported products have iX7,
iX9, or PRO3X NIM8G2 controllers with dual ethernet ports.

USB Cascading

Products with full‑speed USB transfer data at a maximum rate of 12 Mbps.
Products with high-speed USB transfer data at a maximum rate of 480 Mbps. iX7, iX9 and Pro3X
controllers support high-speed USB.
USB communication is always half duplex.
Note that the USB bandwidth between the primary and the first expansion device will limit the actual
data transfer rate between all USB-cascaded expansion devices.
Tip: If two or more PDUs with high-speed USB are involved in a USB‑cascading chain, you can set themas the primary and the first expansion units for optimal data transmission.
The distance between two USB‑cascaded devices CANNOT exceed 5 meters (16 feet).

USB-Cascading Requirements
The USB‑cascading chain comprises either identical or diverse supported products. For example, you
can cascade PX3 PDUs only, or you can mix other supported models in a USB‑cascading chain.

▶ Hardware requirements:
Raritan/Legrand/ServerTech products

Number of USB‑A ports

PX4 series PDU

2647

Raritan/Legrand/ServerTech products

Number of USB‑A ports

PX3 series PDUs, including PX3‑iX7

2PX2 series PDUs

1

PX3TS transfer switches, including PX3TS‑iX7

2

BCM2

2

PMC

2

PMMC

1

PXC

1

PXO

1

Legrand PDUs

1

SRC

2

PRO4X PDU

2

PRO3X PDU

1•

If wireless networking is wanted, the primary device must be a product with "dual" USB‑A ports.

Cascading All Devices via USB-Only
To avoid networking problems, make sure to configure each unit's Cascading Mode in the network
settings before creating the cascade. All units in a cascade must be in the same cascading mode.
•

Any certified USB 2.0 cable up to 5 meters (16 feet) long can be used.

•

Up to 32 units in total can be cascaded. 1 Primary unit and 31 Expansion units.

The following illustrates a USB-cascading chain.

648

Number

Device role
Primary unit
Expansion 1
Expansion 2
Expansion 3▶ To cascade devices:
1. Connect the Primary unit to the LAN, using a method below.
• Bridging mode:

649

Use a standard network patch cable (CAT5e or higher).
• Port Forwarding mode:
Use a standard network patch cable and/or a Raritan USB WIFI wireless LAN adapter.
2. Connect the USB‑A port of the primary device to the USB‑B port of the next product you want tocascade. This additional unit is Expansion 1.
3. Connect Expansion 1's USB‑A port to the USB‑B port of the next product via another USB cable. The
second additional device is Expansion 2.
4. Repeat to connect all remaining expansion devices.

Extended Cascading for Dual Ethernet and USB
Extended cascading can be made via USB or Ethernet interfaces on devices with Dual Ethernet and highspeed USB. See Extended-Cascading Requirements (on page 650)
Data transfer speeds and cable restrictions vary:
Item

Maximum rate or distance

Data transfer rate•

USB: 480 Mbps (half duplex)•

Ethernet: 100 Mbps (full duplex)•

USB: 5 meters (16 feet)•

Ethernet: 100 meters (328 feet)

Cabling distance between two cascaded
devices

Extended-Cascading Requirements
The extended‑cascading chain must meet these requirements.

▶ Hardware requirements:
All cascaded devices must have dual Ethernet ports and at least one USB‑A port. This includes Raritan/
Legrand/Servertech supported devices with:

650

•

iX7 controller•

iX9 controller•

Pro3X NIM8G controller

Note: There is one exception for iX7 controllers. Raritan's BCM2 series, including BCM2‑iX7, PMC‑iX7
and PMMC, are not supported because they have only one Ethernet port in their iX7 controller.

Cascading Devices via Dual Ethernet and USB
To avoid networking problems, make sure to configure each unit's Cascading Mode in the network
settings before creating the cascade. All units in a cascade must be in the same cascading mode.
Make sure all devices in your intended cascade support Extended Cascading. See Extended-Cascading
Requirements (on page 650).
When cascading devices in a port forwarding configuration, make sure to follow additional restrictions.
See Restrictions of Port-Forwarding Connections (on page 654)•

You can use either Ethernet port for cascading.

•If the two Ethernet ports support different network speeds, use the faster one for the upstream
connection.

Note: The following diagram illustrates PX3‑iX7 Zero U PDUs, but the same procedure also applies to all
supported devices.

651

Number

Device role
Primary unit
Expansion 1
Expansion 2
Expansion 3▶ To cascade via Dual Ethernet ports:
1. Choose an appropriate device as the primary unit.
2. Connect the Primary unit to the LAN, using a method below.
• Bridging mode:

652

Use a standard network patch cable (CAT5e or higher).
• Port Forwarding mode:
3.
4.
5.
6.

Use a standard network patch cable and/or a Raritan USB WIFI wireless LAN adapter.
Connect an available Ethernet port of the primary device to either Ethernet port of anothersupported device via a standard network patch cable. This additional unit is Expansion 1.
Connect Expansion 1's available Ethernet port to either Ethernet port of another supported device
via a standard network patch cable. The second additional unit is Expansion 2.
In this "extended cascading" configuration, you can also choose to connect expansion units via USB.
See Cascading All Devices via USB-Only (on page 648) for instructions.
Repeat to connect all remaining expansion devices.

▶ Recommendations for cascade loops:
You can connect both the first and the last PDU to your network (cascade loop)
under the following conditions:a. The remaining network MUST use R/STP to avoid network loops.
AND
b. Both the first and the last PDUs MUST either attach to the same switch or, if they are attached to two
separate switches, you must configure both ports of these switches so that the STP costs are high.
This prevents the STP protocol from sending unrelated traffic through the PDU cascade, which cancause bottlenecks that lead to connectivity issues in the whole network.

Cascading Restrictions▶ Xerus Version Requirements:•

Mixing firmware versions is not supported. All cascaded devices must be on the same firmware
version to ensure compatibility.

▶ Network Requirements:•

Only the primary device is connected to the LAN. Do NOT connect expansion units to the LAN or
WLAN.

•

Appropriate networking methods vary based on the cascading mode.
• The Bridging mode supports the wired networking only.
• The Port Forwarding mode supports both the wired and wireless networking.

•Your network switch's port security settings must support the cascading solution. Make sure thatpackets forwarding is enabled for the "external" Ethernet port where the primary device isconnected.

•

Plug-and-play is not supported. You CANNOT add, remove or swap cascaded devices in a chain
randomly. For the appropriate procedure, see Adding, Removing or Swapping Cascaded Devices.

653

▶ Bridging Mode Restrictions:•

In the Bridging mode, the primary unit device can have only one connection to the network. If the
primary device has two Ethernet ports, DO NOT connect both Ethernet ports to the network(s)unless your network has the R/STP protocol enabled.
Note: The Port Forwarding mode does NOT have this restriction. In this mode, you can enable one
wired and one wireless network connections for devices with only one Ethernet port, or enable two
wired and one wireless network connections for Dual Ethernet devices.

▶ Wireless LAN Restrictions (Port Forwarding mode only):•

You must use Raritan's USB WIFI wireless LAN adapter.

•No external USB hub is used with the primary device.

•

To establish a USB‑cascading chain, the primary unit must have two USB‑A ports so that both thewireless LAN adapter and the expansion device can be connected.

Restrictions of Port-Forwarding Connections
The following guidelines must be obeyed for establishing a cascading chain in the Port Forwardingmode.
•

Each cascaded device, except for the primary device, must have only one upstream device.

•

Each cascaded device, except for the last expansion device, must have only one downstream device.

•

Use only one cable to cascade two devices. That is, NO simultaneous connection of USB and
Ethernet cables between two cascaded devices.

The following diagrams illustrate cascading connections that are NOT supported.
Note: Specific models and port layouts vary, but the same restricted configurations apply to all
supported devices.

▶ UNSUPPORTED connections:•654

One cascaded device has two upstream devices via Ethernet cables.

•One cascaded device has two upstream devices via Ethernet and USB cables.

655

656

•

One cascaded device has two downstream devices.

•

One device is connected to another device via two cascading cables - USB and Ethernet cables.

Adding, Removing or Swapping Cascaded Devices
Change a device's cascading mode first before adding that device to a cascading chain, or before
disconnecting that device from the chain.
If you only want to change the cascading mode of an existing chain, or swap the primary and expansion
device, always start from the expansion device.
Note: If the following procedures are not followed, a networking issue occurs. When a networking issue
occurs, check the cascading connection and/or software settings of all devices in the chain.

▶ To add a device to an existing chain:
1. Connect the device you will cascade to the LAN and find its IP address, or connect it to a computer.
2. Log in to this device and set its cascading mode to be the same as the existing chain's cascadingmode.
3. (Optional) If this device will function as an expansion device, disconnect it from the LAN after
configuring the cascading mode.
4. Connect this device to the chain, using either a USB or Ethernet cable.

▶ To remove a device from the chain:
1. Log in to the desired cascaded device, and change its cascading mode to None.

657

Exception: If you are going to connect the removed device to another cascading chain, set its cascading
mode to be the same as the mode of another chain.
2. Now disconnect it from the cascading chain.

▶ To swap the primary and expansion device:•

In the Bridging mode, you can swap the primary and expansion devices by disconnecting ALL
cascading cables from them, and then reconnecting cascading cables. No changes to softwaresettings are required.

•

In the Port Forwarding mode, you must follow the procedure below:a. Access the expansion device that will replace the primary device, and set its role to'Primary', and correctly set the downstream interface.
b. Access the primary device, set its role to 'Expansion'.
c. Swap the primary and expansion device now.
▪ You must disconnect the LAN cable and ALL cascading cables connected to the two devices
first before swapping them, and then reconnecting all cables.

▶ To change the cascading mode applied to a chain:
1. Access the last expansion device, and change its cascading mode.
• If the new cascading mode is 'Port Forwarding', you must also set its role to 'Expansion'.
2. Access the second to last, third to last and so on until the first expansion device to change theircascading modes one by one.
3. Access the primary device, and change its cascading mode.
• If the new cascading mode is 'Port Forwarding', you must also set its role to 'Primary', and correctly
select the downstream interface.
The following diagram indicates the correct sequence. 'N' is the final one.
•

P = Primary device•

E = Expansion device

Accessing Cascaded Devices
The primary device functions as the network bridge and can transmit IP packets between the LAN andall expansion devices connected to it. Therefore, you can remotely access the primary and every
expansion device via the Web (http or https), SNMP, SSH, or Telnet interface.

Port Numbers for Port-Forwarding Devices
All devices in a Port-Forwarding chain share the same IP address(es). Therefore, a TCP/UDP port number
is required when accessing any cascaded device in the chain.

658

Port Number Syntax
In the Port Forwarding mode, all devices in the cascading chain share the same IP address(es). To accessany cascaded device, you must assign an appropriate port number to it.
•

Primary device: The port number is either 5NNXX or the standard TCP/UDP port.

•

Expansion device: The port number is 5NNXX.

▶ 5NNXX port number syntax:••

NN is a two-digit number representing the network protocol as shown below:
Protocols

NN

HTTPS

00

HTTP

01

SSH

02

TELNET

03

SNMP

05

MODBUS

06

XX is a two-digit number representing the device position as shown below.
PositionXX

PositionXX

Primary device

00

Expansion 8

08

Expansion 1

01

Expansion 9

09

Expansion 2

02

Expansion 10

10

Expansion 3

03

Expansion 11

11

Expansion 4

04

Expansion 12

12

Expansion 5

05

Expansion 13

13

Expansion 6

06

Expansion 14

14

Expansion 7

07

Expansion 15

15

For example, to access the Expansion 4 device via Modbus/TCP, the port number is 50604.
Tip: The full list of each cascaded device's port numbers can be retrieved from the web interface.
Choose Maintenance > Device Information > Port Forwarding.

▶ Standard TCP/UDP ports:
The primary device can be also accessed through standard TCP/UDP ports as listed in the following
table.

659

Protocols

Port Numbers

HTTPS

443

HTTP

80

SSH

22

TELNET

23

SNMP

161

MODBUS

502

In the Port Forwarding mode, the cascaded device does NOT allow you to modify the standard TCP/UDP
port configuration, including HTTP, HTTPS, SSH, Telnet and Modbus/TCP.

Port Forwarding Examples
In this example, Port Forwarding mode is applied to a cascading chain comprising three devices. The IP
address is 192.168.84.77.

▶ Primary device:
Position code for the primary device is '00' so each port number is 5NN00 as listed below.
Protocols

Port numbers

HTTPS

50000

HTTP

50100

SSH

50200

TELNET

50300

SNMP

50500

MODBUS

50600

Examples using "5NN00" ports:•••

To access the primary device via HTTPS, the IP address is:https://192.168.84.77:50000/
To access the primary device via HTTP, the IP address is:
http://192.168.84.77:50100/
To access the primary device via SSH, the command is:ssh -p 50200 192.168.84.77

Examples using standard TCP/UDP ports:•

660

To access the primary device via HTTPS, the IP address is:••

https://192.168.84.77:443/
To access the primary device via HTTP, the IP address is:
http://192.168.84.77:80/
To access the primary device via SSH, the command is:ssh -p 22 192.168.84.77▶ Expansion 1 device:
Position code for Expansion 1 is '01' so each port number is 5NN01 as shown below.
Protocols

Port numbers

HTTPS

50001

HTTP

50101

SSH

50201

TELNET

50301

SNMP

50501

MODBUS

50601

Examples:•••To access Expansion 1 via HTTPS, the IP address is:https://192.168.84.77:50001/
To access Expansion 1 via HTTP, the IP address is:
http://192.168.84.77:50101/
To access Expansion 1 via SSH, the command is:ssh -p 50201 192.168.84.77▶ Expansion 2 device:
Position code for Expansion 2 is '02' so each port number is 5NN02 as shown below.
Protocols

Port numbers

HTTPS

50002

HTTP

50102

SSH

50202

TELNET

50302

SNMP

50502

MODBUS

50602

661

Examples:•••

To access Expansion 2 via HTTPS, the IP address is:https://192.168.84.77:50002/
To access Expansion 2 via HTTP, the IP address is:
http://192.168.84.77:50102/
To access Expansion 2 via SSH, the command is:ssh -p 50202 192.168.84.77

Identifying Cascaded Devices
You can retrieve a device's cascading status from one of these interfaces:•

Web interface: Accessible via HTTP or HTTPS.

•

Command line interface (CLI): Accessible via SSH, Telnet or the serial interface.

•

SNMP: An SNMP manager is required.

•

LCD display: Use the front panel LCD display if your device has it.

Using the Web Interface
1. Choose Maintenance > Device Information.
2. Check the Network section. Press F5 to reload it if needed.

▶ Cascading information in the Bridging mode:•

The Common section contains two read-only fields for indicating the cascading status. Note that thecascading position is NOT available in the Bridging mode.

FieldsDescription

Port forwarding Indicates the Port Forwarding is disabled. See Setting the

Cascading Mode (on page 643).

BRIDGE section Indicates the device is in the Bridging mode and its IP

address.

662

▶ Cascading information in the Port Forwarding mode:•

The Common section contains three read-only fields for indicating the cascading status.

FieldsDescription

Port
forwarding

Indicates the Port Forwarding is enabled. See Setting the
Cascading Mode (on page 643).

Cascadeposition

Indicates the position of the PX-Series PDU in the cascading
chain.

Cascaded
deviceconnected••

0 (zero) represents the primary device.

•

A non-zero number represents a expansion device. 1 isExpansion 1, 2 is Expansion 2, 3 is Expansion 3 and so on.

Indicates whether a expansion device is detected on the
USB‑A or Ethernet port.
•

yes: Connection to a expansion device is detected.

•

no: NO connection to a expansion device is detected.

A primary device shows 0 (zero) in the 'Cascade position' field and yes in the 'Cascaded device
connected' field.

663

•

A expansion device in the middle position shows the number of its exact position in the 'Cascade
position' field and yes in the 'Cascaded device connected' field.
The following diagram shows 1, indicating it is the first expansion device - Expansion 1.

•

The final expansion device shows a non‑zero number which indicates its position in the 'Cascade
position' field and no in the 'Cascaded device connected' field.
The following diagram shows 2, indicating it is the second expansion device - Expansion 2.
The 'Cascaded device connected' field shows no, indicating that it is the final one in the
chain.

664

•For a list of port numbers required for accessing each cascaded device in the Port Forwarding mode,
click the Port Forwarding title bar on the same page.

Using the CLI
1. Log in to the CLI of the desired cascaded device. To use the SSH or Telnet service, see SSH/Telnet
Access.
2. Type the following CLI commands and press Enter.
#show network▶ In the Bridging mode:
In the Bridging mode, IP-related information is shown under the 'BRIDGE' interface, similar to thefollowing.

665

▶ In the Port Forwarding mode:
In the Port Forwarding mode, the Port Forwarding status shows 'Enabled'.

The 'Role' or 'Expansion number' field indicates the device's position.
•

For a primary device, the Role field shows 'Primary'.

•

For a expansion device, the Role field shows 'Expansion'. The 'Expansion number' field indicates its
position: 1 is the first expansion device, 2 is the second, and so on.

Using the SNMP
The unitConfigurationTable in MIB contains entries for cascading information. One SNMP MIB manager,such as a MIB browser, is required for retrieving the SNMP data.
As of release 3.3.10, cascading information other than the cascading mode is no longer available in the
Bridging mode, but all cascading information remains available in the Port Forwarding mode.

▶ In the Port Forwarding mode:
1. Launch your SNMP MIB manager and connect to the desired PX-Series PDU.
2. To find whether the PX-Series PDU is in a cascading chain, retrieve the value of either one below:• SNMP name - pduDaisychainMemberType• SNMP object identifier (OID) - 1.3.6.1.4.1.13742.6.3.2.2.1.41
One of the following values is returned.
SNMP value Description
standalone (0) The PX-Series PDU is not in the cascading chain. It is astandalone device.
primary (1)666

The PX-Series PDU is the primary device.

SNMP value Description
expansion (2)The PX-Series PDU is a expansion device.

3. To check which cascading mode is applied, retrieve the value of either one below:• SNMP name - deviceCascadeType• SNMP OID - 1.3.6.1.4.1.13742.6.3.2.2.1.70
One of the values in the following table is returned.
SNMP value

Cascading mode0

Bridging mode

1

Port Forwarding mode

The value 1 is returned in the Port Forwarding mode.
4. To identify the device's position in the cascading chain, retrieve the value of either one below:• SNMP name - deviceCascadePosition• SNMP OID - 1.3.6.1.4.1.13742.6.3.2.2.1.71
One of the following values is returned.
SNMP value

Device position0

Primary device

1 to 15

Expansion 1 to Expansion 15

5. To find whether the PX-Series PDU is the final expansion device, retrieve the value of either one
below:• SNMP name - cascadedDeviceConnected• SNMP OID - 1.3.6.1.4.1.13742.6.3.2.2.1.58
Check which value is returned. A final expansion device has NO expansion device
connected to its Ethernet (ETH1 or ETH2) or USB‑A port.
SNMP value Description
true (1)

A expansion device has been connected to either Ethernet or
USB‑A port of this PX-Series PDU.

false (2)No expansion device is connected to either Ethernet or USB‑A
port of this PX-Series PDU.

▶ In the Bridging mode:
1. Launch your SNMP MIB manager and connect to the desired PX-Series PDU.
2. To check which cascading mode is applied, retrieve the value of either one below:• SNMP name - deviceCascadeType• SNMP OID - 1.3.6.1.4.1.13742.6.3.2.2.1.70
One of the values in the following table is returned.

667

SNMP value

Cascading mode0

Bridging mode

1

Port Forwarding mode

The value 0 is returned in the Bridging mode.
3. The following cascading information is NOT available in the Bridging mode so they always show apermanent value, which CANNOT correctly indicate the current cascading status.
• pduDaisychainMemberType (1.3.6.1.4.1.13742.6.3.2.2.1.41) always shows'standalone (0)'• deviceCascadePosition (1.3.6.1.4.1.13742.6.3.2.2.1.71) always shows'Primary device (0)'• cascadedDeviceConnected (1.3.6.1.4.1.13742.6.3.2.2.1.58) always shows'false (2)'Using the LCD Display
Some supported products have a front panel display which can show cascading information, such as thedevice position. In the event when the PX-Series PDU releases warning or critical message, LCD will turnon.

Dot-Matrix LCD Display
On the dot‑matrix LCD display, available cascading information depends on the cascading mode.
Note that the diagrams illustrated in this section are for Zero U PDUs, and your dot-matrix LCD display
may look slightly different if it is on a different product model.
1. If the LCD display is in the Automatic mode, exit it by pressing
similar to the following is displayed.

668

or

. The Main Menu

2. Pressorto select "Device Info" in the Main Menu, and press

3. Press

until the Network Cascading page displays.

.

▶ Bridging mode:
In this mode, the LCD display only indicates the Bridging mode is enabled, but thedevice position information is NOT available.

Number Description
Current cascading mode.

•

In the above diagram, it shows the Bridging mode.

669

IPv4/IPv6 network information, including:•

Network configuration: DHCP (or Automatic), or Static. Static represents
Static IP.

•

The device's IP address.

•

IPv4 or IPv6 prefix length (such as "/24").

If you do not enable IPv4 or IPv6 settings, a message is displayed to indicate IPv4 or IPv6 isdisabled.

▶ Port Forwarding mode:
In this mode, the LCD display indicates the cascading mode, device position and thepresence/absence of a connected expansion device.

Description
Cascading mode-related information, including:•Port Forwarding mode•

Primary or Expansion•

Cascade position -- This information is available on expansion devices
only.

1 represents the first expansion, 2 represents the second
expansion, and the like.
•

Expansion Connected: yes indicates a downstream expansion device is
detected, and no indicates no downstream expansion devices aredetected.

The primary device's IPv4/IPv6 address.

670

Character LCD Display
Note: As of release 3.3.10, the following cascading information is no longer available in the Bridging
mode, but remains available in the Port Forwarding mode.
A cascaded device's position is available by operating the LCD display.
Section Example information"d" means the LCD display has entered the Device mode.
"CA" indicates that the cascading information is being displayed.
"Expansion" indicates that this PX-Series PDU is an expansion device.

Note: For a primary device, it shows the word "Primary" instead.
The number 1 means the device position is Expansion 1.

▶ To retrieve the device's cascading position information:
1. Press the MODE button to enter the Device mode, indicated by a 'd' in at the top left of the display.
2. Press the FUNC button until "CA" is displayed at the top right of the display.
3. The device's position is represented by any number defined below:
NumberDevice position

NumberDevice position0

Primary device

8

Expansion 8

1

Expansion 1

9Expansion 9

2

Expansion 2

10

Expansion 10

3

Expansion 3

11

Expansion 11

4

Expansion 4

12Expansion 12

5

Expansion 5

13

Expansion 13

6

Expansion 6

14

Expansion 14

7

Expansion 7

15

Expansion 15

Firmware Upgrade for Cascading Chains
You can upgrade each individual device in the cascading chain through the web interface. The upgrade
procedure is completely identical to the procedure for a standalone device.

671

Do not mix devices running older releases in your cascading chain.

▶ Firmware upgrade restrictions:•Intermediate firmware required for upgrades from "pre-3.3.0" to 3.5.0 or later:
Follow the sequence below:
a. Upgrade to an intermediate firmware first, which is either 3.3.x or 3.4.x.
b. Then upgrade from the intermediate firmware to 3.5.0 or later.

•

Start from the last expansion device for any upgrade from "pre-3.3.10":
To upgrade an existing USB‑cascading chain from a firmware version older than 3.3.10, youmust start from the last expansion device and so on until the primary device. Otherwise, anetworking issue occurs. See Upgrade Sequence in an Existing Cascading Chain.

▶ Warning for firmware DOWNGRADE:AVOID downgrading your cascading chain unless instructed by Technical Support.

Upgrade Sequence for Existing Cascading Chains
Depending on the firmware version(s) of your cascading chain, there may or may not be limitations forthe firmware upgrade sequence in the chain.

▶ Upgrade from 3.3.10 or later:
There is no upgrade sequence limitation.
Firmware version 3.3.10 is compatible with later firmware versions so you can
upgrade all devices of the chain in a random order.
Important: It is not guaranteed that no upgrade sequence limitation will be
required for all future firmware versions. It is highly suggested to check the latest
revision of the Cascading Guide or your product's User Guide/Online Help before
performing the firmware upgrade. The other alternative is to always stick to thesame sequence as the above diagram.

▶ Upgrade from "pre‑3.3.10" to 3.3.10 and later:
You must follow the firmware upgrade sequence below to upgrade a cascading chain
from a firmware version older than 3.3.10 to version 3.3.10 or later. If you do notfollow this upgrade sequence, you will not be able to access some cascaded devices
over the Internet.
• The upgrade must start from the last expansion device (E), then the second to last, the third to last,and so on until the primary device (P).
Red numbers below represent the appropriate upgrade sequence. 'N' is the final one to
upgrade.

672

• You must upgrade ALL devices in the chain to 3.3.10 or later. If you upgrade only some devices in the
chain, networking issues occur on some cascaded devices.

Cascade Troubleshooting
Any accessibility problem in one of the devices in the cascading chain may result in failure to access all
downstream expansion devices that are connected to it.
You can troubleshoot the software settings by connecting the device whose connection has failed to acomputer.
Tip: To determine which device may be the failure point, you may ping each device in the cascading
chain, or check the expansion-related events in the event log of each device.
Symptom

Probable cause

Failure toaccess theprimary
device•Primary device has a loose or lost network connection or power supply connection.

•

Primary device Ethernet or wireless interface is disabled.
• Primary device IPv4 or IPv6 settings are disabled.

•

In the Port Forwarding mode, related settings are incorrectly configured on the
primary device.
• The primary device's role is incorrectly set to Expansion.
• The interface where the network is connected is incorrectly set as thedownstream interface.

•

For the wireless networking, one of the following issues occurs:• The USB wireless LAN adapter attached to the primary device is not the Raritan
USB WIFI LAN adapter.
• The wireless LAN configuration is not supported.
• The installed CA certificate chain contains any certificate that has expired or is not
valid yet.

673

Symptom

Probable cause

Failure toaccess an
expansion
device•One of the following issues occurs on the primary device:• Network connection is lost.
• Power is lost.
• The Ethernet or wireless interface is disabled.

•

One of the following issues occurs on the expansion device in question or any
upstream device (if available):• Connection of the cascading cable is loose or lost.
• No power supply.
• The cascading mode is set incorrectly.

••

For example, the primary device is set to Bridging, but the expansion
device in question or any upstream device is set to Port Forwarding.
In the Bridging mode, IPv4 (or IPv6) settings are disabled on the expansion device inquestion.
In the Port Forwarding mode, one of the following issues occurs:• The primary device's role is incorrectly set to 'Expansion'.
• The primary device's downstream interface is incorrectly set. For example, you usea USB cable to connect the 1st expansion device, but select the Ethernet port as
the downstream interface.
• The role of the expansion device in question or any upstream device is set to'Primary' instead of 'Expansion'.
• The port number you added to the IP address is incorrect. See Port Number
Syntax.
• IPv4 (or IPv6) settings are disabled on the primary device.

•

The expansion device in question or any upstream device is running a "pre‑3.3.10"
firmware version while the rest of the chain runs firmware version 3.3.10 or later.

▶ For a cascading chain comprising only products with "dual" Ethernet ports, also check thefollowing:•

Whether the Ethernet interface (ETH1 or ETH2) where the network or cascading cable is connected
is disabled on the cascaded device in question or any upstream device.

•

Whether the connection complies with the cascading guidelines, when set to the Port Forwarding
mode. See Restrictions of Port-Forwarding Connections.

•

Whether a newer product model, if involved in the chain, runs the appropriate minimum firmware
version or later.

Expansion Device Events in the Log
In the Bridging mode, events regarding connection/disconnection of a downstream expansion device
via USB are NOT logged.
However, in the Port Forwarding mode, whenever the connection or disconnection of a downstream
expansion device via USB is detected, the device at the USB‑A end of the USB cable logs it in its internal
log.

674

There are two expansion-related events in the Port Forwarding mode:
Event

Description

Expansion connected

Expansion device on its USB‑A port is detected

Expansion disconnected Disconnection of a expansion device from its USB‑A

port

675

Resetting to Factory Defaults
Important: Exercise caution before resetting the PX-Series PDU to its factory
defaults.
This erases existing information and customized settings, such as user profiles,
threshold values, and so on. Only energy data and firmware upgrade history areretained.

In This Chapter
Factory Default Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Using the CLI Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Using the Reset Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677

Factory Default Settings
Only secure access--physical or by secure network protocols--is enabled by default in Xerus.
During the first login, before any service can be used, you are forced to change the default password.

▶ Default configuration:
The factory default configuration disables these services:•

SNMP Agent (remains disabled even after default password is changed)•

SCP interface (disabled until default password is changed)

The factory default configuration enables these services:•

Both Ethernet ports are IPv4 enabled for DHCP with access to APIPA link local address•

HTTPS Server•

SSH Server•

Console (not applicable to PX4/PRO4X models)▶ Default password change requirement:
The default password must be changed upon first use, before any other configuration changes or device
access are allowed. In factory default configuration, the following protocols and tools, with thefollowing restrictions, allow you to first update the default password:

676•

HTTPS Server Web User Interface: Restricted to a password change page/form only.

•

HTTPS Server (JSON API Web Service): API limited to a password change for the default account.

•

SSH Server: Prompts for a password change.

•

Console: Prompts for a password change.

Note: Once the default password is changed, the restrictions are removed and the device resumes
normal operations for the protocols and tools listed above. Upon any reset to factory defaults, therestrictions will again be enforced and a change to the default password will again be required.

Using the CLI Command
The Command Line Interface (CLI) provides a reset command for resetting to factory defaults.

▶ To reset to factory defaults after logging in to the CLI:
1. Log in to the CLI by typing the user name "admin" and its password.
2. After the # system prompt appears, type either of the following commands and press Enter.
#

reset factorydefaults-- OR -#

reset factorydefaults /y

3. If you entered the command without "/y" , a message appears prompting you to confirm theoperation. Type y to confirm the reset.
4. Wait until the reset is complete.

▶ To reset to factory defaults without logging in to the CLI:
You can also reset the product to factory defaults in the CLI prior to login. This option requires physicalaccess to the unit, either at the console (for older models) or using a USB configuration method.
1. Connect to the PX-Series PDU and launch a terminal emulation program.
2. At the Username prompt in the CLI, type "factorydefaults" and press Enter.
Username:factorydefaults

3. Type y on a confirmation message to perform the reset.

Using the Reset Button
An RS‑232 serial connection to a computer is required for using the reset button.

▶ To reset to factory defaults using the reset button:
1. Connect a computer to the device.
2. Launch a terminal emulation program such as Kermit or PuTTY, and open a window.
3. Press and release the Reset button while pressing the Esc key of the keyboard several times in rapid
succession. A prompt (=>) should appear after about one second.
4. Type defaults to reset to the factory defaults.
5. Wait until the reset is complete.

677

iX7 Controller Reset Button
This is an example of the reset button location on a sample controller. Port locations may differ on yourmodels.

678

Models with Residual Current Monitoring
Models with residual current monitoring (RCM) detect and report residual current, which is abnormal
flow of current into the protective earth conductor.
Residual current is a safety issue since electrocution is possible if the rack or any device within it istouched.
Depending on the model you purchase, some models report residual current by inlet only, while somemodels report residual current by inlet pole. Some models are also able to report residual DC current inaddition to the total residual current.
Warning: PX-Series PDU RCM cannot disconnect power to stop residual current flow. Devices like RCD
and GFI disconnect power when residual current is detected, but the PX-Series PDU with RCM are NOT
RCD or GFI protected devices.

In This Chapter
RCM Current Sensor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
RCM State Sensor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Compliance with IEC 62020. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
RCM Self-Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Web Interface Operations for RCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Front Panel Operations for RCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
RCM SNMP Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
CLI Operations for RCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690

RCM Current Sensor
The RCM current sensor detects current imbalance which indicates current is flowing to ground. The
sensor cannot determine the exact location. It just reports the sum of all residual current in the PDU
and devices plugged into it, which is either per inlet or per inlet pole, depending on the model.
Most equipment leaks a small amount of current and the UL/IEC 60950-1 standard for IT equipment
permits up to 3mA. For example, if a PDU has one RCM sensor on its inlet and twenty plugged-in
devices -- each leaking 1mA, the RCM sensor then reports the sum - 20mA.
•

All RCM models (M5, M11, M18 and M24) have a residual current sensor.

•

Models with RCM type B (M11, M18 and M24) additionally have separate sensors for "Residual AC
current" and "Residual DC current".

Important: The RCM sensor is 'unavailable' in power‑sharing mode.

RCM State Sensor
The RCM state sensor reports events based on residual current thresholds or RCM self-test failure.

679

The RCM state is always determined by the magnitude of "total" residual current values per inlet or per
inlet pole as explained below.
•

For Type A, it is the sum of residual AC current.

•

For Type B, it is the sum of residual AC and DC current.
In other words, the RCM state is NOT determined by the residual DC current detected by
the separate RCM "DC" sensor on Type B models.
RCM state

Description

normalResidual current is within normal range.

warning

Residual current is above warning level.

criticalResidual current is above critical level.
In addition to an event, the CRITICAL state causes the PX-Series PDU front panel
to display a special error message.

self-test active RCM diagnostics are running.
failureRCM current sensor has malfunctioned. Contact Raritan Technical Support.

Note: The factory default is to disable the Warning state. To define and enable this state, see Setting
RCM Current Thresholds (on page ).
Important: When your PX-Series PDU enters the power-sharing mode, the RCM
sensor enters the 'unavailable' state and will not work until the power‑sharing
mode ends. For information on power sharing, see Power-Sharing Restrictions andConnection.

Compliance with IEC 62020
IEC 62020 is an international standard for Residual Current Monitors. All PX-Series PDU with RCM are
IEC 62020 compliant.
IEC 62020 uses the term rated residual operating current (IΔn) to specify residual current, equal to or
above which causes an alarm. IEC 62020 recommends preferred values 6mA, 10mA, 30mA, 100mA,
300mA and 500mA. In the PX-Series PDU with RCM, IΔn is specified using the Critical Rated Residual
Operating Current threshold.
IEC 62020 uses the term residual non-operating current (IΔno) to specify residual current, below which
does not cause an alarm. IEC 62020 specifies IΔno be no higher than 0.5 IΔn. In PX-Series PDU with
RCM, IΔno is set using the RCM Deassertion Hysteresis and this value must be no higher than 0.5 theRCM critical threshold.
PX-Series PDU with RCM allows you to establish an optional WARNING state, which is not part of the IEC
62020 specification. PX-Series PDU RCM remains IEC 62020 compliant when the RCM deassertion
hysteresis is configured properly.

680

IEC 62020 specification

PX-Series PDU with RCM characteristics

Method of operation

Dependent on line voltage. RCM only functions if line voltage
is present.

Type of installation

PX-Series PDU with flexible line cords and plugs are for mobile
installation and corded connection.

Current paths

1‑phase PX-Series PDU are two current paths RCM.
3‑phase 3W+PE are three current paths RCM.
3‑phase 4W+PE are four current paths RCM.

Ability to adjust residual
operating current

Adjustable.
•

Type A: 6mA-500mA.

•

Type B: 14mA-300mA.

Adjustable time delay

Non‑adjustable time delay.

Protection against external
influence

Enclosed‑type RCM.

Method of mounting

Panel board type RCM.

Method of connection

Not associated with mechanical mounting.

Connection of load conductors

Monitored line is directly connected.

Fault indicating means

Visual, with other output signals.

Ability to directly discriminate

Directionally non-discriminating.

Rated residual operating current

0.5A (highest value).

Residual currents with direct
current components

Model dependent.
•

Models ending in M5 are Type A.

•

Models ending in M11 or M18 are Type B.

RCM Self-Test
PX-Series PDU with RCM have a built-in self-test feature that performs these functions:•

When residual current is less than 3mA, 15mA is momentarily added to determine whether the low
reading is due to a faulty sensor. The residual current added is done in a safe manner that does not
run current into ground or pose operator risk.

•

The RCM state sensor changes to SELF-TEST and then back to its original state if self-test passes, orto the FAILURE state if self-test fails. These state changes are useful to verify your monitoring
systems (SNMP, syslog, or email) are correctly set up to receive PX-Series PDU event notifications.

•

For Type B "M18" models, the self-test feature will perform tests on all poles of the selected inlet
simultaneously.

Note: If self-test fails, the FAILURE state persists until another self-test runs and passes.

681

Web Interface Operations for RCM
The RCM on PX-Series PDU is either an inlet sensor or an inlet pole sensor. To view, configure or run selftest, click Inlet in the Menu.

Checking RCM State and Current
A section titled 'Residual Current Monitor' is available on the Inlet page, showing both the present RCM
state and residual current.
Important: When your PX-Series PDU enters the power-sharing mode, the RCM
sensor enters the 'unavailable' state and will not work until the power‑sharing
mode ends. For information on power sharing, see Power-Sharing Restrictions andConnection.

▶ To check RCM state and current on the Inlet page:
1. Click Inlet.
2. Locate the Residual Current Monitor section on the Inlet page.
• RCM State: There are five states - normal, warning, critical, self-test active and failure. For more
information, see RCM State Sensor (on page ).
• Residual Current:
For Type A, it is the sum of residual AC current.
For Type B, it is the sum of residual AC and DC current.

682

For Type B "M18" models, the listed fields are available per inlet pole as shown below.
Besides, a Type B model, either "M11" or "M18", is able to display the residual DC current.

Note: To determine the RCM's normal, warning and critical levels, configure the RCM current
thresholds. See Setting RCM Current Thresholds (on page ). To configure the residual DC current
thresholds, see Setting RCM DC Current Thresholds (on page ).

RCM Critical State Alarm
When a RCM sensor enters the Critical state, the device beeps and this alarm is displayed in the Alerted
Sensors section of the Dashboard page.
Note that only the RCM sensor will cause the beep while RCM "DC" sensor does not cause the beep
regardless of its sensor state.
Warning: RCM sensors do not work in power-sharing mode.

683

Number Description
The magnitude of residual current reported by the RCM current sensor.
Critical state reported by the RCM state sensor.

Tip: RCM critical state is also indicated on the Inlet page or the Internal Beeper section of the PDU page.

Setting RCM Current Thresholds
Warning Rated Residual Operating Current is the upper warning threshold of the PX-Series PDU RCM
sensor, and Critical Rated Residual Operating Current is the upper critical threshold of the RCM sensor.
These thresholds are set in the configuration mode. See Entering Configuration Mode.
Note: A residual current sensor's LOWER warning and LOWER critical thresholds do NOT affect theoperations of the RCM state sensor so you can ignore them.
For Type B "M18" models, this command configures all RCM sensors of the same inlet simultaneously.

▶ To configure the RCM's Critical level:
config:# residualCurrentMonitor <n> criticalRatedResidualOperatingCurrent<value>Note: The PX-Series PDU triggers events when residual current values are above (but not equal to)thresholds. For example, you would set the critical threshold to 29mA to specify the IEC 62020 IΔn of
30mA. See Compliance with IEC 62020 (on page ).

▶ To configure the RCM's Warning level:
config:# residualCurrentMonitor <n> warningRatedResidualOperatingCurrent<value>▶ To configure the RCM's deassertion hysteresis:
config:#684

residualCurrentMonitor <n> deassertionHysteresis <hy_value>Variables:•<n> is the number of the inlet where the desired RCM current sensor is mounted. For a single-inlet
PDU, this number is always 1.

•<value> is one of the options: enable, disable or a numeric value measured in amperes.

OptionDescription

enableEnables the specified RCM current threshold for the specified inlet.

disableDisables the specified RCM current threshold for the specified
inlet.

A numericvalue

Sets a value for the specified RCM current threshold of thespecified inlet and enables this threshold simultaneously.

Note that this value is measured in A, not mA. Therefore, to
set the value to 6mA, type 0.006.

•<hy_value> is a numeric value measured in amperes (A), not milliamperes (mA). For example, to set
the value to 15mA, type 0.015.

▶ Tip -- other RCM-related "threshold-setting" commands:•

For models detecting residual current per inlet, see Commands for Inlet Sensors•

For models detecting residual current per inlet pole, see Commands for Inlet Pole Sensors

Scheduling RCM Self-Test
You can have the PX-Series PDU run RCM self-test automatically at a regular time interval or on a
specific date and time. See Scheduling an Action for the procedure and select "Start residual current
monitor self test" to create the scheduled RCM self-test action.
Note: For Type B "M18" models, the self-test feature will perform tests on all poles of the selected inlet
simultaneously.

Disabling or Enabling Front Panel RCM Self-Test
You can enable or disable the function of performing the RCM self-test by operating the front panel
buttons. By default, this function is enabled.

▶ To disable or enable the front panel RCM self-test:
1. Choose Device Settings > Front Panel.
2. Do either below:• To disable this function, deselect the "Perform RCM self-test" checkbox.
• To enable this function, select the "Perform RCM self-test" checkbox.
3. Click Save.

685

Setting RCM DC Current Thresholds
RCM DC current sensors are available on Type B models only.
You can also configure upper thresholds for RCM DC current sensors so that an alarm will be displayedon the page of Dashboard when RCM DC sensors enter an alerted state.

▶ To configure RCM DC's upper thresholds:
1. Click Inlet to open the Inlet page.
2. Click the Thresholds title bar at the bottom of the page to display inlet thresholds.

3. Click the desired sensor (required), and then click Edit Thresholds. For example, select "L1 Residual
DC Current".

4. Make changes as needed.
• To enable any threshold, select the corresponding checkbox.
• Type a new value in the accompanying text box.

686

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor
Threshold Settings.
5. Click Save.

Front Panel Operations for RCM
The front panel LCD display shows an alarm message when the RCM enters the critical state. Besides,
you can operate the LCD display to check the RCM status.
This section introduces the RCM information shown on the dot-matrix LCD display.
Note: For RCM information shown on the character LCD display of an old PX-Series PDU model, see RCM
Information (on page ).

LCD Message for RCM Critical StateIn the RCM critical state, the PDU beeps and the LCD display indicates the RCM critical state.
The RCM alarm information continues to display as long as RCM is in a critical state. The top and bottom
bars on the display turn red at the same time.

▶ RCM alarm information in the critical state:
1. The LCD display shows two or three pieces of information for the inlet or inlet pole with the RCM
alarm:

687

• RCM State: Critical.
• Residual Current: Residual current value in Amps.
▪ For Type A, it is the sum of residual AC current.
▪ For Type B, it is the sum of residual AC and DC current.
• Residual DC Current: If your PDU is an RCM Type B model, an additional DC-only residual current
value is also reported on the LCD.

If your PX-Series PDU has more than one inlet, only the inlet which has the RCM alarmenters the critical state.

2. If needed, you can press
to perform RCM self-test for this inlet. For details, see steps 4 to 5
in the topic titled Running RCM Self-Test (on page ).

Checking RCM States and Current
You can retrieve RCM information from the LCD display.

▶ To check RCM information:

1. Pressorto access the Main Menu.

2. Pressorto select "Residual Current", and press.
3. The LCD display shows two or three pieces of information for Inlet 1 as shown below, or a list of inlet
poles.

If a list of inlet poles displays, press
pole.

688

or

, and thento select one inlet

• RCM State: Normal or Warning.
• Residual Current: Residual current value in Amps.
▪ For Type A, it is the sum of residual AC current.
▪ For Type B, it is the sum of residual AC and DC current.
• Residual DC Current: If your PDU is an RCM Type B model, an additional DC-only residual current
value is also reported on the LCD.

If your PX-Series PDU has more than one inlet, a list of inlets is displayed, along with each
inlet's RCM state and reading(s).

4. To return to the Main Menu, press.

Running RCM Self-Test
You can perform RCM self‑test for a specific inlet via CLI. After the self‑test finishes, the test result isshown: pass or fail.
For Type B "M18" models, the self-test feature will perform tests on all poles of the selected inlet
simultaneously.

▶ To perform RCM self-test:#

rcm selfTest inlet <n>689

Variables:•<n> is the inlet's number. For a single-inlet PDU, <n> is always 1.

RCM SNMP Operations
Make sure you have the correct version of SNMP MIB. The PX-Series PDU supports the RCM feature asof firmware version 2.5.20. See Downloading SNMP MIB for details.

RCM Trap
An InletSensorStateChange trap is sent when the RCM state sensor changes. InletSensorStateChange isthe generic trap sent for all inlet sensors. The specific trap for RCM has the object typeOfSensor set to
27. Included with the trap are measurementsInletSensorValue (the residual current value) andmeasurementsInletSensorState (the RCM state that caused the trap).

RCM Residual Current and State Objects
The inletSensorMeasurementsTable contains entries for RCM residual current and states.
Use index sensorType = 26 to retrieve the row for residual current. Column
measurementsInletSensorValue contains the residual current.
Use index sensorType = 27 to retrieve the row for RCM state. Column measurementsInletSensorState
contains the RCM state enumeration value.

Setting RCM Thresholds
The inletSensorConfigurationTable contains a row for configuring RCM thresholds. Use index sensorType= 26 to reference the row. Columns inletSensorUpperWarningThreshold,inletSensorUpperCriticalThreshold and inletSensorHysteresis set values for RCM warning, critical anddeassertion hysteresis respectively.

CLI Operations for RCM
For information on entering and using the CLI, see Using the Command Line Interface.

Showing Residual Current Monitoring Information
This command syntax shows the residual current monitoring (RCM) information, which is only available
on the models with RCM. The information displayed include the RCM current, state and thresholds.
For Type B "M18" models, this command shows the information of all RCM sensors of the same inlet at
a time.
#690

show residualCurrentMonitor <n>Variables:•<n> is one of the options: all, or a number.

OptionDescription

all

Displays the RCM information of all inlets.

Tip: You can also type the command without adding thisoption "all" to get the same data.
A specificinlet number

Displays the RCM information of the specified inlet only.
An inlet number needs to be specified only when there are morethan 1 inlet on your PDU.

▶ Tip -- other RCM-related "show" commands:•

For models detecting residual current per inlet, see Inlet Sensor Threshold Information•

For models detecting residual current per inlet pole, see Inlet Pole Sensor Threshold Information

Setting Front Panel RCM Self-Test
You can enable or disable the front panel RCM self-test function via CLI in addition to the web interface.

▶ To enable the front panel RCM self-test:#

security frontPanelPermissions add rcmSelfTest▶ To disable the front panel RCM self-test:# security frontPanelPermissions remove rcmSelfTest

Degaussing RCM Type B Sensors
Only the models with RCM 'Type B' sensors support degaussing the RCM sensors. Those with RCM TypeA sensors do NOT support this feature.
You can degauss the RCM sensor after a current surge, such as a short circuit.
For Type B "M18" models, this command will degauss all RCM sensors simultaneously.

▶ To degauss RCM Type B sensors:#

rcm degauss691

Remote Authentication Examples

In This Chapter
LDAP Configuration Illustration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
RADIUS Configuration Illustration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Cisco ISE Xerus TACACS+ Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711

LDAP Configuration Illustration
This section provides an LDAP example for illustrating the configuration procedure using Microsoft
Active Directory® (AD). To configure LDAP authentication, four main steps are required:a. Determine user accounts and roles (groups) intended for the device
b. Create user groups for the device on the AD serverc. Configure LDAP authentication on the device
d. Configure roles on the device
Important: TLS is used due to published security vulnerabilities in SSL 3.0. Make
sure your network infrastructure, such as LDAP and mail services, uses TLS rather
than SSL 3.0.

Step A. Determine User Accounts and Roles
Determine the user accounts and roles (groups) that are authenticated for accessing the device. In thisexample, we will create two user roles with different permissions. Each role (group) will consist of twouser accounts available on the AD server.
User roles

User accounts (members)

PX_Userusera
pxuser2

PX_Adminuserb
pxuserGroup permissions:•

The PX_User role will have neither system permissions nor outlet permissions.

•

The PX_Admin role will have full system and outlet permissions.

Step B. Configure User Groups on the AD Server
You must create the groups (roles) for the PX-Series PDU on the AD server, and then make appropriate
users members of these groups.

692

In this illustration, we assume:•

The groups (roles) for the PX-Series PDU are named PX_Admin and PX_User.

•

User accounts pxuser, pxuser2, usera and userb already exist on the AD server.

▶ To configure user groups on the AD server:
1. On the AD server, create new groups -- PX_Admin and PX_User.
Note: Refer to the documentation or online help accompanying Microsoft AD for detailed instructions.
2. Add the pxuser2 and usera accounts to the PX_User group.
3. Add the pxuser and userb accounts to the PX_Admin group.
4. Verify whether each group comprises correct users.

Step C. Configure LDAP Authentication on the PX-Series PDU
You must enable and set up LDAP authentication properly on the PX-Series PDU to use external
authentication.
In the illustration, we assume:•

The DNS server settings have been configured properly. See Wired Network Settings and Role of a
DNS Server.

•

The AD server's domain name is techadssl.com, and its IP address is 192.168.56.3.

•

The AD protocol is NOT encrypted over TLS.

•

The AD server uses the default TCP port 389.

•

Anonymous bind is used.

693

▶ To configure LDAP authentication:
1. Choose Device Settings > Security > Authentication.
2. In the LDAP Servers section, click New to add an LDAP/LDAPS server.
3. Provide the PX-Series PDU with the information about the AD server.
Field/setting

Do this...

IP address / hostname

Type the domain name techadssl.com or IP address 192.168.56.3.
•

Without the encryption enabled, you can type either the domain name or IP
address in this field, but you must type the fully qualified domain name if theencryption is enabled.

Copy settings fromexisting LDAP server

Leave the checkbox deselected unless the new LDAP server's settings are similar toany existing LDAP settings.

Type of LDAP server

Select "Microsoft Active Directory."

Security

Select "None" since the TLS encryption is not applied in this example.

Port (None/StartTLS)

Ensure the field is set to 389.

Port (TLS),

Skip the two fields since the TLS encryption is not enabled.

CA certificate
Anonymous bind

Select this checkbox because anonymous bind is used.

Bind DN,

Skip the three fields because of anonymous bind.

Bind password,
Confirm bind password

694

Base DN for search

Type dc=techadssl,dc=com as the starting point where your search begins on
the AD server.

Login Name Attribute

Ensure the field is set to sAMAccountName because the LDAP server is Microsoft
Active Directory.

User entry object class

Ensure the field is set to user because the LDAP server is Microsoft Active Directory.

User search subfilter

The field is optional. The subfilter information is also useful for filtering out additional
objects in a large directory structure. In this example, we leave it blank.

Active Directory domain

Type techadssl.com.

1. Click Add Server.The LDAP server is saved.
2. In the Authentication Type field, select LDAP.
3. Click Save. The LDAP authentication is activated.
Note: If the PX-Series PDU clock and the LDAP server clock are out of sync, the installed TLS certificates,
if any, may be considered expired. To ensure proper synchronization, administrators should configure
the PX-Series PDU and the LDAP server to use the same NTP server(s).

695Step D. Configure Roles on the PX-Series PDU
A role on the PX-Series PDU determines the system and outlet permissions. You must create the roles
whose names are identical to the user groups created for the PX-Series PDU on the AD server orauthorization will fail. Therefore, we will create the roles named PX_User and PX_Admin on the PDU.
In this illustration, we assume:•

Users assigned to the PX_User role can view settings only, but they can neither configure PX-Series
PDU nor access the outlets.

•

Users assigned to the PX_Admin role have the Administrator Privileges so they can both configure
PX-Series PDU and access the outlets.

▶ To create the PX_User role with appropriate permissions assigned:
1. Choose User Management > Roles.
2. Clickto add a new role.

a. Type PX_User in the Role Name field.
b. Type a description for the PX_User role in the Description field. In this example, we type "View
PX settings" to describe the role.
c. In the Privileges list, select Unrestricted View Privileges, which includes all View permissions. The
Unrestricted View Privileges permission lets users view all settings without the capability toconfigure or change them.

d. Click Save.
3. The PX_User role is created.

696

4. Keep the Roles page open to create the PX_Admin role.

▶ To create the PX_Admin role with full permissions assigned:
1. Clickto add another role.

a. Type PX_Admin in the Role Name field.
b. Type a description for the PX_Admin role in the Description field. In this example, we type
"Includes all PX privileges" to describe the role.
c. In the Privileges list, select Administrator Privileges. The Administrator Privileges allows users to
configure or change all PX-Series PDU settings.

2.

d. Click Save.
The PX_Admin role is created.

RADIUS Configuration Illustration
This section provides illustrations for configuring RADIUS authentication. One illustration is based on theMicrosoft® Network Policy Server (NPS), and the other is based on a FreeRADIUS server.
The following steps are required for any RADIUS authentication:697

1. Configure RADIUS authentication on the PX-Series PDU. See Adding Radius Servers.
2. Configure roles on the PX-Series PDU. See Creating Roles.
3. Configure PX-Series PDU user credentials and roles on your RADIUS server.
• To configure using standard attributes, see Standard Attributes (on page ).
• To configure using vendor-specific attributes, see Vendor-Specific Attributes (on page ).
Note that we assume that the NPS is running on a Windows 2008 system in the NPS illustrations.

Standard Attributes
The RADIUS standard attribute "Filter-ID" is used to convey the group membership, that is, roles.
•

If a user has multiple roles, configure multiple standard attributes for this user.

•

The syntax of a standard attribute is:
Raritan:G{role-name}

FreeRADIUS Standard Attribute Illustration
With standard attributes, NO dictionary files are required. You simply add all user data, including usernames, passwords, and roles, in the following FreeRADIUS path.
/etc/raddb/users▶ Presumptions in the illustration:•

User name = steve•

Steve's password = test123•

Steve's roles = Admin and SystemTester▶ To create a user profile for "steve" in FreeRADIUS:
1. Go to this location: /etc/raddb/users.
2. Add the data of the user "steve" by typing the following. Note that the values after the equal sign (=)
must be enclosed in double quotes (").
steve Cleartext-Password := "test123"
Filter-ID = "Raritan:G{Admin}",
Filter-ID = "Raritan:G{SystemTester}"Vendor-Specific Attributes
You must specify the following properties when using a RADIUS vendor-specific attribute (VSA).
•

Vendor code = 13742•

Vendor-assigned attribute number = 26•

Attribute format = String

The syntax of the vendor-specific attribute for specifying one or multiple roles is:698

Raritan:G{role-name1 role-name2 role-name3}
For configuration on NPS, see NPS VSA Illustration (on page ).
For configuration on FreeRADIUS, see FreeRADIUS VSA Illustration (on page ).

NPS VSA Illustration
To configure Windows 2008 NPS with the vendor-specific attribute, you must:a. Add your PX-Series PDU to NPS. See Step A: Add Your PX-Series PDU as a RADIUS Client (on page ).
b. On the NPS, configure connection request policies and the vendor‑specific attribute. See Step B:
Configure Connection Policies and Vendor-Specific Attributes (on page ).
Some configuration associated with Microsoft Active Directory (AD) is also required for RADIUS
authentication. See AD-Related Configuration (on page ).

Step A: Add Your PX-Series PDU as a RADIUS Client
The RADIUS implementation on the PX-Series PDU follows the standard RADIUS Internet Engineering
Task Force (IETF) specification so you must select "RADIUS Standard" as its vendor name when
configuring the NPS server.

▶ Presumptions in the illustration:•

IP address of your PX-Series PDU = 192.168.56.29•

RADIUS authentication port specified for PX-Series PDU: 1812•

RADIUS accounting port specified for PX-Series PDU: 1813

▶ To add your PX-Series PDU to the RADIUS NPS:
1. Choose Start > Administrative Tools > Network Policy Server. The Network Policy Server console
window opens.

2. Right-click NPS (Local), and select Properties.

699

Verify the authentication and accounting port numbers shown in the properties dialog are thesame as those specified on your PX-Series PDU. In this example, they are 1812 and 1813. Thenclose this dialog.

3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The
New RADIUS Client dialog appears.

7004. Do the following to add your PX-Series PDU to NPS:
a. Verify the "Enable this RADIUS client" checkbox is selected.
b. Type a name for identifying your PX-Series PDU in the "Friendly name" field.
c. Type 192.168.56.29 in the "Address (IP or DNS)" field.
d. Select RADIUS Standard in the "Vendor name" field.
e. Select the Manual radio button.
f. Type the shared secret in the "Shared secret" and "Confirm shared secret" fields. The sharedsecret must be the same as the one specified on your PX-Series PDU.

5. Click OK.

701

Step B: Configure Connection Policies and Vendor-Specific Attributes
You need to configure the following for connection request policies:•

IP address or host name of the PX-Series PDU•

Connection request forwarding method•

Authentication method(s)•Standard RADIUS attributes▶ Presumptions in the illustration:•

IP address of your PX-Series PDU = 192.168.56.29•

Local NPS server is used•

RADIUS protocol selected on your PX-Series PDU = CHAP•

Existing roles of your PX-Series PDU = Admin, User and SystemTester▶ Illustration:
1. Open the NPS console, and expand the Policies folder.

2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog
appears.

702

3. Type a descriptive name for identifying this policy in the "Policy name" field.
• You can leave the "Type of network access server" field to the default -- Unspecified.

4. Click Next to show the "Specify Conditions" screen. Click Add.

703

5. The "Select condition" dialog appears. Click Add.

6. The NAS IPv4 Address dialog appears. Type the PX-Series PDU IP address -- 192.168.56.29, and click
OK.

704

7. Click Next in the New Connection Request Policy dialog.

8. Select "Authenticate requests on this server" because a local NPS server is used in this example.
Then click Next.
Note: Connection Request Forwarding options must match your environment.

705

9. When the system prompts you to select the authentication method, select the following two
options:• Override network policy authentication settings• CHAP -- the PX-Series PDU uses "CHAP" in this example
Note: If your PX-Series PDU uses PAP, then select "PAP."

10. Select Vendor Specific to the left of the dialog, and click Add. The Add Vendor Specific Attributedialog appears.

70611. Select Custom in the Vendor field, and click Add. The Attribute Information dialog appears.
12. Click Add, and the Vendor‑Specific Attribute Information dialog appears.
13. Click "Enter Vendor Code" and type 13742.
14. Select "Yes, it conforms" to indicate that the custom attribute conforms to the RADIUS Request For
Comment (RFC).
15. Click Configure Attribute, and then:a. Type 26 in the "Vendor‑assigned attribute number" field.
b. Select String in the "Attribute format" field.
c. Type Raritan:G{Admin User SystemTester} in the "Attribute value" field. In this example, threeroles 'Admin,' 'User' and 'SystemTester' are specified inside the curved brackets {}.
Note that multiple roles are separated with a space.

16. Click OK.

FreeRADIUS VSA Illustration
A vendor-specific dictionary file is required for the vendor-specific-attribute configuration on
FreeRADIUS. Therefore, there are two major configuration steps.
a. Use a dictionary to define the Raritan vendor-specific attributeb. Add all user data, including user names, passwords, and roles▶ Presumptions in the illustration:•

Raritan attribute = Raritan-User-Roles•

User name = steve•

Steve's password = test123•

Steve's roles = Admin, User and SystemTester707

▶ Step A -- define the vendor-specific attribute in FreeRADIUS:
1. Go to this location: /etc/raddb/dictionary.
2. Type the following in the Raritan dictionary file.
VENDOR Raritan 13742
BEGIN-VENDOR Raritan
ATTRIBUTE Raritan-User-Roles 26 string
END-VENDOR Raritan▶ Step B -- create a user profile for "steve" in FreeRADIUS:
1. Go to this location: /etc/raddb/users.
2. Add the data of the user "steve" by typing the following. Note that the values after the equal sign (=)
must be enclosed in double quotes (").
steve Cleartext-Password := "test123"
Raritan-PDU-User-Roles = "Raritan:G{Admin User SystemTester}"

AD-Related Configuration
When RADIUS authentication is intended, make sure you also configure the following settings related to
Microsoft Active Directory (AD):•Register the NPS server in AD•

Configure remote access permission for users in AD

The NPS server is registered in AD only when NPS is configured for the FIRST time and user accounts are
created in AD.
If CHAP authentication is used, you must enable the following feature for user accounts created in AD:•

Store password using reversible encryption

Important: Reset the user password if the password is set before you enable the"Store password using reversible encryption" feature.

▶ To register NPS:
1. Open the NPS console.
2. Right‑click NPS (Local) and select "Register server in Active Directory."708

3. Click OK, and then OK again.

▶ To grant PX-Series PDU users remote access permission:
1. Open Active Directory Users and Computers.
2. Open the properties dialog of the user whom you want to grant the access permission.
3. Click the Dial-in tab and select the "Allow access" checkbox.

709

▶ To enable reversible encryption for CHAP authentication:
1. Open Active Directory Users and Computers.
2. Open the properties dialog of the user that you want to configure.
3. Click the Account tab and select the "Store password using reversible encryption" checkbox.

710

Cisco ISE Xerus TACACS+ Authentication▶ Configuring Cisco ISE 2.1.x for authenticating TACACS users on the Xerus Platform
Xerus performs authorization through the user’s membership in local roles. You must create a local roleon Xerus and matching role (case sensitive) on Cisco ISE.

▶ Configure TACACS+ on Xerus:
1. Log in to PX-Series PDU with an administrative account.
2. Select Access Device Settings > Security > TACACS+ and add the Cisco ISE running the TACACS+
server. Select the Type of TACACS+ authentication types (ASCII/PAP/CHAP/MS-CHAP) as appropriate
and match the TACACS+ server.

711

3. Create Roles with appropriate permissions by accessing User Management > Roles > and clicking on
Add Role.

▶ Configure Cisco ISE:
Add the Xerus device to Cisco ISE server:
1. Access Cisco ISE Web URL https://x.x.x.x/admin and log in with administrative credentials.
2. Select Access Work Centers tab > Network Access > Network Resources. On Network Devices click.

712

3. Configure Name, Description, IP Address/Range, enable the TACACS Authentication Settings option,
set Shared secret, and click Submit to save changes. Be sure to enable Enable Single Connect Mode
option and select the TACACS Draft Compliance Single Connect Support radio button.

Create/Edit Users:
Note: If your environment already has user accounts or configured with external identity source (AD/LDAP), you may skip this step.

1. Access Work Centers > Device Administration > Identities > and click

to add a user.

713

Create TACACS Profile Policy Element:
1. On Access Work Centers tab>select Device Administration > Policy Elements > Results >TACACSProfiles and click714

to add a profile.

2. Enter Policy Name and clickunder Custom Attributes section. Then, from the Type dropdown, select option Mandatory, Attribute Name as Xerus:roles and value PDU_Admin where
PDU_Admin is the role name created locally on Xerus. (Case sensitive) then Click on
attribute then click Submit to save changes.

to addConfigure/Create Device Admin Policy Set
1. On the Work Centers tab, click Device Administration > Device Admin Policy Sets. Clickcreate a new policy set in left pane. New Policy Set 1 will be created

to

715

2. Click Edit, enter the Name, Description, and Condition (optional), and click Done. Authentication
Policy is optional unless it is explicitly required for security guidelines.

3. Create the required Authorization Policy. Next, click Edit, specify a drop-down / under Command
Sets, select the profile created earlier, and then click Done to save changes.

716

4. Clickor

to save changes.

▶ Troubleshooting Tips
Logs, and ISE reports are great references to troubleshoot the issues with configuration.
1. Verify from Live Logs under Operations> TACACS that the correct Authorization Policy is applied.
to see more information. Alternatively Choose Work Centers > Device
Click the Details icon
Administration > Reports > ISE Reports.

717

2. User authorization may fail on Xerus if an incorrect policy is applied, considering the following
options.
• Moving policy higher up in the order (in case of multiple policy sets).
• More appropriate conditions in policy coupled with device type and location when adding Xerus asa network device in Cisco ISE.

718

Updating the LDAP Schema

In This Chapter
Returning User Group Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Setting the Registry to Permit Write Operations to the Schema. . . . . . . . . . . . . . 719
Creating a New Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
Adding Attributes to the Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Updating the Schema Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Editing rciusergroup Attributes for User Members. . . . . . . . . . . . . . . . . . . . . . . . 723

Returning User Group Information
Use the information in this section to return User Group information (and assist with authorization)
once authentication is successful.

From LDAP/LDAPSWhen an LDAP/LDAPS authentication is successful, the PX-Series PDU determines the permissions for agiven user based on the permissions of the user's . Your remote LDAP server can provide these usernames by returning an attribute named as follows:
rciusergroupattribute type: string

This may require a schema extension on your LDAP/LDAPS server. Consult your authentication server
administrator to enable this attribute.
In addition, for Microsoft® Active Directory®, the standard LDAP memberOf is used.

From Microsoft Active Directory
Note: This should be attempted only by an experienced Active Directory® administrator.
Returning user information from Microsoft's® Active Directory for Windows 2000® operating system
server requires updating the LDAP/LDAPS schema. See your Microsoft documentation for details.
1. Install the schema plug-in for Active Directory. See Microsoft Active Directory documentation for
instructions.
2. Run Active Directory Console and select Active Directory Schema.

Setting the Registry to Permit Write Operations to the Schema
To allow a domain controller to write to the schema, you must set a registry entry that permits schema
updates.

719

▶ To permit write operations to the schema:
1. Right-click the Active Directory® Schema root node in the left pane of the window and then click
Operations Master. The Change Schema Master dialog appears.

2. Select the "Schema can be modified on this Domain Controller" checkbox. Optional
3. Click OK.

Creating a New Attribute▶ To create new attributes for the rciusergroup class:
1. Click the + symbol before Active Directory® Schema in the left pane of the window.
2. Right-click Attributes in the left pane.
3. Click New and then choose Attribute. When the warning message appears, click Continue and theCreate New Attribute dialog appears.

7204. Type rciusergroup in the Common Name field.
5. Type rciusergroup in the LDAP Display Name field.
6. Type 1.3.6.1.4.1.13742.50 in the Unique x5000 Object ID field.
7. Type a meaningful description in the Description field.
8. Click the Syntax drop-down arrow and choose Case Insensitive String from the list.
9. Type 1 in the Minimum field.
10. Type 24 in the Maximum field.
11. Click OK to create the new attribute.

Adding Attributes to the Class▶ To add attributes to the class:
1. Click Classes in the left pane of the window.
2. Scroll to the user class in the right pane and right-click it.

721

3.
4.
5.
6.

Choose Properties from the menu. The user Properties dialog appears.
Click the Attributes tab to open it.
Click Add.
Choose rciusergroup from the Select Schema Object list.

7. Click OK in the Select Schema Object dialog.
8. Click OK in the User Properties dialog.

722

Updating the Schema Cache▶ To update the schema cache:
1. Right-click Active Directory® Schema in the left pane of the window and select Reload the Schema.
2. Minimize the Active Directory Schema MMC (Microsoft® Management Console) console.

Editing rciusergroup Attributes for User Members
To run the Active Directory® script on a Windows 2003® server, use the script provided by Microsoft®
(available on the Windows 2003 server installation CD). These scripts are loaded onto your system witha Microsoft® Windows 2003 installation. ADSI (Active Directory Service Interface) acts as a low-level
editor for Active Directory, allowing you to perform common administrative tasks such as adding,deleting, and moving objects with a directory service.

▶ To edit the individual user attributes within the group rciusergroup:
1. From the installation CD, choose Support > Tools.
2. Double-click SUPTOOLS.MSI to install the support tools.
3. Go to the directory where the support tools were installed. Run adsiedit.msc. The ADSI Edit window
opens.

4. Open the Domain.
5. In the left pane of the window, select the CN=Users folder.

723

6. Locate the user name whose properties you want to adjust in the right pane. Right-click the username and select Properties.
7. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list.

8. Click Edit. The String Attribute Editor dialog appears.
9. Type the user (created in the PX-Series PDU) in the Edit Attribute field. Click OK.

724

Additional Xerus Information - Assorted Products

In This Chapter
Reserving IP Addresses in DHCP Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Sensor Threshold Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Default Voltage and Current Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Altitude Correction Factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Unbalanced Current Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Ways to Probe Existing User Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Role of a DNS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Installing the USB-to-Serial Driver (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Device-Specific Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
TLS Certificate Chain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739

Reserving IP Addresses in DHCP Servers
Xerus uses the product serial number as the client identifier in the DHCP request. To successfully
reserve an IP address in a DHCP server, use the device's serial number as the unique ID instead of the
MAC address.
Since all network interfaces can be simultaneously enabled and configured with diverse static IP
addresses, the client identifier of each network interface is different. The main difference is theabsence/presence of a suffix, which is the interface name added to the end of the serial number. The
table below lists the client identifiers of all network interfaces.
Interface

Client identifier

ETH1

serial number

ETH2

serial number plus the uppercase suffix "-ETH2"

WIRELESS

serial number plus the uppercase suffix "-WIRELESS"BRIDGE

serial number

You can reserve the IP addresses of more than one interfaces in the DHCP server if preferred. Note thatyou must choose/configure the bridge interface if your device is set to the bridging mode.
Important: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

Reserving IP in Windows
To reserve the IP address of any network interface in the Windows DHCP server, you must convert thatinterface's client identifier into hexadecimal ASCII codes.
In the following illustration, it is assumed that the serial number is PEG1A00003.

725

▶ Windows IP address reservation illustration:
1. Convert the client identifier of the desired network interface into ASCII codes (hexadecimal).
Interface Client identifier conversion
ETH1

PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

ETH2

PEG1A00003-ETH2 = 50 45 47 31 41 30 30 30 30 33 2D 45 54 48 32•

The suffix comprising the dash symbol and the word "ETH2" is also
converted.

WIRELESS PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45
53 53•
BRIDGEThe suffix comprising the dash symbol and the word "WIRELESS" is also
converted.

PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

1. In your DHCP server, go to the New Reservation dialog, and enter the converted ASCII codes without
spaces.
For example, to reserve the ETH1 interface's IP address, enter the following data in the dialog.
Field

Data entered

IP address

The IP address you want to reserve.

MAC address

The following ASCII codes.
50454731413030303033

Other fields

Configure as needed.

Reserving IP in Linux
There are two methods to reserve the IP address of any network interface in the standard Linux DHCP
server (ISC DHCP server):•

Convert an interface's client identifier into hexadecimal ASCII codes.

•

Use an interface's original client identifier without converting it into ASCII codes.

In the following illustrations, it is assumed that the PX-Series PDU serial number is PEG1A00003, and theIP address you want to reserve is 192.168.20.1.

▶ Illustration with ASCII code conversion:
1. Convert the client identifier of the desired network interface into ASCII codes (hexadecimal).
Interface Client identifier conversion
ETH1

PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

ETH2

PEG1A00003-ETH2 = 50 45 47 31 41 30 30 30 30 33 2D 45 54 48 32•

726

The suffix comprising the dash symbol and the word "ETH2" is also
converted.

Interface Client identifier conversion
WIRELESS PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45
53 53•
BRIDGEThe suffix comprising the dash symbol and the word "WIRELESS" is also
converted.

PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

1. Separate the converted ASCII codes with a colon, and a prefix "00:" must be added to the beginningof the converted codes.
For example, the converted client identifier of the ETH1 interface looks like the following:
00:50:45:47:31:41:30:30:30:30:33
2. Now enter the converted client identifier with the following syntax.
host mypx {option dhcp-client-identifier = 00:50:45:47:31:41:30:30:30:30:33;
fixed-address 192.168.20.1;}▶ Illustration without ASCII code conversion:
1. Use the original client identifier of the desired network interface. DO NOT convert them into ASCII
codes.
2. A prefix "\000" must be added to the beginning of the client identifier.
For example, the client identifier of the ETH1 interface looks like the following:\000PEG1A00003
3. Now enter the original client identifier with the following syntax. The client identifier is enclosed inquotation marks.
host mypx {option dhcp-client-identifier = "\000PEG1A00003";
fixed-address 192.168.20.1;}

Sensor Threshold Settings
This section explains the thresholds settings for a numeric sensor.

727

Thresholds and Sensor States
A numeric sensor has four thresholds: Lower Critical, Lower Warning, Upper Warning and Upper
Critical.
The threshold settings determine how many sensor states are available for a certain sensor and therange of each sensor state. The diagram below shows how each threshold relates to each state.

above upper critical

Upper Criticalabove upper warning

Upper Warningnormal728

Lower Warning

below lower warning

Lower Critical

below lower critical▶ Available sensor states:
The more thresholds are enabled for a sensor, the more sensor states are available for it. The "normal'
state is always available regardless of whether any threshold is enabled.
For example:•

When a sensor only has the Upper Critical threshold enabled, it has two sensor states: normal andabove upper critical.

•

When a sensor has both the Upper Critical and Upper Warning thresholds enabled, it has three
sensor states: normal, above upper warning, and above upper critical.

States of "above upper warning" and "below lower warning" are warning states to call for yourattention.
States of "above upper critical" and "below lower critical" are critical states that require you to
immediately handle.

▶ Range of each available sensor state:
The value of each enabled threshold determines the reading range of each available sensor state.

"To Assert" and Assertion Timeout
If multiple sensor states are available for a specific sensor, the PX-Series PDU asserts a state for it
whenever a bad state change occurs.

▶ To assert a state:
To assert a state is to announce a new, "worse" state.

729

Below are bad state changes that cause the PX-Series PDU to assert.
1. above upper warning --> above upper critical
2. normal --> above upper warning
3. normal --> below lower warning
4. below lower warning --> below lower critical▶ Assertion Timeout:

In the threshold settings, the Assertion Timeout field postpones the "assertion" action. It determines
how long a sensor must remain in the "worse" new state before the PX-Series PDU triggers the"assertion" action. If that sensor changes its state again within the specified wait time, the PX-Series
PDU does NOT assert the worse state.
To disable the assertion timeout, set it to 0 (zero).

730

Note: For most sensors, the measurement unit in the "Assertion Timeout" field is sample. Sensors aremeasured every second, so the timing of a sample is equal to a second. Raritan's BCM2 is an exception
to this, with a sample of 3 seconds.

▶ How "Assertion Timeout" is helpful:
If you have created an event rule that instructs the PX-Series PDU to send notifications for assertion
events, setting the "Assertion Timeout" is helpful for eliminating a number of notifications that you may
receive in case the sensor's readings fluctuate around a certain threshold.

Assertion Timeout Example for Temperature Sensors
Assumption:
Upper Warning threshold is enabled.
Upper Warning = 25 (degrees Celsius)
Assertion Timeout = 5 samples (that is, 5 seconds)
When a temperature sensor's reading exceeds 25 degrees Celsius, moving from the "normal" range tothe "above upper warning" range, the PX-Series PDU does NOT immediately announce this warningstate. Instead it waits for 5 seconds, and then does either of the following:•

If the temperature remains above 25 degrees Celsius in the "above upper warning" range for 5
seconds, the PX-Series PDU performs the "assertion" action to announce the "above upper warning"state.

•

If the temperature drops below 25 degrees Celsius within 5 seconds, the PX-Series PDU does NOT
perform the "assertion" action.

"To De-assert" and Deassertion Hysteresis
After the PX-Series PDU asserts a worse state for a sensor, it may de‑assert that state later on if thereadings improve.

▶ To de-assert a state:
To de‑assert a state is to announce the end of the previously-asserted worse state.
Below are good state changes that cause the PX-Series PDU to de‑assert the previous state.

731

1. above upper critical --> above upper warning
2. above upper warning --> normal
3. below lower warning --> normal
4. below lower critical --> below lower warning▶ Deassertion Hysteresis:

In the threshold settings, the Deassertion Hysteresis field determines a new level to trigger the"deassertion" action.
This function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system
when the temperature exceeds a pre-determined level. "Deassertion Hysteresis" instructs the PX-Series
PDU to de‑assert the worse state for a sensor only when that sensor's reading reaches the predetermined "deassertion" level.

732

For upper thresholds, this "deassertion" level is a decrease against each threshold. For lower
thresholds, this level is an increase to each threshold. The absolute value of the decrease/increase isexactly the hysteresis value.
For example, if Deassertion Hysteresis = 2, then the deassertion level of each threshold is either "+2" or"-2" as illustrated below.
Threshold value

Deassertion value

Upper Critical = 33

Deassertion level = 31•

Upper Warning = 25

Deassertion level = 23•

Lower Critical = 10

25 - 2 = 23

Deassertion level = 12•

Lower Warning = 18

33 - 2 = 31

10 + 2 = 12

Deassertion level = 20•

18 + 2 = 20

To use each threshold as the "deassertion" level instead of determining a new level, set the Deassertion
Hysteresis to 0 (zero).
Note: The difference between Upper Warning and Lower Warning must be at least "two times" of thedeassertion value.

▶ How "Deassertion Hysteresis" is helpful:
If you have created an event rule that instructs the PX-Series PDU to send notifications for deassertion
events, setting the "Deassertion Hysteresis" is helpful for eliminating a number of notifications that you
may receive in case a sensor's readings fluctuate around a certain threshold.

Deassertion Hysteresis Example for Temperature Sensors
Assumption:
Upper Warning threshold is enabled.
Upper Warning = 20 (degrees Celsius)
Deassertion Hysteresis = 3 (degrees Celsius)"Deassertion" level = 20-3 = 17 (degrees Celsius)733

When the PX-Series PDU detects that a temperature sensor's reading drops below 20 degrees Celsius,
moving from the "above upper warning" range to the "normal" range, either of the following may
occur:•

If the temperature falls between 20 and 17 degrees Celsius, the PX-Series PDU does NOT performthe "deassertion" action.

•

If the temperature drops to 17 degrees Celsius or lower, the PX-Series PDU performs the"deassertion" action to announce the end of the "above upper warning" state.

Default Voltage and Current Thresholds
The following are factory-default voltage and current thresholds. There are no default values set forlower current thresholds because lower thresholds are not useful.
Availability of diverse thresholds depends on the capability of the model you purchased.

▶ Single-phase inlets or outlets:••

RMS voltage:
Threshold

Default value

Lower critical-6% of minimum rating

Lower warning-3% of minimum rating

Upper warning+3% of maximum rating

Upper critical+6% of maximum rating

Hysteresis

2V

RMS current:
Threshold

Default value

Upper warning

65% of rating

Upper critical

80% of rating

Hysteresis

1A▶ Multi-phase inlets or outlets:•734

Line-Line RMS voltage:
Threshold

Default value

Lower critical-6% of minimum rating

Lower warning-3% of minimum rating••

Threshold

Default value

Upper warning+3% of maximum rating

Upper critical+6% of maximum rating

Hysteresis

2V

Line RMS current:
Threshold

Default value

Upper warning

65% of rating

Upper critical

80% of rating

Hysteresis

1A

Unbalanced current:
Threshold

Default value

Upper critical

10% -- disabled by default

Upper warning

5% -- disabled by default

Hysteresis

2%▶ Overcurrent protectors which aims to protect the PDU's outlets:•

OCP RMS current:
Threshold

Default value

Upper critical

80% of OCP rating

Upper warning

65% of OCP rating

Hysteresis

1A▶ Total residual current:
Threshold

Default value

Upper critical

30mA

735

Threshold

Default value

Hysteresis

15mA

Altitude Correction Factors
If a Raritan differential air pressure sensor is attached to your device, the altitude you enter for thedevice can serve as an altitude correction factor. That is, the reading of the differential air pressure
sensor will be multiplied by the correction factor to get a correct reading.
This table shows the relationship between different altitudes and correction factors.
Altitude (meters)

Altitude (feet)

Correction factor

0

0

0.95

250

820

0.98

425

1394

1.00

500

1640

1.01

740

2428

1.04

1500

4921

1.15

2250

7382

1.26

3000

9842

1.38

Unbalanced Current Calculation
Unbalanced current information is available on 3-phase models only. This section explains how PXSeries PDU calculates the unbalanced current percentage.

▶ Calculation:
1. Calculate the average current of all 3 lines.
Average current = (L1+L2+L3) / 3
2. Calculate each line's current unbalance by having each line current subtracted and divided with theaverage current.
L1 current unbalance = (L1 - average current) / average current
L2 current unbalance = (L2 - average current) / average current
L3 current unbalance = (L3 - average current) / average current
3. Determine the maximum absolute value among three lines' current unbalance values.
Maximum (|L1 current unbalance|, |L2 current unbalance|, |L3 current
unbalance|)
4. Convert the maximum value to a percentage.
Unbalanced load percent = 100 * maximum current unbalance736

▶ Example:•

Each line's current:•

L1 = 5.5 amps
L2 = 5.2 amps
L3 = 4.0 amps
Average current: (5.5+5.2+4.0) / 3 = 4.9 amps•

L1 current unbalance: (5.5 - 4.9) / 4.9 = 0.1224•

L2 current unbalance: (5.2 - 4.9) / 4.9 = 0.0612•

L3 current unbalance: (4.0 - 4.9) / 4.9 = -0.1837•

Maximum current unbalance:•

Maximum (|0.1224|, |0.0612|, |-0.1837|) = 0.1837
Current unbalance converted to a percentage:
100 * (0.1837) = 18%

Ways to Probe Existing User Profiles
This section indicates available ways to query existing user accounts on the PX-Series PDU.
•

With SNMP v3 activated, you get the "user unknown" error when the user name used toauthenticate does not exist.

•

Any user with the permission to view event rules can query all local existing users via JSON RPC.

•

Any user with the permission to view the event log may get information about existing users fromthe log entries.

•

Any authenticated users can query currently-existing connection sessions, including Webcam-LivePreview sessions, which show a list of associated user names.

Role of a DNS Server
As Internet communications are carried out on the basis of IP addresses, appropriate DNS server
settings are required for mapping domain names (host names) to corresponding IP addresses, or the PXSeries PDU may fail to connect to the given host.
Therefore, DNS server settings are important for external authentication. With appropriate DNS
settings, the PX-Series PDU can resolve the external authentication server's name to an IP address forestablishing a connection. If the SSL/TLS encryption is enabled, the DNS server settings become criticalsince only fully qualified domain name can be used for specifying the LDAP server.
For information on external authentication, see Setting Up External Authentication.

Installing the USB-to-Serial Driver (Optional)
The PX-Series PDU can emulate a USB-to-serial converter over a USB connection. A USB-to-serial driver
named "Dominion PX2 Serial Console" is required for Microsoft® Windows® operating systems.

737

Download the Windows driver for USB serial console from the Raritan website's Support page(www.raritan.com/support). The downloaded driver's name is dominion-serial-setup-<n>.exe, where<n> represents the file's version number.
There are two ways to install this driver: automatic and manual installation. Automatic driver
installation is highly recommended.

▶ Automatic driver installation in Windows®:
1. Make sure the PX-Series PDU is NOT connected to the computer via a USB cable.
2. Run dominion-serial-setup-<n>.exe on the computer and follow online instructions to install thedriver.
Note: If any Windows security warning appears, accept it to continue the installation.
3. Connect the PX-Series PDU to the computer via a USB cable. The driver is automatically installed.

▶ Manual driver installation in Windows®:
1. Make sure the PX-Series PDU has been connected to the computer via a USB cable.
2. The computer detects the new device and the "Found New Hardware Wizard" dialog appears.
• If this dialog does not appear, choose Control Panel > System > Hardware > Device Manager, rightclick the Dominion PX2 Serial Console, and choose Update Driver.
3. Select the option of driver installation from a specific location, and then specify the location where
both dominion‑serial.inf and dominion‑serial.cat are stored.
Note: If any Windows security warning appears, accept it to continue the installation.
4. Wait until the installation is complete.
Note: If the PX-Series PDU enters the disaster recovery mode when the USB serial driver is not installed
yet, it may be shown as a 'GPS camera' in the Device Manager on the computer connected to it.

▶ In Linux:
No additional drivers are required, but you must provide the name of the tty device, which can be foundin the output of the "dmesg" after connecting the PX-Series PDU to the computer. Usually the tty deviceis "/dev/ttyACM#" or "/dev/ttyUSB#," where # is an integer number.
For example, if you are using the kermit terminal program, and the tty device is "/dev/ttyACM0,"
perform the following commands:> set line /dev/ttyACM0> Connect738

Device-Specific Settings
A bulk configuration file will NOT contain any device-specific information like the following list.
For further information, simply open the built-in bulk profile for a detailed list of 'excluded' settings.
•

Device name•

SNMP system name, contact and location•

Part of network settings (IP address, gateway, netmask and so on)•

Device logs•

Names, states and values of environmental sensors and actuators•

TLS certificate•

Server monitoring entries•

Asset strip names and rack unit names•

Outlet names and states

TLS Certificate Chain
A TLS server sends out a certificate to any client attempting to connect to it. The receiver determines
whether a TLS server can be trusted by verifying that server's certificate, using the certificate (chain)stored on the receiver.
Therefore, to successfully connect to a TLS server, you must upload a valid certificate or (partial)
certificate chain to the receiver.
The uploaded certificate (chain) must contain all missing certificates "related to" that TLS server's
certificate in some way. Otherwise, the connection made to that TLS server will fail.
•For information on how the uploaded certificate (chain) is related to a TLS server's certificate, see
What is a Certificate Chain (on page ).

•For an example of creating and uploading a TLS certificate to PX-Series PDU, see Illustration - GMAIL
SMTP Certificate Chain (on page ).

What is a Certificate Chain
If you are familiar with a certificate chain, you can ignore this topic and refer to Illustration - GMAIL
SMTP Certificate Chain (on page ).
A certificate or a chain of certificates is used for trusting a TLS server that you want to connect.
The receiver, such as PX-Series PDU, can trust a TLS server only after an appropriate certificate (chain)
which is "related to" that TLS server's certificate is uploaded to the receiver.

▶ How a certificate chain is generated:
To explain how a TLS server's certificate is "related to" the certificate (chain) that is uploaded to thereceiver, we assume that there are three "related" certificates.

739

•

Certificate C. The certificate issued to the TLS server you want to connect.

•'Certificate C' is issued by the certificate authority (CA) entity called 'Issuer B'.
Certificate B. The certificate issued to 'Issuer B'.

•'Certificate B' is issued by a CA entity called 'Issuer A', and it is an intermediate certificate.
Certificate A. The self-signed certificate issued by Issuer A. Issuer A is a root CA.

The above three certificates form a certificate path, which is called the "certificate chain".

Each certificate in the chain is the issuer certificate of the certificate that follows it. That is, A is theissuer certificate of B, and B is the issuer certificate of C.
Note: In fact many certificate chains may comprise only the root certificate and a TLS server's certificate
and do not have any intermediate certificate(s) like 'Certificate B' involved. Or some chains may containmore than one intermediate certificates.

▶ Certificate (chain) that you must upload to the receiver, such as PX-Series PDU:
Because the TLS server provides only 'Certificate C', you need to upload a file containing the missing
certificates of the chain (that is, 'Certificate A' and 'Certificate B') to the receiver.

In reality some servers may provide a partial (or even a full) certificate chain instead of a single server
certificate. If your server provides a partial certificate chain containing 'Certificate B' and 'Certificate C',then you only need to upload 'Certificate A" to the receiver. If the server has a full certificate chain
containing Certificates 'A', 'B', and 'C', then you also need to upload the root certificate 'A".

740

Warning: The certificate (chain) uploaded to the receiver must always contain the ROOT certificate eventhough the TLS server provides the root certificate. When uploading a (partial) chain onto the PX-Series
PDU, it means you trust each certificate in the chain to certify the authenticity of certificates a server
sends to PX-Series PDU. Therefore, at least the root certificate must be authentic, issued by a CA you
trust, and downloaded from that CA over a secure channel. Never implicitly trust a root certificate thatis sent by the server which you want to connect to. It could have been created by an attacker.
If either certificate 'A' or 'B' is missing in the certificate file uploaded to the receiver, the connection to
the wanted TLS server will fail.

For PX-Series PDU, if any required certificate is missing, a certificate error message similar to thefollowing is shown on the PX-Series PDU web interface.

It is NOT recommended to upload the server certificate to the receiver except when it is a self-signed
certificate. Using self-signed server certificates is also not recommended and may not even work in allcases.

741

▶ Order of the chain in the certificate file:
The order of a certificate chain's content in the certificate file uploaded to the receiver must look likethe following.

•

The top is the final intermediate certificate of the chain "B" if you have to upload a partial chain.

•

The bottom is always the root certificate "A".

•When copying multiple certificates to a single file, make sure you also copy the lines of BEGIN
CERTIFICATE and END CERTIFICATE from each certificate.

Illustration - GMAIL SMTP Certificate Chain
If you will apply your company's SMTP service to PX-Series PDU, ignore this GMAIL illustration topic.
Simply contact your IT department to retrieve the appropriate certificate (chain) file and upload it to the
PX-Series PDU.
This section illustrates the upload of a TLS "root" certificate for using the "gmail.com" SMTP service.
Unlike normal TLS websites, where you can easily find its server certificate by using a Web browser, themethod to find an SMTP server's certificate is more difficult, which requires appropriate tools andsufficient technical knowledge. For example, you may have to use the openssl command as illustrated
below to retrieve the certificate of the GMAIL SMTP server.

▶ Step 1 -- Find the certificate(s) the SMTP server has:
1. Issue the following command in the appropriate command line application.
• In the following example command, we assume the server "smtp.gmail.com" provides the SMTP
service. You can change the server name, port number, command or even the tool as needed.
openssl s_client -showcerts -connect smtp.gmail.com:465

Alternative: To view the certificate chain instead of all certificates, you can remove the "-showcerts"
option from the above command.
2. Information that shows the certificates the SMTP server has is displayed.

742

.
.
.
Certificate chain
0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com
i:/C=US/O=Google Inc/CN=Google Internet Authority G2-----BEGIN CERTIFICATE----MIIEdjCCA16gAwIBAgIIbzO9vIL2OXcwDQYJKoZIhvcNAQELBQAwSTELMAkGA1UE.
.
YHKKJH96sSNC+6dLpOOoRritL5z+jn2WFLcQkL2mRoWQi6pYTzPyXB4D-----END CERTIFICATE----1 s:/C=US/O=Google Inc/CN=Google Internet Authority G2
i:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA-----BEGIN CERTIFICATE----MIIEKDCCAxCgAwIBAgIQAQAhJYiw+lmnd+8Fe2Yn3zANBgkqhkiG9w0BAQsFADBC.
.
MqO5tzHpCvX2HzLc-----END CERTIFICATE----2 s:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
i:/C=US/O=Equifax/OU=Equifax Secure Certificate Authority-----BEGIN CERTIFICATE----MIIDfTCCAuagAwIBAgIDErvmMA0GCSqGSIb3DQEBBQUAME4xCzAJBgNVBAYTAlVT.
.
b8ravHNjkOR/ez4iyz0H7V84dJzjA1BOoa+Y7mHyhD8S-----END CERTIFICATE------Server certificate
subject=/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com
issuer=/C=US/O=Google Inc/CN=Google Internet Authority G2.
.
.

3. Onscreen information under the title 'Certificate chain' indicates that there are three issuers andthree certificates on this server.
• Each line beginning with the letter "i" indicates an issuer. They are:743

▪ Google Internet Authority G2▪ GeoTrust Global CA▪ Equifax Secure Certificate Authority• Each certificate begins with the line "BEGIN CERTIFICATE" and ends with the line "ENDCERTIFICATE".
• The topmost certificate is the server certificate.
4. The section titled "Server certificate" indicates that the issuer (CA) Google Internet Authority G2
issues the server certificate.
5. As the server has the server certificate and two intermediate certificates, we conclude that thisserver sends a partial certificate chain to the receiver.
6. Check whether the issuer "Equifax Secure Certificate Authority" is the root CA.
• If yes, you only need to upload the root certificate self-signed by Equifax Secure Certificate
Authority to PX-Series PDU.
• If not, you need to find all missing issuer certificates, including the root certificate, and uploadthem to PX-Series PDU.

▶ Step 2 -- Find and download the content of missing issuer certificate(s):1. View the name of the issuer (CA) at the bottom. In this example, this issuer is 'Equifax Secure
Certificate Authority'.
2. Use the issuer's name 'Equifax Secure Certificate Authority' to search for its certificate on theInternet, and then download or copy the content from an authentic source, which is usually its
official website.
Important: To prevent the downloaded certificate from being modified or manipulated, you must secure
the download with TLS via a trusted certificate.
3. As it is found the Equifax Secure Certificate Authority's certificate is self signed by 'Equifax Secure
Certificate Authority', which indicates it is the root CA, there are no more missing certificates tosearch for.

▶ Step 3 -- Upload the missing certificate(s) to PX-Series PDU:
1. Paste the root certificate's content into a plain text file that will be uploaded to PX-Series PDU.
• Content copying must include the lines of "BEGIN CERTIFICATE" and "END CERTIFICATE".
2. Save that file as a .pem, .crt or .cer file. In this example, it is named as "my-root.pem."
3. Upload the file "my-root.pem" to PX-Series PDU for using the GMAIL SMTP service.
Note: If your SMTP server requires the upload of a certificate file comprising multiple certificates, makesure the order of these certificates is correct in the file. See What is a Certificate Chain (on page ).

744

▶ IMPORTANT NOTE:
If your SMTP server provides a full certificate chain, you should be suspicious whether any attacker
fakes the certificate chain and doubt whether the root certificate on that server is authentic. It is
STRONGLY recommended to download the root certificate from an authentic source, which is usually
the root CA's website, rather than from the server you want to connect.

Xerus Product Integration
This section contains information about possible integrations of Xerus products with other Legrand,
Raritan, Server Technology, or third-party products to provide diverse power solutions. Not all Xerus
products support all integrations.

Connecting a PDU to a Dominion KVM or Serial Device
Some Xerus- firmware PDUs can be integrated with Raritan KVM or Serial devices.

▶ PDU connection via Feature port (only for PX2, PX3 or PX3TS devices)
Raritan PX series rack PDUs can be connected to the Dominion device using the D2CIM-PWR CIM.

▶ To connect the rack PDU:
1. Connect the RJ-45 of the D2CIM-PWR to the RJ-45 connector of the rack PDU.
• PX2, PX3 or PX3TS series: RJ-45 "FEATURE" port
2. Connect the RJ-45 connector of the D2CIM-PWR to any of the available system port connectors on
the KX III using a straight through Cat5 cable.
3. Attach an AC power cord to the target server and an available rack PDU outlet.
4. Connect the rack PDU to an AC power source.
5. Power on the device.

Diagram key
Rack PDU745

D2CIM-PWR

KX III

D2CIM-PWR to rack PDU connection

D2CIM-PWR to KX III target device port via Cat5 cable▶ PDU connection via USB port (only for PRO4X and PX4 devices)
PRO3X, PRO4X and PX4 devices do not have a feature port, so the connection to a Power CIM peer canbe achieved through an USB dongle (DSER-PWR-USB-G4 and DKX3-PWR-USB-G4) and a USB-A port. You
can use SNMP protocol to communicate to the Raritan KVM or serial devices.
Note: Power CIM peer stands for either a Raritan KVM switch (KX2, KX3 via D2CIM-PWR) or a Raritan
serial switch (SX2, KSX2).

▶ To connect the PDU:
1. Connect the Power CIM (DSER-PWR-USB-G4 or DKX3-PWR-USB-G4 or DSER-CLI-USB-G4) to a USB-A
port of the PDU.
2. Connect Cat5 cable to the Power CIM (DKX3-PWR-USB) and to the Raritan KVM or connect RS232(RJ45) cable to the Power CIM (DSER-PWR-USB) and to the Raritan Serial device or connect RS232(RJ45) cable to the Power CIM (DSER-CLI-USB) and to the Raritan Serial device.
3. Attach an AC power cord to the target server and an available the PDU outlet.
4. Connect the PDU to an AC power source.
5. Power on the device.

Power IQ Configuration
Sunbird's Power IQ is a software application that collects and manages the data from different PDUs
installed in your server room or data center. With this software, you can:•Do bulk configuration for multiple PDUs•

Name outlets on different PDUs•

Switch on/off outlets on outlet-switching capable PDUs

For more information on Power IQ, refer to the Power IQ online help on the Sunbird website: http://
support.sunbirddcim.com.

746

dcTrack
Sunbird's dcTrack® is a product that allows you to manage the data center. The PX-Series PDU iscategorized as a power item in dcTrack.
You can use dcTrack to:•

Record and manage the data center infrastructure and assets•

Monitor the electrical consumption of the data center•

Track environmental factors in the data center, such as temperature and humidity•

Optimize the data center growth

For more information on dcTrack, refer to the online help accessible from the dcTrack application, oruser documentation available on the Sunbird's website: http://support.sunbirddcim.com.

Asset Management Strips and dcTrack
If any asset strips are connected to the PX-Series PDU, the PX-Series PDU can transmit their information
to Sunbird's dcTrack. Add the PX-Series PDU to dcTrack, and also add each IT item where an asset tag is
attached to dcTrack.
If SNMP is enabled, event information can be transmitted to dcTrack. Specifically, Sunbird's Power IQ
detects when an asset tag is connected or disconnected from an asset strip. Power IQ then generates aconnection or disconnection event. When dcTrack polls Power IQ, the connection/disconnection eventsare pulled into dcTrack, and displayed in the dcTrack Web Client.

▶ To poll and display asset management events in dcTrack•

The PX-Series PDU that the asset strip is connected to must exist in dcTrack.

•

Each IT item connected to the asset strip via an asset tag must exist in dcTrack.
You do not need to manually enter the asset tag IDs for IT items that already exist in
dcTrack as long as these items are in the Installed status.
Plug the item's asset tag into an asset strip that is connected to the PX-Series PDU thatexists in dcTrack. dcTrack automatically assigns the asset tag ID to the existing IT item.

747Third Party Licenses
This appendix contains third party licenses for software used by Xerus that require including the license
in documentation.
For information on open source software, see raritan.com/about-us/legal/open-source-softwarestatement

In This Chapter
Licenses - Angular. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Licenses - Bind9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
Licenses - Clish. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Licenses - Dropbear. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Licenses - FreeType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
Licenses - IW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
Licenses - JSON-C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
Licenses - LIBTIRPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
Licenses - LIBXML2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
Licenses - Mbus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
Licenses - Net-SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
Licenses - Open LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Licenses - OpenSSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
Licenses - Wireless-RegDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
Licenses - WPA Supplicant and Hostapd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783

Licenses - Angular@angular-devkit/build-angular
MIT
The MIT License
Copyright (c) 2017 Google, Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions: The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

748

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
@angular-devkit/coreMIT
The MIT License
Copyright (c) 2017 Google, Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions: The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
@angular/animations
MIT@angular/cdk
MIT
The MIT License
Copyright (c) 2021 Google LLC.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions: The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

749

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
@angular/common
MIT@angular/coreMIT@angular/forms
MIT@angular/material
MIT
The MIT License
Copyright (c) 2021 Google LLC.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
@angular/platform-browser
MIT@angular/router
MIT

750

@babel/runtime
MIT
MIT License
Copyright (c) 2014-present Sebastian McKenzie and other contributors Permission is hereby granted,
free of charge, to any person obtaining a copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
@ctrl/ngx-chartjs
MIT
MIT License
Copyright (c) Scott Cooper <scttcper@gmail.com>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
@ngx-translate/coreMITchart.js

751

MITThe MIT License (MIT)Copyright (c) 2018 Chart.js Contributors
Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
core-jsMIT
Copyright (c) 2014-2021 Denis Pushkarev
Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
regenerator-runtime
MIT
MIT License
Copyright (c) 2014-present, Facebook, Inc.

752

Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
rxjs
Apache-2.0
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by
Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting
the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled
by, or are under common control with that entity. For the purposes of this definition, "control" means (i)the power, direct or indirect, to cause the direction or management of such entity, whether by contract
or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial
ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited tosoftware source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source
form, including but not limited to compiled object code, generated documentation, and conversions toother media types.

753

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the
License, as indicated by a copyright notice that is included in or attached to the work (an example isprovided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derivedfrom) the Work and for which the editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works
shall not include works that remain separable from, or merely link (or bind by name) to the interfacesof, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any
modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to
Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized
to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any
form of electronic, verbal, or written communication sent to the Licensor or its representatives,
including but not limited to communication on electronic mailing lists, source code control systems, andissue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing
and improving the Work, but excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution.""Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution
has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor
hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform,
sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby
grants to You a perpetual,worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent
license to make, have made,use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to thosepatent claims licensable
by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of
their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent
litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Workor a Contribution incorporated within the Work constitutes direct or contributory patent infringement,
then any patent licenses granted to You under this License for that Work shall terminate as of the datesuch litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof inany medium, with or without modifications, and in Source or Object form, provided that You meet thefollowing conditions:(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and(b) You must cause any modified files to carry prominent notices stating that You changed the files; and754

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,
trademark, and attribution notices from the Source form of the Work, excluding those notices that do
not pertain to any part of the Derivative Works; and(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that
You distribute must include a readable copy of the attribution notices contained within such NOTICE file,
excluding those notices that do not pertain to any part of the Derivative Works, in at least one of thefollowing places: within a NOTICE text file distributed as part of the Derivative Works; within the Source
form or documentation, if provided along with the Derivative Works; or, within a display generated by
the Derivative Works, if and wherever such third-party notices normally appear. The contents of the
NOTICE file are for informational purposes only anddo not modify the License. You may add Your own attribution notices within Derivative Works that You
distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such
additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional ordifferent license terms and conditions for use, reproduction, or distribution of Your modifications, or forany such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Workotherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionallysubmitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license
agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service
marks, or product names of the Licensor, except as required for reasonable and customary use indescribing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides
the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIESOR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties
or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULARPURPOSE. You are solely responsible for determining the appropriateness of using or redistributing theWork and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence),
contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts)
or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect,
special, incidental, or consequential damages of any character arising as a result of this License or out of
the use or inability to use the Work (including but not limited to damages for loss of goodwill, work
stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if
such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof,
You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or otherliability obligations and/or rights consistent with this License. However, in accepting such obligations,
You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other755

Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any
liability incurred by, or claims asserted against, such Contributor by reason of your accepting any suchwarranty or additional liability.
END OF TERMS AND CONDITIONSAPPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields
enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!)
The text should be enclosed in the appropriate comment syntax for the file format. We also recommendthat a file or class name and description of purpose be included on the same "printed page" as the
copyright notice for easier identification within third-party archives.
Copyright (c) 2015-2018 Google, Inc., Netflix, Inc., Microsoft Corp. and contributors
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except incompliance with the License.
You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License isdistributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
or implied.
See the License for the specific language governing permissions and limitations under the License.
tslib
0BSD
Copyright (c) Microsoft Corporation.
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is
hereby granted.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
zone.js
MIT
The MIT License
Copyright (c) 2010-2020 Google LLC. https://angular.io/license

756Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORTOR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

Licenses - Bind9
Copyright (C) 2004-2016 Internet Systems Consortium, Inc. ("ISC")
Copyright (C) 1996-2003 Internet Software Consortium.
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby
granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWAREINCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTINGFROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Portions of this code release fall under one or more of the following Copyright notices. Please see individual source
files for details.
For binary releases also see: OpenSSL-LICENSE.
Copyright (C) 1996-2001 Nominum, Inc.
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted,
provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND NOMINUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THISSOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALLNOMINUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.
----------------------------------------------------------------------------Copyright (C) 1995-2000 by Network Associates, Inc.
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby
granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND ISC AND NETWORK ASSOCIATES DISCLAIMS ALL WARRANTIES WITHREGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.
-----------------------------------------------------------------------------

757

Copyright (C) 2002 Stichting NLnet, Netherlands, stichting@nlnet.nl.
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted,
provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND STICHTING NLNET DISCLAIMS ALL WARRANTIES WITH REGARD TO THISSOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
STICHTING NLNET BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.
The development of Dynamically Loadable Zones (DLZ) for Bind 9 was conceived and contributed by Rob Butler.
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted,
provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND ROB BUTLER DISCLAIMS ALL WARRANTIES WITH REGARD TO THISSOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ROB
BUTLER BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.
----------------------------------------------------------------------------Copyright (c) 1987, 1990, 1993, 1994
The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------------Copyright (C) The Internet Society 2005. This version of this module is part of RFC 4178; see the RFC itself for fulllegal notices.
(The above copyright notice is per RFC 3978 5.6 (a), q.v.)----------------------------------------------------------------------------Copyright (c) 2004 Masarykova universita(Masaryk University, Brno, Czech Republic)
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.

758

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------------Copyright (c) 1997 - 2003 Kungliga Tekniska Hogskolan(Royal Institute of Technology, Stockholm, Sweden).
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the Institute nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE INSTITUTE AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE INSTITUTE OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------------Copyright (c) 1998 Doug Rabson
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-----------------------------------------------------------------------------

759

Copyright ((c)) 2002, Rice University
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of Rice University (RICE) nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
This software is provided by RICE and the contributors on an "as is" basis, without any representations or
warranties of any kind, express or implied including, but not limited to, representations or warranties of noninfringement, merchantability or fitness for a particular purpose. In no event shall RICE or contributors be liable forany direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to,
procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused
and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arisingin any way out of the use of this software, even if advised of the possibility of such damage.
----------------------------------------------------------------------------Copyright (c) 1993 by Digital Equipment Corporation.
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted,
provided that the above copyright notice and this permission notice appear in all copies, and that the name of
Digital Equipment Corporation not be used in advertising or publicity pertaining to distribution of the document orsoftware without specific, written prior permission.
THE SOFTWARE IS PROVIDED "AS IS" AND DIGITAL EQUIPMENT CORP. DISCLAIMS ALL WARRANTIES WITH REGARD
TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENTSHALL DIGITAL EQUIPMENT CORPORATION BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE
USE OR PERFORMANCE OF THIS SOFTWARE.
----------------------------------------------------------------------------Copyright 2000 Aaron D. Gifford. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) AND CONTRIBUTOR(S) ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR(S) OR CONTRIBUTOR(S) BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------------Copyright (c) 1998 Doug Rabson.
Copyright (c) 2001 Jake Burkholder.

760

All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------------Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------------Copyright (c) 1999-2000 by Nortel Networks Corporation
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted,
provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND NORTEL NETWORKS DISCLAIMS ALL WARRANTIES WITH REGARD TO THISSOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALLNORTEL NETWORKS BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.
----------------------------------------------------------------------------Copyright (c) 2000-2002 Japan Network Information Center. All rights reserved.
By using this file, you agree to the terms and conditions set forth bellow.
LICENSE TERMS AND CONDITIONS

761

The following License Terms and Conditions apply, unless a different license is obtained from Japan Network
Information Center ("JPNIC"), a Japanese association, Kokusai-Kougyou-Kanda Bldg 6F, 2-3-4 Uchi-Kanda, Chiyodaku, Tokyo 101-0047, Japan.
1. Use, Modification and Redistribution (including distribution of any modified or derived work) in source and/or
binary forms is permitted under this License Terms and Conditions.
2. Redistribution of source code must retain the copyright notices as they appear in each source code file, thisLicense Terms and Conditions.
3. Redistribution in binary form must reproduce the Copyright Notice, this License Terms and Conditions, in the
documentation and/or other materials provided with the distribution. For the purposes of binary distribution the"Copyright Notice" refers to the following language:"Copyright (c) 2000-2002 Japan Network Information Center. All rights reserved."
4. The name of JPNIC may not be used to endorse or promote products derived from this Software without specificprior written approval of JPNIC.
5. Disclaimer/Limitation of Liability: THIS SOFTWARE IS PROVIDED BY JPNIC "AS IS" AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JPNIC BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
----------------------------------------------------------------------------Copyright (C) 2004 Nominet, Ltd.
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted,
provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND NOMINET DISCLAIMS ALL WARRANTIES WITH REGARD TO THISSOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE
LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVERRESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHERTORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
----------------------------------------------------------------------------Portions Copyright RSA Security Inc.
License to copy and use this software is granted provided that it is identified as "RSA Security Inc. PKCS #11
Cryptographic Token Interface (Cryptoki)" in all material mentioning or referencing this software.
License is also granted to make and use derivative works provided that such works are identified as "derived fromthe RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki)" in all material mentioning or referencing
the derived work.
RSA Security Inc. makes no representations concerning either the merchantability of this software or the suitabilityof this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind.
----------------------------------------------------------------------------Copyright (c) 1996, David Mazieres <dm@uun.org>
Copyright (c) 2008, Damien Miller <djm@openbsd.org>
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted,
provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THISSOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.

762

----------------------------------------------------------------------------Copyright (c) 2000-2001 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://
www.OpenSSL.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived
from this software without prior written permission. For written permission, please contact
licensing@OpenSSL.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names
without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://
www.OpenSSL.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------------Copyright (c) 1995, 1997, 1998 The NetBSD Foundation, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Licenses - Clish
This package contains code which is copyrighted to multiple sources. The initial public release of this software wasdeveloped by Graeme McKerrell whilst in the employment of 3Com Europe Ltd.
Copyright (c) 2005, 3Com Corporation

763

All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of 3Com Corporation nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Newport Networks Ltd.
The 0.6-0.7 releases of this software was developed by Graeme McKerrell whilst in the employment of Newport
Networks Ltd.
As well as enhancing the existing code the following new modules were developed.
Copyright (c) 2005,2006, Newport Networks Ltd
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of Newport Networks Ltd nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
tinyxml
Yves Berquin
As of release 0.6 the tinyxml library is included (unchanged) as part of the distribution.
tinyxml (v2.5.1)
http://www.sourceforge.net/projects/tinyxml
Original file by Yves Berquin.
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable
for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and toalter it and redistribute it freely, subject to the following restrictions:764

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software.
If you use this software in a product, an acknowledgment in the product documentation would be appreciated but
is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original
software.
3. This notice may not be removed or altered from any source distribution.
GNU binutils
As of release 0.7.1 libbfd can be used to resolve symbols forstacktraces. This feature can be turned off if linking withGPL code is problematic, using "configure --without-gpl".
The Binary File Descriptor library is part of GNU binutils
http://www.gnu.org/software/binutils/
The following file is licensed under the GPLv2.
This file is part of the CLISH project http://clish.sourceforge.net/
The code in this file is free software; you can redistribute it and/or modify it under the terms of the GNU General
Public License as published by the Free Software Foundation; version 2
This code is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License formore details.
You should have received a copy of the GNU General Public License along with this program; if not, write to theFree Software Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
Derived from addr2line.c in the GNU binutils package by Ulrich.Lauther@mchp.siemens.de
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is notallowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the
GNU General Public License is intended to guarantee your freedom to share and change free software--to makesure the software is free for all its users. This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to using it. (Some other Free Software
Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to yourprograms, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed
to make sure that you have the freedom to distribute copies of free software (and charge for this service if youwish), that you receive source code or can get it if you want it, that you can change the software or use pieces of itin new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you tosurrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of thesoftware, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all
the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show
them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you
legal permission to copy, distribute and/or modify the software.

765

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no
warranty for this free software. If the software is modified by someone else and passed on, we want its recipients
to know that what they have is not the original, so that any problems introduced by others will not reflect on theoriginal authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that
redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To
prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
GNU GENERAL PUBLIC LICENSETERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying
it may be distributed under the terms of this General Public License. The "Program", below, refers to any suchprogram or work, and a "work based on the Program" means either the Program or any derivative work undercopyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications
and/or translated into another language. (Hereinafter, translation is included without limitation in the term
"modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License; they are outside its
scope. The act of running the Program is not restricted, and the output from the Program is covered only if its
contents constitute a work based on the Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium,provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice anddisclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; andgive any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty
protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the
Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided thatyou also meet all of these conditions:a) You must cause the modified files to carry prominent notices stating that you changed the files and the date ofany change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from theProgram or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of thisLicense.
c) If the modified program normally reads commands interactively when run, you must cause it, when started
running for such interactive use in the most ordinary way, to print or display an announcement including anappropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty)
and that users may redistribute the program under these conditions, and telling the user how to view a copy of thisLicense. (Exception: if the Program itself is interactive but does not normally print such an announcement, yourwork based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived
from the Program, and can be reasonably considered independent and separate works in themselves, then thisLicense, and its terms, do not apply to those sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based on the Program, the distribution of the wholemust be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus toeach and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather,
the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work basedon the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of
this License.

766

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executableform under the terms of Sections 1 and 2 above provided that you also do one of the following:a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under
the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany itwith a written offer, valid for at least three years, to give any third party, for a charge no more than your cost ofphysically performing source distribution, a complete machine-readable copy of the corresponding source code, tobe distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange;or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (Thisalternative is allowed only for noncommercial distribution and only if you received the program in object code or
executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executablework, complete source code means all the source code for all modules it contains, plus any associated interface
definition files, plus the scripts used to control compilation and installation of the executable. However, as a special
exception, the source code distributed need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the operating system on which theexecutable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, thenoffering equivalent access to copy the source code from the same place counts as distribution of the source code,even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License.
Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automaticallyterminate your rights under this License. However, parties who have received copies, or rights, from you under thisLicense will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you
permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you
do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying,
distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives
a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions.
You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are notresponsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited
to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict
the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distributeso as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as aconsequence you may not distribute the Program at all. For example, if a patent license would not permit royaltyfree redistribution of the Program by all those who receive copies directly or indirectly through you, then the only
way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of thesection is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest
validity of any such claims; this section has the sole purpose of protecting the integrity of the free software
distribution system, which is implemented by public license practices. Many people have made generous
contributions to the wide range of software distributed through that system in reliance on consistent application ofthat system; it is up to the author/donor to decide if he or she is willing to distribute software through any othersystem and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted
interfaces, the original copyright holder who places the Program under this License may add an explicit
geographical distribution limitation excluding those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of thisLicense.

767

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time
to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new
problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License
which applies to it and "any later version", you have the option of following the terms and conditions either of thatversion or of any later version published by the Free Software Foundation. If the Program does not specify a version
number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions aredifferent, write to the author to ask for permission. For software which is copyrighted by the Free Software
Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be
guided by the two goals of preserving the free status of all derivatives of our free software and of promoting thesharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE
EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS
AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSEDOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR
OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHTHOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE,
BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGESARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA ORDATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE
PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS

Licenses - Dropbear
Dropbear contains a number of components from different sources, hence there are a few licenses and authors
involved. All licenses are fairly non-restrictive.
The majority of code is written by Matt Johnston, under the license below.
Portions of the client-mode work are (c) 2004 Mihnea Stoenescu, under the same license:
Copyright (c) 2002-2015 Matt Johnston
Portions copyright (c) 2004 Mihnea Stoenescu
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
=====
LibTomCrypt and LibTomMath are written by Tom St Denis, and are Public Domain.

768

=====
sshpty.c is taken from OpenSSH 3.5p1,
Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
All rights reserved"As far as I am concerned, the code I have written for this software can be used freely for any purpose. Any derived
versions of this software must be clearly marked as such, and if the derived work is incompatible with the protocol
description in the RFC file, it must be called by a name other than "ssh" or "Secure Shell". "=====loginrec.cloginrec.hatomicio.h
atomicio.cand strlcat() (included in util.c) are from OpenSSH 3.6.1p2, and are licensed under the 2 point BSD license.
loginrec is written primarily by Andre Lucas, atomicio.c by Theo de Raadt.
strlcat() is (c) Todd C. Miller=====
Import code in keyimport.c is modified from PuTTY's import.c, licensed as follows:
PuTTY is copyright 1997-2003 Simon Tatham.
Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong,
Nicolas Barry, Justin Bradford, and CORE SDI S.A.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
=====
curve25519-donna:/* Copyright 2008, Google Inc.
* All rights reserved.
** Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:*
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.

769

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
* curve25519-donna: Curve25519 elliptic curve, public key function* http://code.google.com/p/curve25519-donna/* Adam Langley <agl@imperialviolet.org>* Derived from public domain C code by Daniel J. Bernstein <djb@cr.yp.to>* More information about curve25519 can be found here
* http://cr.yp.to/ecdh.html* djb's sample implementation of curve25519 is written in a special assembly language called qhasm and uses thefloating point registers.
* This is, almost, a clean room reimplementation from the curve25519 paper. It uses many of the tricks described
therein. Only the crecip function is taken from the sample implementation.

Licenses - FreeType
The FreeType Project LICENSE
2006-Jan-27
Copyright 1996-2002, 2006 by
David Turner, Robert Wilhelm, and Werner Lemberg
Introduction============The FreeType Project is distributed in several archive packages; some of them may contain, in addition to the
FreeType font engine, various tools and contributions which rely on, or relate to, the FreeType Project.
This license applies to all files found in such packages, and which do not fall under their own explicit license. The
license affects thus the FreeType font engine, the test programs, documentation and makefiles, at the very least.
This license was inspired by the BSD, Artistic, and IJG (Independent JPEG Group) licenses, which all encourage
inclusion and use of free software in commercial and freeware products alike. As a consequence, its main points arethat:o We don't promise that this software works. However, we will be interested in any kind of bug reports. (`as is'
distribution)o You can use this software for whatever you want, in parts or full form, without having to pay us. (`royalty-free'usage)o You may not pretend that you wrote this software. If you use it, or only parts of it, in a program, you mustacknowledge somewhere in your documentation that you have used the FreeType code. (`credits')
We specifically permit and encourage the inclusion of this software, with or without modifications, in commercial
products.
We disclaim all warranties covering The FreeType Project and assume no liability related to The FreeType Project.
Finally, many people asked us for a preferred form for a credit/disclaimer to use in compliance with this license. We
thus encourage you to use the following text:
Portions of this software are copyright <year> The FreeType Project (www.freetype.org). All rights reserved.
Please replace <year> with the value from the FreeType version you actually use.
Legal Terms

770

===========
0. Definitions-------------Throughout this license, the terms `package', `FreeType Project', and `FreeType archive' refer to the set of files
originally distributed by the authors (David Turner, Robert Wilhelm, and Werner Lemberg) as the `FreeType Project',be they named as alpha, beta or final release.
`You' refers to the licensee, or person using the project, where `using' is a generic term including compiling the
project's source code as well as linking it to form a `program' or `executable'.
This program is referred to as `a program using the FreeType engine'.
This license applies to all files distributed in the original FreeType Project, including all source code, binaries anddocumentation, unless otherwise stated in the file in its original, unmodified form as distributed in the originalarchive.
If you are unsure whether or not a particular file is covered by this license, you must contact us to verify this.
The FreeType Project is copyright (C) 1996-2000 by David Turner, Robert Wilhelm, and Werner Lemberg. All rights
reserved except as specified below.
1. No Warranty-------------THE FREETYPE PROJECT IS PROVIDED `AS IS' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT WILL ANY OF THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY DAMAGES CAUSED BY THE
USE OR THE INABILITY TO USE, OF THE FREETYPE PROJECT.
2. Redistribution----------------This license grants a worldwide, royalty-free, perpetual and irrevocable right and license to use, execute, perform,
compile, display, copy, create derivative works of, distribute and sublicense the FreeType Project (in both source
and object code forms) and derivative works thereof for any purpose; and to authorize others to exercise some or
all of the rights granted herein, subject to the following conditions:o Redistribution of source code must retain this license file (`FTL.TXT') unaltered; any additions, deletions orchanges to the original files must be clearly indicated in accompanying documentation. The copyright notices of theunaltered, original files must be preserved in all copies of source files.
o Redistribution in binary form must provide a disclaimer that states that the software is based in part of the workof the FreeType Team, in the distribution documentation. We also encourage you to put an URL to the FreeType
web page in your documentation, though this isn't mandatory.
These conditions apply to any software derived from or based on the FreeType Project, not just the unmodified
files. If you use our work, you must acknowledge us. However, no fee need be paid to us.
3. Advertising-------------Neither the FreeType authors and contributors nor you shall use the name of the other for commercial, advertising,or promotional purposes without specific prior written permission.
We suggest, but do not require, that you use one or more of the following phrases to refer to this software in yourdocumentation or advertising materials: `FreeType Project', `FreeType Engine', `FreeType library', or `FreeTypeDistribution'.
As you have not signed this license, you are not required to accept it. However, as the FreeType Project is
copyrighted material, only this license, or another one contracted with theauthors, grants you the right to use, distribute, and modify it. Therefore, by using, distributing, or modifying the
FreeType Project, you indicate that you understand and accept all the terms of this license.
4. Contacts-----------

771

There are two mailing lists related to FreeType:o freetype@nongnu.org
Discusses general use and applications of FreeType, as well as future and wanted additions to the library anddistribution. If you are looking for support, start in this list if you haven't found anything to help you in the
documentation.
o freetype-devel@nongnu.org
Discusses bugs, as well as engine internals, design issues, specific licenses, porting, etc.
Our home page can be found at http://www.freetype.org

Licenses - IW
Copyright (c) 2007, 2008 Johannes Berg
Copyright (c) 2007 Andy Lutomirski
Copyright (c) 2007 Mike Kershaw
Copyright (c) 2008-2009 Luis R. Rodriguez
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby
granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THISSOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.

Licenses - JSON-C
Copyright (c) 2009-2012 Eric Haszlakiewicz
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
---------------------------------------------------------------Copyright (c) 2004, 2005 Metaparadigm Pte Ltd
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.

772

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Licenses - LIBTIRPC
Copyright (c) Copyright (c) Bull S.A. 2005 All Rights Reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

Licenses - LIBXML2
Except where otherwise noted in the source code (e.g. the files hash.c, list.c and the trio files, which are covered bya similar licence but with different Copyright notices) all the files are:Copyright (C) 1998-2012 Daniel Veillard. All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Licenses - Mbus
Copyright (c) 2002-2003, 2013-2019 Victor Antonovich (v.antonovich@gmail.com)
Copyright (c) 2011 Andrew Denysenko <nitr0@seti.kr.ua>
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.

773

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Licenses - Net-SNMP
Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read all
the parts.
Part 1: CMU/UCD copyright notice: (BSD like) ----Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000
Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee
is hereby granted, provided that the above copyright notice appears in all copies and that both that copyrightnotice and this permission notice appear in supporting documentation, and that the name of CMU and The Regentsof the University of California not be used in advertising or publicity pertaining to distribution of the software
without specific written permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THISSOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU
OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN
AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
THE USE OR PERFORMANCE OF THIS SOFTWARE.
Part 2: Networks Associates Technology, Inc copyright notice (BSD) ----Copyright (c) 2001-2003, Networks Associates Technology, Inc
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used toendorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

774

DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 3: Cambridge Broadband Ltd. copyright notice (BSD) ----Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from thissoftware without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 4: Sun Microsystems, Inc. copyright notice (BSD) ----Copyright (c) 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights
reserved.
Use is subject to license terms below.
This distribution may include materials developed by third parties.
Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc.
in the U.S. and other countries.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 5: Sparta, Inc copyright notice (BSD) ----Copyright (c) 2003-2013, Sparta, Inc
All rights reserved.

775

Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Sparta, Inc nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 6: Cisco/BUPTNIC copyright notice (BSD) ----Copyright (c) 2004, Cisco, Inc and Information Network
Center of Beijing University of Posts and Telecommunications.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Cisco, Inc, Beijing University of Posts and Telecommunications, nor the names of theircontributors may be used to endorse or promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS;OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 7: Fabasoft R&D Software GmbH & Co KG copyright notice (BSD) ----Copyright (c) Fabasoft R&D Software GmbH & Co KG, 2003
oss@fabasoft.com
Author: Bernhard Penz <bernhard.penz@fabasoft.com>
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
The name of Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names may not be
used to endorse or promote products derived from this software without specific prior written permission.

776

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 8: Apple Inc. copyright notice (BSD) ----Copyright (c) 2007 Apple Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of Apple Inc. ("Apple") nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY APPLE AND ITS CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL APPLE OR ITS CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 9: ScienceLogic, LLC copyright notice (BSD) ----Copyright (c) 2009, ScienceLogic, LLC
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of ScienceLogic, LLC nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 10: Lennart Poettering copyright notice (BSD-like) ----Copyright 2010 Lennart Poettering

777Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Part 11: IETF copyright notice (BSD) ----Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution. Neither the name ofInternet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 12: Arista Networks copyright notice (BSD) ---Copyright (c) 2013, Arista Networks, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Arista Networks, Inc. nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 13: VMware, Inc. copyright notice (BSD) ----Copyright (c) 2016, VMware, Inc.

778

All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of VMware, Inc. nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
Part 14: USC/Information Sciences Institute copyright notice (BSD) ----Copyright (c) 2017-2018, Information Sciences InstituteAll rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Information Sciences Institue nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Licenses - Open LDAP
Copyright 1998-2019 The OpenLDAP Foundation
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized
by the OpenLDAP Public License.
A copy of this license is available in the file LICENSE in the top-level directory of the distribution or, alternatively, at<http://www.OpenLDAP.org/license.html>.
OpenLDAP is a registered trademark of the OpenLDAP Foundation.
Individual files and/or contributed packages may be copyright by other parties and/or subject to additional
restrictions.

779

This work is derived from the University of Michigan LDAP v3.3 distribution. Information concerning this software isavailable at <http://www.umich.edu/~dirsvcs/ldap/ldap.html>.
This work also contains materials derived from public sources. Additional information about OpenLDAP can beobtained at <http://www.openldap.org/>.
Portions Copyright 1998-2012 Kurt D. Zeilenga.
Portions Copyright 1998-2006 Net Boolean Incorporated.
Portions Copyright 2001-2006 IBM Corporation.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted only as authorized by the OpenLDAP
Public License.
Portions Copyright 1999-2008 Howard Y.H. Chu.
Portions Copyright 1999-2008 Symas Corporation.
Portions Copyright 1998-2003 Hallvard B. Furuseth.
Portions Copyright 2007-2011 Gavin Henry.
Portions Copyright 2007-2011 Suretec Systems Ltd.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thisnotice is preserved. The names of the copyright holders may not be used to endorse or promote products derived
from this software without their specific prior written permission. This software is provided "as is'' without express
or implied warranty.
Portions Copyright (c) 1992-1996 Regents of the University of Michigan.
All rights reserved.
Redistribution and use in source and binary forms are permitted provided that this notice is preserved and that due
credit is given to the University of Michigan at Ann Arbor. The name of the University may not be used to endorse
or promote products derived from this software without specific prior written permission. This software is provided``as is'' without express or implied warranty.
The OpenLDAP Public License
Version 2.8, 17 August 2003
Redistribution and use of this software and associated documentation ("Software"), with or without modification,
are permitted provided that the following conditions are met:
1. Redistributions in source form must retain copyright statements and notices,
2. Redistributions in binary form must reproduce applicable copyright statements and notices, this list of
conditions, and the following disclaimer in the documentation and/or other materials provided with the
distribution, and
3. Redistributions must contain a verbatim copy of this document.
The OpenLDAP Foundation may revise this license from time to time. Each revision is distinguished by a version
number. You may use this Software under terms of this license revision or under the terms of any subsequent
revision of the license.
THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS CONTRIBUTORS ``AS IS'' AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
OPENLDAP FOUNDATION, ITS CONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S) OF THE SOFTWARE BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS780

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The names of the authors and copyright holders must not be used in advertising or otherwise to promote the sale,use or other dealing in this Software without specific, written prior permission. Title to copyright in this Software
shall at all times remain with copyright holders.
OpenLDAP is a registered trademark of the OpenLDAP Foundation.
Copyright 1999-2003 The OpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved. Permission tocopy and distribute verbatim copies of this document is granted.

Licenses - OpenSSL
LICENSE ISSUESThe OpenSSL toolkit stays under a double license, i.e. both the conditions of the OpenSSL License and the original
SSLeay license apply to the toolkit. See below for the actual license texts.
OpenSSL License
Copyright (c) 1998-2019 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://
www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived
from this software without prior written permission. For written permission, please contact opensslcore@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names
without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://
www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
====================================================================
This product includes cryptographic software written by Eric Young(eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License----------------------Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

781

All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The
following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not justthe SSL code. The SSL documentation included with this distribution is covered by the same copyright terms exceptthat the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed.
If this package is used in a product, Eric Young should be given attribution as the author of the parts of the libraryused.
This can be in the form of a textual message at program startup or in documentation (online or textual) provided
with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgement:"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)"
The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you
must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The licence and distribution terms for any publically available version or derivative of this code cannot be changed.
i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public
License.]Licenses - Wireless-RegDB
Copyright (c) 2008, Luis R. Rodriguez <mcgrof@gmail.com>
Copyright (c) 2008, Johannes Berg <johannes@sipsolutions.net>
Copyright (c) 2008, Michael Green <Michael.Green@Atheros.com>
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby
granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THISSOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.

782

Licenses - WPA Supplicant and Hostapd
Copyright (c) 2002-2019, Jouni Malinen <j@w1.fi> and contributors
All Rights Reserved.
These programs are licensed under the BSD license (the one with advertisement clause removed).
If you are submitting changes to the project, please see CONTRIBUTIONS file for more instructions.
This package may include either wpa_supplicant, hostapd, or both. See README file respective subdirectories(wpa_supplicant/README or hostapd/README) for more details.
Source code files were moved around in v0.6.x releases and compared to earlier releases, the programs are now
built by first going to a subdirectory (wpa_supplicant or hostapd) and creating build configuration (.config) andrunning 'make' there (for Linux/BSD/cygwin builds).
LicenseThis software may be distributed, used, and modified under the terms of BSD license:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name(s) of the above-listed copyright holder(s) nor the names of its contributors may be used toendorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

783

Index""To Assert" and Assertion Timeout 729"To De-assert" and Deassertion Hysteresis 731

1
1U Products 18

2
2U Products 18

8802.1x Security Overview 238

A
A Note about Firmware Upgrade Time 371
A Note about Infinite Loop 342
A Note about Untriggered Rules 343
About the Link ID 59
Accessing Cascaded Devices 658
Action Group 317
Actuator Configuration Commands 541
Actuator Control Operations 555
Actuator Information 421
Adding a Firewall Rule 478
Adding a Link Unit 58
Adding a Monitored Device 543
Adding a Radius Server 522
Adding a Role-Based Access Control Rule 490
Adding an LDAP Server 515
Adding Attributes to the Class 721
Adding LDAP/LDAPS Servers 278
Adding Radius Servers 281
Adding TACACS+ Servers 282
Adding, Removing or Swapping Cascaded Devices
258, 657
Additional Xerus Information - Assorted Products
725
AD-Related Configuration 708
Alarm 316

784

Alerts 89
Alerts Notice in a Yellow or Red Screen 120
All Privileges 511
Altitude Correction Factors 736
APIPA and Link-Local Addressing 18
Appendices 580
Applicable Products 637
Assertion Timeout Example for Temperature
Sensors 731
Asset Management Commands 547
Asset Management Strips and dcTrack 747
Asset Management Tag List 349
Asset Management Tag Log 350
Asset Strip Automatic Firmware Upgrade 225
Asset Strip Management 547
Asset Strip Settings 433
Asset Strips 217
Asset Strips Page 76
Assets 111
Authentication Commands 514
Authentication Settings 430
Automatic and Manual Modes 86
Automatic Management of Sensors 201
Automatically Completing a Command 409
Automatically Create Pairwise Outlet Groups 74
Available Actions 315
Available Data of the Outlets Overview Page 167

B
Backup and Restore of Device Settings 376
Backup and Restore via SCP 630
Beeper 130
Before You Begin 19
Best Practices for Cascading 48, 640
Built-in Rules and Rule Configuration 292
Bulk Configuration or Firmware Upgrade via DHCP
(TFTP/HTTPS) 605
Bulk Configuration Restrictions 372

Bulk Configuration via SCP 629
Bulk Configuration, Firmware Upgrade, or Backup/
Restore via SCP 627
Bulk Configuration/Upgrade Procedure 605
Button-Type Locking Outlets 36

C
Canceling the Power-On Process 554
Card Readers 395
Cascade Troubleshooting 673
Cascading All Devices via USB-Only 648
Cascading Devices via Dual Ethernet and USB 651
Cascading for Shared Ethernet Connectivity 47
Cascading Modes Overview 252, 641
Cascading Procedure Overview 641
Cascading Restrictions 653
Cascading Solution Overview 637
Cascading Solutions for Xerus 637
Change Load Shedding State 318
Changing a User's Password 502
Changing an Outlet's Default State 496
Changing HTTP(S) Settings 260
Changing Measurement Units 506
Changing Modbus Settings 265
Changing SSH Settings 264
Changing Storage Settings 387
Changing Telnet Settings 265
Changing the Device Name 439
Changing the Inlet Name 499
Changing the LAN Duplex Mode 454
Changing the LAN Interface Speed 454
Changing the Modbus Configuration 471
Changing the Outlet Name 495
Changing the Overcurrent Protector Name 500
Changing the Role(s) 506
Changing the Sensor Description 526
Changing the Sensor Name 525
Changing the SSH Configuration 468
Changing the Telnet Configuration 467
Changing Your Own Password 508
Changing Your Password 133
Character LCD Display 671

Checking Lua Scripts States 363
Checking RCM State and Current 682
Checking RCM States and Current 688
Checking the Accessibility of NTP Servers 476
Checking the Branch Circuit Rating 20
Circuit Breaker Orientation Limitation 36
Circuit Breakers 124
Cisco ISE Xerus TACACS+ Authentication 711
Clearing Diagnostic Log for Network Connections
438
Clearing Event Log 438
Clearing Information 438
CLI Operations for RCM 690
Closing a Local Connection 407
Collected Data 366
Command History 437
Commands for Environmental Sensors 539
Commands for Inlet Pole Sensors 535
Commands for Inlet Sensors 533
Commands for Outlet Group Sensors 532
Commands for Outlet Sensors 530
Commands for Overcurrent Protector Sensors 537
Common Network Settings 237
Compliance with IEC 62020 680
Configuration Files 594
Configuration Files for Linking 601
Configure DSAM Serial Ports 212
Configuring a Multi-Inlet Model 163
Configuring Data Push Settings 346
Configuring DNS Parameters 452
Configuring Environmental Sensors' Default
Thresholds 528
Configuring IPv4 Parameters 444
Configuring IPv6 Parameters 448
Configuring Login Settings 284
Configuring Network Services 259
Configuring NTP Server Settings 402
Configuring Password Policy 285
Configuring Security Settings 268
Configuring SMTP Settings 263
Configuring SNMP Settings 261
Configuring the Cascading Mode 465785

Configuring the Device and Network 438
Configuring the PX-Series PDU 38
Configuring the Serial Port 358
Configuring Webcams and Viewing Live Images
383
Connect to DSAM Serial Targets in the Web
Interface 214
Connect to DSAM Serial Targets via SSH 216
Connecting a Mobile Device 39
Connecting a PDU to a Dominion KVM or Serial
Device 745
Connecting a PX3 Locking Line Cord 30
Connecting the PDU to a Power Source 37
Connecting to a Computer 44
Connecting to Your Network 37
Control Buttons 87
Controlling Outlets in Groups 73
Copying an Existing Authentication Server's
Settings 519
Creating a CSR 273
Creating a New Attribute 720
Creating a Role 510
Creating a Self-Signed Certificate 275
Creating a User Profile 501
Creating an Outlet Group 180, 497
Creating Configuration Files via Mass Deployment
Utility 602
Creating IP Access Control Rules 269
Creating Role Based Access Control Rules 271
Creating Roles 231
Creating Users 226
Curl Upload Return Codes 626
Customizing Bulk Configuration Profiles 374

D
Dashboard - Alarms 146
Dashboard - Alerted Sensors 142
Dashboard - Inlet History 143
Dashboard - Inlet I1 139
Dashboard - OCP 141
Dashboard - PDUs 137
Dashboard Page 572

786

Data Encryption in 'config.txt' 603
Data Push Format Examples 347
Date and Time Settings 418
dcTrack 747
Deassertion Hysteresis Example for Temperature
Sensors 733
Default Measurement Units 418
Default Voltage and Current Thresholds 734
Degaussing RCM Type B Sensors 691
Deleting a Firewall Rule 482
Deleting a Monitored Device 543
Deleting a Role 514
Deleting a Role-Based Access Control Rule 493
Deleting a User Profile 508
Deleting an Outlet Group 184
Derating a Raritan Product 566
Detailed Information on Outlet Pages 178
Determining the Authentication Method 514
Device Configuration 415
Device Configuration Commands 439
Device Configuration/Upgrade Procedure 593
Device Information 366
Device Settings 235
Device-Cascading Methods 647
Device-Specific Settings 739
DHCP IPv4 Configuration in Linux 620
DHCP IPv4 Configuration in Windows 607
DHCP IPv6 Configuration in Linux 621
DHCP IPv6 Configuration in Windows 615
Diagnostic Log for Network Connections 247
Different CLI Modes and Prompts 406
Disabling or Enabling Front Panel RCM Self-Test
685
Displays for Primary and Link Units 76
Door Access 288
Door Status and Control 393
Dot-Matrix LCD Display 668
Download via Curl 624
Download via Web Browsers 623
Downloading Diagnostic Data via SCP 631
Downloading Diagnostic Information 378
Downloading SNMP MIB 400

DSAM CLI Commands 215
DSAM Connection 210
DSAM LED Operation 211

E
EAP CA Certificate Example 459
Editing or Deleting a Rule/Action 337
Editing or Deleting IP Access Control Rules 270
Editing or Deleting Ping Monitoring Settings 355
Editing or Deleting Role Based Access Control
Rules 273
Editing or Deleting Roles 233
Editing or Deleting Users 230
Editing rciusergroup Attributes for User Members
723
Enabling and Configuring SNMP 397
Enabling or Disabling 802.11n High Throughput
461
Enabling or Disabling a User Profile 503
Enabling or Disabling an Inlet (for Multi-Inlet
PDUs) 500
Enabling or Disabling data backup 444
Enabling or Disabling Data Logging 443
Enabling or Disabling Front Panel Actuator Control
494
Enabling or Disabling Front Panel Beeper-Sound
Control 495
Enabling or Disabling Front Panel Outlet Switching
494
Enabling or Disabling Load Shedding 550
Enabling or Disabling Service Advertising 473
Enabling or Disabling Strong Passwords 486
Enabling or Disabling the LAN Interface 453
Enabling or Disabling the Restricted Service
Agreement 482
Enabling Redfish Services 267
Enabling Service Advertising 267
Enabling the Restricted Service Agreement 285
Environmental Sensor Configuration Commands
524
Environmental Sensor Default Thresholds 428
Environmental Sensor Information 419
Environmental Sensor Package Information 420

Environmental Sensor Threshold Information 427
Equipment Setup Worksheet Sample 589
Ethernet (Wired) Interface Settings 238
Event Log 434
Example - Actuator Naming 542
Example - Asset Management 548
Example - Baud Rate 549
Example - Creating a Role 514
Example - Default Upper Thresholds for
Temperature 530
Example - Inlet Naming 500
Example - OCP Naming 501
Example - Outlet Naming 497
Example - Ping Command 561
Example - Power Cycling Specific Outlets 554
Example - Server Settings Changed 546
Example - Turning On a Specific Actuator 556
Example -Time Configuration 476
Example: Ping Monitoring and SNMP Notifications
356, 561
Existing Roles 432
Existing User Profiles 431
Expansion Device Events in the Log 674
Extended Cascading for Dual Ethernet and USB
650
Extended-Cascading Requirements 650
External Beeper 225, 318

F
Factory Default Settings 676
FAQs 54
Filling Out the Equipment Setup Worksheet 20
Finding the Sensor's Serial Number 200
Firewall Control 477
Firmware Update via SCP 627
Firmware Upgrade for Cascading Chains 671
Firmware Upgrade via USB 604
Flexible Cord Installation Instructions 564
Flexible Cord Selection 565
Forcing a Password Change 503
Forcing the Device Detection Mode 549
FreeRADIUS Standard Attribute Illustration 698

787

FreeRADIUS VSA Illustration 707
From LDAP/LDAPS 719
From Microsoft Active Directory 719
Front Panel Display 86
Front Panel Operations for RCM 687
Front Panel Settings 357
Full Disaster Recovery 371
Fuse 126
Fuse Replacement on 1U Models 128
Fuse Replacement on Zero U Models 126
fwupdate.cfg 594

H
Hardware Issue Detection 378
How Long a Link Remains Accessible 386

I
Identifying Cascaded Devices 662
Identifying Snapshots Folders on Remote Servers
389
Identifying the Sensor Position and Channel 201
Idle Timeout 485
If Switchable Outlet Groups are Limited 182
Illustration 638
Illustration - GMAIL SMTP Certificate Chain 742
Illustrations of Adding LDAP Servers 518
Individual OCP Pages 188
Individual Outlet Pages 174
Individual Sensor/Actuator Pages 203
Initial Installation and Configuration 37
Initialization Delay Use Cases 155
Inlet 96, 161, 80
Inlet Configuration Commands 499
Inlet Information 417
Inlet Pole Sensor Threshold Information 425
Inlet Sensor Threshold Information 424
Inlets/Outlets Page 577
In-Line Monitor Unused Channels 566
In-Line Monitors 564
In-Line Monitor's Web Interface 572
Inrush Current and Inrush Guard Delay 155
Installing a CA-Signed Certificate 275

788

Installing Cable Retention Clips on Outlets(Optional) 33
Installing Cable Retention Clips on the Inlet(Optional) 32
Installing or Downloading Existing Certificate andKey 276
Installing the Flexible Cord 566
Internal Beeper 319
Internal Beeper State 152
Introduction to Xerus Technology Platform PDUs PX-Series User Guide 13
IP Configuration 411
IPv4-Only or IPv6-Only Configuration 412
iX7 Controller Reset Button 678

K
Keys that Cannot Be Uploaded 635

L
Latching Relay Behavior 153
LCD Message for RCM Critical State 687
LDAP Configuration Illustration 692
LDAP Settings 515
Legrand PDU, PXC, and PXO Connection Ports 84
Licenses - Angular 748
Licenses - Bind9 757
Licenses - Clish 763
Licenses - Dropbear 768
Licenses - FreeType 770
Licenses - IW 772
Licenses - JSON-C 772
Licenses - LIBTIRPC 773
Licenses - LIBXML2 773
Licenses - Mbus 773
Licenses - Net-SNMP 774
Licenses - Open LDAP 779
Licenses - OpenSSL 781
Licenses - Wireless-RegDB 782
Licenses - WPA Supplicant and Hostapd 783
Linking Cascaded Units 60
Linking CLI Commands 78
Linking in the CLI 78

Linking in the Web Interface 57
Linking Units 54
Load Shedding Configuration Commands 549
Load Shedding Mode: Activate or Deactivate 171
Load Shedding Settings 433
Load Shedding Setup: Setting Non-Critical Outlets
171
Log an Event Message 319
Log Rows 348
Logging in to CLI 404
Logging out of CLI 407
Login and Logout 133
Login Limitation 484
Login, Logout and Password Change 132
Lowercase Character Requirement 487
Lua Scripts 360

M
Main Menu 89
Maintenance 366
Making a Power-Sharing Connection - iX7 Example
50
Managed vs Unmanaged Sensors/Actuators 198
Managing an Outlet Group 497
Managing Firewall Rules 478
Managing One Sensor or Actuator 201
Managing Role-Based Access Control Rules 490
Manually Changing Zero U LCD Orientation 123
Manually Starting or Stopping a Script 362
Maximum Password History 488
Maximum Password Length 486
Menu 136
Minimum and Maximum Values for NumericSensors 157
Minimum Password Length 486
Miscellaneous 364
Models with Residual Current Monitoring 679
Modifying a Firewall Rule 480
Modifying a Monitored Device's Settings 544
Modifying a Role 513
Modifying a Role-Based Access Control Rule 492
Modifying a User Profile 501

Modifying a User's Personal Data 502
Modifying an Existing LDAP Server 519
Modifying an Existing Radius Server 523
Modifying an Outlet Group 183
Modifying Firewall Control Parameters 477
Modifying or Deleting a Script 364
Modifying or Deleting Bulk Configuration Profiles
376
Modifying Role-Based Access Control Parameters
489
Modifying SNMPv3 Settings 504
Monitoring Server Accessibility 350
Mounting 1U or 2U Models 29
Mounting Zero U Models Using Button Mount 24
Mounting Zero U Models Using Claw-Foot Brackets
26
Mounting Zero U Models Using L-Brackets 22
Mounting Zero U Models Using Two Rear Buttons
28
Multi-Command Syntax 409

N
Network Configuration 411
Network Configuration Commands 444
Network Connections Diagnostic Log 436
Network Diagnostics 377, 413
Network Interface Settings 413
Network Service Settings 414
Network Settings 236
Network Troubleshooting in Diagnostic Mode 559
NPS VSA Illustration 699
Numeric Character Requirement 487

O
OCP Trip-Cause Detection 191
OCPs 97, 186
OCPs Page 75
Off and Lock Icons for Outlets 174
Operating the Front Panel Display 88
Optional Parameters 517
Options for Adding Link Units 58
Options for Outlet State on Power Up 154

789

Outlet Configuration Commands 495
Outlet Group Configuration Commands 497
Outlet Group Information 416
Outlet Group Power Control 181
Outlet Group Threshold Information 423
Outlet Groups 179, 70
Outlet Information 415
Outlet Pole Sensor Threshold Information 422
Outlet Sensor Threshold Information 421
Outlets 98, 165
Outlets and Outlet LEDs 81
Overcurrent Protector Configuration Commands
500
Overcurrent Protector Information 417
Overcurrent Protector Sensor Threshold
Information 427

P
Package Contents 18
Pairwise Outlet Groups 73
Password Aging 484
Password Aging Interval 485
PDU 148
PDU 92
Performing Bulk Configuration 375
Peripheral Devices Configuration Commands 546
Peripheral Devices Settings 436
Peripherals Page 75
Placeholders for Custom Messages 333
Plug Selection 565
Port Forwarding Examples 256, 660
Port Number Syntax 254, 659
Port Numbers for Port-Forwarding Devices 658
Port Overload - Reset Fuse 119
Power CIM 226
Power Control Operations 550
Power Cycling the Outlet(s) 553
Power IQ Configuration 746
Power Sharing Port on iX7 Controllers 50
Power Supply Sensor 160
Powering On/Off/Cycle Outlet Groups 498

790

Power-Off Period Options for Individual Outlets
179
Power-Sharing Restrictions and Connection 49
Preparing the Installation Site 20
Primary Units Manage Link Units 63
Push Out Sensor Readings 320
PX2-Series Connection Ports 84
PX2-Series Specifications 584
PX3-1000/PX2-1000 Series Outlets (No LEDs) 81
PX3-3000/PX2-3000 Series Outlets (No LEDs) 81
PX3-4000/PX2-4000 Series Outlets and LEDs 81
PX3-5000/PX2-5000 Series Outlets and LEDs 82
PX3-Series Connection Ports 83
PX3-Series PDU and Transfer Switch Specifications
581
PXC and PXO Metered Series Outlets (No LEDs) 83
PXC and PXO Switched Series Outlets and LEDs 82
PXC/PXO Specifications 587
PXE Connection Ports 84
PXE Specifications 586
PXO Rackmount Method 30

Q
Querying Available Parameters for a Command
408
Querying DNS Servers 559
Quick Access to a Specific Page 137

R
Rack Unit Configuration (Tag Ports) 547
Rack Unit Settings of an Asset Strip 434
Rackmount Safety Guidelines 21
Rack-Mounting the PDU 21
Rackmounts 21
RADIUS Configuration Illustration 697
Radius Settings 522
Raritan PDU Product Models 15
Raw Configuration Upload and Download 622
RCM Critical State Alarm 683
RCM Current Sensor 679
RCM Residual Current and State Objects 690
RCM Self-Test 681

RCM SNMP Operations 690
RCM State Sensor 679
RCM Trap 690
Rebooting 380
Receptacle Selection 565
Record Snapshots to Webcam Storage 320
Regaining Access with HSTS and Expired Certificate
261
Releasing a Link Unit 64
Reliability Data 437
Reliability Error Log 437
Reliability Hardware Failures 437
Re-linking a Link Unit 65
Remote Authentication Examples 692
Removing an Existing LDAP Server 521
Removing an Existing Radius Server 524
Removing the Uploaded Certificate or Private Key
460
Replaceable Controller 130
Requirements for Prometheus and Grafana 365
Reserving IP Addresses in DHCP Servers 725
Reserving IP in Linux 726
Reserving IP in Windows 725
Reset Button 124
Resetting a Group's Energy Counter andMinimum/Maximum Values 182
Resetting All Settings to Factory Defaults 381
Resetting Energy Readings 557
Resetting the Button-Type Circuit Breaker 124
Resetting the Handle-Type Circuit Breaker 125
Resetting the PX-Series PDU 556
Resetting to Factory Defaults 558, 676
Restarting the PX-Series PDU 556
Restricted Service Agreement 482
Retrieving Energy Usage 403
Retrieving Previous Commands 408
Returning User Group Information 719
Role Configuration Commands 510
Role of a DNS Server 737
Role-Based Access Control 489
Running RCM Self-Test 689

S
Safety Guidelines 17
Safety Instructions 16, 564
Sample Environmental-Sensor-Level Event Rule341
Sample Event Rules 338
Sample Inlet-Level Event Rule 340
Sample Outlet-Level Event Rule 338
Sample PDU-Level Event Rule 338
Scheduling an Action 330
Scheduling RCM Self-Test 685
SecureLock™ Outlets and Cords 34
Security Configuration Commands 477
Security Settings 429
Send an SNMP Notification 326
Send Email 322
Send Sensor Report 323
Send Sensor Report Example 330
Send SMS Message 324
Send Snapshots via Email 325
Sending Links to Snapshots or Videos 385
Sensor Descriptors for Inlet Active Power 348
Sensor Log 347
Sensor Threshold Configuration Commands 530
Sensor Threshold Settings 727
Sensor/Actuator Location Example: X, Y, Z
Coordinates 208
Sensor/Actuator States 199
Sequence Setup 169
Serial Access With Dominion Serial Access Module
210
Serial Port Configuration Commands 548
Serial Port Settings 433
Server Reachability Configuration Commands 543
Server Reachability Information 436
Server Reachability Information for a SpecificServer 436
Server Status Checking or Power Control 354
Setting an Outlet's Cycling Power-Off Period 496
Setting Data Logging 344
Setting Data Logging Measurements Per Entry 443
Setting Default Measurement Units 235, 509

791

Setting Ethernet EAP Parameters 456
Setting Front Panel RCM Self-Test 691
Setting IPv4 Static Routes 447
Setting IPv6 Static Routes 451
Setting LAN Interface Parameters 453
Setting Log Capacity 443
Setting Network Service Parameters 466
Setting RCM Current Thresholds 684
Setting RCM DC Current Thresholds 686
Setting RCM Thresholds 690
Setting Redfish Service 472
Setting the Alarmed to Normal Delay for DX2passive infrared sensor 527
Setting the Automatic Daylight Savings Time 475
Setting the Baud Rates 548
Setting the BSSID 464
Setting the Date and Time 286
Setting the Ethernet Authentication Method 455
Setting the HTTP Port 466
Setting the HTTPS Port 467
Setting the Inrush Guard Delay Time 442
Setting the IPv4 Address 446
Setting the IPv4 Configuration Mode 444
Setting the IPv4 Gateway 446
Setting the IPv4 Preferred Host Name 445
Setting the IPv6 Address 450
Setting the IPv6 Configuration Mode 448
Setting the IPv6 Gateway 450
Setting the IPv6 Preferred Host Name 449
Setting the LAN MTU 455
Setting the Outlet Initialization Delay 442
Setting the Outlet Power-On Sequence 440
Setting the Outlet Power-On Sequence Delay 440
Setting the Outlet Relay Behavior 439
Setting the PDU-Defined Cycling Power-Off Period
441
Setting the PDU-Defined Default Outlet State 441
Setting the PSK 461
Setting the Registry to Permit Write Operations to
the Schema 719
Setting the SNMP Configuration 469
Setting the SSID 460

792

Setting the Time Zone 475
Setting the Wireless Authentication Method 461
Setting the Wireless MTU 465
Setting the X Coordinate 525
Setting the Y Coordinate 526
Setting the Z Coordinate 526
Setting Thresholds for Total Active Energy orPower 156
Setting Up a TLS Certificate 273
Setting Up External Authentication 277
Setting Wireless EAP Parameters 462
Setting Wireless Parameters 460
Setting Your Preferred Measurement Units 234
Show and Hide Min/Max Values 158
Showing Information 411
Showing Network Connections 560
Showing Residual Current Monitoring Information
690
Showing the Firmware Upgrade Progress 123
Shut down a Server and Control its Power 319
Single Login Limitation 484
SmartLock 391
SmartLock and Card Reader 390
SNMP Gets and Sets 401
SNMP Sets and Thresholds 402
SNMPv2c Notifications 399
SNMPv3 Notifications 397
Sorting a List 137
Special Character Requirement 488
Special Configuration and Upgrade Methods 593
Specifying Non-Critical Outlets 442
Specifying the Agreement Contents 483
Specifying the CC Sensor Type 525
Specifying the SSH Public Key 507
Standard Attributes 698
Start or Stop a Lua Script 327
Static Route Examples 248
Static Route Interface Names 250
Step A. Determine User Accounts and Roles 692
Step A: Add Your PX-Series PDU as a RADIUS Client
699

Step B. Configure User Groups on the AD Server
692
Step B: Configure Connection Policies and VendorSpecific Attributes 702
Step C. Configure LDAP Authentication on the PXSeries PDU 693
Step D. Configure Roles on the PX-Series PDU 696
Strong Passwords 486
Supported Web Browsers and Mobile Devices 132
Switch Outlet Group 328
Switch Outlets 328
Switch Peripheral Actuator 329
Switching Off an Actuator 555
Switching On an Actuator 555
Switching to a Different Unit 65
Syslog Message 329
System and USB Requirements 594

T
Testing the Network Connectivity 560
TFTP/HTTPS Requirements 606
The ? Command for Showing Available Commands
407
The MIB File 401
Third Party Licenses 748
Threaded Grounding Point 131
Threshold Bulk Setup 168
Thresholds and Sensor States 728
Time Configuration Commands 473
Time Units 155
Tips for Using the CLI 407
TLS Certificate Chain 739
Tracing the Route 561
Trip Cause Outlet Handling 155
Turning Off the Outlet(s) 552
Turning On the Outlet(s) 551

U
Unbalanced Current Calculation 736
Unblocking a User 556
Unpacking the Product and Components 19
Updating the Firmware 370

Updating the LDAP Schema 719
Updating the Schema Cache 723
Upgrade Guidelines for Existing Cascading Chains371
Upgrade Sequence for Existing Cascading Chains
672
Uploading Raw Configuration 624
Uppercase Character Requirement 487
USB Cascading 647
USB-Cascading Requirements 647
User Blocking 485
User Configuration Commands 501
User Interfaces Showing Default Units 235
User Management 226
Using Default Thresholds 527
Using Prometheus and Grafana 365
Using SNMP 397
Using the CLI 665
Using the CLI Command 677
Using the Command Line Interface 404
Using the Hardware Features 80
Using the LCD Display 668
Using the Reset Button 677
Using the SNMP 666
Using the Web Interface 132, 662

V
Vendor-Specific Attributes 698
View DSAM Serial Ports 211
Viewing Connected Users 367
Viewing Firmware Update History 372
Viewing Link Unit Information 66
Viewing More Information 184
Viewing the Primary Unit 57
Viewing, Downloading, Deleting Locally-Saved
Snapshots 386
Viewing, Pausing, Resuming or Clearing the Local
Event Log 369

W
Ways to Probe Existing User Profiles 737
Web Interface Operations for RCM 682

793

Web Interface Overview 134
Webcam Management 382
What is a Certificate Chain 739
When to Avoid Cascading Devices 640
Windows NTP Server Synchronization Solution 288
Wireless Network Settings 243
Wiring of 3-Phase In-Line Monitors 566
With an Analog Modem 406
With HyperTerminal 404
With SSH or Telnet 405
Writing or Loading a Lua Script 360

X
Xerus Default Log Messages for All Products 295
Xerus Product Integration 745

Y
Yellow- or Red-Highlighted Sensors 197

Z
Z Coordinate Format 208
Zero U Models Relocatable Inlet 80
Zero U Products 18794