Dominion PX2-1098 - Inverter Raritan - Free user manual and instructions

USER MANUAL Dominion PX2-1098 Raritan

Copyright © 2012 Raritan, Inc.

DPX2-1000-0D-v2.3-E

March 2012

255-80-6105-00

Safety Guidelines

WARNING! Read and understand all sections in this guide before installing or operating this product.

WARNING! Connect this product to an AC power source whose voltage 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 to comply 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 a device 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 60950-1 or equivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury and death.

WARNING! Do not use a Raritan product containing outlet relays to power large inductive loads such as motors or compressors. 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. Use of this product to power such equipment may result in personal injury and death.

WARNING! If this product is a model that requires assembly of its line cord or plug, all such assembly must be performed by a licensed electrician and the line cord or plugs used must be suitably rated based on the product's nameplate ratings and 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, or other reproductive harm.

Safety Instructions

1. Installation of this product should only be performed by a person who has knowledge and experience with electric power.
2. Make sure the line cord is disconnected from power before physically mounting or moving the location of this product.
3. This product is designed to be used within an electronic equipment rack. The metal case of this product is electrically bonded to the line cord ground wire. A threaded grounding point on the case may 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 the receptacle's power lines, neutral and protective earth ground pins are wired correctly and are the correct 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.

This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated into another language without express prior written consent of Raritan, Inc.

© Copyright 2012 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.

FCC Information

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a commercial installation. This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential environment may cause harmful interference.

VCCI Information (Japan)

Raritan is not responsible for damage to this product resulting from accident, disaster, misuse, abuse, non-Raritan modification of the product, or other events outside of Raritan's reasonable control or not arising under normal operating conditions.

CE cUL us 1F61 LISTED I.T.E.

CAUTION:

To reduce the risk of shock — Use indoors only in a dry location. No user serviceable parts inside. Refer servicing to qualified personnel. For use with IT equipment only. Disconnect power before servicing.

Contents

Safety Guidelines ii

Safety Instructions iii

Applicable Models xiii

What's New in the Dominion PX User Guide

xiv

Chapter 1 Introduction 1

Product Models....1

Product Features .... 1

Package Contents....3

Zero U Products....4

1U Products 4

2U Products 4

Chapter 2 Rack-Mounting the PDU 5

Rackmount Safety Guidelines 5

Circuit Breaker Orientation Limitation 5

Mounting Zero U Models Using L-Brackets....6

Mounting Zero U Models Using Button Mount....7

Mounting Zero U Models Using Claw-Foot Brackets....9

Mounting Zero U Models Using Two Rear Buttons 10

Mounting Zero U Models Using L-Brackets and Buttons....12

Mounting 1U or 2U Models....13

Chapter 3 Installation and Configuration

15

Before You Begin....15

Unpacking the Product and Components....15

Contents

Preparing the Installation Site....16

Filling Out the Equipment Setup Worksheet 16

Checking the Branch Circuit Rating....16

Installing Cable Retention Clips on the Inlet (Optional) 17

Connecting the PDU to a Power Source 17

Configuring the Dominion PX 18

Connecting the Dominion PX to a Computer 19

Installing the USB-to-Serial Driver....20

Connecting the Dominion PX to Your Network 21

Initial Network Configuration....23

Cascading the PDUs via USB 29

Installing Cable Retention Clips on Outlets (Optional) 32

Connecting Environmental Sensors (Optional) 33

About Contact Closure Sensors 35

How to Connect Differential Air Pressure Sensors....38

Connecting the Asset Management Sensor (Optional) 38

Combining Asset Sensors 39

Connecting Asset Sensors to the Dominion PX....41

Connecting Blade Extension Strips 43

Connecting AMS-M2-Z Asset Sensors (Optional)......46

Connecting a Logitech Webcam (Optional)....48

Connecting a GSM Modem (Optional)....48

Connecting a Schroff LHX Heat Exchanger (Optional) 49

Chapter 4 Using the PDU 50

Panel Components 50

Power Cord....50

Outlets 50

Connection Ports 51

LED Display 54

Reset Button 58

Circuit Breakers 59

Resetting the Button-Type Circuit Breaker....59

Resetting the Handle-Type Circuit Breaker....60

Fuse 61

Fuse Replacement on Zero U Models....61

Fuse Replacement on 1U Models....62

Beeper 64

Chapter 5 Using the Web Interface

65

Supported Web Browsers....65

Logging in to the Web Interface....66

Login....66

Changing Your Password....67

Logout 68

Introduction to the Web Interface....69

Menus....70

Contents

Dominion PX Explorer Pane....70

Setup Button....73

Status Bar 73

Add Page Icon 75

Logout Button 75

Data Pane 75

More Information 76

Viewing the Dashboard....81

Alerted Sensors 81

Device Management 82

Displaying the PDU Information 82

Naming the PDU....83

Modifying the Network Configuration....84

Modifying the Network Service Settings....90

Setting the Date and Time....94

Configuring the Feature Port 97

Configuring the Serial Port 98

Specifying the Device Altitude....98

Setting Data Logging 99

Configuring the SMTP Settings 100

Setting the EnergyWise Configuration 101

Rebooting the Dominion PX Device 102

User Management 102

Creating a User Profile 102

Modifying a User Profile 106

Deleting a User Profile....106

Changing the User List View 107

Setting Up Roles....107

Creating a Role....107

Modifying a Role....108

Deleting a Role 109

Changing the Role List View 110

Access Security Control....110

Forcing HTTPS Encryption....110

Configuring the Firewall....110

Setting Up User Login Controls....116

Setting Up Role-Based Access Control Rules 118

Setting Up an SSL Certificate 123

Certificate Signing Request....123

Creating a Self-Signed Certificate 125

Installing Existing Key and Certificate Files....126

Downloading Key and Certificate Files....127

Setting Up LDAP Authentication....128

Gathering the LDAP Information 128

Adding the LDAP Server Settings 129

Sorting the LDAP Access Order....131

Testing the LDAP Server Connection 132

Editing the LDAP Server Settings....132

Deleting the LDAP Server Settings 132

Disabling the LDAP Authentication 133

Enabling LDAP and Local Authentication Services....133

Contents

Outlet Management 133

Naming Outlets 134

Checking Associated Circuit Breakers 134

Outlet Switching....135

Setting the Default Outlet State....137

Changing the Cycling Power-Off Period....139

Setting the Initialization Delay 141

Setting the Inrush Guard Delay 142

Setting the Outlet Power-On Sequence 142

Setting the Outlet-Specific Power-On Delay 143

Setting Non-Critical Outlets and Load Shedding Mode 144

Inlet and Circuit Breaker Management 147

Naming the Inlet 147

Naming Circuit Breakers....147

Monitoring the Inlet 148

Monitoring Circuit Breakers 149

Setting Power Thresholds....150

Setting Inlet Thresholds....150

Setting a Circuit Breaker's Thresholds 151

Bulk Configuration for Circuit Breaker Thresholds 152

What is Deassertion Hysteresis?......153

What is Assertion Timeout? 154

Configuring Event Rules 155

Components of an Event Rule....155

Creating an Event Rule 155

Sample Event Rules 175

A Note about Infinite Loop....178

Modifying an Event Rule....179

Modifying an Action 180

Deleting an Event Rule or Action....181

A Note about Untriggered Rules....181

Managing Event Logging 181

Viewing the Local Event Log 182

Clearing Event Entries....182

Viewing Connected Users 183

Monitoring Server Accessibility....184

Adding IT Devices for Ping Monitoring 184

Editing Ping Monitoring Settings....185

Deleting Ping Monitoring Settings 185

Checking Server Monitoring States....185

Environmental Sensors....186

Identifying Environmental Sensors....187

Managing Environmental Sensors....188

Configuring Environmental Sensors....189

Viewing Sensor Data....192

Unmanaging Environmental Sensors....195

Asset Management....196

Configuring the Asset Sensor....196

Setting Asset Sensor LED Colors....197

Configuring a Specific Rack Unit....198

Expanding a Blade Extension Strip 199

Displaying the Asset Sensor Information 200

Contents

Copying Configurations with Bulk Configuration 201

Saving a Dominion PX Configuration....202

Copying a Dominion PX Configuration....203

Changing the Measurement Units 203

Managing the Webcam Images or Videos....205

Configuring Webcams 205

Adjusting Image or Video Properties 206

Viewing the Webcam Images or Videos....206

Snapshot Storage....208

Network Diagnostics 210

Pinging a Host 210

Tracing the Network Route....210

Listing TCP Connections 211

Viewing the Communication Log 211

Downloading Diagnostic Information 212

Managing the Schroff LHX Heat Exchanger....212

Enabling the LHX Support....213

Configuring the LHX Device 213

Monitoring the LHX Device....215

Controlling the LHX Device 218

Firmware Upgrade 219

Updating the Dominion PX Firmware 219

Viewing Firmware Update History 221

Full Disaster Recovery 221

Updating the Asset Sensor Firmware....222

Accessing the Help 222

Retrieving Software Packages Information 222

Browsing through the Online Help....222

Chapter 6 Using SNMP 224

Enabling SNMP....224

Configuring Users for Encrypted SNMP v3 225

Configuring SNMP Traps....226

SNMP Gets and Sets....227

The Dominion PX MIB 227

A Note about Enabling Thresholds....229

Chapter 7 Using the Command Line Interface 230

About the Interface....230

Logging in to CLI....230

With HyperTerminal....231

With SSH or Telnet....232

Different CLI Modes and Prompts 233

Closing a Serial Connection 233

Help Command....233

Showing Information 234

Network Configuration 234

Contents

IP Configuration....234

LAN Interface Settings....235

Networking Mode....235

Wireless Configuration 235

Network Service Settings 236

PDU Configuration....236

Outlet Information 237

Inlet Information 238

Circuit Breaker Information 239

Date and Time Settings 239

Environmental Sensor Information 240

Inlet Sensor Threshold Information 241

Inlet Pole Sensor Threshold Information 242

Circuit Breaker Sensor Threshold Information 243

Environmental Sensor Threshold Information 244

Security Settings....245

Existing User Profiles 245

Existing Roles 246

Load Shedding Settings 247

Serial Port Settings....247

EnergyWise Settings 247

Asset Sensor Settings 248

Rack Unit Settings of an Asset Sensor 249

Blade Extension Strip Settings 250

Reliability Data....250

Reliability Error Log 251

Command History....251

History Buffer Length....251

Examples 251

Configuring the Dominion PX Device and Network 253

Entering the Configuration Mode....253

PDU Configuration Commands 254

Networking Configuration Commands....262

Time Configuration Commands....287

Security Configuration Commands....290

Outlet Configuration Commands....311

Inlet Configuration Commands 313

Circuit Breaker Configuration Commands....314

Environmental Sensor Configuration Commands 315

Sensor Threshold Configuration Commands 319

User Configuration Commands 343

Role Configuration Commands ....355

EnergyWise Configuration Commands 360

Asset Management Commands 363

Serial Port Configuration Commands 371

Setting the History Buffer Length....372

Multi-Command Syntax 373

Quitting the Configuration Mode....374

Load Shedding Configuration Commands....374

Enabling or Disabling Load Shedding 375

Power Control Operations 375

Turning On the Outlet(s)....376

Contents

Turning Off the Outlet(s)....377
Power Cycling the Outlet(s) 378
Unblocking a User....379
Resetting the Dominion PX....379
Restarting the PDU....380
Resetting to Factory Defaults 380
Network Troubleshooting....380
Entering the Diagnostic Mode 381
Diagnostic Commands 381
Quitting the Diagnostic Mode 384
Querying Available Parameters for a Command 385
Retrieving Previous Commands 385
Automatically Completing a Command....385
Logging out of CLI....386

Appendix A Specifications 387

Power Measurement Accuracy....387

Maximum Ambient Operating Temperature 387

Serial RS-232 Port Pinouts....387

Sensor RJ-12 Port Pinouts 388

Appendix B Equipment Setup Worksheet 389

Appendix C Resetting to Factory Defaults 393

Using the Reset Button....393

Using the CLI Command 394

Appendix D LDAP Configuration Illustration 396

Step A. Determine User Accounts and Groups 396

Step B. Configure User Groups on the AD Server 397

Step C. Configure LDAP Authentication on the Dominion PX Device....398

Step D. Configure User Groups on the Dominion PX Device 400

Appendix E Integration 404

Power IQ Configuration 404

Adding PDUs to Power IQ Management 404

Dominion KX II Configuration 406

Configuring Rack PDU (Power Strip) Targets 406

Contents

RF Code Energy Monitoring Solution 410

Appendix F Additional Dominion PX Information 411

MAC Address....411

Locking Outlets and Cords 411

SecureLock™ Outlets and Cords 412

Button-Type Locking Outlets 413

Altitude Correction Factors 414

Data for BTU Calculation 414

CLI Command Applicability....415

Show Commands 415

Configuration Commands....416

Other Commands 418

Truncated Data in the Web Interface 418

Index 419

Applicable Models

This user guide is applicable to the PX-1000 and PX-2000 series, whose model name follows the PX2-1nnn or PX2-2nnn format, where n is a number.

Note: For information on PX2-3nnn, PX2-4nnn and PX2-5nnn series, see the "PX2-3000/4000/5000 Series" User Guide or online help.

What's New in the Dominion PX User Guide

The following sections have changed or information has been added to the Dominion PX User Guide based on enhancements and changes to the equipment and/or user documentation.

Installing the USB-to-Serial Driver (on page 20)

Connecting Blade Extension Strips (on page 43)

Connecting AMS-M2-Z Asset Sensors (Optional) (on page 46)

Connecting a Schroff LHX Heat Exchanger (Optional) (on page 49)

Fuse (on page 61)

Changing the Modbus Settings (on page 93)

Enabling Service Advertisement (on page 94)

Configuring the Feature Port (on page 97)

Configuring the Serial Port (on page 98)

Configuring the Firewall (on page 110)

Setting Up Role-Based Access Control Rules (on page 118)

Bulk Configuration for Circuit Breaker Thresholds (on page 152)

Configuring Event Rules (on page 155)

Configuring a Specific Rack Unit (on page 198)

Expanding a Blade Extension Strip (on page 199)

Managing the Webcam Images or Videos (on page 205)

Managing the Schroff LHX Heat Exchanger (on page 212)

Showing Information (on page 234)

PDU Configuration Commands (on page 254)

Time Configuration Commands (on page 287)

Security Configuration Commands (on page 290)

Asset Management Commands (on page 363)

Serial Port Configuration Commands (on page 371)

Dominion KX II Configuration (on page 406)

Additional Dominion PX Information (on page 411)

What's New in the Dominion PX User Guide

Truncated Data in the Web Interface (on page 418)

Please see the Release Notes for a more detailed explanation of the changes applied to this version of Dominion PX.

Chapter 1 Introduction

The Dominion PX is an intelligent power distribution unit (PDU) that allows you to reboot remote servers and other network devices and/or to monitor power in the data center.

The intended use of the Raritan Dominion PX is distribution of power to information technology equipment such as computers and communication equipment where such equipment is typically mounted in an equipment rack located in an information technology equipment room.

Raritan offers different types of PDUs -- some are outlet-switching capable, and some are not. With the outlet-switching function, you can recover systems remotely in the event of system failure and/or system lockup, eliminate the need to perform manual intervention or dispatch field personnel, reduce downtime and mean time to repair, and increase productivity.

In This Chapter

Product Models....1

Product Features....1

Package Contents ....3

Product Models

The Dominion PX comes in several models that are built to stock and can be obtained almost immediately. Raritan also offers custom models that are built to order and can only be obtained on request.

Visit the Product Selector page

(http://www.raritan.com/resources/px-product-selector/) on the

Raritan website or contact your local reseller for a list of available models.

Product Features

The Dominion PX models vary in sizes and features. In general, the Dominion PX features include:

• For units with switching, the ability to power on, power off, and reboot the devices connected to each outlet.

• The ability to monitor the following at the inlet level:

• RMS current per line (A)

• RMS voltage per line pair (V)
• Active power (W)

• Apparent power (VA)

• Power factor

• Active energy (Wh)
• Unbalanced load percentage

- The ability to monitor the following at the circuit breaker level:

• Status (closed/open)
• Current drawn (A)
• Current remaining (A)

- The ability to monitor environmental factors such as external temperature and humidity

- User-specified location attributes for environmental sensors

- An audible alarm (beeper) to indicate current overload

- Configurable alarm thresholds and hysteresis

- Configurable assertion timeout for thresholds

- The ability to remotely track the locations of IT devices on the rack through connected asset sensors

- The ability to turn off "non-critical" outlets and keep "critical" outlets turned on when the connected UPS enters the battery-powered mode (PX-2000 series supports this feature while PX-1000 series does not)

• Support for SNMP v1, v2, and v3

- The ability to send traps using the SNMP protocol

- The ability to store a data log of all sensor measurements and retrieve it via SNMP

Note: Raritan's Power IQ or other external systems can retrieve the stored data (samples) from the Dominion PX.

• The ability to configure and set values through SNMP, including power threshold levels
• The ability to save one Dominion PX device's configuration settings and then deploy those settings to other Dominion PX devices
  • LED display orientation adjustment support
  • Support for SSH and Telnet services
• For SSH, both password and public key authentications are supported
• Support for both of IPv4 and IPv6 networking
  • Support for Baytech BSNMP
  • Zero configuration service advertisement support
• Wireless connection via a Raritan-provided wireless USB LAN adapter
• The ability to visually monitor the data center environment through a connected Logitech® QuickCam® Pro 9000 webcam
  • Support for webcam images sent via email to designated recipients
• Support of Cinterion ^® MC52i GSM modems, which allow you to send customized SMS messages to designated recipients for specific events
• The ability to monitor a connected Schroff ^® LHX-20 or LHX-40 heat exchanger
  • Support for Cisco EnergyWise
• Support for RF Code energy monitoring system
• Local overcurrent protection (OCP) via branch circuit breakers or fuses on products rated over 20A to protect connected equipment against overload and short circuits
• A combination of outlet types (for example, C13 and C19 outlets) in select models
  • A combination of outlet voltages (120 and 208 volts) in select models
• Support for high current devices (such as Blade Servers) in select models
• The ability to diagnose the network, such as pinging a host or listing TCP connections
• Full disaster recovery option in case of a catastrophic failure during a firmware upgrade
• The ability to display temperatures in Celsius or Fahrenheit, height in meters or feet, and pressure in Pascal or psi according to user credentials

Package Contents

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

Zero U Products

• The Dominion PX device
- Screws, brackets and/or buttons for Zero U
- A null-modem cable with DB9 connectors on both ends (Raritan number: 254-01-0006-00) (optional)
- Cable retention clips for the inlet (for some models only)
- Cable retention clips for outlets (for some models only)

1U Products

• The Dominion PX device
• 1U bracket pack and screws
- A null-modem cable with DB9 connectors on both ends (Raritan number: 254-01-0006-00) (optional)
- Cable retention clips for the inlet (for some models only)

2U Products

• The Dominion PX device
• 2U bracket pack and screws
- A null-modem cable with DB9 connectors on both ends (Raritan number: 254-01-0006-00) (optional)
- Cable retention clips for the inlet (for some models only)

Chapter 2 Rack-Mounting the PDU

This chapter describes how to rackmount a Dominion PX device. To mount a Zero U PX-1000 series PDU, you can use either two buttons or L-brackets that Raritan provided.

In This Chapter

Rackmount Safety Guidelines ....5

Circuit Breaker Orientation Limitation....5

Mounting Zero U Models Using L-Brackets....6

Mounting Zero U Models Using Button Mount ....7

Mounting Zero U Models Using Claw-Foot Brackets 9

Mounting Zero U Models Using Two Rear Buttons....10

Mounting Zero U Models Using L-Brackets and Buttons ......12

Mounting 1U or 2U Models....13

Rackmount Safety Guidelines

In Raritan products which require rack mounting, follow these precautions:

• Operation 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 387) 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.

Circuit Breaker Orientation Limitation

Usually a PDU can be mounted in any orientation. However, when mounting a PDU with circuit breakers, you must obey these rules:

• Circuit breakers CANNOT face down. For example, do not horizontally mount a Zero U PDU with circuit breakers on ceiling.
• If a rack is subject to shock in environments such as boats or airplanes, the PDU CANNOT be mounted upside down. If installed upside down, shock stress reduces the trip point by 10%.

Note: If normally the line cord is down, upside down means the line cord is up.

Mounting Zero U Models Using L-Brackets

If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it.

Technical line drawing of two vertical metal enclosure panels with mounting holes and mounting brackets (no text or symbols)

To mount Zero U models using L-brackets:

1. Align the baseplates on the rear of the Dominion PX 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.

Simple line drawing of a table with four circular components and a lever, no text or symbols present.

1. 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 side of the Dominion PX device.

2. Fasten the brackets in place with at least three screws (one through each slot). Use additional screws as desired.

Chapter 2: Rack-Mounting the PDU

Technical line drawing of a mechanical assembly with three mounting holes and a base plate (no text or symbols)

1. Using rack screws, fasten the Dominion PX device to the rack through the L-brackets.

Mounting Zero U Models Using Button Mount

If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it.

Pure vertical line diagram with two small circular markers on the left side, no text or symbols present.

Isometric line drawing of a vertical rectangular structure with mounting holes and a small circular component on top (no text or symbols)

To mount Zero-U models using button mount:

1. Align the baseplates on the rear of the Dominion PX device. Leave at least 24 inches between the baseplates for stability.

2. Make the baseplates grasp the Dominion PX 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).

Technical line drawing of a mechanical assembly with a screw and mounting base (no text or symbols)

1. Align the large mounting buttons with the mounting holes in the cabinet, fixing one in place and adjusting the other.

2. Loosen the hex socket screws until the mounting buttons are secured in their position.

3. Ensure that both buttons can engage their mounting holes simultaneously.

4. Press the Dominion PX device forward, pushing the mounting buttons through the mounting holes, then letting the device drop about 5/8". This secures the Dominion PX device in place and completes the installation.

Mounting Zero U Models Using Claw-Foot Brackets

If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it.

Technical line drawing of two vertical metal frame structures with mounting holes and mounting brackets (no text or symbols)

To mount Zero U models using claw-foot brackets:

1. Align the baseplates on the rear of the Dominion PX 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 right side of the Dominion PX device.
4. Fasten the brackets in place with at least three screws (one through each slot). Use additional screws as desired.

Technical line drawing of a mechanical assembly with three mounting holes and a base plate (no text or symbols)

1. Using rack screws, fasten the Dominion PX device to the rack through the claw-foot brackets.

Mounting Zero U Models Using Two Rear Buttons

The following describes how to mount a PDU using two buttons only. If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it.

Pure vertical rectangular frame with mounting holes and a small top cap, no text or symbols present

To mount Zero U models using two buttons:

1. Turn to the rear of the PDU.

2. Locate two screw holes on the rear panel: one near the bottom and the other near the top (the side of 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).

Simple line drawing of a mechanical component with a pin and base, no text or symbols present

1. Screw a button in the screw hole near the top. The recommended torque for the button is 1.96 N·m (20 kgf·cm).

2. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously.

3. Press the Dominion PX device forward, pushing the mounting buttons through the mounting holes, then letting the device drop slightly. This secures the Dominion PX device in place and completes the installation.

Mounting Zero U Models Using L-Brackets and Buttons

This section describes how to mount a PDU using L-brackets and two buttons. If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it.

To mount Zero U models using L-brackets and two buttons:

1. Align the two central holes of the L-bracket with the two screw holes on the top of the Dominion PX device.
2. Screw the L-bracket to the device and ensure the bracket is fastened securely.

Simple line drawing of a mechanical assembly with two mounting holes and a base (no text or symbols)

1. Repeat Steps 1 to 2 to screw another L-bracket to the bottom of the device.
2. After both L-brackets are installed on the device, you can choose either of the following ways to mount the device in the rack.
3. Using rack screws, fasten the device to the rack through two identical holes near the edge of each L-bracket.
4. Mount the device by screwing a mounting button in the back center of each L-bracket and then having both buttons engage the mounting holes in the rack. The recommended torque for the button is 1.96 N·m (20 kgf·cm).

Technical line drawing of a mechanical bracket with a fastener and bolt (no text or symbols)

Mounting 1U or 2U Models

Using the appropriate brackets and tools, fasten the 1U or 2U Dominion PX device to the rack or cabinet. If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it.

To mount the Dominion PX device:

1. Attach one rackmount bracket to one side of the Dominion PX device.

a. Align two oval-shaped holes of the rackmount bracket with two threaded holes on one side of the Dominion PX device.
b. Secure the rackmount bracket with two of the Raritan-provided screws.

Note: The appropriate oval-shaped hole locations of the rackmount bracket may vary according to the threaded holes on you model.

Technical line drawing of a device rear panel with mounting holes and labeled ports (no text or symbols present)

1. Repeat Step 1 for securing the other rackmount bracket to the other side of the Dominion PX.
2. Insert one end of the cable-support bar into the L-shaped hole of the rackmount bracket, and align the hole on the end of the bar with the threaded hole adjacent to the L-shaped hole.

Diagram showing a device transitioning from a flat panel to a rectangular panel with circular holes, indicating a process or transformation (no text or symbols present)

1. Secure the cable-support bar with one of the Raritan-provided cap screws.

Technical line drawing of a mechanical component with circular holes and a central bracket (no text or symbols)

1. Repeat Steps 3 to 4 to secure the other end of the cable-support bar to the other rackmount bracket.

Isometric line drawing of a rectangular electronic device with mounting flanges and a central internal component (no text or symbols)

Mount the Dominion PX device on the rack by securing the rackmount brackets' ears to the rack's front rails with your own screws, bolts, cage nuts, or the like.

Chapter 3 Installation and Configuration

This chapter explains how to install a Dominion PX device and configure it for network connectivity.

In This Chapter

Before You Begin 15

Installing Cable Retention Clips on the Inlet (Optional)....17

Connecting the PDU to a Power Source....17

Configuring the Dominion PX....18

Cascading the PDUs via USB....29

Installing Cable Retention Clips on Outlets (Optional)....32

Connecting Environmental Sensors (Optional) 33

Connecting the Asset Management Sensor (Optional)....38

Connecting a Logitech Webcam (Optional)....48

Connecting a GSM Modem (Optional) 48

Connecting a Schroff LHX Heat Exchanger (Optional)....49

Before You Begin

Before beginning the installation, perform the following activities:

• Unpack the product and components
  • Prepare the installation site
  • Fill out the equipment setup worksheet
• Check the branch circuit rating

Unpacking the Product and Components

1. Remove the Dominion PX device and other equipment from the box in which they were shipped. See Package Contents (on page 3) for a complete list of the contents of the box.
2. Compare the serial number of the equipment with the number on the packing slip located on the outside of the box and make sure they match.
3. Inspect the equipment carefully. If any of the equipment is damaged or missing, contact Raritan's Technical Support Department for assistance.
4. Verify that all circuit breakers on the Dominion PX device are set to ON. If not, turn them ON.
   For a PDU with fuses, ensure that all fuses are inserted and seated properly. If there are any fuse covers, ensure that they are closed.

Note: Not all Dominion PX devices have overcurrent protection mechanisms.

Preparing the Installation Site

1. Make sure the installation area is clean and free of extreme temperatures and humidity.

Note: If necessary, contact Raritan Technical Support for the maximum operating temperature for your model. See Maximum Ambient Operating Temperature (on page 387).

1. Allow sufficient space around the Dominion PX device for cabling and outlet connections.
2. Review the Safety Instructions (on page iii) listed in the beginning of this user guide.

Filling Out the Equipment Setup Worksheet

An Equipment Setup Worksheet is provided in this guide. See Equipment Setup Worksheet (on page 389). Use this worksheet to record the model, serial number, and use of each IT device connected to the PDU.

As you add and remove devices, keep the worksheet up-to-date.

Checking the Branch Circuit Rating

This section describes the rating of the branch circuit supplying power to the PDU:

■ The rating of the branch circuit shall be in accordance with national and local electrical codes.
- For North American, the rating of the branch circuit may be up to 125% greater than the rating of the PDU, unless prohibited by national or local electrical codes.

■ 20A for PDUs rated at 16A input current
■ 30A for PDUs rated at 24A input current
■ 40A for PDUs rated at 32A input current
■ 50A for PDUs rated at 35A input current
- 50A for PDUs rated at 40A input current
- 60A for PDUs rated at 45A input current

- In North America, external overcurrent protectors shall be certified by UL/CSA (or equivalent certification). In other regions or countries, make sure they comply with national and local electrical codes.

Installing Cable Retention Clips on the Inlet (Optional)

If your Dominion PX 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, and environments 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.

Zero U models 1U/2U models

Two technical diagrams showing a device with internal components and blue directional arrows indicating movement (no text or symbols)

1. 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

Two technical illustrations of a cable connector with a plug, shown from different angles (no text or symbols present)

Connecting the PDU to a Power Source

1. Verify that all circuit breakers on the Dominion PX device are set to ON. If not, turn them ON.

For a PDU with fuses, ensure that all fuses are inserted and seated properly. If there are any fuse covers, ensure that they are closed.

Note: Not all Dominion PX devices have overcurrent protection mechanisms.

1. Connect each Dominion PX device to an appropriately rated branch circuit. See the label or nameplate affixed to your Dominion PX device for appropriate input ratings or range of ratings.

Note: When a Dominion PX device powers up, it proceeds with the power-on self test and software loading for a few moments. At this time, the outlet LEDs cycle through different colors.

Note: Outlet LEDs are only available on a outlet-switching capable PDU.

1. When the software has completed loading, the outlet LEDs show a steady color and the LED display illuminates.

Configuring the Dominion PX

There are two ways to initially configure a Dominion PX device:

- Connect the Dominion PX device to a computer to configure it, using a serial or USB connection between the Dominion PX and the computer.

The computer must have a communications program such as HyperTerminal or PuTTY.

For a serial connection, you need a null-modem cable with DB9 connectors on both ends (Raritan part number: 254-01-0006-00).

- Connect the Dominion PX device to a TCP/IP network that supports DHCP.

The DHCP-assigned IP address can be retrieved through the Dominion PX's MAC address. You can contact your LAN administrator for assistance. See MAC Address (on page 411).

A Category 5e/6 UTP cable is required for a wired network connection.

Connecting the Dominion PX to a Computer

To configure the Dominion PX using a computer, it must be connected to the computer with an RS-232 serial interface.

These diagrams show the serial port location on different types of PDUs.

Zero U models:

Ranton RESET USB 128-148 USB CONTAIN OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT OUTPUT

1U models:

Raritan 电源输入 电源管理 CORPORATE PRODUCER CURRENT VOLTAGE POWER USB LOAD RESOURCES LINE / CBS / USB RESET 80Hz 60Hz 50Hz 40Hz

2U models:

OUTLET / LONE - CB - GB CONTENTS UNITED BY: POTATO POWER USB SUPPORT USB PC CONSOLE / BIOSCI AC UP Power LUX Control

If your computer does not have a serial port, use a regular USB cable to connect the Dominion PX to the computer for initial configuration. The Dominion PX device can emulate a USB-to-serial converter after the USB-to-serial driver is properly installed in the Windows® operating system.

Note: Not all serial-to-USB converters work properly with the Dominion PX device so this section does not introduce the use of such converters.

Now connect the Dominion PX to a computer for initial configuration by following either of the following procedures.

To make a serial connection:

1. Connect one end of the null-modem cable to the RS-232 port labeled CONSOLE / MODEM on the Dominion PX.
2. Connect the other end of the null-modem cable to the serial port (COM) on the computer.

To make a USB connection:

1. Connect one end of a regular USB cable to the USB-B port on the Dominion PX.
2. Connect the other end of the USB cable to the USB-A port on the computer.

Note: If you plan to use the serial connection to log in to the command line interface, leave the cable connected after the configuration is complete.

Installing the USB-to-Serial Driver

The Dominion PX can emulate a USB-to-serial converter over a USB connection. A USB-to-serial driver named "Dominion Serial Console" is required for Microsoft® Windows® operating systems. Download the dominion-serial.zip driver file, which contains dominion-serial.inf and dominion-serial-setup.exe files, from the following URL on the Raritan website:

http://www.raritan.com/support/dominion-px/2.2.0/dominion-px2 series-usb-serial-driver.

To install the driver in Windows ^® Vista and 7:

1. Disconnect the Dominion PX's USB cable from the computer.
2. Run dominion-serial-setup.exe. A Dominion Serial Console Driver Setup Wizard appears.
3. Click Install to install the driver.
4. Click Finish when the installation is complete.
5. Connect the Dominion PX's USB cable to the computer. The driver is automatically installed.

To install the driver in Windows ^® XP:

1. Disconnect the Dominion PX's USB cable from the computer.
2. Check if the file "usbser.sys" is available in C:\Windows\ServicePackFiles\i386. If not, extract it from the Windows installation CD disc, and copy it to the same directory where the USB-to-serial driver is stored.

3. On a CD disc with SP3 included, it is extracted from I386\SP3.CAB.

4. On a CD disc with SP2 included, it is extracted from I386\SP2.CAB.

5. On a CD without an SP, it is extracted from I386\DRIVER.CAB.

6. Connect the Dominion PX's USB cable to the computer.

7. 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, right-click the Dominion Serial Console, and choose Update Driver.
8. Select "Install from a list or specific location," and specify the location where the driver is stored.
9. If you see the message requesting the file "usbser.sys," specify the location of the file.
10. The installation is complete.

In Linux:

No additional drivers are required, but you must provide the name of the tty device, which can be found in the output of the "dmesg" after connecting the Dominion PX to the computer. Usually the tty device is "/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
connect

Connecting the Dominion PX to Your Network

To use the web interface to administer the Dominion PX, you must connect the Dominion PX to your local area network (LAN). The Dominion PX can be connected to a wired or wireless network.

Note: If your PDU is not implemented with the wireless networking feature or if it will be used as a master device in the USB cascading configuration, make a wired connection.

To make a wired connection:

1. Connect a standard Category 5e/6 UTP cable to the ETHERNET port on the Dominion PX.
2. Connect the other end of the cable to your LAN.

See this diagram for the ETHERNET port location on Zero U models.

Ronlon RESET MODE/USB CURRENT USB VOLTAGE USB POWER USB URLONG USB Ethernet USB-B SEWER CONSENSY/HOBOU

For 1U/2U models, the ETHERNET port is usually located on the back except for a few models. This diagram shows the port on the back.

SENSOR 1 SENSOR 2 ETHERNET FEATURE

For 2U models, the ETHERNET port is located on the front. This diagram shows the port on a 2U model.

To make a wireless connection:

Do one of the following:

• Plug a 802.11n wireless USB LAN adapter into the USB-A port on your Dominion PX.
• Connect a USB docking station to the USB-A port on the Dominion PX and plug the 802.11n wireless USB LAN adapter into the appropriate USB port on the docking station.

Supported Wireless LAN Configuration

If you select the wireless connection, ensure that both of your wireless USB LAN adapter and wireless network configuration meet the following requirements.

■ Network type: 802.11n
■ Protocol: WPA2 (RSN)
■ Key management: WPA-PSK
■ Encryption: CCMP (AES)

Important: Currently only Raritan-provided wireless USB LAN adapters are supported. You may contact Raritan Technical Support for this information.

Initial Network Configuration

After the Dominion PX device is connected to your network, you must provide it with an IP address and some additional networking information.

This section describes the initial configuration via a serial or USB connection.

Note: To configure the Dominion PX via the LAN, see Using the Web Interface (on page 65) for using the web interface.

To configure the Dominion PX device:

1. Go to the computer that you connected to the Dominion PX and open a communications program such as HyperTerminal or PuTTY.

2. Select the appropriate COM port, and make sure the port settings are configured as follows:

3. Bits per second = 115200 (115.2Kbps)

4. Data bits = 8
5. Stop bits = 1
6. Parity = None
   ■ Flow control = None

Tip: For a USB connection, you can find out which COM port is assigned to the Dominion PX by choosing Control Panel > System > Hardware > Device Manager, and locating the "Dominion Serial Console" under the Ports group.

1. Press Enter.
2. The Dominion PX prompts you to log in. Note that both of user name and password are case sensitive.

a. At the Username prompt, type admin and press Enter.
b. At the Password prompt, type raritan and press Enter.

1. You are prompted to change the password if this is the first time you log in to the Dominion PX. Follow the onscreen instructions to type your new password.
2. The # prompt appears when you log in successfully.
3. Type config and press Enter.
4. To configure network settings, type appropriate commands, and press Enter. All commands are case sensitive.

a. To set the networking mode, type this command:

network mode

where is either wired for wired connection (default) or wireless for wireless connection.

b. For the wired network mode, you may configure the LAN interface settings. In most scenarios, the default setting (auto) works well and should not be changed unless required.

To set Use this command
LAN interface speed	network interface LANInterfaceSpeedwhereis auto, 10Mbps, or 100Mbps.
LAN interface duplex mode	network interface LANInterfaceDuplexModewhereis half, full or auto.

Tip: You can combine multiple commands to configure multiple parameters at a time. For example, network interface LANInterfaceSpeed LANInterfaceDuplexMode

c. For the wireless network mode, you must configure the Service Set Identifier (SSID) parameter.

To set Use this command
SSID	network wireless SSIDwhereis the SSID string.

If necessary, configure more wireless parameters shown in the following table.

To set Use this command
BSSID	network wireless BSSIDwhereis the AP MAC address.
Authentication method	network wireless authMethodwhereis psk for Pre-Shared Key or eap for Extensible Authentication Protocol.
PSK	network wireless PSKwhereis the PSK string.
EAP outer authentication	network wirelesseapOuterAuthenticationwhereis PEAP.
EAP inner authentication	network wirelesseapInnerAuthenticationwhereis MSCHAPv2.
EAP identity	network wireless eapIdentitywhereis your user name for EAP authentication.
EAP password	network wireless eapPasswordWhen prompted to enter the password for EAP authentication, type the password.
EAP CA certificate	network wirelesseapCACertificateWhen prompted to enter the CA certificate, open the certificate with a text editor, copy and paste the content into the communications program.

Note: The content to be copied from the CA certificate does NOT include the first line containing "BEGIN CERTIFICATE" and the final line containing "END CERTIFICATE."
d. To determine which IP protocol is enabled and which IP address returned by the DNS server is used, configure the following parameters.

To set Use this command
IP protocol	network ip protowhereis v4Only for enabling IPv4, v6Only for enabling IPv6 or both for enabling both IPv4 and IPv6 protocols.
IP address returned by the DNS server	network ipdnsResolverPreferencewhereis preferV4 for IPv4 addresses or preferV6 for IPv6 addresses.

e. If you enabled the IPv4 protocol in the previous step, configure the IPv4 network parameters.

To set Use this command
IP configuration method	network ipv4ipConfigurationModewhereis either dhcp for auto configuration (default) or static for specifying a static IP address.

- For the IPv4 DHCP configuration, configure this parameter.

To set Use this command
Preferred host name (optional)	network ipv4 preferredHostNamewhereis the preferred host name.

Tip: To override the DHCP-assigned IPv4 DNS servers with those you specify manually, type this command:

network ipv4 overrideDNS

where is enable or disable. See the table below for the IPv4 commands for manually specifying DNS servers.

- For the static IPv4 configuration, configure these parameters.

To set Use this command
Static IPv4 address	network ipv4 ipAddressis the IP address you want to assign.
Subnet mask	network ipv4 subnetMaskis the subnet mask.
Gateway	network ipv4 gatewayis the IP address of the gateway.
Primary DNS server	network ipv4 primaryDNSServeris the IP address of the primary DNS server.
Secondary DNS server (optional)	network ipv4secondaryDNSServeris the IP address of the secondary DNS server.

f. If you enabled IPv6 in the earlier step, configure the IPv6 network parameters.

To set Use this command
IP configuration method	network ipv6ipConfigurationModewhereis either automatic for auto configuration (default) or static for specifying a static IP address.

Tip: To override the DHCP-assigned IPv6 DNS servers with those you specify manually, type this command:

network ipv6 overrideDNS

where is enable or disable. See the table below for the IPv6 commands for manually specifying DNS servers.

- For the static IPv6 configuration, you should configure the following parameters. Note that the IP address must follow the IPv6 format.

To set Use this command
Static IPv6 address	network ipv6 ipAddressis the IP address you want to assign.
Gateway	network ipv6 gatewayis the IP address of the gateway.
Primary DNS server	network ipv6 primaryDNSServeris the IP address of the primary DNS server.
Secondary DNS server (optional)	network ipv6secondaryDNSServeris the IP address of the secondary DNS server.

1. To quit the configuration mode with or without saving the changes, type either command, and press Enter.

Command Description
apply	Save all configuration changes and quit the configuration mode.
cancel	Abort all configuration changes and quit the configuration mode.

The # prompt appears, indicating that you have quit the configuration mode.

1. To verify whether all settings are correct, type the following commands one by one. Current network settings are displayed.

Command Description
show network	Show network parameters.
show network ip all	Show all IP configuration parameters.
show network wireless details	Show all wireless parameters. (Perform this command only when you enable the wireless mode.)

Tip: You can also type "show network wireless" to display a shortened version of wireless settings.

1. If all are correct, type exit to log out of the Dominion PX. If any are incorrect, repeat Steps 7 to 10 to change any network settings.

The IP address configured may take seconds to take effect.

Cascading the PDUs via USB

A maximum of four identical or different Dominion PX models can be cascaded via the USB interface. The first device is the master device and all subsequent devices connected to it are slave devices. The master device shares its wired networking with the slave devices by functioning as a network bridge that transmits IP packets between the LAN and slave devices. You can access the slave devices via the Web, SNMP, SSH or Telnet interface.

The USB cascading configuration only supports wired networking so you must make sure:

• The master device has the "wired" Ethernet connectivity.
• None of the slave devices have the wired Ethernet connectivity.
If any slave device is connected to the LAN through a networking cable, its wired Ethernet interface is automatically disabled.
• None of the devices in the daisy chain has the wireless connectivity.

Important: Only Dominion PX devices whose model names begin with PX2 support the USB cascading function.

To cascade the Dominion PX devices:

1. Verify the firmware version of the Dominion PX devices meet the requirement below. If not, upgrade these devices. See Updating the Dominion PX Firmware (on page 219).

- Dominion PX: version 2.3 or later

1. Determine which device is used as the master device.

- The master device must be connected to the LAN via a standard Category 5e/6 UTP cable.

1. Connect the USB-A port of the master device to the USB-B port of another Dominion PX device via an USB cable.

- The device connected to the master device is the first slave device.

1. Connect the USB-A port of the first slave device to the USB-B port of another Dominion PX device via an USB cable.

- The device connected to the first slave device is the second salve device.

1. Connect the USB-A port of the second slave device to the USB-B port of another Dominion PX device via an USB cable.

- The device connected to the second slave device is the third slave device.

Chapter 3: Installation and Configuration

graph TD
    A["LAN"] --> B["1"]
    B --> C["2"]
    C --> D["3"]
    D --> E["4"]
    B --> F["USB-A"]
    C --> G["USB-B"]
    D --> H["USB-A"]
    D --> I["USB-B"]
    F <--> G
    G <--> H
    H <--> I

Number Device role
1	Master device
2	The first slave device
3	The second slave device
4	The third slave device

Note: On a master device, the networking mode shows "Wired." On a slave device, the networking mode shows "Wired(USB)," which indicates it is connected to the LAN through a USB cascading configuration. See Displaying the PDU Information (on page 82).

Installing Cable Retention Clips on Outlets (Optional)

If your Dominion PX 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, and environments 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 you reseller. Make sure you use a clip that fits the power cord snugly to facilitate the installation or removal operation (for servicing).

Note: Some NEMA sockets on PSE-certified PDUs for Japan have integral locking capability and do not need cable retention clips.

To install and use a cable retention clip on the outlet:

1. Locate two tiny holes adjacent to the outlet.
2. Install the cable retention clip by inserting two ends of the clip into the tiny holes.

Diagram showing three electrical socket blocks connected by a line, with blue arrows indicating direction of movement or connection.

1. 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 area holding the plug should face downwards toward the ground, like an inverted "U". This allows gravity to keep the clip in place.

Diagram of a plug inserted into three outlets (no text or symbols present)

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

Tip: Raritan also provides other mechanisms to securely hold the power cords in place. See Locking Outlets and Cords (on page 411).

Connecting Environmental Sensors (Optional)

To enable the detection of environmental factors around the Dominion PX, connect one or more Raritan environmental sensors to the Dominion PX device.

The maximum distance for all sensor cabling plugged into the product's sensor port should not exceed 30 meters/100 feet. Contact Raritan Technical Support if you have questions.

You can connect up to 16 environmental sensors to a Dominion PX device by using a Raritan sensor hub.

Note that a Raritan environmental sensor usually contains more than one sensor. For example, a DPX-T2H2 counts as 4 sensors, and a DPX-T3H1 counts as 4 sensors.

Warning: For proper operation, wait for 15\~30 seconds between each connection operation or each disconnection operation of environmental sensors.

To directly connect one or multiple environmental sensors:

- Plug the connector of the environmental sensor into the SENSOR port on your Dominion PX device.

Note: Depending on the model you purchased, the total number of SENSOR ports varies.

To connect environmental sensors via an optional PX sensor hub:

1. Connect a Raritan sensor hub to the Dominion PX device.

a. Plug one end of the Raritan-provided phone cable (4-wire, 6-pin, RJ-12) into the IN port (Port 1) of the hub. b. Plug the other end into the SENSOR port on the Dominion PX device.

1. Connect Raritan environmental sensors to any of the four OUT ports on the hub.

Raritan sensor hubs CANNOT be cascaded so at most a sensor hub can be connected to each SENSOR port on the Dominion PX device. This diagram illustrates a configuration with a sensor hub connected.

Diagram showing a rack-mounted device connected to a power bank via four labeled wires, with a red arrow indicating 'IN' pointing to the rack.

1	The Dominion PX device
2	Raritan-provided phone cable
3	Raritan PX sensor hub
4	Raritan environmental sensors

1. If there are any Raritan air flow sensors attached, make sure that sensor faces the source of the wind (such as a fan) in the appropriate orientation as indicated by the arrow on that sensor.

Diagram showing a wind turbine connected to a device with bidirectional arrows indicating signal flow.

About Contact Closure Sensors

Raritan's contact closure sensor (DPX-CC2-TR) can detect the open-and-closed status of the connected detectors/switches.

This feature requires the integration of at least a discrete (on/off) detector/switch to work properly. The types of discrete detectors/switches that can be plugged into DPX-CC2-TR include those for:

• Door open/closed detection
- Door lock detection
• Floor water detection
- Smoke detection
- Vibration detection

Raritan does NOT provide discrete detectors/switches. They are third-party probes, so you must test them with Raritan's DPX-CC2-TR to ensure they work properly.

Important: Integration and testing for third-party detectors/switches is the sole responsibility of the customer. Raritan cannot assume any liability as a result of improper termination or failure (incidental or consequential) of third-party detectors/switches that customers provide and install. Failure to follow installation and configuration instructions can result in false alarms or no alarms. Raritan makes no statement or claim that all third-party detectors/switches will work with DPX-CC2-TR.

Connecting Third-Party Detectors/Switches to DPX-CC2-TR

A DPX-CC2-TR unit provides two channels for connecting two third-party detectors/switches. There are four spring-loaded termination points on the body of DPX-CC2-TR: the two to the right are associated with one channel (as indicated by the LED number), and the two to the left are associated with another channel. You must plug the third-party detectors/switches into these termination points.

To connect third-party detectors/switches:

1. Strip the insulation around 12mm from the end of each wire of two third-party detectors/switches.
2. Press and hold down the tiny rectangular buttons above the termination points on the body of DPX-CC2-TR.

Note: Each button controls the spring of each corresponding termination point.

Line drawing of a plug with three pins and a black arrow pointing to one end (no text or symbols)

1. Fully insert each wire of both third-party detectors/switches into each termination point.

2. Plug both wires of a detector/switch into the two termination points to the left.

3. Plug both wires of another detector/switch into the two termination points to the right.

Line drawing of a mechanical component with multiple wires extending from its side (no text or symbols)

1. Release the tiny rectangular buttons after inserting the wires properly.
2. Verify that these wires are firmly fastened.

Configuring a Contact Closure Sensor

Before using DPX-CC2-TR to detect the contact closure status, water, smoke or vibration, you must determine the normal state by adjusting its dip switch, which controls the LED state on the body of DPX-CC2-TR. A dip switch is associated with a channel.

▶ To adjust the dip switch setting:

1. Place the detectors/switches connected to DPX-CC2-TR to the position where you want to detect a specific environmental situation.
2. Uncover the dip switch on the body of DPX-CC2-TR.

Line drawing of a mechanical device with a labeled component (no text or symbols)

1. To set the Normal state for channel 1, locate the dip switch labeled 1.

2. Use a pointed tip such as a pen to move the slide switch to the end labeled NO (Normally Open) or NC (Normally Closed).

3. Normally Open: The open status of the connected detector/switch is considered normal.

4. Normally Closed: The closed status of the connected detector/switch is considered normal. This is the default.

Diagram of a microfluidic chip being inserted into a housing (no text or symbols)

1. To set the Normal state for channel 2, repeat Step 4 for adjusting the other dip switch's setting.
2. Install back the dip switch cover.

Note: The dip switch setting must be properly configured, or the sensor LED may be incorrectly lit in the Normal state.

Contact Closure Sensor LEDs

DPX-CC2-TR is equipped with the LEDs for showing the state of the connected detectors/switches.

The LED is lit when the associated detector/switch is in the "abnormal" state, which is the opposite of the Normal state. See Configuring a Contact Closure Sensor (on page 36) for how to set the Normal state.

The meaning of a lit LED varies depending on the Normal state settings.

- When the Normal state is set to Closed:

LED Sensor state
Not lit Closed
Lit	Open

- When the Normal state is set to Open:

LED Sensor state
Not lit Open
Lit	Closed

How to Connect Differential Air Pressure Sensors

You can have a Raritan differential air pressure sensor connected to the Dominion PX device if the differential air pressure data is desired.

With this sensor, the temperature around the sensor can be also detected through a temperature sensor implemented inside it.

To connect a differential air pressure sensor:

1. Plug one end of a Raritan-provided phone cable to the SENSOR port of the Dominion PX device.
2. Plug the other end of this phone cable to the IN port of the differential air pressure sensor.

1	The Dominion PX device
2	The Raritan differential air pressure sensor

① ② IN OUT IN OUT IN

Connecting the Asset Management Sensor (Optional)

You can remotely track the locations of up to 64 IT devices in the rack by connecting an asset management sensor (asset sensor) to the Dominion PX after these IT devices are tagged electronically.

To use this asset management feature, you need the following items:

• Raritan asset sensors: An asset sensor transmits the tagging and positioning information to the Dominion PX.
• Raritan asset tags: An asset tag electronically tags the IT device where it is attached.

Combining Asset Sensors

Each tag port on the asset sensors corresponds to a rack unit and can be used to locate the IT devices on a specific rack (or cabinet). For each rack, you can attach asset sensors up to 64U long, consisting of one MASTER and multiple SLAVE asset sensors. The difference between the master and slave asset sensors is that the master asset sensor has an RJ-45 connector while the slave one does not.

The following diagram illustrates some asset sensors. Note that Raritan provides more types of asset sensors than the diagram.

Three technical line drawings of vertical metal beams with mounting holes, labeled ①, ②, and ③ (no text or symbols on the beams themselves)

Number Item
1	8U MASTER asset sensor with 8 tag ports
2	8U SLAVE asset sensor with 8 tag ports
3	5U "ending" SLAVE asset sensor with 5 tag ports

Note: Unlike regular slave asset sensors, which have one DIN connector respectively on either end, the ending slave asset sensor has one DIN connector on only one end. An ending asset sensor is installed at the end of the asset sensor assembly.

To assemble asset sensors:

1. Connect a MASTER asset sensor to an 8U SLAVE asset sensor.

- Plug the white male DIN connector of the slave asset sensor into the white female DIN connector of the master asset sensor.

■ Make sure that the U-shaped sheet metal adjacent to the male DIN connector is inserted into the rear slot of the master asset sensor. Screw up the U-shaped sheet metal to reinforce the connection.

Diagram showing a mechanical assembly process with labeled components and directional arrow indicating motion or transformation.

1. Connect another 8U slave asset sensor to the one being attached to the master asset sensor in the same manner as Step 1.

2. Repeat the above step to connect more slave asset sensors. The length of the asset sensor assembly can be up to 64U.

3. The final asset sensor can be 8U or 5U, depending on the actual height of your rack.

4. Using the "ending" asset sensor as the final asset sensor is strongly recommended.

5. Vertically attach the asset sensor assembly to the rack, next to the IT equipment, making each tag port horizontally align with a rack unit. The asset sensors are automatically attracted to the rack because of magnetic stripes on the back.

Note: The asset sensor is implemented with a tilt sensor so it can be mounted upside down.

Connecting Asset Sensors to the Dominion PX

You need both of asset sensors and asset tags for tracking IT devices. Asset tags, which are affixed to IT devices, provide an ID number for each IT device, while the asset sensors transmit ID numbers and positioning information to the connected Dominion PX device.

The following diagram illustrates an asset tag.

A B A C

Letter Item

A Barcode	(ID number), which is available oneither end of the asset tag
B	Tag connector
C Adhesive area with the tape

Note: The barcode of each asset tag is unique and is displayed in the Dominion PX web interface so it can easily be identified.

To connect asset sensors to the Dominion PX device:

1. Affix the adhesive end of an asset tag to each IT device through the tag's tape.
2. Plug the connector on the other end of each asset tag into the corresponding tag port on the asset sensor.
3. Connect the asset sensor assembly on the rack to the Dominion PX device by following this procedure:

a. Connect one end of the Category 5e/6 cable to the RJ-45 connector on the MASTER asset sensor.

b. Connect the other end of the cable to the FEATURE port on the Dominion PX device.

The Dominion PX device supplies power to the asset sensor assembly through the Category 5e/6 cable. All LEDs on the asset sensor assembly may cycle through different colors during the power-on process if the asset sensor's firmware is being upgraded by the Dominion PX device. After the power-on or firmware upgrade process completes, the LEDs show solid colors. Note that the LED color of the tag ports with asset tags connected will be different from the LED color of the tag ports without asset tags connected.

A ③ ② B ① D C

Letter Item
A The Dominion PX device
B	Asset sensors
C	Asset tags
D IT devices, such as servers

Note: The Dominion PX cannot detect how many rack units the connected asset sensor(s) has. You must provide the information to it manually. See Configuring the Asset Sensor (on page 196).

Connecting Blade Extension Strips

For blade servers, which are contained in a single chassis, you can use a blade extension strip to track individual blade servers.

Raritan's blade extension strip functions similar to a Raritan asset sensor but requires a tag connector cable for connecting to a tag port on the regular asset sensor or AMS-M2-Z. The blade extension strip contains 4 to 16 tag ports, depending on which model you purchased.

The diagram illustrates a tag connector cable and a blade extension strip with 16 tag ports.

Tag connector cable

Item Description

A Barcode	(ID number) for the tag connector cable
B	Tag connector
C Cable	connector for connecting the blade extension strip

Note: A tag connector cable has a unique barcode, which is displayed in the Dominion PX's web interface for identifying each blade extension strip where it is connected.

Blade extension strip

D F E F

Item Description

D	Mylar section with the adhesive tape

E

Tag

ports

F	Cable socket(s) for connecting the tag connector cable

Note: Each tag pot on the blade extension strip is labeled a number, which is displayed as the slot number in the Dominion PX's web interface.

To install a blade extension strip:

1. Connect the tag connector cable to the blade extension strip.

- Plug the cable's connector into the socket at either end of the blade extension strip.

Diagram showing a device connected to a panel with labeled pins and an arrow indicating direction

1. Move the blade extension strip toward the bottom of the blade chassis until its mylar section is fully under the chassis, and verify that the blade extension strip does not fall off easily. If necessary, you may use the adhesive tape in the back of the mylar section to help fix the strip in place.

Diagram illustrating a mechanical assembly process with labeled components and directional arrow

1. Connect one end of an asset tag to a blade server and connect the other end to the blade extension strip.

a. Affix the adhesive part of the asset tag to one side of a blade server through the tag's tape.

b. Plug the tag connector of the asset tag into the tag port on the blade extension strip.

Diagram showing a computer monitor with an open door and a close-up view of the screen with a red arrow indicating motion (no text or symbols present)

1. Repeat the above step until all blade servers in the chassis are connected to the blade extension strip via asset tags.
2. Plug the tag connector of the blade extension strip into the closest tag port of the asset sensor assembly or the AMS-M2-Z asset sensor on the rack.

Diagram of a mechanical device with curved blades and a vertical scale, showing no text or symbols.

Note: If you need to temporarily disconnect the tag connector of the blade extension strip, wait at least 1 second before connecting it back, or the Dominion PX may not detect it.

Connecting AMS-M2-Z Asset Sensors (Optional)

The AMS-M2-Z is a special type of asset sensor that functions the same as regular MASTER asset sensors with the following differences.

• It provides two RJ-45 connectors.
  • Multiple AMS-M2-Z asset sensors can be daisy chained.
• Only two tag ports are available on each AMS-M2-Z so only two asset tags can be connected.

This product is especially useful for tracking large devices such as SAN boxes in the cabinet.

A B

Item Description
A	RJ-45	connectors
B	Tag	ports

To connect the AMS-M2-Z asset sensors to the Dominion PX:

1. Connect the AMS-M2-Z to the Dominion PX via a Category 5e/6 cable.

a. Connect one end of the cable to the RJ-45 port labeled "Input" on the AMS-M2-Z.
b. Connect the other end of the cable to the FEATURE port on the Dominion PX.

1. Affix an asset tag to the IT device and connect this asset tag to the AMS-M2-Z by plugging the tag connector into the tag port on the AMS-M2-Z. See Connecting Asset Sensors to the Dominion PX (on page 41) for details.

2. If necessary, daisy chain multiple AMS-M2-Z to track more than two IT devices via this Dominion PX.

a. Verify that the Category 5e/6 cable length is within the limitation. See AMS-M2-Z Daisy-Chain Limitations (on page 47) for the cable length limitations.
b. Connect one end of the Category 5e/6 cable to the RJ-45 connector labeled "Output" on the AMS-M2-Z being connected to the Dominion PX.

c. Connect the other end of the cable to the RJ-45 connector labeled "Input" on another AMS-M2-Z.
d. Repeat the above steps to daisy chain additional AMS-M2-Z. See AMS-M2-Z Daisy-Chain Limitations (on page 47) for the maximum number of AMS-M2-Z asset sensors supported in the chain.
e. It is highly recommended using the cable ties to help hold the weight of all connecting cables.

Diagram of a network device with two connected cable links (no text or symbols)

1. Repeat Step 2 to connect IT devices to the other AMS-M2-Z's in the chain via the asset tags.

AMS-M2-Z Daisy-Chain Limitations

There are some limitations when daisy chaining the AMS-M2-Z asset sensors. The limitations vary according to the Raritan product model connected to the first AMS-M2-Z.

Models Daisy-chain limitations
All PDUs whose model names begin with PX2	Up to 2 AMS-M2-Z can be daisy chained.The maximum cable length between each AMS-M2-Z in the chain is 2 meters.
EMX2-111	Up to 2 AMS-M2-Z can be daisy chained.The maximum cable length between each AMS-M2-Z in the chain is 2 meters.
EMX2-888	Up to 6 AMS-M2-Z can be daisy chained.The maximum cable length between each AMS-M2-Z in the chain is 3 meters.

Connecting a Logitech Webcam (Optional)

The Dominion PX supports Logitech ^® QuickCam ^® Pro 9000 webcams connected to it, allowing you to view video or snapshots of the area surrounding the webcam. The Dominion PX supports up to one webcam. After connecting a webcam, you can visually monitor environmental conditions near the Dominion PX through the web interface from anywhere.

For more information on the QuickCam webcam, see the user documentation accompanying it.

To connect a webcam:

1. Connect the webcam to the USB-A port on the Dominion PX device. The Dominion PX automatically detects the webcam.
2. Position the webcam properly.

Static images or videos captured by the webcam are immediately displayed in the Dominion PX web interface. See Viewing the Webcam Images or Videos (on page 206).

Connecting a GSM Modem (Optional)

A Cinteron ^® MC52i/MC55iGSM modem must be connected to the Dominion PX in order to send SMS event messages. See Creating Actions (on page 156) for more information on SMS event messages.

Note: The Dominion PX cannot receive SMS messages.

To connect the GSM modem:

1. Connect the GSM modem to the DB9 serial port on the Dominion PX.
2. Configure the GSM modem as needed. See the supporting GSM modem help for information on configuring the GSM modem.

Connecting a Schroff LHX Heat Exchanger (Optional)

To remotely monitor and administer the Schroff® LHX-20 or LHX-40 heat exchangers through the Dominion PX device, you must establish a connection between the heat exchanger and the Dominion PX device. Note that only the PDUs whose model names begin with PX2 support the LHX heat exchangers.

For more information on the LHX heat exchanger, see the user documentation accompanying that product.

To establish a connection between the PDU and LHX heat exchanger, an RJ-45 to RS-232 adapter cable provided by Schroff is required.

To connect an LHX heat exchanger:

1. Plug the RS-232 DB9 end of the adapter cable into the RS-232 port on the Schroff LHX heat exchanger.
2. Plug the RJ-45 end of the cable into the port labeled FEATURE on your Dominion PX device.

See Managing the Schroff LHX Heat Exchanger (on page 212) for enabling the support of the LHX heat exchanger.

Chapter 4 Using the PDU

This chapter explains how to use the Dominion PX device. It describes the LEDs and ports on the PDU, and explains how to use the LED display panel. It also explains how the circuit breaker (overcurrent protector) works and when the beeper sounds.

In This Chapter

Panel Components....50

Circuit Breakers....59

Fuse....61

Beeper 64

Panel Components

The Dominion PX comes in Zero U, 1U, and 2U sizes. All types of models come with the following components on the outer panels.

• Power cord
• Outlets
• Connection ports
• LED display
• Reset button

Power Cord

Most of Raritan PDUs come with an installed power cord, which is ready to be plugged into an appropriate receptacle for receiving electricity. Such devices cannot be rewired by the user.

Connect each Dominion PX device to an appropriately rated branch circuit. See the label or nameplate affixed to your Dominion PX device for appropriate input ratings or range of ratings.

There is no power switch on the Dominion PX device. To power cycle the PDU, unplug it from the branch circuit, wait 10 seconds and then plug it back in.

Outlets

The total number of outlets varies from model to model.

PX-1000 Series

These PDUs are NOT outlet-switching capable models so all outlets are always in the ON state.

Outlet LEDs are not available.

PX-2000 Series

These models are outlet-switching capable PDUs. A small LED is adjacent to each outlet to indicate the state of the relay board.

LED state Outlet status What it means
Not lit Powered OFF		The outlet is not connected to power, or the control circuitry's power supply is broken.
Red	ON and LIVE LIVE power. The outlet is on and power is available.
	ON and NOT LIVE	The outlet is turned on but power is not available because a circuit breaker has tripped.

Connection Ports

Depending on the model you purchased, the total number of ports available varies.

- For most of Zero U models, there are 6 ports located on the front panel as shown below.

FEATURES USB-D SENSOR ETHERNET USB-A CONSOLE/MODEM

- For most of 1U and 2U models, there are 7 ports located on front and back panels respectively.

- Front panel ports:

1U

2U

USB-A USB-B CONSOLE / MODEM

- Back panel ports:

SENSOR 1 SENSOR 2

ETHERNET FEATURE

The only port difference between Zero U, 1U and 2U models is that Zero U models provide only one sensor port while 1U and 2U models provide two.

The table below explains the function of each port.

Port Used for...
USB-B Establishing	a USB connection between a computer and the Dominion PX device.This port can be used for disaster recovery of the Dominion PX device.Contact Raritan Technical Support for instructions.
USB-A Connecting	a USB device.This is a "host" port, which is powered, per USB 2.0 specifications.
FEATURE Connection to some Raritan access products (such as Dominion KX II) through the use of a power CIM, OR --Connection to a Schroff® LHX-20 or LHX-40 device through a RJ-45 to RS-232 cable provided by Schroff, OR --Connection to a Raritan asset management sensor, which allows you to track the locations of the IT devices on the rack. SeeConnecting the Asset Management Sensor (Optional) (on page 38).
CONSOLE/MODEM	Establishing a serial connection between a computer and the Dominion PX device:This is a standard DTE RS-232 port. You can use a null-modem cable with two DB9 connectors on both ends to connect the Dominion PX device to the computer.
SENSOR Connection to Raritan's environmental sensors.
ETHERNET Connecting the Dominion PX device to your company's network:
		Note: Connection to this port is not required if the Dominion PX device is connected to a wireless network.

LED Display

The LED display is located on the side where outlets are available.

These diagrams show the LED display on different types of PDUs. Note that the LED display might slightly vary according to the PDU you purchased.

Zero U models:

LINE/CB/UB UP BOTH DOWN CURRENT (A) VOLTAGE (V) POWER (W) UB LOAD (N) SENSOR

1U models:

CURRENT (A) VOLTAGE (V) POWER (kW) US LOAD (%) SENSOR LINE / CB / US RESET UP BOTH DOWN

2U models:

OUTLET / LINE / CS / UB CURRENT ○ (41) VOLTAGE ○ (91) POWER ○ (MW) UB LOAD ○ (51) SENSOR ○ △ UP ○ BOTH ○ RESET ▽ DOWN

The LED display consists of:

• A row displaying three digits
• A row displaying two digits
- Up and Down buttons

- Five LEDs for measurement units

A Zero U model can detect its own orientation through the built-in tilt sensor and automatically changes the direction of the alphanumeric digits shown on the LED display for easy reading. To lock the direction of the digits shown on the LED display, you can set the display orientation using the command line interface. See Changing the LED Display Orientation (on page 262).

Note: When a Dominion PX device powers up, it proceeds with the power-on self test and software loading for a few moments. When the software has completed loading, the LED display illuminates.

Three-Digit Row

The three-digit row shows the readings for the selected component. Values that may appear include:

• Active power or unbalanced load of the inlet
• Current of the selected circuit breaker
- Current, voltage, or active power of the selected line

Note: L1 voltage refers to the L1-L2 or L1-N voltage, L2 voltage refers to the L2-L3 or L2-N voltage, and L3 voltage refers to the L3-L1 or L3-N voltage.

• The text "FuP," which indicates that the Firmware uPgrade is being performed
• The text "CbE," which indicates the selected circuit breaker has tripped

LEDs for Measurement Units

Five small LED indicators are on the LED display: four measurement units LEDs and one Sensor LED.

The measurement units vary according to the readings that appear in the three-digit row. They are:

• Amp (A) for current
• Volt (V) for voltage
• Kilowatt (kW) for active power
  • Percentage (%) of the unbalanced load

One of the measurement unit LEDs will be lit to indicate the unit for the value currently shown in the three-digit row.

The Sensor LED is lit only when Dominion PX detects the physical connection of any environmental sensor.

The five LEDs look similar to this diagram but may slightly vary according to the model you purchased.

Two-Digit Row

The two-digit row shows the number of the currently selected outlet, line or circuit breaker. Values that may appear include:

• Two-digit numbers: This indicates the selected outlet. For example, 03 indicates outlet 3.
• Cx: This indicates the selected circuit breaker, where x is the circuit breaker number. For example, C1 represents Circuit Breaker 1.
• Lx: This indicates the selected line of a single-inlet PDU, where x is the line number. For example, L2 represents Line 2.

Note: For a single-phase model, L1 current represents the Unit Current.

• AP: This indicates the selected inlet's active power.
• UL: This represents the selected inlet or outlet's Unbalanced Load, which is only available for a three-phase PDU.

During the firmware upgrade, some Dominion PX models may show bx in the two-digit row to indicate the relay or meter board numbered x is being updated.

Automatic Mode

When left alone, the LED display cycles through the line readings and circuit breaker readings at intervals of 10 seconds, as available for your Dominion PX. This is the Automatic Mode.

Manual Mode

You can press the Up or Down button to enter the Manual Mode so that a particular line or circuit breaker can be selected to show specific readings.

To operate the LED display:

1. Press the Up or Down button until the desired line or circuit breaker number is selected in the two-digit row. Or you can press either button to select the inlet's active power, which is shown as AP.

2. Pressing the (UP) button moves up one selection.

3. Pressing the (DOWN) button moves down one selection.

4. Current of the selected component is shown in the three-digit row. Simultaneously the CURRENT(A) LED is lit. See LEDs for Measurement Units (on page 56).

5. When selecting a line, you can press the Up and Down buttons simultaneously to switch between voltage, active power and current readings.

6. When the voltage is displayed, the VOLTAGE(V) LED is lit. It is displayed for about five seconds, after which the current reading re-appears.

7. When the active power is displayed, the POWER(kW) LED is lit. It is displayed for about five seconds, after which the current reading re-appears.

8. When selecting the inlet (AP), it displays the active power reading.

- When the active power is displayed, the POWER(kW) LED is lit.

Note: The LED display returns to the Automatic Mode after 20 seconds elapse since the last time any button was pressed.

Reset Button

The reset button is located inside the small hole near the two-digit row.

The Dominion PX device can be reset to its factory default values using this button when a serial connection is available. See Resetting to Factory Defaults (on page 393).

Without the serial connection, pressing this reset button restarts the Dominion PX device's software without any loss of power to outlets. This operation also power cycles the LED display, causing the LED display to go blank and then return to normal.

The following images indicate the locations of the reset button on 0U, 1U and 2U models.

卷Ranlon RESET USB/CB/RB USB/Tu/USB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RGB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RGB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RDB USB/RD310000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

The Dominion PX models rated over 20A (North American) or 16A (international) contain branch circuit breakers. These circuit breakers automatically trip (disconnect power) when the current flowing through the circuit breaker exceeds its rating.

If the circuit breaker switches off power, the LED display shows:

- CbE, which means "circuit breaker error," in the three-digit row.

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.

Depending on the model you purchased, the circuit breaker may use a button- or handle-reset mechanism.

Resetting the Button-Type Circuit Breaker

Your 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 the breaker has tripped.

ON 201 O OFF

1. Examine your Dominion PX device 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 next step.

2. Press the ON button until it is completely down.

ON 20 OFF

Resetting the Handle-Type Circuit Breaker

Your 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 the breaker has tripped.

C8 80°C 40V ABN1277V- pole 20A FA2-C20/CNA

1. Examine your Dominion PX device 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 next step.
2. Pull up the operating handle until the colorful rectangle or triangle turns RED.

LISTED C.B. HPC 4kV 40kV-20kV- Pole 20A FAZ-C20/2-NA

Fuse

Some Dominion PX devices are implemented with fuses instead of circuit breakers. A fuse blows to protect associated outlets if it detects the overload.

If your PDU uses fuses, you must replace it with a new one when it blows or malfunctions. The rating 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 the Zero U model:

1. Lift the hinged cover over the fuse.

Close-up of a black electronic device with a red arrow indicating motion or change (no visible text or symbols)

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

Close-up of a black electronic device with a red circular annotation highlighting a component (no visible text or symbols)

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

Close-up of a black electronic device showing internal components and a magnified view of the internal structure (no text or symbols visible)

1. Take the fuse out of the holder.

Close-up of a black electronic device showing internal components and a magnified inset highlighting a mechanical component (no text or symbols visible)

1. Insert a new fuse into the holder. There is no orientation limit for fuse insertion.
2. 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.

n 12 11 10 ① ②

Number Description

1	Fuse carrier
2	Fuse knob where a fuse is installed

To replace a fuse on the 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.

Two circular metallic objects with internal markings, one showing a horizontal slot and the other with a diagonal slot, both before and after transformation (no text or symbols)

b. Take this knob out of the fuse carrier.

1. 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.

Diagram showing three stages of a mechanical component with numbered labels and an arrow indicating process direction.

Number	Description
1	Fuse knob
2	Fuse

1. 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.

Close-up of a black control panel with numbered buttons and a knife inserted, showing a red arrow pointing to the knife (no text or symbols visible)

b. Gently push this knob into the fuse carrier and then rotate it clockwise until its slot is horizontal.

1. Verify whether this knob's head is aligned with the fuse carrier. If its head is higher or lower than the fuse carrier, re-install it.

Diagram showing three labeled components (①, ②, ③) with cross symbols and colored indicators on a surface.

Number Description

1	INAPPROPRIATE installations
2	Appropriate installation

1. 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 Dominion PX includes a beeper to issue an audible alarm when a significant situation occurs.

• 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.

Chapter 5 Using the Web Interface

This chapter explains how to use the web interface to administer a Dominion PX.

In This Chapter

Supported Web Browsers....65

Logging in to the Web Interface 66

Logout....68

Introduction to the Web Interface 69

Viewing the Dashboard ....81

Device Management....82

User Management....102

Setting Up Roles......107

Access Security Control 110

Setting Up an SSL Certificate....123

Setting Up LDAP Authentication ....128

Outlet Management....133

Inlet and Circuit Breaker Management....147

Setting Power Thresholds 150

Configuring Event Rules....155

Managing Event Logging....181

Viewing Connected Users 183

Monitoring Server Accessibility....184

Environmental Sensors ....186

Asset Management....196

Copying Configurations with Bulk Configuration....201

Changing the Measurement Units....203

Managing the Webcam Images or Videos 205

Network Diagnostics....210

Viewing the Communication Log....211

Downloading Diagnostic Information....212

Managing the Schroff LHX Heat Exchanger 212

Firmware Upgrade....219

Accessing the Help....222

Supported Web Browsers

The following web browsers can be used to access the Dominion PX web interface:

- Internet Explorer ^® 8 and 9

- Firefox ^® 3.x and 4+

- Safari ^ 5.x (MacOS Lion)

- Google ^ Chrome ^ 12+

Logging in to the Web Interface

To log in to the web interface, you must enter a user name and password. The first time you log in to the Dominion PX, use the default user name (admin) and password (raritan). You are then prompted to change the password for security purposes.

Exception: If you already changed the password for the admin account during the Initial Network Configuration (on page 23), use the new password instead to log in to the web interface, and the Dominion PX will NOT prompt you to change the password.

After successfully logging in, you can create user profiles for your other users. These profiles define their login names and passwords. See Creating a User Profile (on page 102).

Login

The web interface allows a maximum of 16 users to log in simultaneously.

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

To log in to the web interface:

1. Open a browser, such as Microsoft Internet Explorer or Mozilla Firefox, and type this URL:

http(s)://

where is the IP address of the Dominion PX device.

1. If any security alert message appears, click OK or Yes to accept. The Login page then opens.

Login User Name: Password: Login Clear

1. Type your user name in the User Name field, and password in the Password field.

Note: Both the user name and password are case sensitive, so make sure you capitalize them correctly. If you typed them incorrectly, click Clear to clear either the inputs or any error message that appears.

1. Click Login or press Enter. The Dominion PX page opens.

Note: Depending on your hardware configuration, elements shown on the Dominion PX page may appear slightly different from this image.

Raritan. Dominion PX User Management - Device Settings - Maintenance - Domion PX Explorer Dashboard my PX (192 168 04:50) PMI (1) Outlets Overcurrent Protectors External Sensors Feature Port Wepcam Management Snapshots Wepcam Dashboard Inlet RMS Current: 9.2 A / 16.0 A RMS Voltage: 111 V Active Power: 15 W Apparent Power: 26 VA Power Factor: 0.58 Active Energy: 134448 Wh Alerted Sensors Sensor Reading State Overcurrent Protectors (2)

None (Label) Current Drawn Current Remaining Status

1 Overcurrent Protector C1 0.00 A 20.00 A pivot 2 Overcurrent Protector C2 0.00 A 20.00 A pivot External Sensors (4 managed, 6 immunaged) Name Reading State Humidity 1 55 % normal Humidity 2 55 % normal Temperature 1 26.5 °C normal Temperature 2 26.6 °C normal my FX (192 168 04:50) Administrator (scmm) Lad Logic: 3/1/12 4:14 AM 3/1/12 4:18 AM

Changing Your Password

Normal users can change their own passwords if they have the Change Own Password permission. See Setting Up Roles (on page 107).

If you are the administrator (admin), the Dominion PX web interface automatically prompts you to change the password if this is your first time to log in to the Dominion PX. If you have the Administrator Privileges, you can change other users' passwords, as well. See Modifying a User Profile (on page 106).

▶ To change your password:

1. Choose User Management > Change Password. The Change User Password dialog appears.

Change User 'admin' Password Old Password: Password: Enter new password Confirm Password: Repeat new password OK Cancel

1. Type the current password in the Old Password field.

2. Type your new password in the Password and Confirm Password fields. The password can be 4 to 32 characters long. It is case sensitive.

3. Click OK to save the changes.

Tip: If you have the Administrator Privileges, you can change other users' passwords. See Modifying a User Profile (on page 106).

Logout

After finishing your tasks with the Dominion PX, you should log out to prevent others from accessing the web interface.

To log out of the web interface:

1. Do one of these:

- Click "logout" on the top-right corner of the web interface.

© logout

• Close the web browser by clicking the Close button ( ✗) on the top-right corner of the browser.
• Close the web browser by choosing File > Close, or File > Exit. The command varies according to the version of the browser you use.

• Choose the Refresh command or click the Refresh button on the web browser.

• Either the login page opens or the browser is closed, depending on your choice in the previous step.

Introduction to the Web Interface

The web interface provides two panes, a menu bar, a status bar, an Add Page icon, and a logout button throughout every page.

Raritan. Dominion PX User Management - Dendal Settings - Maintenance Dimension PX Explorer Dendal my PX (192.168.84.46) Settings Name: my PX External Hesur Zsopordnike format: Rack units Attitudes: 0 m Firmware Version: 2.3.0.5-36503 MAC Address: 08.0d.56.11.33.22 Rating: 150-120V, 164, 1.0-1.9VVA, 50/60Hz: Default Outlet Sequence Outlet sequence: Default Group Load Shedding Load Shedding: Disabled Non-critical Outlets: None Create Load Shedding Setup Non-Critical Outlets My RS (192.168.84.46) Administrator (admin) Last Page: 1/13/02 7:12 PM 116:00 0:25 PM

Number Web interface element
1	Menus
2	Dominion PX Explorer pane
3	Setup button*
4	Status bar
5	Add Page icon
6	Logout button
7	Data pane

* The Setup button is not available on some pages, such as the Dashboard page.

For detailed information about these web interface elements, see the sections that follow.

Menus

There is a menu bar across the top of the page. You can click any menu to select the desired menu item from the drop-down list.

Four menus are available for managing different tasks or showing information.

• User Management contains menu items for managing user profiles, permissions (roles), and password.
• Device Settings deals with device-related settings, such as the device name, network settings, security settings, and system time.
• Maintenance provides tools that are helpful for maintaining the Dominion PX, such as the event log, hardware information, firmware upgrade and so on.
• Help displays information regarding the firmware and all open source packages embedded on the Dominion PX. In addition, you can access the user guide from this menu.

Dominion PX Explorer Pane

The hierarchical tree to the left displays the Dominion PX device you are accessing as well as all physical components embedded on or connected to this PDU, such as inlets, outlets, and environmental sensors. In addition, an icon named Dashboard is available for displaying the PDU summary information.

The tree structure comprises three hierarchical levels.

First level Second level Third level
Dashboard	None None
PDU folder*	Inlet I1 None
	Outlets 1 to n**
	Overcurrent Protectors folder C1 to Cn^**
	External Sensors folder A list of connected environmental sensors
First level Second level Third level
	Feature Port folder One of the following is displayed, depending on your configuration:NoneAsset StripPower CIMLHX-20LHX-40
	Webcam Management	SnapshotsWebcam

* The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).
** n represents the final number of that component.
Note: A Webcam icon appears only when a Logitech® QuickCam® Pro 9000 Webcam is connected to the Dominion PX. See Connecting a Logitech Webcam (Optional) (on page 48).

To navigate through the tree:

1. To expand any folders, see Expanding the Tree (on page 71).
2. To show any tree item's data, click on that item. See Add Page Icon (on page 75).

Expanding the Tree

The icons representing all components implemented on or connected to the Dominion PX device are expanded by default. If they are hidden, you may expand the tree manually to show all component icons.

To expand the tree:

1. By default, the PDU folder has been expanded.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

If it is not expanded, click the white arrow ▷prior to the folder icon, or double-click the folder. The arrow then turns into a black, gradient arrow ▲ and icons of components or component groups appear below the PDU folder.

1. To expand any component group at the second level, click the white arrow ▷ prior to the folder icon, or double-click the folder.

The arrow then turns into a black, gradient arrow ▲ and icons representing individual components appear below the group folder.

Repeat Step 2 for other component groups you want to expand. The expanded tree looks similar to this image.

Dashboard my PX (192.168.84.48) Inlet I1 Outlets 1 2 3 4 5 Overcurrent Protectors C1 C2 External Sensors Humidity 1 On/Off 1 Temperature 1 Feature Port Asset Strip (1) Webcam Management Snapshots Webcam

Collapsing the Tree

You can collapse the whole tree structure or a specific component group to hide all or partial tree items.

To collapse the whole tree:

- Click the black, gradient arrow ▲prior to the PDU folder icon, or double-click the folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

The arrow then turns into a white arrow , and all items below the PDU folder disappear.

To hide some tree items:

1. Click the black, gradient arrow ▲prior to the component group folder that you want to collapse, or double-click the folder.

The arrow then turns into a white arrow , and all items below the folder disappear.

1. Repeat Step 1 for other component groups you want to collapse.

Adjusting the Pane

You can change the width of the pane to make the area larger or smaller.

To adjust the pane's width:

1. Move the mouse pointer to the right border of the Dominion PX Explorer pane.

2. When the mouse pointer turns into a two-way arrow, drag the border horizontally to widen or shrink the pane.

Setup Button

The Setup button is available for most tree items. It triggers a setup dialog where you can change settings for the selected tree item.

Status Bar

The status bar shows five pieces of information from left to right.

- Device name:

This is the name assigned to the Dominion PX device. The default is "my PX." See Naming the PDU (on page 83).

- IP address:

The numbers enclosed in parentheses is the IP address assigned to the Dominion PX device. See Initial Network Configuration (on page 23) or Modifying the Network Settings (on page 86).

Tip: The presence of the device name and IP address in the status bar indicates the connection to the Dominion PX device. If the connection is lost, it shows "disconnected" instead.

- Login name:

This is the user name you used to log in to the web interface.

Administrator (admin)

- Last login time:

This shows the date and time this login name was used to log in to this Dominion PX device last time.

Last Login: 3/24/11 9:46 PM

When the mouse pointer hovers over the last login time, detailed information about the last login is displayed, including the access client and IP address.

For the login via a serial connection, is displayed instead of an IP address.

There are different types of access clients:

• Web GUI: Refers to the Dominion PX web interface.

• CLI: Refers to the command line interface (CLI). The information in parentheses following "CLI" indicates how this user was connected to the CLI.

• Serial: Represents the local connection (serial or USB).

• SSH: Represents the SSH connection.
• Telnet: Represents the Telnet connection.

- System date and time:

Current date, year, and time are displayed to the right of the bar. If positioning the mouse pointer over the system date and time, the time zone information is also displayed.

3/24/11 10:18 PM

Sometimes a flag icon (💡) may appear to the far right of the bar when a communication error between the Dominion PX device and the graphical user interface (GUI) occurs. When the icon appears, you can click the icon to view the communications log. See Viewing the Communication Log (on page 211).

Add Page Icon

The Add Page icon, located on the top of the data pane, lets you open data pages of multiple tree items without overriding any opened page.

▶ To open new data pages:

1. Click the Add Page icon appears.
   . A new tab along with a blank data page
2. Click a tree item whose data page you want to open. The data of the selected tree item is then displayed on the blank page.
3. To open more data pages, repeat Steps 1 to 2. All tabs representing opened pages are shown across the top of the page.
   The following diagram shows a multi-tab example.

1. With multiple pages opened, you can take these actions:

- To switch to one of the opened data pages, click the corresponding tab.

If there are too many tabs to be all shown, two arrows (← and →) appear at the left and right borders of the pane. Click either arrow to navigate through all tabs.

- To close any data page, click the Close button ( ✗) on the corresponding tab.

Logout Button

Click the logout button when you want to log out of the web interface.

© logout

Data Pane

The right pane shows the data page of the selected tree item. The data page includes the item's current status, settings and a Setup button (if available).

All tabs above the pane represent the opened data pages. The highlighted tab indicates the current selection.

You can change the width of the pane to make the area larger or smaller.

To adjust the pane's width:

1. Move the mouse pointer to the left border of the right pane.

2. When the mouse pointer turns into a two-way arrow, drag the border horizontally to widen or shrink the pane.

More Information

This section explains additional web interface elements or operations that are useful.

Warning Icon

If the value you entered in a specific field is invalid, a red warning icon appears to the right and the field in question is surrounded by a red frame as shown in this illustration.

When this occurs, position your mouse pointer over the warning icon to view the reason and modify the entered value accordingly.

The Yellow- or Red-Highlighted Reading

When a numeric sensor's reading crosses any upper or lower threshold, the background color of the whole row turns to yellow or red for alerting users.

For a discrete (on/off) sensor, the row changes the background color when the sensor enters the abnormal state.

If any circuit breaker trips, the circuit breaker's row is also highlighted in red.

See the table for the meaning of each color:

Color State

White The background is white in one of the following scenarios:

• For a numeric sensor, no thresholds have been enabled.
• If any thresholds have been enabled for a numeric sensor, the sensor reading is between the lower and upper warning thresholds.
• For a discrete (on/off) sensor, the sensor state is normal.
• The sensor reading or state is unavailable.

Yellow The reading drops below the lower warning threshold or rises above the upper warning threshold.

Color State

Red The meaning of the red color varies depending on the sensor type:

• For a numeric sensor, this color indicates the reading drops below the lower critical threshold or rises above the upper critical threshold.
• For a discrete (on/off) sensor, this color indicates the sensor is in the "alarmed" state.
• For a circuit breaker trip sensor, it means the circuit breaker has tripped.

To find the exact meaning of the alert, read the information shown in the State (or Status) column:

• below lower critical: The numeric sensor's reading drops below the lower critical threshold.
• below lower warning: The numeric sensor's reading drops below the lower warning threshold.
• above upper critical: The numeric sensor's reading reaches or exceeds the upper critical threshold.
• above upper warning: The numeric sensor's reading reaches or exceeds the upper warning threshold.
• alarmed: The discrete sensor is NOT in the normal state.
• Open: The circuit breaker has tripped.

For information on the thresholds, see Setting Power Thresholds (on page 150).

Changing the View of a List

Some dialogs and data pages contain a list or table, such as the Manage Users dialog shown below. You may change the number of displayed columns or re-sort the list for better viewing the data. Note the column or sorting changes are not saved when quitting the dialog or data page. Next time when the dialog or page re-opens, the list returns to the default view.

Manage Users Active User Name Full Name Roles ✓ Johnny Johnny TS Operator ✓ admin Administrator Admin Manage Roles New Edit Delete Close

Note: Not all dialogs support the sorting or column change functions.

Changing the Column

You can hide some columns of a list or table, or adjust a specific column's width.

▶ To change displayed columns:

1. Hover your mouse pointer over any column header. A black triangle

appears to the far right of this column header.

1. Click the black triangle, and a drop-down menu appears.

2. Point to Columns. A submenu showing all columns appears.

3. Click any column you want to deselect or select.

4. To hide a column, have its checkbox deselected.

5. To show a column, have its checkbox selected.

To change the column width:

1. Hover the mouse pointer to the right border of the desired column.

2. When the mouse pointer turns to a two-way arrow, drag the border horizontally to widen or shrink the column.

Changing the Sorting

By default, a list or table is sorted against the first column in the ascending order. You can re-sort the list in a reverse order or against a different column.

To re-sort the list by doing either of the following:

- Click the column header against which you want to sort the list.

a. The first click sorts the list in the ascending order, indicated by a blue upward-pointing triangle ▲.
b. The second click reverses the sorting to the descending order, indicated by a blue downward-pointing triangle ▼.

- Select a sorting command from the column menu.

a. Hover your mouse pointer over the column header against which you want to sort the list. A black triangle ▼ appears to the far right of this column header.
b. Click the black triangle, and a drop-down menu appears.
c. Select Sort Ascending or Sort Descending.

The newly selected column header is marked with the upward- or downward-pointing triangle.

Resizing a Dialog

Most dialogs cannot be resized except for a few ones (such as the Event Log dialog), which can be resized to display more information at a time.

To resize a dialog:

1. Hover your mouse pointer over any border of the dialog.
2. When the mouse pointer turns to a double-headed arrow, drag the border vertically or horizontally to make the dialog bigger or smaller.

Browser-Defined Shortcut Menu

A shortcut menu, which is built in the web browser, may appear when right-clicking anywhere in the Dominion PX web interface.

The shortcut menu functions are defined by the browser. For example, the Back command on the Internet Explorer ^® (IE) shortcut menu works the same as the Back button in the IE browser. Both of these functions take you to the previous page.

For information on each shortcut menu command or item, see the online help or documentation accompanying your web browser.

Below is the illustration of the IE browser's shortcut menu. Available menu commands or items may slightly differ based on your web browser version.

Back Forward Save Background As... Set as Background Copy Background Set as Desktop Item... Select All Paste Create Shortcut Add to Favorites... View Source Encoding Print Refresh Append to Existing PDF Convert to Adobe PDF Export to Microsoft Excel Properties

Viewing the Dashboard

When you log in to the web interface, the Dashboard page is displayed by default. This page provides an overview of the Dominion PX device's status.

The page is divided into various sections according to the component type, such as inlet and circuit breakers.

Note: If a sensor reading row is colored, it means the sensor reading already crosses one of the thresholds, or the circuit breaker has tripped. See The Yellow- or Red-Highlighted Reading (on page 76).

After clicking any other icon in the hierarchical tree, the Dashboard page is overridden. To return to the Dashboard page, click the Dashboard icon.

When the Dashboard page is opened, you can do the following to uncover or hide specific data.

▶ To collapse any section:

1. Locate the section you want to collapse.

2. Click the upward arrow prior to the section title. The data specific to the section is hidden.

▶ To expand a collapsed section:

1. Locate the section you want to expand.
2. Click the downward arrow ▼ prior to the section title. The data specific to the section appears.

Alerted Sensors

One of the sections on the Dashboard page only displays critical or significant conditions detected by internal or external sensors so that you are alerted to take actions. This section is labeled as Alerted Sensors.

The Alerted Sensors section lists any or all of the following:

• Any sensor that crosses the upper or lower thresholds if the thresholds are enabled
  • The tripped circuit breakers
• Discrete (on/off) sensors that enter the alarmed state

Sensor	Reading	State
Inlet I1 L1-L2 RMS Voltage	427 V	above upper warning
Temperature 1	20.7 °C	below lower warning
Temperature 2	20.2 °C	below lower warning
On/Off 1		alarmed

For the background color meanings in this section, see The Yellow- or Red-Highlighted Reading (on page 76).

Device Management

Using the web interface, you can retrieve basic hardware and software information, give the Dominion PX a new device name, set the system date and time, and modify network settings that were entered during the initial configuration process.

Displaying the PDU Information

To display information specific to the Dominion PX device that you are using, such as inlet or outlet types, trigger the Device Information dialog.

To display the PDU-specific information:

1. Choose Maintenance > Device Information. The Device Information dialog appears.

Device Information Device Information Network Outlets Controllers Model: PX2-1486C Serial Number: PL51234567 Rating: 100-240V, 16A, 1.6-3.8kVA, 50/60Hz Device MAC Address: 00:0d:5d:07:6a:48 Firmware Version: 2.3.0.5-36900 Board ID: PNW8050423 Board Revision: 0x64 PDU2-MIB:Download ASSETMANAGEMENT-MIB:download USB Console INF file:download Close

1. Click the tab containing the information you want to view. The number of available tabs varies according to the model you purchased.

Tab Data

Device Information General PDU information, such as model name, serial number, firmware version,

Tab Data
	hardware revision, and so on.
Network The PDU specific network information, such as the current networking mode, IPv4 and/or IPv6 addresses and so on.This tab also indicates whether the PDU is part of an USB cascading configuration. See Cascading the PDUs via USB (on page 29).
Outlets Each outlet's receptacle type, operating voltage and rated current.
Inlets Each inlet's plug type, rated voltage and current.
Overcurrent Protectors Each circuit breaker's type, rated current and the outlets that it protects.
Controllers Each inlet or outlet controller's serial number, firmware and hardware version.
Asset Strips Each asset sensor's ID, boot version, application version and protocol version.

Note: An outlet's operating voltage is derived from the inlet's rated voltage. The result of this calculation is rounded off mathematically to the nearest integer in volt. For example, if the calculation for the minimum voltage is 380/sqrt(3)=219.39, the web interface displays 219 V.

1. Enlarge the dialog if necessary.
2. You can re-sort the list or change the columns displayed.
3. Click Close to quit the dialog.

Tip: The firmware version is also available by clicking the PDU folder in the Dominion PX Explorer pane.

Naming the PDU

The default name for Dominion PX is my PX. You may give it a unique device name.

▶ To change the device name:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Setup in the Settings section. The Pdu Setup dialog appears.

2. Type a new name in the Device Name field.

3. Click OK to save the changes.

Modifying the Network Configuration

The network settings you can change via the web interface include wired, wireless, IPv4 and/or IPv6 settings.

Modifying the Network Interface Settings

The Dominion PX supports two types of network interfaces: wired and wireless. You should configure the network interface settings according to the networking mode that applies. See Connecting the Dominion PX to Your Network (on page 21).

Wired Network Settings

The LAN interface speed and duplex mode were set during the installation and configuration process. See Initial Network Configuration (on page 23).

By default, the LAN speed and duplex mode are set to "Auto" (automatic), which works in nearly all scenarios. You can change them if there are special local requirements.

To modify the network interface settings:

1. Choose Device Settings > Network. The Network Configuration dialog appears.
2. The Interface Settings tab should have been selected. If not, click the Interface Settings tab.
3. In the Network Interface field, click the drop-down arrow, and select Wired from the list.

4. To change the LAN speed, click the drop-down arrow in the Speed field and select an option from the list.

5. Auto: System determines the optimum LAN speed through auto-negotiation.

6. 10 Mbit/s: The LAN speed is always 10 Mbps.
   ■ 100 Mbit/s: The LAN speed is always 100 Mbps.

7. To change the duplex mode, click the drop-down arrow in the Duplex field and select an option from the list.

- Auto: The Dominion PX selects the optimum transmission mode through auto-negotiation.

- Full: Data is transmitted in both directions simultaneously.

- Half: Data is transmitted in one direction (to or from the Dominion PX device) at a time.

1. Click OK to save the changes.

Tip: You can check the LAN status in the Current State field, including the speed and duplex mode.

Wireless Network Settings

Wireless SSID, PSK and BSSID parameters were set during the installation and configuration process. See Initial Network Configuration (on page 23). You can change them via the web interface.

To modify the wireless interface settings:

1. Choose Device Settings > Network. The Network Configuration dialog appears.
2. The Interface Settings tab should have been selected. If not, click the Interface Settings tab.
3. In the Network Interface field, click the drop-down arrow, and select Wireless from the list.
4. Check the Hardware State field to ensure that the Dominion PX device has detected a wireless USB LAN adapter. If not, verify whether the USB LAN adapter is firmly connected or whether it is supported. See Connecting the Dominion PX to Your Network (on page 21).
5. Type the name of the wireless access point (AP) in the SSID field.
6. If the BSSID is available, select the Force AP BSSID checkbox, and type the MAC address in the BSSID field.

Note: BSSID refers to the MAC address of an access point in the wireless network.

1. In the Authentication field, click the drop-down arrow, and select an appropriate option from the list.

Option Description
No Authentication	Select this option when no authentication data is required.
PSK A Pre-Shared Key is required for this option.▪ In the Pre-Shared Key field, type the PSK string.

Option Description

EAP - PEAP PEAP stands for Protected Extensible Authentication Protocol.

The following authentication data is required:Inner Authentication: Only Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) is supported, allowing authentication to databases that support MSCHAPv2.Identity: Type your user name for EAP authentication.Password: Type your password for EAP authentication.CA Certificate: A third-party CA certificate must be provided for EAP authentication. Click Browse to select a valid certificate file.- To view the contents of the selected certificate file, click Show.- If the selected certificate file is invalid, click Remove. Then select a new file.

1. Click OK to save the changes.

Modifying the Network Settings

The Dominion PX was configured for network connectivity during the installation and configuration process. See Configuring the Dominion PX (on page 18). If necessary, you can modify any network settings using the web interface.

Selecting the Internet Protocol

The Dominion PX device supports two types of Internet protocols -- IPv4 and IPv6. You can enable either or both Internet protocols. After enabling the desired Internet protocol(s), all but not limited to the following protocols will be compliant with the enabled Internet protocol(s):

• LDAP
  • NTP
• SMTP
• SSH
• Telnet
• FTP
• SSL
  • SNMP
• SysLog

To select the appropriate Internet Protocol:

1. Choose Device Settings > Network. The Network Configuration dialog appears.
2. Click the IP Protocol tab.

3. Select one checkbox according to the Internet protocol(s) you want to enable:

4. IPv4 only: Enables IPv4 only on all interfaces. This is the default.

5. IPv6 only: Enables IPv6 only on all interfaces.

6. IPv4 and IPv6: Enables both IPv4 and IPv6 on all interfaces.

7. If you selected the "IPv4 and IPv6" checkbox in the previous step, you must determine which IP address is used when the DNS resolver returns both of IPv4 and IPv6 addresses.

8. IPv4 Address: Use the IPv4 addresses returned by the DNS server.

9. IPv6 Address: Use the IPv6 addresses returned by the DNS server.

10. Click OK to save the changes.

Modifying the IPv4 Settings

You must enable the IPv4 protocol before you can modify the IPv4 network settings. See Selecting the Internet Protocol (on page 87).

▶ To modify the IPv4 settings:

1. Choose Device Settings > Network. The Network Configuration dialog appears.

2. Click the IPv4 Settings tab.

3. In the IP Auto Configuration field, click the drop-down arrow, and select the desired option from the list.

Option Description

DHCP To auto-configure the Dominion PX, select DHCP.

With DHCP selected, you can enter a preferred DHCP host name, which is optional. Type the host name in the Preferred Hostname field.

The host name:

• 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

Select the "Specify DNS server manually" checkbox if necessary. Then type the address of the primary DNS server in the Primary DNS Server field. The secondary DNS server and DNS suffix are optional.

Static To manually assign an IP address, select Static, and enter the following information in the corresponding fields:

IP address
Netmask
- Gateway
■ Primary DNS server
■ Secondary DNS server (optional)
- DNS Suffix (optional)

1. Click OK to save the changes.

Note: The Dominion PX supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the Dominion PX only uses the primary IPv4 and IPv6 DNS servers.

Modifying the IPv6 Settings

You must enable the IPv6 protocol before you can modify the IPv6 network settings. See Selecting the Internet Protocol (on page 87).

▶ To modify the IPv6 settings:

1. Choose Device Settings > Network. The Network Configuration dialog appears.
2. Click the IPv6 Settings tab.
3. In the IP Auto Configuration field, click the drop-down arrow, and select the desired option from the list.

Option Description

Automatic To auto-configure Dominion PX, select Automatic.

With this option selected, you can enter a preferred host name, which is optional. Type the host name in the Preferred Hostname field.

The host name:

• 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

Select the "Specify DNS server manually" checkbox if necessary. Then type the address of the primary DNS server in the Primary DNS Server field. The secondary DNS server and DNS suffix are optional.

Static To manually assign an IP address, select Static, and enter the following information in the corresponding fields:

IP address
- Gateway
■ Primary DNS server
■ Secondary DNS server (optional)
■ DNS Suffix (optional)

1. Click OK to save the changes.

Note: The Dominion PX supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the Dominion PX only uses the primary IPv4 and IPv6 DNS servers.

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 Dominion PX may fail to connect to the given host.

Therefore, DNS server settings are important for LDAP authentication. With appropriate DNS settings, the Dominion PX can resolve the LDAP server's name to an IP address for establishing a connection. If the SSL encryption is enabled, the DNS server settings become critical since only fully qualified domain name can be used for specifying the LDAP server.

For information on LDAP authentication, see Setting Up LDAP Authentication (on page 128).

Modifying the Network Service Settings

The Dominion PX supports these network communication services: HTTPS, HTTP, Telnet and SSH.

HTTPS and HTTP enable the access to the web interface, and Telnet and SSH enable the access to the command line interface (see "Using the Command Line Interface" on page 230).

By default, SSH is enabled, Telnet is disabled, and all TCP ports for supported services are set to standard ports. You can change default settings if necessary.

Note: Telnet access is disabled by default because it communicates openly and is thus insecure.

In addition, the Dominion PX also supports the SNMP protocol.

Changing the HTTP(S) Settings

HTTPS uses Secure Sockets Layer (SSL) technology to encrypt all traffic to and from the Dominion PX device so it is a more secure protocol than HTTP.

By default, any access to the Dominion PX device via HTTP is automatically redirected to HTTPS. See Forcing HTTPS Encryption (on page 110).

To change the HTTP or HTTPS port settings:

1. Choose Device Settings > Network Services > HTTP. The HTTP Settings dialog appears.

2. To use a different port for HTTP or HTTPS, type a new port number in the corresponding field. Valid range is 1 to 65535.

Warning: Different network services cannot share the same TCP port.

1. Click OK to save the changes.

Changing the SSH Settings

You can enable or disable the SSH access to the command line interface, or change the default TCP port for the SSH service. In addition, you can decide to log in using either the password or the public key over the SSH connection.

To change the SSH service settings:

1. Choose Device Settings > Network Services > SSH. The SSH Settings dialog appears.
2. To use a different port, type a new port number in the field. Valid range is 1 to 65535.
3. To enable the SSH application, select the Enable SSH checkbox. To disable it, deselect the checkbox.
4. To select a different authentication method, select one of the checkboxes.
5. Allow password authentication only: Enables the password-based login only.
6. Allow public key authentication only: Enables the public key-based login only.

7. Allow password and public key authentication: Enables both the password- and public key-based login. This is the default.

8. Click OK to save the changes.

If the public key authentication is selected, you must type a valid SSH public key for each user profile to log in over the SSH connection. See Creating a User Profile (on page 102).

Changing the Telnet Settings

You can enable or disable the Telnet access to the command line interface, or change the default TCP port for the Telnet service.

To change the Telnet service settings:

1. Choose Device Settings > Network Services > Telnet. The Telnet Settings dialog appears.
2. To use a different port, type a new port number in the field. Valid range is 1 to 65535.
3. To enable the Telnet application, select the Enable Telnet Access checkbox. To disable it, deselect the checkbox.
4. Click OK to save the changes.

Configuring the SNMP Settings

You can enable or disable SNMP communication between an SNMP manager and the Dominion PX device. Enabling SNMP communication allows the manager to retrieve and control the power status of each outlet.

Besides, you may need to configure the SNMP destination(s) if the built-in "System SNMP Trap Rule" is enabled and the trap destination has not been set yet. See Configuring Event Rules (on page 155).

To configure the SNMP communication:

1. Choose Device Settings > Network Services > SNMP. The SNMP Settings dialog appears.

SIIMP Settings General Traps SNMP v1 / v2c Settings SNMP v1 / v2c: enable Read Community String: public Write Community String: private SNMP v3 Settings SNMP v3: enable MIB-II System Group sysContact: sysName: sysLocation: Download MB OK Cancel

1. Select the "enable" checkbox in the "SNMP v1 / v2c" field to enable communication with an SNMP manager using SNMP v1 or v2c protocol.

2. Type the SNMP read-only community string in the Read Community String field. Usually the string is "public."

3. Type the read/write community string in the Write Community String field. Usually the string is "private."

4. Select the "enable" checkbox in the "SNMP v3" field to enable communication with an SNMP manager using SNMP v3 protocol.

Tip: You can permit or disallow a user to access the Dominion PX via the SNMP v3 protocol. See Configuring Users for Encrypted SNMP v3 (on page 225).

1. Type the SNMP MIB-II sysContact value in the sysContact field.
2. Type the SNMP MIB-II sysName value in the sysName field.

3. Type the SNMP MIB-II sysLocation value in the sysLocation field.

4. Click OK to save the changes.

Important: You must download the SNMP MIB for your Dominion PX to use with your SNMP manager. Click Download MIB in this dialog to download the desired MIB file. For more details, see Downloading SNMP MIB (on page 227).

To configure SNMP trap destinations:

1. Choose Device Settings > Network Services > SNMP. The SNMP Settings dialog appears.
2. Click the Traps tab.
3. Select the Enabled checkbox in the "System Snmp Trap Event Rule" field.

4. Specify the SNMP trap destinations by doing the following:
   a. You can specify up to 3 SNMP trap destinations in the Host x fields, where x is a number between 1 and 3.
   b. Specify a port number for each destination in the Port x fields, where x is a number between 1 and 3.
   c. Specify a community string for each destination in the Community x fields, where x is a number between 1 and 3.

5. Click OK to save the changes.

Tip: The SNMP trap destination settings can be also set in the Event Rule Settings dialog. See Modifying an Action (on page 180).

Changing the Modbus Settings

You can enable or disable the Modbus access to the Dominion PX or the read-only mode, or change the default TCP port for the Modbus service.

To change the Modbus service settings:

1. Choose Device Settings > Network Services > Modbus. The Modbus Settings dialog appears.
2. To use a different port, type a new port number in the field. Valid range is 1 to 65535.
3. To enable the Modbus access, select the Enable Modbus/TCP Access checkbox. To disable it, deselect the checkbox.
4. To enable the Modbus read-only mode, select the "Enable read-only mode" checkbox. To disable it, deselect the checkbox.
5. Click OK to save the changes.

Enabling Service Advertisement

The Dominion PX advertises all enabled services that are reachable using the IP network. This feature uses 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

This feature is enabled by default.

To enable service advertisement:

1. Choose Device Settings > Network Services to select the Service Advertisement checkbox.
2. Click Yes on the confirmation message to switch to zero configuration advertising. The feature is enabled and the Service Advertisement checkbox is selected in the menu.

▶ To disable service advertisement:

1. Choose Device Settings > Network Services to deselect the Service Advertisement checkbox.
2. Click Yes on the confirmation message to switch off the zero configuration advertising. The feature is disabled and the Service Advertisement checkbox is deselected in the menu.

Setting the Date and Time

Set the internal clock on the Dominion PX device manually, or link to a Network Time Protocol (NTP) server and let it set the date and time for the Dominion PX.

To set the date and time:

1. Choose Device Settings > Date/Time. The Configure Date/Time Settings dialog appears.

2. In the Time Zone field, click the drop-down arrow, and 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.

If the daylight saving time rules are not available for the selected time zone, the checkbox is not configurable.

1. Choose one of the methods to set the date and time:

- To customize the date and time, select the User Specified Time radio button, and then enter the date and time in appropriate fields. Use the yyyy-mm-dd format for the date and the hh:mm:ss format for the time.

- To set the date, delete existing numbers in the Date field and type new ones, or click the calendar icon ☐ to select a date.

- The time is measured in 24-hour format so enter 13 for 1:00pm, 14 for 2:00pm, and so on. You can enter the time by deleting existing numbers and typing new ones in the hour, minute and second fields, or clicking the arrows to adjust each number.

- To let an NTP server set the date and time, select the "Synchronize with NTP Server" radio button. There are two ways to assign the NTP servers.

- To use the DHCP-assigned NTP servers, make sure the "Always use the servers below and ignore DHCP-provided servers" checkbox is deselected. This method is usable only when either IPv4 or IPv6 DHCP is enabled.

- To use the NTP servers that are manually specified, select the "Always use the servers below and ignore DHCP-provided servers" checkbox, and specify the primary NTP server in the First Time Server field. A secondary NTP server is optional.

Note: If the Dominion PX device's IP address is assigned through IPv4 or IPv6 DHCP, the NTP servers can be automatically discovered. When this occurs, the data you entered in the fields of First and Second Time Server will be overridden.

1. Click OK to save the changes.

Important: If you are using Raritan's Power IQ to manage the Dominion PX, you must configure Power IQ and the Dominion PX to have the same date/time or NTP settings.

How to Use the Calendar

The calendar icon next to the Date field is a convenient tool to quickly change the year, month and date.

1999-12-31 July 2010 S M T W T F S 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 Today

▶ To select a date using the calendar:

1. To change the year shown in the calendar, do either of the following:

2. Press Ctrl+Up arrow or Ctrl+Down arrow to switch between years.

3. Click ▼, which is adjacent to the year, to show a list of years and months. Select the desired year from the list to the right and click OK. If the list does not show the desired year, click ▼ or □ to show additional years.

Jan Jul Feb Aug 2005 2010 Mar Sep 2006 2011 Apr Oct 2007 2012 May Nov 2008 2013 Jun Dec 2009 2014 OK Cancel

1. To change the month shown in the calendar, do one of the following:

- Press Ctrl+Right arrow or Ctrl+Left arrow to switch between months.

• Click ▶ or ▶ on the top of the calendar to switch between months.

• Click ▼, which is adjacent to the year, to show a list of years and months. Select the desired month from the list to the left and click OK.

• To select a date, click that date on the calendar.

- Click Today if you want to select today.

Note: On the calendar, the date for today is marked with a red frame.

Configuring the Feature Port

The Dominion PX device supports connecting one of the following devices to its FEATURE port:

• Raritan asset management sensors (asset sensors). See Connecting the Asset Management Sensor (Optional) (on page 38).
• Ra ritan Computer Interface Module (CIM) for PDU use. See Dominion KX II Configuration (on page 406).
• Schroff ^ LHX-20 or LHX-40 heat exchanger. See Connecting a Schroff LHX Heat Exchanger (Optional) (on page 49).

By default, the FEATURE port can automatically detects and displays the device connected to the FEATURE port. The only exception is the Schroff® LHX-20 or LHX-40 device, which requires enabling the LHX support before the Dominion PX can detect or display it. See Managing the Schroff LHX Heat Exchanger (on page 212).

You can change the mode applied to the FEATURE port so that the Dominion PX web interface only displays the device as you wish.

To configure the FEATURE port:

1. Click the Feature Port folder. The Feature Port page opens in the right pane.
2. Select the Port# 1 device on the Feature Port page, and click Setup. The Feature Port Setup dialog appears.
3. Select the desired mode in the Detected Mode field.

■ Auto: The Dominion PX automatically detects and displays the device connected to the FEATURE port. This is the default.
- Disabled: The FEATURE port is disabled so the Dominion PX does not detect and display the connected device.
- Pinned: The Dominion PX always displays the selected device type no matter which device is connected or whether the selected device is detected or not. Available device types are listed below.

Device type Description
Asset Strip Raritan asset sensors.
Power CIM Raritan power CIM, D2CIM-PWR. This CIM is used to connect the Dominion PX to the Raritan digital KVM switch, Dominion KX II.
LHX-20	Schroff® LHX-20 heat exchanger. This device type is available only after the LHX support is enabled.
LHX-40	Schroff® LHX-40 heat exchanger. This device is available only after the LHX support is enabled.

1. Click OK to save the changes.

Configuring the Serial Port

You can change the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the Dominion PX device. The default baud rate is 115200 bps. Baud rate adjustment may be necessary only when you integrate the Dominion PX with another Raritan product via the serial interface. Change the baud rate before connecting it to a Raritan product through the serial port, or there are communication problems.

Note: The serial port setting is especially useful when the Dominion PX works in conjunction with Raritan's Dominion LX KVM switch. The Dominion LX only supports 19200 bps for communications over the serial interface.

To change the serial port baud rate settings:

1. Choose Device Settings > Serial Port Settings. The Serial Port Configuration dialog appears.
2. In the Baud Rate field, click the drop-down arrow, and select the desired baud rate from the list.

Specifying the Device Altitude

You must specify the Dominion PX device's altitude above sea level if a Raritan differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor. See Altitude Correction Factors (on page 414).

The default altitude measurement unit is meter. You can have the measurement unit vary between meter and foot according to user credentials. See Changing the Measurement Units (on page 203).

To specify the altitude of the Dominion PX device:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Setup in the Settings section. The Pdu Setup dialog appears.
2. Type an integer number in the Altitude field. Depending on the measurement unit displayed, the range of valid numbers differs.

- For meters (m), the value ranges between 0 and 3000.

- For feet (ft), the value ranges between 0 and 9842.

1. Click OK to save the changes.

Setting Data Logging

The Dominion PX can store 120 measurements for each sensor in a memory buffer. This memory buffer is known as the data log. Sensor readings in the data log can be retrieved using SNMP.

You can configure how often measurements are written into the data log using the Measurements Per Log Entry field. Since the Dominion PX's internal sensors are measured every second, specifying a value of 60, for example, would cause measurements to be written to the data log once every minute. Since there are 120 measurements of storage per sensor, specifying a value of 60 means the log can store the last two hours of measurements before the oldest one in log gets overwritten.

Whenever measurements 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.

Note that the outlet-level measurement data is NOT available for the Raritan PDU models described in this user guide.

Note: The Dominion PX's SNMP agent must be enabled for this feature to work. See Enabling SNMP (on page 224) for more details. In addition, using an NTP time server ensures accurately time-stamped measurements.

Enabling Data Logging

By default, data logging is disabled. Only users having the "Administrator" or "Change Data Logging Settings" permissions can enable or disable this feature. See Setting Up Roles (on page 107).

To configure the data logging feature:

1. Choose Device Settings > Data Logging. The Data Logging Options dialog appears.

2. To enable the data logging feature, select the "enable" checkbox in the Enable Data Logging field.

3. Type a number in the Measurements Per Log Entry field. Valid range is from 1 to 600. The default is 60.
4. Verify that all sensor logging is enabled. If not, click Enable All in Page to have all sensors selected.
5. Click OK to save the changes.

Important: Although it is possible to selectively enable/disable logging for individual sensors on the Dominion PX in Step 4, it is NOT recommended and this capability may be removed in the future.

Configuring the SMTP Settings

The Dominion PX can be configured to send alerts or event messages to a specific administrator by email. To do this, you have to configure the SMTP settings and enter an IP address for your SMTP server and a sender's email address.

Note: See Configuring Event Rules (on page 155) for information on creating event rules to send email notifications.

To set the SMTP server settings:

1. Choose Device Settings > SMTP Server. The SMTP Server Settings dialog appears.
2. Type the name or IP address of the mail server in the Server Name field.
3. Type the port number for the SMTP server in the Port field. The default is 25.
4. Type an email address for the sender in the Sender Email Address field.
5. Type the number of email retries in the Number of Sending Retries field. The default is 2 retries.
6. Type the time interval between email retries in the "Time Interval Between Sending Retries (in minutes)" field. The time is measured in minutes. The default is 2 minutes.

7. If your SMTP server requires password authentication, do this:
   a. Select the Server Requires Authentication checkbox.
   b. Type a user name in the User Name field.
   c. Type a password in the Password field.

8. Now that you have set the SMTP settings, you can test it to ensure it works properly. Do the following:

a. Type the recipient's email address in the Recipient Email Addresses field. Use a comma to separate multiple email addresses.
b. Click Send Test Email.

1. Click OK to save the changes.
2. Check if the recipient(s) receives the email successfully.

Setting the EnergyWise Configuration

If a Cisco ^® EnergyWise energy management architecture is implemented in your place, you can enable the Cisco EnergyWise endpoint implemented on the Dominion PX device so that this device becomes part of the Cisco EnergyWise domain.

The Cisco EnergyWise feature implemented on the Dominion PX is disabled by default.

To set the Cisco EnergyWise configuration:

1. Choose Device Settings > EnergyWise. The EnergyWise Configuration dialog appears.
2. In the Enable EnergyWise field, select the "enable" checkbox to enable the Cisco EnergyWise feature.
3. In the "Domain name" field, type the name of a Cisco EnergyWise domain where the Dominion PX belongs. The domain name comprises up to 127 printable ASCII characters.
4. Spaces and asterisks are NOT acceptable.
5. In the "Domain password" field, type the authentication password (secret) for entering the Cisco EnergyWise domain. The password comprises up to 127 printable ASCII characters.
6. Spaces and asterisks are NOT acceptable.
7. In the Port field, type a User Datagram Protocol (UDP) port number for communication in the Cisco EnergyWise domain. The port ranges from 1 to 65535. Default is 43440.
8. In the "Polling interval" field, type a polling interval to determine how often the Dominion PX is queried in the Cisco EnergyWise domain. The polling interval ranges from 30 to 600 seconds. Default is 180 seconds.
9. Click OK to save the changes.

Rebooting the Dominion PX Device

You can remotely reboot the Dominion PX device via the web interface.

▶ To reboot the device:

1. Choose Maintenance > Unit Reset. The Reset Device dialog appears.

Reset Device Do you really want to reset the device? Yes No

1. Click Yes to reset the Dominion PX.
2. A message appears with a countdown timer showing the remaining time of the operation. It takes about one minute to complete.
3. When the reset is complete, the Login page opens. Now you can log back in to the Dominion PX device.

Note: If you are not redirected to the Login page after the reset is complete, click the underlined text "this link" in the message.

User Management

The Dominion PX is shipped with one built-in user profile: admin, which is used for initial login and configuration. This profile has full system and outlet permissions, and should be reserved for the system administrator. It cannot be deleted and its permissions are not user-configurable except for the SNMP v3 permission.

All users must have a user profile, which specifies a login name and password, and contains additional (optional) information about the user. Every user profile must have at least a role to determine the user's system and outlet permissions. See Setting Up Roles (on page 107).

Tip: By default, multiple users can log in simultaneously using the same login name.

Creating a User Profile

Creating new users adds a new login to the Dominion PX.

To create a user profile:

1. Choose User Management > Users. The Manage Users dialog appears.

2. Click New. The Create New User dialog appears.

3. Type the information about the user in the corresponding fields. Note that User Name, Password and Confirm Password fields are required.

Field Type this...
User Name The name the user enters to log in to the Dominion PX.▪ The name can be 4 to 32 characters long.▪ It is case sensitive.▪ Spaces are NOT permitted
Full Name The user's first and last names.
Password, Confirm Password	The password the user enters to log in. Type it first in the Password field and then again in the Confirm Password field.▪ The password can be 4 to 32 characters long.▪ It is case sensitive.▪ Spaces are permitted.
Telephone Number A phone number where the user can be reached.
eMail Address An email address where the user can be reached.▪ The email can be up to 32 characters long.▪ It is case sensitive.

1. Select the Enabled checkbox. If not, the user CANNOT log in to the Dominion PX device.
2. Select the "Force password change on next login" checkbox if you prefer a password change by the user when the user logs in for the first time after this checkbox is enabled.
3. Click the SNMPv3 tab to set the SNMPv3 access permission. The permission is disabled by default.

a. To permit the SNMPv3 access by this user, select the "Enable SNMPv3 access" checkbox. Otherwise, leave the checkbox disabled.

Note: The SNMPv3 protocol must be enabled for SNMPv3 access. See Configuring the SNMP Settings (on page 92).
b. Set up SNMPv3 parameters if enabling the SNMPv3 access permission.

Field Description

Security Level Click	the drop-down arrow to select a preferred security level from the list:NoAuthNoPriv: No authentication and no privacy.AuthNoPriv: Authentication and no privacy.AuthPriv: Authentication and privacy. This is the default.
Use Password as Authentication Pass Phrase	This checkbox is configurable only if AuthNoPriv or AuthPriv is selected.When the checkbox is selected, the authentication pass phrase is identical to the user's password. To specify a different authentication pass phrase, disable the checkbox.
Authentication Pass Phrase	Type the authentication pass phrase in this field if the "Use Password as Authentication Pass Phrase" checkbox is disabled.The pass phrase must consist of 8 to 32 ASCII printable characters.
Confirm Authentication Pass Phrase	Re-type the same authentication pass phrase for confirmation.
Use Authentication Pass Phrase as Privacy Pass Phrase	This checkbox is configurable only if AuthPriv is selected.When the checkbox is selected, the privacy pass phrase is identical to the authentication pass phrase. To specify a different privacy pass phrase, disable the checkbox.
Privacy Pass Phrase	Type the privacy pass phrase in this field if the "Use Authentication Pass Phrase as Privacy Pass Phrase" checkbox is disabled.The pass phrase must consist of 8 to 32 ASCII printable characters.
Confirm Privacy Pass Phrase	Re-type the same privacy pass phrase for confirmation.
Authentication Protocol	Click the drop-down arrow and select the desired authentication protocol from the list. Two protocols are available:MD5SHA-1 (default)
Field Description
Privacy Protocol Click the drop-down arrow and select the desired privacy protocol from the list. Two protocols are available:DES (default)AES-128

1. Click the SSH tab to enter the public key if the public key authentication for the SSH service is enabled. See Changing the SSH Settings (on page 91).

a. Open the SSH public key with a text editor.
b. Copy and paste all contents in the text editor into the Public Key field on the SSH tab.

1. Click the Roles tab to determine the permissions of the user.

2. Select one or multiple roles by selecting corresponding checkboxes.

■ The Admin role provides full permissions.
- The Operator role provides limited permissions for frequently-used functions. See Setting Up Roles (on page 107) for the scope of permissions. This role is selected by default.
- If no roles meet your needs, you can:

- Modify the permissions of an existing role: To modify the permissions of any role, double-click the role or highlight it and then click Edit Role. See Modifying a Role (on page 108).

- Create a new role b y clicking the Manage Roles button: See Creating a Role (on page 107).

Note: With multiple roles selected, a user has the union of all roles' permissions.

1. To change any measurement units displayed in the web interface for this new user, click the Preferences tab, and do any of the following:

2. In the Temperature Unit field, select °C (Celsius) or °F (Fahrenheit) as the measurement unit for temperatures.

3. In the Length Unit field, select "Meter" or "Feet" as the measurement unit for length or height.
4. In the Pressure Unit field, select "Pascal" or "psi" as the measurement unit for pressure.

A Pascal is equal to one newton per square meter. Psi stands for pounds per square inch.

Note: The measurement unit change only applies to the web interface and command line interface.

1. Click OK to save the changes.

Modifying a User Profile

You can change any user profile's information except for the user name.

▶ To modify a user profile:

1. Choose User Management > Users. The Manage Users dialog appears.
2. Select the user by clicking it.
3. Click Edit or double-click the user. The Edit User 'XXX' dialog appears, where XXX is the user name.
4. Make all necessary changes to the information shown.

To change the password, type a new password in the Password and Confirm Password fields. If the password field is left blank, the password is not changed.

1. To change the SNMPv3 access permissions, click the SNMPv3 tab and make necessary changes. For details, see Step 6 of Creating a User Profile (on page 102).

2. To change the permissions, click the Roles tab and do one of these:

3. Select or deselect any role's checkbox.

4. To modify the permissions of any role, double-click the role or highlight it and then click Edit Role. See Modifying a Role (on page 108).

5. To change the measurement unit for temperature, length or pressure, click the Preferences tab, and select a different option from the drop-down list.

Note: The measurement unit change only applies to the web interface and command line interface.

1. Click OK to save the changes.

Deleting a User Profile

Delete outdated or redundant user profiles when necessary.

To delete user profiles:

1. Choose User Management > Users. The Manage Users dialog appears.
2. Select the user you want to delete by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.

3. Click Delete.

4. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.

Changing the User List View

You may change the number of displayed columns or re-sort the list for better viewing the data. See Changing the View of a List (on page 78).

Setting Up Roles

A role defines the operations and functions a user is permitted to perform or access. Every user must be assigned at least a role.

The Dominion PX is shipped with two built-in roles: Admin and Operator.

• The Admin role provides full permissions. You can neither modify nor delete this role.
• The Operator role provides limited permissions for frequently-used functions. You can modify or delete this role. By default, the Operator role contains these permissions:
• View Event Settings
• View Local Event Log
• Change Event Settings
• Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration
• Change Own Password
• Switch Outlet (all outlets)

Note: PX-1000 series are not outlet-switching capable so the "Switch Outlet" permission is not available.

The Operator role is assigned to a newly created user profile by default. See Creating a User Profile (on page 102).

Creating a Role

Create a new role when you need a new combination of permissions.

To create a role:

1. Choose User Management > Roles. The Manage Roles dialog appears.

Tip: You can also access the Manage Roles dialog by clicking the Manage Roles button in the Edit User 'XXX' dialog.

1. Click New. The Create New Role dialog appears.
2. Type the role's name in the Role Name field.

3. Type a description for the role in the Description field.

4. Click the Privileges tab to assign one or multiple permissions.

a. Click Add. The "Add Privileges to new Role" dialog appears.
b. Select the permission you want from the Privileges list.
c. If the permission you selected contains any argument setting, the Arguments list is shown to the right. Then select one or multiple arguments.

For example, if the Switch Outlet permission is selected, the Arguments list shows all outlets for you to determine which outlets this role can control. Select the desired outlets' checkboxes or select the checkbox labeled "all" if you want to select all outlets.

d. Click Add to add the selected permission (and arguments if any).

e. Repeat Steps a to d until you add all necessary permissions.

1. Click OK to save the changes.

Now you can assign the new role to any users. See Creating a User Profile (on page 102) or Modifying a User Profile (on page 106).

Modifying a Role

You can change an existing role's settings except for the name.

▶ To modify a role:

1. Choose User Management > Roles. The Manage Roles dialog appears.

Tip: You can also access the Manage Roles dialog by clicking the Manage Roles button in the Edit User 'XXX' dialog.

1. Select the role you want to modify by clicking it.

2. Click Edit or double-click the role. The Edit Role 'XXX' dialog appears, where XXX is the role name.

Tip: You can also access the Edit Role 'XXX' dialog by clicking the Edit Role button in the Edit User 'XXX' dialog.

1. Modify the text shown in the Description field if necessary.

2. To change the permissions, click the Privileges tab.

Note: You cannot change the Admin role's permissions.

1. To delete any permissions, do this:

a. Select the permission you want to remove by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.

b. Click Delete.

1. To add any permissions, do this:

a. Click Add. The Add Privileges to Role 'XXX' dialog appears, where XXX is the role name.
b. Select the permission you want from the Privileges list.
c. If the permission you selected contains any argument setting, the Arguments list is shown to the right. Then select one or multiple arguments.
For example, if the Switch Outlet permission is selected, the Arguments list shows all outlets for you to determine which outlets this role can control. Select the desired outlets' checkboxes or select the checkbox labeled "all" if you want to select all outlets.
d. Click Add to add the selected permission (and arguments if any).
e. Repeat Steps a to d until you add all necessary permissions.

1. To change a specific permission's arguments, do this:

a. Select the permission by clicking it.
b. Click Edit. The "Edit arguments of privilege 'XXX'" dialog appears, where XXX is the privilege name.

Note: If the permission you selected does not contain any arguments, the Edit button is disabled.

c. Select the argument you want. You can make multiple selections.

d. Click OK.

1. Click OK to save the changes.

Deleting a Role

You can delete any role other than the Admin role.

To delete a role:

1. Choose User Management > Roles. The Manage Roles dialog appears.

Tip: You can also access the Manage Roles dialog by clicking the Manage Roles button in the Edit User 'XXX' dialog.

1. Select the role you want to delete by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.

2. Click Delete.

3. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.

Changing the Role List View

You may change the number of displayed columns or re-sort the list for better viewing the data. See Changing the View of a List (on page 78).

Access Security Control

The Dominion PX provides tools to control access. You can require HTTPS encryption, enable the internal firewall and create firewall rules, and create login limitations.

Tip: You can also create and install the certificate or set up external authentication servers to control any access. See Setting Up an SSL Certificate (on page 123) and Setting Up LDAP Authentication (on page 128).

Forcing HTTPS Encryption

HTTPS uses Secure Sockets Layer (SSL) technology to encrypt all traffic to and from the Dominion PX device so it is a more secure protocol than HTTP.

You can force users to access the Dominion PX web interface through the HTTPS protocol only. By default, this protocol is enabled.

To force HTTPS access to the web interface:

1. Choose Device Settings > Security > Force HTTPS for Web Access.
2. A message appears, prompting you to confirm the operation. Click Yes to enforce the HTTPS service.
3. Choose Device Settings > Security to verify the "Force HTTPS for Web Access" checkbox is selected as shown in this diagram.

Force HTTPS for Web Access

If the checkbox is not selected, repeat these steps.

After enabling the HTTPS protocol, all access attempts using HTTP are redirected to HTTPS automatically.

Configuring the Firewall

The Dominion PX has a firewall that you can configure to prevent specific IP addresses and ranges of IP addresses from accessing the Dominion PX device. By default the firewall is disabled.

To configure the firewall:

1. Enable the firewall. See Enabling the Firewall (on page 111).

2. Set the default policy. See Changing the Default Policy (on page 111).

3. Create fire wall rules specifying which addresses to accept and which ones to discard. See Creating Firewall Rules (on page 112).

Changes made to firewall rules take effect immediately. Any unauthorized IP activities cease instantly.

Note: The purpose of disabling the firewall by default is to prevent users from accidentally locking themselves out of the device.

Enabling the Firewall

The firewall rules, if any, take effect only after the firewall is enabled.

To enable the Dominion PX firewall:

1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears.
2. To enable the IPv4 firewall, click the IPv4 tab, and select the Enable IPv4 Access Control checkbox.
3. To enable the IPv6 firewall, click the IPv6 tab, and select the Enable IPv6 Access Control checkbox.
4. Click OK to save the changes.

Changing the Default Policy

After enabling the firewall, the default policy is to accept traffic from all IP addresses. This means only IP addresses discarded by a specific rule will NOT be permitted to access the Dominion PX.

You can change the default policy to Drop or Reject, in which case traffic from all IP addresses is discarded except the IP addresses accepted by a specific rule.

▶ To change the default policy:

1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears.
2. To determine the default policy for IPv4 addresses:

a. Click the IPv4 tab if necessary.

b. Ensure the Enable IPv4 Access Control checkbox is selected.

c. The default policy is shown in the Default Policy field. To change it, select a different policy from the drop-down list.

• Accept: Accepts traffic from all IPv4 addresses.
• Drop: Discards traffic from all IPv4 addresses, without sending any failure notification to the source host.

• Reject: Discards traffic from all IPv4 addresses, and an ICMP message is sent to the source host for failure notification.

• To determine the default policy for IPv6 addresses:

a. Click the IPv6 tab.
b. Ensure the Enable IPv6 Access Control checkbox is selected.
c. The default policy is shown in the Default Policy field. To change it, select a different policy from the drop-down list.
- Accept: Accepts traffic from all IPv6 addresses.
- Drop: Discards traffic from all IPv6 addresses, without sending any failure notification to the source host.
- Reject: Discards traffic from all IPv6 addresses, and an ICMP message is sent to the source host for failure notification.

1. Click OK to save the changes. The new default policy is applied.

Creating Firewall Rules

Firewall rules determine whether to accept or discard traffic intended for the Dominion PX, based on the IP address of the host sending the traffic. When creating firewall rules, keep these principles in mind:

• Rule order is important.

When traffic reaches the Dominion PX device, the rules are executed in numerical order. 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 by the Dominion PX.

- Subnet mask may be required.

When typing the IP address, you may or may not need to specify BOTH the address and a subnet mask. The default subnet mask is /32 (that is, 255.255.255.255). You must specify a subnet mask only when it is not the same as the default. For example, to specify a single address in a Class C network, use this format:

$$ x. x. x. x / 2 4 $$

where /24 = a subnet mask of 255.255.255.0.

To specify an entire subnet or range of addresses, change the subnet mask accordingly.

Note: Valid IP addresses range from 0.0.0.0 through 255.255.255.255.

Make sure the IP addresses entered are within the scope.

To create firewall rules:

1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears.
2. Click the IPv4 tab for creating firewall rules, or click the IPv6 tab for creating IPv6 firewall rules.
3. Ensure the Enable IPv4 Access Control checkbox is selected on the IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.
4. Create specific rules. See the table for different operations.

Action Procedure
Add a rule to the end of the rules list	Click Append. The "Append new Rule" dialog appears.Type an IP address and subnet mask in the IP/Mask field.Select Accept, Drop or Reject from the drop-down list in the Policy field.Accept: Accepts traffic from the specified IP address(es).Drop: Discards traffic from the specified IP address(es), without sending any failure notification to the source host.Reject: Discards traffic from the specified IP address(es), and an ICMP message is sent to the source host for failure notification.Click OK to save the changes.The system automatically numbers the rule.
Insert a rule between two existing rules	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. The "Insert new Rule" dialog appears.Type an IP address and subnet mask in the IP/Mask field.Select Accept, Drop or Reject from the drop-down list in the Policy field.Accept: Accepts traffic from the specified IP address(es).Drop: Discards traffic from the specified IP address(es), without sending any failure notification to the source host.Reject: Discards traffic from the specified IP address(es), and an ICMP message is sent to the source host for failure notification.Click OK to save the changes.The systems inserts the rule and automatically renumbers the following rules.

1. When finished, the rules appear in the Configure IP Access Control Settings dialog.

Configure IP Access Control Settings IPv4 IPv6 Enable IPv4 Access Control: Default Policy: Accept

IP/Mask Policy

1 192.168.80.80/32 ACCEPT 2 192.255.255.255/24 ACCEPT 3 192.155.123.123/32 DROP Append Insert Edit Delete OK Cancel

1. Click OK to save the changes. The rules are applied.

Editing Firewall Rules

When an existing firewall rule requires updates of IP address range and/or policy, modify them accordingly.

▶ To modify a firewall rule:

1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears.
2. To modify the IPv4 firewall rules, click the IPv4 tab. To modify the IPv6 firewall rules, click the IPv6 tab.
3. Ensure the Enable IPv4 Access Control checkbox is selected on the IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.
4. Select the rule to be modified in the rules list.
5. Click Edit or double-click the rule. The Edit Rule dialog appears.
6. Make changes to the information shown.

7. Click OK to save the changes.

8. Click OK to quit the Configure IP Access Control Settings dialog, or the changes are lost.

Sorting Firewall Rules

The rule order determines which one of the rules matching the same IP address is performed.

To sort the firewall rules:

1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears.
2. To sort the IPv4 firewall rules, click the IPv4 tab. To sort the IPv6 firewall rules, click the IPv6 tab.
3. Ensure the Enable IPv4 Access Control checkbox is selected on the IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.
4. Select a specific rule by clicking it.
5. Click ▲ or ▼ to move the selected rule up or down until it reaches the desired location.
6. Click OK to save the changes.

Deleting Firewall Rules

When any firewall rules become obsolete or unnecessary, remove them from the rules list.

▶ To delete a firewall rule:

1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears.
2. To delete the IPv4 firewall rules, click the IPv4 tab. To delete the IPv6 firewall rules, click the IPv6 tab.
3. Ensure the Enable IPv4 Access Control checkbox is selected on the IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.
4. Select the rule that you want to delete. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
5. Click Delete.
6. A message appears, prompting you to confirm the operation. Click Yes to remove the selected rule(s) from the rules list.
7. Click OK to save the changes.

Setting Up User Login Controls

You can set up login controls to make it more difficult for hackers to access the Dominion PX and the devices connected to it. You can arrange to lock persons out after a specified number of failed logins, limit the number of persons who log in using the same user name at the same time, and force users to create strong passwords.

Enabling User Blocking

User blocking determines how many times a user can attempt to log in to the Dominion PX and fail authentication before the user's login is blocked.

Note that this function applies only to local authentication instead of authentication through external AA servers.

Note: If any user blocking event occurs, you can unblock that user manually by using the "unblock" CLI command via a serial connection. See Unblocking a User (on page 379).

To enable user blocking:

1. Choose Device Settings > Security > Login Settings. The Login Settings dialog appears.
2. Locate the User Blocking section.
3. To enable the user blocking feature, select the "Block user on login failure" checkbox.
4. Type a number in the "Maximum number of failed logins" field. This is the maximum number of failed logins the user is permitted before the user's login is blocked from accessing the Dominion PX device.
5. To determine how long the login is blocked, select the desired length of time from the drop-down list in the "Block timeout" field. The following describes available options.
6. Infinite: This option sets no time limit on blocking the login.
7. X min: This type of option sets the time limit to X minutes, where X is a number.
8. X h: This type of option sets the time limit to X hours, where X is a number.
   ■ 1 d: This option sets the time limit to 1 day.

Tip: If the desired time option is not listed, you can manually type the desired time in this field. For example, you can type "4 min" to set the time to 4 minutes.

1. Click OK to save the changes.

Enabling Login Limitations

Login limitations determine whether more than one person can use the same login name at the same time, and how long users are permitted to stay idle before being forced to log out.

To enable login limitations:

1. Choose Device Settings > Security > Login Settings. The Login Settings dialog appears.
2. Locate the Login Limitations section.
3. To prevent more than one person from using the same login at the same time, select the "Prevent concurrent login with same username" checkbox.

4. To adjust how long users can remain idle before they are forcibly logged out by the Dominion PX, select a time option in the Idle Timeout Period field. The default is 10 minutes.

5. X min: This type of option sets the time limit to X minutes, where X is a number.

6. X h: This type of option sets the time limit to X hours, where X is a number.
   ■ 1 d: This option sets the time limit to 1 day.

Tip: If the desired time option is not listed, you can manually type the desired time in this field. For example, you can type "4 min" to set the time to 4 minutes.

1. Click OK to save the changes.

Tip: 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 Dominion PX.

Enabling Strong Passwords

Use of strong passwords makes it more difficult for intruders to crack user passwords and access the Dominion PX device. By default, strong passwords should be at least eight characters long and contain upper- and lower-case letters, numbers, and special characters, such as @ or &.

To force users to create strong passwords:

1. Choose Device Settings > Security > Password Policy. The Password Policy dialog appears.
2. Select the Strong Passwords checkbox 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 restricted passwords in history = 5 

Note: The maximum password length accepted by the Dominion PX is 32 characters. 

1. Make necessary changes to the default settings.
2. Click OK to save the changes.

Enabling Password Aging

Password Aging determines whether users are required to change passwords at regular intervals. The default interval is 60 days.

To force users to change passwords regularly:

1. Choose Device Settings > Security > Password Policy. The Password Policy dialog appears.
2. Select the Password Aging checkbox to enable the password aging feature.
3. To determine how often users are requested to change their passwords, select a number of days in the Password Aging Interval field. Users are required to change their password every time that number of days has passed.

Tip: If the desired time option is not listed, you can manually type the desired time in this field. For example, you can type "9 d" to set the password aging time to 9 days.

1. Click OK to save the changes.

Setting Up Role-Based Access Control Rules

Role-based access control rules are similar to firewall rules, except they are applied to members sharing a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses.

To set up role-based access control rules:

1. Enable the feature. See Enabling the Feature (on page 119).

2. Set the default policy. See Changing the Default Policy (on page 119).

3. Create rules specifying which addresses to accept and which ones to discard when the addresses are associated with a specific role. See Creating Role-Based Access Control Rules (on page 120).

Changes made do not affect users currently logged in until the next login.

Enabling the Feature

You must enable this access control feature before any relevant rule can take effect.

To enable role-based access control rules:

1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
2. To enable the IPv4 firewall, click the IPv4 tab, and select the Enable Role Based Access Control for IPv4 checkbox.
3. To enable the IPv6 firewall, click the IPv6 tab, and select the Enable Role Based Access Control for IPv6 checkbox.
4. Click OK to save the changes.

Changing the Default Policy

The default policy is to accept all traffic from all IP addresses regardless of the role applied to the user.

To change the default policy:

1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
2. To determine the default policy for IPv4 addresses:

a. Click the IPv4 tab if necessary.
b. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected.
c. Select the action you want from the Default Policy drop-down list.

• Allow: Accepts traffic from all IPv4 addresses regardless of the user's role.

• Deny: Drops traffic from all IPv4 addresses regardless of the user's role.

• To determine the default policy for IPv6 addresses:

a. Click the IPv6 tab.
b. Ensure the Enable Role Based Access Control for IPv6 checkbox is selected.

c. Select the action you want from the Default Policy drop-down list.

• Allow: Accepts traffic from all IPv6 addresses regardless of the user's role.

• Deny: Drops traffic from all IPv6 addresses regardless of the user's role.

• Click OK to save the changes.

Creating Role-Based Access Control Rules

Role-based access control rules accept or drop traffic, based on the user's role and IP address. Like firewall rules, the order of rules is important, since the rules are executed in numerical order.

To create role-based access control rules:

1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
2. Click the IPv4 tab for creating firewall rules, or click the IPv6 tab for creating IPv6 firewall rules.
3. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected on the IPv4 tab, or the Enable Role Based Access Control for IPv6 checkbox is selected on the IPv6 tab.
4. Create specific rules:

Action Do this...

Add a rule to the end of the rules list

- Click Append. The "Append new Rule" dialog appears.

- Type a starting IP address in the Starting IP Address field.

- Type an ending IP address in the Ending IP Address field.

- Select a role from the drop-down list in the Role field. This rule applies to members of this role only.

- Select Allow or Deny from the drop-down list in the Policy field.

- Allow: Accepts traffic from the specified IP address range when the user is a member of the specified role

- Deny: Drops traffic from the specified IP address range when the user is a member of the specified role

- Click OK to save the changes.

The system automatically numbers the rule.

Action Do this...

Insert a rule between two existing rules

• 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. The "Insert new Rule" dialog appears.
• Type a starting IP address in the Starting IP Address field.
• Type an ending IP address in the Ending IP Address field.
• Select a role from the drop-down list in the Role field. This rule applies to members of this role only.
• Select Allow or Deny from the drop-down list in the Policy field.

- Allow: Accepts traffic from the specified IP address range when the user is a member of the specified role

- Deny: Drops traffic from the specified IP address range when the user is a member of the specified role

- Click OK to save the changes.

The system inserts the rule and automatically renumbers the following rules.

1. Click OK to save the changes.

Editing Role-Based Access Control Rules

You can modify existing rules when these rules do not meet your needs.

To modify a role-based access control rule:

1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
2. To modify the IPv4 firewall rules, click the IPv4 tab. To modify the IPv6 firewall rules, click the IPv6 tab.
3. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected on the IPv4 tab, or the Enable Role Based Access Control for IPv6 checkbox is selected on the IPv6 tab.
4. Select the rule to be modified in the rules list.
5. Click Edit or double-click the rule. The Edit Rule dialog appears.
6. Make changes to the information shown.
7. Click OK to save the changes.

Sorting Role-Based Access Control Rules

Similar to firewall rules, the order of role-based access control rules determines which one of the rules matching the same IP address is performed.

To sort role-based access control rules:

1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
2. To sort the IPv4 firewall rules, click the IPv4 tab. To sort the IPv6 firewall rules, click the IPv6 tab.
3. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected on the IPv4 tab, or the Enable Role Based Access Control for IPv6 checkbox is selected on the IPv6 tab.
4. Select a specific rule by clicking it.
5. Click ▶ or ▽ to move the selected rule up or down until it reaches the desired location.
6. Click OK to save the changes.

Deleting Role-Based Access Control Rules

When any access control rule becomes unnecessary or obsolete, remove it.

To delete a role-based access control rule:

1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
2. To delete the IPv4 firewall rules, click the IPv4 tab. To delete the IPv6 firewall rules, click the IPv6 tab.
3. Ensure the Enable Role Based Access Control for IPv4 checkbox is selected on the IPv4 tab, or the Enable Role Based Access Control for IPv6 checkbox is selected on the IPv6 tab.
4. Select the rule to be deleted in the rules list. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
5. Click Delete.
6. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.
7. Click OK to save the changes.

Setting Up an SSL Certificate

Having an X.509 digital certificate ensures that both parties in an SSL connection are who they say they are.

To obtain a certificate for the Dominion PX, create a Certificate Signing Request (CSR) and submit it to a certificate authority (CA). After the CA processes the information in the CSR, it provides you with an SSL certificate, which you must install on the Dominion PX device.

Note: See Forcing HTTPS Encryption (on page 110) for instructions on forcing users to employ SSL when connecting to the Dominion PX.

A CSR is not required in either of the following scenarios:

• You decide to generate a self-signed certificate on the Dominion PX device.
• Appropriate, valid certificate and key files have been available.

Certificate Signing Request

When appropriate certificate and key files for the Dominion PX are NOT available, one of the alternatives is to create a CSR and private key on the Dominion PX device, and send the CSR to a CA for signing the certificate.

Creating a Certificate Signing Request

Follow this procedure to create the CSR for your Dominion PX device.

To create a CSR:

1. Choose Device Settings > Security > SSL Certificate. The Manage SSL Certificate dialog appears.
2. Click the New SSL Certificate tab.
3. Provide the information requested.

- In the Subject section:

Field Type this information

Country (ISO Code)	The country where your company is located. Use the standard ISO country code. For a list of ISO codes, visit theISO website(http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm).
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.
Field Type this information
Common Name The fully qualified domain name (FQDN) of your Dominion PX device.
Email Address An email address where you or another administrative user can be reached.
	Note: All fields in the Subject section are mandatory, except for the Organization, Organizational Unit and Email Address fields. If you generate a CSR without values entered in the required fields, you cannot obtain third party certificates.

■ In the Key Creation Parameters section:

Field Do this
Key Length Select the key length (bits) from the drop-down list in this field. A larger key length enhances the security, but slows down the Dominion PX device's response.
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, and the value should be 4 to 64 characters long.The password is case sensitive, so ensure you capitalize the letters correctly.
Confirm Challenge Type the same password again for confirmation.

1. Click Create New SSL Key to create both the CSR and private key. This may take several minutes to complete.
2. To download the newly-created CSR to your computer, click Download Certificate Signing Request.

a. You are prompted to open or save the file. Click Save to save it on your computer.
b. After the file is stored on your computer, submit it to a CA to obtain the digital certificate.
c. If desired, click Delete Certificate Signing Request to remove the CSR file permanently from the Dominion PX device.

1. To store the newly-created private key on your computer, click Download Key. You are prompted to open or save the file. Click Save to save it on your computer.

2. Click Close to quit the dialog.

Installing a CA-Signed Certificate

After the CA provides a signed certificate according to the CSR you submitted, you must install it on the Dominion PX device.

To install the certificate:

1. Choose Device Settings > Security > SSL Certificate. The Manage SSL Certificate dialog appears.
2. Click the New SSL Certificate tab.
3. In the Certificate File field, click Browse to select the certificate file provided by the CA.
4. Click Upload. The certificate is installed on the Dominion PX device.

Tip: To verify whether the certificate has been installed successfully, click the Active SSL Certificate tab later.

1. Click Close to quit the dialog.

Creating a Self-Signed Certificate

When appropriate certificate and key files for the Dominion PX device are unavailable, the alternative other than submitting 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 > SSL Certificate. The Manage SSL Certificate dialog appears.
2. Click the New SSL Certificate tab.
3. Provide the information requested.

Field Type this information
Country (ISO Code)	The country where your company is located. Use the standard ISO country code. For a list of ISO codes, visit theISO website(http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm).
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 Dominion PX device.
Email Address	An email address where you or another administrative user can be reached.
Key Length Select the key length (bits) from the drop-down list in this field. A larger key length enhances the security, but slows down the Dominion PX device's response.
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 is valid in this field.

Note: All fields in the Subject section are mandatory, except for the Organization, Organizational Unit and Email Address fields.

A password is not required for a self-signed certificate so the Challenge and Confirm Challenge fields disappear after the Self Sign checkbox is selected.

1. Click Create New SSL Key to create both the self-signed certificate and private key. This may take several minutes to complete.
2. You can also do any of the following:

- Click "Install Key and Certificate" to immediately install the self-signed certificate and private key. When any confirmation and security messages appear, click Yes to continue.

Tip: To verify whether the certificate has been installed successfully, click the Active SSL Certificate tab later.

• To download the self-signed certificate or private key, click Download Certificate or Download Key. You are prompted to open or save the file. Click Save to save it on your computer.

• To remove the self-signed certificate and private key permanently from the Dominion PX device, click "Delete Key and Certificate".

• If you installed the self-signed certificate in Step 5, after the installation completes, the Dominion PX device resets and the login page re-opens.

Installing Existing Key and Certificate Files

If the SSL certificate and private key files are already available, you can install them directly without going through the process of creating a CSR or a self-signed certificate.

To install the existing key and certificate files:

1. Choose Device Settings > Security > SSL Certificate. The Manage SSL Certificate dialog appears.

2. Click the New SSL Certificate tab.

3. Select the "Upload Key and Certificate" checkbox. The Key File and Certificate File fields appear.

4. In the Key File field, click Browse to select the private key file.
5. In the Certificate File field, click Browse to select the certificate file.
6. Click Upload. The selected files are installed on the Dominion PX device.

Tip: To verify whether the certificate has been installed successfully, click the Active SSL Certificate tab later.

1. Click Close to quit the dialog.

Downloading Key and Certificate Files

You can download the key and certificate files currently installed on the Dominion PX device for backup or other operations. For example, you can install the files on a replacement Dominion PX device, add the certificate to your browser and so on.

To download the certificate and key files from an Dominion PX device:

1. Choose Device Settings > Security > SSL Certificate. The Manage SSL Certificate dialog appears.
2. The Active SSL Certificate tab should open. If not, click it.
3. Click Download Key to download the private key file installed on the Dominion PX device. You are prompted to open or save the file. Click Save to save it on your computer.
4. Click Download Certificate to download the certificate file installed on the Dominion PX device. You are prompted to open or save the file. Click Save to save it on your computer.
5. Click Close to quit the dialog.

Setting Up LDAP Authentication

For security purposes, users attempting to log in to the Dominion PX must be authenticated. The Dominion PX supports the access using one of the following authentication mechanisms:

• Local database of user profiles on the Dominion PX device
  • Lightweight Directory Access Protocol (LDAP)

By default, the Dominion PX is configured for local authentication. If you stay with this method, you do not need to do anything other than create user profiles for each authorized user. If you prefer to use an external LDAP server, you must:

• Provide the Dominion PX with information about the LDAP server.
• Create user profiles for users who are authenticated externally because a user profile on the Dominion PX device determines the role(s) applied to the user, and determines the permissions for the user accordingly.

When configured for LDAP authentication, all Dominion PX users must have an account on the LDAP server. Local-authentication-only users will have no access to the Dominion PX except for the admin, who always can access the Dominion PX.

Gathering the LDAP Information

It requires knowledge of your LDAP server and directory settings to configure the Dominion PX for LDAP authentication. If you are not familiar with the settings, consult your LDAP administrator for help.

To configure LDAP authentication, you need to check:

• The IP address or hostname of the LDAP server
• Whether the Secure LDAP protocol (LDAP over SSL) is being used

- If Secure LDAP is in use, consult your LDAP administrator for the CA certificate file.

• The network port used by the LDAP server
• The type of the LDAP server, usually one of the following options:

- OpenLDAP

- If using an OpenLDAP server, consult the LDAP administrator for the Bind Distinguished Name (DN) and password.

■ Microsoft Active Directory ^® (AD)

- If using a Microsoft Active Directory server, consult your AD administrator for the name of the Active Directory Domain.

• Bind Distinguished Name (DN) and password (if anonymous bind is NOT used)
• The Base DN of the server (used for searching for users)
• The login name attribute (or AuthorizationString)
• The user entry object class
• The user search subfilter (or BaseSearch)

Adding the LDAP Server Settings

To activate and use external LDAP/LDAPS server authentication, enable LDAP authentication and enter the information you have gathered for any LDAP/LDAPS server.

Note: An LDAPS server refers to an SSL-secured LDAP server.

To add the LDAP/LDAPS server settings:

1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.
2. Select the LDAP radio button to activate remote LDAP/LDAPS server authentication.
3. Click New to add an LDAP/LDAPS server for authentication. The "Create new LDAP Server Configuration" dialog appears.
4. IP Address / Hostname - Type the IP address or hostname of your LDAP/LDAPS authentication server.

Important: Without the SSL 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 the SSL encryption is enabled.

1. Type of external LDAP/LDAPS server. Choose from among the options available:

OpenLDAP
- Microsoft Active Directory. Active Directory is an implementation of LDAP/LDAPS directory services by Microsoft for use in Windows environments.

1. LDAP over SSL - Select this checkbox if you would like to use SSL. Secure Sockets Layer (SSL) is a cryptographic protocol that allows the Dominion PX to communicate securely with the LDAP/LDAPS server.

2. Port - The default Port is 389. Either use the standard LDAP TCP port or specify another port.

3. SSL Port - The default is 636. Either use the default port or specify another port. This field is enabled when the "LDAP over SSL" checkbox is selected.

4. Use only trusted LDAP Server Certificates - Select this checkbox if you would like to use a trusted LDAP server certificate file, that is, a certificate file signed by the CA. When NOT selected, you can use all LDAP/LDAPS server certificates, including a self-signed certificate file. A certificate file is required after enabling this option.
5. Server Certificate - Consult your authentication server administrator to get the CA certificate file for the LDAP/LDAPS server. Use the Browse button to navigate to the certificate file. This file is required when the "Use only trusted LDAP Server Certificates" checkbox is selected.

Tip: You can first upload the CA certificate file for a future use before selecting the "Use only trusted LDAP Server Certificates" checkbox, and then select the checkbox when you need to utilize the certificate file.

1. Anonymous Bind - For "OpenLDAP," use this checkbox to enable or disable anonymous bind.

2. To use anonymous bind, select this checkbox.

3. When a Bind DN and password are required to bind to the external LDAP/LDAPS server, deselect this checkbox.

4. Use Bind Credentials - For "Microsoft Active Directory," use this checkbox to enable or disable anonymous bind.

5. To use anonymous bind, deselect this checkbox. By default it is deselected.

6. When a Bind DN and password are required to bind to the external LDAP/LDAPS server, select this checkbox.

7. Bind DN - Specify the DN of the user who is permitted to search the LDAP directory in the defined search base. This information is required only when the Use Bind Credentials checkbox is selected.

8. Bind Password and Confirm Bind Password - Enter the Bind password in the Bind Password field first and then the Confirm Bind Password field. This information is required only when the Use Bind Credentials checkbox is selected.

9. Base DN for Search - Enter the name you want to bind against the LDAP/LDAPS (up to 31 characters), and where in the database to begin searching for the specified Base DN. An example Base Search value might be: cn=Users, dc=raritan, dc=com. Consult your authentication server administrator for the appropriate values to enter into these fields.

10. Type the following information in the corresponding fields. LDAP needs this information to verify user names and passwords.

- Login name attribute (also called AuthorizationString)

• User entry object class
• User search subfilter (also called BaseSearch)

Note: The Dominion PX will preoccupy the login name attribute and user entry object class with default values, which should not be changed unless required.

1. Active Directory Domain - Type the name of the Active Directory Domain. For example, testradius.com. Consult with your Active Directory Administrator for a specific domain name.
2. To verify if the LDAP/LDAPS configuration is done correctly, you may click Test Connection to check whether the Dominion PX can connect to the LDAP/LDAPS server successfully.

Tip: You can also do this by using the Test Connection button in the Authentication Settings dialog.

1. Click OK to save the changes. The new LDAP server is listed in the Authentication Settings dialog.

2. To add additional LDAP/LDAPS servers, repeat Steps 3 to 19.

3. Click OK to save the changes. The LDAP authentication is now in place.

Note: If the Dominion PX clock and the LDAP server clock are out of sync, the certificates are considered expired and users are unable to authenticate using LDAP. To ensure proper synchronization, administrators should configure the Dominion PX and the LDAP server to use the same NTP server.

More Information about AD Configuration

For more information about the LDAP configuration using Microsoft Active Directory, see LDAP Configuration Illustration (on page 396).

Sorting the LDAP Access Order

The order of the LDAP list determines the access priority of remote LDAP/LDAPS servers. The Dominion PX first tries to access the top LDAP/LDAPS server in the list for authentication, then the next one if the access to the first one fails, and so on until the Dominion PX device successfully connects to one of the listed LDAP/LDAPS servers.

Note: After successfully connecting to one LDAP/LDAPS server, the Dominion PX STOPS trying to access the remaining LDAP/LDAPS servers in the list regardless of the user authentication result.

To re-sort the LDAP server access list:

1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.

2. Select the LDAP/LDAPS server whose priority you want to change.

3. Click "Move up" or "Move down" until the selected server reaches the desired position in the list.
4. Click OK to save the changes.

Testing the LDAP Server Connection

You can test the connection to any LDAP/LDAPS server to verify the server accessibility or the validity of the authentication settings.

To test the connection to an LDAP/LDAPS server:

1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.
2. Select the LDAP/LDAPS server that you want to test.
3. Click Test Connection to start the connection test.

Editing the LDAP Server Settings

If the configuration on any LDAP/LDAPS server has been changed, such as the port number, bind DN and password, you must modify the LDAP/LDAPS settings on the Dominion PX device accordingly, or the authentication fails.

To modify the LDAP authentication configuration:

1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.
2. Select the LDAP/LDAPS server that you want to edit.
3. Click Edit. The Edit LDAP Server Configuration dialog appears.
4. Make necessary changes to the information shown.
5. Click OK to save the changes.

Deleting the LDAP Server Settings

You can delete the authentication settings of a specific LDAP/LDAPS server when the server is not available or used for remote authentication.

To remove one or multiple LDAP/LDAPS servers:

1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.
2. Select the LDAP/LDAPS server that you want to remove. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.

3. Click Delete.

4. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.

5. Click OK to save the changes.

Disabling the LDAP Authentication

When the remote authentication service is disabled, the Dominion PX authenticates users against the local database stored on the Dominion PX device.

To disable the LDAP authentication service:

1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.
2. Select the Local Authentication radio button.
3. Click OK to save the changes.

Enabling LDAP and Local Authentication Services

To make authentication function properly all the time -- even when external authentication is not available, you can enable both the local and remote authentication services.

When both authentication services are enabled, the Dominion PX follows these rules for authentication:

• When any of the LDAP/LDAPS servers in the access list is accessible, the Dominion PX authenticates against the connected LDAP/LDAPS server only.
• When the connection to every LDAP/LDAPS server fails, the Dominion PX allows authentication against the local database.

To enable both authentication services:

1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.
2. Ensure the LDAP radio button has been selected.
3. Select the "Use Local Authentication if Remote Authentication service is not available" checkbox.
4. Click OK to save the changes.

Outlet Management

The Dominion PX allows you to remotely customize the name of each outlet or remotely check which circuit breaker is associated with each outlet through the web interface.

With PX-2000 series, you can even remotely turn on/off each outlet.

Naming Outlets

You can give each outlet a unique name up to 32 characters long to identify the equipment connected to it. The customized name is followed by the label in parentheses.

Note: In this context, the label refers to the outlet number, such as 1, 2, 3 and so on.

To name an outlet:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).
2. Click Outlets in the Dominion PX Explorer pane, and the Outlets page opens in the right pane.
3. Click the outlet you want in the right pane.

Tip: For PX-2000 series, you can click the desired outlet in the Dominion PX Explorer pane.

1. Click Setup in the Settings section. The setup dialog for the selected outlet appears.
2. Type a name in the Outlet Name field.
3. Click OK to save the changes.

Checking Associated Circuit Breakers

To find out each outlet is protected by which circuit breaker on the PDU, you can check the Outlets page.

Tip: The same information is also available by choosing Maintenance > Device Information. See Displaying the PDU Information (on page 82).

To check associated circuit breaker for all outlets:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).
2. Click Outlets in the Dominion PX Explorer pane, and the Outlets page opens in the right pane.

All outlets are listed with associated circuit breakers shown in the Overcurrent Protector column.

Outlets

Name (Label) Overcurrent Protector

1 Outlet 1 Overcurrent Protector C1 2 Outlet 2 Overcurrent Protector C1 3 Outlet 3 Overcurrent Protector C1 4 Outlet 4 Overcurrent Protector C1 5 Outlet 5 Overcurrent Protector C2 6 Outlet 6 Overcurrent Protector C2 7 Outlet 7 Overcurrent Protector C2 8 Outlet 8 Overcurrent Protector C2

Outlet Switching

This section only applies to outlet-switching capable PDUs.

You can change the power status of one or multiple outlets with one click in the web interface. To change the power state, the PDU must be implemented with the outlet switching function, and you must have the Switch Outlet permission.

Note: If your Dominion PX device does not support outlet switching, no outlets can be switched on/off regardless of the permissions you have.

Switching Multiple or All Outlets

This section only applies to outlet-switching capable PDUs.

The power state can be changed regardless of each outlet's current state. That is, you can turn the outlets on or off or power cycle them even if they are already in the selected state.

Power cycling the outlet(s) turns the outlet(s) off and then back on.

To turn on or off multiple or all outlets, or cycle their power:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click the Outlets folder, and the Outlets page opens in the right pane.

2. Select the outlets whose power states you want to change, and ensure their checkboxes are all selected.

- To select all outlets, select the top checkbox in the header row.

• To select multiple outlets, select the checkbox of each desired outlet one by one.

• To select a single outlet, select that outlet's checkbox.

• Click On, Off, or Cycle.

• A dialog for confirming the operation appears. Click Yes and all outlets switch ON, OFF, or cycle their power.

Outlet State Change Do you really want to switch on all outlets? Yes No

Switching an Outlet

This section only applies to outlet-switching capable PDUs.

You can turn on or off or power cycle any outlet regardless of the outlet's current state.

Power cycling the outlet(s) turns the outlet(s) off and then back on.

There are different ways to turn an outlet on or off, or cycle its power.

To control an outlet with a particular outlet icon selected:

1. If the Outlets folder is not expanded, expand it to show all outlets. See Expanding the Tree (on page 71).
2. Click the outlet you want in the PX Explorer pane, and locate the Control section in the right pane.
3. Click On, Off, or Cycle.
4. A dialog for confirming the operation appears. Click Yes and the outlet switches ON, OFF, or cycles its power.

Outlet State Change Do you really want to switch off Outlet 1? Yes No

To control an outlet with the Outlets folder icon selected:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click the Outlets folder, and the Outlets page opens in the right pane.
2. Click the outlet you want in the right pane, and the corresponding checkbox is selected.
3. Click On, Off, or Cycle.
4. A dialog for confirming the operation appears. Click Yes and the outlet switches ON, OFF, or cycles its power.

Setting the Default Outlet State

This section only applies to outlet-switching capable PDUs.

Default outlet state determines the initial power state of outlets after the Dominion PX device powers up. You can set up the default outlet state for all outlets or for a specific outlet. Note that the value set for an individual outlet always overrides the value set for all outlets.

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

Setting the PDU-Defined Default State

This section only applies to outlet-switching capable PDUs.

This procedure sets the PDU-defined outlet state, which determines the initial power state of all outlets after powering up the Dominion PX device.

Tip: To set a different state on a particular outlet, see Setting the Outlet-Specific Default State (on page 138).

To set the default state for all outlets:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Setup in the Settings section. The Pdu Setup dialog appears.
2. In the "Outlet state on device startup" field, click the drop-down arrow and select an option from the list.

- on: Turns on all outlets when the Dominion PX device powers up.

- off: Turns off all outlets when the Dominion PX device powers up.

- last known: Restores all outlets to their previous power states before the Dominion PX device was powered off.

1. Click OK to save the changes.

Setting the Outlet-Specific Default State

This section only applies to outlet-switching capable PDUs.

By default, the power state of each outlet follows the PDU-defined setting. Setting the default state of a particular outlet to a value other than "PDU defined" overrides the PDU-defined setting on that outlet.

To set the default power state for a specific outlet:

1. If the Outlets folder is not expanded, expand it to show all outlets. See Expanding the Tree (on page 71).
2. Click the outlet you want in the Dominion PX Explorer pane. The page specific to that outlet opens in the right pane.
3. Click Setup in the Settings section. The setup dialog for the selected outlet appears.

Tip: When the Outlets folder is selected, you can also trigger the same dialog by highlighting the outlet on the Outlets page and then clicking Setup.

1. In the "State on device startup" field, click the drop-down arrow and select an option from the list.

2. on: Turns on this outlet when the Dominion PX device powers up.

3. off: Turns off this outlet when the Dominion PX device powers up.
4. last known: Restores this outlet to the previous power state before the Dominion PX device was powered off.
5. PDU defined: The outlet's default power state is determined by the PDU-defined state. See Setting the PDU-Defined Default State (on page 137)

Tip: The information in parentheses following the option "PDU defined" indicates the current PDU-defined selection.

1. Click OK to save the changes.

Changing the Cycling Power-Off Period

This section only applies to outlet-switching capable PDUs.

Power cycling the outlet(s) turns the outlet(s) off and then back on. You can adjust the length of the time it takes for the outlets to turn back on after they are switched OFF during the power cycle.

The power-off period of power cycle can be set for all outlets or for an individual outlet. Note that the value set for an individual outlet always overrides the value set for all outlets.

Changing the PDU-Defined Cycling Power-Off Period

This section only applies to outlet-switching capable PDUs.

The "PDU-defined" power-off period determines how long it takes for all outlets to turn on after they are turned OFF during the power cycle. The default PDU-defined power-off period is 10 seconds (10 s).

Note: To set a different power-off period on a particular outlet, see Changing the Outlet-Specific Cycling Power-Off Period (on page 140).

To set the power-off period for all outlets:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Setup in the Settings section. The Pdu Setup dialog appears.
2. In the "Power off period during power cycle" field, click the drop-down arrow and select an option from the list. Valid range is zero second to one hour.

Time units in the list are explained below:

■ s: second(s)
- min: minute(s)
■ h: hour(s)

You can also type a value if the desired time is not listed. For example, type "15 s" if you want a 15-second delay.

1. Click OK to save the changes.

Tip: When there are a large number of outlets, set the value to a lower number so that you can avoid a long wait before all the outlets are available again.

Changing the Outlet-Specific Cycling Power-Off Period

This section only applies to outlet-switching capable PDUs.

When the power cycling occurs, the default power-off period of each outlet follows the PDU-defined setting. You can adjust the power-off period of a particular outlet so that it is turned back on after a different power-off period.

Setting the power-off period for a particular outlet to a value other than "PDU defined" overrides the PDU-defined setting on that outlet.

To set the power-off period for a specific outlet:

1. If the Outlets folder is not expanded, expand it to show all outlets. See Expanding the Tree (on page 71).
2. Click the outlet you want in the Dominion PX Explorer pane. The page specific to that outlet opens in the right pane.
3. Click Setup in the Settings section. The setup dialog for the selected outlet appears.

Tip: When the Outlets folder is selected, you can also trigger the same dialog by highlighting the outlet on the Outlets page and then clicking Setup.

1. In the "Power off period during power cycle" field, click the drop-down arrow and select an option from the list. Valid range is zero second to one hour.

Time units in the list are explained below:

■ s: second(s)
- min: minute(s)
■ h: hour(s)
- To make the outlet's power-off period identical to the PDU-defined setting, select the "PDU defined" option. See Changing the PDU-Defined Cycling Power-Off Period (on page 139).

Tip: The information in parentheses following the option "PDU defined" indicates the current PDU-defined selection.

You can also type a value if the desired time is not listed. For example, type "15 s" if you want a 15-second delay.

1. Click OK to save the changes.

Setting the Initialization Delay

This section only applies to outlet-switching capable PDUs.

The outlet initialization delay determines how long the Dominion PX device waits before providing power to all outlets during power cycling or after recovering from a temporary power loss. This is useful in cases where power may not initially be stable after being restored, or when UPS batteries may be charging.

To set the initialization delay for all outlets:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Setup in the Settings section. The Pdu Setup dialog appears.
2. In the "Outlet initialization delay on device startup" field, click the drop-down arrow and select an option from the list. Valid range is 1 second to 1 hour.

Time units in the list are explained below:

■ s: second(s)
- min: minute(s)
■ h: hour(s)

1. Click OK to save the changes.

Tip: When there are a large number of outlets, set the value to a lower number so that you can avoid a long wait before all the outlets are available again.

Setting the Inrush Guard Delay

This section only applies to outlet-switching capable PDUs.

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. The inrush guard delay feature prevents a circuit breaker trip due to the combined inrush current of 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 on at the same time, the PDU will sequentially turn the outlets on with a 100 millisecond delay occurring between each one.

To set the inrush guard delay time:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Setup in the Settings section. The Pdu Setup dialog appears.

2. In the Inrush Guard Delay field, click the drop-down arrow and select an option from the list. Valid range is from 100 milliseconds to 100 seconds.

Time units in the list are explained below:

■ ms: millisecond(s)

■ s: second(s)

1. Click OK to save the changes.

Setting the Outlet Power-On Sequence

This section only applies to outlet-switching capable PDUs.

By default, the outlets are sequentially powered on in ascending order from outlet 1 to the highest-numbered outlet when turning ON or power cycling all outlets on the Dominion PX device. You can change the order in which the outlets power ON. This is useful when there is a specific order in which the connected IT equipment should be powered up.

To set the outlet power-on sequence:

1. Trigger the Outlet Sequence Setup dialog by doing either of the following:

- Click the Outlets folder, and the Outlets page opens in the right pane. Click Sequence Setup.

- Click the PDU folder, and then the Setup button in the Outlet Sequence section.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

The Outlet Sequence Setup dialog appears, with the current power-up sequence indicated by the outlet order in the list.

1. To change the priority of an outlet, select it from the list and click one of the following buttons.

■ Moves the outlet to the top of the list, making it the first outlet to receive power.
■ Moves the outlet up one position in the list.
■ : Moves the outlet down one position in the list.
■ Moves the outlet to the bottom of the list, making it the final outlet to receive power.
■: Restores the list to the default power-up sequence, that is, the ascending order.

1. You can re-sort the list or change the columns displayed. Note that re-sorting the list makes changes to the outlet power-up sequence.
2. Click OK to save the changes.

Next time when power cycling the PDU, it will turn on all outlets based on the new order of the list.

Setting the Outlet-Specific Power-On Delay

This section only applies to outlet-switching capable PDUs.

You can make a power-on delay occur between two outlets that are turned on consecutively when the PDU turns on all outlets.

For example, if the power-up sequence is Outlet 1 through Outlet 12, and you want the PDU to wait for 5 seconds after turning on Outlet 3 before turning on Outlet 4, assign a delay of 5 seconds on Outlet 3.

To set the outlet-specific power-on delay:

1. Trigger the Outlet Sequence Setup dialog by doing either of the following:

- Click the Outlets folder, and the Outlets page opens in the right pane. Click Sequence Setup.

- Click the PDU folder, and then the Setup button in the Outlet Sequence section.

1. Click the Delay column of the outlet where a delay is intended after this outlet is turned on, delete the existing value and type a new number in seconds. The number can be a decimal number.
2. To disable the delay, simply type the number 0 (zero).
3. Repeat the above step to change the delay settings of additional outlets.
4. Click OK to save the changes.

Setting Non-Critical Outlets and Load Shedding Mode

This section only applies to outlet-switching capable PDUs.

When a UPS supplying power to the PDU switches into battery backup operation, it may be desirable to switch off non-critical outlets to conserve UPS battery life. This feature is known as load shedding.

Activation of load shedding can be accomplished using the web interface, SNMP or CLI, or triggered by the contact closure sensors.

Outlets that are turned off when load shedding is activated are called non-critical. Outlets that are not affected by load shedding are called critical outlets. When load shedding is deactivated, the PDU will turn back on all non-critical outlets. By default, all outlets are configured as critical until you configure them otherwise.

Marking All Outlets

This section only applies to outlet-switching capable PDUs.

You can configure all critical and non-critical outlets at a time.

To mark all outlets at a time:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Setup Non-Critical Outlets in the Load Shedding section. The "Non-critical Outlet Setup" dialog appears.

Tip: This dialog can be also triggered by clicking the "Non-critical Outlet Setup" button on the Outlets page when selecting the Outlets folder.

1. To mark an outlet as "non-critical," select it from the list in the "Critical outlets" pane, and click 🔍 to move it into the "Non-critical outlets" pane. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
2. To mark an outlet as "critical," select it from the list in the "Non-critical outlets" pane, and click to move it into the "Critical outlets" pane. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
3. Click OK to save the changes.

Marking an Outlet

This section only applies to outlet-switching capable PDUs.

You can also choose to mark a specific outlet as a critical or non-critical outlet in its setup dialog.

To mark an outlet:

1. If the Outlets folder is not expanded, expand it to show all outlets. See Expanding the Tree (on page 71).
2. Click the outlet you want in the Dominion PX Explorer pane. The page specific to that outlet opens in the right pane.
3. Click Setup in the Settings section. The setup dialog for the selected outlet appears.

Tip: When the Outlets folder is selected, you can also trigger the same dialog by highlighting the outlet on the Outlets page and then clicking Setup.

1. In the Non Critical field, select an option from the drop-down list.

2. True: This option marks the outlet as a non-critical outlet.

3. False: This option marks the outlet as a critical outlet.

4. Click OK to save the changes.

Activating or Deactivating the Load Shedding Mode

This section only applies to outlet-switching capable PDUs.

When entering the load shedding mode, Dominion PX turns OFF all non-critical outlets.

When exiting from the load shedding mode, Dominion PX turns ON all non-critical outlets that were ON before entering the load shedding mode.

You can activate or deactivate this mode from the PDU or Outlets page.

To enter or exit from the load shedding mode from the PDU page:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. In the Load Shedding section, click Enable Load Shedding to enter the load shedding mode or Disable Load Shedding to deactivate the mode.
2. You are then prompted to confirm this operation.
3. If you chose to activate the mode in the previous step, click Yes to turn off all non-critical outlets. If you chose to deactivate the mode, click Yes to turn on all non-critical outlets that were previously ON prior to the load shedding mode.

To enter or exit from the load shedding mode from the Outlets page:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).
2. Click the Outlets folder, and the Outlets page opens in the right pane.
3. To enter the load shedding mode, select the Load Shedding checkbox. To exit from the load shedding mode, deselect the Load Shedding checkbox.
4. You are then prompted to confirm this operation.
5. If you chose to activate the mode in the previous step, click Yes to turn off all non-critical outlets. If you chose to deactivate the mode, click Yes to turn on all non-critical outlets that were previously ON prior to the load shedding mode.

Note: During the load shedding mode, this icon appears on all non-critical outlets on the Outlets page, and you CANNOT turn on any of them.

Inlet and Circuit Breaker Management

You can name each inlet and circuit breaker or monitor their status.

Naming the Inlet

You can customize the inlet's name for your own purpose. The customized name is followed by the label in parentheses.

Note: In this context, the label refers to the inlet number, such as 11.

To name the inlet:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Inlet I1 in the Dominion PX Explorer pane, and the Inlet I1 page opens in the right pane.
2. Click Setup. The Inlet I1 Setup dialog appears.
3. Type a new name in the Name field.
4. Click OK to save the changes.

Naming Circuit Breakers

You can name each circuit breaker for easily identifying them.

The customized name is followed by the label in parentheses.

Note: In this context, the label refers to the circuit breaker number, such as C1.

To name a circuit breaker:

1. Expand the Overcurrent Protectors folder to show all circuit breakers in the Dominion PX Explorer pane. See Expanding the Tree (on page 71).
2. Click the desired circuit breaker in the Dominion PX Explorer pane, and the page for this circuit breaker opens in the right pane.
3. Click Setup. The Overcurrent Protector Setup dialog appears.

Tip: This dialog can be also triggered by clicking Setup on the Overcurrent Protectors page when the Overcurrent Protectors folder is selected in the Dominion PX Explorer pane.

1. Type a new name in the Name field.
2. Click OK to save the changes.

Monitoring the Inlet

You can view the inlet's details, including its:

• Label (number)
• Customized name

• Inlet sensor readings:

• RMS current per line (A)

• RMS voltage per line pair (V)
• Active power (W)
• Apparent power (VA)
• Power factor
• Active energy (Wh)
• Unbalanced load percentage

Note: If a sensor reading row is colored, it means the sensor reading already crosses one of the thresholds. See The Yellow- or Red-Highlighted Reading (on page 76).

There are two ways to access the inlet information.

To get the overview of the inlet status:

1. Click the Dashboard icon in the Dominion PX Explorer pane, and the Dashboard page opens in the right pane.
2. Locate the Inlet section on the Dashboard page.

To view the inlet's details:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Inlet I1 in the Dominion PX Explorer pane, and the Inlet I1 page opens in the right pane.

Monitoring Circuit Breakers

Each circuit breaker on the Dominion PX device delivers power to a bank of outlets, and draws power from one or two lines.

You can view the circuit breaker's details, including its:

• Label (number)
  Name
  ■ Status (closed/open)
  ■ Lines associated with the circuit breaker
  ■ Sensor readings:
• Current drawn (A)
• Current remaining (A)

Note: If a sensor reading row is colored, it means the sensor reading already crosses one of the thresholds, or the circuit breaker has tripped. See The Yellow- or Red-Highlighted Reading (on page 76).

You can view the summary of all circuit breakers at a time or the status of individual circuit breakers.

To view all circuit breakers' status:

You can check the status of all circuit breakers at a time via either the Dashboard or Overcurrent Protectors page.

• Using the Dashboard page:
  a. Click the Dashboard icon in the Dominion PX Explorer pane, and the Dashboard page opens in the right pane.
  b. Locate the Overcurrent Protectors section on the Dashboard page.
  ■ Using the Overcurrent Protectors page:
  a. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).
  b. Click Overcurrent Protectors in the Dominion PX Explorer pane, and the Overcurrent Protectors page opens in the right pane.

To view a circuit breaker's details:

1. Expand the Overcurrent Protectors folder to show all circuit breakers in the Dominion PX Explorer pane. See Expanding the Tree (on page 71).
2. Click the desired circuit breaker in the Dominion PX Explorer pane, and the page for this circuit breaker opens in the right pane.

Setting Power Thresholds

Setting and enabling the thresholds causes the Dominion PX to generate alert notifications when it detects that any component's power state crosses the thresholds.

There are four thresholds for each sensor: Lower Critical, Lower Warning, Upper Warning and Upper Critical.

• Upper and Lower Warning thresholds indicate the sensor reading enters the warning range before the critical threshold.
• Upper and Lower Critical thresholds indicate the sensor reading is at the critical level.

To avoid generating a large amount of alert events, the deassertion hysteresis for each threshold is enabled. You can change the default hysteresis value if necessary. For more information on the deassertion hysteresis, see What is Deassertion Hysteresis? (on page 153).

Note: After setting the thresholds, remember to configure the event rules. See Configuring Event Rules (on page 155).

Setting Inlet Thresholds

You can set the inlet thresholds so that the alerts are generated when the inlet current and/or voltage crosses the thresholds.

▶ To set the inlet thresholds:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Inlet I1 in the Dominion PX Explorer pane, and the Inlet I1 page opens in the right pane.
2. Click Setup. The Inlet I1 Setup dialog appears.
3. In the Threshold Configuration table, click the sensor whose thresholds you want to configure.
4. Click Edit. A threshold setup dialog for the selected sensor appears.

Tip: You can also double-click the desired sensor in the Threshold Configuration table to trigger this dialog.

1. Configure the Lower Critical, Lower Warning, Upper Warning and Upper Critical thresholds respectively.

2. To enable any threshold, select the corresponding checkbox. To disable a threshold, deselect the checkbox.
   ■ After any threshold is enabled, type an appropriate numeric value in the accompanying text box.

3. To enable the deassertion hysteresis for all thresholds, type a numeric value other than zero in the Deassertion Hysteresis field. See What is Deassertion Hysteresis? (on page 153).

4. To enable the assertion timeout for all thresholds, type a numeric value other than zero in the Assertion Timeout (samples) field. See What is Assertion Timeout? (on page 154).
5. Click OK in the threshold setup dialog to retain the changes.
6. To set the thresholds for other sensors, repeat Steps 4 to 9.
7. Click OK to save the changes.

Important: The final step is required or the threshold changes are not saved.

Setting a Circuit Breaker's Thresholds

Setting the circuit breaker thresholds enables the PDU to generate alerts when any circuit breaker crosses the thresholds.

To set the thresholds for a circuit breaker:

1. Expand the Overcurrent Protectors folder to show all circuit breakers in the Dominion PX Explorer pane. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click the desired circuit breaker in the Dominion PX Explorer pane, and the page for this circuit breaker opens in the right pane.
2. Click Setup. The Overcurrent Protector Setup dialog appears.
3. In the Threshold Configuration table, click the sensor whose thresholds you want to configure.
4. Click Edit. A threshold setup dialog for the selected sensor appears.

Tip: You can also double-click the desired sensor in the Threshold Configuration table to trigger this dialog.

1. Configure the Lower Critical, Lower Warning, Upper Warning and Upper Critical thresholds respectively.

- To enable any threshold, select the corresponding checkbox. To disable a threshold, deselect the checkbox.

■ After any threshold is enabled, type an appropriate numeric value in the accompanying text box.

1. To enable the deassertion hysteresis for all thresholds, type a numeric value other than zero in the Deassertion Hysteresis field. See What is Deassertion Hysteresis? (on page 153).
2. To enable the assertion timeout for all thresholds, type a numeric value other than zero in the Assertion Timeout (samples) field. See What is Assertion Timeout? (on page 154).
3. Click OK to save the changes.

Bulk Configuration for Circuit Breaker Thresholds

The Dominion PX allows you to set the power thresholds for multiple circuit breakers at a time so that you can save time when configuring a number of circuit breaker thresholds.

Note: To set the power thresholds for an individual circuit breaker, you can either follow the instructions below or those described in the section Setting a Circuit Breaker's Thresholds (on page 151).

To configure thresholds, deassertion hysteresis and assertion timeout for multiple circuit breakers:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click the Overcurrent Protectors folder. The Overcurrent Protectors page opens.
2. Click Bulk Setup. The Overcurrent Protector Threshold Bulk Setup dialog appears, with a list of all circuit breakers.

3. Select desired circuit breakers by having their corresponding checkboxes selected.

4. To select all circuit breakers, select the checkbox labeled Sensor in the header row, and all checkboxes are selected.

5. To select partial circuit breakers, select the corresponding checkboxes of those circuit breakers by clicking on their checkboxes.

6. To deselect any circuit breaker, just click on the checkbox once again.

7. Click Edit Thresholds. The threshold bulk setup dialog appears.

8. Configure the Lower Critical, Lower Warning, Upper Warning and Upper Critical thresholds respectively.

9. To enable any threshold, select the corresponding checkbox. To disable a threshold, deselect the checkbox.
   ■ After any threshold is enabled, type an appropriate numeric value in the accompanying text box.

10. To enable the deassertion hysteresis for all thresholds, type a numeric value other than zero in the Deassertion Hysteresis field. See What is Deassertion Hysteresis? (on page 153).

11. To enable the assertion timeout for all thresholds, type a numeric value other than zero in the Assertion Timeout (samples) field. See What is Assertion Timeout? (on page 154).

12. Click OK to save the changes.

What is Deassertion Hysteresis?

The hysteresis setting determines when a threshold condition is reset. This diagram illustrates how hysteresis values relate to thresholds:

Hysteresis Upper Critical Threshold Upper Critical Reset Hysteresis Upper Warning Threshold Upper Warning Reset Hysteresis Lower Warning Reset Lower Warning Threshold Hysteresis Lower Critical Reset Lower Critical Threshold

The hysteresis values define a reset threshold. For upper thresholds, the measurement must fall past this reset threshold before a deassertion event is generated. For lower thresholds, the measurement must rise above this reset threshold before a deassertion event is generated.

Example: When Hysteresis is Useful

This example demonstrates when a deassertion hysteresis is useful.

The current critical threshold for the inlet is set to 19 amps (A). The current draw rises to 20A, triggering a Current Critical alert. The current then continues to fluctuate between 18.1A and 20A.

With the hysteresis set to 1A, Dominion PX continues to indicate that the current on the inlet is above critical. Without hysteresis (that is, the hysteresis is set to zero), Dominion PX would de-assert the condition each time the current dropped to 18.9A, and re-assert the condition each time the current reached 19A or higher. With the fluctuating current, this could result in a number of repeating SNMP traps, and/or an e-mail account full of repeating SMTP alert notifications.

Example: When to Disable Hysteresis

This is an example of when you want to disable hysteresis for the inlet. Hysteresis is disabled when its value is set to zero.

The upper warning threshold for current in the inlet is set to 15A. In normal usage, the inlet draws 14.6A of current. A spike in demand causes the current to reach 16A, triggering an alert. The current then settles to the normal draw of 14.6A.

With the hysteresis disabled, Dominion PX de-asserts the condition once the current drops to 14.9A. Otherwise the inlet would still be considered above the warning threshold as long as the current never dropped to 14.0A. The condition would not de-assert, even if the current returned to normal.

What is Assertion Timeout?

When the assertion timeout is enabled, the Dominion PX device asserts any warning or critical condition only after a specified number of consecutive samples that cross a particular threshold are generated. This prevents a number of threshold alerts from being generated if the measurements return to normal immediately after rising above any upper threshold or dropping below any lower threshold.

Configuring Event Rules

A benefit of the product's intelligence is its ability to notify you of and react to a change in conditions. This event notification or reaction is an "event rule."

The Dominion PX is shipped with two built-in event rules, which cannot be deleted.

• System Event Log Rule: This rule causes ANY event occurred to the Dominion PX to be recorded in the internal log. The rule is enabled by default.
• System SNMP Trap Rule: This rule causes SNMP traps to be sent to specified IP addresses or hosts when ANY event occurs to the Dominion PX. The rule is disabled by default.

If these two do not satisfy your needs, you can create additional rules to respond to different events.

Note: Internet Explorer ^® 8 (IE8) does not use compiled JAVA script. When using IE8 to create or change event rules, the CPU performance may be degraded, resulting in the appearance of the connection time out message. When this occurs, click Ignore to continue.

Components of an Event Rule

An event rule defines what the Dominion PX does in certain situations and is composed of two parts:

• Event: This is the situation where the Dominion PX or part of it meets a certain condition. For example, the inlet's voltage exceeds the warning threshold.
• Action: This is the response to the event. For example, the Dominion PX notifies the system administrator of the event and records the event in the log.

Creating an Event Rule

The best way to create a new set of event rule, in sequence, is:

• Create actions for responding to one or multiple events.
• Create rules to determine what actions are taken when these events occur.

Creating Actions

The Dominion PX comes with two built-in actions:

• System Event Log Action: This action records the selected event in the internal log when the event occurs.
• System SNMP Trap Action: This action sends SNMP traps to one or multiple IP addresses after the selected event occurs.

Note: No IP addresses are specified for the "System SNMP Trap Action" by default so you must specify IP addresses before applying this action to any event rule.

The built-in actions cannot be deleted. If these actions do not satisfy your needs, then create new ones.

To create new actions:

1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. Click the Actions tab.
3. Click New Action.
4. In the "Action name" field, type a new name for the action. The default name is New Action , where is a sequential number.
5. In the Action field, click the drop-down arrow, and select the desired action from the list.

Option Description
Execute an action group	This option allows you to group "multiple" existing actions so that a combination of selected actions is performed when an event occurs.
Log event message	This option records the selected events in the internal log.
Send Snapshots via SMTP	This option notifies one or multiple persons of the selected events by emailing the snapshots captured by a connected Logitech® QuickCam® Pro 9000 Webcam (if any).In the "Recipients email addresses" field, specify the email address(es) of the recipient(s). Use a comma to separate multiple email addresses.To use the SMTP server specified in the SMTP Server Settings dialog, select the Use Default SMTP Server checkbox. To use a different SMTP server, select the Use Custom SMTP Settings checkbox. If the SMTP server settings are not configured yet, click Configure. SeeConfiguring the SMTP Settings(on page 100) for the information of each field.In the Web cam field, select the webcam whose snapshots you want to send.In the Number of Snapshots field, determine the total number of images to be captured when the event occurs.In the Snapshots/Mail field, determine the maximum number of images to be emailed at one time.In the "Time before first Snapshot (s):" field, determine the amount of time after the event occurs and before the first snapshot is captured.In the "Time between Snapshots (s):" field, determine the amount of time between each snapshot capturing action.
Send SMTP message	This option notifies one or multiple persons of the selected events by emailing a message.In the "Recipients email addresses" field, specify the email address(es) of the recipient(s). Use a comma to separate multiple email addresses.To use the SMTP server specified in the SMTP Server Settings dialog, select the Use Default SMTP Server checkbox. To use a different SMTP server, select the Use Custom SMTP Settings checkbox. If the SMTP server settings are not configured yet, click Configure. SeeConfiguring the SMTP Settings(on page 100) for the information of each field.
Send SNMP trap This	option sends SNMP traps to one or multiple SNMP managers.You can specify up to 3 SNMP trap destinations in the Host x fields, where x is a number between 1 and 3.Specify a port number for each destination in the Port x fields, where x is a number between 1 and 3.Specify a community string for each destination in the Community x fields, where x is a number between 1 and 3.
Syslog message This	option makes the Dominion PX automatically forward event messages to the specified syslog server.In the "Syslog server" field, specify the IP address to which syslog is forwarded.In the Port field, specify an appropriate port number.
Send SMS message	This option sends an English text message to the specified mobile phone.To perform this function, a Cinterion® GSM MC52i or MC55i modem must be connected to the Dominion PX.Type the phone number in the Recipient Phone Number field.Note: The Dominion PX cannot receive any SMS messages.
Record Snapshots to Webcam Storage	This option starts or stops a specific webcam from taking snapshots when the event occurs.In the Webcam field, select the webcam that is intended to take snapshots when the event occurs.In the Action field, select "Start recording" to have the selected webcam start taking snapshots, or "Stop recording" to stop the selected webcam from taking snapshots.If the "Start recording" options is selected, you must fill in the following three fields.In the Number of Snapshots field, determine the total number of images to be captured when the event occurs.In the "Time before first Snapshot (s):" field, determine the amount of time after the event occurs and before the first snapshot is captured.In the "Time between Snapshots (s):" field, determine the amount of time between each snapshot capturing action.
Change load shedding state	This option activates or deactivates the load shedding mode when the event occurs.In the Operation field, select either "Enable load shedding" to activate the load shedding mode or "Disable load shedding" to deactivate the load shedding mode.

Option Description

Switch outlet This option turns on, off or power cycles a specific outlet.

• In the Operation field, select an operation for the selected outlet(s).
  Turn Outlet On: Turns on the selected outlet.
  Turn Outlet Off: Turns off the selected outlet.
  Cycle Outlet: Cycles power to the selected outlet.
• To select the outlet where the specified action is applied, select it in the Available Outlets list and click 📋. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
• To remove an outlet from the Switched Outlets list, select it in the Switched Outlets list and click 📋. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.

Note: The ""Change load shedding state" and Switch outlet" options are only available for outlet-switching capable PDUs.

1. Click Save to save the new action.

Note: If you do not click Save before quitting the current settings page, a message appears. Then click Yes to save the changes, Discard to abort the changes or Cancel to return to the current settings page.

1. To create additional actions, repeat Steps 3 to 7.
2. Click Close to quit the dialog.

Creating an Action Group

You can create an action group that performs up to 32 actions. After creating such an action group, you can easily assign a set of specific actions to an event rule rather than selecting all needed actions one by one for each rule.

▶ To create an action group:

1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.

2. Click the Actions tab.

3. Click New Action.

4. In the "Action name" field, type a new name for the action. The default name is New Action , where is a sequential number.
5. In the Action field, click the drop-down arrow, and select the desired action from the list. To create the action group, select "Execute an action group."
6. To mark an action as part of the action group, select it from the list in the "Available Actions" pane, and click 🔍 to move it to the "Used Actions" pane. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones. A maximum of 32 actions can be grouped.
7. To remove an action from the action group, select it from the list in the "Used Actions" pane, and click ✦ to move it to the "Available Actions" pane. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
8. Click Save to save the new action.

Note: If you do not click Save before quitting the current settings page, a message appears. Then click Yes to save the changes, Discard to abort the changes or Cancel to return to the current settings page.

1. To create additional action groups, repeat Steps 3 to 8.

Creating Custom Email Messages

If you have configured emails to be sent when an event occurs, you can customize the message that is included in the email.

Messages consist of a combination of free text and Dominion PX placeholders. The placeholders represent information is pulled from the Dominion PX and inserted into the message.

For example:

[USERNAME] logged into the device on [TIMESTAMP]

translates to

JQPublic logged into the device on 2012-January-30 21:00

See Email Message Placeholders (on page 162) for a list and definition of available variables.

▶ To create a custom message:

1. Choose Device Settings > Event Rules.
2. Click the Actions tab.

3. From the left pane, select the previously-created "Send SMTP message" action, or create a new action. See Creating Actions (on page 156).

4. Select "Send SMTP message" from the Actions drop-down in the Action Settings section of the dialog.

5. Select the Use Custom Log Message checkbox.
6. Build the message in the open text field that is provided by entering custom information. If needed, use placeholders as part of the message.

Note: Click the Information icon ⓘ to open the Event Context Information dialog, which contains a list of placeholders and their definitions. Then select the desired placeholder, and either double-click it or click the "Paste into message" button to insert it into the customized message.

7. Click Save.

Email Message Placeholders

Following are placeholders that can be used in custom event email messages.

Note: Click the Information icon ⓘ to open the Event Context Information dialog, which contains a list of placeholders and their definitions.

Placeholder Definition

[TIMESTAMP] The timestamp of the event occurrence
[TARGETUSER] The user, an action was triggered for
[USERIP] The IP address, a user connected from
[ASSERTION] Boolean	flag whether an event condition was entered (1) or left (0)
[EXTSENSORNAME]	The name of an external sensor
[EXTSENSORSLOT]	The ID of an external sensor slot
[IFNAME] The human readable name of a network interface
[INLET] The power inlet label
[INLETPOLE] The inlet power line identifier
[INLETSENSOR] The inlet sensor name
[LEDCOLOR] The RGB LED color
[LEDMODE] The LED indication mode
[LEDOPMODE]	The LED operating mode
[LHXFANID] The ID of a fan connected to an LHX
Placeholder Definition
[LHXPOWERSUPPLY ID]	The ID of an LHX power supply
[LHXSENSORID] The ID of an LHX sensor probe
[STATE] The human readable state of an asset strip
[VALUE] The new value of a parameter
[VERSION] The firmware version the device is upgrading to
[OCP] The overcurrent protector label
[OCPSENSOR] The overcurrent protector sensor name
[OLDVERSION] The firmware version the device is being upgraded from
[OUTLET] The outlet label
[OUTLETPOLE] The outlet power line identifier
[OUTLETSENSOR] The outlet sensor name
[PARAMETER] The name of a configuration parameter
[POLESENSOR] The sensor name for a certain power line
[PORTID]	The label of the external port, the event triggering device is connected to
[PORTTYPE]	The type of the external port (for example, 'feature' or 'auxiliary', the event triggering device is connected to
[RACKUNIT] The (vertical) rack unit position, an action applies to
[TARGETROLE]	The name of a user management role, an action was applied on
[SERVER]	The name or IP address of a server
[RACKSLOT]	The (horizontal) slot position, an action applies to
[STRIPID] The numeric ID of an asset strip
[STRIPNAME]	The name of an asset strip
[TAGID]	The asset tag ID
[USERNAME]	The user who triggered an action
[RECIPIENTS]	The list of recipients, an SMTP message was sent to
[LDAPERRORDESC]	An LDAP error occurred

Default Log Messages

Following are default log messages triggered and emailed to specified recipients when Dominion PX events occur (are TRUE) or, in some cases, do not occur (are FALSE). See Creating Actions (on page 156) for information configuring email messages to be sent when specified events occur.

Event/Context Default Assertion Message when the Event = TRUE		Default Assertion Message when the Event = FALSE*
Device > System started System	started.
Device > System reset System reset performed by user'[USERNAME]' from host '[USERIP]'.
Device > Firmware validation failed	Firmware validation failed by user'[USERNAME]' from host '[USERIP]'.
Device > Firmware update started	Firmware upgrade started from version'[OLDVERSION]' to version'[VERSION]' by user '[USERNAME]' from host '[USERIP]'.
Device > Firmware update completed	Firmware upgraded successfully from version '[OLDVERSION]' to version'[VERSION]' by user '[USERNAME]' from host '[USERIP]'.
Device > Firmware update failed	Firmware upgrade failed from version'[OLDVERSION]' to version'[VERSION]' by user '[USERNAME]' from host '[USERIP]'.
Device > Device identification changed	Config parameter '[PARAMETER]' changed to '[VALUE]' by user'[USERNAME]' from host '[USERIP]'.
Device > Event log cleared Event	log cleared by user'[USERNAME]' from host '[USERIP]'.
Device > Bulk configuration saved	Bulk configuration saved from host'[USERIP]'.
Device > Bulk configuration copied	Bulk configuration copied from host'[USERIP]'.
Device > Network interface link state is up	The [IFNAME] network interface link is now up.	The [IFNAME] network interface link is now down.
Device > Sending SMTP message failed	Sending SMTP message to'[RECIPIENTS]' using server'[SERVER]' failed.

Chapter 5: Using the Web Interface

Event/Context Default Assertion Message when the Event = TRUE		Default Assertion Message when the Event = FALSE*
Device > An LDAP error occurred	An LDAP error occurred: [LDAPERRORDESC].
Device > USB slave connected	USB slave connected. USB slave disconnected.
Device > Features > Schroff LHX Support	Schroff LHX support enabled. Schroff LHX support disabled.
User Administration > User added	User '[TARGETUSER]' added by user '[USERNAME]' from host '[USERIP]'.
User Administration > User modified	User '[TARGETUSER]' modified by user '[USERNAME]' from host '[USERIP]'.
User Administration > User deleted	User '[TARGETUSER]' deleted by user '[USERNAME]' from host '[USERIP]'.
User Administration > Password changed	Password of user '[TARGETUSER]' changed by user '[USERNAME]' from host '[USERIP]'.
User Administration > Password settings changed	Password settings changed by user '[USERNAME]' from host '[USERIP]'.
User Administration > Role added	Role '[TARGETROLE]' added by user '[USERNAME]' from host '[USERIP]'.
User Administration > Role modified	Role '[TARGETROLE]' modified by user '[USERNAME]' from host '[USERIP]'.
User Administration > Role deleted	Role '[TARGETROLE]' deleted by user '[USERNAME]' from host '[USERIP]'.
User Activity > * > User logged in	User '[USERNAME]' from host '[USERIP]' logged in.	User '[USERNAME]' from host '[USERIP]' logged out.
User Activity > * > Authentication failure	Authentication failed for user '[USERNAME]' from host '[USERIP]'.
User Activity > * > User blocked	User '[USERNAME]' from host '[USERIP]' was blocked.
User Activity > * > Session timeout	Session of user '[USERNAME]' from host '[USERIP]' timed out.
PDU > Load Shedding > Enabled	PX placed in Load Shedding Mode by user '[USERNAME]' from host '[USERIP]'.	PX removed from Load Shedding Mode by user '[USERNAME]' from host '[USERIP]'.
Inlet > * > Sensor > * > Unavailable	Sensor '[INLETSENSOR]' on inlet '[INLET]' unavailable.	Sensor '[INLETSENSOR]' on inlet '[INLET]' available.
Inlet > * > Sensor > * > Above	Sensor '[INLETSENSOR]' on inlet	Sensor '[INLETSENSOR]' on inlet '[INLET]' deasserted 'above upper
upper critical threshold	'[INLET]' asserted 'above upper critical'.	critical'.
Inlet > * > Sensor > * > Above upper warning threshold	Sensor '[INLETSENSOR]' on inlet '[INLET]' asserted 'above upper warning'.	Sensor '[INLETSENSOR]' on inlet '[INLET]' deasserted 'above upper warning'.
Inlet > * > Sensor > * > Below lower warning threshold	Sensor '[INLETSENSOR]' on inlet '[INLET]' asserted 'below lower warning'.	Sensor '[INLETSENSOR]' on inlet '[INLET]' deasserted 'below lower warning'.
Inlet > * > Sensor > * > Below lower critical threshold	Sensor '[INLETSENSOR]' on inlet '[INLET]' asserted 'below lower critical'.	Sensor '[INLETSENSOR]' on inlet '[INLET]' deasserted 'below lower critical'.
Inlet > * > Pole > * > Sensor > * > Unavailable	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' unavailable.	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' available.
Inlet > * > Pole > * > Sensor > * > Above upper critical threshold	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' asserted 'above upper critical'.	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' deasserted 'above upper critical'.
Inlet > * > Pole > * > Sensor > * > Above upper warning threshold	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' asserted 'above upper warning'.	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' deasserted 'above upper warning'.
Inlet > * > Pole > * > Sensor > * > Below lower warning threshold	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' asserted 'below lower warning'.	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' deasserted 'below lower warning'.
Inlet > * > Pole > * > Sensor > * > Below lower critical threshold	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' asserted 'below lower critical'.	Sensor '[POLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' deasserted 'below lower critical'.
Outlet > * > Power control > Powered on	Outlet '[OUTLET]' has been powered on by user '[USERNAME]' from host '[USERIP]'.
Outlet > * > Power control > Powered off	Outlet '[OUTLET]' has been powered off by user '[USERNAME]' from host '[USERIP]'.
Outlet > * > Power control > Power cycled	Outlet '[OUTLET]' power cycle initiated by user '[USERNAME]' from host '[USERIP]'.
Outlet > * > Sensor > * > Unavailable	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' unavailable.	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' available.
Outlet > * > Sensor > * > Above upper critical threshold	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' asserted 'above upper critical'.	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'above upper critical'.

Chapter 5: Using the Web Interface

Event/Context Default Assertion Message when the Event = TRUE		Default Assertion Message when the Event = FALSE*
Outlet > * > Sensor > * > Above upper warning threshold	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' asserted 'above upper warning'.	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'above upper warning'.
Outlet > * > Sensor > * > Below lower warning threshold	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' asserted 'below lower warning'.	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'below lower warning'.
Outlet > * > Sensor > * > Below lower critical threshold	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' asserted 'below lower critical'.	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'below lower critical'.
Outlet > * > Sensor > * > On	Outlet '[OUTLET]' state changed to on.	Outlet '[OUTLET]' state changed to off.
Outlet > * > Pole > * > Sensor > Unavailable	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' unavailable.	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' available.
Outlet > * > Pole > * > Sensor > Above upper critical threshold	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'above upper critical'.	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' deasserted 'above upper critical'.
Outlet > * > Pole > * > Sensor > Above upper warning threshold	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'above upper warning'.	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' deasserted 'above upper warning'.
Outlet > * > Pole > * > Sensor > Below lower warning threshold	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'below lower warning'.	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' deasserted 'below lower warning'.
Outlet > * > Pole > * > Sensor > Below lower critical threshold	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'below lower critical'.	Sensor '[POLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' deasserted 'below lower critical'.
Overcurrent Protector > * > Sensor > * > Unavailable	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' unavailable.	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' available.
Overcurrent Protector > * > Sensor > * > Above upper critical threshold	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'above upper critical'.	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'above upper critical'.
Overcurrent Protector > * > Sensor > * > Above upper warning threshold	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'above upper warning'.	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'above upper warning'.
Overcurrent Protector > * > Sensor > * > Below lower	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]'

Chapter 5: Using the Web Interface

Event/Context Default Assertion Message when the Event = TRUE		Default Assertion Message when the Event = FALSE*
warning threshold 'below lower warning'. deasserted 'below lower warning'.
Overcurrent Protector > * > Sensor > * > Below lower critical threshold	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'below lower critical'.	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'below lower critical'.
Overcurrent Protector > * > Sensor > * > Open	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' is open.	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' is closed.
External Sensor Slot > * > Numeric Sensor > Unavailable	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' unavailable.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' available.
External Sensor Slot > * > Numeric Sensor > Above upper critical threshold	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' asserted 'above upper critical'.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' deasserted 'above upper critical'.
External Sensor Slot > * > Numeric Sensor > Above upper warning threshold	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' asserted 'above upper warning'.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' deasserted 'above upper warning'.
External Sensor Slot > * > Numeric Sensor > Below lower warning threshold	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' asserted 'below lower warning'.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' deasserted 'below lower warning'.
External Sensor Slot > * > Numeric Sensor > Below lower critical threshold	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' asserted 'below lower critical'.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' deasserted 'below lower critical'.
External Sensor Slot > * > State Sensor > Unavailable	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' unavailable.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' available.
External Sensor Slot > * > State Sensor > Closed	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is closed.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is open.
External Sensor Slot > * > State Sensor > On	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is on.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is off.
External Sensor Slot > * > State Sensor > Alarmed	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is alarmed.	External sensor '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' is no longer alarmed.
Server Monitoring > * > Monitored	Server '[SERVER]' is now being monitored.	Server '[SERVER]' is no longer being monitored.

Chapter 5: Using the Web Interface

Event/Context Default Assertion Message when the Event = TRUE		Default Assertion Message when the Event = FALSE*
Server Monitoring > * > Unreachable	Server '[SERVER]' is unreachable. Server '[SERVER]' is reachable.
EnergyWise > Enabled User '[USERNAME]' from host '[USERIP]' enabled EnergyWise.		User '[USERNAME]' from host '[USERIP]' disabled EnergyWise.
Asset Management > State State of asset strip [STRIPID ('[STRIPNAME]') changed to '[STATE]').
Asset Management > Rack Unit > * > Tag Connected	Asset tag with ID '[TAGID]' connected at rack unit [RACKUNIT], slot [RACKSLOT] of asset strip [STRIPID ('[STRIPNAME]').	Asset tag with ID '[TAGID]' disconnected at rack unit [RACKUNIT], slot [RACKSLOT] of asset strip [STRIPID ('[STRIPNAME]').
Asset Management > Rack Unit > * > Blade Extension Connected	Blade extension with ID '[TAGID]' connected at rack unit [RACKUNIT] of asset strip [STRIPID ('[STRIPNAME]').	Blade extension with ID '[TAGID]' disconnected at rack unit [RACKUNIT] of asset strip [STRIPID ('[STRIPNAME]').
Asset Management > Firmware Update	Firmware update for asset strip [STRIPID ('[STRIPNAME]'): status changed to '[STATE]').
Asset Management > Device Config Changed	Config parameter '[PARAMETER]' of asset strip [STRIPID ('[STRIPNAME]') changed to '[VALUE]' by user '[USERNAME]').
Asset Management > Rack Unit Config Changed	Config of rack unit [RACKUNIT] of asset strip [STRIPID ('[STRIPNAME]') changed by user '[USERNAME]' to: LED Operation Mode '[LEDOPMODE]', LED Color '[LEDCOLOR]', LED Mode '[LEDMODE]'
Asset Management > Blade Extension Overflow	Blade extension overflow occurred on strip [STRIPID ('[STRIPNAME]').	Blade extension overflow cleared for strip [STRIPID ('[STRIPNAME]').
Asset Management > Composite Asset Strip Composition Changed	Composition changed on composite asset strip [STRIPID ('[STRIPNAME]').
RF Code Tag > Connected RF Code tag has been connected. RF Code tag has been disconnected.
LHX > Connected LHX has been connected to [PORTTYPE] port [PORTID].		LHX has been disconnected from [PORTTYPE] port [PORTID].
LHX > Operational State LHX connected to [PORTTYPE] port [PORTID] has been switched on.		LHX connected to [PORTTYPE] port [PORTID] has been switched off.

Chapter 5: Using the Web Interface

Event/Context Default Assertion Message when the Event = TRUE	Default Assertion Message when the Event = FALSE*
LHX > Sensor > Unavailable Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' unavailable.	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' available.
LHX > Sensor > Above upper critical threshold Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' asserted 'above upper critical'.	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'above upper critical'.
LHX > Sensor > Above upper warning threshold Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' asserted 'above upper warning'.	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'above upper warning'.
LHX > Sensor > Below lower warning threshold Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' asserted 'below lower warning'.	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'below lower warning'.
LHX > Sensor > Below lower critical threshold Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' asserted 'below lower critical'.	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'below lower critical'.
LHX > Emergency Cooling Emergency cooling on LHX at [PORTTYPE] port '[PORTID]' was activated.	Emergency cooling on LHX at [PORTTYPE] port '[PORTID]' was deactivated.
LHX > Maximum cooling request Maximum cooling was requested for LHX at [PORTTYPE] port '[PORTID]'.	Maximum cooling is not any more requested for LHX at [PORTTYPE] port '[PORTID]'.
LHX > Parameter Data Loss Data loss in parameter memory was detected on LHX at [PORTTYPE] port '[PORTID]'.
LHX > ST-Bus Communication Error An ST-Bus communication error was detected on LHX at [PORTTYPE] port '[PORTID]'.
LHX > Collective fault A collective fault occurred on LHX at [PORTTYPE] port '[PORTID]'.
LHX > Door Contact The door of LHX at [PORTTYPE] port '[PORTID]' was opened.	The door of LHX at [PORTTYPE] port '[PORTID]' was closed.
LHX > Sensor Failure A sensor failure (broken or short circuit) occurred on LHX at [PORTTYPE] port '[PORTID]' at sensor '[LHXSENSORID]'.
LHX > Fan Failure A fan motor failure occurred on LHX at [PORTTYPE] port '[PORTID]' at fan '[LHXFANID]'.
LHX > Power Supply Failure A power supply failure occurred on LHX at [PORTTYPE] port '[PORTID]' at

Chapter 5: Using the Web Interface

Event/Context Default Assertion Message when the Event = TRUE		Default Assertion Message when the Event = FALSE*
	power supply'[LHXPOWERSUPPLYID'].
LHX > Threshold Air Inlet The air inlet temperature threshold on LHX at [PORTTYPE] port '[PORTID]' was crossed.		The air inlet temperature on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
LHX > Threshold Air Outlet The air outlet temperature threshold on LHX at [PORTTYPE] port '[PORTID]' was crossed.		The air outlet temperature on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
LHX > Threshold Water Inlet The water inlet temperature threshold on LHX at [PORTTYPE] port '[PORTID]' was crossed.		The water inlet temperature on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
LHX > Threshold Water Outlet The water outlet temperature threshold on LHX at [PORTTYPE] port '[PORTID]' was crossed.		The water outlet temperature on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
LHX > Threshold Humidity The humidity threshold on LHX at [PORTTYPE] port '[PORTID]' was crossed.		The humidity on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
LHX > External Water Cooling Failure	An external water cooling failure occurred on LHX at [PORTTYPE] port '[PORTID]'.
LHX > Water Leak Water leakage was detected on LHX at [PORTTYPE] port '[PORTID]'.

*Note: Not set for 'trigger' events (see [ASSERTION]).

Creating Rules

After required actions are available, you can create event rules to determine what actions are taken to respond to specific events.

By default, the Dominion PX provides two built-in event rules -- System Event Log Rule and System SNMP Trap Rule. If the built-in rules do not satisfy you needs, create new ones.

To create event rules:

1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. On the Rules tab, click New Rule.
3. In the "Rule name" field, type a new name for identifying the rule. The default name is New Rule , where is a sequential number.

4. Select the Enabled checkbox to enable this event rule.

5. Click Event to select an event for which you want to trigger an action. A pull-down menu showing all types of events appears.

- Select the desired event type from the pull-down menu, and if a submenu appears, continue the navigation until the desired event is selected.

Note: The option refers to all events/items listed on the same submenu, refers to all slots, refers to all servers, and refers to all users.

1. According to the event you selected in the previous step, the "Trigger condition" field containing three radio buttons may or may not appear.

Event types Radio buttons
Numeric sensor threshold-crossing events, or asset tag connections or disconnections	Available radio buttons include "Asserted," "Deasserted" and "Both."Asserted: The Dominion PX takes the action only when the event occurs. This means the status of the described event transits from FALSE to TRUE.Deasserted: The Dominion PX takes the action only when the event condition disappears. This means the status of the described event transits from TRUE to FALSE.Both: The Dominion PX takes the action both when the event occurs (asserts) and when the event condition disappears (deasserts).
Discrete (on/off) sensor state change	Available radio buttons include "Alarmed," "No longer alarmed" and "Both."Alarmed: The Dominion PX takes the action only when the chosen sensor enters the alarmed state, that is, the abnormal state.No longer alarmed: The Dominion PX takes the action only when the chosen sensor returns to normal.Both: The Dominion PX takes the action both when the chosen sensor enters or quits the alarmed state.
Sensor availability	Available radio buttons include "Unavailable," "Available" and "Both." ·Unavailable: The Dominion PX takes the action only when the chosen sensor is NOT detected and becomes unavailable. ·Available: The Dominion PX takes the action only when the chosen sensor is detected and becomes available. ·Both: The Dominion PX takes the action both when the chosen sensor becomes unavailable or available.
Network interface link state	Available radio buttons include "Link state is up," "Link state is down" and "Both." ·Link state is up: The Dominion PX takes the action only when the network link state changes from down to up. ·Link state is down: The Dominion PX takes the action only when the network link state changes from up to down. ·Both: The Dominion PX takes the action whenever the network link state changes.
Function enabled or disabled	Available radio buttons include "Enabled," "Disabled" and "Both." ·Enabled: The Dominion PX takes the action only when the chosen function is enabled. ·Disabled: The Dominion PX takes the action only when the chosen function is disabled. ·Both: The Dominion PX takes the action when the chosen function is either enabled or disabled.
User login or logout	Available radio buttons include "Logged in," "Logged out," and "Both." ·Logged in: The Dominion PX takes the action only when the selected user logs in. ·Logged out: The Dominion PX takes the action only when the selected user logs out. ·Both: The Dominion PX takes the action both when the selected user logs in and logs out.
Server monitoring event	Available radio buttons include "Monitoring started," "Monitoring stopped," and "Both."Monitoring started: The Dominion PX takes the action only when the monitoring of any specified server starts.Monitoring stopped: The Dominion PX takes the action only when the monitoring of any specified server stops.Both: The Dominion PX takes the action when the monitoring of any specified server starts or stops.
Server reachability	Available radio buttons include "Unreachable," "Reachable," and "Both."Unreachable: The Dominion PX takes the action only when any specified server becomes inaccessible.Reachable: The Dominion PX takes the action only when any specified server becomes accessible.Both: The Dominion PX takes the action when any specified server becomes either inaccessible or accessible.
RF Code tag connection or disconnection	Available radio buttons include "Connected," "Disconnected" and "Both."Connected: Dominion PX takes the action only when an RF Code tag is physically connected to it.Disconnected: Dominion PX takes the action only when an RF Code tag is physically disconnected from it.Both: Dominion PX takes the action both when the RF Code tag is physically connected to it and when it is disconnected.
Outlet power state change	Available radio buttons include "On," "Off" and "Both."On: Dominion PX takes the action only when the chosen outlet is turned ON.Off: Dominion PX takes the action only when the chosen outlet is turned OFF.Both: Dominion PX takes the action when the chosen outlet is either turned ON or turned OFF.

Note: The outlet power state change events are available only for outlet-switching capable PDUs.

1. In the Actions field, click the drop-down arrow, select the desired

action from the list, and click the Add Action button 🧑 Add Action to add the action.

The added action will be listed in the list box to the right of the Actions filed.

1. To add additional actions, repeat Step 7.

2. To remove any added action, select it from the list box, and click the

"Remove selected Action" button Remove selected Action

1. Click Save to save the new event rule.

Note: If you do not click Save before quitting the current settings page, a message appears. Then click Yes to save the changes, Discard to abort the changes or Cancel to return to the current settings page.

1. Repeat Steps 2 to 10 to create additional event rules.

2. Click Close to quit the dialog.

Sample Event Rules

Sample PDU-Level Event Rule

In this example, we want Dominion PX to record the firmware upgrade failure in the internal log when it happens. The sample event rule looks like this:

• Event: Events > Device > Firmware update failed
- Trigger condition: asserted
- Actions: System Event Log Action

To create the above event rule:

1. Select Events > Device to indicate we are specifying an event at the PDU level.
2. Select "Firmware update failed" in the submenu because we want Dominion PX to respond to the event related to firmware upgrade failure.
3. Select System Event Log Action as we intend to record the firmware update failure event in the internal log.
4. Select the "asserted" radio button since we want the selected event to be recorded only when it occurs.

Sample Outlet-Level Event Rule

In this example, we want Dominion PX to send SNMP traps to the SNMP manager both when any sensor reading of outlet 3 crosses any threshold and when it returns to normal. To do that we would set up an event rule like this:

• Event: Events > Outlet > Outlet 3 > Sensor > Any sub-event
- Trigger condition: both
- Actions: System SNMP Trap Action

To create the above event rule:

1. Select Events > Outlet to indicate we are specifying an event at the outlet level.
2. Select "Outlet 3" from the submenu because that is the outlet in question.
3. Select "Sensor" to refer to sensor readings.
4. Select "Any sub-event" because we want to specify all events related to all types of outlet sensors and thresholds, such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold, lower warning threshold, and so on.
5. Select "System SNMP Trap Action" to send SNMP traps to respond to the specified event.
6. Select the "both" radio button so that the SNMP traps are sent both when any sensor reading of outlet 3 moves past any threshold into the warning or critical range and when the sensor reading returns to normal.

For example, when the outlet 3's voltage crosses into the upper warning range, the SNMP traps are sent, and when the voltage drops below the upper warning threshold, the SNMP traps are sent again.

Sample Inlet-Level Event Rule

In this example, we want Dominion PX to send SNMP traps to the SNMP manager both when any sensor reading of the Inlet I1 crosses any threshold and when it returns to normal. The event rule is set like this:

• Event: Events > Inlet > Inlet I1 > Sensor > Any sub-event
- Trigger condition: both
- Actions: System SNMP Trap Action

▶ To create the above event rule:

1. Select Events > Inlet to indicate we are specifying an event at the inlet level.

2. Select "Inlet I1" from the submenu because that is the inlet in question.

3. Select "Sensor" to refer to sensor readings.
4. Select "Any sub-event" because we want to specify all events related to all types of inlet sensors and thresholds, such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold, lower warning threshold, and so on.
5. Select "System SNMP Trap Action" to send SNMP traps to respond to the specified event.
6. Select the "both" radio button so that the SNMP traps are sent both when any sensor reading of Inlet I1 moves past any threshold into the warning or critical range and when the sensor reading returns to normal.

For example, when the Inlet I1's voltage crosses into the upper warning range, the SNMP traps are sent, and when the voltage drops below the upper warning threshold, the SNMP traps are sent again.

Sample Environmental-Sensor-Level Event Rule

This section only applies to outlet-switching capable PDUs.

In this example, we want Dominion PX to enable the load shedding function when a contact closure sensor enters the alarmed state. This sample event rule requires the creation of a new action before creating the rule.

Step 1: create a new action for enabling the load shedding mode

1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. Click the Actions tab.
3. Click New Action.
4. In the Action Name field, type a name to identify this action. In this illustration, type Enable Load Shedding.
5. In the Action field, select "Change load shedding state."
6. In the Operation field, select "Enable load shedding."
7. Click Save to save this action.

After the new action for enabling the load shedding mode is created, you can create an event rule that can trigger the load shedding mode when the contact closure sensor enters the alarmed state. This sample event rule looks like this:

• Event: Events > External Sensor Slot > Slot 1 > State Sensor > Alarmed
• Trigger condition: Alarmed
• Actions: Enable Load Shedding

Step 2: create the contact closure triggered load shedding event rule

1. Click the Rules tab.
2. Click New Rule.
3. In the "Rule name" field, type a name to identify this event rule. In this illustration, type Contact Closure Triggered Load Shedding.
4. Select the Enabled checkbox. Otherwise, the new event rule will not be carried out.
5. Select Events > External Sensor Slot to indicate we are specifying an event related to the environmental sensor.
6. Select the ID number of the desired contact closure sensor. In this illustration, the ID number of the desired contact closure sensor is 1, so select Slot 1 in the submenu.
7. Select State Sensor because the contact closure sensor is a discrete sensor, which indicates the environmental changes through the status changes.
8. Select Alarmed in the submenu since we want the action "Enable Loading Shedding" to be taken when the selected contact closure sensor changes its state related to the "alarmed" state.
9. In the "Trigger condition" field, select the Alarmed radio button because we want the Dominion PX to respond to the event only when the contact closure sensor enters the Alarm state.

A Note about Infinite Loop

You should avoid building an infinite loop when creating event rules.

The infinite loop refers to a condition where the 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 event again.

Example 1

This example illustrates an event rule which continuously causes the PDU to send out SMTP messages.

Event selected Action included
Device > Sending SMTP message failed	Send SMTP message

Example 2

This example illustrates an event rule which continuously causes the PDU to send out SMTP messages when one of the selected events listed on the Device menu occurs. Note that the under the Device menu includes the event "Sending SMTP message failed."

Event selected Action included
Device > Any sub-event Send SMTP message

Example 3

This example illustrates a situation where two event rules combined regarding the outlet state changes causes the PDU to continuously power cycle outlets 1 and 2.

Event selected Action included
Outlet > Outlet 1 > Sensor > State > On/Off	Cycle Outlet 2(Switch Outlets --> Cycle Outlet --> Outlet 2)
Outlet > Outlet 2 > Sensor > State > On/Off	Cycle Outlet 1(Switch Outlets --> Cycle Outlet --> Outlet 1)

Modifying an Event Rule

You can change an event rule's event, action, trigger condition and other settings, if any.

Exception: Events and actions selected in the built-in event rules are not changeable, including System Event Log Rule and System SNMP Trap Rule.

▶ To modify an event rule:

1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.

2. On the Rules tab, select the event rule that you want to modify in the left pane.

3. To disable the event rule, deselect the Enabled checkbox.
4. To change the event, click the desired tab in the Event field and select a different item from the pull-down menu or submenu.

For example, in a user activity event rule for the "admin" user, you can click the "admin" tab to display a pull-down submenu showing all user names, and then select a different user name or all user names (referred to as ).

1. If radio buttons are available, you may select a radio button other than the current selection to change the rule triggering condition.

2. To change the action(s), do any of the following in the Actions field:

3. To add a new action, click the drop-down arrow, select the action from the list, and click the Add Action button.

4. To remove any added action, select it from the list box, and click the "Remove selected Action" button Remove selected Action

5. Click Save to save the changes.

Note: If you do not click Save before quitting the current settings page, a message appears. Then click Yes to save the changes, Discard to abort the changes or Cancel to return to the current settings page.

1. Click Close to quit the dialog.

Modifying an Action

An existing action can be changed so that all event rules where this action is involved change their behavior accordingly.

Exception: The built-in action "System Event Log Action" is not user-configurable.

▶ To modify an action:

1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. Click the Actions tab.
3. Select the action that you want to modify from the left list.
4. Make necessary changes to the information shown.
5. Click Save to save the changes.

Note: If you do not click Save before quitting the current settings page, a message appears. Then click Yes to save the changes, Discard to abort the changes or Cancel to return to the current settings page.

1. Click Close to quit the dialog.

Deleting an Event Rule or Action

If any event rule or action is obsolete, simply remove it.

Note: You cannot delete the built-in event rules and actions.

To delete an event rule or action:

1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. To delete an event rule:

a. Ensure the Rules tab is selected. If not, click the Rules tab.
b. Select the desired rule from the left list, and click Delete Rule.
c. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.

1. To delete an action:

a. Click the Actions tab.
b. Select the desired action from the left list, and click Delete Action.
c. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.

1. Click Close to quit the dialog.

A Note about Untriggered Rules

In some cases, a measurement exceeds a threshold causing the Dominion PX to generate an alert. The measurement then returns to a value within the threshold, but the Dominion PX does not generate an alert message for the Deassertion event. Such scenarios can occur due to the hysteresis tracking the Dominion PX uses. See What is Deassertion Hysteresis? (on page 153).

Managing Event Logging

By default, the Dominion PX captures certain system events and saves them in a local (internal) event log.

Viewing the Local Event Log

You can view up to 2,000 historical events that occurred to the Dominion PX device in the local event log.

When the log already contains 2,000 entries, each new entry overwrites the oldest entry.

▶ To display the local log:

1. Choose Maintenance > View Event Log. The Event Log dialog appears.

Each event entry in the local log consists of:

• Date and time of the event

• Type of the event
  ■ A description of the event
  ■ ID number of the event

• The dialog shows the final page by default. You can:

- Switch between different pages by doing one of the following:

• Click ↩ or ▶ to go to the first or final page.
• Click ◀ or ▶ to go to the prior or next page.

- Type a number in the Page text box and press Enter to go to a specific page.

- Select a log entry from the list and click Show Details, or simply double-click the log entry to view detailed information.

Note: Sometimes when the dialog is too narrow, the icon >> takes the place of the Show Details button. In that case, click >> and select Show Details to view details.

- Click ➤ to view the latest events.

1. Enlarge the dialog if necessary.
2. You can re-sort the list or change the columns displayed.
3. Click Close to quit the dialog.

Clearing Event Entries

If it is not necessary to keep existing event history, you can remove all of it from the local log.

▶ To delete all event entries:

1. Choose Maintenance > View Event Log. The Event Log dialog appears.

2. Click Clear Event Log.

3. Click Close to quit the dialog.

Viewing Connected Users

You can see which users are connected to the Dominion PX device and their status. If you have administrator privileges, you can terminate any user's connection to the Dominion PX device.

▶ To view connected users:

1. Choose Maintenance > Connected Users. The Connected Users dialog appears, showing a list of connected users with the following information:

Column Description

User Name The login name used by each connected user.

IP Address The IP address of each user's host.For the login via a serial connection,is displayed instead of an IP address.

Client Type The interface through which the user is being connected to the Dominion PX.▪ Web GUI: Refers to the Dominion PX web interface.▪ CLI: Refers to the command line interface (CLI).The information in parentheses following "CLI" indicates how this user was connected to the CLI.- Serial: Represents the local connection (serial or USB).- SSH: Represents the SSH connection.- Telnet: Represents the Telnet connection.

Idle Time The length of time for which a user remains idle.The unit "min" represents minutes.

1. To disconnect any user, click the corresponding Disconnect button.

a. A dialog appears, prompting you to confirm the operation.
b. Click Yes to disconnect the user or No to abort the operation. If clicking Yes, the connected user is forced to log out.

1. You may change the sorting order of the list if necessary. See Changing the Sorting (on page 79).
2. Click Close to quit the dialog.

Monitoring Server Accessibility

You can monitor whether specific IT devices are alive by having the Dominion PX device continuously ping them. An IT device's successful response to the ping commands indicates that the IT device is still alive and can be remotely accessed.

Adding IT Devices for Ping Monitoring

You can have the Dominion PX monitor the accessibility of any IT equipment, such as DB servers and remote authentication servers.

To add IT equipment for ping monitoring:

1. Choose Device Settings > Server Reachability. The Server Reachability dialog appears.
2. Click New. The Add New Server dialog appears.
3. By default, the "Enable Ping Monitoring for this Server" checkbox is selected. If not, select it to enable the ping monitoring feature.
4. Provide the information required.

Field Description
IP Address/Hostname	IP address or host name of the IT equipment whose accessibility you want to monitor.
Number of Successful Pings to Enable Feature	The number of successful pings required to enable this feature. Valid range is 0 to 200.
Wait Time (in seconds) after Successful Ping	The wait time before sending the next ping if the previous ping was successfully responded. Valid range is 5 to 600 (seconds).
Wait Time (in seconds) after Unsuccessful Ping	The wait time before sending the next ping if the previous ping was not responded. Valid range is 3 to 600 (seconds).
Number of Consecutive Unsuccessful Pings for Failure	The number of consecutive pings without any response before the IT equipment is declared unresponsive. Valid range is 1 to 100.
Wait Time (in seconds) before Resuming Pinging	The wait time before resuming pinging after the IT equipment is declared unresponsive. Valid range is 1 to 1200 (seconds).

1. Click OK to save the changes.

2. To add more IT devices, repeat Steps 2 to 5.

3. Click Close to quit the dialog.

Editing Ping Monitoring Settings

You can edit the ping monitoring settings for any IT device whenever it requires changes.

To modify the ping monitoring settings for an IT device:

1. Choose Device Settings > Server Reachability. The Server Reachability dialog appears.
2. Select the IT device whose settings you want to modify by clicking it.
3. Click Edit or double-click the IT device. The Edit Server 'XXX' dialog appears, where XXX is the IP address or host name of the IT device.
4. Make changes to the information shown.
5. Click OK to save the changes.

Deleting Ping Monitoring Settings

When it is not necessary to monitor the accessibility of any IT device, just remove it.

To delete ping monitoring settings for an IT device:

1. Choose Device Settings > Server Reachability. The Server Reachability dialog appears.
2. Select the IT device whose ping monitoring settings you want to remove by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
3. Click Delete.
4. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.
5. Click Close to quit the dialog.

Checking Server Monitoring States

Server monitoring results are available in the Server Reachability dialog after specifying servers for the Dominion PX device to monitor.

To check the server monitoring states and results:

1. Choose Device Settings > Server Reachability. The Server Reachability dialog appears.

2. The column labeled "Ping Enabled" indicates whether the monitoring for the corresponding server is activated or not.

3. : This icon denotes that the monitoring for the corresponding server is enabled.

4. ✗ : This icon denotes that the monitoring for the corresponding server is disabled.

5. The column labeled "Status" indicates the accessibility of each monitored server.

Status Description

Reachable The server is accessible.
Unreachable The server is inaccessible.
Waiting for reliable connection	The connection between the Dominion PX device and the server is not established yet.

1. You may change the sorting order of the list if necessary. See Changing the Sorting (on page 79).
2. Click CI ose to quit the dialog.

Environmental Sensors

The Dominion PX can monitor the environmental conditions, such as temperature and humidity, where environmental sensors are placed.

To add environmental sensors:

1. Physically connect environmental sensors to the Dominion PX device. See Connecting Environmental Sensors (Optional) (on page 33).
2. Log in to the Dominion PX web interface. The Dominion PX should have detected the connected sensors, and display them in the web interface.
3. Identify each sensor through the sensor's serial number. See Identifying Environmental Sensors (on page 187).
4. The Dominion PX should automatically manage the detected sensors. Verify whether detected sensors are managed. If not, have them managed. See Managing Environmental Sensors (on page 188).
5. Configure the sensors. See Configuring Environmental Sensors (on page 189). The steps include:

a. Nam e the sensor.
b. If the connected sensor is a Raritan contact closure sensor, specify an appropriate sensor type.
c. Mark the sensor's physical location on the rack or in the room.
d. For a numeric sensor, configure the sensor's threshold, hysteresis and assertion timeout settings.

Note: Numeric sensors use numeric values to indicate the environmental or internal conditions while discrete (on/off) sensors use alphabetical characters to indicate the state. Only numeric sensors have the threshold settings.

Identifying Environmental Sensors

An environmental sensor includes a serial number tag on the sensor cable.

SN1: AHI8100078 SN2: AHI8100079 RoHS CE SN: AHI8100100 RoHS CE

The serial number for each sensor appears listed in the web interface after each sensor is detected by the Dominion PX.

To identify each detected environmental sensor:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click External Sensors in the Dominion PX Explorer pane, and the External Sensors page opens in the right pane.

External Sensors
#.n	Serial Number	Type	Channel	Name	Reading	State
1	PRC0190292	Contact (On/Off)	1	On/Off 1		normal
2	PRC0190292	Contact (On/Off)	2	On/Off 2		normal
3	AEI7A00022	Temperature		Temperature 1	25.6 °C	normal
4	AEI7A00022	Humidity		Humidity 1	59 %	normal

1. Match the serial number from the tag to those listed in the sensor table.

Managing Environmental Sensors

The Dominion PX starts to retrieve an environmental sensor's reading and/or state and records the state transitions after the environmental sensor is managed.

The Dominion PX device can manage a maximum of 16 environmental sensors.

When there are less than 16 managed sensors, the Dominion PX automatically brings detected environmental sensors under management. You should only have to manually manage a sensor when it is not under management.

To manually manage an environmental sensor:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click External Sensors in the Dominion PX Explorer pane, and the External Sensors page opens in the right pane.

2. Click the sensor you want to manage on the External Sensors page.

Note: To identify all detected sensors, see Identifying Environmental Sensors (on page 187).

1. Click Manage. The "Manage sensor ()" dialog appears, where is the sensor's serial number and is the sensor's type.

Note: For a contact closure sensor, a channel number is added to the end of the .

1. There are two ways to manage the sensor:

2. To manage this sensor by letting the Dominion PX assign a number to it, select "Automatically assign a sensor number." This method does not release any managed sensors.

3. To manage this sensor by assigning the number you want to it, select "Manually select a sensor number." Then click the drop-down arrow to select a number.

If the number you selected was already assigned to a sensor, that sensor becomes released after losing this ID number.

Tip: The information in parentheses following each ID number indicates whether the number has been assigned to any sensor. If it has been assigned to a sensor, it shows that sensor's serial number. Otherwise, it shows the term "unused."

1. Click OK. The Dominion PX starts to track and display the managed sensor's reading and/or state.
2. To manage additional sensors, repeat Steps 3 to 6.

Note: When the number of managed sensors reaches the maximum, you CANNOT manage additional sensors until you remove or replace any managed sensors. To remove a sensor, see Unmanaging Environmental Sensors (on page 195).

Configuring Environmental Sensors

You may change the default name for easily identifying the managed sensor, and describe its location with X, Y and Z coordinates.

To configure environmental sensors:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click External Sensors in the Dominion PX Explorer pane, and the External Sensors page opens in the right pane.
2. Select the sensor that you want to configure.
3. Click Setup. The "Setup of external sensor ()" dialog appears, where is the serial number of this sensor and is the sensor's type.

Tip: You can also trigger the same setup dialog by selecting the desired environmental sensor icon in the tree and then clicking Setup on that sensor's page opened in the right pane.

1. If the selected environmental sensor is the Raritan contact closure sensor connected with a third-party detector/switch, select the appropriate sensor type in the Binary Sensor Subtype field.

2. Contact: The detector/switch is designed to detect the door lock or door open/closed status.

3. Smoke Detection: The detector/switch is designed to detect the appearance of smoke.
4. Water Detection: The detector/switch is designed to detect the appearance of water on the floor.

- Vibration: The detector/switch is designed to detect the vibration in the floor.

1. Type a new name in the Name field.

2. Describe the sensor's location by assigning alphanumeric values to the X, Y and Z coordinates. See Describing the Sensor Location (on page 191).

Note: When the term "Rack Units" appears inside the parentheses in the Z location field, indicating that the Z coordinate format is set to Rack Units, you must type an integer number.

1. If the selected environmental sensor is a numeric sensor, its threshold settings are displayed in the dialog. Click Edit or double-click the Threshold Configuration table to adjust the threshold, deassertion hysteresis and assertion timeout settings.

2. To enable any threshold, select the corresponding checkbox. To disable a threshold, deselect the checkbox.
   ■ After any threshold is enabled, type an appropriate numeric value in the accompanying text box.

3. To enable the deassertion hysteresis for all thresholds, type a numeric value other than zero in the Deassertion Hysteresis field. See What is Deassertion Hysteresis? (on page 153).
4. To enable the assertion timeout for all thresholds, type a numeric value other than zero in the Assertion Timeout (samples) field. See What is Assertion Timeout? (on page 154).

Note: The Upper Critical and Lower Critical values are points at which the Dominion PX considers the operating environment critical and outside the range of the acceptable threshold.

1. Click OK to save the changes.
2. Repeat Steps 3 through 9 to configure additional environmental sensors.

Setting the Z Coordinate Format

You can use either the number of rack units or a descriptive text to describe the vertical locations (Z coordinates) of environmental sensors.

To determine the Z coordinate format:

1. Click the PDU folder.

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click Setup in the Settings section. The Pdu Setup dialog appears.

2. In the "External sensors Z coordinate format" field, click the drop-down arrow and select an option from the list.

3. Rack Units: The height of the Z coordinate is measured in standard rack units. When this is selected, you can type a numeric value in the rack unit to describe the Z coordinate of any environmental sensors.

4. Free-Form: Any alphanumeric string can be used for specifying the Z coordinate.

5. Click OK to save the changes.

Describing the Sensor Location

Use the X, Y and Z coordinates to describe each sensor's physical location. You can use these location values to track records of environmental conditions in fixed locations around your IT equipment. The X, Y and Z values act as additional attributes and are not tied to any specific measurement scheme. If you choose to, you can use non-measurement values. For example:

$$ \begin{array}{l} X = \text { Brown Cabinet Row } \ Y = \text { Third Rack } \ Z = \text { Top of Cabinet } \ \end{array} $$

Values for the X, Y and Z coordinates may consist of:

• For X and Y: Any combination of alphanumeric characters. The coordinate value can be 0 to 32 characters long.
• For Z when the Z coordinate format is set to Rack Units, any numeric value ranging from 0 to 60.
• For Z when the Z coordinate format is set to Free-Form, any alphanumeric characters from 0 to 32 characters.

Tip: To configure and retrieve these coordinate values over SNMP, see the Dominion PX MIB. To configure and retrieve these values over the CLI, see Using the Command Line Interface (on page 230).

Viewing Sensor Data

Readings of the environmental sensors will display in the web interface after these sensors are properly connected and managed.

The Dashboard page shows the information for managed environmental sensors only, while the External Sensors page shows the information for both of managed and unmanaged ones.

If a sensor reading row is colored, it means the sensor reading already crosses one of the thresholds, or the circuit breaker has tripped. See The Yellow- or Red-Highlighted Reading (on page 76).

To view managed environmental sensors only:

1. Click the Dashboard icon in the Dominion PX Explorer pane, and the Dashboard page opens in the right pane.
2. Locate the External Sensors section on the Dashboard page. The section shows:

■ Total number of managed sensors
■ Total number of unmanaged sensors
■ Information of each managed sensor, including:

• Name
• Reading
• State

To view both of managed and unmanaged environmental sensors:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click External Sensors in the Dominion PX Explorer pane, and the External Sensors page opens in the right pane.

Detailed information for each connected sensor is displayed, including:

• Label (number)
• Serial number
• Sensor type
  Name
• Reading

State
■ Channel (for a contact closure sensor only)

Sensor Measurement Accuracy

Raritan environmental sensors are with the following factory specifications. Calibration is not required for environmental sensors.

• Temperature: +/-2%
- Humidity: + / - 5%
• Differential air pressure: +/-1.5%
• Air flow: +/-6.5%

States of Managed Sensors

An environmental sensor shows the state after being managed.

Available sensor states vary depending on the sensor type -- numeric or discrete. For example, a contact closure sensor is a discrete sensor so it switches between three states only -- unavailable, alarmed and normal.

Note: Numeric sensors use numeric values to indicate the environmental or internal conditions while discrete (on/off) sensors use alphabetical characters to indicate the state.

Sensor state Applicable to
unavailable	All sensors
alarmed	Discrete sensors
normal	All sensors
below lower critical Numeric sensors
below lower warning Numeric sensors
above upper warning Numeric sensors
above upper critical Numeric sensors

"unavailable" State

The unavailable state means the connectivity to the sensor is lost.

The Dominion PX pings all managed sensors at regular intervals in seconds. If it does not detect a particular sensor for three consecutive scans, the unavailable state is displayed for that sensor.

When the communication with a contact closure sensor's processor is lost, all detectors (that is, all switches) connected to the same sensor module show the "unavailable" state.

Note: When the sensor is deemed unavailable, the existing sensor configuration remains unchanged. For example, the ID number assigned to the sensor remains associated with it.

The Dominion PX continues to ping unavailable sensors, and moves out of the unavailable state after detecting the sensor for two consecutive scans.

"normal" State

This state indicates the sensor is in the normal state.

For a contact closure sensor, this state is the normal state you have set.

• If the normal state is set to Normally Closed, the normal state means the contact closure switch is closed.
• If the normal state is set to Normally Open, the normal state means the contact closure switch is open.

Note: See Configuring a Contact Closure Sensor (on page 36) for setting the normal state.

For a numeric sensor, this state means the sensor reading is within the acceptable range as indicated below:

Lower Warning threshold <= Reading < Upper Warning threshold

Note: The symbol <= means smaller than (<) or equal to (=).

"alarmed" State

This state means a discrete (on/off) sensor is in the "abnormal" state.

For a contact closure sensor, the meaning of this state varies based on the sensor's normal state setting.

• If the normal state is set to Normally Closed, the alarmed state means the contact closure switch is open.
• If the normal state is set to Normally Open, the alarmed state means the contact closure switch is closed.

Note: See Configuring a Contact Closure Sensor (on page 36) for setting the normal state.

Tip: A contact closure sensor's LED is lit after entering the alarmed state. If the sensor module has two channels for connecting two switches, two LEDs are available. Check which contact closure switch is in the "abnormal" status according to the channel number of the LED.

"below lower critical" State

This state means a numeric sensor's reading is below the lower critical threshold as indicated below:

Reading < Lower Critical Threshold

"below lower warning" State

This state means a numeric sensor's reading is below the lower warning threshold as indicated below:

Lower Critical Threshold <= Reading < Lower Warning Threshold

Note: The symbol <= means smaller than (<) or equal to (=).

"above upper warning" State

This state means a numeric sensor's reading is above the upper warning threshold as indicated below:

Upper Warning Threshold <= Reading < Upper Critical Threshold

Note: The symbol <= means smaller than (<) or equal to (=) .

"above upper critical" State

This state means a numeric sensor's reading is above the upper critical threshold as indicated below:

Upper Critical Threshold <= Reading

Note: The symbol <= means smaller than (<) or equal to (=).

Unmanaging Environmental Sensors

When it is unnecessary to monitor a particular environmental factor, you can unmanage or release the corresponding environmental sensor so that the Dominion PX device stops retrieving the sensor's reading and/or state.

To release a managed sensor:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click External Sensors in the Dominion PX Explorer pane, and the External Sensors page opens in the right pane.
2. Click the sensor you want to unmanage on the External Sensors page.
3. Click Release.

After a sensor is removed from management, the ID number assigned to that sensor is released and can be automatically assigned to any newly-detected sensor.

Asset Management

Configure the asset management settings only when an asset sensor is physically connected to the Dominion PX device.

Note: To set up an asset management system, see Connecting the Asset Management Sensor (Optional) (on page 38).

Configuring the Asset Sensor

The Dominion PX CANNOT detect how many rack units (tag ports) a connected asset sensor supports so you must provide this information manually.

In addition, you can name the asset sensor or determine the numbering way for all rack units in the web interface.

To configure an asset sensor (asset strip):

1. If the Feature Port folder is not expanded, expand it to show the device under the Feature Port folder. See Expanding the Tree (on page 71).
2. Click the asset sensor in the left pane. The asset sensor's page opens in the right pane.

Note: The asset sensor is named "Asset Strip 1" by default. The name changes after being customized.

Tip: The same asset sensor's page can be also opened by clicking Feature Port in the left pane, and then double-clicking the asset sensor in the right pane.

1. Click Setup. The setup dialog for the asset sensor appears.

Tip: You can also trigger the same dialog by clicking Asset Management in the left pane, and then clicking Asset Strip Setup or double-clicking the asset sensor in the right pane.

1. To rename the asset sensor, type a new name in the Name field.

2. Type the total number of rack units the selected asset sensor has in the "Number of Rack Units" field. This field shows 48 by default.

3. Determine how to number all rack units on the asset sensor by selecting an option in the Numbering Mode.

4. Top-Down: The rack units are numbered in the ascending order from the highest to the lowest rack unit.

5. Bottom-Up: The rack units are numbered in the descending order from the highest to the lowest rack unit.

6. In the Numbering Offset field, select the starting number. For example, if you select 3, the first rack unit is numbered 3, the second is numbered 4, the third is numbered 5, and so on until the final number.

7. Indicate how the asset sensor is mounted in the rack in the Orientation field. The rack unit that is most close to the RJ-45 connector of the asset sensor will be marked with the index number 1 in the web interface.

For the latest version of asset sensors with a built-in tilt sensor, it is NOT necessary to configure the orientation setting manually. The Dominion PX device can detect the orientation of the asset sensors and automatically configure it.

- Top Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located on the top.

1. Bottom Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom. Click OK to save the changes.

Setting Asset Sensor LED Colors

Each LED on the asset sensor indicates the presence and absence of a connected asset tag by changing its color. You can configure or change the color settings for all LEDs on the connected asset sensor(s) by following the procedure below.

This feature is accessible only by users with Administrative Privileges.

To configure all LED colors:

1. Connect the asset sensor to the Dominion PX if it is not already. See Connecting Asset Sensors to the Dominion PX (on page 41).
2. Click on the Feature Ports folder in the navigation tree to expand it.

3. Click the desired asset sensor. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports).

4. Click Setup on the asset sensor page. The setup dialog for that asset sensor appears.

5. To change the LED color denoting the presence of a connected tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color with connected Tag" field.
6. To change the LED color denoting the absence of a connected tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color without connected Tag" field.
7. Click OK to save the changes.

Tip: To make a specific LED's color settings different from other LEDs, see Configuring a Specific Rack Unit (on page 198).

Configuring a Specific Rack Unit

In the Dominion PX web interface, a rack unit refers to a tag port on the asset sensor. You can name a specific rack unit, or change its LED color settings so that this LED behaves differently from others on the same asset sensor.

To configure a specific rack unit:

1. If the Feature Port folder is not expanded, expand it to show the device under the Feature Port folder. See Expanding the Tree (on page 71).
2. Click the asset sensor in the left pane. The asset sensor's page opens in the right pane.

Note: The asset sensor is named "Asset Strip 1" by default. The name changes after being customized.

Tip: The same asset sensor's page can be also opened by clicking Feature Port in the left pane, and then double-clicking the asset sensor in the right pane.

1. Select the rack unit whose LED settings you want to change.
2. Click Configure Rack Unit or double-click the selected rack unit. The setup dialog for the selected rack unit appears.
3. In the Name field, type a name for identifying this rack unit.
4. Select either Auto or Manual Override as this rack unit's LED mode.

- Auto (based on Tag): This is the default setting. With this option selected, the LED follows the global LED color settings.

- Manual Override: This option differentiates this LED's behavior. After selecting this option, you must select an LED mode and/or an LED color for the selected rack unit.

• LED Mode: Select On to have the LED stay lit, Off to have it stay off, "Slow blinking" to have it blink slowly, or "Fast blinking" to have it blink quickly.

• LED Color: If you select On, "Slow blinking" or "Fast blinking" in the LED Mode field, select an LED color by either clicking a color in the color palette or typing the hexadecimal RGB value of a color in the accompanying text box.

• Click OK to save the changes.

Expanding a Blade Extension Strip

A blade extension strip, like an asset sensor, has multiple tag ports. After connecting it to a specific asset sensor, it is displayed as a folder on that asset sensor's page.

Note: If you need to temporarily disconnect the tag connector of the blade extension strip, wait at least 1 second before connecting it back, or the Dominion PX may not detect it.

To expand a blade extension strip folder:

1. Click the desired asset sensor in the left pane. The selected asset sensor's page opens in the right pane.
2. Locate the rack unit (tag port) where the blade extension strip is connected.

Rack Units Rack Unit Index Slot Name Asset / ID 1 1 2 2 00000007CACB 3 3 4 4

1. Double-click that rack unit or click the white arrow prior to the folder icon. The arrow then turns into a black, gradient arrow and all tag ports appear below the folder.

Rack Units
	Rack Unit	Index	Slot	Name	Asset / ID
III	1	1
✓	2	2			00000007CACB
III			1
III			2
III			3
III			4
III			5
III			6
III			7
III			8
III			9
III			10
III			11
III			12
III			13
III			14
III			15
III			16
III	3	3
III	4	4

▶ To collapse a blade extension strip:

- Double-click the blade extension strip folder, or click the black, gradient arrow ▲prior to the folder icon. All tag ports under the folder are hidden.

Displaying the Asset Sensor Information

The hardware and software information of the connected asset sensor is available through the web interface.

▶ To display the asset sensor information:

1. Connect the asset sensor to the Dominion PX if it is not already. See Connecting Asset Sensors to the Dominion PX (on page 41).

2. Click on the Feature Ports folder in the navigation tree to expand it.

3. Click the desired asset sensor. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports).

Note: You can also access this dialog by double-clicking the asset sensor shown on the Dashboard page.

1. Click Extended Device Info, where the asset sensor data is displayed.
2. Click Close to quit the dialog.

Copying Configurations with Bulk Configuration

The Bulk Configuration feature lets you save the settings of a configured Dominion PX device to your PC. You can use this configuration file to:

• Copy that configuration to other Dominion PX devices of the same model and firmware version.
• Restore the settings of the same Dominion PX device to previous configuration.

You must have the administrator privileges to save and copy the Dominion PX configurations.

Bulk Configuration Save Bulk Configuration Download Bulk Configuration Copy Bulk Configuration Bulk Configuration File: Browse... Upload & Restore Bulk Configuration Close

Saving a Dominion PX Configuration

A source device is an already configured Dominion PX device that is used to create a configuration file containing the settings that can be shared between Dominion PX devices. These settings include user and role configurations, thresholds, event rules, security settings, and so on.

This file does NOT contain device-specific information, including:

• Device name
  • System name, system contact and system location
  • Network settings (IP address, gateway, netmask and so on)
• Device logs
• Outlet names
• Outlet status
  • Environmental sensor names
  • Environmental sensor states and values
• SSL certificate

Because the date and time settings are saved in the configuration file, users should exercise caution when distributing the configuration file to the Dominion PX devices in a different time zone than the source device.

To save a configuration file:

1. Choose Maintenance > Bulk Configuration. The Bulk Configuration dialog appears.
2. Click Download Bulk Configuration.
3. When the web browser prompts you to open or save the configuration file, click Save. Choose a suitable location and save the configuration file to your PC.

The file is saved in the XML format, and its content is encrypted using the AES-128 encryption algorithm.

Copying a Dominion PX Configuration

A target device is an Dominion PX device that loads another Dominion PX device's configuration file.

Copying an Dominion PX configuration to a target device adjusts that Dominion PX device's settings to match those of the source Dominion PX device. In order to successfully copy an Dominion PX configuration:

• The user must be the Admin user. Or the Admin role is assigned to the user.
• The target Dominion PX device must be of the same model type as the source Dominion PX device.
• The target Dominion PX device must be running the same firmware version as the source Dominion PX device.

To copy a Dominion PX Configuration:

1. Log in to the target device's web interface.
2. If the target device's firmware version does not match that of the source device, update the target's firmware. See Firmware Upgrade (on page 219).
3. Cho ose Maintenance > Bulk Configuration. The Bulk Configuration dialog appears.
4. In the Copy Bulk Configuration section, click Browse and select the configuration file stored on your PC.
5. Click Upload & Restore Bulk Configuration to copy the file.
6. A message appears, prompting you to confirm the operation. Click Yes to confirm the operation.
7. Wait until the Dominion PX device resets and the Login page re-appears, indicating that the configuration copy is complete.

Changing the Measurement Units

By default, the following measurement units are applied to all data shown in the Dominion PX web interface:

• Temperature: degrees in Celsius (°C)
  ■ Length or height: meters (m)
  ■ Air pressure: pascal (pa)

The Dominion PX web interface allows shows different measurement units based on user login name. That is, different users may see different measurement units displayed according to their preferences. The other alternatives for each measurement unit include:

- Temperature: degrees in Fahrenheit (°F)

■ Length or height: feet (ft)
■ Air pressure: psi

Determine the desired measurement unit when creating user profiles. See Creating a User Profile (on page 102). To change the measurement unit setting, you must have the administrator privileges.

To set the preferred measurement units:

1. Choose User Management > Users. The Manage Users dialog appears.
2. Select the user by clicking it.
3. Click Edit or double-click the user. The Edit User 'XXX' dialog appears, where XXX is the user name.
4. Click the Preferences tab.
5. To change the temperature unit, select the desired option in the Temperature Unit field.

- °C: This option displays the temperature in Celsius.

- °F: This option displays the temperature in Fahrenheit.

1. To change the length or height unit, select the desired option in the Length Unit field.

2. Meter: This option displays the length or height in meters.

3. Feet: This option displays the length or height in feet.

4. To change the pressure unit, select the desired option in the Pressure Unit field.

5. Pascal: This option displays the pressure value in Pascals (Pa). A Pascal is equal to one newton per square meter.

6. psi: This option displays the pressure value in psi. Psi stands for pounds per square inch.

7. Click OK to save the changes.

Managing the Webcam Images or Videos

If you connect a Logitech ^® QuickCam ^® Pro 9000 Webcam to the Dominion PX device, you can visually monitor the environment close to the Dominion PX. See Connecting a Logitech Webcam (Optional) (on page 48).

Snapshots or videos captured by the webcam are displayed in the right pane of Dominion PX web interface once a webcam is selected in the tree. Snapshots and videos can also be displayed in a separate browser

window by clicking on the Live Preview icon

You can manually store snapshots taken from the webcam in the web interface. See Saving Snapshots (on page 209).

Links to video being captured by a webcam can be sent via email or instant message. See Sending Snapshots or Videos in an Email or Instant Message (on page 207).

Events that trigger emails containing snapshots from a webcam can be created. See Creating Actions (on page 156).

Configuring Webcams

Before you can configure a webcam, it must be connected to the Dominion PX. See Connecting a Logitech Webcam (Optional) (on page 48).

▶ To configure a webcam:

1. In the navigation tree, click on the Webcam Management folder. The Webcam Management page opens.
2. Click on the webcam you want to configure and then click Setup at the bottom right of page. The Webcam Setup dialog opens.
3. Enter a name for the webcam. Up to 64 characters are supported.
4. Select a resolution for the webcam.
5. Select the webcam mode. This can be changed as needed once the webcam is configured.
   a. Video - the webcam is in video mode. Set the Framerate (frames per second) rate.
   b. Snapshot - the webcam displays images from the webcam. Set the Time Between Image(s) rate as measured in seconds.
6. Click OK. The image or video from the webcam is now available in the Dominion PX once you click on the webcam in the navigation tree.

To edit a webcam configuration:

1. In the navigation tree, click on the Webcam Management folder. The Webcam Management page opens.

2. Double-click on the webcam you want to edit. The webcam image or video opens in a new tab.

3. Click Setup.
4. Edit the information as needed. Changes to the resolution do not apply to existing, stored images - it applies only to images and videos taken after the resolution is changed.
5. Click OK.

Adjusting Image or Video Properties

If any image or video properties, such as the brightness, contrast, saturation, and gain settings, do not satisfy your needs, adjust them in the Webcam Setup dialog.

To adjust the image or video properties:

1. Click on the webcam on the Webcam Management page or in the navigation tree. See Configuring Webcams (on page 205).
2. Click Setup. The Webcam Setup dialog appears.
3. Click the Controls tab.
4. Adjust the desired property by adjusting the corresponding slide bar.
5. Click OK to save the changes.

Viewing the Webcam Images or Videos

If you connect a Logitech ^® QuickCam ^® Pro 9000 Webcam to the Dominion PX device, you can visually monitor the environment close to the Dominion PX. See Connecting a Logitech Webcam (Optional) (on page 48).

The Dominion PX allows you to switch between static images or live videos captured by the webcam.

To view the snapshots or videos:

1. Click the Webcam icon in the left pane.

Note: A Webcam icon appears only when a Logitech ^® QuickCam ^® Pro 9000 Webcam is connected to the Dominion PX. See Connecting a Logitech Webcam (Optional) (on page 48).

1. By default the Dominion PX enters the snapshot mode. Wait around one minute for a snapshot to appear. In the snapshot mode, a snapshot mode icon 📄 appears on the top-left corner of the image. The location of the webcam is displayed in the Location pane below the image.

2. To change the image resolution, click Setup. Select a different resolution from the Resolution drop-down list. The image is updated with the latest snapshot while the resolution changes.

3. To take a snapshot of the image, click the Store Snapshot to Webcam Storage icon 📋. See Saving Snapshots (on page 209).

If the current mode is video, to return to the snapshot mode:

a. Click Setup.
b. In the Webcam Mode field, select Snapshot.

1. To switch to the video mode:

a. Click Setup.
b. In the Webcam Mode field, select Video.

In the video mode, a video mode icon ▶ appears on the top-left corner of the image.

- To change the video resolution, click Setup and select a different resolution from the Resolution drop-down list.

Sending Snapshots or Videos in an Email or Instant Message

You are able to email or instant message up to two (2) recipients a link to webcams attached to the Dominion PX. Users can then click on the links and view snapshots or videos.

Note: For remote Live Preview sessions, such as those accessed via link in an email or instant message, a total of up to three (3) simultaneous Live Preview sessions are supported at a time. One (1) from the originator in the Dominion PX interface, and up to two (2) remote sessions.

Note: For the purposes of this topic, the message sender is User A and the recipient is User B.

The recipient is able to access the snapshot or video image via the link so long as either:

- The snapshot or video remains open in Live Preview mode in the User A's Dominion PX interface, and User A does not log out of the interface and the session does not time out.

Or

- The snapshot or video remains open in a secondary Live Preview window in the User A's Dominion PX interface. So long as the secondary Live Preview window is open in User A's interface, even after User A logs out of the Dominion PX interface or the session times out, the link is available.

Best Practice

As a best practice, in the Dominion PX interface, User A should open the snapshot or video in a secondary Live Preview window and leave the Live Preview window open at least until User B opens the snapshot or video via the link.

Once User B opens the snapshot or video via the link, the secondary Live Preview mode window can be closed in the User A's Dominion PX interface.

User B can either manually let User A know they have opened the link, or User A can check to see if User B is currently connected to the application by choosing Maintenance > Connected Users.

To send a snapshot or video link via email or instant message:

1. In the navigation tree, click on the webcam that is capturing the snapshot or video you want to provide a link to in the email. The snapshot or video is displayed in Live Preview mode in the right pane.
2. Click on the Live Preview icon located above the snapshot or video. The snapshot or video opens in a secondary Live Preview window.
3. Copy the URL from the Live Preview window, paste it into the email or instant message application. Leave the Live Preview window open at least until the recipient opens the snapshot or video via the link.

Snapshot Storage

The Dominion PX provides a mechanism for storing a history of selected snapshots. All stored snapshots are saved as JPEG-formatted files on the Dominion PX, with the filename, file size, save date and time displayed.

Warning: The stored snapshots are lost when you reset the Dominion PX so make sure it is fine to clear up the snapshot history before performing the reset.

Saving Snapshots

If it is intended to keep the currently-displayed webcam snapshot, you can manually save it onto the Dominion PX.

Warning: The stored snapshots are lost when you reset the Dominion PX so make sure it is fine to clear up the snapshot history before performing the reset.

To save the current snapshot:

1. Click on the webcam icon in the tree, or double-click on the webcam listed on the Webcam Management page to open the Webcam page.
2. Click the Save icon above the snapshot. The currently-displayed snapshot is immediately saved to a JPEG-formatted file and stored in the Snapshots icon.

Note: If the current mode is the Video mode, the Save icon is not available. See Viewing the Webcam Images or Videos (on page 206).

1. Click on the Snapshots icon in the tree to verify the selected snapshot is successfully saved and listed on the Snapshots page.

Managing the Snapshot History

All saved snapshots are listed and displayed on the Snapshots page.

The Snapshots page is divided into three panes: Storage, Snapshot and Details. On the top of the Storage pane, it indicates the summary storage information, which shows the total number of snapshots (Used) and the maximum number of snapshots allowed (Size) in storage.

To manage the snapshot history:

1. To view any snapshot, click on it in the list of the Storage pane. The selected snapshot image is shown in the Snapshot pane.
2. To change the sorting of the Storage list or the displayed columns, see Changing the View of a List (on page 78).
3. To re move one or multiple snapshots from the storage, select them by clicking on the corresponding checkboxes, and click the Remove icon
4. To select or deselect all snapshots in the list, simply select or deselect the checkbox in the header row.

Network Diagnostics

The Dominion PX provides the following tools in the web interface for diagnosing potential networking issues.

• Ping
• Trace Route
• List TCP Connections

Tip: These network diagnostic tools are also available through CLI. See Network Troubleshooting (on page 380).

Pinging a Host

The Ping tool is useful for checking whether a host is accessible through the network or Internet.

To ping a host:

1. Choose Maintenance > Network Diagnostics > Ping. The Ping Network Host dialog appears.
2. In the Host Name field, type the name or IP address of the host that you want to check.
3. In the Number of Requests field, type a number up to 10 or adjust the value by clicking either arrow. This number determines how many packets are sent for pinging the host.
4. Click Run Ping to start pinging the host. A dialog appears, displaying the Ping results.
5. Click Close to quit the dialog.

Tracing the Network Route

Trace Route lets you find out the route over the network between two hosts or systems.

To trace the route for a host:

1. Choose Maintenance > Network Diagnostics > Trace Route. The Trace Route to Host dialog appears.
2. Type the IP address or name of the host whose route you want to check in the Host Name field.
3. Click Run. A dialog appears, displaying the Trace Route results.
4. Click Close to quit the dialog.

Listing TCP Connections

You can use the "List TCP Connections" to display a list of TCP connections.

To trace the route for a host:

1. Choose Maintenance > Network Diagnostics > List TCP Connections. The TCP connections dialog appears.
2. Click Close to quit the dialog.

Viewing the Communication Log

The Dominion PX allows you to inspect all communications occurred between the Dominion PX device and its graphical user interface (GUI). The information is usually useful for a technical support engineer only and you may not need to view it.

This feature is accessible only by users with Administrative Privileges.

▶ To view the communication log:

1. Choose Maintenance > View Communication Log. The Communication Log dialog appears.

2. The dialog shows the final page by default. You can:

3. Switch between different pages by doing one of the following:

4. Click ↩ or ▶ to go to the first or final page.
5. Click ◀ or ▶ to go to the prior or next page.
6. Type a number in the Page text box and press Enter to go to a specific page.
7. Select a log entry from the list and click Show Details, or simply double-click the log entry to view detailed information.

Note: Sometimes when the dialog is too narrow, the icon >> takes the place of the Show Details button. In that case, click >> and select Show Details to view details.

1. To immediately update the communication log, click

1. To save the communication log on your computer, click

1. Enlarge the dialog if necessary.

2. You can re-sort the list or change the columns displayed.

3. Click Close to quit the dialog.

Downloading Diagnostic Information

Important: This function is for use by Raritan Field Engineers or when you are directed by Raritan Technical Support.

You can download the diagnostic file from the Dominion PX device to a client machine. The file is compressed into a .tgz file and should be sent to Raritan Technical Support for interpretation.

This feature is accessible only by users with Administrative Privileges.

▶ To retrieve a diagnostic file:

1. Choose Maintenance > Download Diagnostic Information. The File Download dialog appears.

File Download Do you want to open or save this file? Name: diag-data.tgz Type: WinRAR archive From: 192.168.84.57 Open Save Cancel While files from the Internet can be useful, some files can potentially harm your computer. If you do not trust the source, do not open or save this file. What's the risk?

1. Click Save. The Save As dialog appears.
2. Navigate to the desired directory and click Save.
3. E-mail this file as instructed by Raritan Technical Support.

Managing the Schroff LHX Heat Exchanger

The Dominion PX supports monitoring and administering the Schroff® LHX-20 or LHX-40 heat exchanger if this device is connected to the Dominion PX.

To monitor one LHX heat exchanger using the Dominion PX:

1. Physically connect an LHX-20 or LHX-40 heat exchanger to the Dominion PX device if it is not already connected. See Connecting a Schroff LHX Heat Exchanger (Optional) (on page 49).

2. Enable the support of LHX heat exchanger on the Dominion PX. See Enabling the LHX Support (on page 213).

3. Configure the connected heat exchanger. See Configuring the LHX Device (on page 213).
4. No w you can remotely monitor or control the connected LHX heat exchanger via the Dominion PX.

- To monitor the heat exchanger, see Monitoring the LHX Device (on page 215).

- To control the heat exchanger, see Controlling the LHX Device (on page 218).

Enabling the LHX Support

By default, the Dominion PX disables the support of the LHX heat exchanger so you must enable the LHX support to remotely monitor or control the connected LHX heat exchanger.

Note that enabling or disabling the LHX support requires the restart of the Dominion PX device for the changes to take effect.

To enable or disable the LHX support:

1. Choose Device Settings > Features to select or deselect the Schroff LHX Support checkbox.
2. Click Yes to confirm.
3. A message appears, indicating that the Dominion PX will restart. Click Continue to reboot the device.
4. A countdown timer dialog appears. Wait until the Dominion PX completes the reboot, and then you are redirected to the login page. If you are not redirected to the login page after tens of seconds, click "this link" in the dialog.

Configuring the LHX Device

After enabling the LHX support on the Dominion PX, the Dominion PX should automatically detect the connected LHX device and display it under the Feature Port folder unless the Feature Port is set to a mode different than the Auto mode. If so, change the Feature Port mode so that the LHX device is correctly displayed in the web interface. See Configuring the Feature Port (on page 97).

Besides, the Dominion PX allows you to set temperature or fan speed thresholds for alerts or to customize the name of the LHX device for easy identification.

Correctly Displaying the LHX Device

There are two ways to have the Dominion PX show the correct LHX model in the web interface.

• Auto detection: Set the mode of the Feature Port to Auto to let the Dominion PX automatically detects the device type.
• Manual assignment: Set the mode of the Feature Port to either LHX-20 or LHX-40, depending on which LHX model is physically connected to the Dominion PX.

For details on how to change the Feature Port mode, see Configuring the Feature Port (on page 97).

After the correct LHX device type is detected or assigned, the LHX icon

appears below the Feature Port folder.

Note that the device icon changes its image when the device changes its states. See Device States and Icon Variations (on page 218) for details.

Naming the LHX Device

To help identify an LHX heat exchanger in the Dominion PX web interface, assign a name to it. The customized LHX heat exchanger's name is followed by the Feature Port number in parentheses.

To name a heat exchanger:

1. If the Feature Port folder is not expanded, expand it to show the device under the Feature Port folder. See Expanding the Tree (on page 71).
2. Click the LHX heat exchanger in the Dominion PX Explorer pane. The page specific to that device opens in the right pane.
3. Click Setup in the Settings section. A setup dialog appears.
4. Type a name for the heat exchanger in the Name field.
5. Click OK to save the changes.

Configuring Temperature and Fan Thresholds

An LHX heat exchanger is implemented with various sensors for detecting the air temperature, water temperature, and fan speed. You can set thresholds for these sensors so that the Dominion PX alerts you when any sensor readings are getting close to a critical condition. These settings are stored on the Dominion PX port where the heat exchanger is connected, and are lost if that heat exchanger is moved to a different port.

To configure the thresholds for a sensor:

1. Connect the LHX heat exchanger to Dominion PX if it is not already connected.
2. If the Feature Port folder is not expanded, expand it to show the device under the Feature Port folder. See Expanding the Tree (on page 71).
3. Click the LHX heat exchanger in the Dominion PX Explorer pane. The page specific to that device opens in the right pane.
4. Select the desired sensor in the Sensors table and click Setup Thresholds, or simply double-click that sensor. The setup dialog for the selected sensor appears.
5. Adjust the threshold and deassertion hysteresis settings. The Upper Critical and Lower Critical values are points at which the Dominion PX considers the operating environment critical and outside the range of the acceptable threshold.
6. To enable any threshold, select the corresponding checkbox. To disable a threshold, deselect the checkbox.
   ■ After any threshold is enabled, type an appropriate numeric value in the accompanying text box.

7. To enable the deassertion hysteresis for all thresholds, type a numeric value other than zero in the Deassertion Hysteresis field. See What is Deassertion Hysteresis? (on page 153).

8. Click OK to save the changes.

Monitoring the LHX Device

The Dominion PX web interface lets you monitor the status of the connected LHX heat exchanger as well as the status of the LHX built-in sensor.

Viewing the Summary

Both the Dashboard and Feature Port page display the summary of the connected LHX heat exchangers, including the heat exchanger's name and status, if the LHX device is detected or manually assigned to the Feature Port.

If the LHX heat exchanger is highlighted in red in the summary, it indicates that there is LHX sensor failure on that heat exchanger. View the State column to identify failed sensors.

To view the LHX summary on the Dashboard page:

1. Click the Dashboard icon in the Dominion PX Explorer pane. The Dashboard page opens in the right pane.

2. Locate the LHX Heat Exchanger section.

To view the LHX summary on the Feature Port page:

1. If the PDU folder is not expanded, expand it to show all components and component groups. See Expanding the Tree (on page 71).

Note: The PDU folder is named "my PX" by default. The name changes after customizing the device name. See Naming the PDU (on page 83).

1. Click the Feature Port folder. The Feature Port page opens in the right pane, showing the connected LHX device information.

Viewing Details

An LHX heat exchanger page shows detailed information, including:

• Device information and settings
• The air outlet temperature
- Readings and states of all LHX built-in sensors
• Accumulative operating hours
- Errors, such as failed LHX sensors or emergency cooling activation

To view details of a specific LHX heat exchanger:

1. If the Feature Port folder is not expanded, expand it to show the device under the Feature Port folder. See Expanding the Tree (on page 71).
2. Click the LHX icon in the left pane. The LHX page opens in the right pane.

Tip: The same LHX page can be also opened by clicking Feature Port in the left pane, and then double-clicking the LHX in the right pane.

If any LHX sensor reading reaches or crosses the critical or warning threshold, that sensor reading row is highlighted in red or yellow. See The Yellow- or Red-Highlighted Reading (on page 76).

Alert States and LHX Event Log

When an LHX heat exchanger is physically connected to the Dominion PX device, a section labeled Alert States appears on its device page. The Alert States section shows information identifying the LHX sensors that currently fail.

Tip: The Dashboard and Feature Port pages also point out failed sensors. See Monitoring the LHX Device (on page 215).

A button labeled Show Event Log is located in the Alert States section. To view the events associated with the Dominion PX, click this button.

Operating Hours

Operating hours are the accumulative time since the LHX heat exchanger is first connected to the Dominion PX device and turned ON.

The Dominion PX web interface displays the operating hours both for the heat exchanger and its fans. Operating hour information is located in the Statistics section of each heat exchanger page.

Operating Hours (Varistar LHX):	41 d 16 h
Operating Hours (Fan M1):	0 h
Operating Hours (Fan M2):	4 d 4 h
Operating Hours (Fan M3):	8 d 8 h
Operating Hours (Fan M4):	12 d 12 h
Operating Hours (Fan M5):	16 d 16 h
Operating Hours (Fan M6):	20 d 20 h
Operating Hours (Fan M7):	25 d

Below are the time units used for operating hours:

• h: hour(s)
• d: day(s)

For example, "3d 5h" means the total operating time is 3 days and 5 hours.

Device States and Icon Variations

The Dominion PX web interface changes icons to represent different statuses of the connected LHX heat exchanger.

Icons Device status
	The heat exchanger is turned ON and operating normally.
	The heat exchanger is turned OFF.
	The heat exchanger is turned ON but enters the critical state because of any LHX sensor failure.
	At least one of the LHX sensor readings has crossed the upper or lower warning threshold.
	NO LHX device is detected on the FEATURE port.

To identify the cause of the critical state, view one of the following.

• The LHX Heat Exchanger section of the Dashboard page.
• The Feature Port page.

For details, see Viewing the Summary (on page 216).

Controlling the LHX Device

The Dominion PX allows you to remotely turn on or off a connected heat exchanger.

To control the LHX heat exchanger:

1. If the Feature Port folder is not expanded, expand it to show the device under the Feature Port folder. See Expanding the Tree (on page 71).

2. Click the LHX heat exchanger in the Dominion PX Explorer pane. The page specific to that device opens in the right pane.

3. Locate the Information section.

4. To turn off the LHX heat exchanger, click Switch Off.

5. To turn on the LHX heat exchanger, click Switch On.

6. If you clicked Switch Off in the previous step, a dialog appears, prompting you to confirm the operation. Click Yes to turn it off or No to abort the operation.

The heat exchanger's icon shown in the web interface changes after being turned on or off. See Device States and Icon Variations (on page 218).

Firmware Upgrade

You may upgrade your Dominion PX device to benefit from the latest enhancements, improvements and features.

The Dominion PX firmware files are available on the Raritan website's Firmware and Documentation section (http://www.raritan.com/support/firmware-and-documentation/).

Updating the Dominion PX Firmware

You must be the system administrator or log in to the user profile with the Firmware Update permission to update the Dominion PX device's firmware.

If applicable to your model, download the latest firmware file from the Raritan website, read the release notes, then start the upgrade. If you have any questions or concerns about the upgrade, contact Raritan Technical Support BEFORE upgrading.

Warning: Do NOT perform the firmware upgrade over a wireless connection.

▶ To update the firmware:

1. Choose Maintenance > Update Firmware. The Firmware Update dialog appears.
2. In the Firmware File field, click Browse to select an appropriate firmware file.
3. Click Upload. A progress bar appears to indicate the upload status.
4. When the upload is complete, version information of both the existing firmware and uploaded firmware is shown, providing you a last chance to terminate the update.
5. To view the certificate of the uploaded firmware, click View Certificate. Optional.
6. To proceed with the update, click Update Firmware. The update may take several minutes.

Warning: Do NOT power off the Dominion PX device during the update.

During the firmware update:

• A progress bar appears in the web interface, indicating the update status.
• On the Dominion PX device, the three-digit LED display shows "FUP."

• No users can successfully log in to the Dominion PX.

• In the web interface, all logged-in users see the Dominion PX time out message, and the "disconnected" state is shown in the status bar.

• The user management operation, if any, is forced to suspend.

• When the update is complete, a message appears, indicating the update is successful.

• The Dominion PX device resets, and the Login page re-appears. You can now log in and resume your operation.

Note 1: The other logged-in users are also logged out when the firmware update is complete.

Note 2: If you are using the Dominion PX with an SNMP manager, you should re-download the Dominion PX MIB after the firmware update. This ensures your SNMP manager has the correct MIB for the latest release you are using. See Using SNMP (on page 224).

A Note about Firmware Upgrade Time

The 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 at which 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 when required. 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 web-interface-based upgrades. Upgrades through other management systems, such as Raritan's Power IQ, may take additional time beyond the control of the PDU itself. This note does not address the upgrades using other management systems.

Viewing Firmware Update History

The firmware upgrade history, if available, is permanently stored on the Dominion PX device.

This history indicates when a firmware upgrade event occurred, the prior and new versions associated with the firmware upgrade event, and the upgrade result.

To view the firmware update history:

1. Choose Maintenance > View Firmware Update History. The Firmware Update History dialog appears, with the following information displayed.

2. Date and time of the firmware upgrade event
   ■ Previous firmware version
   ■ Update firmware version
   ■ Firmware upgrade result

3. You may change the number of displayed columns or re-sort the list for better viewing the data. See Changing the View of a List (on page 78).

4. To view the details of any firmware upgrade event, select it and click Details, or simply double-click the event. The Firmware Update Details dialog appears, showing detailed information of the selected event.
5. Click Close to quit the dialog.

Full Disaster Recovery

If the firmware upgrade fails, causing the Dominion PX device to stop working, you can recover it by using a special utility rather than returning the device to Raritan.

Contact Raritan Technical Support for the recovery utility, which works in Windows XP/Vista/7 and Linux. In addition, an appropriate Dominion PX firmware file is required in the recovery procedure.

Updating the Asset Sensor Firmware

After connecting the asset sensor to the Dominion PX device, it automatically checks its own firmware version against the version of the asset sensor firmware stored in the Dominion PX firmware. If two versions are different, the asset sensor automatically starts downloading the new firmware from the Dominion PX device to upgrade its own firmware.

During the firmware upgrade, the following events take place:

• The asset sensor is completely lit up, with the blinking LEDs changing the color from red to green.
• A firmware upgrade process is indicated in the Dominion PX web interface.
  • An SNMP trap is sent to indicate the firmware upgrade event.

Accessing the Help

The Help menu provides:

• Current firmware and software packages information
  • A link to the Dominion PX User Guide (that is, the online help)

Retrieving Software Packages Information

You can check the current firmware version and the information of all open source packages embedded in the Dominion PX device through the web interface.

To retrieve the embedded software packages information:

1. Choose Help > About Dominion PX. The About Dominion PX dialog appears, with a list of open source packages displayed.
2. You can click any link in the dialog to access related information or download any software package.

Browsing through the Online Help

The Dominion PX User Guide is also provided in the form of online help, and accessible over the Internet.

To use online help, Active Content must be enabled in your browser. If you are using Internet Explorer 7, you must enable Scriptlets. Consult your browser help for information on enabling these features.

To use the Dominion PX online help:

1. Choose Help > User Guide. The online help opens in the default web browser.

2. To view the content of any topic, click the topic in the left pane. Then its content is displayed in the right pane.

3. To select a different topic, do any of the following:

4. To view the next topic, click the Next icon ⬆ in the toolbar.

5. To view the previous topic, click the Previous icon

6. To view the first topic, click the Home icon

7. To expand or collapse a topic that contains sub-topics, do the following:

8. To expand any topic, click the white arrow prior to the topic, or double-click that topic. The arrow turns into a black, gradient arrow and sub-topics appear below the topic.

9. To collapse any expanded topic, click the black, gradient arrow prior to the topic, or double-click the expanded topic. The arrow then turns into a white arrow D, and all sub-topics below that topic disappear.

10. To search for specific information, type the key word(s) or string(s) in the Search text box, and press Enter or click the Search icon 🔗 to start the search.

- If necessary, select the "Match partial words" checkbox to include information matching part of the words entered in the Search text box.

The search results are displayed in the left pane.

1. To have the left pane show the list of topics, click the Contents tab at the bottom.
2. To show the Index page, click the Index tab.
3. To email any URL link to the currently selected topic to any person, click the "Email this page" icon 📋 in the toolbar.
4. To email your comments or suggestions regarding the user guide to Raritan, click the "Send feedback" icon 🔒.
5. To print the currently selected topic, click the "Print this page" icon 📄.

Chapter 6 Using SNMP

This SNMP section helps you set up the Dominion PX for use with an SNMP manager. The Dominion PX can be configured to send traps 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 SNMP ....224 Configuring Users for Encrypted SNMP v3....225 Configuring SNMP Traps....226 SNMP Gets and Sets ....227

Enabling SNMP

To communicate with an SNMP manager, you must first enable the SNMP agent on the Dominion PX device.

To enable SNMP:

1. Choose Device Settings > Network Services > SNMP. The SNMP Settings dialog appears.

SNMP Settings General Traps SNMP v1 / v2c Settings SNMP v1 / v2c: enable Read Community String: public Write Community String: private SNMP v3 Settings SNMP v3: enable MIB-II System Group sysContact: sysName: sysLocation: Download MIB • OK Cancel

1. Select the "enable" checkbox in the "SNMP v1 / v2c" field to enable communication with an SNMP manager using SNMP v1 or v2c protocol.

- Type the SNMP read-only community string in the Read Community String field. Usually the string is "public."

- Type the read/write community string in the Write Community String field. Usually the string is "private."

1. Select the "enable" checkbox in the "SNMP v3" field to enable communication with an SNMP manager using SNMP v3 protocol.

Tip: You can permit or disallow a user to access the Dominion PX via the SNMP v3 protocol. See Configuring Users for Encrypted SNMP v3 (on page 225).

1. Type the SNMP MIB-II sysContact value in the sysContact field.
2. Type the SNMP MIB-II sysName value in the sysName field.
3. Type the SNMP MIB-II sysLocation value in the sysLocation field.
4. Click OK to save the changes.

Important: You must download the SNMP MIB for your Dominion PX to use with your SNMP manager. Click Download MIB in this dialog to download the desired MIB file. For more details, see Downloading SNMP MIB (on page 227).

Configuring Users for Encrypted SNMP v3

The SNMP v3 protocol allows for encrypted communication. To take advantage of this, users need to have an Authentication Pass Phrase and Privacy Pass Phrase, which act as shared secrets between them and the Dominion PX.

To configure users for SNMP v3 encrypted communication:

1. Choose User Management > Users. The Manage Users dialog appears.
2. Select the user by clicking it.
3. Click Edit or double-click the user. The Edit User 'XXX' dialog appears, where XXX is the user name.
4. To change the SNMPv3 access permissions, click the SNMPv3 tab and make necessary changes. For details, see Step 6 of Creating a User Profile (on page 102).
5. Click OK to save the changes. The user is now set up for encrypted SNMP v3 communication.

Configuring SNMP Traps

The Dominion PX automatically keeps an internal log of events that occur. See Configuring Event Rules (on page 155). These events can also be used to send SNMP traps to a third party manager.

To configure the Dominion PX to send SNMP traps:

1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears.
2. On the Rules tab, select the System SNMP Trap Rule.
3. Select the Enabled checkbox to enable this event rule.
4. Click Save to save the changes.
5. Click the Actions tab if you have not configured the SNMP trap actions.
6. Select System SNMP Trap Action to set up the trap destinations.
7. Type an IP address in the Host 1 field. This is the address to which traps are sent by the SNMP system agent.
8. Type the communication port number in the Port 1 field.
9. Type the name of the SNMP community in the Community field. The community is the group representing the Dominion PX and all SNMP management stations.
10. To specify more than one SNMP trap destination, repeat Steps 8 to 10 for additional destinations. A maximum of 3 destinations can be specified.
11. Click Save to save the changes.
12. Click Close to quit the dialog.

Note: You should update the MIB used by your SNMP manager when updating to a new Dominion PX release. This ensures your SNMP manager has the correct MIB for the release you are using. See Downloading SNMP MIB (on page 227).

SNMP Gets and Sets

In addition to sending traps, the Dominion PX is able to receive SNMP get and set requests from third-party SNMP managers.

• Get requests are used to retrieve information about the Dominion PX, 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 Dominion PX device name. When you change the SNMP system name, the device name shown in the web interface is also changed.

The Dominion PX 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 the custom Dominion PX MIB.

The Dominion PX MIB

The SNMP MIB file is required for using your Dominion PX device with an SNMP manager. An SNMP MIB file describes the SNMP functions.

Downloading SNMP MIB

The SNMP MIB file for the Dominion PX can be easily downloaded from the web interface. There are two ways to download the SNMP MIB file.

To download the file from the SNMP Settings dialog:

1. Choose Device Settings > Network Services > SNMP. The SNMP Settings dialog appears.
2. Click Download MIB. A submenu of MIB files appear.
3. Select the desired MIB file to download.

■ PDU2-MIB: The SNMP MIB file for Dominion PX's power management.
- ASSETMANAGEMENT-MIB: The SNMP MIB file for asset management.

1. Click Save to save the file onto your computer.

To download the file from the Device Information dialog:

1. Choose Maintenance > Device Information. The Device Information dialog appears.
2. Click the PDU2-MIB or ASSETMANAGEMENT-MIB link to download the desired SNMP MIB file.

■ PDU2-MIB: The SNMP MIB file for Dominion PX's power management.
- ASSETMANAGEMENT-MIB: The SNMP MIB file for asset management.

The "USB Console INF file" link lets you download the USB-to-serial driver that may be required only when the PDU is connected to a computer via an USB cable for configuration. See Installing the USB-to-Serial Driver (on page 20) for details.

1. Click Save to save the file onto your computer.

Layout

Opening the MIB reveals the custom objects that describe the Dominion PX system at the unit level as well 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.

measurementsGroup OBJECT-GROUP OBJECTS { measurementsUnitSensorIsAvailable, measurementsUnitSensorState, measurementsUnitSensorValue, measurementsUnitSensorTimeStamp, measurementsInletSensorIsAvailable, measurementsInletSensorState, measurementsInletSensorValue, measurementsInletSensorTimeStamp, measurementsInletPoleSensorIsAvailable, measurementsInletPoleSensorState, measurementsInletPoleSensorValue, measurementsInletPoleSensorTimeStamp, measurementsOutletSensorIsAvailable, measurementsOutletSensorState, measurementsOutletSensorValue, measurementsOutletSensorTimeStamp, measurementsOutletPoleSensorIsAvailable, measurementsOutletPoleSensorState, measurementsOutletPoleSensorValue, measurementsOutletPoleSensorTimeStamp, measurementsOverCurrentProtectorSensorIsAvailable, measurementsOverCurrentProtectorSensorState, measurementsOverCurrentProtectorSensorValue, measurementsOverCurrentProtectorSensorTimeStamp, measurementsExternalSensorIsAvailable, measurementsExternalSensorState, measurementsExternalSensorValue, measurementsExternalSensorTimeStamp STATUS current DESCRIPTION "A collection of objects providing the logging capabilities about the pdu."

For example, the measurementsGroup group contains objects for sensor readings of Dominion PX as a whole. 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 can be configured have a MAX-ACCESS level of "read-write" in the MIB.

These objects include threshold objects, which causes the Dominion PX to generate a warning and send an SNMP trap when certain parameters are exceeded. See Setting Power Thresholds (on page 150) for a description of how thresholds work.

Note: When configuring the thresholds via SNMP set commands, ensure the value of upper critical threshold is higher than that of upper warning threshold.

A Note about Enabling Thresholds

When enabling previously disabled thresholds via SNMP, make sure you set a correct value for all thresholds that are supposed to be enabled prior to actually enabling them. Otherwise, you may get an error message.

Chapter 7 Using the Command Line Interface

This section explains how to use the command line interface (CLI) to administer a Dominion PX device.

In This Chapter

About the Interface 230

Logging in to CLI 230

Help Command....233

Showing Information....234

Configuring the Dominion PX Device and Network....253

Load Shedding Configuration Commands ....374

Power Control Operations 375

Unblocking a User 379

Resetting the Dominion PX 379

Network Troubleshooting....380

Querying Available Parameters for a Command....385

Retrieving Previous Commands....385

Automatically Completing a Command ....385

Logging out of CLI 386

About the Interface

The Dominion PX provides a command line interface that enables data center administrators to perform some basic management tasks.

Using this interface, you can do the following:

• Reset the Dominion PX device
• Display the Dominion PX and network information, such as the device name, firmware version, IP address, and so on
• Configure the Dominion PX and network settings
• Troubleshoot network problems

You can access the interface over a serial 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 because it communicates openly and is thus insecure. To enable Telnet, see Modifying the Network Service Settings (on page 90).

Logging in to CLI

Logging in via HyperTerminal over a local connection is a little different than logging in using SSH or Telnet.

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.

To log in using HyperTerminal:

1. Connect your computer to the Dominion PX device 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 find out which COM port is assigned to the Dominion PX by choosing Control Panel > System > Hardware > Device Manager, and locating the "Dominion Serial Console" under the Ports group.

1. Press Enter. The Username prompt appears.

Username: _

1. Type a name and press Enter. The name is case sensitive, so make sure you capitalize the correct letters. Then you are prompted to enter a password.

Username: admin

Password: _

1. Type a password and press Enter. The password is case sensitive, so make sure you capitalize the correct letters.

After properly entering the password, the # or > system prompt appears. See Different CLI Modes and Prompts (on page 233) for details.

Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile was once used to log in to the Dominion PX web interface or CLI.

1. You are now logged in to the command line interface and can begin administering the Dominion PX device.

With SSH or Telnet

You can remotely log in to the command line interface using an SSH or Telnet client, such as PuTTY.

Note: PuTTY is a free program you can download from the Internet. See PuTTY's documentation for details on configuration.

To log in using SSH or Telnet:

1. Ensure SSH or Telnet has been enabled. See Modifying the Network Service Settings (on page 90).
2. Launch an SSH or Telnet client and open a console window. A login prompt appears.

1. Type a name and press Enter. The name is case sensitive, so make sure you capitalize the correct letters.

Note: If using the SSH client, the name must NOT exceed 25 characters. Otherwise, the login fails.

Then you are prompted to enter a password.

login as: admin admin@192.168.84.88's password:

1. Type a password and press Enter. The password is case sensitive, so make sure you capitalize the correct letters.

2. After properly entering the password, the # or > system prompt appears. See Different CLI Modes and Prompts (on page 233) for details.

Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile was once used to log in to the Dominion PX web interface or CLI.

1. You are now logged in to the command line interface and can begin administering the Dominion PX device.

Different CLI Modes and Prompts

Depending on the login name you use and the mode you enter, the system prompt in the CLI varies.

• User Mode: When you log in as a normal user, who does not have full permissions to configure the Dominion PX device, the > prompt appears.
• Administrator Mode: When you log in as an administrator, who has full permissions to configure the Dominion PX device, the # prompt appears.
• Configuration Mode: You can enter the configuration mode from the administrator mode. In this mode, the prompt changes to config:# and you can change Dominion PX device and network configurations. See Entering the Configuration Mode (on page 253).
• Diag nostic Mode: You can enter the diagnostic mode from the administrator mode. In this mode, the prompt changes to diag:> and you can perform the network troubleshooting commands, such as the ping command. See Entering the Diagnostic Mode (on page 381).

Closing a Serial Connection

Close the window or terminal emulation program when you finish accessing a Dominion PX device over the serial connection.

When accessing or upgrading multiple Dominion PX devices, do not transfer the serial cable from one device to another without closing the serial connection window first.

Help Command

The help command shows a list of main CLI commands. This is helpful when you are not familiar with the commands.

The help command syntax is:

# help

Press Enter after typing the command, and a list of main commands is displayed.

Tip: You can check what parameters are available for a specific CLI command by adding a question mark to the end of the command. See Querying Available Parameters for a Command (on page 385).

Showing Information

You can use the show commands to view current settings or status of the Dominion PX device or part of it, such as the IP address, networking mode, firmware version, circuit breaker state, inlet ratings, 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, such as the IP address, networking mode, and MAC address.

# show network

IP Configuration

This command shows the IP-related configuration only, such as IPv4 and IPv6 configuration, address(es), gateway, and subnet mask.

# show network ip

Variables:

- is one of the options: all, v4 or v6.

Option Description
all This options shows both of IPv4 and IPv6 settings.
	Tip: You can also type the command without adding this option "all" to get the same data.
v4 This option shows the IPv4 settings only.
v6 This option shows the IPv6 settings only.

LAN Interface Settings

This command shows the LAN interface information only, such as LAN interface speed, duplex mode, and current LAN interface status.

# show network interface

Networking Mode

This command shows whether the current networking mode is wired or wireless.

# show network mode

Wireless Configuration

This command only shows the wireless configuration of the Dominion PX device, such as the SSID parameter.

# show network wireless

To show detailed information, add the parameter "details" to the end of the command.

# show network wireless details

Network Service Settings

This command shows the network service settings only, including the Telnet setting, TCP ports for HTTP, HTTPS and SSH services, and SNMP settings.

# show network services

Variables:

- is one of the options: all, http, https, telnet, ssh, snmp and zeroconfig.

Option Description

all Displays the settings of all network services,including HTTP, HTTPS, Telnet, SSH and SNMP.

http Only displays the TCP port for the HTTP service.

https Only displays the TCP port for the HTTPS service.

telnet Only displays the settings of the Telnet service.

ssh Only displays the settings of the SSH service.

snmp Only displays the SNMP settings.

zeroconfig Only displays the settings of the zero configuration advertising.

modbus Only displays the settings of the Modbus service.

PDU Configuration

This command shows the PDU configuration, such as the device name, firmware version and model type.

# show pdu

To show detailed information, add the parameter "details" to the end of the command.

# show pdu details

Outlet Information

This command syntax shows the outlet information.

<h1 id="show-outlets-n">show outlets <n></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-outlets-n-details">show outlets <n> details</h1>

Variables:

- is one of the options: all, or a number.

Option Description
all Displays the information for all outlets.
	Tip: You can also type the command without adding this option "all" to get the same data.
A specific outlet number	Displays the information for the specified outlet only.

Displayed information:

• Without the parameter "details," only the outlet name is displayed. For PX-2000 series, the outlet state is also displayed.
• With the parameter "details," more outlet information is displayed in addition to the outlet name, such as the outlet rating.

Inlet Information

This command syntax shows the inlet information.

<h1 id="show-inlets-n">show inlets <n></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-inlets-n-details">show inlets <n> details</h1>

Variables:

- is one of the options: all, or a number.

Option Description
all Displays the information for all inlets.
	Tip: You can also type the command without adding this option "all" to get the same data.
A specific inlet number	Displays the information for the specified inlet only.An inlet number may need to be specified only when there are more than 1 inlet on your PDU.

Displayed information:

• Without the parameter "details," only the inlet's RMS current value(s) and inlet name are displayed.
• With the parameter "details," more inlet information is displayed in addition to the RMS current values, such as the inlet's RMS current, voltage, and active power.

Circuit Breaker Information

This command is only available for PDUs with overcurrent protection mechanism implemented.

This command syntax shows the circuit breaker information.

<h1 id="show-ocp-n">show ocp <n></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-ocp-n-details">show ocp <n> details</h1>

Variables:

- is one of the options: all, or a number.

Option Description
all Displays the information for all circuit breakers.
	Tip: You can also type the command without adding this option "all" to get the same data.
A specific circuit breaker number	Displays the information for the specified circuit breaker only.

Displayed information:

• Without the parameter "details," only the circuit breaker status and name are displayed.
• With the parameter "details," more circuit breaker information is displayed in addition to status, such as the rating and RMS current value.

Date and Time Settings

This command shows the current date and time settings on the Dominion PX device.

<h1 id="show-time">show time</h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-time-details">show time details</h1>

Environmental Sensor Information

This command syntax shows the environmental sensor's information.

# show externalsensors

To show detailed information, add the parameter "details" to the end of the command.

# show externalsensors details

Variables:

- is one of the options: all, or a number.

Option Description

all Displays the information for all environmental sensors.
A specific environmental sensor number*	Displays the information for the specified environmental sensor only.

* The environmental sensor number is the ID number assigned to the sensor, which can be found on the External Sensors page of the Dominion PX web interface.

Displayed information:

- Without the parameter "details," only the sensor ID, sensor type and reading are displayed.

Note: A discrete (on/off) sensor displays the sensor state instead of the reading.

- With the parameter "details," more information is displayed in addition to the ID number and sensor reading, such as the serial number and X, Y, and Z coordinates.

Inlet Sensor Threshold Information

This command syntax shows the specified inlet sensor's threshold-related information.

<h1 id="show-sensor-inlet-n-sensor-type">show sensor inlet <n> <sensor type></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-sensor-inlet-n-sensor-type-details">show sensor inlet <n> <sensor type> details</h1>

Variables:

• is the number of the inlet whose sensors you want to query.
• 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

Displayed information:

• Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion delay settings of the specified inlet sensor are displayed.
• With the parameter "details," more sensor information is displayed, including accuracy and range.
• If the requested sensor type is not supported, the message "Not available" is displayed.

Inlet Pole Sensor Threshold Information

This command is only available for a three-phase PDU except for an inline monitor (PX2-3000 series).

This command syntax shows the specified inlet pole sensor's threshold-related information.

# show sensor inletpole

To show detailed information, add the parameter "details" to the end of the command.

# show sensor inletpole

details

Variables:

• is the number of the inlet whose pole sensors you want to query.

• is the label of the inlet pole whose sensors you want to query.

Pole Label		Current sensor Voltage sensor
1	L1	L1 L1 - L2
2	L2	L2 L2 - L3
3	L3	L3 L3 - L1

- 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 and assertion timeout settings of the specified inlet pole sensor are displayed.
• With the parameter "details," more sensor information is displayed, including accuracy and range.
• If the requested sensor type is not supported, the message "Not available" is displayed.

Circuit Breaker Sensor Threshold Information

This command is only available for PDUs with overcurrent protection mechanism implemented.

This command syntax shows the specified circuit breaker sensor's threshold-related information.

# show sensor ocp

To show detailed information, add the parameter "details" to the end of the command.

# show sensor ocp details

Variables:

• is the number of the circuit breaker whose sensors you want to query.
• is one of the following sensor types:

Sensor type Description

current

Current

sensor

Displayed information:

• Without the parameter "details," only the reading, state, threshold and deassertion hysteresis settings of the specified circuit breaker sensor are displayed.
• With the parameter "details," more sensor information is displayed, including accuracy and range.
• If the requested sensor type is not supported, the message "Not available" is displayed.

Environmental Sensor Threshold Information

This command syntax shows the specified environmental sensor's threshold-related information.

# show sensor externalsensor

To show detailed information, add the parameter "details" to the end of the command.

# show sensor externalsensor details

Variables:

- is the environmental sensor number. The environmental sensor number is the ID number assigned to the sensor, which can be found on the External Sensors page of the Dominion PX 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 accuracy and range.

Note: For a discrete (on/off) sensor, the threshold-related and accuracy-related data is NOT available.

Security Settings

This command shows the security settings of the Dominion PX.

<h1 id="show-security">show security</h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-security-details">show security details</h1>

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 and user idle timeout.

Existing User Profiles

This command shows the data of one or all existing user profiles.

<h1 id="show-user-user_name">show user <user_name></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-user-user_name-details">show user <user_name> details</h1>

Variables:

- is the name of the user whose profile you want to query. The variable can be one of the options: all or a user's name.

Option Description
all This option shows all existing user profiles.
a specific user's name	This option shows the profile of the specified user only.

Displayed information:

• Without the parameter "details," only four pieces of user information are displayed: user name, "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 temperature unit and so on.

Existing Roles

This command shows the data of one or all existing roles.

# show roles

Variables:

- is the name of the role whose permissions you want to query. The variable can be one of the following options:

Option Description
all This option shows all existing roles.
a specific role's name 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 only applies to outlet-switching capable PDUs.

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 and non-critical outlets through CLI, see Specifying Non-Critical Outlets (on page 259).

Serial Port Settings

This command shows the baud rate setting of the serial port labeled CONSOLE / MODEM on the Dominion PX device.

# show serial

EnergyWise Settings

This command shows the Dominion PX's current configuration for Cisco® EnergyWise.

# show energywise

Asset Sensor Settings

This command shows the asset sensor settings, such as the total number of rack units (tag ports), asset sensor state, numbering mode, orientation, available tags and LED color settings.

# show assetStrip

Variables:

- is one of the options: all, or a number.

Option Description
all Displays all asset sensor information.
	Tip: You can also type the command without adding this option "all" to get the same data.
A specific asset sensor number	Displays the settings of the asset sensor connected to the specified FEATURE port number.For the Dominion PX device with only one FEATURE port, the valid number is always 1.

This command syntax sets the LED color for all rack units on the connected asset sensor(s) to indicate the absence of a connected asset tag.

config:# assetStrip LEDColorForDisconnectedTags

Variables:

- is the hexadecimal RGB value of a color in HTML format. The variable ranges from #000000 to #FFFFFF.

Rack Unit Settings of an Asset Sensor

For the Raritan asset sensor, a rack unit refers to a tag port. This command shows the settings of a specific rack unit or all rack units on an asset sensor, such as a rack unit's LED color and LED mode.

# show rackUnit

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is one of the options: all or a specific rack unit's index number.

Option Description

all Displays the settings of all rack units on the specified asset sensor.
	Tip: You can also type the command without adding this option "all" to get the same data.
A specific number	Displays the settings of the specified rack unit on the specified asset sensor.Use the index number to specify the rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.

Blade Extension Strip Settings

This command shows the information of a blade extension strip, including the total number of tag ports, and if available, the ID (barcode) number of any connected tag.

<h1 id="show-bladeslot-n-rack_unit-blade_slot">show bladeSlot <n> <rack_unit> <blade_slot></h1>

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit (tag port) on the selected asset sensor. The index number of each rack unit is available on the Asset Strip page of the web interface.
• is one of the options: all or a specific number of a tag port on the blade extension strip.

Option Description
all Displays the information of all tag ports on the specified blade extension strip connected to a particular rack unit.
A specific number	Displays the information of the specified tag port on the blade extension strip connected to a particular rack unit.The number of each tag port on the blade extension strip is available on the Asset Strip page.

Reliability Data

This command shows the reliability data.

# show reliability data

Reliability Error Log

This command shows the reliability error log.

# show reliability errorlog

Variables:

- is one of the options: 0 (zero) or any other integer number.

Option Description
0 Displays all entries in the reliability error log.
A specific integer number	Displays the specified number of last entries in the reliability error log.

Command History

This command syntax 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.

History Buffer Length

This command syntax shows the length of the history buffer for storing the history commands.

# show history bufferlength

Displayed information:

- The current history buffer length is displayed.

Examples

This section provides examples of the show command.

Example 1 - Basic Security Information

The diagram shows the output of the show security command.

<h1 id="show-security-2">show security</h1>
IP access control: Disabled
Role based access control: Disabled
Password aging: Enabled
Prevent concurrent user login: No
Strong passwords: Disabled
Enforce HTTPS for web access: Yes # 

Example 2 - In-Depth Security Information

More information is displayed when typing the show security details command.

<h1 id="show-security-details-2">show security details</h1>
IP access control: Disabled

Role based access control: Disabled

Password aging: Enabled
Aging interval: 60 days

Prevent concurrent user login: No
Maximum number of failed logins: 3
User block time: 10 minutes

User idle timeout: 10 minutes

Strong passwords: Disabled

Enforce HTTPS for web access: Yes
# 

Example 3 - Basic PDU Information

The diagram shows the output of the show pdu command.

<h1 id="show-pdu">show pdu</h1>
PDU 'my PX'
Model: PX2-5260R
Firmware version: 2.2.0.1-26020
# 

Example 4 - In-Depth PDU Information

More information is displayed when typing the show pdu details command.

<h1 id="show-pdu-details">show pdu details</h1>
PDU 'my PX'
Model: PX2-5260R
Firmware version: 2.2.0.1-26020
Serial number: PEG1234567

Default outlet state on startup: Last known state
Power cycle delay: 10 seconds

Outlet power sequence: default
Outlet sequence delays: 1-12: 0 s
Inrush guard delay: 200 ms

Voltage rating: 200-240V
Current rating: 16A
Frequency rating: 50/60Hz
Power rating: 3.2-3.8kVA

Sensor data retrieval: Enabled
Measurements per log entry: 60

External sensor Z coordinate format: Rack units
Device altitude: 0 m
# 

Configuring the Dominion PX Device and Network

To configure the Dominion PX device or network settings through the CLI, you must log in as the administrator.

Entering the Configuration Mode

You must enter the configuration mode since configuration commands function in the configuration mode only.

▶ To enter the configuration mode:

1. Ensure you have entered the administrator mode and the # prompt is displayed.

Note: If you enter the configuration mode from the user mode, you may have limited permissions to make configuration changes. See Different CLI Modes and Prompts (on page 233).

1. Type config and press Enter. The config:# prompt appears, indicating that you have entered the configuration mode.

config:# _

1. 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. See Quitting the Configuration Mode (on page 374).

PDU Configuration Commands

A PDU configuration command begins with pdu. You can use the PDU configuration commands to change the settings that apply to the whole Dominion PX device.

The commands are case sensitive so ensure you capitalize them correctly.

Changing the PDU Name

This command syntax changes the Dominion PX device's name.

config:# pdu name ""

Variables:

- is a string comprising up to 32 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Example

The following command assigns the name "my px12" to the PDU.

config:# pdu name "my px12"

Setting the Outlet Power-On Sequence

This section only applies to outlet-switching capable PDUs.

This command syntax sets the outlet power-on sequence when the PDU powers up.

config:# pdu outletSequence

Variables:

- is one of the options: default, or a comma-separated list of outlet numbers.

Option Description
default All outlets	are switched ON in the ASCENDING order (from outlet 1 to the final outlet) when the Dominion PX device powers up.
A comma-separated list of outlet numbers	All outlets are switched ON in the order you specify using the comma-separated list.The list must include all outlets on the PDU.

Example

The following command causes a 10-outlet PDU to first power on the 8th to 6th outlets and then the rest of outlets in the ascending order after the PDU powers up.

config:# pdu outletSequence 8-6,1-5,9,10

Setting the Outlet Power-On Sequence Delay

This section only applies to outlet-switching capable PDUs.

This command syntax sets the delays (in seconds) for outlets when turning on all outlets in sequence.

config:# pdu outletSequenceDelay :;:;:;...

Separate outlet numbers and their delay settings with a colon. Outlets followed by delays are separated with a semicolon.

Variables:

• , , and the like are individual outlet numbers or a range of outlets.
• , , and the like are the delay time in seconds.

Example

The following command determines that the outlet 1's delay is 2.5 seconds, outlet 2's delay is 3 seconds, and the delay for outlets 3 through 5 is 10 seconds.

config:# pdu outletSequenceDelay 1:2.5;2:3;3-5:10

Setting the PDU-Defined Default Outlet State

This section only applies to outlet-switching capable PDUs.

This command syntax determines the initial power condition of all outlets after powering up the PDU.

config:# pdu outletStateOnDeviceStartup

Variables:

- is one of the options: off, on or lastKnownState.

Option Description
off Switches OFF	all outlets when the Dominion PX device powers up.
on Switches ON	all outlets when the Dominion PX device powers up.

Option Description

lastKnownState

Restores all outlets to the previous status before powering down the Dominion PX device when the PDU powers up again.

Example

The following command causes all outlets to return to the last power state before powering down the PDU, after you power up the PDU again.

config:# pdu outletStateOnDeviceStartup lastKnownState

Setting the PDU-Defined Cycling Power-Off Period

This section only applies to outlet-switching capable PDUs.

This command syntax sets the power-off period of the power cycling operation for all outlets.

config:# pdu cyclingPowerOffPeriod

Variables:

- is the time of the cycling power-off period in seconds, which is an integer between 0 and 3600.

Example

The following command sets the power off period of the power cycling operation to 5 seconds.

config:# pdu cyclingPowerOffPeriod 5

Setting the Inrush Guard Delay Time

This section only applies to outlet-switching capable PDUs.

This command syntax sets the inrush guard delay.

config:# pdu inrushGuardDelay

Variables:

- is a delay time between 100 and 100000 milliseconds.

Example

The following command sets the inrush guard delay to 1000 milliseconds.

config:# pdu inrushGuardDelay 1000

Setting the Outlet Initialization Delay

This section only applies to outlet-switching capable PDUs.

This command syntax determines the outlet initialization delay timing on device startup. See Setting the Initialization Delay (on page 141) for information on outlet initialization delay.

config:# pdu outletInitializationDelayOnDeviceStartup

Variables:

- is a delay time between 1 and 3600 seconds.

Example

The following command sets the outlet initialization delay timing to 5 seconds.

config:# pdu outletInitializationDelayOnDeviceStartup 5

Specifying Non-Critical Outlets

This section only applies to outlet-switching capable PDUs.

This command syntax determines critical and non-critical outlets. It is associated with the load shedding mode. See Setting Non-Critical Outlets and Load Shedding Mode (on page 144).

config:# pdu nonCriticalOutlets :false;:true

Separate outlet numbers and their settings with a colon. Separate each "false" and "true" setting with a semicolon.

Variables:

• is one or multiple outlet numbers to be set as NON-critical outlets. Use commas to separate outlet numbers.
• is one or multiple outlet numbers to be set as critical outlets. User commas to separate outlet numbers.

Example

The following command sets outlets 1, 2, 3, 7, and 9 to be critical outlets, and 4, 5, 6, 8, 10, 11 and 12 to be non-critical outlets on a 12-outlet PDU.

config:# pdu nonCriticalOutlets 1-3,7,9:false;4-6,8,10-12:true

Enabling or Disabling Data Logging

This command syntax enables or disables the data logging feature.

config:# pdu dataRetrieval

Variables:

- is one of the options: enable or disable.

Option Description
enable Enables	the data logging feature.
disable	Disables the data logging feature.

For more information, see Setting Data Logging (on page 99).

Example

The following command enables the data logging feature.

config:# pdu dataRetrieval enable

Setting the Data Logging Measurements Per Entry

This command syntax defines the number of measurements accumulated per log entry.

config:# pdu measurementsPerLogEntry

Variables:

- is an integer between 1 and 600. The default is 60 samples per log entry.

For more information, see Setting Data Logging (on page 99).

Example

The following command determines that 66 measurements are accumulated per log entry for sensors, that is, 66 seconds.

config:# pdu measurementsPerLogEntry 66

Specifying the Device Altitude

This command syntax specifies your Dominion PX device's altitude above sea level (in meters). You must specify the Dominion PX device's altitude above sea level if a Raritan differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor. See Altitude Correction Factors (on page 414).

config:# pdu deviceAltitude

Variables:

- is an integer between 1 and 3000 meters.

Example

The following command determines that the Dominion PX device is located at 1500 meters above sea level.

config:# pdu deviceAltitude 1500

Setting the Z Coordinate Format for Environmental Sensors

This command syntax enables or disables the use of rack units for specifying the height (Z coordinate) of environmental sensors.

config:# pdu externalSensorsZCoordinateFormat

Variables:

- is one of the options: rackUnits or freeForm.

Option Description

rackUnits The height of the Z coordinate is measured in standard rack units. When this is selected, you can type a numeric value in the rack unit to describe the Z coordinate of any environmental sensors.

freeForm Any alphanumeric string can be used for specifying the Z coordinate.

Note: After determining the format for the Z coordinate, you can set a value for it. See Setting the Z Coordinate (on page 318).

Example

The following command determines that the unit of rack is used for specifying the Z coordinate of environmental sensors.

config:# pdu externalSensorsZCoordinateFormat rackUnits

Changing the LED Display Orientation

This command syntax determines the orientation of the value shown on the LED display of a Zero U PDU.

config:# pdu displayOrientation

Variables:

- is one of the options: automatic, flipped or normal.

Option Description

automatic The direction of the value shown on the LED display is determined depending on the PDU's orientation detected by the built-in tilt sensor.

flipped The value shown on the LED display always stays in the opposite direction regardless of the PDU's orientation.

normal The value shown on the LED display always stays in the normal direction regardless of the PDU's orientation.

Note that this command is NOT applicable to a non-Zero U PDU.

Example

The following command makes the Zero U PDU reverses the direction of the value shown on the LED display.

config:# pdu displayOrientation flipped

Networking Configuration Commands

A number of network settings can be changed through the CLI, such as the IP address, transmission speed, duplex mode, and so on.

Setting the Networking Mode

If your Dominion PX device is implemented with both of the wired and wireless networking mechanisms, you must determine which mechanism is enabled for network connectivity before further configuring networking parameters.

This command syntax enables the wired or wireless networking mode.

config:#network mode

Variables:

- is one of the modes: wired or wireless.

Mode Description

wired Enables the wired networking mode.

wireless Enables the wireless networking mode.

Note: If you enable the wireless networking mode, and the Dominion PX does not detect any wireless USB LAN adapter or the connected wireless USB LAN adapter is not supported, the message "Supported Wireless device not found" is displayed.

Example

The following command enables the wired networking mode.

config:# network mode wired

Configuring IP Protocol Settings

By default, only the IPv4 protocol is enabled. You can enable both the IPv4 and IPv6 protocols, or only the IPv6 protocol for your Dominion PX device.

An IP protocol configuration command begins with network ip.

Enabling IPv4 or IPv6

This command syntax determines which IP protocol is enabled on the Dominion PX.

config:# network ip proto

Variables:

- is one of the options: v4Only, v6Only or both.

Mode Description
v4Only Enables	IPv4 only on all interfaces. This is the default.
v6Only Enables	IPv6 only on all interfaces.
both Enables both	IPv4 and IPv6 on all interfaces.

Example

The following command determines that both of IPv4 and IPv6 protocols are enabled.

config:# network ip proto both

Selecting IPv4 or IPv6 Addresses

This command syntax determines which IP address is used when the DNS server returns both of IPv4 and IPv6 addresses. You need to configure this setting only after both of IPv4 and IPv6 protocols are enabled on the Dominion PX.

config:# network ip dnsResolverPreference

Variables:

- is one of the options: preferV4 or preferV6.

Option Description

preferV4 Use the IPv4 addresses returned by the DNS server.

preferV6 Use the IPv6 addresses returned by the DNS server.

Example

The following command determines that only IPv4 addresses returned by the DNS server are used.

config:# network ip dnsResolverPreference preferV4

Setting the 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 is enabled.

A wireless configuration command begins with network wireless.

Note: If current networking mode is not wireless, the SSID, PSK and BSSID values are not applied until the networking mode is changed to "wireless." In addition, a message appears, indicating that the active network interface is not wireless.

The commands are case sensitive so ensure you capitalize them correctly.

Setting the SSID

This command syntax specifies the SSID string.

config:# network wireless SSID

Variables:

- is the name of the wireless access point, which consists of:

- Up to 32 ASCII characters

- No spaces

- ASCII codes 0x20 \~ 0x7E

Example

The following command assigns "myssid" as the SSID.

config:# network wireless SSID myssid

Setting the Authentication Method

This command syntax sets the wireless authentication method to either PSK or Extensible Authentication Protocol (EAP).

config:# network wireless authMethod

Variables:

- is one of the authentication methods: PSK or EAP.

Method Description

PSK The wireless authentication method is set to PSK.

EAP The wireless authentication method is set to EAP.

Example

The following command sets the wireless authentication method to PSK.

config:# network wireless authMethod PSK

Setting the PSK

If the Pre-Shared Key (PSK) authentication method is selected, you must assign a PSK passphrase by using this command syntax.

config:# network wireless PSK

Variables:

- is a string or passphrase that consists of:

• Up to 32 ASCII characters
• No spaces
• ASCII codes 0x20 \~ 0x7E

Example

This command assigns "encryp-key" as the PSK.

config:# network wireless PSK encryp-key

Setting the EAP Parameters

When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, password, and CA certificate.

Setting the Outer Authentication

This command syntax determines the outer authentication protocol for the EAP.

config:# network wireless eapOuterAuthentication

Variables:

- The value of is PEAP because Dominion PX only supports Protected Extensible Authentication Protocol (PEAP) as the outer authentication.

Example

The following command determines the outer authentication protocol for the EAP authentication is Protected Extensible Authentication Protocol (PEAP).

config:# network wireless eapOuterAuthentication PEAP

Setting the Inner Authentication

This command syntax determines the inner authentication protocol for the EAP.

config:# network wireless eapInnerAuthentication

Variables:

- The value of is MSCHAPv2 because Dominion PX only supports Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) as the inner authentication.

Example

The following command determines the inner authentication protocol for the EAP authentication is MSCHAPv2.

config:# network wireless eapInnerAuthentication MSCHAPv2

Setting the EAP Identity

This command syntax determines the EAP identity.

config:# network wireless eapIdentity

Variables:

- is your user name for the EAP authentication.

Example

The following command sets the EAP identity to "eap_user01."

config:# network wireless eapIdentity eap_user01

Setting the EAP Password

This command syntax determines the EAP password.

config:# network wireless eapPassword

Variables:

- is your password for EAP authentication.

Example

The following command sets the EAP password to "user01_password."

config:# network wireless eapPassword user01_password

Providing the EAP CA Certificate

You may need to provide a third-party CA certificate for the EAP authentication.

▶ To provide a CA certificate:

1. Type the CA certificate command as shown below and press Enter.

config:# network wireless eapCACertificate

1. The system prompts you to enter the contents of the CA certificate. Do the following to input the contents:

a. Open your CA certificate with a text editor.

b. Copy the contents between the "-- BEGIN CERTIFICATE --" and "-- END CERTIFICATE --" lines in a certificate.

c. Paste the certificate contents into the terminal.

d. Press Enter.

Tip: To remove an existing CA certificate, simply press Enter without typing or pasting anything when the system prompts you to input the certificate contents.

1. If the certificate is valid, the system shows the command prompt "config:#" again. If not, it shows a message indicating that the certificate is not valid.

Example

This section provides a CA certificate example only. Your CA certificate contents should be different from the contents displayed in this example.

▶ To provide a CA certificate:

1. Make sure you have entered the configuration mode. See Entering the Configuration Mode (on page 253).
2. Type the following command and press Enter.
   config:#network wireless 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.

--- BEGIN CERTIFICATE --- MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAkGA1UEBhMCVVMx NjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGFuZCBTcGFjZSBBZG1pbmlz dHJhdGlvbjAmFxE5NjA1MjgxMzQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAw ZzELMAkGA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGFu ZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEwYDVQQDEwxTdGV2 ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwRgJBALrAwyYdgxmzNP/ts0Uyf6Bp miJYktU/w4NG67ULaN4B5CnEz7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0C AQOjgaswgagwZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAIVTMTYWNAYDVQQK Ey1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRtaW5pc3RyYXRpb24x DTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0wC4AJODMyOTcwODEwMBgGA1UdAgQR MA8ECTgzMjk3MDgyM4ACBSAwDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GB AH2y1VCEw/A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOHH21 X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atObEuJy1ZZ0pBDWINR3 WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZita+z4IBO --- END CERTIFICATE ---

1. Select and copy the contents, excluding the starting line containing "BEGIN CERTIFICATE" and the ending line containing "END CERTIFICATE" as illustrated below.

MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAKGA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEF1cm9uYXV0aWNzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxMzQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEF1cm9uYXV0aWNzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEwYDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwRgJBALrAwyYdgxmzNP/tsOUyf6BpmiJYktU/w4NG67ULaN4B5CnEz7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgagwZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYWNAYDVQQKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRtaW5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0wC4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSAwDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOHH21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atObEuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZita+z4IBO

1. Paste the contents in the terminal.
2. Press Enter.
3. Verify whether the system shows the following command prompt, indicating the provided CA certificate is valid.

config:#

Setting the BSSID

This command syntax specifies the BSSID.

config:# network wireless BSSID

Variables:

- is the MAC address of the wireless access point.

Example

The following command specifies that the BSSID is 00:14:6C:7E:43:81.

config:# network wireless BSSID 00:14:6C:7E:43:81

Configuring the IPv4 Parameters

An IPv4 configuration command begins with network ipv4.

The commands are case sensitive so ensure you capitalize them correctly.

Setting the IPv4 Configuration Mode

This command syntax determines the IP configuration mode.

config:# network ipv4 ipConfigurationMode

Variables:

- is one of the modes: dhcp or static.

Mode Description

dhcp The IPv4 configuration mode is set to DHCP.

static The IPv4 configuration mode is set to static IP address.

Example

The following command enables the Static IP configuration mode.

config:# network ipv4 ipConfigurationMode static

Setting the 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 syntax:

config:# network ipv4 preferredHostName

Variables:

- 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

Example

The following command sets the preferred host name to "my-host."

config:# network ipv4 preferredHostName my-host

Setting the IPv4 Address

After selecting the static IP configuration mode, you can use this command syntax to assign a permanent IP address to the Dominion PX device.

config:# network ipv4 ipAddress

Variables:

- is the IP address being assigned to your Dominion PX device. The value ranges from 0.0.0.0 to 255.255.255.255.

Example

The following command assigns the static IPv4 address "192.168.84.222" to the Dominion PX device.

config:# network ipv4 ipAddress 192.168.84.222

Setting the IPv4 Subnet Mask

After selecting the static IP configuration mode, you can use this command syntax to define the subnet mask.

config:# network ipv4 subnetMask

Variables:

- is the subnet mask address. The value ranges from 0.0.0.0 to 255.255.255.255.

Example

The following command sets the subnet mask to 192.168.84.0.

config:# network ipv4 subnetMask 192.168.84.0

Setting the IPv4 Gateway

After selecting the static IP configuration mode, you can use this command syntax to specify the gateway.

config:# network ipv4 gateway

Variables:

- is the IP address of the gateway. The value ranges from 0.0.0.0 to 255.255.255.255.

Example

The following command sets the IPv4 gateway to 255.255.255.0.

config:# network ipv4 gateway 255.255.255.0

Setting the IPv4 Primary DNS Server

After selecting the static IP configuration mode, you can use this command syntax to specify the primary DNS server.

config:# network ipv4 primaryDNSServer

Variables:

- is the IP address of the primary DNS server. The value ranges from 0.0.0.0 to 255.255.255.255.

Example

The following command determines that the primary DNS server is 192.168.84.30.

config:# network ipv4 primaryDNSServer 192.168.84.30

Setting the IPv4 Secondary DNS Server

After selecting the static IP configuration mode, you can use this command syntax to specify the secondary DNS server.

config:# network ipv4 secondaryDNSServer

Variables:

- is the IP address of the secondary DNS server. The value ranges from 0.0.0.0 to 255.255.255.255.

Note: The Dominion PX supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the Dominion PX only uses the primary IPv4 and IPv6 DNS servers.

Example

The following command determines that the secondary DNS server is 192.168.84.33.

config:# network ipv4 secondaryDNSServer 192.168.84.33

Overriding the IPv4 DHCP-Assigned DNS Server

After specifying the primary/secondary DNS server, you can use this command to override the DHCP-assigned DNS server with the one you specified.

config:# network ipv4 overrideDNS

Variables:

- is one of the options: enable or disable.

Option Description
enable This option	overrides the DHCP-assigned DNS server with the primary/secondary DNS server you assign.
disable This option	resumes using the DHCP-assigned DNS server.

Example

The following command overrides the DHCP-assigned DNS server with the one you specified.

config:# network ipv4 overrideDNS enable

Configuring the IPv6 Parameters

An IPv6 configuration command begins with network ipv6.

The commands are case sensitive so ensure you capitalize them correctly.

Setting the IPv6 Configuration Mode

This command syntax determines the IP configuration mode.

config:# network ipv6 ipConfigurationMode

Variables:

- is one of the modes: automatic or static.

Mode Description

automatic The IPv6 configuration mode is set to automatic.

static The IPv6 configuration mode is set to static IP address.

Example

The following command sets the IP configuration mode to the static IP address mode.

config:# network ipv6 ipConfigurationMode static

Setting the IPv6 Address

After selecting the static IP configuration mode, you can use this command syntax to assign a permanent IP address to the Dominion PX device.

config:# network ipv6 ipAddress

Variables:

- is the IP address being assigned to your Dominion PX device. This value uses the IPv6 address format.

Example

The following command assigns the static IPv6 address

"3210:4179:0:8:0:800:200C:417A" to the Dominion PX device.

config:# network ipv6 ipAddress 3210:4179:0:8:0:800:200C:417A

Setting the IPv6 Gateway

After selecting the static IP configuration mode, you can use this command syntax to specify the gateway.

config:# network ipv6 gateway

Variables:

- is the IP address of the gateway. This value uses the IPv6 address format.

Example

The following command sets the gateway to 500:0:330:0:4:9:3:2.

config:# network ipv6 gateway 500:0:330:0:4:9:3:2

Setting the IPv6 Primary DNS Server

After selecting the static IP configuration mode, you can use this command syntax to specify the primary DNS server. It is required to enable overriding the auto-assigned DNS server before you can specify the DNS servers manually. See Overriding the IPv6 DHCP-Assigned DNS Server (on page 278).

config:# network ipv6 primaryDNSServer

Variables:

- is the IP address of the primary DNS server. This value uses the IPv6 address format.

Example

The following command determines that the primary DNS server is 2103:288:8201:1::14.

config:# network ipv6 primaryDNSServer 2103:288:8201:1::14

Setting the IPv6 Secondary DNS Server

After selecting the static IP configuration mode, you can use this command syntax to specify the secondary DNS server. It is required to enable overriding the auto-assigned DNS server before you can specify the DNS servers manually. See Overriding the IPv6 DHCP-Assigned DNS Server (on page 278).

config:# network ipv6 secondaryDNSServer

Variables:

- is the IP address of the secondary DNS server. This value uses the IPv6 address format.

Note: The Dominion PX supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the Dominion PX only uses the primary IPv4 and IPv6 DNS servers.

Example

The following command determines that the secondary DNS server is 2103:288:8201:1::700.

config:# network ipv6 secondaryDNSServer 2103:288:8201:1::700

Overriding the IPv6 DHCP-Assigned DNS Server

After specifying the primary/secondary DNS server, you can use this command to override the DHCP-assigned DNS server with the one you specified.

config:# network ipv6 overrideDNS

Variables:

- is one of the options: enable or disable.

Option Description
enable This option	overrides the DHCP-assigned DNS server with the primary/secondary DNS server you assign.
disable This option	resumes using the DHCP-assigned DNS server.

Example

The following command overrides the DHCP-assigned DNS server with the one you specified.

config:# network ipv6 overrideDNS enable

Setting the LAN Interface Parameters

A LAN interface configuration command begins with network interface.

The commands are case sensitive so ensure you capitalize them correctly.

Changing the LAN Interface Speed

This command syntax determines the LAN interface speed.

config:# network interface LANInterfaceSpeed

Variables:

- is one of the options: auto, 10Mbps, and 100Mbps.

Option Description

auto System determines the optimum LAN speed through auto-negotiation.

Option Description

10Mbps The LAN speed is always 10 Mbps.

100Mbps The LAN speed is always 100 Mbps.

Example

The following command lets the Dominion PX determine the optimal LAN interface speed through auto-negotiation.

config:# network interface LANInterfaceSpeed auto

Changing the LAN Duplex Mode

This command syntax determines the LAN interface duplex mode.

config:# network interface LANInterfaceDuplexMode

Variables:

- is one of the modes: auto, half or full.

Option Description
auto The Dominion PX selects the optimum transmission mode through auto-negotiation.
half	Half duplex:Data is transmitted in one direction (to or from the Dominion PX device) at a time.
full	Full duplex:Data is transmitted in both directions simultaneously.

Example

The following command lets the Dominion PX determine the optimal transmission mode through auto-negotiation.

config:# network interface LANInterfaceDuplexMode auto

Setting the Network Service Parameters

A network service command begins with network services.

Changing the HTTP Port

This command syntax changes the HTTP port.

config:# network services http

Variables:

- is a TCP port number between 1 and 65535. The default HTTP port is 80.

Example

The following command sets the HTTP port to 81.

config:# network services http 81

Changing the HTTPS Port

This command syntax changes the HTTPS port.

config:# network services https

Variables:

- is a TCP port number between 1 and 65535. The default HTTPS port is 443.

Example

The following command sets the HTTPS port to 333.

config:# network services https 333

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 syntax enables or disables the Telnet service.

config:# network services telnet enabled

Variables:

- is one of the options: true or false.

Option Description

true The Telnet service is enabled.

false The Telnet service is disabled.

Example

The following command enables the Telnet service.

config:# network services telnet enabled true

Changing the Telnet Port

This command syntax changes the Telnet port.

config:# network services telnet port

Variables:

- is a TCP port number between 1 and 65535. The default Telnet port is 23.

Example

The following command syntax sets the TCP port for Telnet to 44.

config:# network services telnet port 44

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 syntax enables or disables the SSH service.

config:# network services ssh enabled

Variables:

- is one of the options: true or false.

Option Description

true The SSH service is enabled.

false The SSH service is disabled.

Example

The following command enables the SSH service.

config:# network services ssh enabled true

Changing the SSH Port

This command syntax changes the SSH port.

config:# network services ssh port

Variables:

- is a TCP port number between 1 and 65535. The default SSH port is 22.

Example

The following command syntax sets the TCP port for SSH to 555.

config:# network services ssh port 555

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 syntax enables or disables the SNMP v1/v2c protocol.

config:# network services snmp v1/v2c

Variables:

- is one of the options: enable or disable.

Option Description
enable	The SNMP v1/v2c protocol is enabled.
disable	The SNMP v1/v2c protocol is disabled.

Example

The following command enables the SNMP v1/v2c protocol.

config:# network services snmp v1/v2c enable

Enabling or Disabling SNMP v3

This command syntax enables or disables the SNMP v3 protocol.

config:# network services snmp v3

Variables:

- is one of the options: enable or disable.

Option Description
enable	The SNMP v3 protocol is enabled.
disable	The SNMP v3 protocol is disabled.

Example

The following command enables the SNMP v3 protocol.

config:# network services snmp v3 enable

Setting the SNMP Read Community

This command syntax sets the SNMP read-only community string.

config:# network services snmp readCommunity

Variables:

• is a string comprising 4 to 64 ASCII printable characters.
• The string CANNOT include spaces.

Example

This command syntax sets the SNMP read-only community string to "public."

config:# network services snmp readCommunity public

Setting the SNMP Write Community

This command syntax sets the SNMP read/write community string.

config:# network services snmp writeCommunity

Variables:

• is a string comprising 4 to 64 ASCII printable characters.
• The string CANNOT include spaces.

Example

The following command sets the SNMP read/write community string to "private."

config:# network services snmp writeCommunity private

Setting the sysContact Value

This command syntax sets the SNMP sysContact MIB-II value.

config:# network services snmp sysContact

Variables:

- is a string comprising 0 to 255 alphanumeric characters.

Example

The following command sets the SNMP MIB-II sysContact to "John_Krause."

config:# network services snmp sysContact John_Krause

Setting the sysName Value

This command syntax sets the SNMP sysName MIB-II value.

config:# network services snmp sysName

Variables:

- is a string comprising 0 to 255 alphanumeric characters.

Example

The following command sets the SNMP MIB-II sysName to "Win7_system"

config:# network services snmp sysName Win7_system

Setting the sysLocation Value

This command syntax sets the SNMP sysLocation MIB-II value.

config:# network services snmp sysLocation

Variables:

- is a string comprising 0 to 255 alphanumeric characters.

Example

The following command sets the SNMP MIB-II sysLocation to "New_TAPEI"

config:# network services snmp sysLocation New_TAIPEI

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 syntax enables or disables the Modbus protocol.

config:# network services modbus enabled

Variables:

- is one of the options: true or false.

Option Description

true The Modbus agent is enabled.

false The Modbus agent is disabled.

Example

The following command enables the Modbus protocol.

config:# network services modbus enabled true

Enabling or Disabling the Read-Only Mode

This command syntax enables or disables the read-only mode for the Modbus agent.

config:# network services modbus read-only

Variables:

- is one of the options: true or false.

Option Description

true The read-only mode is enabled.

false The read-only mode is disabled.

Example

The following command disables the read-only mode for the Modbus agent.

config:# network services modbus read-only false

Changing the Modbus Port

This command syntax changes the Modbus port.

config:# network services modbus port

Variables:

- is a TCP port number between 1 and 65535. The default Modbus port is 502.

Example

This following command changes the Modbus port.

config:# network services modbus port 600

Enabling or Disabling the Service Advertisement

This command syntax enables or disables the zero configuration protocol, which enables advertising or auto discovery of network services. See Enabling Service Advertisement (on page 94) for details.

config:# network services zeroconfig enabled

Variables:

- is one of the options: true or false.

Option Description
true The zero configuration protocol is enabled.
false	The zero configuration protocol is disabled.

Example

The following command enables the zero configuration protocol.

config:# network services zeroconfig enabled true

Time Configuration Commands

A time configuration command begins with time.

Determining the Time Setup Method

This command syntax determines the method to configure the system date and time.

config:# time method

Variables:

- 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.

Example

The following command sets the date and time settings by using the NTP servers.

config:# time method ntp

Setting the NTP Parameters

A time configuration command that is used to set the NTP parameters begins with time ntp.

Specifying the Primary NTP Server

This command syntax specifies the primary time server if synchronization with the NTP server is enabled.

config:# time ntp firstServer

Variables:

- The is the IP address or host name of the primary NTP server.

Example

The following command sets the primary time server to 192.168.80.66.

config:# time ntp firstServer 192.168.80.66

Specifying the Secondary NTP Server

This command syntax specifies the primary time server if synchronization with the NTP server is enabled.

config:# time ntp secondServer

Variables:

- The is the IP address or host name of the secondary NTP server.

Example

The following command sets the secondary time server to 192.168.80.78.

config:# time ntp secondServer 192.168.80.78

Overriding the DHCP-Assigned NTP Servers

This command syntax determines whether the customized NTP server settings override the DHCP-specified NTP servers.

config:# time ntp overrideDHCPProvidedServer

Variables:

- is one of these options: true or false.

Mode Description
true Customized	NTP server settings override the DHCP-specified NTP servers.
false Customized	NTP server settings do NOT override the DHCP-specified NTP servers.

Example

The following command overrides the DHCP-specified NTP servers with the customized NTP servers, including the primary and secondary NTP servers.

config:# time ntp overrideDHCPProvidedServer true

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 Dominion PX device from 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 the Firewall Control Parameters

There are different commands for modifying firewall control parameters.

- IPv4 commands

To enable or disable the IPv4 firewall control feature, use this command syntax:

config:# security ipAccessControl ipv4 enabled <option> 

To determine the default IPv4 firewall control policy, use this command syntax:

config:# security ipAccessControl ipv4 defaultPolicy <policy> 

- IPv6 commands

To enable or disable the IPv6 firewall control feature, use this command syntax:

config:# security ipAccessControl ipv6 enabled <option> 

To determine the default IPv6 firewall control policy, use this command syntax:

config:# security ipAccessControl ipv6 defaultPolicy <policy> 

Variables:

- is one of the options: true or false.

Option Description

true Enables the IP access control feature.

false Disables the IP access control feature.

- is one of the options: accept, drop or reject.

Option Description

accept	Accepts	traffic	from all IP addresses.
drop	Discards	traffic from all IP addresses, without sending any failure notification to the source host.

Option Description

reject Discards traffic from all IP addresses, and an ICMP message is sent to the source host for failure notification.

Tip: You can combine both commands to modify all firewall control parameters at a time. See Multi-Command Syntax (on page 373).

Example

The following command sets up two parameters of the IPv4 access control feature.

config:# security ipAccessControl ipv4 enabled true defaultPolicy accept

Results:

• The IPv4 access control feature is enabled.
• The default policy is set to "accept."

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 syntax for adding a rule varies.

• IPv4 commands
  To add a new rule to the bottom of the IPv4 rules list, use this command syntax:

config:# security ipAccessControl ipv4 rule add

To add a new IPv4 rule by inserting it above or below a specific rule, use this command syntax:

Chapter 7: Using the Command Line Interface

config:# security ipAccessControl ipv4 rule add <ip_mask> <policy> <insert> <rule_number>
-- OR --
config:# security ipAccessControl ipv4 rule add <insert> <rule_number> <ip_mask> <policy> 

• IPv6 commands
  To add a new rule to the bottom of the IPv6 rules list, use this command syntax:

config:# security ipAccessControl ipv6 rule add <ip_mask> <policy> 

To add a new IPv6 rule by inserting it above or below a specific rule, use this command syntax:

config:# security ipAccessControl ipv6 rule add <ip_mask> <policy> <insert>
    <rule_number>
    -- OR -- 

config:# security ipAccessControl ipv6 rule add <insert> <rule_number> <ip_mask> <policy> 

Variables:

• is the combination of the IP address and subnet mask values, which are separated with a slash. For example, an IPv4 combination looks like this: 192.168.94.222/24.
• is one of the options: accept, drop or reject.

Policy Description
accept Accepts	traffic from the specified IP address(es).
drop Discards	traffic from the specified IP address(es), without sending any failure notification to the source host.
reject Discards	traffic from the specified IP address(es), and an ICMP message is sent to the source host for failure notification.

- is one of the options: insertAbove or insertBelow.

Option Description

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

- is the number of the existing rule which you want to insert the new rule above or below.

Example

The following command adds a new IPv4 access control rule and specifies its location in the list.

config:# security ipAccessControl ipv4 rule add 192.168.84.123/24 accept insertAbove 5

Results:

• A new IPv4 firewall control rule is added, allowing all packets from the IPv4 address 192.168.84.123 to be accepted.
• The newly-added rule is inserted above the 5th rule. That is, the new rule becomes the 5th rule, and the original 5th rule becomes the 6th rule.

Modifying a Firewall Rule

Depending on what to modify in an existing rule, the command syntax varies.

- IPv4 commands

The command syntax to modify an IPv4 rule's IP address and/or subnet mask:

config:# security ipAccessControl ipv4 rule modify ipMask

The command syntax to modify an IPv4 rule's policy:

Chapter 7: Using the Command Line Interface

config:# security ipAccessControl ipv4 rule modify <rule_number> policy <policy> 

The command syntax to modify all contents of an existing IPv4 rule:

config:# security ipAccessControl ipv4 rule modify <rule_number> ipMask <ip_mask> policy <policy> 

- IPv6 commands

The command syntax to modify an IPv6 rule's IP address and/or subnet mask:

config:# security ipAccessControl ipv6 rule modify <rule_number> ipMask <ip_mask> 

The command syntax to modify an IPv6 rule's policy:

config:# security ipAccessControl ipv6 rule modify <rule_number> policy
<policy> 

The command syntax to modify all contents of an IPv6 existing rule:

config:# security ipAccessControl ipv6 rule modify <rule_number> ipMask <ip_mask> policy <policy> 

Variables:

• is the number of the existing rule that you want to modify.
• is the combination of the IP address and subnet mask values, which are separated with a slash. For example, an IPv4 combination looks like this: 192.168.94.222/24.
• is one of the options: accept, drop or reject.

Option Description

accept

Accepts traffic from the specified IP address(es).

drop	Discards traffic from the specified IP address(es), without sending any failure notification to the source host.

Option Description

reject

Discards traffic from the specified IP address(es), and an ICMP message is sent to the source host for failure notification.

Example

The following command modifies all contents of the 5th IPv4 rule.

config:# security ipAccessControl ipv4 rule modify 5 ipMask 192.168.84.123/24 policy accept

Results:

• The IPv4 address is changed to 192.168.84.123, and the subnet mask to 255.255.255.0.
• The policy now becomes "accept."

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

- IPv6 commands

config:# security ipAccessControl ipv6 rule delete

Variables:

- is the number of the existing rule that you want to remove.

Example

The following command removes the 5th rule from the IPv6 access control list.

config:# security ipAccessControl ipv6 rule delete 5

HTTPS Access

This command determines whether the HTTPS access to the Dominion PX web interface is forced. If yes, all HTTP access attempts are automatically directed to HTTPS.

config:# security enforceHttpsForWebAccess

Variables:

- is one of the options: enable or disable.

Option Description

enable Enables the HTTPS access to the web interface.

disable Disables the HTTPS access to the web interface.

Example

The following command disables the HTTPS access feature.

config:# security enforceHttpsForWebAccess disable

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 being forced to log out.

A login limitation command begins with security loginLimits.

You can combine multiple commands to modify the login limitation parameters at a time. See Multi-Command Syntax (on page 373).

Single Login Limitation

This command syntax enables or disables the single login feature, which controls whether multiple logins using the same login name simultaneously is permitted.

config:# security loginLimits singleLogin

Variables:

- is one of the options: enable or disable.

Option Description

enable	Enables	the single login feature.
disable	Disables	the single login feature.

Example

The following command disables the single login feature so that more than one user can log in using the same user name at the same time.

config:# security loginLimits singleLogin disable

Password Aging

This command syntax enables or disables the password aging feature, which controls whether the password should be changed at a regular interval:

config:# security loginLimits passwordAging

Variables:

- is one of the options: enable or disable.

Option Description

enable	Enables	the password aging feature.
disable	Disables	the password aging feature.

Example

The following command enables the password aging feature.

config:# security loginLimits passwordAging enable

Password Aging Interval

This command syntax determines how often the password should be changed.

config:# security loginLimits passwordAgingInterval

Variables:

- is a numeric value in days set for the password aging interval. The interval ranges from 7 to 365 days.

Example

The following command sets the password again interval to 90 days.

config:# security loginLimits passwordAgingInterval 90

Idle Timeout

This command syntax determines how long a user can remain idle before that user is forced to log out of the Dominion PX web interface.

config:# security loginLimits idleTimeout

Variables:

- is a numeric value in minutes set for the idle timeout. The timeout ranges from 1 to 1440 minutes (24 hours).

Example

The following command sets the idle timeout to 10 munites.

config:# security loginLimits idleTimeout 10

User Blocking

There are different commands for changing different user blocking parameters. These commands begin with security userBlocking.

To determine the maximum number of failed logins before blocking a user, use this command syntax:

config:# security userBlocking maximumNumberOfFailedLogins

To determine how long a user's login is blocked, use this command syntax:

config:# security userBlocking blockTime

Variables:

• is an integer between 3 and 10, or unlimited, which sets no limit on the maximum number of failed logins and thus disables the user blocking function.
• is a numeric value in minutes.

Tip: You can combine multiple commands to modify the user blocking parameters at a time. See Multi-Command Syntax (on page 373).

Example

The following command sets up two user blocking parameters.

config:# security userBlocking maximumNumberOfFailedLogins 5 blockTime 30

Results:

• The maximum number of failed logins is set to 5.
• The user blocking time is set to 30 minutes.

Strong Passwords

The strong password commands determine whether a strong password is required for login, and what a strong password should contain at least.

A strong password command begins with security strongPasswords.

You can combine multiple strong password commands to modify different parameters at a time. See Multi-Command Syntax (on page 373).

Enabling or Disabling Strong Passwords

This command syntax enables or disables the strong password feature.

config:# security strongPasswords enabled

Variables:

- is one of the options: true or false.

Option Description

true Enables the strong password feature.

false Disables the strong password feature.

Example

This command syntax enables the strong password feature.

config:# security strongPasswords enabled true

Minimum Password Length

This command syntax determines the minimum length of the password.

config:# security strongPasswords minimumLength

Variables:

- is an integer between 8 and 32.

Example

This command syntax determines a password must comprise at least 8 characters.

config:# security strongPasswords minimumLength 8

Maximum Password Length

This command syntax determines the maximum length of the password.

config:# security strongPasswords maximumLength

Variables:

- is an integer between 16 and 64.

Example

This command syntax determines that a password must NOT comprise more than 20 characters.

config:# security strongPasswords maximumLength 20

Lowercase Character Requirement

This command syntax determines whether a strong password includes at least a lowercase character.

config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter

Variables:

- is one of the options: enable or disable.

Option Description

enable At least one lowercase character is required.

disable No lowercase character is required.

Example

This command syntax determines that a password must include at least a lowercase character.

config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter enable

Uppercase Character Requirement

This command syntax determines whether a strong password includes at least a uppercase character.

config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter

Variables:

- is one of the options: enable or disable.

Option Description

enable At least one uppercase character is required.

disable No uppercase character is required.

Example

This command determines a password must comprise at least one uppercase character.

config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter enable

Numeric Character Requirement

This command syntax determines whether a strong password includes at least a numeric character.

config:# security strongPasswords enforceAtLeastOneNumericCharacter

Variables:

- is one of the options: enable or disable.

Option Description

enable At least one numeric character is required.

disable No numeric character is required.

Example

The following command determines that a password must comprise at least one numeric character.

config:# security strongPasswords enforceAtLeastOneNumericCharacter enable

Special Character Requirement

This command syntax determines whether a strong password includes at least a special character.

config:# security strongPasswords enforceAtLeastOneSpecialCharacter

Variables:

- is one of the options: enable or disable.

Option Description

enable At least one special character is required.

disable No special character is required.

Example

The following command determines that a password must comprise at least one special character.

config:# security strongPasswords enforceAtLeastOneSpecialCharacter enable

Maximum Password History

This command syntax determines the number of previous passwords that CANNOT be repeated when changing the password.

config:# security strongPasswords passwordHistoryDepth

Variables:

- is an integer between 1 and 12.

Example

The following command determines that the previous 7 passwords CANNOT be re-used when changing the password.

config:# security strongPasswords passwordHistoryDepth 7

Role-Bassed Access Control

In addition to firewall access control based on IP addresses, you can configure other access control rules that 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 the Role-Based Access Control Parameters

There are different commands for modifying role-based access control parameters.

- IPv4 commands

To enable or disable the IPv4 role-based access control feature, use this command syntax:

config:# security roleBasedAccessControl ipv4 enabled

To determine the IPv4 role-based access control policy, use this command syntax:

config:# security roleBasedAccessControl ipv4 defaultPolicy

- IPv6 commands

To enable or disable the IPv6 role-based access control feature, use this command syntax:

config:# security roleBasedAccessControl ipv6 enabled

To determine the IPv6 role-based access control policy, use this command syntax:

config:# security roleBasedAccessControl ipv6 defaultPolicy

Variables:

- is one of the options: true or false.

Option Description

true Enables the role-based access control feature. false Disables the role-based access control feature.

- is one of the options: allow or deny.

Policy Description

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. See Multi-Command Syntax (on page 373).

Example

The following command sets two parameters of the role-based IPv4 access control feature.

config:# security roleBasedAccessControl ipv4 enabled true defaultPolicy allow

Results:

• The role-based IPv4 access control feature is enabled.
• The default policy is set to "allow."

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 rule varies.

• IPv4 commands
  To add a new rule to the bottom of the IPv4 rules list, use this command syntax:

config:# security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip> <role>
<policy> 

To add a new IPv4 rule by inserting it above or below a specific rule, use this command syntax:

config:# security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip> <role>
<policy> <insert> <rule_number> 

- IPv6 commands

To add a new rule to the bottom of the IPv6 rules list, use this command syntax:

config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role>
<policy> 

To add a new IPv6 rule by inserting it above or below a specific rule, use this command syntax:

config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role>
<policy> <insert> <rule_number> 

Variables:

• is the starting IP address.
• is the ending IP address.
• is the role for which you want to create an access control rule.
• is one of the options: allow or deny.

Policy Description

allow Accepts traffic from the specified IP address range when the user is a member of the specified role

deny Drops traffic from the specified IP address range when the user is a member of the specified role

- is one of the options: insertAbove or insertBelow.

Option Description

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

- is the number of the existing rule which you want to insert the new rule above or below.

Example

The following command creates a newIPv4 role-based access control rule and specifies its location in the list.

config:# security roleBasedAccessControl ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertAbove 3

Results:

• A new IPv4 role-based access control rule is added, dropping all packets from any IPv4 address between 192.168.78.50 and 192.168.90.100 when the user is a member of the role "admin."
• The newly-added IPv4 rule is inserted above the 3rd rule. That is, the new rule becomes the 3rd rule, and the original 3rd rule becomes the 4th rule.

Modifying a Role-Based Access Control Rule

Depending on what to modify in an existing rule, the command syntax varies.

- IPv4 commands

To modify a rule's IPv4 address range, use this command syntax:

config:# security roleBasedAccessControl ipv4 rule modify startIpAddress endIpAddress

To modify an IPv4 rule's role, use this command syntax:

Chapter 7: Using the Command Line Interface

config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role <role> 

To modify an IPv4 rule's policy, use this command syntax:

config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy <policy> 

To modify all contents of an existing IPv4 rule, use this command syntax:

config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> 

- IPv6 commands

To modify a rule's IPv6 address range, use this command syntax:

config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> 

To modify an IPv6 rule's role, use this command syntax:

config:# security roleBasedAccessControl ipv6 rule modify <rule_number> role <role> 

To modify an IPv6 rule's policy, use this command syntax:

config:# security roleBasedAccessControl ipv6 rule modify <rule_number> policy <policy> 

To modify all contents of an existing IPv6 rule, use this command syntax:

config:# security roleBasedAccessControl ipv6 rule modify startIpAddress endIpAddress role policy

Variables:

• is the number of the existing rule that you want to modify.
• is the starting IP address.
• is the ending IP address.
• is one of the existing roles.
• is one of the options: allow or deny.

Policy Description

allow Accepts traffic from the specified IP address rangewhen the user is a member of the specified role

deny Drops traffic from the specified IP address rangewhen the user is a member of the specified role

Example

The following command modifies all contents of the 8th IPv4 rule.

config:# security roleBasedAccessControl ipv4 rule modify 8 startIpAddress 192.168.8.8 endIpAddress 192.168.90.90 role operator policy allow

Results:

• The starting IPv4 address is changed to 192.168.8.8, and the ending IPv4 address to 192.168.90.90.
• The role is changed to "operator."
• The policy now becomes "allow."

Deleting a Role-Based Access Control Rule

This command removes a specific rule from the list.

- IPv4 commands

config:# security roleBasedAccessControl ipv4 rule delete

- IPv6 commands

config:# security roleBasedAccessControl ipv6 rule delete

Variables:

- is the number of the existing rule that you want to remove.

Example

The following command removes the 7th IPv6 rule.

config:# security roleBasedAccessControl ipv6 rule delete 7

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 syntax names an outlet.

config:# outlet name ""

Variables:

• is the number of the outlet that you want to configure.
• is a string comprising up to 32 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Example

The following command assigns the name "Win XP" to outlet 8.

config:# outlet 8 name "Win XP"

Changing an Outlet's Default State

This section only applies to outlet-switching capable PDUs.

This command syntax determines the initial power condition of an outlet after the PDU powers up.

config:# outlet stateOnDeviceStartup

Variables:

• is the number of the outlet that you want to configure.
• is one of the options: off, on, lastKnownState and pduDefined.

Option Description
off Switches OFF	the outlet when the Dominion PX device powers up.
on Switches ON	the outlet when the Dominion PX device powers up.
lastKnownState	Restores the outlet to the previous status before the Dominion PX device powered down when powering up the PDU.
pduDefined	Determines the outlet's default state according to the 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. See Setting the PDU-Defined Default Outlet State (on page 256).

Example

The following command makes the outlet 8 return to the last power state before powering down the PDU, after you power it up again.

config:# outlet 8 stateOnDeviceStartup lastKnownState

Setting an Outlet's Cycling Power-Off Period

This section only applies to outlet-switching capable PDUs.

This command syntax determines the power-off period of the power cycling operation for a specific outlet.

config:# outlet cyclingPowerOffPeriod

Variables:

• is the number of the outlet that you want to configure.
• is the time of the cycling power-off period in seconds, which is an integer between 0 and 3600.

Note: This setting overrides the PDU-defined cycling power-off period on a particular outlet. See Setting the PDU-Defined Cycling Power-Off Period (on page 257).

Example

The following command sets the power off period of outlet 8 to 3 seconds when the power cycling operation is performed.

config:# outlet 8 cyclingPowerOffPeriod 3

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 name ""

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always the number 1. The value is an integer between 1 and 50.
• is a string comprising up to 32 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Example

The following command assigns the name "AC source" to the inlet 1. If your Dominion PX device contains multiple inlets, this command names the 1st inlet.

config:# inlet 1 name "AC source"

Circuit Breaker Configuration Commands

A circuit breaker configuration command begins with ocp. The command configures an individual circuit breaker.

Changing the Circuit Breaker Name

This command syntax names a circuit breaker.

config:# ocp name ""

Variables:

• is the number of the circuit breaker that you want to configure. The value is an integer between 1 and 50.
• is a string comprising up to 32 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Example

The command assigns the name "Email servers CB" to the circuit breaker 3.

config:# ocp 3 name "Email servers CB"

Environmental Sensor Configuration Commands

An environmental sensor configuration command begins with externalsensor. You can configure the name and location parameters of an individual environmental sensor.

Changing the Sensor Name

This command syntax names an environmental sensor.

config:# externalsensor name ""

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is a string comprising up to 32 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Example

The following command assigns the name "Cabinet humidity" to the environmental sensor with the ID number 4.

config:#externalsensor4name"Cabinethumidity"

Specifying the Sensor Type

Raritan's contact closure sensor (DPX-CC2-TR) supports the connection of diverse third-party detectors/switches, and you must specify the type of connected detector/switch for proper operation. Use this command syntax when you need to specify the sensor type.

config:#externalsensor sensorSubType

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is one of these types: contact, smokeDetection, waterDetection or vibration.

Type Description
contact The connected detector/switch is for detection of door lock or door closed/open status.
smokeDetection	The connected detector/switch is for detection of the smoke presence.
waterDetection	The connected detector/switch is for detection of the water presence.
vibration The connected detector/switch is for detection of the vibration.

Example

The following indicates that a smoke detector is being connected to Raritan's contact closure sensor (DPX-CC2-TR) whose ID number shown in the Dominion PX web interface is 2.

config:#externalsensor2sensorSubType smokeDetection

Setting the X Coordinate

This command syntax specifies the X coordinate of an environmental sensor.

config:# externalsensor xlabel ""

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.

Example

The following command sets the value "The 2nd cabinet" to the X coordinate of the environmental sensor with the ID number 4.

config:#externalsensor4xlabel"The2ndcabinet"

Setting the Y Coordinate

This command syntax specifies the Y coordinate of an environmental sensor.

config:# externalsensor ylabel ""

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.

Example

The following command sets the value "The 4th row" to the Y coordinate of the environmental sensor with the ID number 4.

config:#externalsensor4ylabel"The4throw"

Setting the Z Coordinate

This command syntax specifies the Z coordinate of an environmental sensor.

config:# externalsensor zlabel ""

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• Depending on the Z coordinate format you set, there are two types of values for the variable:

Type Description

Free formis a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.

Rack unitsis an integer number in rack units.

Note: To specify the Z coordinate using the rack units. See Setting the Z Coordinate Format for Environmental Sensors (on page 261).

Example

The following command sets the value "The 5th rack" to the Z coordinate of the environmental sensor with the ID number 4 after the Z coordinate's format is set to freeForm.

config:#externalsensor4zlabel"The5thrack"

Changing the Sensor Description

This command syntax provides a description for a specific environmental sensor.

config:# externalsensor description ""

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is a string comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.

Example

The following command gives the description "humidity detection" to the environmental sensor with the ID number 4.

config:# externalsensor 4 description "humidity detection"

Sensor Threshold Configuration Commands

A sensor configuration command begins with sensor. You can use the commands to configure the threshold, hysteresis and assertion timeout values for any sensor associated with the following items:

Inlets
- Inlet poles (for three-phase PDUs only)
- Circuit breakers
■ Environmental sensors

It is permitted to assign a new value to the threshold at any time regardless of whether the threshold is being enabled.

Commands for Inlet Sensors

A sensor configuration command for inlets begins with sensor inlet.

Setting the Inlet's Upper Critical Threshold

This command syntax configures the Upper Critical threshold of an inlet.

config:# sensor inlet upperCritical

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always the number 1.
• 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the upper critical threshold for the specified inlet sensor.
disable Disables	the upper critical threshold for the specified inlet sensor.
A numeric value	Sets a value for the upper critical threshold of the specified inlet sensor and enables this threshold at the same time.

Example

The following command enables the Upper Critical threshold for the inlet 1 RMS current.

config:# sensor inlet 1 current upperCritical enable

Setting the Inlet's Upper Warning Threshold

This command syntax configures the Upper Warning threshold of an inlet.

config:# sensor inlet upperWarning

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always the number 1.
• 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description

enable Enables	the upper warning threshold for the specified inlet sensor.
disable	Disables the upper warning threshold for the specified inlet sensor.
A numeric value	Sets a value for the upper warning threshold of the specified inlet sensor and enables this threshold at the same time.

Example

The following command sets the Upper Warning threshold for the inlet 1 RMS current to 12A. It also enables the upper warning threshold if this threshold has not been enabled yet.

config:# sensor inlet 1 current upperWarning 12

Setting the Inlet's Lower Critical Threshold

This command syntax configures the Lower Critical threshold of an inlet.

config:# sensor inlet lowerCritical

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always the number 1.
• 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the lower critical threshold for the specified inlet sensor.
disable Disables	the lower critical threshold for the specified inlet sensor.
A numeric value	Sets a value for the lower critical threshold of the specified inlet sensor and enables this threshold at the same time.

Example

The following command disables the Lower Critical threshold for the inlet 1 RMS current.

config:# sensor inlet 1 current lowerCritical disable

Setting the Inlet's Lower Warning Threshold

This command syntax configures the Lower Warning threshold of an inlet.

config:# sensor inlet lowerWarning

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always the number 1.
• 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description

enable Enables	the lower warning threshold for the specified inlet sensor.
disable	Disables the lower warning threshold for the specified inlet sensor.
A numeric value	Sets a value for the lower warning threshold of the specified inlet sensor and enables this threshold at the same time.

Example

The following command sets the Lower Warning threshold for the inlet 1 RMS current to 20A. It also enables the lower warning threshold if this threshold has not been enabled yet.

config:# sensor inlet 1 current lowerWarning 20

Setting the Inlet's Deassertion Hysteresis

This command syntax configures the deassertion hysteresis value of an inlet.

config:# sensor inlet hysteresis

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always the number 1.
• 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is a numeric value that is assigned to the hysteresis for the specified inlet sensor. See What is Deassertion Hysteresis? (on page 153) for the function of the deassertion hysteresis.

Example

The following command sets the deassertion hysteresis for the inlet 1 RMS current to 0.2A. That is, the current must drop by at least 0.2A below the upper threshold or rise by at least 0.2A above the lower threshold before any threshold-crossing event is deasserted.

config:# sensor inlet 1 current hysteresis 0.2

Setting the Inlet's Assertion Timeout

This command syntax configures the assertion timeout value of an inlet.

config:# sensor inlet assertionTimeout

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always the number 1.
• 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is a number in samples that is assigned to the assertion timeout for the specified inlet sensor. See What is Assertion Timeout? (on page 154).

Example

The following command sets the assertion timeout value of the inlet 1 RMS current to 4 samples. That is, at least 4 consecutive samples must cross a specific current threshold before that threshold-crossing event is asserted.

config:# sensor inlet 1 current assertionTimeout 4

Commands for Inlet Pole Sensors

A sensor configuration command for inlet poles begins with sensor inletpole. This type of command is available on a three-phase PDU only.

Setting the Upper Critical Threshold for an Inlet Pole

This command syntax configures the Upper Critical threshold of an inlet pole.

config:# sensor inletpole

upperCritical

Variables:

• is the number of the inlet whose pole sensors you want to configure.

• is the label of the inlet pole that you want to configure.

Pole Label		Current sensor Voltage sensor
1	L1	L1 L1 - L2
2	L2	L2 L2 - L3
3	L3	L3 L3 - L1

- 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the upper critical threshold for the specified inlet pole sensor.
disable	Disables the upper critical threshold for the specified inlet pole sensor.

Option Description

A numeric value

Sets a value for the upper critical threshold of the specified inlet pole sensor and enables this threshold at the same time.

Example

The following command disables the Upper Critical threshold for the pole 3 (L3-L1) voltage of the inlet 1.

config:# sensor inletpole 1 L3 voltage upperCritical disable

Setting the Upper Warning Threshold for an Inlet Pole

This command syntax configures the Upper Warning threshold of an inlet pole.

config:# sensor inletpole

upperWarning

Variables:

• is the number of the inlet whose pole sensors you want to configure.

• is the label of the inlet pole that you want to configure.

Pole Label		Current sensor Voltage sensor
1	L1	L1 L1 - L2
2	L2	L2 L2 - L3
3	L3	L3 L3 - L1

- 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the upper warning threshold for the specified inlet pole sensor.
disable Disables	the upper warning threshold for the specified inlet pole sensor.
A numeric value	Sets a value for the upper warning threshold of the specified inlet pole sensor and enables this threshold at the same time.

Example

The following command sets the Upper Warning threshold for the pole 2 (L2-L3) voltage of the inlet 1 to 180V. It also enables the upper warning threshold if this threshold has not been enabled yet.

config:# sensor inletpole 1 L2 voltage upperWarning 180

Setting the Lower Critical Threshold for an Inlet Pole

This command syntax configures the Lower Critical threshold of an inlet pole.

config:# sensor inletpole

lowerCritical

Variables:

• is the number of the inlet whose pole sensors you want to configure.

• is the label of the inlet pole that you want to configure.

Pole Label		Current sensor Voltage sensor
1	L1	L1 L1 - L2
2	L2	L2 L2 - L3
3	L3	L3 L3 - L1

- 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the lower critical threshold for the specified inlet pole sensor.
disable Disables	the lower critical threshold for the specified inlet pole sensor.
A numeric value	Sets a value for the lower critical threshold of the specified inlet pole sensor and enables this threshold at the same time.

Example

The following command enables the Lower Critical threshold for the pole 2 (L2-L3) voltage of the inlet 1.

config:# sensor inletpole 1 L2 voltage lowerCritical enable

Setting the Lower Warning Threshold for an Inlet Pole

This command syntax configures the Lower Warning threshold of an inlet pole.

config:# sensor inletpole

lowerWarning

Variables:

• is the number of the inlet whose pole sensors you want to configure.

• is the label of the inlet pole that you want to configure.

Pole Label		Current sensor Voltage sensor
1	L1	L1 L1 - L2
2	L2	L2 L2 - L3
3	L3	L3 L3 - L1

- 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the lower warning threshold for the specified inlet pole sensor.
disable	Disables the lower warning threshold for the specified inlet pole sensor.
A numeric value	Sets a value for the lower warning threshold of the specified inlet pole sensor and enables this threshold at the same time.

Example

The following command sets the Lower Warning threshold for the pole 3 (L3-L1) voltage of the inlet 1 to 190V. It also enables the lower warning threshold if this threshold has not been enabled yet.

config:# sensor inletpole 1 L3 voltage lowerWarning 190

Setting the Inlet Pole's Deassertion Hysteresis

This command syntax configures the deassertion hysteresis value of an inlet pole.

config:# sensor inletpole

hysteresis

Variables:

• is the number of the inlet whose pole sensors you want to configure.

• is the label of the inlet pole that you want to configure.

Pole Label		Current sensor Voltage sensor
1	L1	L1 L1 - L2
2	L2	L2 L2 - L3
3	L3	L3 L3 - L1

- 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is a numeric value that is assigned to the hysteresis for the specified inlet pole sensor. See What is Deassertion Hysteresis? (on page 153) for the function of the deassertion hysteresis.

Example

The following command sets the deassertion hysteresis of the pole 2 (L2) current of the inlet 1 to 0.2A. That is, the current must drop by at least 0.2A below the upper threshold or rise by at least 0.2A above the lower threshold before any threshold-crossing event is deasserted.

config:# sensor inletpole 1 L2 current hysteresis 0.2

Setting the Inlet Pole's Assertion Timeout

This command syntax configures the assertion timeout value of an inlet pole.

config:# sensor inletpole

assertionTimeout

Variables:

• is the number of the inlet whose pole sensors you want to configure.

• is the label of the inlet pole that you want to configure.

Pole Label		Current sensor Voltage sensor
1	L1	L1 L1 - L2
2	L2	L2 L2 - L3
3	L3	L3 L3 - L1

- 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

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is a number in samples that is assigned to the assertion timeout for the specified inlet pole sensor. See What is Assertion Timeout? (on page 154).

Example

The following command sets the assertion timeout value of the pole 2 (L2) current of the inlet 1 to 4 samples. That is, at least 4 consecutive samples must cross a specific current threshold before that threshold-crossing event is asserted.

config:# sensor inletpole 1 L2 current assertionTimeout 4

Commands for Circuit Breaker Sensors

A sensor configuration command for circuit breakers begins with sensor ocp.

Setting the Upper Critical Threshold for a Circuit Breaker

This command syntax configures the Upper Critical threshold of a circuit breaker.

config:# sensor ocp upperCritical

Variables:

• is the number of the circuit breaker that you want to configure.
• is one of the following sensor types:

Sensor type Description

current

Current

sensor

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description

enable

Enables

the upper critical threshold for the specified circuit breaker sensor.

Option Description
disable Disables	the upper critical threshold for the specified circuit breaker sensor.
A numeric value	Sets a value for the upper critical threshold of the specified circuit breaker sensor and enables this threshold at the same time.

Example

The following command sets the Upper Critical threshold for the 3rd circuit breaker to 16A. It also enables the upper critical threshold if this threshold has not been enabled yet.

config:# sensor ocp 3 current upperCritical 16

Setting the Upper Warning Threshold for a Circuit Breaker

This command syntax configures the Upper Warning threshold of a circuit breaker.

config:# sensor ocp upperWarning

Variables:

• is the number of the circuit breaker that you want to configure.
• is one of the following sensor types:

Sensor type Description
current	Current	sensor

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the upper warning threshold for the specified circuit breaker sensor.
disable Disables	the upper warning threshold for the specified circuit breaker sensor.
A numeric value	Sets a value for the upper warning threshold of the specified circuit breaker sensor and enables this threshold at the same time.

Example

The following command enables the Upper Warning threshold for the 3rd circuit breaker.

config:# sensor ocp 3 current upperWarning enable

Setting the Lower Critical Threshold for a Circuit Breaker

This command syntax configures the Lower Critical threshold of a circuit breaker.

config:# sensor ocp lowerCritical

Variables:

• is the number of the circuit breaker that you want to configure.
• is one of the following sensor types:

Sensor type Description
current	Current	sensor

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the lower critical threshold for the specified circuit breaker sensor.
disable Disables	the lower critical threshold for the specified circuit breaker sensor.
A numeric value	Sets a value for the lower critical threshold of the specified circuit breaker sensor and enables this threshold at the same time.

Example

The following command sets the Lower Critical threshold for the 3rd circuit breaker to 5A. It also enables the lower critical threshold if this threshold has not been enabled yet.

config:# sensor ocp 3 current lowerCritical 5

Setting the Lower Warning Threshold for a Circuit Breaker

This command syntax configures the Lower Warning threshold of a circuit breaker.

config:# sensor ocp lowerWarning

Variables:

• is the number of the circuit breaker that you want to configure.
• is one of the following sensor types:

Sensor type Description

current

Current

sensor

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description

enable Enables	the lower warning threshold for the specified circuit breaker sensor.
disable Disables	the lower warning threshold for the specified circuit breaker sensor.
A numeric value	Sets a value for the lower warning threshold of the specified circuit breaker sensor and enables this threshold at the same time.

Example

The following command enables the Lower Warning threshold for the 3rd circuit breaker.

config:# sensor ocp 3 current lowerWarning enable

Setting the Circuit Breaker's Deassertion Hysteresis

This command syntax configures the deassertion hysteresis value of a circuit breaker.

config:# sensor ocp hysteresis

Variables:

• is the number of the circuit breaker that you want to configure.
• is one of the following sensor types:

Sensor type Description

current

Current

sensor

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is a numeric value that is assigned to the hysteresis of the specified circuit breaker sensor. See What is Deassertion Hysteresis? (on page 153) for the function of the deassertion hysteresis.

Example

The following command sets the deassertion hysteresis of the RMS current of the 3rd circuit breaker to 0.2A. That is, the current must drop by at least 0.2A below the upper threshold or rise by at least 0.2A above the lower threshold before any threshold-crossing event is deasserted.

config:# sensor ocp 3 current hysteresis 0.2

Setting the Circuit Breaker's Assertion Timeout

This command syntax configures the assertion timeout value of a circuit breaker.

config:# sensor ocp assertionTimeout

Variables:

• is the number of the circuit breaker that you want to configure.
• is one of the following sensor types:

Sensor type Description

current

Current

sensor

Note: If the requested sensor type is not supported, the message "Not available" is displayed.

- is a number in samples that is assigned to the assertion timeout of the specified circuit breaker sensor. See What is Assertion Timeout? (on page 154).

Example

The following command sets the assertion timeout value of the RMS current of the 3rd circuit breaker to 4 samples. That is, at least 4 consecutive samples must cross a specific current threshold before that threshold-crossing event is asserted.

config:# sensor ocp 3 current assertionTimeout 4

Commands for Environmental Sensors

A sensor threshold configuration command for environmental sensors begins with sensor externalsensor.

Setting the Sensor's Upper Critical Threshold

This command syntax configures the Upper Critical threshold of a numeric environmental sensor.

config:# sensor externalsensor upperCritical

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is one of these sensor types: temperature, humidity, airPressure or air Flow.

Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears: "Specified sensor type 'XXX' does not match the sensor's type ()," where XXX is the specified sensor type, and is the correct sensor type.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the upper critical threshold for the specified environmental sensor.
disable Disables	the upper critical threshold for the specified environmental sensor.
A numeric value	Sets a value for the upper critical threshold of the specified environmental sensor and enables this threshold at the same time.

Example

The following command sets the Upper Critical threshold of the environmental "temperature" sensor with the ID number 2 to 40 degrees Celsius. It also enables the upper critical threshold if this threshold has not been enabled yet.

config:# sensor externalsensor 2 temperature upperCritical 40

Setting the Sensor's Upper Warning Threshold

This command syntax configures the Upper Warning threshold of a numeric environmental sensor.

config:# sensor externalsensor upperWarning

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is one of these sensor types: temperature, humidity, airPressure or air Flow.

Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears: "Specified sensor type 'XXX' does not match the sensor's type ()," where XXX is the specified sensor type, and is the correct sensor type.

- is one of the options: enable, disable or a numeric value.

Option Description

enable Enables the upper warning threshold for the specified environmental sensor.

Option Description
disable Disables	the upper warning threshold for the specified environmental sensor.
A numeric value	Sets a value for the upper warning threshold of the specified environmental sensor and enables this threshold at the same time.

Example

The following command enables the Upper Warning threshold of the environmental "temperature" sensor with the ID number 4.

config:# sensor externalsensor 4 temperature upperWarning enable

Setting the Sensor's Lower Critical Threshold

This command syntax configures the Lower Critical threshold of a numeric environmental sensor.

config:# sensor externalsensor lowerCritical

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is one of these sensor types: temperature, humidity, airPressure or air Flow.

Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears: "Specified sensor type 'XXX' does not match the sensor's type ()," where XXX is the specified sensor type, and is the correct sensor type.

- is one of the options: enable, disable or a numeric value.

Option Description

enable Enables	the lower critical threshold for the specified environmental sensor.
disable Disables	the lower critical threshold for the specified environmental sensor.
A numeric value	Sets a value for the lower critical threshold of the specified environmental sensor and enables this threshold at the same time.

Example

The following command sets the Lower Critical threshold of the environmental "humidity" sensor with the ID number 1 to 15%. It also enables the lower critical threshold if this threshold has not been enabled yet.

config:# sensor externalsensor 1 humidity lowerCritical 15

Setting the Sensor's Lower Warning Threshold

This command syntax configures the Lower Warning threshold of a numeric environmental sensor.

config:# sensor externalsensor lowerWarning

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is one of these sensor types: temperature, humidity, airPressure or air Flow.

Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears: "Specified sensor type 'XXX' does not match the sensor's type ()," where XXX is the specified sensor type, and is the correct sensor type.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the lower warning threshold for the specified environmental sensor.
disable Disables	the lower warning threshold for the specified environmental sensor.
A numeric value	Sets a value for the lower warning threshold of the specified environmental sensor and enables this threshold at the same time.

Example

The following command disables the Lower Warning threshold of the environmental "humidity" sensor with the ID number 3.

config:# sensor externalsensor 3 humidity lowerWarning disable

Setting the Sensor's Deassertion Hysteresis

This command syntax configures the deassertion hysteresis value of a numeric environmental sensor.

config:# sensor externalsensor hysteresis

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is one of these sensor types: temperature, humidity, airPressure or air Flow.

Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears: "Specified sensor type 'XXX' does not match the sensor's type ()," where XXX is the specified sensor type, and is the correct sensor type.

- is a numeric value that is assigned to the hysteresis for the specified environmental sensor. See What is Deassertion Hysteresis? (on page 153) for the function of the deassertion hysteresis.

Example

The following command sets the deassertion hysteresis of the environmental "temperature" sensor with the ID number 4 to 2 degrees Celsius. That is, the temperature must drop by at least 2 degrees Celsius below the upper threshold or rise by at least 2 degrees Celsius above the lower threshold before any threshold-crossing event is deasserted.

config:# sensor externalsensor 4 temperature hysteresis 2

Setting the Sensor's Assertion Timeout

This command syntax configures the assertion timeout value of a numeric environmental sensor.

config:# sensor externalsensor assertionTimeout

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the Dominion PX web interface. It is an integer between 1 and 16.
• is one of these sensor types: temperature, humidity, airPressure or air Flow.

Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears: "Specified sensor type 'XXX' does not match the sensor's type ()," where XXX is the specified sensor type, and is the correct sensor type.

- is a number in samples that is assigned to the assertion timeout for the specified environmental sensor. See What is Assertion Timeout? (on page 154).

Example

The following command sets the assertion timeout of the environmental "temperature" sensor with the ID number 3 to 4 samples. That is, at least 4 consecutive samples must cross a specific current threshold before that threshold-crossing event is asserted.

config:# sensor externalsensor 3 temperature assertionTimeout 4

User Configuration Commands

Most of user configuration commands begin with user except for the password change command.

Creating a User Profile

This command syntax creates a new user profile.

config:# user create

After performing the user creation command, the Dominion PX 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:

• is a string comprising up to 32 ASCII printable characters. The variable CANNOT contain spaces.
• is one of the options: enable or disable.

Option Description

enable Enables the newly-created user profile.

disable Disables the newly-created user profile.

- is a role or a list of comma-separated roles assigned to the specified user profile.

Example

The following command creates a new user profile and sets two parameters for the new user.

config:# user create May enable admin

Results:

• A new user profile "May" is created.
• The new user profile is enabled.
• The admin role is assigned to the new user profile.

Modifying a User Profile

A user profile contains various parameters that you can modify.

Tip: You can combine all commands to modify the parameters of a specific user profile at a time. See Multi-Command Syntax (on page 373).

Changing a User's Password

This command syntax allows you to change an existing user's password if you have the Administrator Privileges.

config:#user modify password

After performing the above command, Dominion PX prompts you 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:

- 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. See Entering the Configuration Mode (on page 253).
2. Type the following command to change the password for the user profile "May."

config:# user modify May password

1. Type a new password when prompted, and press Enter.

2. Type the same new password and press Enter.

3. 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.

To change a user's full name, use this command syntax:

config:# user modify <name> hullName "<full_name>" 

To change a user's telephone number, use this command syntax:

config:# user modify <name> telephoneNumber "<phone_number>" 

To change a user's email address, use this command syntax:

config:# user modify <name> eMailAddress <email_address> 

Variables:

• is the name of the user whose settings you want to change.
• is a string comprising up to 32 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.
• is the phone number that can reach the specified user. The variable must be enclosed in quotes when it contains spaces.
• is the email address of the specified user.

Tip: You can combine all commands to modify the parameters of a specific user profile at a time. See Multi-Command Syntax (on page 373).

Example

The following command modifies two parameters for the user profile -- May:

config:# user modify May fullName "May Turner" telephoneNumber 123-4567

Results:

• May's full name is specified as May Turner.
• May's telephone number is set to 123-4567.

Enabling or Disabling a User Profile

This command syntax enables or disables a user profile. A user can log in to the Dominion PX device only after that user's user profile is enabled.

config:#user modify enabled

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: true or false.

Option Description

true Enables the specified user profile. false Disables the specified user profile.

Example

The following command enables the user profile -- May.

config:# user modify May enabled true

Forcing a Password Change

This command syntax determines whether the password change is forced when a user logs in to the specified user profile next time.

config:# user modify forcePasswordChangeOnNextLogin

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: true or false.

Option Description

true A password change is forced on the user's next login.

false No password change is forced on the user's next login.

Example

The following command enforces a password change on May's next login.

config:# user modify May forcePasswordChangeOnNextLogin true

Modifying the 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. See Multi-Command Syntax (on page 373).

To enable or disable the SNMP v3 access to Dominion PX for the specified user:

config:# user modify snmpV3Access

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: enable or disable.

Option Description

enable Enables	the SNMP v3 access permission for the specified user.
disable Disables	the SNMP v3 access permission for the specified user.

▶ To determine the security level:

config:# user modify securityLevel

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: noAuthNoPriv, authNoPriv or authPriv.

Option Description

noAuthNoPriv No authentication and no privacy.

authNoPriv Authentication and no privacy.

authPriv Authentication and privacy.

To determine whether the authentication passphrase is identical to the password:

config:# user modify userPasswordAsAuthenticationPassPhrase

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: true or false.

Option Description

true	Authentication password.	passphrase is identical to the
false	Authentication password.	passphrase is different from the

To determine the authentication passphrase:

config:# user modify authenticationPassPhrase

Variables:

• is the name of the user whose settings you want to change.
• is a string used as an authentication passphrase, comprising up to 32 ASCII printable characters.

To determine whether the privacy passphrase is identical to the authentication passphrase:

config:# user modify useAuthenticationPassPhraseAsPrivacyPassPhrase

Variables:

• is the name of the user whose settings you want to change.
• 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.

To determine the privacy passphrase:

config:# user modify privacyPassPhrase

Variables:

• is the name of the user whose settings you want to change.
• is a string used as a privacy passphrase, comprising up to 32 ASCII printable characters.

To determine the authentication protocol:

config:# user modify authenticationProtocol

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: MD5 or SHA-1.

Option Description

MD5 MD5 authentication protocol is applied. SHA-1 SHA-1 authentication protocol is applied.

To determine the privacy protocol:

config:# user modify privacyProtocol

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: DES or AES-128.

Option Description

DES DES privacy protocol is applied. AES-128 AES-128 privacy protocol is applied.

Example

The following command sets three SNMPv3 prameters of the user "May."

config:# user modify May snmpV3Access enable securityLevel authNoPriv userPasswordAsAuthenticationPassPhrase true

Results:

• The user's SNMPv3 access permission is enabled.
  • The SNMPv3 security level is authentication only, no privacy.
  • The authentication passphrase is identical to the user's password.

Changing the Role(s)

This command syntax changes the role(s) of a specific user.

config:#user modify roles

Variables:

• is the name of the user whose settings you want to change.
• is a role or a list of comma-separated roles assigned to the specified user profile.

Example

The following command assigns two roles to the user "May."

config:# user modify May roles admin, tester

Results:

- The user May has the union of all privileges of "admin" and "tester."

Changing the Measurement Units

You can change the measurement units displayed for temperatures, length, and pressure for a specific user profile. Different measurement unit commands can be combined so that you can set all measurement units at a time. To combine all commands, see Multi-Command Syntax (on page 373).

Note: The measurement unit change only applies to the web interface and command line interface.

To set the preferred temperature unit:

config:# user modify preferredTemperatureUnit

Variables:

• is the name of the user whose settings you want to change.
  • is one of the options: C or F.

Option Description

C This option displays the temperature in Celsius.

F This option displays the temperature in Fahrenheit.

To set the preferred length unit:

config:# user modify preferredLengthUnit

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: meter or feet.

Option Description

meter This option displays the length or height in meters.

feet This option displays the length or height in feet.

To set the preferred pressure unit:

config:# user modify preferredPressureUnit

Variables:

• is the name of the user whose settings you want to change.
• is one of the options: pascal or psi.

Option Description

pascal This option displays the pressure value in Pascals (Pa).

psi This option displays the pressure value in psi.

Example

The following command sets all measurement unit preferences for the user "May."

config:#user modify May preferredTemperatureUnit F preferredLengthUnit feet preferredPressureUnit psi

Results:

• The preferred temperature unit is set to Fahrenheit.
• The preferred length unit is set to feet.
• The preferred pressure unit is set to psi.

Deleting a User Profile

This command syntax deletes an existing user profile.

config:#user delete

Example

The following command deletes the user profile "May."

config:#user delete May

Changing Your Own Password

Every user can change their own password via this command syntax if they have the Change Own Password privilege. Note that this command does not begin with user.

config:# password

After performing this command, the Dominion PX prompts you to enter both current and new passwords respectively.

Important: After the password is changed successfully, the new password is effective immediately no matter you type the command "apply" or not to save the changes.

Example

This procedure changes your own password:

1. Verify that you have entered the configuration mode. See Entering the Configuration Mode (on page 253).
2. Type the following command and press Enter.

config:# password

1. Type the existing password and press Enter when the following prompt appears.

Current password:

1. Type the new password and press Enter when the following prompt appears.

Enter new password:

1. Re-type the new password for confirmation and press Enter when the following prompt appears.

Re-type new password:

Role Configuration Commands

A role configuration command begins with role.

Creating a Role

This command syntax creates a new role, with a list of semicolon-separated privileges assigned to the role.

Chapter 7: Using the Command Line Interface

config:# role create "" ; ; ...

If a specific privilege contains any arguments, that privilege should be followed by a colon and the argument(s).

config:# role create "" :,...; :,...; :,...; ...

Variables:

• is a string comprising up to 32 ASCII printable characters.
• , , and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See All Privileges (on page 356).
• , and the like are arguments set for a particular privilege. Separate a privilege and its argument with a colon.

All Privileges

This 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
adminPrivilege	Administrator
changeAssetStripConfiguration Change Asset Strip Configuration
changeAuthSettings Change Authentication Settings
changeDataTimeSettings	Change Date/Time
changeEventSetup Change Event Settings
changeExternalSensorsConfiguration	Change External Sensors Configuration
changeLhxConfiguration	Change LHX
changeNetworkSettings	Change Network
changePassword	Change Own
changePduConfiguration Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration

Privileges

Settings

Configuration

Settings

Pa

Privilege Description
changeSecuritySettings Change Security Settings
changeSnmpSettings Change SNMP Settings
changeUserSettings Change Local User Management
changeWebcamSettings Change Webcam Configuration
clearLog Clear Local Event Log
firmwareUpdate	Firmware Update
performReset Reset (Warm Start)
switchOutlet*	Switch Outlet
viewEventSetup View Event Settings
viewLog View Local Event Log
viewSecuritySettings View Security Settings
viewSnmpSettings	View SNMP
viewUserSettings	View Local User Management
viewWebcamSettings	View Webcam Snapshots and Configuration

Setting

* 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

Example

The 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).

Modifying a Role

You can modify diverse parameters of an existing role, including its privileges.

To modify a role's description:

config:# role modify description

Variables:

• is a string comprising up to 32 ASCII printable characters.
• is a description comprising alphanumeric characters. The variable must be enclosed in quotes when it contains spaces.

To add more privileges to a specific role:

config:# role modify addPrivileges ;;...

If a specific privilege contains any arguments, add a colon and the argument(s) after that privilege.

config:# role modify <name> addPrivileges
    <privilege1>:<argument1>,<argument2>...;
    <privilege2>:<argument1>,<argument2>...;
    <privilege3>:<argument1>,<argument2>...;
    ... 

Variables:

• is a string comprising up to 32 ASCII printable characters.
• , , and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See All Privileges (on page 356).
• , and the like are arguments set for a particular privilege. Separate a privilege and its argument with a colon.

To 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 that privilege.

config:# role modify <name> removePrivileges
    <privilege1>:<argument1>,<argument2>...;
    <privilege2>:<argument1>,<argument2>...;
    <privilege3>:<argument1>,<argument2>...;
    ... 

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 privileges that are not available.

Variables:

• is a string comprising up to 32 ASCII printable characters.
• , , and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See All Privileges (on page 356).
• , and the like are arguments set for a particular privilege. Separate a privilege and its argument with a colon.

Example

The following command modifies the privileges of the role "tester."

config:# role modify tester addPrivileges changeAuthSettings removePrivileges firmwareUpgrade

Results:

• The "changeAuthSettings" (Change Authentication Settings) privilege is added to the role.
• The "firmwareUpgrade" (Firmware Upgrade) privilege is removed from the role.

Deleting a Role

This command syntax deletes an existing role.

config:# role delete

Example

The following command deletes an existing role.

config:# role delete tester

EnergyWise Configuration Commands

An EnergyWise configuration command begins with energywise.

Enabling or Disabling EnergyWise

This command syntax determines whether the Cisco ^® EnergyWise endpoint implemented on the Dominion PX device is enabled.

config:# energywise enabled

Variables:

- is one of the options: true or false.

Option Description

true The Cisco EnergyWise feature is enabled.

false The Cisco EnergyWise feature is disabled.

Example

The following command enables the Cisco® EnergyWise feature.

config:# energywise enabled true

Specifying the EnergyWise Domain

This command syntax specifies to which Cisco ^® EnergyWise domain the Dominion PX device belongs.

config:# energywise domain

Variables:

- is a string comprising up to 127 ASCII printable characters. Spaces and asterisks are NOT acceptable.

Example

The following command configures the Dominion PX device to belong to the Cisco® EnergyWise domain named "helloDomain."

config:# energywise domain helloDomain

Specifying the EnergyWise Secret

This command syntax specifies the password (secret) to enter the Cisco® EnergyWise domain.

config:# energywise secret

Variables:

- is a string comprising up to 127 ASCII printable characters. Spaces and asterisks are NOT acceptable.

Example

The following command specifies "password5233" as the Cisco® EnergyWise domain secret (password).

config:# energywise secret password5233

Changing the UDP Port

This command syntax specifies the UDP port for communications in the Cisco® EnergyWise domain.

config:# energywise port

Variables:

- is the UDP port number ranging between 1 and 65535.

Example

The following command specifies 10288 as the UDP port for Cisco® EnergyWise.

config:# energywise port 10288

Setting the Polling Interval

This command syntax determines the polling interval at which the Cisco® EnergyWise domain queries the Dominion PX device.

config:# energywise polling

Variables:

- is an integer number in seconds. It ranges between 30 and 600 seconds.

Example

The following command determines the polling interval to query the Dominion PX device is 300 seconds.

config:# energywise polling 300

Asset Management Commands

You can use the CLI commands to change the settings of the connected asset sensor (if any) or the settings of LEDs on the asset sensor.

Asset Sensor Management

An asset sensor management configuration command begins with assetStrip.

Naming an Asset Sensor

This command syntax names or changes the name of an asset sensor connected to the Dominion PX device.

config:# assetStrip name ""

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is a string comprising up to 32 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Example

This command syntax names or changes the name of an asset sensor connected to the Dominion PX device.

config:# assetStrip 1 name "Red Rack"

Specifying the Number of Rack Units

This command syntax specifies the total number of rack units on an asset sensor connected to the Dominion PX device.

config:# assetStrip <n> numberOfRackUnits <number> 

Note: For the Raritan asset sensor, a rack unit refers to a tag port.

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is the total number of rack units available on the connected asset sensor. This value ranges from 8 to 64.

Example

The following command specifies the total number of rack units on the asset sensor #1 to 48 rack units.

config:# assetStrip 1 numberOfRackUnits 48 

Specifying the Rack Unit Numbering Mode

This command syntax specifies the numbering mode of rack units on the asset sensors connected to the Dominion PX device. The numbering mode changes the rack unit numbers.

config:# assetStrip <n> rackUnitNumberingMode <mode> 

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is one of the numbering modes: topDown or bottomUp.

Mode Description

topDown The rack units are numbered in the ascending order from the highest to the lowest rack unit.

bottomUp The rack units are numbered in the descending order from the highest to the lowest rack unit.

Example

The following command causes the rack units of the asset sensor #1 to be numbered in an ascending order from the one closest to the asset sensor's RJ-45 connector to the farthest one. That is, the rack unit that is most close to the RJ-45 connector is numbered 1.

config:# assetStrip 1 rackUnitNumberingMode topDown

Specifying the Rack Unit Numbering Offset

This command syntax specifies the starting number of rack units on the asset sensors connected to the Dominion PX device.

config:# assetStrip rackUnitNumberingOffset

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is a starting number for numbering rack units on the connected asset sensor. This value is an integer number.

Example

The following command specifies the starting number of rack units of the asset sensor #1 to be 5. That is, the rack units are numbered 5, 6, 7 and so on from the first to the final rack unit on the asset sensor #1.

config:# assetStrip 1 rackUnitNumberingOffset 5

Specifying the Asset Sensor Orientation

This command syntax specifies the orientation of the asset sensors connected to the Dominion PX device. Usually you do not need to perform this command unless your asset sensors do NOT come with the tilt sensor, causing the Dominion PX unable to detect the asset sensors' orientation.

config:# assetStrip assetStripOrientation

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is one of the options: topConnector or bottomConnector.

Orientation Description
topConnector This	option indicates that the asset sensor is mounted with the RJ-45 connector located on the top.
bottomConnector This	option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom.

Example

The following command specifies the orientation of the RJ-45 connector on the asset sensor #1 to be on the top.

config:# assetStrip 1 assetStripOrientation topConnector

Setting LED Colors for Connected Tags

This command syntax sets the LED color for all rack units on the asset sensor #1 to indicate the presence of a connected asset tag.

config:# assetStrip LEDColorForConnectedTags

Variables:

- is the hexadecimal RGB value of a color in HTML format. The variable ranges from #000000 to #FFFFFF.

Example

The following command sets the LED color for all rack units on the asset sensor #1 to RED (that is, FF0000) to indicate the presence of a connected asset tag.

config:# assetStrip 1 LEDColorForConnectedTags #FF0000

Setting LED Colors for Disconnected Tags

This command syntax sets the LED color for all rack units on the connected asset sensor(s) to indicate the absence of a connected asset tag.

config:# assetStrip LEDColorForDisconnectedTags

Variables:

- is the hexadecimal RGB value of a color in HTML format. The variable ranges from #000000 to #FFFFFF.

Example

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.

Rack Unit Configuration

For the Raritan asset sensor, a rack unit refers to a tag port. A rack unit configuration command begins with rackUnit.

Naming a Rack Unit

This command syntax assigns or changes the name of the specified rack unit on the specified asset sensor.

config:# rackUnit <n> <rack_unit> name "<name>" 

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.
• is a string comprising up to 32 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Example

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" 

Setting the LED Operation Mode

This command syntax determines whether a specific rack unit on the specified asset sensor follows the global LED color settings.

config:# rackUnit LEDOperationMode

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.
• is one of the LED modes: automatic or manual.

Mode Description

automatic This option makes the LED of the specified rack unit follow the global LED color settings. See Setting LED Colors for Connected Tags (on page 366) and Setting LED Colors for Disconnected Tags (on page 367).This is the default.

manual This option enables selection of a different LED color and LED mode for the specified rack unit.When this option is selected, see Setting an LED Color for a Rack Unit (on page 370) and Setting an LED Mode for a Rack Unit (on page 371) to set different LED settings.

Example

The following command allows the rack unit whose index number is 25 on the asset sensor#1 to have a different LED color and mode.

config:# rackUnit 1 25 LEDOperationMode manual

Setting an LED Color for a Rack Unit

This command syntax sets the LED color for a specific rack unit on the specified asset sensor. You need to set a rack unit's LED color only when the LED operation mode of this rack unit has been set to "manual."

config:# rackUnit LEDColor

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.
• is the hexadecimal RGB value of a color in HTML format. The variable ranges from #000000 to #FFFFFF.

Note: A rack unit's LED color setting overrides the global LED color setting on it. See Setting LED Colors for Connected Tags (on page 366) and Setting LED Colors for Disconnected Tags (on page 367).

Example

The following command sets the LED color of the rack unit whose index number is 25 on the asset sensor#1 to PINK (that is, FF00FF).

config:# rackUnit 1 25 LEDColor #FF00FF

Setting an LED Mode for a Rack Unit

This command syntax sets the LED mode for a specific rack unit on the specified asset sensor. You need to set a rack unit's LED mode only when the LED operation mode of this rack unit has been set to "manual."

config:# rackUnit LEDMode

Variables:

• is the number of the FEATURE port where the selected asset sensor is physically connected. For the Dominion PX device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit. The index number of each rack unit is available on the Asset Strip page of the web interface.
• is one of the LED modes: on, off, blinkSlow or blinkFast.

Mode Description

on This mode has the LED stay lit permanently.

off This mode has the LED stay off permanently

blinkSlow This mode has the LED blink slowly.

blinkFast This mode has the LED blink quickly.

Example

The following command causes the LED of the rack unit whose index number is 25 on the asset sensor#1 to blink quickly.

config:# rackUnit 1 25 LEDMode blinkFast

Serial Port Configuration Commands

A serial port configuration command begins with serial.

Setting the Serial Port Baud Rate

This command syntax sets the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the Dominion PX device. Note that you must log out of the CLI for this setting to take effect if you change the baud rate via the local connection.

config:# serial baudRate

Variables:

- is one of the baud rate options: 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200.

Note: The serial port setting is especially useful when the Dominion PX works in conjunction with Raritan's Dominion LX KVM switch. The Dominion LX only supports 19200 bps for communications over the serial interface.

Example

The following command sets the baud rate of the Dominion PX device's serial port to 9600 bps.

config:# serial baudRate 9600

Setting the History Buffer Length

This command syntax changes the history buffer length. The default length is 25.

config:# history length

Variables:

• is an integer number between 1 and 250.
• If you leave the variable blank when using the command, the history buffer is set to 25 by default.

Multi-Command Syntax

To shorten the configuration time, you can combine various configuration commands in one command and perform all of them at a time.

A multi-command syntax looks like this:

<setting 1> <value 1> <setting 2> <value 2> <setting 3> <value 3> ... 

Example 1 - Combination of IP, Subnet Mask and Gateway Parameters

The following multi-command syntax configures IPv4 address, subnet mask and gateway for the network connectivity simultaneously.

config:# network ipv4 ipAddress 192.168.84.225 subnetMask 255.255.255.0 gateway 192.168.84.0 

Results:

• The IP address is set to 192.168.84.225.
• The subnet mask is set to 255.255.255.0.
• The gateway is set to 192.168.84.0.

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 3rd circuit breaker.

config:# sensor ocp 3 current upperCritical disable upperWarning 20 

Results:

• The Upper Critical threshold of the 3rd circuit breaker's RMS current is disabled.
• The Upper Warning threshold of the 3rd circuit breaker's RMS current is set to 20A and enabled at the same time.

Example 3 - Combination of SSID and PSK Parameters

This multi-command syntax configures both of SSID and PSK parameters simultaneously for the wireless feature.

config:# network wireless SSID myssid PSK encryp_key

Results:

• The SSID value is set to myssid.
• The PSK value is set to encryp_key.

Quitting the Configuration Mode

Both of "apply" and "cancel" commands let you quit the configuration mode. The difference is that "apply" saves all changes you made in the configuration mode while "cancel" aborts all changes.

To quit the configuration mode, use either command:

config:# apply

-- OR --

config:# cancel

The # prompt appears after pressing Enter, indicating that you have entered the administrator mode.

Load Shedding Configuration Commands

This section only applies to outlet-switching capable PDUs.

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. See Different CLI Modes and Prompts (on page 233).

Enabling or Disabling Load Shedding

This section only applies to outlet-switching capable PDUs.

This command syntax determines whether the load shedding feature is enabled.

# loadshedding

After performing the above command, Dominion PX prompts you to confirm the operation. Press y to confirm 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 the operation is executed immediately.

# loadshedding /y

Variables:

- is one of the options: enable or disable.

Option Description

enable The load shedding feature is enabled.

disable The load shedding feature is disabled.

Example

The following command enables the load shedding feature.

config:# loadshedding enable

Power Control Operations

This section only applies to outlet-switching capable PDUs.

Outlets on the Dominion PX device can be turned on or off or power cycled through the CLI.

You must perform this operation in the administrator mode. See Different CLI Modes and Prompts (on page 233).

Turning On the Outlet(s)

This section only applies to outlet-switching capable PDUs.

This command syntax turns on one or multiple outlets.

# power outlets on

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.

# power outlets on /y

Variables:

- is one of the options: all, an outlet number, a list or a range of outlets.

Option Description
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 and 15, type outlets 2, 4, 9, 11-13, 15.
A range of outlets with an en dash in between	Switches ON multiple, consecutive outlets.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

Example

The following command turns on all outlets.

# power outlets all on

Turning Off the Outlet(s)

This section only applies to outlet-switching capable PDUs.

This command syntax turns off one or multiple outlets.

# power outlets off

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.

# power outlets off /y

Variables:

- is one of the options: all, an outlet number, a list or a range of outlets.

Option Description
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 and 15, type outlets 2, 4, 9, 11-13, 15.
A range of outlets with an en dash in between	Switches OFF multiple, consecutive outlets.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

Example

The following command turns off the outlet 6.

# power outlets 6 off

Power Cycling the Outlet(s)

This section only applies to outlet-switching capable PDUs.

This command syntax power cycles one or multiple outlets.

# power outlets cycle

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.

# power outlets cycle /y

Variables:

- is one of the options: all, an outlet number, a list or a range of outlets.

Option Description
all Power cycles	all outlets.
A specific outlet number	Power 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 and 15, type outlets 2, 4, 9, 11-13, 15.
A range of outlets with an en dash in between	Power cycles multiple, consecutive outlets.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

Example

The following command power cycles these outlets: 2, 6, 7, 8, 10, 13, 14, 15 and 16.

# power outlets 2,6-8,10,13-16 cycle

Unblocking a User

If any user is blocked from accessing the Dominion PX, you can unblock them at the local console.

To unblock a user:

1. Log in to the CLI interface using any terminal program via a local connection. See With HyperTerminal (on page 231).
2. When the Username prompt appears, type unblock and press Enter.

Username: unblock

1. When the "Username to unblock" prompt appears, type the login name of the user to be unblocked and press Enter.

Username to unblock:

1. A message appears, indicating that the specified user was unblocked successfully.

Resetting the Dominion PX

You can reset the Dominion PX device to factory defaults or simply restart it using the CLI commands.

Restarting the PDU

This command restarts the Dominion PX device. It is not a factory default reset.

To restart the Dominion PX device:

1. Ensure you have entered the administrator mode and the # prompt is displayed.
2. Type either of the following commands to restart the Dominion PX device.

<h1 id="reset-unit">reset unit</h1>
-- OR --
<h1 id="reset-unit-y">reset unit /y</h1>

1. 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.

2. Wait until the Username prompt appears, indicating the reset is complete.

Resetting to Factory Defaults

This command restores all settings of the Dominion PX device to factory defaults.

To reset Dominion PX settings, use either command:

<h1 id="reset-factorydefaults">reset factorydefaults</h1>
    -- OR --
<h1 id="reset-factorydefaults-y">reset factorydefaults /y</h1>

See Using the CLI Command (on page 394) for more information.

Network Troubleshooting

The Dominion PX 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.

Entering the Diagnostic Mode

Diagnostic commands function in the diagnostic mode only.

▶ To enter the diagnostic mode:

1. Ensure you have entered the administrator mode and the # prompt is displayed.
2. Type diag and press Enter. The diag> prompt appears, indicating that you have entered the diagnostic mode.
3. Now you can type any diagnostic commands for troubleshooting.

Diagnostic Commands

The diagnostic command syntax varies from command to command.

Querying the DNS Servers

This command syntax queries Internet domain name server (DNS) information of a network host.

diag> nslookup

Variables:

- is the name or IP address of the host whose DNS information you want to query.

Example

The following command checks the DNS information regarding the host 192.168.84.222.

diag> nslookup 192.168.84.222

Showing the Network Connections

This command syntax displays network connections and/or status of ports.

diag> netstat

Variables:

- is one of the options: ports or connections.

Option Description
ports Shows TCP/UDP ports.
connections	Shows network connections.

Example

The following command displays the server connections to your Dominion PX device.

diag> netstat connections

Testing the Network Connectivity

This command syntax 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 is good, or the host is shut down or not being connected to the network.

diag> ping

Variables:

- 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
countDetermines the number of messages to be sent.is an integer number.	Determines the number of messages to be sent.is an integer number.
sizeDetermines the packet size.is an integer number in bytes.	Determines the packet size.is an integer number in bytes.
timeoutDetermines the waiting period before timeout.is an integer number in seconds.	Determines the waiting period before timeout.is an integer number in seconds.

The command looks like this syntax when it includes all options:

diag> ping count size timeout

Example

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.

diag> ping 192.168.84.222 count 5

Tracing the Route

This command syntax traces the network route between your Dominion PX device and a network host.

diag> traceroute

Variables:

- is the name or IP address of the host you want to trace.

Example

The following command displays the existing network routing for the host 192.168.84.222.

diag> traceroute 192.168.84.222

Quitting the Diagnostic Mode

To quit the diagnostic mode, use this command:

diag> exit

The # prompt appears after pressing Enter, indicating that you have entered the administrator mode.

Querying Available Parameters for a Command

If you are not sure what commands or parameters are available for a particular type of CLI command, you can have the CLI show them by adding a space and then a question mark 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, the syntax is:

show ?

To query available network configuration parameters, the syntax is:
config:#network?
To query available role configuration parameters, the syntax is:
config:#role?

Retrieving Previous Commands

If you would like to retrieve any command that was previously typed in the same connection session, press the Up arrow (↑) on the keyboard until the desired command is displayed.

Automatically Completing a Command

A CLI command always consists of several words. For some unique CLI commands, such as the "reset" command, you can easily complete them by pressing the Tab or Ctrl+i instead of typing the whole command word by word.

To have a unique command completed automatically:

1. Type initial letters or words of the command. For example, type the first word of the "reset factorydefaults" command, that is, reset.

2. Press Tab or Ctrl+i until the complete command appears. For example, although you typed only one word for the reset command, the rest of the command appears after pressing Tab or Ctrl+i.

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 the administrator mode and the # prompt is displayed.
2. Type exit and press Enter.

Appendix A Specifications

In This Chapter

Power Measurement Accuracy ....387

Maximum Ambient Operating Temperature 387

Serial RS-232 Port Pinouts....387

Sensor RJ-12 Port Pinouts....388

Power Measurement Accuracy

The following measurement accuracy applies to all Raritan PDUs whose model names begin with PX2 or PXE.

	Power measurement accuracy	Measurement accuracy range
RMS voltage (V)	1%
RMS current (A)	1%+/-0.1A 0.1A to rated current
Active power (Watts)	1% 20W to rated power
Apparent power (VA)	1% 20VA to rated power
Active energy (Watts-hour)	1%

Maximum Ambient Operating Temperature

The maximum ambient operating temperature (TMA) for Dominion PX varies from 50 to 60 degrees Celsius, depending on the model and certification standard (CE or UL). If necessary, contact Raritan Technical Support for this information for your model.

Specification	Measure
Max Ambient Temperature 50 to 60 degrees Celsius

Serial RS-232 Port Pinouts

RS-232 Pin/signal definition

Pin No.	Signal	Direction	Description
1	DCD	Input	Data
2	RxD	Input	Receive data (data in)
3	TxD	Output	Transmit	data
4	DTR	Output	Data terminal ready
5	GND	—	Signal	ground
6	DSR	Input	Data set ready
7	RTS	Output	Request to send
8	CTS	Input	Clear to send
9	RI	Input	Ring	indicator

Sensor RJ-12 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 Ground
6	1-wire		Used for Feature Port

Appendix B Equipment Setup Worksheet

Dominion PX Series Model

Dominion PX Series Serial Number

OUTLET 1	OUTLET 2 OUTLET 3
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE
OUTLET 4	OUTLET 5 OUTLET 6
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE

Appendix B: Equipment Setup Worksheet

OUTLET 7	OUTLET 8 OUTLET 9
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE
OUTLET 10	OUTLET 11 OUTLET 12
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE
OUTLET 13	OUTLET 14 OUTLET 15
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE

Appendix B: Equipment Setup Worksheet

OUTLET 16	OUTLET 17 OUTLET 18
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE
OUTLET 19	OUTLET 20 OUTLET 21
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE

Appendix B: Equipment Setup Worksheet

OUTLET 22	OUTLET 23 OUTLET 24
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE

Types of adapters

Types of cables

Name of software program

Appendix C Resetting to Factory Defaults

For security reasons, the Dominion PX device can be reset to factory defaults only at the local console.

Important: Exercise caution before resetting the Dominion PX to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on. Only active energy data and firmware upgrade history are retained forever.

You can use either the reset button or the command line interface (CLI) to reset the Dominion PX.

In This Chapter

Using the Reset Button....393

Using the CLI Command 394

Using the Reset Button

To reset to factory defaults using the reset button:

1. Connect a computer to the Dominion PX device. See Connecting the Dominion PX to a Computer (on page 19).
2. Launch a terminal emulation program such as HyperTerminal, Kermit, or PuTTY, and open a window on the Dominion PX. For information on the serial port configuration, see Step 2 of Initial Network Configuration (on page 23).
3. Press (an d release) the Reset button of the Dominion PX device 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 the Dominion PX to its factory defaults.
5. Wait until the Username prompt appears, indicating the reset is complete.

This diagram shows the location of the reset button on Zero U models.

卷Ranion RESET USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/USB-108 USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBS USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBC USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UBB USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2 USB/UB2

This diagram shows the location of the reset button on 1U models.

Roritan LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示灯 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光 LED指示光电

This diagram shows the location of the reset button on 2U models.

OUTLET CLOSE / USB CURRENT USB VOLTAGE V73 POWER USB USB USB RESET USB-4 COMCAST / MODE UP ON DOWN USB-4

Note: HyperTerminal is available on Windows operating systems prior to Windows Vista. For Windows Vista or later versions, you may use PuTTY, which is a free program you can download from the Internet. See PuTTY's documentation for details on configuration.

Using the CLI Command

The Command Line Interface (CLI) provides a reset command for restoring the Dominion PX to factory defaults. For information on CLI, see Using the Command Line Interface (on page 230).

To reset to factory defaults using the CLI command:

1. Connect a computer to the Dominion PX device. See Connecting the Dominion PX to a Computer (on page 19).

2. Launch a terminal emulation program such as HyperTerminal, Kermit, or PuTTY, and open a window on the Dominion PX. For information on the serial port configuration, see Step 2 of Initial Network Configuration (on page 23).

Appendix C: Resetting to Factory Defaults

1. Log in to the CLI by typing the user name "admin" and its password. See Step 4 of Initial Network Configuration (on page 23).

2. After the # system prompt appears, type either of the following commands and press Enter.

<h1 id="reset-factorydefaults-2">reset factorydefaults</h1>
-- OR --
<h1 id="reset-factorydefaults-y-2">reset factorydefaults /y</h1>

1. If you entered the command without "/y" in Step 4, a message appears prompting you to confirm the operation. Type y to confirm the reset.

2. Wait until the Username prompt appears, indicating the reset is complete.

Appendix D 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 groups intended for the Dominion PX
b. Create user groups for the Dominion PX on the AD server
c. Configure LDAP authentication on the Dominion PX device
d. Configure roles on the Dominion PX device

In This Chapter

Step A. Determine User Accounts and Groups 396

Step B. Configure User Groups on the AD Server 397

Step C. Configure LDAP Authentication on the Dominion PX Device..398

Step D. Configure User Groups on the Dominion PX Device......400

Step A. Determine User Accounts and Groups

Determine the user accounts and groups that are authenticated for accessing the Dominion PX. In this example, we will create two user groups with different permissions. Each group will consist of two user accounts available on the AD server.

User groups User accounts (members)
	usera PX_User
	pxuser2
	userb PX_Admin
	pxuser

Group permissions:

• The PX_User group will have neither system permissions nor outlet permissions.
• The PX_Admin group will have full system and outlet permissions.

Step B. Configure User Groups on the AD Server

You must create the groups for the Dominion PX on the AD server, and then make appropriate users members of these groups.

In this illustration, we assume:

• The groups for the Dominion PX are named PX_Admin and PX_User.
- User accounts pxuser, pxuser2, usera and userb already exist on the AD server.

To configure the user groups on the AD server:

1. On the AD server, create new groups -- PX_Admin and PX_User.

Note: See the documentation or online help accompanying Microsoft AD for detailed instructions.

1. Add the pxuser2 and usera accounts to the PX_User group.
2. Add the pxuser and userb accounts to the PX_Admin group.
3. Verify whether each group comprises correct users.

PX_Admin Properties General Members Member Of Managed By Members: Name Active Directory Folder pxuser techadssl.com/Users userb techadssl.com/ServicesApps/raritan PX_User Properties General Members Member Of Managed By Members: Name Active Directory Folder pxuser2 techadssl.com/Users usera techadssl.com/ServicesApps/raritan

Step C. Configure LDAP Authentication on the Dominion PX Device

You must enable and set up LDAP authentication properly on the Dominion PX device to use external authentication.

In the illustration, we assume:

• The DNS server settings have been configured properly. See Modifying the Network Settings (on page 86) and Role of a DNS Server (on page 90).
• The AD serve r's domain name is techadssl.com, and its IP address is 192.168.56.3.
• The AD protocol is NOT encrypted over SSL.
  • The AD server uses the default TCP port 389.
• Anonymous bind is used.

To configure LDAP authentication:

1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.
2. Select the LDAP radio button to activate remote LDAP/LDAPS server authentication.

3. Click New to add an LDAP/LDAPS server for authentication. The "Create new LDAP Server Configuration" dialog appears.

4. Provide the Dominion PX with the information about the AD server.

■ IP Address / Hostname - Type the domain name techadssl.com or IP address 192.168.56.3.

Important: Without the SSL 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 the SSL encryption is enabled.

• Use settings from LDAP server - Leave the checkbox deselected.
• Type of LDAP Server - Select "Microsoft Active Directory" from the drop-down list.
• LDAP over SSL - Have the checkbox deselected since the SSL encryption is not applied in this example.
  ■ Port - Ensure the field is set to 389.
• SSL Port and Server Certificate - Skip the two fields since the SSL encryption is not enabled.
• Use Bind Credentials - Do NOT select this checkbox because anonymous bind is used.

• Bind DN, Bind Password and Confirm Bind Password -- Skip the three fields because anonymous bind is used.

• 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.

Create new LDAP Server Configuration IP Address / Hostname: 192.168.56.3 Use settings from LDAP Server Select LDAP Server Type of LDAP Server: Microsoft Active Directory LDAP over SSL Port: 389 SSL Port: 635 Use only trusted LDAP Server Certificates Server Certificate: not set Show Remove select new certificate... Browse... Anonymous Bind Use Bind Credentials Bind DN: Bind Password: Confirm Bind Password: Base DN for Search: dc=techadssl,dc=com Login Name Attribute: sAMAccountName User Entry Object Class: user User Search Subfilter: Active Directory Domain: techadssl.com Test Connection OK Cancel

Note: For more information on LDAP configuration, see Setting Up LDAP Authentication (on page 128).

1. Click OK to save the changes. The LDAP server is saved.
2. Click OK to save the changes. The LDAP authentication is activated.

Note: If the Dominion PX clock and the LDAP server clock are out of sync, the certificates are considered expired and users are unable to authenticate using LDAP. To ensure proper synchronization, administrators should configure the Dominion PX and the LDAP server to use the same NTP server.

Step D. Configure User Groups on the Dominion PX Device

A role on the Dominion PX device determines the system and outlet permissions. You must create the roles whose names are identical to the user groups created for the Dominion PX on the AD server or authorization 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 neither configure Dominion PX nor access the outlets.
• Users assigned to the PX_Admin role have the Administrator permissions so they can both configure Dominion PX and access the outlets.

To create the PX\_User role with appropriate permissions assigned:

1. Choose User Management > Roles. The Manage Roles dialog appears.

Tip: You can also access the Manage Roles dialog by clicking the Manage Roles button in the Edit User 'XXX' dialog.

1. Click New. The Create New Role dialog appears.
2. Type PX_User in the Role Name field.
3. Type a description for the PX_User role in the Description field. In this example, we type "The role can only view PX settings" to describe the role.
4. Click the Privileges tab to select all View XXX permissions (where XXX is the name of the setting). A View XXX permission lets users view the XXX settings without the capability to configure or change them.

a. Click Add. The "Add Privileges to new Role" dialog appears.

Appendix D: LDAP Configuration Illustration

b. Select a permission beginning with the word "View" from the Privileges list, such as View Event Settings.
c. Click Add.
d. Repeat Steps a to c to add all permissions beginning with "View."

Create New Role Settings Privileges Privilege ▲ Arguments View Data Logging Settings View Event Settings View Local Event Log View Local User Management View SNMP Settings View Security Settings View Webcam Images and Configur Add Edit Delete OK Cancel

1. Click OK to save the changes. The PX_User role is created.

Manage Roles Role Name ▲ Description Admin System defined administrator role including all privileges. Operator Predefined operator role. PX_User The role can only view PX settings New Edit Delete Close

1. Keep the Manage Roles dialog opened to create the PX_Admin role.

To create the PX\_Admin role with full permissions assigned:

1. Click New. The Create New Role dialog appears.
2. Type PX_Admin in the Role Name field.
3. Type a description for the PX_Admin role in the Description field. In this example, we type "The role includes all privileges" to describe the role.
4. Click the Privileges tab to select the Administrator permission. The Administrator permission allows users to configure or change all Dominion PX settings.

a. Click Add. The "Add Privileges to new Role" dialog appears.
b. Select the permission named Administrator Privileges from the Privileges list.
c. Click Add.

Create New Role Settings Privileges Privilege ▲ Arguments Administrator Privileges Add Edit Delete OK Cancel

1. Click OK to save the changes. The PX_Admin role is created.

Manage Roles Role Name ▲ Description Admin System defined administrator role including all privileges. Operator Predefined operator role. PX_Admin The role includes all privileges PX_Admin The role can only view PX settings New Edit Delete Close

1. Click Close to quit the dialog.

Appendix E Integration

The Dominion PX device can work with certain Raritan or non-Raritan products to provide diverse power solutions.

In This Chapter

Power IQ Configuration 404

Dominion KX II Configuration 406

RF Code Energy Monitoring Solution....410

Power IQ Configuration

Raritan'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, see either of the following:

• Power IQ User Guide: Available on the Raritan website's Firmware and Documentation section (http://www.raritan.com/support/firmware-and-documentation/).
• Power IQ Online Help: Available on the Product Online Help section (http://www.raritan.com/support/online-help/).

Adding PDUs to Power IQ Management

Once Power IQ is configured, add Dominion PX or other PDUs to its management. Power IQ can then gather data from these PDUs.

You can also add PDUs to Power IQ by uploading a CSV file containing the information. See Adding PDUs in Bulk with CSV Files in the Power IQ User Guide.

Use this procedure to add a Raritan EMX to Power IQ.

To add PDUs to Power IQ management:

1. In the PDUs tab, click Add.
2. Enter the IP address of the PDU.
3. If the PDU is in a daisy-chained configuration or console server configuration, enter the PDU's position number in the chain or serial port number in the Proxy Index field.

Note: If the PDU is not in this type of configuration, leave the Proxy Index field blank.

1. Enter an asset tag number or other asset management code in the External Key field. Optional.
2. Enter data in Custom Field 1 and Custom Field 2. Optional. The labels may have been changed in Power IQ to identify these fields.
3. If the PDU is a Dominion PX, enter a valid Username and Password for the PDU in the Dominion PX Credentials section. Re-enter the password in the Password Confirm field.

4. Select the SNMP Version.

5. For SNMP version 1/2c PDUs, enter an SNMP Community String that has at least READ permissions to this PDU. This enables polling the PDU for data. Enter an SNMP community string that has both READ and WRITE permissions to the PDU to enable power control, outlet renaming, and buffered data retrieval.

6. For SNMP version 3 PDUs, enter the Username and select an Authorization Level. The authorization levels are:

7. noAuthNoPriv - No Authentication Passkey, No Encoding Passkey

8. authNoPriv - Authentication Passkey, No Encoding Passkey
9. authPriv - Authentication Passkey, Encoding Passkey

a. Depending on the Authorization Level selected, you must enter additional credentials for Authorization and Privacy.
b. Authorization Protocol: Select MD5 or SHA.
c. Enter the PDU's Authorization Passkey, then re-enter the passkey in the Authorization Passkey Confirm field.
d. Privacy Protocol: Select DES or AES.
e. Enter the PDU's Privacy Passkey, then re-enter the passkey in the Privacy Passkey Confirm field.

Note: You must enable the SNMP agent on all PDUs added to Power IQ.

1. Select "Validate and wait for discovery to complete before proceeding" to check credentials and view the discovery process status as you add this PDU. Optional. See Validating PDU Credentials in the Power IQ User Guide.
2. Click Add.

Note: PDU discovery is complete once the PDU model type is determined. SNMP fields such as contact or location values are not determined until this device is polled for the first time.

Once added, the PDU appears in the PDU list. Power IQ begins polling the PDU for sensor data. You can configure how often Power IQ polls PDU. See Configuring Polling Intervals in the Power IQ User Guide.

Dominion KX II Configuration

PX2 series PDUs can be connected to the Raritan's Dominion KX II device (a digital KVM switch) to provide one more alternative of power control.

Note that this integration requires the following firmware versions:

• Dominion KX II -- 2.4 or later
- PX2 series -- 2.2 or later

Dominion KX II integration requires D2CIM-PWR and straight CAT5 cable.

For more information on Dominion KX II, see either of the following:

• Dominion KX II User Guide: Available on the Raritan website's Firmware and Documentation section (http://www.raritan.com/support/firmware-and-documentation/).
• Dominion KX II Online Help : Available on the Product Online Help section (http://www.raritan.com/support/online-help/).

Configuring Rack PDU (Power Strip) Targets

The KX II allows you to connect rack PDUs (power strips) to KX II ports. KX II rack PDU configuration is done from the KX II Port Configuration page.

Connecting a Rack PDU

Rack PDUs are connected to the KX II using the D2CIM-PWR CIM.

To connect the rack PDU:

1. Connect the male RJ-45 of the D2CIM-PWR to the female RJ-45 connector labeled "FEATURE" of the rack PDU.
2. Connect the female RJ-45 connector of the D2CIM-PWR to any of the available female system port connectors on the KX II 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.

Front view of a network switch device connected to a rack-mounted cable, showing ports and ports without any text or symbols.

Naming the Rack PDU in the KX II or LX (Port Page for Power Strips)

Note: PX rack PDUs (power strips) can be named in the PX as well as in KX II and LX.

Once a Raritan remote rack PDU is connected to the KX II or LX, it will appear on the Port Configuration page. Click on the power port name on that page to access it. The Type and the Name fields are prepopulated.

Note: The (CIM) Type cannot be changed.

The following information is displayed for each outlet on the rack PDU: [Outlet] Number, Name, and Port Association.

Use this page to name the rack PDU and its outlets. Names can be up to 32 alphanumeric characters and can include special characters.

Note: When a rack PDU is associated with a target server (port), the outlet name is replaced by the target server name, even if you assigned another name to the outlet.

To name the rack PDU and outlets:

Note: CommandCenter Secure Gateway does not recognize rack PDU names containing spaces.

1. Enter the Name of the rack PDU (if needed).
2. Change the [Outlet] Name if desired. (Outlet names default to the outlet #.)

3. Click OK.

Home > Device Settings > Port Configuration > Port Port 17 Type: PowerStrip Name: PowerStrip-PCR8 Outlets Number Name Port Association 1 Dominion-Port1(1) Dominion-Port7 2 Outlet 2 3 Outlet 3 4 Outlet 4 5 Outlet 5 6 Outlet 6 7 Outlet 7 8 Outlet 8 OK Cancel

Associating Outlets with Target Servers on KX II and LX

The Port page opens when you click on a port on the Port Configuration page. From this page, you can make power associations, change the port name to something more descriptive, and update target server settings if you are using the D2CIM-VUSB CIM. The (CIM) Type and the (Port) Name fields are prepopulated; note that the CIM type cannot be changed.

A server can have up to four power plugs and you can associate a different rack PDU (power strip) with each. From this page, you can define those associations so that you can power on, power off, and power cycle the server from the Port Access page.

To use this feature, you will need:

• Raritan remote rack PDU(s)
  • Power CIMs (D2CIM-PWR)

To make power associations (associate rack PDU outlets to KVM target servers):

Note: When a rack PDU is associated to a target server (port), the outlet name is replaced by the target server name (even if you assigned another name to the outlet).

1. Choose the rack PDU from the Power Strip Name drop-down list.
2. For that rack PDU, choose the outlet from the Outlet Name drop-down list.
3. Repeat steps 1 and 2 for all desired power associations.
4. Click OK. A confirmation message is displayed.

▶ To change the port name:

1. Type something descriptive in the Name field. For example, the name of the target server would be a likely candidate. The name can be up to 32 alphanumeric characters and can include special characters.

2. Click OK.

Removing Power Associations

When disconnecting target servers and/or rack PDUs from the device, all power associations should first be deleted. When a target has been associated with a rack PDU and the target is removed from the device, the power association remains. When this occurs, you are not able to access the Port Configuration for that disconnected target server in Device Settings so that the power association can be properly remove.

To remove a rack PDU association:

1. Select the appropriate rack PDU from the Power Strip Name drop-down list.

2. For that rack PDU, select the appropriate outlet from the Outlet Name drop-down list.

3. From the Outlet Name drop-down list, select None.
4. Click OK. That rack PDU/outlet association is removed and a confirmation message is displayed.

To remove a rack PDU association if the rack PDU has been removed from the target:

1. Click Device Settings > Port Configuration and then click on the active target.
2. Associate the active target to the disconnected power port. This will break the disconnected target's power association.

Finally, associate the active target to the correct power port.

RF Code Energy Monitoring Solution

With the RF Code active RFID hardware and management software and Raritan's Dominion PX combined, a wire-free energy monitoring solution that provides a picture of power utilization is offered.

This combined solution does not require any additional IP address configuration or association. All you need to do is plug an RF Code R170 PDU sensor tag into the SENSOR port of the Dominion PX device.

The RF Code R170 PDU sensor tag collects the power data generated by Raritan Dominion PX and sends the data to the RF Code Sensor Manager software, which not only manages the power data but also make computations about the power usage from the collected data.

You can use the RF Code Sensor Manager to manage the power data using:

• Live table views
• Map views
• Interactive graphing and reporting
• Scheduled graphing and reporting
• Alerting and thresholding

Appendix F Additional Dominion PX Information

In This Chapter

MAC Address 411

Locking Outlets and Cords 411

Altitude Correction Factors....414

Data for BTU Calculation....414

CLI Command Applicability 415

Truncated Data in the Web Interface 418

MAC Address

A label is affixed to a Dominion PX device, near the LED display, showing both the serial number and MAC address of the PDU.

MAC: 00:00:50:06:C7:2U SIN : PXL0600001

If necessary, you can find the PDU's IP address through the MAC address by using commonly-used network tools. Contact your LAN administrator for assistance.

Locking Outlets and Cords

In addition to the cable retention clips, Raritan also provides other approaches to secure the connection of the power cords from your IT equipment to the Raritan PDUs, including:

• SecureLock ^TM outlets and cords
• Button-type locking outlets

Note that NOT all Raritan PDUs are implemented with any of the above locking outlets.

SecureLock™ Outlets and Cords

SecureLock ^™ is an innovative mechanism designed by Raritan, which securely holds C14 or C20 plugs that are plugged into Raritan PDUs in place. This method requires the following two components:

• Raritan 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 either side of its plug. The following diagram illustrates such a plug.

Diagram of a plug with labeled section A (no text or symbols present)

Item Description

A Latches on the SecureLock ™ cord's plug

Only specific PDUs are implemented with the SecureLock™ mechanism. If you PDU does not have this design, do NOT use the SecureLock™ cords with it.

Tip: The SecureLock ^™ outlets can accept regular power cords for power distribution but the SecureLock ^™ mechanism does not take effect.

To lock a power cord using the SecureLock™ mechanism:

1. Verify that the SecureLock ^™ cord you purchased meets your needs.

2. The cords' female socket matches the power socket type (C14 or C20) on your IT equipment.

3. The cord's male plug matches the outlet type (C13 or C19) on your PDU.

4. Connect the SecureLock ^™ cord between the IT equipment and your PDU.

5. Plug the female socket end of the cord into the power socket of the desired IT equipment.

6. Plug the male plug end of the cord into the appropriate SecureLock™ outlet on the PDU. Push the plug toward the outlet until you hear the click, which indicates the plug's latches are snapped into the latch slots of the outlet.

To remove a SecureLock ^TM power cord from the PDU:

1. Press and hold down the two latches on the cord's plug as illustrated in the diagram below.

Diagram of a plug inserted into a socket with red arrows indicating direction (no text or symbols)

1. Unplug the cord now.

Button-Type Locking Outlets

A button-type locking outlet has a button on it. Such outlets do not require any special power cords to achieve the locking purpose. All you need to do is simply plug a regular power 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 on the outlet. Depending on the outlet type, the button location differs.

Diagram showing two electrical socket installation steps with blue arrows indicating direction of movement

1. Unplug the power cord now.

Altitude Correction Factors

If a Raritan differential air pressure sensor is attached to your device, the altitude you enter for the device 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

Data for BTU Calculation

The heat generated by the Dominion PX device differs according to the model you purchased. To calculate the heat (BTU/hr), use the following power data according to your model type in the BTU calculation formula.

Model name Maximum power (Watt)
PX2-1nnn series 5
PX2-2nnn series 20
PX2-3nnn series 24
PX2-4nnn series 24
PX2-5nnn series 24

The letter "n" included in the model names represents a number.

CLI Command Applicability

Not every CLI command applies to all Dominion PX PDUs because features vary from model to model. For example, PX-1000 series are not implemented with the outlet switching capability, so outlet-switching commands are not applicable.

The tables in this appendix show the command applicability for diverse Dominion PX product lines. In all tables:

• PX-1000 represents PDUs ranging from PX2-1000 to PX2-1999
• PX-2000 represents PDUs ranging from PX2-2000 to PX2-2999

Show Commands

This table indicates the show commands applicability.

• Y: applicable
  • N: NOT applicable

CLI commands PX-1000 PX-2000
show assetStrip	Y	Y
show assetStripManagement	Y	Y
show energywise	Y	Y
show externalsensors (details)	Y	Y
show history	Y	Y
show history bufferlength	Y	Y
show inlets (details)	Y	Y
show loadshedding	N	Y
show network	Y	Y
show network mode	Y	Y
show network services	Y	Y
show network wireless (details)	Y	Y
show ocp (details)	Y	Y
show outlets (details)	Y	Y
show pdu (details)	Y (1) Y
show reliability data	Y	Y
show reliability errorlog	Y	Y
show roles	Y	Y
show security (details)	Y	Y
show sensor externalsensor(n)(details)	Y	Y
show sensor inlet(n)(details)	Y	Y
show sensor inletpole(n)(details)	Y	Y
show sensor ocp(n)(details)	Y	Y
show serial	Y	Y
show time (details)	Y	Y
show user(details)	Y	Y
show network wireless (details)	Y	Y

Notes:

1. After performing the show pdu (details) command, the following PDU information is not available for PX-1000 series:

■ Default outlet state on startup
- Outlet power sequence
- Outlet power sequence delay

Configuration Commands

This table indicates the configuration commands applicability.

• Y: applicable
  • N: NOT applicable

CLI commands PX-1000 PX-2000
All network commands	Y	Y
All network services commands	Y	Y
All security commands	Y	Y
All inlet commands	Y	Y
All ocp commands	Y	Y
All externalsensor commands	Y	Y
All sensor inlet commands	Y	Y
All sensor inletpole commands	Y	Y
All sensor ocp commands	Y	Y
All sensor externalsensor commands	Y	Y
All serial commands	Y	Y
All time commands	Y	Y
All user commands	Y	Y
All role commands	Y	Y
All energywise commands	Y	Y
All assetStrip commands	Y	Y
All loadshedding commands	N	Y
history length	Y	Y
network mode	Y	Y
outlet cyclingPowerOffPeriod	N	Y
outlet name ""	Y	Y
outlet stateOnDeviceStartup	N	Y
pdu cyclingPowerOffPeriod	Y	Y
pdu dataRetrieval	Y	Y
pdu deviceAltitude	Y	Y
pdu displayOrientation	Y (1) Y (1)
pdu externalSensorsZCoordinateFormat	Y	Y
pdu inrushGuardDelay	N	Y
pdu measurementsPerLogEntry	Y	Y
pdu name ""	Y	Y
pdu nonCriticalOutlets:false;:true	N	Y
pdu outletInitializationDelayOnDeviceStartup	N	Y
pdu outletSequence	N	Y
pdu outletSequenceDelay::::...	N	Y
pdu outletStateOnDeviceStartup	N	Y

Notes:

1. The pdu displayOrientation command only applies to Zero U models.

Other Commands

This table indicates the applicability of CLI commands other than the show and configuration commands.

• Y: applicable
  • N: NOT applicable

CLI commands PX-1000 PX-2000
All power outlets commands	N	Y
All reset pdu commands	Y	Y
nslookup	Y	Y
netstat	Y	Y
ping	Y	Y
traceroute	Y	Y

Truncated Data in the Web Interface

Some fields of the Dominion PX web interface can accommodate data entry up to 256 characters. When the data entered is too long, it may be truncated due to some or all of the following factors:

• Screen resolution
• Font size
• Font type
  • Size of different characters

Current web browser technology cannot break or wrap these fields with long inputs.

The solution for this issue includes:

• Increase of the screen resolution
• Application of smaller font size
• Use of other interfaces, such as the CLI or SNMP, to view the data in these fields

Index

1

1U Products • 4

2

2U Products • 4

A

A Note about Enabling Thresholds • 229

A Note about Firmware Upgrade Time • 220

A Note about Infinite Loop • 178

A Note about Untriggered Rules • 181

About Contact Closure Sensors • 35

About the Interface • 230

Access Security Control • 110

Accessing the Help • 222

Activating or Deactivating the Load Shedding Mode • 146

Add Page Icon • 71, 75

Adding a Firewall Rule • 292

Adding a Role-Based Access Control Rule • 307

Adding IT Devices for Ping Monitoring • 184

Adding PDUs to Power IQ Management • 404

Adding the LDAP Server Settings • 129

Additional Dominion PX Information • xiv, 411

Adjusting Image or Video Properties • 206

Adjusting the Pane • 73

Alert States and LHX Event Log • 217

Alerted Sensors • 81

All Privileges • 356, 359

Altitude Correction Factors • 98, 260, 414

AMS-M2-Z Daisy-Chain Limitations • 46, 47

Applicable Models • xiii

Asset Management • 196

Asset Management Commands • xiv, 363

Asset Sensor Management • 363

Asset Sensor Settings • 248

Associating Outlets with Target Servers on KX II and LX • 409

Automatic Mode • 57

Automatically Completing a Command • 385

B

Beeper • 64

Before You Begin · 15

Blade Extension Strip Settings • 250

Browser-Defined Shortcut Menu • 80

Browsing through the Online Help • 222

Bulk Configuration for Circuit Breaker Thresholds • xiv, 152

Button-Type Locking Outlets • 413

C

Cascading the PDUs via USB • 29, 53, 83

Certificate Signing Request • 123

Changing a User's Password • 345

Changing an Outlet's Default State • 312

Changing the Circuit Breaker Name • 314

Changing the Column • 78

Changing the Cycling Power-Off Period • 139

Changing the Default Policy • 111, 119

Changing the HTTP Port • 280

Changing the HTTP(S) Settings • 90

Changing the HTTPS Port • 280

Changing the Inlet Name • 314

Changing the LAN Duplex Mode • 279

Changing the LAN Interface Speed • 278

Changing the LED Display Orientation • 55, 262

Changing the Measurement Units • 98, 203, 353

Changing the Modbus Configuration • 285

Changing the Modbus Port • 287

Changing the Modbus Settings • xiv, 93

Changing the Outlet Name • 311

Changing the Outlet-Specific Cycling Power-Off Period • 139, 140

Changing the PDU Name • 254

Changing the PDU-Defined Cycling Power-Off Period • 139, 140

Changing the Role List View • 110

Changing the Role(s) • 352

Changing the Sensor Description • 319

Changing the Sensor Name • 315

Changing the Sorting • 79, 183, 186

Changing the SSH Configuration · 281

Changing the SSH Port • 282

Changing the SSH Settings • 91, 105

Changing the Telnet Configuration • 280

Changing the Telnet Port • 281

Changing the Telnet Settings • 91

Changing the UDP Port • 362

Index

Changing the User List View • 107

Changing the View of a List • 78, 107, 110, 209, 221

Changing Your Own Password • 355

Changing Your Password • 67

Checking Associated Circuit Breakers • 134

Checking Server Monitoring States • 185

Checking the Branch Circuit Rating • 16

Circuit Breaker Configuration Commands • 314

Circuit Breaker Information • 239

Circuit Breaker Orientation Limitation • 5, 6, 7, 9, 10, 12, 13

Circuit Breaker Sensor Threshold Information • 243

Circuit Breakers • 59

Clearing Event Entries • 182

CLI Command Applicability • 415

Closing a Serial Connection • 233

Collapsing the Tree • 72

Combining Asset Sensors • 39

Command History • 251

Commands for Circuit Breaker Sensors • 333

Commands for Environmental Sensors • 338

Commands for Inlet Pole Sensors • 325

Commands for Inlet Sensors • 319

Components of an Event Rule • 155

Configuration Commands • 416

Configuring a Contact Closure Sensor • 36, 37, 194

Configuring a Specific Rack Unit • xiv, 198

Configuring Environmental Sensors • 186, 189

Configuring Event Rules • xiv, 92, 100, 150, 155, 226

Configuring IP Protocol Settings · 263

Configuring Rack PDU (Power Strip) Targets • 406

Configuring SNMP Traps • 226

Configuring Temperature and Fan Thresholds • 215

Configuring the Asset Sensor • 42, 196

Configuring the Dominion PX • 18, 86

Configuring the Dominion PX Device and Network • 253

Configuring the Feature Port • xiv, 97, 213, 214

Configuring the Firewall • xiv, 110

Configuring the IPv4 Parameters • 271

Configuring the IPv6 Parameters • 275

Configuring the LHX Device • 213

Configuring the Serial Port • xiv, 98

Configuring the SMTP Settings • 100, 157, 158

Configuring the SNMP Settings • 92, 103

Configuring Users for Encrypted SNMP v3 • 92, 225

Configuring Webcams • 205, 206

Connecting a GSM Modem (Optional) • 48

Connecting a Logitech Webcam (Optional) • 48, 71, 205, 206

Connecting a Rack PDU • 406

Connecting a Schroff LHX Heat Exchanger (Optional) • xiv, 49, 97, 212

Connecting AMS-M2-Z Asset Sensors (Optional) • xiv, 46

Connecting Asset Sensors to the Dominion PX • 41, 46, 197, 200

Connecting Blade Extension Strips • xiv, 43

Connecting Environmental Sensors (Optional) • 33, 186

Connecting the Asset Management Sensor (Optional) • 38, 52, 97, 196

Connecting the Dominion PX to a Computer • 19, 393, 394

Connecting the Dominion PX to Your Network • 21, 84, 85

Connecting the PDU to a Power Source • 17

Connecting Third-Party Detectors/Switches to DPX-CC2-TR • 35

Connection Ports • 51

Contact Closure Sensor LEDs • 37

Controlling the LHX Device • 213, 218

Copying a Dominion PX Configuration • 203

Copying Configurations with Bulk Configuration • 201

Correctly Displaying the LHX Device • 214

Creating a Certificate Signing Request • 123

Creating a Role · 105, 107, 355

Creating a Self-Signed Certificate • 125

Creating a User Profile • 66, 91, 102, 106, 107, 108, 204, 225, 343

Creating Actions • 48, 156, 161, 164, 205

Creating an Action Group • 160

Creating an Event Rule • 155

Creating Custom Email Messages • 161

Creating Firewall Rules • 111, 112

Creating Role-Based Access Control Rules • 119, 120

Creating Rules • 171

D

Data for BTU Calculation • 414

Data Pane • 75

Date and Time Settings • 239

Index

Default Log Messages • 164

Deleting a Firewall Rule • 296

Deleting a Role • 109, 360

Deleting a Role-Based Access Control Rule • 310

Deleting a User Profile • 106, 354

Deleting an Event Rule or Action • 181

Deleting Firewall Rules • 115

Deleting Ping Monitoring Settings • 185

Deleting Role-Based Access Control Rules • 122

Deleting the LDAP Server Settings • 132

Describing the Sensor Location • 190, 191

Determining the Time Setup Method • 288

Device Management • 82

Device States and Icon Variations • 214, 218

Diagnostic Commands • 381

Different CLI Modes and Prompts • 231, 232, 233, 253, 374, 375

Disabling the LDAP Authentication • 133

Displaying the Asset Sensor Information • 200

Displaying the PDU Information • 31, 82, 134

Dominion KX II Configuration • xiv, 97, 406

Dominion PX Explorer Pane · 70

Downloading Diagnostic Information • 212

Downloading Key and Certificate Files • 127

Downloading SNMP MIB • 93, 225, 226, 227

E

Editing Firewall Rules • 114

Editing Ping Monitoring Settings • 185

Editing Role-Based Access Control Rules • 121

Editing the LDAP Server Settings • 132

Email Message Placeholders • 161, 162

Enabling Data Logging • 99

Enabling IPv4 or IPv6 · 264

Enabling LDAP and Local Authentication Services • 133

Enabling Login Limitations • 117

Enabling or Disabling a User Profile • 347

Enabling or Disabling Data Logging • 259

Enabling or Disabling EnergyWise • 360

Enabling or Disabling Load Shedding • 375

Enabling or Disabling Modbus • 286

Enabling or Disabling SNMP v1/v2c • 283

Enabling or Disabling SNMP v3 • 283

Enabling or Disabling SSH • 282

Enabling or Disabling Strong Passwords • 301

Enabling or Disabling Telnet • 281

Enabling or Disabling the Read-Only Mode • 286

Enabling or Disabling the Service

Advertisement • 287

Enabling Password Aging • 118

Enabling Service Advertisement • xiv, 94, 287

Enabling SNMP • 99, 224

Enabling Strong Passwords • 117

Enabling the Feature • 118, 119

Enabling the Firewall • 110, 111

Enabling the LHX Support • 213

Enabling User Blocking • 116

EnergyWise Configuration Commands • 360

EnergyWise Settings • 247

Entering the Configuration Mode · 233, 253, 269, 345, 355

Entering the Diagnostic Mode • 233, 381

Environmental Sensor Configuration

Commands • 315

Environmental Sensor Information • 240

Environmental Sensor Threshold Information • 244

Environmental Sensors • 186

Equipment Setup Worksheet • 16, 389

Example • 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 292, 294, 296, 297, 298, 299, 300, 301, 302, 303, 304, 306, 308, 310, 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 327, 328, 329, 331, 332, 333, 334, 335, 336, 337, 338, 339, 340, 341, 342, 343, 344, 345, 346, 347, 348, 351, 352, 354, 355, 358, 359, 360, 361, 362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 372, 375, 377, 378, 379, 381, 382, 383, 384 When Hysteresis is Useful • 154 When to Disable Hysteresis • 154

Example 1 • 179

Example 1 - Basic Security Information • 252

Example 1 - Combination of IP, Subnet Mask and Gateway Parameters • 373

Example 2 • 179

Example 2 - Combination of Upper Critical and Upper Warning Settings • 373

Example 2 - In-Depth Security Information • 252

Example 3 · 179

Example 3 - Basic PDU Information • 252

Example 3 - Combination of SSID and PSK Parameters • 374

Example 4 - In-Depth PDU Information • 253

Examples • 251

Index

Existing Roles • 246

Existing User Profiles • 245

Expanding a Blade Extension Strip • xiv, 199

Expanding the Tree • 71, 134, 135, 136, 137, 138, 140, 145, 146, 147, 148, 149, 150, 151, 152, 187, 188, 189, 192, 195, 196, 198, 214, 215, 216, 218

F

Filling Out the Equipment Setup Worksheet • 16

Firewall Control • 290

Firmware Upgrade • 203, 219

Forcing a Password Change • 347

Forcing HTTPS Encryption • 90, 110, 123

Full Disaster Recovery • 221

Fuse • xiv, 61

Fuse Replacement on 1U Models • 62

Fuse Replacement on Zero U Models • 61

G

Gathering the LDAP Information • 128

H

Help Command • 233

History Buffer Length · 251

How to Connect Differential Air Pressure Sensors • 38

How to Use the Calendar • 96

HTTPS Access • 297

|

Identifying Environmental Sensors • 186, 187, 188

Idle Timeout • 299

Initial Network Configuration • 23, 66, 73, 84, 85, 393, 394, 395

Inlet and Circuit Breaker Management • 147

Inlet Configuration Commands • 313

Inlet Information • 238

Inlet Pole Sensor Threshold Information • 242

Inlet Sensor Threshold Information • 241

Installation and Configuration • 15

Installing a CA-Signed Certificate • 125

Installing Cable Retention Clips on Outlets (Optional) • 32

Installing Cable Retention Clips on the Inlet (Optional) • 17

Installing Existing Key and Certificate Files • 126

Installing the USB-to-Serial Driver • xiv, 20, 228

Integration • 404

Introduction • 1

Introduction to the Web Interface • 69

IP Configuration • 234

L

LAN Interface Settings • 235

Layout • 228

LDAP Configuration Illustration • 131, 396

LED Display • 54

LEDs for Measurement Units • 56, 57

Listing TCP Connections • 211

Load Shedding Configuration Commands • 374

Load Shedding Settings • 247

Locking Outlets and Cords • 33, 411

Logging in to CLI • 230

Logging in to the Web Interface • 66

Logging out of CLI • 386

Login • 66

Login Limitation • 297

Logout · 68

Logout Button • 75

Lowercase Character Requirement • 302

M

MAC Address • 18, 411

Managing Environmental Sensors • 186, 188

Managing Event Logging • 181

Managing Firewall Rules • 292

Managing Role-Based Access Control Rules • 306

Managing the Schroff LHX Heat Exchanger • xiv, 49, 97, 212

Managing the Snapshot History • 209

Managing the Webcam Images or Videos • xiv, 205

Manual Mode • 57

Marking All Outlets • 144

Marking an Outlet • 145

Maximum Ambient Operating Temperature • 16, 387

Maximum Password History • 304

Maximum Password Length • 302

Menus • 70

Minimum Password Length • 301

Modifying a Firewall Rule • 294

Index

Modifying a Role • 105, 106, 108, 358

Modifying a Role-Based Access Control Rule • 308

Modifying a User Profile • 67, 68, 106, 108, 344

Modifying a User's Personal Data • 346

Modifying an Action • 93, 180

Modifying an Event Rule • 179

Modifying the Firewall Control Parameters • 291

Modifying the IPv4 Settings • 87

Modifying the IPv6 Settings • 89

Modifying the Network Configuration • 84

Modifying the Network Interface Settings · 84

Modifying the Network Service Settings • 90, 230, 232

Modifying the Network Settings • 73, 86, 398

Modifying the Role-Based Access Control Parameters • 305

Modifying the SNMPv3 Settings • 348

Monitoring Circuit Breakers • 149

Monitoring Server Accessibility • 184

Monitoring the Inlet • 148

Monitoring the LHX Device • 213, 215, 217

More Information · 76

More Information about AD Configuration • 131

Mounting 1U or 2U Models • 13

Mounting Zero U Models Using Button Mount • 7

Mounting Zero U Models Using Claw-Foot Brackets • 9

Mounting Zero U Models Using L-Brackets • 6

Mounting Zero U Models Using L-Brackets and Buttons • 12

Mounting Zero U Models Using Two Rear Buttons • 10

Multi-Command Syntax • 292, 297, 300, 301, 306, 344, 346, 348, 353, 373

N

Naming a Rack Unit • 368

Naming an Asset Sensor • 363

Naming Circuit Breakers • 147

Naming Outlets • 134

Naming the Inlet • 147

Naming the LHX Device • 214

Naming the PDU • 71, 72, 73, 83, 99, 135, 137, 139, 141, 142, 143, 144, 146, 147, 148, 150, 151, 152, 187, 188, 189, 190, 192, 195, 216

Naming the Rack PDU in the KX II or LX (Port Page for Power Strips) • 407

Network Configuration • 234

Network Diagnostics • 210

Network Service Settings • 236

Network Troubleshooting • 210, 380

Networking Configuration Commands • 262

Networking Mode · 235

Numeric Character Requirement • 303

0

Operating Hours • 217

Other Commands • 418

Outlet Configuration Commands • 311

Outlet Information • 237

Outlet Management • 133

Outlet Switching • 135

Outlets · 50

Overriding the DHCP-Assigned NTP Servers • 289

Overriding the IPv4 DHCP-Assigned DNS Server • 274

Overriding the IPv6 DHCP-Assigned DNS Server • 277, 278

P

Package Contents • 3, 15

Panel Components • 50

Password Aging • 298

Password Aging Interval • 299

PDU Configuration • 236

PDU Configuration Commands • xiv, 254

Pinging a Host • 210

Power Control Operations · 375

Power Cord • 50

Power Cycling the Outlet(s) • 378

Power IQ Configuration • 404

Power Measurement Accuracy · 387

Preparing the Installation Site • 16

Product Features • 1

Product Models • 1

Providing the EAP CA Certificate • 268

PX-1000 Series • 51

PX-2000 Series • 51

Q

Querying Available Parameters for a Command • 233, 385

Querying the DNS Servers • 381

Quitting the Configuration Mode • 254, 374

Quitting the Diagnostic Mode • 384

R

Rack Unit Configuration • 367

Rack Unit Settings of an Asset Sensor • 249

Rackmount Safety Guidelines • 5

Rack-Mounting the PDU • 5

Rebooting the Dominion PX Device • 102

Reliability Data · 250

Reliability Error Log · 251

Reset Button · 58

Resetting the Button-Type Circuit Breaker • 59

Resetting the Dominion PX • 379

Resetting the Handle-Type Circuit Breaker • 60

Resetting to Factory Defaults • 58, 380, 393

Resizing a Dialog • 79

Restarting the PDU · 380

Retrieving Previous Commands • 385

Retrieving Software Packages Information • 222

RF Code Energy Monitoring Solution • 410

Role Configuration Commands • 355

Role of a DNS Server • 90, 398

Role-Bassed Access Control • 305

S

Safety Guidelines • ii

Safety Instructions • iii, 16

Sample Environmental-Sensor-Level Event Rule • 177

Sample Event Rules • 175

Sample Inlet-Level Event Rule • 176

Sample Outlet-Level Event Rule • 176

Sample PDU-Level Event Rule • 175

Saving a Dominion PX Configuration • 202

Saving Snapshots • 205, 207, 209

SecureLock™ Outlets and Cords • 412

Security Configuration Commands • xiv, 290

Security Settings · 245

Selecting IPv4 or IPv6 Addresses • 264

Selecting the Internet Protocol • 87, 89

Sending Snapshots or Videos in an Email or Instant Message • 205, 207

Sensor Measurement Accuracy • 193

Sensor RJ-12 Port Pinouts • 388

Sensor Threshold Configuration Commands • 319

Serial Port Configuration Commands • xiv, 371

Serial Port Settings • 247

Serial RS-232 Port Pinouts • 388

Setting a Circuit Breaker's Thresholds • 151, 152

Setting an LED Color for a Rack Unit • 369, 370

Setting an LED Mode for a Rack Unit • 369, 371

Setting an Outlet's Cycling Power-Off Period • 313

Setting Asset Sensor LED Colors • 197

Setting Data Logging • 99, 260

Setting Inlet Thresholds • 150

Setting LED Colors for Connected Tags • 366, 369, 370

Setting LED Colors for Disconnected Tags • 367, 369, 370

Setting Non-Critical Outlets and Load Shedding Mode • 144, 259

Setting Power Thresholds • 77, 150, 229

Setting the Authentication Method • 266

Setting the BSSID · 270

Setting the Circuit Breaker's Assertion Timeout • 337

Setting the Circuit Breaker's Deassertion Hysteresis • 337

Setting the Data Logging Measurements Per Entry · 260

Setting the Date and Time • 94

Setting the Default Outlet State • 137

Setting the EAP Identity • 268

Setting the EAP Parameters • 267

Setting the EAP Password • 268

Setting the EnergyWise Configuration • 101

Setting the History Buffer Length · 372

Setting the Initialization Delay • 141, 258

Setting the Inlet Pole's Assertion Timeout • 332

Setting the Inlet Pole's Deassertion Hysteresis • 331

Setting the Inlet's Assertion Timeout • 325

Setting the Inlet's Deassertion Hysteresis • 324

Setting the Inlet's Lower Critical Threshold • 322

Setting the Inlet's Lower Warning Threshold • 323

Setting the Inlet's Upper Critical Threshold • 320

Setting the Inlet's Upper Warning Threshold • 321

Setting the Inner Authentication • 267

Setting the Inrush Guard Delay • 142

Setting the Inrush Guard Delay Time • 258

Setting the IPv4 Address • 272

Setting the IPv4 Configuration Mode • 271

Setting the IPv4 Gateway • 273

Index

Setting the IPv4 Primary DNS Server • 273

Setting the IPv4 Secondary DNS Server • 274

Setting the IPv4 Subnet Mask • 272

Setting the IPv6 Address • 276

Setting the IPv6 Configuration Mode • 275

Setting the IPv6 Gateway · 276

Setting the IPv6 Primary DNS Server • 277

Setting the IPv6 Secondary DNS Server • 277

Setting the LAN Interface Parameters • 278

Setting the LED Operation Mode • 369

Setting the Lower Critical Threshold for a Circuit Breaker • 335

Setting the Lower Critical Threshold for an Inlet Pole • 328

Setting the Lower Warning Threshold for a Circuit Breaker • 336

Setting the Lower Warning Threshold for an Inlet Pole • 329

Setting the Network Service Parameters • 279

Setting the Networking Mode • 263

Setting the NTP Parameters • 288

Setting the Outer Authentication • 267

Setting the Outlet Initialization Delay · 258

Setting the Outlet Power-On Sequence • 142, 255

Setting the Outlet Power-On Sequence Delay • 255

Setting the Outlet-Specific Default State • 137, 138

Setting the Outlet-Specific Power-On Delay • 143

Setting the PDU-Defined Cycling Power-Off Period • 257, 313

Setting the PDU-Defined Default Outlet State • 256, 312

Setting the PDU-Defined Default State • 137, 138

Setting the Polling Interval • 362

Setting the Preferred Host Name • 271

Setting the PSK • 266

Setting the Sensor's Assertion Timeout • 342

Setting the Sensor's Deassertion Hysteresis • 342

Setting the Sensor's Lower Critical Threshold · 340

Setting the Sensor's Lower Warning Threshold • 341

Setting the Sensor's Upper Critical Threshold • 338

Setting the Sensor's Upper Warning Threshold • 339

Setting the Serial Port Baud Rate • 372

Setting the SNMP Configuration • 282

Setting the SNMP Read Community • 284

Setting the SNMP Write Community • 284

Setting the SSID · 265

Setting the sysContact Value • 284

Setting the sysLocation Value • 285

Setting the sysName Value • 285

Setting the Upper Critical Threshold for a Circuit Breaker • 333

Setting the Upper Critical Threshold for an Inlet Pole • 326

Setting the Upper Warning Threshold for a Circuit Breaker • 334

Setting the Upper Warning Threshold for an Inlet Pole • 327

Setting the Wireless Parameters • 265

Setting the X Coordinate • 317

Setting the Y Coordinate • 317

Setting the Z Coordinate • 261, 318

Setting the Z Coordinate Format • 190

Setting the Z Coordinate Format for Environmental Sensors • 261, 318

Setting Up an SSL Certificate • 110, 123

Setting Up LDAP Authentication • 90, 110, 128, 400

Setting Up Role-Based Access Control Rules • xiv, 118

Setting Up Roles • 67, 99, 102, 105, 107

Setting Up User Login Controls • 116

Setup Button • 73

Show Commands • 415

Showing Information • xiv, 234

Showing the Network Connections • 382

Single Login Limitation • 298

Snapshot Storage • 208

SNMP Gets and Sets • 227

SNMP Sets and Thresholds • 229

Sorting Firewall Rules • 115

Sorting Role-Based Access Control Rules • 122

Sorting the LDAP Access Order • 131

Special Character Requirement • 304

Specifications · 5, 387

Specifying Non-Critical Outlets • 247, 259

Specifying the Asset Sensor Orientation • 366

Specifying the Device Altitude • 98, 260

Specifying the EnergyWise Domain • 361

Specifying the EnergyWise Secret • 361

Specifying the Number of Rack Units • 364

Specifying the Primary NTP Server • 288

Specifying the Rack Unit Numbering Mode • 364

Index

Specifying the Rack Unit Numbering Offset • 365

Specifying the Secondary NTP Server • 289

Specifying the Sensor Type • 316

States of Managed Sensors • 193

Status Bar • 73

Step A. Determine User Accounts and Groups • 396

Step B. Configure User Groups on the AD Server • 397

Step C. Configure LDAP Authentication on the Dominion PX Device • 398

Step D. Configure User Groups on the Dominion PX Device • 400

Strong Passwords · 301

Supported Web Browsers • 65

Supported Wireless LAN Configuration • 22

Switching an Outlet • 136

Switching Multiple or All Outlets • 135

T

Testing the LDAP Server Connection • 132

Testing the Network Connectivity • 383

The Dominion PX MIB • 227

The Yellow- or Red-Highlighted Reading • 76, 81, 82, 148, 149, 192, 217

Three-Digit Row • 55

Time Configuration Commands • xiv, 287

Tracing the Network Route • 210

Tracing the Route • 384

Truncated Data in the Web Interface • xv, 418

Turning Off the Outlet(s) • 377

Turning On the Outlet(s) • 376

Two-Digit Row • 56

U

Unblocking a User • 116, 379

Unmanaging Environmental Sensors • 189, 195

Unpacking the Product and Components • 15

Updating the Asset Sensor Firmware • 222

Updating the Dominion PX Firmware • 29, 219

Uppercase Character Requirement • 303

User Blocking • 300

User Configuration Commands • 343

User Management • 102

Using SNMP • 220, 224

Using the CLI Command • 380, 394

Using the Command Line Interface • 90, 191, 230, 394

Using the PDU • 50

Using the Reset Button • 393

Using the Web Interface • 23, 65

V

Viewing Connected Users • 183

Viewing Details • 216

Viewing Firmware Update History • 221

Viewing Sensor Data • 192

Viewing the Communication Log • 74, 211

Viewing the Dashboard • 81

Viewing the Local Event Log • 182

Viewing the Summary • 216, 218

Viewing the Webcam Images or Videos • 48, 206, 209

W

Warning Icon • 76

What is Assertion Timeout? • 151, 152, 153, 154, 190, 325, 333, 338, 343

What is Deassertion Hysteresis? • 150, 151, 152, 153, 181, 190, 215, 324, 332, 337, 342

What's New in the Dominion PX User Guide • xiv

Wired Network Settings • 84

Wireless Configuration • 235

Wireless Network Settings • 85

With HyperTerminal • 231, 379

With SSH or Telnet • 232

Z

Zero U Products • 4

Raritan.

U.S./Canada/Latin America

Monday - Friday

8 a.m. - 6 p.m. ET

Phone: [phone] or 732-764-8886

For CommandCenter NOC: Press 6, then Press 1

For CommandCenter Secure Gateway: Press 6, then Press 2

Fax: [phone]

Email for CommandCenter NOC: [e-mail]

Email for all other products: [e-mail]

China

Beijing

Monday - Friday

9 a.m. - 6 p.m. local time

Phone: [phone]

Shanghai

Monday - Friday

9 a.m. - 6 p.m. local time

Phone: [phone]

GuangZhou

Monday - Friday

9 a.m. - 6 p.m. local time

Phone: [phone]

India

Monday - Friday

9 a.m. - 6 p.m. local time

Phone: [phone]

Japan

Monday - Friday

9:30 a.m. - 5:30 p.m. local time

Phone: [phone]

Email: [e-mail]

Europe

Europe

Monday - Friday

8:30 a.m. - 5 p.m. GMT+1 CET

Phone: [phone]

Email: [e-mail]

United Kingdom

Monday - Friday

8:30 a.m. to 5 p.m. GMT

Phone [phone]

France

Monday - Friday

8:30 a.m. - 5 p.m. GMT+1 CET

Phone: [phone]

Germany

Monday - Friday

8:30 a.m. - 5:30 p.m. GMT+1 CET

Phone: [phone]

Email: [e-mail]

Melbourne, Australia

Monday - Friday

9:00 a.m. - 6 p.m. local time

Phone: [phone]

Taiwan

Monday - Friday

9 a.m. - 6 p.m. GMT -5 Standard -4 Daylight

Phone: [phone]

Email: [e-mail]