PX2-5524K2 - Inverter Raritan - Free user manual and instructions

USER MANUAL PX2-5524K2 Raritan

PX2-3000/4000/5000 Series

User Guide

Xerus™ Firmware v3.5.0

Copyright © 2019 Raritan, Inc.

DPX2-1C-v3.5.0-E

January 2019

255-80-6101-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.

Tip 1: The outlet (socket) shall be installed near the equipment and shall be easily accessible.

Tip 2: For detailed information on any Raritan PDU's overcurrent protectors' design, refer to that model's product specification on Raritan website's PDU Product Selector page https://www.raritan.com/product-selector.

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

If a power cable is included with this product, it must be used exclusively for this product.

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

Warning

This is a class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.

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 xvii

What's New in the PX2 User Guide xix

Chapter 1 Introduction 1

Product Models....1

Package Contents....1

Zero U Products 2

1U Products....2

2U Products.... 2

APIPA and Link-Local Addressing 2

Before You Begin 3

Unpacking the Product and Components.... 3

Preparing the Installation Site....4

Checking the Branch Circuit Rating 4

Filling Out the Equipment Setup Worksheet 4

Chapter 2 Rackmount, Inlet and Outlet Connections 5

Circuit Breaker Orientation Limitation 5

Rack-Mounting the PDU....5

Rackmount Safety Guidelines....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....8

Mounting Zero U Models Using Two Rear Buttons 10

Mounting 1U or 2U Models .... 11

Installing Cable Retention Clips on the Inlet (Optional) 12

Installing Cable Retention Clips on Outlets (Optional) 13

Locking Outlets and Cords 14

SecureLock™ Outlets and Cords 14

Button-Type Locking Outlets....16

Chapter 3 Initial Installation and Configuration

17

Connecting the PDU to a Power Source 17

Connecting the PX2 to Your Network....17

USB Wireless LAN Adapters....18

Supported Wireless LAN Configuration 19

Configuring the PX2....19

Connecting a Mobile Device to PX2 20

Connecting the PX2 to a Computer 25

Bulk Configuration Methods 27

Cascading Multiple PX2 Devices for Sharing Ethernet Connectivity.... 28

Cascading Guidelines for Port Forwarding 29

Cascading All Devices via USB 30

Chapter 4 Connecting External Equipment (Optional)

33

Connecting Raritan Environmental Sensor Packages 33

Identifying the Sensor Port 33

DX2 Sensor Packages 34

DX Sensor Packages 35

DPX3 Sensor Packages 37

DPX2 Sensor Packages 38

DPX Sensor Packages....41

Using an Optional DPX3-ENVHUB4 Sensor Hub 46

Mixing Diverse Sensor Types....47

Guidelines for PX2 with Two Sensor Ports 52

Connecting Asset Management Strips.... 53

Combining Regular Asset Strips 53

Introduction to Asset Tags 55

Connecting Regular Asset Strips to PX2 56

Connecting Blade Extension Strips 58

Connecting Composite Asset Strips (AMS-Mx-Z)....60

Using an X Cable 63

Connecting a Logitech Webcam....65

Connecting a GSM Modem 66

Connecting an Analog Modem 66

Connecting an External Beeper 67

Connecting a Schroff LHX/SHX Heat Exchanger 67

Chapter 5 Introduction to PDU Components 69

Panel Components 69

Power Cord....69

Contents

Outlets 69

Connection Ports....71

LED Display 73

Reset Button 78

Circuit Breakers 79

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

Resetting the Handle-Type Circuit Breaker 80

Fuse 81

Fuse Replacement on Zero U Models 81

Fuse Replacement on 1U Models....82

Beeper 84

Threaded Grounding Point 84

Chapter 6 Using the Web Interface 86

Supported Web Browsers 86

Login, Logout and Password Change....86

Login 86

Changing Your Password....88

Remembering User Names and Passwords 90

Logout 90

Web Interface Overview....90

Menu....92

Quick Access to a Specific Page 95

Sorting a List....96

Dashboard 97

Dashboard - Inlet I1 99

Dashboard - OCP 101

Dashboard - Alerted Sensors 102

Dashboard - Inlet History 103

Dashboard - Alarms.... 106

PDU 107

Internal Beeper State 110

Options for Outlet State on Startup 110

Initialization Delay Use Cases.... 111

Inrush Current and Inrush Guard Delay.... 111

Time Units 112

Setting Thresholds for Total Active Energy or Power 112

Inlet....113

Configuring a Multi-Inlet Model.... 116

Outlets 118

Available Data of the Outlets Overview Page 122

Bulk Configuration for Outlet Thresholds 123

Setting Outlet Power-On Sequence and Delay 124

Setting Non-Critical Outlets 125

Load Shedding Mode....126

Contents

Off and Lock Icons for Outlets 128

Individual Outlet Pages 129

Outlet Groups.... 136

Creating an Outlet Group....137

Outlet Group Power Control 138

Resetting a Group's Active Energy 141

Modifying an Outlet Group 143

Deleting an Outlet Group 146

Viewing More Information.... 147

OCPs 149

Individual OCP Pages 152

Peripherals 156

Yellow- or Red-Highlighted Sensors.... 163

Managed vs Unmanaged Sensors/Actuators 164

Sensor/Actuator States.... 165

Finding the Sensor's Serial Number 166

Identifying the Sensor Position and Channel 167

How the Automatic Management Function Works.... 169

Managing One Sensor or Actuator 170

Individual Sensor/Actuator Pages 171

Z Coordinate Format....177

Feature Port 178

Asset Strip 179

External Beeper 187

Schroff LHX/SHX 187

Power CIM 192

User Management 192

Creating Users 193

Editing or Deleting Users.... 197

Creating Roles....199

Editing or Deleting Roles 201

Setting Your Preferred Measurement Units 202

Setting Default Measurement Units 202

Device Settings 203

Configuring Network Settings 205

Configuring Network Services.... 226

Configuring Security Settings.... 234

Setting the Date and Time 258

Event Rules and Actions 262

Setting Data Logging.... 322

Configuring Data Push Settings 323

Monitoring Server Accessibility.... 331

Front Panel Settings 340

Configuring the Serial Port 340

Lua Scripts 342

Miscellaneous 348

Contents

Maintenance 350

Device Information 351

Viewing Connected Users 357

Viewing or Clearing the Local Event Log 358

Updating the PX2 Firmware 359

Viewing Firmware Update History 363

Bulk Configuration 364

Backup and Restore of Device Settings....371

Network Diagnostics....372

Downloading Diagnostic Information 374

Hardware Issue Detection 374

Rebooting the PX2 375

Resetting All Settings to Factory Defaults 376

Retrieving Software Packages Information....377

Webcam Management....377

Configuring Webcams and Viewing Live Images.... 379

Sending Links to Snapshots or Videos 382

Viewing and Managing Locally-Saved Snapshots 385

Changing Storage Settings 387

Chapter 7 Using SNMP 391

Enabling and Configuring SNMP 391

SNMPv2c Notifications....392

SNMPv3 Notifications 393

Downloading SNMP MIB 396

SNMP Gets and Sets 396

The PX2 MIB 397

Retrieving Energy Usage 399

A Note about Enabling Thresholds 399

Chapter 8 Using the Command Line Interface 400

About the Interface 400

Logging in to CLI....401

With HyperTerminal....401

With SSH or Telnet 402

With an Analog Modem 403

Different CLI Modes and Prompts 403

Closing a Local Connection 404

The ? Command for Showing Available Commands 404

Querying Available Parameters for a Command.... 405

Showing Information 405

Network Configuration....406

PDU Configuration 410

Outlet Information 410

Contents

Outlet Group Information....411

Inlet Information 411

Overcurrent Protector Information 412

Date and Time Settings 413

Default Measurement Units 413

Environmental Sensor Information 414

Environmental Sensor Package Information 415

Actuator Information 416

Outlet Sensor Threshold Information 417

Outlet Pole Sensor Threshold Information 417

Outlet Group Threshold Information 419

Inlet Sensor Threshold Information 419

Inlet Pole Sensor Threshold Information 420

Overcurrent Protector Sensor Threshold Information 421

Environmental Sensor Threshold Information 422

Environmental Sensor Default Thresholds 423

Security Settings 424

Authentication Settings....425

Existing User Profiles 426

Existing Roles 427

Load Shedding Settings 427

Serial Port Settings 427

EnergyWise Settings 428

Asset Strip Settings 428

Rack Unit Settings of an Asset Strip 428

Blade Extension Strip Settings 429

Event Log....430

Wireless LAN Diagnostic Log 431

Server Reachability Information 431

Command History 432

Reliability Data 433

Reliability Error Log 433

Reliability Hardware Failures 433

Examples....433

Clearing Information 435

Clearing Event Log 435

Clearing WLAN Log....436

Configuring the PX2 Device and Network 436

Entering Configuration Mode 436

Quitting Configuration Mode 437

PDU Configuration Commands.... 437

Network Configuration Commands 444

Time Configuration Commands 468

Checking the Accessibility of NTP Servers 471

Security Configuration Commands.... 472

Outlet Configuration Commands 491

Contents

Outlet Group Configuration Commands 493

Inlet Configuration Commands....495

Overcurrent Protector Configuration Commands.... 497

User Configuration Commands 497

Role Configuration Commands....509

Authentication Commands 514

Environmental Sensor Configuration Commands 526

Configuring Environmental Sensors' Default Thresholds 530

Sensor Threshold Configuration Commands.... 532

Actuator Configuration Commands.... 543

Server Reachability Configuration Commands 545

EnergyWise Configuration Commands.... 548

Asset Management Commands 550

Serial Port Configuration Commands 556

Multi-Command Syntax 558

Load Shedding Configuration Commands 560

Enabling or Disabling Load Shedding....560

Power Control Operations....561

Turning On the Outlet(s) 561

Turning Off the Outlet(s) 562

Power Cycling the Outlet(s) 563

Canceling the Power-On Process.... 564

Example - Power Cycling Specific Outlets 564

Actuator Control Operations 564

Switching On an Actuator....565

Switching Off an Actuator 565

Example - Turning On a Specific Actuator 566

Unblocking a User 566

Resetting the PX2 566

Restarting the PDU 566

Resetting Active Energy Readings....567

Resetting to Factory Defaults 568

Network Troubleshooting....568

Entering Diagnostic Mode.... 568

Quitting Diagnostic Mode....569

Diagnostic Commands....569

Contents

Retrieving Previous Commands.... 571

Automatically Completing a Command 571

Logging out of CLI....572

Chapter 9 Using SCP Commands 573

Firmware Update via SCP 573

Bulk Configuration via SCP 574

Backup and Restore via SCP 575

Downloading Diagnostic Data via SCP 576

Uploading or Downloading Raw Configuration Data 578

Keys that Cannot Be Uploaded 582

Chapter 10 In-Line Monitors 583

Overview 583

Safety Instructions....583

Flexible Cord Installation Instructions 584

Flexible Cord Selection 585

Plug Selection 585

Receptacle Selection 585

Derating a Raritan Product 585

Wiring of 3-Phase In-Line Monitors 586

In-Line Monitor Unused Channels....587

Step by Step Flexible Cord Installation 587

In-Line Monitor's LED Display 592

Automatic Mode 592

Manual Mode....592

In-Line Monitor's Web Interface 593

Dashboard Page 593

Inlets/Outlets Page 598

Appendix A Specifications 601

Maximum Ambient Operating Temperature....601

Serial RS-232 "DB9" Port Pinouts 601

Sensor RJ-12 Port Pinouts 602

Feature RJ-45 Port Pinouts 602

Appendix B Equipment Setup Worksheet 604

Appendix C Configuration or Firmware Upgrade with a USB Drive 607

Device Configuration/Upgrade Procedure....607

System and USB Requirements 608

Configuration Files 609

fwupdate.cfg 609

config.txt 614

devices.csv 616

Creating Configuration Files via Mass Deployment Utility 617

Data Encryption in 'config.txt' 618

Firmware Upgrade via USB 620

Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP 622

Bulk Configuration/Upgrade Procedure 622

TFTP Requirements....623

DHCP IPv4 Configuration in Windows 624

DHCP IPv6 Configuration in Windows 634

DHCP IPv4 Configuration in Linux....641

DHCP IPv6 Configuration in Linux 643

Appendix E Raw Configuration Upload and Download 645

Downloading Raw Configuration.... 645

Download via Web Browsers 645

Download via Curl 646

Uploading Raw Configuration.... 647

Upload via Curl 648

Curl Upload Return Codes 649

Appendix F Resetting to Factory Defaults 651

Using the Reset Button 651

Using the CLI Command 652

Appendix G LDAP Configuration Illustration 654

Step A. Determine User Accounts and Roles 654

Step B. Configure User Groups on the AD Server 655

Step C. Configure LDAP Authentication on the PX2 655

Step D. Configure Roles on the PX2....657

Appendix H Updating the LDAP Schema 660

Returning User Group Information 660

From LDAP/LDAPS 660

From Microsoft Active Directory....660

Setting the Registry to Permit Write Operations to the Schema.... 661

Creating a New Attribute....661

Adding Attributes to the Class 662

Updating the Schema Cache 664

Editing rciusergroup Attributes for User Members 664

Appendix I RADIUS Configuration Illustration 667

Standard Attributes 667

NPS Standard Attribute Illustration 667

FreeRADIUS Standard Attribute Illustration 684

Vendor-Specific Attributes 685

NPS VSA Illustration 685

FreeRADIUS VSA Illustration....696

AD-Related Configuration 697

Appendix J Additional PX2 Information 701

MAC Address 701

Reserving IP Addresses in DHCP Servers 701

Reserving IP in Windows....702

Reserving IP in Linux 703

Sensor Threshold Settings....705

Thresholds and Sensor States....705

"To Assert" and Assertion Timeout 707

Contents

"To De-assert" and Deassertion Hysteresis 709

Default Voltage and Current Thresholds 711

Altitude Correction Factors 713

Unbalanced Current Calculation.... 714

Data for BTU Calculation....715

Ways to Probe Existing User Profiles 715

Raritan Training Website 716

Role of a DNS Server 716

Cascading Troubleshooting....716

Possible Root Causes 717

Slave Device Events in the Log 719

The Ping Tool....719

Installing the USB-to-Serial Driver (Optional) 719

Initial Network Configuration via CLI 721

Device-Specific Settings....726

TLS Certificate Chain....726

What is a Certificate Chain 726

Illustration - GMAIL SMTP Certificate Chain.... 730

Browsing through the Online Help....733

Appendix K Integration 735

Dominion KX II / III Configuration.... 735

Configuring Rack PDU Targets 735

Turning Outlets On/Off and Cycling Power 739

Dominion KSX II, SX or SX II Configuration 740

Dominion KSX II....740

Dominion SX and SX II....741

Power IQ Configuration 745

dcTrack 745

dcTrack Overview 746

Asset Management Strips and dcTrack 747

Index 749

Applicable Models

This User Guide is applicable to the following PDU Generation.

• PX2 PDU Generation (3000/4000/5000 series)

Any PX Generations can be associated with existing metering families called "Series", from 1000 series to 5000 series.

For example, PX2-4000, PX3-4000 series and PX3-iX7-4000 series are all inlet metered and outlet metered PDUs, but have different controller generations.

Note: For information on other PX2, PX3 or PX3-iX7 models, see their respective Online Help or User Guide on the Raritan website's Support page (http://www.raritan.com/support/).

PX models comparison in brief:

Features	Inlet power measurement	Outlet power measurement	Outlet switching	Load shedding
1000 Series
2000 Series
3000 Series (Inline meters)
4000 Series
5000 Series

Important: PDUs with similar model names but of different product families may vary in their designs. For example, PX2-5660V and PX3-5660V do NOT share the same outlet sequence and technical designs. For details on a model's technical design, refer to their product specifications on Raritan website's PDU Product Selector page https://www.raritan.com/product-selector.

▶ Comparison between PX2, PX3 and PXC series:

Product models PX2 PX3 PXC
Front panel display	LED display	Dot-matrix LCD display	Dot-matrix LCD display
Outlet latching relays		*
Number of LAN ports	1	2 2
Maximum LAN rate	100 Mbps **	1,000 Mbps	100 Mbps
Replaceable controller		***
Number of USB-A ports	1	2 1
Maximum USB rate	12 Mbps	480 Mbps 480 Mbps
RS-232 port (CONSOLE/MODEM)	Male DB9 Connector	RJ-45 Connector	RJ-45 Connector
Expansion ports		****
SENSOR port type	R J - 1 2	R J - 4 5	R J - 4 5

* Only PX3 models with outlet switching have outlet latching relays.
** A few customized PX2 models also support the Ethernet speed up to 1000 Mbps.
*** Only PX3 "Zero U" models have the replaceable controller.
**** PX3 Expansion port is designed for power sharing of controllers.

Note: PX3 in this table only refers to PX3 PDUs with "iX7" controller.

What's New in the PX2 User Guide

Important: If your PX2 is running any firmware version older than 3.3.0, you must upgrade it to 3.3.x or 3.4.x before upgrading it to

3.5.0 or later. See Updating the PX2 Firmware (on page 359).

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

Applicable Models (on page xvii)

Supported Wireless LAN Configuration (on page 19)

Saving User Credentials for PDView's Automatic Login (on page 23)

Bulk Configuration Methods (on page 27)

Cascading All Devices via USB(on page 30)

DX2 Sensor Packages (on page 34)

DX Sensor Packages (on page 35)

DPX3 Sensor Packages (on page 37)

DPX2 Sensor Packages (on page 38)

DPX Sensor Packages (on page 41)

Using an Optional DPX-ENVHUB4 Sensor Hub (on page 43)

Using an Optional DPX-ENVHUB2 Cable (on page 44)

Supported Maximum DPX Sensor Distances (on page 45)

Mixing Diverse Sensor Types (on page 47)

Guidelines for PX2 with Two Sensor Ports (on page 52)

Connecting a Logitech Webcam (on page 65)

PX2-5000 Series (on page 70)

Threaded Grounding Point (on page 84)

Supported Web Browsers (on page 86)

Login (on page 86)

Web Interface Overview (on page 90)

Menu (on page 92)

Dashboard (on page 97)

Dashboard - Inlet 11 (on page 99)

Dashboard - Alarms (on page 106)

PDU (on page 107)

Off and Lock Icons for Outlets (on page 128)

Outlet Groups (on page 136)

Creating an Outlet Group (on page 137)

Outlet Group Power Control (on page 138)

If Switchable Outlet Groups are Limited (on page 141)

Resetting a Group's Active Energy (on page 141)

Modifying an Outlet Group (on page 143)

Deleting an Outlet Group (on page 146)

Viewing More Information (on page 147)

Peripherals (on page 156)

Configuring Network Settings (on page 205)

Changing HTTP(S) Settings (on page 228)

Setting the Date and Time(on page 258)

Default Log Messages (on page 269)

Available Actions (on page 284)

Shut down a Server and Control its Power(on page 290)

Send Email (on page 292)

Send SMS Message (on page 296)

Switch Outlet Group (on page 301)

Placeholders for Custom Messages (on page 310)

Configuring Data Push Settings (on page 323)

Data Push Format (on page 325)

Sensor Log (on page 325)

Sensor Descriptors for Inlet Active Power(on page 326)

Log Rows (on page 327)

Asset Management Tag List (on page 328)

Asset Management Log (on page 330)

Monitoring Server Accessibility (on page 331)

Server Status Checking or Power Control (on page 336)

Miscellaneous (on page 348)

Maintenance (on page 350)

Updating the PX2 Firmware (on page 359)

Bulk Configuration (on page 364)

Performing Bulk Configuration (on page 368)

Hardware Issue Detection(on page 374)

Outlet Group Information (on page 411)

Outlet Group Threshold Information (on page 419)

Reliability Hardware Failures (on page 433)

Setting IPv4 Static Routes (on page 447)

Setting IPv6 Static Routes (on page 451)

Configuring the Cascading Mode (on page 459)

Outlet Group Configuration Commands (on page 493)

Creating an Outlet Group (on page 493)

Managing an Outlet Group (on page 494)

Powering On/Off/Cycle Outlet Groups (on page 495)

Sensor Threshold Configuration Commands (on page 532)

Commands for Outlet Group Sensors (on page 534)

Resetting Active Energy Readings (on page 567)

Bulk Configuration via SCP(on page 574)

Uploading or Downloading Raw Configuration Data (on page 578)

Keys that Cannot Be Uploaded (on page 582)

Device Configuration/Upgrade Procedure (on page 607)

fwupdate.cfg (on page 609)

config.txt (on page 614)

Firmware Upgrade via USB(on page 620)

Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 622)

Bulk Configuration/Upgrade Procedure (on page 622)

Raw Configuration Upload and Download (on page 645)

Downloading Raw Configuration (on page 645)

Download via Web Browsers (on page 645)

Download via Curl (on page 646)

Uploading Raw Configuration (on page 647)

Upload via Curl (on page 648)

Curl Upload Return Codes(on page 649)

"To De-assert" and Deassertion Hysteresis (on page 709)

Data for BTU Calculation (on page 715)

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

Chapter 1 Introduction

Raritan's PX2 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 PX2 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 PX2 models -- 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

Package Contents....1

APIPA and Link-Local Addressing....2

Before You Begin....3

Product Models

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

Download the PX2 Data Sheet from Raritan's website, visit the Product Selector page (http://www.findmypdu.com/) on Raritan's website, or contact your local reseller for a list of available models.

Package Contents

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

Zero U Products

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

1U Products

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

2U Products

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

APIPA and Link-Local Addressing

The PX2 supports Automatic Private Internet Protocol Addressing (APIPA).

With APIPA, your PX2 automatically configures a link-local IP address and a link-local host name when it cannot obtain a valid IP address from any DHCP server in the TCP/IP network.

Only IT devices connected to the same subnet can access the PX2 using the link-local address/host name. Those in a different subnet cannot access it.

Exception: PX2 in the Port Forwarding mode does not support APIPA.

See Setting the Cascading Mode (on page 218).

Once the PX2 can get a DHCP-assigned IP address, it stops using APIPA and the link-local address is replaced by the DHCP-assigned address.

Scenarios where APIPA applies:

- DHCP is enabled on the PX2, but no IP address is assigned to the PX2.

This may be caused by the absence or malfunction of DHCP servers in the network.

Note: Configuration by connecting the PX2 to a computer using a network cable is an application of this scenario. See Connecting the PX2 to a Computer (on page 25).

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

Link-local addressing:

- IPv4 address:

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

- IPv6 address:

A link-local IPv6 address is available only after IPv6 is enabled on the PX2. See Configuring Network Settings (on page 205).

- Host name - pdu.local:

You can type https://pdu.local to access the PX2 instead of typing the link-local IP address.

▶ Retrieval of the link-local address:

- Perform the first three steps in the Initial Network Configuration via CLI(on page 721).

Before You Begin

Before beginning the installation, perform the following activities:

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

Unpacking the Product and Components

1. Remove the PX2 and other equipment from the box in which they were shipped. See Package Contents (on page 1) 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 Technical Support Department for assistance.
4. Verify that all circuit breakers on the PX2 are set to ON. If not, turn them ON.
   Or make sure that all fuses are inserted and seated properly. If there are any fuse covers, ensure that they are closed.

Note: Not all models have overcurrent protectors.

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 601).

1. Allow sufficient space around the PX2 for cabling and outlet connections.
2. Review Safety Instructions (on page iii) listed in this User Guide.

Checking the Branch Circuit Rating

The rating of the branch circuit supplying power to the PDU shall be in accordance with national and local electrical codes.

Filling Out the Equipment Setup Worksheet

An Equipment Setup Worksheet is provided in this User Guide. See Equipment Setup Worksheet (on page 604). 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.

Chapter 2 Rackmount, Inlet and Outlet Connections

In This Chapter

Circuit Breaker Orientation Limitation....5

Rack-Mounting the PDU....5

Installing Cable Retention Clips on the Inlet (Optional) 12

Installing Cable Retention Clips on Outlets (Optional) 13

Locking Outlets and Cords....14

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

Rack-Mounting the PDU

This chapter describes how to rack mount a PX2. Only the most common rackmount method is displayed. Follow the procedure suitable for your model.

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 601) 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.

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.

Pure vertical line diagram with no text, numbers, or symbols

Technical line drawing of a vertical rectangular structure with mounting holes and internal components (no text or symbols)

To mount Zero U models using L-brackets:

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

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 PX2 device.

2. 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 bolt holes and a base plate (no text or symbols)

1. Using rack screws, fasten the PX2 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.

Technical line drawing of two vertical rectangular components with mounting holes, no text or symbols present

To mount Zero-U models using button mount:

1. Align the baseplates on the rear of the PX2 device. Leave at least 24 inches between the baseplates for stability.
2. Make the baseplates grasp the device lightly. Use the included L-shaped hex key to loosen the hex socket screws until the baseplate is "slightly" fastened.
3. Screw each mounting button in the center of each baseplate. The recommended torque for the button is 1.96 N·m (20 kgf·cm).

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 PX2 device forward, pushing the mounting buttons through the mounting holes, then letting the device drop about 5/8". This secures the PX2 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.

Pure electrical circuit lines without any symbols

Isometric line drawing of a vertical metal frame with two side panels and mounting holes (no text or symbols)

To mount Zero U models using claw-foot brackets:

1. Align the baseplates on the rear of the PX2 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 PX2 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 PX2 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 line diagram without any text, numbers, or symbols

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

Pure technical line drawing of a mechanical component with no text or symbols

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 PX2 device forward, pushing the mounting buttons through the mounting holes, then letting the device drop slightly. This secures the PX2 device in place and completes the installation.

Mounting 1U or 2U Models

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

To mount the PX2 device:

1. Attach a rackmount bracket to both sides of the PX2 with the provided screws.

Technical line drawing of a rectangular electronic device with mounting holes and a side panel (no text or symbols)

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

Diagram showing a device transitioning from a rectangular panel to a rectangular frame with circular holes, indicated by an arrow (no text or symbols present)

1. Secure with the provided end cap screws.

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

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

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

Installing Cable Retention Clips on the Inlet (Optional)

If your PX2 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 a lever and a close-up of its internal components, both without any 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

Technical illustration of two electrical plug connectors (no text or symbols)

Installing Cable Retention Clips on Outlets (Optional)

If your PX2 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. See Locking Outlets and Cords (on page 14).

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

1. Locate two tiny holes at two sides of an outlet.

2. Install the cable retention clip by inserting two ends of the clip into the tiny holes.

graph TD
    A["Switch 1"] --> B["Switch 2"]
    C["Switch 3"] --> D["Switch 4"]
    E["Switch 5"] --> F["Switch 6"]
    G["Switch 7"] --> H["Switch 8"]
    I["Switch 9"] --> J["Switch 10"]
    K["Switch 11"] --> L["Switch 12"]
    M["Switch 13"] --> N["Switch 14"]
    O["Switch 15"] --> P["Switch 16"]
    Q["Switch 17"] --> R["Switch 18"]
    S["Switch 19"] --> T["Switch 20"]
    U["Switch 21"] --> V["Switch 22"]
    W["Switch 23"] --> X["Switch 24"]
    Y["Switch 25"] --> Z["Switch 26"]
    AA["Switch 27"] --> AB["Switch 28"]
    AC["Switch 29"] --> AD["Switch 30"]
    AE["Switch 31"] --> AF["Switch 32"]
    AG["Switch 33"] --> AH["Switch 34"]
    AI["Switch 35"] --> AJ["Switch 36"]
    AK["Switch 37"] --> AL["Switch 38"]
    AM["Switch 39"] --> AN["Switch 40"]
    AO["Switch 41"] --> AP["Switch 42"]
    AQ["Switch 43"] --> AR["Switch 44"]
    AS["Switch 45"] --> AT["Switch 46"]
    AU["Switch 47"] --> AV["Switch 48"]
    AW["Switch 49"] --> AX["Switch 50"]

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

Illustration of a hand connecting three electrical socket plugs to a cable (no text or symbols)

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

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 each side of its plug. The following diagram illustrates such a plug.

Diagram of a plug with labeled terminals A and a cable, no text or symbols present

Item Description

A Latches on the SecureLock

^TH cord's plug

Only specific PDUs are implemented with the SecureLock ^™ mechanism. If your 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.

Chapter 2: Rackmount, Inlet and Outlet Connections

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

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 adjacent to 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 or change.

1. Unplug the power cord now.

Chapter 3 Initial Installation and Configuration

This chapter explains how to install your PX2 and configure it for network connectivity.

In This Chapter

Connecting the PDU to a Power Source 17

Connecting the PX2 to Your Network....17

Configuring the PX2....19

Bulk Configuration Methods ...... 27

Cascading Multiple PX2 Devices for Sharing Ethernet Connectivity......28

Connecting the PDU to a Power Source

1. Verify that all circuit breakers on the PX2 are set to ON. If not, turn them ON. Or make sure that all fuses are inserted and seated properly. If there are any fuse covers, ensure that they are closed.

Note: Not all models have overcurrent protectors.

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

Note: When a PX2 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 that outlet LEDs are only available on some PDU models.

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

Connecting the PX2 to Your Network

To remotely administer the PX2, you must connect the PX2 to your local area network (LAN). PX2 can be connected to a wired or wireless network.

Note: If your PX2 will work as a master device in the bridging mode, you must make a wired connection. See Cascading Multiple PX2 Devices for Sharing Ethernet Connectivity (on page 28).

To make a wired connection:

1. Connect a standard network patch cable to the Ethernet port on the PX2.
2. Connect the other end of the cable to your LAN.

Below indicates the ETHERNET port on PX Zero U models:

Raritan RESET CATLET/LIME I/OI/UB UP BOTH SCAND CURRENT (A) VOLTAGE (O) POWER (W) VERLOAD (V) SENSOR FEATURE USB-B SENSOR ETHERNET USB-A CONSOLE/ORDER

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

Warning: Accidentally plugging an RS-232 RJ-45 connector into the Ethernet port can cause permanent damage(s) to the Ethernet hardware.

To make a wireless connection:

Do one of the following:

• Plug a supported USB wireless LAN adapter into the USB-A port on your PX2.
• Connect a USB hub to the USB-A port on the PX2. Then plug the supported USB wireless LAN adapter into the appropriate USB port on the hub.

See USB Wireless LAN Adapters (on page 18) for a list of supported wireless LAN adapters.

USB Wireless LAN Adapters

The PX2 supports the following USB Wi-Fi LAN adapters.

Wi-Fi LAN adapters Supported 802.11

protocols

SparkLAN WUBR-508N A/B/G/N

Wi-Fi LAN adapters Supported 802.11 protocols
Proxim Orinoco 8494 A/B/G
Zyxel NWD271N B/G
Edimax EW-7722UnD A/B/G/N
TP-Link TL-WDN3200 v1 A/B/G/N
Raritan USB WIFI A/B/G/N

Supported Wireless LAN Configuration

If wireless networking is preferred, ensure that the wireless LAN configuration of your PX2 matches the access point. The following is the wireless LAN configuration that the PX2 supports.

■ Network type: 802.11 A/B/G/N
■ Protocol: WPA2 (RSN)
■ Key management: WPA-PSK, or WPA-EAP with PEAP and MSCHAPv2 authentication
■ Encryption: CCMP (AES)

Tip 1: Supported 802.11 network protocols vary according to the wireless LAN adapter being used with the PX2. See USB Wireless LAN Adapters (on page 18).

Tip 2: You must configure PX2 to enable its wireless LAN interface. See the topic titled Configuring Network Settings (on page 205) in the User Guide.

Configuring the PX2

You can initially configure the PX2 via one of the following:

• A mobile device with PDView installed
  • A TCP/IP network that supports DHCP
• A computer physically connected to the PX2

Configuration via a connected mobile device:

1. Download the PDView app to your mobile device. See Connecting a Mobile Device to PX2(on page 20).
2. Connect the mobile device to PX2 via USB.
3. Launch PDView to configure the PX2.

Configuration over a DHCP-enabled network:

1. Connect the PX2 to a DHCP IPv4 network. See Connecting the PX2 to Your Network (on page 17).
2. Retrieve the DHCP-assigned IPv4 address. Do one of the following:

- Perform the first three steps in the section titled Initial Network Configuration via CLI (on page 721). The IPv4 address is displayed in the communications program as illustrated below.

Login for PX2 CLI (192.168.84.30) Enter 'unblock' to unblock a user. Username:

- Use the MAC address of the PX2 to retrieve the IP address. Contact your administrator for help. See MAC Address (on page 701).

1. La unch a web browser to configure the PX2. See Login (on page 86).

Configuration via a connected computer:

1. Connect the PX2 to a computer. See Connecting the PX2 to a Computer(on page 25).
2. Use the connected computer to configure the PX2 via the command line or web interface.

- Command line interface: See Initial Network Configuration via CLI (on page 721).

- Web interface: Launch the web browser on the computer, and type the link-local IP address or pdu.local to access the PX2. See Login (on page 86).

Tip: To configure a number of PX2 devices quickly, see Bulk Configuration Methods (on page 27).

Connecting a Mobile Device to PX2

Raritan's PDView is a free app that turns your iOS or Android mobile device into a local display for PX2.

PDView is especially helpful when your PX2 is not connected to the network but you need to check the PX2 status, retrieve its information, or change its settings.

▶ Requirements for using PDView:

• PX2 is running any post-3.0.0 firmware version.
• If using an Android device, it must support USB "On-The-Go" (OTG).
• An appropriate USB cable is required. For information, refer to Step B below.

Step A: Download and install PDView

1. Visit either Apple App or Google Play Store.

- https://itunes.apple.com/app/raritan-pdview/id780382738

- https://play.google.com/store/apps/details?id=com.raritan.android.pdview

1. Install PDView.

Step B: Connect the mobile device to PX2

1. Get an appropriate USB cable for your mobile device.

2. iOS: Use the regular USB cable shipped with your iOS mobile device.
   ■ Android: Use an USB OTG adapter cable.

3. Connect the mobile device to the appropriate USB port on the PX2.

4. iOS: USB-A port.

5. Android: USB-B port

graph TD
    A["Smartphone"] --> B["Device"]
    C["iOS"] --> D["USB-A Device"]
    E["Android"] --> F["USB-B Device"]
    B -.-> G["User Controller"]
    F -.-> G

Step C: Launch PDView to access the PX2

1. Launch the PDView app from your mobile device. Below illustrate iPad's PDView screens.

a. The "Disconnected" message displays first when PDView has not detected the PX2 yet.

A diagram in PDView indicates the appropriate USB port your mobile device should connect according to your mobile operating system.

FEATURE USB-A T ETHERNET USB-B Disconnected Please connect your device to the USB-A port on your PDU.

Note: PDView also shows the 'Disconnected' status during the firmware upgrade. If so, wait until the firmware upgrade finishes.

b. The PDView shows the "Connected" message when it detects the connected PX2.

FEATURE USB-A T ETHERNET USB-B

Connected

Authenticating...

1. If the factory-default user credentials "admin/raritan" remain unchanged, PDView automatically logs in to the web interface of PX2. If they have been changed, the login screen displays instead and you must enter appropriate user credentials for login.

2. The web interface opens. Now you can view or modify the data of PX2.

- The web interface prompts you to change the password if this is the first time you log in.

Tip: You can store the updated "admin" or other user credentials in PDView so that automatic login always functions properly upon detection of the PX2. See Saving User Credentials for PDView's Automatic Login (on page 23).

Saving User Credentials for PDView's Automatic Login

When PDView detects PX2 for the "first" time, it automatically attempts to log in with the factory-default user credentials -- admin (user name) and raritan (password).

If you have modified the factory-default user credentials, PDView's automatic login fails and the login screen displays for you to manually enter user credentials.

To make automatic login work again, you can save the modified admin credentials or any custom user credentials in PDView. A maximum of 5 user credentials can be saved, and PDView will try these credentials one by one until the login succeeds.

The following procedure illustrates iPad only, but the procedure applies to any iOS or Android mobile devices.

To save user credentials in PDView:

1. Make sure your mobile device is NOT connected to the PX2 so that PDView does NOT perform the automatic login feature after it is launched.
2. Launch PDView on your mobile device.

1. Tap the top-right icon

(iOS) or Android).

Raritan. PDView Sensor Identifier FEATURE USB-A T ETHERNET USB-B Disconnected Please connect your device to the USB-A port on your PDU.

1. The user credentials setup page opens.

■ Per default, three administrator user credentials are pre-configured for three companies' power products:
Raritan

Chapter 3: Initial Installation and Configuration

Legrand
■ ServerTech (Server Technology)

Default Username/Password Credentials: Username 1: admin Password: •••••••• Raritan standard password Username 2: admin Password: ••••••••• Legrand standard password Username 3: admin Password: •••••••••••• ServerTech standard password Username 4: Password: Username 5: Password:

1. Modify existing user credentials or type new ones, and tap Save.

- The pre-configured admin credentials can be removed or overwritten to meet your needs.

Connecting the PX2 to a Computer

The PX2 can be connected to a computer for configuration via one of the following ports.

• Ethernet port
• USB-B port
  • RS-232 serial port (male DB9)

Zero U models:

USB-B Raritan RESET LINE / CB / UB UP BOTH DOWN > CURRENT VOLTAGE (VS) POWER (HRS) US LOAD (%) SENSOR FEATURE USB-B SENSOR ETHERNET USB-A CONSOLE / MODEM RS-232 ETHERNET

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

To use a web browser for configuration, make a network connection to the computer. The PX2 is automatically configured with the following link-local addressing in any network without DHCP available:

• https://169.254.x.x (where x is a number)
• https://pdu.local

See APIPA and Link-Local Addressing (on page 2).

Establish one of the following connections to a computer. Ethernet port of PX2 must be enabled for the described connection to work properly, which has been enabled per default.

▶ Direct network connection:

1. Connect one end of a standard network patch cable to the Ethernet port of the PX2.
2. Connect the other end to a computer's Ethernet port.
3. On the connected computer, launch a web browser to access the PX2, using either link-local addressing: pdu.localor 169.254.x.x. See Login (on page 86).

USB connection:

1. A USB-to-serial driver is required in Windows®. Install this driver before connecting the USB cable. See Installing the USB-to-Serial Driver (Optional) (on page 719).
2. Connect a USB cable between a computer's USB-A port and the USB-B port of PX2.
3. Perform Initial Network Configuration via CLI(on page 721).

Note: Not all serial-to-USB converters work properly with the PX2 so Raritan does not introduce the use of such converters.

Serial connection for RS-232 connector on PX2:

1. Connect one end of the null-modem DB9 cable to the male "DB9" RS-232 port labeled CONSOLE / MODEM on PX2.
2. Connect the other end to your computer's RS-232 port (COM).
3. Perform Initial Network Configuration via CLI(on page 721).

Bulk Configuration Methods

If you have to set up multiple PX2 devices, you can use one of the following configuration methods to save your time.

▶ A bulk configuration file downloaded from PX2:

• Requirement: All PX2 devices to configure are of the same model and firmware.
• Procedure: First finish configuring one PX2. Then download the bulk configuration file from it and copy this file to all of the other PX2 devices.
  See Bulk Configuration (on page 364).

A TFTP server:

• Requirement: DHCP is enabled in your network and a TFTP server is available.
• Procedure: Prepare special configuration files, which must include fwupdate.cfg, and copy them to the root directory of the TFTP server. Re-boot all PX2 devices after connecting them to the network.
  See Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 622).

▶ Curl command:

• Requirement: Two files are required -- one is a configuration file in TXT and the other is a devices list file in CSV. See config.txt (on page 614) and devices.csv (on page 616).
• Procedure: Upload both files to all of PX2 devices one by one, using the appropriate curl command.
  See Upload via Curl (on page 648).

SCP or PSCP command:

• Requirement: Two files are required -- one is a configuration file in TXT and the other is a devices list file in CSV.
• Procedure: Upload both files to all of PX2 devices one by one, using the appropriate SCP or PSCP command.

See Uploading or Downloading Raw Configuration Data (on page 578).

A USB flash drive:

• Requirement: A FAT32- or supperfloppy-formatted USB flash drive containing two special configuration files and one devices list file is required.
• Procedure: Plug this USB drive into the PX2. When a happy smiley is shown on the front panel display, press and hold one of the control buttons on the front panel until the display turns blank.

See Configuration or Firmware Upgrade with a USB Drive (on page 607).

Cascading Multiple PX2 Devices for Sharing Ethernet Connectivity

Important: To upgrade an existing Raritan USB-cascading chain from any pre-3.3.10 firmware version to version 3.3.10 or later, follow the Upgrade Sequence in an Existing Cascading Chain (on page 362).

You can have multiple PX2 devices share one Ethernet connection by cascading them via USB.

The first one in the cascading chain is the master device and all the other are slave devices. Only the master device is physically connected to the LAN -- wired or wireless.

Each device in the chain is accessible over the network, with the Bridging or Port-Forwarding cascading mode activated on the master device. See Setting the Cascading Mode (on page 218).

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

Basic cascading restrictions:

• All devices in the chain must run "compatible" firmware versions.
• Firmware version 3.3.10 or later is NOT compatible with pre-3.3.10 firmware versions in terms of the cascading feature so all Raritan devices in the cascading chain must run version 3.3.10 or later.
• The cascading mode of all devices in the chain must be the same.
• In the Bridging mode, the master device can have "only one" connection to the network.

Note: The Port Forwarding mode does NOT have this restriction. In this mode, you can enable one wired and one wireless network connections.

• Do NOT connect slave devices to the LAN or WLAN.
• (WIFI only) You must use Raritan's USB WIFI wireless LAN adapter instead of other WIFI adapters for wireless network connection.

Troubleshooting:

When a networking issue occurs, check the cascading connection and/or software settings of all devices in the chain. See Cascading Troubleshooting (on page 716).

▶ Online Cascading Guide:

For detailed information on the cascading configuration and restrictions, refer to the Cascading Guide, which is available from Raritan website's Support page (http://www.raritan.com/support).

Cascading Guidelines for Port Forwarding

The following guidelines must be obeyed for establishing a cascading chain in the Port Forwarding mode.

• Each cascaded device, except for the master device, must have only one upstream device.
• Each cascaded device, except for the last slave device, must have only one downstream device.
  • Use only one cable to cascade two devices.

Cascading All Devices via USB

You must set the cascading mode before establishing the chain. See Setting the Cascading Mode (on page 218).

Any certified USB 2.0 cable up to 5 meters (16 feet) long can be used. Both cascading modes support a maximum of 16 devices in a chain. The following diagram illustrates PX2 devices cascaded via USB.

graph TD
    A["LAN"] --> B["1 USB-A"]
    B --> C["2 USB-B"]
    C --> D["3 USB-A"]
    D --> E["4 USB-B"]
    style A fill:#f9f,stroke:#333
    style B fill:#ccf,stroke:#333
    style C fill:#cfc,stroke:#333
    style D fill:#fcc,stroke:#333
    style E fill:#cff,stroke:#333

Number Device role
1	Master device
2	Slave 1
3	Slave 2

Number Device role

Slave 3

To cascade PX2 devices via USB:

1. Make sure all Raritan devices are running firmware version 3.3.10 or later. Cabinet Inspector
2. Choose the appropriate one as the master device.

- When the Port Forwarding mode over "wireless LAN" is intended, the master device must be a Raritan product with two USB-A ports, such as PX3, EMX2-888, PX3TS or BCM2.

1. Log in to all devices one by one and select the same cascading mode.

2. Bridging mode:
   Set the cascading mode of all devices to Bridging.
   ■ Port Forwarding mode:

Set the cascading mode of all devices to Port Forwarding. Make sure the cascading role and downstream interface are also set correctly.

See Setting the Cascading Mode (on page 218).

1. Connect the master device to the LAN, using a method below.

2. Bridging mode:
   Use a standard network patch cable (CAT5e or higher).

■ Port Forwarding mode:

Use a standard network patch cable and/or a Raritan USB WIFI wireless LAN adapter. For information on the Raritan USB WIFI adapter, see USB Wireless LAN Adapters (on page 18).

1. Connect the USB-A port of the master device to the USB-B port of an additional PX2 via a USB cable. This additional device is Slave 1.

2. Connect Slave 1's USB-A port to the USB-B port of an additional PX2 via another USB cable. The second additional device is Slave 2.

3. Repeat the same step to connect more slave devices. You can cascade up to 15 slave devices.

4. (Optional) Configure or change the network settings of the master and/or slave devices as needed. See Configuring Network Settings (on page 205).

- Bridging mode: Each cascaded device has its own network settings.

For example, you can have some devices use DHCP-assigned IP addresses and the others use static IP addresses.

- Port Forwarding mode: Only the master device's network settings should be configured.

▶ A tip for USB cascading:

The "USB-cascading" chain can be a combination of diverse Raritan products that support the USB-cascading feature, including PX2, PX3, PXC, transfer switch, BCM and EMX.

Chapter 4 Connecting External Equipment (Optional)

More features are available if you connect Raritan's or third-party external equipment to your PX2.

In This Chapter

Connecting Raritan Environmental Sensor Packages ....33

Connecting Asset Management Strips....53

Connecting a Logitech Webcam....65

Connecting a GSM Modem 66

Connecting an Analog Modem 66

Connecting an External Beeper 67

Connecting a Schroff LHX/SHX Heat Exchanger 67

Connecting Raritan Environmental Sensor Packages

PX2 supports all types of Raritan environmental sensor packages, including DPX, DPX2, DPX3, DX and DX2 sensor packages. DPX series is the first generation while DX2 series is the latest generation.

For detailed information on each sensor package, refer to the Environmental Sensors and Actuators Guide (or Online Help) on Raritan website's Support page (http://www.raritan.com/support/).

An environmental sensor package may comprise sensors only or a combination of sensors and actuators.

PX2 can manage a maximum of 32 sensors and/or actuators. The supported maximum cabling distance is 98 feet (30 meters), except for DPX sensor packages.

For information on connecting different types of sensor packages, see:

• DX2 Sensor Packages (on page 34)
• DX Sensor Packages (on page 35)
• DPX3 Sensor Packages (on page 37)
• DPX2 Sensor Packages (on page 38)
• DPX Sensor Packages (on page 41)

Identifying the Sensor Port

Warning: If you purchase Raritan's environmental sensor packages, make sure you connect them to the correct port on the PX2, or damages may be caused to PX2 and/or connected sensor packages.

How to identify the SENSOR port:
• The correct port is labeled SENSOR.

DX2 Sensor Packages

You can cascade up to 12 DX2 sensor packages.

When cascading DX2, remember that the PX2 only supports a maximum of 32 sensors and/or actuators.

If there are more than 32 sensors and/or actuators connected, every sensor and/or actuator after the 32nd one is NOT managed by the PX2.

Tip: To manage the last several sensors/actuators after 32nd function, you can release some "managed" sensors or actuators, and then manually bring the last several sensors/actuators into management. See Peripherals (on page 156).

RJ-45 RJ-45

Numbers Components

1

RJ-45 ports, each of which is located on either end of a DX2 sensor package.

2

LED, which indicates the sensor package's status

Connect DX2 to the PX2:

1. Connect an RJ-12 to RJ-45 adapter cable to the DX.

- Connect the adapter's RJ-45 connector to either RJ-45 port of the DX.

Tip: You can request the RJ-12 to RJ-45 adapter cable (Part number: RJ12M-RJ45M) from Raritan if needed.

1. If you want to cascade DX2 packages, get an additional standard network patch cable (CAT5e or higher) and then:

a. Plug one end of the cable into the remaining RJ-45 port on the prior DX2 package.

b. Plug the other end into either RJ-45 port on an additional DX2 package.

Repeat the same steps to cascade more DX2 packages.

RJ-12

1. Connect the first DX sensor package to the PX2.

- Plug the adapter cable's RJ-12 connector into the RJ-12 SENSOR port of the PX2.

1. If needed, connect a DPX2 sensor package to the end of the DX2 chain. See Connecting a DPX2 Sensor Package to DX2, DX or DPX3 (on page 40).

Note: If your PX2 has "two" RJ-12 SENSOR ports, see Guidelines for PX2 with Two Sensor Ports (on page 52) for sensor connection restrictions.

DX Sensor Packages

Most DX sensor packages contain terminals for connecting detectors or actuators. For information on connecting actuators or detectors to DX terminals, refer to the Environmental Sensors and Actuators Guide (or Online Help) on Raritan website's Support page (http://www.raritan.com/support/).

You can cascade up to 12 DX sensor packages.

When cascading DX, remember that the PX2 only supports a maximum of 32 sensors and/or actuators.

If there are more than 32 sensors and/or actuators connected, every sensor and/or actuator after the 32nd one is NOT managed by the PX2.

For example, if you cascade 12 DX packages, and each package contains 3 functions (a function is a sensor or actuator), the PX2 does NOT manage the last 4 functions because the total 36 (12*3=36) exceeds 32 by 4.

Tip: To manage the last several sensors/actuators after 32nd function, you can release some "managed" sensors or actuators, and then manually bring the last several sensors/actuators into management. See Peripherals (on page 156).

RJ-45 ① ② ③

Numbers Components

1	RJ-45 ports, each of which is located on either end of a DX sensor package.
2	RJ-12 port, which is reserved for future use and now blocked.
3	Removable rackmount brackets.

Connect DX to the PX2:

1. Connect an RJ-12 to RJ-45 adapter cable to the DX.

- Connect the adapter's RJ-45 connector to either RJ-45 port of the DX.

Tip: You can request the RJ-12 to RJ-45 adapter cable (Part number: RJ12M-RJ45M) from Raritan if needed.

1. If you want to cascade DX packages, get an additional standard network patch cable (CAT5e or higher) and then:

a. Plug one end of the cable into the remaining RJ-45 port on the prior DX package.
b. Plug the other end into either RJ-45 port on an additional DX package.

Repeat the same steps to cascade more DX packages.

Diagram of four connected electrical connectors with cable, showing internal wiring (no text or symbols)

RJ-12

1. Connect the first DX sensor package to the PX2.

- Plug the adapter cable's RJ-12 connector into the RJ-12 SENSOR port of the PX2.

1. If needed, connect a DPX2 sensor package to the end of the DX chain. See Connecting a DPX2 Sensor Package to DX2, DX or DPX3(on page 40).

Note: If your PX2 has "two" RJ-12 SENSOR ports, see Guidelines for PX2 with Two Sensor Ports (on page 52) for sensor connection restrictions.

DPX3 Sensor Packages

A DPX3 sensor package features the following:

• Its connection interface is RJ-45.
• You can cascade a maximum of 12 DPX3 sensor packages.

RJ-45 RJ-45

Numbers	Components
1	RJ-45 ports, each of which is located on either end of a DPX3 sensor package.
2	LED for indicating the sensor status.

To connect DPX3 sensor packages to the PX2:

1. Connect an RJ-12 to RJ-45 adapter cable to the DPX3 sensor package.

- Connect the adapter's RJ-45 connector to either RJ-45 port of the DPX3 sensor package.

Tip: You can request the RJ-12 to RJ-45 adapter cable (part number: RJ12M-RJ45M) from Raritan if needed.

1. If you want to cascade DPX3 sensor packages, get an additional standard network patch cable (CAT5e or higher) and then:

a. Plug one end of the cable into the remaining RJ-45 port on the prior DPX3.
b. Plug the other end into either RJ-45 port on an additional DPX3.

Repeat the same steps to cascade more DPX3 sensor packages.

RJ-12

1. Connect the first DPX3 sensor package to the PX2.

- Plug the adapter cable's RJ-12 connector into the RJ-12 SENSOR port on the PX2.

Note: If your PX2 has "two" RJ-12 SENSOR ports, see Guidelines for PX2 with Two Sensor Ports (on page 52) for sensor connection restrictions.

DPX2 Sensor Packages

A DPX2 sensor cable is shipped with a DPX2 sensor package. This cable is made up of one RJ-12 connector and one to three head connectors. You have to connect DPX2 sensor packages to the sensor cable.

For more information on DPX2 sensor packages, access the Environmental Sensors and Actuators Guide (or Online Help) on Raritan website's Support page (http://www.raritan.com/support/).

① ② RJ-12

Item
1	DPX2 sensor package
2	DPX2 sensor cable with one RJ-12 connector and three head connectors

The following procedure illustrates a DPX2 sensor cable with three head connectors. Your sensor cable may have fewer head connectors.

Warning: If there are free head connectors between a DPX2 sensor cable's RJ-12 connector and the final attached DPX2 sensor package, the sensor packages following the free head connector(s) on the same cable do NOT work properly. Therefore, always occupy all head connectors prior to the final sensor package with a DPX2 sensor package.

To connect DPX2 to the PX2:

1. Connect a DPX2 sensor package to the first head connector of the DPX2 sensor cable.

Diagram of a USB cable with connector, showing a connector and two cables (no text or symbols)

1. Connect remaining DPX2 sensor packages to the second and then the third head connector.

RJ-12 1 2 3

Tip: If the number of sensors you are connecting is less than the number of head connectors on your sensor cable, connect them to the first one or first two head connectors to ensure that there are NO free head connectors prior to the final DPX2 sensor package attached.

1. Plug the RJ-12 connector of the DPX2 sensor cable into the RJ-12 SENSOR port on the PX2.

OR you can directly connect the DPX2 sensor package to a DX sensor chain without using any RJ-12 to RJ-45 adapter. See Connecting a DPX2 Sensor Package to DX2, DX or DPX3 (on page 40).

Note: If your PX2 has "two" RJ-12 SENSOR ports, see Guidelines for PX2 with Two Sensor Ports (on page 52) for sensor connection restrictions.

Connecting a DPX2 Sensor Package to DX2, DX or DPX3

You can connect one DPX2 sensor package to the "end" of a DX2, DX or DPX3 sensor chain. It is strongly recommended to use an RJ-12 to RJ-45 adapter for connecting the DPX2 to the final DX2, DX or DPX3 in the chain.

The maximum number of DX2, DX or DPX3 sensor packages in the chain must be less than 12 when a DPX2 sensor package is involved.

The following diagrams illustrate DX sensor chain only, but the same principles also apply to DX2 and DPX3 sensor chains if connecting DPX2 to the end of DX2 or DPX3 sensor chains.

When connecting a DPX2 sensor package containing "three" DPX2 sensors:

A maximum of nine DX sensor packages can be cascaded because 12-3=9.

graph LR
    DX["DX"] -->|9| DPX2["DPX2"]
    DPX2 -->|USB ports| DPX2
    DPX2 -->|USB ports| DPX2
    DPX2 -->|USB ports| DPX2
    DPX2 -->|USB ports| DPX2

When connecting a DPX2 sensor package containing "two" DPX2 sensors:

A maximum of ten DX sensor packages can be cascaded because 12-2=10.

DX 10 DPX2

When connecting a DPX2 sensor package containing "one" DPX2 sensor:

A maximum of eleven DX sensor packages can be cascaded because 12-1=11.

graph LR
    DX["DX"] -->|11| DPX2["DPX2"]
    DPX2 -->|Dashed Line| DX
    DPX2 -->|Solid Line| DX
    DPX2 -->|Solid Line| DPX2
    DPX2 -->|Solid Line| DPX2
    DPX2 -->|Solid Line| DPX2
    DPX2 -->|Solid Line| DPX2

DPX Sensor Packages

Most DPX sensor packages come with a factory-installed sensor cable, whose sensor connector is RJ-12.

Simple line drawing of a RJ-12 device with a coiled cable and connector (no text or symbols)

For the cabling length restrictions, see Supported Maximum DPX Sensor Distances (on page 45).

Warning: For proper operation, wait for 15-30 seconds between each connection operation or each disconnection operation of environmental sensor packages.

To connect a DPX sensor package with a factory-installed sensor cable:
- Plug the sensor cable's RJ-12 connector into the RJ-12 SENSOR port on the PX2.
To connect a DPX differential air pressure sensor:
1. Plug one end of a Raritan-provided phone cable into the IN port of a differential air pressure sensor.
2. Plug the other end of this phone cable into the RJ-12 SENSOR port on the PX2.
3. If intended, connect one DPX sensor package to the OUT port of the differential air pressure sensor. It can be any DPX sensor package, such as a DPX-T3H1.

IN OUT ① ② ③

1	The PX2
2	Raritan differential air pressure sensors
3	One DPX sensor package (optional)

Using an Optional DPX-ENVHUB4 Sensor Hub

Optionally, you can connect a Raritan DPX-ENVHUB4 sensor hub to the PX2. This allows you to connect up to four DPX sensor packages to the PX2 via the hub.

This sensor hub supports DPX sensor packages only. Do NOT connect DPX2, DPX3, DX or DX2 sensor packages to it.

DPX-ENVHUB4 sensor hubs CANNOT be cascaded. You can connect only one hub to each SENSOR port on the PX2.

Tip: The Raritan sensor hub that supports ALL types of Raritan environmental sensor packages is DPX3-ENVHUB4. See Using an Optional DPX3-ENVHUB4 Sensor Hub (on page 46).

To connect DPX sensor packages via the DPX-ENVHUB4 hub:

1. Connect the DPX-ENVHUB4 sensor hub to the PX2.

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 of the cable into the RJ-12 SENSOR port of the PX2.

1. Connect DPX sensor packages to any of the four OUT ports on the hub.

This diagram illustrates a configuration with a sensor hub connected.

Diagram showing a rack-mounted device connected to a network switch with four labeled components and dashed lines indicating connections.

The PX2 device

2	Raritan-provided phone cable
3	DPX-ENVHUB4 sensor hub
4	DPX sensor packages

Using an Optional DPX-ENVHUB2 Cable

A Raritan DPX-ENVHUB2 cable doubles the number of connected environmental sensors per SENSOR port.

This cable supports DPX sensor packages only. Do NOT connect DPX2, DPX3, DX or DX2 sensor packages to it.

To connect DPX sensor packages via the DPX-ENVHUB2 cable:

1. Plug the connector of this cable directly into the PX2 device's RJ-12 SENSOR port.

Diagram showing a connector with a cable and a plug, connected to a network icon (no text or symbols)

RJ-12 SENSOR

1. The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports.

Diagram of a USB port with two Ethernet ports highlighted in a speech bubble (no text or symbols present)

1. Repeat the above steps if there are additional SENSOR ports on your PX2.

Supported Maximum DPX Sensor Distances

When connecting the following DPX sensor packages to the PX2, you must follow two restrictions.

• DPX-CC2-TR
• DPX-T1
• DPX-T3H1
• DPX-AF1
• DPX-T1DP1

▶ Sensor connection restrictions:

• Connect a DPX sensor package to the PX2 using the sensor cable pre-installed (or provided) by Raritan. You MUST NOT extend or modify the sensor cable's length by using any tool other than the Raritan's sensor hubs.
• If using a DPX-ENVHUB4 sensor hub, the cabling distance between the PX2 and the sensor hub is up to 33' (10 m).

▶ Maximum distance illustration:

The following illustrates the maximum distance when connecting DPX sensor packages with a maximum 16' (5 m) sensor cable to the PX2 via a sensor hub.

- The sum of a DPX-T3H1 sensor cable's length is 16 feet (5 meters).

3 m 1 m 1 m 3 m + 1 m + 1 m = 5 m

- The total cabling length between the PX2 and one DPX-T3H1 is 49' (15 m) as illustrated below.

Note that the length 16 feet (5 meters) is the length of each DPX-T3H1 sensor cable, which is defined in the above diagram.

PX2

→ 33' (10 m) cable

→ 1 sensor hub

→ 16' (5 m) cable

→ Up to 4 DPX-T3H1 sensor packages

Using an Optional DPX3-ENVHUB4 Sensor Hub

A Raritan DPX3-ENVHUB4 sensor hub is physically and functionally similar to the DPX-ENVHUB4 sensor hub, which increases the number of sensor ports for the PX2, except for the following differences:

• All ports on the DPX3-ENVHUB4 sensor hub are RJ-45 instead of RJ-12 as the DPX-ENVHUB4 sensor hub.
• The DPX3-ENVHUB4 sensor hub supports all Raritan environmental sensor packages, including DPX, DPX2, DPX3, DX and DX2 sensor packages.

To connect diverse types of sensor packages to this sensor hub, you must follow the combinations shown in the section titled Mixing Diverse Sensor Types (on page 47).

To connect DPX3 sensor packages via the DPX3-ENVHUB4 hub:

1. Connect the DPX3-ENVHUB4 sensor hub to the PX2 using an RJ-12 to RJ-45 adapter cable.

a. Plug the RJ-45 connector of this cable into the IN port (Port 1) of the hub.
b. Plug the RJ-12 connector of this cable into the RJ-12 SENSOR port of the PX2.

1. Connect the Raritan sensor packages to any of the four OUT ports on the hub.

- An RJ-12 to RJ-45 adapter is required for connecting a DPX or DPX2 sensor package to the hub.

This diagram illustrates a configuration with a sensor hub connected.

Diagram showing a cable connector with four labeled components and wiring connections, including a red vertical line and 'IN' label.

1	The PX2
2	RJ-12 to RJ-45 adapter cable
3	DPX3-ENVHUB4 sensor hub
4	Any Raritan sensor packages

Mixing Diverse Sensor Types

You can mix diverse sensor packages on one PX2 according to the following sensor combination principles. In some scenarios, the DPX3-ENVHUB4 sensor hub is required.

When mixing different sensor types, remember that the PX2 only supports a maximum of 32 sensors/actuators.

PX2 does NOT support any other sensor-mixing combinations than those described in this section.

In most illustrations below, any DX or DPX3 sensor package can be replaced with a DX2 sensor package.

For those illustrations where DX, DPX3 and DX2 are interchangeable, they are all marked with the following oval image.

Important: Unlike DX or DPX3 series, DX2 CANNOT be connected with DPX sensor package(s).

1 DX + 1 DPX:

• An RJ-12 to RJ-45 adapter cable is required for connecting the DX sensor package to the PX2.
• It is strongly recommended to use an RJ-12 to RJ-45 adapter to connect the DPX sensor package to the DX sensor package.
• You can replace the DX in the following diagram with one DPX3 package, but NOT with DX2.

graph TD
    A["PC2"] --> B["RJ-12"]
    B --> C["DX"]
    C --> D["DPX"]

Diverse combinations via the DPX3-ENVHUB4 sensor hub:

- You must use the DPX3-ENVHUB4 sensor hub instead of the old DPX-ENVHUB4 sensor hub. Each port on the hub supports any of the following:

■ One individual DX2 sensor package
■ A chain of DX2 sensor packages
■ One individual DX sensor package
- A chain of DX sensor packages
■ One individual DPX3 sensor package
■ A chain of DPX3 sensor packages
■ One individual DPX2 sensor package
■ One individual DPX sensor package

• An RJ-12 to RJ-45 adapter is recommended to connect a DPX or DPX2 sensor package to DPX3-ENVHUB4.
• In the following diagrams, the sensor package in "green" can be replaced by a DPX2 sensor package. The sensor package in "blue" can be one DPX2, DPX3, DX or DX2 sensor package.
• An RJ-12 to RJ-45 adapter cable MUST be used for connecting the DPX3-ENVHUB4 to the PX2.

This section only illustrations the following three combinations, but actually there are tens of different combinations by using the DPX3-ENVHUB4 sensor hub.

graph TD
    A["Port 1"] --> B["Port 2"]
    C["Port 3"] --> D["Port 4"]
    E["Port 5"] --> F["Port 6"]
    G["Port 7"] --> H["Port 8"]
    I["Port 9"] --> J["Port 10"]
    K["RJ-12"] --> L["IN"]
    M["DX"] --> N["DX / DPX2"]
    O["DX / DPX2 / DPX3"] --> P["DPX"]
    Q["DPX3"] --> R["DPX3 / DPX2"]
    S["DPX3"] --> T["DPX3 -ENVHUB4"]

Chapter 4: Connecting External Equipment (Optional)

graph TD
    A["Port 1"] --> B["Port 2"]
    B --> C["RJ-12"]
    C --> D["Port 3"]
    D --> E["IN"]
    E --> F["Port 4"]
    F --> G["DPX3-ENVHUB4"]
    G --> H["DX"]
    G --> I["DX"]
    G --> J["DPX"]
    H --> K["DX"]
    I --> L["DX"]
    J --> M["DPX"]
    K --> N["DX / DPX2"]
    L --> O["DX / DPX2"]
    M --> P["DPX"]

Chapter 4: Connecting External Equipment (Optional)

graph TD
    A["Port 1"] --> B["Port 2"]
    C["Port 3"] --> D["Port 4"]
    E["Port 5"] --> F["Port 6"]
    G["Port 7"] --> H["Port 8"]
    I["Port 9"] --> J["Port 10"]
    K["Port 11"] --> L["Port 12"]
    M["Port 13"] --> N["Port 14"]
    O["Port 15"] --> P["Port 16"]
    Q["RJ-12"] --> R["IN"]
    S["DPX3"] --> T["DPX2 / DPX3 / DX / DX2"]
    U["DPX3"] --> V["DPX2 / DPX3 / DX / DX2"]
    W["DPX"] --> X["DPX3 / DPX2"]
    Y["DPX3-ENVHUB4"] --> Z["IN"]

Mix DX2, DX and DPX3 in a sensor chain:

Any DX or DX2 sensor package in a chain can be replaced by a DPX3 sensor package, or vice versa. The total number of sensor packages in this chain cannot exceed 12.

For example, the following diagram shows a sensor chain comprising DX2, DX and DPX3 sensor packages.

graph LR
    A["DPX3"] --> B["DX"]
    B --> C["DX"]
    C --> D["DX"]
    D --> E["DPX3"]
    E --> F["DPX3"]
    F --> G["DX2"]
    G --> H["DX2"]
    H --> I["DX"]
    I --> J["DPX3"]
    J --> K["DX2"]
    K --> L["DX2"]

You can add a DPX2 sensor package to the end of such a sensor-mixing chain if needed. See Connecting a DPX2 Sensor Package to DX2, DX or DPX3 (on page 40).

Guidelines for PX2 with Two Sensor Ports

You CANNOT simultaneously connect Raritan environmental sensor packages to both sensor ports of the PX2 models with "two" sensor ports, unless only DPX sensor packages are connected.

DPX sensor packages:

- You can connect the DPX sensor package(s) to either or both sensor ports.

graph TD
    A["DPX"] --> B["CPX"]
    B --> C["C/CRCU T5"]
    B --> D["C/CRCU T3"]
    B --> E["C/CRCU T1"]
    B --> F["C/CRCU T6"]
    B --> G["C/CRCU T4"]
    B --> H["C/CRCU T2"]
    style A fill:#f9f,stroke:#333
    style B fill:#ccf,stroke:#333
    style C fill:#cfc,stroke:#333
    style D fill:#cfc,stroke:#333
    style E fill:#cfc,stroke:#333
    style F fill:#cfc,stroke:#333
    style G fill:#cfc,stroke:#333
    style H fill:#cfc,stroke:#333

DX2, DX, DPX3 or DPX2 sensor packages:

• You can connect the DX2, DX, DPX3, or DPX2 sensor package(s) to either sensor port, but you MUST NOT connect them to both sensor ports simultaneously.
• An RJ-12 to RJ-45 adapter cable is required for connecting the DX2, DX or DPX3 sensor package to the PX2.

In the following diagram, the red box can be:

• A DX2, DX, DPX3, or DPX2 sensor package
  ■ A DX2, DX or DPX3 sensor chain

PX2 DX2 / DX / DPX2 / DPX3

▶ Sensor-mixing connections:

• The PX2 with "two" sensor ports supports the sensor-mixing combinations listed in the section titled Mixing Diverse Sensor Types (on page 47).
• You can connect the sensor-mixing combination to either sensor port, but you MUST NOT connect them to both sensor ports simultaneously.

Connecting Asset Management Strips

You can remotely track the locations of up to 64 IT devices in the rack by connecting asset management strips (asset strips) to the PX2 after IT devices are tagged electronically.

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

• Raritan asset strips: An asset strip transmits the asset management tag's ID and positioning information to the PX2.
• Raritan asset tags: An asset management tag (asset tag) is adhered to an IT device. The asset tag uses an electronic ID to identify and locate the IT device.

Combining Regular Asset Strips

Each tag port on the regular asset strips corresponds to a rack unit and can be used to locate IT devices in a specific rack (or cabinet).

For each rack, you can attach asset strips up to 64U long, consisting of one MASTER and multiple SLAVE asset strips.

The difference between the master and slave asset strips is that the master asset strip has an RJ-45 connector while the slave does not.

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

Three technical diagrams of a vertical metal bracket with mounting holes, labeled 1, 2, and 3 (no text or symbols on the brackets themselves)

1	8U MASTER asset strip with 8 tag ports
2	8U SLAVE asset strip with 8 tag ports
3	5U "ending" SLAVE asset strip with 5 tag ports

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

To assemble asset strips:

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

2. Plug the white male DIN connector of the slave strip into the white female DIN connector of the master strip.
   ■ Make sure that the U-shaped sheet metal adjacent to the male DIN connector is inserted into the rear slot of the master strip. Screw up the U-shaped sheet metal to reinforce the connection.

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

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

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

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

4. Connect the "ending" asset strip as the final one in the assembly.

5. Vertically attach the asset strip assembly to the rack, next to the IT equipment, making each tag port horizontally align with a rack unit.

6. The asset strips are automatically attracted to the rack because of magnetic stripes on the back.

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

Introduction to Asset Tags

You need both asset strips and asset tags for tracking IT devices.

Asset tags provide an ID number for each IT device. The asset tags are adhered to an IT device at one end and plugged in to an asset strip at the other.

The asset strip is connected to the PX2, and the asset tag transmits the ID and positioning information to the asset strip.

The following diagram illustrates an asset tag. Note that there are two types of asset tags: non-programmable and programmable tags. The only difference is that programmable asset tags allow you to customize each tag's ID or barcode number while non-programmable ones have factory default ID or barcode numbers, which you cannot change.

A B A C

A	Barcode (ID number), which is available on either end of the "non-programmable" asset tag
B	Tag connector
C	Adhesive area with the tape

Note: The barcode of each "non-programmable" asset tag is unique and is displayed in the PX2 device's web interface for identification.

Connecting Regular Asset Strips to PX2

The cabling distance between an asset strip assembly and the PX2 can be up to 10 meters.

The FEATURE port of PX2 supports 5 volts of power only, which is insufficient for connecting the latest generation (G3) of asset strips. Therefore, the use of a Raritan X cable is required for PX2 to connect current asset strips, or PX2 cannot detect them.

To connect a regular asset strip assembly to PX2:

1. Affix the adhesive end of an asset tag to each IT device through the tag's tape.

2. Plug the connector of each asset tag into the corresponding tag port on the asset strip.

Note: If an IT device occupies more than one rack unit in the rack, it is suggested to plug the asset tag into the lowest tag port. For example, if a device occupies the 5th and 6th rack units, plug the asset tag into the tag port matches the 5th rack unit.

1. Connect the MASTER asset strip's RJ-45 connector to the male RJ-45 connector at the longer end of the Raritan X cable.

2. Connect the X cable to the PX2.

- Plug the male RJ-12 phone connector at the shorter end of the X cable into the RJ-12 SENSOR port on the PX2 device.

- Plug the male RJ-45 connector at the shorter end of the X cable into the FEATURE port on the PX2 device.

Chapter 4: Connecting External Equipment (Optional)

Tip: To connect Raritan's environmental sensor packages to PX2, connect them to the female RJ-12 connector of the X cable. For details, see Using an X Cable (on page 63).

The PX2 device supplies power to the connected asset strip assembly. All LEDs on the asset strip assembly may cycle through different colors during the power-on process if the asset strip's firmware is being upgraded by the PX2. 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.

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 strip but requires a tag connector cable for connecting it to a tag port on the regular or composite asset strip. A blade extension strip contains 4 to 16 tag ports.

The following diagrams illustrate a tag connector cable and a blade extension strip with 16 tag ports.

Tag connector cable

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 PX2 device's web interface for identifying each blade extension strip where it is connected.

Blade extension strip with 16 tag ports

D F E F

D	Mylar section with the adhesive tape
E	Tag ports
F	Cable socket(s) for connecting the tag connector cable

Note: Each tag port on the blade extension strip is labeled a number, which is displayed as the slot number in the PX2 device'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.

Pure diagram of a connector with pinout and arrow, no text or symbols present

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 showing two views of a storage unit with a red arrow indicating rotation or assembly (no text or symbols present)

1. Connect one end of an asset tag to a blade server and 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 a tag port on the blade extension strip.

Diagram showing a door opening and a close-up of a cabinet with red arrows indicating movement or force (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 regular or composite asset strip on the rack.

Diagram of a mechanical device with curved internal components and a red arrow indicating direction (no text or symbols)

1. Repeat the above steps to connect additional blade extension strips. Up to 128 asset tags on blade extension strips are supported per FEATURE port.

Note: If you need to temporarily disconnect the blade extension strip from the asset strip, wait at least 1 second before re-connecting it back, or the PX2 device may not detect it.

Connecting Composite Asset Strips (AMS-Mx-Z)

A composite asset strip is named AMS-Mx-Z, where x is a number, such as AMS-M2-Z or AMS-M3-Z. It is a type of asset strip that functions the same as regular MASTER asset strips except for the following differences:

• It has two RJ-45 connectors.
• Multiple composite asset strips can be daisy chained.
  • It contains less tag ports than regular asset strips.

For example, AMS-M2-Z contains two tag ports, and AMS-M3-Z contains three tag ports only.

The composite asset strip is especially useful for tracking large devices such as SAN boxes in the cabinet.

The following diagram illustrates AMS-M3-Z.

Diagram showing two connected electrical components labeled A and B, with connection points indicated.

A	Two RJ-45 connectors
B	Tag ports

Important: DO NOT hot swap or hot plug any AMS-Mx-Z in a composite asset strip chain after connecting the chain to the PX2 device. Doing so may cause the device's FEATURE port to malfunction.

To connect composite asset strips to the PX2 device:

If there are only 2 or 3 IT devices to track, you can connect only one AMS-M2-Z or AMS-M3-Z to the PX2 device. In this case, go to step 2. If there are more than 2 or 3 IT devices, you need to daisy chain multiple composite asset strips and start from step 1.

1. (Optional) Daisy chain multiple composite asset strips.

a. Get a standard network patch cable that is within 2 meters.
b. Connect one end of the network cable to the RJ-45 connector labeled "Output" on the first composite asset strip.
c. Connect the other end of the cable to the RJ-45 connector labeled "Input" on the secondary composite asset strip.
d. Repeat the same steps to connect more composite asset strips. See Daisy-Chain Limitations of Composite Asset Strips (on page 62) for the maximum number of composite asset strips supported per chain.

Note: Different types of composite asset strips can be mixed in a chain as of release 3.3.0.

1. Connect the composite asset strip(s) to the PX2 device via a standard network patch cable (CAT5e or higher).

a. Connect one end of the cable to the RJ-45 port labeled "Input" on the composite asset strip.
- For a composite asset strip chain, connect the cable to the "Input" port of the first asset strip.
b. Connect the other end of the cable to the FEATURE port on the PX2 device.

1. Affix an asset tag to the IT device. Then connect this asset tag to the composite asset strip by plugging the tag connector into the tag port on the composite asset strip. For details, see Connecting Regular Asset Strips to PX2 (on page 56).
2. (Optional) For a chain, it is highly recommended using the cable ties to help hold the weight of all connecting cables.

Diagram of three connected mechanical components with blue cables, no text or symbols present

1. Repeat Step 3 to connect IT devices to the other composite asset strips in the chain.

Daisy-Chain Limitations of Composite Asset Strips

There are some limitations when daisy chaining composite asset strips "AMS-Mx-Z," where x is a number.

• The maximum cable length between composite asset strips is 2 meters, but the total cable length cannot exceed 10 meters.
• The maximum number of composite asset strips that can be daisy chained depends on the Raritan product you purchased.

Raritan devices Maximum strips per chain

EMX2-111,PX2 PDUs,BCM1 (NOT BCM2 series)	Up to 4 composite asset strips are supported.
EMX2-888,PX3 PDUs,PX3TS transfer switchesPMC (BCM2 series)	Up to 6 composite asset strips are supported.

Tip: To increase the maximum number of composite asset strips attached to a Raritan PX2 PDU, EMX2-111 or BCM1, use Raritan's X cable to enhance the power supply to the asset strip chain. See Using an X Cable (on page 63).

Using an X Cable

Raritan's PX2 products support a maximum of four composite asset strips in a chain. For details, see Daisy-Chain Limitations of Composite Asset Strips (on page 62).

If you need to exceed the daisy-chain limitation, use Raritan's X cable to connect composite asset strips. This allows you to expand the maximum number of composite asset strips from four units per chain to six units per chain.

An X cable is a combination of two male RJ-45 connectors, one Raritan-defined male phone connector, and one female RJ-12 sensor port.

The X cable supplies 12V voltage from the SENSOR port of the PX2 to the connected composite asset strips.

Note: An X cable does not help enhance the power supply to asset strips connected to Raritan's PX3 or PX3TS devices, so do not use this cable with these models.

To connect composite asset strips via an X cable:

1. Plug the male RJ-45 connector at the shorter end of the X cable into the FEATURE port on the PX2 device.

2. Plug the male RJ-12 phone connector at the shorter end of the X cable into the RJ-12 SENSOR port on the PX2 device. This step is required for enhancing the power supply to asset strips.

1. Plug the male RJ-45 connector at the longer end of the X cable into the RJ-45 port labeled "Input" on the composite asset strips.

- A maximum of 5 additional composite asset strips can be connected to the first composite asset strip being attached to the X cable. See Connecting Composite Asset Strips (AMS-Mx-Z) (on page 60) for step-by-step instructions.

1. Con nect any Raritan environmental sensor package or sensor hub to the female RJ-12 sensor port of the X cable if environmental sensor packages are needed. Note that a DX or DPX3 sensor requires an RJ-12 to RJ-45 adapter to connect the X cable. See Connecting Raritan Environmental Sensor Packages (on page 33).

RJ-12 RJ-45 RJ-12 RJ-45 ④ ③

Connecting a Logitech Webcam

Connect webcams to PX2 in order to view videos or snapshots of the webcam's surrounding area.

The following USB Video Class (UVC) compliant webcam is supported:

• Logitech ^ HD pro C920
• Logitech ^ Webcam ^ Pro 9000, Model 960-000048

Other UVC-compliant webcams may also work. However, Raritan has neither tested them nor claimed that they will work properly.

Tip: You can easily find a list of UVC-compliant webcams on the Internet.

The PX2 supports up to two webcams. You can use a "powered" USB hub to connect webcams if needed.

After connecting a webcam, you can retrieve visual information from anywhere through the PX2 web interface.

For more information on the Logitech webcam, refer to the user documentation accompanying it.

To connect a webcam:

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

Important: If a USB hub is used to connect the webcam, make sure it is a "powered" hub.

Snapshots or videos captured by the webcam are immediately displayed in the PX2 web interface after the connection is complete. See Configuring Webcams and Viewing Live Images (on page 379).

Connecting a GSM Modem

The following Cinterion ^® GSM modems can be connected to the PX2 in order to send SMS messages containing event information.

• MC52iT
• MC55iT
  • EHS6

See Available Actions (on page 284) for more information on SMS messages.

Note: PX2 cannot receive SMS messages.

To connect the GSM modem:

1. Connect the GSM modem to the serial port labeled CONSOLE / MODEM on the PX2.
2. Configure the GSM modem as needed. See the supporting GSM modem help for information on configuring the GSM modem.
3. Configure the GSM modem settings in the PX2 to specify the modem's SIM PIN number and the recipient phone number. See Configuring the Serial Port (on page 340).

Connecting an Analog Modem

The PX2 supports remote dial-in communications to access the CLI through an analog modem. This dial-in feature provides an additional alternative to access the PX2 when the LAN access is not available. To dial in to the PX2, the remote computer must have a modem connected and dial the correct phone number.

Below are the analog modems that the PX2 supports for sure:

• NETCOMM IG6000 Industrial Grade SmartModem
• US Robotics 56K modem

The PX2 may also support other analog modems which Raritan did not test.

Note that the PX2 does NOT support dial-out or dial-back operations via the modem.

To connect an analog modem:

1. Plug a telephone cord into the phone jack of the supported modem.
2. Plug the modem's RS-232 cable into the serial port labeled CONSOLE / MODEM on the PX2.

You need to enable the modem dial-in support to take advantage of this feature, see Configuring the Serial Port (on page 340).

Connecting an External Beeper

The PX2 supports the use of an external beeper for audio alarms.

External beepers that are supported include but may not be limited to the following:

• Mallory Sonalert MODEL SNP2R

After having an external beeper connected, you can create event rules for the PX2 to switch on or off the external beeper when specific events occur. See Event Rules and Actions (on page 262).

To connect an external beeper:

1. Connect a standard network patch cable to the FEATURE port of the PX2.
2. Plug the other end of the cable into the external beeper's RJ-45 socket.

The beeper can be located at a distance up to 330 feet (100 m) away from the PX2.

Connecting a Schroff LHX/SHX Heat Exchanger

To remotely monitor and administer the Schroff® LHX-20, LHX-40 and SHX-30 heat exchangers through the PX2 device, you must establish a connection between the heat exchanger and the PX2 device.

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

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

To connect an LHX or SHX heat exchanger:

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

To enable the support of the LHX/SHX heat exchanger, see Miscellaneous (on page 348).

Chapter 5 Introduction to PDU Components

This chapter explains how to use the PX2 device, including:

• Introduction to the LEDs and ports on the PDU
  • Operation of the front panel display
• The overcurrent protector's behavior
  • The internal beeper's behavior
• The reset button

In This Chapter

Panel Components 69

Circuit Breakers 79

Fuse....81

Beeper....84

Threaded Grounding Point 84

Panel Components

The PX2 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 PX2 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 PX2 to an appropriately rated branch circuit. See the label or nameplate affixed to your PX2 for appropriate input ratings or range of ratings.

There is no power switch on the PX2. 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.

PX2-3000 Series

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

Outlet LEDs are not available.

PX2-4000 Series

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

A small LED adjacent to each outlet indicates the outlet state. Outlet LEDs always light red, indicating that the outlet power is ON.

PX2-5000 Series

These models are outlet-switching capable. A small LED adjacent to each outlet indicates the outlet or PDU state. The PDU is shipped from the factory with all outlets turned ON.

The table below explains how to interpret different outlet LED states.

LED state Outlet status What it means
Not lit Powered OFF		The outlet is turned off and no power is available.OR the control circuitry's power supply is broken.
Red ON and LIVE LIVE power. The outlet is on and power is available.
Red flashing ON and LIVE		The current flowing through the outlet is greater than the upper warning (non-critical) threshold.
Green	OFF and	The outlet is turned off and power is available when the outlet is turned on.
Green flashing OFF and NOT LIVE		The outlet is turned off and power is not available.For example, a circuit breaker has tripped or a phase fails on a three-phase model.
Red and Green flashing alternatively	ON and NOT LIVE	The outlet is turned on but power is not available.For example, a circuit breaker has tripped or a phase fails on a three-phase model.
Cycling through Red, Green and Yellow	n/a	The PX2 device has just been plugged in and its management software is loading. LED color cycling does not interrupt power to outlets. It is an indication of firmware loading.

Note: When a PX2 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. When the software has completed loading, the outlet LEDs show a steady color and the front panel display illuminates.

Connection Ports

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

Zero U Connection Ports

For most of PX2 Zero U models, there are 6 ports on the front panel.

FEATURE USB-B SENSOR ETHERNET USB-A CONSOLE/MODEM

1U and 2U Port Locations

The difference between Zero U, 1U and 2U models is that Zero U models have all the connection ports located on the front panel while 1U and 2U models have the ports located respectively on the front and back panels. In addition, many PX2 series 1U and 2U models are implemented with two SENSOR ports on the back panel as shown on the following diagram.

SENSOR 1 SENSOR 2 ETHERNET FEATURE

Connection Port Functions

The table below explains the function of each port.

Port Used for...
USB-B	Cascading PX2 devices for sharing a network connection. See Cascading All Devices via USB (on page 30).Establishing a USB connection between a computer and the PX2 for:Using the command line interface.Performing the disaster recovery. Contact Raritan Technical Support for instructions.Connecting to an Android mobile device for viewing or configuring the PX2.See Connecting a Mobile Device to PX2 (on page 20).
USB-A	This is a "host" port, which is powered, per USB 2.0 specifications.Connecting to an iOS mobile device for viewing or configuring the PX2.See Connecting a Mobile Device to PX2 (on page 20).Connecting a USB device, such as a Logitech® webcam or wireless LAN adapter.Cascading PX2 devices for sharing a network connection.
FEATURE Connection to one of the following devices:A Raritan access product, such as Dominion KX III KVM switch, with the use of a power CIM.A Schroff® LHX-20, SHX-30 or LHX-40 device, using an RJ-45 to RS-232 cable provided by Schroff.An external beeper with the RJ-45 socket.A Raritan asset management strip, which allows you to track the locations of IT devices on the rack.See Connecting External Equipment (Optional) (on page 33).Warning: This is not an RS-232 port so do NOT plug in an RS-232 device, or damages can be caused to the device.
CONSOLE/MODEM(DB9)	Establishing a serial connection between the PX2 and a computer or modem.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 PX2 to the computer.
SENSOR(RJ-45)	Connection to one of the following devices:Raritan's environmental sensor package(s).Raritan's sensor hub, which expands the number of a sensor port to four ports.

Port Used for...

ETHERNET Connecting the PX2 to your company's network via a standard network patch cable (Cat5e/6). This connection is necessary to administer or access the PX2 remotely.

There are two small LEDs adjacent to the port:

■ Green indicates a physical link and activity.
- Yellow indicates communications at 10/100 BaseT speeds.

Note: Network connection to this port is not required if wireless connection is preferred, or if the PX2 is a slave device in the cascading configuration.

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/GB/UB UP BOTH DOWN CURRENT (A) VOLTAGE (V) POWER (kW) UB LOAD (%) SENSOR

1U models:

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

2U models:

OUTLET / LINE / CB / US CURRENT ○ (A) VOLTAGE ○ (V) POWER ○ (kW) UB LOAD ○ (%) 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 readability.

Note: When a PX2 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:

• Current, voltage, or active power of the selected outlet
• Active power or unbalanced load of the inlet
• Current of the selected circuit breaker
- Current and voltage 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 circuit breaker associated with the selected outlet has tripped or the fuse has blown

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 PX2 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, 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.
☐ ix: This refers to the selected inlet on a multi-inlet PDU, where x is the inlet number. For example, i1 refers to Inlet 1, and i2 refers to Inlet 2.

The two-digit row shows the inlet number while displaying an inlet's line or active power on a multi-inlet PDU. It will cycle through the selected inlet number and that inlet's line or active power (AP). For example, when cycling through i1 and L1, the value displayed in the three-digit row belongs to Inlet 1's L1, and when cycling through i2 and L1, the displayed value belongs to Inlet 2's L1.

Note: The point of the alphabet 'i' cannot be displayed on the LED display so i1 looks like 1 and i2 looks like 2.

During the firmware upgrade, some PX2 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 PX2. This is the Automatic Mode.

If your PDU is a multi-inlet PDU, it will cycle through the line readings of different inlets and circuit breaker readings.

For each line reading, the PX2 always displays i1 for Inlet 1 or i2 for Inlet 2 in the two-digit row of the LED display as described below:

When showing L1 of Inlet 1, the two-digit row cycles through i1 and L1.
When showing L1 of Inlet 2, the two-digit row cycles through i2 and L1.

Note: The point of the alphabet 'i' cannot be displayed on the LED display so i1 looks like 1 and i2 looks like 2.

Manual Mode

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

In addition, you can select a particular inlet if your PDU has more than one inlet. Each inlet is indicated as i1, i2, or the like in the two-digit row of the LED display.

Note: The point of the alphabet 'i' cannot be displayed on the LED display so i1 looks like 1 and i2 looks like 2.

To operate the LED display:

1. Press the Up or Down button until the desired outlet, 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.

If your PDU is a multi-inlet PDU and you select a specific inlet's line or active power (AP), the two-digit row will cycle through the selected inlet number and that inlet's line or active power. For example:

• When showing L1 of Inlet 1, the two-digit row cycles through i1 and L1.
• When showing L1 of Inlet 2, the two-digit row cycles through i2 and L1.
• When showing active power of Inlet 1, the two-digit row cycles through i1 and AP.

• When showing active power of Inlet 2, the two-digit row cycles through i2 and AP.

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

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

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

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

• When selecting AP, it displays the selected inlet's 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.

Outlet Switching

This section applies to outlet-switching capable models only.

You can operate the front panel LED display to turn on or off an outlet. To do this, you must first enable the front panel outlet control function. See Front Panel Settings (on page 340).

▶ To turn on an outlet:

1. Press the Up or Down button until the desired outlet's number is shown in the two-digit row.
2. Press and hold the Up button until the confirmation message "on?" is shown in the three-digit row.

onP

1. Press and hold the Up button until the above confirmation message disappears, indicating that the outlet has been turned on.
2. Verify that the desired outlet's LED has turned red.

To turn off an outlet:

1. Press the Up or Down button until the desired outlet's number is shown in the two-digit row.
2. Press and hold the Down button until the confirmation message "oF?" is shown in the three-digit row.

oFP

1. Press and hold the Down button until the above confirmation message disappears, indicating that the outlet has been turned off.
2. Verify that the desired outlet's LED has turned green.

Tip: If you want to abort the outlet switching operation after the confirmation message appears, press either button (without holding it) and the confirmation message will disappear.

Reset Button

The reset button is located inside the small hole near the display panel on the PDU.

Pressing this reset button restarts the software of PX2 without any loss of power to outlets.

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

The following image illustrates the location of the reset button on Zero U models only.

PX2 Zero U models:

Raritan RESET CUTLET/LIME (CB) /SB UP BOTH DOWN CURRENT (IN) VOLTAGE (IN) POWER (PWM) UNLOAD (IN) SENSOR FEATURE USB-B SENSOR ETHERNET USB-A CONSOLE/HOSEM

Circuit Breakers

PX2 models rated over 20A (North American) or 16A (international) contain overcurrent protectors for outlets, which are usually 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 front panel display shows:

• CbE, which means "circuit breaker error."
  • The affected circuit breaker's number, such as C1, C2, and the like.
  You are still able to switch between outlets on the PDU's display panel when the circuit breaker error occurs. Outlets affected by the error show CbE. Unaffected outlets can show diverse sensor readings properly.

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

ON 20 O OFF

1. Examine your PX2 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 that the breaker has tripped.

42°C 40V 480N 3270V X pole FAZ-C2010-NA

1. Examine your PX2 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. 40°C 40V 480V×275V- pole FAZ-C20/2-NA

Fuse

Some PX2 devices may be 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 and type of the new fuse must be the same as the original one.

Use of inappropriately rated fuse results in damage to the PDU and connected equipment, electric shock, fire, personal injury or death.

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

Fuse Replacement on Zero U Models

This section only applies to a Zero U PDU with "replaceable" fuses.

To replace a fuse on Zero U models:

1. Lift the hinged cover over the fuse.

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

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 rear panel with a magnified inset showing internal components and a red arrow indicating rotation (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 view of a connector (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

②

Fuse knob where a fuse is installed

To replace a fuse on 1U PDUs:

1. Disconnect the PDU's power cord from the power source.

2. Remove the desired fuse from the PDU's fuse carrier using a flat screwdriver.

a. Rotate the fuse knob counterclockwise until its slot is inclined to 45 degrees.

Two circular metallic objects with internal markings, one showing a horizontal bar and the other with a diagonal stripe (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

②

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 tool tip, showing no readable text or symbols.

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 panel background.

Number Description

①

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 PX2 includes an internal beeper to issue an audible alarm for an overcurrent protector which is open.

• The beeper sounds an alarm within 3 seconds of a circuit breaker trip.
• The beeper stops as soon as all circuit breakers have been reset. You can also set the internal beeper to sound for specific events. See Event Rules and Actions (on page 262).

Tip: To remotely check this beeper's state via the web interface, see PDU (on page 107).

Threaded Grounding Point

If the PX2 model you purchased is designed to have a threaded grounding point, you can identify it via the grounding symbol as shown below:

Wire this point to an electrical system in order to protectively ground the PX2.

Chapter 6 Using the Web Interface

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

In This Chapter

Supported Web Browsers 86

Login, Logout and Password Change 86

Web Interface Overview....90

Dashboard 97

PDU 107

Inlet....113

Outlets 118

Outlet Groups 136

OCPs 149

Peripherals....156

Feature Port 178

User Management....192

Device Settings....203

Maintenance 350

Webcam Management....377

Supported Web Browsers

■ Internet Explorer © 11
- Firefox ^® 52 and later
■ Safari ^® (Mac)
- Google ^ Chrome ^ 52 and later
- Android 4.2 and later
- iOS 7.0 and later

Login, Logout and Password Change

The first time you log in to the PX2, use the factory default "admin" user credentials. For details, refer to the Quick Setup Guide accompanying the product.

After login, you can create user accounts for other users. See Creating Users (on page 193).

Login

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

To log in to the web interface:

1. Open a browser and type the IP address of your PX2.

- If the link-local addressing has been enabled, you can type pdu.local instead of an IP address. See APIPA and Link-Local Addressing (on page 2).

New Tab 192.168.84.92

Tip: You can also enter the desired page's URL so that you can immediately go to that page after login. See Quick Access to a Specific Page (on page 95).

1. If any security alert message appears, accept it.
2. The login screen displays. Type your user name and password. User credentials are case sensitive.

Raritan® A brand of □ legrand admin Login

1. [Optional] If a security agreement is displayed, accept it. Otherwise, you cannot log in.

Note: To configure the security agreement, see Enabling the Restricted Service Agreement (on page 257).

1. Click Login or press Enter. The web interface of PX2 opens. Depending on your hardware configuration, your web interface shown onscreen may look slightly different from the image below.

Note: The address to access a slave device in the Port Forwarding mode via non-standard ports is a combination of a protocol (http:// or https://), an IP address and a port number. SeePort Forwarding Examples (on page 223).

Changing Your Password

You need appropriate permissions to change your password. Refer to the following for details.

To change other users' passwords, Administrator Privileges are required instead. See Editing or Deleting Users (on page 197).

▶ Password change request on first login:

On first login if you have both the Change Local User Management and Change Security Settings permissions, you can choose to either change your password or ignore it.

• Not Now ignores the request for this time only.
- Do not ask again ignores the request permanently. If you select this checkbox, then click Not Now.
- Or enter the new password and click Ok.

Password change recommended for User 'admin' Password required Confirm password required □ Do not ask again. Not Now Ok

Users without permissions listed must change password.

Note: This password change request also appears if the 'force password change' is enabled in the user account setting. See Creating Users (on page 193).

To change your password via the Change Password command:

You must have the Change Own Password permission to change your own password. See Creating Roles (on page 199).

1. Choose User Management > Change Password.
2. First type the current password, and then the new password twice. Passwords are case sensitive.
3. A password comprises 4 to 64 characters.

Change Password - admin Old Password required New password required Confirm password required ✓ Save

Remembering User Names and Passwords

PX2 supports the password manager of common web browsers, including:

• Microsoft Internet Explorer®
- Mozilla Firefox ^®
- Google Chrome ^③

You can save the login name and password when these browsers ask whether to remember them.

For information on how to activate a web browser's password manager, see the user documentation accompanying your browser.

PX2 does NOT support other browser password managers.

Logout

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

To log out without closing the web browser:

• Click "Logout" on the top-right corner.
  -- OR --
• Close the tab of PX2 while there are other tabs available in the browser.

To log out by closing the web browser:

- Click ✗ on the top-right corner of the window. -- OR --

- Choose File > Close, or File > Exit.

Web Interface Overview

The web interface consists of four areas as shown below.

▶ Operation:

1. Click any menu or submenu item in the area of ①.
2. That item's data/setup page is then opened in the area of ②.
3. Now you can view or configure settings on the opened page.
4. To return to the main menu and the Dashboard page, click

on the top-left corner.

Chapter 6: Using the Web Interface

Number Web interface element
1	Menu (on page 92)
2	Data/setup page of the selected menu item.
3	■ Left side:- PX2 device name.Note: To customize the device name, see PDU (on page 107).■ Right side:- Displayed language, which is English (EN) by default. You can change it.- Your login name, which you can click to view your user account settings.- Logout button.
4	From top to bottom --■ Your PX2 model.■ Current firmware version.■ Online Documentation: link to the online help of PX2.- SeeBrowsing through the Online Help(on page 733).■ Raritan Support: link to Raritan Technical Support webpage.■ Date and time of your user account's last login.- Click Last Login to view your login history.■ PX2 system time, which is converted to the time zone of your computer or mobile device.- Click Device Time to open the Date/Time setup page.

Menu

Depending on your model and hardware configuration, your PX2 may show all or some menu items shown below.

Chapter 6: Using the Web Interface

Dashboard
PDU
Inlet
Outlets
Outlet Groups
OCPs
Peripherals
Feature Port
User Management	>
Device Settings	>
Maintenance	>

Menu Information shown
Dashboard Summary of the PX2 status, including a list of alerted sensors and alarms, if any.See Dashboard (on page 97).
PDU Device data and settings, such as the device name and MAC address.See PDU (on page 107).
Inlet Inlet status and settings, such as inlet thresholds.See Inlet (on page 113).
Outlets Outlet status, settings and outlet control if your model is outlet-switching capable.See Outlets (on page 118).
Outlet Groups You can create one or multiple groups comprising one or multiple outlets of the same PX2.Functions which you can perform on an outlet group vary depending on the model you purchased.See Outlet Groups (on page 136).
OCPs	The OCPs menu item displays only when there are overcurrent protectors implemented on your model.
	OCP status and settings, such as OCP thresholds.See OCPs (on page 149).
Peripherals	Status and settings of Raritan environmental sensor packages, if connected.See Peripherals (on page 156).
Feature Port	Status and settings of the device connected to the Feature port(s), which can be one of the following.
The name‘Feature Port(s)’will be replaced with one of the device names listed to the right	Asset StripExternal BeeperLHX 20SHX 30LHX 40Power CIMSee Feature Port (on page 178).
Webcams	The ‘Webcams’ menu item appears when there is any webcam(s) connected to the PX2, or when there are snapshots saved onto the PX2 already.
	Webcam live snapshots/video and webcam settings.See Webcam Management (on page 377).
User Management	Data and settings of user accounts and groups, such as password change.See User Management (on page 192).
Device Settings	Device-related settings, including network, security, system time, event rules and more.See Device Settings (on page 203).
Maintenance Device	information and maintenance commands, such as firmware upgrade, device backup and reset.See Maintenance (on page 350).

If a menu item contains the submenu, the submenu is shown after clicking that item.

To return to the previous menu list, do any below:
- Click the topmost link with the symbol < . For example, click

Home User Management Users Roles Change Password User Preferences Default Preferences

- Click men

on the top-left corner to return to the main

Quick Access to a Specific Page

If you often visit a specific page in the PX2 web interface, you can note down its URL or bookmark it with your web browser. Next time, you just enter its URL in the address bar of the browser prior to login. After login, the PX2 immediately shows the wanted page rather than the Dashboard page.

Besides, you can also send the URL to other users so that they immediately see that page after login, using their own user credentials.

URL examples:

In the following examples, it is assumed that the IP address of PX2 is 192.168.84.118.

Page URL
Peripherals	https://192.168.84.118/#/peripherals
Event Log https://192.168.84.118/#/maintenance/eventLog/0

Sorting a List

If any list displays an arrow (▲ or ▼) in one of its column headers, you are allowed to resort the list by clicking any column header. The list will be resorted in the ascending or descending order based on the selected column.

▶ Illustration -- Event Log:

1. By default, the Event Log is sorted in the descending order based on the ID column. Therefore, the arrow ▼ is displayed adjacent to the ID header.
2. To have it resorted in the ascending order based on the same column, click the ID header.

ID ▼	Timestamp	Event Class
665	7/24/2017, 3:14:43 AM Eastern Daylight Time	User Activity
664	7/24/2017, 2:42:35 AM Eastern Daylight Time	Sensor
663	7/24/2017, 2:42:35 AM Eastern Daylight Time	Sensor
662	7/24/2017, 2:42:35 AM Eastern Daylight Time	Sensor

1. The arrow turns to ▲, indicating the list is sorted in the "ascending" order.

1. To resort the list based on a different column, click a different column header. In this example, the 'Event Class' column is clicked.

ID ▲ Timestamp Event Class Event

1. The arrow ▲ now appears adjacent to the selected column 'Event Class,' indicating the list is sorted in the ascending order based on that column.

ID

Timestamp

Event Class ▲

Event

Dashboard

The Dashboard page contains four to five sections, depending on your model.

Number Section Information shown
1	Inlet 11	Overview of inlet power dataA current bar per phase, which changes colors to indicate the RMS current state- green: normalyellow: warningred: criticalSee Dashboard - Inlet 11(on page 99).
2	Overcurrent Protectors	This section is available only when your PX2 contains overcurrent protectors (OCPs).
		Overview of each OCP's statusA current bar per OCP, which changes colors to indicate the RMS current state- green: normal- yellow: warning- red: criticalSee Dashboard - OCP (on page 101).
3	Alerted Sensors	When no sensors enter the alarmed state, this section shows the message "No Alerted Sensors."When any sensor enters the alarmed state, this section lists all of them.See Dashboard - Alerted Sensors (on page 102).
4	Inlet History	The chart of the inlet's active power history is displayed by default. You can make it show a different data type.See Dashboard - Inlet History (on page 103).
5	Alarms	This section can show data only after you have set event rules requiring users to take the acknowledgment action.When there are no unacknowledged events, this section shows the message "No Alarms."When there are unacknowledged events, this section lists all of them.See Dashboard - Alarms (on page 106).

The Hardware Failures section:

If PX2 detects any internal hardware issues, a section labeled "Hardware Failures" will appear on the Dashboard page, listing all of current hardware issues.

Hardware Failures

Failure Message	Last Asserted ▲	Number of Occurrences
I2C bus 0 is stuck.	1/1/2018, 1:18:24 AM UTC+0100	17

This section does NOT display as long as there are no hardware failures present. See Hardware Issue Detection (on page 374).

Dashboard - Inlet I1

The number of phases shown in the Inlet section is model dependent.

▶ Link to the Inlet page:

To view more information or configure the inlet(s), click this section's title 'Inlet l1' to go to the Inlet page. See Inlet (on page 113).

Inlet I1

Inlet 11

4.44 kW

5.13 kVA

Active Energy: 0 Wh

Power Factor: 0.86

Line Frequency: 50.0 Hz

Unbalanced Current: 25%

L1

7.5A/16A

L1-L2:398 V

L1-N:229V

L2

7.0A/16A

L2-L3: 399 V

L2-N: 230 V

L3

4.9A/16A

L3-L1:396 V

L3-N: 230 V

Left side - generic inlet power data:

4.44 kW

5.13 kVA

Active Energy: 0 Wh

Power Factor: 0.86

Line Frequency: 50.0 Hz

Unbalanced Current: 25%

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

• Active power (kW or W)
- Apparent power (kVA or VA)
• Active energy (kWh or Wh)
- Power factor
- Unbalanced current (%) - model dependent

Right side - inlet's current and voltage:

L1 7.5 A / 16A L1-L2: 398 V L1-N: 229 V

The right side shows the current and voltage data per phase. For a single-phase device, it shows only one line, but for a three-phase device, it shows three lines (L1, L2 and L3).

Inlet data from top to bottom includes:

• RMS current (A) and rated current
- The smaller, gray text adjacent to RMS current is the rated current.
• A bar showing the RMS current level
- RMS voltage (V)

The RMS current bars automatically change colors to indicate the current status if the thresholds have been enabled. To configure thresholds, see Inlet(on page 113).

Status Bar colors
normal
above upper warning
above upper critical

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

Dashboard - OCP

Availability and total number of OCPs depend on the models.

▶ Each OCP's link:

To view more information or configure individual OCPs, click the desired OCP's index number, which is C1, C2 and the like, to go to its setup page.

▶ Each OCP's power data:

OCP data from top to bottom includes:

• RMS current (A), and rated current

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

• A bar showing OCP current levels
- OCP status -- open or closed
• Associated line pair

The RMS current bars automatically change colors to indicate the current status if OCP thresholds have been enabled. To configure thresholds, see OCPs (on page 149).

Status Bar colors
normal
above upper warning
above upper critical

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

Dashboard - Alerted Sensors

When any internal sensors or environmental sensor packages connected to the PX2 enter an abnormal state, the Alerted Sensors section in the Dashboard show them for alerting users. This section also lists tripped circuit breakers or blown fuses, if available.

To view detailed information or configure each alerted sensor, you can click each sensor's name to go to individual sensor pages. See Individual Sensor/Actuator Pages (on page 171).

If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

Alerted Sensors (1 Critical, 1 Warned) Sensors Value State ▲ Temperature 3 20.7 °C ▲ above upper critical Temperature 1 19.8 °C ▲ above upper warning

Summary in the section title:

Information in parentheses adjacent to the title is the total number of alerted sensors.

For example:

• 1 Critical: 1 sensor enters the critical or alarmed state.

• Numeric sensors enter the critical state.
• State sensors enter the alarmed state.

• 1 Warned: 1 'numeric' sensor enters the warning state.

List of alerted sensors:

Two icons are used to indicate various sensor states.

Icons Sensor states
	Numeric sensors:▪ above upper warning▪ below lower warning
	Numeric sensors:▪ above upper critical▪ below lower critical
	State sensors:▪ alarmed state

For details, see Sensor/Actuator States (on page 165).

Dashboard - Inlet History

The inlet's power chart helps you observe whether there were abnormal events within the past tens of minutes. The default is to show the inlet's active power data.

You can have it show the chart of other inlet power data. Simply select a

different data type by clicking the selector ▼ below the diagram. Available data types include:

• RMS current
• RMS voltage
  • Active power
• Apparent power

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

Inlet selection on multi-inlet models:

If your PDU is a multi-inlet model, you can have one or multiple inlets show their power charts by selecting the checkbox(es) of the desired inlet(s).

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

Inlet A

Inlet B

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

Dashboard - Alarms

If configuring any event rules which require users to take the acknowledgment action, the Alarms section will list any event which no one acknowledges yet since event occurrence.

Note: For information on event rules, see Event Rules and Actions (on page 262).

Only users with the 'Acknowledge Alarms' permission can manually acknowledge an alarm.

To acknowledge an alarm:

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

Alarms

Name: System Tamper Alarm

Reason: Peripheral device 'Tamper Detector 1' in slot 11 is alarmed.

First Appearance: 7/4/2017, 7:55:44 AM Eastern Daylight Time

Last Appearance: 7/4/2017, 7:58:20 AM Eastern Daylight Time

Count: 3

More Alerts: 1 more reasons

Acknowledge

This table explains each column of the alarms list.

Field Description

Name Custom name of the Alarm action.

Reason The first event that triggers the alert.

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

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

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

Field Description

More Alerts

This field appears only when there are more than one types of events triggering this alert.

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

The date and time shown on the PX2 web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of PX2 to your computer or mobile device.

PDU

The PX2 device's generic information and PDU settings are available on the PDU page.

To open the PDU page, click 'PDU' in the Menu (on page 92).

▶ Device information shown:

• Firmware version
• Serial number
• MAC address

• Rating
  • Internal beeper state (on page 110)
  ▶ To configure global settings:

• Click Edit Settings.

Settings
Name	My PDU
Outlet state on device startup	last known
Outlet initialization delay on device startup	3 s
Power off period during power cycle	10 s
Inrush guard delay	200 ms
Reset all energy counters	Reset

1. Now you can configure the fields.

Click ▼ to select an option. Adjust the numeric values. For time-related fields, if you do not prefer the option selection using ▼, you can type a value manually which must include a time unit, such as '50 s'. See Time Units (on page 112).

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

Field Function Note
Name Customizes the device name.
*Outlet state on device startup	Determines the initial power state of ALL outlets after the PX2 powers up.▪Options: on, off, and last known SeeOptions for Outlet State on Startup(on page 110).	▪ After removing power from the PDU, you must wait for a minimum of 10 seconds before powering it up again. Otherwise, the default outlet state settings may not work properly.▪ You can override the global outlet state setting on a per-outlet basis so specific outlets behave differently on startup. SeeIndividual Outlet Pages(on page 129).
*Outlet initialization delay on device startup	Determines how long the PX2 waits before providing power to all outlets during power cycling or after recovering from a temporary power loss.▪Range: 1 second to 1 hour	SeeInitialization Delay Use Cases(on page 111).
*Power off period during power cycle	Determines the power-off period after the outlet is switched OFF during a power cycle.▪Range: 1 second to 1 hour	▪ Power cycling the outlet(s) turns the outlet(s) off and then back on.▪ You can override this global power cycle setting on a per-outlet basis so specific outlets' power-off period is different. SeeIndividual Outlet Pages(on page 129).
*Inrush guard delay	Prevents a circuit breaker trip due to inrush current when many devices connected to the PDU are turned on.▪Range: 100 milliseconds to 10 seconds	SeeInrush Current and Inrush Guard Delay(on page 111).

1. Click Save.

To reset ALL active energy counters:

An active energy reading is a value of total accumulated energy, which is never reset, even if the power fails or the PX2 is rebooted. However, you can manually reset this reading to restart the energy accumulation process.

Only users with the "Admin" role assigned can reset active energy readings.

Note: This reset button does not reset the active energy values of outlet groups. See Outlet Groups (on page 136).

Reset

1. Click

2. Click Reset on the confirmation message.

- All active energy readings on this PX2 are reset to zero.

Tip: You can choose to reset the active energy reading of an individual inlet or outlet only. See Inlet (on page 113) or Individual Outlet Pages (on page 129).

To view total active energy and power on multi-inlet models:

If your PX2 is a multi-inlet model or an in-line monitor, a "Power" section for showing the data of total active energy and total active power is available on the PDU page.

For a regular PX2 model with multiple inlets:

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

For an in-line monitor with multiple inlets/outlets:

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

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

Sensor	Value	State
Active Power	16 W	normal
Active Energy	100243 Wh	normal

To configure the thresholds of total active energy and power:

For a multi-inlet model or an in-line monitor, a "Thresholds" section is also available on the PDU page. See Setting Thresholds for Total Active Energy or Power (on page 112).

Thresholds

Internal Beeper State

The PDU page indicates the internal beeper state.

Internal Beeper

State

Off

Available beeper states:

States Description

Off The beeper is turned off.

The beeper is turned on. Active

"Activation Reason" is displayed, indicating why the beeper sounds an alarm.

For example, if the beeper is turned on because of a specific event rule "XXX," the activation reason looks like:

Event Action triggered by rule: XXX

▶ Scenarios when the beeper sounds an alarm:

• Any overcurrent protector on the PX2, including fuses and circuit breakers, has tripped or blown. See Beeper (on page 84).
• You have set an event rule that turns on the internal beeper when a specific event occurs, and that event occurs now. See Event Rules and Actions (on page 262).

Tip: To check the internal beeper state via CLI, see PDU Configuration (on page 410).

Options for Outlet State on Startup

The following are available options for initial power states of outlets after powering up the PX2 device.

Option Function

on Turns on the outlet(s).

off Turns off the outlet(s).

last known Restores the outlet(s) to the previous power state(s) before the PX2 was powered off.

If you are configuring an individual outlet on Individual Outlet Pages (on page 129), there is one more outlet state option.

Additional option	Function
PDU defined (xxx)	Follows the global outlet state setting, which is set on PDU (on page 107).The value xxx in parentheses is the currently-selected global option - on, off, or last known.

Initialization Delay Use Cases

Apply the initialization delay in either of the following scenarios.

• When power may not initially be stable after being restored
• When UPS batteries may be charging

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

Inrush Current and Inrush Guard Delay

Inrush current:

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

Inrush guard delay:

The inrush guard delay feature helps prevent a circuit breaker trip due to the combined inrush 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.

Time Units

If you choose to type a new value in the time-related fields, such as the Inrush Guard Delay field, you must add a time unit after the numeric value. For example, you can type '15 s' for 15 seconds.

Note that different fields have different range of valid values.

Time units:

Unit Time
ms	millisecond(s)
s	second(s)
min	minute(s)
h	hour(s)
d	day(s)

Setting Thresholds for Total Active Energy or Power

This section applies only to multi-inlet models, including in-line monitors.

Thresholds for total active energy and total active power are disabled by default. You can enable and set them so that you are alerted when the total active energy or total active power hits a certain level.

For a regular PX2 model with multiple inlets:

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

For an in-line monitor with multiple inlets/outlets:

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

To configure thresholds for total active energy and/or power:

1. Click PDU.

Chapter 6: Using the Web Interface

- On the PDU page, you can also view the total active power and total active energy. See PDU (on page 107).

1. Click the Thresholds title bar at the bottom of the page to display thresholds.

Thresholds

1. Click the desired sensor (required), and then click Edit Thresholds.

Thresholds Edit Thresholds Sensor ▲ Lower Critical Lower Warning Upper Warning Upper Critical Active Energy --- --- --- --- Active Power --- --- --- ---

1. Make changes as needed.

2. To enable any threshold, select the corresponding checkbox.
   ■ Type a new value in the accompanying text box.

Lower Critical 0 W Lower Warning 0 W Upper Warning 0 W Upper Critical 0 W Deassertion Hysteresis 0 W Assertion Timeout 0 Samples

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

1. Click Save.

Inlet

You can view all inlet information, configure inlet-related settings, or reset the inlet active energy on the Inlet page. To open this page, click 'Inlet' in the Menu (on page 92).

Inlet thresholds, once enabled, help you identify whether the inlet enters the warning or critical level. In addition, you can have PX2 automatically generate alert notifications for any warning or critical status. See Event Rules and Actions (on page 262).

Note: If your PX2 is a multi-inlet model, see Configuring a Multi-Inlet Model (on page 116).

▶ Generic inlet information shown:

• Inlet power overview, which is the same as Dashboard - Inlet 11 (on page 99).
• A list of inlet sensors with more details. Number of available inlet sensors depends on the model.

■ Sensors show both readings and states.
■ Sensors in warning or critical states are highlighted in yellow or red.

See Yellow- or Red-Highlighted Sensors (on page 163).

- Inlet's power chart, which is the same as Dashboard - Inlet History (on page 103)

To customize the inlet's name:

1. Click Edit Settings.

Settings Edit Settings Label 11 Name Reset energy counter Reset

1. Type a name for the inlet.

- For example, you can name it to identify the power source.

1. Click Save.
2. The inlet's custom name is displayed on the Inlet or Dashboard page, followed by its label in parentheses.

To reset the inlet's active energy counter:

Only users with the "Admin" role assigned can reset active energy readings.

The energy reset feature per inlet is especially useful when your PX2 has more than one inlet.

Reset

1. Click

2. Click Reset on the confirmation message.

This inlet's active energy reading is then reset to zero.

Tip: To reset ALL active energy counters on the PX2, see PDU (on page 107).

To configure inlet thresholds:

Per default, there are pre-defined RMS voltage and current threshold values in related fields. See Default Voltage and Current Thresholds (on page 711). You can modify them to meet your needs.

1. Click the Thresholds title bar at the bottom of the page to display inlet thresholds.

Thresholds

1. Click the desired sensor (required), and then click Edit Thresholds.

Thresholds
				Edit Thresholds
Sensor ▲	Lower Critical	Lower Warning	Upper Warning	Upper Critical
Active Energy	—	—	—	—
Active Power	—	—	—	—
Apparent Power	—	—	—	—
Line Frequency	57 Hz	59 Hz	61 Hz	63 Hz
Power Factor	—	—	—	—
RMS Current	—	—	5 A	10 A
RMS Voltage	160 V	180 V	240 V	250 V

1. Make changes as needed.

■ To enable any threshold, select the corresponding checkbox.
■ Type a new value in the accompanying text box.

Lower Critical 94 V Lower Warning 97 V Upper Warning 247 V Upper Critical 254 V Deassertion Hysteresis 2 V Assertion Timeout 0 Samples

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

1. Click Save.

Configuring a Multi-Inlet Model

If the PX2 has more than one inlet, the Inlets page lists all inlets.

To view or configure each inlet:

1. Click 'Show Details' of the desired inlet.

1. Now you can configure the selected inlet, such as enabling thresholds or resetting its energy. See Inlet (on page 113).
2. To disable the inlet, see the following instructions.

To disable one or multiple inlets:

1. On the individual inlet's data page, click Edit Settings.

Settings Edit Settings Label A Name Status Enabled Reset Active Energy Reset Energy

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

Settings Edit Settings Label A Name Status Disabled Reset Active Energy Reset Energy

1. To disable additional inlets, repeat the above steps.

- If disabling an inlet will result in all inlets being disabled, a confirmation dialog appears, indicating that all inlets will be disabled. Then click Yes to confirm this operation or No to abort it.

After disabling any inlet, the following information or features associated with the disabled one are no longer available:

• Sensor readings, states, warnings, alarms or event notifications associated with the disabled inlet.
• Sensor readings, states, warnings, alarms or event notifications for all outlets and overcurrent protectors associated with the disabled inlet.
• The outlet-switching capability, if available, for all outlets associated with the disabled inlet.

Exception: All active energy sensors continue to accumulate data regardless of whether any inlet has been disabled.

Warning: A disabled inlet, if remaining connected to a power source, continues to receive power from the connected power source and supplies power to the associated outlets and overcurrent protectors.

Outlets

The Outlets page shows a list of all outlets and the overview of outlet status and data. To open this page, click 'Outlets' in the Menu (on page 92).

On this page, you can:

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

Outlets
#▲	Name	Status	RMS Current	Active Power	Power Factor
1	Outlet 1	on	0.211 A	41 W	0.98
2	Outlet 2	on	0.793 A	155 W	0.98
3	Outlet 3	on	0.274 A	53 W	0.98
4	Outlet 4	on	0.236 A	46 W	0.98
5	Outlet 5	on	0.673 A	131 W	0.98
6	Outlet 6	on	0.782 A	153 W	0.98
7	Outlet 7	on	0.547 A	107 W	0.98
8	Outlet 8	on	0.305 A	59 W	0.98

- Go to an individual outlet's data/setup page by clicking an outlet's name. See Individual Outlet Pages (on page 129).

Outlets
#▲	Name
1	Outlet 1
2	Outlet 2
3	Outlet 3
4	Outlet 4

If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

To show or hide specific columns on the outlets overview page:

1. Click to show a list of outlet data types.
2. Select those you want to show, and deselect those you want to hide. See Available Data of the Outlets Overview Page (on page 122).

To configure global outlet settings or perform the load-shedding command:

1. Click : to show a list of commands.
2. Select the desired command.

Note that only outlet-switching capable models have the commands marked with * in the table.

Command Refer to
Threshold Bulk Setup	Bulk Configuration for Outlet Thresholds (on page 123)
*Sequence Setup	Setting Outlet Power-On Sequence and Delay (on page 124)
*Load Shedding Setup	Setting Non-Critical Outlets (on page 125)
*Activate Load Shedding -- OR--Deactivate Load Shedding	Load Shedding Mode (on page 126)

To power control or reset the active energy readings of multiple outlets:

You can switch any outlet regardless of its current power state. That is, you can turn on any outlet that is already turned on, or turn off any outlet that is already turned off.

1. Click ☑ to make checkboxes appear in front of outlets.

Tip: To perform the desired action on only one outlet, you can simply click that outlet without making the checkboxes appear.

1. Select multiple outlets.

- To select ALL outlets, select the topmost checkbox in the header row.

▲

Name 1 Outlet 1 2 Outlet 2 3 Outlet 3

1. Click or select the desired button or command.

Button/command Action
On	Power ON.
Off	Power OFF.
Cycle	Power cycle.▪ Power cycling the outlet(s) turns the outlet(s) off and then back on.
> Reset Active Energy	Resets active energy readings of selected outlets.▪ Only users with the "Admin" role assigned can reset active energy readings.

Confirm the operation when prompted.

Tip: To reset ALL active energy counters on the PX2, see PDU (on page 107). You can also power control an outlet or reset its active energy from Individual Outlet Pages (on page 129).

1. When performing any outlet-switching operation, a 'Sequence running' message similar to the following displays before the outlet-switching process finishes.

- It indicates how many selected outlets are NOT switched on/off or cycled yet.

- If needed, click operation. ✗ Cancel to stop the outlet-switching

Sequence running, 8 remaining × Cancel

▲ Name

✓ 1 Outlet 1 ✓ 2 Outlet 2 ✓ 3 Outlet 3

Available Data of the Outlets Overview Page

All or some of the following outlet data is displayed on the outlets overview page based on your model and selection. To show or hide

specific data, click 📄. See Outlets (on page 118).

- Outlet status, which is marked with either icon below. This information is available on outlet-switching capable models only.

Icon Outlet status
	Outlet turned on
	Outlet turned off

• RMS current (A)
  • Active power (W)
• Power factor
• Non-critical setting for indicating whether the outlet is a non-critical outlet. This information is available on outlet-switching capable models only.

Non-critical setting Description

true The outlet is a non-critical outlet, which will be turned OFF in the load shedding mode. See Load Shedding Mode (on page 126).

false The outlet is a critical outlet, which will remain unchanged in the load shedding mode.

Note: To set critical and non-critical outlets, go to Outlets (on page 118).

Bulk Configuration for Outlet Thresholds

Outlet thresholds, if enabled, help you identify whether any outlet enters the warning or critical level. See Yellow- or Red-Highlighted Sensors (on page 163). In addition, you can have PX2 automatically generate alert notifications for any warning or critical status. See Event Rules and Actions (on page 262).

Thresholds of multiple or all outlets can be configured simultaneously on the Outlets page.

Per default, there are pre-defined RMS voltage and current threshold values in related fields. See Default Voltage and Current Thresholds (on page 711).

To configure thresholds-related settings for multiple outlets:

1. On the Outlets page, click > Threshold Bulk Setup.

2. In the "Show Outlet Sensors of Type" field, select a sensor type.

3. Select one or multiple outlets.

- To select ALL outlets, select the topmost checkbox in the header row.

▲

Name 1 Outlet 1 2 Outlet 2 3 Outlet 3

1. Click Edit Thresholds.

2. Make changes as needed.

■ To enable any threshold, select the corresponding checkbox.
- Type a new value in the accompanying text box.

Lower Critical 94 V Lower Warning 97 V Upper Warning 247 V Upper Critical 254 V Deassertion Hysteresis 2 V Assertion Timeout 0 Samples

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

1. Click Save.

Setting Outlet Power-On Sequence and Delay

By default, outlets are sequentially powered on in the ascending order from outlet 1 to the final when turning ON or power cycling all outlets on the PX2. You can change the order in which the outlets power ON. This is useful when there is a specific order in which some IT equipment should be powered up first.

In addition, you can make a delay occur between two outlets that are turned on consecutively. For example, if the power-on sequence is Outlet 1 through Outlet 8, and you want the PX2 to wait for 5 seconds before turning on Outlet 4, after Outlet 3 is turned on, assign a delay of 5 seconds to Outlet 3.

To set the outlet power-on sequence:

1. On the Outlets page, click > Sequence Setup.
2. Select one or multiple outlets by clicking them one by one in the 'Outlet' column.
3. Click the arrow buttons to change the outlet positions.

Button Function
	Top
	Up
↓	Down
≡	Bottom
∽	Restores to the default sequence

Next time when power cycling the PX2, it will turn on all outlets based on the new outlet order.

The new order also applies when performing the power-on or power-cycling operation on partial outlets.

To set a power-on delay for any outlet:

1. On the same outlets list, click the 'Delay' column of the outlet that requires a wait after it is turned on.
2. Type a new value in seconds.
3. Click Save.

PX2 will insert a power-on delay between the configured outlet and the one following it during the power-on process.

Setting Non-Critical Outlets

Outlets that are turned off when load shedding is activated are called non-critical outlets. Outlets that are not affected by load shedding are called critical outlets. See Load Shedding Mode (on page 126).

Per default, all outlets are configured as critical.

To determine critical and non-critical outlets:

1. On the Outlets page, click > Load Shedding Setup.
2. To set non-critical outlets, select the checkboxes of those you want.
3. To select ALL outlets, select the topmost checkbox in the header row.

Load Shedding ✓ Non Critical Outlets ▲ Outlet 1 Outlet 2 Outlet 3

1. To turn non-critical outlets into critical ones, deselect their checkboxes.

- To deselect ALL outlets, deselect the topmost checkbox in the header row.

1. Click Save.

Tip: You can also set up non-critical outlet setting by configuring outlets one by one. See Individual Outlet Pages (on page 129).

Load Shedding Mode

When a UPS supplying power to PX2 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.

Outlets that are turned off when load shedding is activated are called non-critical outlets. Outlets that are not affected by load shedding are called critical outlets. By default, all outlets are critical. To set non-critical ones, see Setting Non-Critical Outlets (on page 125).

When load shedding is activated, the PX2 turns off all non-critical outlets. When load shedding is deactivated, the PX2 turns back on all non-critical outlets that were ON before entering the load shedding mode.

Exception: If you once manually perform switch-off operation on any non-critical outlets during the load shedding mode, those outlets will NOT be turned back on when exiting the load shedding mode.

Activation of load shedding can be accomplished using the web interface, SNMP or CLI, or triggered by the contact closure sensors.

Tip: It is better to check non-critical outlets prior to manually entering the load shedding mode. The non-critical information can be retrieved from the Outlets page. See Outlets (on page 118) or Available Data of the Outlets Overview Page (on page 122).

You must have the following two permissions to perform the load shedding commands.

• 'Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration'
• 'Switch Outlet' permission for all non-critical outlets

To enter the load shedding mode:

1. On the Outlets page, click

Activate Load Shedding.

Note: In case PX2 prevents you from performing this command, check your permissions, especially whether you have the Switch Outlet permission for ALL non-critical outlets.

2. Click Activate on the confirmation message.

In the load shedding mode:

■ You CANNOT power on any "non-critical" outlets.
- The lock icon 📁 appears for "non-critical" outlets that WILL be automatically powered on when deactivating the load shedding mode.
- The off icon appears for outlets, critical or non-critical, that WILL NOT be automatically powered on when deactivating the load shedding mode.

Tip: The above two icons are switched if you manually perform any power operations on non-critical outlets during the load shedding mode. See Off and Lock Icons for Outlets (on page 128).

• The message "Load Shedding Active" appears next to the 'Outlets' title.
• The Non Critical column, if not shown prior to the load shedding mode, automatically displays on the Outlets page.

Outlets Load Shedding Active
# ▲	Name	Status	Non Critical	Receptacle Type	Lines
1	Outlet 1	off	true	NEMA 5-20R	L1-NEUTRAL
2	Outlet 2	off	true	NEMA 5-20R	L1-NEUTRAL
3	Outlet 3	on	false	NEMA 5-20R	L1-NEUTRAL
4	Outlet 4	off	true	NEMA 5-20R	L1-NEUTRAL
5	Outlet 5	on	false	NEMA 5-20R	L1-NEUTRAL
6	Outlet 6	on	false	NEMA 5-20R	L1-NEUTRAL

Tip: To make the Non Critical column appear when the load shedding mode is not activated yet. See Outlets (on page 118) or Available Data of the Outlets Overview Page (on page 122).

To exit from the load shedding mode:

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

TIP -- automatic load shedding via contact closure sensors:

If you have connected a Raritan contact closure sensor to PX2, you can set up an event rule in a manner that this sensor's status change automatically activates or deactivates the load shedding mode. For an example, see Sample Environmental-Sensor-Level Event Rule (on page 319).

Off and Lock Icons for Outlets

This section further explains the following two icons for outlets, which display in the load shedding mode.

• Lock icon: It means the outlet WILL be automatically powered on after deactivating the load shedding mode.
• Off icon ⏻: It means the outlet WILL NOT be automatically powered on when deactivating the load shedding mode.

Which outlets show the lock icon :

• Non-critical outlets that were powered ON prior to the load shedding mode
• Non-critical outlets that you manually switch on during the load shedding mode

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

Which outlets show the Off icon :

• Any outlets, critical or non-critical, that were powered OFF prior to the load shedding mode
• Any outlets, critical or non-critical, that you manually switch off during the load shedding mode

Individual Outlet Pages

An outlet's data/setup page is opened after clicking the outlet's name on the Outlets overview page. See Outlets (on page 118).

Outlets
# ▲	Name
1	Outlet 1
2	Outlet 2
3	Outlet 3
4	Outlet 4

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

In addition, you can perform the following operations on this outlet page. Note that only outlet-switching capable models show the power-control buttons, and you must have the Switch Outlet permission to perform outlet-switching operations.

▶ To power control this outlet:

1. Click one of the power-control buttons.

Outlet 1 Details Label 1 Outlet Status on Receptacle Type IEC 60320 C19 Lines L1-NEUTRAL Inlet Inlet I1 Overcurrent Protector Overcurrent Protector C1

Button/command Action
On	Power ON.
Off	Power OFF.
Cycle	Power cycle. ■ Power cycling the outlet(s) turns the outlet(s) off and then back on.

1. Confirm it on the confirmation message.

Tip: To switch an outlet using the front panel display, see Outlet Switching (on page 78).

To configure this outlet:

1. Click Edit Settings.

Settings Edit Settings Name State on device startup PDU defined (last known) Power off period during power cycle PDU defined (10 seconds) Non-critical False Reset energy counter Reset

1. Configure available fields. Note that the fields marked with * are only available on outlet-switching capable models.

Field Description
Name Type an outlet	name up to 64 characters long.
*State on device startup	Click this field to select this outlet's initial power state after PX2 powers up.Options: on, off, last known and PDU defined.See Options for Outlet State on Startup(on page 110).Note that any option other than "PDU defined" will override the global outlet state setting on this particular outlet.
*Power off period during power cycle	Select an option to determine how long this outlet is turned off before turning back on.Options: PDU defined or customized time.See Power-Off Period Options for Individual Outlets(on page 136).Note that any time setting other than "PDU defined" will override the global power-off period setting on this particular outlet.
*Non-critical Select	this checkbox only when you want this outlet to turn off in the load shedding mode. See Load Shedding Mode(on page 126).

1. Click Save.
2. The outlet's custom name, if available, is displayed in the outlets list, following by its label in parentheses.

To reset this outlet's active energy reading:

Only users with the "Admin" role assigned can reset active energy readings.

Reset Energy

1. Click
2. Click Reset on the confirmation message.

Tip: To reset ALL active energy counters on the PX2, see PDU (on page 107).

To view this outlet's power chart:

By default this outlet's active power data within the past tens of minutes is shown in the power chart.

You can click the selector ▼ below the chart to show a different data type for this outlet, including:

• RMS current
• RMS voltage
  • Active power
• Apparent power

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

To configure this outlet's threshold settings:

Per default, there are pre-defined RMS voltage and current threshold values in related fields. See Default Voltage and Current Thresholds (on page 711). You can modify the defaults as needed.

Note: The threshold values set for an individual outlet will override the bulk threshold values, if any, stored on that particular outlet. SeeBulk Configuration for Outlet Thresholds (on page 123).

1. If the outlet's threshold data is invisible, click the Thresholds title bar to display it.

Thresholds

1. Click the desired sensor (required), and then click Edit Thresholds.

Thresholds
				Edit Thresholds
Sensor ▲	Lower Critical	Lower Warning	Upper Warning	Upper Critical
Active Energy	—	—	—	—
Active Power	—	—	—	—
Apparent Power	—	—	—	—
Line Frequency	—	—	—	—
Power Factor	—	—	—	—
RMS Current	—	—	10.4 A	12.8 A
RMS Voltage	—	—	—	—

1. Make changes as needed.

2. To enable any threshold, select the corresponding checkbox.
   ■ Type a new value in the accompanying text box.

Lower Critical 94 V Lower Warning 97 V Upper Warning 247 V Upper Critical 254 V Deassertion Hysteresis 2 V Assertion Timeout 0 Samples

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

1. Click Save.

▶ Other operations:

• You can go to another outlet's data/setup page by clicking the outlet selector ▲ on the top-left corner.
• You can go to the associated Inlet's or overcurrent protector's data pages by clicking the Inlet or Overcurrent Protector links in the Details section.

Outlet 1 Details Label 1 Outlet Status on Receptacle Type IEC 60320 C19 Lines L1-NEUTRAL Inlet Inlet I1 Overcurrent Protector Overcurrent Protector C1

Detailed Information on Outlet Pages

Each outlet's data page has the Details section for showing general outlet information and Sensors section for showing the outlet sensor status.

Details section:

Field Description
Label The physical outlet number
Outlet Status	This information is only available on outlet-switching capable models.
	On or Off
Receptacle Type This outlet's receptacle type
Lines Lines associated with this outlet
Inlet	This information is useful when there are multiple inlets on your PDU.
	Inlet associated with this outlet
Overcurrent Protector	This information is available only when your PX2 has overcurrent protectors.
	Overcurrent protector associated with this outlet

▶ Sensors section:

• RMS current (A)
• RMS voltage (V)
  • Active power (W)
  • Active energy (Wh)
• Apparent power (VA)
• Power factor
  • Line frequency (Hz) -- model dependent

If any outlet sensor enters the alarmed state, it is highlighted in yellow or red. See Yellow- or Red-Highlighted Sensors (on page 163).

Power-Off Period Options for Individual Outlets

There are two options for setting the power-off period during the power cycle on each individual outlet's page. See Individual Outlet Pages (on page 129).

Option Function
PDU defined (xxx)	Follows the global power-off period setting, which is set on PDU (on page 107). The value xxx in parentheses is the current global value.
Customized time	If selecting this option, do either of the following:Click to select an existing time option.Type a new value with an appropriate time unit added. See Time Units (on page 112).

Outlet Groups

Only PDUs with outlet-switching and/or outlet-metering feature show this menu item.

Choose Outlet Groups in the Menu(on page 92). The following Outlet Groups page opens.

Outlet Groups

+ Add group

☑ :

No groups were created yet.

▶ Required permissions:

You must have one of the permissions below to be able to operate all or some of the outlet group features.

• Administrator Privileges -- all operations
• Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration -- creating, editing and deleting outlet groups
• Switch Outlet Group -- powering on, off or cycle outlet groups

▶ Outlet group operations:

You can group one or multiple outlets on this page using

+ Add group

. See Creating an Outlet Group (on page 137).

The Outlet Groups page will list all outlet groups you create.

Outlet Groups
#▲	Name	Outlet State	Active Power	Outlets
1	Outlet group 1	2 on	0 W	1-2
2	Outlet group 2	1 on, 2 off	0 W	1 and 3-4
3	Outlet group 3	1 on, 3 off	0 W	1, 3 and 5-6

Then you can perform one of the following actions on one or multiple outlet groups:

• Power on, off or cycle the selected group(s). See Outlet Group Power Control(on page 138).
• Observe the power status of each outlet group and/or power status of each member outlet.
• Re-name a group or change its member outlets. See Modifying an Outlet Group (on page 143).

- Observe or monitor the following group sensors.

• A group's active power: sum of all member outlets' active power values.
• A group's active energy: sum of increments of all member outlets' active energy values. The initial value is zero when a group is created. Removal of any member outlet will NOT cause its group's active energy value to decrease.

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

• Reset the active energy values of the selected group(s). See Resetting a Group's Active Energy (on page 141).
• Enable and set up the thresholds of a group's sensor(s) so that the PDU can display an alarm when a threshold is reached or crossed. See Modifying an Outlet Group (on page 143).

Creating an Outlet Group

You can create an outlet group if you often have to perform the same action on the same outlets at a regular interval.

For example, create an outlet group when you need to:

• Power cycle specific outlets every week.
• Sum up and track specific outlets' active power values every month.
- Sum up the increased values of specific outlet's active energy values every month.

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

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

• Administrator Privileges

• Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration
  To create an outlet group:

• Click

1. Type the group name.

New Outlet Group Group name required Selected Member outlets Available -- Select an item -- Please select at least one item. Select All Deselect All Cancel ✓Save

1. Select the outlets you want in the Available field.

- To select all outlets of the PDU, click Select All.

1. To delete any selected outlet(s), select an outlet's ✗ in the Selected field.

- To remove all selected outlets, click Deselect All.

1. Click Save.

Tip: PX2 allows you to assign the same name to diverse outlet groups. If this really occurs, you still can identify different groups through their unique index numbers.

Outlet Group Power Control

You must have either permission below to power control any outlet groups.

• Administrator Privileges
• Switch Outlet Group

You can switch one or multiple outlet groups at a time on the Outlet Groups page.

To switch one single outlet group only, there are two methods -- either the Outlet Groups page or individual group page.

To switch one or multiple groups on the Outlet Groups page:

This method allows you to switch more than one outlet group simultaneously.

1. Click ☑ to make checkboxes appear in front of outlet groups.

Tip: To perform the desired action on only one outlet group, you can simply click that group without making the checkboxes appear.

2. Select multiple outlet groups.

- To select ALL outlet groups, select the topmost checkbox in the header row.

▲ Name

1 Outlet group 1 2 Outlet group 2 3 Outlet group 3

3. Click the desired button.

Button/command Action
	Power ON.
	Power OFF.
	Power cycle.▪ Power cycling the outlet(s) turns the outlet(s) off and then back on.

Confirm the operation when prompted.

4. Verify that the outlet-switching result on the Outlet State column of the Outlet Groups page.

- For example, if a group's Outlet State reads "1 on, 2 off", it means there are 3 outlets in total, and one of the outlets is turned ON, and two of the outlets are turned OFF.

- For detailed information about which outlets are turned on and which are turned off, you can open that outlet group's page by clicking on its name.

Outlet Groups

#▲	Name	Outlet State
1	Outlet group 1	2 on
2	Outlet group 2	1 on, 2 off
3	Outlet group 3	1 on, 3 off

To switch one group on a specific outlet group's page:

This method allows you to switch ONLY one outlet group at a time.

1. Open a specific outlet group's page by clicking on its name.

Outlet Groups

#▲	Name
1	Outlet group 1
2	Outlet group 2
3	Outlet group 3

1. Click the desired power control button on the top-right corner.

- Confirm the operation when prompted.

# ▲	Outlet	Status	Active Power
1	Outlet 1	on	0 W
2	Outlet 2	on	0 W

If Switchable Outlet Groups are Limited

For the Switch Outlet Group permission, if you assign a role to the user, which permits the user to switch only "specific" outlet groups instead of all outlet groups, the following switching issue may appear.

Issue:

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

Solution:

1. Edit the role assigned to the user. See Editing or Deleting Roles (on page 201).
2. Find the Switch Outlet Group permission, and re-select that outlet group in its outlet group list.

Note: The above issue does not occur for any role which has "All Outlet Groups" selected for its Switch Outlet Group permission.

Resetting a Group's Active Energy

An outlet group's active energy is the sum of increments of all member outlets' active energy values. For detailed information, see Outlet Groups (on page 136).

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

A group's active energy decreases to zero when it is reset.

• You can reset the active energy sensor(s) of one or multiple outlet groups at a time on the Outlet Groups page.
• To reset a single outlet group's active energy sensor, there are two methods -- either Outlet Groups page or individual group page.
• Resetting an outlet group's active energy has NO impact on any member outlet's active energy so all member outlets' active energy values remain unchanged.

It requires the Administrator Privileges to reset any outlet group's active energy.

To reset the active energy of one or multiple groups on the Outlet Groups page:

This method allows you to reset the active energy of more than one outlet group simultaneously.

1. Click ☑ to make checkboxes appear in front of outlet groups.

Tip: To perform the desired action on only one outlet group, you can simply click that group without making the checkboxes appear.

1. Select multiple outlet groups.

- To select ALL outlet groups, select the topmost checkbox in the header row.

▲ Name

1 Outlet group 1 2 Outlet group 2 3 Outlet group 3

1. Click : > Reset Energy Counter.

- Confirm the operation when prompted.

To reset one group's active energy on a specific outlet group's page:

This method allows you to reset the active energy of ONLY one outlet group at a time.

1. Open a specific outlet group's page by clicking on its name.

Outlet Groups
# ▲	Name
1	Outlet group 1
2	Outlet group 2
3	Outlet group 3

1. Click Reset in the Settings section.

- Confirm the operation when prompted.

Settings Edit Settings Name outlet group 1 Reset energy counter Reset

Note: The energy reset feature on the PDU page resets active energy of "outlets" and/or "inlet(s)" only. It does NOT reset outlet groups' active energy values. See PDU (on page 107).

Modifying an Outlet Group

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

• Administrator Privileges
• Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration

You can do the following on an individual outlet group's page:

• Change its member outlets
• Modify its group name
• Observe its group sensors' values and states

■ Active power: sum of all member outlets' active power values.
■ Active energy: sum of increments of all member outlets' active energy values.

For detailed information on the two group sensors, see Outlet Groups (on page 136).

• View the group's active power chart
- Configure the thresholds of its group sensors

To open any outlet group's page, click on its name on the Outlet Groups page.

Outlet Groups
#▲	Name
1	Outlet group 1
2	Outlet group 2
3	Outlet group 3

To modify the member outlets:

1. Click Edit Members.

Outlets
			Edit Members
#▲	Outlet	Status	Active Power
1	Outlet 1	on	0 W
2	Outlet 2	on	0 W

1. Add or remove outlets of this group.

2. To select any outlet(s), select them one by one from the Available list.
   ■ To select all available outlets, click Select All.

3. To remove any outlet(s) from the Selected field, click that outlet's ✗.
   ■ To remove all outlets, click Deselect All.

Outlets Member outlets Selected Outlet 1 × Outlet 2 × Available – Select an item – Select All Deselect All Cancel Save

1. Click Save.

To change the group name:

1. Click Edit Settings.

Settings Edit Settings Name Outlet group 1

1. Type a new name.
2. Click Save.

Tip: PX2 allows you to assign the same name to diverse outlet groups. If this really occurs, you still can identify different groups through their unique index numbers.

To configure the thresholds of group sensors:

1. Click the Thresholds title bar at the bottom of the page to display thresholds.

Thresholds

1. Click the desired sensor (required), and then click Edit Thresholds.

Thresholds Edit Thresholds Sensor ▲ Lower Critical Lower Warning Upper Warning Upper Critical Active Energy --- --- --- --- Active Power --- --- --- ---

1. Make changes as needed.

2. To enable any threshold, select the corresponding checkbox.

3. Type a new value in the accompanying text box.

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

1. Click Save.

Deleting an Outlet Group

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

• Administrator Privileges
• Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration

You can delete one or multiple outlet groups at a time.

To delete a single outlet group only, there are two methods -- either Outlet Groups page or individual group page.

To delete one or multiple groups on the Outlet Groups page:

This method allows you to delete more than one outlet group.

1. Click ☑ to make checkboxes appear in front of outlet groups.

Tip: To perform the desired action on only one outlet group, you can simply click that group without making the checkboxes appear.

1. Select multiple outlet groups.
2. To select ALL outlet groups, select the topmost checkbox in the header row.

▲ Name

1 Outlet group 1 2 Outlet group 2 3 Outlet group 3

1. Click : > Delete.

- Confirm the operation when prompted.

To delete a group on a specific outlet group's page:

This method allows you to delete ONLY one outlet group at a time.

1. Open a specific outlet group's page by clicking on its name.

Outlet Groups

# ▲

Name

1

Outlet group 1

2

Outlet group 2

3

Outlet group 3

1. Click : > Delete.

- Confirm the operation when prompted.

Viewing More Information

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

To observe an outlet group's active power chart:

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

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

To visit a member outlet's page from the current page:
- On an outlet group's individual page, you can go to a member outlet's page easily. Just click the outlet links in the Outlets section.

Outlet Group 1 - Outlet group 1 On Off Cycle Outlets Edit Members #▲ Outlet Status Active Power 1 Outlet 1 on 0 W 2 Outlet 2 on 0 W

To visit a different outlet group's page from the current page:
- On an outlet group's individual page, you can go to another outlet group's page easily. Just click the outlet selector ▲ on the top-left corner.

Outlet Group 1 - Outlet group 1 On Off Cycle Outlets Edit Members #▲ Outlet Status Active Power 1 Outlet 1 on 0 W 2 Outlet 2 on 0 W

OCPs

The OCPs page is available only when your PX2 has overcurrent protectors, such as circuit breakers.

The OCPs page lists all overcurrent protectors as well as their status. If any OCP trips or its current level enters the alarmed state, it is highlighted in red or yellow. See Yellow- or Red-Highlighted Sensors (on page 163).

To open the OCPs page, click 'OCPs' in the Menu (on page 92).

You can go to each OCP's data/setup page by clicking its name on this page.

Overcurrent Protector C1 Overcurrent Protector C2 Overcurrent Protector C3 Status Current

Overcurrent Protectors
# ▲	Name	Status		Current Drawn	Protected Outlets	Lines
1	Overcurrent Protector C1	closed	4.390 A		1-10	L1-L2
2	Overcurrent Protector C2	closed	5.619 A		11-20	L2-L3
3	Overcurrent Protector C3	closed	5.396 A		21-30	L3-L1

If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

▶ Overcurrent protector overview:

• OCP status - open (tripped) or closed
• Current drawn and current bar

The RMS current bars change colors to indicate the status if the OCP thresholds have been configured and enabled.

Status Bar colors
normal
above upper warning
above upper critical

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

• Protected outlets, which are indicated with outlet numbers
• Associated lines

To configure current thresholds for multiple overcurrent protectors:

OCP thresholds, when enabled, help you identify the OCP whose RMS current enters the warning or critical level with the yellow or red color. In addition, you can have PX2 automatically generate alert notifications for any warning or critical status. See Event Rules and Actions (on page 262).

Note: By default, upper thresholds of an OCP's RMS current have been configured. See Default Voltage and Current Thresholds (on page 711). You can modify them as needed.

1. Click : > Threshold Bulk Setup.
2. Select one or multiple OCPs.

- To select all OCPs, simply click the topmost checkbox in the header row.

OCP ▲ Overcurrent Protector C1 Overcurrent Protector C2

1. Click Edit Thresholds.
2. Make changes as needed.

■ To enable any threshold, select the corresponding checkbox.
- Type a new value in the accompanying text box.

Lower Critical 0 A Lower Warning 0 A Upper Warning 10.4 A Upper Critical 12.8 A Deassertion Hysteresis 1 A Assertion Timeout 0 Samples

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

1. Click Save.

Individual OCP Pages

An OCP's data/setup page is opened after clicking any OCP's name on the OCPs or Dashboard page. See OCPs (on page 149) or Dashboard (on page 97).

▶ General OCP information:

Field Description
Label This OCP's physical number.
Status open or closed.
Type This OCP's type.
Rating This OCP's rated current.
Lines Lines associated with this OCP.
Protected Outlets Outlets associated with this OCP.
Inlet Inlet associated with this OCP.
RMS current This OCP's current state and readings,including current drawn and currentremaining.

To customize this OCP's name:

1. Click Edit Settings.
2. Type a name.
3. Click Save.

To view this OCP's RMS current chart:

This OCP's data chart is shown in the Overcurrent Protector History section.

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

To configure this OCP's threshold settings:

By default, upper thresholds of an OCP's RMS current have been configured. See Default Voltage and Current Thresholds(on page 711). You can modify them as needed.

Note: The threshold values set for an individual OCP will override the bulk threshold values stored on that particular OCP. To configure thresholds for multiple OCPs at a time, see OCPs (on page 149).

1. Click the Thresholds title bar at the bottom of the page to display the threshold data.

Thresholds

1. Click the RMS current sensor (required), and then click Edit Thresholds.

Thresholds
				Edit Thresholds
Sensor ▲	Lower Critical	Lower Warning	Upper Warning	Upper Critical
RMS Current	-	-	10.4 A	12.8 A

1. Make changes as needed.

■ To enable any threshold, select the corresponding checkbox.
■ Type a new value in the accompanying text box.

Lower Critical 0 A Lower Warning 0 A Upper Warning 10.4 A Upper Critical 12.8 A Deassertion Hysteresis 1 A Assertion Timeout 0 Samples

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

1. Click Save.

▶ Other operations:

• You can go to another OCP's data/setup page by clicking the OCP selector □ on the top-left corner.
• You can go to the associated Inlet's data page by clicking the Inlet link in the Details section.

Overcurrent Protector C1

Details
Label	C1
Status	closed
Type	1-Pole Circuit Breaker
Rating	16 A
Lines	L1
Protected Outlets	1-4
Inlet	Inlet I1

Peripherals

If there are Raritan environmental sensor packages connected to the PX2, they are listed on the Peripherals page. See Connecting Raritan Environmental Sensor Packages (on page 33).

An environmental sensor package comprises one or some of the following sensors/actuators:

• Numeric sensors: Detectors that show both readings and states, such as temperature sensors.
• State sensors: Detectors that show states only, such as contact closure sensors.
• Actuators: An actuator controls a system or mechanism so it shows states only.

PX2 communicates with managed sensors/actuators only and retrieves their data. It does not communicate with unmanaged ones. See Managed vs Unmanaged Sensors/Actuators (on page 164).

When the number of "managed" sensors/actuators has not reached the maximum, PX2 automatically brings newly-detected sensors/actuators under management by default.

One PX2 can manage a maximum of 32 sensors/actuators.

Note: To disable the automatic management function, go to PDU (on page 107). You need to manually manage a sensor/actuator only when it is not under management.

When any sensor/actuator is no longer needed, you can unmanage/release it.

Open the Peripheral Devices page by clicking Peripherals in the Menu (on page 92). Then you can:

- Perfor rm actions on multiple sensors/actuators by using the control/action icons on the top-right corner.

Peripheral Devices
#▲	Name	Reading	State	Type	Serial Number	Position	Actuator
1	Temperature 1	24.0 °C	normal	Temperature	QMTemu0005	Port 1, Chain Position 5
2	Temperature 2	24.0 °C	normal	Temperature	QMSemu0004	Port 1, Chain Position 4
3	Relative Humidity 1	42 %	normal	Humidity	QMSemu0004	Port 1, Chain Position 4
4	On/Off 1		normal	Contact Closure	QU7emu0003	Port 1, Chain Position 3, Channel 1
5	On/Off 2		normal	Contact Closure	QU7emu0003	Port 1, Chain Position 3, Channel 2

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

Peripheral Devices

# ▲	Name
1	Temperature 1
2	Temperature 2
3	Relative Humidity 1
4	On/Off 1

If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

▶ Sensor/actuator overview on this page:

If any sensor enters an alarmed state, it is highlighted in yellow or red. See Yellow- or Red-Highlighted Sensors (on page 163). An actuator is never highlighted.

Column Description
Name By default the PX2 assigns a name comprising the following two elements to a newly-managed sensor/actuator.Sensor/actuator type, such as "Temperature" or "Dry Contact."Sequential number of the same sensor/actuator type, like 1, 2, 3 and so on.You can customize the name. See Individual Sensor/Actuator Pages (on page 171).
Reading Only managed 'numeric' sensors show this data, such as temperature and humidity sensors.
State The data is available for all sensors and actuators.See Sensor/Actuator States (on page 165).
Type Sensor or actuator type.
Serial Number	This is the serial number printed on the sensor package's label. It helps to identify your Raritan sensors/actuators. SeeFinding the Sensor's Serial Number(on page 166).
Position The data indicates where this sensor or actuator is located in the sensor chain.SeeIdentifying the Sensor Position and Channel (on page 167).
Actuator Indicates whether this sensor package is an actuator or not. If yes, the symbol √ is shown.

To release or manage sensors/actuators:

When the total of managed sensors/actuators reaches the maximum value (32), you cannot manage additional ones. The only way to manage any sensor/actuator is to release or replace the managed ones. To replace a managed sensor/actuator, see Managing One Sensor or Actuator (on page 170). To release any one, follow this procedure.

1. Click ☑ to make checkboxes appear in front of sensors/actuators.

Tip: To perform the desired action on only one sensor/actuator, simply click that sensor/actuator without making the checkboxes appear.

1. Select multiple sensors/actuators.

2. To release sensors/actuators, you must select "managed" ones only. See Sensor/Actuator States (on page 165).

3. To manage sensors/actuators, you must select "unmanaged" ones only.
4. To select ALL sensors/actuators, select the topmost checkbox in the header row.

Peripheral Devices ✓ # ▲ Name □ 1 Temperature 1 □ 2 Temperature 2 □ 3 Relative Humidity 1

1. To release selected ones, click : > Release.

To manage them, click > Manage.

- The management action triggers a "Manage peripheral device" dialog. Simply click Manage if you are managing multiple sensors/actuators.

Manage Peripheral Device Automatically assign a sensor number Manually select a sensor number Sensor 1 (unused) Cancel Manage

- If you are managing only one sensor/actuator, you can choose to assign an ID number by selecting "Manually select a sensor number." See Managing One Sensor or Actuator (on page 170).

1. Now released sensors/actuators become "unmanaged."

Managed ones show one of the managed states.

To configure sensor/actuator-related settings:

1. Click : > Peripheral Device Setup.

2. Now you can configure the fields.

3. Click ▼ to select an option.
   ■ Adjust the numeric values.

4. Select or deselect the checkbox.

Field Function Note
Peripheral device z coordinate format	Determines how to describe the vertical locations (Z coordinates) of Raritan environmental sensor packages.▪ Options: Rack-Units and Free-FormSee Z Coordinate Format(on page 177).	To specify the location of any sensor/actuators in the data center, see Individual Sensor/Actuator Pages(on page 171).
Peripheral device auto management	Enables or disables the automatic management feature for Raritan environmental sensor packages.▪ The default is to enable it.	See How the Automatic Management Function Works(on page 169).
Altitude Specifies the altitude of PX2 above sea level when a Raritan's DPX differential air pressure sensor is attached.▪ Range: -425 to 3000 meters (-1394 to 9842 feet)▪ Note that it can be a negative value down to -425 meters (-1394 feet) because some locations are below the sea level.	▪ The device's altitude is associated with the altitude correction factor. See Altitude Correction Factors (on page 713).▪ The d efault altitude measurement unit is meter. See Setting Default Measurement Units(on page 202).▪ You can have the measurement unit vary between meter and foot according to user credentials. See Setting Your Preferred Measurement Units(on page 202).
Active powered dry contact limit	Determines the maximum number of "active" powered dry contact actuators that is permitted concurrently.■ Range: 0 to 24	■ An "active" actuator is the one that is turned ON, or, if with a door handle connected, is OPENED.■ This setting only applies to "powered dry contact" (PD) actuators rather than normal "dry contact" actuators.■ You need either 'Change Peripheral Device Configuration' privilege or 'Administrator Privileges' to change its upper limit.■ To turn on/off the connected actuators, see Peripherals (on page 156).

1. Click Save.
2. To return to the sensor list on the Peripheral Devices page, click "Peripheral Devices" on the top.

Peripheral Devices | Setup

To configure default threshold settings:

Note that any changes made to default threshold settings not only re-determine the initial threshold values that will apply to newly-added sensors but also the threshold values of the already-managed sensors where default thresholds are being applied. See Individual Sensor/Actuator Pages (on page 171).

1. Click : > Default Threshold Setup.
2. Click the desired sensor type (required), and then click Edit Thresholds.

Peripherals Default Thresholds
				Edit Thresholds
Sensor Type	Lower Critical	Lower Warning	Upper Warning	Upper Critical
Absolute Humidity	2 g/m3	4 g/m3	20 g/m3	22 g/m3
Air Flow	0.4 m/s	0.8 m/s	2.6 m/s	3.2 m/s
Air Pressure	—	—	80 Pa	100 Pa
Relative Humidity	10 %	15 %	85 %	90 %
Temperature	10 °C	15 °C	30 °C	35 °C
Vibration	—	—	0.05 g	0.1 g

3. Make changes as needed.

■ To enable any threshold, select the corresponding checkbox.
■ Type a new value in the accompanying text box.

Lower Critical	✓ 10	°C
Lower Warning	✓ 15	°C
Upper Warning	✓ 30	°C
Upper Critical	✓ 35	°C
Deassertion Hysteresis	1	°C
Assertion Timeout	0	Samples

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

4. Click Save.

Tip: To customize the threshold settings on a per-sensor basis, go to Individual Sensor/Actuator Pages (on page 171).

To turn on or off any actuator(s):

1. Select one or multiple actuators which are in the same status-on or off.

- To select multiple actuators, click ✅ to make checkboxes appear and then select desired actuators.

1. Click the desired button.

Turn ON.

Turn OFF.

Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered dry contact" actuator can be turned on at the same time. To change this limitation of "powered dry contact" actuators, modify the active powered dry contact setting. See Peripherals (on page 156).

1. Confirm the operation when prompted.

Yellow- or Red-Highlighted Sensors

The PX2 highlights those sensors that enter the abnormal state with a yellow or red color. Note that numeric sensors can change colors only after you have enabled their thresholds.

Tip: When an actuator is turned ON, it is also highlighted in red for drawing attention.

For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

# ▲	Name	Reading	State	Type	Serial Number	Position	Actuator
1	Temperature 1	25.0 °C	above upper critical	Temperature	AEH2A51454	Port 1
2	Absolute Humidity 1	10.8 g/m3	normal	Absolute Humidity	AEI1750551	Port 4
3	Absolute Humidity 2	11.0 g/m3	above upper warning	Absolute Humidity	AEI2850240	Port 4
4	Temperature 2	25.8 °C	above upper critical	Temperature	AEI2A50775	Port 1
5	Relative Humidity 1	44 %	normal	Humidity	AEI2A50775	Port 1

In the following table, "R" represents any numeric sensor's reading. The symbol <= means "smaller than" or "equal to."

Sensor status	Color States shown in the interface		Description
Unknown		unavailable	Sensor state or readings cannot be detected.
		unmanaged Sensors are not being managed. See Managed vs Unmanaged Sensors/Actuators (on page 164).

Chapter 6: Using the Web Interface

Sensor status	Color States shown in the interface		Description
Normal		normal	Numeric or state sensors are within the normal range.-- OR --No thresholds have been enabled for numeric sensors.
Warning		above upper warning	Upper Warning threshold < "R" <= Upper Critical threshold
		below lower warning	Lower Critical threshold <= "R" < Lower Warning threshold
Critical		above upper critical	Upper Critical threshold < "R"
		below lower critical	"R" < Lower Critical threshold
Alarmed		alarmed State sensors enter the abnormal state.
OCP alarm		Open	Circuit breaker trips.-- OR --Fuse blown.

If you have connected a Schroff® LHX/SHX heat exchanger, when any sensor implemented on that device fails, it is also highlighted in red.

Managed vs Unmanaged Sensors/Actuators

To manually manage or unmanage/release a sensor or actuator, see Peripherals (on page 156).

▶ Managed sensors/actuators:

• PX2 communicates with managed sensors/actuators and retrieves their data.
• Managed sensors/actuators are always listed on the Peripheral Devices page no matter they are physically connected or not.
  • They have an ID number as illustrated below.

Peripheral Devices
# ▲	Name
1	On/Off 1
2	On/Off 2
3	Temperature 1
4	Absolute Humidity 1
5	Relative Humidity 1

• They show one of the managed states. See Sensor/Actuator States (on page 165).
• For managed 'numeric' sensors, their readings are retrieved and displayed. If any numeric sensor is disconnected or its reading cannot be retrieved, it shows "unavailable" for its reading.

▶ Unmanaged sensors/actuators:

• PX2 does NOT communicate with unmanaged sensors/actuators so their data is not retrieved.
• Unmanaged sensors/actuators are listed only when they are physically connected to PX2.

They disappear when they are no longer connected.

• They do not have an ID number.
• They show the "unmanaged" state.

Sensor/Actuator States

An environmental sensor or actuator shows its real-time state after being managed.

Available sensor states depend on the sensor type -- numeric or state sensors. For example, a contact closure sensor is a state sensor so it switches between three states only -- unavailable, alarmed and normal.

Sensors will be highlighted in yellow or red when they enter abnormal states. See Yellow- or Red-Highlighted Sensors (on page 163).

An actuator's state is marked in red when it is turned on.

▶ Managed sensor states:

In the following table, "R" represents any numeric sensor's reading. The symbol <= means "smaller than" or "equal to."

State Description
normal	For numeric sensors, it means the readings are within the normal range.For state sensors, it means they enter the normal state.
below lower critical "R"	< Lower Critical threshold
below lower warning Lower Critical threshold <= "R" < Lower Warning threshold
above upper warning Upper Warning threshold < "R" <= Upper Critical threshold
above upper critical Upper Critical threshold < "R"
alarmed The state sensor enters the abnormal state.
unavailable	The communication with the managed sensor is lost.-- OR --DPX2, DPX3, DX or DX2 sensor packages are upgrading their sensor firmware.

Note that for a contact closure sensor, the normal state depends on the normal setting you have configured. Refer to the Environmental Sensors and Actuators Guide (or Online Help) for detailed information, which is available on Raritan's Support page (http://www.raritan.com/support).

▶ Managed actuator states:

State Description
on The actuator is turned on.
off The actuator is turned off.
unavailable	The communication with the managed actuator is lost.-- OR --DX sensor packages are upgrading their sensor firmware.

▶ Unmanaged sensor/actuator states:

State Description

unmanaged Sensors or actuators are physically connected to the PX2 but not managed yet.

Note: Unmanaged sensors or actuators will disappear from the web interface after they are no longer physically connected to the PX2. To manage a sensor/actuator, go to Peripherals (on page 156).

Finding the Sensor's Serial Number

A DPX environmental sensor package includes a serial number tag on the sensor cable.

SN1: AHI8100078 SN2: AHI8100079 RoHS CE SN: AHI8100100 RoHS CE

A DPX2, DPX3, DX or DX2 sensor package has a serial number tag attached to its rear side.

Raritan. MIL KELIGHT SENSOR EX-40-04, Light Sensor 0045.06 PAN: 81-0233-540 Model: QL15740043 REV: 81-0233-540

The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the PX2. Match the serial number from the tag to those listed in the sensor table.

Peripheral Devices
#▲	Name	Reading	State	Type	Serial Number	Position	Actuator
1	On/Off 1		normal	Contact Closure	QLLemu0001	Port 1, Chain Position 1, Channel 1
2	On/Off 2		normal	Contact Closure	QLLemu0001	Port 1, Chain Position 1, Channel 3
3	Temperature 1	24.0 °C	normal	Temperature	QMTemu0005	Port 1, Chain Position 5
4	Absolute Humidity 1	9.2 g/m3	normal	Absolute Humidity	QMSemu0004	Port 1, Chain Position 4
5	Relative Humidity 1	42%	normal	Humidity	QMSemu0004	Port 1, Chain Position 4

Identifying the Sensor Position and Channel

Raritan has developed five types of environmental sensor packages - DPX, DPX2, DPX3, DX and DX2 series. Only DPX2, DPX3, DX and DX2 sensor packages can be daisy chained.

PX2 can indicate where each sensor or actuator is connected on the Peripheral Devices page.

Peripheral Devices
#▲	Name	Reading	State	Type	Serial Number	Position	Actuator
1	On/Off 1		normal	Contact Closure	QLLemu0001	Port 1, Chain Position 1, Channel 1
2	On/Off 2		normal	Contact Closure	QLLemu0001	Port 1, Chain Position 1, Channel 3
3	Temperature 1	24.0 °C	normal	Temperature	QMTemu0005	Port 1, Chain Position 5
4	Absolute Humidity 1	9.2 g/m3	normal	Absolute Humidity	QMSemu0004	Port 1, Chain Position 4
5	Relative Humidity 1	42 %	normal	Humidity	QMSemu0004	Port 1, Chain Position 4

- DPX series shows the sensor port number only.

For example, Port 1.

- DPX2, DPX3, DX and DX2 series show both the sensor port number and its position in a sensor chain.

For example, Port 1, Chain Position 2.

- If a Raritan DPX3-ENVHUB4 sensor hub is involved, the hub port information is also indicated for DPX2, DPX3, DX and DX2 series, but NOT indicated for DPX series.

For example, Hub Port 3.

- If a sensor/actuator contains channels, such as a contact closure sensor or dry contact actuator, the channel information is included in the position information.

For example, Channel 1.

▶ Sensor/actuator position examples:

Example Physical position
Port 1	Connected to the sensor port #1.
Port 1, Channel 2	• Connected to the sensor port #1.• The sensor/actuator is the 2nd channel of the sensor package.
Port 1, Chain Position 4	• Connected to the sensor port #1.• The sensor/actuator is located in the 4th sensor package of the sensor chain.
Port 1, Chain Position 3, Channel 2	• Connected to the sensor port #1.• The sensor/actuator is located in the 3rd sensor package of the sensor chain.• It is the 2nd channel of the sensor package.
Port 1, Chain Position 1, Hub Port 2, Chain Position 3	• Connected to the sensor port #1.• Connected to the 2nd port of the DPX3-ENVHUB4 sensor hub, which shows the following two pieces of information:• The hub's position in the sensor chain -- "Chain Position 1"• The hub port where this particular sensor package is connected -- "Hub Port 2"• The sensor/actuator is located in the 3rd sensor package of the sensor chain connected to the hub's port 2.

How the Automatic Management Function Works

This setting is configured on PDU (on page 107).

▶ After enabling the automatic management function:

When the total number of managed sensors and actuators has not reached the upper limit yet, PX2 automatically brings newly-connected environmental sensors and actuators under management after detecting them.

PX2 can manage up to 32 sensors/actuators.

▶ After disabling the automatic management function:

PX2 no longer automatically manages any newly-added environmental sensors and actuators, and therefore neither ID numbers are assigned nor sensor readings or states are available for newly-added ones.

You must manually manage new sensors/actuators. See Peripherals (on page 156).

Managing One Sensor or Actuator

If you are managing only one sensor or actuator, you can assign the desired ID number to it. Note that you cannot assign ID numbers when managing multiple sensors/actuators at a time.

Tip: When the total of managed sensors/actuators reaches the maximum value (32), you cannot manage additional ones. The only way to manage any sensor/actuator is to release or replace the managed ones. To replace a managed one, assign an ID number to it by following the procedure below. To release any one, see Peripherals (on page 156).

To manage only one sensor/actuator:

1. From the list of "unmanaged" sensors/actuators, click the one you want to manage.
2. The Manage Peripheral Device dialog appears.

Manage Peripheral Device Automatically assign a sensor number Manually select a sensor number Sensor 1 (unused) Cancel Manage

• To let PX2 randomly assign an ID number to it, select "Automatically assign a sensor number." This method does not release any managed sensor or actuator.
• To assign a desired ID number, select "Manually select a sensor number." Then click ▼ to select an ID number.

This method may release a managed sensor/actuator if the number you selected has been assigned to a specific sensor/actuator.

Tip: The information in parentheses following each ID number indicates whether the number has been assigned to a sensor or actuator. If it has been assigned to a sensor or actuator, it shows the sensor package's serial number. Otherwise, it shows the word "unused."

3. Click Manage.

▶ Special note for a Raritan humidity sensor:

A Raritan humidity sensor is able to provide two measurements - relative and absolute humidity values.

■ A relative humidity value is measured in percentage (%).
- An absolute humidity value is measured in grams per cubic meter (g/m ^3 ).

However, only relative humidity sensors are "automatically" managed if the automatic management function is enabled. You must "manually" manage absolute humidity sensors as needed.

Note that relative and absolute values of the same humidity sensor do NOT share the same ID number though they share the same serial number and position.

Peripheral Devices
#▲	Name	Reading	State	Type	Serial Number	Position
1	On/Off 1		normal	Contact Closure	QLLemu0001	Port 1, Chain Position 1, Channel 1
2	On/Off 2		normal	Contact Closure	QLLemu0001	Port 1, Chain Position 1, Channel 3
3	Relative Humidity 1	42%	normal	Humidity	QMSemu0004	Port 1, Chain Position 4
4	Absolute Humidity 1	9.2 g/m3	normal	Absolute Humidity	QMSemu0004	Port 1, Chain Position 4
5	Temperature 1	24.0 °C	normal	Temperature	QMSemu0004	Port 1, Chain Position 4

Individual Sensor/Actuator Pages

A sensor's or actuator's data/setup page is opened after clicking any sensor or actuator name on the Peripheral Devices page. See Peripherals (on page 156).

Note that only a numeric sensor has threshold settings, while a state sensor or actuator has no thresholds.

Threshold settings, if enabled, help you identify whether any numeric sensor enters the warning or critical level. See Yellow- or Red-Highlighted Sensors (on page 163). In addition, you can have PX2 automatically generate alert notifications for any warning or critical status. See Event Rules and Actions (on page 262).

To configure a numeric sensor's threshold settings:

1. Click Edit Thresholds.

Sensor
Reading	23.3 °C
State	normal
Last Time Changed	7/26/2017, 10:13:00 AM Eastern Daylight Time

Tip: The date and time shown on the PX2 web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of PX2 to your computer or mobile device.

2. Select or deselect Use Default Thresholds according to your needs.

Sensor Edit Thresholds Use Default Thresholds ✓ Lower Critical ✓ 10 °C Lower Warning ✓ 15 °C Upper Warning ✓ 57 °C Upper Critical ✓ 68 °C Deassertion Hysteresis 1 °C Assertion Timeout 0 Samples Cancel ✓ Save

- To have this sensor follow the default threshold settings configured for its own sensor type, select the Use Default Thresholds checkbox.

The default threshold settings are configured on the page of Peripherals (on page 156).

- To customize the threshold settings for this particular sensor, deselect the Use Default Thresholds checkbox, and then modify the threshold fields below it.

Note: For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 705).

1. Click Save.
   To set up a sensor's or actuator's physical location and additional settings:
2. Click Edit Settings.

Settings
Name	Temperature 1
Description
Location (X)
Location (Y)
Location (Z: Rack Units)

1. Make changes to available fields, and then click Save.

Fields Description
Name A name for the sensor or actuator.
Description Any descriptive text you want.
Location (X, Y and Z)	Describe the sensor's or actuator's location in the data center by typing alphanumeric values for the X, Y and Z coordinates. SeeSensor/Actuator Location Example(on page 177).If the term "Rack Units" appears in parentheses in the Z location, you must type an integer number. The Z coordinate's format is determined on the page ofPDU(on page 107).
Alarmed to Normal Delay	This field is available for the DX-PIR presence detector only.It determines the wait time before the PX2 announces that the presence detector is back to normal after it already returns to normal.Adjust the value in seconds.
Binary Sensor Subtype	This field is available for any Raritan contact closure sensor except for DX2-DH2C2's contact closure sensors.
	Determine the sensor type of your contact closure detector.Contact Closure detects the door lock or door open/closed status.Smoke Detection detects the appearance of smoke.Water Detection detects the appearance of water on the floor.Vibration detects the vibration of the floor.
Sensor Polarity	This field is available for DX2-CC2 contact closure sensors only.
	Determine the normal state of your DX2-CC2.Normal Open: The open status of the connected detector/switch is considered normal. An alarm is triggered when the detector/switch turns closed.Normal Closed: The closed status of the connected detector/switch is considered normal. An alarm is triggered when the detector/switch turns opened.

To view a numeric sensor's chart

This sensor's data within the past tens of minutes is shown in the chart. Note that only a numeric sensor has this diagram. State sensors and actuators do not have such data.

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

To turn on or off an actuator:
1. Click the desired control button.

Dry Contact 1 On Off Details Peripheral Device ID 7 Position Port 1, Chain Position 1 Serial Number QLLemu0001 Type Contact Closure (On/Off)

Turn ON.

: Turn OFF.

1. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on.

Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered dry contact" actuator can be turned on at the same time. To change this limitation of "powered dry contact" actuators, modify the active powered dry contact setting. See Peripherals (on page 156).

▶ Other operations:

You can go to another sensor's or actuator's data/setup page by clicking the selector ▼ on the top-left corner.

Details
Peripheral Device ID	1
Position	Port 1
Serial Number	AEH2A51454
Type	Temperature

Z Coordinate Format

Z coordinates refer to vertical locations of Raritan's environmental sensor packages. You can use either the number of rack units or a descriptive text to describe Z coordinates.

For a Z coordinate example, see Sensor/Actuator Location Example (on page 177).

To configure Z coordinates:

1. Determine the Z coordinate format on PDU (on page 107). Available Z coordinate formats include:

Format Description
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 or actuators.
Free-Form	Any alphanumeric string can be used for specifying the Z coordinate. The value comprises 0 to 24 characters.

1. Configure Z coordinates on the Individual Sensor/Actuator Pages (on page 171).

Sensor/Actuator Location Example

Use the X, Y and Z coordinates to describe each sensor's or actuator's physical location in the data center. See Individual Sensor/Actuator Pages (on page 171).

The X, Y and Z values act as additional attributes and are not tied to any specific measurement scheme. Therefore, you can use non-measurement values.

Example:

X = Brown Cabinet Row
Y = Third Rack
Z = Top of Cabinet 

Values of the X, Y and Z coordinates:

• X and Y: They can be any alphanumeric values comprising 0 to 24 characters.
• Z: When the Z coordinate format is set to Rack Units, it can be any number ranging from 0 to 60. When its format is set to Free-Form, it can be any alphanumeric value comprising 0 to 24 characters. See Peripherals (on page 156).

Feature Port

The FEATURE port supports connection to the following devices.

Device Description
Asset Strip Raritan asset strips
ExternalBeeper	An external beeper with the RJ-45 socket.
LHX 20 Schroff	^3 LHX-20 heat exchanger.
SHX 30 Schroff	^3 SHX-30 heat exchanger.
LHX 40 Schroff	^3 LHX-40 heat exchanger.
Power CIM This type represents one of the following Raritan products:Raritan power CIM, D2CIM-PWR. This CIM is used to connect the PX2 to the Raritan digital KVM switch -- Dominion KX II / III.Dominion KSX IIDominion SX or SX II

When the PX2 detects the connection of any listed device, it replaces 'Feature Port' in the menu with that device's name and shows that device's data/settings instead. See Asset Strip (on page 179), External Beeper (on page 187), Schroff LHX/SHX (on page 187) and Power CIM (on page 192).

When no devices are detected, the PX2 displays the name 'Feature Port' and the Feature Port page shows the message "No device is currently connected."

Open the Feature Port page by clicking it in the Menu(on page 92). From this page, you can enable or disable this port's detection capability, or force it to show a specific device's data/settings even though no device is detected.

Note: You must enable the LHX/SHX support for the PX2 to detect the presence of a supported Schroff® LHX/SHX heat exchanger. See Miscellaneous (on page 348).

To configure the feature port:

1. Click ⋮ on the top-right corner. The Feature Port Setup dialog appears.

Feature Port Setup Port: 1 Device Type: Asset Strip Detection Mode: Auto Cancel Save

1. Click the Detection Mode field, and select one mode.

Mode Description
Auto Enable the port to automatically detect the device connection.
Disabled	Disable the port's detection capability.
Asset Strip, Raritan asset strips, LHX 20, SHX 30, LHX 40, Power CIM	Force the PX2 to show the selected device's data/setup page regardless of the physical connection status.

Note: 'LHX 20', 'SHX 30', and 'LHX 40' are not available when the support of LHX/SHX heat exchangers is disabled. See Miscellaneous (on page 348).

Asset Strip

After connecting and detecting Raritan asset management strips (asset strips), the PX2 shows 'Asset Strip' in place of 'Feature Port' in the menu.

Note: For connection instructions, see Connecting Asset Management Strips (on page 53).

To open the Asset Strip page, click it in the Menu (on page 92). On this page, you can configure the rack units of asset strips and asset tags. A rack unit refers to a tag port on the asset strips. The "Change Asset Strip Configuration" permission is required.

For the functionality of this icon : on the top-right corner, see Feature Port [on page 178].

To configure asset strip and rack unit settings:

1. Click Edit Settings.

Settings
Name	Edit Settings
Number of Rack Units	48
Numbering Mode	Bottom-Up
Numbering Offset	1
Orientation	Bottom Connector

2. Make changes to the settings by directly typing a new value, or clicking that field to select a different option.

Field Description
Name Name for this asset strip assembly.
Number of Rack Units	Total of available tag ports on this asset strip assembly, ranging between 8 and 64.For the current generation of asset strips, which show the suffix "G3" on its hardware label, the PX2 automatically detects the number of its tag ports (rack units), and you cannot change this value.For old "non-G3" asset strips, there is no automatic detection for them so you must manually adjust this value.
Numbering Mode	The rack unit numbering method in a rack/cabinet.Top-Down: The numbering starts from the highest rack unit of a rack/cabinet.Bottom-Up: The numbering starts from the lowest rack unit of a rack/cabinet.
Numbering Offset	The start number in the rack unit numbering. For example, if this value is set to 3, then the first number is 3, the second number is 4, and so on.
Orientation The asset strip's orientation by indicating the location of its RJ-45 connector.Top Connector: The RJ-45 connector is located on the top.Bottom Connector: The RJ-45 connector is located on the bottom. Asset strips can detect their strip orientation and show it in this field. You need to adjust this value only when your asset strips are the oldest ones without tilt sensors implemented.
Color with connected tag	Click this field to determine the LED color denoting the presence of an asset tag.Default is green.
Color without connected tag	Click this field to determine the LED color denoting the absence of an asset tag.Default is red.

For color settings, there are two ways to set the color.

• Click a color in the color palette.

- Type the hexadecimal RGB value of the color, such as #00FF00.

Enter a color Color code #00FF00 Cancel Ok

1. Click Ok. The rack unit numbering and LED color settings are immediately updated on the Rack Units list illustrated below.

- The 'Index' number is the physical tag port number printed on the asset strip, which is not configurable. However, its order will change to reflect the latest rack unit numbering.

Rack unit ▲	Index	Slot	Name	Asset / ID	Operation Mode	LED Mode	Program Asset IDs LED Color
1	1			000015B914BB	Auto	On
2	2			000015B9152E	Auto	On
3	3			000015B9158C	Auto	On
4	4				Auto	On
5	5			000015B91600	Auto	On
6	6			000015B91546	Auto	On

• A blade extension strip and a programmable tag are marked with the word 'programmable' in the Asset/ID column. You can customize their Asset IDs. For instructions, refer to this section's last procedure below.
• If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

To customize a single rack unit's settings:

You can make a specific rack unit's LED behave differently from the others on the asset strip, including the LED light and color.

1. Click the desired rack unit on the Rack Units list. The setup dialog for the selected one appears.

Setup of Rack Unit 3 Name Operation Mode Auto (based on Tag) LED Mode On LED Color Cancel Save

1. Make changes to the information by typing a new value or clicking that field to select a different option.

Field Description
Name Name for this rack unit. For example, you can name it based on the associated IT device.
Operation Mode Determine whether this rack unit's LED behavior automatically changes according to the presence and absence of the asset tag. Auto: The LED behavior varies, based on the asset tag's presence. Manual Override: This option differentiates this rack unit's LED behavior.
LED Mode	This field is configurable only after the Operation Mode is set to Manual Override.
	Determine how the LED light behaves for this particular rack unit. On: The LED stays lit. Off: The LED stays off. Slow blinking: The LED blinks slowly. Fast blinking: The LED blinks quickly.
LED Color	This field is configurable only after the Operation Mode is set to Manual Override.
	Determine what LED color is shown for this rack unit if the LED is lit.

To expand a blade extension strip:

A blade extension strip, like an asset strip, has multiple tag ports. An extension strip is marked with a grayer color on the Asset Strip page, and its tag ports list is collapsed by default.

Note: If you need to temporarily disconnect the blade extension strip from the asset strip, wait at least 1 second before re-connecting it back, or the PX2 device may not detect it.

1. Locate the rack unit (tag port) where the blade extension strip is connected. Click its slot number, whose format is similar to

1-N ↗, where N is the total number of its tag ports.

Rack units Program Asset IDs
Rack unit ▲	Index	Slot	Name	Asset / ID	Operation Mode	LED Mode	LED Color
1	1			000015B914BB	Auto	On
2	2	1-16 ↗		0000ABC12345 (programmable)	Auto	On
3	3			000015B9152E	Auto	On
4	4				Auto	On

1. All tag ports of the blade extension strip are listed below it. Their port numbers are displayed in the Slot column.

Rack unit ▲	Index	Slot	Name	Asset / ID	Operation Mode	LED Mode	Program Asset IDs LED Color
1	1			000015B914BB	Auto	On
2	2	1-16✓		0000ABC12345 (programmable)	Auto	On
	Extension	1		000015B9160A
	Extension	2		000015B91610
	Extension	3		000015B91622
	Extension	4		000015B9158C
	Extension	5		000015B91600
	Extension	6		000015B91546
	Extension	7
	Extension	8
	Extension	9
	Extension	10
	Extension	11
	Extension	12
	Extension	13
	Extension	14
	Extension	15
	Extension	16
3	3			000015B9152E	Auto	On

- To hide the blade extension slots list, click

To customize asset IDs on programmable asset tags:

You can customize asset IDs only when the asset tags are "programmable" ones. Non-programmable tags do not support this feature. In addition, you can also customize the ID of a blade extension strip.

If a barcode reader is intended, connect it to the computer you use to access the PX2.

1. Click Program Asset IDs.

Rack Units							Program Asset IDs
Rack unit ▲	Index	Slot	Name	Asset / ID	Operation Mode	LED Mode	LED Color
1	16				Auto	On
2	15				Auto	On
3	14				Auto	On
4	13				Auto	On
5	12				Auto	On
6	11				Auto	On
7	10			(programmable)	Auto	On
8	9			(programmable)	Auto	On
9	8			(programmable)	Auto	On
10	7			00001492BD47	Auto	On
11	6			00001492CB50	Auto	On

2. In the Asset/ID column, enter the customized asset IDs by typing values or scanning the barcode.

• When using a barcode reader, first click the desired rack unit, and then scan the asset tag. Repeat this step for all desired rack units.
• An asset ID contains up to 12 characters that comprise only numbers and/or UPPER CASE alphabets. Lower case alphabets are NOT accepted.

Rack Units
				Rack Units
Rack unit ▲	Index	Slot	Name	Asset / ID
1	16			Tag ID
2	15			Tag ID
3	14			Tag ID
4	13			Tag ID
5	12			Tag ID
6	11			Tag ID
7	10			WINDOWS
8	9			LINUX
9	8			ROUTER| ×
10	7			00001492BD47

1. Verify the correctness of customized asset IDs and modify as needed.
2. Click Apply at the bottom of the page to save changes.

- Or click Cancel to abort changes.

Tip: Another way to abort changes is to click Rack Units. Refer to the diagram below.

Rack Units
				Rack Units
Rack unit ▲	Index	Slot	Name	Asset / ID
1	16			Tag ID
2	15			Tag ID

Asset Strip Automatic Firmware Upgrade

After connecting the asset strip to the PX2, it automatically checks its own firmware version against the version of the asset strip firmware stored in the PX2 firmware. If two versions are different, the asset strip automatically starts downloading the new firmware from the PX2 to upgrade its own firmware.

During the firmware upgrade, the following events take place:

• The asset strip is completely lit up, with the blinking LEDs cycling through diverse colors.
• A firmware upgrade process is indicated in the PX2 web interface.
  • An SNMP trap is sent to indicate the firmware upgrade event.

External Beeper

After connecting and detecting a supported external beeper, the PX2 shows 'External Beeper' in place of 'Feature Port' in the menu.

Note: For connection instructions, see Connecting an External Beeper (on page 67).

To open the External Beeper page, click it in the Menu (on page 92). This page shows an external beeper's status, including:

• Number of the FEATURE port where this external beeper is connected
• Its device type
• Its connection status
  • The beeper's state - off or active

For the functionality of this icon Port (on page 178).

on the top-right corner, see Feature

Schroff LHX/SHX

You must enable the LHX/SHX support for the PX2 to detect the presence of a supported Schroff® LHX/SHX heat exchanger. See Miscellaneous (on page 348).

After enabling the LHX/SHX support and connecting a supported Schroff® LHX/SHX heat exchanger to the PX2, the PX2 shows the connected device type in place of 'Feature Port' in the menu -- LHX 20, LHX 40 or SHX 30.

Note: For connection instructions, see Connecting a Schroff LHX/SHX Heat Exchanger (on page 67).

To open the LHX/SHX page, click 'LHX 20', 'LHX 40' or 'SHX 30' in the Menu (on page 92). Then you can monitor and administer the connected LHX/SHX device with the following.

• Name the heat exchanger
  • Monitor LHX/SHX built-in sensors and device states
• Configure the air outlet temperature setpoint
• Configure the default fan speed
• Configure the air temperature/fan speed thresholds (for alert generation)
• Request maximum cooling using the fan speed and opening the cold water valve
• Acknowledge alerts or errors remotely, such as failed LHX/SHX sensors or emergency cooling activation
  • Accumulative operating hours
• Indicate the number of power supplies present and whether a condenser pump is present

Available information/operation is model dependent. For example, only LHX devices can show sensor alerts. See your LHX/SHX user documentation for details.

Important: The LHX/SHX settings are stored on the port where the LHX/SHX device is connected, and are lost if that device is re-connected to a different PX2 port.

For the functionality of this icon on the top-right corner, see Port[on page 178].

To view the LHX/SHX device state:

The Operation State field indicates whether the device is operating fine, and the Switch State field indicates its power status.

If the device does not operate properly, such as some sensor failure, it shows "critical" and the symbol 🔊.

Operational State	critical
Switch State	On

To turn on or off the LHX/SHX device:

1. Click the desired power-control button on the top-right corner.

LHX 40 (1) On Off Information Schroff® Model LHX 40 Firmware Version 0x3d Operational State critical Switch State On

1. Confirm the operation on the confirmation message.

To configure LHX/SHX settings:

1. Click Edit Settings.

Settings
		Edit Settings
Name
Setpoint Air Outlet	20 °C
Default Fan Speed	80 %

1. Configure the settings as needed.

■ Provide a customized name.
- Specify the desired air outlet setpoint temperature.
■ Specify the default fan speed.

1. Click Save.

To view all sensor data and configure thresholds:

1. Locate the Sensors section, which lists all air outlet/inlet temperatures and fan speeds, and indicates the door closed/open status of the LHX/SHX device.
2. To set the thresholds for any temperature or fan speed sensor implemented on the LHX/SHX device:

a. Click the desired sensor.

b. Click Edit Thresholds.

Sensors
		Edit Thresholds
Name	Reading	Status
Temperature Air Outlet (F1)	19.9 °C	normal
Temperature Air Outlet (F2)	19.9 °C	normal
Temperature Air Inlet (F3)	25.9 °C	normal
Temperature Air Inlet (F4)	25.9 °C	normal
Temperature Water Inlet (F6)	26.6 °C	normal
Fan Speed (M1)	2844 rpm	normal
Fan Speed (M2)	3035 rpm	normal
Fan Speed (M3)	2837 rpm	normal
Fan Speed (M4)	3008 rpm	normal
Fan Speed (M5)	2682 rpm	normal
Fan Speed (M6)	2855 rpm	normal
Fan Speed (M7)	2907 rpm	normal
Door Contact	0	closed

c. Enable and set the desired thresholds and deassertion hysteresis.

Note that assertion timeout is NOT available on LHX/SHX.

d. Click Save.

1. After thresholds are enabled, sensors may be highlighted in yellow or red if they enter the warning or critical range. See Yellow- or Red-Highlighted Sensors(on page 163).

Tip: You can also create event rules to notify you of the warning or critical levels. See Event Rules and Actions (on page 262).

To view sensor alerts and LHX event log:

Remote alert acknowledgment is supported by the LHX-20 and LHX-40. The SHX-30 does not support this feature.

1. Locate the Alert States section.
2. If any LHX sensors fail, they are indicated. Click Acknowledge to acknowledge the sensor failure.

Alert States Fans M2, M4, M5 failure Acknowledge Alert Status Acknowledge Show Event Log

1. To view the history of LHX events, click Show Event Log to go to the Event Log page.

▶ Operation time statistics:

This section indicates the accumulative operation hours of the LHX/SHX device and its fans since the device is connected to the PX2 and turned on.

Available time units in the statistics --

• h: hour(s)
• d: day(s)

Statistics
Operating Hours (Varistar LHX)	7 h
Operating Hours (Fan 1)	6 h
Operating Hours (Fan 2)	6 h
Operating Hours (Fan 3)	6 h
Operating Hours (Fan 4)	3 h
Operating Hours (Fan 5)	3 h
Operating Hours (Fan 6)	0 h
Operating Hours (Fan 7)	0 h

Request maximum cooling:

Only SHX 30 supports this feature. See SHX Request Maximum Cooling (on page 192).

SHX Request Maximum Cooling

The PX2 allows you to remotely activate the Schroff SHX 30's maximum cooling feature. Both LHX 20 and LHX 40 do not support remote activation of maximum cooling.

The Request Maximum Cooling feature is available only after the PX2 detects SHX 30. For additional information on the SHX 30 maximum cooling feature, see the SHX 30 documentation.

▶ To perform maximum cooling:

• Go to the SHX page, and click Request Maximum Cooling.
  Then the SHX 30 enters into emergency cooling mode and runs at its maximum cooling level of 100% in order to cool the device.
  When maximum cooling is requested for an SHX 30, the message "Maximum cooling requested" is displayed.

To stop maximum cooling:

- Click Cancel Maximum Cooling.

Power CIM

After connecting and detecting a Raritan power CIM, the PX2 shows 'Power CIM' in place of 'Feature Port' in the menu. See Dominion KX II / III Configuration (on page 735) or Dominion KSX II, SX or SX II Configuration (on page 740).

Open the Power CIM page by clicking it in the Menu (on page 92). This page shows the CIM's status, including:

• Number of the FEATURE port where this CIM is connected
- Its device type
- Its connection status

For the functionality of this icon Port (on page 178).

on the top-right corner, see Feature

User Management

User Management menu deals with user accounts, permissions, and preferred measurement units on a per-user basis.

PX2 is shipped with one built-in administrator account: admin, which is ideal for initial login and system administration. You cannot delete 'admin' or change its permissions, but you can and should change its password.

A "role" determines the tasks/actions a user is permitted to perform on the PX2 so you must assign one or multiple roles to each user.

Click 'User Management' in the Menu (on page 92), and the following submenu displays.

User Management Users Roles Change Password User Preferences Default Preferences

Submenu command Refer to...
Users	Creating Users(on page 193)
Roles	Creating Roles(on page 199)
Change Password	Changing Your Password(on page 88)
User Preferences	Setting Your Preferred Measurement Units(on page 202)
Default Preferences	Setting Default Measurement Units(on page 202)

Creating Users

All users must have a user account, containing the login name and password. Multiple users can log in simultaneously using the same login name.

To add users, choose User Management > Users >

Users
Enabled ▲	User name	Full Name	Roles
√	admin	Administrator	Admin

Note that you must enter information in the fields showing the message 'required.'

required

▶ User information:

Field/setting Description
User Name The name the user enters to log in to the PX2.▪ 4 to 32 characters▪ Case sensitive▪ Spaces are NOT permitted.
Full Name The user's first and last names.
Password,Confirm Password	▪ 4 to 64 characters▪ Case sensitive▪ Spaces are permitted.
Telephone Number The user's telephone number
eMail Address The user's email address▪ Up to 128 characters▪ Case sensitive
Enable When selected, the user can log in to the PX2.
Force password change on next login	When selected, a password change request automatically appears when next time the user logs in.For details, seeChanging Your Password(on page 88).

SSH:

You need to enter the SSH public key only if the public key authentication for SSH is enabled. See Changing SSH Settings (on page 232).

1. Open the SSH public key with a text editor.

2. Copy and paste all content in the text editor into the SSH Public Key field.

SNMPv3:

The SNMPv3 access permission is disabled by default.

Field/setting Description
Enable SNMPv3	Select this checkbox when intending to permit the SNMPv3 access by this user.
	Note: The SNMPv3 protocol must be enabled for SNMPv3 access. See Configuring SNMP Settings (on page 228).
Security Level Click	the field to select a preferred security level from the list:None: No authentication and no privacy. This is the default.Authentication: Authentication and no privacy.Authentication & Privacy: Authentication and privacy.

- Authentication Password: This section is configurable only when 'Authentication' or 'Authentication & Privacy' is selected.

Field/setting Description
Same as User Password	Select this checkbox if the authentication password is identical to the user's password.To specify a different authentication password, disable the checkbox.
Password, Confirm Password	Type the authentication password if the 'Same as User Password' checkbox is deselected.The password must consist of 8 to 32 ASCII printable characters.

- Privacy Password: This section is configurable only when 'Authentication & Privacy' is selected.

Field/setting Description
Same as Authentication Password	Select this checkbox if the privacy password is identical to the authentication password.To specify a different privacy password, disable the checkbox.

Field/setting Description

Password, Confirm Password

Type the privacy password if the 'Same as Authentication Password' checkbox is deselected. The password must consist of 8 to 32 ASCII printable characters.

- Protocol: This section is configurable only when 'Authentication' or 'Authentication & Privacy' is selected.

Field/setting Description

Authentication Click this field to select the desired authentication protocol. Two protocols are available:MD5SHA-1 (default)

Privacy Click this field to select the desired privacy protocol. Two protocols are available:DES (default)AES-128

Preferences:

This section determines the measurement units displayed in the web interface and command line interface for this user.

Field Description
Temperature Unit	Preferred units for temperatures -- °C (Celsius) or °F (Fahrenheit).
Length Unit Preferred units for length or height -- Meter or Feet.
Pressure Unit Preferred units for pressure -- Pascal or Psi.▪ Pascal = one newton per square meter▪ Psi = pounds per square inch

Note: Users can change the measurement units at any time by setting their own preferences. See Setting Your Preferred Measurement Units (on page 202).

Roles:

Select one or multiple roles to determine the user's permissions.

To select all roles, select the topmost checkbox in the header row.

However, a user can have a maximum of 32 roles only.

If the built-in roles do not satisfy your needs, add new roles by clicking

+ New Role

This newly-created role will be then automatically

assigned to the user account currently being created. See Creating Roles (on page 199).

Built-in role Description
Admin Provide full permissions.
Operator Provide frequently-used permissions, including:
	Acknowledge AlarmsChange Own PasswordChange Pdu, Inlet, Outlet & Overcurrent Protector ConfigurationSwitch Outlet (if your PX2 is outlet-switching capable)View Event SettingsView Local Event Log

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

Editing or Deleting Users

To edit or delete users, choose User Management > Users to open the Users page, which lists all users.

Users
Enabled	User name ▲	Full Name	Roles
✓	admin	Administrator	Admin
×	John		Operator
✓	Mary		Operator
✓	Teresa		Admin

In the Enabled column:

• : The user is enabled.
• ✗: The user is disabled.

If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

To edit or delete a user account:

1. On the Users page, click the desired user. The Edit User page for that user opens.

2. Make changes as needed.

3. For information on each field, see Creating Users (on page 193).

4. To change the password, type a new password in the Password and Confirm Password fields. If the password field is left blank, the password remains unchanged.

- To delete this user, click 🔒, and confirm the operation.

Edit User - John User User Name John Full Name Password

1. Click Save.

To delete multiple user accounts:

1. On the Users page, click user names.

to make checkboxes appear in front of

Tip: To delete only one user, you can simply click that user without making the checkboxes appear. Refer to the above procedure.

1. Select one or multiple users.

- To select all roles, except for the admin user, select the topmost checkbox in the header row.

1. Click

Users Enabled User name ▲ Full Name Roles ✓ admin Administrator Admin ✓ ✗ John Operator ✓ Mary Operator ✓ Teresa Admin

1. Click Delete on the confirmation message.

Creating Roles

A role is a combination of permissions. Each user must have at least one role.

The PX2 provides two built-in roles.

Built-in role Description

Admin Provide full permissions.

Operator Provide frequently-used permissions, including:

Acknowledge Alarms Change Own Password Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration Switch Outlet (if your PX2 is outlet-switching capable) View Event Settings View Local Event Log

If the two do not satisfy your needs, add new roles. PX2 supports up to 64 roles.

To create a role:

1. Choose User Management > Roles >

Roles
Role Name ▲	Description
Admin	System defined administrator role including all privileges.
Operator	Predefined operator role.

1. Assign a role name.

■ 1 to 32 characters long
- Case sensitive
■ Spaces are permitted

1. Type a description for the role in the Description field.
2. Select the desired privilege(s).

■ The 'Administrator Privileges' includes all privileges.

The 'Unrestricted View Privileges' includes all 'View' privileges.

1. If any privilege requires the argument setting, the symbol displays in the rightmost edge of that privilege's row. To select such a privilege:

a. Click on that privilege's row to display a list of available arguments for that privilege.
b. Select the desired arguments.

- To select all arguments, simply select the checkbox labeled 'ALL XXX'.

Tip: The other way to select all arguments is to select that privilege's checkbox while the arguments list is not expanded yet.

For example, on an outlet-switching capable model, you can specify the outlets that users can switch on/off as shown below. To select all outlets, select the 'All Outlets' checkbox instead.

Switch Outlet 2-4 and 7 All Outlets Outlet 1 ✓ Outlet 2 ✓ Outlet 3 ✓ Outlet 4 Outlet 5 Outlet 6 ✓ Outlet 7 Outlet 8

1. Click Save.

Now you can assign the role to any user. See Creating Users (on page 193) or Editing or Deleting Users (on page 197).

Editing or Deleting Roles

Choose User Management > Roles to open the Roles page, which lists all roles.

If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

Roles
Role Name ▲	Description
Admin	System defined administrator role including all privileges.
Manager	Able to change all settings except for security settings
Operator	Predefined operator role.

The Admin role is not user-configurable so the lock icon 📄 displays, indicating that you are not allowed to configure it.

To edit a role:

1. On the Roles page, click the desired role. The Edit Role page opens.
2. Make changes as needed.

■ The role name cannot be changed.
- To delete this role, click 📄, and confirm the operation.

Edit Role - Manager Settings Role Name Manager Description Able to change all settings except for security settings

1. Click Save.

To delete any roles:

1. On the Roles page, click roles.

to make checkboxes appear in front of

Tip: To delete only one role, you can simply click that role without making the checkboxes appear. Refer to the above procedure.

1. Select one or multiple roles.

- To select all roles, except for the Admin role, select the topmost checkbox in the header row.

1. Click 📄 on the top-right corner.
2. Click Delete on the confirmation message.

Setting Your Preferred Measurement Units

You can change the measurement units shown in the PX2 user interface according to your own preferences regardless of the permissions you have.

Tip: Preferences can also be changed by administrators for specific users on the Edit User page. See Editing or Deleting Users (on page 197).

Measurement unit changes only apply to the web interface and command line interface.

Setting your own preferences does not change the default measurement units. See Setting Default Measurement Units (on page 202).

To select the measurement units you prefer:

1. Choose User Management > User Preferences.
2. Make changes as needed.

Field Description
Temperature Unit	Preferred units for temperatures -- °C (Celsius) or °F (Fahrenheit).
Length Unit Preferred	units for length or height -- Meter or Feet.
Pressure Unit Preferred	units for pressure -- Pascal or Psi.Pascal = one newton per square meterPsi = pounds per square inch

1. Click Save.

Setting Default Measurement Units

Default measurement units are applied to all PX2 user interfaces across all users, including users accessing the PX2 via external authentication servers.

For a list of affected user interfaces, see User Interfaces Showing Default Units (on page 203).

Note: The preferred measurement units set by any individual user or by the administrator on a per-user basis will override the default units in the web interface and command line interface. SeeSetting Your Preferred Measurement Units (on page 202) or Creating Users (on page 193).

To set up default user preferences:

1. Click User Management > Default Preferences.
2. Make changes as needed.

Field Description
Temperature Unit	Preferred units for temperatures -- °C (Celsius) or °F (Fahrenheit).
Length Unit Preferred	units for length or height -- Meter or Feet.
Pressure Unit Preferred	units for pressure -- Pascal or Psi.Pascal = one newton per square meterPsi = pounds per square inch

3. Click Save.

User Interfaces Showing Default Units

Default measurement units will apply to the following user interfaces or data:

• Web interface for "newly-created" local users when they have not configured their own preferred measurement units. See Creating Users (on page 193).
• Web interface for users who are authenticated via LDAP/Radius servers.
• The sensor report triggered by the "Send Sensor Report" action. See Send Sensor Report (on page 294).

Device Settings

Click 'Device Settings' in the Menu(on page 92), and the following submenu displays.

Chapter 6: Using the Web Interface

Device Settings
Network
Network Services	>
Security	>
Date/Time
Event Rules
Data Logging
Data Push
Server Reachability
Front Panel
Serial Port
Lua Scripts
Miscellaneous

Menu command Submenu command Refer to...
Network		Configuring Network Settings (on page 205)
Network Services	HTTP	Changing HTTP(S) Settings (on page 228)
	SNMP	Configuring SNMP Settings (on page 228)
	SMTP Server	Configuring SMTP Settings (on page 230)
	SSH	Changing SSH Settings (on page 232)
	Telnet	Changing Telnet Settings (on page 233)

Menu command Submenu command Refer to...

	Modbus	Changing Modbus Settings (on page 233)
	Server Advertising	Enabling Service Advertising (on page 233)
Security	IP Access Control	Creating IP Access Control Rules (on page 235)
	Role Based Access Control	Creating Role Based Access Control Rules (on page 239)
	SSL Certificate	Setting Up an SSL/TLS Certificate (on page 242)
	Authentication	Setting Up External Authentication (on page 247)
	Login Settings	Configuring Login Settings (on page 255)
	Password Policy	Configuring Password Policy (on page 256)
	Service Agreement	Enabling the Restricted Service Agreement (on page 257)
Date/Time		Setting the Date and Time (on page 258)
Event Rules		Event Rules and Actions (on page 262)
Data Logging		Setting Data Logging (on page 322)
Data Push		Configuring Data Push Settings (on page 323)
Server Reachability		Monitoring Server Accessibility (on page 331)
Front Panel*		Front Panel Settings (on page 340)
Serial Port		Configuring the Serial Port (on page 340)
Lua Scripts		Lua Scripts (on page 342)
Miscellaneous		Miscellaneous (on page 348)

* The availability of "Front Panel" is model dependent.

Configuring Network Settings

Configure wired, wireless, and Internet protocol-related settings on the Network page after connecting the PX2 to your network (on page 17).

You can enable both the wired and wireless networking on PX2 so that it has multiple IP addresses -- wired and wireless IP. For example, you can obtain one IPv4 and/or IPv6 address by enabling one Ethernet interface, and obtain one more IPv4 and/or IPv6 address by enabling/configuring the wireless interface. This also applies when PX2 enters the port forwarding mode so that PX2 has more than one IPv4 or IPv6 address in the port forwarding mode.

However, PX2 in the BRIDGING mode obtains "only one" IP address for wired networking. Wireless networking is NOT supported in this mode.

Important: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

To set up the network settings:

1. Choose Device Settings > Network.

2. To use DHCP-assigned DNS servers and gateway instead of static ones, go to step 3. To manually specify DNS servers and default gateway, configure the Common Network Settings section. See Common Network Settings (on page 208).

■ Static routes and cascading mode are also in this section. You need to configure them only when there are such local requirements. See Setting the Cascading Mode (on page 218) and Static Route Examples (on page 214).

1. To configure IPv4/IPv6 settings for a wired network, click the ETHERNET or BRIDGE section. See Wired Network Settings (on page 207).

- If the device's cascading mode is set to 'Bridging', the BRIDGE section appears. Then you must click the BRIDGE section for IPv4/IPv6 settings.

1. To configure IPv4/IPv6 settings for a wireless network, click the WIRELESS section. See Wireless Network Settings (on page 210).

- You must connect a USB wireless LAN adapter to the PX2 for wireless networking.

Note: If the device's cascading mode is set to 'Bridging' or its role is set to 'Slave' in the port forwarding mode, the wireless settings will be disabled.

1. To configure the ETHERNET interface settings, see Ethernet Interface Settings(on page 209).

2. Click Save.

▶ After enabling either or both Internet protocols:

After enabling IPv4 and/or IPv6, all but not limited to the following protocols will be compliant with the selected Internet protocol(s):

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

Note: As of release 3.5.0, PX2 disables TLS1.0 and 1.1 by default. It enables only TLS 1.2 and 1.3.

Wired Network Settings

On the Network page, click the ETHERNET section to configure IPv4/IPv6 settings.

If the device's cascading mode is set to 'Bridging', the BRIDGE section appears. Then you must click the BRIDGE section for IPv4/IPv6 settings. See Setting the Cascading Mode (on page 218).

▶ Enable Interface:

Make sure the Ethernet interface is enabled, or all networking through this interface fails. This setting is available in the ETHERNET section, but not available in the BRIDGE section.

Enable Interface

IPv4 settings:

Field/setting Description

Enable IPv4 Enable or disable the IPv4 protocol.

IP Auto Configuration

Select the method to configure IPv4 settings.

• DHCP: Auto-configure IPv4 settings via DHCP servers.
  ■ Static: Manually configure the IPv4 settings.

- DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements:

■ Consists of alphanumeric characters and/or hyphens
- Cannot begin or end with a hyphen
- Cannot contain more than 63 characters

- Cannot contain punctuation marks, spaces, and other symbols

- Static settings: Assign a static IPv4 address, which follows this syntax "IP address/prefix length".

Example: 192.168.84.99/24

IPv6 settings:

Field/setting Description

Enable IPv6 Enable or disable the IPv6 protocol.

IP Auto

Configuration

Select the method to configure IPv6 settings.

■ Automatic: Auto-configure IPv6 settings via DHCPv6.

■ Static: Manually configure the IPv6 settings.

- Automatic settings: Optionally specify the preferred hostname, which must meet the above requirements.

- Static settings: Assign a static IPv6 address, which follows this syntax "IP address/prefix length".

Example: fd07:2fa:6cff:1111::0/128

Common Network Settings

Common Network Settings are OPTIONAL, not required. Therefore, leave them unchanged if there are no specific local networking requirements.

Field Description
Cascading Mode Leave it to the default "None" unless you are establishing a cascading chain.For more information, refer to:▪ Cascading Multiple PX2 Devices for Sharing Ethernet Connectivity(on page 28)▪ Setting the Cascading Mode(on page 218)
DNS Resolver Reference	Determine which IP address is used when the DNS resolver returns both IPv4 and IPv6 addresses.▪ IPv4 Address: Use the IPv4 addresses.▪ IPv6 Address: Use the IPv6 addresses.
DNS Suffixes (optional)	Specify a DNS suffix name if needed.
First/Second/Third DNS Server	Manually specify static DNS server(s).If any static DNS server is specified in these fields, it will override the DHCP-assigned DNS server.If DHCP (or Automatic) is selected for IPv4/IPv6 settings, and there are NO static DNS servers specified, the PX2 will use DHCP-assigned DNS servers.
IPv4/IPv6 Routes You need to configure these settings only when your local network contains two subnets, and you want PX2 to communicate with the other subnet. If so, make sure IP forwarding has been enabled in your network, and then you can click 'Add Route' to add static routes.See Static Route Examples (on page 214).

Ethernet Interface Settings

By default the Ethernet interface is enabled.

▶ Enable Interface:

Make sure the Ethernet interface is enabled, or all networking through this interface fails. This setting is available in the ETHERNET section, but not available in the BRIDGE section.

Enable Interface

▶ Other Ethernet settings:

Field Description
Speed Select a LAN	speed.
	• Auto: System determines the optimum LAN speed through auto-negotiation.
	• 10 MBit/s: Speed is always 10 Mbps.
	• 100 MBit/s: Speed is always 100 Mbps.
	• 1 GBit/s: Speed is always 1 Gbps (1000 Mbps).Available only for specific PX2 models with the suffix "-G1".
Duplex Select a duplex mode.	• Auto: The PX2 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 PX2) at a time.
Current State	Show the LAN's current status, including the current speed and duplex mode.

Note: Auto-negotiation is disabled after setting both the speed and duplex settings of the PX2 to NON-Auto values, which may result in a duplex mismatch.

Wireless Network Settings

If the device's cascading mode is set to 'Bridging' or its role is set to 'Slave' in the port forwarding mode, the wireless settings will be disabled. See Setting the Cascading Mode (on page 218).

By default the wireless interface is disabled. You should enable it if wireless networking is wanted.

On the Network page, click the WIRELESS section to configure wireless and IPv4/IPv6 settings.

Interface Settings:

Field/setting Description
Enable Interface Enable or disable the wireless interface.When disabled, the wireless networking fails.
Hardware State Check this field to ensure that the PX2 has detected a wireless USB LAN adapter. If not, verify whether the USB LAN adapter is firmly connected or whether it is supported.
SSID Type the name of the wireless access point (AP).
Force AP BSSID If the BSSID is available, select this checkbox.
BSSID Type the MAC address of an access point.
Enable High Throughput (802.11n)	Enable or disable 802.11n protocol.
Authentication	Select an authentication method.No Authentication: No authentication data is required.PSK: A Pre-Shared Key is required.EAP - PEAP: Use Protected Extensible Authentication Protocol. Only MSCHAPv2 is supported. Enter required authentication data in the fields that appear.
Pre-Shared Key	This field appears only when PSK is selected.Type the PSK string.
Identity	This field appears only when 'EAP - PEAP' is selected.Type your user name.
Password	This field appears only when 'EAP - PEAP' is selected.Type your password.
CA Certificate	This field appears only when 'EAP - PEAP' is selected.A third-party CA certificate may or may not be needed. If needed, follow the steps below.

• Available settings for the CA Certificate:

If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see TLS Certificate Chain (on page 726).

Field/setting Description
Enable verification of TLS certificate chain	Select this checkbox for the PX2 to verify the validity of the TLS certificate that will be installed.▪ For example, the PX2 will check the certificate's validity period against the systemtime.
Browse...	Click this button to import a certificate file. Then you can:Click Show to view the certificate's content.Click Remove to delete the installed certificate if it is inappropriate.
Allow expired and not yet valid certificates	Select this checkbox to make the authentication succeed regardless of the certificate's validity period.After deselecting this checkbox, the authentication fails whenever any certificate in the selected certificate chain is outdated or not valid yet.
Allow wireless connection if system clock is incorrect	When this checkbox is deselected, and if the system time is incorrect, the installed TLS certificate is considered not valid yet and will cause the wireless network connection to fail.When this checkbox is selected, it will make the wireless network connection successful when the PX2 system time is earlier than the firmware build before synchronizing with any NTP server.The incorrect system time issue may occur when the PX2 has once been powered off for a long time.

IPv4 settings:

Field/setting Description
Enable IPv4 Enable or disable the IPv4 protocol.
IP Auto Configuration	Select the method to configure IPv4 settings.DHCP: Auto-configure IPv4 settings via DHCP servers.Static: Manually configure the IPv4 settings.

- DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements:

• Consists of alphanumeric characters and/or hyphens

• Cannot begin or end with a hyphen

• Cannot contain more than 63 characters

• Cannot contain punctuation marks, spaces, and other symbols

- Static settings: Assign a static IPv4 address, which follows this syntax "IP address/prefix length".

Example: 192.168.84.99/24

IPv6 settings:

Field/setting Description

Enable IPv6 Enable or disable the IPv6 protocol.

IP Auto Configuration

Select the method to configure IPv6 settings.

■ Automatic: Auto-configure IPv6 settings via DHCPv6.
■ Static: Manually configure the IPv6 settings.

- Automatic settings: Optionally specify the preferred hostname, which must meet the above requirements.

- Static settings: Assign a static IPv6 address, which follows this syntax "IP address/prefix length".

Example: fd07:2fa:6cff:1111::0/128

(Optional) To view the wireless LAN diagnostic log:

- Click Show WLAN Diagnostic Log. See Wireless LAN Diagnostic Log (on page 213).

WIRELESS Show WLAN Diagnostic Log Enable Interface Hardware State not detected Wireless Settings

Wireless LAN Diagnostic Log

The PX2 provides a diagnostic log for inspecting connection errors that occurred over the wireless network interface. The information is useful for technical support.

Note that the WLAN Diagnostic Log shows data only after the Network Interface is set to Wireless.

Each entry in the log consists of:

• ID number
• Date and time
• Description

To view the log:

1. Choose Device Settings > Network > WIRELESS > Show WLAN Diagnostic Log. See Configuring Network Settings (on page 205).
2. The log is refreshed automatically at a regular interval of five seconds. To avoid any new events' interruption during data browsing, you can suspend the automatic update by clicking || Pause.

- To restore automatic update, click Resume. Those new events that have not been listed yet due to suspension will be displayed in the log now.

1. To go to other pages of the log, click the pagination bar at the bottom of the page.

- When there are more than 5 pages and the page numbers listed does not show the desired one, click ... to have the bar show the next or previous five page numbers, if available.

First

Previous

1

2

3

4

5

...

Next

Last

1. If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

▶ To clear the diagnostic log:

1. On the top-right corner of the log, click : >

Clear Log

1. Click Clear Log on the confirmation message.

Static Route Examples

This section describes two static route examples: IPv4 and IPv6. Both examples assume that two network interface controllers (NIC) have been installed in one network server, leading to two available subnets, and IP forwarding has been enabled. All of the NICs and PX2 devices in the examples use static IP addresses.

Most of local multiple networks are not directly reachable and require the use of a gateway. Therefore, we will select Gateway in the following examples. If your local multiple networks are directly reachable, you should select Interface rather than Gateway.

Note: If Interface is selected, you should select an interface name instead of entering an IP address. See Interface Names (on page 217).

IPv4 example:

• Your PX2: 192.168.100.64
  • Two NICs: 192.168.200.75 and 192.168.100.88
• Two networks: 192.168.200.0 and 192.168.100.0
• Prefix length: 24

graph TD
    A["NIC - 1\n192.168.200.75"] --> C["192.168.200.0"]
    B["NIC - 2\n192.168.100.88"] --> D["192.168.100.0"]
    E["Raritan\n192.168.100.64"] --> D

192.168.200.X

In this example, NIC-2 (192.168.100.88) is the next hop router for your PX2 to communicate with any device in the other subnet 192.168.200.0. In the IPv4 "Static Routes" section, you should enter the data as shown below. Note that the address in the first field must be of the Classless Inter-Domain Routing (CIDR) notation.

1 192.168.200.0/24 Gateway 192.168.100.88 ↑ ↓ ↕

Tip: If you have configured multiple static routes, you can click on any

route and then make changes, use ↑ or ↓ to re-sort the priority, or click to delete it.

IPv6 example:

• Your PX2: fd07:2fa:6cff:2405::30
• Two NICs: fd07:2fa:6cff:1111::50 and fd07:2fa:6cff:2405::80
• Two networks: fd07:2fa:6cff:1111::0 and fd07:2fa:6cff:2405::0
• Prefix length: 64

graph TD
    A["NIC - 1\nfd07:2fa:6cff:1111::50"] --> D["fd07:2fa:6cff:1111::0"]
    B["NIC - 2\nfd07:2fa:6cff:2405::80"] --> E["fd07:2fa:6cff:2405::0"]
    F["Raritan\nfd07:2fa:6cff:2405::30"] --> E

fd07:2fa:6cff:1111::X

In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your PX2 to communicate with any device in the other subnet fd07:2fa:6cff:1111::0.

In the IPv6 "Static Routes" section, you should enter the data as shown below. Note that the address in the first field must be of the Classless Inter-Domain Routing (CIDR) notation.

1 fd07:2fa:6cff:2405::0/64 Gateway fd07:2fa:6cff:2405::80 ↑ ↓ ↓ Tip: If you have configured multiple static routes, you can click on any route and then make changes, use ↑ or ↓ to re-sort the priority, or click to delete it.

Interface Names

When your local multiple networks are "directly reachable", you should select Interface for static routes. Then choose the interface where another network is connected.

192.168.200.0/24 Interface BRIDGE ETHERNET WIRELESS

Interface name Description
BRIDGE When another wired network is connected to the Ethernet port of your PX2, and your PX2 has been set to the bridging mode, select this interface name instead of the Ethernet interface.
ETHERNET When another wired network is connected to the Ethernet port of your PX2, and the bridging mode is NOT enabled, select this interface name.
WIRELESS	When another wireless network is connected to your PX2, select this interface name.

Setting the Cascading Mode

A maximum of 16 PX2 devices can be cascaded to share one Ethernet connection. See Cascading Multiple PX2 Devices for Sharing Ethernet Connectivity (on page 28).

The cascading mode configured on the master device determines the Ethernet sharing method, which is either network bridging or port forwarding. See Overview of the Cascading Modes (on page 219).

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

Only a user with the Change Network Settings permission can configure the cascading mode.

Note: PX2 in the Port Forwarding mode does not support APIPA. See APIPA and Link-Local Addressing (on page 2).

To configure the cascading mode:

1. Connect the device you will cascade to the LAN and find its IP address, or connect it to a computer.

2. For computer connection instructions, see Connecting the PX2 to a Computer (on page 25).

3. To find the IP address, follow the first three steps of Initial Network Configuration via CLI (on page 721), and you will see the IP address.

4. Log in to its web interface. See Login (on page 86).

5. Choose Device Settings > Network.
6. Select the preferred mode in the Cascading Mode field.

Mode Description
None	No cascading mode is enabled. This is the default.
Bridging	Each device in the cascading chain is accessed with a different IP address.
Port Forwarding	Each device in the cascading chain is accessed with the same IP address(es) but with a different port number assigned.For details on port numbers, see Port Number Syntax (on page 221).

Tip: If selecting Port Forwarding, the Device Information page will show a list of port numbers for all cascaded devices. Simply choose Maintenance > Device Information > Port Forwarding.

1. For the Port Forwarding mode, one to two more fields have to be configured.

Note that if either setting below is incorrectly configured, a networking issue occurs.

Field Description
Role(available on all cascaded devices)	Master or Slave.This is to determine which device is the master and which ones are slave devices.
Downstream interface(available on the maser device only)	USB or ETHERNET.This is to determine which port on the master device is connected to Slave 1.Always select USB.

1. (Optional) Configure the network settings by clicking the BRIDGE, ETHERNET, or WIRELESS section on the same page.

In the Bridging mode, each cascaded device can have different network settings. You may need to configure each device's network settings in the BRIDGE section.
- In the Port Forwarding mode, all cascaded devices share the master device's network settings. You only need to configure the master device's network settings in the ETHERNET and/or WIRELESS section.

See Wired Network Settings (on page 207) or Wireless Network Settings (on page 210)

Tip: You can enable/configure multiple network interfaces in the Port Forwarding mode so that the cascading chain has multiple IP addresses.

1. Click Save.

For information on accessing each cascaded device in the Port Forwarding mode, see Port Forwarding Examples (on page 223).

▶ Online cascading information:

For detailed information on the cascading configuration and restrictions, refer to the Cascading Guide, which is available from Raritan website's Support page (http://www.raritan.com/support/).

Overview of the Cascading Modes

You must apply a cascading mode to the cascading chain. See Setting the Cascading Mode (on page 218).

There are two cascading modes: Bridging and Port Forwarding.

In the following illustration, it is assumed that users enable the DHCP networking for the cascading chain comprising four devices. In the diagrams, "M" is the master device and "S" is a slave device.

▶ Illustration:

- "Bridging" mode:

graph TD
    A["DHCP"] -->|100.1.1.7| B["M"]
    A -->|100.1.1.2| C["S"]
    A -->|100.1.1.3| D["S"]
    A -->|100.1.1.4| E["S"]
    B --> F["LAN"]
    C --> F
    D --> F
    E --> F

In this mode, the DHCP server communicates with every cascaded device respectively and assigns four different IP addresses. Each device has its own IP address.

The way to remotely access each cascaded device is completely the same as accessing a standalone device in the network.

- "Port Forwarding" mode:

graph LR
    A["DHCP"] -->|100.1.1.1| B["M"]
    B --> C["S"]
    C --> D["S"]
    D --> E["S"]
    style A fill:#f9f,stroke:#333
    style B fill:#ccf,stroke:#333
    style C fill:#cfc,stroke:#333
    style D fill:#fcc,stroke:#333
    style E fill:#cff,stroke:#333

In this mode, the DHCP server communicates with the master device alone and assigns one IP address to the master device. All slave devices share the same IP address as the master device.

You must specify a 5XXXX port number (where X is a number) when remotely accessing any slave device with the shared IP address. See Port Number Syntax (on page 221).

▶ Comparison between cascading modes:

• The Bridging mode supports the wired network only, while the Port Forwarding mode supports both wired and wireless networks.
• Both cascading modes support a maximum of 16 devices in a chain.
• Both cascading modes support both DHCP and static IP addressing.
• In the Bridging mode, each cascaded device has a unique IP address. In the Port Forwarding mode, all cascaded devices share the same IP address(es) as the master device.
• In the Bridging mode, each cascaded device has only one IP address. In the Port Forwarding mode, each cascaded device can have multiple IP addresses as long as the master device has multiple network interfaces enabled/configured properly.

For example:

- When the master device has two Ethernet ports (ETH1/ETH2), you can enable ETH1, ETH2 and WIRELESS interfaces so that the Port-Forwarding chain has two wired IP addresses and one wireless IP address.

Port Number Syntax

In the Port Forwarding mode, all devices in the cascading chain share the same IP address(es). To access any cascaded device, you must assign an appropriate port number to it.

• Master device: The port number is either 5NNXX or the standard TCP/UDP port.
• Slave device: The port number is 5NNXX.

5NNXX port number syntax:

- NN is a two-digit number representing the network protocol as shown below:

Protocols NN
HTTPS	00
HTTP	01
SSH	02
TELNET	03
SNMP	05
MODBUS	06

- XX is a two-digit number representing the device position as shown below.

Position XX Position XX
Master device	00	Slave 8	08
Slave 1	01	Slave 9	09
Slave 2	02	Slave 10	10
Slave 3	03	Slave 11	11
Slave 4	04	Slave 12	12
Slave 5	05	Slave 13	13
Slave 6	06	Slave 14	14
Slave 7	07	Slave 15	15

For example, to access the Slave 4 device via Modbus/TCP, the port number is 50604. See Port Forwarding Examples (on page 223) for further illustrations.

Tip: The full list of each cascaded device's port numbers can be retrieved from the web interface. Choose Maintenance > Device Information > Port Forwarding.

▶ Standard TCP/UDP ports:

The master device can be also accessed through standard TCP/UDP ports as listed in the following table.

Protocols Port Numbers
HTTPS	443
HTTP	80
SSH	22
TELNET	23
SNMP	161
MODBUS	502

In the Port Forwarding mode, the cascaded device does NOT allow you to modify the standard TCP/UDP port configuration, including HTTP, HTTPS, SSH, Telnet and Modbus/TCP.

Port Forwarding Examples

To access a cascaded device in the Port Forwarding mode, assign a port number to the IP address.

• Master device: Assign proper 5NNXX port numbers or standard TCP/UDP ports. See Port Number Syntax (on page 221) for details.
• Slave device: Assign proper 5NNXX port numbers.

Assumption: The Port Forwarding mode is applied to a cascading chain comprising three devices. The IP address is 192.168.84.77.

Master device:

Position code for the master device is '00' so each port number is 5NN00 as listed below.

Protocols Port numbers
HTTPS	50000
HTTP	50100
SSH	50200
TELNET	50300
SNMP	50500
MODBUS	50600

Examples using "5NN00" ports:

• To access the master device via HTTPS, the IP address is: https://192.168.84.77:50000/
• To access the master device via HTTP, the IP address is: http://192.168.84.77:50100/
• To access the master device via SSH, the command is: ssh -p 50200 192.168.84.77

Examples using standard TCP/UDP ports:

• To access the master device via HTTPS, the IP address is: https://192.168.84.77:443/
• To access the master device via HTTP, the IP address is: http://192.168.84.77:80/

- To access the master device via SSH, the command is: ssh -p 22 192.168.84.77

▶ Slave 1 device:

Position code for Slave 1 is '01' so each port number is 5NN01 as shown below.

Protocols Port numbers
HTTPS	50001
HTTP	50101
SSH	50201
TELNET	50301
SNMP	50501
MODBUS	50601

Examples:

• To access Slave 1 via HTTPS, the IP address is: https://192.168.84.77:50001/
• To access Slave 1 via HTTP, the IP address is: http://192.168.84.77:50101/
• To access Slave 1 via SSH, the command is: ssh -p 50201 192.168.84.77

Slave 2 device:

Position code for Slave 2 is '02' so each port number is 5NN02 as shown below.

Protocols Port numbers
HTTPS	50002
HTTP	50102
SSH	50202
TELNET	50302
SNMP	50502
MODBUS	50602

Examples:

• To access Slave 2 via HTTPS, the IP address is: https://192.168.84.77:50002/
• To access Slave 2 via HTTP, the IP address is: http://192.168.84.77:50102/
• To access Slave 2 via SSH, the command is: ssh -p 50202 192.168.84.77

Adding, Removing or Swapping Cascaded Devices

Change a device's cascading mode first before adding that device to a cascading chain, or before disconnecting that device from the chain.

If you only want to change the cascading mode of an existing chain, or swap the master and slave device, always start from the slave device.

Note: If the following procedures are not followed, a networking issue occurs. When a networking issue occurs, check the cascading connection and/or software settings of all devices in the chain. See Cascading Troubleshooting (on page 716).

To add a device to an existing chain:

1. Connect the device you will cascade to the LAN and find its IP address, or connect it to a computer.
2. Log in to this device and set its cascading mode to be the same as the existing chain's cascading mode. See Setting the Cascading Mode (on page 218).
3. (Optional) If this device will function as a slave device, disconnect it from the LAN after configuring the cascading mode.
4. Connect this device to the chain, using either a USB or Ethernet cable.

To remove a device from the chain:

1. Log in to the desired cascaded device, and change its cascading mode to None.

Exception: If you are going to connect the removed device to another cascading chain, set its cascading mode to be the same as the mode of another chain.

1. Now disconnect it from the cascading chain.

To swap the master and slave device:

• In the Bridging mode, you can swap the master and slave devices by simply disconnecting ALL cascading cables from them, and then reconnecting cascading cables. No changes to software settings are required.
  • In the Port Forwarding mode, you must follow the procedure below:

a. Access the slave device that will replace the master device, and set its role to 'Master', and correctly set the downstream interface.
b. Access the master device, set its role to 'Slave'.
c. Swap the master and slave device now.

- You must disconnect the LAN cable and ALL cascading cables connected to the two devices first before swapping them, and then reconnecting all cables.

To change the cascading mode applied to a chain:

1. Access the last slave device, and change its cascading mode.
   If the new cascading mode is 'Port Forwarding', you must also set its role to 'Slave'.
2. Access the second to last, third to last and so on until the first slave device to change their cascading modes one by one.
3. Access the master device, and change its cascading mode.

- If the new cascading mode is 'Port Forwarding', you must also set its role to 'Master', and correctly select the downstream interface.

The following diagram indicates the correct sequence. 'N' is the final one.

■ M = Master device
■ S = Slave device

graph LR
    M --> S
    S --> S
    S --> S
    S --> S
    N <--> 4
    4 <--> 3
    3 <--> 2
    2 <--> 1

Configuring Network Services

The PX2 supports the following network communication services.

Network Services

HTTP

SNMP

SMTP Server

SSH

Telnet

Modbus

Service Advertising

HTTPS and HTTP enable the access to the web interface. Telnet and SSH enable the access to the command line interface. See Using the Command Line Interface (on page 400).

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.

Submenu command Refer to
HTTP	Changing HTTP(S) Settings (on page 228)
SNMP	Configuring SNMP Settings (on page 228)
SMTP Server	Configuring SMTP Settings (on page 230)
SSH	Changing SSH Settings (on page 232)
Telnet	Changing Telnet Settings (on page 233)
Modbus	Changing Modbus Settings (on page 233)
Service Advertising	Enabling Service Advertising (on page 233)

Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather

than SSL 3.0.

Changing HTTP(S) Settings

HTTPS uses Transport Layer Security (TLS) technology to encrypt all traffic to and from the PX2 so it is a more secure protocol than HTTP. As of release 3.5.0, PX2 disables TLS 1.0 and 1.1 by default. It enables only TLS 1.2 and 1.3.

By default, any access to the PX2 via HTTP is automatically redirected to HTTPS. You can disable this redirection if needed.

To change HTTP or HTTPS port settings:

1. Choose Device Settings > Network Services > HTTP.
2. Enable either or both protocols by selecting the corresponding 'Enable' checkbox.
3. To use a different port for HTTP or HTTPS, type a new port number.

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

1. To redirect the HTTP access to the PX2 to HTTPS, select the "Redirect HTTP connections to HTTPS."

- The redirection checkbox is configurable only when both HTTP and HTTPS have been enabled.

▶ Special note for AES ciphers:

The PX2 device's SSL/TLS-based protocols, including HTTPS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between PX2 and the client (such as a web browser), which is impacted by the cipher priority of PX2 and the client's cipher availability/settings.

Tip: To force PX2 to use a specific AES cipher, refer to your client's user documentation for information on configuring AES settings. For example, you can enable a cipher and disable the other in the Firefox via the "about:config" command.

Configuring SNMP Settings

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

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

To configure SNMP communication:

1. Choose Device Settings > Network Services > SNMP.

SNMP SNMP Agent Enable SNMP v1 / v2c Read community string public Write community string Enable SNMP v3 MIB-II System Group sysContact sysName sysLocation SNMP Notifications Enable SNMP notifications Notification type SNMPv2c trap Timeout 3 s Number of retries 5

Host Port Community

1 162 2 162 3 162 Download MIBs ✓ Save

1. Enable or disable "SNMP v1 / v2c" and/or "SNMP v3" by clicking the corresponding checkbox.

- The SNMP v1/v2c read-only access is enabled by default. The default 'Read community string' is "public."

- To enable read-write access, type the 'Write community string.' Usually the string is "private."

1. Enter the MIB-II system group information, if applicable.

- sysContact - the contact person in charge of the system

- sysName - the name assigned to the system

- sysLocation - the location of the system

1. To configure SNMP notifications:

a. Select the 'Enable SNMP notifications' checkbox.

b. Select a notification type -- SNMPv2c trap, SNMPv2c inform, SNMPv3 trap, and SNMPv3 inform.

c. Specify the SNMP notification destinations and enter necessary information. For details, refer to:

■ SNMPv2c Notifications (on page 392)

■ SNMPv3 Notifications (on page 393)

Note: Any changes made to the 'SNMP Notifications' section on the SNMP page will update the settings of the System SNMP Notification Action, and vice versa. See Available Actions (on page 284). To add more than three SNMP destinations, you can create new SNMP notification actions. See Send an SNMP Notification (on page 298).

1. You must download the SNMP MIB for your PX2 to use with your SNMP manager.

a. Click the Download MIBs title bar to show the download links.

Download MIBs

b. Click the PDU2-MIB download link. See Downloading SNMP MIB(on page 396).

1. Click Save.

Configuring SMTP Settings

The PX2 can be configured to send alerts or event messages to a specific administrator by email. See Event Rules and Actions(on page 262).

To send emails, you have to configure the SMTP settings and enter an IP address for your SMTP server and a sender's email address.

If any email messages fail to be sent successfully, the failure event and reason are available in the event log. See Viewing or Clearing the Local Event Log (on page 358).

To set SMTP server settings:

1. Choose Device Settings > Network Services > SMTP Server.
2. Enter the information needed.

Field Description
IP Address/Host Name	Type the name or IP address of the mail server.
Port Type the port number.	Default is 25
Sender Email Address	Type an email address for the sender.
Number of Sending Retries	Type the number of email retries. Default is 2 retries
Time Between Sending Retries	Type the interval between email retries in minutes. Default is 2 minutes.
Server Requires Authentication	Select this checkbox if your SMTP server requires password authentication.
User Name, Password	Type a user name and password for authentication after selecting the above checkbox. The length of user name and password ranges between 4 and 64. Case sensitive. Spaces are not allowed for the user name, but allowed for the password.
Enable SMTP over TLS (StartTLS)	If your SMTP server supports the Transport Layer Security (TLS), select this checkbox.

■ Settings for the CA Certificate:

If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see TLS Certificate Chain (on page 726).

Field/setting Description
Browse...	Click this button to import a certificate file. Then you can:Click Show to view the certificate's content.Click Remove to delete the installed certificate if it is inappropriate.

Field/setting Description

Allow expired and not yet valid certificates

• Select this checkbox to make the authentication succeed regardless of the certificate's validity period.
  ■ After deselecting this checkbox, the authentication fails whenever any certificate in the selected certificate chain is outdated or not valid yet.

• Now that you have set the SMTP settings, you can test it to ensure it works properly.

a. Type the recipient's email address in the Recipient Email Addresses field. Use a comma to separate multiple email addresses.
b. Click Send Test Email.
c. Check if the recipient(s) receives the email successfully.

1. Click Save.

▶ Special note for AES ciphers:

The PX2 device's SSL/TLS-based protocols, including SMTP over StartTLS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between PX2 and the client (such as a web browser), which is impacted by the cipher priority of PX2 and the client's cipher availability/settings.

Tip: To force PX2 to use a specific AES cipher, refer to your client's user documentation for information on configuring AES settings.

Changing SSH Settings

You can enable or disable the SSH access to the command line interface, change the TCP port, or set a password or public key for login over the SSH connection.

To change SSH settings:

1. Choose Device Settings > Network Services > SSH.
2. To enable or disable the SSH access, select or deselect the checkbox.
3. To use a different port, type a port number.
4. Select one of the authentication methods.

- Password authentication only: Enables the password-based login only.

■ Public key authentication only: Enables the public key-based login only.
- Password and public key authentication: Enables both the password- and public key-based login. This is the default.

5. Click Save.

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

Changing Telnet Settings

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

To change Telnet settings:

1. Choose Device Settings > Network Services > Telnet.
2. To enable the Telnet access, select the checkbox.
3. To use a different port, type a new port number.
4. Click Save.

Changing Modbus Settings

You can enable or disable the Modbus/TCP access to the PX2, set it to the read-only mode, or change the TCP port.

To change the Modbus/TCP settings:

1. Choose Device Settings > Network Services > Modbus.
2. To enable the Modbus/TCP access, select the "Modbus/TCP Access" checkbox.
3. To use a different port, type a new port number.
4. To enable the Modbus read-only mode, select the checkbox of the "Read-only mode" field. To enable the read-write mode, deselect it.

Enabling Service Advertising

The PX2 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

By default, this feature is enabled.

Enabling this feature also enables Link-Local Multicast Name Resolution (LLMNR) and/or MDNS, which are required for resolving APIPA host names. See APIPA and Link-Local Addressing (on page 2).

The service advertisement feature supports both IPv4 and IPv6 protocols.

If you have set a preferred host name for IPv4 and/or IPv6, that host name can be used as the zero configuration .local host name, that is, .local, where is the preferred host name you have specified for PX2. The IPv4 host name is the first priority. If an IPv4 host name is not available, then use the IPv6 host name.

Note: For information on configuring IPv4 and/or IPv6 network settings, see Wired Network Settings (on page 207).

To enable or disable service advertising:

1. Choose Device Settings > Network Services > Service Advertising.
2. To enable the service advertising, select either or both checkboxes.
3. To advertise via MDNS, select the Multicast DNS checkbox.

4. To advertise via LLMNR, select the Link-Local Multicast Name Resolution checkbox.

5. Click Save.

Configuring Security Settings

The PX2 provides tools to control access. You can enable the internal firewall, create firewall rules, and set login limitations. In addition, you can create and install the certificate or set up external authentication servers for access control. This product supports SHA-2 TLS certificates.

Tip: To force all HTTP accesses to the PX2 to be redirected to HTTPS, see Changing HTTP(S) Settings (on page 228).

Chapter 6: Using the Web Interface

Security

IP Access Control

Role Based Access Control

SSL Certificate

Authentication

Login Settings

Password Policy

Service Agreement

Submenu command Refer to
IP Access Control	Creating IP Access Control Rules (on page 235)
Role Based Access Control	Creating Role Based Access Control Rules (on page 239)
SSL Certificate	Setting Up an SSL/TLS Certificate (on page 242)
Authentication	Setting Up External Authentication (on page 247)
Login Settings	Configuring Login Settings (on page 255)
Password Policy	Configuring Password Policy (on page 256)
Service Agreement	Enabling the Restricted Service Agreement (on page 257)

Creating IP Access Control Rules

IP access control rules (firewall rules) determine whether to accept or discard traffic to/from the PX2, based on the IP address of the host sending or receiving the traffic. When creating rules, keep these principles in mind:

• Rule order is important.

When traffic reaches or is sent from the PX2, 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.

- Prefix length is required.

When typing the IP address, you must specify it in the CIDR notation. That is, BOTH the address and the prefix length are included. For example, to specify a single address with the 24-bit prefix length, use this format:

x.x.x.x/24

/24 = the prefix length.

Note: Valid IPv4 addresses range from 0.0.0.0 through 255.255.255.255.

To configure IPv4 access control rules:

1. Choose Device Settings > Security > IP Access Control.
2. Select the 'Enable IPv4 access control' checkbox to enable IPv4 access control rules.

3. Determine the IPv4 default policy.

4. Accept: Accepts traffic from all IPv4 addresses.

5. Drop: Discards traffic from all IPv4 addresses, without sending any failure notification to the source host.

6. Reject: Discards traffic from all IPv4 addresses, and an ICMP message is sent to the source host for failure notification.

7. Go to the Inbound Rules section or the Outbound Rules section according to your needs.

8. Inbound rules control the data sent to the PX2.

9. Outbound rules control the data sent from the PX2.

10. Create rules. Refer to the tables below for different operations.

ADD a rule to the end of the list

• Click Append.
• Type an IP address and subnet mask in the IP/Mask field.
• Select an option in the Policy field.
• Accept: Accepts traffic from/to the specified IP address(es).
• Drop: Discards traffic from/to the specified IP address(es), without sending any failure notification to the source or destination host.
• Reject: Discards traffic from/to the specified IP address(es), and an ICMP message is sent to the source or destination host for failure notification.

INSERT a rule between two 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 Above.
• Type an IP address and subnet mask in the IP/Mask field.
• Select Accept, Drop or Reject in the Policy field. Refer to the above table for details.

The system automatically numbers the rule.

1. When finished, the rules are listed.

- You can select any existing rule and then click

to change its priority.

IPv4 Enable IPv4 access control ✓ Inbound Rules Default policy Accept ▼

IP/Mask Policy

1 192.168.8.8/32 Drop 2 192.168.255.33/24 Accept 3 192.210.15.30/32 Reject Append Insert Above Outbound Rules Default policy Accept ▼

IP/Mask Policy

1 192.23.89.100/24 Drop Append Insert Above ✓ Save

1. Click Save. The rules are applied.

To configure IPv6 access control rules:

1. On the same page, select the 'Enable IPv6 access control' checkbox to enable IPv6 access control rules.

2. Follow the same procedure as the above IPv4 rule setup to create IPv6 rules.

3. Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are not saved.

Editing or Deleting IP Access Control Rules

When an existing IP access control rule requires updates of IP address range and/or policy, modify them accordingly. Or you can delete any unnecessary rules.

To modify or delete a rule:

1. Choose Device Settings > Security > IP Access Control.
2. Go to the IPv4 or IPv6 section.
3. Select the desired rule in the list.

- Ensure the IPv4 or IPv6 checkbox has been selected, or you cannot edit or delete any rule.

1. Perform the desired action.

■ Make changes to the selected rule, and then click Save. For information on each field, see Creating IP Access Control Rules (on page 235).
- Click to remove it.
■ To resort its order, click

1. Click Save.

2. IPv4 rules: Make sure you click the Save button in the IPv4 section, or the changes made to IPv4 rules are not saved.

3. IPv6 rules: Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are not saved.

Creating Role Based Access Control Rules

Role-based access control rules are similar to IP access control rules, except that they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses.

Same as IP access control rules, the order of role-based access control rules is important, since the rules are executed in numerical order.

To create IPv4 role-based access control rules:

1. Choose Device Settings > Security > Role Based Access Control.

2. Select the 'Enable role based access control for IPv4' checkbox to enable IPv4 access control rules.

3. Determine the IPv4 default policy.

4. Accept: Accepts traffic when no matching rules are present.

5. Deny: Rejects any user's login attempt when no matching rules are present.

6. Create rules. Refer to the tables below for different operations.

ADD a rule to the end of the list

• Click Append.
• Type a starting IP address in the Start IP field.
• Type an ending IP address in the End IP field.
• Select a role in the Role field. This rule applies to members of this role only.

• Select an option in the Policy field.

• Accept: Accepts traffic from the specified IP address range when the user is a member of the specified role.

• Deny: Rejects the login attempt of a user from the specified IP address range when that user is a member of the specified role.

INSERT a rule between two 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 Above.
• Type a starting IP address in the Start IP field.
• Type an ending IP address in the End IP field.
• Select a role in the Role field. This rule applies to members of this role only.
• Select Accept or Deny in the Policy field. Refer to the above table for details.

The system automatically numbers the rule.

1. When finished, the rules are listed on this page.

- You can select any existing rule and then click

to change its priority.

IPv4 Enable role based access control for IPv4 ✓ Default policy Accept

Start IP End IP Role Policy

1 192.168.255.0 192.168.255.255 Operator Deny 2 192.168.90.16 192.168.90.55 Admin Accept Append Insert Above ✓ Save

1. Click Save. The rules are applied.

To configure IPv6 access control rules:

1. On the same page, select the 'Enable role based access control for IPv6' checkbox to enable IPv6 access control rules.
2. Follow the same procedure as the above IPv4 rule setup to create IPv6 rules.
3. Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are not saved.

Editing or Deleting Role Based Access Control Rules

You can modify existing rules to update their roles/IP addresses, or delete them when they are no longer needed.

To modify a role-based access control rule:

1. Choose Device Settings > Security > Role Based Access Control.
2. Go to the IPv4 or IPv6 section.
3. Select the desired rule in the list.

- Ensure the IPv4 or IPv6 checkbox has been selected, or you cannot select any rule.

1. Perform the desired action.

■ Make changes to the selected rule, and then click Save. For information on each field, see Creating Role Based Access Control Rules[on page 239].

- Click to remove it. - To resort its order, click ↑ or ↓

5. Click Save.

• IPv4 rules: Make sure you click the Save button in the IPv4 section, or the changes made to IPv4 rules are not saved.
• IPv6 rules: Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are not saved.

Setting Up an SSL/TLS Certificate

Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.

Having an X.509 digital certificate ensures that both parties in an SSL/TLS connection are who they say they are.

Besides, you can create or apply for a multi-domain certificate with subject alternative names.

To obtain a CA-signed certificate:

1. Create a Certificate Signing Request (CSR) on the PX2. See Creating a CSR (on page 242).
2. Submit it to a certificate authority (CA). After the CA processes the information in the CSR, it provides you with a certificate.
3. Import the CA-signed certificate onto the PX2. See Installing a CA-Signed Certificate (on page 244).

Note: If you are using a certificate that is part of a chain of certificates, each part of the chain is signed during the validation process.

▶ A CSR is not required in either scenario below:

• Make the PX2 create a self-signed certificate. See Creating a Self-Signed Certificate (on page 245).
• Appropriate, valid certificate and key files are already available, and you just need to import them. See Installing or Downloading Existing Certificate and Key (on page 246).

Creating a CSR

Follow this procedure to create the CSR for your PX2.

Note that you must enter information in the fields showing the message 'required.'

required

To create a CSR:

1. Choose Device Settings > Security > SSL Certificate.
2. Provide the information requested.

■ Subject:

Field Description
Country 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 PX2.
Email Address An email address where you or another administrative user can be reached.

Warning: If you generate a CSR without values entered in the required fields, you cannot obtain third-party certificates.

■ Subject Alternative Names:

If you want a certificate to secure multiple hosts across different domains or subdomains, you can add additional DNS host names or IP addresses of the wanted hosts to this CSR so that a single certificate will be valid for all of them.

Click

+ Add Name

when there are more than one additional

hosts to add.

■ Examples of subject alternative names: support.raritan.com, help.raritan.com, help.raritan.net, and 192.168.77.50.

■ Key Creation Parameters:

Field Do this
Key Length Select an	available key length (bits). A larger key length enhances the security, but slows down the response of PX2.▪ Only 2048 is available now.
Self-Sign	For requesting a certificate signed by the CA, ensure this checkbox is NOT selected.
Challenge, Confirm Challenge	Type a password. The password is used to protect the certificate or CSR. This information is optional.The value should be 4 to 64 characters long. Case sensitive.

1. Click Create New SSL Key to create both the CSR and private key. This may take several minutes to complete.

2. Click Download Certificate Signing Request to download the CSR to your computer.
   a. You are prompted to open or save the file. Click Save to save it onto your computer.
   b. Submit it to a CA to obtain the digital certificate.
   c. If the CSR contains incorrect data, click Delete Certificate Signing Request to remove it, and then repeat the above steps to re-create it.

3. To store the newly-created private key on your computer, click Download Key in the New SSL Certificate section.

Note: The Download Key button in the Active SSL Certificate section is for downloading the private key of the currently-installed certificate rather than the newly-created one.

- You are prompted to open or save the file. Click Save to save it onto your computer.

1. After getting the CA-signed certificate, install it. See Installing a CA-Signed Certificate (on page 244).

Installing a CA-Signed Certificate

To get a certificate from a certificate authority (CA), first create a CSR and send it to the CA. See Creating a CSR (on page 242).

After receiving the CA-signed certificate, install it onto the PX2.

To install the CA-signed certificate:

1. Choose Device Settings > Security > SSL Certificate.

Browse

1. Click to navigate to the CA-signed certificate file.

2. Click Upload to install it.

3. To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section.

Creating a Self-Signed Certificate

When appropriate certificate and key files for the PX2 are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate.

Note that you must enter information in the fields showing the message 'required.'

required

To create and install a self-signed certificate:

1. Choose Device Settings > Security > SSL Certificate.
2. Enter information.

Field Description
Country 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 PX2.
Email Address An email address where you or another administrative user can be reached.
Key Length Select an available key length (bits). A larger key length enhances the security, but slows down the response of PX2.▪ Only 2048 is available now.
Self-Sign Ensure this checkbox is selected, which indicates that you are creating a self-signed certificate.
Validity in days	This field appears after the Self Sign checkbox is selected.Type the number of days for which the self-signed certificate will be valid.

A password is not required for a self-signed certificate so the Challenge and Confirm Challenge fields disappear.

1. Click Create New SSL Key to create both the self-signed certificate and private key. This may take several minutes to complete.
2. Once complete, do the following:

a. Double check the data shown in the New SSL Certificate section.
b. If correct, click "Install Key and Certificate" to install the self-signed certificate and private key.

Tip: To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section.

If incorrect, click "Delete Key and Certificate" to remove the self-signed certificate and private key, and then repeat the above steps to re-create them.

1. (Optional) To download the self-signed certificate and/or private key, click Download Certificate or Download Key in the New SSL Certificate section.

- You are prompted to open or save the file. Click Save to save it onto your computer.

Note: The Download Key button in the Active SSL Certificate section is for downloading the private key of the currently-installed certificate rather than the newly-created one.

Installing or Downloading Existing Certificate and Key

You can download the already-installed certificate and private key from any PX2 for backup or file transfer. For example, you can install the files onto a replacement PX2, add the certificate to your browser and so on.

If valid certificate and private key files are already available, you can install them on the PX2 without going through the process of creating a CSR or a self-signed certificate.

Note: If you are using a certificate that is part of a chain of certificates, each part of the chain is signed during the validation process.

To download active key and certificate files from the PX2:

1. Choose Device Settings > Security > SSL Certificate.
2. In the Active SSL Certificate section, click Download Key and Download Certificate respectively.

Note: The Download Key button in the New SSL Certificate section, if present, is for downloading the newly-created private key rather than the one of the currently-installed certificate.

1. You are prompted to open or save the file. Click Save to save it onto your computer.

To install available key and certificate files onto the PX2:

1. Choose Device Settings > Security > SSL Certificate.
2. Select the "Upload Key and Certificate" checkbox at the bottom of the page.
3. The Key File and Certificate File fields appear. Click to select the key and/or certificate file.
4. Click Upload. The selected files are installed.
5. To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section.

Browse.

Setting Up External Authentication

Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.

For security purposes, users attempting to log in to the PX2 must be authenticated. The PX2 supports the following authentication mechanisms:

• Local user database on the PX2
  • Lightweight Directory Access Protocol (LDAP)
• Remote Access Dial-In User Service (Radius) protocol

By default, the PX2 is configured for local authentication. If you stay with this method, you only need to create user accounts. See Creating Users (on page 193).

If you prefer external authentication, you must provide the PX2 with information about the external Authentication and Authorization (AA) server.

If both local and external authentication is needed, create user accounts on the PX2 in addition to providing the external AA server data.

When configured for external authentication, all PX2 users must have an account on the external AA server. Local-authentication-only users will have no access to the PX2 except for the admin, who always can access the PX2.

If the external authentication fails, an "Authentication failed" message is displayed. Details regarding the authentication failure are available in the event log. See Viewing or Clearing the Local Event Log (on page 358).

Note that only users who have both the "Change Authentication Settings" and "Change Security Settings" permissions can configure or modify the authentication settings.

To enable external authentication:

1. Collect external AA server information. See Gathering LDAP/Radius Information (on page 248).
2. Enter required data for external AA server(s) on the PX2. See Adding LDAP/LDAPS Servers (on page 249) or Adding Radius Servers (on page 252).
3. For il lustrations, see LDAP Configuration Illustration (on page 654) or Radius Configuration Illustration (on page 667).
4. If both the external and local authentication is needed, or you have to return to the local authentication only, see Managing External Authentication Settings (on page 254).

▶ Special note about the AES cipher:

The PX2 device's SSL/TLS-based protocols, including LDAPS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between PX2 and the client (such as a web browser), which is impacted by the cipher priority of PX2 and the client's cipher availability/settings.

Tip: To force PX2 to use a specific AES cipher, refer to your client's user documentation for information on configuring AES settings.

Gathering LDAP/Radius Information

It requires knowledge of your AA server settings to configure the PX2 for external authentication. If you are not familiar with these settings, consult your AA server administrator for help.

Information needed for LDAP authentication:

• The IP address or hostname of the LDAP server
  • Whether the Secure LDAP protocol (LDAP over TLS) 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)

Information needed for Radius authentication:

• The IP address or host name of the Radius server
- Authentication protocol used by the Radius server
- Shared secret for a secure communication
- UDP authentication port and accounting port used by the Radius server

Adding LDAP/LDAPS Servers

To use LDAP authentication, enable it and enter the information you have gathered.

Note that you must enter information in the fields showing the message 'required.'

required

To add LDAP/LDAPS servers:

1. Choose Device Settings > Security > Authentication.
2. Click New in the LDAP Servers section.
3. Enter information.

Field/setting Description
IP Address / Hostname	The IP address or hostname of your LDAP/LDAPS server.▪ Without the encryption enabled, you can type either the domain name or IP address in this field, but you must type the fully qualified domain name if the encryption is enabled.
Copy settings from existing LDAP server	This checkbox appears only when there are existing AA server settings on the PX2. To duplicate any existing AA server's settings, refer to the duplicating procedure below.
Type of LDAP Server	Choose one of the following options:OpenLDAPMicrosoft Active Directory. Active Directory is an implementation of LDAP/LDAPS directory services by Microsoft for use in Windows environments.
Security	Determine whether you would like to use Transport Layer Security (TLS) encryption, which allows the PX2 to communicate securely with the LDAPS server.Three options are available:StartTLSTLSNone
Port(None/StartTLS)	The default Port is 389. Either use the standard LDAP TCP port or specify another port.
Port (TLS)	Configurable only when "TLS" is selected in the Security field.The default is 636. Either use the default port or specify another one.
Enable verification of LDAP Server Certificate	Select this checkbox if it is required to validate the LDAP server's certificate by the PX2 prior to the connection.If the certificate validation fails, the connection is refused.
CA Certificate	Consult your AA server administrator to get the CA certificate file for the LDAPS server.ClickBrowse...to select and install the certificate file.Click Show to view the installed certificate's content.Click Remove to delete the installed certificate if it is inappropriate.Note: If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see TLS Certificate Chain (on page 726).
Allow expired and not yet valid certificates	Select this checkbox to make the authentication succeed regardless of the certificate's validity period.After deselecting this checkbox, the authentication fails whenever any certificate in the selected certificate chain is outdated or not valid yet.
Anonymous Bind Use	this checkbox to enable or disable anonymous bind.To use anonymous bind, select this checkbox.When a Bind DN and password are required to bind to the external LDAP/LDAPS server, deselect this checkbox.
Bind DN	Required after deselecting the Anonymous Bind checkbox.Distinguished Name (DN) of the user who is permitted to search the LDAP directory in the defined search base.
Bind Password, Confirm Bind Password	Required after deselecting the Anonymous Bind checkbox.Enter the Bind password.
Base DN for Search	Distinguished Name (DN) of the search base, which is the starting point of the LDAP search.Example: ou=dev, dc=example, dc=com
Login Name Attribute	The attribute of the LDAP user class which denotes the login name.Usually it is the uid.
User Entry Object Class	The object class for user entries.Usually it is inetOrgPerson.
User Search Subfilter	Search criteria for finding LDAP user objects within the directory tree.
Active Directory Domain	The name of the Active Directory Domain.Example: testradius.com

1. To verify if the authentication configuration is set correctly, click Test Connection to check whether the PX2 can connect to the new server successfully.
   Tip: You can also test the connection on the Authentication page after finishing adding servers. See Managing External Authentication Settings (on page 254).

2. Click Add Server. The new LDAP server is listed on the Authentication page.

3. To add more servers, repeat the same steps.
4. In the Authentication Type field, select LDAP. Otherwise, the LDAP authentication does not work.
5. Click Save. The LDAP authentication is now in place.

To duplicate LDAP/LDAPS server settings:

If you have added any LDAP/LDAPS server to the PX2, and the server you will add shares identical settings with an existing one, the most convenient way is to duplicate that LDAP/LDAPS server's data and then revise the IP address/host name.

1. Repeat Steps 1 to 2 in the above procedure.
2. Select the "Copy settings from existing LDAP server" checkbox.
3. Click the "Select LDAP Server" field to select the LDAP/LDAPS server whose settings you want to copy.
4. Modify the IP Address/Hostname field.
5. Click Add Server.

Note: If the PX2 clock and the LDAP server clock are out of sync, the installed TLS certificates, if any, may be considered expired. To ensure proper synchronization, administrators should configure the PX2 and the LDAP server to use the same NTP server(s).

Adding Radius Servers

To use Radius authentication, enable it and enter the information you have gathered.

Note that you must enter information in the fields showing the message 'required.'

required

To add Radius servers:

1. Choose Device Settings > Security > Authentication.
2. Click New in the Radius section.
3. Enter information.

Field/setting Description
IP Address / Hostname	The IP address or hostname of your Radius server.
Type of RADIUS Authentication	Select an authentication protocol.PAP (Password Authentication Protocol)CHAP (Challenge Handshake Authentication Protocol)MS-CHAPv2 (Microsoft Challenge Handshake Authentication Protocol)CHAP is generally considered more secure because the user name and password are encrypted, while in PAP they are transmitted in the clear.MS-CHAPv2 provides stronger security than the above two. Selecting this option will support both MS-CHAPv1 and MS-CHAPv2.
Authentication Port, Accounting Port	The defaults are standard ports -- 1812 and 1813.To use non-standard ports, type a new port number.
Timeout This sets the	maximum amount of time to establish contact with the Radius server before timing out.Type the timeout period in seconds.
Retries Type the number of retries.
Shared Secret, Confirm Shared Secret	The shared secret is necessary to protect communication with the Radius server.

1. To verify if the authentication configuration is set correctly, click Test Connection to check whether the PX2 can connect to the new server successfully.

Tip: You can also test the connection on the Authentication page after finishing adding servers. See Managing External Authentication Settings (on page 254).

1. Click Add Server. The new Radius server is listed on the Authentication page.
2. To add more servers, repeat the same steps.
3. In the Authentication Type field, select Radius. Otherwise, the Radius authentication does not work.
4. Click Save. Radius authentication is now in place.

Managing External Authentication Settings

Choose Device Settings > Security > Authentication to open the Authentication page, where you can:

• Enable both the external and local authentication
• Edit or delete a server
• Resort the access order of servers
• Test the connection to a server
• Disable external authentication without removing servers

To test, edit or delete a server, or resort the server list:

1. Select a server in the list.

Access Order	IP Address / Hostname	Security	Port	LDAP Server Type
1	192.168.91.100	None	389	OpenLDAP
2	192.168.1.33	StartTLS	389	OpenLDAP
3	192.168.8.95	None	389	Microsoft Active Directory

1. Perform the desired action.

2. Click Edit to edit its settings, and click Modify Server to save changes. For information on each field, see Adding LDAP/LDAPS Servers (on page 249) or Adding Radius Servers (on page 252).

3. Cl ick Delete to delete the server, and then confirm the operation.
4. Click Test Connection to verify the connection to the selected server. User credentials may be required.

- Click or to change the server order, which determines the access priority, and click Save Order to save the new sequence.

Note: Whenever PX2 is successfully connected to one external authentication server, it STOPS trying access to remaining servers in the authentication list regardless of the user authentication result.

To enable both external and local authentication:

1. In the Authentication Type field, select the external authentication you want -- LDAP or Radius.
2. Select the following checkbox. Then the PX2 always tries external authentication first. Whenever the external authentication fails, the PX2 switches to local authentication.

Use Local Authentication if Remote Authentication is not available

1. Click Save.

To disable external authentication:

1. In the Authentication Type, select Local.
2. Click Save.

Configuring Login Settings

Choose Device Settings > Security > Login Settings to open the Login Settings page, where you can:

- Configure the user blocking feature.

Note: The user blocking function applies only to local authentication instead of external authentication through AA servers.

• Determine the timeout period for any inactive user.
• Prevent simultaneous logins using the same login name.

▶ To configure user blocking:

1. To enable the user blocking feature, select the "Block user on login failure" checkbox.
2. In the "Block timeout" field, type a value or click ▼ to select a time option. This setting determines how long the user is blocked.

If you type a value, the value must be followed by a time unit, such as '4 min.' See Time Units (on page 112).

1. In the "Maximum number of failed logins" field, type a number. This is the maximum number of login failure the user is permitted before the user is blocked from accessing the PX2.
2. Click Save.

Tip: If any user blocking event occurs, you can unblock that user manually by using the "unblock" CLI command over a local connection. See Unblocking a User (on page 566).

To set limitations for login timeout and use of identical login names:

1. In the "Idle timeout period" field, type a value or click ▼ to select a time option. This setting determines how long users are permitted to stay idle before being forced to log out.

If you type a value, the value must be followed by a time unit, such as '4 min.' See Time Units (on page 112).

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

1. Select the "Prevent concurrent login with same username" checkbox if intending to prevent multiple persons from using the same login name simultaneously.
2. Click Save.

Configuring Password Policy

Choose Device Settings > Security > Password Policy to open the Password Policy page, where you can:

• Force users to use strong passwords.
• Force users to change passwords at a regular interval -- that is, password aging.

Use of strong passwords makes it more difficult for intruders to crack user passwords and access the PX2.

To configure password aging:

1. Select the 'Enabled' checkbox of Password Aging.

2. In the Password Aging Interval field, type a value or click ▼ to select a time option. This setting determines how often users are requested to change their passwords.

If you type a value, the value must be followed by a time unit, such as '10 d.' See Time Units(on page 112).

1. Click Save.

To force users to create strong passwords:

1. Select the 'Enabled' checkbox of Strong Passwords to activate the strong password feature. The following are the default settings:

Minimum length = 8 characters

Maximum length = 32 characters

At least one lowercase character = Required

At least one uppercase character = Required

At least one numeric character = Required

At least one special character = Required

Number of forbidden previous passwords = 5

Note: The maximum password length accepted by PX2 is 64 characters.

1. Make changes to the default settings as needed.
2. Click Save.

Enabling the Restricted Service Agreement

The restricted service agreement feature, if enabled, forces users to read a security agreement when they log in to the PX2.

Users must accept the agreement, or they cannot log in.

An event notifying you if a user has accepted or declined the agreement can be generated. See Default Log Messages(on page 269)

To enable the service agreement:

1. Click Device Settings > Security > Service Agreement.
2. Select the Enforce Restricted Service Agreement checkbox.
3. Edit or paste the content as needed.

- A maximum of 10,000 characters can be entered.

1. Click Save.

Login manner after enabling the service agreement:

After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen.

Raritan® A brand of legrand Unauthorized access prohibited; all access and activities not explicitly authorized by management are unauthorized. All activities are monitored and logged. There is no privacy on this system. Unauthorized access and activities or any criminal activity will be reported to appropriate authorities. I understand and accept the Restricted Service Agreement User Name Password Login

Do either of the following, or the login fails:

- In the web interface, select the checkbox labeled "I understand and accept the Restricted Service Agreement."

Tip: To select the agreement checkbox using the keyboard, first press Tab to go to the checkbox and then Enter.

- In the CLI, type y when the confirmation message "I understand and accept the Restricted Service Agreement" is displayed.

Setting the Date and Time

Set the internal clock on the PX2 manually, or link to a Network Time Protocol (NTP) server.

Note: If you are using Sunbird's Power IQ to manage the PX2, you must configure Power IQ and the PX2 to have the same date/time or NTP settings.

To set the date and time:

1. Choose Device Settings > Date/Time.

2. Click the Time Zone field to select your time zone from the list.

3. If the daylight saving time applies to your time zone, verify the Automatic Daylight Saving Time Adjustment checkbox is selected.

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

1. Select the method for setting the date and time.

Customize the date and time

• Select User Specified Time.
• Type values in the Date field using the yyyy-mm-dd format, or click a date. For details, see Calendar (on page 260).
  ■ Determine the time format you want by clicking 12H or 24H button.

■ 12H represents the 12-hour format.

■ 24H represents the 24-hour format.

07 : 24 : 55 PM 12H

to select

- If selecting 12-hour format, then determine the current period by clicking the AM or PM button.

07 : 24 : 55 PM 12H

- Type values in the Time field using the hh:mm:ss format, or click to adjust values.

- When 12H is being applied, the hour cannot exceed the maximum number 12. If exceeding 12, the time change cannot be saved.

Use the NTP server

• Select "Synchronize with NTP server."
  ■ There are two ways to assign the NTP servers:

• To use the DHCP-assigned NTP servers, DO NOT enter any NTP servers for the First and Second time server.
  DHCP-assigned NTP servers are available only when either IPv4 or IPv6 DHCP is enabled.

- To use the manually-specified NTP servers, specify the primary NTP server in the "First time server" field. A secondary NTP server is optional.

Click Check NTP Servers to verify the validity and accessibility of the manually-specified NTP servers.

5. Click Save.

PX2 follows the NTP server sanity check per the IETF RFC. If your PX2 has problems synchronizing with a Windows NTP server, see Windows NTP Server Synchronization Solution (on page 261).

Calendar

The calendar icon

in the Date field is a convenient tool to select a calendar similar to the following appears.

July 2017 Sun Mon Tue Wed Thu Fri Sat 26 25 26 27 28 29 30 01 27 02 03 04 05 06 07 08 28 09 10 11 12 13 14 15 29 16 17 18 19 20 21 22 30 23 24 25 26 27 28 29 31 30 31 01 02 03 04 05 Today Clear Close ③ ④ ⑤

Number	Item Description
1	arrows	Switch between months.
2		dates(01-31)All dates of the selected month. To select a date, simply click it.
3	Today	Select today's date.
4	Clear	Clear the entry, if any, in the Date field.
5	Close	Close the calendar.

Windows NTP Server Synchronization Solution

The NTP client on the PX2 follows the NTP RFC so the PX2 rejects any NTP servers whose root dispersion is more than one second. An NTP server with a dispersion of more than one second is considered an inaccurate NTP server by the PX2.

Note: For information on NTP RFC, visit http://tools.ietf.org/html/rfc4330 - http://tools.ietf.org/html/rfc4330 to refer to section 5.

Windows NTP servers may have a root dispersion of more than one second, and therefore cannot synchronize with the PX2. When the NTP synchronization issue occurs, change the dispersion settings to resolve it.

To change the Windows NTP's root dispersion settings:

1. Access the registry settings associated with the root dispersion on the Windows NTP server.
   HKEY_LOCAL_MACHINE|SYSTEM|CurrentControlSet|Services|W32Time|Config
2. AnnounceFlags must be set to 0x05 or 0x06.
3. 0x05 = 0x01 (Always time server) and 0x04 (Always reliable time server)
4. 0x06 = 0x02 (Automatic time server) and 0x04 (Always reliable time server)

Note: Do NOT use 0x08 (Automatic reliable time server) because its dispersion starts at a high value and then gradually decreases to one second or lower.

1. LocalClockDispersion must be set to 0.

Event Rules and Actions

A benefit of the product's intelligence is its ability to notify you of or react to a change in conditions. This event notification or reaction is an "event rule."

An event rule consists of two parts:

• Event: This is the situation where the PX2 or a device connected to it meets a certain condition. For example, the inlet's voltage reaches the warning level.
• Action: This is the response to the event. For example, the PX2 notifies the system administrator of the event via email.

If you want the PX2 to perform one action at a regular interval instead of waiting until an event occurs, you can schedule that action. For example, you can make the PX2 email the temperature report every hour.

Note that you need the Administrator Privileges to configure event rules.

To create an event rule:

1. Choose Device Settings > Event Rules.

2. If the needed action is not available yet, create it by clicking

+ New Action.

a. Assign a name to this action.
b. Select the desired action and configure it as needed.
c. Click Create.

For details, see Available Actions (on page 284).

1. Click + New Rule to create a new rule.

a. Assign a name to this rule.
b. Make sure the Enabled checkbox is selected, or the new event rule does not work.
c. In the Event field, select the event to which you want the PX2 to react.
d. In the Available Actions field, select the desired action(s) to respond to the selected event.
e. Click Create.

For details, see Built-in Rules and Rule Configuration (on page 263).

To create a scheduled action:

1. If the needed action is not available yet, create it by clicking

+ New Action. See above.

Note: When creating scheduled actions, available actions are less than usual because it is meaningless to schedule certain actions like "Alarm," "Log event message," "Send email," "Syslog message" and the like.

1. Click + New Scheduled Action to schedule the desired action.

a. Assign a name to this scheduled action.
b. Make sure the Enabled checkbox is selected, or the PX2 does not perform this scheduled action.
c. Set the interval time, which ranges from every minute to yearly.
d. In the Available Actions field, select the desired action(s).
e. Click Create.
For details, see Scheduling an Action (on page 304).

Built-in Rules and Rule Configuration

PX2 is shipped with four built-in event rules, which cannot be deleted. If the built-in event rules do not satisfy your needs, create new rules.

Built-in rules:

• System Event Log Rule:

This causes ANY event occurred to the PX2 to be recorded in the internal log. It is enabled by default.

Note: For the default log messages generated for each event, see Default Log Messages (on page 269).

• System SNMP Notification Rule:

This causes SNMP traps or informs to be sent to specified IP addresses or hosts when ANY event occurs to the PX2. It is disabled by default.

• System Tamper Detection Alarmed:

This causes the PX2 to send alarm notifications if a DX tamper sensor has been connected and the PX2 detects that the tamper sensor enters the alarmed state. It is enabled by default.

• System Tamper Detection Unavailable:

This causes the PX2 to send alarm notifications if a DX tamper sensor was once connected or remains connected but then the PX2 does not detect the presence of the tamper sensor. It is enabled by default.

▶ Event rule configuration illustration:

1. Choose Device Settings > Event Rules >

New Rule.

1. Click the Event field to select an event type.

2. means all events shown on the list.

3. means all numeric sensors of the PX2, including internal and environmental sensors. is especially useful if you want to receive the notifications when any numeric sensor's readings pass through a specific threshold.

Event

1. In this example, the Peripheral Device Slot is selected, which is related to the environmental sensor packages. Then a sensor ID field for this event type appears. Click this additional field to specify which sensor should be the subject of this event.

Event Peripheral Device Slot

1. In this example, sensor ID 3 (Slot 3) is selected, which is a temperature sensor. Then a new field for this sensor appears. Click this field to specify the type of event(s) you want.

Event Peripheral Device Slot Slot 3 (Temperature 2)

1. In this example, Numeric Sensor is selected because we want to select numeric-sensor-related event(s). Then a field for numeric-sensor-related events appears. Click this field to select one of the numeric-sensor-related events from the list.

Event Peripheral Device Slot Slot 3 (Temperature 2) Numeric Sensor

1. In this example, 'Above upper critical threshold' is selected because we want the PX2 to react only when the selected temperature sensor's reading enters the upper critical range. A "Trigger condition" field appears, requiring you to define the "exact" condition related to the "upper critical" event.

Event Peripheral Device Slot Slot 3 (Temperature 2) Numeric Sensor Above upper critical threshold Trigger condition Asserted Deasserted Both

1. Select the desired radio button to finish the event configuration. Refer to the following table for different types of radio buttons.
2. If needed, you may refer to event rule examples in the section titled Sample Event Rules (on page 315).
3. To select any action(s), select them one by one from the Available Actions list.
4. To select all available actions, click Select All.
5. To remove any action(s) from the Selected Actions field, click that action's ✗.
   ■ To remove all actions, click Deselect All.

Radio buttons for different events:

According to the event you select, the "Trigger condition" field containing three radio buttons may or may not appear.

Event types Radio buttons

Numeric sensor threshold-crossing events, or the occurrence of the selected event -- true or false	Available radio buttons include "Asserted," "Deasserted" and "Both." Asserted: PX2 takes the action only when the selected event occurs. That is, the status of the event transits from FALSE to TRUE. Deasserted: PX2 takes the action only when the selected event disappears or stops. That is, the status of the selected event transits from TRUE to FALSE. Both: PX2 takes the action both when the event occurs (asserts) and when the event stops/disappears (deasserts).
State sensor state change	Available radio buttons include "Alarmed/Open/On," "No longer alarmed/Closed/Off" and "Both." Alarmed/Open/On: PX2 takes the action only when the chosen sensor enters the alarmed, open or on state. No longer alarmed/Closed/Off: PX2 takes the action only when the chosen sensor returns to the normal, closed, or off state. Both: PX2 takes the action whenever the chosen sensor switches its state.
Sensor availability	Available radio buttons include "Unavailable," "Available" and "Both." Unavailable: PX2 takes the action only when the chosen sensor is NOT detected and becomes unavailable. Available: PX2 takes the action only when the chosen sensor is detected and becomes available. Both: PX2 takes the action both when the chosen sensor becomes unavailable or available.
Event types Radio buttons
Network interface link state	Link state is up: PX2 takes the action only when the network link state changes from down to up.Link state is down: PX2 takes the action only when the network link state changes from up to down.Both: PX2 takes the action whenever the network link state changes.
Function enabled or disabled	Enabled: PX2 takes the action only when the chosen function is enabled leveld: PX2 takes the action only when the chosen function is disabled.Both: PX2 takes the action when the chosen function is either enabled or disabled.
Restricted service agreement	Accepted: PX2 takes the action only when the specified user accepts the restricted service agreement.Declined: PX2 takes the action only when the specified user rejects the restricted service agreement.Both: PX2 takes the action both when the specified user accepts or rejects the restricted service agreement.
Server monitoring event	Monitoring started: PX2 takes the action only when the monitoring of any specified server starts.Monitoring stopped: PX2 takes the action only when the monitoring of any specified server stops.Both: PX2 takes the action when the monitoring of any specified server starts or stops.
Server reachability	Unreachable: PX2 takes the action only when any specified server becomes inaccessible.Reachable: PX2 takes the action only when any specified server becomes accessible.Both: PX2 takes the action when any specified server becomes either inaccessible or accessible.

Event types Radio buttons

Device connection or disconnection, such as a USB-cascaded slave device

■ Connected: PX2 takes the action only when the selected device is physically connected to it.■ Disconnected: PX2 takes the action only when the selected device is physically disconnected from it.■ Both: PX2 takes the action both when the selected device is physically connected to it and when it is disconnected.

Default Log Messages

These default log messages are recorded internally and emailed to specified recipients when PX2 events occur (are TRUE) or, in some cases, stop or become unavailable (are FALSE). See Send Email (on page 292) to configure email messages.

Event/context Default message when the event = TRUE		Default message when the event = FALSE
Asset Management > State State of asset strip [AMSNUMBER]('[AMSNAME]') changed to '[AMSSTATE]'.
Asset Management > Rack Unit > * > Tag Connected	Asset tag with ID '[AMSTAGID]' connected at rack unit [AMSRACKUNITPOSITION], slot [AMSBLADESLOTPOSITION] of asset strip [AMSNUMBER] ('[AMSNAME]').	Asset tag with ID '[AMSTAGID]' disconnected at rack unit [AMSRACKUNITPOSITION], slot [AMSBLADESLOTPOSITION] of asset strip [AMSNUMBER] ('[AMSNAME]').
Asset Management > Rack Unit > * > Blade Extension Connected	Blade extension with ID '[AMSTAGID]' connected at rack unit [AMSRACKUNITPOSITION] of asset strip [AMSNUMBER] ('[AMSNAME]').	Blade extension with ID '[AMSTAGID]' disconnected at rack unit [AMSRACKUNITPOSITION] of asset strip [AMSNUMBER] ('[AMSNAME]').
Asset Management > Firmware Update	Firmware update for asset strip [AMSNUMBER] ('[AMSNAME]'): status changed to '[AMSSTATE]'.
Asset Management > Device Config Changed	Config parameter '[CONFIGPARAM]' of asset strip [AMSNUMBER] ('[AMSNAME]') changed to '[CONFIGVALUE]' by user '[USERNAME'].
Asset Management > Rack Unit Config Changed	Config of rack unit [AMSRACKUNITPOSITION] of asset strip [AMSNUMBER] ('[AMSNAME]') changed by user '[USERNAME]' to: Name '[AMSRACKUNITNAME]', LED Operation Mode '[AMSLEDOPMODE]', LED Color '[AMSLEDCOLOR]', LED Mode '[AMSLEDMODE]
Asset Management > Blade Extension Overflow	Blade extension overflow occurred on strip [AMSNUMBER] ('[AMSNAME]').	Blade extension overflow cleared for strip [AMSNUMBER] ('[AMSNAME]').
Asset Management > Composite Asset Strip Composition Changed	Composition changed on composite asset strip [AMSNUMBER] ('[AMSNAME]').
Card Reader Management > Card Reader > * > Card inserted	Card of type '[SMARTCARDTYPE]' with ID '[SMARTCARDID]' inserted at Card Reader '[CARDREADERID]'.
Card Reader Management > Card Reader attached	Card Reader with id '[CARDREADERID]' disconnected.
Card Reader Management > Card Reader detached	Card of type '[SMARTCARDTYPE]' with ID '[SMARTCARDID]' inserted.
Card Reader Management > Card Reader > * > Card removed	Card of type '[SMARTCARDTYPE]' with ID '[SMARTCARDID]' removed at Card Reader '[CARDREADERID]'.
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 > Hardware failure present	Failure '[FAILURETYPESTR]' asserted for component '[COMPONENTID]'.	Failure '[FAILURETYPESTR]' deasserted for component '[COMPONENTID]'.
Device > Device identification changed	Config parameter '[CONFIGPARAM]' changed to '[CONFIGVALUE]' by user '[USERNAME]' from host '[USERIP]'.
Device > Device settings saved	Device settings saved by user '[USERNAME]' from host '[USERIP]'.
Device > Device settings restored	Device settings restored from host '[USERIP]'.
Device > Data push failed Data push to URL [DATAPUSH_URL] failed. [ERRORDESC].
Device > Event log cleared Event log cleared by user '[USERNAME]' from host '[USERIP]'.
Device > Bulk configuration saved	Bulk configuration saved by user '[USERNAME]' from host '[USERIP]'.
Device > Bulk configuration copied	Bulk configuration copied by user '[USERNAME]' 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 > Peripheral Device Firmware Update	Firmware update for peripheral device [EXTSENSORSERIAL] from [OLDVERSION] to [VERSION] [SENSORSTATENAME].
Device > Sending SMTP message failed	Sending SMTP message to '[SMTPRECIPIENTS]' using server '[SMTPSERVER]' failed. [ERRORDESC].
Device > Sending SNMP inform failed or no response	Sending SNMP inform to manager [SNMPMANAGER]:[SNMPMANAGERPORT] failed or no response. [ERRORDESC].
Device > Sending Syslog message failed	Sending Syslog message to server [SYSLOGSERVER]:[SYSLOGPORT] ([SYSLOGTRANSPORTPROTO]) failed. [ERRORDESC].
Device > Sending SMS message failed	Sending SMS message to '[PHONENUMBER]' failed.
Device > An LDAP error occurred	An LDAP error occurred: [ERRORDESC].
Device > A Radius error occurred	A Radius error occurred: [ERRORDESC].
Device > Raw configuration downloaded	Raw configuration downloaded by user '[USERNAME]' from host '[USERIP]'.
Device > Raw configuration updated	Raw configuration updated by user '[USERNAME]' from host '[USERIP]'.
Device > Unknown peripheral device attached	An unknown peripheral device with rom code '[ROMCODE]' was attached at position '[PERIPHDEVPOSITION]'.
Device > Slave connected Slave connected. Slave disconnected.
Device > WLAN authentication over TLS with incorrect system clock	Established connection to wireless network '[SSID]' via Access Point with BSSID '[BSSID]' using '[AUTHPROTO]' authentication with incorrect system clock.
Device > Features > Schroff LHX / SHX Support	Schroff LHX / SHX support enabled. Schroff LHX / SHX support disabled.
Energywise > Enabled User '[USERNAME]' from host '[USERIP]' enabled EnergyWise.		User '[USERNAME]' from host '[USERIP]' disabled EnergyWise.
Peripheral Device Slot > * > Numeric Sensor > Unavailable	Peripheral device'[EXTSENSORNAME]' in slot'[EXTSENSORSLOT]' unavailable.	Peripheral device'[EXTSENSORNAME]' in slot'[EXTSENSORSLOT]' available.
Peripheral Device Slot > * > Numeric Sensor > Above upper critical threshold	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] asserted 'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] deasserted 'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].
Peripheral Device Slot > * > Numeric Sensor > Above upper warning threshold	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] asserted 'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] deasserted 'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].
Peripheral Device Slot > * > Numeric Sensor > Below lower warning threshold	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] asserted 'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] deasserted 'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].
Peripheral Device Slot > * > Numeric Sensor > Below lower critical threshold	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] asserted 'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] deasserted 'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].
Peripheral Device Slot > * > State Sensor/Actuator > Unavailable	Peripheral device'[EXTSENSORNAME]' in slot'[EXTSENSORSLOT]' unavailable.	Peripheral device'[EXTSENSORNAME]' in slot'[EXTSENSORSLOT]' available.
Peripheral Device Slot > * > State Sensor/Actuator > Alarmed/Open/On	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] is[SENSORSTATENAME].	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] is[SENSORSTATENAME].
Peripheral Device Slot > * > State Sensor/Actuator > Switched by user	Peripheral device'[EXTSENSORNAME]' in slot[EXTSENSORSLOT] has been switched to [SENSORSTATENAME] by user'[USERNAME]' from host.

Event/context Default message when the event = TRUE	Default message when the event = FALSE
Inlet > * > Enabled Inlet '[INLET]' has been enabled by user '[USERNAME]' from host '[USERIP]'.	Inlet '[INLET]' has been disabled by user '[USERNAME]' from host '[USERIP]'.
Inlet > * > Sensor > * > Unavailable	Sensor '[INLETSENSOR]' on inlet '[INLET]' unavailable.
Inlet > * > Sensor > * > Above upper critical threshold	Sensor '[INLETSENSOR]' on inlet '[INLET]' asserted 'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].
Inlet > * > Sensor > * > Above upper warning threshold	Sensor '[INLETSENSOR]' on inlet '[INLET]' asserted 'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].
Inlet > * > Sensor > * > Below lower warning threshold	Sensor '[INLETSENSOR]' on inlet '[INLET]' asserted 'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].
Inlet > * > Sensor > * > Below lower critical threshold	Sensor '[INLETSENSOR]' on inlet '[INLET]' asserted 'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].
Inlet > * > Sensor > * > Reset Sensor '[INLETSENSOR]' on inlet '[INLET]' has been reset by user '[USERNAME]' from host '[USERIP]'.
Inlet > * > Sensor > * > Normal Sensor '[INLETSENSOR]' on inlet '[INLET]' entered normal state.	Sensor '[INLETSENSOR]' on inlet '[INLET]' exited normal state.
Inlet > * > Sensor > * > Failed Sensor '[INLETSENSOR]' on inlet '[INLET]' entered failed state.	Sensor '[INLETSENSOR]' on inlet '[INLET]' entered normal state.
Inlet > * > Sensor > * > OK Sensor '[INLETSENSOR]' on inlet '[INLET]' entered OK state.	Sensor '[INLETSENSOR]' on inlet '[INLET]' exited OK state.
Inlet > * > Sensor > * > Warning Sensor '[INLETSENSOR]' on inlet '[INLET]' entered warning state.	Sensor '[INLETSENSOR]' on inlet '[INLET]' exited warning state.
Inlet > * > Sensor > * > Critical Sensor '[INLETSENSOR]' on inlet '[INLET]' entered critical state.	Sensor '[INLETSENSOR]' on inlet '[INLET]' exited critical state.
Inlet > * > Sensor > * > Self-Test Sensor '[INLETSENSOR]' on inlet '[INLET]' started self test.	Sensor '[INLETSENSOR]' on inlet '[INLET]' finished self test.

Event/context Default message when the event = TRUE		Default message when the event = FALSE
Inlet > Pole > * > Sensor > Unavailable	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' unavailable.	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' available.
Inlet > Pole > * > Sensor > Above upper critical threshold	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' asserted 'above upper critical' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' deasserted 'above upper critical' at [SENSORREADING] [SENSORREADINGUNIT].
Inlet > Pole > * > Sensor > Above upper warning threshold	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' asserted 'above upper warning' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' deasserted 'above upper warning' at [SENSORREADING] [SENSORREADINGUNIT].
Inlet > Pole > * > Sensor > Below lower warning threshold	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' asserted 'below lower warning' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' deasserted 'below lower warning' at [SENSORREADING] [SENSORREADINGUNIT].
Inlet > Pole > * > Sensor > Below lower critical threshold	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' asserted 'below lower critical' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' deasserted 'below lower critical' at [SENSORREADING] [SENSORREADINGUNIT].
Inlet > Pole > * > Sensor > Normal	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' entered normal state.	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' exited normal state.
Inlet > Pole > * > Sensor > Failed	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' entered failed state.	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' exited failed state.
Inlet > Pole > * > Sensor > Warning	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' entered warning state.	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' exited warning state.
Inlet > Pole > * > Sensor > Critical	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' entered critical state.	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' exited critical state.
Inlet > Pole > * > Sensor > Self-Test	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' started self test.	Sensor '[PDUPOLESENSOR]' on pole '[INLETPOLE]' of inlet '[INLET]' finished self test.

Chapter 6: Using the Web Interface

Event/context Default message when the event = TRUE		Default message when the event = FALSE
Modem > Dial-in link established	An incoming call from caller '[CALLERID]' was received.	The incoming call from caller '[CALLERID]' was disconnected: [CALLENDREASON].
Modem > Modem attached A [MODEMTYPE] modem was attached.
Modem > Modem detached A [MODEMTYPE] modem was removed.
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' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'above upper critical' at [SENSORREADING] [SENSORREADINGUNIT].
Outlet > * > Sensor > * > Above upper warning threshold	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' asserted 'above upper warning' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'above upper warning' at [SENSORREADING] [SENSORREADINGUNIT].
Outlet > * > Sensor > * > Below lower warning threshold	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' asserted 'below lower warning' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'below lower warning' at [SENSORREADING] [SENSORREADINGUNIT].
Outlet > * > Sensor > * > Below lower critical threshold	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' asserted 'below lower critical' at [SENSORREADING]	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'below lower critical' at [SENSORREADING]

Event/context Default message when the event = TRUE	Default message when the event = FALSE
	[SENSORREADINGUNIT]. [SENSORREADING] [SENSORREADINGUNIT].
Outlet > * > Sensor > Active Energy > Reset	Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' has been reset by user '[USERNAME]' from host '[USERIP]'.
Outlet > * > Sensor > Outlet State > On/Off	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.
Outlet > * > Pole > * > Sensor > Above upper critical threshold	Sensor '[PDUPOLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'above upper critical' at [SENSORREADING] [SENSORREADINGUNIT].
Outlet > * > Pole > * > Sensor > Above upper warning threshold	Sensor '[PDUPOLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'above upper warning' at [SENSORREADING] [SENSORREADINGUNIT].
Outlet > * > Pole > * > Sensor > Below lower warning threshold	Sensor '[PDUPOLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'below lower warning' at [SENSORREADING] [SENSORREADINGUNIT].
Outlet > * > Pole > * > Sensor > Below lower critical threshold	Sensor '[PDUPOLESENSOR]' on pole '[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'below lower critical' at [SENSORREADING] [SENSORREADINGUNIT].
Outlet Grouping > Outlet Group > * > Outlet Group Modified	Outlet group '[OUTLETGROUPID]' was modified.
Outlet Grouping > Outlet Group > * > Power control > Power cycled	Outlet group '[OUTLETGROUPID]' power cycle initiated by user '[USERNAME]' from host '[USERIP]'.

Event/context Default message when the event = TRUE		Default message when the event = FALSE
Outlet Grouping > Outlet Group > * > Power control > Powered off	Outlet group '[OUTLETGROUPID]' has been powered off by user '[USERNAME]' from host '[USERIP]'.
Outlet Grouping > Outlet Group > * > Power control > Powered on	Outlet group '[OUTLETGROUPID]' has been powered on by user '[USERNAME]' from host '[USERIP]'.
Outlet Grouping > Outlet Group > * > Sensor > Above upper critical threshold	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' asserted 'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' deasserted 'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].
Outlet Grouping > Outlet Group > * > Sensor > Above upper warning threshold	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' asserted 'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' deasserted 'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].
Outlet Grouping > Outlet Group > * > Sensor > Below lower critical threshold	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' asserted 'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' deasserted 'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].
Outlet Grouping > Outlet Group > * > Sensor > Below lower warning threshold	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' asserted 'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' deasserted 'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].
Outlet Grouping > Outlet Group > * > Sensor > Unavailable	Sensor '[OUTLETGROUPSENSOR]' of outlet group '[OUTLETGROUPID]' unavailable.	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' available.
Outlet Grouping > Outlet Group > * > Sensor > Reset	Sensor '[OUTLETGROUPSENSOR]' on outlet group '[OUTLETGROUPID]' has been reset by user '[USERNAME]' from host '[USERIP]'.
Outlet Grouping > Outlet Group Created	Outlet group '[OUTLETGROUPID]' was created.
Outlet Grouping > Outlet Group Deleted	Outlet group '[OUTLETGROUPID]' was deleted.
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' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'above upper critical' at [SENSORREADING] [SENSORREADINGUNIT].
Overcurrent Protector > * > Sensor > * > Above upper warning threshold	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'above upper warning' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'above upper warning' at [SENSORREADING] [SENSORREADINGUNIT].
Overcurrent Protector > * > Sensor > * > Below lower warning threshold	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'below lower warning' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'below lower warning' at [SENSORREADING] [SENSORREADINGUNIT].
Overcurrent Protector > * > Sensor > * > Below lower critical threshold	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'below lower critical' at [SENSORREADING] [SENSORREADINGUNIT].	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'below lower critical' at [SENSORREADING] [SENSORREADINGUNIT].
Overcurrent Protector > * > Sensor > Trip > Open/Close	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' is open.	Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' is closed.
PDU > Controller > * > Communication failed	Communication with controller '[CONTROLLER]' (board ID [BOARDID]) failed.	Communication with controller '[CONTROLLER]' (board ID [BOARDID]) restored.
PDU > Controller > * > Firmware update	Controller '[CONTROLLER]' with board ID [BOARDID] has started firmware update	Controller '[CONTROLLER]' with board ID [BOARDID] has completed firmware update
PDU > Controller > * > Incompatible	Controller '[CONTROLLER]' with board ID [BOARDID] is incompatible.	Controller '[CONTROLLER]' with board ID [BOARDID] is no longer incompatible.

Event/context Default message when the event = TRUE	Default message when the event = FALSE
PDU > Controller > * > OK Controller '[CONTROLLER]' with board ID [BOARDID] is OK.	Controller '[CONTROLLER]' with board ID [BOARDID] is no longer OK.
PDU > Load Shedding > Started PX placed in Load Shedding Mode by user '[USERNAME]' from host '[USERIP]'.	PX removed from Load Shedding Mode by user '[USERNAME]' from host '[USERIP]'.
Server Monitoring > * > Error Error monitoring server '[MONITOREDHOST]': [ERRORDESC]
Server Monitoring > * > Monitored	Server '[MONITOREDHOST]' is now being monitored.
Server Monitoring > [MONITOREDHOST] > Power control completed	Power control operation for '[MONITOREDHOST]' finished with result: [SERVERPOWERRESULT]
Server Monitoring > [MONITOREDHOST] > Power control initiated	User '[USERNAME]' initiated a power control operation for '[MONITOREDHOST]': [SERVERPOWEROPERATION]
Server Monitoring > * > Unreachable	Server '[MONITOREDHOST]' is unreachable.
Server Monitoring > * > Unrecoverable	Connection to server '[MONITOREDHOST]' could not be restored.
User Activity > * > User logon state	User '[USERNAME]' from host '[USERIP]' logged in.
User Activity > * > Authentication failure	Authentication failed for user '[USERNAME]' from host '[USERIP]'.
User Activity > * > User accepted the Restricted Service Agreement	User '[USERNAME]' from host '[USERIP]" accepted the Restricted Service Agreement.
User Activity > * > User blocked	User '[USERNAME]' from host '[USERIP]' was blocked.
User Activity > * > Session timeout	Session of user '[USERNAME]' from host '[USERIP]' timed out.
User Administration > User added	User '[UMTARGETUSER]' added by user '[USERNAME]' from host '[USERIP]'.

Event/context Default message when the event = TRUE		Default message when the event = FALSE
User Administration > User modified	User '[UMTARGETUSER]' modified by user '[USERNAME]' from host '[USERIP]'.
User Administration > User deleted	User '[UMTARGETUSER]' deleted by user '[USERNAME]' from host '[USERIP]'.
User Administration > Password changed	Password of user '[UMTARGETUSER]' 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 '[UMTARGETROLE]' added by user '[USERNAME]' from host '[USERIP]'.
User Administration > Role modified	Role '[UMTARGETROLE]' modified by user '[USERNAME]' from host '[USERIP]'.
User Administration > Role deleted	Role '[UMTARGETROLE]' deleted by user '[USERNAME]' from host '[USERIP]'.
Webcam Management > Webcam attached	Webcam '[WEBCAMNAME]' ('[WEBCAMUVCID]') added to port '[WEBCAMUSBPORT]'.
Webcam Management > Webcam detached	Webcam '[WEBCAMNAME]' ('[WEBCAMUVCID]') removed from port '[WEBCAMUSBPORT]'.
Webcam Management > Webcam settings changed	Webcam '[WEBCAMNAME]' settings changed by user '[USERNAME]'.
LHX/SHX > Connected LHX has been connected to [PORTTYPE] port [PORTID].		LHX has been disconnected from [PORTTYPE] port [PORTID].
LHX/SHX > Operational State LHX connected to [PORTTYPE] port [PORTID] has been switched on.		LHX connected to [PORTTYPE] port [PORTID] has been switched off.
LHX/SHX > Sensor > Unavailable	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' unavailable.	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' available.
LHX/SHX > Sensor > Above upper critical threshold	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' asserted 'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'above upper critical' at [SENSORREADING][SENSORREADINGUNIT].
LHX/SHX > Sensor > Above upper warning threshold	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' asserted 'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'above upper warning' at [SENSORREADING][SENSORREADINGUNIT].
LHX/SHX > Sensor > Below lower warning threshold	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' asserted 'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'below lower warning' at [SENSORREADING][SENSORREADINGUNIT].
LHX/SHX > Sensor > Below lower critical threshold	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' asserted 'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].	Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' deasserted 'below lower critical' at [SENSORREADING][SENSORREADINGUNIT].
LHX/SHX > Base Electronics Failure	The base electronics on LHX at [PORTTYPE] port '[PORTID]' failed.	The base electronics on LHX at [PORTTYPE] port '[PORTID]' is back to normal.
LHX/SHX > Condenser Pump Failure	The condenser pump on LHX at [PORTTYPE] port '[PORTID]' failed.	The condenser pump on LHX at [PORTTYPE] port '[PORTID]' is back to normal.
LHX/SHX > Emergency Cooling	Emergency cooling on LHX at [PORTTYPE] port '[PORTID]' was activated.	Emergency cooling on LHX at [PORTTYPE] port '[PORTID]' was deactivated.
LHX/SHX > 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/SHX > Parameter Data Loss	Data loss in parameter memory was detected on LHX at [PORTTYPE] port '[PORTID]'.
LHX/SHX > ST-Bus Communication Error	An ST-Bus communication error was detected on LHX at [PORTTYPE] port '[PORTID]',
LHX/SHX > Collective fault A collective fault occurred on LHX at [PORTTYPE] port '[PORTID]',
LHX/SHX > Door Contact The door of LHX at [PORTTYPE] port '[PORTID]' was opened.		The door of LHX at [PORTTYPE] port '[PORTID]' was closed.
LHX/SHX > Sensor Failure A sensor failure (broken or short circuit) occurred on LHX at [PORTTYPE] port '[PORTID]' at sensor '[LHXSENSORID'].
LHX/SHX > Fan Failure A fan motor failure occurred on LHX at [PORTTYPE] port '[PORTID]' at fan '[LHXFANID'].
LHX/SHX > Power Supply Failure	A power supply failure occurred on LHX at [PORTTYPE] port '[PORTID]' at power supply '[LHXPOWERSUPPLYID'].
LHX/SHX > 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/SHX > 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/SHX > 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/SHX > 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/SHX > Voltage Low The supply voltage on LHX at [PORTTYPE] port '[PORTID]' is low.		The supply voltage on LHX at [PORTTYPE] port '[PORTID]' is back to normal.
LHX/SHX > 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/SHX > External Water Cooling Failure	An external water cooling failure occurred on LHX at [PORTTYPE] port '[PORTID]',
LHX/SHX > Water Leak Water leakage	akage was detected on LHX at [PORTTYPE] port '[PORTID]',

The asterisk symbol (*) represents anything you select for the 'trigger' events.

Available Actions

The PX2 comes with three built-in actions, which cannot be deleted. You can create additional actions for responding to different events.

Built-in actions:

• System Event Log Action:
This action records the selected event in the internal log when the event occurs.
• System SNMP Notification Action:
This action sends SNMP notifications to one or multiple IP addresses after the selected event occurs.

Note: No IP addresses are specified for this notification action by default so you must enter IP addresses before applying this action to any event rule. See Editing or Deleting a Rule/Action (on page 314). Any changes made to the 'SNMP Notifications' section on the SNMP page will update the settings of the System SNMP Notification Action, and vice versa. See Configuring SNMP Settings (on page 228).

• System Tamper Alarm:

This action causes the PX2 to show the alarm for the DX tamper sensor, if any, on the Dashboard page until a person acknowledges it. By default, this action has been assigned to the built-in tamper detection event rules. For information on acknowledging an alarm, see Dashboard - Alarms (on page 106).

Actions you can create:

1. Choose Device Settings > Event Rules >

+ New Action

1. Click the Action field to select an action type from the list.

Action

-- Select an action type ▼

3. Below is the list of available actions.

Note: The "Change load shedding state", "Power control server", "Switch outlets" and "Switch outlet group" options are only available for outlet-switching capable models.

Action Function
Alarm Requires the user to acknowledge the alert after it is generated. If needed, you can have the alert notifications regularly generated until a person takes the acknowledgment action.See Alarm (on page 287).
Change load shedding state	Enters or quits the load shedding mode. See Change Load Shedding State (on page 288).
Execute an action group	Creates a group of actions comprising existing actions. See Action Group (on page 288).
External beeper Enables or disables the connected external beeper, or causes it to enter an alarm cycle.See External Beeper (on page 289).
Internal beeper Turns on or off the internal beeper. See Internal Beeper (on page 289).
Log event message Records the selected events in the internal log.See Log an Event Message (on page 290).
Power control server Two operations are available.Shuts down a monitored server and then powers off the outlet(s) associated with that server.Powers up the outlet(s) associated with a monitored server.See Shut down a Server and Control its Power (on page 290).
Push out sensor readings	Sends internal sensor log, environmental sensor log or asset management strip data to a remote server using HTTP POST requests. See Push Out Sensor Readings (on page 291).
Record snapshots to webcam storage	Makes a connected webcam start or stop taking snapshots. See Record Snapshots to Webcam Storage (on page 291).
Request LHX/SHX maximum cooling	Applies the maximum cooling to the LHX/SHX device. See Request LHX/SHX Maximum Cooling (on page 292).This option is available only when the Schroff LHX/SHX support has been enabled.
Send email Emails a textual message. See Send Email (on page 292).
Send sensor report Reports the readings or status of the selected sensors, including internal or external sensors. See Send Sensor Report (on page 294).
Send SMS message Sends a message to a mobile phone. See Send SMS Message (on page 296).
Send snapshots via email	Emails the snapshots captured by a connected Logitech® webcam (if available). See Send Snapshots via Email (on page 297).
Send SNMP notification	Sends SNMP traps or informs to one or multiple SNMP destinations. See Send an SNMP Notification (on page 298).
Start/stop Lua script If you are a developer who can create a Lua script, you can upload it to the PX2, and have the PX2 automatically perform or stop the script in response to an event. See Start or Stop a Lua Script (on page 300).
Switch LHX/SHX Switches on or off the LHX/SHX device. See Switch LHX/SHX (on page 301).This option is available only when the Schroff LHX/SHX support has been enabled.
Switch outlets Switches on, off or cycles the power to the specified outlet(s). See Switch Outlets (on page 301).
Switch outlet group Switches on, off or cycles the power to all outlets of the specified outlet group. See Switch Outlet Group (on page 301).
Switch peripheral actuator	Switches on or off the mechanism or system connected to the specified actuator. SeeSwitch Peripheral Actuator(on page 302).
Syslog message Makes	the PX2 automatically forward event messages to the specified syslog server. SeeSyslog Message(on page 303).

1. Enter the information as needed and click Create.
2. Then you can assign the newly-created action to an event rule or schedule it. See Event Rules and Actions(on page 262).

Alarm

The Alarm is an action that requires users to acknowledge an alert. This helps ensure that the user is aware of the alert.

If the Alarm action has been included in a specific event rule and no one acknowledges that alert after it occurs, the PX2 resends or regenerates an alert notification regularly until the alert is acknowledged or the maximum number of alert notifications is sent.

For information on acknowledging an alert, see Dashboard(on page 97).

▶ Operation:

1. Choose Device Settings > Event Rules >

+ New Action.

1. Select Alarm from the Action list.
2. In the Alarm Notifications list box, specify one or multiple ways to issue the alert notifications. Available methods vary, depending on how many notification-based actions have been created.

Notification-based action types include:

■ External beeper
- Syslog message
- Send email
- Send SMS message
- Internal beeper

If no appropriate actions are available, create them first.

a. To select any methods, select them one by one in the Available field.

To add all available methods, simply click Select All.

b. To delete any methods, click a method's ✗ in the Selected field.

To remove all methods, simply click Deselect All.

1. To enable the notification-resending feature, select the "Enable Re-scheduling of Alarm Notifications" checkbox.
2. In the "Re-scheduling Period" field, specify the time interval (in minutes) at which the alert notification is resent or regenerated regularly.
3. In the "Re-scheduling Limit" field, specify the maximum number of times the alert notification is resent. Values range from 1 to infinite.
4. (Optional) You can instruct the PX2 to send the acknowledgment notification after the alarm is acknowledged in the Acknowledgment Notifications field. Available methods are identical to those for generating alarm notifications.

a. In the Available field, select desired methods one by one, or click Select All. See step 3 for details.

b. In the Selected field, click any method's ✗ to remove unnecessary ones, or click Deselect All.

Action Group

You can create an action group that performs up to 32 actions. After creating such an action group, you can easily assign this set of actions to any event rule rather than selecting all needed actions one by one per rule.

If the needed action is not available yet, create it first. See Available Actions (on page 284).

Operation:

+ New Action.

1. Choose Device Settings > Event Rules >
2. Select "Execute an action group" from the Action list.
3. To select any action(s), select them one by one from the Available Actions list.

- To select all available actions, click Select All.

1. To remove any action(s) from the Selected Actions field, click that action's ✗.

- To remove all actions, click Deselect All.

Change Load Shedding State

The "Change load shedding state" action is available only when your PX2 is able to control outlet power. Use this action to activate or deactivate the load shedding mode for responding to a specific event. For additional information, see Load Shedding Mode (on page 126).

▶ Operation:

1. Choose Device Settings > Event Rules >

+ New Action

1. Select "Change load shedding state" from the Action list.

2. In the Operation field, select either one below:

3. Start Load Shedding: Enters the load shedding mode when the specified event occurs.

4. Stop Load Shedding: Quits the load shedding mode when the specified event occurs.

External Beeper

If an external beeper is connected to the PX2, the PX2 can change the beeper's behavior or status to respond to a certain event.

To control the connected external beeper:

+ New Action

1. Choose Device Settings > Event Rules >
2. Select "External beeper" from the Action list.
3. In the Beeper Port field, select the port where the external beeper is connected. This port is the FEATURE port.
4. In the Beeper Action field, select an action for the external beeper to carry out.

- Alarm: Causes the external beeper to sound an alarm cycle every 20 seconds - stays on for 0.7 seconds and then off for 19.3 seconds.

- On: Turns on the external beeper so that it buzzes continuously.

- Off: Turns off the external beeper so that it stops buzzing.

Warning: If you create an event rule for the external beeper but disconnect it when an event causes it to beep, the beeper no longer beeps after it is re-connected even though the event triggering the beeping action remains asserted.

Internal Beeper

You can have the built-in beeper of the PX2 turned on or off when a certain event occurs.

▶ Operation:

1. Choose Device Settings > Event Rules >

+ New Action

1. Select "Internal beeper" from the Action list.

2. Select an option from the Operation field.

■ Turn Beeper On: Turns on the internal beeper to make it buzz.

- Turn Beeper Off: Turns off the internal beeper to make it stop buzzing.

Log an Event Message

The option "Log event message" records the selected events in the internal log.

The default log message generated for each type of event is available in the section titled Default Log Messages (on page 269).

Shut down a Server and Control its Power

The "Power control server" action is available only when your PX2 is outlet-switching capable.

You can configure the PX2 to shut down a specific server and then turn off its outlet(s), or turn on that server's outlet(s) after a certain event occurs.

The only restriction is a server must be one of the servers being monitored by your PX2 and the same PX2 supplies power to it. To have any server monitored, see Monitoring Server Accessibility(on page 331).

Tip: If the server has multiple power cords, make sure all of its power cords are connected to the same PX2 and you have created an outlet group for controlling all outlets simultaneously. SeeOutlet Groups (on page 136).

Operation:

1. Choose Device Settings > Event Rules >

+ New Action

1. Select "Power control server" from the Action list.

2. In the Operation field, select an action for the server.

■ Power up: Turns on the outlet or outlet group associated with the selected server.
■ Graceful shutdown: Shuts down the selected server first and then turn off its associated outlet or outlet group.

1. Select the server you want in the Server field.

- If PX2 cannot power control any server, a message "Power control not configured" is shown in the end of the server's host name or IP address.

Push Out Sensor Readings

You can configure the PX2 to push sensor log to a remote server after a certain event occurs, including logs of internal sensors, environmental sensors and actuators.

If you have connected Raritan's asset strips to the PX2, you can also configure the PX2 to push the data to a server.

Before creating this action, make sure that you have properly defined the destination servers and the data to be sent on the Data Push page. See Configuring Data Push Settings (on page 323).

Tip: To send the data at a regular interval, schedule this action. See Scheduling an Action (on page 304). Note that the "Asset management log" is generated only when there are changes made to any asset strips or asset tags, such as connection or disconnection events.

Operation:

1. Choose Device Settings > Event Rules >

+ New Action

1. Select "Push out sensor readings" from the Action list.

2. Select a server or host which receives the data in the Destination field.

- If the desired destination is not available yet, go to the Data Push page to specify it.

Record Snapshots to Webcam Storage

This option allows you to define an action that starts or stops a specific webcam from taking snapshots.

Per default the snapshots are stored on the PX2. See Viewing and Managing Locally-Saved Snapshots (on page 385).

It is recommended to specify a remote server to store as many snapshots as possible. See Changing Storage Settings(on page 387).

Operation:

1. Choose Device Settings > Event Rules >

+ New Action

1. Select "Record snapshots to webcam storage" from the Action list.

2. Select a webcam in the Webcam field.

3. Select the action to perform - "Start recording" or "Stop recording." If "Start recording" is selected, adjust the values of the following:

■ Number of Snapshots - the number of snapshots to be taken when the event occurs.

The maximum amount of snapshots that can be stored on the PX2 is 10. If you set it for a number greater than 10 and the storage location is on the PX2, after the 10th snapshot is taken and stored, the oldest snapshots are overwritten. Storing snapshots on a remote server does not have such a limitation.

• Time Before First Snapshot - the amount of time in seconds between when the event is triggered and the webcam begins taking snapshots.
  ■ Time Between Snapshots - the amount of time in seconds between when each snapshot is taken.

Request LHX/SHX Maximum Cooling

If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will be available. See Miscellaneous (on page 348).

The "Request LHX/SHX Maximum Cooling" action applies the maximum cooling to the SHX-30 device only. The LHX-20 and LHX-40 devices do not support this feature.

In the maximum cooling mode, an SHX-30 device runs at 100% fan speed and the cold water valve is open 100%.

Operation:

1. Choose Device Settings > Event Rules >
2. Select "Request LHX/SHX Maximum Cooling" from the Action list.
3. In the Available LHX/SHX field, select the desired SHX-30 device one by one, or click Select All.
4. To remove any SHX-30 device from the Selected LHX/SHX field, click that device's ✗ or click Deselect All.

+ New Action

Send Email

You can configure emails to be sent when an event occurs and can customize the message.

Messages consist of a combination of free text and PX2 placeholders. The placeholders represent information which is pulled from the PX2 and inserted into the message.

For example:

[USERNAME] logged into the device on [TIMESTAMP]

translates to

Mary logged into the device on 2012-January-30 21:00

For a list and definition of available variables, see Placeholders for Custom Messages (on page 310).

▶ Operation:

1. Choose Device Settings > Event Rules >

+ New Action.

1. Select "Send email" from the Action list.

2. In the "Recipient Email Addresses" field, specify the email address(es) of the recipient(s). Use a comma to separate multiple email addresses.

3. By default, the SMTP server specified on the SMTP Server page will be the SMTP server for performing this action.

To use a different SMTP server, select the "Use custom settings" radio button. The fields for customized SMTP settings appear. For information on each field, see Configuring SMTP Settings (on page 230).

Default messages are sent based on the event. For a list of default log messages and events that trigger them, see Default Log Messages (on page 269).

1. If needed, select the Use Custom Log Message checkbox, and then create a custom message up to 1024 characters in the provided field.

- When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 310).

Use custom log message Event Context Information In your custom message, you may use placeholders for certain event contexts. For example, a message displaying the username and host the user connected from might read like: User [USERNAME] from [USERIP] caused an event. search Placeholder ▲ Description [AMSBLADESLOTPOSITION] The (horizontal) slot position inside a blade extension [AMSLEDCOLOR] The RGB LED color [AMSLEDMODE] The LED indication mode [AMSI FDOPMODE] The LED operating mode 1024 characters remaining.

- To start a new line in the text box, press Enter.

Note: In case you need to type any square brackets "[" and "]" in the custom message for non-placeholder words, always add a backslash in front of the square bracket. That is, [or] . Otherwise, the message sent will not display the square brackets.

Send Sensor Report

You may set the PX2 so that it automatically reports the latest readings or states of one or multiple sensors by sending a message or email or simply recording the report in a log. These sensors can be either internal or environmental sensors listed below.

• Inlet sensors, including RMS current, RMS voltage, active power, apparent power, power factor and active energy.
• Outlet sensors, including RMS current, RMS voltage, active power, apparent power, power factor, active energy and outlet state (for outlet-switching capable PDUs only).
• Overcurrent protector sensors, including RMS current and tripping state.
• Peripheral device sensors, which can be any Raritan environmental sensor packages connected to the PX2, such as temperature or humidity sensors.

An example of this action is available in the section titled Send Sensor Report Example (on page 306).

Operation:

1. Choose Device Settings > Event Rules >

+ New Action.

1. Select "Send sensor report" from the Action list.
2. In the Destination Actions section, select the method(s) to report sensor readings or states. The number of available methods varies, depending on how many messaging actions have been created.

The messaging action types include:

• Log event message
• Syslog message
• Send email

• Send SMS message

• If no messaging actions are available, create them now. See Available Actions (on page 284).

a. To select any methods, select them one by one in the Available field.

To add all available methods, simply click Select All.

b. To delete any methods, click a method's ✗ in the Selected field.

To remove all methods, simply click Deselect All.

1. In the Available Sensors field, select the desired target's sensor.

a. Click the first ▲ to select a target component from the list.

Peripheral Devices Temperature 1

b. Click the second to select the specific sensor for the target from the list.

Peripheral Devices Temperature 1

c. Click to add the selected sensor to the Report Sensors list box.

For example, to monitor the current reading of the Inlet 1, select Inlet 1 from the left field, and then select RMS Current from the right field.

1. To report additional sensors simultaneously, repeat the above step to add more sensors.

■ To remove any sensor from the Report Sensors list box, select it

and click 📄. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.

Peripheral Devices - Temperature 1 Peripheral Devices - Temperature 2 Peripheral Devices - Relative Humidity 1 Report sensors Available sensors Peripheral Devices On/Off 1

1. To immediately send out the sensor report, click Send Report Now.

Tip: When intending to send a sensor report using custom messages, use the placeholder [SENSORREPORT] to report sensor readings. See Placeholders for Custom Messages (on page 310).

Send SMS Message

You can configure SMS messages to be sent when an event occurs and can customize the message.

Only the 7-bit ASCII charset is supported for SMS messages. Messages consist of a combination of free text and PX2 placeholders. The placeholders represent information which is pulled from the PX2 and inserted into the message.

A supported modem, such as the Cinterion® GSM MC52i modem, must be plugged into the PX2 in order to send SMS messages. See Connecting a GSM Modem (on page 66).

Note: The PX2 cannot receive SMS messages.

For example:

[USERNAME] logged into the device on [TIMESTAMP]

translates to

Mary logged into the device on 2012-January-30 21:00

For a list and definition of available variables, see Placeholders for Custom Messages (on page 310).

Operation:

1. Choose Device Settings > Event Rules >
2. Select "Send SMS message" from the Action list.
3. In the Recipient Phone Number field, specify the phone number of the recipient.
4. Select the Use Custom Log Message checkbox, and then create a custom message in the provided text box.

+ New Action.

- When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 310).

Use custom log message Event Context Information In your custom message, you may use placeholders for certain event contexts. For example, a message displaying the username and host the user connected from might read like: User [USERNAME] from [USERIP] caused an event. search Placeholder ▲ Description [AMSBLADESLOTPOSITION] The (horizontal) slot position inside a blade extension [AMSLEDCOLOR] The RGB LED color [AMSLEDMODE] The LED indication mode [AMSLEDOPMODE] The LED operating mode 1024 characters remaining.

- To start a new line in the text box, press Enter.

Note: In case you need to type any square brackets "[" and "]" in the custom message for non-placeholder words, always add a backslash in front of the square bracket. That is, |[ or ]. Otherwise, the message sent will not display the square brackets.

Send Snapshots via Email

This option notifies one or multiple persons for the selected events by emailing snapshots or videos captured by a connected Logitech® webcam.

▶ Operation:

1. Choose Device Settings > Event Rules >
2. Select "Send snapshots via email" from the Action list.
3. In the "Recipient Email Addresses" field, specify the email address(es) of the recipient(s). Use a comma to separate multiple email addresses.
4. By default, the SMTP server specified on the SMTP Server page will be the SMTP server for performing this action.
   To use a different SMTP server, select the "Use custom SMTP Server" checkbox. The fields for customized SMTP settings appear. For information on each field, see Configuring SMTP Settings (on page 230).

+ New Action

1. Select the webcam that is capturing the images you want sent in the email.
2. Adjust the values of the following:

■ Number of Snapshots - the number of snapshots to be taken when the event occurs. For example, you can specify 10 images be taken once the event triggers the action.
- Snapshots per Mail - the number of snapshots to be sent at one time in the email.
■ Time Before First Snapshot - the amount of time in seconds between when the event is triggered and the webcam begins taking snapshots.
■ Time Between Snapshots - the amount of time in seconds between when each snapshot is taken.

Send an SNMP Notification

This option sends an SNMP notification to one or multiple SNMP destinations.

▶ Operation:

+ New Action.

1. Choose Device Settings > Event Rules >
2. Select "Send SNMP notification" from the Action list.
3. Select the type of SNMP notification. See either procedure below according to your selection.

To send SNMP v2c notifications:

1. In the Notification Type field, select SNMPv2c Trap or SNMPv2c Inform.
2. For SNMP INFORM communications, leave the resend settings at their default or do the following:

a. In the Timeout field, specify the interval of time, in seconds, after which a new inform communication is resent if the first is not received. For example, resend a new inform communication once every 3 seconds.
b. In the Number of Retries field, specify the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails.

1. In the Host fields, enter the IP address of the device(s) you want to access. This is the address to which notifications are sent by the SNMP system agent.

2. In the Port fields, enter the port number used to access the device(s).

3. In the Community fields, enter the SNMP community string to access the device(s). The community is the group representing the PX2 and all SNMP management stations.

Tip: An SNMP v2c notification action permits only a maximum of three SNMP destinations. To assign more than three SNMP destinations to a specific rule, first create several SNMP v2c notification actions, each of which contains completely different SNMP destinations, and then add all of these SNMP v2c notification actions to the same rule.

To send SNMP v3 notifications:

1. In the Notification Type field, select SNMPv3 Trap or SNMPv3 Inform.
2. For SNMP TRAPs, the engine ID is prepopulated.
3. For SNMP INFORM communications, leave the resend settings at their default or do the following:

a. In the Timeout field, specify the interval of time, in seconds, after which a new inform communication is resent if the first is not received. For example, resend a new inform communication once every 3 seconds.
b. In the Number of Retries field, specify the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails.

1. For both SNMP TRAPS and INFORMS, enter the following as needed and then click OK to apply the settings:

a. Host name
b. Port number
c. User ID for accessing the host -- make sure the User ID has the SNMPv3 permission.
d. Select the host security level

Security level Description

"noAuthNoPriv" Select this if no authorization or privacy protocols are needed.

Security level Description

"authNoPriv" Select this if authorization is required but no privacy protocols are required.Select the authentication protocol - MD5 or SHA.Enter the authentication passphrase and then confirm the authentication passphrase

"authPriv" Select this if authentication and privacy protocols are required.Select the authentication protocol - MD5 or SHA.Enter the authentication passphrase and confirm the authentication passphraseSelect the Privacy Protocol - DES or AESEnter the privacy passphrase and then confirm the privacy passphrase

Start or Stop a Lua Script

If you have created or loaded a Lua script file into the PX2, you can have that script automatically run or stop in response to a specific event.

For instructions on creating or loading a Lua script into this product, see Lua Scripts (on page 342).

To automatically start or stop a Lua script:

+ New Action.

1. Choose Device Settings > Event Rules >
2. Select "Start/stop Lua script" from the Action list.
3. In the Operation field, select Start Script or Stop Script.
4. In the Script field, select the script that you want it to be started or stopped when an event occurs.

- No script is available if you have not created or loaded it into the PX2.

1. To apply different arguments than the default, do the following. Note that the newly-added arguments will override this script's default arguments.

+ Add argument

a. Click
b. Type the key and value.
c. Repeat the same steps to enter more arguments as needed.

- To remove any existing argument, click it.

adjacent to

Switch LHX/SHX

If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will be available. See Miscellaneous (on page 348).

Use this action to switch the LHX/SHX on or off when, for example, temperature thresholds are reached.

▶ Operation:

1. Choose Device Settings > Event Rules >
2. New Action
3. Select "Switch LHX/SHX" from the Action list.
4. In the Operation field, select Turn LHX/SHX On or Turn LHX/SHX Off.
5. In the Available LHX/SHX field, select the LHX/SHX device to be turned on or off. To select all available LHX/SHX devices, click Select All.
   To remove any LHX/SHX device from the Selected LHX/SHX field, click that device's ✗. To remove all devices, click Deselect All.

Switch Outlet Group

The "Switch outlet group" action is available only when your PX2 is outlet-switching capable. This action turns on, off or power cycles a specific outlet group.

▶ Operation:

1. Choose Device Settings > Event Rules >
2. Select "Switch outlet group" from the Action list.
3. To specify the outlet group where this action will be applied, select it from the 'Group to switch' list.
4. In the Operation field, select an operation for the selected outlet group.
   ■ Turn on all outlets in group: Turns on the selected outlet group.
   ■ Turn off all outlets in group: Turns off the selected outlet group.
5. Cycle all outlets in group: Cycles power to the selected outlet group.

+ New Action

Switch Outlets

The "Switch outlets" action is available only when your PX2 is outlet-switching capable. This action turns on, off or power cycles a specific outlet.

▶ Operation:

1. Choose Device Settings > Event Rules >

+ New Action

1. Select "Switch outlets" from the Action list.

2. In the Operation field, select an operation for the selected outlet(s).

3. Turn Outlet On: Turns on the selected outlet(s).

4. Turn Outlet Off: Turns off the selected outlet(s).

5. Cycle Outlet: Cycles power to the selected outlet(s).

6. To specify the outlet(s) where this action will be applied, select them one by one from the Available Outlets list.

- To add all outlets, click Select All.

1. To remove any outlets from the Selected Outlets field, click that outlet's ✗.

■ To remove all outlets, click Deselect All.

1. If "Turn Outlet On" or "Cycle Outlet" is selected in step 3, you can choose to select the "Use sequence order and delays" checkbox so that all selected outlets will follow the power-on sequence defined on the page of Outlets (on page 118).

Switch Peripheral Actuator

If you have any actuator connected to the PX2, you can set up the PX2 so it automatically turns on or off the system controlled by the actuator when a specific event occurs.

Note: For information on connecting actuators, see DX Sensor Packages (on page 35) or DX2 Sensor Packages (on page 34).

Operation:

1. Choose Device Settings > Event Rules >

+ New Action

1. Select "Switch peripheral actuator" from the Action list.

2. In the Operation field, select an operation for the selected actuator(s).

3. Turn On: Turns on the selected actuator(s).

4. Turn Off: Turns off the selected actuator(s).

5. To select the actuator(s) where this action will be applied, select them one by one from the Available Actuators list.

- To add all actuators, click Select All.

1. To remove any selected actuator from the Selected Actuators field, click that actuator's ✗.

- To remove all actuators, click Deselect All.

Syslog Message

Use this action to automatically forward event messages to the specified syslog server. Determine the syslog transmission mechanism you prefer when setting it up - UDP, TCP or TLS over TCP.

PX2 may or may not detect the syslog message transmission failure. If yes, it will log this syslog failure as well as the failure reason in the event log. See Viewing or Clearing the Local Event Log (on page 358).

Operation:

+ New Action.

1. Choose Device Settings > Event Rules >
2. Select "Syslog message" from the Action list.
3. In the Syslog Server field, specify the IP address to which the syslog is forwarded.
4. In the Transport Protocol field, select one of the syslog protocols: TCP, UDP or TCP+TLS. The default is UDP.

Transport protocols	Next steps
UDP	In the UDP Port field, type an appropriate port number. Default is 514.Select the "Legacy BSD Syslog Protocol" checkbox if applicable.
TCP NO TLS certificate is required. Type an appropriate port number in the TCP Port field.
TCP+TLS	A TLS certificate is required. Do the following:a. Type an appropriate port number in the "TCP Port" field. Default is 6514.b. In the CA Certificate field, clickBrowse...to select a TLS certificate. After importing the certificate, you may:Click Show to view its contents.Click Remove to delete it if it is inappropriate.c. Determine whether to select the "Allow expired and not yet valid certificates" checkbox.To always send the event message to the specified syslog server as long as a TLS certificate is available, select this checkbox.To prevent the event message from being sent to the specified syslog server when any TLS certificate in the selected certificate chain is outdated or not valid yet, deselect this checkbox.

Note: If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see TLS Certificate Chain (on page 726).

Scheduling an Action

An action can be regularly performed at a preset time interval instead of being triggered by a specific event. For example, you can make the PX2 report the reading or state of a specific sensor regularly by scheduling the "Send Sensor Report" action.

When scheduling an action, make sure you have a minimum of 1-minute buffer between this action's creation and first execution time. Otherwise, the scheduled action will NOT be performed at the specified time when the buffer time is too short. For example, if you want an action to be performed at 11:00 am, you should finish scheduling it at 10:59 am or earlier.

If the needed action is not available yet, create it first. See Available Actions (on page 284).

Operation:

1. Choose Device Settings > Event Rules >

+ New Scheduled Action.

1. To select any action(s), select them one by one from the Available Actions list.

- To select all available actions, click Select All.

1. To remove any action(s) from the Selected Actions field, click that action's ✗.

■ To remove all actions, click Deselect All.

1. Select the desired frequency in the Execution Time field, and then specify the time interval or a specific date and time in the field(s) that appear.

Execution time	Frequency settings
Minutes	Click the Frequency field to select an option.The frequency ranges from every minute, every 5 minutes, every 10 minutes and so on until every 30 minutes.
Hourly	Type a value in the Minute field, which is set to either of the following:▪ The Minute field is set to 0 (zero). Then the action is performed at 1:00 am, 2:00 am, 3:00 am and so on.▪ The Minute field is set to a non-zero value. For example, if it is set to 30, then the action is performed at 1:30 am, 2:30 am, 3:30 am and so on.
Daily	Type values or click ▲.▼The time is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM/PM button.For example, if you specify 01:30PM, the action is performed at 13:30 pm every day.
Weekly	Both the day and time must be specified for the weekly option.▪ Days range from Sunday to Saturday.▪ The time is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM/PM button.
Monthly	Both the date and time must be specified for the monthly option.▪ The dates range from 1 to 31.▪ The time is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM/PM button.Note that NOT every month has the date 31, and February in particular does not have the date 30 and probably even 29. Check the calendar when selecting 29, 30 or 31.
Yearly	This option requires three settings:Month - January through December.Day of month - 1 to 31.Time - the value is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM/PM button.

An example of the scheduled action is available in the section titled Send Sensor Report Example (on page 306).

Send Sensor Report Example

To create a scheduled action for emailing a temperature sensor report hourly, it requires:

• A 'Send email' action
• A 'Send sensor report' action
• A timer - that is, the scheduled action

Steps:

1. Click + New Action to create a 'Send email' action that sends an email to the desired recipient(s). For details, see Send Email (on page 292).

2. In this exam ple, this action is named Email a Sensor Report.
   ■ If wanted, you can customize the email messages in this action.

New Action

Action name

Email a Sensor Report

Action

Send email

Recipient email addresses

[e-mail]

SMTP server

Use default settings

Server name: not configured Sender email address: not configured

Settings can be changed in SMTP Server settings.

Use custom log message

Use custom settings

Custom log message

The following is the report of sensor

[EXTSENSOR] - [EXTSENSORNAME].

[SENSORREPORT]

938 characters remaining.

×Cancel

√ Create

1. Click + New Action to create a 'Send sensor report' action that includes the 'Email a Sensor Report' action as its destination action. For details, see Send Sensor Report (on page 294).

- In this example, this action is named Send Temperature Sensor Readings.

- You can specify more than one temperature sensor as needed in this action.

New Action Action name Send Temperature Sensor Readings Action Send sensor report Destination actions Selected Email a Sensor Report ✗ Available - Select an item -- Select All Deselect All Report sensors Peripheral Devices - Temperature 1 Peripheral Devices - Temperature 2 Available sensors ▲ Peripheral Devices ▼ Relative Humidity 1 Send Report Now Note: Reported sensor units can be changed in the Default Preferences. Cancel ✓ Create

1. Click + New Scheduled Action to create a timer for performing the 'Send Temperature Sensor Readings' action hourly. For details, see Scheduling an Action (on page 304).

In this example, the timer is named Hourly Temperature Sensor Reports.

■ To perform the specified action at 12:30 pm, 01:30 pm, 02:30 pm, and so on, select Hourly, and set the Minute to 30.

New Scheduled Action

Timer name

Hourly Temperature Sensor Reports

Enabled

Execution time

Hourly

Minute

30

Selected actions

Send Temperature Sensor Readings ✗

Available actions

- Select an item -

Select All

Deselect All

×Cancel

√ Create

Then the PX2 will send out an email containing the specified temperature sensor readings hourly every day.

Whenever you want the PX2 to stop sending the temperature report, simply deselect the Enabled checkbox in the timer.

Placeholders for Custom Messages

Actions of "Send email" and "Send SMS message" allow you to customize event messages. See Send Email (on page 292) or Send SMS Message (on page 296).

When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Simply drag the scroll bar and then click the desired placeholder to insert it into the custom message. Or you can type a keyword in the "search" box to quickly find the desired placeholder.

Chapter 6: Using the Web Interface

Use custom log message Event Context Information In your custom message, you may use placeholders for certain event contexts. For example, a message displaying the username and host the user connected from might read like: User [USERNAME] from [USERIP] caused an event. search Placeholder ▲ Description [AMSBLADESLOTPOSITION] The (horizontal) slot position inside a blade extension [AMSLEDCOLOR] The RGB LED color [AMSLEDMODE] The LED indication mode [AMSI FEDOPMODE] The LED operating mode 1024 characters remaining.

If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

To make the Event Context Information disappear, click anywhere inside the browser's window.

The following are placeholders that can be used in custom messages.

Placeholder Definition
[AMSBLADESLOTPOSITION] The (horizontal) slot position, an action applies to
[AMSLEDCOLOR] The RGB LED color
[AMSLEDMODE] The LED indication mode
[AMSLEDOPMODE] The LED operating mode
[AMSNAME] The name of an asset strip
[AMSNUMBER]	The numeric ID of an asset strip
[AMSRACKUNITPOSITION] The (vertical) rack unit position, an action applies to
[AMSSTATE] The human readable state of an asset strip
[AMSTAGID] The asset tag ID
[CARDREADERCHANNEL] The channel number of a card reader
[CARDREADERID] The id of a card reader
[CARDREADERMANUFACTURER]	The manufacturer of a card reader

Placeholder Definition
[CARDREADERPRODUCT] The product name of a card reader
[CARDREADERSERIALNUMBER] The serial number of a card reader
[COMPONENTID] The ID of a hardware component
[CONFIGPARAM] The name of
[CONFIGVALUE] The new value of a parameter
[DATETIME] The human readable timestamp of the event occurrence
[DEVICEIP] The IP address of the device, the event occurred on
[DEVICENAME] The name of the device, the event occurred on
[DEVICESERIAL] The unit serial number of the device the event occurred on
[ERRORDESC] The error message
[EVENTRULENAME] The name of the matching event rule
[EXTSENSOR] The peripheral device identifier
[EXTSENSORNAME] The name of a peripheral device
[EXTSENSORSLOT] The ID of a peripheral device slot
[FAILURETYPE] The numeric hardware failure type
[FAILURETYPESTR] The textual hardware failure type
[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
[ISASSERTED] Boolean flag whether an event condition became true (1) or false (0)
[LDAPERRORDESC] An LDAP error occurred
[LHXFANID] The ID of a fan connected to an LHX/SHX
[LHXPOWERSUPPLYID] The ID of an LHX/SHX power supply
[LHXSENSORID] The ID of an LHX/SHX sensor probe
[LOGMESSAGE] The original log message

a configuration par

Placeholder Definition
[MONITOREDHOST] The name or IP address of a monitored host
[OCP] The overcurrent protector label
[OCPSENSOR] The overcurrent protector sensor name
[OCPTRIPCAUSELABEL] The label of the outlet that likely caused the OCP trip
[OLDVERSION] The firmware version of the device is being upgraded from
[OUTLET] The outlet label
[OUTLETGROUPID] The outlet group ID
[OUTLETGROUPNAME] The outlet group name
[OUTLETGROUPSENSOR] The outlet group sensor name
[OUTLETNAME] The outlet name
	Note: If any outlet does not have a name, neither an outlet name nor an outlet number will be shown in the custom message for it. Therefore, it is recommended to check the availability of all outlet names if intending to use this placeholder.
[OUTLETPOLE] The outlet power line identifier
[OUTLETSENSOR] The outlet sensor name
[PERIPHDEVPOSITION]	The position of an attached peripheral device
[PHONENUMBER]	The phone number an SMS was sent to
[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
[RADIUSERRORDESC]	A Radius error occurred
[ROMCODE]	The rom code of an attached peripheral device
[SENSORREADING]	The value of a sensor reading
[SENSORREADINGUNIT]	The unit of a sensor reading
[SENSORREPORT]	The formatted sensor report contents
[SENSORSTATENAME]	The human readable state of a sensor
[SENSORTHRESHOLDNAME]	The name of the threshold being crossed
[SENSORTHRESHOLDVALUE] The value of the threshold being crossed
[SERVERPOWEROPERATION]	The power control operation that was initiated on a server (on/off)
[SERVERPOWERRESULT] The result of a power control operation
[SMARTCARDID]	The id of a smart card
[SMARTCARDTYPE] The type of a smart card
[SMTPRECIPIENTS] The list of recipients, an SMTP message was sent to
[SMTPSERVER] The name or IP address of an SMTP server
[SYSCONTACT] SysContact as configured for SNMP
[SYSLOCATION] SysLocation as configured for SNMP
[SYSNAME] SysName as configured for SNMP
[TIMEREVENTID] The id of a timer event
[TIMESTAMP]	The timestamp of the event occurrence
[UMTARGETROLE] The name of a user management role, an action was applied on
[UMTARGETUSER] The user, an action was triggered for
[USERIP] The IP address, a user connected from
[USERNAME]	The user who triggered an action
[VERSION]	The firmware version the device is upgrading to

Note: In case you need to type any square brackets "[" and "]" in the custom message for non-placeholder words, always add a backslash in front of the square bracket. That is, [or] . Otherwise, the message sent will not display the square brackets.

Editing or Deleting a Rule/Action

You can change the settings of an event rule, action or scheduled action, or delete them.

Exception: Some settings of the built-in event rules or actions are not user-configurable. Besides, you cannot delete built-in rules and actions. See Built-in Rules and Rule Configuration (on page 263) or Available Actions (on page 284).

To edit or delete an event rule, action or scheduled action:

1. Choose Device Settings > Event Rules.

2. Click the desired one in the list of rules, actions or scheduled actions. Its setup page opens.

3. Perform the desired action.

4. To modify settings, make necessary changes and then click Save.

5. To delete it, click Delete on the top-right corner. Then click Delete on the confirmation message.

Sample Event Rules

Sample PDU-Level Event Rule

In this example, we want the PX2 to record the firmware upgrade failure in the internal log when it happens.

The event rule involves:

• Event: Device > Firmware update failed
• Action: System Event Log Action

To create this PDU-level event rule:

1. For an event at the PDU level, select "Device" in the Event field.
2. Select "Firmware update failed" so that the PX2 responds to the event related to firmware upgrade failure.
3. To make the PX2 record the firmware update failure event in the internal log, select "System Event Log Action" in the 'Available actions' field.

Event Device 1 Firmware update failed 2 Selected actions 3 System Event Log Action ✗ Available actions -- Select an item -- Select All Deselect All Cancel ✓ Create

Sample Outlet-Level Event Rule

In this example, we want the PX2 to send SNMP notifications to the SNMP manager for any sensor change event of outlet 3.

The event rule involves:

• Event: Outlet > Outlet 3 > Sensor > Any sub-event
• Action: System SNMP Notification Action

To create this outlet-level event rule:

1. For an event at the outlet level, select "Outlet" in the Event field.
2. Select "Outlet 3" because that is the desired outlet.
3. Select "Sensor" to refer to sensor-related events.
4. Select "Any sub-event" to include all events related to all sensors of this outlet and all thresholds, such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold, lower warning threshold, and so on.
5. To make the PX2 send SNMP notifications, select "System SNMP Notification Action" in the 'Available actions' field.

Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for the System SNMP Notification Action. See Enabling and Configuring SNMP (on page 391).

Event Outlet 1 Outlet 3 2 Sensor 3 4 Selected actions 5 System SNMP Notification Action ✗ Available actions -- Select an item - Select All Deselect All Cancel ✓ Create

Then the SNMP notifications are sent when:

• Any numeric sensor's reading enters the warning or critical range.
• Any sensor reading or state returns to normal.
• Any sensor becomes unavailable.
• The active energy sensor is reset.
  ■ Any state sensor changes its state.

For example, when the outlet 3's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again.

Sample Inlet-Level Event Rule

In this example, we want the PX2 to send SNMP notifications to the SNMP manager for any sensor change event of the Inlet I1.

The event rule involves:

• Event: Inlet > Sensor > Any sub-event
• Action: System SNMP Notification Action

To create the above event rule:

1. For an event at the inlet level, select "Inlet" in the Event field.
2. Select "Sensor" to refer to sensor-related events.
3. Select "Any sub-event" to include all events related to all sensors of this inlet and all thresholds, such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold, lower warning threshold, and so on.
4. To make the PX2 send SNMP notifications, select "System SNMP Notification Action" in the 'Available actions' box.

Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for the System SNMP Notification Action. See Enabling and Configuring SNMP (on page 391).

Event Inlet 1 Sensor 2 3 Selected actions 4 System SNMP Notification Action ✗ Available actions -- Select an item -- Select All Deselect All Cancel ✓ Create

Then the SNMP notifications are sent when:

• Any numeric sensor's reading enters the warning or critical range.
• Any sensor reading or state returns to normal.
  ■ Any sensor becomes unavailable.
  ■ The active energy sensor is reset.

For example, when the Inlet I1's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again.

Sample Environmental-Sensor-Level Event Rule

This section applies to outlet-switching capable models only.

In this example, we want PX2 to activate the load shedding function when a contact closure sensor enters the alarmed state. This event rule requires creating a new action before creating the rule.

▶ Step 1: create a new action for activating the load shedding

1. Choose Device Settings > Event Rules >
2. In this illustration, assign the name "Activate Load Shedding" to the new action.
3. In the Action field, select "Change load shedding state."
4. In the Operation field, select Start Load Shedding.

New Action

Action name

Activate Load Shedding

2

Action

Change load shedding state

3

Operation

Start load shedding

4

×Cancel

√ Create

5. Click Create to finish the creation.

After the new action is created, follow the procedure below to create an event rule that triggers the load shedding mode when the contact closure sensor enters the alarmed state. This event rule involves the following:

• Event: Peripheral Device Slot > Slot 1 > State Sensor/Actuator > Alarmed/Open/On
• Trigger condition: Alarmed
  • Action: Activate Load Shedding

Step 2: create the contact closure-triggered load shedding event rule

1. Click + New Rule on the Event Rules page.

2. In this illustration, assign the name "Contact Closure Triggered Load Shedding" to the new rule.

3. In the Event field, select "Peripheral Device Slot" to indicate we are specifying an event related to the environmental sensor package.
4. 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.

Note: ID numbers of all sensors/actuators are available on the Peripherals page. See Peripherals (on page 156).

1. Select "State Sensor/Actuator" because the contact closure sensor is a state sensor.
2. Select "Alarmed" since we want the PX2 to respond when the selected contact closure sensor changes its state related to the "alarmed" state.
3. In the "Trigger condition" field, select the Alarmed/Open/On radio button so that the action is taken only when the contact closure sensor enters the alarmed state.
4. Select "Activate Load Shedding" from the 'Available actions' list.

Event Peripheral Device Slot 3 Slot 1 (On/Off 1) 4 State Sensor / Actuator 5 Alarmed / Open / On 6 Trigger condition 7 Alarmed / open / on No longer alarmed / closed / off Both Selected actions 8 Activate Load Shedding ✗ Available actions -- Select an item -- Select All Deselect All Cancel ✓ Create

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 PX2 keeps busy because the action or one of the actions taken for a certain event triggers an identical or similar event which will result in an action triggering one more event.

Example 1

This example illustrates an event rule which continuously causes the PX2 to send out email messages.

Event selected Action included
Device > Sending SMTP message failed Send email

Example 2

This example illustrates an event rule which continuously causes the PX2 to send out SMTP messages when one of the selected events listed on the Device menu occurs. Note that under the Device menu includes the event "Sending SMTP message failed."

Event selected Action included
Device > Any sub-event Send email

Example 3

This example illustrates a situation where two event rules combined regarding the outlet state changes causes the PX2 to continuously power cycle outlets 1 and 2 in turn.

Event selected Action included
Outlet > Outlet 1 > Sensor > Outlet State > On/Off > Both (trigger condition)	Cycle Outlet 2(Switch outlets --> Cycle Outlet --> Outlet 2)
Outlet > Outlet 2 > Sensor > Outlet State > On/Off > Both (trigger condition)	Cycle Outlet 1(Switch outlets --> Cycle Outlet --> Outlet 1)

A Note about Untriggered Rules

In some cases, a measurement exceeds a threshold causing the PX2 to generate an alert. The measurement then returns to a value within the threshold, but the PX2 does not generate an alert message for the Deassertion event. Such scenarios can occur due to the hysteresis tracking the PX2 uses. See "To De-assert" and Deassertion Hysteresis (on page 709).

Setting Data Logging

The PX2 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 PX2 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 the 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: The PX2 device's SNMP agent must be enabled for this feature to work. See Enabling and Configuring SNMP (on page 391). In addition, using an NTP time server ensures accurately time-stamped measurements.

By default, data logging is enabled. You must have the "Administrator Privileges" or "Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration" permissions to change the setting.

To configure the data logging feature:

1. Choose Device Settings > Data Logging.
2. To enable the data logging feature, select the "Enable" checkbox in the General Settings section.
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 at the bottom of the page to have all sensors selected.
5. You can also click the topmost checkbox labeled "Logging Enabled" in the header row of each section to select all sensors of the same type.
6. If any section's number of sensors exceeds 35, the remaining sensors are listed on next page(s). If so, a pagination bar similar to the following diagram displays in this section, which you can click any button to switch between pages.

First

Previous

1

2

3

4

5

...

Next

Last

1. Click Save. This button is located at the bottom of the page.

Important: Although it is possible to selectively enable/disable logging for individual sensors on the PX2, it is NOT recommended to do so.

Configuring Data Push Settings

You can push the sensor or asset strip data to a remote server for data synchronization. The destination and authentication for data push have to be configured properly on the PX2.

The data will be sent in JSON format using HTTP POST requests. For more information on its format, see Data Push Format (on page 325).

For instructions on connecting asset strips, see Connecting Asset Management Strips (on page 53).

After configuring the destination and authentication settings, do either or both of the following:

• To perform the data push after the occurrence of a certain event, create the data push action and assign it to an event rule.
• To push the data at a regular interval, schedule the data push action. See Event Rules and Actions (on page 262).

To configure data push settings:

1. Choose Device Settings > Data Push.

2. To specify a destination, click + New Destination.

3. Do the following to set up the URL field.

a. Click ▼ to select http or https.

b. Type the URL or host name in the accompanying text box.

1. If selecting https, a CA certificate is required for making the

connection. Click Browse... to install it. Then you can:

• Click Show to view the certificate's content.
• Click Remove to delete the installed certificate if it is inappropriate.

Note: If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see TLS Certificate Chain (on page 726).

1. If the destination server requires authentication, select the Use Authentication checkbox, and enter the following data.

■ User name comprising up to 64 characters
■ Password comprising up to 128 characters

1. In the Entry Type field, determine the data that will be transmitted.

2. Asset management tag list: Transmit the information of the specified asset strip(s), including the general status of the specified strip(s) and a list of asset tags. The asset tags list also includes the tags on blade extension strips, if any.
   ■ Asset management log: Transmit the log of all asset strips, which is generated when there are changes made to asset tags and asset strips, including asset tag connection or disconnection events.

- Sensor log: Transmit the record of all logged sensors, including their sensor readings and/or status. Logged sensors refer to all internal and/or environmental sensors/actuators that you have selected on the Data Logging page. See Setting Data Logging (on page 322).

1. If "Ass et management tag list" is selected in the above step, specify the asset strip(s) whose information to send. For PX2 with only one FEATURE port, only one asset strip is available.

2. To specify the asset strip(s), select them one by one from the Available AMS Ports list. Or click Select All to add all.

3. To remove the asset strip(s), click that asset strip's ✗ in the Selected AMS Ports field. Or click Deselect All to remove all.

4. Click Create.

5. Repeat the same steps for additional destinations. Up to 64 destinations are supported.

To modify or delete data push settings:

1. On the Data Push page, click the one you want in the list.
2. Perform either action below.

■ To modify settings, make necessary changes and then click Save.

- To delete it, click Delete, and then confirm it on the confirmation message.

Data Push Format

Each push message contains exactly one JSON object. The data format is formally defined in IDL files, sharing several definitions from the JSON-RPC data model.

IDL files are available by launching JSON-RPC v3.5.0 online help (https://help.raritan.com/json-rpc/pdu/v3.5.0/namespacedatapush.html).

To have an overview of the data format, see the following topic.

• Sensor Log (on page 325)
• Asset Management Tag List(on page 328)
• Asset Management Log (on page 330)

Sensor Log

The root object of the message is a SensorLogPushMessage structure. It comprises a list of sensor descriptors and a list of log rows.

▶ Sensor descriptors:

The sensor descriptor vector contains static information of all logged sensors, including:

• The electrical component a sensor is associated with. For example, an inlet pole or an overcurrent protector.
• The sensor's type. For example, RMS current or active energy.
• Unit and range of the sensor's readings.

See Sensor Descriptors for Inlet Active Power(on page 326)

Log rows:

Each log row consists of a time stamp (accumulated seconds since 1/1/1970) and a list of log records -- one for each logged sensor.

The length and order of the record list is the same as the sensor descriptor vector.

See Log Rows (on page 327).

Sensor Descriptors for Inlet Active Power

The following illustrates a descriptor for an inlet active power sensor.

The metadata field is relevant only to numeric sensors so the readingtype field is displayed twice in the illustration.

Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.

{
    "device": {
    "type": 0, // Inlet sensor (see DeviceType enumeration)
    "label": "I1", // Inlet label: I1
    "line": 0 // Power line; not applicable for inlet sensors
},
"id": "activePower", // Sensor identification
"readingtype": 0, // Reading type: numeric
"metadata": {
    "type": {
    "readingtype": 0, // Reading type: numeric
    "type": 5, // Sensor type: Active power
    "unit": 3 // Reading unit: Watt
    },
    "decdigits": 0, // No decimal digits
    "accuracy": 1.0, // Accuracy: 1 percent
    "resolution": 1.0, // Reading resolution: 1 W
    "tolerance": 1.5, // Reading tolerance: +/- 1.5 W
    "range": {
    "lower": 0.0, // Minimum reading: 0 W
    "upper": 30000.0 // Maximum reading: 30 kW
    }
}
} 

Log Rows

The following illustrates log rows with only one sensor record shown.

The actual length and order of log rows will be the same as those of sensors descriptors.

Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.

{
    "timestamp": 1334052852, // Time stamp (seconds since 1/1/1970)
    "records": [
    {
    "available": true, // This record is available
    "takenValidSamples": 60, // Number of valid samples in this log period
    "state": 5, // Sensor was in normal range
    "minValue": 5800.0, // Minimum sensor value: 5.8 kW
    "avgValue": 5900.0, // Average sensor value: 5.9 kW
    "maxValue": 6100.0, // Maximum sensor value: 6.1 kW
    },
    {
    // [...] record for next sensor
    }
    ]
} 

Asset Management Tag List

The root object of the asset management tag list message is an AssetStripsMessage structure. It contains current data about all connected asset management strips and tags, which is similar to the illustration below.

{
    "assetStrips": [
    {
    "stripInfo": {
    "bladeOverflow": false,
    "bladeTagCount": 0,
    "cascadeState": 0,
    "componentCount": 1,
    "mainTagCount": 2,
    "maxBladeTagCount": 128,
    "maxMainTagCount": 64,
    "rackUnitCount": 48
    },
    "deviceInfo": {
    "appVersion": 24,
    "bootVersion": 6,
    "deviceId": 48,
    "hardwareId": 2,
    "isCascadable": false,
    "orientationSensAvailable": true,
    "protocolVersion": 257,
    "rackUnitCountConfigurable": true
    },
    "settings": {
    "rackUnitCount": 48,
    "name": "Asset Strip 1",
    "scanMode": 0,
    "defaultColorConnected": { "r": 0, "g": 255, "b": 0 },
    "defaultColorDisconnected": { "r": 255, "g": 0, "b": 0 },
    "numberingMode": 1,
    "numberingOffset": 1,
    "orientation": 0
    },
} 

(Continued)

"tags": [
    {
    "rackUnitNumber": 4,
    "slotNumber": 0,
    "familyDesc": "Unknown",
    "rawId": "DEADBEEF0000",
    "programmable": 0
    },
    {
    "rackUnitNumber": 5,
    "slotNumber": 0,
    "familyDesc": "Unknown",
    "rawId": "DEADBEEF0500",
    "programmable": 0
    }
]
} 

Asset Management Log

The root object of the asset management log message is an AssetLogPushMessage structure. It contains a list of tag or strip events since the last successful push.

Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.

{
    "records": [
    {
    "timestamp": 1334052852, // Time stamp (seconds since 1/1/1970)
    "type": 1, // 0: empty, 1: tag connected, 2: tag disconnected,
    // 3: asset strip state changed
    "assetStripNumber": 0, // Asset strip number
    "rackUnitNumber": 10, // Rack unit number
    "rackUnitPosition": 12, // Rack unit position
    "slotNumber", // Blade extension slot number
    "tagId", // The ID of the asset management tag
    "state": 5, // Sensor was in normal range
    "parentBladeId", // ID of the parent blade extension tag
    "state": 0 // 0: disconnected, 1: firmware update,
    // 2: unsupported, 3: available
    },
    {
    // [...] next record
    }
    ]
} 

Monitoring Server Accessibility

You can monitor whether specific IT devices are alive by having the PX2 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.

This function is especially useful when you are not located in an area with Internet connectivity.

PX2 can monitor any IT device, such as database servers, remote authentication servers, power distribution units (PDUs), and so on. It supports monitoring a maximum of 64 IT devices.

To perform this feature, you need the Administrator Privileges.

The default ping settings may not be suitable for monitoring devices that require high connection reliability so it is strongly recommended that you should adjust the ping settings for optimal results.

In addition, if your PX2 is outlet switching capable, you can even connect a monitored IT device to one or multiple outlets of PX2 and then have PX2 perform the following two actions as needed, in addition to monitoring its status:

• First shut down the monitored IT device.
• After the IT device is shut down, power off the outlet(s) where that device is connected.

Important: Not every IT device can be shut down by PX2 so it is suggested to verify whether the device can be shut down using a shutdown command. For example, PX2 cannot shut down another PDU with a shutdown command.

Tip: To make the PX2 automatically log, send notifications or perform other actions for any server monitoring events, you can create event rules. See Event Rules and Actions (on page 262). An example is available in Example: Ping Monitoring and SNMP Notifications (on page 338).

To add IT equipment for ping monitoring:

1. Choose Device Settings > Server Reachability.
2. Click + Monitor New Server.
3. By default, the "Enable ping monitoring for this server" checkbox is selected. If not, select it to enable this feature.
4. Configure the following.

Field Description
IP address/hostname	IP address or host name of the IT equipment which you want to monitor.
Number of successful pings to enable feature	The number of successful pings required to declare that the monitored equipment is "Reachable." Valid range is 0 to 200.
Wait time 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 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 monitored equipment is declared "Unreachable." Valid range is 1 to 100.
Wait time before resuming pinging after failure	The wait time before the PX2 resumes pinging after the monitored equipment is declared "Unreachable." Valid range is 1 to 1200 (seconds).
Number of consecutive failures before disabling feature (0 = unlimited)	The number of times the monitored equipment is declared "Unreachable" consecutively before the PX2 disables the ping monitoring feature for it and shows "Waiting for reliable connection." Valid range is 0 to 100.

1. On a PDU with outlet switching capability, there is one more checkbox available -- Power control enabled.

To be able to shut down and power control the monitored IT device via the Server Reachability page, enable this checkbox and configure related settings. Refer to the following section for configuration details.

1. Click Create.
2. To add more IT devices, repeat the same steps.

To configure the shutdown and power control settings:

Restriction: To make the power control feature work properly, the power cord(s) of the monitored IT device must be connected to the "same" PDU which is monitoring the IT device.

Field Description
Shutdown command	This is the command which is sent to the monitored IT device via SSH for shutting it down after you press the Shutdown button on PX2.GNU/Linux.This option sends the GNU/Linux shutdown command.Windows.This option sends the Windows shutdown command.Custom:If the monitored device's system is neither GNU/Linux nor Windows, choose this option to specify a proper shutdown command, which can comprise a maximum of 1024 ASCII characters.
User name,Password	Specify user credentials for logging in to the monitored device via SSH.User name.The name comprises up to 128 non-empty ASCII characters.Password:The password comprises up to 128 ASCII characters.
SSH port The monitored device's SSH port.Default is 22.
Power target to switch	Select the outlet or outlet group that is powering the monitored device.
Method of checking successful shutdown	This field determines when PX2 will power off the outlet(s) that supplies power to the monitored device, after PX2 issues the shutdown command to that device.Timer:PX2 will power off the selected outlet or outlet group after the time specified in the 'Timer delay' field expires.Active power drop:PX2 will power off the selected outlet(s) after the active power value of the selected outlet or outlet group drops below the value specified in the 'Active power threshold' field.
	Note:Number of available methods is model dependent.The 'Active power drop' method is available only on models with outlet metering capability.
Timer delay	This field appears for the 'Timer' method. Valid values range between 5 and 10,000 seconds.
Active power threshold	The field appears for the 'Active power drop' method. Valid values range between 0 and 21,000 W.
Timeout for shutdown check	This field appears for the 'Active power drop' method.
	Valid values range between 5 and 10,000 seconds.The power-off operation is performed only when the active power value of the selected outlet or outlet group drops below the 'Active power threshold' within the period of time specified in this field.If the active power value drops below the 'Active power threshold' after the specified time expires, the power-off operation will not be performed.

Server Status Checking or Power Control

It is model dependent whether your PX2 supports the shutdown and power control features via the Server Reachability page.

After adding IT equipment for monitoring, all IT devices are listed on the Server Reachability page.

Server Reachability
IP Address/Hostname ▲	Ping Enabled	Status	Power Control
100.192.3.55	yes	Waiting for reliable connection	(disabled)
150.33.84.99	yes	Waiting for reliable connection	Server power is off
www.legrand.com	yes	Reachable	Server power is on
www.raritan.com	yes	Reachable	Server power is on

In the beginning, the status of the added IT equipment shows "Waiting for reliable connection," which means the requested number of consecutive successful or unsuccessful pings has not reached before PX2 can declare that the monitored device is reachable or unreachable.

To check the server monitoring states and results:

1. The column labeled "Ping Enabled" indicates whether the monitoring for the corresponding IT device is activated or not.

2. The column labeled "Status" indicates the accessibility of monitored equipment.

Status Description
Reachable The monitored equipment is accessible.
Unreachable The monitored equipment is inaccessible.
Waiting for reliable connection	The connection between the PX2 device and the monitored equipment is not reliably established yet.

1. If your PX2 supports outlet switching, one more column displays -- Power Control.

Power control status	Description
(disabled) Power control is not enabled for the monitored equipment.
Server power is on	The outlet or outlet group associated with the monitored equipment is being powered on.▪ In the scenario where an 'outlet group' is associated with the equipment, the message 'Server power is on' is shown as long as one of the outlets in the outlet group remains powered on.
Server power is off	The outlet or all outlets of the outlet group associated with the monitored equipment are being powered off.
Server is shutting down	PX2 has sent the shutdown command to the monitored equipment, but the shutdown operation has not completed or succeeded yet.
Power state unknown	PX2 cannot determine the power state of the outlet(s) associated with the monitored device. For example, maybe the outlet group associated with the monitored device has been deleted.

To shut down a monitored device:

1. Select the IT device that you want to shut down.
2. Click Ⓧ Shutdown.

3. Confirm the operation when prompted.

4. Observe the Power Control status of the monitored device to make sure the shutdown operation succeeds.

▶ To power on a monitored device:

1. Select the IT device that you want to turn on.
2. Click ⏻ Power Up.
3. Confirm the operation when prompted.
4. Observe the Power Control status of the monitored device to make sure the power-on operation succeeds.

Editing or Deleting Ping Monitoring Settings

You can edit the ping monitoring settings of any IT device or simply delete it if no longer needed.

To modify or delete any monitored IT device:

1. Choose Device Settings > Server Reachability.
2. Click the desired one in the list.
3. Perform the desired action.

- To modify settings, make necessary changes and then click Save. For information on each field, see Monitoring Server Accessibility(on page 331).

- To delete it, click 📄 on the top-right corner.

Example: Ping Monitoring and SNMP Notifications

In this illustration, it is assumed that a significant PDU (IP address: 192.168.84.95) shall be monitored by your PX2 to make sure that PDU is properly operating all the time, and the PX2 must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or network failure. The prerequisite for this example is that the power sources are different between your PX2 and the monitored PDU.

This requires the following two steps.

Step 1: Set up the ping monitoring for the target PDU

1. Choose Device Settings > Server Reachability.
2. Click + Monitor New Server.
3. Ensure the "Enable ping monitoring for this server" checkbox is selected.
4. Enter the data shown below.

- Enter the server's data.

Field Data entered

IP address/hostname 192.168.84.95

- To make the PX2 declare the accessibility of the monitored PDU every 15 seconds (3 pings * 5 seconds) when that PDU is accessible, enter the following data.

Field Data entered

Number of successful pings to enable feature 3

Wait time after successful ping 5

- To make the PX2 declare the inaccessibility of the monitored PDU when that PDU becomes inaccessible for around 12 seconds (4 seconds * 3 pings), enter the following data.

Field Data entered

Wait time after unsuccessful ping 4

Number of consecutive unsuccessful pings for 3 failure

- To make the PX2 stop pinging the target PDU for 60 seconds (1 minute) after the PDU inaccessibility is declared, enter the following data. After 60 seconds, the PX2 will re-ping the target PDU,

Field Data entered

Wait time before resuming pinging after failure 60

- The "Number of consecutive failures before disabling feature (0 = unlimited)" can be set to any value you want.

1. Click Create.

Step 2: Create an event rule to send SNMP notifications for the target PDU

1. Choose Device Settings > Event Rules.

2. Click + New Rule.

3. Select the Enabled checkbox to enable this new rule.

4. Configure the following.

Field/setting Data specified

Rule name Send SNMP notifications for PDU{192.168.84.95} inaccessibility

Event Choose Server Monitoring > 192.168.84.95> Unreachable

Trigger condition Select the Unreachable radio button

This will make the PX2 react only when the target PDU becomes inaccessible.

5. Select the System SNMP Notification Action.

Note: If you have not configured the System SNMP Notification Action to specify the SNMP destination(s), see Editing or Deleting a Rule/Action (on page 314).

Front Panel Settings

You can perform outlet switching via the front panel. Note that this feature is available on outlet-switching capable models only. By default this feature is disabled.

To enable the front panel outlet-switching feature:

1. Choose Device Settings > Front Panel.
2. To enable the front panel outlet-switching function, select the "Outlet switching" checkbox.
3. Click Save.

Now you can turn on or off any outlets by operating the front panel. See Outlet Switching (on page 78).

Configuring the Serial Port

You can change the bit rate of the serial port labeled CONSOLE / MODEM on the PX2. The default bit rate for console and modem operation is 115200 bps.

The PX2 supports using the following devices via the serial interface:

• A computer for console management.
  • A Raritan KVM product.
• An analog modem for remote dial-in and access to the CLI.
  • A GSM modem for sending out SMS messages to a cellular phone.

Bit-rate adjustment may be necessary. Change the bit rate before connecting the supported device to the PX2 through the serial port, or there are communication problems.

Note: The serial port bit-rate change is required when the PX2 works in conjunction with Raritan's Dominion LX KVM switch. Dominion LX only supports 19200 bps for communications over the serial interface.

You can set diverse bit-rate settings for console and modem operations. Usually the PX2 can detect the device type, and automatically apply the preset bit rate.

The PX2 will indicate the detected device in the Port State section of the Serial Port page.

To configure serial port and modem settings, choose Device Settings > Serial Port.

To change the serial port's baud rate settings:

1. Click the "Connected device" field to make the serial port enter an appropriate state.

Options Description
Automatic detection The	PX2 automatically detects the type of the device connected to the serial port.Select this option unless your PX2 cannot correctly detect the device type.
Force console The PX2	attempts to recognize that the connected device is set for the console mode.
Force analog modem The	PX2 attempts to recognize that the connected device is an analog modem.
Force GSM modem The	PX2 attempts to recognize that the connected device is a GSM modem.

1. Click the Console Baud Rate field to select the baud rate intended for console management.

Note: For a serial RS-232 or USB connection between a computer and the PX2, leave it at the default (115200 bps).

1. Click the Modem Baud Rate field to select the baud rate for the modem connected to the PX2.

The following modem settings/fields appear in the web interface after the PX2 detects the connection of an analog or GSM modem.

To configure the analog modem:

1. Select the "Answer incoming calls" checkbox to enable the remote access via a modem. Otherwise, deselect it.
2. Type a value in the "Number of rings before answering" field to determine the number of rings the PX2 must wait before answering the call.

To configure the GSM modem:

1. Enter the SIM PIN code.
2. Select the "Use custom SMS center number" checkbox if a custom SMS center will be used.
3. Enter the SMS center number in the "SMS center" field.
4. If needed, click Advanced Information to view detailed information about the modem, SIM and mobile network.
5. To test whether the PX2 can successfully send out SMS messages with the modem settings:
   a. Enter the number of the recipient's phone in the Recipient Phone field.
   b. Click Send SMS Test to send a test SMS message.

Lua Scripts

If you can write or obtain any Lua scripts, you can create or load them into the PX2 to control its behaviors.

Raritan also provides some Lua scripts examples, which you can load as needed.

Note: Not all Raritan Lua script examples can apply to your PX2 model. You should read each example's introduction before applying them.

You must have the Administrator Privileges to manage Lua scripts.

Writing or Loading a Lua Script

You can enter or load up to 4 scripts to the PX2.

Tip: If you can no longer enter or load a new script after reaching the upper limit, you can either delete any existing script or simply modify/replace an existing script's codes. See Modifying or Deleting a Script (on page 347).

To write or load a Lua script:

1. Choose Device Settings > Lua Scripts >

+ Create New Script

1. Type a name for this script. Its length ranges between 1 to 63 characters.

The name must contain the following characters only.

■ Alphanumeric characters
■ Underscore(_)
- Minus (-)

Note: Spaces are NOT permitted.

1. Determine whether and when to automatically execute the loaded script.

Checkbox Behavior when selected
Start automatically at system boot	Whenever the PX2 reboots, the script is automatically executed.
Restart after termination	The script is automatically executed each time after 10 seconds since the script execution finishes.

1. (Optional) Determine the arguments that will be executed by default.

a. Click

+ Add argument

b. Type the key and value.
c. Repeat the same steps to enter more arguments as needed.

- To remove any existing argument, click it.

adjacent to

Note: The above default arguments will be overridden by new arguments specified with the "Start with Arguments" command or with any Lua-script-related event rule. See Manually Starting or Stopping a Script (on page 344) or Start or Stop a Lua Script (on page 300).

1. In the Source Code section, do one of the following. It is recommended to leave the Enable Syntax Highlighting checkbox selected unless you do not need different text colors to identify diverse code syntaxes.

■ To write a Lua script, type the codes in the Source Code section.

Source Code Load Local File Load Example Enable Syntax Highlighting -- Type your codes here.

• To load an existing Lua script file, click Load Local File.
• To use one of Raritan's Lua script examples, click Load Example.

Warning: The newly-loaded script will overwrite all existing codes in the Source Code section. Therefore, do not load a new script if the current script meets your needs.

1. If you chose to load a script or Raritan's example in the previous step, its codes are then displayed in the Source Code section. Double check the codes. If needed, modify the codes to meet your needs.
2. Click Create.

Next steps:

• To execute the newly-added script immediately, click ▶ Start, or click ⋮ > Start with Arguments. See Manually Starting or Stopping a Script (on page 344).
• To add more scripts, first return to the scripts list by clicking "Lua Scripts" on the top (see below) or in the Menu(on page 92), and then repeat the above steps.

Lua Scripts | Script Status: xxx

Manually Starting or Stopping a Script

You can manually start or stop an existing Lua script at any time.

When starting a script, you can choose to start it either with its default arguments or with new arguments.

Tip: To have the PX2 automatically start or stop a script in response to an event, create an event rule. See Event Rules and Actions (on page 262) and Start or Stop a Lua Script (on page 300).

To manually start a script:

1. Choose Device Settings > Lua Scripts. The Lua scripts list displays.

Lua Scripts			+ Create New Script
Name	State	Autostart	Restart
script-1	Terminated	yes	no
script-2	New	no	yes
script-3	Running	no	no

1. Click the desired script whose state is either 'Terminated' or 'New.' For details, see Checking Lua Scripts States (on page 346).
2. To start with default arguments, click ▶ Start.

To start with new arguments, click ⚠ > Start with Arguments. Newly-assigned arguments will override default ones.

1. If you chose "Start with Arguments" in the above step, enter the key and value in the Start Lua Script dialog.

+ Add argument

- Click

if needing additional arguments.

Start Lua Script Key Value + Add Argument Cancel Start

1. Click Start.
2. The script output will be shown in the Script Output section.

■ If needed, click

to delete the existing output data.

Script Output PDU Manufacturer: Raritan PDU Model: PX3-5024CV-F5M5 PDU metadata: macAddress: 00:0d:5d:64:21:33 fwRevision: 3.4.0.5-43927 nameplate: --> table: 0x113ca90 rating: --> table: 0x113fd18 voltage: 100-240V power: 1.6-3.8kVA current: 16A

To manually stop a script:

1. Choose Device Settings > Lua Scripts.
2. Click the desired script whose state is either 'Running' or 'Restarting.' For details, see Checking Lua Scripts States[on page 346].
3. Click ■ Stop on the top-right corner.
4. Click Stop on the confirmation message.

To return to the scripts list:

- Click "Lua Scripts" on the top of the page.

Lua Scripts | Script Status: xxx

- Or click "Lua Scripts" in the Menu (on page 92).

Checking Lua Scripts States

Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state and settings of each script.

Lua Scripts			+ Create New Script
Name	State	Autostart	Restart
script-1	Terminated	yes	no
script-2	New	no	yes
script-3	Running	no	no

State:

Four script states are available.

State Description
New	The script is never executed since the device boot.
Running	The script is currently being executed.
Terminated	The script was once executed, but stops now.
Restarting	The script will be executed. Only the scripts with the "Restart" column set to "yes" will show this state.

Autostart:

This column indicates whether the checkbox labeled "Start automatically at system boot" is enabled. See Writing or Loading a Lua Script (on page 342).

▶ Restart:

This column indicates whether the checkbox labeled "Restart after termination" is enabled. See Writing or Loading a Lua Script (on page 342).

Modifying or Deleting a Script

You can edit an existing script's codes or even replace it with a new script. Or you can simply remove a unnecessary script from the PX2.

▶ To modify or replace a script:

1. Choose Device Settings > Lua Scripts.

2. Click the desired one in the scripts list.

3. Click : > Edit Script.

4. Make changes to the information shown, except for the script's name, which cannot be revised.

- To replace the current script, click Load Local File or Load Example to select a new script.

To delete a script:

1. Choose Device Settings > Lua Scripts.
2. Click the desired one in the scripts list.
3. Click : > Delete.
4. Click Delete on the confirmation message.

To return to the scripts list:

- Click "Lua Scripts" on the top of the page.

Lua Scripts | Script Status: xxx

- Or click "Lua Scripts" in the Menu (on page 92).

Miscellaneous

By default, the Schroff LHX/SHX heat exchanger support and Cisco EnergyWise feature implemented on the PX2 are disabled.

Support needs to be enabled for the LHX/SHX information to appear in the PX2 web interface. Besides, Schroff LHX/SHX support must be enabled in order for the LHX-MIB to be accessible through SNMP.

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

In addition, if you have to prevent others from accessing your PX2 via USB-A for security reasons, you can disable all of USB-A ports on the PX2. By default, USB-A ports are enabled.

Important: Disabling USB-A ports will disable all of 'USB-A' based features, such as wireless networking, USB cascading or pdView access using iOS mobile devices. Therefore, re-think about it before disabling USB-A.

To configure any of the above features, choose Device Settings > Miscellaneous.

To enable the support for Schroff LHX/SHX:

1. Select the Schroff LHX/SHX Support checkbox.
2. Click Save in the Features section.

3. Click Apply on the confirmation message.

4. The PX2 reboots.

To set the Cisco EnergyWise configuration:

1. Select the Enable EnergyWise checkbox.
2. Configure the following:

Field Description
Domain name Type the	name of a Cisco EnergyWise domain where the PX2 belongsUp to 127 printable ASCII characters are permitted.Spaces and asterisks are NOT acceptable.
Domain password Type	the authentication password (secret) for entering the Cisco EnergyWise domainUp to 127 printable ASCII characters are permitted.Spaces and asterisks are NOT acceptable.
Port Type a User Data	gram Protocol (UDP) port number for communications in the Cisco EnergyWise domain.Range from 1 to 65535.Default is 43440.
Polling interval Type a	polling interval to determine how often the PX2 is queried in the Cisco EnergyWise domain.Range from 30 to 600 ms.Default is 180 ms.

1. Click Save in the EnergyWise section.

For Raritan's PDU models of 3000, 4000, and 5000 series, the parent/child relationship is formed after the Cisco EnergyWise feature is enabled.

• The PDU becomes a parent domain member.
• All outlets become children of the PDU.

To disable the access to USB-A port(s):

1. Deselect the Enable USB Host Ports checkbox.
2. Click Save in the USB Host Ports section.

Tip: After the Enable USB Host Ports checkbox is deselected, only the access to USB-A port(s) is prevented while the USB-B port works as normal. That is, users still can access the USB-B port, such as accessing CLI via USB-B. To disable the access to the USB-B port, you have to apply a mechanical method.

Maintenance

Click 'Maintenance' in the Menu (on page 92), and the following submenu displays.

Maintenance

Device Information

Connected Users

Event Log

Update Firmware

Firmware History

Bulk Configuration

Backup / Restore

Network Diagnostics

Download Diagnostic

Hardware Failures

Unit Reset

About PDU

Submenu command Refer to...

Device Information	Device Information (on page 351)
Connected Users	Viewing Connected Users (on page 357)
Event Log	Viewing or Clearing the Local Event Log (on page 358)
Update Firmware	Updating the PX2 Firmware (on page 359)
Firmware History	Viewing Firmware Update History (on page 363)
Submenu command Refer to...
Bulk Configuration	Bulk Configuration (on page 364)
Backup/Restore	Backup and Restore of Device Settings (on page 371)
Network Diagnostic	Network Diagnostics (on page 372)
Download Diagnostic	Downloading Diagnostic Information (on page 374)
Hardware Failures	Hardware Issue Detection (on page 374)
Unit Reset	Rebooting the PX2 (on page 375)Resetting All Settings to Factory Defaults (on page 376)
About PDU	Retrieving Software Packages Information (on page 377)

Device Information

Using the web interface, you can retrieve hardware and software information of components or peripheral devices connected to your PX2.

Tip: If the information shown on this page does not match the latest status, press F5 to reload it.

▶ To display device information:

1. Choose Maintenance > Device Information.

Device Information information Model PX3-5024CV-F5M5 Serial number 13P1231231 Rating 100-240V, 16A, 1.6-3.8kVA, 50/60Hz Firmware version 3.5.0.5-45323 Board ID 1371234567 Board revision 0x10 PDU2-MIB download ASSETMANAGEMENT-MIB download LHX-MIB download Network Port Forwarding Outlets Overcurrent Protectors Controllers Peripheral Devices Asset Management

1. Click the desired section's title bar to show that section's information. For example, click the Network section.

Network

The number of available sections is model dependent.

Section title Information shown

Information General device information, such as modelname, serial number, firmware version,hardware revision, MIB download link(s) andso on.Note that the download link of LHX-MIB isavailable only after enabling the SchroffLHX/SHX support. See Miscellaneous (onpage 348).

Network The network information, such as the current networking mode, IPv4 and/or IPv6 addresses and so on.This tab also indicates whether the PX2 is part of a cascading configuration. See Identifying Cascaded Devices (on page 353).

Port Forwarding If the port forwarding mode is activated, this section will show a list of port numbers for all cascaded devices.

Outlets Each outlet's receptacle type, operating voltage and rated current.

Overcurrent Protectors Each overcurrent protector's type, rated current and the outlets that it protects.

Controllers Each inlet or outlet controller's serial number, board ID, firmware version and hardware version.

Inlets Each inlet's plug type, rated voltage and current.

Peripheral Devices Serial numbers, model names, position and firmware-related information of connected Raritan's environmental sensor packages.

Asset Management Each asset strip's ID, boot version, application version and protocol version.

Identifying Cascaded Devices

For information on how to cascade PX2 devices, see Cascading Multiple PX2 Devices for Sharing Ethernet Connectivity (on page 28).

This section explains how to identify a cascaded device on the Device Information page.

Note: For detailed information on the cascading configuration and restrictions, refer to the Cascading Guide, which is available from Raritan website's Support page (http://www.raritan.com/support/).

To identify the cascading status:

1. Choose Maintenance > Device Information.
2. Click the Network title bar.

Network

- If the information shown on this page does not match the latest status, press F5 to reload it.

▶ Cascading information in the Bridging mode:

- The Common section contains two read-only fields for indicating the cascading status. Note that the cascading position is NOT available in the Bridging mode.

Fields Description
Port forwarding	Indicates the Port Forwarding is disabled. See Setting the Cascading Mode (on page 218).
BRIDGE section	Indicates the device is in the Bridging mode and its IP address.

Network Common DNS servers 192.168.80.249, 192.168.80.19 DNS suffixes rgp.raritan.com. DNS resolver preference IPv6 address IPv4 routes 192.168.84.0/24 dev BRIDGE Default via 192.168.84.254 (BRIDGE) IPv6 routes none Port forwarding disabled BRIDGE IPv4 address 192.168.84.94/24

▶ Cascading information in the Port Forwarding mode:

- The Common section contains three read-only fields for indicating the cascading status.

Fields Description
Port forwarding	Indicates the Port Forwarding is enabled. See Setting the Cascading Mode (on page 218).
Cascade position	Indicates the position of the PX2 in the cascading chain.▪ 0 (zero) represents the master device.▪ A non-zero number represents a slave device. 1 is Slave 1, 2 is Slave 2, 3 is Slave 3 and so on.
Cascaded device connected	Indicates whether a slave device is detected on the USB-A or Ethernet port.▪ yes: Connection to a slave device is detected.▪ no: NO connection to a slave device is detected.

• A master device shows O(zero) in the 'Cascade position' field and yes in the 'Cascaded device connected' field.

Network
Common
DNS servers	192.168.80.249, 192.168.80.19
DNS suffixes	rgp.raritan.com.
DNS resolver preference	IPv6 address
IPv4 routes	192.168.84.0/24 dev ETH1Default via 192.168.84.254 (ETH1)
IPv6 routes	none
Port forwarding	enabled
Cascade position	0 (Master)
Cascaded device connected	yes

• A slave device in the middle position shows a non-zero number which indicates its exact position in the 'Cascade position' field and yes in the 'Cascaded device connected' field.
  The following diagram shows 1, indicating it is the first slave device - Slave 1.

Network Common DNS servers 192.168.80.249, 192.168.80.19 DNS suffixes rgp.raritan.com. DNS resolver preference IPv6 address Port forwarding enabled Cascade position 1 (Slave) Cascaded device connected yes IPv4 address 192.168.84.94

- The final slave device shows a non-zero number which indicates its position in the 'Cascade position' field and no in the 'Cascaded device connected' field.

The following diagram shows 2, indicating it is the second slave device - Slave 2. The 'Cascaded device connected' field shows no, indicating that it is the final one in the chain.

Network Common DNS servers 192.168.80.249, 192.168.80.19 DNS suffixes rgp.raritan.com. DNS resolver preference IPv6 address Port forwarding enabled Cascade position 2 (Slave) Cascaded device connected no IPv4 address 192.168.84.94

- For a list of port numbers required for accessing each cascaded device in the Port Forwarding mode, click the Port Forwarding title bar on the same page.

Port Forwarding

Viewing Connected Users

You can check which users have logged in to the PX2 and their status. If you have administrator privileges, you can terminate any user's connection to the PX2.

▶ To view and manage connected users:

1. Choose Maintenance > Connected Users. A list of logged-in users displays.

Connected Users
User name ▲	IP Adress	Client Type	Idle Time
admin	192.168.84.18	Web GUI	0 min	Disconnect
Mary	192.168.78.77	Web GUI	0 min	Disconnect

If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

Column Description

User name The login name of each connected user.

IP Address The IP address of each user's host.For the login via a local connection (serial RS-232 or USB),is displayed instead of an IP address.

Client Type The interface through which the user is being connected to the PX2.▪ Web GUI: Refers to the web interface.▪ CLI: Refers to the command line interface (CLI).The information in parentheses following "CLI" indicates how this user is connected to the CLI.- Serial: The local connection, such as the serial RS-232 or USB connection.- SSH: The SSH connection.- Telnet: The Telnet connection.▪ Webcam Live Preview: Refers to the live webcam image sessions. See below.

Idle Time The length of time for which a user remains idle.

Disconnect

1. To disconnect any user, click the corresponding

a. Click Disconnect on the confirmation message.
b. The disconnected user is forced to log out.

If there are live webcam sessions:

All Live Preview window sessions sharing the same URL, including one Primary Standalone Live Preview window and multiple Secondary Standalone Live Preview windows, are identified as one single "" user in the Connected Users list. You can disconnect a "" user to terminate all sessions sharing the same URL.

User name ▲	IP Adress	Client Type	Idle Time
	192.168.84.14	Webcam Live Preview	0 min	Disconnect

The IP address refers to the IP address of the host where the Primary Standalone Live Preview window exists, NOT the IP address of the other two associated sessions.

For more webcam information, see Webcam Management (on page 377).

Viewing or Clearing the Local Event Log

By default, the PX2 captures certain system events and saves them in a local (internal) event log.

You can view over 2000 historical events that occurred on the PX2 in the local event log. When the log size exceeds 256KB, each new entry overwrites the oldest one.

To display the local log:

1. Choose Maintenance > Event Log.

Each event entry consists of:

■ ID number of the event
■ Date and time of the event

Tip: The date and time shown on the PX2 web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of PX2 to your computer or mobile device.

■ Event type
■ A description of the event

1. To view a specific type of events only, select the desired event type in the 'Filter event class' field.

Filter event class:

Any

1. The log is refreshed automatically at a regular interval of five seconds. To avoid any new events' interruption during data browsing, you can suspend the automatic update by clicking || Pause.

- To restore automatic update, click 📄 Resume. Those new events that have not been listed yet due to suspension will be displayed in the log now.

1. To go to other pages of the log, click the pagination bar at the bottom of the page.

- When there are more than 5 pages and the page numbers listed does not show the desired one, click ... to have the bar show the next or previous five page numbers, if available.

First

Previous

1

2

3

4

5

...

Next

Last

1. If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

To clear the local log:

1. Click Clear Log on the top-right corner.
2. Click Clear Log on the confirmation message.

Updating the PX2 Firmware

Firmware files are available on Raritan website's Support page (http://www.raritan.com/support/).

When performing the firmware upgrade, the PX2 keeps each outlet's power status unchanged so no server operation is interrupted. During and after the firmware upgrade, outlets that have been powered on prior to the firmware upgrade remain powered ON and outlets that have been powered off remain powered OFF.

You must be the administrator or a user with the Firmware Update permission to update the PX2 firmware.

Before starting the upgrade, read the release notes downloaded from Raritan website's Support page (http://www.raritan.com/support/). If you have any questions or concerns about the upgrade, contact Raritan Technical Support BEFORE upgrading.

On a multi-inlet PDU, all inlets must be connected to power for the PDU to successfully upgrade its firmware.

Note that firmware upgrade via iOS mobile devices, such as iPad, requires the use of iCloud Drive or a file manager app.

Warning: Do NOT perform the firmware upgrade over a wireless network connection.

▶ Firmware upgrade restrictions:

- Intermediate firmware required for upgrades from "pre-3.3.0" to 3.5.0 or later: If your PX2 is running any firmware version older than 3.3.0, such as 3.2.30, an intermediate firmware is required for the upgrade to 3.5.0 or later. Follow the sequence below:

a. Upgrade to an intermediate firmware first, which is either 3.3.x or 3.4.x.
b. Then upgrade from the intermediate firmware to 3.5.0 or later.

- Upgrade from "pre-3.3.10" versions on a cascading CHAIN: If you are upgrading an existing cascading chain from a "pre-3.3.10" firmware version, you must follow the Upgrade Guidelines for Existing Cascading Chains (on page 361).

To update the firmware:

1. Choose Maintenance > Update Firmware.

Browse

1. Click to select an appropriate firmware file.

2. Click Upload. A progress bar appears to indicate the upload process.

3. Once complete, information of both installed and uploaded firmware versions as well as compatibility and signature-checking results are displayed.

- If anything is incorrect, click Discard Upload.

1. To proceed with the update, click Update Firmware.

Warning: Do NOT power off the PX2 during the update.

1. During the firmware update:

- A progress bar appears on the web interface, indicating the update status.

• The front panel display shows the firmware upgrade message. See Three-Digit Row(on page 74).
• The outlet LEDs flash if the relay boards are being updated. If the firmware update does not include the update of the relay board firmware, outlet LEDs do NOT flash.
• No users can successfully log in to the PX2.

• Other users' operation, if any, is forced to suspend.

• When the update is complete, the PX2 resets, and the Login page re-appears.

- Other logged-in users are logged out when the firmware update is complete.

Important: If you are using the PX2 with an SNMP manager, download its MIB again after the firmware update to ensure your SNMP manager has the correct MIB for the latest release you are using. See Using SNMP (on page 391).

Alternatives:

To use a different method to update the firmware, refer to:

• Firmware Update via SCP(on page 573)
- Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 622)
• Firmware Upgrade via USB (on page 620)

Upgrade Guidelines for Existing Cascading Chains

You must obey the following guidelines when upgrading a chain. Otherwise, a networking issue occurs.

- Firmware version 3.3.10 or later is NOT compatible with pre-3.3.10 firmware versions in terms of the cascading feature so all Raritan devices in the cascading chain must run version 3.3.10 or later.

Alternative: You can also choose to have the USB-cascading chain comprising Raritan devices run any pre-3.3.10 firmware. The disadvantage is that you will not benefit from the latest software enhancements and features.

- To upgrade an existing Raritan USB-cascading chain from a firmware version older than 3.3.10, you must start from the last slave device and so on until the master device. See Upgrade Sequence in an Existing Cascading Chain (on page 362).

Upgrade Sequence in an Existing Cascading Chain

Depending on the firmware version(s) of your cascading chain, there may or may not be limitations for the firmware upgrade sequence in the chain.

Upgrade from "pre-3.3.10" to 3.3.10 or post-3.3.10:

You must follow the firmware upgrade sequence below to upgrade a cascading chain from a firmware version older than 3.3.10 to version 3.3.10 or later. If you do not follow this upgrade sequence, you will not be able to access some cascaded devices over the Internet.

• The upgrade must start from the last slave device (S), then the second to last, the third to last, and so on until the master device (M).
  Red numbers below represent the appropriate upgrade sequence. 'N' is the final one to upgrade.

graph LR
    M --> S
    S --> S
    S --> S
    S --> S
    N <--> 4
    4 <--> 3
    3 <--> 2
    2 <--> 1

- You must upgrade ALL devices in the chain to 3.3.10 or later. If you upgrade only some devices in the chain, networking issues occur on some cascaded devices.

Exception: A few products, such as PXC, are developed much later so they may not support older firmware versions, such as 3.4.0, 3.3.10, and so on. Therefore, it is suggested to AVOID downgrading your cascading chain unless instructed by Raritan or Legrand Technical Support.

Upgrade from 3.3.10 or post-3.3.10 to post-3.3.10:

There is no upgrade sequence limitation.

Firmware version 3.3.10 is compatible with later firmware versions so you can upgrade all devices of the chain in a random order.

Important: Raritan does not guarantee that no upgrade sequence limitation will be required for all future firmware versions. It is highly suggested to check the latest revision of the Cascading Guide or your product's User Guide/Online Help before performing the firmware upgrade. The other alternative is to always stick to the same sequence as the above diagram.

Downgrade from 3.3.10 to pre-3.3.10:

There is no downgrade sequence limitation. However, firmware downgrade in a cascading chain is NOT recommended. Consult Raritan (or Legrand) Technical Support first if downgrade is needed.

Firmware versions earlier than 3.3.10 are compatible with any pre-3.3.10 version so you can downgrade or upgrade all devices of the chain in a random order when all firmware versions in the chain are prior to version 3.3.10.

Note: It is suggested to always stick to the same sequence as the above diagram though there is no firmware downgrade limitation.

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 PX2 web-interface-based upgrades. Upgrades through other management systems, such as Sunbird'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.

Full Disaster Recovery

If the firmware upgrade fails, causing the PX2 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/10 and Linux. In addition, an appropriate PX2 firmware file is required in the recovery procedure.

Viewing Firmware Update History

The firmware upgrade history is permanently stored on the PX2. It remains available even though you perform a device reboot or any firmware update.

To view the firmware update history:

1. Choose Maintenance > Firmware History.

Each firmware update event consists of:

• Update date and time
  ■ Previous firmware version
  ■ Update firmware version

• Update result

• If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 96).

Bulk Configuration

The Bulk Configuration feature lets you save generic settings of a configured PX2 device to your computer. You can use this configuration file to copy common settings to other PX2 devices of the same model and firmware version. See Bulk Configuration Restrictions (on page 365).

A source device is the PX2 device where the configuration file is downloaded/saved. A target device is the PX2 device that loads the configuration file.

By default the configuration file downloaded from the source device contains settings based on the built-in bulk profile. The built-in bulk profile defines that all settings should be saved except for device-specific settings.

You can decide which settings are downloaded and which are not by creating your own bulk configuration profile.

Note that "device-specific" settings, such as the device's IP address or environmental sensor settings, will never be included into any profile you will create so they will never be downloaded from any source device. See Device-Specific Settings (on page 726).

When the date and time settings are included in the bulk configuration file, exercise caution when distributing that file to target devices located in a different time zone than the source device.

Tip: To back up or restore "all" settings, including device-specific ones, use the Backup/Restore feature instead. See Backup and Restore of Device Settings (on page 371).

▶ Main bulk configuration procedure:

1. If you prefer customizing the bulk configuration file, create your own bulk configuration profile(s) first. See Customizing Bulk Configuration Profiles (on page 367).

2. Perform the bulk configuration operation, which includes the following steps. For details, see Performing Bulk Configuration (on page 368).

a. Make sure the desired bulk configuration profile has been selected on the source device.
b. Save a bulk configuration file from the source device.
c. Perform bulk configuration on one or multiple target devices.

Note: On startup, PX2 performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset. For example, the "Bulk configuration copied" event is logged only when the new configuration file contains the "Bulk configuration copied" event rule.

The last configuration-copying record:

If you once copied any bulk configuration or device backup file to the PX2, the last record similar to the following is displayed at the bottom of both the Bulk Configuration and Backup/Restore pages.

Last Restore: 10/18/2017, 8:33:38 PM GMT+0800, Status: OK

Tip: The date and time shown on the PX2 web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of PX2 to your computer or mobile device.

Alternatives:

To use a different bulk configuration method, refer to:

• Bulk Configuration via SCP(on page 574)
- Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 622)
- Configuration or Firmware Upgrade with a USB Drive (on page 607)
• Raw Configuration Upload and Download (on page 645)

Tip: Both the methods of uploading 'bulk configuration' file or 'raw configuration' file via SCP can serve the purpose of bulk configuration. The only difference is that you can configure device-specific settings with the upload of raw configuration but not with the 'bulk configuration' file.

Bulk Configuration Restrictions

Before performing bulk configuration, make sure your source and target devices are compatible devices for sharing general settings.

Restrictions for bulk configuration:

• The target device must be running the same firmware version as the source device.
• The target device must be of the same model type as the source device.
• Bulk configuration is permitted if the differences between the target and source devices are only "mechanical" designs which are indicated in the model name's suffix.

For example, you can perform bulk configuration between PX3-4724-E2N1K2 and PX3-4724-E2N1K9 since the only difference between the two models is their chassis colors represented by K2 (blue) and K9 (gray).

▶ Mechanical designs ignored by bulk configuration:

When the source and target devices share the same technical specifications but are only different with any "mechanical designs" which are indicated in the table below, the bulk configuration remains feasible.

These mechanical designs are represented by suffixes added to the model name of a PX2 device. In the table, x represents a number. For example, Ax can be A1, A2, A3, and so on.

Suffix Mechanical design Example
Ax The line cord's length in meters		A20 = 3.3 meters
Bx The line cord's color B501 = bright red		orange
Cx Cord types or options C4 = power cord		with the standard gauge
Dx Plug types or options D1 = IP67		watertight plug
Ex Outlet types or options E2 =		Locking C13 or Locking C19
Gx Controller options G0 = no		controller
Kx Chassis colors K6 = yellow
Lx The line cord's length in centimeters
Nx Chassis dimensions or other mechanical changes
Ox	OCP brand options
Px Special requests for device painting or printing
Qx Special requests for physical placement arrangements
Ux Different power plug brands

Customizing Bulk Configuration Profiles

A bulk profile defines which settings are downloaded/saved from the source device and which are not. The default is to apply the built-in bulk profile, which downloads all settings from the source device except for device-specific data.

If the built-in profile does not meet your needs, you can create your own profile(s), and then apply the wanted profile before downloading/saving any settings from the source device.

To create new bulk profile(s):

1. Log in to the source PX2, whose settings you want to download.

2. Choose Maintenance > Bulk Configuration.

3. Click + in the Bulk Profiles section.

4. In the Profile Name and Description fields, enter information for identifying the new profile.

5. To make this new profile the default one for future bulk configuration operations, select the "Select as default profile" checkbox.

■ After setting any profile as the default, the original default profile will no longer functions as the default one.

1. Now decide which settings are wanted and which are not.

a. Click ▼ of the setting which you want to configure.

b. When the pop-up menu appears, select one of the options. Note that the two options "Inherited" and "Built In" are mutually exclusive.

Option Description
Excluded	The setting not be downloaded.
Included The	setting will be downloaded.
Inherited The	setting will follow its parent setting (that is, the upper-level setting).If you select "Excluded" for its upper-level setting, this setting will be also excluded.If you select "Included" for its upper-level setting, this setting will be also included.The option inherited from its parent setting will be enclosed in parentheses.
Built In The	setting will follow the same setting of Raritan's built-in profile.If "Excluded" is selected in the built-in profile, this setting will be also excluded.If "Included" is selected in the built-in profile, this setting will be also included.The option inherited from the built-in profile will be enclosed in parentheses.Note: The option "Built In" is available in those settings whose corresponding settings in the built in profile have been set to a non-inherited option -- Excluded or Included.

1. Click Save.
2. Repeat the same steps if you want to create more bulk profiles.

Performing Bulk Configuration

On the source device, make sure the wanted profile has been set as the default one. If not, start from step 1 below. If yes, go to step 2 directly.

Bulk Profiles
#▲	Name	Description	Default Profile
1	Built in
2	custom-1	No network settings copied
3	custom-2	No user settings copied

Step 1: Select the desired bulk configuration profile (optional)

1. Log in to the source PX2, whose settings you want to copy.
2. Choose Maintenance > Bulk Configuration.
3. Click on the row of the wanted profile to open the Edit Bulk Profile page.
4. Select the "Select as default profile" checkbox.
5. Click Save.

Step 2: Save a bulk configuration file

You must have the Administrator Privileges or "Unrestricted View Privileges" to download the configuration.

1. Log in to the source PX2 if you have not yet.
2. Choose Maintenance > Bulk Configuration.
3. Check the Bulk Format field. If the chosen value does not match your need, change it.

Option Description
Encrypted	Partial content is base64 encoded.Its content is encrypted using the AES-128 encryption algorithm.The file is saved to the TXT format
Cleartext	Content is displayed in clear text.The file is saved to the TXT format.

1. Click Download Bulk Configuration.

2. When prompted to open or save the configuration file, click Save.

▶ Step 3: Perform bulk configuration

You must have the Administrator Privileges to upload the configuration.

1. Log in to the target PX2, which is of the same model and runs the same firmware as the source PX2.
2. Choose Maintenance > Bulk Configuration.

Browse.

1. Click to select the configuration file.

2. Click 'Upload & Restore Bulk Configuration' to copy it.

3. A message appears, prompting you to confirm the operation and enter the admin password.

4. Click to select the configuration file.

5. Click 'Upload & Restore Bulk Configuration' to copy it.
6. A message appears, prompting you to confirm the operation and enter the admin password.

Enter the admin password, and click Restore.

1. Wait until the PX2 resets and the login page re-appears.

Alternatives:

To use a different bulk configuration method, refer to:

• Bulk Configuration via SCP(on page 574)
- Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 622)
- Configuration or Firmware Upgrade with a USB Drive (on page 607)
• Raw Configuration Upload and Download (on page 645)

Tip: Both the methods of uploading 'bulk configuration' file or 'raw configuration' file via SCP can serve the purpose of bulk configuration. The only difference is that you can configure device-specific settings with the upload of raw configuration but not with the 'bulk configuration' file.

Modifying or Removing Bulk Profiles

You can modify or remove any bulk profile except for the built-in one.

Note that a profile that has been set as the default cannot be removed, either. To remove it, you have to remove its default setting first.

Choose Maintenance > Bulk Configuration. A list of profiles displays and then do one of the following.

To modify an existing profile:

1. Click on the row of the wanted profile in the list.
2. Change the settings you want.
3. Click Save.

To remove a single profile:

1. Click on the row of the wanted profile.
2. Click 📄 on the top-right corner.
3. Click Delete on the confirmation message.

To remove one or multiple profiles:

1. Click ☑ to make checkboxes appear in front of profiles.

2. Select one or multiple profiles.

- To select ALL profiles, select the topmost checkbox in the header row.

▲

Name Built in 1 custom-1 2 custom-2 3

1. Click 📁 on the top-right corner.
2. Click Delete on the confirmation message.

Backup and Restore of Device Settings

Unlike the bulk configuration file, the backup file contains ALL device settings, including device-specific data like device names and all network settings. To back up or restore the settings of PX2, you should perform the Backup/Restore feature.

All PX2 information is captured in the plain-TEXT-formatted backup file except for the device logs and TLS certificate.

Note: To perform bulk configuration among multiple PX2 devices, use the Bulk Configuration feature instead. See Bulk Configuration (on page 364).

To download a backup PX2 file:

You must have the Administrator Privileges or "Unrestricted View Privileges" to download a backup file.

1. Choose Maintenance > Backup/Restore.
2. Check the Backup Format field. If the chosen value does not match your need, change it.

Option Description
Encrypted	Partial content is base64 encoded.Its content is encrypted using the AES-128 encryption algorithm.The file is saved to the TXT format
Cleartext	Content is displayed in clear text.The file is saved to the TXT format.

1. Click Download Device Settings. Save the file onto your computer.

To restore the PX2 using a backup file:

You must have the Administrator Privileges to restore the device settings.

1. Choose Maintenance > Backup/Restore.

Browse.

1. Click to select the backup file.

2. Click 'Upload & Restore Device Settings' to upload the file.

- A message appears, prompting you to confirm the operation and enter the admin password.

1. Enter the admin password, then click Restore.

2. Wait until the PX2 resets and the Login page re-appears, indicating that the restore is complete.

Note: On startup, PX2 performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset. For example, the "Bulk configuration copied" event is logged only when the new configuration file contains the "Bulk configuration copied" event rule.

The last configuration-copying record:

If you once copied any bulk configuration or device backup file to the PX2, the last record similar to the following is displayed at the bottom of both the Bulk Configuration and Backup/Restore pages.

Last Restore: 10/18/2017, 8:33:38 PM GMT+0800, Status: OK

Alternative:

To use a different method to perform backup/restore, refer to:

• Backup and Restore via SCP(on page 575)

Network Diagnostics

PX2 provides the following tools in the web interface for diagnosing potential networking issues.

• Ping: The tool is useful for checking whether a host is accessible through the network or Internet.
• Trace Route: The tool lets you find out the route over the network between two hosts or systems.
• List TCP Connections: You can use this function to display a list of TCP connections.

Tip: These network diagnostic tools are also available through CLI. See Network Troubleshooting (on page 568).

Choose Maintenance > Network Diagnostics, and then perform any function below.

Ping:

1. Type values in the following fields.

Field Description
Network Host The name or IP address of the host that you want to check.
Number of Requests	A number up to 20.This determines how many packets are sent for pinging the host.

1. Click Run Ping to ping the host. The Ping results are then displayed.

Trace Route:

1. Type values in the following fields.

Field/setting Description

Host Name The IP address or name of the host whose route you want to check.

Timeout(s) A timeout value in seconds to end the trace route operation.

Use ICMP Packets To use the Internet Control Message Protocol (ICMP) packets to perform the trace route command, select this checkbox.

1. Click Run. The Trace Route results are then displayed.

List TCP Connections:

1. Click the List TCP Connections title bar to show the list.

Downloading Diagnostic Information

Important: 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 PX2 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 or Unrestricted View Privileges.

▶ To retrieve a diagnostic file:

1. Choose Maintenance > Download Diagnostic >

Download Diagnostic

1. The system prompts you to save or open the file. Save the file then.
2. E-mail this file as instructed by Raritan Technical Support.

Hardware Issue Detection

This page lists any internal hardware issues PX2 has detected, including current events and historical records.

Choose Maintenance > Hardware Failures, and the page similar to either of the following diagrams opens.

NO hardware failures detected:

Hardware Failures

No hardware failures

Hardware failure(s) detected:

Hardware Failures

Current Hardware Failures
Failure Message	Last Asserted ▲	Last Deasserted	Number of Occurrences
I2C bus 0 is stuck.	1/1/2018, 1:18:24 AM UTC+0100	1/1/2018, 1:00:00 AM UTC+0100	17
Past Hardware Failures
Failure Message	Last Asserted ▲	Last Deasserted	Number of Occurrences
Network device ETH2 was not detected.	8/3/2018, 3:06:46 PM UTC+0200	8/3/2018, 3:13:10 PM UTC+0200	7

Hardware Failure alerts on the Dashboard page:

Note that current hardware failure events, if any, will also display on the Dashboard (on page 97).

Hardware failure types:

Hardware issues Description
Network device not detected	A specific networking interface of PX2 is NOT detected.
I2C Bus stuck	A specific I2C bus is stuck, which affects the communication with sensors.
Slave controller not reachable	Communication with a specific slave controller fails.
Slave controller malfunction	A specific slave controller does not work properly.
Outlet power state inconsistent	The physical power state of a specific outlet is different from the chosen power state set by the software.

Rebooting the PX2

You can remotely reboot the PX2 via the web interface.

Resetting the PX2 does not interrupt the operation of connected servers because there is no loss of power to outlets. During and after the reboot, outlets that have been powered on prior to the reboot remain powered on, and outlets that have been powered off remain powered off.

Warning: Rebooting the PX2 deletes all webcam snapshots that are saved onto the PX2 locally. If needed, download important snapshots before rebooting the device. See Viewing and Managing Locally-Saved Snapshots(on page 385).

To reboot the device:

1. Choose Maintenance > Unit Reset >

Reboot Unit

Reboot Unit Do you really want to reboot the device? Cancel Reboot

1. Click Reboot to restart the PX2.
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 restart is complete, the login page opens.

Note: If you are not redirected to the login page after the restart is complete, click the text "this link" in the countdown message.

Resetting All Settings to Factory Defaults

You must have the Administrator Privileges to reset all settings of the PX2 to factory defaults.

Important: Exercise caution before resetting the PX2 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.

To reset the device to factory defaults:

1. Choose Maintenance > Unit Reset >

Reset to Factory Defaults

Factory Reset Do you really want to reset the device to factory defaults? Saying yes will clear all settings, including the network setup. Cancel Factory Reset

1. Click Factory Reset to reset the PX2 to factory defaults.
2. A message appears, with a countdown timer showing the remaining time of the operation. It takes about two minutes to complete.
3. When the reset is complete, the login page opens.

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

Alternative:

There are two more methods to reset the device to factory defaults.

• Use the "mechanical" reset button
  • Perform the CLI command

For details, see Resetting to Factory Defaults(on page 651).

Retrieving Software Packages Information

You can check the current firmware version and the information of all open source packages embedded in the PX2 through the web interface.

To retrieve the embedded software packages information:

1. Choose Maintenance > About PDU. A list of open source packages is displayed.
2. You can click any link to access related information or download any software package.

Webcam Management

The 'Webcams' menu item appears when there is any webcam(s) connected to the PX2, or when there are snapshots saved onto the PX2 already. See Connecting a Logitech Webcam (on page 65).

Chapter 6: Using the Web Interface

Dashboard Webcams User Management > Device Settings > Maintenance >

With a Logitech ^® webcam connected to the PX2, you can visually monitor the environment around the PX2 via snapshots or videos captured by the webcam.

▶ Permissions required:

To do... Permission(s) required
View snapshots and videos	Either permission below: · Change Webcam Configuration · View Webcam Snapshots and Configuration
Configure webcam settings	Change Webcam Configuration

Additional webcam-related actions you can take:

Action Refer to
Manually store snapshots taken from the webcam onto the PX2 or a remote server	Configuring Webcams and Viewing Live Images (on page 379)Changing Storage Settings (on page 387)
Send a snapshot or video session's link to other people via email or instant message	Sending Links to Snapshots or Videos (on page 382)
Create event rules to trigger emails containing snapshots from a webcam	Available Actions (on page 284)

For more information on your Logitech webcam, refer to the user documentation accompanying it.

Configuring Webcams and Viewing Live Images

To configure a webcam or view live snapshot/video sessions, choose Webcams in the Menu (on page 92). Then click the desired webcam to open that webcam's page.

Note that default webcam names are determined by the detection order. The one that is detected first is named Webcam, and the other that is detected later is named Webcam 2.

Webcams
Name ▲	Location	Resolution	Mode
Webcam		352x288	Snapshot

The Webcam page consists of three sections -- Live Preview, Image Controls and Settings.

Live Preview:

1. By default the Live Preview section is opened, displaying the live snapshot/video session captured by the webcam.
2. The default is to show live snapshots. Interval time and capture date/time of the image are displayed on the top of the image.

Live Preview Interval 5s 9/29/2017 7:37:03 PM GMT+0800 Raritan Save Snapshot New Live Preview Window

Tip: The date and time shown on the PX2 web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of PX2 to your computer or mobile device.

1. To save the current image onto PX2 or a remote server, click

Save Snapshot

• The default storage location for snapshots is the PX2 device. To save them onto a remote server, see Changing Storage Settings (on page 387).

• To download an image onto your computer, move your mouse to that image, right click on it, and choose Save Image As.

• To have the same live session displayed in a separate window, click

New Live Preview Window

■ A separate window appears, which is called the Primary Standalone Live Preview window in this User Guide.
- You can send out this window's URL to share the live image with others. See Sending Links to Snapshots or Videos (on page 382).

Note: Make sure your browser does not block the pop-up window, or the separate window does not show up.

1. To switch between snapshot and video modes, refer to the Settings section below.

In the video mode, the number of frames to take per second (fps) and the video capture date/time are displayed on the top of the image.

▶ Image Controls:

1. Click the Image Controls title bar to expand it.

Image Controls

1. Adjust the brightness, contrast, saturation and gain by modifying their values or adjusting the corresponding slide bar.

2. To customize the gain value, you must deselect the Auto Gain checkbox first.

3. To restore all settings to this webcam's factory defaults, click

Set to Webcam Defaults

Settings:

1. By default the Settings section is open. If not, click the Settings title bar.
2. Click Edit Settings.
3. Enter a name for the webcam. Up to 64 ASCII printable characters are supported.

- If configured to store snapshots on a remote server, the webcam's name determines the name of the folder where snapshots are stored. See Changing Storage Settings(on page 387) and Identifying Snapshots Folders on Remote Servers(on page 389).

- It is suggested to customize a webcam's name "prior to" saving snapshots on the remote server. In case you change the webcam's name after saving any snapshots, PX2 will create a new folder with the new webcam name while keeping the old folder with the old name.

1. Type the location information in each location field as needed. Up to 63 ASCII printable characters are supported.

- Note that the location data you enter is not available in those snapshots stored on remote servers.

Tip: If the webcam's location is important, you can customize the webcam's name based on its location when configuring PX2 to save snapshots onto a remote server.

1. Select a resolution for the webcam.

- If you connect two webcams to one USB-A port using a powered USB hub, set the resolution to 352x288 or lower for optimal performance.

1. Select the webcam mode.

Mode Description
Video	The webcam enters the video mode.▪ Set the 'Framerate' (frames per second) as needed.
Snapshot	The webcam shows static images captured by the webcam at a regular interval.▪ To determine the interval, set the 'Time Between Snapshots' (seconds) as needed.

1. Click Save. The changes made to the settings are applied to the live session in the above Live Preview section immediately.

To return to the Webcam Management page:

- Click Webcam Management on the top of the page.

◀ Webcam Management | Webcam

- Or click Webcams again in the Menu (on page 92).

Sending Links to Snapshots or Videos

When opening a Primary Standalone Live Preview window, a unique URL is generated for this window session. You can email or instant message this URL to as many people as possible as long as your system resources permit. Recipients can then click on the provided link and view live snapshots or videos simultaneously in the Secondary Standalone Live Preview window(s).

Tip: All Live Preview window sessions sharing the same URL, including one Primary Standalone Live Preview window and multiple Secondary Standalone Live Preview windows, are identified as one single "" user in the Connected Users list. You can disconnect a "" user to terminate all sessions sharing the same URL. See Viewing Connected Users (on page 357).

Best practice:

1. The sender opens the Primary Standalone Live Preview window, and sends the link to one or multiple recipients.
2. The sender must wait until at least one recipient opens the Secondary Standalone Live Preview window.
3. The recipient(s) should inform the sender that the link has been opened.
4. Now the sender can close the Primary Standalone Live Preview window.

■ For additional information, see How Long a Link Remains Accessible (on page 384).

To send a snapshot or video link via email or instant message:

1. Choose Webcams in the Menu (on page 92).
2. Click the desired webcam to open the Webcam page.

- Note that default webcam names are determined by the detection order. The one that is detected first is named Webcam, and the other that is detected later is named Webcam 2.

Webcams
Name ▲	Location	Resolution	Mode
Webcam		352x288	Snapshot

1. Click in the Live Preview section. The live snapshot or video in a standalone window opens. See Configuring Webcams and Viewing Live Images (on page 379).

2. Copy the URL from that live preview window. a. Select the URL shown on the top of the image.

Webcam Live Preview - Webcam - Mo... https://192.168 84.20/webcam/livepreview/liveprev Interval 3s 6:26:17 10:28 AM

b. Right click to copy the URL, or press CTRL+ C.

1. Send the URL link through an email or instant message application to one or multiple persons.
2. Leave the live preview window open until the recipient(s) opens the snapshot or video via the link.

How Long a Link Remains Accessible

For documentation purposes, the one who opens and sends the URL of the Primary Standalone Live Preview window is called User A and the two recipients of the same URL link are called User B and C.

User C is able to access the snapshot or video image via the link when the URL link remains valid, which can be one of these scenarios:

• The Primary Standalone Live Preview window remains open on User A's computer. If so, even though User A logs out of the PX2 or the login session times out, the link remains accessible.
• User B's Secondary Standalone Live Preview window remains open. If so, even though User A already closes the Primary Standalone Live Preview window, the link remains accessible.
• Neither User A's Primary Standalone Live Preview window nor User B's Secondary Standalone Live Preview window remains open, but it has not exceeded two minutes yet after the final live preview window session was closed.

Note: The link is no longer valid after two minutes since the final live preview window is closed.

Viewing and Managing Locally-Saved Snapshots

This section describes the operation for snapshots saved onto the PX2 device only. To access snapshots saved onto remote servers, you must use appropriate third-party applications, such as an FTP client, to access them.

When saving a snapshot, it is stored locally on the PX2 device by default. For snapshot-saving operations, see Configuring Webcams and Viewing Live Images (on page 379).

Up to 10 snapshots can be stored onto the PX2. The oldest snapshot is automatically overridden by the newest one when the total of snapshots exceeds 10, if no snapshots are deleted manually.

When there are more than one webcam connected, then the oldest snapshot of the webcam "with the most snapshots" is overridden.

Tip: To save more than 10 snapshots, you must change the storage location from the PX2 to an FTP or Common Internet File System (CIFS)/Samba server. See Changing Storage Settings (on page 387).

Snapshots are saved as JPG files, and named based on the sequential numbers, such as 1.jpg, 2.jpg, 3.jpg and the like.

Warning: Rebooting the PX2 deletes all webcam snapshots that are saved onto the PX2 locally. If needed, download important snapshots before rebooting the device.

▶ To view saved snapshots:

Browse Snapshots

1. Choose Webcams > opens.

The Snapshots page

1. Click the snapshot you want to view from the list.

< Webcam Management | Snapshots

Snapshot	Size	Time▼	Webcam
4.jpg	3.9 kiB	9/29/2017, 7:44:04 PM GMT+0800	Webcam
3.jpg	8.0 kiB	9/29/2017, 7:43:03 PM GMT+0800	Webcam
2.jpg	8.0 kiB	9/29/2017, 7:38:12 PM GMT+0800	Webcam
1.jpg	8.2 kiB	9/29/2017, 7:34:42 PM GMT+0800	Webcam

Tip: The date and time shown on the PX2 web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of PX2 to your computer or mobile device.

1. The selected snapshot as well as its information, such as captured time and resolution, is displayed on the same page.
2. If the latest saved snapshot is not listed yet, click

To manually delete any snapshots:

1. Click ☑ to make checkboxes appear.
2. Select the checkboxes of the images you want to remove.

- To select all images, select the topmost checkbox in the header row.

Snapshot 4.jpg 3.jpg 2.jpg 1.jpg

1. On the top of the list, click

1. Click Delete on the confirmation message.

To download any image onto the computer:

- To download an image onto your computer, move your mouse to that image, right click on it, and choose Save Image As.

Changing Storage Settings

Important: The PX2 web interface only lists the snapshots stored locally on the PX2 device, but does NOT list those saved onto remote servers. You must launch appropriate third-party applications, such as an FTP client, to access and manage the snapshots stored on remote servers.

The default is to store snapshots onto the PX2 device, which has a limitation of 10 snapshots. Note that any operation involving device reboot will remove the snapshots saved on the PX2, such as firmware upgrade.

If you have either or both needs below, you must save snapshots onto a remote server like FTP or CIFS/Samba, instead of the PX2.

• Total number of saved snapshots will exceed 10.
- Saved snapshots must be stored permanently, or at least should not be removed by the PX2 device's reboot.

To configure the storage settings:

1. Choose Webcams > Edit Settings.

Snapshot Storage Edit Settings Storage Type Local Browse Snapshots

1. Click the Storage Type field to select the desired storage location and configure as needed.

Note: When entering user credentials for remote servers, make sure the user credentials you enter have the write permission, or NO snapshots can be successfully saved onto remote servers.

Storage location	Description
Local	'Local' means the PX2 device. This is the default.It can store a maximum of 10 snapshots only.The web interface can list and display all snapshots stored on the PX2. See Viewing and Managing Locally-Saved Snapshots (on page 385).All s napshots are CLEARED when the PX2 is rebooted.
CIFS/Samba	Snapshots are saved onto a Common Internet File System/Samba.Total number of saved snapshots depends on the server's capacity.All saved snapshots remain available after rebooting the PX2.Configure the following fields:* Server- the desired CIFS/Samba server* Share/Folder- this is the share drive/folder* Username- for server access* Password- for server access
FTP	Snapshots are saved onto a FTP server.Total number of saved snapshots depends on the server's capacity.All saved snapshots remain available after rebooting the PX2.Configure the following fields:* Server URL- the FTP server's path* Username- for server access* Password- for server access

To find where the snapshots are saved on CIFS/Samba or FTP, see Identifying Snapshots Folders on Remote Servers (on page 389).

3. Click Save.

Warning: Before disconnecting or powering off any remote server where the webcam snapshots are being stored, you must first change the storage settings, or the connectivity issue of the remote server may degrade the performance of the PX2 web interface. If this issue occurs, first restore the connectivity of the remote server and then change the storage settings of the webcam snapshots.

Identifying Snapshots Folders on Remote Servers

If saving snapshots onto a remote server, you can access those snapshots via an appropriate third-party application, such as an FTP client.

All snapshots are saved as JPEG and named according to the date and time when saving the snapshots. Note that the date and time of the filename are based on the time zone of the PX2 device rather than that of the computer or mobile device you are operating.

Tip: To check the time zone of your PX2, choose Device Settings > Date/Time. See Setting the Date and Time (on page 258).

The structure of a snapshots folder looks similar to the diagram below.

graph TD
    A["user"] --> B["? PH83650005"]
    A --> C["? PH85350018"]
    A --> D["? Webcam"]
    A --> E["? Webcam 2"]
    B --> F["②"]
    C --> G["③"]
    D --> H["④"]

Number Folder name description

1	User-defined parent directory, whose name depends your server settings, such as your FTP configuration.
2	Serial number of your PX2 device where the webcam is connected. For example, PH85350018.To find your PX2 serial number, seeDevice Information(on page 351).
3	The name of the webcam that PX2 detects first.This is the folder where the snapshots captured by the first webcam are stored.The first webcam's default name is "Webcam".You can customize the webcam's name, which will change the snapshots folder's name.SeeConfiguring Webcams and Viewing Live Images(on page 379).If t he webcam's location is important, you can customize the webcam's name based on its location when configuring PX2 to save snapshots onto a remote server.

Number Folder name description

4

The name of the webcam that PX2 detects later, if an additional webcam is connected.

This is the folder where the snapshots captured by the second webcam are stored.

• The second webcam's default name is "Webcam 2".
• Changing this webcam's name also changes the second snapshots folder's name.
• If the webcam's location is important, you can customize the webcam's name based on its location when configuring PX2 to save snapshots onto a remote server.

Note: It is suggested to customize a webcam's name "prior to" saving snapshots on the remote server. In case you change the webcam's name after saving any snapshots, PX2 will create a new folder with the new webcam name while keeping the old folder with the old name.

Chapter 7 Using SNMP

This SNMP section helps you set up the PX2 for use with an SNMP manager. The PX2 can be configured to send traps or informs to an SNMP manager, as well as receive GET and SET commands in order to retrieve status and configure some basic settings.

In This Chapter

Enabling and Configuring SNMP....391

Downloading SNMP MIB 396

SNMP Gets and Sets....396

Enabling and Configuring SNMP

To communicate with an SNMP manager, you must enable SNMP protocols on the PX2. By default the "read-only" mode of SNMP v1/v2c is enabled.

The SNMP v3 protocol allows for encrypted communication. To take advantage of this, you must configure the users with the SNMP v3 access permission and set Authentication Pass Phrase and Privacy Pass Phrase, which act as shared secrets between SNMP and the PX2.

Important: You must download the SNMP MIB for your PX2 to use with your SNMP manager. See Downloading SNMP MIB (on page 396).

To enable SNMP v1/v2c and/or v3 protocols:

1. Choose Device Settings > Network Services > SNMP.

2. In the SNMP Agent section, enable SNMP v1/v2c or SNMP v3, and configure related fields, such as the community strings.

- If SNMP v3 is enabled, you must determine which users shall have the SNMP v3 access permission. See below.

For details, see Configuring SNMP Settings (on page 228).

To configure users for SNMP v3 access:

1. Choose User Management > Users.

2. Create or modify users to enable their SNMP v3 access permission.

- If authentication and privacy is enabled, configure the SNMP password(s) in the user settings.

For details, see Creating Users(on page 193).

▶ To enable SNMP notifications:

1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Notifications section, enable the SNMP notification feature, and configure related fields. For details, refer to:
   ■ SNMPv2c Notifications (on page 392)
   ■ SNMPv3 Notifications (on page 393)

Note: Any changes made to the 'SNMP Notifications' section on the SNMP page will update the settings of the System SNMP Notification Action, and vice versa. See Available Actions (on page 284).

SNMPv2c Notifications

1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox is selected.
3. In the SNMP Notifications section, make sure the Enable SNMP Notifications checkbox is selected.

SNMP Notifications Enable SNMP notifications Notification type SNMPv2c inform Timeout 3 s Number of retries 5

Host Port Community

1. Select SNMPv2c Trap or SNMPv2c Inform as the notification type.
2. Type values in the following fields.

Field Description
Timeout The interval of time, in seconds, after which a new inform communication is resent if the first is not received.▪ For example, resend a new inform communication once every 3 seconds.
Number of Retries The number of times you want to resend the inform communication if it fails.▪ For example, inform communications are resent up to 5 times when the initial communication fails.
Host The IP address of the device(s) you want to access.This is the address to which notifications are sent by the SNMP agent.You can specify up to 3 SNMP destinations.
Port The port number used to access the device(s).
Community The SNMP community string to access the device(s). The community is the group representing the PX2 and all SNMP management stations.

1. Click Save.

SNMPv3 Notifications

1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox is selected.
3. In the SNMP Notifications section, make sure the Enable SNMP Notifications checkbox is selected.

SNMP Notifications Enable SNMP notifications Notification type SNMPv3 inform Host required Port 162 User ID required Timeout 3 s Number of retries 5 Security level authPriv Authentication protocol SHA Authentication passphrase required Confirm authentication passphrase Privacy protocol AES Privacy passphrase required Confirm privacy passphrase

1. Select SNMPv3 Trap or SNMPv3 Inform as the notification type.
2. For SNMP TRAPs, the engine ID is prepopulated.
3. Type values in the following fields.

Field Description
Host The IP address of the device(s) you want to access.This is the address to which notifications are sent by the SNMP agent.
Field Description
Port The port number used to access the device(s).
User ID User name for accessing the device.▪ Make sure the user has the SNMP v3 access permission.
Timeout The interval of time, in seconds, after which a new inform communication is resent if the first is not received.▪ For example, resend a new inform communication once every 3 seconds.
Number of Retries Specify the number of times you want to resend the inform communication if it fails.▪ For example, inform communications are resent up to 5 times when the initial communication fails.
Security Level Three types are available.▪ noAuthNoPriv - neither authentication nor privacy protocols are needed.▪ authNoPriv - only authentication is required.▪ authPriv - both authentication and privacy protocols are required.
Authentication Protocol, Authentication Passphrase, Confirm Authentication Passphrase	The three fields are available when the security level is set to AuthNoPriv or authPriv.▪ Select the authentication protocol - MD5 or SHA▪ Enter the authentication passphrase
Privacy Protocol, Privacy Passphrase, Confirm Privacy Passphrase	The three fields are available when the security level is set to authPriv.▪ Select the Privacy Protocol - DES or AES▪ Enter the privacy passphrase and then confirm the privacy passphrase

1. Click Save.

Downloading SNMP MIB

You must download an appropriate SNMP MIB file for successful SNMP communications. Always use the latest SNMP MIB downloaded from the current firmware of your PX2.

You can download the MIBs from two different pages of the web interface.

▶ MIB download via the SNMP page:

1. Choose Device Settings > Network Services > SNMP.
2. Click the Download MIBs title bar.

Download MIBs

1. Select the desired MIB file to download.

■ PDU2-MIB: The SNMP MIB file for PX2 power management.
- ASSETMANAGEMENT-MIB: The SNMP MIB file for asset management.
- LHX-MIB: The SNMP MIB file for managing the LHX/SHX heat exchanger(s).

1. Click Save to save the file onto your computer.

▶ MIB download via the Device Information page:

1. Choose Maintenance > Device Information.
2. In the Information section, click the desired download link:

■ PDU2-MIB
■ ASSETMANAGEMENT-MIB
LHX MIB

1. Click Save to save the file onto your computer.

Note: LHX-MIB is available only after the LHX/SHX support has been enabled. See Miscellaneous (on page 348).

SNMP Gets and Sets

In addition to sending notifications, the PX2 is able to receive SNMP get and set requests from third-party SNMP managers.

• Get requests are used to retrieve information about the PX2, 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 PX2 device name. When you change the SNMP system name, the device name shown in the web interface is also changed.

The PX2 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 PX2 MIB.

The PX2 MIB

The SNMP MIB file is required for using your PX2 with an SNMP manager. An SNMP MIB file describes the SNMP functions.

Layout

Opening the MIB reveals the custom objects that describe the PX2 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 PX2 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 PX2 to generate a warning and send an SNMP notification when certain parameters are exceeded. See Sensor Threshold Settings (on page 705) 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.

Configuring NTP Server Settings

Using SNMP, you can change the following NTP server-related settings in the unitConfigurationTable:

• Enable or disable synchronization of the device's date and time with NTP servers (synchronizeWithNTPServer)
• Enable or disable the use of DHCP-assigned NTP servers if synchronization with NTP servers is enabled (useDHCPPProvidedNTPServer)
• Manually assign the primary NTP server if the use of DHCP-assigned NTP servers is disabled (firstNTPServerAddressType and firstNTPServerAddress)
• Manually assign the secondary NTP server (optional) (secondNTPServerAddressType and secondNTPServerAddress)

Tip: To specify the time zone, use the CLI or web interface instead. For the CLI, see Setting the Time Zone (on page 470). For the web interface, see Setting the Date and Time (on page 258).

When using the SNMP SET command to specify or change NTP servers, it is required that both the NTP server's address type and address be set in the command line simultaneously.

For example, the SNMP command to change the primary NTP server's address from IPv4 (192.168.84.84) to host name looks similar to the following:

snmpset -v2c -c private 192.168.84.84

firstNTPServerAddressType = dns firstNTPServerAddress = "angu.pep.com"

Retrieving Energy Usage

You can discover how much energy an IT device consumes by retrieving the Active Energy for the outlet this IT device is plugged into. The Active Energy values are included in the outletSensorMeasurementsTable, along with other outlet sensor readings.

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 8 Using the Command Line Interface

This section explains how to use the command line interface (CLI) to administer the PX2.

Note that available CLI commands are model dependent.

CLI commands are case sensitive.

In This Chapter

About the Interface....400

Logging in to CLI....401

The ? Command for Showing Available Commands.... 404

Querying Available Parameters for a Command.... 405

Showing Information 405

Clearing Information 435

Configuring the PX2 Device and Network....436

Load Shedding Configuration Commands 560

Power Control Operations....561

Actuator Control Operations 564

Unblocking a User 566

Resetting the PX2 566

Network Troubleshooting 568

Retrieving Previous Commands....571

Automatically Completing a Command 571

Logging out of CLI 572

About the Interface

The PX2 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 PX2
• Display the PX2 and network information, such as the device name, firmware version, IP address, and so on
• Configure the PX2 and network settings
• Troubleshoot network problems

You can access the interface over a local connection using a terminal emulation program such as HyperTerminal, or via a Telnet or SSH client such as PuTTY.

Note: Telnet access is disabled by default because it communicates openly and is thus insecure. To enable Telnet, see Changing Telnet Settings (on page 233).

Logging in to CLI

Logging in via HyperTerminal over a local connection is a little different than logging in using SSH or Telnet.

If a security login agreement has been enabled, you must accept the agreement in order to complete the login. Users are authenticated first and the security banner is checked afterwards.

With HyperTerminal

You can use any terminal emulation programs for local access to the command line interface.

This section illustrates HyperTerminal, which is part of Windows operating systems prior to Windows Vista.

To log in using HyperTerminal:

1. Connect your computer to the product via a local (USB or RS-232) connection.
2. Launch HyperTerminal on your computer and open a console window. When the window first opens, it is blank.

Make sure the COM port settings use this configuration:

• Bits per second = 115200 (115.2Kbps)
• Data bits = 8
• Stop bits = 1
  ■ Parity = None
  ■ Flow control = None

Tip: For a USB connection, you can determine the COM port by choosing Control Panel > System > Hardware > Device Manager, and locating the "Dominion PX2 Serial Console" under the Ports group.

1. In the communications program, press Enter to send a carriage return to the PX2. The Username prompt appears.

Username: _

1. Type a name and press Enter. The name is case sensitive. Then you are prompted to enter a password.

Username: admin

Password: _

1. Type a password and press Enter. The password is case sensitive.

After properly entering the password, the # or > system prompt appears. See Different CLI Modes and Prompts(on page 403) in the User Guide for more information.

Tip: The "Last Login" information, including the date and time, is also displayed if the same user account was used to log in to this product's web interface or CLI.

1. You are now logged in to the command line interface and can begin administering this product.

With SSH or Telnet

You can remotely log in to the command line interface (CLI) using an SSH or Telnet client, such as PuTTY.

Note: PuTTY is a free program you can download from the Internet. Refer to PuTTY's documentation for details on configuration.

To log in using SSH or Telnet:

1. Ensure SSH or Telnet has been enabled. See Configuring Network Services (on page 226) in the User Guide.
2. Launch an SSH or Telnet client and open a console window. A login prompt appears.

login as:

1. Type a name and press Enter. The name is case sensitive.

Note: If using the SSH client, the name must NOT exceed 25 characters. Otherwise, the login fails.

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.
2. After properly entering the password, the # or > system prompt appears. See Different CLI Modes and Prompts(on page 403) in the User Guide for more information.

Tip: The "Last Login" information, including the date and time, is also displayed if the same user account was used to log in to this product's web interface or CLI.

1. You are now logged in to the command line interface and can begin administering this product.

With an Analog Modem

The PX2 supports remote access to the CLI via a connected analog modem. This feature is especially useful when the LAN access is not available.

To connect to the PX2 via the modem:

1. Make sure the PX2 has an analog modem connected. See Connecting an Analog Modem (on page 66).
2. Make sure the computer you are using has an appropriate modem connected.
3. Launch a terminal emulation program, and configure its baud rate settings according to the baud rate set for the analog modem connected to the PX2. See Configuring the Serial Port (on page 340).
4. Ty pe the following AT command to make a connection with the PX2. ATD
5. The CLI login prompt appears after the connection is established successfully. Then type the user name and password to log in to the CLI.

To disconnect from the PX2:

1. Return to the modem's command mode using the escape code +++.
2. After the OK prompt appears, type the following AT command to disconnect from the PX2.
   ATH

Different CLI Modes and Prompts

Depending on the login name you use and the mode you enter, the system prompt in the CLI varies.

• User Mode: When you log in as a normal user, who may not have full permissions to configure the PX2, the > prompt appears.
• Administrator Mode: When you log in as an administrator, who has full permissions to configure the PX2, the # prompt appears.
• Configuration Mode: You can enter the configuration mode from the administrator or user mode. In this mode, the prompt changes to config:# or config:> and you can change PX2 device and network configurations. See Entering Configuration Mode (on page 436).
• Diagnostic Mode: You can enter the diagnostic mode from the administrator or user mode. In this mode, the prompt changes to diag:# or diag:> and you can perform the network troubleshooting commands, such as the ping command. See Entering Diagnostic Mode (on page 568).

Closing a Local Connection

Close the window or terminal emulation program when you finish accessing the PX2 over the local connection.

When accessing or upgrading multiple PX2 devices, do not transfer the local connection cable from one device to another without closing the local connection window first.

The ? Command for Showing Available Commands

When you are not familiar with CLI commands, you can press the ? key at anytime for one of the following purposes.

• Show a list of main CLI commands available in the current mode.
- Show a list of available commands or parameters for the command you type. See Querying Available Parameters for a Command (on page 405).

In the administrator mode:

# ?

In the configuration mode:

config:# ?

In the diagnostic mode:

diag:# ?

Press Enter after pressing the ? command, and a list of main commands for the current mode is displayed.

Tip: To automatically complete a command after typing part of the full command, see Automatically Completing a Command (on page 571).

To re-execute one of the previous commands, see Retrieving Previous Commands (on page 571).

Querying Available Parameters for a Command

f you are not sure what commands or parameters are available for a particular type of CLI command or its syntax, you can have the CLI show them by adding a space and the help command (?) or list command (ls) to the end of that command. A list of available parameters and their descriptions will be displayed.

The following shows a few query examples.

To query available parameters for the "show" command:

# show ?

To query available parameters for the "show user" command:

# show user ?

To query available role configuration parameters:

config:#role?

To query available parameters for the "role create" command:

config:# role create ?

Tip: To automatically complete a command after typing part of the full command, see Automatically Completing a Command (on page 571). To re-execute one of the previous commands, see Retrieving Previous Commands (on page 571).

Showing Information

You can use the show commands to view current settings or the status of the PX2 device or part of it, such as the IP address, networking mode, firmware version, states or readings of internal or external sensors, user profiles, and so on.

Some "show" commands have two formats: one with the parameter "details" and the other without. The difference is that the command without the parameter "details" displays a shortened version of information while the other displays in-depth information.

After typing a "show" command, press Enter to execute it.

Note: Depending on your login name, the # prompt may be replaced by the > prompt. See Different CLI Modes and Prompts (on page 403).

Network Configuration

This command shows all network configuration and all network interfaces' information, such as the IP address, MAC address, the Ethernet interface's duplex mode, and the wireless interface's status/settings.

# show network

IP Configuration

This command shows the IP settings shared by all network interfaces, such as DNS and routes. Information shown will include both IPv4 and IPv6 configuration.

Tip: To show IPv4-only and IPv6-only configuration data, seeIPv4-Only or IPv6-Only Configuration (on page 407).

# show network ip common

To show the IP settings of a specific network interface, use the following command.

# show network ip interface

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Option Description

ethernet Show the IP-related configuration of the ETHERNET interface.

wireless Show the IP-related configuration of the WIRELESS interface.

bridge Show the IP-related configuration of the BRIDGE interface.

all Show the IP-related configuration of all interfaces.

IPv4-Only or IPv6-Only Configuration

To show IPv4-only or IPv6-only configuration, use any of the following commands.

Tip: To show both IPv4 and IPv6 configuration data, seeIP Configuration (on page 406).

To show IPv4 settings shared by all network interfaces, such as DNS and routes:

# show network ipv4 common

To show IPv6 settings shared by all network interfaces, such as DNS and routes:

# show network ipv6 common

To show the IPv4 configuration of a specific network interface:

# show network ipv4 interface

To show the IPv6 configuration of a specific network interface:

# show network ipv6 interface

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Option Description

ethernet Show the IPv4 or IPv6 configuration of the ETHERNET interface.

wireless Show the IPv4 or IPv6 configuration of the WIRELESS interface.

bridge Show the IPv4 or IPv6 configuration of the BRIDGE interface.

all Show the IPv4 or IPv6 configuration of all interfaces.

Network Interface Settings

This command shows the specified network interface's information which is NOT related to IP configuration. For example, the Ethernet port's LAN interface speed and duplex mode, or the wireless interface's SSID parameter and authentication protocol.

# show network interface

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Option Description
ethernet Show the ETHERNET interface's non-IP settings.
wireless Show the WIRELESS interface's non-IP settings.
bridge Show the BRIDGE interface's non-IP settings.
all Show the non-IP settings of all interfaces.
	Tip: You can also type the command without adding this option "all" to get the same data. That is, show network interface.

Network Service Settings

This command shows the network service settings only, including the Telnet setting, TCP ports for HTTP, HTTPS, SSH and Modbus/TCP services, and SNMP settings.

# show network services

Variables:

- is one of the options: all, http, https, telnet, ssh, snmp, modbus 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.

modbus Only displays the settings of the Modbus/TCP service.

zeroconfig Only displays the settings of the zero configuration advertising.

PDU Configuration

This command shows the PDU configuration, such as the device name, firmware version, model type and upper limit of active powered dry contact actuators.

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

# show outlets

To show detailed information, add the parameter "details" to the end of the command.

# show outlets details

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 and state are displayed.
• With the parameter "details," more outlet information is displayed in addition to the state, such as rated current, voltage, active power, active energy, and outlet settings.

Outlet Group Information

This command syntax shows the outlet group information.

# show outletgroups

To show detailed information, add the parameter "details" to the end of the command.

# show outletgroups details

Variables:

- is one of the options: all, or a number.

Option Description
all Displays the	information for all outlet groups.
	Tip: You can also type the command without adding this option "all" to get the same data.
A specific outlet group number	Displays the information for the specified outlet group only.

Displayed information:

• Without the parameter "details," only the group's name, the group's index number, member outlets and the group's power state (if it is a switched PDU) are displayed.
• With the parameter "details," more inlet information is displayed in addition to the above outlet group information, such as each member outlet's power state and the group's active energy.

Tip: PX2 allows you to assign the same name to diverse outlet groups. If this really occurs, you still can identify different groups through their unique index numbers.

Inlet Information

This command syntax shows the inlet information.

<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.
A specific inlet number	Displays the information for the specified inlet only.An inlet number needs to be specified only when there are more than 1 inlet on your PDU.

Displayed information:

• Without the parameter "details," only the inlet's name and RMS current are displayed.
• With the parameter "details," more inlet information is displayed in addition to the inlet name and RMS current, such as the inlet's RMS voltage, active power and active energy.

Overcurrent Protector Information

This command is only available for models with overcurrent protectors for protecting outlets.

This command syntax shows the overcurrent protector information, such as a circuit breaker or a fuse.

# show ocp

To show detailed information, add the parameter "details" to the end of the command.

# show ocp details

Variables:

- is one of the options: all, or a number.

Option Description
all Displays the information for all overcurrent protectors.
A specific overcurrent protector number	Displays the information for the specified overcurrent protector only.

Displayed information:

• Without the parameter "details," only the overcurrent protector status and name are displayed.
• With the parameter "details," more overcurrent protector information is displayed in addition to status, such as the rating and RMS current value.

Date and Time Settings

This command shows the current date and time settings on the PX2.

# show time

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-time-details">show time details</h1>

Default Measurement Units

This command shows the default measurement units applied to the PX2 web and CLI interfaces across all users, especially those users authenticated through remote authentication servers.

<h1 id="show-user-defaultpreferences">show user defaultPreferences</h1>

Note: If a user has set his/her own preferred measurement units or the administrator has changed any user's preferred units, the web and CLI interfaces show the preferred measurement units for that user instead of the default ones after that user logs in to the PX2. See Existing User Profiles (on page 426) for the preferred measurement units for a specific user.

Environmental Sensor Information

This command syntax shows the environmental sensor's information.

<h1 id="show-externalsensors-n">show externalsensors <n></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-externalsensors-n-details">show externalsensors <n> details</h1>

<h1 id="show-externalsensors-2-details">show externalsensors 2 details</h1>
External sensor 2 ('Temperature 2')
Sensor type: Temperature
Reading: 24.0 deg C (normal)
Serial number: QMSemu0004
Description: Not configured
Location: X Not configured
Y Not configured
Z Not configured
Position: Port 1, Chain Position 4
Using default thresholds: yes 

Variables:

- is one of the options: all, or a number.

Option Description
all Displays the information of 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 Peripherals page of the PX2 web interface.

Displayed information:

- Without the parameter "details," only the sensor ID, sensor type and reading are displayed.

Note: A state sensor displays the sensor state instead of the reading.

- With the parameter "details," more information is displayed in addition to the ID number and sensor reading, such as the serial number, sensor position, and X, Y, and Z coordinates.

Note: DPX sensor packages do not provide chain position information.

Environmental Sensor Package Information

Different from the "show externalsensors" commands, which show the reading, status and configuration of an individual environmental sensor, the following command shows the information of all connected environmental sensor packages, each of which may contain more than one sensor or actuator.

# show peripheralDevicePackages

Information similar to the following is displayed. An environmental sensor package is a peripheral device package.

Peripheral Device Package 1
Serial Number: AEI7A00022
Package Type: DPX-T1H1
Position: Port 1
Package State: operational
Firmware Version: Not available 

Peripheral Device Package 2
Serial Number: AEI7A00021
Package Type: DPX-T3H1
Position: Port 1
Package State: operational
Firmware Version: Not available 

Actuator Information

This command syntax shows an actuator's information.

<h1 id="show-actuators-n">show actuators <n></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-actuators-n-details">show actuators <n> details</h1>

Variables:

- is one of the options: all, or a number.

Option Description
all Displays the information for all actuators.
A specific actuator number*	Displays the information for the specified actuator only.

* The actuator number is the ID number assigned to the actuator. The ID number can be found using the PX2 web interface or CLI. It is an integer starting at 1.

Displayed information:

• Without the parameter "details," only the actuator ID, type and state are displayed.
• With the parameter "details," more information is displayed in addition to the ID number and actuator state, such as the serial number and X, Y, and Z coordinates.

Outlet Sensor Threshold Information

This command syntax shows the specified outlet sensor's threshold-related information.

<h1 id="show-sensor-outlet-n-sensor-type">show sensor outlet <n> <sensor type></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-sensor-outlet-n-sensor-type-details">show sensor outlet <n> <sensor type> details</h1>

Variables:

• is the number of the outlet 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
lineFrequency	Line frequency sensor

Displayed information:

• Without the parameter "details," only the sensor reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified outlet sensor are displayed.
• With the parameter "details," more sensor information is displayed, including resolution and range.
• If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

Outlet Pole Sensor Threshold Information

This command is available for an in-line monitor only, including PX2-3000 and PX3-3000 series.

This command syntax shows the specified outlet pole sensor's threshold-related information.

# show sensor outletpole

To show detailed information, add the parameter "details" to the end of the command.

# show sensor outletpole

details

Variables:

• is the number of the outlet whose pole sensors you want to query.

• is the label of the outlet 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 delay settings of the specified outlet pole sensor are displayed.
• With the parameter "details," more sensor information is displayed, including resolution and range.
• If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

Outlet Group Threshold Information

This command syntax shows the specified outlet group sensor's threshold-related information.

<h1 id="show-sensor-outletgroup-id-sensor-type">show sensor outletgroup <ID> <sensor type></h1>

To show detailed information, add the parameter "details" to the end of the command.

<h1 id="show-sensor-outletgroup-id-sensor-type-details">show sensor outletgroup <ID> <sensor type> details</h1>

Variables:

• is an outlet group's index number.
• is one of the following sensor types:

Sensor type Description

activePower An outlet group's active power sensor

activeEnergy An outlet group's active energy sensor

For definitions on an outlet group's sensors, see Outlet Groups (on page 136).

Displayed information:

• Without the parameter "details," only the sensor reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified group sensor are displayed.
• With the parameter "details," more sensor information is displayed, including resolution and range.

Inlet Sensor Threshold Information

This command is NOT available for an in-line monitor (PX2-3000 series).

This command syntax shows the specified inlet sensor's threshold-related information.

# show sensor inlet

To show detailed information, add the parameter "details" to the end of the command.

# show sensor inlet details

Variables:

• is the number of the inlet whose sensors you want to query. For a single-inlet PDU, is always 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
lineFrequency	Line frequency sensor

Displayed information:

• Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified inlet sensor are displayed.
• With the parameter "details," more sensor information is displayed, including resolution and range.
• If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

Inlet Pole Sensor Threshold Information

This command is only available for a three-phase PDU except for an in-line 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. For a single-inlet PDU, is always 1.

• 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 resolution and range.
• If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

Overcurrent Protector Sensor Threshold Information

This command is only available for models with overcurrent protectors for protecting outlets.

This command syntax shows the specified overcurrent protector sensor's threshold-related information.

# show sensor ocp

To show detailed information, add the parameter "details" to the end of the command.

# show sensor ocp details

Variables:

• is the number of the overcurrent protector 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, deassertion hysteresis and assertion timeout settings of the specified overcurrent protector sensor are displayed.
• With the parameter "details," more sensor information is displayed, including resolution and range.

Environmental Sensor Threshold Information

This command syntax shows the specified environmental sensor's threshold-related information.

# show sensor externalsensor

To show detailed information, add the parameter "details" to the end of the command.

# show sensor externalsensor details

External sensor 3 (Temperature):

Reading: 31.8 deg C

State: normal

Active Thresholds: Sensor specific thresholds

Default Thresholds for Temperature sensors:

Lower critical threshold: 10.0 deg C

Lower warning threshold: 15.0 deg C

Upper warning threshold: 30.0 deg C

Upper critical threshold: 35.0 deg C

Deassertion hysteresis: 1.0 deg C

Assertion timeout: 0 samples

Sensor Specific Thresholds:

Lower critical threshold: 8.0 deg C

Lower warning threshold: 13.0 deg C

Upper warning threshold: 28.0 deg C

Upper critical threshold: 33.0 deg C

Deassertion hysteresis: 1.0 deg C

Assertion timeout: 0 samples

Variables:

- is the environmental sensor number. The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripherals page of the PX2 web interface.

Displayed information:

- Without the parameter "details," only the reading, threshold, deassertion hysteresis and assertion timeout settings of the specified environmental sensor are displayed.

- With the parameter "details," more sensor information is displayed, including resolution and range.

Note: For a state sensor, the threshold-related and accuracy-related data is NOT available.

Environmental Sensor Default Thresholds

This command syntax shows a certain sensor type's default thresholds, which are the initial thresholds applying to the specified type of sensor.

# show defaultThresholds

To show detailed information, add the parameter "details" to the end of the command.

# show defaultThresholds details

Variables:

- is one of the following numeric sensor types:

Sensor types Description
absoluteHumidity Absolute humidity sensors
relativeHumidity	Relative humidity sensors
temperature	Temperature sensors
airPressure	Air pressure sensors
airFlow Air flow sensors
vibration	Vibration sensors
all All of the above numeric sensors
	Tip: You can also type the command without adding this option “all” to get the same data.

Displayed information:

• Without the parameter "details," only the default upper and lower thresholds, deassertion hysteresis and assertion timeout settings of the specified sensor type are displayed.
• With the parameter "details," the threshold range is displayed in addition to default thresholds settings.

Security Settings

This command shows the security settings of the PX2.

# show security

To show detailed information, add the parameter "details" to the end of the command.

# show security details

Displayed information:

• Without the parameter "details," the information including IP access control, role-based access control, password policy, and HTTPS encryption is displayed.
• With the parameter "details," more security information is displayed, such as user blocking time, user idle timeout and front panel permissions (if supported by your model).

Authentication Settings

▶ General authentication settings:

This command displays the authentication settings of the PX2, including both LDAP and Radius settings.

# show authentication

One LDAP server's settings:

To show the configuration of a specific LDAP server, assign the desired LDAP server with its sequential number in the command. To get detailed information, add "details" to the end of the command.

<h1 id="show-authentication-ldapserver-server_num">show authentication ldapServer <server_num></h1>
-- OR --
<h1 id="show-authentication-ldapserver-server_num-details">show authentication ldapServer <server_num> details</h1>

One Radius server's settings:

To show the configuration of a specific Radius server, assign the desired Radius server with its sequential number in the command. To get detailed information, add "details" to the end of the command.

<h1 id="show-authentication-radiusserver-server_num">show authentication radiusServer <server_num></h1>
-- OR--
<h1 id="show-authentication-radiusserver-server_num-details">show authentication radiusServer <server_num> details</h1>

Variables:

- is the sequential number of the specified authentication server on the LDAP or Radius server list.

Displayed information:

• Without specifying any server, PX2 shows the authentication type and a list of both LDAP and Radius servers that have been configured.
• When specifying a server, only that server's basic configuration is displayed, such as IP address and port number.
• With the parameter "details" added, detailed information of the specified server is displayed, such as an LDAP server's bind DN and the login name attribute, or a Radius server's timeout and retries values.

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, user "Enabled" status, SNMP v3 access privilege, and role(s).
• With the parameter "details," more user information is displayed, such as the telephone number, e-mail address, preferred measurement units and so on.

Existing Roles

This command shows the data of one or all existing roles.

<h1 id="show-roles-role_name">show roles <role_name></h1>

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 applies to outlet-switching capable models only.

This command shows the load shedding settings.

# show loadshedding

Displayed information:

- The load shedding state is displayed along with non-critical outlets.

Note: The load shedding mode is associated with critical and non-critical outlets. To specify critical and non-critical outlets through CLI, see Specifying Non-Critical Outlets (on page 440).

Serial Port Settings

This command shows the baud rate setting of the serial port labeled CONSOLE / MODEM on the PX2.

# show serial

EnergyWise Settings

This command shows the PX2 device's current configuration for Cisco® EnergyWise.

# show energywise

Asset Strip Settings

This command shows the asset strip settings, such as the total number of rack units (tag ports), asset strip state, numbering mode, orientation, available tags and LED color settings.

# show assetStrip

Variables:

- is one of the options: all, or a number.

Option Description
all Displays all asset strip information.
A specific asset strip number	Displays the settings of the asset strip connected to the specified FEATURE port number.For the PX2 device with only one FEATURE port, the valid number is always 1.

Rack Unit Settings of an Asset Strip

A rack unit refers to a tag port on the asset strips. This command shows the settings of a specific rack unit or all rack units on an asset strip, such as a rack unit's LED color and LED mode.

<h1 id="show-rackunit-n-rack_unit">show rackUnit <n> <rack_unit></h1>

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 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 strip.
A specific number	Displays the settings of the specified rack unit on the specified asset strip.Use the index number to specify the rack unit. The index number is available on the asset strip or 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-slot">show bladeSlot <n> <rack_unit> <slot></h1>

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 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 strip. The index number is available on the asset strip or 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.
	Tip: You can also type the command without adding this option “all” to get the same data.
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.

Event Log

The command used to show the event log begins with show event log. You can add either the limit or class parameters or both to show specific events.

Show the last 30 entries:

# show eventlog

Show a specific number of last entries in the event log:

# show eventlog limit

▶ Show a specific type of events only:

# show eventlog class

Show a specific number of last entries associated with a specific type of events only:

# show eventlog limit class

Variables:

- is one of the options: all or a number.

Option Description
all Displays all entries in the event log.
An integer number	Displays the specified number of last entries in the event log. The number ranges between 1 to 10,000.

- is one of the following event types.

Event type Description
all	All events.
device Device-related	events, such as system starting or firmware upgrade event.
userAdministration	User management events, such as a new user profile or a new role.
userActivity User activities, such as login or logout.
pdu Displays PDU-related	events, such as entry or exit of the load shedding mode.
sensor Internal or external	sensor events, such as state changes of any sensors.
serverMonitor	Server-monitoring records, such as a being declared reachable or unreachable.
assetManagement Raritan	asset management events, such as asset tag connections or disconnections.
lhx	Schroff® LHX/SHX heat exchanger events.
modem	Modem-related events.
timerEvent	Scheduled action events.
webcam	Events for webcam management, if available.
cardReader Events for card reader management, if available.
energywise	Cisco EnergyWise-related events, such as enabling the support of the EnergyWise function.

Wireless LAN Diagnostic Log

This command shows the diagnostic log for the wireless LAN connection.

# show wlanlog

Server Reachability Information

This command shows all server reachability information with a list of monitored servers and status.

# show serverReachability

Server Reachability Information for a Specific Server

To show the server reachability information for a certain IT device only, use the following command.

# show serverReachability server

To show detailed information, add the parameter "details" to the end of the command.

# show serverReachability server details

Variables:

- is a number representing the sequence of the IT device in the monitored server list.

You can find each IT device's sequence number using the CLI command of show serverReachability as illustrated below.

# IP address Enabled Status

1	192.168.84.126	Yes	Waiting for reliable connection
2	www.raritan.com	Yes	Waiting for reliable connection

Displayed information:

• Without the parameter "details," only the specified device's IP address, monitoring enabled/disabled state and current status are displayed.
• With the parameter "details," more settings for the specified device are displayed, such as number of pings and wait time prior to the next ping.

Command History

This command shows the command history for current connection session.

# show history

Displayed information:

- A list of commands that were previously entered in the current session is displayed.

Reliability Data

This command shows the reliability data.

# show reliability data

Reliability Error Log

This command shows the reliability error log.

# show reliability errorlog

Variables:

- is one of the options: O (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.

Reliability Hardware Failures

This command shows a list of detected hardware failures.

# show reliability hwfailures

For details, see Hardware Issue Detection (on page 374).

Examples

This section provides examples of the show command.

Example 1 - Basic Security Information

The diagram shows the output of the show security command.

# show security

IPv4 access control: Disabled

IPv6 access control: Disabled

Role based access control for IPv4: Disabled

Role based access control for IPv6: Disabled

Password aging: Disabled

Prevent concurrent user login: No

Strong passwords: Disabled

Enforce HTTPS for web access: Yes

Restricted Service Agreement: disabled

Example 2 - In-Depth Security Information

More information is displayed when typing the show security details command.

Chapter 8: Using the Command Line Interface

# show security details IPv4 access control: Disabled

IPv6 access control: Disabled

Role based access control for IPv4: Disabled

Role based access control for IPv6: Disabled

Password aging: Disabled

Prevent concurrent user login: No Maximum number of failed logins: 3 User block time: 10 minutes

User idle timeout: 1440 minutes

Strong passwords: Disabled

Enforce HTTPS for web access: Yes

Restricted Service Agreement: disabled Restricted Service Agreement Banner Content: Unauthorized access prohibited; all access and activities not explicitly authorized by management are unauthorized. All activities are monitored and logged. There is no privacy on this system. Unauthorized access and activities or any criminal activity will be reported to appropriate authorities.

Example 3 - Basic PDU Information

The diagram shows the output of the show pdu command.

# show pdu PDU 'my PX' Model: PX3-XXXX Firmware Version: 2.X.0.5-40956

Example 4 - In-Depth PDU Information

More information is displayed when typing the show pdu details command. Displayed information varies depending on the model you purchased.

# show pdu details PDU 'my PX'

Model: PX3-XXXX

Firmware Version: 2.8.0.5-40956

Serial Number: QGZ3792136

Board Revision: 0x01

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

Clearing Information

You can use the clear commands to remove unnecessary data from the PX2.

After typing a "clear" command, press Enter to execute it.

Note: Depending on your login name, the # prompt may be replaced by the > prompt. See Different CLI Modes and Prompts (on page 403).

Clearing Event Log

This command removes all data from the event log.

# clear eventlog

-- OR --

# clear eventlog/y

If you entered the command without "/y," a message appears, prompting you to confirm the operation. Type y to clear the event log or n to abort the operation.

If you type y, a message "Event log was cleared successfully" is displayed after all data in the event log is deleted.

Clearing WLAN Log

This command removes all data from the diagnostic log for the wireless LAN (WLAN) connection.

# clear wlanlog

-- OR --

# clear wlanlog /y

If you entered the command without "/y," a message appears, prompting you to confirm the operation. Type y to clear the WLAN log or n to abort the operation.

If you type y, a message "WLAN log was cleared successfully" is displayed to indicate all data in the WLAN log has been deleted.

Configuring the PX2 Device and Network

To configure the PX2 device or network settings through the CLI, it is highly recommended to log in as the administrator so that you have full permissions.

To configure any settings, enter the configuration mode. Configuration commands are case sensitive so ensure you capitalize them correctly.

Entering Configuration Mode

Configuration commands function in configuration mode only.

▶ To enter configuration mode:

1. Ensure you have entered administrator mode and the # prompt is displayed.

Note: If you enter configuration mode from user mode, you may have limited permissions to make configuration changes. See Different CLI Modes and Prompts (on page 403).

1. Type config and press Enter.

2. The config:# prompt appears, indicating that you have entered 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 Configuration Mode (on page 437).

Quitting 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 # or > prompt appears after pressing Enter, indicating that you have entered the administrator or user mode. See Different CLI Modes and Prompts (on page 403).

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 PX2 device.

Changing the PDU Name

This command changes the device name of PX2.

config:# pdu name ""

Variables:

- is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Setting the Outlet Power-On Sequence

This section applies to outlet-switching capable models only.

This command 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 PX2 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.

Setting the Outlet Power-On Sequence Delay

This section applies to outlet-switching capable models only.

This command sets the delays (in seconds) for outlets when turning on all outlets in sequence.

config:# pdu outletSequenceDelay :;:;:;...

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 using a dash. For example, 3-8 represents outlets 3 to 8.
• , , and the like are the delay time in seconds.

Setting the PDU-Defined Default Outlet State

This section applies to outlet-switching capable models only.

This command determines the initial power condition of all outlets after powering up the PDU.

config:# pdu outletStateOnDeviceStartup

Variables:

- is one of the options: off, on or lastKnownState.

Option Description
off Switches OFF	all outlets when the PX2 powers up.
on Switches ON	all outlets when the PX2 powers up.
lastKnownState	Restores all outlets to the previous status before powering down the PX2 when the PDU powers up again.

Setting the PDU-Defined Cycling Power-Off Period

This section applies to outlet-switching capable models only.

This command sets the power-off period of the power cycling operation for all outlets.

config:# pdu cyclingPowerOffPeriod

Variables:

- is the time of the cycling power-off period in seconds, which is an integer between 0 and 3600, or pduDefined for following the PDU-defined timing.

Setting the Inrush Guard Delay Time

This section applies to outlet-switching capable models only.

This command sets the inrush guard delay.

config:# pdu inrushGuardDelay

Variables:

- is a delay time between 100 and 100000 milliseconds.

Setting the Outlet Initialization Delay

This section applies to outlet-switching capable models only.

This command determines the outlet initialization delay timing on device startup. See PDU (on page 107) for information on outlet initialization delay.

config:# pdu outletInitializationDelayOnDeviceStartup

Variables:

- is a delay time between 1 and 3600 seconds.

Specifying Non-Critical Outlets

This section applies to outlet-switching capable models only.

This command determines critical and non-critical outlets. It is associated with the load shedding mode. See Load Shedding Mode (on page 126).

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 critical outlets. Use commas to separate outlet numbers.

Use a dash for a range of consecutive outlets. For example, 3-8 represents outlets 3 to 8.

- is one or multiple outlet numbers to be set as NON-critical outlets. Use commas to separate outlet numbers.

Use a dash for a range of consecutive outlets. For example, 3-8 represents outlets 3 to 8.

Enabling or Disabling Data Logging

This command 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 322).

Setting Data Logging Measurements Per Entry

This command 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 322).

Specifying the Device Altitude

This command specifies the altitude of your PX2 above sea level (in meters). You must specify the altitude of PX2 above sea level if a Raritan's DPX 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 713).

config:#pdu deviceAltitude

Variables:

• is an integer between -425 and 3000 meters.
• Note that the lower limit "-425" is a negative value because some locations are below the seal level.

Setting the Z Coordinate Format for Environmental Sensors

This command 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 or actuators.

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 528).

Enabling or Disabling Peripheral Device Auto Management

This command enables or disables the Peripheral Device Auto Management feature.

config:# pdu peripheralDeviceAutoManagement

Variables:

- is one of the options: enable or disable.

Option Description

enable Enables the automatic management feature for environmental sensor packages.

Option Description
disable	Disables the automatic management feature for environmental sensor packages.

For more information, see How the Automatic Management Function Works (on page 169).

Setting the Maximum Number of Active Powered Dry Contact Actuators

This command determines the upper limit of "active" powered dry contact actuators on one PX2 device. You need either 'Change Peripheral Device Configuration' privilege or 'Administrator Privileges' to change its upper limit.

config:# pdu activePoweredDryContactLimit

Variables:

- is the number representing the maximum number of active powered dry contact actuators. Its value ranges between 0 to 24.

Note: An "active" actuator is the one that is turned ON, or, if with a door handle connected, is OPENED.

Examples

This section illustrates several PDU configuration examples.

Example 1 - PDU Naming

The following command assigns the name "my px12" to the PDU.

config:# pdu name "my px12"

Example 2 - Outlet Sequence

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

Example 3 - Outlet Sequence Delay

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

Example 4 - Non-Critical Outlets

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

config:# pdu nonCriticalOutlets 1-3,7,9:false;4-6,8,10-12:true

Network Configuration Commands

A network configuration command begins with network. A number of network settings can be changed through the CLI, such as the IP address, transmission speed, duplex mode, and so on.

Configuring IPv4 Parameters

An IPv4 configuration command begins with network ipv4.

Setting the IPv4 Configuration Mode

This command determines the IP configuration mode.

config:# network ipv4 interface configMethod

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Interface Description

ethernet Determine the IPv4 configuration mode of the ETHERNET interface (that is, wired networking).

Interface Description

wireless Determine the IPv4 configuration mode of the WIRELESS interface (that is, wireless networking).

bridge Determine the IPv4 configuration mode of the BRIDGE interface (that is, bridging mode).

- is one of the modes: dhcp or static.

Mode Description
dhcp The IPv4 configuration mode is set to DHCP.
static	The IPv4 configuration address.

mode is set to

Setting the IPv4 Preferred Host Name

After selecting DHCP as the IPv4 configuration mode, you can specify the preferred host name, which is optional. The following is the command:

config:# network ipv4 interface preferredHostName

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Interface Description

ethernet Determine the IPv4 preferred host name of the ETHERNET interface (that is, wired networking).

wireless Determine the IPv4 preferred host name of the WIRELESS interface (that is, wireless networking).

bridge Determine the IPv4 preferred host name of the BRIDGE interface (that is, bridging mode).

- is a host name which:

• Consists of alphanumeric characters and/or hyphens
• Cannot begin or end with a hyphen
• Cannot contain more than 63 characters
• Cannot contain punctuation marks, spaces, and other symbols

Setting the IPv4 Address

After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX2.

config:# network ipv4 interface address

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Interface Description

ethernet Determine the IPv4 address of the ETHERNET interface (that is, wired networking).

wireless Determine the IPv4 address of the WIRELESS interface (that is, wireless networking).

bridge Determine the IPv4 address of the BRIDGE interface (that is, the bridging mode).

- is the IP address being assigned to your PX2. Its format is "IP address/prefix". For example, 192.168.84.99/24.

Setting the IPv4 Gateway

After selecting the static IP configuration mode, you can use this command to specify the gateway.

config:# network ipv4 gateway

Variables:

- is the IP address of the gateway. The value ranges from 0.0.0.0 to 255.255.255.255.

Setting IPv4 Static Routes

If the IPv4 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the PX2 and devices in the other subnet.

These commands are prefixed with network ipv4 staticRoutes.

Depending on whether the other network is directly reachable or not, there are two methods for adding a static route. For further information, see Static Route Examples (on page 214).

Method 1: add a static route when the other network is NOT directly reachable:

config:# network ipv4 staticRoutes add

Method 2: add a static route when the other network is directly reachable:

config:# network ipv4 staticRoutes add interface

▶ Delete an existing static route:

config:# network ipv4 staticRoutes delete

Modify an existing static route:

config:# network ipv4 staticRoutes modify -- OR --

config:# network ipv4 staticRoutes modify interface

Variables:

• is a combination of the IP address and subnet mask of the other subnet. The format is IP address/subnet mask.
• is the IP address of the next hop router.
• is one of the interfaces: ETHERNET, WIRELESS and BRIDGE. Type "bridge" only when your PX2 is in the bridging mode.
• is the ID number of the route setting which you want to delete or modify.
• is a modified route setting that will replace the original route setting. Its format is IP address/subnet mask. You can modify either the IP address or the subnet mask or both.

Configuring IPv6 Parameters

An IPv6 configuration command begins with network ipv6.

Setting the IPv6 Configuration Mode

This command determines the IP configuration mode.

config:# network ipv6 interface configMethod

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Interface Description

ethernet Determine the IPv6 configuration mode of the ETHERNET interface (that is, wired networking).

wireless Determine the IPv6 configuration mode of the WIRELESS interface (that is, wireless networking).

bridge Determine the IPv6 configuration mode of the BRIDGE interface (that is, bridging mode).

- is one of the modes: automatic or static.

Mode Description
automatic The IPv6 configuration mode is set to automatic.
static	The IPv6 configuration address.

mode is set to

Setting the IPv6 Preferred Host Name

After selecting DHCP as the IPv6 configuration mode, you can specify the preferred host name, which is optional. The following is the command:

config:# network ipv6 interface preferredHostName

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Interface Description

ethernet Determine the IPv6 preferred host name of the ETHERNET interface (that is, wired networking).

wireless Determine the IPv6 preferred host name of the WIRELESS interface (that is, wireless networking).

bridge Determine the IPv6 preferred host name of the BRIDGE interface (that is, bridging mode).

- is a host name which:

• Consists of alphanumeric characters and/or hyphens
• Cannot begin or end with a hyphen
• Cannot contain more than 63 characters

- Cannot contain punctuation marks, spaces, and other symbols

Setting the IPv6 Address

After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX2.

config:# network ipv6 interface address

Variables:

- is one of the network interfaces: ETHERNET, WIRELESS, or BRIDGE. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Interface Description

ethernet Determine the IPv6 address of the ETHERNET interface (that is, wired networking).

wireless Determine the IPv6 address of the WIRELESS interface (that is, wireless networking).

bridge Determine the IPv6 address of the BRIDGE interface (that is, the bridging mode).

- is the IP address being assigned to your PX2. This value uses the IPv6 address format. Note that you must add /xx, which indicates a prefix length of bits such as /64, to the end of this IPv6 address.

Setting the IPv6 Gateway

After selecting the static IP configuration mode, you can use this command to specify the gateway.

config:# network ipv6 gateway

Variables:

- is the IP address of the gateway. This value uses the IPv6 address format.

Setting IPv6 Static Routes

If the IPv6 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the PX2 and devices in the other subnet.

These commands are prefixed with network ipv6 staticRoutes.

Depending on whether the other network is directly reachable or not, there are two methods for adding a static route. For further information, see Static Route Examples (on page 214).

Method 1: add a static route when the other network is NOT directly reachable:

config:# network ipv6 staticRoutes add

Method 2: add a static route when the other network is directly reachable:

config:# network ipv6 staticRoutes add interface

▶ Delete an existing static route:

config:# network ipv6 staticRoutes delete

Modify an existing static route:

config:# network ipv6 staticRoutes modify

-- OR --

config:# network ipv6 staticRoutes modify interface

Variables:

• is the IP address and prefix length of the subnet where the PX2 belongs. The format is IP address/prefix length.
• is the IP address of the next hop router.
• is one of the interfaces: ETHERNET, WIRELESS and BRIDGE. Type "bridge" only when your PX2 is in the bridging mode.
• is the ID number of the route setting which you want to delete or modify.
• is a modified route setting that will replace the original route setting. Its format is IP address/prefix length. You can modify either the IP address or the prefix length or both.

Configuring DNS Parameters

Use the following commands to configure static DNS-related settings.

▶ Specify the primary DNS server:
config:# network dns firstServer
▶ Specify the secondary DNS server:
config:# network dns secondServer
▶ Specify the third DNS server:
config:# network dns thirdServer
▶ Specify one or multiple optional DNS search suffixes:
config:# network dns searchSuffixes
-- OR --
▶ Determine which IP address is used when the DNS server returns both IPv4 and IPv6 addresses:
config:# network dns resolverPreference

config:# network dns searchSuffixes ,,,...,

Variables:

• is the IP address of the DNS server.
• , , and the like are the DNS suffixes that automatically apply when searching for any device via PX2. For example, can be raritan.com, and can be legrand.com. You can specify up to 6 suffixes by separating them with commas.
• 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.

Setting LAN Interface Parameters

A LAN interface configuration command begins with network ethernet.

Enabling or Disabling the LAN Interface

This command enables or disables the LAN interface.

config:# network ethernet ETHERNET enabled

Variables:

- is one of the options: true or false.

Option Description

true The specified network interface is enabled.

false The specified network interface is disabled.

Changing the LAN Interface Speed

This command determines the LAN interface speed.

config:# network ethernet ETHERNET speed

Variables:

- is one of the options: auto, 10Mbps, 100Mbps and 1000Mbps.

Option Description
auto System determines the optimum LAN speed through auto-negotiation.
10Mbps The LAN speed is always 10 Mbps.
100Mbps The LAN speed is always 100 Mbps.
1000Mbps	This option is only available on specific PX2 models with the suffix "-G1".
	The LAN speed is always 1000 Mbps.

Changing the LAN Duplex Mode

This command determines the LAN interface duplex mode.

config:# network ethernet ETHERNET duplexMode

Variables:

- is one of the modes: auto, half or full.

Option Description
auto The PX2 selects the optimum transmission mode through auto-negotiation.
half	Half duplex:Data is transmitted in one direction (to or from the PX2) at a time.
full	Full duplex:Data is transmitted in both directions simultaneously.

Setting Wireless Parameters

You must configure wireless parameters, including Service Set Identifier (SSID), authentication method, Pre-Shared Key (PSK), and Basic Service Set Identifier (BSSID) after the wireless networking mode 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.

Setting the SSID

This command 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

Setting the Authentication Method

This command 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.

Setting the PSK

If the Pre-Shared Key (PSK) authentication method is selected, you must assign a PSK passphrase by using this command.

config:#network wireless PSK

Variables:

- is a string or passphrase that consists of:

- 8 to 63 characters

- No spaces

- ASCII codes 0x20 \~ 0x7E

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

▶ Determine the outer authentication protocol:

config:# network wireless eapOuterAuthentication

▶ Determine the inner authentication protocol:

config:# network wireless eapInnerAuthentication

▶ Set the EAP identity:

config:# network wireless eapIdentity

Set the EAP password:

config:# network wireless eapPassword

After performing the above command, the PX2 prompts you to enter the password. Then type the password and press Enter.

▶ Provide a CA TLS certificate:

config:# network wireless eapCACertificate

After performing the above command, the system prompts you to enter the CA certificate's contents. For details, see EAP CA Certificate Example (on page 458).

Enable or disable verification of the TLS certificate chain:

config:# network wireless enableCertVerification

▶ Allow expired and not yet valid TLS certificates:

config:# network wireless allowOffTimeRangeCerts

Allow wireless network connection with incorrect system time:

config:# network wireless allowConnectionWithIncorrectClock

Variables:

• The value of is PEAP because PX2 only supports Protected Extensible Authentication Protocol (PEAP) as the outer authentication.
• The value of is MSCHAPv2 because PX2 only supports Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) as the inner authentication.
• is your user name for the EAP authentication.
• is one of the options: true or false.

Option Description

true Enables the verification of the TLS certificate chain.

false Disables the verification of the TLS certificate chain.

- is one of the options: true or false.

Option Description
true Always make successful	the wireless network connection successful even though the TLS certificate chain contains any certificate which is outdated or not valid yet.
false The wireless	network connection is NOT successfully established when the TLS certificate chain contains any certificate which is outdated or not valid yet.

- is one of the options: true or false.

Option Description

true Make the wireless network connection successful when the PX2 system time is earlier than the firmware build before synchronizing with the NTP server, causing the TLS certificate to become invalid.

false The wireless network connection is NOT successfully established when the PX2 finds that the TLS certificate is not valid due to incorrect system time.

EAP CA Certificate 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 Configuration Mode (on page 436).
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 --- MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAkGA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxMzQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEwYDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwRgJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnEz7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgagwZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAIVTMTYWNAYDVQQKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRtaW5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0wC4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSAwDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOHH21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atObEuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZita+z4IBO --- END CERTIFICATE ---

1. Select and copy the contents as illustrated below, excluding the starting line containing "BEGIN CERTIFICATE" and the ending line containing "END CERTIFICATE."

MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAkGA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/tsOUyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYWNAYDVQ QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA wDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/ A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOH H21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atOb EuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZ ita+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 specifies the BSSID.

config:# network wireless BSSID

Variables:

- is either the MAC address of the wireless access point or none for automatic selection.

Configuring the Cascading Mode

This command determines the cascading mode.

config:# network enabled

Variables:

- is one of the following cascading modes.

Mode Description
bridge The Bridging mode, where each cascaded device is assigned a unique IP address.
portForwarding The Port Forwarding mode, where every cascaded device in the chain shares the same IP address, with diverse port numbers assigned.

Important: When enabling either cascading mode, you must make sure the other cascading mode is disabled, or the preferred cascading mode may not be enabled successfully.

- is one of the following options:

Option Description
true The selected cascading mode is enabled.
false The selected cascading mode is disabled.

If Port Forwarding mode is enabled, you must configure two more settings to finish the configuration:

On ALL cascaded devices, you must configure the 'role' setting one by one.

config:# network portForwarding role

On the master device, you must configure the 'downstream interface' setting.

config:# network portForwarding masterDownstreamInterface

Variables:

- is one of the following cascading roles:

Role Description
master The device is a master device.
slave The device is a slave device.

- is one of the following options:

Option Description
ETHERNET ETHERNET	port is the port where the 1st slave device is connected.
Usb USB port is the port	where the 1st slave device is connected.

Setting Network Service Parameters

A network service command begins with network services.

Setting the HTTP Port

The commands used to configure the HTTP port settings begin with network services http.

Change the HTTP port:

config:# network services http port

▶ Enable or disable the HTTP port:

config:# network services http enabled

Variables:

• is a TCP port number between 1 and 65535. The default HTTP port is 80.
• is one of the options: true or false.

Option Description

true The HTTP port is enabled.

false The HTTP port is disabled.

Setting the HTTPS Port

The commands used to configure the HTTPS port settings begin with network services https.

Change the HTTPS port:

config:# network services https port

▶ Enable or disable the HTTPS access:

config:# network services https enabled

Variables:

• is a TCP port number between 1 and 65535. The default HTTPS port is 443.
• is one of the options: true or false.

Option Description
true Forces any	access to the PX2 via HTTP to be redirected to HTTPS.
false No HTTP	access is redirected to HTTPS.

Changing the Telnet Configuration

You can enable or disable the Telnet service, or change its TCP port using the CLI commands.

A Telnet command begins with network services telnet

Enabling or Disabling Telnet

This command enables or disables the Telnet service.

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.

Changing the Telnet Port

This command 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.

Changing the SSH Configuration

You can enable or disable the SSH service, or change its TCP port using the CLI commands.

An SSH command begins with network services ssh.

Enabling or Disabling SSH

This command enables or disables the SSH service.

config:# network services ssh enabled

Variables:

- is one of the options: true or false.

Option Description

true The SSH service is enabled.

false The SSH service is disabled.

Changing the SSH Port

This command 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.

Determining the SSH Authentication Method

This command syntax determines the SSH authentication method.

config:# network services ssh authentication

Variables:

- is one of the options: passwordOnly, publicKeyOnly or passwordOrPublicKey.

Option Description
passwordOnly Enables the password-based login only.
publicKeyOnly Enables the public key-based login only.
passwordOrPublicKey	Enables both the password- and public key-based login. This is the default.

If the public key authentication is selected, you must enter a valid SSH public key for each user profile to log in over the SSH connection. See Specifying the SSH Public Key (on page 505).

Setting the SNMP Configuration

You can enable or disable the SNMP v1/v2c or v3 agent, configure the read and write community strings, or set the MIB-II parameters, such as sysContact, using the CLI commands.

An SNMP command begins with network services snmp.

Enabling or Disabling SNMP v1/v2c

This command enables or disables the SNMP v1/v2c protocol.

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.

Enabling or Disabling SNMP v3

This command 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.

Setting the SNMP Read Community

This command 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.

Setting the SNMP Write Community

This command 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.

Setting the sysContact Value

This command sets the SNMP MIB-II sysContact value.

config:# network services snmp sysContact

Variables:

- is a string comprising 0 to 255 alphanumeric characters.

Setting the sysName Value

This command sets the SNMP MIB-II sysName value.

config:# network services snmp sysName

Variables:

- is a string comprising 0 to 255 alphanumeric characters.

Setting the sysLocation Value

This command sets the SNMP MIB-II sysLocation value.

config:# network services snmp sysLocation

Variables:

is a string comprising 0 to 255 alphanumeric characters.

Changing the Modbus Configuration

You can enable or disable the Modbus agent, configure its read-only capability, or change its TCP port.

A Modbus command begins with network services modbus.

Enabling or Disabling Modbus

This command enables or disables the Modbus protocol.

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.

Enabling or Disabling the Read-Only Mode

This command enables or disables the read-only mode for the Modbus agent.

config:# network services modbus readonly

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.

Changing the Modbus Port

This command 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.

Enabling or Disabling Service Advertising

This command enables or disables the zero configuration protocol, which enables advertising or auto discovery of network services. See Enabling Service Advertising (on page 233) 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.

Examples

This section illustrates several network configuration examples.

Example 1 - Networking Mode

The following command enables the wired networking mode.

config:#network mode wired

Example 2 - Enabling Both IP Protocols

The following command determines that both IPv4 and IPv6 protocols are enabled.

config:# network ip proto both

Example 3 - Wireless Authentication Method

The following command sets the wireless authentication method to PSK.

config:# network wireless authMethod PSK

Example 4 - Static IPv4 Configuration

The following command enables the Static IP configuration mode.

config:# network ipv4 ipConfigurationMode static

Time Configuration Commands

A time configuration command begins with time.

Determining the Time Setup Method

This command determines the method to configure the system date and time.

config:# time method

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.

Setting NTP Parameters

A time configuration command for NTP-related parameters begins with time ntp.

▶ Specify the primary time server:

config:# time ntp firstServer

▶ Specify the secondary time server:

config:# time ntp secondServer

To delete the primary time server:

config:#time ntp firstServer ""

To delete the secondary time server:

config:# time ntp secondServer ""

Variables:

• The is the IP address or host name of the primary NTP server.
• The is the IP address or host name of the secondary NTP server.
• 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.

Customizing the Date and Time

If intending to manually configure the date and time, use the following CLI commands to specify them.

Note: You shall set the time configuration method to "manual" prior to customizing the date and time. See Determining the Time Setup Method (on page 468).

▶ Assign the date:

config:# time set date

▶ Assign the time:

config:# time set time

Variables:

Variable Description
	Type the date in the format of yyyy-mm-dd. For example, type 2015-11-30for November 30, 2015.
	Type the time in the format of hh:mm:ss in the 24-hour format. For example, type 13:50:20for 1:50:20 pm.

Setting the Time Zone

The CLI has a list of time zones to configure the date and time for the PX2.

config:#time zone

After a list of time zones is displayed, type the index number of the time zone or press Enter to cancel.

Example

To set the time zone:

1. Type the time zone command as shown below and press Enter.
   config:# time zone
2. The system shows a list of time zones. Type the index number of the desired time zone and press Enter.
3. Type apply for the selected time zone to take effect.

Setting the Automatic Daylight Savings Time

This command determines whether the daylight savings time is applied to the time settings.

config:# time autoDST

Variables:

- is one of the options: enable or disable.

Mode Description

enable Daylight savings time is enabled.

Mode Description

disable Daylight savings time is disabled.

Examples

This section illustrates several time configuration examples.

Example 1 - Time Setup Method

The following command sets the date and time settings by using the NTP servers.

config:# time method ntp

Example 2 - Primary NTP Server

The following command sets the primary time server to 192.168.80.66.

config:# time ntp firstServer 192.168.80.66

Checking the Accessibility of NTP Servers

This command verifies the accessibility of NTP servers specified manually on your PX2 and then shows the result. For instructions on specifying NTP servers via CLI, see Setting NTP Parameters (on page 468).

To perform this command successfully, you must:

• Own the "Change Date/Time Settings" permission.
• Customize NTP servers. See Setting NTP Parameters (on page 468).

This command is available either in the administrator/user mode or in the configuration mode. See Different CLI Modes and Prompts (on page 403).

In the administrator/user mode:

# check ntp

In the configuration mode:

config# check ntp

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 PX2 from a specific or a range of IP addresses.

• An IPv4 firewall configuration command begins with security ipAccessControl ipv4.
• An IPv6 firewall configuration command begins with security ipAccessControl ipv6.

Modifying Firewall Control Parameters

There are different commands for modifying firewall control parameters.

• IPv4 commands
  ▶ Enable or disable the IPv4 firewall control feature:

config:# security ipAccessControl ipv4 enabled

▶ Determine the default IPv4 firewall control policy for inbound traffic:

config:# security ipAccessControl ipv4 defaultPolicyIn

▶ Determine the default IPv4 firewall control policy for outbound traffic:

config:# security ipAccessControl ipv4 defaultPolicyOut

• IPv6 commands
  ▶ Enable or disable the IPv6 firewall control feature:

config:# security ipAccessControl ipv6 enabled

▶ Determine the default IPv6 firewall control policy for inbound traffic:

config:# security ipAccessControl ipv6 defaultPolicyIn

▶ Determine the default IPv6 firewall control policy for outbound traffic:

config:# security ipAccessControl ipv6 defaultPolicyOut

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, dropor 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.

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 558).

Managing Firewall Rules

You can add, delete or modify firewall rules using the CLI commands.

• An IPv4 firewall control rule command begins with security ipAccessControl ipv4 rule.
• An IPv6 firewall control rule command begins with security ipAccessControl ipv6 rule.

Adding a Firewall Rule

Depending on where you want to add a new firewall rule in the list, the command for adding a rule varies.

Chapter 8: Using the Command Line Interface

• IPv4 commands
  ▶ Add a new rule to the bottom of the IPv4 rules list:

config:# security ipAccessControl ipv4 rule add

Add a new IPv4 rule by inserting it above or below a specific rule:

config:# security ipAccessControl ipv4 rule add

-- OR -- 

config:# security ipAccessControl ipv4 rule add

• IPv6 commands
  Add a new rule to the bottom of the IPv6 rules list:

config:# security ipAccessControl ipv6 rule add

Add a new IPv6 rule by inserting it above or below a specific rule:

config:# security ipAccessControl ipv6 rule add

-- OR -- 

config:# security ipAccessControl ipv6 rule add

Variables:

- is one of the options: in or out.

Direction Description
in	Inbound	traffic.
out	Outbound	traffic.

• is the combination of the IP address and subnet mask values (or prefix length), 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/to the specified IP address(es).

drop Discards traffic from/to the specified IP address(es), without sending any failure notification to the source or destination host.

reject Discards traffic from/to the specified IP address(es), and an ICMP message is sent to the source or destination host for failure notification.

- is one of the options: insertAboveor 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.

Modifying a Firewall Rule

Depending on what to modify in an existing rule, the command varies.

• IPv4 commands
  Modify an IPv4 rule's IP address and/or subnet mask:

config:# security ipAccessControl ipv4 rule modify ipMask

Modify an IPv4 rule's policy:

config:# security ipAccessControl ipv4 rule modify policy

Modify all contents of an existing IPv4 rule:

config:# security ipAccessControl ipv4 rule modify ipMask policy

- IPv6 commands

Modify an IPv6 rule's IP address and/or prefix length:

config:# security ipAccessControl ipv6 rule modify ipMask

Modify an IPv6 rule's policy:

config:# security ipAccessControl ipv6 rule modify policy

Modify all contents of an IPv6 existing rule:

config:# security ipAccessControl ipv6 rule modify ipMask policy

Variables:

- is one of the options: in or out.

Direction Description
in	Inbound	traffic.
out	Outbound	traffic.

- is the number of the existing rule that you want to modify.

- is the combination of the IP address and subnet mask values (or prefix length), 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/to the specified IP address(es).
drop Discards	traffic from/to the specified IP address(es), without sending any failure notification to the source or destination host.
reject Discards	traffic from/to the specified IP address(es), and an ICMP message is sent to the source or destination host for failure notification.

Deleting a Firewall Rule

The following commands remove a specific IPv4 or IPv6 rule from the list.

IPv4 commands

config:# security ipAccessControl ipv4 rule delete

IPv6 commands

config:# security ipAccessControl ipv6 rule delete

Variables:

- is one of the options: in or out.

Direction Description
in	Inbound	traffic.
out	Outbound	traffic.

- is the number of the existing rule that you want to remove.

Restricted Service Agreement

The CLI command used to set the Restricted Service Agreement feature begins with security restrictedServiceAgreement,

Enabling or Disabling the Restricted Service Agreement

This command activates or deactivates the Restricted Service Agreement.

config:# security restrictedServiceAgreement enabled

Variables:

- is one of the options: true or false.

Option Description
true Enables the	Restricted Service Agreement feature.
false Disables the	Restricted Service Agreement feature.

After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen.

Raritan® A brand of □ legrand Unauthorized access prohibited; all access and activities not explicitly authorized by management are unauthorized. All activities are monitored and logged. There is no privacy on this system. Unauthorized access and activities or any criminal activity will be reported to appropriate authorities. I understand and accept the Restricted Service Agreement User Name Password Login

Do either of the following, or the login fails:

- In the web interface, select the checkbox labeled "I understand and accept the Restricted Service Agreement."

Tip: To select the agreement checkbox using the keyboard, first press Tab to go to the checkbox and then Enter.

- In the CLI, type y when the confirmation message "I understand and accept the Restricted Service Agreement" is displayed.

Specifying the Agreement Contents

This command allows you to create or modify contents of the Restricted Service Agreement.

config:# security restrictedServiceAgreement bannerContent

After performing the above command, do the following:

1. Type the text comprising up to 10,000 ASCII characters when the CLI prompts you to enter the content.
2. To end the content:

a. Press Enter.
b. Type --END-- to indicate the end of the content.
c. Press Enter again.

If the content is successfully entered, the CLI displays this message "Successfully entered Restricted Service Agreement" followed by the total number of entered characters in parentheses.

Note: The new content of Restricted Service Agreement is saved only after typing the apply command. See Quitting Configuration Mode (on page 437).

Example

The following example illustrates how to specify the content of the Restricted Service Agreement.

1. Type the following command and press Enter to start entering the content. config:# security restrictedServiceAgreement bannerContent
2. Type the following content when the CLI prompts you to enter the content. IMPORTANT!! You are accessing a PDU. If you are not the system administrator, do NOT power off or power cycle any outlet without the permission of the system administrator.
3. Press Enter.
4. Type the following: --END--

5. Press Enter again.

6. Verify that the message "Successfully entered Restricted Service Agreement" is displayed, indicating that the content input is successful.

Login Limitation

The login limitation feature controls login-related limitations, such as password aging, simultaneous logins using the same user name, and the idle time permitted before forcing a user to log out.

A login limitation command begins with security loginLimits.

You can combine multiple commands to modify various login limitation parameters at a time. See Multi-Command Syntax (on page 558).

Single Login Limitation

This command enables or disables the single login feature, which controls whether multiple logins using the same login name simultaneously is permitted.

config:# security loginLimits singleLogin

Variables:

- is one of the options: enable or disable.

Option Description
enable Enables	the single login feature.
disable	Disables the single login feature.

Password Aging

This command enables or disables the password aging feature, which controls whether the password should be changed at a regular interval:

config:# security loginLimits passwordAging

Variables:

- is one of the options: enable or disable.

Option Description
enable Enables	the password aging feature.
disable	Disables the password aging feature.

Password Aging Interval

This command 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.

Idle Timeout

This command determines how long a user can remain idle before that user is forced to log out of the PX2 web interface or CLI.

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

User Blocking

There are different commands for changing different user blocking parameters. These commands begin with security userBlocking. You can combine multiple commands to modify the user blocking parameters at a time. See Multi-Command Syntax (on page 558).

▶ Determine the maximum number of failed logins before blocking a user:

config:# security userBlocking maximumNumberOfFailedLogins

▶ Determine how long a user is blocked: 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 ranging from 1 to 1440 minutes (one day), or infinite, which blocks the user all the time until the user is unblocked manually.

Strong Passwords

The strong password commands determine whether a strong password is required for login, and what 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 558).

Enabling or Disabling Strong Passwords

This command 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.

Minimum Password Length

This command determines the minimum length of the password.

config:# security strongPasswords minimumLength

Variables:

- is an integer between 8 and 32.

Maximum Password Length

This command determines the maximum length of the password.

config:# security strongPasswords maximumLength

Variables:

- is an integer between 16 and 64.

Lowercase Character Requirement

This command determines whether a strong password includes at least a lowercase character.

config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter

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.

Uppercase Character Requirement

This command 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.

Numeric Character Requirement

This command 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.

Special Character Requirement

This command 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.

Maximum Password History

This command 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.

Role-Based 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 Role-Based Access Control Parameters

There are different commands for modifying role-based access control parameters.

• IPv4 commands
  Enable or disable the IPv4 role-based access control feature:

config:# security roleBasedAccessControl ipv4 enabled

▶ Determine the IPv4 role-based access control policy:

config:# security roleBasedAccessControl ipv4 defaultPolicy

• IPv6 commands
Enable or disable the IPv6 role-based access control feature:

config:# security roleBasedAccessControl ipv6 enabled

▶ Determine the IPv6 role-based access control policy:

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.

Policy Description

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 558).

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

Add a new rule to the bottom of the IPv4 rules list:

config:# security roleBasedAccessControl ipv4 rule add

Add a new IPv4 rule by inserting it above or below a specific rule:

config:# security roleBasedAccessControl ipv4 rule add

- IPv6 commands

▶ Add a new rule to the bottom of the IPv6 rules list:

config:# security roleBasedAccessControl ipv6 rule add

Add a new IPv6 rule by inserting it above or below a specific rule:

config:# security roleBasedAccessControl ipv6 rule add

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.

Modifying a Role-Based Access Control Rule

Depending on what to modify in an existing rule, the command syntax varies.

- IPv4 commands

Modify a rule's IPv4 address range:

config:# security roleBasedAccessControl ipv4 rule modify startIpAddress endIpAddress

Modify an IPv4 rule's role:

config:# security roleBasedAccessControl ipv4 rule modify role

Modify an IPv4 rule's policy:

config:# security roleBasedAccessControl ipv4 rule modify policy

Modify all contents of an existing IPv4 rule:

config:# security roleBasedAccessControl ipv4 rule modify startIpAddress endIpAddress role policy

- IPv6 commands

Modify a rule's IPv6 address range:

config:# security roleBasedAccessControl ipv6 rule modify startIpAddress endIpAddress

Modify an IPv6 rule's role:

config:# security roleBasedAccessControl ipv6 rule modify role

Modify an IPv6 rule's policy:

config:# security roleBasedAccessControl ipv6 rule modify policy

Modify all contents of an existing IPv6 rule:

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

Deleting a Role-Based Access Control Rule

These commands remove 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.

Enabling or Disabling Front Panel Outlet Switching

This section applies to outlet-switching capable models only.

The following CLI commands control whether you can turn on or off an outlet by operating the front panel display.

To enable the front panel outlet control feature:

config:# security frontPanelPermissions add switchOutlet

To disable the front panel outlet control feature:

config:# security frontPanelPermissions remove switchOutlet

Examples

This section illustrates several security configuration examples.

Example 1 - IPv4 Firewall Control Configuration

The following command sets up two parameters of the IPv4 access control feature.

config:# security ipAccessControl ipv4 enabled true defaultPolicyIn accept defaultPolicyOut accept

Results:

• The IPv4 access control feature is enabled.
• The default policy for inbound traffic is set to "accept."
• The default policy for outbound traffic is set to "accept."

Example 2 - Adding an IPv4 Firewall Rule

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 to accept all packets sent from the IPv4 address 192.168.84.123.
• 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.

Example 3 - User Blocking

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.

Example 4 - Adding an IPv4 Role-based Access Control Rule

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.

Outlet Configuration Commands

An outlet configuration command begins with outlet. Such a command allows you to configure an individual outlet.

Changing the Outlet Name

This command names an outlet.

config:# outlet name ""

Variables:

• is the number of the outlet that you want to configure.
• is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Changing an Outlet's Default State

This section applies to outlet-switching capable models only.

This command determines the initial power condition of an outlet after the PX2 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 Turn off the outlet.
on Turn on the outlet.
lastKnownState	Restore the outlet to the state prior to last PDU power down.
pduDefined	PDU-defined setting.

Note: Setting the outlet's default state to an option other than pduDefined overrides the PDU-defined default state on that outlet. See Setting the PDU-Defined Default Outlet State (on page 439).

Setting an Outlet's Cycling Power-Off Period

This section applies to outlet-switching capable models only.

This command determines the power-off period of the power cycling operation for a specific outlet.

config:# 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, or pduDefined for following the PDU-defined timing.

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 439).

Example - Outlet Naming

The following command assigns the name "Win XP" to outlet 8.

config:# outlet 8 name "Win XP"

Outlet Group Configuration Commands

An outlet group configuration command begins with outletgroup. Such a command allows you to configure or operate an outlet group.

Creating an Outlet Group

This command creates a new outlet group.

config:# outletgroup add ""

Variables:

- is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Tip: PX2 allows you to assign the same name to diverse outlet groups. If this really occurs, you still can identify different groups through their unique index numbers.

- is one or multiple member outlets' index numbers separated with commas. If the member outlets are consecutive outlets, you can type a hyphen between the initial and the final index number instead of using commas.

For example, to assign outlets 3, 4, 5, 8 and 10 to the outlet group named "servers", you have two choices -- either use a hyphen for consecutive outlets 3 to 5, or use commas for all of member outlets:

- outletgroup add servers 3-5,8,10

-- OR --

- outletgroup add servers 3,4,5,8,10

Managing an Outlet Group

You can modify an outlet group's name and member outlets, or simply remove any existing outlet group.

You can modify both the name and members of an outlet group at a time by combining multiple commands. See Multi-Command Syntax(on page 558).

Modify an outlet group's name:

config:# outletgroup modify name ""

Modify an outlet group's member outlets:

config:# outletgroup modify members

▶ Delete an outlet group:

config:# outletgroup delete

Variables:

• is an outlet group's index number.
• is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.
• is one or multiple member outlets' index numbers separated with commas. If the member outlets are consecutive outlets, you can type a hyphen between the initial and the final index number instead of using commas.
  For example, to assign outlets 3, 4, 5, 8 and 10 to the outlet group named "servers", you have two choices -- either use a hyphen for consecutive outlets 3 to 5, or use commas for all of member outlets: In the following examples, it is assumed that the "servers" outlet group's index number is 2.
• outletgroup modify 2 members 3-5,8,10
  -- OR --
• outletgroup modify 2 members 3,4,5,8,10

Powering On/Off/Cycle Outlet Groups

This section applies to outlet-switching capable models only.

Power on one outlet group:

power outletgroup on

Power off one outlet group:

power outletgroup off

▶ Power cycle one outlet group:

power outletgroup cycle

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.

For example:

# power outletgroup off /y

If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:

■ Type y to confirm the operation, OR
■ Type n to abort the operation

Variables:

- is an outlet group's index number.

Inlet Configuration Commands

An inlet configuration command begins with inlet. You can configure an inlet by using the inlet configuration command.

Changing the Inlet Name

This command syntax names an inlet.

config:# inlet name ""

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always 1. The value is an integer between 1 and 50.
• is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Enabling or Disabling an Inlet (for Multi-Inlet PDUs)

Enabling or disabling an inlet takes effect on a multi-inlet PDU only.

This command enables or disables an inlet.

config:# inlet enabled

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always 1. The value is an integer between 1 and 50.
• is one of the options: true or false.

Option Description

true The specified inlet is enabled.

false The specified inlet is disabled.

Note: If performing this command causes all inlets to be disabled, a warning message appears, prompting you to confirm. When this occurs, press y to confirm or n to cancel the operation.

Example - Inlet Naming

The following command assigns the name "AC source" to the inlet 1. If your PX2 contains multiple inlets, this command names the 1st inlet.

config:# inlet 1 name "AC source"

Overcurrent Protector Configuration Commands

An overcurrent protector configuration command begins with ocp. The command configures an individual circuit breaker or fuse which protects outlets.

Changing the Overcurrent Protector Name

This command names a circuit breaker or a fuse which protects outlets on your PX2.

config:# ocp name ""

Variables:

• is the number of the overcurrent protector that you want to configure. The value is an integer between 1 and 50.
• is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Example - OCP Naming

The command assigns the name "Email servers CB" to the overcurrent protector labeled 2.

config:# ocp 2 name "Email servers CB"

User Configuration Commands

Most user configuration commands begin with user except for the password change command.

Creating a User Profile

This command creates a new user profile.

config:# user create

After performing the user creation command, the PX2 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

- is a role or a list of comma-separated roles assigned to the specified user profile.

Modifying a User Profile

A user profile contains various parameters that you can modify.

Tip: You can combine all commands to modify the parameters of a specific user profile at a time. See Multi-Command Syntax (on page 558).

Changing a User's Password

This command allows you to change an existing user's password if you have the Administrator Privileges.

config:#user modify password

After performing the above command, PX2 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 Configuration Mode (on page 436).
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.

Various commands can be combined to modify the parameters of a specific user profile at a time. See Multi-Command Syntax (on page 558).

Change a user's full name:

config:# user modify hullName ""

Change a user's telephone number:

config:# user modify telephoneNumber ""

Change a user's email address:

config:# user modify eMailAddress

Variables:

• is the name of the user whose settings you want to change.
• is a string comprising up to 64 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.

Enabling or Disabling a User Profile

This command enables or disables a user profile. A user can log in to the PX2 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.

Forcing a Password Change

This command 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.

Modifying SNMPv3 Settings

There are different commands to modify the SNMPv3 parameters of a specific user profile. You can combine all of the following commands to modify the SNMPv3 parameters at a time. See Multi-Command Syntax (on page 558).

▶ Enable or disable the SNMP v3 access to PX2 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.

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

▶ 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 passphrase is identical to the password.
false Authentication passphrase is different from the password.

▶ 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 8 to 32 ASCII printable characters.

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

▶ 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 8 to 32 ASCII printable characters.

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

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

Changing the Role(s)

This command 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. See All Privileges (on page 510).

Changing 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 558).

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

Tip: To set the default measurement units applied to the PX2 user interfaces for all users via CLI, see Setting Default Measurement Units (on page 507).

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

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

Option Description

feet This option displays the length or height in feet.

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

Specifying the SSH Public Key

If the SSH key-based authentication is enabled, specify the SSH public key for each user profile using the following procedure.

To specify or change the SSH public key for a specific user:

1. Type the SSH public key command as shown below and press Enter. config:# user modify sshPublicKey
2. The system prompts you to enter the contents of the SSH public key. Do the following to input the contents:

a. Open your SSH public key with a text editor.
b. Copy all contents in the text editor.
c. Paste the contents into the terminal.
d. Press Enter.

To remove an existing SSH public key:

1. Type the same command as shown above.
2. When the system prompts you to input the contents, press Enter without typing or pasting anything.

Example

The following procedure illustrates how to change the SSH public key for the user "assistant."

1. Verify that you have entered the configuration mode. See Entering Configuration Mode (on page 436).
2. Type the following command and press Enter. config:#user modify assistant sshPublicKey
3. You are prompted to enter a new SSH public key.
4. Type the new key and press Enter.

Deleting a User Profile

This command deletes an existing user profile.

config:#user delete

Changing Your Own Password

Every user can change their own password via this command if they have the Change Own Password privilege. Note that this command does not begin with user.

config:# password

After performing this command, the PX2 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 Configuration Mode (on page 436).

2. Type the following command and press Enter. config:# password

3. Type the existing password and press Enter when the following prompt appears. Current password:

4. Type the new password and press Enter when the following prompt appears. Enter new password:

5. Re-type the new password for confirmation and press Enter when the following prompt appears.

Re-type new password:

Setting Default Measurement Units

Default measurement units, including temperature, length, and pressure units, apply to the PX2 user interfaces across all users except for those whose preferred measurement units are set differently by themselves or the administrator. Diverse measurement unit commands can be combined so that you can set all default measurement units at a time. To combine all commands, see Multi-Command Syntax (on page 558).

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

Tip: To change the preferred measurement units displayed in the PX2 user interfaces for a specific user via CLI, see Changing Measurement Units (on page 504).

▶ Set the default temperature unit:

config:# user defaultpreferences preferredTemperatureUnit

Variables:

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

▶ Set the default length unit:

config:# user defaultpreferences preferredLengthUnit

Variables:

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

▶ Set the default pressure unit:

config:# user defaultpreferences preferredPressureUnit

Variables:

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

Examples

This section illustrates several user configuration examples.

Example 1 - Creating a User Profile

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.

Example 2 - Modifying a User's Roles

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

Example 3 - Default Measurement Units

The following command sets all default measurement units at a time.

config:# user defaultpreferences preferredTemperatureUnit F preferredLengthUnit feet preferredPressureUnit psi

Results:

• The default temperature unit is set to Fahrenheit.
• The default length unit is set to feet.
• The default pressure unit is set to psi.

Role Configuration Commands

A role configuration command begins with role.

Creating a Role

This command creates a new role, with a list of semicolon-separated privileges assigned to the role.

config:# role create ; ; ...

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 510).
• , and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.

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
acknowledgeAlarms	Acknowledge Alarms
adminPrivilege	Administrator Privileges
changeAssetStripConfiguration Change	Asset Strip Configuration
changeAuthSettings Change Authentication Settings
changeDataTimeSettings Change Date/Time Settings
changeExternalSensorsConfiguration	Change Peripheral Device Configuration
changeLhxConfiguration Change LHX/SHX Configuration
changeModemConfiguration Change Modem Configuration
changeNetworkSettings Change Network Settings
changePassword	Change 0v
changePduConfiguration Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration
changeSecuritySettings	Change Security Settings
changeSnmpSettings Change SNMP Settings
changeUserSettings Change Local User Management
changeWebcamSettings	Change Webcam Configuration

Privilege Description
clearLog Clear Local Event Log
firmwareUpdate	Firmware Update
performReset	Reset (Warm)
switchActuator*	Switch Actuator
switchOutlet**	Switch Outlet
viewEventSetup View Event Settings
viewEverything	Unrestricted
viewLog View Local Event Log
viewSecuritySettings View Security Settings
viewSnmpSettings View SNMP Settings
viewUserSettings View Local User Management
viewWebcamSettings View Webcam Snapshots and Configuration

* The "switchActuator" privilege requires an argument that is separated with a colon. The argument could be:
- All actuators, that is, switchActuator:all
- An actuator's ID number. For example: switchActuator:1 switchActuator:2 switchActuator:3
- A list of comma-separated ID numbers of different actuators. For example: switchActuator:1,3,6

Note: The ID number of each actuator is shown in the PX2 web interface. It is an integer between 1 and 32.

** 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

Modifying a Role

You can modify diverse parameters of an existing role, including its privileges.

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.

▶ 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 addPrivileges :,...; :,...; :,...; ...

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 510).
• , and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.

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 510).
• , and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.

Deleting a Role

This command deletes an existing role.

config:# role delete <name> 

Example - Creating a Role

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

Authentication Commands

An authentication configuration command begins with authentication.

Determining the Authentication Method

You can choose to set the authentication type only, or both set the authentication type and determine whether to switch to local authentication in case the remote authentication is not available.

▶ Determine the authentication type only:
config:# authentication type
▶ Determine the authentication type and enable/disable the option of switching to local authentication:

config:# authentication type useLocalIfRemoteUnavailable

Note: You cannot enable or disable the option of switching to local authentication without determining the authentication type in the CLI. Therefore, always type "authentication type " when setting up "useLocalIfRemoteUnavailable".

Variables:

- is one of the options: local, ldap or radius.

Option Description
local	Enable	Local	authentication only.
ldap	Enable	LDAP	authentication.
radius Enable Radius authentication.

- is one of the options: true or false.

Option Description

true Remote authentication is the first priority. The device will switch to local authentication when the remote authentication is not available.

false Always stick to remote authentication regardless of the availability of remote authentication.

LDAP Settings

All LDAP-related commands begin with authentication ldap.

If you enable LDAP authentication, you must add at least one LDAP server. Later you can modify or delete any existing LDAP server as needed.

Adding an LDAP Server

Adding an LDAP server requires the entry of quite a lot of parameters, such as the server's IP address, TCP port number, Base DN and so on.

You can repeat the following CLI command to add more than one LDAP server.

Tip: If any LDAP server's settings are identical to an existing LDAP server's, you can add it by just copying the existing one, instead of using the following command. See Copying an Existing Server's Settings (on page 519).

▶ Add a new LDAP server:

config:# authentication ldap add "Optional Parameters"

Note: "Optional Parameters" refer to one or multiple parameters listed in the section Optional Parameters (on page 517). They are required only when your server settings need to specify these parameters. For example, if setting the to "authenticatedBind", then you must add the parameter "bindDN" to this command.

When the above command is successfully performed, a list of all LDAP servers, including the newly-added one, will be displayed, which is similar to the following diagram.

#	IP address	Server type
1	192.1.1.1	OpenLDAP
2	192.2.2.2	OpenLDAP

Tip: To verify all settings of a newly-added server, see Authentication Settings (on page 425).

Variables:

• is the IP address or host name of the LDAP server.
• is the port number assigned for communication with the LDAP server.
• is one of the LDAP server types: openldap or activeDirectory.

Type Description
openldap	OpenLDAP server
activeDirectory	Microsoft Active Directory

- is one of the security options: none, startTls or tls.

Type Description
none	No security
startTls	StartTLS
tls	TLS

- is one of the bind options: anonymouseBind, or authenticatedBind.

Type Description
anonymousBind		Enable the anonymous Bind. Bind DN and password are NOT required.
authenticatedBind		Enable the Bind with authentication. Bind DN and password are required.

• is the base DN for search.
• is the login name attribute.
• is the User Entry Object Class.

Optional Parameters

You can add one or multiple "optional parameters", such as specifying the Bind DN or certificate upload, to an LDAP-server-adding command as illustrated below. If adding multiple optional parameters, you must add them to the END of the command and separate them with a space.

Example 1 -- Specify an Active Directory Domain's name:

config:# authentication ldap add <host> <port> <ldap_type> <security>
<bind_type> <base_DN> <login_name_att> <user_entry_class>
adDomain <AD_domain> 

■ Example 2 -- Set up the bind DN:

config:# authentication ldap add <host> <port> <ldap_type> <security>
<bind_type> <base_DN> <login_name_att> <user_entry_class> bindDN
<bind_DN> 

"Optional Parameters" table:

Parameters To configure
userSearchSubfilter	User search subfilter
bindDN	bind DNThe system will prompt you to enter and re-confirm the bind password after adding this parameter to the command.For details, see Illustrations of Adding LDAP Servers (on page 518).
adDomain	Active Directory Domain name
verifyServerCertificate	Certificate verification settingAfter setting to true, the system will prompt you to upload a certificate. For details, see Illustrations of Adding LDAP Servers (on page 518).
allowExpiredCertificate	Whether to accept expired or not valid yet certificate

Variables:

• is the user search subfilter you specify.
• is bind DN.
• is the Active Directory Domain.
• is one of the options: true or false.

Option Description
true	Enable the verification of the LDAP server certificate.
false	Disable the verification of the LDAP server certificate.

- is one of the options: true or false.

Option Description
true	Certificates that are either expired or not valid yet are all accepted.
false	Only valid certificates are accepted.

Illustrations of Adding LDAP Servers

This section shows several LDAP command examples. Those words highlighted in bold are required for their respective examples.

An OpenLDAP server:

config:# authentication ldap add op-ldap.raritan.com 389 openldap none anonymousBind dc=raritan,dc=com uid inetOrgPerson

A Microsoft Active Directory server:

config:# authentication ldap add ac-ldap.raritan.com 389 activeDirectory none anonymousBind dc=raritan,dc=com sAMAccountName user adDomain raritan.com

An LDAP server with a TLS certificate uploaded:

a. Enter the CLI command with the following two TLS-related options set and/or added:

• is set to tls or startTls.
• The "verifyServerCertificate" parameter is added to the command and set to "true."

config:# authentication ldap add ldap.raritan.com 389 openldap startTls ... inetOrgPerson verifyServerCertificate true

b. The system now prompts you to enter the certificate's content.
c. Type or copy the certificate's content in the CLI and press Enter.

Note: The certificate's content is located between the line containing "BEGIN CERTIFICATE" and the line containing "END CERTIFICATE".

An LDAP server with the bind DN and bind password configured:

a. Enter the CLI command with the "bindDN" parameter and its data added.

config:# authentication ldap add op-ldap.raritan.com 389 openldap none authenticatedBind cn=Manager, dc=raritan, dc=com uid inetOrgPerson bindDN [e-mail]

b. The system prompts you to specify the bind DN password.
c. Type the password and press Enter.
d. Re-type the same password.

Copying an Existing Server's Settings

If the server that you will add completely shares the same settings with any server that has been configured, use the following command.

Add an LDAP server by copying an existing server's settings:

config:# authentication ldap addClone

Variables:

• is the IP address or host name of the LDAP server.
• is the sequential number of the specified server shown on the server list of the PX2. See Authentication Settings (on page 425).

Modifying an Existing LDAP Server

You can modify one or multiple parameters of an existing LDAP server, such as its IP address, TCP port number, Base DN and so on. Besides, you can also change the priority or sequence of existing LDAP servers in the server list.

Command syntax:

A command to modify an existing LDAP server's settings looks like the following:

config:# authentication ldap modify "parameters"

Variables:

• is the sequential number of the specified server in the LDAP server list.
• Replace "parameters" with one or multiple commands in the following table, depending on which parameter(s) you want to modify.

A list of "parameters":

Parameters Description
host	Change the IP address or host name.▪is the new IP address or host name.
port	Change the TCP port number.▪is the new TCP port number.
serverType	Change the server type.▪is the new type of the LDAP server.▪values include: openldap and activeDirectory.
securityType	Change the security type.▪is the new security type.▪values include: none, startTls, and ssl
bindType	Change the bind type.▪is the new bind type.▪values include: anonymousBind and authenticatedBind.
searchBaseDN	Change the base DN for search.▪is the new base DN for search.
loginNameAttribute	Change the login name attribute.▪is the new login name attribute.
userEntryObjectClass	Change the user entry object class.▪is the new user entry class.
userSearchSubfilter	Change the user search subfilter.▪is the new user search subfilter.
adDomain	Change the Active Directory Domain name.▪is the new domain name of the Active Directory.
verifyServerCertificate	Enable or disable the certificate verification.▪enables or disables the certificate verification feature.▪Available values include: true,false
certificate	Re-upload a different certificate.a. First add the "certificate" parameter to the command, and press Enter.b. The system prompts you for the input of the certificate.c. Type or copy the content of the certificate in the CLI and press Enter.
allowExpiredCertificate	Determine whether to accept a certificate which is expired or not valid yet.determines whether to accept an expired or not valid yet certificatevalues include: true, and false
bindDN	Change the bind DN.is the new bind DN.
bindPassword	Change the bind DN password.a. First add the "bindPassword" parameter to the command, and press Enter.b. The system prompts you for the input of the password.c. Type the password and press Enter.
sortPosition	Change the priority of the server (that is, resorting).is the new sequential number of the server in the LDAP server list.

Note: For details of the above variables' values, see Adding an LDAP Server (on page 515).

Examples:

- Change the IP address of the 1st LDAP server

config:# authentication ldap modify 1 host 192.168.3.3

- Change both the IP address and TCP port of the 1st LDAP server

config:# authentication ldap modify 1 host 192.168.3.3 port 633

- Change the IP address, TCP port and the type of the L1st DAP server

config:# authentication ldap modify 1 host 192.168.3.3 port 633

serverType activeDirectory

Removing an Existing LDAP Server

This command removes an existing LDAP server from the server list.

config:# authentication ldap delete

Variables:

- is the sequential number of the specified server in the LDAP server list.

Radius Settings

All Radius-related commands begin with authentication radius.

If you enable Radius authentication, you must add at least one Radius server. Later you can modify or delete any existing Radius server as needed.

Adding a Radius Server

You can repeat the following commands to add Radius servers one by one.

Command syntax:

config:# authentication radius add

Variables:

• is the IP address or host name of the Radius server.
• is one of the Radius authentication types: pap, chap, msChapV2.

Type Description
chap	CHAP
pap	PAP
msChapV2	MSCHAP v2

• is the authentication port number.
• is the accounting port number.
• is the timeout value in seconds. It ranges between 1 to 10 seconds.
• is the number of retries. It ranges between 0 to 5.

To enter the shared secret:

1. After executing the above Radius command, the system automatically prompts you to enter the shared secret.
2. Type the secret and press Enter.
3. Re-type the same secret and press Enter.

Example:

config:# authentication radius add 192.168.7.99 chap 1812 1813 10 3

Modifying an Existing Radius Server

You can modify one or multiple parameters of an existing Radius server, or change the priority or sequence of existing servers in the server list.

Change the IP address or host name:

config:# authentication radius modify host

Change the Radius authentication type:

config:# authentication radius modify authType

▶ Change the authentication port:

config:# authentication radius modify authPort

Change the accounting port:

config:# authentication radius modify accountPort

Change the timeout value:

config:# authentication radius modify timeout

▶ Change the number of retries:

config:# authentication radius modify retries

▶ Change the shared secret:

config:# authentication radius modify secret

Change the priority of the specified server:

config:# authentication radius modify sortPositon

Tip: You can add more than one parameters to the command. For example, "authentication radius modify host authType authPort accountPort ...".

Variables:

• is the sequential number of the specified server in the Radius server list.
• is the new IP address or host name of the Radius server.
• is one of the Radius authentication types: pap, chap, msChapV2.
• is the new authentication port number.
• is the new accounting port number.
• is the new timeout value in seconds. It ranges between 1 to 10 seconds.
• is the new number of retries. It ranges between 0 to 5.

To enter the shared secret:

1. After executing the above Radius command, the system automatically prompts you to enter the shared secret.
2. Type the secret and press Enter.
3. Re-type the same secret and press Enter.

Example:

config:# authentication radius add 192.168.7.99 chap 1812 1813 10 3

Removing an Existing Radius Server

This command removes an existing Radius server from the server list.

config:# authentication radius delete

Variables:

- is the sequential number of the specified server in the Radius server list.

Environmental Sensor Configuration Commands

An environmental sensor configuration command begins with externalsensor. You can configure the name and location parameters of an individual environmental sensor.

Note: To configure an actuator, see Actuator Configuration Commands (on page 543).

Changing the Sensor Name

This command 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 available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Note: To name an actuator, see Actuator Configuration Commands (on page 543).

Specifying the CC Sensor Type

Raritan's contact closure sensor (DPX-CC2-TR) supports the connection of diverse third-party or Raritan's detectors/switches. You must specify the type of connected detector/switch for proper operation. Use this command 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 available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• 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 the vibration.

Setting the X Coordinate

This command 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 available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.

Setting the Y Coordinate

This command 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 available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.

Setting the Z Coordinate

This command 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 available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• 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, seeSetting the Z Coordinate Format for Environmental Sensors (on page 442).

Changing the Sensor Description

This command 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 available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• is a string comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.

Using Default Thresholds

This command determines whether default thresholds, including the deassertion hysteresis and assertion timeout, are applied to a specific environmental sensor.

config:# externalsensor useDefaultThresholds

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• is one of the options: true or false.

Option Description

true Default thresholds are selected as the threshold option for the specified sensor.

false Sensor-specific thresholds are selected as the threshold option for the specified sensor.

Setting the Alarmed to Normal Delay for DX-PIR

This command determines the value of the Alarmed to Normal Delay setting for a DX-PIR presence detector.

config:# externalsensor alarmedToNormalDelay

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• is an integer number in seconds, ranging between 0 and 300.

Examples

This section illustrates several environmental sensor configuration examples.

Example 1 - Environmental Sensor Naming

The following command assigns the name "Cabinet humidity" to the environmental sensor with the ID number 4.

config:#externalsensor4name"Cabinethumidity"

Example 2 - Sensor Threshold Selection

The following command sets the environmental sensor #1 to use the default thresholds, including the deassertion hysteresis and assertion timeout, as its threshold settings.

config:#externalsensor1useDefaultThresholds true

Configuring Environmental Sensors' Default Thresholds

You can set the default values of upper and lower thresholds, deassertion hysteresis and assertion timeout on a sensor type basis, including temperature, humidity, air pressure and air flow sensors. The default thresholds automatically apply to all environmental sensors that are newly detected or added.

A default threshold configuration command begins with defaultThresholds.

You can configure various default threshold settings for the same sensor type at a time by combining multiple commands. See Multi-Command Syntax (on page 558).

▶ Set the Default Upper Critical Threshold for a specific sensor type:

config:# defaultThresholds upperCritical

▶ Set the Default Upper Warning Threshold for a specific sensor type:

config:# defaultThresholds upperWarning

▶ Set the Default Lower Critical Threshold for a specific sensor type:

Chapter 8: Using the Command Line Interface

config:# defaultThresholds lowerCritical

▶ Set the Default Lower Warning Threshold for a specific sensor type:

config:# defaultThresholds lowerWarning

Set the Default Deassertion Hysteresis for a specific sensor type:

config:# defaultThresholds hysteresis

Set the Default Assertion Timeout for a specific sensor type:

config:# defaultThresholds assertionTimeout

Variables:

- is one of the following numeric sensor types:

Sensor types Description
absoluteHumidity Absolute humidity sensors
relativeHumidity	Relative humidity sensors
temperature	Temperature sensors
airPressure	Air pressure sensors
airFlow Air flow sensors
vibration	Vibration sensors

- is the value for the specified threshold of the specified sensor type. Note that diverse sensor types use different measurement units.

Sensor types Measurement units
absoluteHumidity g/m^3 (that is, g/m 3)
relativeHumidity	%
temperature	Degrees Celsius (°C) or Fahrenheit (°F, depending on your measurement unit settings.
airPressure Pascal (Pa) or psi, depending on your measurement unit settings.
airFlow	m/s
vibration	g

• is the deassertion hysteresis value applied to the specified sensor type.
• is the assertion timeout value applied to the specified sensor type. It ranges from 0 to 100 (samples).

Example - Default Upper Thresholds for Temperature

It is assumed that your preferred measurement unit for temperature is set to degrees Celsius. Then the following command sets the default Upper Warning threshold to 20^ C and Upper Critical threshold to 24^ C for all temperature sensors.

config:#defaultThresholds temperature upperWarning 20

upperCritical 24

Sensor Threshold Configuration Commands

A sensor configuration command begins with sensor. You can use the commands to configure the threshold, hysteresis and assertion timeout values for any sensor associated with the following items:

• Outlets
• Outlet groups
  Inlets
  ■ Inlet poles (for three-phase PDUs only)
  ■ Overcurrent protectors
  ■ Environmental sensors

It is permitted to assign a new value to the threshold at any time regardless of whether the threshold has been enabled.

Commands for Outlet Sensors

A sensor configuration command for outlets begins with sensor outlet.

Chapter 8: Using the Command Line Interface

You can configure various outlet sensor threshold settings at a time by combining multiple commands. See Multi-Command Syntax (on page 558).

▶ Set the Upper Critical threshold for an outlet sensor:

config:# sensor outlet upperCritical

Set the Upper Warning threshold for an outlet sensor:

config:# sensor outlet upperWarning

Set the Lower Critical threshold for an outlet sensor:

config:# sensor outlet lowerCritical

Set the Lower Warning threshold for an outlet sensor:

config:# sensor outlet lowerWarning

Set the deassertion hysteresis for an outlet sensor:

config:# sensor outlet hysteresis

Set the assertion timeout for an outlet sensor:

config:# sensor outlet assertionTimeout

Variables:

☐ is the number of the outlet that you want to configure.
☐ is one of the following sensor types:

Sensor type Description
current	Current	sensor
voltage	Voltage	sensor
activePower	Active	power	sensor
apparentPower Apparent	power sensor
powerFactor	Power	factor	sensor
activeEnergy Active energy sensor
lineFrequency	Line	frequency sensor

Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables the specified threshold for a specific outlet sensor.
disable	Disables the specified threshold outlet sensor.
A numeric value	Sets a value for the specified threshold of a specific outlet sensor and enables this threshold at the same time.

• is a numeric value that is assigned to the hysteresis for the specified outlet sensor. See "To De-assert" and Deassertion Hysteresis (on page 709).
• is a number in samples that is assigned to the assertion timeout for the specified outlet sensor. See "To Assert" and Assertion Timeout (on page 707).

Commands for Outlet Group Sensors

A sensor configuration command for outlets begins with sensor outletgroup.

You can configure various outlet group sensor threshold settings at a time by combining multiple commands. See Multi-Command Syntax (on page 558).

Set the Upper Critical threshold for an outlet group sensor:

config:# sensor outletgroup upperCritical

Set the Upper Warning threshold for an outlet group sensor:

config:# sensor outletgroup upperWarning

Set the Lower Critical threshold for an outlet group sensor:

config:# sensor outletgroup lowerCritical

Set the Lower Warning threshold for an outlet group sensor:

config:# sensor outletgroup lowerWarning

Set the deassertion hysteresis for an outlet group sensor:

config:# sensor outletgroup hysteresis

Set the assertion timeout for an outlet group sensor:

config:# sensor outletgroup assertionTimeout

Variables:

• is an outlet group's index number.
• is one of the following sensor types:

Sensor type Description

activePower

An outlet group's active power sensor

activeEnergy

An outlet group's active energy sensor

For definitions on an outlet group's sensors, see Outlet Groups (on page 136).

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the specified threshold for a specific group sensor of the chosen outlet group.
disable	Disables the specified threshold group sensor of the chosen outlet group.
A numeric value	Sets a value for the specified threshold of the chosen outlet group's specific group sensor, and enables this threshold at the same time.

• is a numeric value that is assigned to the hysteresis for the specified group sensor of the chosen outlet group. See "To De-assert" and Deassertion Hysteresis (on page 709).
• is a number in samples that is assigned to the assertion timeout for the specified group sensor of the chosen outlet group. See "To Assert" and Assertion Timeout (on page 707).

Commands for Inlet Sensors

A sensor configuration command for inlets begins with sensor inlet.

You can configure various inlet sensor threshold settings at a time by combining multiple commands. See Multi-Command Syntax (on page 558).

Set the Upper Critical threshold for an inlet sensor:

config:# sensor inlet upperCritical

Set the Upper Warning threshold for an inlet sensor:

config:# sensor inlet upperWarning

Set the Lower Critical threshold for an inlet sensor:

config:# sensor inlet lowerCritical

Set the Lower Warning threshold for an inlet sensor:

config:# sensor inlet lowerWarning

▶ Set the deassertion hysteresis for an inlet sensor:

config:# sensor inlet hysteresis

▶ Set the assertion timeout for an inlet sensor:

config:# sensor inlet assertionTimeout

Variables:

• is the number of the inlet that you want to configure. For a single-inlet PDU, is always 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
lineFrequency	Line frequency sensor
phaseAngle Inlet phase angle sensor

Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the specified threshold for a specific inlet sensor.
disable	Disables the specified threshold inlet sensor.
A numeric value	Sets a value for the specified threshold of a specific inlet sensor and enables this threshold at the same time.

• is a numeric value that is assigned to the hysteresis for the specified inlet sensor. See "To De-assert" and Deassertion Hysteresis (on page 709).
• is a numeric value that is assigned to the assertion timeout for the specified inlet sensor. See "To Assert" and Assertion Timeout (on page 707).

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.

You can configure various inlet pole sensor threshold settings at a time by combining multiple commands. See Multi-Command Syntax(on page 558).

▶ Set the Upper Critical Threshold for an Inlet Pole:

config:# sensor inletpole

upperCritical

Set the Upper Warning Threshold for an Inlet Pole:

config:# sensor inletpole

upperWarning

▶ Set the Lower Critical Threshold for an Inlet Pole:

config:# sensor inletpole

lowerCritical

▶ Set the Lower Warning Threshold for an Inlet Pole:

config:# sensor inletpole

lowerWarning

Set the Inlet Pole's Deassertion Hysteresis:

config:# sensor inletpole

hysteresis

▶ Set the Inlet Pole's Assertion Timeout:

config:# sensor inletpole

assertionTimeout

Variables:

• is the number of the inlet whose pole sensors you want to configure. For a single-inlet PDU, is always 1.

• 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

Sensor type Description
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 "Sensor is not available" message is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the specified threshold for the specified inlet pole sensor.
disable	Disables the specified threshold inlet pole sensor.
A numeric value	Sets a value for the specified threshold of the specified inlet pole sensor and enables this threshold at the same time.

• is a numeric value that is assigned to the hysteresis for the specified inlet pole sensor. See "To De-assert" and Deassertion Hysteresis (on page 709).
• is a number in samples that is assigned to the assertion timeout for the specified inlet pole sensor. See "To Assert" and Assertion Timeout (on page 707).

Commands for Overcurrent Protector Sensors

A sensor configuration command for overcurrent protectors begins with sensor ocp.

You can configure various overcurrent protector threshold settings at a time by combining multiple commands. See Multi-Command Syntax (on page 558).

Set the Upper Critical threshold for an overcurrent protector:

config:# sensor ocp upperCritical

Set the Upper Warning threshold for an overcurrent protector:

Chapter 8: Using the Command Line Interface

config:# sensor ocp upperWarning

Set the Lower Critical threshold for an overcurrent protector:

config:# sensor ocp lowerCritical

Set the Lower Warning threshold for an overcurrent protector:

config:# sensor ocp lowerWarning

Set the deassertion hysteresis for an overcurrent protector:

config:# sensor ocp hysteresis

Set the assertion timeout for an overcurrent protector:

config:# sensor ocp assertionTimeout

Variables:

• is the number of the overcurrent protector 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 "Sensor is not available" message is displayed.

- is one of the options: enable, disable or a numeric value.

Option Description
enable Enables	the specified threshold for the overcurrent protector sensor.
disable Disables	the specified threshold for the overcurrent protector sensor.

Option Description

A numeric value

Sets a value for the specified threshold of the overcurrent protector sensor and enables this threshold at the same time.

• is a numeric value that is assigned to the hysteresis for the specified overcurrent protector sensor. See "To De-assert" and Deassertion Hysteresis (on page 709).
• is a number in samples that is assigned to the assertion timeout for the specified overcurrent protector sensor. See "To Assert" and Assertion Timeout (on page 707).

Commands for Environmental Sensors

A sensor threshold configuration command for environmental sensors begins with sensor externalsensor.

You can configure various environmental sensor threshold settings at a time by combining multiple commands. See Multi-Command Syntax (on page 558).

Set the Upper Critical threshold for an environmental sensor:

config:# sensor externalsensor upperCritical

Set the Upper Warning threshold for an environmental sensor:

config:# sensor externalsensor upperWarning

Set the Lower Critical threshold for an environmental sensor:

config:# sensor externalsensor lowerCritical

Set the Lower Warning threshold for an environmental sensor:

config:# sensor externalsensor lowerWarning

Set the deassertion hysteresis for an environmental sensor:

config:# sensor externalsensor hysteresis

Set the assertion timeout for an environmental sensor:

config:# sensor externalsensor assertionTimeout

Variables:

• is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX2 web interface or using the command "show externalsensors " in the CLI. It is an integer between 1 and 32.
• is one of these sensor types: temperature, absoluteHumidity, relativeHumidity, airPressure, airflow vibration.

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 specified threshold for a specific environmental sensor.
disable	Disables the specified threshold environmental sensor.
A numeric value	Sets a value for the specified threshold of a specific environmental sensor and enables this threshold at the same time.

• is a numeric value that is assigned to the hysteresis for the specified environmental sensor. See "To De-assert" and Deassertion Hysteresis (on page 709).
• is a number in samples that is assigned to the assertion timeout for the specified environmental sensor. It ranges between 1 and 100. See "To Assert" and Assertion Timeout (on page 707).

Examples

This section illustrates several environmental sensor threshold configuration examples.

Example 1 - Upper Critical Threshold for a Temperature Sensor

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

Example 2 - Warning Thresholds for Inlet Sensors

The following command sets both the Upper Warning and Lower Warning thresholds for the inlet 1 RMS current.

config:# sensor inlet 1 current upperWarning 20 lowerWarning 12

Results:

• The Upper Warning threshold for the inlet 1 RMS current is set to 20A. It also enables the upper warning threshold if this threshold has not been enabled yet.
• The Lower Warning threshold for the inlet 1 RMS current is set to 12A. It also enables the lower warning threshold if this threshold has not been enabled yet.

Example 3 - Upper Thresholds for Overcurrent Protector Sensors

The following command sets both the Upper Critical and Upper Warning thresholds for the 2nd overcurrent protector.

config:# sensor ocp 2 current upperWarning enable upperCritical 16

Results:

• The Upper Critical threshold for the 2nd overcurrent protector's RMS current is set to 16A. It also enables the upper critical threshold if this threshold has not been enabled yet.
• The Upper Warning threshold for the 2nd overcurrent protector's RMS current is enabled.

Actuator Configuration Commands

An actuator configuration command begins with actuator. You can configure the name and location parameters of an individual actuator.

You can configure various parameters for one actuator at a time. See Multi-Command Syntax (on page 558).

Change the name:
Set the X coordinate:
Set the Y coordinate:
Set the Z coordinate:
Modify the actuator's description:

config:# actuator <n> name "<name>" 

config:# actuator <n> xlabel "<coordinate>" 

config:# actuator <n> ylabel "<coordinate>" 

config:# actuator <n> zlabel "<z_label>" 

config:# actuator <n> description "<description>" 

Variables:

• is the ID number assigned to the actuator. The ID number can be found using the PX2 web interface or CLI. It is an integer starting at 1.
• is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.
• is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
• There are two types of values for the variable, depending on the Z coordinate format you set:

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 442).

- is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.

Example - Actuator Naming

The following command assigns the name "Door lock" to the actuator whose ID number is 9.

config:# actuator 9 name "Door lock"

Server Reachability Configuration Commands

You can use the CLI to add or delete an IT device, such as a server, from the server reachability list, or modify the settings for a monitored IT device. A server reachability configuration command begins with serverReachability.

Adding a Monitored Device

This command adds a new IT device to the server reachability list.

config:# serverReachability add <IP_host> <enable> <succ_ping> <fail_ping> <succ_wait> <fail_wait> <resume> <disable_count> 

Variables:

• is the IP address or host name of the IT device that you want to add.
• is one of the options: true or false.

Option Description
true Enables the	ping monitoring feature for the newly added device.
false Disables the	ping monitoring feature for the newly added device.

• is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200.
• is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to 100.
• is the wait time to send the next ping after a successful ping. Valid range is 5 to 600 (seconds).
• is the wait time to send the next ping after a unsuccessful ping. Valid range is 3 to 600 (seconds).
• is the wait time before the PX2 resumes pinging after declaring the monitored device "Unreachable." Valid range is 5 to 120 (seconds).
• is the number of consecutive "Unreachable" declarations before the PX2 disables the ping monitoring feature for the monitored device and returns to the "Waiting for reliable connection" state. Valid range is 1 to 100 or unlimited.

Deleting a Monitored Device

This command removes a monitored IT device from the server reachability list.

config:# serverReachability delete

Variables:

• is a number representing the sequence of the IT device in the monitored server list.
  You can find each IT device's sequence number using the CLI command of show serverReachability as illustrated below.

# IP address Enabled Status

1 192.168.84.126 Yes Waiting for reliable connection 2 www.raritan.com Yes Waiting for reliable connection

Modifying a Monitored Device's Settings

The command to modify a monitored IT device's settings begins with serverReachability modify.

You can modify various settings for a monitored device at a time. See Multi-Command Syntax (on page 558).

Modify a device's IP address or host name:

Chapter 8: Using the Command Line Interface

config:# serverReachability modify <n> ipAddress <IP_host>

▶ Enable or disable the ping monitoring feature for the device:
config:# serverReachability modify <n> pingMonitoringEnabled <option>

▶ Modify the number of successful pings for declaring "Reachable":
config:# serverReachability modify <n> numberOfSucc ssfulPingsToEnable <succ_number>

▶ Modify the number of unsuccessful pings for declaring "Unreachable":
config:# serverReachability modify <n> numberOfUnsuccessfulPingsForFailure <fail_number>

▶ Modify the wait time after a successful ping:
config:# serverReachability modify <n> waitTimeAfterSuccessfulPing <succ_wait>

▶ Modify the wait time after a unsuccessful ping:
config:# serverReachability modify <n> waitTimeAfterUnsuccessfulPing <fail_wait>

▶ Modify the wait time before resuming pinging after declaring "Unreachable":
config:# serverReachability modify <n> waitTimeBeforeResumingPinging <resume>

▶ Modify the number of consecutive "Unreachable" declarations before disabling the ping monitoring feature:
config:# serverReachability modify <n> numberOfFailuresToDisable <disable_count> 

Variables:

• is a number representing the sequence of the IT device in the server monitoring list.
• is the IP address or host name of the IT device whose settings you want to modify.
• is one of the options: true or false.

Option Description
true Enables the	ping monitoring feature for the monitored device.
false Disables the	ping monitoring feature for the monitored device.

• is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200.
• is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to 100.
• is the wait time to send the next ping after a successful ping. Valid range is 5 to 600 (seconds).
• is the wait time to send the next ping after a unsuccessful ping. Valid range is 3 to 600 (seconds).
• is the wait time before the PX2 resumes pinging after declaring the monitored device "Unreachable." Valid range is 5 to 120 (seconds).
• is the number of consecutive "Unreachable" declarations before the PX2 disables the ping monitoring feature for the monitored device and returns to the "Waiting for reliable connection" state. Valid range is 1 to 100 or unlimited.

Example - Server Settings Changed

The following command modifies several ping monitoring settings for the second server in the server reachability list.

config:# serverReachability modify 2 nu mberOfSuccessfulPingsToEnable 10 numberOfUnsuccessfulPingsForFailure 8 waitTimeAfterSuccessfulPing 30

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

Specifying the EnergyWise Domain

This command syntax specifies to which Cisco® EnergyWise domain the PX2 belongs.

config:# energywise domain

Variables:

- is a string comprising up to 127 ASCII printable characters. Spaces and asterisks are NOT acceptable.

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.

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.

Setting the Polling Interval

This command syntax determines the polling interval at which the Cisco® EnergyWise domain queries the PX2.

config:# energywise polling

Variables:

- is an integer number in seconds. It ranges between 30 and 600 seconds.

Example - Setting Up EnergyWise

The following command sets up two Cisco® EnergyWise-related features.

config:# energywise enabled true port 10288

Results:

• The EnergyWise feature implemented on the PX2 is enabled.
  • The UDP port is set to 10288.

Asset Management Commands

You can use the CLI commands to change the settings of the connected asset strip (if any) or the settings of LEDs on the asset strip.

Asset Strip Management

An asset strip management configuration command begins with assetStrip.

Naming an Asset Strip

This command syntax names or changes the name of an asset strip connected to the PX2 device.

config:# assetStrip name ""

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 device with only one FEATURE port, the number is always 1.
• is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Specifying the Number of Rack Units

This command syntax specifies the total number of rack units on an asset strip connected to the PX2 device.

config:# assetStrip numberOfRackUnits

Note: A rack unit refers to a tag port on the asset strips.

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 device with only one FEATURE port, the number is always 1.
• is the total number of rack units available on the connected asset strip. This value ranges from 8 to 64.

Specifying the Rack Unit Numbering Mode

This command syntax specifies the numbering mode of rack units on the asset strips connected to the PX2 device. The numbering mode changes the rack unit numbers.

config:# assetStrip rackUnitNumberingMode

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 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.

Specifying the Rack Unit Numbering Offset

This command syntax specifies the starting number of rack units on the asset strips connected to the PX2 device.

config:# assetStrip rackUnitNumberingOffset

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 device with only one FEATURE port, the number is always 1.
• is a starting number for numbering rack units on the connected asset strip. This value is an integer number.

Specifying the Asset Strip Orientation

This command syntax specifies the orientation of the asset strips connected to the PX2 device. Usually you do not need to perform this command unless your asset strips do NOT come with the tilt sensor, causing the PX2 unable to detect the asset strips' orientation.

config:# assetStrip assetStripOrientation

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 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.

Setting LED Colors for Connected Tags

This command syntax sets the LED color for all rack units on the asset strip #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.

Setting LED Colors for Disconnected Tags

This command syntax sets the LED color for all rack units on the connected asset strip(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 Configuration

A rack unit refers to a tag port on the asset strips. 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 strip.

config:# rackUnit name ""

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit. The index number is available on the asset strip or the Asset Strip page of the web interface.
• is a string comprising up to 64 ASCII printable characters. The variable must be enclosed in quotes when it contains spaces.

Setting the LED Operation Mode

This command syntax determines whether a specific rack unit on the specified asset strip follows the global LED color settings.

config:# rackUnit LEDOperationMode

Variables:

• is the number of the FEATURE port where the selected asset strip is physically connected. For the PX2 device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit. The index number is available on the asset strip or 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 553) and Setting LED Colors for Disconnected Tags (on page 553).This is the default.

Mode Description

manual This option enables selection of a different LED color and LED mode for the specified rack unit.When this option is selected, seeSetting an LED Color for a Rack Unit(on page 555) andSetting an LED Mode for a Rack Unit(on page 555) to set different LED settings.

Setting an LED Color for a Rack Unit

This command syntax sets the LED color for a specific rack unit on the specified asset strip. 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 strip is physically connected. For the PX2 device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit. The index number is available on the asset strip or 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 553) and Setting LED Colors for Disconnected Tags (on page 553).

Setting an LED Mode for a Rack Unit

This command syntax sets the LED mode for a specific rack unit on the specified asset strip. 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 strip is physically connected. For the PX2 device with only one FEATURE port, the number is always 1.
• is the index number of the desired rack unit. The index number is available on the asset strip or 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.

Examples

This section illustrates several asset management examples.

Example 1 - Asset Strip LED Colors for Disconnected Tags

This command syntax sets the LED color for all rack units on the asset sensor #1 to BLACK (that is, 000000) to indicate the absence of a connected asset tag.

config:# assetStrip 1 LEDColorForDisconnectedTags #000000

Note: Black color causes the LEDs to stay off.

Example 2 - Rack Unit Naming

The following command assigns the name "Linux server" to the rack unit whose index number is 25 on the asset sensor#1.

config:# rackUnit 1 25 name "Linux server"

Serial Port Configuration Commands

A serial port configuration command begins with serial.

Setting the Baud Rates

The following commands set the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the PX2 device. Change the baud rate before connecting it to the desired device, such as a computer, a Raritan's P2CIM-SER, or a modem, through the serial port, or there are communications errors. If you change the baud rate dynamically after the connection has been made, you must reset the PX2 or power cycle the connected device for proper communications.

▶ Determine the CONSOLE baud rate:

config:# serial consoleBaudRate

Note: The serial port bit-rate change is required when the PX2 works in conjunction with Raritan's Dominion LX KVM switch. Dominion LX only supports 19200 bps for communications over the serial interface.

▶ Determine the MODEM baud rate:

config:# serial modemBaudRate

Variables:

- is one of the baud rate options: 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200.

Forcing the Device Detection Mode

This command forces the serial port on the PX2 to enter a specific device detection mode.

config:# serial deviceDetectionType

Variables:

- is one of the detection modes: automatic, forceConsole, forceAnalogModem, or forceGsmModem.

Option Description
automatic The PX2 automatically detects the type of the device connected to the serial port.Select this option unless your PX2 cannot correctly detect the device type.
forceConsole The PX2	attempts to recognize that the connected device is set for the console mode.
forceAnalogModem The	PX2 attempts to recognize that the connected device is an analog modem.
forceGsmModem The	PX2 attempts to recognize that the connected device is a GSM modem.

Example

The following command sets the CONSOLE baud rate of the PX2 device's serial port to 9600 bps.

config:# serial consoleBaudRate 9600

Multi-Command Syntax

To shorten the configuration time, you can combine various configuration commands in one command to perform all of them at a time. All combined commands must belong to the same configuration type, such as commands prefixed with network, user modify, sensor externalsensor and so on.

A multi-command syntax looks like this:

...

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 2nd overcurrent protector.

config:# sensor ocp 2 current upperCritical disable upperWarning 15

Results:

• The Upper Critical threshold of the 2nd overcurrent protector's RMS current is disabled.
• The Upper Warning threshold of the 2nd overcurrent protector's RMS current is set to 15A and enabled at the same time.

Example 3 - Combination of SSID and PSK Parameters

This multi-command syntax configures both SSID and PSK parameters simultaneously for the 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.

Example 4 - Combination of Upper Critical, Upper Warning and Lower Warning Settings

The following multi-command syntax configures Upper Critical, Upper Warning and Lower Warning thresholds for the outlet 5 RMS current simultaneously.

config:# sensor outlet 5 current upperCritical disable upperWarning enable lowerWarning 1.0

Results:

• The Upper Critical threshold of outlet 5 RMS current is disabled.
• The Upper Warning threshold of outlet 5 RMS current is enabled.
- The Lower Warning threshold of outlet 5 RMS current is set to 1.0A and enabled at the same time.

Load Shedding Configuration Commands

This section applies to outlet-switching capable models only.

A load shedding configuration command begins with loadshedding.

Unlike other CLI configuration commands, the load shedding configuration command is performed in the administrator mode rather than the configuration mode. See Different CLI Modes and Prompts (on page 403).

Enabling or Disabling Load Shedding

This section applies to outlet-switching capable models only.

This command determines whether to enter or exit from the load shedding mode.

# loadshedding

After performing the above command, PX2 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

start Enter the load shedding mode.

stop Quit the load shedding mode.

Example

The following command has the PX2 enter the load shedding mode.

config:# loadshedding start

Power Control Operations

This section applies to outlet-switching capable models only.

Outlets on the PX2 can be turned on or off or power cycled through the CLI.

Besides, you can cancel the power-on process while the PX2 is powering on ALL outlets.

You must perform this operation in the administrator mode. See Different CLI Modes and Prompts (on page 403).

Turning On the Outlet(s)

This section applies to outlet-switching capable models only.

This command 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 a hyphen 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

Turning Off the Outlet(s)

This section applies to outlet-switching capable models only.

This command 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 a hyphen 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

Power Cycling the Outlet(s)

This section applies to outlet-switching capable models only.

This command 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 a hyphen 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

Canceling the Power-On Process

This section applies to outlet-switching capable models only.

After issuing the command to power on ALL outlets, you can use the following command to stop the power-on process.

# power cancelSequence

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.

# power cancelSequence /y

Example - Power Cycling Specific Outlets

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

Actuator Control Operations

An actuator, which is connected to a dry contact signal channel of a DX sensor, can control a mechanism or system. You can switch on or off that mechanism or system through the actuator control command in the CLI.

Perform these commands in the administrator or user mode. See Different CLI Modes and Prompts(on page 403).

Switching On an Actuator

This command syntax turns on one actuator.

<h1 id="control-actuator-n-on">control actuator <n> on</h1>

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.

<h1 id="control-actuator-n-on-y">control actuator <n> on /y</h1>

Variables:

- is an actuator's ID number.

The ID number is available in the PX2 web interface or using the show command in the CLI. It is an integer between 1 and 32.

If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:

■ Type y to confirm the operation, OR
■ Type n to abort the operation

Switching Off an Actuator

This command syntax turns off one actuator.

<h1 id="control-actuator-n-off">control actuator <n> off</h1>

To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.

<h1 id="control-actuator-n-off-y">control actuator <n> off /y</h1>

Variables:

- is an actuator's ID number.

The ID number is available in the PX2 web interface or using the show command in the CLI. It is an integer between 1 and 32.

If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:

■ Type y to confirm the operation, OR
■ Type n to abort the operation

Example - Turning On a Specific Actuator

The following command turns on the actuator whose ID number is 8.

# control actuator 8 on

Unblocking a User

If any user is blocked from accessing the PX2, 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 401).
2. When the Username prompt appears, type unblock and press Enter.

Username: unblock

1. When the "Username to unblock" prompt appears, type the name of the blocked user and press Enter.

Username to unblock:

1. A message appears, indicating that the specified user was unblocked successfully.

Resetting the PX2

You can reset the PX2 to factory defaults or simply restart it using the CLI commands.

Restarting the PDU

This command restarts the PX2. It is not a factory default reset.

To restart the PX2:

1. Ensure you have entered administrator mode and the # prompt is displayed.

2. Type either of the following commands to restart the PX2.

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

Note: If you are performing this command over a USB connection, re-connect the USB cable after the reset is completed, or the CLI communications are lost.

Resetting Active Energy Readings

You can reset either one active energy sensor or all active energy sensors at a time to restart the energy accumulation process.

Only users with the "Admin" role assigned can reset active energy readings.

To reset all active energy readings of the PX2:

<h1 id="reset-activeenergy-pdu">reset activeEnergy pdu</h1>
-- OR --
<h1 id="reset-activeenergy-pdu-y">reset activeEnergy pdu /y</h1>

To reset one inlet's active energy readings:

<h1 id="reset-activeenergy-inlet-n">reset activeEnergy inlet <n></h1>
-- OR --
<h1 id="reset-activeenergy-inlet-n-y">reset activeEnergy inlet <n> /y</h1>

To reset one outlet's active energy readings:

<h1 id="reset-activeenergy-outlet-outlet_n">reset activeEnergy outlet <outlet_n></h1>
-- OR --
<h1 id="reset-activeenergy-outlet-outlet_n-y">reset activeEnergy outlet <outlet_n> /y</h1>

To reset one outlet group's active energy readings:

<h1 id="reset-activeenergy-outletgroup-id">reset activeEnergy outletgroup <ID></h1>
-- OR -- 

# reset activeEnergy outletgroup /y

If you entered the command without "/y", a message appears prompting you to confirm the operation. Type y to confirm the reset or n to abort it.

Variables:

• is the inlet number.
• is an outlet number.
• is an outlet group's index number.

Resetting to Factory Defaults

The following commands restore all settings of the PX2 to factory defaults.

To reset PX2 settings after login, use either command:

<h1 id="reset-factorydefaults">reset factorydefaults</h1>
-- OR --
<h1 id="reset-factorydefaults-y">reset factorydefaults /y</h1>

To reset PX2 settings before login:

Username: factorydefaults

See Using the CLI Command(on page 652) for details.

Network Troubleshooting

The PX2 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 Diagnostic Mode

Diagnostic commands function in the diagnostic mode only.

To enter the diagnostic mode:

1. Enter either of the following modes:

2. Administrator mode: The # prompt is displayed.

3. User mode: The > prompt is displayed.

4. Type diag and press Enter. The diag# or diag> prompt appears, indicating that you have entered the diagnostic mode.

5. Now you can type any diagnostic commands for troubleshooting.

Quitting Diagnostic Mode

To quit the diagnostic mode, use this command:

diag> exit

The # or > prompt appears after pressing Enter, indicating that you have entered the administrator or user mode. See Different CLI Modes and Prompts (on page 403).

Diagnostic Commands

The diagnostic command syntax varies from command to command.

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

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

Testing the Network Connectivity

This ping command sends the ICMP ECHO_REQUEST message to a network host for checking its network connectivity. If the output shows the host is responding properly, the network connectivity is good. If not, either the host is shut down or it is not being properly 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
count	Determines the number of messages to be sent. is an integer number between 1 and 100.
size	Determines the packet size. is an integer number in bytes between 1 and 65468.
timeout	Determines the waiting period before timeout. is an integer number in seconds ranging from 1 to 600.

The command looks like the following when it includes all options:

diag> ping count size timeout

Tracing the Route

This command syntax traces the network route between your PX2 and a network host.

diag> traceroute

Variables:

- is the name or IP address of the host you want to trace.

Example - Ping Command

The following command checks the network connectivity of the host 192.168.84.222 by sending the ICMP ECHO_REQUEST message to the host for 5 times.

diag> ping 192.168.84.222 count 5

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 several times until the desired command is displayed.

Automatically Completing a Command

A CLI command always consists of several words. You can easily enter a command by typing first word(s) or letter(s) and then pressing Tab or Ctrl+i instead of typing the whole command word by word.

To have a command completed automatically:

1. Type initial letters or words of the desired command. Make sure the letters or words you typed are unique so that the CLI can identify the command you want.
2. Press Tab or Ctrl+i until the complete command appears.
3. If there are more than one possible commands, a list of these commands is displayed. Then type the full command.

Examples:

• Example 1 (only one possible command):
a. Type the first word and the first letter of the second word of the "reset factorydefaults" command -- that is, reset f. b. Then press Tab or Ctrl+i to complete the second word.

• Example 2 (only one possible command):

a. Type the first word and initial letters of the second word of the "security enforceHttpsForWebAccess" command -- that is, security enf.

b. Then press Tab or Ctrl+i to complete the second word.

• Example 3 (more than one possible commands):

a. Type only the first two words of the "network ipv4 gateway xxx.xxx.xxx.xxx" command -- that is, network ipv4.

b. Then press Tab or Ctrl+i one or two times, a list of possible commands displays as shown below.

gateway interface staticRoutes

c. Type the full command "network ipv4 gateway xxx.xxx.xxx.xxx", according to the onscreen command list.

Logging out of CLI

After completing your tasks using the CLI, always log out of the CLI to prevent others from accessing the CLI.

To log out of the CLI:

1. Ensure you have entered administrator mode and the # prompt is displayed.

2. Type exit and press Enter.

Chapter 9 Using SCP Commands

You can perform a Secure Copy (SCP) command to update the PX2 firmware, do bulk configuration, or back up and restore the configuration.

In This Chapter

Firmware Update via SCP 573

Bulk Configuration via SCP 574

Backup and Restore via SCP 575

Downloading Diagnostic Data via SCP 576

Uploading or Downloading Raw Configuration Data 578

Firmware Update via SCP

Same as any PX2 firmware update, all user management operations are suspended and all login attempts fail during the SCP firmware update. For details, see Updating the PX2 Firmware (on page 359).

Warning: Do NOT perform the firmware upgrade over a wireless network connection.

To update the firmware via SCP:

1. Type the following SCP command and press Enter. scp @:/fwupdate

2. is the PX2 firmware's filename. If the firmware file is not in the current directory, you must include the path in the filename.

3. is the "admin" or any user profile with the Firmware Update permission.

4. is the IP address or hostname of the PX2 where you want to upload the specified file.

5. Type the password when prompted, and press Enter.

6. The system transmits the specified firmware file to the PX2, and shows the transmission speed and percentage.
7. When the transmission is complete, it shows the following message, indicating that the PX2 starts to update its firmware now. Wait until the upgrade completes.

Starting firmware update. The connection will be closed now.

SCP example:

scp pdu-px2-030410-44599.bin admin@192.168.87.50:/fwupdate 

Windows PSCP command:

PSCP in Windows works in a similar way to the SCP.

- pscp <firmware file> <user name>@<device ip>:/fwupdate 

Bulk Configuration via SCP

Like performing bulk configuration via the web interface, there are two steps with the bulk configuration using the SCP commands:

a. Save a configuration from a source PX2.
b. Copy the configuration file to one or multiple destination PX2.

For detailed information on the bulk configuration requirements, see Bulk Configuration (on page 364).

To save the configuration via SCP:

1. Type the following SCP command and press Enter.

scp <user name>@<device ip>:/bulk_config.txt 

• is the "admin" or any user profile with Administrator Privileges.

• is the IP address or hostname of the PX2 whose configuration you want to save.

• Type the user password when prompted.

• The system saves the configuration from the PX2 to a file named "bulk_config.txt."

To copy the configuration via SCP:

1. Type the following SCP command and press Enter.

scp bulk_config.txt <user name>@<device ip>:/bulk_restore 

• is the "admin" or any user profile with Administrator Privileges

• is the IP address of the PX2 whose configuration you want to copy.

• Type the user password when prompted.

• The system copies the configuration included in the file "bulk_config.txt" to another PX2, and displays the following message.

Starting restore operation. The connection will be closed now.

SCP examples:

• Save operation: scp admin@192.168.87.50:/bulk_config.txt
• Copy operation: scp bulk_config.txt admin@192.168.87.47:/bulk_restore

Windows PSCP commands:

PSCP in Windows works in a similar way to the SCP.

• Save operation: pscp @:/bulk_config.txt
• Copy operation: pscp bulk_config.txt @:/bulk_restore

Alternative of bulk configuration via SCP:

Both the methods of uploading 'bulk configuration' file or 'raw configuration' file via SCP can serve the purpose of bulk configuration. The only difference is that you can configure device-specific settings with the upload of raw configuration but not with the 'bulk configuration' file.

- Uploading or Downloading Raw Configuration Data (on page 578)

Backup and Restore via SCP

To back up ALL settings of a PX2, including device-specific settings, you should perform the backup operation instead of the bulk configuration. You can restore all settings to previous ones after a backup file is available.

To back up the settings via SCP:

1. Type the following SCP command and press Enter. scp @:/backup_settings.txt

- is the "admin" or any user profile with Administrator Privileges

- is the IP address or hostname of the PX2 whose settings you want to back up.

1. Type the user password when prompted.
2. The system saves the settings from the PX2 to a file named "backup_settings.txt."

To restore the settings via SCP:

1. Type the following SCP command and press Enter.

scp backup_settings.txt <user name>@<device ip>:/settings_restore 

• is the "admin" or any user profile with Administrator Privileges

• is the IP address or hostname of the PX2 whose settings you want to restore.

• Type the user password when prompted.

• The system copies the configuration included in the file "backup_settings.txt" to the PX2, and displays the following message.

Starting restore operation. The connection will be closed now. 

SCP examples:

- Backup operation: scp admin@192.168.87.50:/backup_settings.txt

- Restoration operation: scp backup_settings.txt admin@192.168.87.50:/settings_restore

Windows PSCP commands:

PSCP in Windows works in a similar way to the SCP.

• Backup operation: pscp @:/backup_settings.txt
• Restoration operation: pscp backup_settings.txt @:/settings_restore

Downloading Diagnostic Data via SCP

You can download the diagnostic data via SCP.

To download the diagnostic data via SCP:

1. Type one of the following SCP commands and press Enter.

Scenario 1: Use the default SCP port and default filename

■ SSH/SCP port is the default (22), and the accessed PX2 is a standalone device.
- The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot (.) in the end of the SCP command as shown below.

scp @:/diag-data.zip.

Scenario 2: Specify a different SCP port but use the default filename

• SSH/SCP port is NOT the default (22), or the accessed PX2 is a Port-Forwarding slave device.
• The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot in the end of the SCP command as shown below.

scp -P @:/diag-data.zip.

Scenario 3: Specify a new filename but use the default SCP port

■ SSH/SCP port is the default (22), and the accessed PX2 is a standalone device.
■ Renaming the diagnostic file is wanted.

scp @:/diag-data.zip

Scenario 4: Specify a different SCP port and a new filename

• SSH/SCP port is NOT the default (22), or the accessed PX2 is a Port-Forwarding slave device.
• Renaming the diagnostic file is wanted.

scp -P @:/diag-data.zip

• is the "admin" or any user profile with Administrator Privileges or "Unrestricted View Privileges" privileges.
• is the IP address or hostname of the PX2 whose data you want to download.
• is the current SSH/SCP port number, or the port number of a specific slave device in the Port-Forwarding chain.

• is the new filename of the downloaded file.

• Type the password when prompted.

• The system downloads the specified data from the PX2 onto your computer.

• If you do NOT specify a new filename in the command, such as Scenarios 1 or 2, the downloaded file's default name is "diag-data.zip."

• If you specify a new filename in the command, such as Scenarios 3 or 4, the downloaded file is renamed accordingly.

SCP example:

scp admin@192.168.87.50:/diag-data.zip.

Windows PSCP command:

PSCP in Windows works in a similar way to the SCP.

- pscp -P @:/diag-data.zip

Uploading or Downloading Raw Configuration Data

You can download the raw configuration data of a specific PX2 for review, backup or modification.

After modifying or creating any raw configuration data, you can upload it to a specific PX2 for changing its configuration. The uploaded raw configuration file can contain only partial configuration keys that you want to modify. Other settings that are not contained in the uploaded file will remain unchanged.

Syntax of the raw configuration data is completely the same as the syntax in the config.txt file. See config.txt (on page 614).

Warning: Some configuration keys in the downloaded raw configuration are commented out, and those must NOT be part of the configuration that will be uploaded to any PX2. See Keys that Cannot Be Uploaded(on page 582).

To download raw configuration data:

1. Type one of the following SCP commands and press Enter.

Scenario 1: Use the default SCP port and default filename

• SSH/SCP port is the default (22), and the accessed PX2 is a standalone device.
• The raw configuration file's default filename "raw_config.txt" is wanted. Then add a dot (.) in the end of the SCP command as shown below.

scp @:/raw_config.txt.

Scenario 2: Specify a different SCP port but use the default filename

• SSH/SCP port is NOT the default (22), or the accessed PX2 is a Port-Forwarding slave device.
• The raw configuration file's default filename "raw_config.txt" is wanted. Then add a dot in the end of the SCP command as shown below.

scp -P @:/raw_config.txt .

Scenario 3: Specify a new filename but use the default SCP port

• SSH/SCP port is the default (22), and the accessed PX2 is a standalone device.
• Renaming the raw configuration file is wanted.

scp @:/raw_config.txt

Scenario 4: Specify a different SCP port and a new filename

• SSH/SCP port is NOT the default (22), or the accessed PX2 is a Port-Forwarding slave device.
• Renaming the raw configuration file is wanted.

scp -P @:/raw_config.txt

• is the "admin" or any user profile with Administrator Privileges.
• is the IP address or hostname of the PX2 whose data you want to download.
• is the current SSH/SCP port number, or the port number of a specific slave device in the Port-Forwarding chain.
• is the new filename of the downloaded file.

2. Type the password when prompted.

3. The system downloads the specified data from the PX2 onto your computer.

• If you do NOT specify a new filename in the command, such as Scenarios 1 or 2, the downloaded file's default name is "raw_config.txt."
• If you specify a new filename in the command, such as Scenarios 3 or 4, the downloaded file is renamed accordingly.

To upload raw configuration data:

1. Type one of the following SCP commands and press Enter.

Scenario 1: Only one PX2 to configure, with the default SCP port

• SSH/SCP port is the default (22), and the accessed PX2 is a standalone device.
• There is only one device to configure so a CSV file for device-specific settings is NOT needed.

scp @:/raw_config_update

Scenario 2: Only one PX2 to configure, with a non-default SCP port

• SSH/SCP port is NOT the default (22), or the accessed PX2 is a Port-Forwarding slave device.
• There is only one device to configure so a CSV file for device-specific settings is NOT needed.

scp-P @:/raw_config_update

Scenario 3: Multiple PX2 to configure, with the default SCP port

• SSH/SCP port is the default (22), and the accessed PX2 is a standalone device.
• There are multiple devices to configure so a CSV file for device-specific settings is needed during the upload.

scp @:/raw_config_update /match=

Scenario 4: Multiple PX2 to configure, with a non-default SCP port

• SSH/SCP port is NOT the default (22), or the accessed PX2 is a Port-Forwarding slave device.
• There are multiple devices to configure so a CSV file for device-specific settings is needed during the upload.

scp -P @:/raw_config_update /match=

• is the filename of the custom raw configuration that you want to upload.
• is the "admin" or any user profile with Administrator Privileges.
• is the IP address or hostname of the PX2 where you want to upload the specified file.

• is the current SSH/SCP port number, or the port number of a specific slave device in the Port-Forwarding chain.

• is the name of the CSV file for configuring multiple PX2 with device-specific settings. For this file's format, see devices.csv (on page 616).

• For device-specific settings in the , refer each device-specific configuration key to a specific column in the . See config.txt (on page 614).
• comprises "serial:" or "mac:" and the number of the column where the serial number or MAC address of each PX2 is in the uploaded CSV file. This is the data based on which each device finds its device-specific settings.

For example:

• If the second column contains each device's serial number, the parameter is then serial:2.
• If the seventh column contains each device's MAC address, the parameter is then mac:7.

SCP examples:

• Raw configuration download example -- scp admin@192.168.87.50:/raw_config.txt config.txt
• Raw configuration upload example with the configuration file only -- scp config.txt admin@192.168.87.50:/raw_config_update
• Raw configuration upload example with both configuration and device list files -- scp devices.csv config.txt admin@192.168.87.50:/raw_config_update/match=serial:2

Windows PSCP commands:

PSCP in Windows works in a similar way to the SCP.

• pscp -P @: /raw_config.txt
• pscp -P @: /raw_config_update /match=

Alternative of bulk configuration via SCP:

Both the methods of uploading 'bulk configuration' file or 'raw configuration' file via SCP can serve the purpose of bulk configuration. The only difference is that you can configure device-specific settings with the upload of raw configuration but not with the 'bulk configuration' file.

• Bulk Configuration via SCP(on page 574)

Keys that Cannot Be Uploaded

The raw configuration downloaded from any PX2 contains a few configuration keys that are commented out with either syntax below.

Comment syntax Description

#INTERNAL# These keys are internal ones. They are NOT user configurable settings.

#OLD/INVALID# These keys are old or invalid ones.

Note that these configuration keys cannot be part of the configuration that you will upload to any PX2. That is, they should be either not available or they remain to be commented out in the configuration file you will upload.

Chapter 10 In-Line Monitors

The model name of a PX2 in-line monitor follows this format: PX2-3nnn, where n is a number, such as PX2-3411.

Unlike most of PX2 devices, each inlet of an in-line monitor is connected to an outlet only, so an inlet's rating/power data is the same as an outlet's rating/power data.

In This Chapter

Overview 583

Safety Instructions 583

Flexible Cord Installation Instructions ....584

In-Line Monitor's LED Display 592

In-Line Monitor's Web Interface 593

Overview

An in-line monitor is implemented with the same number of inlets and outlets.

• Inlets are located at the side labeled Line.
- Outlets are located at the side labeled Load.

An inlet is connected to a power source for receiving electricity, such as electric distribution panels or branch circuit receptacles. An outlet is connected to a device that draws power, such as a cooling or IT device.

Safety Instructions

1. Installation of this product should only be performed by a licensed electrician.
2. Make sure the line cord is disconnected from power before physically mounting or moving the location of this product.
3. This product is intended to be located in an equipment rack in an information technology room. In the United States, installation must comply and be done in accordance with NEC (2011) Article 645 Information Technology Equipment.

4. This product is designed to be used within an electronic equipment rack. The metal case of 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.

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

6. If the product is a model that contains receptacles that can be switched on/off, electric power may still be present at a receptacle even when it is switched off.

Flexible Cord Installation Instructions

The following instructions are for Raritan products manufactured to accept user-installed flexible cords. These products are visually identified by the cable gland used to hold the flexible cord.

Close-up of a black electronic device with a knob and red arrows pointing to ports, shown above with LHE-branded ports (no readable text or symbols)

Important: Complete and the most updated instructions on installing a flexible cord on Raritan PDUs are included in the Raritan PX Power Cord Installation Guide, which is available on the Raritan website's Support page (http://www.raritan.com/support/).

Flexible Cord Selection

• The preferred flexible cable is type SOOW, 600V, 90°C or 105°C. Consult Raritan before using a different flexible cable type.
• The rated ampacity of the flexible cord must be greater than or equal to the Raritan product's rated ampacity marked on its nameplate. In the United States, relevant ampacity ratings for flexible cords can be found in NEC(2011) section 400.5.
• The number of wires in the flexible cord must match the number of terminals (including the ground terminal) inside the Raritan product. See Wiring of 3-Phase In-Line Monitors (on page 586) for exceptions.
• If a plug is to be attached to the flexible cord, the length of the flexible cord must not exceed 4.5 meters - as specified in UL 60950-1 (2007) and NEC 645.5 (2011).
• The flexible cord may be permanently connected to power subject to local regulatory agency approval. In the United States, relevant electrical regulations can be found in NEC (2011) sections 400.7(A)(8), 400.7(B), 368.56 and table 400.4.

Plug Selection

If a plug is to be attached to the flexible cord, the plug's rated ampacity is chosen as follows:

• In the United States, as specified in UL 60950-1, the plug's rated ampacity must be 125% greater than the Raritan product's rated ampacity. In some Raritan products, such as 35A 3-phase delta wired PDUs, an exactly 125% rated plug is not available. In these cases, choose the closest plug that is more than 125% . For example, a 50A plug is the closest fit for a 35A 3-phase PDU.
• For all other locations, subject to local regulatory agency policy, the plug's rated ampacity is the same as the Raritan products rated ampacity.

Receptacle Selection

For Raritan in-line monitors, any receptacle fitted to the outlet flexible cord must have identical ratings as the plug attached to the inlet flexible cord.

Derating a Raritan Product

Lower rated plugs, receptacles and flexible cords may be connected to a Raritan product. This results in a derated (reduced) ampacity rating for the product.

Derating guidelines:

1. Choose the plug and use its rated ampacity to determine the derated ampacity.

In the United States, as specified in UL 60950-1, the derated ampacity is 80% of the plug's rated ampacity. For example, a 30A plug would result in a derated ampacity of 24A.
In other geographic locations, subject to local regulatory agency approval, the derated ampacity is the plug's rated ampacity. For example, using a 16A plug would result in a derated ampacity of 16A.

1. The derated ampacity must be marked on the Raritan product so the new reduced rating can be easily identified.
2. For in-line monitors, the receptacles used must have the same voltage and ampacity rating as the plug chosen in step 1.
3. The flexible cord must have a rated ampacity greater than or equal to the derated ampacity. Since the new flexible cord may be smaller diameter, a check must be performed to insure the cable gland nut, when tightened, will securely hold the flexible cord so that it cannot be twisted, pulled or pushed in the cable gland. A sealing ring, for small diameter flexible cords, may have been included with the Raritan product, or one can be requested from Raritan, to reduce the inside diameter of the cable gland.

Diagram showing two mechanical components: a threaded connector and a hexagonal nut, with no text or symbols present.

Wiring of 3-Phase In-Line Monitors

3-phase in-line monitors contain 4-pole wiring terminal blocks (L1, L2, L3, N) to monitor 5-wire (4P+PE) 3-phase wye connections. Delta wired 4-wire (3P+PE) 3-phase connections are also permitted (no wire connected to the terminal block neutral "N"). No additional hardware or firmware configuration is required to specify whether the connection is 5-wire wye or 4-wire delta.

In-Line Monitor Unused Channels

It is not necessary to wire up all channels of multi-channel in-line monitors. The inlet and outlet openings of unused channels must be completely closed off. "Goof plugs" for this purpose may be a good choice if they are available in your country or region.

Step by Step Flexible Cord Installation

The following items are required to complete the installation:

• Flexible cord(s).
• Insulated ring terminals (one for each wire) and appropriate crimp tool.
• Plug(s) and receptacle(s) (for in-line monitors)
• Torque screwdriver, torque nut driver and torque wrench to tighten the wiring terminal block screws, ground nut and cable gland nut.

To install a flexible cord:

1. Open the PDU's access panel (or in-line monitor top panel) to expose the power wiring terminal block(s).

One-channel in-line monitor

Technical line drawing of a mechanical assembly with no visible text or symbols

Zero U PDU

Make sure to locate the ground wire mounting stud(s). There is a separate ground wire mounting stud for each terminal block. Each flexible cord MUST have its green (or green/yellow) ground wire bonded to a ground wire mounting stud.

Close-up of an electronic device showing a central button and internal components (no visible text or symbols)

For in-line monitors, make sure to identify the inlet terminal blocks (rear of monitor) and outlet terminal blocks (front of monitor). Each inlet terminal block has a corresponding outlet terminal block.

Technical diagram of a mechanical device with labeled components and connection points

Number Description

1

Inlets (labeled LINE)

2

Outlets (labeled LOAD)

1. Strip off the outer jacket of the flexible cord and remove any jute, paper or other fillers. Use the following to help determine how much jacket to remove:

- In the finished assembly, the outer jacket should protrude inside the Raritan product.

• The wires will have ring terminals crimped onto them.
• In the finished assembly, the wires should have some slack and not be taught.

• In the finished assembly, if the flexible cord slips in the cable gland placing a strain on the cord's wires, the ground wire must be the last wire to take the strain.

• Crimp an insulated ring terminal onto each wire. A non-insulated ring terminal may be used for the ground wire. Inspect each crimp to insure it is secure and verify no exposed wire protrudes from the rear of an insulated ring terminal.

• Loosen the cable gland nut and push the flexible cord assembly through the gland.

Close-up of a black electrical cable with multiple wires and metal fittings (no text or symbols visible)

Temporarily hand tighten the gland nut and verify the cord cannot be twisted or pushed or pulled in the gland. Do not proceed if hand tightening results in a loose cord. In some models, especially in-line monitors, the flexible cord's diameter may be too small for the cable gland. A sealing ring for smaller diameter line cords may have been included with the Raritan product, or can be requested from Raritan, to reduce the inside diameter of the cable gland.

Diagram showing two mechanical components: a threaded bolt and a hexagonal nut, with no text or symbols present.

1. Fasten the ring terminal of the green (or green/yellow) ground wire to the chassis's threaded ground stud in this order:

a. Place the lock washer on the stud.
b. Place the ground wire ring terminal on the stud.
c. Place the nut on the stud and tighten with a torque wrench. The appropriate torque settings vary according to the nut size.

Nut size Torque setting (N·m) Tolerance

M3

0.49

10%

Nut size Torque setting (N·m) Tolerance

M4	1.27	8%
M5	1.96	5%
M6	2.94	3.5%
M8	4.9	2%

d. Check the ground wire connection. It should be secure and not move or rotate.

Close-up of a cable being inserted into an electrical switchgear box, with a red circle highlighting the component (no text or symbols visible)

1. Fasten the ring terminals of all remaining wires to the terminal block and tighten each using a torque screwdriver. The appropriate torque settings vary according to the screw size.

Screw size Torque setting (N·m) Tolerance
M3	0.49	10%
M4	1.27	8%
M5	1.96	5%
M6	2.94	3.5%
M8	4.9	2%

Make sure each ring terminal is firmly fastened and cannot be twisted by hand. Use the following guidelines to help terminal block wiring.

In single-phase Raritan products with world-wide ratings, the terminals are labeled L1 and L2. L1 is the phase wire. L2 is either the neutral (120/230V installations) or another phase wire (208V installations).

CH4 L1 L2

In all 3-phase products, L1 is phase A, L2 is phase B, L3 is phase C and N is neutral.
- If your PDU is inlet metered, such as PDU models PX2-1nnn and PX2-2nnn (where n is a number), you must pass each line cord wire through the correct CT in the correct direction. Each CT is labeled and contains a direction arrow. Push the ring terminal end of the line cord through the CT in the direction indicated by the arrow. For example, push the L1 line cord wire through the CT labeled L1 and then connect it to the L1 terminal block.

Terminal block

- For Raritan in-line monitors, where there is a one to one correspondence between plug and receptacle, maintain the same wire colors for inlet and outlet flexible cords.

1. Make final adjustments to the cable gland and verify the jacket of the flexible cord extends into the Raritan product. Hand tighten the gland nut and finish tightening with a torque wrench. Appropriate torque settings vary according to the cable gland size.

Cable gland size Torque setting (N·m)
M12x1.5 0.7 to 0.9
M16x1.5 2.0 to 3.0
M20x1.5 2.7 to 4.0
M25x1.5 5.0 to 7.5
M32x1.5 7.5 to 10.0
M40x1.5 7.5 to 10.0

Cable gland size Torque setting (N·m)

M50x1.5 7.5 to 10.0
M63x1.5 7.5 to 10.0

Note: The cable gland size is marked on the cable gland body.

After tightening, examine the flexible cord and cable gland for the following:

■ Make sure you can see a few remaining threads between the cable gland body and cable gland nut. The gland nut must not bottom out on the gland body.
■ Make sure the flexible cord does not move in the cable gland when it is twisted, pushed or pulled.

1. Re-install the PDU wiring access panel or in-line monitor cover plate. This completes internal wiring of the Raritan product.
2. For in-line monitors, fasten the receptacles to the outlet flexible cords following the manufacturer's instructions.
3. Complete the wiring of the inlet flexible cord by performing one of these steps:

- Assemble the plug following the manufacturer's instructions.

■ Permanently attach and strain relief the flexible cord to a junction box following applicable electrical codes.

In-Line Monitor's LED Display

The LED display of an in-line monitor is the same as a regular PX2 model. See LED Display(on page 73).

Automatic Mode

Unlike regular PX2 models, the in-line monitor's LED display only cycles through the current readings of each outlet in the Automatic Mode.

Manual Mode

You can switch between voltage, active power and current readings of the selected outlet in the Manual Mode on an in-line monitor. To enter the Manual Mode, press the Up or Down button.

To operate the LED display of an inline monitor:

1. Press the Up or Down button until the desired outlet number is selected in the two-digit row.
2. Pressing the Up button moves up one selection.

- Pressing the Down button moves down one selection.

If your inline monitor has only one outlet, go to Step 2.

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

2. If desired, you can press the Up and Down buttons simultaneously to switch between voltage, active power and current readings.

- The voltage appears in this format: XXX (V). It is displayed for about five seconds, after which the current reading re-appears. When the voltage is displayed, the VOLTAGE(V) LED is lit.

- The active power appears in one of the formats: X.XX, XX.X, and XXX (kW). It is displayed for about five seconds, after which the current reading re-appears. When the active power is displayed, the POWER(kW) LED is lit.

1. While the final outlet's active power is being displayed, you can press the Up button to show the first outlet's unbalanced load. The UB LOAD (%) LED is lit.

- Then press the Up and Down buttons to switch between different outlet's unbalanced load readings if there are more than one outlet.

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

In-Line Monitor's Web Interface

An in-line monitor's web interface is similar to a regular PX2 model's web interface.

See Using the Web Interface (on page 86) for login instructions and additional information.

Dashboard Page

An in-line monitor's Dashboard page looks slightly different from a regular PX2 device's Dashboard page.

Note: Depending on your model, elements shown on your page may appear slightly different from this image.

Number Section Content
1	Outlet(s)	Overview of each outlet's power data -- in the above diagram, there are 4 outlets.A current bar per outlet, which changes colors to indicate the RMS current state -- normal (green), warning (yellow) or critical (red).This is similar to Dashboard - Inlet 11(on page 99).
2	Alerted Sensors	When no sensors enter the alarmed state, this section shows the message "No Alerted Sensors."When any sensor enters the alarmed state, this section lists all of them.See Dashboard - Alerted Sensors(on page 102).
3	Outlet History	The historical chart of the first outlet's active power is displayed by default.You can make the diagram show another outlet's or multiple outlets' active power history or select a different data type. See instructions below.
4	Alarms	This section can show data only after you have set event rules requiring users to take the acknowledgment action.When there are no unacknowledged events, this section shows the message "No Alarms."When there are unacknowledged events, this section lists all of them.See Dashboard - Alarms (on page 106).

To go to each outlet's setup page:

1. Locate the desired outlet section.
2. Click its title, such as Inlet/Outlet 1, Inlet/Outlet 2, and the like. The selected outlet's page opens.

▶ To view the inlet power chart:

1. To view the power chart of one or multiple outlets, select one or multiple outlet checkboxes below the diagram.

- When multiple outlets are displayed in the chart, their data lines' colors differ. You can identify their lines according to the colors of the selected outlet checkboxes as illustrated below.

Inlet/Outlet 1 Inlet/Outlet 2 Inlet/Outlet 3 Inlet/Outlet 4

1. To view a different data type, click the selector ▼ at the bottom.

■ Available data types include RMS current, RMS voltage, active power and apparent power.

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

- When the data of multiple outlets is shown in the chart, simply hover your mouse over any outlet's data line. Values of all outlets display simultaneously, marked with corresponding colors.

Inlets/Outlets Page

On the Inlets/Outlets page, you can:

• View each outlet's power data (which is also each inlet's power data)
- Configure each inlet/outlet as needed, such as customizing outlet names, setting thresholds or resetting energy.

Outlet thresholds, when enabled, help you identify whether the outlet enters the warning or critical level. In addition, you can have PX2 automatically generate alert notifications for any warning or critical status. See Event Rules and Actions (on page 262).

Number of available outlet sensors are model dependent.

Operation:

1. Click Inlets/Outlets to open the Inlet(s)/Outlet(s) page.

Chapter 10: In-Line Monitors

Dashboard PDU Inlets / Outlets Peripherals Feature Port User Management Device Settings Maintenance

1. A list of inlets/outlets is displayed. Click "Show Details" of the desired inlet/outlet.

1. The individual inlet/outlet page opens.

On this page, you can:

■ View details, such as its receptacle type
■ View all of its sensors data
- Reset its active energy
■ View its power chart
- Configure its power thresholds

For detailed instructions, see Individual Outlet Pages (on page 129).

Appendix A Specifications

In This Chapter

Maximum Ambient Operating Temperature....601

Serial RS-232 "DB9" Port Pinouts 601

Sensor RJ-12 Port Pinouts....602

Feature RJ-45 Port Pinouts 602

Maximum Ambient Operating Temperature

The maximum ambient operating temperature (TMA) for PX2 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 of your model.

Specification	Measure
Max Ambient Temperature 50 to 60 degrees Celsius

Serial RS-232 "DB9" 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
3	—	—	—
4	—	—	—
5	GND	—	Signal
6 1-wire	1-wire signal for external		environmental sensor packages

Feature RJ-45 Port Pinouts

RJ-45 Pin/signal definition

Pin No.	Signal Direction Description
1	DTR	Output	Reserved
2	GND	—	Signal	Ground
3 +5V	—	Power for CIM(200mA, fuse protected)Warning: Pin 3 is onlyintended for use withRaritan devices.
4 TxD	Output	Transmit Data (Data out)
5 RxD	Input	Receive Data (Data in)
6	N/C	N/C	No Connection	Ground
7	GND	—	Signal
8	DCD	Input	Reserved

Appendix B Equipment Setup Worksheet

PX2 Series Model

PX2 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
OUTLET 7	OUTLET 8 OUTLET 9
MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE
OUTLET 10 OUTLET 11	OUTLET 12

Appendix B: Equipment Setup Worksheet

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
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
OUTLET 22 OUTLET 23 O	OUTLET 24

Appendix B: Equipment Setup Worksheet

MODEL	MODEL	MODEL
SERIAL NUMBER	SERIAL NUMBER	SERIAL NUMBER
USE	USE	USE

Types of adapters

Types of cables

Name of software program

Appendix C Configuration or Firmware Upgrade with a USB Drive

You can accomplish part or all of the following tasks simultaneously by plugging a USB flash drive which contains one or several special configuration files into the PX2.

• Configuration changes
• Firmware upgrade
• Downloading diagnostic data

Tip: You can also accomplish the same tasks via the TFTP server in a DHCP network. See Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 622).

In This Chapter

Device Configuration/Upgrade Procedure....607

System and USB Requirements....608

Configuration Files 609

Firmware Upgrade via USB....620

Device Configuration/Upgrade Procedure

As of version 3.5.0, any firmware downgrade using "fwupdate.cfg" is NOT supported by default. Only firmware upgrade is permitted with "fwupdate.cfg". A special parameter is required to permit firmware downgrade via "fwupdate.cfg". See fwupdate.cfg (on page 609).

Therefore, firmware downgrade via USB is disallowed by default since release 3.5.0.

You can use one USB drive to configure or upgrade multiple PX2 devices one by one as long as it contains valid configuration files.

To use a USB drive to configure the PX2 or upgrade firmware:

1. Verify that both the USB drive and your PX2 meet the requirements. See System and USB Requirements (on page 608).

2. Prepare required configuration files. See Configuration Files (on page 609).

3. Co py required configuration files to the root directory of the USB drive.

- For firmware upgrade, an appropriate firmware binary file is also required.

1. Plug the USB drive into the USB-A port of the PX2.

2. The initial message shown on the front panel display depends on the first task performed by the PX2.

- If no firmware upgrade task will be performed, a happy smiley is displayed after around 30 seconds.

The happy smiley looks like one of the following, depending on your Raritan product. For the first diagram, its background color will turn green.

Simple graphic with a smiley face and a geometric symbol resembling a bracket or minus sign.

■ If the USB drive contains the firmware upgrade data, the PX2:

a. First performs the firmware upgrade, showing the upgrade message on the front panel display.

b. Then shows the happy smiley when the firmware upgrade completes successfully. See Firmware Upgrade via USB(on page 620).

1. After the happy smiley appears, press one of the control buttons next to the display for one second until the smiley disappears.

Tip: You can remove the USB drive and plug it into another PX2 device for performing the same task(s) once the happy smiley or the firmware upgrade message displays.

1. Wait for several seconds until the PX2 resumes normal operation, indicated by the normal message of the display.

If nothing is shown on the display and no task is performed after plugging the USB drive, check the log file in the USB drive.

System and USB Requirements

You must satisfy ALL of the following requirements prior to using a USB flash drive to perform device configuration and/or firmware upgrade.

PX2 system requirements:

• There is at least one USB-A port available on your Raritan device.
- Your PX2 must run firmware version 2.2.13 or later.

Note that the PX2 interpreted the USB drive's contents using the firmware which was running when plugging the USB drive, not the new firmware after firmware upgrade.

USB drive requirements:

• The drive contains either a single partition formatted as a Windows FAT32 filesystem, or NO partition tables (that is, a superfloppy-formatted drive).
• The drive contains a configuration file called fwupdate.cfg in its root directory. See fwupdate.cfg (on page 609).

Configuration Files

There are three types of configuration files.

• fwupdate.cfg:
  This file MUST be always present for performing configuration or firmware upgrade tasks. See fwupdate.cfg (on page 609).
• config.txt:
  This file is used for configuring device settings. See config.txt (on page 614).
• devices. csv:
  This file is required only when there are device-specific settings to configure for multiple PX2 devices. See devices.csv (on page 616).

Raritan provides a Mass Deployment Utility, which helps you to quickly generate all configuration files for your PX2. See Creating Configuration Files via Mass Deployment Utility (on page 617).

fwupdate.cfg

The configuration file, fwupdate.cfg, is an ASCII text file containing key-value pairs, one per line.

Each value in the file must be separated by an equal sign (=), without any surrounding spaces. Keys are not case sensitive.

Illustration:

user=admin
password=raritan
logfile=log.txt
config=config.txt
device_list=devices.csv 

This section only explains common options in the file.

Note: To make sure all of the following options work fine, you must update your PX2 to the latest firmware version.

user

• A required option.
• Specify the name of a user account with Administrator Privileges.
• For PX2 with factory default configuration, set this option to admin.

password

• A required option.
• Specify the password of the specified admin user.
• For PX2 with factory default configuration, set this option to raritan.

Tip: As of release 3.5.0, you can add multiple user credentials to fwupdate.cfg. Each 'user' line must be immediately followed by its 'password' line. PX2 will authenticate listed user credentials one by one until one of them succeeds, or until all user credentials fail.

logfile

• Specify the name of a text file where the PX2 will append the log messages when interpreting the USB drive contents.
• If the specified file does not exist in the USB drive, it will be automatically created.
• If this option is not set, no log messages are recorded. The disadvantage is that no feedback is available if the PX2 detects a problem with the USB drive contents.

firmware

• Specify the name of a firmware binary file used to upgrade your PX2.
• The specified firmware file must be compatible with your PX2 and have an official Raritan signature.
• If the specified firmware file is the same as the current firmware version of your PX2, no firmware upgrade is performed.
• As of version 3.5.0, the default is to NOT permit any firmware downgrade via USB on Raritan power products with "USB-A" port(s). To do this, the parameter "allow_downgrade" must be present and properly set in the fwupdate.cfg file.

config

• Specify the name of the configuration file containing device settings.
• The suggested filename is config.txt. See config.txt(on page 614).

device\_list

• Specify the name of the configuration file listing all PX2 devices to configure and their device-specific settings.
• This file is required if any macros are used in the device configuration file "config.txt."
• The suggested filename is devices.csv. See devices.csv(on page 616).

match

- Specify a match condition for identifying a line or one PX2 device in the device configuration file "devices.csv."

The option's value comprises one word and one number as explained below:

• The word prior to the colon is an identification property, which is either serial for serial number or mac for MAC address.
• The number following the colon indicates a column in the devices.csvfile.

For example, mac: 7 instructs the PX2 to search for the MAC address in the 7th column of the "devices.csv" file.

• The default value is serial:1, making the PX2 search for its serial number in the first column.
• This option is used only if the "device_list" option has been set.

factory\_reset

• If this option is set to true, the PX2 will be reset to factory defaults.
• If the device configuration will be updated at the same time, the factory reset will be executed before updating the device configuration.

bulk\_config\_restore

- Specify the name of the bulk configuration file used to configure or restore the PX2.

Note: See Bulk Configuration (on page 364) for instructions on generating a bulk configuration file.

• Additional configuration keys set via the config.txt file will be applied after performing the bulk restore operation.
• This option CANNOT be used with the option "full_config_restore."
• If a firmware upgrade will be performed at the same time, you must generate the bulk configuration file based on the NEW firmware version instead of the current firmware version.

full\_config\_restore

- Specify the name of the full configuration backup file used to restore the PX2.

Note: See Backup and Restore of Device Settings (on page 371) for instructions on generating the full configuration backup file.

• Additional configuration keys set via the config.txt file will be applied after performing the configuration restore operation.
• This option CANNOT be used with the option "bulk_config_restore."
• If a firmware upgrade will be performed at the same time, you must generate the full configuration backup file based on the NEW firmware version instead of the current firmware version.

collect\_diag

• If this option is set to true, the diagnostic data of the PX2 is transmitted to the USB drive.
• The filename of the diagnostic data written into the USB drive is: diag_.zip

- The PX2 device beeps after it finishes writing the diagnostic data to the USB drive.

switch\_outlets

• This feature works on outlet-switching capable models only.
- Switch on or off specific outlets.
- The option's value comprises outlet numbers and the setting "on" or "off" as explained below:

• Each "on" or "off" setting consists of three parts: outlet numbers, a colon, and the word "on" or "off".
  ■ Each "on" or "off" setting is separated with a semicolon.
  If all outlets will share the same "on" or "off" setting, replace the outlet numbers with the word "all".

- Examples:

• Turn on outlets 1 to 3, and 10, and turn off outlets 4 to 9. switch_outlets=1,2,3:on;4-9:off;10:on
• Turn on all outlets. switch_outlets=all:on

tls\_cert\_file

• Specify the filename of the wanted TLS server certificate. The filename can contain a single placeholder \${SERIAL} that is replaced with the serial number of the PX2.
• This option should be used with tls_key_file listed below.
• This option is NOT supported by bulk configuration or backup/restore via DHCP/TFTP.

tls\_key\_file

• Specify the filename of the wanted TLS server key. The filename can contain a single placeholder \${SERIAL} that is replaced with the serial number of the PX2.
• This option should be used with tls_cert_file listed above.
• This option is NOT supported by bulk configuration or backup/restore via DHCP/TFTP.

execute\_lua\_script

- Specify a Lua script file. For example: execute_lua_script=my_script.lua

• Script output will be recorded to a log file -- ..log. Note this log file's size is limited on DHCP/TFTP.
• A DHCP/TFTP-located script has a timeout of 60 seconds. After that duration the script will be removed.
• This feature can be used to manage LuaService, such as upload, start, get output, and so on.
• If you unplug the USB drive while the Lua script is still running, the script will be removed.
• An exit handler can be used but the execution time is limited to three seconds. Note that this is not implemented on DHCP/TFTP yet.

allow\_downgrade

• As of version 3.5.0, this parameter is required for any firmware downgrade via USB drive, or the firmware upgrade via USB drive will fail.
• Add this parameter to this configuration file and set its value to yes.

Tip: Only firmware downgrade via USB is disabled by default. To downgrade firmware using other methods is still feasible by default, such as firmware downgrade via web interface.

config.txt

To perform device configuration using a USB drive, you must:

• Copy the device configuration file "config.txt" to the root directory of the USB drive.
• Reference the "config.txt" file in the configuration of the "fwupdate.cfg" file. See fwupdate.cfg (on page 609).

The file, config.txt, is a text file containing a number of configuration keys and values to configure or update.

This section only introduces the device configuration file in brief, and does not document all configuration keys, which vary according to the firmware version and your PX2 model.

You can use Raritan's Mass Deployment Utility to create this file by yourself, or contact Raritan to get a device configuration file specific to your PX2 model and firmware version.

Tip: You can choose to encrypt important data in the "config.txt" file so that people cannot easily recognize it, such as the SNMP write community string. See Data Encryption in 'config.txt' (on page 618).

▶ Regular configuration key syntax:

- Each configuration key and value pair is in a single line as shown below:

key=value 

Note: Each value in the file must be separated by an equal sign (=) , without any surrounding spaces.

- Multi-line values are supported by using the Here Document Syntax with a user-chosen delimiter.

The following illustration declares a value in two lines. You can replace the delimiter EOF with other delimiter strings.

key<<EOF 

value line 1 

value line 2 

EOF 

Note: The line break before the closing EOF is not part of the value. If a line break is required in the value, insert an additional empty line before the closing EOF. 

▶ Special configuration keys:

There are 3 special configuration keys that are prefixed with magic:.

- A special key that sets a user account's password without knowing the firmware's internal encryption/hashing algorithms is implemented.

Example:

magic:users[1].cleartext_password=joshua 

- Two special keys that set the SNMPv3 passphrases without knowing the firmware's internal encryption/hashing algorithms are implemented.

Examples:

magic:users[1].snmp_v3.auth_phrase=swordfish 

magic:users[1].snmp_v3.priv_phrase=opensesame 

To configure device-specific settings:

1. Make sure the device list configuration file "devices.csv" is available in the USB drive. See devices.csv (on page 616)

2. In the "config.txt" file, refer each device-specific configuration key to a specific column in the "devices.csv" file. The syntax is: \${column}, where "column" is a column number.

Examples:
net.interfaces[eth0].ipv4.static.addr_cidr.addr=${4}
pdu.name=${16} 

To rename the admin user:

You can rename the admin user by adding the following configuration key:

users[0].name=new admin name 

Example:

users[0].name=May 

To encrypt any settings:

You can encrypt the value of any setting in the config.txt. See Data Encryption in 'config.txt' (on page 618).

To restore a specific setting to factory default:

Add "delete:" to the beginning of the key whose setting you want to remove. The custom setting will be removed and then reset to factory default.

Example:

delete:net.port_forwarding 

Tip:

You can also download "config.txt" from a specific PX2 or upload it to a specific PX2 from anywhere in the world via Internet. See Raw Configuration Upload and Download (on page 645).

devices.csv

If there are device-specific settings to configure, you must create a device list configuration file - devices.csv, to store unique data of each PX2 device.

This file must be:

• A CSV (comma-separated values) format file exported from a spreadsheet application like Excel.
  • Copied to the root directory.
• Referenced in the device_list option of the "fwupdate.cfg" file. See fwupdate.cfg (on page 609).

Every PX2 identifies its entry in the "devicelist.csv" file by comparing its serial number or MAC address to one of the columns in the file.

▶ Determine the column to identify PX2 devices:

• By default, the PX2 searches for its serial number in the 1st column.
• To override the default, set the match option in the "fwupdate.cfg" file to a different column.

Syntax:

• Values containing commas, line breaks or double quotes are all supported.
• The commas and line breaks to be included in the values must be enclosed in double quotes.
• Every double quote to be included in the value must be escaped with another double quote.

For example: Value-1, "Value-2, with, three, commas", Value-3

Value-1, "Value-2," "with" "three" "double-quotes", Value-3

Value-1, "Value-2 with a line break", Value-3

Creating Configuration Files via Mass Deployment Utility

The Mass Deployment Utility is an Excel file that lets you fill in basic information required for the three configuration files, such as the admin account and password.

After entering required information, you can generate all configuration files with only one click, including fwupdate.cfg, config.txt and devices.csv.

To use the Mass Deployment Utility:

1. Download the Mass Deployment Utility from the Raritan website.

- The utility is named mass_deployment-xxx(where xxx is the firmware version number).

It is available on the PX2 product section of Raritan website's Support page (http://www.raritan.com/support/).

1. Launch Excel to open this utility.

Note: Other office suites, such as OpenOffice and LibreOffice, are not supported.

1. Read the instructions in the 1st worksheet of the utility, and make sure Microsoft Excel's security level has been set to Medium or the equivalent for executing unsigned macros of this utility.

2. Enter information in the 2nd and 3rd worksheets.

3. The 2nd worksheet contains information required for fwupdate.cfg and config.txt.
   ■ The 3rd worksheet contains device-specific information for devices.csv.

4. Return to the 2nd worksheet to execute the export macro.

a. In the Target Directory field, specify the folder where to generate the configuration files. For example, you can specify the root directory of a connected USB drive.
b. Click Export Lists to generate configuration files.

Target Directory: C:\temp Browse... Export Lists

1. Verify that at least 3 configuration files are created - fwupdate.cfg, config.txt and devices.csv. You are ready to configure or upgrade any PX2 with these files. See Configuration or Firmware Upgrade with a USB Drive (on page 607).

Data Encryption in 'config.txt'

When intending to prevent people from identifying the values of any settings, you can encrypt them. Encrypted data still can be properly interpreted and performed by any PX2 running firmware version 3.2.20 or later.

Data encryption procedure:

1. Open the "config.txt" file to determine which setting(s) to encrypt.

If an appropriate "config.txt" is not created yet, see Creating Configuration Files via Mass Deployment Utility (on page 617).

1. Launch a terminal to log in to the CLI of any PX2 running version 3.2.20 or later. See Logging in to CLI (on page 401).

2. Type the encryption command and the value of the setting you want to encrypt.

3. The value cannot contain any double quotes (") or backslashes (-).

4. If the value contains spaces, it must be enclosed in double quotes.

<h1 id="config-encrypt-value">config encrypt <value></h1>

-- OR -- 

<h1 id="config-encrypt-value-with-spaces">config encrypt "<value with spaces>"</h1>

1. Press Enter. The CLI generates and displays the encrypted form of the typed value.
2. Go to the "config.txt" file and replace the chosen value with the encrypted one by typing or copying the encrypted value from the CLI.
3. Add the text "encrypted:" to the beginning of the encrypted setting.
4. Repeat steps 3 to 6 for additional settings you intend to encrypt.
5. Save the changes made to the "config.txt" file. Now you can use this file to configure any PX2 running version 3.2.20 or later. See Configuration or Firmware Upgrade with a USB Drive(on page 607).

Illustration:

In this example, we will encrypt the word "private", which is the value of the SNMP write community in the "config.txt" file.

snmp.write_community=private 

1. In the CLI, type the following command to encrypt "private."

1. The CLI generates and shows the encrypted form of "private."

1. In the "config.txt" file, make the following changes to the SNMP write community setting.

a. Replace the word "private" with the encrypted value that CLI shows.

snmp.write_community=ZTtnYcvQUw== 

b. Add "encrypted:" to the beginning of that setting.

encrypted: snmp.write_community=ZTtnYcvQUw== 

Firmware Upgrade via USB

Firmware files are available on Raritan website's Support page (http://www.raritan.com/support/).

Note that if the firmware file used for firmware upgrade is the same as the firmware version running on the PX2, no firmware upgrade will be performed unless you have set the force_update option to true in the "fwupdate.cfg" file. See fwupdate.cfg (on page 609).

To use a USB drive to upgrade the PX2:

1. Copy the configuration file "fwupdate.cfg" and an appropriate firmware file to the root directory of the USB drive.
2. Reference the firmware file in the image option of the "fwupdate.cfg" file.
3. Plug the USB drive into the USB-A port on the PX2.
4. The PX2 performs the firmware upgrade. The upgrade message "FuP" is shown on the front panel display.

Tip: You can remove the USB drive and plug it into another PX2 for firmware upgrade when the firmware upgrade message displays.

1. It may take one to five minutes to complete the firmware upgrade, depending on your product.

2. When the firmware upgrade finishes, the front panel display indicates the firmware upgrade result.

- Happy smiley: Successful. Depending on your product, the happy smiley looks like one of the following. For the first diagram, its background color will turn green.

Simple graphic with a smiley face and a geometric symbol resembling a bracket or minus sign.

- Sad smiley: Failed. Check the log file in the USB drive or contact Raritan Technical Support to look into the failure cause.

The sad smiley looks like one of the following. For the first diagram, its background color will turn red.

Simple visual symbols including a sad face and a simple geometric line, possibly representing a negative or neutral expression.

Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP

If a TFTP server is available, you can use it and appropriate configuration files to perform any or all of the following tasks for a large number of PX2 devices in the same network.

• Initial deployment
• Configuration changes
• Firmware upgrade
• Downloading diagnostic data

This feature is drastically useful if you have hundreds or even thousands of PX2 devices to configure or upgrade.

Warning: The feature of bulk configuration or firmware upgrade via DHCP/TFTP only works on standalone PX2 devices directly connected to the network. This feature does NOT work for slave devices in the cascading configuration.

Tip: For the other alternatives, see Configuration or Firmware Upgrade with a USB Drive (on page 607) or Raw Configuration Upload and Download (on page 645).

In This Chapter

Bulk Configuration/Upgrade Procedure 622

TFTP Requirements 623

DHCP IPv4 Configuration in Windows....624

DHCP IPv6 Configuration in Windows....634

DHCP IPv4 Configuration in Linux 641

DHCP IPv6 Configuration in Linux 643

Bulk Configuration/Upgrade Procedure

As of version 3.5.0, any firmware downgrade using "fwupdate.cfg" is NOT supported by default. Only firmware upgrade is permitted with "fwupdate.cfg". A special parameter is required to permit firmware downgrade via "fwupdate.cfg". See fwupdate.cfg (on page 609).

Therefore, firmware "downgrade" via DHCP/TFTP is disallowed by default since release 3.5.0.

Steps of using DHCP/TFTP for bulk configuration/upgrade:

1. Create configuration files specific to your PX2 models and firmware versions. See Configuration Files (on page 609) or contact Raritan Technical Support to properly prepare some or all of the following files:

■ fwupdate.cfg (always required)
- config.txt
■ devices.csv

Note: Supported syntax of "fwupdate.cfg" and "config.txt" may vary based on different firmware versions. If you have existing configuration files, it is suggested to double check with Raritan Technical Support for the correctness of these files prior to using this feature.

1. Configure your TFTP server properly. See TFTP Requirements (on page 623).
2. Copy ALL required configuration files into the TFTP root directory. If the tasks you will perform include firmware upgrade, an appropriate firmware binary file is also required.
3. Properly configure your DHCP server so that it refers to the file "fwupdate.cfg" on the TFTP server for your PX2.

Click one or more of the following links for detailed DHCP configuration instructions, based on your operating system and the IP address type.

■ DHCP IPv4 Configuration in Windows (on page 624)
- DHCP IPv6 Configuration in Windows (on page 634)
■ DHCP IPv4 Configuration in Linux (on page 641)
■ DHCP IPv6 Configuration in Linux (on page 643)

1. Make sure all of the desired PX2 devices use DHCP as the IP configuration method and have been directly connected to the network.
2. Re-boot these PX2 devices. The DHCP server will execute the commands in the "fwupdate.cfg" file on the TFTP server to configure or upgrade those PX2 devices supporting DHCP in the same network.

DHCP will execute the "fwupdate.cfg" commands once for IPv4 and once for IPv6 respectively if both IPv4 and IPv6 settings are configured properly in DHCP.

TFTP Requirements

To perform bulk configuration or firmware upgrade successfully, your TFTP server must meet the following requirements:

• The server is able to work with both IPv4 and IPv6.

In Linux, remove any IPv4 or IPv6 flags from /etc/xinetd.d/tftp.

Note: DHCP will execute the "fwupdate.cfg" commands once for IPv4 and once for IPv6 respectively if both IPv4 and IPv6 settings are configured properly in DHCP.

- All required configuration files are available in the TFTP root directory. See Bulk Configuration/Upgrade Procedure(on page 622).

If you are going to upload any PX2 diagnostic file or create a log file in the TFTP server, the first of the following requirements is also required.

- The TFTP server supports the write operation, including file creation and upload.

In Linux, provide the option "-c" for write support.

- Required for uploading the diagnostic file only - the timeout for file upload is set to one minute or longer.

DHCP IPv4 Configuration in Windows

For those PX2 devices using IPv4 addresses, follow this procedure to configure your DHCP server. The following illustration is based on Microsoft® Windows Server 2012 system.

▶ Required Windows IPv4 settings in DHCP:

1. Add a new vendor class for Raritan's PX2 under IPv4.

a. Right-click the IPv4 node in DHCP to select Define Vendor Classes.

b. Click Add to add a new vendor class.

DHCP Vendor Classes Available classes: Name Description Microsoft Windows 20... Microsoft vendor-specific option... Microsoft Windows 98 ... Microsoft vendor-specific option... Microsoft Options Microsoft vendor-specific option... Add... Edit... Remove Close

c. Specify a unique name for this vendor class and type the binary codes of "Raritan PDU 1.0" in the New Class dialog.

The vendor class is named "Raritan PDU" in this illustration.

New Class Display name: Raritan PDU Description: Raritan PDU ID: Binary: ASCII: 0000 52 61 72 69 74 61 6E 20 Raritan 0008 50 44 55 20 31 2E 30 PDU 1.0 OK Cancel

1. Define one DHCP standard option - Vendor Class Identifier.

a. Right-click the IPv4 node in DHCP to select Set Predefined Options.
b. Select DHCP Standard Options in the "Option class" field, and Vendor Class Identifier in the "Option name" field. Leave the String field blank.

Predefined Options and Values Option class: DHCP Standard Options Option name: 060 Vendor Class Identifier 046 WINS/NBT Node Type 047 NetBIOS Scope ID 048 X Window System Font 049 X Window System Display Description: 060 Vendor Class Identifier 064 NIS÷ Domain Name 065 NIS÷ Servers Value String: OK Cancel

1. Add three options to the new vendor class "Raritan PDU" in the same dialog.

a. Select Raritan PDU in the "Option class" field.

Predefined Options and Values Option class: Raritan PDU Option name: DHCP Standard Options Microsoft Windows 2000 Options Microsoft Windows 98 Options Microsoft Options Raritan PDU Description: Value String: OK Cancel

b. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.

Option Type Class: Raritan PDU Name: pdu-tftp-server Data type: IP Address □ Array Code: 1 Description: OK Cancel

c. Click Add to add the second option. Type "pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field.

Option Type Class: Raritan PDU Name: pdu-update-control-file Data type: String Array Code: 2 Description: OK Cancel

d. Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field.

Option Type Class: Raritan PDU Name: pdu-update-magic Data type: String Array Code: 3 Description: OK Cancel

1. Create a new policy associated with the "Raritan PDU" vendor class.

a. Right-click the Policies node under IPv4 to select New Policy.
b. Specify a policy name, and click Next.

The policy is named "PDU" in this illustration.

DHCP Policy Configuration Wizard Policy based IP Address and Option Assignment This feature allows you to distribute configurable settings (IP address, DHCP options) to clients based on certain conditions (e.g. vendor class, user class, MAC address, etc.). This wizard will guide you setting up a new policy. Provide a name (e.g. VoIP Phone Configuration Policy) and description (e.g. NTP Server option for VoIP Phones) for your policy. Policy Name: PDU Description: < Back Next > Cancel

c. Click Add to add a new condition.
d. Select the vendor class "Raritan PDU" in the Value field, click Add and then Ok.

Add/Edit Condition Specify a condition for the policy being configured. Select a criteria, operator and values for the condition. Criteria: Vendor Class Operator: Equals Value(s) Value: Raritan PDU Add Prefix wildcard(*) Append wildcard(*) Raritan PDU Remove Ok Cancel

e. Click Next.

f. Select DHCP Standard Options in the "Vendor class" field, select "060 Vendor Class Identifier" from the Available Options list, and type "Raritan PDU 1.0" in the "String value" field.

DHCP Policy Configuration Wizard Configure settings for the policy If the conditions specified in the policy match a client request, the settings will be applied. Vendor class: DHCP Standard Options Available Options Description 049 X Window System Display Array of X Windows Display M# 060 Vendor Class Identifier 064 NIS÷ Domain Name The name of the client's NIS÷ Data entry String value: Raritan PDU 1.0 < Back Next > Cancel

g. Select the "Raritan PDU" in the "Vendor class" field, select "001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv4 address in the "IP address" field.

DHCP Policy Configuration Wizard Configure settings for the policy If the conditions specified in the policy match a client request, the settings will be applied. Vendor class: Raritan PDU Available Options Description ✓ 001 pdu-tftp-server □ 002 pdu-update-control-file □ 003 pdu-update-magic Data entry IP address: 192 . 168 . 85 . 93 < Back Next > Cancel

h. Select "002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field.

DHCP Policy Configuration Wizard

Configure settings for the policy

If the conditions specified in the policy match a client request, the settings will be applied.

Vendor class:

Raritan PDU

Available Options

Description

001 pdu-tftp-server
002 pdu-update-control file
□ 003 pdu-update-magic

- Data entry

String value:

fwupdate.cfg

< Back

Next >

Cancel

i. Select "003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly. It does NOT matter whether the IPv4 magic cookie is identical to or different from the IPv6 magic cookie.

The magic cookie is a string comprising numerical and/or alphabetical digits in any format. In the following illustration diagram, it is a combination of a date and a serial number.

Important: The magic cookie is transmitted to and stored in PX2 at the time of executing the "fwupdate.cfg" commands. The DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX2. Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg" commands next time.

DHCP Policy Configuration Wizard Configure settings for the policy If the conditions specified in the policy match a client request, the settings will be applied. Vendor class: Raritan PDU Available Options Description ✓ 001 pdu-tftp-server ✓ 002 pdu-update-control-file ✓ 003 pdu-update-magic Data entry String value: 20150427-0001 < Back Next > Cancel

DHCP IPv6 Configuration in Windows

For those PX2 devices using IPv6 addresses, follow this procedure to configure your DHCP server. The following illustration is based on Microsoft® Windows Server 2012 system.

▶ Required Windows IPv6 settings in DHCP:

1. Add a new vendor class for Raritan's PX2 under IPv6.

a. Right-click the IPv6 node in DHCP to select Define Vendor Classes.
b. Click Add to add a new vendor class.

DHCP Vendor Classes Available classes: Name Description Microsoft Windows Opt... Microsoft vendor-specific option... Add... Edit... Remove Close

c. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)" field, and type the binary codes of "Raritan PDU 1.0" in the New Class dialog.

The vendor class is named "Raritan PDU 1.0" in this illustration.

New Class Display name: Raritan PDU 1.0 Description: Raritan PDU 1.0 Vendor ID (IANA): 13742 ID: Binary: ASCII: 0000 52 61 72 69 74 61 6E 20 Raritan 0008 50 44 55 20 31 2E 30 PDU 1.0 OK Cancel

1. Add three options to the "Raritan PDU 1.0" vendor class.

a. Right-click the IPv6 node in DHCP to select Set Predefined Options.
b. Select Raritan PDU 1.0 in the "Option class" field.

Predefined Options and Values for v6 Option class: Raritan PDU 1.0 Option name: DHCP Standard Options Microsoft Windows Options Raritan PDU 1.0 Add... Edit... Delete Description: Value String: OK Cancel

c. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.

Option Type Class: Raritan PDU 1.0 Name: pdu-tftp-server Data type: IP Address □ Array Code: 1 Description: OK Cancel

d. Click Add to add the second option. Type "pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field.

Option Type Class: Raritan PDU 1.0 Name: pdu-update-control-file Data type: String Array Code: 2 Description: OK Cancel

e. Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field.

Option Type Class: Raritan PDU 1.0 Name: pdu-update-magic Data type: String Array Code: 3 Description: OK Cancel

1. Configure server options associated with the "Raritan PDU 1.0" vendor class.

a. Right-click the Server Options node under IPv6 to select Configure Options.
b. Click the Advanced tab.
c. Select "Raritan PDU 1.0" in the "Vendor class" field, select "00001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv6 address in the "IPv6 address" field.

Server Options General Advanced Vendor class: Raritan PDU 1.0 User class: Default User Class Available Options Description 00001 pdu-tftp-server 00002 pdu-update-control-file 00002.pdu-update-magia Data entry IPv6 address: fd07:2fa:6cff:1010::200 OK Cancel Apply

d. Select "00002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field.

Server Options General Advanced Vendor class: Raritan PDU 1.0 User class: Default User Class Available Options Description ✓ 00001 pdu-tftp-server ✓ 00002 pdu-update-control file ✓ 00002 pdu-update-magio < III > Data entry String value: fwupdate.cfg OK Cancel Apply

e. Select "00003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly. It does NOT matter whether the IPv6 magic cookie is identical to or different from the IPv4 magic cookie.

The magic cookie is a string comprising numerical and/or alphabetical digits in any format. In the following illustration diagram, it is a combination of a date and a serial number.

Important: The magic cookie is transmitted to and stored in PX2 at the time of executing the "fwupdate.cfg" commands. The DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX2. Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg" commands next time.

Server Options General Advanced Vendor class: Raritan PDU 1.0 User class: Default User Class Available Options Description ✓ 00002 pdu-update-control-file ✓ 00003 pdu-update-magic Data entry String value: 20150427-6001 OK Cancel Apply

DHCP IPv4 Configuration in Linux

Modify the "dhcpd.conf" file for IPv4 settings when your DHCP server is running Linux.

▶ Required Linux IPv4 settings in DHCP:

1. Locate and open the "dhcpd.conf" file of the DHCP server.
2. The PX2 will provide the following value of the vendor-class-identifier option (option 60).

■ vendor-class-identifier = "Raritan PDU 1.0"

Configure the same option in DHCP accordingly. The PX2 accepts the configuration or firmware upgrade only when this value in DHCP matches.

1. Set the following three sub-options in the

"vendor-encapsulated-options" (option 43).

code 1 (pdu-tftp-server) = the TFTP server's IPv4 address

• code 2 (pdu-update-control-file) = the name of the control file "fwupdate.cfg"
• code 3 (pdu-update-magic) = any string
  This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly. It does NOT matter whether the IPv4 magic cookie is identical to or different from the IPv6 magic cookie.
  The magic cookie is a string comprising numerical and/or alphabetical digits in any format. In the following illustration diagram, it is a combination of a date and a serial number.

Important: The magic cookie is transmitted to and stored in PX2 at the time of executing the "fwupdate.cfg" commands. The DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX2. Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg" commands next time.

IPv4 illustration example in dhcpd.conf:

[...]
set vendor-string = option vendor-class-identifier;
option space RARITAN code width 1 length width 1 hash size 3;
option RARITAN.pdu-tftp-server code 1 = ip-address;
option RARITAN.pdu-update-control-file code 2 = text;
option RARITAN.pdu-update-magic code 3 = text;

class "raritan" {
    match if option vendor-class-identifier = "Raritan PDU 1.0";
    vendor-option-space    RARITAN;
    option RARITAN.pdu-tftp-server 192.168.1.7;
    option RARITAN.pdu-update-control-file "fwupdate.cfg";
    option RARITAN.pdu-update-magic "20150123-0001";
    option vendor-class-identifier "Raritan PDU 1.0";
}
[...] 

DHCP IPv6 Configuration in Linux

Modify the "dhcpd6.conf" file for IPv6 settings when your DHCP server is running Linux.

▶ Required Linux IPv6 settings in DHCP:

1. Locate and open the "dhcpd6.conf" file of the DHCP server.
2. The PX2 will provide the following values to the "vendor-class" option (option 16). Configure related settings in DHCP accordingly.

■ 13742 (Raritan's IANA number)
- Raritan PDU 1.0
■ 15 (the length of the above string "Raritan PDU 1.0")

1. Set the following three sub-options in the "vendor-opts" (option 17).

code 1 (pdu-tftp-server) = the TFTP server's IPv6 address
- code 2 (pdu-update-control-file) = the name of the control file "fwupdate.cfg"
■ code 3 (pdu-update-magic) = any string

This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly. It does NOT matter whether the IPv6 magic cookie is identical to or different from the IPv4 magic cookie.

The magic cookie is a string comprising numerical and/or alphabetical digits in any format. In the following illustration diagram, it is a combination of a date and a serial number.

Important: The magic cookie is transmitted to and stored in PX2 at the time of executing the "fwupdate.cfg" commands. The DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX2. Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg" commands next time.

IPv6 illustration example in dhcpd6.conf:

[...]
option space RARITAN code width 2 length width 2 hash size 3;
option RARITAN.pdu-tftp-server code 1 = ip6-address;
option RARITAN.pdu-update-control-file code 2 = text;
option RARITAN.pdu-update-magic code 3 = text;
option vsio.RARITAN code 13742 = encapsulate RARITAN;

[...]

subnet6 xxxx {

[...]
option RARITAN.pdu-tftp-server 1::2;
option RARITAN.pdu-update-control-file "fwupdate.cfg";
option RARITAN.pdu-update-magic "20150123-0001";
[...]

} 

Appendix E Raw Configuration Upload and Download

You can modify any existing "config.txt", and then upload it to a specific PX2 for modifying part or all of its settings.

There are two ways to get one "config.txt":

• You create this file by yourself, either using or not using the Mass Deployment Utility. See Configuration Files (on page 609) and config.txt (on page 614).
• You download the raw configuration data from any PX2.

The downloaded raw configuration contains "almost" all of current settings on your PX2.

Warning: Some configuration keys in the downloaded raw configuration are commented out, and those must NOT be part of the configuration that will be uploaded to any PX2. See Keys that Cannot Be Uploaded (on page 582).

Both configuration download and upload operations require the Administrator Privileges.

In This Chapter

Downloading Raw Configuration....645 Uploading Raw Configuration....647

Downloading Raw Configuration

There are three download methods:

• Web browsers: See Download via Web Browsers (on page 645).
- SCP or PSCP command: See Uploading or Downloading Raw Configuration Data (on page 578).
- CURL command: See Download via Curl (on page 646).

Download via Web Browsers

There are two scenarios by using web browsers.

URL containing login credentials:

To log in immediately while issuing the download request, type an URL containing the login credentials in the web browser.

http(s)://:@/cgi-bin/raw_config_download.cgi

Parameter Description
	Any user name that has the Administrator Privileges.
	The password of the specified user name.
	Hostname or IP address of the PX2 whose raw configuration you want to download.

■ For example:

https://admin:raritan@192.168.84.114/cgi-bin/raw_config_download.cgi

URL without login credentials contained:

If you would like to log in after issuing the download request, type an URL without login credentials contained in the web browser. The system will then prompt you to enter the login credentials.

http(s):///cgi-bin/raw_config_download.cgi

■ For example:

https://192.168.84.114/cgi-bin/raw_config_download.cgi

Download via Curl

If you have installed curl on your computer, you can download the raw configuration from your PX2 by performing the curl command.

To download raw configuration from PX2 via curl:

1. Type the following curl command in the command line interface.

curl -k https://:@/cgi-bin/raw_config_download.cgi > config.txt

Parameter Description
	Any user name that has the Administrator Privileges.
	The password of the specified user name.
	Hostname or IP address of the PX2 whose raw configuration you want to download.

1. When the download is complete, a line indicates 100 in the first % column.

% Total	% Received % Xferd				Average Speed Dload Upload Time Total			Time Spent	Time Left	Current Speed
100 20184	0	20184	0	0	9511	0	--:--:--	0:00:02	--:--:--	9584

1. Go to the directory where you perform the curl command to find the "config.txt" file.

Tip: In the above curl command, you can replace the filename "config.txt" with any filename you prefer.

Example:

curl -k https://admin:raritan@192.168.84.114/cgi-bin/raw_config_downloadcgi > config.txt

Uploading Raw Configuration

There are two upload methods:

• SCP or PSCP command: See Uploading or Downloading Raw Configuration Data (on page 578).
• CURL command: See Upload via Curl (on page 648).

The uploaded raw configuration file can contain only partial configuration keys that you want to modify. Other settings that are not contained in the uploaded file will remain unchanged.

Authentication-related data or HTTP(S) port may be no longer the same after uploading raw configuration. Therefore, it is suggested to double check what configuration keys will be changed in the raw configuration file that you will upload.

Upload via Curl

If curl is available on your computer, you can upload the raw configuration to PX2 with the curl command.

There are two scenarios with the curl upload methods.

• When there are NO device-specific settings involved, you upload the configuration file only, regardless of the number of PX2 devices to update.
• When there are device-specific settings involved for updating more than one PX2 devices, you must upload two files. including one configuration file and one device list file.

To upload one configuration file only:

1. Type the following curl command in the command line interface.

curl -k -F "config_file=@" https://:@/cgi-bin/raw_config_update.cgi

Parameter Description
	Any user name that has the Administrator Privileges.
	The password of the specified user name.
	Hostname or IP address of the PX2 whose raw configuration you want to upload.
	Filename of the configuration file.▪ For the syntax, see config.txt(on page 614).

1. When the upload is completed successfully, the curl returns the code 0 (zero).

Note: If the upload fails and curl returns other codes, see Curl Upload Return Codes (on page 649).

1. After several seconds, PX2 reboots automatically. Changed settings take effect after the reboot process finishes.

To upload both configuration and device list files:

1. Type the following curl command in the command line interface.

curl -k -F "config_file=@" -F "device_list_file=@" https://:@/cgi-bin/raw_config_update.cgi?match=

Parameter Description
	Refer to the above table for explanation.▪ For device-specific settings in the, refer each device-specific configuration key to a specific column in the.See config.txt(on page 614).
	Filename of the device list file in CSV format.▪ For the content format, see devices.csv(on page 616).
	comprises "serial:" or "mac:" and the number of the column where the serial number or MAC address of each PX2 is in the uploaded CSV file. This is the data based on which each device finds its device-specific settings.For example:▪ If the second column contains each device's serial number, the parameter is then serial:2.▪ If the seventh column contains each device's MAC address, the parameter is then mac:7.

1. PX2 will reboot after Curl shows the return code 0. For details, refer to above steps 2 to 3.

Examples:

- Upload of the configuration file only:

curl -k -F "config_file=@config.txt"

https://admin:raritan@192.168.84.114/cgi-bin/raw_config_download.cgi

- Upload of both configuration and device list files:

curl -k -F "config_file=@config.txt" -F "device_list_file=@devices.csv" https://admin:raritan@192.168.84.114/cgi-bin/raw_config_download.cgi

Curl Upload Return Codes

After performing raw configuration Upload via Curl (on page 648), curl will return a code to indicate the result of the file upload.

Code Description
0 Operation	was successful.
1 An internal error occurred.
2 A parameter error occurred.
3 A raw configuration update operation is already running.
4 The file is too large.
5 Invalid raw configuration file provided.
6 Invalid device list file or match provided.
7 Device list file required but missing.
8 No matching entry in device list found.
9	Macro substitution error.
10	Decrypting value failed.
11 Unknown magic line.
12 Processing magic line failed.

Appendix F Resetting to Factory Defaults

You can use either the reset button or the command line interface (CLI) to reset the PX2.

Important: Exercise caution before resetting the PX2 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.

Alternative:

Another method to reset it to factory defaults is to use the web interface. See Resetting All Settings to Factory Defaults (on page 376).

In This Chapter

Using the Reset Button 651

Using the CLI Command 652

Using the Reset Button

An RS-232 serial connection to a computer is required for using the reset button.

To reset to factory defaults using the reset button:

1. Connect a computer to the PX2. See Connecting the PX2 to a Computer(on page 25).
2. Launch a terminal emulation program such as Kermit or PuTTY, and open a window on the PX2. For information on the serial port configuration, see Step 2 of Initial Network Configuration via CLI (on page 721).
3. Press (a nd release) the Reset button of the PX2 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 PX2 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.

Raton RESET LINE / CB-1/6 UP BOTH SCAND CURRENT (A) VOLTAGE (V) POWER (W) UPLOAD (L) SENSOR FEATURE USB-A SENSOR ETHERNET USB-A COMBULE/INDICM

This diagram shows the location of the reset button on 1U models.

Raritan USB-A USB-B CURRENT (A) VOLTAGE (V) POWER (W) USB LOAD (K) SENSOR LINE / CR / GB RESET A BOTH DOWN

This diagram shows the location of the reset button on 2U models.

OUTLET / LINE / USB CURRENT ○ VOLTAGE ○ POWER ○ USB LOAD ○ SENSOR ○ CONSOLE / MODEM UP NOT RESET DOWN USB-A USB-B

Note: PuTTY 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 PX2 to factory defaults. For information on CLI, see Using the Command Line Interface (on page 400).

To reset to factory defaults after logging in to the CLI:

1. Connect to the PX2. See Logging in to CLI (on page 401) or Connecting the PX2 to a Computer (on page 25).
2. Launch a terminal emulation program such as HyperTerminal, Kermit, or PuTTY, and open a window on the PX2. For information on the serial port configuration, see Step 2 of Initial Network Configuration via CLI (on page 721).
3. Log in to the CLI by typing the user name "admin" and its password.
4. 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.

To reset to factory defaults without logging in to the CLI:

The PX2 provides an easier way to reset the product to factory defaults in the CLI prior to login.

1. Connect to the PX2 and launch a terminal emulation program as described in the above procedure.
2. At the Username prompt in the CLI, type "factorydefaults" and press Enter.
   Username: factorydefaults
3. Type y on a confirmation message to perform the reset.

Appendix G LDAP Configuration Illustration

This section provides an LDAP example for illustrating the configuration procedure using Microsoft Active Directory® (AD). To configure LDAP authentication, four main steps are required:

a. Determine user accounts and roles (groups) intended for the PX2
b. Create user groups for the PX2 on the AD server
c. Configure LDAP authentication on the PX2
d. Configure roles on the PX2

Important: Raritan disables SSL 3.0 and uses TLS due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.

In This Chapter

Step A. Determine User Accounts and Roles 654

Step B. Configure User Groups on the AD Server 655

Step C. Configure LDAP Authentication on the PX2 655

Step D. Configure Roles on the PX2....657

Step A. Determine User Accounts and Roles

Determine the user accounts and roles (groups) that are authenticated for accessing the PX2. In this example, we will create two user roles with different permissions. Each role (group) will consist of two user accounts available on the AD server.

User roles User accounts (members)
	usera PX_User
	pxuser2
	userb PX_Admin
	pxuser

Group permissions:

• The PX_User role will have neither system permissions nor outlet permissions.
• The PX_Admin role will have full system and outlet permissions.

Step B. Configure User Groups on the AD Server

You must create the groups (roles) for the PX2 on the AD server, and then make appropriate users members of these groups.

In this illustration, we assume:

• The groups (roles) for the PX2 are named PX_Admin and PX_User .
• User accounts pxuser, pxuser2, usera and userb already exist on the AD server.

To configure user groups on the AD server:

1. On the AD server, create new groups -- PX_Admin and PX_User.

Note: Refer to the documentation or online help accompanying Microsoft AD for detailed instructions.

1. Add the pxuser2 and usera accounts to the PX_User group.
2. Add the pxuser and useraccounts 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 PX2

You must enable and set up LDAP authentication properly on the PX2 to use external authentication.

In the illustration, we assume:

• The DNS server settings have been configured properly. See Wired Network Settings (on page 207) and Role of a DNS Server (on page 716).
• The AD server's domain name is techadssl.com, and its IP address is 192.168.56.3.
• The AD protocol is NOT encrypted over TLS.
• The AD server uses the default TCP port 389.
• Anonymous bind is used.

To configure LDAP authentication:

1. Choose Device Settings > Security > Authentication.
2. In the LDAP Servers section, click New to add an LDAP/LDAPS server.
3. Provide the PX2 with the information about the AD server.

Field/setting Do this...
IP Address / Hostname	Type the domain name techadssl.com or IP address 192.168.56.3.▪ Without the encryption enabled, you can type either the domain name or IP address in this field, but you must type the fully qualified domain name if the encryption is enabled.
Copy settings from existing LDAP server	Leave the checkbox deselected unless the new LDAP server's settings are similar to any existing LDAP settings.
Type of LDAP Server Select "Microsoft Active Directory."
Security Select "None" since the TLS encryption is not applied in this example.
Port (None/StartTLS)	Ensure the field is set to 389.
Port (TLS), CA Certificate	Skip the two fields since the TLS encryption is not enabled.
Anonymous Bind Select this checkbox because anonymous bind is used.
Bind DN, Bind Password, Confirm Bind Password	Skip the three fields because of anonymous bind.
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.
	4. Click Add Server.The LDAP server is saved.5. In the Authentication Type field, select LDAP.6. Click Save. The LDAP authentication is activated.
	Note: If the PX2 clock and the LDAP server clock are out of sync, the installed TLS certificates, if any, may be considered expired. To ensure proper synchronization, administrators should configure the PX2 and the LDAP server to use the same NTP server(s).

Step D. Configure Roles on the PX2

A role on the PX2 determines the system and outlet permissions. You must create the roles whose names are identical to the user groups created for the PX2 on the AD server or authorization will fail. Therefore, we will create the roles named PX_Userand PX_Admin on the PDU.

In this illustration, we assume:

• Users assigned to the PX_User role can view settings only, but they can neither configure PX2 nor access the outlets.
• Users assigned to the PX_Admin role have the Administrator Privileges so they can both configure PX2 and access the outlets.

To create the PX\_User role with appropriate permissions assigned:

1. Choose User Management > Roles.
2. Click 🖱️ to add a new role.

a. Type PX_User in the Role Name field.

b. Type a description for the PX_User role in the Description field. In this example, we type "View PX settings" to describe the role.

c. In the Privileges list, select Unrestricted View Privileges, which includes all View permissions. The Unrestricted View Privileges permission lets users view all settings without the capability to configure or change them.

Unrestricted View Privileges View Event Settings View Local Event Log View Local User Management View Security Settings View SNMP Settings View Webcam Snapshots and Configuration

d. Click Save.

1. The PX_User role is created.

Role Name ▲ Admin System defined administrator role including all privileges. Operator Predefined operator role. PX_User View PX settings

1. Keep the Roles page open to create the PX_Admin role.

To create the PX_Admin role with full permissions assigned:

1. Click 2+ to add another role.

a. Type PX_Admin in the Role Name field.
b. Type a description for the PX_Admin role in the Description field. In this example, we type "Includes all PX privileges" to describe the role.
c. In the Privileges list, select Administrator Privileges. The Administrator Privileges allows users to configure or change all PX2 settings.

Privileges Select privilege to add to role. Be aware some privileges may require additional arguments. Acknowledge Alarms Administrator Privileges Change Asset Strip Configuration Change Authentication Settings

d. Click Save.

1. The PX_Admin role is created.

Role Name ▲	Description
Admin	System defined administrator role including all privileges.
Operator	Predefined operator role.
PX_Admin	Includes all PX privileges
PX_User	View PX settings

Appendix H Updating the LDAP Schema

In This Chapter

Returning User Group Information....660

Setting the Registry to Permit Write Operations to the Schema ...... 661

Creating a New Attribute....661

Adding Attributes to the Class 662

Updating the Schema Cache 664

Editing rciusergroup Attributes for User Members ....664

Returning User Group Information

Use the information in this section to return User Group information (and assist with authorization) once authentication is successful.

From LDAP/LDAPS

When an LDAP/LDAPS authentication is successful, the PX2 determines the permissions for a given user based on the permissions of the user's role. Your remote LDAP server can provide these user role names by returning an attribute named as follows:

rciusergroup attribute type: string

This may require a schema extension on your LDAP/LDAPS server. Consult your authentication server administrator to enable this attribute. In addition, for Microsoft® Active Directory®, the standard LDAP memberOf is used.

From Microsoft Active Directory

Note: This should be attempted only by an experienced Active Directory® administrator.

Returning user role information from Microsoft's ^® Active Directory for Windows 2000 ^® operating system server requires updating the LDAP/LDAPS schema. See your Microsoft documentation for details.

1. Install the schema plug-in for Active Directory. See Microsoft Active Directory documentation for instructions.

2. Run Active Directory Console and select Active Directory Schema.

Setting the Registry to Permit Write Operations to the Schema

To allow a domain controller to write to the schema, you must set a registry entry that permits schema updates.

To permit write operations to the schema:

1. Right-click the Active Directory ^ Schema root node in the left pane of the window and then click Operations Master. The Change Schema Master dialog appears.

Change Schema Master The schema master manages modifications to the schema. Only one server in the enterprise performs this role. Current schema master (online): rci-gcf4j2nzmzt.mypc.mydomain.com To transfer the schema master role to the targeted domain controller below, click Change. rci-gcf4j2nzmzt.mypc.mydomain.com Change Close

1. Select the "Schema can be modified on this Domain Controller" checkbox. Optional

2. Click OK.

Creating a New Attribute

To create new attributes for the rciusergroup class:

1. Click the + symbol before Active Directory ^® Schema in the left pane of the window.
2. Right-click Attributes in the left pane.
3. Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears.

Create New Attribute Create a New Attribute Object Identification Common Name: iciusergroup LDAP Display Name: iciusergroup Unique X500 Object ID: 1.3.6.1.4.1.13742.50 Description: LDAP attribute Syntax and Range Syntax: Case Insensitive String Minimum: 1 Maximum: 24 Multi-Valued OK Cancel

1. Type rciusergroup in the Common Name field.
2. Type rciusergroup in the LDAP Display Name field.
3. Type 1.3.6.1.4.1.13742.50 in the Unique x5000 Object ID field.
4. Type a meaningful description in the Description field.
5. Click the Syntax drop-down arrow and choose Case Insensitive String from the list.
6. Type 1 in the Minimum field.
7. Type 24 in the Maximum field.
8. Click OK to create the new attribute.

Adding Attributes to the Class

To add attributes to the class:

1. Click Classes in the left pane of the window.
2. Scroll to the user class in the right pane and right-click it.

Console1 - [Console Root\Active Directory Schema [rci-gcf4]2nzmzt.mypc.mydomain.com... File Action View Favorites Window Help Console Root Active Directory Schema Classes Attributes Name Type Status Desci serviceConnectionPoint Structural Active Servi serviceInstance Structural Active Servi simpleSecurityObject Auxiliary Active The s site Structural Active Site siteLink Structural Active Site-l siteLinkBridge Structural Active Site-l sitesContainer Structural Active Sites- storage Structural Active Store subnet Structural Active Subn subnetContainer Structural Active Subn subSchema Structural Active SubS top Abstract Active Top trustedDomain Structural Active Trust typelibrary Structural Active Type User New Window from Here Active User volume Active Volun Refresh Properties Help

1. Choose Properties from the menu. The user Properties dialog appears.
2. Click the Attributes tab to open it.
3. Click Add.
4. Choose rciusergroup from the Select Schema Object list.

Select Schema Object Select a schema object: productCode profilePath providedObjectName proxyAddresses proxyGenerationEnabled proxyLifetime publicKeyPolicy purportedSearch pwdHistoryLength pwdLastSet pwdProperties qualityOfService queryFilter queryPoint queryPolicyBL queryPolicyObject rangeLower rangeUpper routergroup rtusergroup1 rDNAID

1. Click OK in the Select Schema Object dialog.
2. Click OK in the User Properties dialog.

Updating the Schema Cache

To update the schema cache:

1. Right-click Active Directory ^ Schema in the left pane of the window and select Reload the Schema.
2. Minimize the Active Directory Schema MMC (Microsoft ® Management Console) console.

Editing rciusergroup Attributes for User Members

To run the Active Directory® script on a Windows 2003® server, use the script provided by Microsoft® (available on the Windows 2003 server installation CD). These scripts are loaded onto your system with a Microsoft® Windows 2003 installation. ADSI (Active Directory Service Interface) acts as a low-level editor for Active Directory, allowing you to perform common administrative tasks such as adding, deleting, and moving objects with a directory service.

To edit the individual user attributes within the group rciusergroup:

1. From the installation CD, choose Support > Tools.
2. Double-click SUPTOOLS.MSI to install the support tools.
3. Go to the directory where the support tools were installed. Run adsedit.msc. The ADSI Edit window opens.

ADST Editor File Action View Window Help ADST Editor Domain [[e-mail] Configuration [[e-mail] Scheme [[e-mail]] Name Class Distinguished Name Domain [[e-mail]... domainDNS Configuration [rc-gc4@2nmat... configuration Scheme [[e-mail]... dMD

1. Open the Domain.
2. In the left pane of the window, select the CN=Users folder.

ADST Edit Domain [rd-gd4]2nemot.mypc.m; DC=mypc,DC=mydomain,DC CN=Buthin CN=Computers CN=Domain Controllers CN=ForeignSecurityPrinc1 CN=LostAndFound CN=NTDS Quotas CN=Program Data CN=System CN=Users Configuration [rc-gd4]2nemot.m; Scheme [rc-gd4]2nemot.mypc.m; Name Class Distinguished Name CN=Administrator User CN=Administrator,ON=Users,DC=mypc,DC=mydomain,DC CN=Cert Publishers/group CN=Cert Publishers,ON=Users,DC=mypc,DC=mydomain CN=OnsAdmins/group CN=OnsAdmins,ON=Users,DC=mypc,DC=mydomain,DC CN=OneUpdateProxy/group CN=OneUpdateProxy,ON=Users,DC=mypc,DC=mydomain CN=Domain Admins/group CN=Domain Admins,ON=Users,DC=mypc,DC=mydomain CN=Domain Computers/group CN=Domain Computers,ON=Users,DC=mypc,DC=mydom CN=Domain Controllers/group CN=Domain Controllers,ON=Users,DC=mypc,DC=mydom CN=Domain Guests/group CN=Domain Guests,ON=Users,DC=mypc,DC=mydomain CN=Domain Users/group CN=Domain Users,CN=Users,DC=mypc,DC=mydomain,I CN=Enterprise Admins/group CN=Enterprise Admins,ON=Users,DC=mypc,DC=mydom CN=Group Policy Creator Dom...group CN=Group Policy Creator Owners,CN=Users,DC=mypc,I CN=Guest(userServicesGroup/group CN=Guest,CN=Users,DC=mypc,DC=mydomain,DC=com CN=lvbrgt(userServicesGroup,CN=lvbrgt,CN=lvbrgt,ON=Livbrgt,DC=mypc,DC=mydomain,DC=com CN=RAS and IAS Servers/group CN=RAS and IAS Servers,CN=Users,DC=mypc,DC=mypc CN=Schema Admins/group CN=Schema Admins,CN=Users,DC=mypc,DC=mydomain CN=SUPPORT_388945a0 User CN=SUPPORT_388945a0,CN=Users,DC=mypc,DC=mypc, CN=TelnerClients group CN=TelnerClients,CN=Users,DC=mypc,DC=mydomain,C

1. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties.

2. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list.

CN=Administrator Properties Attribute Editor | Security | ✓ Show mandatory attributes ✓ Show optional attributes ☐ Show only attributes that have values Attributes: Attribute Syntax Value proxyAddresses Unicode String pwdLastSet Large Integer/... 128299285248088608 queryPolicyBL Distinguished ... rciusergroup Case Insensiti... registeredAddress Octet String replPropertyMetaData Octet String 0x01 0x00 0x00 0x00 0x0 replUpToDateVector Octet String repsFrom Octet String repsTo Octet String revision(Integer rid(Integer roomNumber Unicode String sAMAccountName Unicode String Administrator Edit OK Cancel Apply

1. Click Edit. The String Attribute Editor dialog appears.
2. Type the user role (created in the PX2) in the Edit Attribute field. Click OK.

String Attribute Editor Attribute: rciusergroup Value: Admin Clear OK Cancel

Appendix I RADIUS Configuration Illustration

This section provides illustrations for configuring RADIUS authentication. One illustration is based on the Microsoft® Network Policy Server (NPS), and the other is based on a FreeRADIUS server.

The following steps are required for any RADIUS authentication:

1. Configure RADIUS authentication on the PX2. See Adding Radius Servers (on page 252).
2. Configure roles on the PX2. See Creating Roles (on page 199).

3. Configure PX2 user credentials and roles on your RADIUS server.

4. To configure using standard attributes, see Standard Attributes (on page 667).

5. To c onfigure using vendor-specific attributes, see Vendor-Specific Attributes (on page 685).

Note that we assume that the NPS is running on a Windows 2008 system in the NPS illustrations.

In This Chapter

Standard Attributes....667

Vendor-Specific Attributes....685

AD-Related Configuration....697

Standard Attributes

The RADIUS standard attribute "Filter-ID" is used to convey the group membership, that is, roles.

• If a user has multiple roles, configure multiple standard attributes for this user.
• The syntax of a standard attribute is: Raritan:G{role-name}

For configuration on NPS, see NPS Standard Attribute Illustration (on page 667).

For configuration on FreeRADIUS, see FreeRADIUS Standard Attribute Illustration (on page 684).

NPS Standard Attribute Illustration

To configure Windows 2008 NPS with the standard attribute, you must:

a. Add your PX2 to NPS. See Step A: Add Your PX2 as a RADIUS Client (on page 668).

b. On the NPS, configure Connection Request Policies and the standard attribute. See Step B: Configure Connection Policies and Standard Attributes (on page 671).

Some configuration associated with Microsoft Active Directory (AD) is also required for RADIUS authentication. See AD-Related Configuration (on page 697).

Step A: Add Your PX2 as a RADIUS Client

The RADIUS implementation on a PX2 follows the standard RADIUS Internet Engineering Task Force (IETF) specification so you must select "RADIUS Standard" as its vendor name when configuring the NPS server.

Presumptions in the illustration:

• IP address of your PX2 = 192.168.56.29

• RADIUS authentication port specified for PX2: 1812

• RADIUS accounting port specified for PX2: 1813

To add your PX2 to the RADIUS NPS:

1. Choose Start > Administrative Tools > Network Policy Server. The Network Policy Server console window opens.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers RADIUS Clients Remote RADIUS Server Groups Policies Connection Request Policies Network Policies Health Policies Network Access Protection Accounting Getting Started Network Policy Server (NPS) allows you to create and enforce organization-wide network authentication, and connection request authorization. Standard Configuration Select a configuration scenario from the list and then click the link below to open the scenario RADIUS server for Dial-Up or VPN Connections RADIUS server for Dial-Up or VPN Connections When you configure NPS as a RADIUS server for Dial-Up or VPN connections, you create net authorize connections from Dial-Up or VPN network access servers (also called RADIUS client) Configure VPN or Dial-Up Learn more Advanced Configuration

1. Right-click NPS (Local), and select Properties.

Network Policy Server File Action View Help Import Configuration Export Configuration Start NPS Service Stop NPS Service Register server in Active Directory Properties View Help

Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX2. In this example, they are 1812 and 1813. Then close this dialog.

Network Policy Server (Local) Properties General Ports Enter the RADIUS authentication and accounting port numbers. Authentication: 1812,1645 Authentication default ports 1812,1645 Accounting: 1813,1646 Accounting default ports 1813,1646

1. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers RADIUS Client Remote R Policies Network Acce Accounting New RADIUS Client Export List View Refresh Help

1. Do the following to add your PX2 to NPS:

a. Verify the "Enable this RADIUS client" checkbox is selected.
b. Type a name for identifying your PX2 in the "Friendly name" field.
c. Type 192.168.56.29 in the "Address (IP or DNS)" field.
d. Select RADIUS Standard in the "Vendor name" field.
e. Select the Manual radio button.

f. Type the shared secret in the "Shared secret" and "Confirm shared secret" fields. The shared secret must be the same as the one specified on your PX2.

New RADIUS Client Enable this RADIUS client Name and Address Friendly name: RaritanDominion Address (IP or DNS): 192.168.56.29 Verify... Vendor Specify RADIUS Standard for most RADIUS clients, or select the RADIUS client vendor from the list. Vendor name: RADIUS Standard Shared Secret To manually type a shared secret, click Manual. To automatically generate a shared secret, click Generate. You must configure the RADIUS client with the same shared secret entered here. Shared secrets are case-sensitive. ● Manual ○ Generate Shared secret: ************ Confirm shared secret: ************ Additional Options □ Access-Request messages must contain the Message-Authenticator attribute □ RADIUS client is NAP-capable OK Cancel

1. Click OK.

Step B: Configure Connection Policies and Standard Attributes

You need to configure the following for connection request policies:

• IP address or host name of the PX2
- Connection request forwarding method
- Authentication method(s)
• Standard RADIUS attributes

Presumptions in the illustration:

• IP address of your PX2 = 192.168.56.29
- LocalNPS server is used
• RADIUS protocol selected on your PX2 = CHAP
• Existing role of your PX2 = Admin

Illustration:

1. Open the NPS console, and expand the Policies folder.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers RADIUS Clients Remote RADIUS Server Groups Policies Connection Request Policies Network Policies Health Policies Network Access Protection Accounting Getting Started Network Policy Server (NPS) allows you to create and enforce organization-wide network authentication, and connection request authorization. Standard Configuration Select a configuration scenario from the list and then click the link below to open the scenario RADIUS server for Dial-Up or VPN Connections RADIUS server for Dial-Up or VPN Connections When you configure NPS as a RADIUS server for Dial-Up or VPN connections, you create net authorize connections from Dial-Up or VPN network access servers (also called RADIUS client Configure VPN or Dial-Up Learn more Advanced Configuration

1. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers RADIUS Clients Remote RADIUS Server Groups Policies Connection Request Policies Network Policies Health Policies Network Access Protection Accounting New Export List View Refresh Help

1. Type a descriptive name for identifying this policy in the "Policy name" field.

- You can leave the "Type of network access server" field to the default -- Unspecified.

New Connection Request Policy Specify Connection Request Policy Nam You can specify a name for your connection request policy and I applied. Policy name: RaritanDominionPolicy Network connection method Select the type of network access server that sends the connection request to NPS. type or Vendor specific. Type of network access server: Unspecified Vendor specific: 10

1. Click Next to show the "Specify Conditions" screen. Click Add.

New Connection Request Policy Specify Conditions Specify the conditions that determine whether this connection request policy is evaluated for a connection request. A minimum of one condition is required. Conditions: Condition Value Condition description: Add... Edit... Remove Previous Next Finish Cancel

1. The "Select condition" dialog appears. Click Add.

Select condition Select a condition, and then click Add. Called Station ID The Called Station ID condition specifies a character string that is the telephone number of the network access server (NAS). You can use pattern matching syntax to specify area codes. NAS Identifier The NAS Identifier condition specifies a character string that is the name of the network access server (NAS). You can use pattern matching syntax to specify NAS names. NAS IPv4 Address The NAS IP Address condition specifies a character string that is the IP address of the NAS. You can use pattern matching syntax to specify IP networks. NAS IPv6 Address The NAS IPv6 Address condition specifies a character string that is the IPv6 address of the NAS. You can use pattern matching syntax to specify IPv6 networks. NAS Port Type The NAS Port Type condition specifies the type of media used by the access client, such as analog phone lines, ISDN, tunnels or virtual private networks, IEEE 802.11 wireless, and Ethernet switches. Add... Cancel

1. The NAS IPv4 Address dialog appears. Type the PX2 IP address -- 192.168.56.29, and click OK.

NAS IPv4 Address Specify the IPv4 address of the network access server sending the access request message. You can use pattern matching syntax. 192.168.56.29 OK Cancel

1. Click Next in the New Connection Request Policy dialog.

New Connection Request Policy Specify Conditions Specify the conditions that determine whether t A minimum of one condition is required. Conditions: Condition Value NAS IPv4 Address 192.168.56.29

1. Select "Authenticate requests on this server" because a local NPS server is used in this example. Then click Next.

Note: Connection Request Forwarding options must match your environment.

New Connection Request Policy Specify Connection Request Forwarding The connection request can be authenticated by the local server or it can be forwarded to RADIUS servers in a remote RADIUS server group. If the policy conditions match the connection request, these settings are applied. Settings: Forwarding Connection Request Specify whether connection requests are processed locally, are forwarded to remote RADIUS servers for authentication, or are accepted without authentication. ● Authenticate requests on this server ○ Forward requests to the following remote RADIUS server group for authentication: {not configured} ○ Accept users without validating credentials Previous Next Finish Cancel

1. When the system prompts you to select the authentication method, select the following two options:

2. Override network policy authentication settings

3. CHAP -- the PX2 uses "CHAP" in this example

Note: If your PX2 uses PAP, then select "PAP."

New Connection Request Policy

Specify Authentication Methods

Configure one or more authentication methods required authentication, you must configure an EAP type. If you d Protected EAP.

√ Override network policy authentication settings

These authentication settings are used rather than the constraints and auth connections with NAP, you must configure PEAP authentication here.

EAP types are negotiated between NPS and the client in the order in which

EAP Types:

Add...

Edit

Remove

Less secure authentication methods:

☐ Microsoft Encrypted Authentication version 2 (MS-CHAP-v2)

User can change password after it has expired

Microsoft Encrypted Authentication (MS-CHAP)

User can change password after it has expired

☑ Encrypted authentication (CHAP)

Unencrypted authentication (PAP, SPAP)

□ Allow clients to connect without negotiating an authentication method.

1. Select Standard to the left of the dialog and then click Add.

New Connection Request Policy Configure Settings NPS applies settings to the connection request if all of the connection request policy conditions for the policy are matched. Configure the settings for this network policy. If conditions match the connection request and the policy grants access, settings are applied. Settings: Specify a Realm Name Attribute RADIUS Attributes Standard Vendor Specific To send additional attributes to RADIUS clients, select a RADIUS standard attribute, and then click Edit. If you do not configure an attribute, it is not sent to RADIUS clients. See your RADIUS client documentation for required attributes. Attributes: Name Value Add Edit Remove Previous Next Finish Cancel

1. Select Filter-Id from the list of attributes and click Add.

Add Standard RADIUS Attribute To add an attribute to the settings, select the attribute, and then click Add. To add a custom or predefined Vendor Specific attribute, close this dialog and select Vendor Specific, and then click Add. Access type: All Attributes: Name Acct-Interim-Interval Callback-Id Callback-Number Class Filter-Id Framed-AppleTalk-Link FramedAppleTalk-Networks Description: Specifies the name of filter list for the user requesting authentication. Add... Close

1. In the Attribute Information dialog, click Add.

Attribute Information Attribute name: Filter-Id Attribute number: 11 Attribute format: OctetString Attribute values: Vendor Value Add... Edit... Remove Move Up Move Down OK Cancel

1. Select String, type Raritan:G{Admin} in the text box, and then click OK.

Admin inside the curved brackets {} is the existing role on the PX2. It is recommended to use the Admin role to test this configuration. The role name is case sensitive.

Attribute Information Attribute name: Filter-Id Attribute number: 11 Attribute format: OctetString Enter the attribute value in: ● String ○ Hexadecimal Raritan:G{Admin} OK Cancel

1. The new attribute is added. Click OK.

Appendix I: RADIUS Configuration Illustration

Attribute Information Attribute name: Filter-Id Attribute number: 11 Attribute format: Octet String Attribute values: Vendor Value RADIUS Standard Raritan:G{Admin} Add... Edit... Remove Move Up Move Down OK Cancel

1. Click Next to continue.

New Connection Request Policy Configure Settings NPS applies settings to the connection request if all of the connect matched. Configure the settings for this network policy. If conditions match the connection request and the policy grants access, settings are a Settings: Specify a Realm Name Attribute RADIUS Attributes Standard Vendor Specific To send additional attributes to RADIUS clien then click Edit. If you do not configure an attr your RADIUS client documentation for require Attributes: Name Value Filter-Id Raritan:G(Admin)

1. A summary showing connection request policy settings is displayed. Click Finish to close the dialog.

New Connection Request Policy Completing Connection Request Policy Wizard You have successfully created the following connection request policy: KXII Policy Policy conditions: Condition Value NAS IPv4 Address 192.168.56.29 Policy settings: Condition Value Authentication Provider Local Computer Override Authentication Enabled Authentication Method Encryption authentication (CHAP) Filter-Id Raritan:G(Admin) To close this wizard, click Finish. Previous Next Finish Cancel

FreeRADIUS Standard Attribute Illustration

With standard attributes, NO dictionary files are required. You simply add all user data, including user names, passwords, and roles, in the following FreeRADIUS path.

/etc/raddb/users

Presumptions in the illustration:

• User name = steve
  • Steve's password = test123
  • Steve's roles = Admin and SystemTester

To create a user profile for "steve" in FreeRADIUS:

1. Go to this location: /etc/raddb/users.
2. Add the data of the user "steve" by typing the following. Note that the values after the equal sign (=) must be enclosed in double quotes (").

steve Cleartext-Password := "test123"
Filter-ID = "Raritan:G{Admin}",
Filter-ID = "Raritan:G{SystemTester}" 

Vendor-Specific Attributes

You must specify the following properties when using a RADIUS vendor-specific attribute (VSA).

• Vendor code = 13742
• Vendor-assigned attribute number = 26
• Attribute format = String

The syntax of the vendor-specific attribute for specifying one or multiple roles is:

Raritan:G{role-name1 role-name2 role-name3}

For configuration on NPS, see NPS VSA Illustration (on page 685).

For configuration on FreeRADIUS, see FreeRADIUS VSA Illustration (on page 696).

NPS VSA Illustration

To configure Windows 2008 NPS with the vendor-specific attribute, you must:

a. Add your PX2 to NPS. See Step A: Add Your PX2 as a RADIUS Client (on page 668).
b. On the NPS, configure connection request policies and the vendor-specific attribute. See Step B: Configure Connection Policies and Vendor-Specific Attributes (on page 688).

Some configuration associated with Microsoft Active Directory (AD) is also required for RADIUS authentication. See AD-Related Configuration (on page 697).

Step A: Add Your PX2 as a RADIUS Client

The RADIUS implementation on a PX2 follows the standard RADIUS Internet Engineering Task Force (IETF) specification so you must select "RADIUS Standard" as its vendor name when configuring the NPS server.

Presumptions in the illustration:

• IP address of your PX2 = 192.168.56.29
• RADIUS authentication port specified for PX2: 1812
• RADIUS accounting port specified for PX2: 1813

To add your PX2 to the RADIUS NPS:

1. Choose Start > Administrative Tools > Network Policy Server. The Network Policy Server console window opens.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers RADIUS Clients Remote RADIUS Server Groups Policies Connection Request Policies Network Policies Health Policies Network Access Protection Accounting Getting Started Network Policy Server (NPS) allows you to create and enforce organization-wide network authentication, and connection request authorization. Standard Configuration Select a configuration scenario from the list and then click the link below to open the scenario RADIUS server for Dial-Up or VPN Connections RADIUS server for Dial-Up or VPN Connections When you configure NPS as a RADIUS server for Dial-Up or VPN connections, you create net authorize connections from Dial-Up or VPN network access servers (also called RADIUS client Configure VPN or Dial-Up Learn more Advanced Configuration

1. Right-click NPS (Local), and select Properties.

Network Policy Server File Action View Help Import Configuration Export Configuration Start NPS Service Stop NPS Service Register server in Active Directory Properties View Help

Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX2. In this example, they are 1812 and 1813. Then close this dialog.

Network Policy Server (Local) Properties General Ports Enter the RADIUS authentication and accounting port numbers. Authentication: 1812,1645 Authentication default ports 1812,1645 Accounting: 1813,1646 Accounting default ports 1813,1646

1. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers RADIUS Client Remote R Policies Network Acce Accounting New RADIUS Client Export List View Refresh Help

1. Do the following to add your PX2 to NPS:

a. Verify the "Enable this RADIUS client" checkbox is selected.
b. Type a name for identifying your PX2 in the "Friendly name" field.
c. Type 192.168.56.29 in the "Address (IP or DNS)" field.
d. Select RADIUS Standard in the "Vendor name" field.

e. Select the Manual radio button.
f. Type the shared secret in the "Shared secret" and "Confirm shared secret" fields. The shared secret must be the same as the one specified on your PX2.

New RADIUS Client Enable this RADIUS client Name and Address Friendly name: RaritanDominion Address (IP or DNS): 192.168.56.29 Verify... Vendor Specify RADIUS Standard for most RADIUS clients, or select the RADIUS client vendor from the list. Vendor name: RADIUS Standard Shared Secret To manually type a shared secret, click Manual. To automatically generate a shared secret, click Generate. You must configure the RADIUS client with the same shared secret entered here. Shared secrets are case-sensitive. Manual Generate Shared secret: ************ Confirm shared secret: ************ Additional Options Access-Request messages must contain the Message-Authenticator attribute RADIUS client is NAP-capable OK Cancel

1. Click OK.

Step B: Configure Connection Policies and Vendor-Specific Attributes

You need to configure the following for connection request policies:

• IP address or host name of the PX2
- Connection request forwarding method
- Authentication method(s)
• Standard RADIUS attributes

Presumptions in the illustration:

• IP address of your PX2 = 192.168.56.29
- LocalNPS server is used
• RADIUS protocol selected on your PX2 = CHAP
- Existing roles of your PX2 = Admin, User and SystemTester

Illustration:

1. Open the NPS console, and expand the Policies folder.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers RADIUS Clients Remote RADIUS Server Groups Policies Connection Request Policies Network Policies Health Policies Network Access Protection Accounting Getting Started Network Policy Server (NPS) allows you to create and enforce organization-wide network authentication, and connection request authorization. Standard Configuration Select a configuration scenario from the list and then click the link below to open the scenario RADIUS server for Dial-Up or VPN Connections RADIUS server for Dial-Up or VPN Connections When you configure NPS as a RADIUS server for Dial-Up or VPN connections, you create net authorize connections from Dial-Up or VPN network access servers (also called RADIUS client) Configure VPN or Dial-Up Learn more Advanced Configuration

1. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers RADIUS Clients Remote RADIUS Server Groups Policies Connection Request Policies Network Policies Health Policies Network Access Protection Accounting New Export List View Refresh Help

1. Type a descriptive name for identifying this policy in the "Policy name" field.

- You can leave the "Type of network access server" field to the default -- Unspecified.

New Connection Request Policy Specify Connection Request Policy Nam You can specify a name for your connection request policy and I applied. Policy name: RaritanDominionPolicy Network connection method Select the type of network access server that sends the connection request to NPS. type or Vendor specific. Type of network access server: Unspecified Vendor specific: 10

1. Click Next to show the "Specify Conditions" screen. Click Add.

New Connection Request Policy Specify Conditions Specify the conditions that determine whether this connection request policy is evaluated for a connection request. A minimum of one condition is required. Conditions: Condition Value Condition description: Add... Edit... Remove Previous Next Finish Cancel

1. The "Select condition" dialog appears. Click Add.

Select condition Select a condition, and then click Add. Called Station ID The Called Station ID condition specifies a character string that is the telephone number of the network access server (NAS). You can use pattern matching syntax to specify area codes. NAS Identifier The NAS Identifier condition specifies a character string that is the name of the network access server (NAS). You can use pattern matching syntax to specify NAS names. NAS IPv4 Address The NAS IP Address condition specifies a character string that is the IP address of the NAS. You can use pattern matching syntax to specify IP networks. NAS IPv6 Address The NAS IPv6 Address condition specifies a character string that is the IPv6 address of the NAS. You can use pattern matching syntax to specify IPv6 networks. NAS Port Type The NAS Port Type condition specifies the type of media used by the access client, such as analog phone lines, ISDN, tunnels or virtual private networks, IEEE 802.11 wireless, and Ethernet switches. Add... Cancel

1. The NAS IPv4 Address dialog appears. Type the PX2 IP address -- 192.168.56.29, and click OK.

NAS IPv4 Address Specify the IPv4 address of the network access server sending the access request message. You can use pattern matching syntax. 192.168.56.29 OK Cancel

1. Click Next in the New Connection Request Policy dialog.

New Connection Request Policy Specify Conditions Specify the conditions that determine whether t A minimum of one condition is required. Conditions: Condition Value NAS IPv4 Address 192.168.56.29

1. Select "Authenticate requests on this server" because a local NPS server is used in this example. Then click Next.

Note: Connection Request Forwarding options must match your environment.

New Connection Request Policy Specify Connection Request Forwarding The connection request can be authenticated by the local server or it can be forwarded to RADIUS servers in a remote RADIUS server group. If the policy conditions match the connection request, these settings are applied. Settings: Forwarding Connection Request Specify whether connection requests are processed locally, are forwarded to remote RADIUS servers for authentication, or are accepted without authentication. ● Authenticate requests on this server ○ Forward requests to the following remote RADIUS server group for authentication: {not configured} ○ Accept users without validating credentials Previous Next Finish Cancel

1. When the system prompts you to select the authentication method, select the following two options:

2. Override network policy authentication settings

3. CHAP -- the PX2 uses "CHAP" in this example

Note: If your PX2 uses PAP, then select "PAP."

New Connection Request Policy

Specify Authentication Methods

Configure one or more authentication methods required authentication, you must configure an EAP type. If you d Protected EAP.

√ Override network policy authentication settings

These authentication settings are used rather than the constraints and auth connections with NAP, you must configure PEAP authentication here.

EAP types are negotiated between NPS and the client in the order in which

EAP Types:

Add...

Edit

Remove

Less secure authentication methods:

☐ Microsoft Encrypted Authentication version 2 (MS-CHAP-v2)

User can change password after it has expired

Microsoft Encrypted Authentication (MS-CHAP)

User can change password after it has expired

☑ Encrypted authentication (CHAP)

Unencrypted authentication (PAP, SPAP)

□ Allow clients to connect without negotiating an authentication method.

1. Select Vendor Specific to the left of the dialog, and click Add. The Add Vendor Specific Attribute dialog appears.
2. Select Custom in the Vendor field, and click Add. The Attribute Information dialog appears.
3. Click Add, and the Vendor-Specific Attribute Information dialog appears.
4. Click "Enter Vendor Code" and type 13742.
5. Select "Yes, it conforms" to indicate that the custom attribute conforms to the RADIUS Request For Comment (RFC).
6. Click Configure Attribute, and then:

a. Type 26 in the "Vendor-assigned attribute number" field.
b. Select String in the "Attribute format" field.
c. Type Raritan:G{Admin User SystemTester} in the "Attribute value" field. In this example, three roles 'Admin,' 'User' and 'SystemTester' are specified inside the curved brackets {}.

Note that multiple roles are separated with a space.

Network Policy Server File Action View Help NPS (Local) RADIUS Clients and Servers Policies Connection Request Policy Network Policies Health Policies Network Access Protection Accounting Connection request VPN or 802.1X, you Policy Name DPX2-VendorSpecific DPX2-VendorSpecific Pro Overview Conditions Si Configure the settings for I if conditions and constraint Settings: Required Authenical Methods Authentication Met Forwarding Connecti Request Authentication Accounting Specify a Realm Nam Attribute RADIUS Attributes Standard Vendor Specific Attribute Information Attribute name: Vendor-Specific Attribute number: 26 Attribute format: OctetString Attribute values: Vendor Value Add... Vendor Code: 13742 Rantan G(Admin) Vendor-Specific At- Configure VSA (RFC Compliant) Attribute name: Vendor Specific Vendor-assigned attribute number: 26 Specify network acces Select from list: String Enter Vendor Code Attribute value: Rantan G(Admin User SystemTester) Specify whether the a vendor specific attribu Yes, It conforms No, It does not convoam. OK Cancel Configure Attribute... OK Cancel nded to remote RADIUS servers. attribute, and clients. See

1. Click OK.

FreeRADIUS VSA Illustration

A vendor-specific dictionary file is required for the vendor-specific-attribute configuration on FreeRADIUS. Therefore, there are two major configuration steps.

a. Use a dictionary to define the Raritan vendor-specific attribute
b. Add all user data, including user names, passwords, and roles

Presumptions in the illustration:

• Raritan attribute = Raritan-User-Roles
- User name = steve
• Steve's password = test123
• Steve's roles = Admin, User and SystemTester

Step A -- define the vendor-specific attribute in FreeRADIUS:

1. Go to this location: /etc/raddb/dictionary.
2. Type the following in the Raritan dictionary file.

VENDOR Raritan 13742
BEGIN-VENDOR Raritan
ATTRIBUTE Raritan-User-Roles 26 string
END-VENDOR Raritan 

Step B -- create a user profile for "steve" in FreeRADIUS:

1. Go to this location: /etc/raddb/users.
2. Add the data of the user "steve" by typing the following. Note that the values after the equal sign (=) must be enclosed in double quotes (").

steve Cleartext-Password := "test123"
Raritan-PDU-User-Roles = "Raritan:G{Admin User SystemTester}" 

AD-Related Configuration

When RADIUS authentication is intended, make sure you also configure the following settings related to Microsoft Active Directory (AD):

• Register the NPS server in AD
• Configure remote access permission for users in AD
  The NPS server is registered in AD only when NPS is configured for the FIRST time and user accounts are created in AD.

If CHAP authentication is used, you must enable the following feature for user accounts created in AD:

- Store password using reversible encryption

Important: Reset the user password if the password is set before you enable the "Store password using reversible encryption" feature.

To register NPS:

1. Open the NPS console.
2. Right-click NPS (Local) and select "Register server in Active Directory."

Network Policy Server File Action View Help NPS (Local) Import Configuration Export Configuration Start NPS Service Stop NPS Service Register server in Active Directory Properties View Help

1. Click OK, and then OK again.

Network Policy Server To enable NPS to authenticate users in the Active Directory, the computers running NPS must be authorized to read users' dial-in properties from the domain. Do you wish to authorize this computer to read users' dial-in properties from the dc08.com domain? OK Cancel

Network Policy Server This computer is now authorized to read users' dial-in properties from domain dc08.com. To authorize this computer to read users' dial-in properties from other domains, you must register this computer to be a member of the RAS/NPS Servers Group in that domain.

To grant PX2 users remote access permission:

1. Open Active Directory Users and Computers.
2. Open the properties dialog of the user whom you want to grant the access permission.
3. Click the Dial-in tab and select the "Allow access" checkbox.

Remote control Terminal Services Profile COM+ General | Address | Account | Profile | Telephones | Organization Member Of | Dial-in | Environment | Sessions Network Access Permission Allow access Deny access Control access through NPS Network Policy Verify Caller-ID: Callback Options No Callback Set by Caller (Routing and Remote Access Service only) Always Callback to: Assign Static IP Addresses Define IP addresses to enable for this Dial-in connection. Static IP Addresses ... Apply Static Routes Define routes to enable for this Dial-in connection. Static Routes ... OK Cancel Apply Help

To enable reversible encryption for CHAP authentication:

1. Open Active Directory Users and Computers.
2. Open the properties dialog of the user that you want to configure.
3. Click the Account tab and select the "Store password using reversible encryption" checkbox.

Member Of Dial-in Environment Sessions Remote control Terminal Services Profile COM+ General | Address | Account | Profile | Telephones | Organization User logon name: User logon name (pre-Windows 2000): DC08\ Administrator Logon Hours... Log On To... Unlock account Account options: User must change password at next logon User cannot change password Password never expires Store password using reversible encryption Account expires Never End of: Saturday , May 23, 2009 OK Cancel Apply Help

Appendix J Additional PX2 Information

In This Chapter

MAC Address 701

Reserving IP Addresses in DHCP Servers 701

Sensor Threshold Settings....705

Default Voltage and Current Thresholds.... 711

Altitude Correction Factors....713

Unbalanced Current Calculation 714

Data for BTU Calculation....715

Ways to Probe Existing User Profiles 715

Raritan Training Website....716

Role of a DNS Server....716

Cascading Troubleshooting....716

Installing the USB-to-Serial Driver (Optional)....719

Initial Network Configuration via CLI....721

Device-Specific Settings....726

TLS Certificate Chain....726

Browsing through the Online Help 733

MAC Address

A label is affixed to the product, showing both the serial number and MAC address.

If necessary, you can find its IP address through the MAC address by using commonly-used network tools. Contact your LAN administrator for assistance.

Reserving IP Addresses in DHCP Servers

The PX2 uses its serial number as the client identifier in the DHCP request. Therefore, to successfully reserve an IP address for the PX2 in a DHCP server, use the PX2 device's serial number as the unique ID instead of the MAC address.

Since all network interfaces of the PX2 can be simultaneously enabled and configured with diverse static IP addresses, the client identifier of each network interface is different. The main difference is the absence/presence of a suffix, which is the interface name added to the end of the serial number. The table below lists the client identifiers of all network interfaces.

Interface Client Identifier
ETHERNET	serial number
WIRELESS serial number plus the uppercase suffix "-WIRELESS"
BRIDGE	serial number

You can reserve the IP addresses of more than one interfaces in the DHCP server if preferred. Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.

Important: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of ETHERNET and WIRELESS interfaces do NOT function.

Reserving IP in Windows

To reserve the IP address of any network interface in the Windows DHCP server, you must convert that interface's client identifier into hexadecimal ASCII codes.

For each interface's client identifier, see Reserving IP Addresses in DHCP Servers (on page 701).

In the following illustration, it is assumed that the PX2 serial number is PEG1A00003.

Windows IP address reservation illustration:

1. Convert the client identifier of the desired network interface into ASCII codes (hexadecimal).

Interface Client identifier conversion
ETHERNET PEG1A00003 = 50 45 47 31 41 30 30 30 30 33
WIRELESS	PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45 53 53▪ The suffix comprising the dash symbol and the word "WIRELESS" is also converted.
BRIDGE PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

1. In your DHCP server, bring up the New Reservation dialog, and separate the converted ASCII codes with spaces.

For example, to reserve the IP address of the ETHERNET interface, enter the following data in the dialog.

Field Data entered
IP address The IP address you want to reserve.
MAC address The following ASCII codes.
	50 45 47 31 41 30 30 30 30 33
Other fields Configure as needed.

New Reservation Provide information for a reserved client. Reservation name: Test System IP address: 192.168.3.5 MAC address: 50 45 47 31 41 30 30 30 30 33 Description: Supported types Both DHCP only BOOTP only Add Close

Reserving IP in Linux

There are two methods to reserve the IP address of any network interface in the standard Linux DHCP server (ISC DHCP server):

• Convert an interface's client identifier into hexadecimalASCII codes.
• Use an interface's original client identifier without converting it into ASCII codes.

For each interface's client identifier, see Reserving IP Addresses in DHCP Servers (on page 701).

In the following illustrations, it is assumed that the PX2 serial number is PEG1A00003, and the IP address you want to reserve is 192.168.20.1.

▶ Illustration with ASCII code conversion:

1. Convert the client identifier of the desired network interface into ASCII codes (hexadecimal).

Interface Client identifier conversion
ETHERNET PEG1A00003 = 50 45 47 31 41 30 30 30 30 33
WIRELESS	PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45 53 53The suffix comprising the dash symbol and the word "WIRELESS" is also converted.
BRIDGE PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

1. Separate the converted ASCII codes with a colon, and a prefix "00:" must be added to the beginning of the converted codes.

For example, the converted client identifier of the ETHERNET interface looks like the following:

00:50:45:47:31:41:30:30:30:30:33

1. Now enter the converted client identifier with the following syntax.

host mypx {
option dhcp-client-identifier = 00:50:45:47:31:41:30:30:30:33;
fixed-address 192.168.20.1;
} 

▶ Illustration without ASCII code conversion:

1. Use the original client identifier of the desired network interface. DO NOT convert them into ASCII codes.
2. A prefix "\000" must be added to the beginning of the client identifier.
   For example, the client identifier of the ETHERNET interface looks like the following:
   \000PEG1A00003
3. Now enter the original client identifier with the following syntax. The client identifier is enclosed in quotation marks.

host mypx {
option dhcp-client-identifier = "\000PEG1A00003";
fixed-address 192.168.20.1;
} 

Sensor Threshold Settings

This section explains the thresholds settings for a numeric sensor.

Lower Critical ✓ 0 Lower Warning ✓ 0 Upper Warning ✓ 0 Upper Critical ✓ 0 Deassertion Hysteresis 0 Assertion Timeout 0 Samples Cancel ✓ Save

Thresholds and Sensor States

A numeric sensor has four thresholds: Lower Critical, Lower Warning, Upper Warning and Upper Critical.

The threshold settings determine how many sensor states are available for a certain sensor and the range of each sensor state. The diagram below shows how each threshold relates to each state.

above upper critical Upper Critical

Appendix J: Additional PX2 Information

above upper warning Upper Warning normal Lower Warning below lower warning Lower Critical below lower critical

Available sensor states:

The more thresholds are enabled for a sensor, the more sensor states are available for it. The "normal" state is always available regardless of whether any threshold is enabled.

For example:

• When a sensor only has the Upper Critical threshold enabled, it has two sensor states: normal and above upper critical.
• When a sensor has both the Upper Critical and Upper Warning thresholds enabled, it has three sensor states: normal, above upper warning, and above upper critical.

States of "above upper warning" and "below lower warning" are warning states to call for your attention.

States of "above upper critical" and "below lower critical" are critical states that require you to immediately handle.

Range of each available sensor state:

The value of each enabled threshold determines the reading range of each available sensor state. For details, see Yellow- or Red-Highlighted Sensors (on page 163).

"To Assert" and Assertion Timeout

If multiple sensor states are available for a specific sensor, the PX2 asserts a state for it whenever a bad state change occurs.

To assert a state:

To assert a state is to announce a new, "worse" state.

Below are bad state changes that cause the PX2 to assert.

graph TD
    A["above upper critical"] --> B["above upper warning"]
    B --> C["normal"]
    C --> D["below lower warning"]
    D --> E["below lower critical"]

1. above upper warning --> above upper critical
2. normal --> above upper warning
3. normal --> below lower warning
4. below lower warning --> below lower critical

▶ Assertion Timeout:

Lower Critical ✓ 0 Lower Warning ✓ 0 Upper Warning ✓ 0 Upper Critical ✓ 0 Deassertion Hysteresis 0 Assertion Timeout 0 Samples Cancel ✓ Save

In the threshold settings, the Assertion Timeout field postpones the "assertion" action. It determines how long a sensor must remain in the "worse" new state before the PX2 triggers the "assertion" action. If that sensor changes its state again within the specified wait time, the PX2 does NOT assert the worse state.

To disable the assertion timeout, set it to 0 (zero).

Note: For most sensors, the measurement unit in the "Assertion Timeout" field is sample. Sensors are measured every second, so the timing of a sample is equal to a second. Raritan's BCM2 is an exception to this, with a sample of 3 seconds.

How "Assertion Timeout" is helpful:

If you have created an event rule that instructs the PX2 to send notifications for assertion events, setting the "Assertion Timeout" is helpful for eliminating a number of notifications that you may receive in case the sensor's readings fluctuate around a certain threshold.

Assertion Timeout Example for Temperature Sensors

Assumption:

Upper Warning threshold is enabled.
Upper Warning = 25 (degrees Celsius)
Assertion Timeout = 5 samples (that is, 5 seconds) 

When a temperature sensor's reading exceeds 25 degrees Celsius, moving from the "normal" range to the "above upper warning" range, the PX2 does NOT immediately announce this warning state. Instead it waits for 5 seconds, and then does either of the following:

• If the temperature remains above 25 degrees Celsius in the "above upper warning" range for 5 seconds, the PX2 performs the "assertion" action to announce the "above upper warning" state.
• If the temperature drops below 25 degrees Celsius within 5 seconds, the PX2 does NOT perform the "assertion" action.

"To De-assert" and Deassertion Hysteresis

After the PX2 asserts a worse state for a sensor, it may de-assert that state later on if the readings improve.

To de-assert a state:

To de-assert a state is to announce the end of the previously-asserted worse state.

Below are good state changes that cause the PX2 to de-assert the previous state.

graph TD
    A["above upper critical"] --> B["1"]
    B --> C["above upper warning"]
    C --> D["2"]
    D --> E["normal"]
    E --> F["3"]
    F --> G["below lower warning"]
    G --> H["4"]
    H --> I["below lower critical"]

1. above upper critical --> above upper warning
2. above upper warning --> normal
3. below lower warning --> normal
4. below lower critical --> below lower warning

Deassertion Hysteresis:

Lower Critical 0 Lower Warning 0 Upper Warning 0 Upper Critical 0 Deassertion Hysteresis 0 Assertion Timeout 0 Samples Cancel Save

In the threshold settings, the Deassertion Hysteresis field determines a new level to trigger the "deassertion" action.

This function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system when the temperature exceeds a pre-determined level. "Deassertion Hysteresis" instructs the PX2 to de-assert the worse state for a sensor only when that sensor's reading reaches the pre-determined "deassertion" level.

For upper thresholds, this "deassertion" level is a decrease against each threshold. For lower thresholds, this level is an increase to each threshold. The absolute value of the decrease/increase is exactly the hysteresis value.

For example, if Deassertion Hysteresis = 2, then the deassertion level of each threshold is either "+2" or "-2" as illustrated below.

Threshold value Deassertion value
Upper Critical = 33 Deassertion level = 31	• 33 - 2 = 31
Upper Warning = 25 Deassertion level = 23	• 25 - 2 = 23
Lower Critical = 10 Deassertion level = 12	• 10 + 2 = 12
Lower Warning = 18 Deassertion level = 20	• 18 + 2 = 20

To use each threshold as the "deassertion" level instead of determining a new level, set the Deassertion Hysteresis to 0 (zero).

Note: The difference between Upper Warning and Lower Warning must be at least "two times" of the deassertion value.

How "Deassertion Hysteresis" is helpful:

If you have created an event rule that instructs the PX2 to send notifications for deassertion events, setting the "Deassertion Hysteresis" is helpful for eliminating a number of notifications that you may receive in case a sensor's readings fluctuate around a certain threshold.

Deassertion Hysteresis Example for Temperature Sensors

Assumption:

Upper Warning threshold is enabled.
Upper Warning = 20 (degrees Celsius)
Deassertion Hysteresis = 3 (degrees Celsius)
"Deassertion" level = 20-3 = 17 (degrees Celsius) 

When the PX2 detects that a temperature sensor's reading drops below 20 degrees Celsius, moving from the "above upper warning" range to the "normal" range, either of the following may occur:

• If the temperature falls between 20 and 17 degrees Celsius, the PX2 does NOT perform the "deassertion" action.
• If the temperature drops to 17 degrees Celsius or lower, the PX2 performs the "deassertion" action to announce the end of the "above upper warning" state.

Default Voltage and Current Thresholds

The following are factory-default voltage and current thresholds applied to a Raritan power product. There are no default values set for lower current thresholds because lower thresholds are not useful.

Availability of diverse thresholds depends on the capability of the model you purchased.

▶ Single-phase inlets or outlets:

- RMS voltage:

Threshold Default value
Lower critical -6% of minimum rating
Lower warning -3% of minimum rating
Upper warning +3% of maximum rating
Upper critical +6% of maximum rating
Hysteresis	2V

- RMS current:

Threshold Default value
Upper warning 65% of rating
Upper critical 80% of rating
Hysteresis	1A

Multi-phase inlets or outlets:

• Line-Line RMS voltage:

Threshold Default value
Lower critical -6% of minimum rating
Lower warning -3% of minimum rating
Upper warning +3% of maximum rating
Upper critical +6% of maximum rating
Hysteresis	2V

- Line RMS current:

Threshold Default value
Upper warning 65% of rating
Upper critical 80% of rating
Hysteresis	1A

- Unbalanced current:

Threshold Default value
Upper critical 10% -- disabled by default
Upper warning 5% -- disabled by default
Hysteresis	2%

Overcurrent protectors which aims to protect the PDU's outlets:
- OCP RMS current:

Threshold Default value
Upper critical 80% of OCP rating
Upper warning 65% of OCP rating
Hysteresis	1A

▶ Total residual current:

Threshold Default value
Upper critical 30mA
Hysteresis	15mA

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

Unbalanced Current Calculation

Unbalanced current information is available on 3-phase models only. This section explains how PX2 calculates the unbalanced current percentage.

▶ Calculation:

1. Calculate the average current of all 3 lines.

Average current = (L1+L2+L3) / 3 

1. Calculate each line's current unbalance by having each line current subtracted and divided with the average current.

L1 current unbalance = (L1 - average current) / average current
L2 current unbalance = (L2 - average current) / average current
L3 current unbalance = (L3 - average current) / average current 

1. Determine the maximum absolute value among three lines' current unbalance values.

Maximum (|L1 current unbalance|, |L2 current unbalance|, |L3 current unbalance|) 

1. Convert the maximum value to a percentage.

Unbalanced load percent = 100 * maximum current unbalance 

Example:

• Each line's current:

L1 = 5.5 amps 

L2 = 5.2 amps 

L3 = 4.0 amps 

• Average current: (5.5+5.2+4.0)/3=4.9 amps
• L1 current unbalance: (5.5 - 4.9) / 4.9 = 0.1224
• L2 current unbalance: (5.2 - 4.9) / 4.9 = 0.0612
• L3 current unbalance: (4.0 - 4.9) / 4.9 = -0.1837
- Maximum current unbalance: Maximum (|0.1224|, |0.0612|, |-0.1837|) = 0.1837
- Current unbalance converted to a percentage: 100 * (0.1837) = 18%

Data for BTU Calculation

The heat generated by the PX2 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)
1000 series 5
2000 series 20
3000 series 24
4000 series 24
5000 series 24

Ways to Probe Existing User Profiles

This section indicates available ways to query existing user accounts on the PX2.

• With SNMP v3 activated, you get the "user unknown" error when the user name used to authenticate does not exist.
• Any user with the permission to view event rules can query all local existing users via JSON RPC.
• Any user with the permission to view the event log may get information about existing users from the log entries.
• Any authenticated users can query currently-existing connection sessions, including Webcam-Live-Preview sessions, which show a list of associated user names.

Raritan Training Website

Raritan offers free training materials for various Raritan products on the Raritan training website http://www.raritantraining.com. The Raritan products introduced on this website include intelligent PDU, KVM, EMX, BCM, and CommandCenter Secure Gateway (CC-SG).

To get access to these training materials or courses, you need to apply for a username and password through the Raritan training website. After you are verified, you can access the Raritan training website anytime.

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

Therefore, DNS server settings are important for external authentication. With appropriate DNS settings, the PX2 can resolve the external authentication server's name to an IP address for establishing a connection. If the SSL/TLS 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 external authentication, see Setting Up External Authentication (on page 247).

Cascading Troubleshooting

Any accessibility problem occurred on one of the devices in the cascading chain may result in failure to access all downstream slave devices that are connected to it.

Possible Root Causes

The following lists the network accessibility issues and possible root causes.

You can always troubleshoot the software settings by connecting the PX2 to a computer if network access to that PX2 fails. See Connecting the PX2 to a Computer(on page 25).

Symptom Probable cause
Failure to access the master device	·Anything below is lost or loose on the master device: ·Network connection ·Power supply ·Anything below is disabled on the master device: ·The Ethernet or wireless interface ·IPv4 or IPv6 settings ·In the Port Forwarding mode, related settings are incorrectly configured on the master device. ·The master device's role is incorrectly set to 'Slave'. ·The interface where the network is connected is incorrectly set as the downstream interface. ·For the wireless networking, one of the following issues occurs: ·The USB wireless LAN adapter attached to the master device is not the Raritan USB WIFI LAN adapter. SeeUSB Wireless LAN Adapters(on page 18). ·The wireless s LAN configuration is not supported. SeeSupported Wireless LAN Configuration(on page 19). ·The installed CA certificate chain contains any certificate that has expired or is not valid yet.
Failure to access a slave device	One of the following issues occurs on the master device:Network connection is lost.Power is lost.The Ethernet or wireless interface is disabled.One of the following issues occurs on the slave device in question or any upstream device (if available):Connection of the cascading cable is loose or lost.No power supply.The cascading mode is set incorrectly.For example, the master device is set to Bridging, but the slave device in question or any upstream device is set to Port Forwarding.In the Bridging mode, IPv4 (or IPv6) settings are disabled on the slave device in question.In the Port Forwarding mode, one of the following issues occurs:The master device's role is incorrectly set to 'Slave'.The master device's downstream interface is incorrectly set. For example, you use a USB cable to connect the 1st slave device, but select the Ethernet port as the downstream interface.The role of the slave device in question or any upstream device is set to 'Master' instead of 'Slave'.The port number you added to the IP address is incorrect. SeePort Number Syntax(on page 221).IPv4 (or IPv6) settings are disabled on the master device.The slave device in question or any upstream device is a Raritan product that runs a "pre-3.3.10" firmware version while the rest of the chain runs firmware version 3.3.10 or later.

Tip: To determine which PX2 may be the failure point of network, you may ping each PX2 in the cascading chain, or check the slave-related events in the event log of each PX2. SeeThe Ping Tool (on page 719) and Slave Device Events in the Log (on page 719).

Slave Device Events in the Log

In the Bridging mode, events regarding connection/disconnection of a downstream slave device via USB is NOT logged.

However, in the Port Forwarding mode, whenever the connection or disconnection of a downstream slave device via USB is detected, the PX2 at the USB-A end of the USB cable logs it in the internal log. Note that the PX2 at the USB-B end of the cable does NOT log these events.

There are two slave-related events in the Port Forwarding mode:

Event Description
Slave connected	This log entry is generated when the PX2 detects the presence of a slave device on its USB-A port.
Slave disconnected	This log entry is generated when it detects the disconnection of a slave device from its USB-A port.

The Ping Tool

The PX2 provides a ping tool in the web interface and CLI so you can ping any host or PX2 in your data center.

▶ Ping via the Web Interface:

To log in to the web interface, see Login (on page 86).

The Ping tool is useful for checking whether a host is accessible through the network or Internet.

- Choose Maintenance > Network Diagnostics

▶ Ping via the CLI:

You can access the CLI interface by connecting a computer to the PX2 or using SSH/Telnet. See With SSH or Telnet (on page 402).

1. You must perform the ping command in the diagnostic mode. See Entering Diagnostic Mode (on page 568).

2. Then perform the ping command. See Testing the Network Connectivity (on page 570).

Installing the USB-to-Serial Driver (Optional)

The PX2 can emulate a USB-to-serial converter over a USB connection. A USB-to-serial driver named "Dominion PX2 Serial Console" is required for Microsoft® Windows® operating systems.

Download the Windows driver for USB serial console from the Raritan website's Support page (http://www.raritan.com/support/). The downloaded driver's name is dominion-serial-setup-.exe, where represents the file's version number.

There are two ways to install this driver: automatic and manual installation. Automatic driver installation is highly recommended.

▶ Automatic driver installation in Windows ®:

1. Make sure the PX2 is NOT connected to the computer via a USB cable.
2. Run dominion-serial-setup-.exe on the computer and follow online instructions to install the driver.

Note: If any Windows security warning appears, accept it to continue the installation.

1. Connect the PX2 to the computer via a USB cable. The driver is automatically installed.

▶ Manual driver installation in Windows ®:

1. Make sure the PX2 has been connected to the computer via a USB cable.
2. The computer detects the new device and the "Found New Hardware Wizard" dialog appears.

- If this dialog does not appear, choose Control Panel > System > Hardware > Device Manager, right-click the Dominion PX2 Serial Console, and choose Update Driver.

1. Select the option of driver installation from a specific location, and then specify the location where both dominion-serial.inf and dominion-serial.cat are stored.

Note: If any Windows security warning appears, accept it to continue the installation.

1. Wait until the installation is complete.

Note: If the PX2 enters the disaster recovery mode when the USB serial driver is not installed yet, it may be shown as a 'GPS camera' in the Device Manager on the computer connected to it.

In Linux:

No additional drivers are required, but you must provide the name of the tty device, which can be found in the output of the "dmesg" after connecting the PX2 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

Initial Network Configuration via CLI

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

This section describes the initial network configuration via a serial RS-232 or USB connection. To configure the network settings using the web interface, see Configuring Network Settings (on page 205).

To configure the PX2 device:

1. On the computer connected to the PX2, open a communications program such as HyperTerminal or PuTTY.
2. Select the appropriate COM port, and set the following port settings:

■ Bits per second = 115200 (115.2Kbps)
- Data bits = 8
■ Stop bits = 1
- Parity = None
■ Flow control = None

Tip: For a USB connection, you can determine the COM port by choosing Control Panel > System > Hardware > Device Manager, and locating the "Dominion PX2 Serial Console" under the Ports group.

1. In the communications program, press Enter to send a carriage return to the PX2.
2. The PX2 prompts you to log in. Both user name and password are case sensitive.

a. Username: admin
b. Default password: raritan (or a new password if you have changed it).

1. If prompted to change the default password, change or ignore it.

2. To change it, follow onscreen instructions to type your new password.
   ■ To ignore it, simply press Enter.

3. The # prompt appears.

4. Type config and press Enter.

5. To configure network settings, type appropriate commands and press Enter. Refer to the following commands list. CLI commands are case sensitive.

6. After finishing the network settings, type apply to save changes. To abort, type cancel.

Commands for wired networking:

The variable in the following commands is either ipv4 or ipv6, depending on the type of IP protocol you are configuring. Replace the variable with the word 'ethernet' when you are configuring the wired networking.

- General IP settings:

To set or enable	Use this command
IPv4 or IPv6 protocol	networkinterfaceenabled=true, or false
IPv4 configuration method	network ipv4 interfaceconfigMethod= dhcp (default) or static
IPv6 configuration method	network ipv6 interfaceconfigMethod= automatic (default) or static
Preferred host name (optional)	networkinterfacepreferredHostName= preferred host name
IP address returned by the DNS server	network dns resolverPreference= preferV4 or preferV6

• Static IP configuration:

To set Use this command
Static IPv4 or IPv6 address	networkinterfaceaddress= static IP address, with a syntax similar to the example below.▪ Example: 192.168.7.9/24
Static IPv4 or IPv6 gateway	networkgateway= gateway's IP address
IPv4 or IPv6 primary DNS server	network dns firstServer= DNS server's IP address
IPv4 or IPv6 secondary DNS server	network dns secondServer= DNS server's IP address
IPv4 or IPv6 third DNS server	network dns thirdServer= DNS server's IP address

Commands for wireless networking:
• General wireless settings:

To set or enable	Use this command
Wireless interface	network wireless enabled
	=true, or false
SSID	network wireless SSID
	= SSID string
BSSID	network wireless BSSID
	= AP MAC address or none
802.11n protocol	network wireless enableHT
	=true, or false
Authentication method	network wireless authMethod
	= psk or eap
PSK	network wireless PSK
	= PSK string
EAP outer authentication	network wirelesseapOuterAuthentication
	= PEAP
EAP inner authentication	network wirelesseapInnerAuthentication
	= MSCHAPv2
EAP identity	network wireless eapIdentity
	= 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.

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." If a certificate is installed, configure the following:

Whether to Use this command
Verify the certificate	network wireless enableCertVerification
	=true or false
Accept an expired or not valid certificate	network wireless allowOffTimeRangeCerts
	=true or false
Make the connection successful by ignoring the "incorrect" system time	network wireless allowConnectionWithIncorrectClock
	=true or false

• Wireless IPv4 / IPv6 settings:

Commands for wireless IP settings are identical to those for wired networking. Just replace the variable with the word 'wireless'. The following illustrates a few examples.

To set or enable	Use this command
IPv4 configuration method	network ipv4 interface WIRELES configMethod
	= dhcp (default) or static
IPv6 configuration method	network ipv6 interface WIRELES configMethod
	= automatic (default) or static

▶ To verify network settings:

After exiting the above configuration mode and the # prompt re-appears, type this command to verify all network settings.

• show network

The IP address configured may take seconds to take effect.

Device-Specific Settings

A bulk configuration file will NOT contain any device-specific information like the following list.

For further information, simply open the built-in bulk profile for a detailed list of 'excluded' settings.

• Device name
  • SNMP system name, contact and location
  • Part of network settings (IP address, gateway, netmask and so on)
• Device logs
• Names, states and values of environmental sensors and actuators
• TLS certificate
  • Server monitoring entries
• Asset strip names and rack unit names
• Outlet names and states

TLS Certificate Chain

A TLS server sends out a certificate to any client attempting to connect to it. The receiver determines whether a TLS server can be trusted by verifying that server's certificate, using the certificate (chain) stored on the receiver.

Therefore, to successfully connect to a TLS server, you must upload a valid certificate or (partial) certificate chain to the receiver.

The uploaded certificate (chain) must contain all missing certificates "related to" that TLS server's certificate in some way. Otherwise, the connection made to that TLS server will fail.

• For information on how the uploaded certificate (chain) is related to a TLS server's certificate, see What is a Certificate Chain (on page 726).
• For an example of creating and uploading a TLS certificate to PX2, see Illustration - GMAIL SMTP Certificate Chain (on page 730).

What is a Certificate Chain

If you are familiar with a certificate chain, you can ignore this topic and refer to Illustration - GMAIL SMTP Certificate Chain (on page 730).

A certificate or a chain of certificates is used for trusting a TLS server that you want to connect.

The receiver, such as PX2, can trust a TLS server only after an appropriate certificate (chain) which is "related to" that TLS server's certificate is uploaded to the receiver.

▶ How a certificate chain is generated:

To explain how a TLS server's certificate is "related to" the certificate (chain) that is uploaded to the receiver, we assume that there are three "related" certificates.

• Certificate C. The certificate issued to the TLS server you want to connect.
  'Certificate C' is issued by the certificate authority (CA) entity called 'Issuer B'.
  • Certificate B. The certificate issued to 'Issuer B'.
  'Certificate B' is issued by a CA entity called 'Issuer A', and it is an intermediate certificate.
• Certificate A. The self-signed certificate issued by Issuer A. Issuer A is a root CA.

The above three certificates form a certificate path, which is called the "certificate chain".

graph LR
    A["ROOT"] --> B["B"]
    B --> C["SERVER"]

Each certificate in the chain is the issuer certificate of the certificate that follows it. That is, A is the issuer certificate of B, and B is the issuer certificate of C.

Note: In fact many certificate chains may comprise only the root certificate and a TLS server's certificate and do not have any intermediate certificate(s) like 'Certificate B' involved. Or some chains may contain more than one intermediate certificates.

▶ Certificate (chain) that you must upload to the receiver, such as PX2:

Because the TLS server provides only 'Certificate C', you need to upload a file containing the missing certificates of the chain (that is, 'Certificate A' and 'Certificate B') to the receiver.

C SERVER + B A = C B A ✓

In reality some servers may provide a partial (or even a full) certificate chain instead of a single server certificate. If your server provides a partial certificate chain containing 'Certificate B' and 'Certificate C', then you only need to upload 'Certificate A" to the receiver. If the server has a full certificate chain containing Certificates 'A', 'B', and 'C', then you also need to upload the root certificate 'A".

C B SERVER + A = C B A ✓

Warning: The certificate (chain) uploaded to the receiver must always contain the ROOT certificate even though the TLS server provides the root certificate. When uploading a (partial) chain onto the PX2, it means you trust each certificate in the chain to certify the authenticity of certificates a server sends to PX2. Therefore, at least the root certificate must be authentic, issued by a CA you trust, and downloaded from that CA over a secure channel. Never implicitly trust a root certificate that is sent by the server which you want to connect to. It could have been created by an attacker.

If either certificate 'A' or 'B' is missing in the certificate file uploaded to the receiver, the connection to the wanted TLS server will fail.

C + A = C ? A SERVER

For PX2, if any required certificate is missing, a certificate error message similar to the following is shown on the PX2 web interface.

Select new certificate × Certificate 'C = US, O = GeoTrust Inc., CN = GeoTrust Global CA': unable to get issuer certificate OK

It is NOT recommended to upload the server certificate to the receiver except when it is a self-signed certificate. Using self-signed server certificates is also not recommended and may not even work in all cases.

Order of the chain in the certificate file:

The order of a certificate chain's content in the certificate file uploaded to the receiver must look like the following.

B A

• The top is the final intermediate certificate of the chain "B" if you have to upload a partial chain.
  • The bottom is always the root certificate "A".
• When copying multiple certificates to a single file, make sure you also copy the lines of BEGIN CERTIFICATE and END CERTIFICATE from each certificate.

Illustration - GMAIL SMTP Certificate Chain

If you will apply your company's SMTP service to PX2, ignore this GMAIL illustration topic. Simply contact your IT department to retrieve the appropriate certificate (chain) file and upload it to the PX2.

This section illustrates the upload of a TLS "root" certificate for using the "gmail.com" SMTP service.

Unlike normal TLS websites, where you can easily find its server certificate by using a Web browser, the method to find an SMTP server's certificate is more difficult, which requires appropriate tools and sufficient technical knowledge. For example, you may have to use the openssl command as illustrated below to retrieve the certificate of the GMAIL SMTP server.

Step 1 -- Find the certificate(s) the SMTP server has:

1. Issue the following command in the appropriate command line application.

- In the following example command, we assume the server "smtp.gmail.com" provides the SMTP service. You can change the server name, port number, command or even the tool as needed.

openssl s_client -showcerts -connect smtp.gmail.com:465 

Alternative: To view the certificate chain instead of all certificates, you can remove the "-showcerts" option from the above command.

1. Information that shows the certificates the SMTP server has is displayed.

.
.
.
Certificate chain
0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com
i:/C=US/O=Google Inc/CN=Google Internet Authority G2
----BEGIN CERTIFICATE----
MIIEdjCCA16gAwIBAgIIbzO9vIL2OXcwDQYJKoZIhvcNAQELBQAwSTELMAkGA1UE
.
.
YHKKJH96sSNC+6dLpOOoRritL5z+jn2WFLcQkL2mRoWQi6pYTzPyXB4D
----END CERTIFICATE----
1 s:/C=US/O=Google Inc/CN=Google Internet Authority G2
i:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA 

----BEGIN CERTIFICATE----
MIIEKDCCAxCgAwIBAgIQAQAhJYiw+lmnd+8Fe2Yn3zANBgkqhkiG9w0BAQsFADBC
.
.
MqO5tzHpCvX2HzLc
----END CERTIFICATE----
2 s:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
i:/C=US/O=Equifax/OU=Equifax Secure Certificate Authority
----BEGIN CERTIFICATE----
MIIDfTCCAuagAwIBAgIDErvmMA0GCSqGSIb3DQEBBQUAME4xCzAJBgNVBAYTA1VT
.
.
b8ravHNjkOR/ez4iyz0H7V84dJzjA1BOoa+Y7mHyhD8S
----END CERTIFICATE----
---
Server certificate
subject=/C=US/ST=California/L=Mountain View/O=Google
Inc/CN=smtp.gmail.com
issuer=/C=US/O=Google Inc/CN=Google Internet Authority G2
.
.
. 

1. Onscreen information under the title 'Certificate chain' indicates that there are three issuers and three certificates on this server.

■ Each line beginning with the letter "i" indicates an issuer. They are:
■ Google Internet Authority G2
■ GeoTrust Global CA
■ Equifax Secure Certificate Authority

- Each certificate's content is located between the line of "BEGIN CERTIFICATE" and the line of "END CERTIFICATE".

- The topmost certificate is the server certificate.

1. The section titled "Server certificate" indicates that the issuer (CA) Google Internet Authority G2 issues the server certificate.

2. As the server has the server certificate and two intermediate certificates, we conclude that this server sends a partial certificate chain to the receiver.

3. Check whether the issuer "Equifax Secure Certificate Authority" is the root CA.

- If yes, you only need to upload the root certificate self-signed by Equifax Secure Certificate Authority to PX2.

- If not, you need to find all missing issuer certificates, including the root certificate, and upload them to PX2.

Step 2 -- Find and download the content of missing issuer certificate(s):

1. View the name of the issuer (CA) at the bottom. In this example, this issuer is 'Equifax Secure Certificate Authority'.
2. Use the issuer's name 'Equifax Secure Certificate Authority' to search for its certificate on the Internet, and then download or copy the content from an authentic source, which is usually its official website.

Important: To prevent the downloaded certificate from being modified or manipulated, you must secure the download with TLS via a trusted certificate.

1. As it is found the Equifax Secure Certificate Authority's certificate is self signed by 'Equifax Secure Certificate Authority', which indicates it is the root CA, there are no more missing certificates to search for.

Step 3 -- Upload the missing certificate(s) to PX2:

1. Paste the root certificate's content into a plain text file that will be uploaded to PX2.
2. Content copying must include the lines of "BEGIN CERTIFICATE" and "END CERTIFICATE".
3. Save that file as a .pem, .crt or .cer file. In this example, it is named as "my-root.pem."
4. Upload the file "my-root.pem" to PX2 for using the GMAIL SMTP service.

Note: If your SMTP server requires the upload of a certificate file comprising multiple certificates, make sure the order of these certificates is correct in the file. See What is a Certificate Chain (on page 726).

IMPORTANT NOTE:

If your SMTP server provides a full certificate chain, you should be suspicious whether any attacker fakes the certificate chain and doubt whether the root certificate on that server is authentic. It is STRONGLY recommended to download the root certificate from an authentic source, which is usually the root CA's website, rather than from the server you want to connect.

Browsing through the Online Help

The PX2 Online Help is accessible over the Internet.

To use online help, Active Content must be enabled in your browser. Consult your browser help for information on enabling the feature.

To use the PX2 online help:

1. Click Online Documentation. See Web Interface Overview (on page 90).
2. The online help opens in the default web browser.

3. To view the content of any topic, click the topic in the left pane. Then its content is displayed in the right pane.

4. To select a different topic, do any of the following:

5. To view the next topic, click the Next icon ↓ in the toolbar.
   ■ 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:

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

- 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 , and all sub-topics below that topic disappear.

1. 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 online help to Raritan, click the "Send feedback" icon 🔗.

Appendix J: Additional PX2 Information

1. To print the currently selected topic, click the "Print this page" icon

Appendix K Integration

The PX2 can work with certain Raritan or third-party products to provide diverse power solutions.

In This Chapter

Dominion KX II / III Configuration....735

Dominion KSX II, SX or SX II Configuration 740

Power IQ Configuration 745

dcTrack 745

Dominion KX II / III Configuration

Raritan PX2, PX3 or PX3TS series can be connected to the Raritan's Dominion KX II or KX III device (a digital KVM switch) to provide one more alternative of power management.

Note that this integration requires the following firmware versions:

• Dominion KX II -- 2.4 or later
• Dominion KX III -- ALL versions
• PX2 series -- 2.2 or later
• PX3 series -- 2.5.10 or later
• PX3TS series -- 2.6.1 or later

Dominion KX II or KX III integration requires D2CIM-PWR and straight CAT5 cable.

For more information on KX II / III, refer to:

• KX II or KX III User Guide on the Support page (http://www.raritan.com/support/)
• KX II or KX III Online Help on the Product Online Help page (http://www.raritan.com/support/online-help/)

Note: For documentation conveniences, both Dominion KX II and KX III products are referred to as "KX III" in the following sections.

Configuring Rack PDU Targets

KX III allows you to connect rack PDUs (power strips) to KX III ports.

KX III rack PDU configuration is done from the KX III Port Configuration page.

Note: Raritan recommends no more than eight (8) rack PDUs (power strips) be connected to a KX III at once since performance may be affected.

Connecting a PX PDU

Raritan PX series rack PDUs (power strips) are connected to the Dominion device using the D2CIM-PWR CIM.

To connect the rack PDU:

1. Connect the male RJ-45 of the D2CIM-PWR to the following female RJ-45 connector of the rack PDU.
   ■ PX1 series: RJ-45 "SERIAL" port
2. PX2, PX3 or PX3TS series: RJ-45 "FEATURE" port
3. Connect the female RJ-45 connector of the D2CIM-PWR to any of the available female system port connectors on the KX III using a straight through Cat5 cable.
4. Attach an AC power cord to the target server and an available rack PDU outlet.
5. Connect the rack PDU to an AC power source.
6. Power on the device.

graph TD
    A["Router"] -->|1| B["Switch"]
    B -->|2| C["Server"]
    style A fill:#f9f,stroke:#333
    style B fill:#bbf,stroke:#333
    style C fill:#dfd,stroke:#333

Diagram key

PX rack PDU

B	D2CIM-PWR
C	KX III
1	D2CIM-PWR to rack PDU connection
2	D2CIM-PWR to KX III target device port via Cat5 cable

Naming the Rack PDU (Port Page for Power Strips)

Note: PX rack PDUs (power strips) can be named in the PX as well as in the KX III.

Once a Raritan remote rack PDU is connected to the KX III, 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 Devices

The Port page opens when you click on a port on the Port Configuration page.

If an outlet is connected to the same server that the port is connected to, a power association can be made with the target device.

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)

Make a Power Association

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. On the Port Configuration page, select the target server you are associating the PDU with.
2. Choose the rack PDU from the Power Strip Name drop-down list.
3. For that rack PDU, choose the outlet from the Outlet Name drop-down list.
4. Repeat steps 1 and 2 for all desired power associations.
5. Click OK. A confirmation message is displayed.

Turning Outlets On/Off and Cycling Power

▶ To turn an outlet on:

1. Click the Power menu to access the Powerstrip page.
2. From the Powerstrip drop-down, select the PX rack PDU (power strip) you want to turn on.
3. Click Refresh to view the power controls.
4. Click On next to the outlet you want to power on.
5. Click OK to close the Power On confirmation dialog. The outlet will be turned on and its state will be displayed as 'on'.

To turn an outlet off:

1. Click Off next to the outlet you want to power off.
2. Click OK on the Power Off dialog.
3. Click OK on the Power Off confirmation dialog. The outlet will be turned off and its state will be displayed as 'off'.

To cycle the power of an outlet:

1. Click Cycle next to the outlet you want to cycle. The Power Cycle Port dialog opens.

2. Click OK. The outlet will then cycle (note that this may take a few seconds).

3. Once the cycling is complete the dialog will open. Click OK to close the dialog.

Dominion KSX II, SX or SX II Configuration

Raritan PX2 support the integration with Raritan's serial access products - Dominion KSX II, Dominion SX and Dominion SX II.

Cables used for connecting the PX2 to different Dominion access products are different.

• KSX II - a standard network patch cable (CAT5 or higher)
- SX - a CSCSPCS cable
• SX II - a CSCSPCS cable

Note: To only access the CLI of the PX2 via SX/SX II, treat the PX2 as a serial device by connecting SX/SX II to the PDU's serial port instead of the FEATURE port.

For more information on these Dominion serial access product, refer to:

• KSX II, SX or SX II User Guide on the Support page (http://www.raritan.com/support/)
• KSX II, SX or SX II Online Help on the Product Online Help page (http://www.raritan.com/support/online-help/)

Dominion KSX II

After connecting a Dominion KSX II to the Raritan PDU, you can monitor the PDU and even control its outlets if the PDU is an outlet-switching capable model.

Connecting a Rack PDU

To connect the Raritan PX to the KSX II:

1. Connect one end of a Cat5 cable to the following ports of different Raritan PX.
   ■ PX1 series: RJ-45 "SERIAL" port
2. PX2, PX3 or PX3TS series: RJ-45 "FEATURE" port
3. Connect the other end of the Cat5 cable to either the Power Ctrl. 1 or Power Ctrl. 2 ports on the back of the KSX II.
4. Attach an AC power cord to the target server and an available rack PDU outlet.
5. Connect the rack PDU to an AC power source.
6. Power on the KSX II device.

Important: When using CC-SG, the power ports should be inactive

before attaching rack PDUs that were swapped between the power ports. If this is not done, there is a possibility that the number of power outlets will not be correctly detected, especially after swapping 8 and 20 outlet rack PDU models.

A B C D

Diagram key
A	KSX II	D	PX SERIAL or FEATURE port
B	KSX II Power Ctrl. 1 Port or Power Ctrl. 2 Port	1	Cat5 cable
C	PX

Power Control

The KSX II operation to turn on/off or power cycle a PX is the same as the KX III operation. See Turning Outlets On/Off and Cycling Power (on page 739).

Dominion SX and SX II

By connecting to a Dominion SX or SX II device, you can associate one or more outlets on a PX2 device to specific SX or SX II ports.

Dominion SX II

The way to use Dominion SX II to configure and control a Raritan PDU is similar to using Dominion KX III, but the connection method is different from KX III.

Note: If using a CSCSPCS-1 cable for the connection, it must be "Rev.0C". If using a CSCSPCS-10 cable, it must be "Rev.0D".

Note that the appliances used in the diagram may not match your specific models. However, the connections and ports used are the same across models.

To connect the SX II to the Feature port on the PX:

1. Connect the gray end of the CSCSPCS crossover Cat5 cable into the Feature port on the PX.
2. Connect the yellow end of the CSCSPCS crossover Cat5 cable into a port on the SX II.
3. Power on the PX (if it is not already).
4. You can now add the PX as a managed power strip to the SX II. See Configure Power Strips from the Remote Console or Configure Power Strips Using CLI. in the SX II User Guide or Online Help.

A B

A	PX appliance
B	SX II

Dominion SX

Configuring a PX2 on Dominion SX

1. Choose Setup > Power Strip Configuration.
2. Click Add. The Power Strip Configuration screen appears.

Name: Description: Number of Outlets: 8 Port: OK Cancel

1. Type a name and description in the Name and Description fields.
2. Select the number of outlets from the Number of Outlets drop-down menu.
3. Type the port number in the Port field.
4. Click OK.

Power Control

1. Choose Power Control > Power Strip Power Control. The Outlet Control screen appears.

Outlet Control Outlet State □ Outlet 1 OFF ✓ Outlet 2 OFF □ Outlet 3 OFF □ Outlet 4 ON ✓ Outlet 5 OFF □ Outlet 6 OFF □ Outlet 7 ON □ Outlet 8 OFF ✓ Outlet 9 OFF □ Outlet 10 OFF □ Outlet 11 OFF □ Outlet 12 OFF □ Outlet 13 OFF □ Outlet 14 OFF □ Outlet 15 OFF □ Outlet 16 OFF □ Outlet 17 OFF □ Outlet 18 OFF □ Outlet 19 OFF □ Outlet 20 ON Select All On Off Recycle

1. Check the box of outlet number you wish to control, and click On/Off buttons to power on/off the selected outlet(s).
2. A confirmation message appears, indicating successful operation.

Outlet 19: The power operation has been sent.

The system shall reflect successful operations shortly.

Checking Power Strip Status

1. Choose Power Control > Power Strip Status.

DPX Status:

Power strip: Outlet Breaker Status: 1 True RMS Current: 0.0 Maxium Detected Current: 0.4 True RMS Voltage : 113.0 Internal Temperature : 45.0 Average Power : 0 Apparent Power : 0 Outlets: 20 1. Outlet 1 : Off 2. Outlet 2 : Off 3. Outlet 3 : Off 4. Outlet 4 : On 5. Outlet 5 : Off 6. Outlet 6 : Off 7. Outlet 7 : On 8. Outlet 8 : Off 9. Outlet 9 : Off 10. Outlet 10 : Off 11. Outlet 11 : Off 12. Outlet 12 : Off 13. Outlet 13 : Off 14. Outlet 14 : Off 15. Outlet 15 : Off 16. Outlet 16 : Off

1. A status box appears, displaying details of the controlled PX2, including power state of each outlet on the device.

Power IQ Configuration

Sunbird's Power IQ is a software application that collects and manages the data from different PDUs installed in your server room or data center. With this software, you can:

• Do bulk configuration for multiple PDUs
  • Name outlets on different PDUs
• Switch on/off outlets on outlet-switching capable PDUs

For more information on Power IQ, refer to the Power IQ online help on the Sunbird website: http://support.sunbirddcim.com.

dcTrack

Sunbird's dcTrack® is a product that allows you to manage the data center. The PX2 is categorized as a power item in dcTrack. dcTrack offers an import wizard for conveniently adding the PX2 as well as other IT equipment to dcTrack for management.

You can use dcTrack to:

• Record and manage the data center infrastructure and assets
• Monitor the electrical consumption of the data center
- Track environmental factors in the data center, such as temperature and humidity
- Optimize the data center growth

For more information on dcTrack, refer to the online help accessible from the dcTrack application, or user documentation available on the Sunbird's website: http://support.sunbirddcim.com.

dcTrack Overview

dcTrack ^® is a powerful and intelligent data center management and automation application.

It has been designed by data center and IT professionals to provide broad and deep visibility into the data center. It empowers data center managers to plan for growth and change by optimizing their current operations, assets, and infrastructure.

With dcTrack, you can view everything in the data center from servers, blades, virtual servers and applications to data networks, IP addressing space and cabling. dcTrack also allows you to track real-time power consumption and manage raised floor space and rack elevations.

Use dcTrack to build your floor map data center map directly in the application, or import an existing floor map into the dcTrack. Further, dcTrack allows you to import AutoCAD® 2012 (and earlier) objects to build a data center map.

If you currently maintain data center information in spreadsheet format, that data can be imported into dcTrack using the Import wizard.

Isolate potential problems with end-to-end power and data circuits by visually tracing them. This allows you to identify all intermediate circuit points and locate problems.

By using dcTrack's workflow and change management feature, data center managers are better able to enforce best practices across the enterprise and meet ITIL framework guidelines. You can also opt to skip the Change Control workflow process and work in Request Bypass so requests are processed immediately.

dcTrack ^® can be used as a standalone product or integrated with Power IQ ^® for power and environmental monitoring.

Asset Management Strips and dcTrack

If any asset strips are connected to the PX2, the PX2 can transmit their information to Sunbird's dcTrack. All you have to do is to add the PX2 to dcTrack, and also add each IT item where an asset tag is attached to dcTrack.

Note: For instructions on connecting asset strips, see Connecting Asset Management Strips (on page 53).

If SNMP is enabled, event information can be transmitted to dcTrack. Specifically, Sunbird's Power IQ detects when an asset tag is connected or disconnected from an asset strip. Power IQ then generates a connection or disconnection event. When dcTrack polls Power IQ, the connection/disconnection events are pulled into dcTrack, and displayed in the dcTrack Web Client.

To poll and display asset management events in dcTrack

• The PX2 that the asset strip is connected to must exist in dcTrack. EMX devices are identified as probes in dcTrack; Raritan and Legrand PDUs are identified as sensors.
• Each IT item connected to the asset strip via an asset tag must exist in dcTrack.

You do not need to manually enter the asset tag IDs for IT items that already exist in dcTrack as long as these items are in the Installed status.

Simply, plug the item's asset tag into an asset strip that is connected to the PX2 that exists in dcTrack. dcTrack automatically assigns the asset tag ID to the existing IT item.

Note: If needed, the asset tag number can be overwritten.

For more information on dcTrack as well as how asset strips work with dcTrack, contact Sunbird Professional Services and Support from the http://support.sunbirddcim.com.

Index

1

1U and 2U Port Locations • 81

1U Products • 2

2

2U Products • 2

A

A Note about Enabling Thresholds • 429

A Note about Firmware Upgrade Time • 390

A Note about Infinite Loop • 345

A Note about Untriggered Rules • 346

About the Interface • 431

Action Group • 307, 311

Actuator Configuration Commands • 569, 588

Actuator Control Operations • 611

Actuator Information • 448

Adding a Firewall Rule • 513

Adding a Monitored Device • 589

Adding a Radius Server • 566

Adding a Role-Based Access Control Rule • 526

Adding an LDAP Server • 559, 565

Adding Attributes to the Class • 712

Adding LDAP/LDAPS Servers • 270, 272, 276

Adding Radius Servers • 270, 275, 276, 717

Adding, Removing or Swapping Cascaded Devices • 246

Additional PX2 Information • 753

AD-Related Configuration • 718, 736, 749

Alarm • 307, 309

All Privileges • 546, 552, 556

Altitude Correction Factors • 176, 477, 767

APIPA and Link-Local Addressing • 3, 30, 97, 239, 256

Applicable Models • xvii, xx

Assertion Timeout Example for Temperature Sensors • 761

Asset Management Commands • 595

Asset Management Log • xxi, 350, 356

Asset Management Strips and dcTrack • 803

Asset Management Tag List • xxi, 350, 353

Asset Strip • 195, 197

Asset Strip Automatic Firmware Upgrade • 205

Asset Strip Management • 595

Asset Strip Settings • 461

Associating Outlets with Target Devices • 794

Authentication Commands • 557

Authentication Settings • 458, 559, 563

Automatic Mode • 86, 640

Automatically Completing a Command • 435, 436, 618

Available Actions • xxi, 77, 252, 285, 306, 311, 317, 327, 339, 407, 421

Available Data of the Outlets Overview Page • 132, 135, 140, 141

B

Backup and Restore of Device Settings • 377, 391, 399, 661

Backup and Restore via SCP • 400, 622

Beeper • 95, 122

Before You Begin • 4

Blade Extension Strip Settings • 463

Browsing through the Online Help • 103, 788

Built-in Rules and Rule Configuration • 285, 286, 339

Bulk Configuration • xxi, 31, 377, 391, 399, 621, 661

Bulk Configuration for Outlet Thresholds • 132, 136, 147

Bulk Configuration Methods • xx, 24, 31

Bulk Configuration or Firmware Upgrade via DHCP/TFTP • xxii, 31, 388, 392, 397, 656, 672

Bulk Configuration Restrictions • 391, 393

Bulk Configuration via SCP • xxii, 392, 397, 621, 629

Bulk Configuration/Upgrade Procedure • xxii, 673, 674

Button-Type Locking Outlets • 19

C

Calendar • 281, 283

Index

Canceling the Power-On Process • 610

Cascading All Devices via USB • xx, 35, 82

Cascading Guidelines for Port Forwarding • 34

Cascading Multiple PX2 Devices for Sharing Ethernet Connectivity • 21, 32, 228, 239, 380

Cascading Troubleshooting • 33, 246, 771

Change Load Shedding State • 307, 311

Changing a User's Password • 540

Changing an Outlet's Default State • 532

Changing HTTP(S) Settings • xxi, 224, 248, 249, 257

Changing Measurement Units • 546, 549

Changing Modbus Settings • 225, 248, 255

Changing SSH Settings • 214, 225, 248, 254

Changing Storage Settings • 314, 407, 409, 410, 413, 416

Changing Telnet Settings • 225, 248, 255, 431

Changing the Inlet Name • 537

Changing the LAN Duplex Mode • 490

Changing the LAN Interface Speed • 490

Changing the Modbus Configuration • 504

Changing the Modbus Port • 505

Changing the Outlet Name • 532

Changing the Overcurrent Protector Name • 538

Changing the PDU Name • 472

Changing the Role(s) • 546

Changing the Sensor Description • 572

Changing the Sensor Name • 569

Changing the SSH Configuration • 501

Changing the SSH Port • 501

Changing the Telnet Configuration • 500

Changing the Telnet Port • 501

Changing the UDP Port • 594

Changing Your Own Password • 548

Changing Your Password • 99, 212, 214

Checking Lua Scripts States • 370, 371, 372

Checking Power Strip Status • 800

Checking the Accessibility of NTP Servers • 511

Checking the Branch Circuit Rating • 5

Circuit Breaker Orientation Limitation • 6, 7, 9, 10, 12

Circuit Breakers • 90

Clearing Event Log • 470

Clearing Information • 470

Clearing WLAN Log • 471

Closing a Local Connection • 434

Combining Regular Asset Strips • 62

Command History • 467

Commands for Environmental Sensors • 585

Commands for Inlet Pole Sensors • 581

Commands for Inlet Sensors • 580

Commands for Outlet Group Sensors • xxii, 578

Commands for Outlet Sensors • 576

Commands for Overcurrent Protector Sensors • 583

Common Network Settings • 226, 228

config.txt • xxii, 32, 625, 628, 658, 660, 664, 695, 698, 699

Configuration Files • 656, 658, 673, 695

Configuration or Firmware Upgrade with a USB Drive • 32, 392, 397, 656, 669, 672

Configuring a Multi-Inlet Model • 126, 129

Configuring a PX2 on Dominion SX • 798

Configuring Data Push Settings • xxi, 225, 314, 348

Configuring DNS Parameters • 488

Configuring Environmental Sensors' Default Thresholds • 574

Configuring IPv4 Parameters • 480

Configuring IPv6 Parameters • 484

Configuring Login Settings • 225, 257, 277

Configuring Network Services • 248, 432

Configuring Network Settings • xxi, 3, 22, 36, 224, 226, 234, 775

Configuring NTP Server Settings • 428

Configuring Password Policy • 225, 257, 278

Configuring Rack PDU Targets • 791

Configuring Security Settings • 257

Configuring SMTP Settings • 225, 248, 252, 316, 321

Configuring SNMP Settings • 214, 224, 248, 250, 307, 420

Configuring the Cascading Mode • xxi, 497

Configuring the PX2 • 23

Configuring the PX2 Device and Network • 471

Configuring the Serial Port • 77, 78, 225, 366, 433

Configuring Webcams and Viewing Live Images • 76, 407, 408, 412, 413, 418

Index

Connecting a DPX2 Sensor Package to DX2, DX or DPX3 • 40, 42, 47, 60

Connecting a GSM Modem • 77, 319

Connecting a Logitech Webcam • xx, 76, 406

Connecting a Mobile Device to PX2 • 23, 24, 82

Connecting a PX PDU • 791

Connecting a Rack PDU • 796

Connecting a Schroff LHX/SHX Heat Exchanger • 78, 206

Connecting an Analog Modem • 77, 433

Connecting an External Beeper • 78, 205

Connecting Asset Management Strips • 61, 197, 348, 803

Connecting Blade Extension Strips • 67

Connecting Composite Asset Strips (AMS-Mx-Z) • 70, 74

Connecting External Equipment (Optional) • 38, 82

Connecting Raritan Environmental Sensor Packages • 38, 75, 172

Connecting Regular Asset Strips to PX2 • 64, 71

Connecting the PDU to a Power Source • 20

Connecting the PX2 to a Computer • 3, 23, 30, 239, 701, 702, 771

Connecting the PX2 to Your Network • 21, 23, 226

Connection Port Functions • 81

Connection Ports • 81

Copying an Existing Server's Settings • 559, 563

Creating a CSR • 264, 265, 266

Creating a New Attribute • 711

Creating a Role • 552

Creating a Self-Signed Certificate • 264, 267

Creating a User Profile • 539

Creating an Outlet Group • xx, xxii, 151, 152, 534

Creating Configuration Files via Mass Deployment Utility • 658, 668, 669

Creating IP Access Control Rules • 225, 257, 258, 261

Creating Role Based Access Control Rules • 225, 257, 262, 264

Creating Roles • 99, 212, 216, 219, 717

Creating Users • 96, 99, 212, 213, 217, 220, 223, 254, 270, 420

Curl Upload Return Codes • xxii, 698, 700

Customizing Bulk Configuration Profiles • 391, 394

Customizing the Date and Time • 509

D

Daisy-Chain Limitations of Composite Asset Strips • 71, 72, 73

Dashboard • xx, 104, 108, 167, 309, 402

Dashboard - Alarms • xx, 109, 118, 307, 643

Dashboard - Alerted Sensors • 109, 113, 643

Dashboard - Inlet History • 109, 115, 127

Dashboard - Inlet l1 • xx, 109, 110, 126, 643

Dashboard - OCP • 109, 112

Dashboard Page • 642

Data Encryption in 'config.txt' • 664, 666, 669

Data for BTU Calculation • xxii, 769

Data Push Format • xxi, 348, 350

Date and Time Settings • 445

dcTrack • 801

dcTrack Overview • 802

Deassertion Hysteresis Example for Temperature Sensors • 764

Default Log Messages • xxi, 279, 286, 291, 312, 316

Default Measurement Units • 445

Default Voltage and Current Thresholds • 127, 136, 147, 166, 169, 765

Deleting a Firewall Rule • 516

Deleting a Monitored Device • 590

Deleting a Role • 557

Deleting a Role-Based Access Control Rule • 529

Deleting a User Profile • 548

Deleting an Outlet Group • xx, 161

Derating a Raritan Product • 633

Detailed Information on Outlet Pages • 143, 149

Determining the Authentication Method • 557

Determining the SSH Authentication Method • 502

Determining the Time Setup Method • 507, 509

Index

Device Configuration/Upgrade Procedure • xxii, 656

Device Information • 376, 378, 418

Device Settings • 105, 224

devices.csv • 32, 628, 658, 660, 665, 667, 699

Device-Specific Settings • 391, 780

DHCP IPv4 Configuration in Linux • 673, 691

DHCP IPv4 Configuration in Windows • 673, 674

DHCP IPv6 Configuration in Linux • 673, 693

DHCP IPv6 Configuration in Windows • 673, 684

Diagnostic Commands • 615

Different CLI Modes and Prompts • 432, 433, 434, 436, 470, 471, 472, 511, 605, 607, 611, 615

Dominion KSX II • 795

Dominion KSX II, SX or SX II Configuration • 211, 795

Dominion KX II / III Configuration • 211, 790

Dominion SX • 798

Dominion SX and SX II • 797

Dominion SX II • 797

Download via Curl • xxii, 695, 696

Download via Web Browsers • xxii, 695

Downloading Diagnostic Data via SCP • 624

Downloading Diagnostic Information • 377, 401

Downloading Raw Configuration • xxii, 695

Downloading SNMP MIB • 252, 420, 425

DPX Sensor Packages • xx, 38, 48

DPX2 Sensor Packages • xx, 38, 45

DPX3 Sensor Packages • xx, 38, 43

DX Sensor Packages • xx, 38, 41, 325

DX2 Sensor Packages • xx, 38, 39, 325

E

EAP CA Certificate Example • 493, 495

Editing or Deleting a Rule/Action • 307, 339, 365

Editing or Deleting IP Access Control Rules • 261

Editing or Deleting Ping Monitoring Settings • 363

Editing or Deleting Role Based Access Control Rules • 263

Editing or Deleting Roles • 156, 221

Editing or Deleting Users • 99, 217, 220, 222

Editing rciusergroup Attributes for User Members • 714

Enabling and Configuring SNMP • 341, 342, 347, 420

Enabling or Disabling a User Profile • 542

Enabling or Disabling an Inlet (for Multi-Inlet PDUs) • 537

Enabling or Disabling Data Logging • 476

Enabling or Disabling EnergyWise • 593

Enabling or Disabling Front Panel Outlet Switching • 530

Enabling or Disabling Load Shedding • 606

Enabling or Disabling Modbus • 504

Enabling or Disabling Peripheral Device Auto Management • 478

Enabling or Disabling Service Advertising • 505

Enabling or Disabling SNMP v1/v2c • 502

Enabling or Disabling SNMP v3 • 503

Enabling or Disabling SSH • 501

Enabling or Disabling Strong Passwords • 522

Enabling or Disabling Telnet • 500

Enabling or Disabling the LAN Interface • 489

Enabling or Disabling the Read-Only Mode • 505

Enabling or Disabling the Restricted Service Agreement • 517

Enabling Service Advertising • 225, 249, 256, 505

Enabling the Restricted Service Agreement • 97, 225, 257, 279

EnergyWise Configuration Commands • 593

EnergyWise Settings • 461

Entering Configuration Mode • 434, 471, 495, 540, 548

Entering Diagnostic Mode • 434, 615, 773

Environmental Sensor Configuration Commands • 569

Environmental Sensor Default Thresholds • 456

Environmental Sensor Information • 446

Environmental Sensor Package Information • 447

Index

Environmental Sensor Threshold Information • 455

Equipment Setup Worksheet • 5,652

Ethernet Interface Settings • 227, 229

Event Log • 464

Event Rules and Actions • 78, 95, 118, 122, 126, 136, 166, 188, 209, 225, 250, 252, 285, 309, 348, 357, 370, 647

Example • 509, 519, 540, 548, 603, 606

Ping Monitoring and SNMP Notifications • 357, 363

Example - Actuator Naming • 589

Example - Creating a Role • 557

Example - Default Upper Thresholds for Temperature • 576

Example - Inlet Naming • 538

Example - OCP Naming • 538

Example - Outlet Naming • 533

Example - Ping Command • 618

Example - Power Cycling Specific Outlets • 610

Example - Server Settings Changed • 592

Example - Setting Up EnergyWise • 595

Example - Turning On a Specific Actuator • 612

Example 1 • 345

Example 1 - Asset Strip LED Colors for Disconnected Tags • 601

Example 1 - Basic Security Information • 468

Example 1 - Combination of IP, Subnet Mask and Gateway Parameters • 604

Example 1 - Creating a User Profile • 551

Example 1 - Environmental Sensor Naming • 573

Example 1 - IPv4 Firewall Control Configuration • 530

Example 1 - Networking Mode • 506

Example 1 - PDU Naming • 479

Example 1 - Time Setup Method • 510

Example 1 - Upper Critical Threshold for a Temperature Sensor • 587

Example 2 • 346

Example 2 - Adding an IPv4 Firewall Rule • 530

Example 2 - Combination of Upper Critical and Upper Warning Settings • 604

Example 2 - Enabling Both IP Protocols • 506

Example 2 - In-Depth Security Information • 469

Example 2 - Modifying a User's Roles • 551

Example 2 - Outlet Sequence • 479

Example 2 - Primary NTP Server • 510

Example 2 - Rack Unit Naming • 602

Example 2 - Sensor Threshold Selection • 573

Example 2 - Warning Thresholds for Inlet Sensors • 587

Example 3 • 346

Example 3 - Basic PDU Information • 469

Example 3 - Combination of SSID and PSK Parameters • 605

Example 3 - Default Measurement Units • 551

Example 3 - Outlet Sequence Delay • 479

Example 3 - Upper Thresholds for Overcurrent Protector Sensors • 587

Example 3 - User Blocking • 531

Example 3 - Wireless Authentication Method • 506

Example 4 - Adding an IPv4 Role-based Access Control Rule • 531

Example 4 - Combination of Upper Critical, Upper Warning and Lower Warning Settings • 605

Example 4 - In-Depth PDU Information • 470

Example 4 - Non-Critical Outlets • 480

Example 4 - Static IPv4 Configuration • 506

Examples • 468, 479, 506, 510, 530, 550, 573, 586, 601

Existing Roles • 460

Existing User Profiles • 445, 459

External Beeper • 195, 205, 307, 311

F

Feature Port • 105, 194, 197, 205, 207, 211

Feature RJ-45 Port Pinouts • 650

Filling Out the Equipment Setup Worksheet • 5

Finding the Sensor's Serial Number • 174, 183

Firewall Control • 511

Firmware Update via SCP • 388, 620

Firmware Upgrade via USB • xxii, 388, 657, 670

Flexible Cord Installation Instructions • 631

Index

Flexible Cord Selection • 632

Forcing a Password Change • 542

Forcing the Device Detection Mode • 603

FreeRADIUS Standard Attribute Illustration • 717, 735

FreeRADIUS VSA Illustration • 736, 748

From LDAP/LDAPS • 710

From Microsoft Active Directory • 710

Front Panel Settings • 88, 225, 365

Full Disaster Recovery • 390

Fuse • 92

Fuse Replacement on 1U Models • 93

Fuse Replacement on Zero U Models • 92

fwupdate.cfg • xxii, 656, 658, 659, 664, 667, 670, 673

G

Gathering LDAP/Radius Information • 270, 271

Guidelines for PX2 with Two Sensor Ports • xx, 40, 42, 44, 47, 60

H

Hardware Issue Detection • xxi, 110, 377, 402, 467

How Long a Link Remains Accessible • 411, 413

How the Automatic Management Function Works • 176, 186, 478

|

Identifying Cascaded Devices • 379, 380

Identifying Snapshots Folders on Remote Servers • 410, 417, 418

Identifying the Sensor Port • 39

Identifying the Sensor Position and Channel • 174, 184

Idle Timeout • 521

If Switchable Outlet Groups are Limited • xx, 156

Illustration - GMAIL SMTP Certificate Chain • 781, 785

Illustrations of Adding LDAP Servers • 561, 562

Individual OCP Pages • 167

Individual Outlet Pages • 120, 121, 123, 132, 134, 139, 143, 150, 648

Individual Sensor/Actuator Pages • 113, 173, 176, 177, 178, 188, 194

Initial Installation and Configuration • 20

Initial Network Configuration via CLI • 4, 23, 31, 239, 701, 702, 775

Initialization Delay Use Cases • 120, 123

Inlet • 104, 110, 111, 121, 126, 129

Inlet Configuration Commands • 536

Inlet Information • 443

Inlet Pole Sensor Threshold Information • 453

Inlet Sensor Threshold Information • 452

Inlets/Outlets Page • 647

In-Line Monitor Unused Channels • 634

In-Line Monitors • 630

In-Line Monitor's LED Display • 640

In-Line Monitor's Web Interface • 641

Inrush Current and Inrush Guard Delay • 120, 124

Installing a CA-Signed Certificate • 264, 266

Installing Cable Retention Clips on Outlets (Optional) • 15

Installing Cable Retention Clips on the Inlet (Optional) • 14

Installing or Downloading Existing Certificate and Key • 264, 268

Installing the USB-to-Serial Driver (Optional) • 31,774

Integration • 790

Interface Names • 235, 238

Internal Beeper • 307, 312

Internal Beeper State • 119, 122

Introduction • 1

Introduction to Asset Tags • 64

Introduction to PDU Components • 79

IP Configuration • 437, 438

IPv4-Only or IPv6-Only Configuration • 437, 438

K

Keys that Cannot Be Uploaded • xxii, 625, 629, 695

Index

L

Layout • 427

LDAP Configuration Illustration • 270, 704

LDAP Settings • 558

LED Display • 83, 640

LEDs for Measurement Units • 85, 87, 640

Load Shedding Configuration Commands • 605

Load Shedding Mode • 133, 135, 138, 140, 145, 311, 476

Load Shedding Settings • 460

Locking Outlets and Cords • 16, 17

Log an Event Message • 308, 312

Log Rows • xxi, 350, 352

Logging in to CLI • 431, 669, 702

Logging out of CLI • 619

Login • xx, 23, 30, 97, 239, 773

Login Limitation • 520

Login, Logout and Password Change • 96

Logout • 100

Lowercase Character Requirement • 523

Lua Scripts • 225, 323, 367

M

MAC Address • 23,753

Maintenance • xxi, 105, 376

Make a Power Association • 794

Managed vs Unmanaged Sensors/Actuators • 172, 179, 181

Managing an Outlet Group • xxii, 534

Managing External Authentication Settings • 270, 274, 276

Managing Firewall Rules • 513

Managing One Sensor or Actuator • 174, 175, 186

Managing Role-Based Access Control Rules • 526

Manual Mode • 87, 640

Manually Starting or Stopping a Script • 368, 369, 370

Maximum Ambient Operating Temperature • 4,649

Maximum Password History • 524

Maximum Password Length • 522

Menu • xx, 102, 104, 119, 126, 131, 151, 165, 172, 195, 197, 205, 206, 211, 212, 224, 369, 372, 373, 376, 408, 411

Minimum Password Length • 522

Miscellaneous • xxi, 78, 195, 196, 206, 225, 315, 324, 374, 379, 425

Mixing Diverse Sensor Types • xx, 54, 55, 61

Modifying a Firewall Rule • 515

Modifying a Monitored Device's Settings • 590

Modifying a Role • 555

Modifying a Role-Based Access Control Rule • 527

Modifying a User Profile • 539

Modifying a User's Personal Data • 541

Modifying an Existing LDAP Server • 563

Modifying an Existing Radius Server • 567

Modifying an Outlet Group • xx, 152, 159

Modifying Firewall Control Parameters • 511

Modifying or Deleting a Script • 368, 373

Modifying or Removing Bulk Profiles • 397

Modifying Role-Based Access Control Parameters • 525

Modifying SNMPv3 Settings • 543

Monitoring Server Accessibility • xxi, 225, 313, 357, 363

Mounting 1U or 2U Models • 13

Mounting Zero U Models Using Button Mount • 9

Mounting Zero U Models Using Claw-Foot Brackets • 10

Mounting Zero U Models Using L-Brackets • 7

Mounting Zero U Models Using Two Rear Buttons • 12

Multi-Command Syntax • 513, 520, 521, 522, 526, 534, 539, 541, 543, 546, 549, 574, 576, 578, 580, 581, 583, 585, 588, 590, 604

N

Naming a Rack Unit • 599

Naming an Asset Strip • 595

Naming the Rack PDU (Port Page for Power Strips) • 792

Network Configuration • 436

Network Configuration Commands • 480

Network Diagnostics • 377, 400

Network Interface Settings • 439

Index

Network Service Settings • 440

Network Troubleshooting • 400, 615

NPS Standard Attribute Illustration • 717

NPS VSA Illustration • 736

Numeric Character Requirement • 523

0

OCPs • 105, 113, 165, 167, 169

Off and Lock Icons for Outlets • xx, 141, 142

Optional Parameters • 559, 560

Options for Outlet State on Startup • 120, 123, 144

Outlet Configuration Commands • 532

Outlet Group Configuration Commands • xxi, 533

Outlet Group Information • xxi, 442

Outlet Group Power Control • xx, 152, 153

Outlet Group Threshold Information • xxi, 451

Outlet Groups • xx, 105, 121, 151, 157, 159, 313, 451, 579

Outlet Information • 441

Outlet Pole Sensor Threshold Information • 450

Outlet Sensor Threshold Information • 449

Outlet Switching • 88, 144, 365

Outlets • 79, 104, 131, 135, 140, 141, 143, 325

Overcurrent Protector Configuration Commands • 538

Overcurrent Protector Information • 444

Overcurrent Protector Sensor Threshold Information • 454

Overview • 630

Overview of the Cascading Modes • 239, 241

P

Package Contents • 1, 4

Panel Components • 79

Password Aging • 520

Password Aging Interval • 521

PDU • xx, 95, 102, 104, 119, 123, 125, 127, 134, 146, 150, 158, 172, 186, 190, 193, 475

PDU Configuration • 122, 441

PDU Configuration Commands • 472

Performing Bulk Configuration • xxi, 391, 396

Peripherals • xxi, 39, 41, 105, 172, 177, 179, 181, 183, 186, 188, 189, 193, 194, 344

Placeholders for Custom Messages • xxi, 316, 319, 320, 335

Plug Selection • 632

Port Forwarding Examples • 98, 240, 243, 244

Port Number Syntax • 239, 241, 242, 244, 772

Possible Root Causes • 771

Power CIM • 195, 211

Power Control • 797, 799

Power Control Operations • 607

Power Cord • 79

Power Cycling the Outlet(s) • 609

Power IQ Configuration • 800

Powering On/Off/Cycle Outlet Groups • xxii, 536

Power-Off Period Options for Individual Outlets • 145, 150

Preparing the Installation Site • 4

Product Models • 1

Push Out Sensor Readings • 308, 314

PX2-3000 Series • 80

PX2-4000 Series • 80

PX2-5000 Series • xx, 80

Q

Querying Available Parameters for a Command • 434, 435

Querying DNS Servers • 616

Quick Access to a Specific Page • 97, 106

Quitting Configuration Mode • 472, 519

Quitting Diagnostic Mode • 615

R

Rack Unit Configuration • 598

Rack Unit Settings of an Asset Strip • 462

Rackmount Safety Guidelines • 6

Rackmount, Inlet and Outlet Connections • 6

Rack-Mounting the PDU • 6

RADIUS Configuration Illustration • 270, 717

Radius Settings • 566

Raritan Training Website • 770

Raw Configuration Upload and Download • xxii, 392, 397, 666, 672, 695

Rebooting the PX2 • 377, 403

Index

Receptacle Selection • 632

Record Snapshots to Webcam Storage • 308, 314

Reliability Data • 467

Reliability Error Log • 467

Reliability Hardware Failures • xxi, 467

Remembering User Names and Passwords • 100

Removing an Existing LDAP Server • 566

Removing an Existing Radius Server • 569

Request LHX/SHX Maximum Cooling • 308, 315

Reserving IP Addresses in DHCP Servers • 754, 756

Reserving IP in Linux • 756

Reserving IP in Windows • 754

Reset Button • 89

Resetting a Group's Active Energy • xx, 152, 157

Resetting Active Energy Readings • xxii, 613

Resetting All Settings to Factory Defaults • 377, 404, 701

Resetting the Button-Type Circuit Breaker • 90

Resetting the Handle-Type Circuit Breaker • 91

Resetting the PX2 • 613

Resetting to Factory Defaults • 89, 405, 614, 701

Restarting the PDU • 613

Restricted Service Agreement • 517

Retrieving Energy Usage • 429

Retrieving Previous Commands • 435, 436, 618

Retrieving Software Packages Information • 377, 405

Returning User Group Information • 710

Role Configuration Commands • 552

Role of a DNS Server • 706, 770

Role-Based Access Control • 524

S

Safety Guidelines • ii

Safety Instructions • iii, 4, 630

Sample Environmental-Sensor-Level Event Rule • 141, 343

Sample Event Rules • 288, 339

Sample Inlet-Level Event Rule • 342

Sample Outlet-Level Event Rule • 340

Sample PDU-Level Event Rule • 339

Saving User Credentials for PDView's Automatic Login • xx, 27, 28

Scheduling an Action • 286, 314, 327, 333

Schroff LHX/SHX • 195, 206

SecureLock™ Outlets and Cords • 17

Security Configuration Commands • 511

Security Settings • 457

Send an SNMP Notification • 252, 308, 321

Send Email • xxi, 291, 308, 315, 329, 335

Send Sensor Report • 223, 308, 317, 332

Send Sensor Report Example • 317, 329

Send SMS Message • xxi, 308, 319, 335

Send Snapshots via Email • 308, 320

Sending Links to Snapshots or Videos • 407, 409, 411

Sensor Descriptors for Inlet Active Power • xxi, 350, 351

Sensor Log • xxi, 350

Sensor RJ-12 Port Pinouts • 650

Sensor Threshold Configuration Commands • xxii, 576

Sensor Threshold Settings • 126, 128, 137, 148, 161, 167, 170, 178, 179, 189, 428, 757

Sensor/Actuator Location Example • 190, 193, 194

Sensor/Actuator States • 114, 173, 174, 181, 182

Serial Port Configuration Commands • 602

Serial Port Settings • 461

Serial RS-232 • 649

Server Reachability Configuration Commands • 589

Server Reachability Information • 465

Server Reachability Information for a Specific Server • 466

Server Status Checking or Power Control • xxi, 361

Setting an LED Color for a Rack Unit • 600

Setting an LED Mode for a Rack Unit • 600, 601

Setting an Outlet's Cycling Power-Off Period • 533

Index

Setting Data Logging • 225, 347, 349, 476, 477

Setting Data Logging Measurements Per Entry • 477

Setting Default Measurement Units • 176, 212, 222, 223, 546, 549

Setting EAP Parameters • 493

Setting IPv4 Static Routes • xxi, 483

Setting IPv6 Static Routes • xxi, 487

Setting LAN Interface Parameters • 489

Setting LED Colors for Connected Tags • 598, 599, 600

Setting LED Colors for Disconnected Tags • 598, 599, 600

Setting Network Service Parameters • 498

Setting Non-Critical Outlets • 132, 138, 140

Setting NTP Parameters • 508, 511

Setting Outlet Power-On Sequence and Delay • 132, 137

Setting the Alarmed to Normal Delay for DX-PIR • 573

Setting the Authentication Method • 492

Setting the Automatic Daylight Savings Time • 510

Setting the Baud Rates • 602

Setting the BSSID • 496

Setting the Cascading Mode • 3, 33, 35, 36, 226, 227, 228, 230, 239, 241, 246, 380, 381

Setting the Date and Time • xxi, 225, 281, 418, 428

Setting the HTTP Port • 499

Setting the HTTPS Port • 500

Setting the Inrush Guard Delay Time • 475

Setting the IPv4 Address • 482

Setting the IPv4 Configuration Mode • 480

Setting the IPv4 Gateway • 482

Setting the IPv4 Preferred Host Name • 481

Setting the IPv6 Address • 486

Setting the IPv6 Configuration Mode • 484

Setting the IPv6 Gateway • 486

Setting the IPv6 Preferred Host Name • 485

Setting the LED Operation Mode • 599

Setting the Maximum Number of Active Powered Dry Contact Actuators • 479

Setting the Outlet Initialization Delay • 475

Setting the Outlet Power-On Sequence • 473

Setting the Outlet Power-On Sequence Delay • 473

Setting the PDU-Defined Cycling Power-Off Period • 475, 533

Setting the PDU-Defined Default Outlet State • 474, 533

Setting the Polling Interval • 594

Setting the PSK • 492

Setting the Registry to Permit Write Operations to the Schema • 711

Setting the SNMP Configuration • 502

Setting the SNMP Read Community • 503

Setting the SNMP Write Community • 503

Setting the SSID • 491

Setting the sysContact Value • 503

Setting the sysLocation Value • 504

Setting the sysName Value • 504

Setting the Time Zone • 428, 509

Setting the X Coordinate • 570

Setting the Y Coordinate • 571

Setting the Z Coordinate • 478, 571

Setting the Z Coordinate Format for Environmental Sensors • 478, 571, 589

Setting Thresholds for Total Active Energy or Power • 122, 125

Setting Up an SSL/TLS Certificate • 225, 257, 264

Setting Up External Authentication • 225, 257, 269, 770

Setting Wireless Parameters • 491

Setting Your Preferred Measurement Units • 176, 212, 216, 222, 223

Showing Information • 436

Showing Network Connections • 616

Shut down a Server and Control its Power • xxi, 308, 313

SHX Request Maximum Cooling • 210, 211

Single Login Limitation • 520

Slave Device Events in the Log • 772, 773

SNMP Gets and Sets • 426

SNMP Sets and Thresholds • 428

SNMPv2c Notifications • 252, 421

SNMPv3 Notifications • 252, 421, 422

Sorting a List • 107, 113, 132, 165, 173, 199, 217, 221, 234, 335, 384, 386, 390

Special Character Requirement • 524

Index

Specifications • 6, 649

Specifying Non-Critical Outlets • 460, 476

Specifying the Agreement Contents • 519

Specifying the Asset Strip Orientation • 597

Specifying the CC Sensor Type • 570

Specifying the Device Altitude • 477

Specifying the EnergyWise Domain • 593

Specifying the EnergyWise Secret • 594

Specifying the Number of Rack Units • 596

Specifying the Rack Unit Numbering Mode • 596

Specifying the Rack Unit Numbering Offset • 597

Specifying the SSH Public Key • 502, 547

Standard Attributes • 717

Start or Stop a Lua Script • 309, 323, 368, 370

Static Route Examples • 226, 229, 235, 483, 487

Step A

Add Your PX2 as a RADIUS Client • 717, 718, 736, 737

Step A. Determine User Accounts and Roles • 704

Step B

Configure Connection Policies and Standard Attributes • 718, 722

Configure Connection Policies and Vendor-Specific Attributes • 736, 741

Step B. Configure User Groups on the AD Server • 705

Step by Step Flexible Cord Installation • 634

Step C. Configure LDAP Authentication on the PX2 • 706

Step D. Configure Roles on the PX2 • 707

Strong Passwords • 522

Supported Maximum DPX Sensor Distances • xx, 48, 53

Supported Web Browsers • xx, 96

Supported Wireless LAN Configuration • xx, 22, 771

Switch LHX/SHX • 309, 324

Switch Outlet Group • xxi, 309, 324

Switch Outlets • 309, 325

Switch Peripheral Actuator • 309, 325

Switching Off an Actuator • 612

Switching On an Actuator • 611

Syslog Message • 309, 326

System and USB Requirements • 656, 657

T

Testing the Network Connectivity • 617, 773

TFTP Requirements • 673, 674

The ? Command for Showing Available Commands • 434

The Ping Tool • 772, 773

The PX2 MIB • 426

Threaded Grounding Point • xx, 95

Three-Digit Row • 84, 387

Thresholds and Sensor States • 757

Time Configuration Commands • 506

Time Units • 120, 124, 150, 278, 279

TLS Certificate Chain • 232, 253, 273, 327, 349, 781

Tracing the Route • 618

Turning Off the Outlet(s) • 608

Turning On the Outlet(s) • 607

Turning Outlets On/Off and Cycling Power • 794, 797

Two-Digit Row • 85

U

Unbalanced Current Calculation • 768

Unblocking a User • 278, 612

Unpacking the Product and Components • 4

Updating the LDAP Schema • 710

Updating the PX2 Firmware • xix, xxi, 376, 386, 620

Updating the Schema Cache • 714

Upgrade Guidelines for Existing Cascading Chains • 387, 388

Upgrade Sequence in an Existing Cascading Chain • 32, 388

Upload via Curl • xxii, 32, 697, 698, 700

Uploading or Downloading Raw Configuration Data • xxii, 32, 622, 625, 695, 697

Uploading Raw Configuration • xxii, 697

Uppercase Character Requirement • 523

USB Wireless LAN Adapters • 22, 36, 771

User Blocking • 521

User Configuration Commands • 538

User Interfaces Showing Default Units • 223

Index

User Management • 105, 212

Using an Optional DPX3-ENVHUB4 Sensor Hub • 49, 54

Using an Optional DPX-ENVHUB2 Cable • xx, 51

Using an Optional DPX-ENVHUB4 Sensor Hub • xx, 49

Using an X Cable • 67, 73

Using Default Thresholds • 572

Using SCP Commands • 620

Using SNMP • 388, 420

Using the CLI Command • 614, 702

Using the Command Line Interface • 248, 430, 702

Using the Reset Button • 701

Using the Web Interface • 96, 641

V

Vendor-Specific Attributes • 717, 736

Viewing and Managing Locally-Saved Snapshots • 314, 403, 413, 417

Viewing Connected Users • 376, 383, 411

Viewing Firmware Update History • 376, 390

Viewing More Information • xxi, 163

Viewing or Clearing the Local Event Log • 252, 270, 326, 376, 385

W

Ways to Probe Existing User Profiles • 770

Web Interface Overview • xx, 101, 788

Webcam Management • 105, 385, 406

What is a Certificate Chain • 781, 787

What's New in the PX2 User Guide • xix

Windows NTP Server Synchronization Solution • 282, 284

Wired Network Settings • 226, 227, 240, 256, 706

Wireless LAN Diagnostic Log • 233, 234, 465

Wireless Network Settings • 226, 230, 240

Wiring of 3-Phase In-Line Monitors • 632, 634

With an Analog Modem • 433

With HyperTerminal • 431, 612

With SSH or Telnet • 432, 773

Writing or Loading a Lua Script • 368, 372

Y

Yellow- or Red-Highlighted Sensors • 126, 131, 136, 150, 165, 173, 179, 182, 188, 209, 759

Z

Z Coordinate Format • 176, 193

Zero U Connection Ports • 81

Zero U Products • 2