PX3-1000 Series
User Guide

Xerus Firmware v3.6.0™

Copyright © 2019 Raritan, Inc.
PX3-1000-1H-v3.6.0-E
March 2020
255-80-0034-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 tocomply with this warning may result in electric shock, personal injury and death.
WARNING! Use this product in a dry location. Failure to use this product in a dry location may result in electric
shock, personal injury and death.
WARNING! Do not rely on this product's receptacle lamps, receptacle relay switches or any other receptacle
power on/off indicator to determine whether power is being supplied to a receptacle. Unplug a device
connected to this product before performing repair, maintenance or service on the device. Failure to unplug adevice before servicing it may result in electric shock, fire, personal injury and death.
WARNING! Only use this product to power information technology equipment that has a UL/IEC 60950-1 orequivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury anddeath.
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. Useof 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, orother 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 ofthis product.

3.

This product is designed to be used within an electronic equipment rack. The metal case of this product iselectrically 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 thereceptacle’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 bepresent 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 pagehttps://www.raritan.com/product-selector.

This document contains proprietary information that is protected by copyright. All rights reserved. No part ofthis document may be photocopied, reproduced, or translated into another language without express priorwritten consent of Raritan, Inc.
© Copyright 2019 Raritan, Inc. All third-party software and hardware mentioned in this document areregistered trademarks or trademarks of and are the property of their respective holders.
FreeType Project Copyright Notice

Portions of this software are copyright © 2015 The FreeType Project (www.freetype.org). All rights reserved.
FCC Information

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant toPart 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmfulinterference 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 toradio communications. Operation of this equipment in a residential environment may cause harmfulinterference.
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 arisingunder normal operating conditions.
If a power cable is included with this product, it must be used exclusively for this product.

Contents
Safety Guidelines

ii

Safety Instructionsiii

Applicable Models

xvii

What's New in the PX3 User Guide

xix

Chapter 1 Introduction

1

Product Models ............................................................................................................................................ 1
Package Contents ......................................................................................................................................... 1
Zero U Products................................................................................................................................. 1
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 ........................................................................................................... 3
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 Zero U Models Using L-Brackets and Buttons ................................................................ 11
Mounting 1U or 2U Models ............................................................................................................ 12
Connecting a PX3 Locking Line Cord ........................................................................................................... 14
Disconnecting a PX3 Locking Line Cord ........................................................................................... 15
Installing Cable Retention Clips on the Inlet (Optional) ............................................................................. 16
Installing Cable Retention Clips on Outlets (Optional) ............................................................................... 17
Locking Outlets and Cords .......................................................................................................................... 18
SecureLock™ Outlets and Cords ...................................................................................................... 18vi

Contents

Button-Type Locking Outlets ........................................................................................................... 20

Chapter 3 Initial Installation and Configuration

21

Connecting the PDU to a Power Source ..................................................................................................... 21
Connecting the PX3 to Your Network ......................................................................................................... 22
USB Wireless LAN Adapters ............................................................................................................ 23
Supported Wireless LAN Configuration .......................................................................................... 23
Dual Ethernet Connection ............................................................................................................... 24
Configuring the PX3 .................................................................................................................................... 24
Connecting a Mobile Device to PX3 ................................................................................................ 25
Connecting the PX3 to a Computer ................................................................................................. 31
Bulk Configuration Methods ...................................................................................................................... 33
Cascading Multiple PX3 Devices for Sharing Ethernet Connectivity .......................................................... 34
Cascading All Devices via USB ......................................................................................................... 35
Extended Cascading with PX3 Devices ............................................................................................ 38
Restrictions of Port-Forwarding Connections ................................................................................. 41
Power-Sharing Restrictions and Connection .............................................................................................. 43
Making a Power-Sharing Connection .............................................................................................. 44
Power-Sharing Configurations and Restrictions.............................................................................. 45
Supported Sensor Configurations for Power Sharing ..................................................................... 46

Chapter 4

Connecting External Equipment (Optional)

48

Connecting Raritan Environmental Sensor Packages ................................................................................. 48
Identifying the Sensor Port ............................................................................................................. 49
DX2 Sensor Packages....................................................................................................................... 49
DX Sensor Packages......................................................................................................................... 51
DPX3 Sensor Packages .................................................................................................................... 52
DPX2 Sensor Packages .................................................................................................................... 54
DPX Sensor Packages ...................................................................................................................... 57
Using an Optional DPX3-ENVHUB4 Sensor Hub .............................................................................. 62
Mixing Diverse Sensor Types ........................................................................................................... 63
Connecting Asset Management Strips ....................................................................................................... 68
Combining Regular Asset Strips ...................................................................................................... 69
Introduction to Asset Tags .............................................................................................................. 71
Connecting Regular Asset Strips to PX3 .......................................................................................... 71
Connecting Blade Extension Strips .................................................................................................. 73
Connecting Composite Asset Strips (AMS-Mx-Z) ............................................................................ 75vii

Contents

Connecting a Logitech Webcam ................................................................................................................. 78
Connecting a GSM Modem ........................................................................................................................ 79
Connecting an Analog Modem ................................................................................................................... 79
Connecting an External Beeper .................................................................................................................. 80
Connecting a Schroff LHX/SHX Heat Exchanger ......................................................................................... 80
Connecting a Modbus RTU Device or Bus .................................................................................................. 81

Chapter 5

PDU Linking

82

FAQs ........................................................................................................................................................... 83
PDU Linking in the Web GUI ....................................................................................................................... 85
Designating the Master Unit ........................................................................................................... 86
Adding a Link Unit ........................................................................................................................... 87
Master Units Manage Link Units ..................................................................................................... 90
Releasing a Link Unit ....................................................................................................................... 91
Switching to a Different PDU .......................................................................................................... 92
Re-linking a Link Unit ....................................................................................................................... 93
Viewing Link Unit Information ........................................................................................................ 95
Outlet Groups ................................................................................................................................ 103
Pairwise Outlet Groups ................................................................................................................. 108
OCPs Page ..................................................................................................................................... 110
Peripherals Page............................................................................................................................ 110
Feature Ports Page ........................................................................................................................ 111
Displays for Master and Link Units ........................................................................................................... 111
PDU Linking in the CLI ............................................................................................................................... 113
PDU Linking CLI Commands .......................................................................................................... 114

Chapter 6 Introduction to PDU Components

115

Panel Components ................................................................................................................................... 115
Inlet ............................................................................................................................................... 116
Outlets ........................................................................................................................................... 117
Connection Ports ........................................................................................................................... 117
Dot-Matrix LCD Display ................................................................................................................. 119
Reset Button.................................................................................................................................. 151
Circuit Breakers ........................................................................................................................................ 151
Resetting the Button-Type Circuit Breaker ................................................................................... 152
Resetting the Handle-Type Circuit Breaker ................................................................................... 152
Fuse .......................................................................................................................................................... 153
Fuse Replacement on Zero U Models ........................................................................................... 153
Fuse Replacement on 1U Models ................................................................................................. 155

viii

Contents

Beeper ...................................................................................................................................................... 156
Replaceable Controller ............................................................................................................................. 157
Threaded Grounding Point ....................................................................................................................... 158

Chapter 7

Using the Web Interface

159

Supported Web Browsers ........................................................................................................................ 159
Login, Logout and Password Change ........................................................................................................ 159
Login .............................................................................................................................................. 159
Changing Your Password ............................................................................................................... 162
Remembering User Names and Passwords .................................................................................. 163
Logout ........................................................................................................................................... 163
Web Interface Overview .......................................................................................................................... 164
Menu ............................................................................................................................................. 167
Quick Access to a Specific Page ..................................................................................................... 169
Sorting a List .................................................................................................................................. 170
Dashboard ................................................................................................................................................ 171
Dashboard - Inlet I1 ....................................................................................................................... 173
Dashboard - OCP ........................................................................................................................... 175
Dashboard - Alerted Sensors ......................................................................................................... 176
Dashboard - Inlet History .............................................................................................................. 178
Dashboard - Alarms ....................................................................................................................... 180
PDU ........................................................................................................................................................... 182
Internal Beeper State .................................................................................................................... 183
Time Units ..................................................................................................................................... 184
Setting Thresholds for Total Active Energy or Power.................................................................... 184+12V Power Supply Sensor ........................................................................................................... 186
Inlet .......................................................................................................................................................... 187
Configuring a Multi-Inlet Model .................................................................................................... 190
Outlets ...................................................................................................................................................... 192
Available Data of the Outlets Overview Page ............................................................................... 193
Individual Outlet Pages ................................................................................................................. 193
OCPs ......................................................................................................................................................... 195
Individual OCP Pages ..................................................................................................................... 197
Peripherals ............................................................................................................................................... 202
Yellow- or Red-Highlighted Sensors .............................................................................................. 208
Managed vs Unmanaged Sensors/Actuators ................................................................................ 210
Sensor/Actuator States ................................................................................................................. 211
Finding the Sensor's Serial Number .............................................................................................. 212
Identifying the Sensor Position and Channel ................................................................................ 213
How the Automatic Management Function Works ...................................................................... 215
Managing One Sensor or Actuator ................................................................................................ 215
Individual Sensor/Actuator Pages ................................................................................................. 217
Z Coordinate Format ..................................................................................................................... 222
Feature Port ............................................................................................................................................. 223
Asset Strip ..................................................................................................................................... 225
External Beeper ............................................................................................................................. 233

ix

Contents

Schroff LHX/SHX ............................................................................................................................ 234
Power CIM ..................................................................................................................................... 239
User Management .................................................................................................................................... 240
Creating Users ............................................................................................................................... 241
Editing or Deleting Users ............................................................................................................... 244
Creating Roles ............................................................................................................................... 246
Editing or Deleting Roles ............................................................................................................... 248
Setting Your Preferred Measurement Units ................................................................................. 249
Setting Default Measurement Units ............................................................................................. 250
Device Settings ......................................................................................................................................... 251
Configuring Network Settings ....................................................................................................... 253
Configuring Network Services ....................................................................................................... 278
Configuring Security Settings ........................................................................................................ 289
Setting the Date and Time ............................................................................................................ 312
Event Rules and Actions ................................................................................................................ 316
Setting Data Logging ..................................................................................................................... 372
Configuring Data Push Settings ..................................................................................................... 373
Monitoring Server Accessibility ..................................................................................................... 382
Front Panel Settings ...................................................................................................................... 386
Configuring the Serial Port ............................................................................................................ 387
Lua Scripts ..................................................................................................................................... 389
Miscellaneous ............................................................................................................................... 394
Maintenance ............................................................................................................................................ 396
Device Information........................................................................................................................ 398
Viewing Connected Users ............................................................................................................. 403
Viewing or Clearing the Local Event Log ....................................................................................... 405
Updating the PX3 Firmware .......................................................................................................... 406
Viewing Firmware Update History ................................................................................................ 410
Bulk Configuration......................................................................................................................... 411
Backup and Restore of Device Settings ......................................................................................... 418
Network Diagnostics ..................................................................................................................... 420
Downloading Diagnostic Information ........................................................................................... 421
Hardware Issue Detection ............................................................................................................. 421
Rebooting the PX3 ......................................................................................................................... 423
Resetting All Settings to Factory Defaults ..................................................................................... 423
Retrieving Software Packages Information ................................................................................... 424
Webcam Management ............................................................................................................................. 425
Configuring Webcams and Viewing Live Images ........................................................................... 427
Sending Links to Snapshots or Videos ........................................................................................... 430
Viewing and Managing Locally-Saved Snapshots .......................................................................... 432
Changing Storage Settings............................................................................................................. 434
SmartLock and Card Reader ..................................................................................................................... 438
SmartLock ...................................................................................................................................... 440
Card Readers ................................................................................................................................. 445

x

Contents

Chapter 8

Using SNMP

447

Enabling and Configuring SNMP ............................................................................................................... 447
SNMPv2c Notifications .................................................................................................................. 448
SNMPv3 Notifications ................................................................................................................... 449
Downloading SNMP MIB .......................................................................................................................... 452
SNMP Gets and Sets ................................................................................................................................. 453
The PX3 MIB .................................................................................................................................. 453
A Note about Enabling Thresholds ................................................................................................ 455

Chapter 9

Using the Command Line Interface

456

About the Interface .................................................................................................................................. 456
Logging in to CLI ....................................................................................................................................... 457
With HyperTerminal ...................................................................................................................... 457
With SSH or Telnet ........................................................................................................................ 458
With an Analog Modem ................................................................................................................ 459
Different CLI Modes and Prompts ................................................................................................. 459
Closing a Local Connection ............................................................................................................ 460
The ? Command for Showing Available Commands ................................................................................. 460
Querying Available Parameters for a Command ...................................................................................... 461
Showing Information ................................................................................................................................ 462
Network Configuration.................................................................................................................. 462
PDU Configuration ........................................................................................................................ 466
Outlet Information ........................................................................................................................ 467
Inlet Information ........................................................................................................................... 468
Overcurrent Protector Information .............................................................................................. 469
Date and Time Settings ................................................................................................................. 470
Default Measurement Units .......................................................................................................... 470
Environmental Sensor Information ............................................................................................... 471
Environmental Sensor Package Information ................................................................................. 472
Actuator Information .................................................................................................................... 473
Inlet Sensor Threshold Information .............................................................................................. 474
Inlet Pole Sensor Threshold Information ...................................................................................... 476
Overcurrent Protector Sensor Threshold Information .................................................................. 478
Environmental Sensor Threshold Information .............................................................................. 479
Environmental Sensor Default Thresholds .................................................................................... 480
Security Settings ............................................................................................................................ 481
Authentication Settings ................................................................................................................. 482
Existing User Profiles ..................................................................................................................... 483
Existing Roles................................................................................................................................. 484
Serial Port Settings ........................................................................................................................ 484
EnergyWise Settings ...................................................................................................................... 484
Asset Strip Settings........................................................................................................................ 485
Rack Unit Settings of an Asset Strip .............................................................................................. 485
Event Log ....................................................................................................................................... 486

xi

Contents

Network Connections Diagnostic Log ........................................................................................... 487
Server Reachability Information ................................................................................................... 487
Command History ......................................................................................................................... 488
Reliability Data .............................................................................................................................. 489
Reliability Error Log ....................................................................................................................... 489
Reliability Hardware Failures ........................................................................................................ 489
Examples ....................................................................................................................................... 489
Clearing Information ................................................................................................................................ 492
Clearing Event Log ......................................................................................................................... 492
Clearing Diagnostic Log for Network Connections ........................................................................ 493
Configuring the PX3 Device and Network ................................................................................................ 493
Entering Configuration Mode ....................................................................................................... 493
Quitting Configuration Mode ........................................................................................................ 494
PDU Configuration Commands ..................................................................................................... 494
Network Configuration Commands .............................................................................................. 498
Time Configuration Commands .................................................................................................... 528
Checking the Accessibility of NTP Servers ..................................................................................... 533
Security Configuration Commands ............................................................................................... 533
Outlet Configuration Commands .................................................................................................. 554
Inlet Configuration Commands ..................................................................................................... 554
Overcurrent Protector Configuration Commands......................................................................... 556
User Configuration Commands ..................................................................................................... 556
Role Configuration Commands ..................................................................................................... 568
Authentication Commands ........................................................................................................... 571
Environmental Sensor Configuration Commands ......................................................................... 583
Configuring Environmental Sensors' Default Thresholds .............................................................. 587
Sensor Threshold Configuration Commands................................................................................. 589
Actuator Configuration Commands .............................................................................................. 600
Server Reachability Configuration Commands .............................................................................. 601
EnergyWise Configuration Commands ......................................................................................... 604
Asset Management Commands .................................................................................................... 606
Serial Port Configuration Commands ............................................................................................ 613
Multi-Command Syntax ................................................................................................................ 615
Actuator Control Operations .................................................................................................................... 616
Switching On an Actuator ............................................................................................................. 617
Switching Off an Actuator ............................................................................................................. 617
Example - Turning On a Specific Actuator ..................................................................................... 618
Unblocking a User .................................................................................................................................... 618
Resetting the PX3 ..................................................................................................................................... 618
Restarting the PDU ........................................................................................................................ 618
Resetting to Factory Defaults ........................................................................................................ 619
Network Troubleshooting ........................................................................................................................ 619
Entering Diagnostic Mode ............................................................................................................. 619
Quitting Diagnostic Mode ............................................................................................................. 620
Diagnostic Commands ................................................................................................................... 620

xii

Contents

Retrieving Previous Commands ............................................................................................................... 622
Automatically Completing a Command .................................................................................................... 622
Logging out of CLI ..................................................................................................................................... 623

Chapter 10

Using SCP Commands

624

Firmware Update via SCP ......................................................................................................................... 624
Bulk Configuration via SCP ....................................................................................................................... 625
Backup and Restore via SCP ..................................................................................................................... 626
Downloading Diagnostic Data via SCP ...................................................................................................... 627
Uploading or Downloading Raw Configuration Data ............................................................................... 629
Keys that Cannot Be Uploaded ..................................................................................................... 632

Appendix A

Specifications

634

Maximum Ambient Operating Temperature ........................................................................................... 634
Serial RS-232 "RJ-45" Port Pinouts ........................................................................................................... 634
Sensor RJ-45 Port Pinouts ........................................................................................................................ 634
Feature RJ-45 Port Pinouts ....................................................................................................................... 635
Expansion RJ-45 Port Pinouts ................................................................................................................... 636

Appendix B

Equipment Setup Worksheet

637

Appendix C

Configuration or Firmware Upgrade with a USB Drive641

Device Configuration/Upgrade Procedure ............................................................................................... 641
System and USB Requirements ................................................................................................................ 642
Configuration Files .................................................................................................................................... 643
fwupdate.cfg ................................................................................................................................. 644
config.txt ....................................................................................................................................... 648
devices.csv .................................................................................................................................... 650
Creating Configuration Files via Mass Deployment Utility ............................................................ 651
Data Encryption in 'config.txt' ....................................................................................................... 652

xiii

Contents

Firmware Upgrade via USB ....................................................................................................................... 653

Appendix D

Bulk Configuration or Firmware Upgrade via DHCP/TFTP

655

Bulk Configuration/Upgrade Procedure ................................................................................................... 656
TFTP Requirements .................................................................................................................................. 657
DHCP IPv4 Configuration in Windows ...................................................................................................... 657
DHCP IPv6 Configuration in Windows ...................................................................................................... 667
DHCP IPv4 Configuration in Linux ............................................................................................................. 674
DHCP IPv6 Configuration in Linux ............................................................................................................. 676

Appendix E

Raw Configuration Upload and Download

678

Downloading Raw Configuration .............................................................................................................. 678
Download via Web Browsers ........................................................................................................ 678
Download via Curl ......................................................................................................................... 679
Uploading Raw Configuration .................................................................................................................. 680
Upload via Curl .............................................................................................................................. 681
Curl Upload Return Codes ............................................................................................................. 682

Appendix F

Resetting to Factory Defaults

684

Using the Reset Button ............................................................................................................................. 684
Using the CLI Command ........................................................................................................................... 685

Appendix G

PX3 Models with Residual Current Monitoring

686

RCM Current Sensor ................................................................................................................................. 686
RCM State Sensor ..................................................................................................................................... 687
Compliance with IEC 62020 ...................................................................................................................... 688
RCM Self-Test ........................................................................................................................................... 689
Web Interface Operations for RCM .......................................................................................................... 690
Checking RCM State and Current .................................................................................................. 690
Setting RCM Current Thresholds ................................................................................................... 692
Scheduling RCM Self-Test.............................................................................................................. 693
Disabling or Enabling Front Panel RCM Self-Test .......................................................................... 694
Setting RCM DC Current Thresholds ............................................................................................. 694
Front Panel Operations for RCM .............................................................................................................. 696
LCD Message for RCM Critical State .............................................................................................. 696
Checking RCM States and Current ................................................................................................ 697
Running RCM Self-Test .................................................................................................................. 698
RCM SNMP Operations ............................................................................................................................ 699
RCM Trap ....................................................................................................................................... 699
RCM Residual Current and State Objects ...................................................................................... 700
Setting RCM Thresholds ................................................................................................................ 700
Running RCM Self-Test .................................................................................................................. 700

xiv

Contents

CLI Operations for RCM ............................................................................................................................ 700
Showing Residual Current Monitoring Information ...................................................................... 701
Setting RCM Current Thresholds ................................................................................................... 701
Setting Front Panel RCM Self-Test ................................................................................................ 703
Running RCM Self-Test .................................................................................................................. 703
Degaussing RCM Type B Sensors ................................................................................................... 703

Appendix H

Old Generations of PX3 Models

704

PX3 'Phase II' Front Panel Display............................................................................................................. 704
PX3 'Phase I' Front Panel Display.............................................................................................................. 705
Overview of the LCD Display ......................................................................................................... 705
Control Buttons ............................................................................................................................. 706
Operating the LCD Display ............................................................................................................ 707
Serial RS-232 "DB9" Port Pinouts ............................................................................................................. 720

Appendix I

LDAP Configuration Illustration

721

Step A. Determine User Accounts and Roles ............................................................................................ 721
Step B. Configure User Groups on the AD Server ..................................................................................... 722
Step C. Configure LDAP Authentication on the PX3 ................................................................................. 723
Step D. Configure Roles on the PX3 .......................................................................................................... 726

Appendix J

Updating the LDAP Schema

729

Returning User Group Information .......................................................................................................... 729
From LDAP/LDAPS ......................................................................................................................... 729
From Microsoft Active Directory ................................................................................................... 729
Setting the Registry to Permit Write Operations to the Schema ............................................................. 730
Creating a New Attribute ......................................................................................................................... 730
Adding Attributes to the Class .................................................................................................................. 731
Updating the Schema Cache .................................................................................................................... 733
Editing rciusergroup Attributes for User Members .................................................................................. 733

Appendix K

RADIUS Configuration Illustration

736

Standard Attributes .................................................................................................................................. 736
NPS Standard Attribute Illustration............................................................................................... 736
FreeRADIUS Standard Attribute Illustration.................................................................................. 754
Vendor-Specific Attributes ....................................................................................................................... 755
NPS VSA Illustration ...................................................................................................................... 755
FreeRADIUS VSA Illustration ......................................................................................................... 767

xv

Contents

AD-Related Configuration ........................................................................................................................ 768

Appendix L

Additional PX3 Information

772

RJ45-to-DB9 Cable Requirements for Modem Connections .................................................................... 772
Reserving IP Addresses in DHCP Servers .................................................................................................. 773
Reserving IP in Windows ............................................................................................................... 774
Reserving IP in Linux...................................................................................................................... 775
Sensor Threshold Settings ........................................................................................................................ 777
Thresholds and Sensor States ....................................................................................................... 777"To Assert" and Assertion Timeout ............................................................................................... 780"To De-assert" and Deassertion Hysteresis................................................................................... 782
Default Voltage and Current Thresholds .................................................................................................. 785
Altitude Correction Factors ...................................................................................................................... 787
Unbalanced Current Calculation .............................................................................................................. 787
Data for BTU Calculation .......................................................................................................................... 788
Ways to Probe Existing User Profiles ........................................................................................................ 789
Raritan Training Website .......................................................................................................................... 789
Role of a DNS Server ................................................................................................................................. 790
Cascading Troubleshooting ...................................................................................................................... 790
Possible Root Causes ..................................................................................................................... 790
Slave Device Events in the Log ...................................................................................................... 793
The Ping Tool ................................................................................................................................. 794
Installing the USB-to-Serial Driver (Optional) ........................................................................................... 795
Initial Network Configuration via CLI ........................................................................................................ 796
Device-Specific Settings ............................................................................................................................ 803
TLS Certificate Chain ................................................................................................................................. 804
What is a Certificate Chain ............................................................................................................ 804
Illustration - GMAIL SMTP Certificate Chain ................................................................................. 807
Browsing through the Online Help ........................................................................................................... 810

Appendix M

Integration

812

Dominion KX II / III Configuration ............................................................................................................. 812
Configuring Rack PDU Targets ....................................................................................................... 812
Turning Outlets On/Off and Cycling Power ................................................................................... 816
Dominion KSX II, SX or SX II Configuration ............................................................................................... 817
Dominion KSX II ............................................................................................................................. 817
Dominion SX and SX II ................................................................................................................... 818
Power IQ Configuration ............................................................................................................................ 822
dcTrack ..................................................................................................................................................... 823
dcTrack Overview .......................................................................................................................... 823
Asset Management Strips and dcTrack ......................................................................................... 824

Index

xvi

825

Applicable Models
This User Guide is applicable to all the following PDU Generations.
•

PX3 with iX7™ PDU Generation (1000 series)

Any PX Generations can be associated with existing metering families called“Series”, from 1000 series to 5000 series.
For example, PX2-4000 and PX3-4000 series are all inlet metered and outlet
metered PDUs, but have different controller generations.
Note: For information on other PX2, PX3, PXC or PXO models, refer to 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 amodel's technical design, refer to their product specifications on Raritan
website's PDU Product Selector pagehttps://www.raritan.com/product-selector.

Comparison between PX2, PX3, PXC and PXO series:

xvii

Chapter 1: Applicable Models

Product models
Front panel display

PX2

PX3

PXC / PXO

LED display

Dot-matrix LCD
display

Dot-matrix LCD
display

Outlet latching relays
Number of LAN ports
Maximum LAN rate*
1

2

100 Mbps **1,000 Mbps

Replaceable controller

Number of USB-A ports

Maximum USB rate
RS-232 port
(CONSOLE/MODEM)

100 Mbps

***
1

2

1

12 Mbps

480 Mbps

480 Mbps

RJ-45 Connector

RJ-45 Connector

Male DB9
Connector

Expansion ports

SENSOR port type

2

****
RJ-12

RJ-45

RJ-45

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

xviii

What's New in the PX3 User Guide
Important: If your PX3 is running any firmware version older than 3.3.0, youmust upgrade it to 3.3.x or 3.4.x before upgrading it to 3.5.0 or later. See
Updating the PX3 Firmware (on page 406).

•

New Features and Updates:
PDU Linking (on page 82)

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

xix

Chapter 1

Introduction

In this User Guide, PX3 refers to PX3 with "iX7™" controller (that is, PX3-iX7)
unless otherwise specified.
Raritan's PX3 is an intelligent power distribution unit (PDU) that allows you toreboot remote servers and other network devices and/or to monitor power inthe data center.
The intended use of PX3 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 PX3 models -- some are outlet-switchingcapable, and some are not. This guide introduces PX3-1000 series only, which
does NOT support outlet switching.

In This Chapter
Product Models ....................................................................................................1
Package Contents .................................................................................................1
APIPA and Link-Local Addressing ..........................................................................2
Before You Begin ..................................................................................................3

Product Models
PX3 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 PX3 Data Sheet from Raritan's website, visit the Product Selector
page (http://www.findmypdu.com/) on Raritan's website, or contact yourlocal 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 PX3
• Screws, brackets and/or buttons for Zero U• Cable retention clips for the inlet (for some models only)• Cable retention clips for outlets (for some models only)1Chapter 1: Introduction

1U Products• One PX3
• 1U bracket pack and screws• Cable retention clips for the inlet (for some models only)

2U Products• One PX3
• 2U bracket pack and screws• Cable retention clips for the inlet (for some models only)

APIPA and Link-Local Addressing
PX3 supports Automatic Private Internet Protocol Addressing (APIPA).
With APIPA, your PX3 automatically configures a link-local IP address and alink-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 PX3 using thelink-local address/host name. Those in a different subnet cannot access it.
Exception: PX3 in the Port Forwarding mode does not support APIPA. See
Setting the Cascading Mode (on page 270).
Once the PX3 can get a DHCP-assigned IP address, it stops using APIPA and thelink-local address is replaced by the DHCP-assigned address.

•

Scenarios where APIPA applies:
DHCP is enabled on the PX3, but no IP address is assigned to the PX3.
This may be caused by the absence or malfunction of DHCP servers in the
network.
Note: Configuration by connecting the PX3 to a computer using a network
cable is an application of this scenario. See Connecting the PX3 to a
Computer (on page 31).

••

The PX3 previously obtained an IP address from the DHCP server, but thelease of this IP address has expired, and the lease cannot be renewed, orno new IP address is available.
Link-local addressing:
IPv4 address:
Factory default is to enable IPv4 only. The link-local IPv4 address is169.254.x.x/16, which ranges between 169.254.1.0 and 169.254.254.255.

2

Chapter 1: Introduction•

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

•

Host name - pdu.local:
You can type https://pdu.local to access the PX3 instead of typing thelink-local IP address.

•

Retrieval of the link-local address:
See Device Info (on page 141).

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 PX3 and other equipment from the box in which they wereshipped. See Package Contents (on page 1) for a complete list of thecontents of the box.

2.

Compare the serial number of the equipment with the number on thepacking 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 PX3 are set to ON. If not, turn themON.
Or make sure that all fuses are inserted and seated properly. If there areany 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 temperaturesand humidity.
Note: If necessary, contact Raritan Technical Support for the maximum
operating temperature for your model. See Maximum Ambient Operating
Temperature (on page 634).

2.

Allow sufficient space around the PX3 for cabling and outlet connections.

3.

Review Safety Instructions (on page iii) listed in this User Guide.

3

Chapter 1: Introduction

Checking the Branch Circuit Rating
The rating of the branch circuit supplying power to the PDU shall be inaccordance 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 637). 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.

4Chapter 2

Rackmount, Inlet and Outlet Connections

In This Chapter
Circuit Breaker Orientation Limitation .................................................................5
Rack-Mounting the PDU .......................................................................................5
Connecting a PX3 Locking Line Cord ...................................................................14
Installing Cable Retention Clips on the Inlet (Optional) .....................................16
Installing Cable Retention Clips on Outlets (Optional) .......................................17
Locking Outlets and Cords ..................................................................................18

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, shockstress reduces the trip point by 10%.
Note: If normally the line cord is down, upside down means the line cord isup.

Rack-Mounting the PDUThis chapter describes how to rack mount a PX3. To mount a Zero U PX3-1000
series PDU, you can use either two buttons or L-brackets that Raritan provided.
Rackmount Safety Guidelines
In Raritan products which require rack mounting, follow these precautions:▪

Operation temperature in a closed rack environment may be greaterthan room temperature. Do not exceed the rated maximum ambient
temperature of the Power Distribution Units. See Specifications (onpage 634) in the User Guide.

▪

Ensure sufficient airflow through the rack environment.

▪

Mount equipment in the rack carefully to avoid uneven mechanicalloading.

▪

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

▪

Ground all equipment properly, especially supply connections, to thebranch circuit.

5

Chapter 2: Rackmount, Inlet and Outlet Connections

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.

To mount Zero U models using L-brackets:

6

1.

Align the baseplates on the rear of the PX3 device.

2.

Secure the baseplates in place. Use the included L-shaped hex key toloosen the hex socket screws until the baseplate is "slightly" fastened.

3.

Align the L-brackets with the baseplates so that the five screw-holes on the
baseplates line up through the L-bracket's slots. The rackmount side ofbrackets should face either the left or right side of the PX3 device.

4.

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

Chapter 2: Rackmount, Inlet and Outlet Connections

5.

Using rack screws, fasten the PX3 device to the rack through theL-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.

To mount Zero-U models using button mount:1.

Align the baseplates on the rear of the PX3 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).

7

Chapter 2: Rackmount, Inlet and Outlet Connections

4.

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

5.

Loosen the hex socket screws until the mounting buttons are secured intheir position.

6.

Ensure that both buttons can engage their mounting holes simultaneously.

7.

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

To mount Zero U models using claw-foot brackets:
1.

8

Align the baseplates on the rear of the PX3 device.

Chapter 2: Rackmount, Inlet and Outlet Connections

2.

Secure the baseplates in place. Use the included L-shaped hex key toloosen the hex socket screws until the baseplate is "slightly" fastened.

3.

Align the claw-foot brackets with the baseplates so that the fivescrew-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 thePX3 device.

4.

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

5.

Using rack screws, fasten the PX3 device to the rack through the claw-footbrackets.

9Chapter 2: Rackmount, Inlet and Outlet Connections

Mounting Zero U Models Using Two Rear Buttons
The following describes how to mount a PX3 using two buttons only. If yourPDU has circuit breakers implemented, read Circuit Breaker Orientation
Limitation (on page 5) before mounting it.

To mount Zero U models using two buttons:

101.

Turn to the rear of the PX3.

2.

Locate two screw holes on the rear panel: one near the bottom and theother 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).

Chapter 2: Rackmount, Inlet and Outlet Connections

4.

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

5.

Ensure that the two buttons can engage their mounting holes in the rackor cabinet simultaneously.

6.

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

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

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

Align the two central holes of the L-bracket with the two screw holes on
the top of the PX3 device.

11

Chapter 2: Rackmount, Inlet and Outlet Connections

2.

Screw the L-bracket to the device and ensure the bracket is fastened
securely.

3.

Repeat Steps 1 to 2 to screw another L-bracket to the bottom of thedevice.

4.

After both L-brackets are installed, you can choose either of the following
ways to mount the device in the rack.
▪

Using rack screws, fasten the device to the rack through two identicalholes near the edge of each L-bracket.

▪

Mount the device by screwing a mounting button in the back center of
each L-bracket and then having both buttons engage the mounting
holes in the rack. The recommended torque for the button is 1.96 N·m(20 kgf·cm).

Mounting 1U or 2U Models
Using the appropriate brackets and tools, fasten the 1U or 2U device to therack or cabinet.
To mount the PX3 device:1.

12

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

Chapter 2: Rackmount, Inlet and Outlet Connections

2.

Insert the cable-support bar into rackmount brackets.

3.

Secure with the provided end cap screws.

4.

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

13

Chapter 2: Rackmount, Inlet and Outlet Connections

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

A line cord with locking clips: A locking inlet on the PDU is required for thiscord.
A line cord with slide release buttons: This line cord automatically locks
after being connected to the inlet. A locking inlet is not required for thiscord.

A locking inlet and/or locking line cord ensure that the line cord is securely
fastened to the inlet.
To connect a cord with locking clips:
Make sure the line cord's locking clips fit into the locking holes at two sides of
the inlet when plugging the cord's connector into the PDU's locking inlet.

NumberItem

1

Locking holes on the inlet

2

Locking clips of the line cord
To connect a cord with slide release buttons:

Simply plug the cord's connector into the PDU's inlet.

14Chapter 2: Rackmount, Inlet and Outlet Connections

NumberItem

1

Slide release buttons

For information on removing the locking line cord, see Disconnecting a PX3
Locking Line Cord (on page 15).
Disconnecting a PX3 Locking Line Cord
The ways to disconnect a locking line cord vary according to the cord type.
To disconnect a line cord with locking clips:
Press both locking clips of the line cord while unplugging the cord.
Tip: You can slightly move the line cord's plug horizontally while pulling it out tofacilitate the disconnection process.

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

15

Chapter 2: Rackmount, Inlet and Outlet Connections

Installing Cable Retention Clips on the Inlet (Optional)
If your PX3 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 highseismic 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 tinyholes.
Zero U models

3.

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

16

1U/2U models

1U/2U models

Chapter 2: Rackmount, Inlet and Outlet Connections

Installing Cable Retention Clips on Outlets (Optional)
If your PX3 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 highseismic 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 canrequest 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 theinstallation 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 18).
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 tinyholes.

17

Chapter 2: Rackmount, Inlet and Outlet Connections

3.

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

4.

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

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™ 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. Thismethod requires the following two components:••

18

Raritan PDU with SecureLock™ outlets, which have a latch slot inside eitherside of the outlet.
SecureLock™ cords, which is a power cord with a locking latch on each sideof its plug. The following diagram illustrates such a plug.

Chapter 2: Rackmount, Inlet and Outlet Connections

Item

Description

A

Latches on the SecureLock™ cord's plug

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

2.

Verify that the SecureLock™ cord you purchased meets your needs.
▪

The cords' female socket matches the power socket type (C14 or C20)
on your IT equipment.

▪

The cord's male plug matches the outlet type (C13 or C19) on your
PDU.

Connect the SecureLock™ cord between the IT equipment and your PDU.
▪

Plug the female socket end of the cord into the power socket of thedesired IT equipment.

▪

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

To remove a SecureLock™ power cord from the PDU:
1.

Press and hold down the two latches on the cord's plug as illustrated in the
diagram below.

2.

Unplug the cord now.

19

Chapter 2: Rackmount, Inlet and Outlet Connections

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:

20

1.

Press and hold down the tiny button adjacent to the outlet. Depending on
the outlet type, the button location differs.

2.

Unplug the power cord now.

Chapter 3

Initial Installation and Configuration
This chapter explains how to install your PX3 and configure it for network
connectivity.

In This Chapter
Connecting the PDU to a Power Source .............................................................21
Connecting the PX3 to Your Network .................................................................22
Configuring the PX3 ............................................................................................24
Bulk Configuration Methods ...............................................................................33
Cascading Multiple PX3 Devices for Sharing Ethernet Connectivity ...................34
Power-Sharing Restrictions and Connection ......................................................43

Connecting the PDU to a Power Source
1.

Verify that all circuit breakers on the PX3 are set to ON. If not, turn themON.
Or make sure that all fuses are inserted and seated properly. If there areany fuse covers, ensure that they are closed.
Note: Not all models have overcurrent protectors.

2.

Connect each PX3 to an appropriately rated branch circuit. Refer to thelabel or nameplate affixed to your PX3 for appropriate input ratings or
range of ratings.
Note: When a PX3 powers up, it proceeds with the power-on self test andsoftware 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.

3.

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

21

Chapter 3: Initial Installation and Configuration

Connecting the PX3 to Your Network
To remotely administer the PX3, you must connect the PX3 to your local area
network (LAN). PX3 can be connected to a wired or wireless network.
Note: If your PX3 will work as a master device in the bridging mode, you must
make a wired connection. See Cascading Multiple PX3 Devices for Sharing
Ethernet Connectivity (on page 34).
Ethernet port of PX3 must be enabled for the described connection to work
properly, which has been enabled per default. See Wired Network Settings (onpage 254).
To make a wired connection:
1.

2.

Connect a standard network patch cable to either or both Ethernet portson the PX3.
▪

The two Ethernet ports must be connected to different subnets. See
Dual Ethernet Connection (on page 24).

▪

The "green" Ethernet port labeled "ETH 10/100/1000" supports up to
1000 Mbps so it is highly recommended for network connection.

Connect the other end of the cable to your LAN.
Below illustrates the ETHERNET ports on PX3 Zero U models. Note that the port
locations on your models may differ.

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:▪

22

Plug a supported USB wireless LAN adapter into the USB-A port onyour PX3.

Chapter 3: Initial Installation and Configuration▪

Connect a USB hub to the USB-A port on the PX3. Then plug the
supported USB wireless LAN adapter into the appropriate USB port on
the hub.

See USB Wireless LAN Adapters (on page 23) for a list of supported
wireless LAN adapters.
USB Wireless LAN Adapters
The PX3 supports the following USB Wi-Fi LAN adapters.
Wi-Fi LAN adapters

Supported 802.11
protocols

SparkLAN WUBR-508N

A/B/G/N

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 configurationof your PX3 matches the access point. The following is the wireless LAN
configuration that the PX3 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: Supported 802.11 network protocols vary according to the wireless LAN
adapter being used with the PX3. See USB Wireless LAN Adapters (on page23).
Note: You must configure PX3 to enable its wireless LAN interface. See thetopic titled Configuring Network Settings (on page 253) in the User Guide.

23

Chapter 3: Initial Installation and Configuration

Dual Ethernet Connection
One PX3 device has two Ethernet (LAN) ports:••

ETH 10/100/1000 (marked in green) supports up to 1000 Mbps. This is"ETH1".
ETH 10/100 (marked in white) supports up to 100 Mbps. This is "ETH2".

For more information on the two ports, see Connection Ports (on page 117,
"Connection Port Functions" on page 118).
You can connect both ports to different subnets (networks) and therefore
obtain two IP addresses for wired networking. It is strongly recommended thatyou DO NOT connect both ports to the same subnet to avoid potential issues.
Contact your IT department if you are not sure whether the two Ethernet ports
are connecting to the same or different subnets.
Exception: A USB-cascading chain must connect to "only one" network. Do NOT
connect both Ethernet ports of any PX3 master or slave device to the LAN. See
Cascading Multiple PX3 Devices for Sharing Ethernet Connectivity (on page
34).

•
•

•

Check list when connecting both ports to the networks:
Both Ethernet interfaces are connecting to different subnets.
Both Ethernet interfaces have been enabled. By default both are enabled.
See Device Info (on page 141) and Ethernet Interface Settings (on page257).
Both Ethernet interfaces are configured with proper IPv4 and/or IPv6
settings. See Wired Network Settings (on page 254).
▪

•

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

The cascading mode is disabled. By default it is disabled. See Setting the
Cascading Mode (on page 270).

Configuring the PX3
You can initially configure the PX3 via one of the following:•••

A TCP/IP network that supports DHCP
A mobile device with PDView installed
A computer physically connected to the PX3
Configuration via a DHCP-enabled network:

1.

24

Connect the PX3 to a DHCP IPv4 network. See Connecting the PX3 to Your
Network (on page 22).

Chapter 3: Initial Installation and Configuration

2.

Retrieve the DHCP-assigned IPv4 address. Use the front panel LCD display
to retrieve it. See Device Info (on page 141).

3.

Launch a web browser to configure the PX3. See Login (on page 159).
Configuration via a connected mobile device:1.

Download the PDView app to your mobile device. See Connecting a
Mobile Device to PX3 (on page 25).

2.

Connect the mobile device to PX3 via USB.

3.

Launch PDView to configure the PX3.
Configuration via a connected computer:

1.

Connect the PX3 to a computer. See Connecting the PX3 to a Computer(on page 31).

2.

Use the connected computer to configure the PX3 via the command line or
web interface.
▪

Command line interface: See Initial Network Configuration via CLI (onpage 796).

▪

Web interface: Launch the web browser on the computer, and typethe link-local IP address or pdu.local to access the PX3. See Login (onpage 159).
For link-local IP address retrieval, see Device Info (on page 141).

Tip: To configure a number of PX3 devices quickly, see Bulk Configuration
Methods (on page 33).
Connecting a Mobile Device to PX3Raritan's PDView is a free app that turns your iOS or Android mobile device into
a local display for PX3.
PDView is especially helpful when your PX3 is not connected to the network
but you need to check the PX3 status, retrieve its information, or change its
settings.

•••

Requirements for using PDView:
PX3 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.

25

Chapter 3: Initial Installation and Configuration2.

▪

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

https://play.google.com/store/apps/details?id=com.raritan.android.pd
viewInstall PDView.

Step B: Connect the mobile device to PX3
1.

2.

Get an appropriate USB cable for your mobile device.
▪

iOS: Use the regular USB cable shipped with your iOS mobile device.

▪

Android: Use an USB OTG adapter cable.

Connect the mobile device to the appropriate USB port on the PX3.
▪

iOS: USB-A port.

▪

Android: USB-B port

Step C: Launch PDView to access the PX3
1.

26

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

Chapter 3: Initial Installation and Configurationa.

The "Disconnected" message displays first when PDView has notdetected the PX3 yet.
A diagram in PDView indicates the appropriate USB port your mobile
device should connect according to your mobile operating system.

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

27

Chapter 3: Initial Installation and Configurationb.

2.

The PDView shows the "Connected" message when it detects theconnected PX3.

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

3.

The web interface opens. Now you can view or modify the data of PX3.
▪

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

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

28

Chapter 3: Initial Installation and Configuration

Saving User Credentials for PDView's Automatic Login

When PDView detects PX3 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 admincredentials 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 PX3 so that PDView
does NOT perform the automatic login feature after it is launched.

2.

Launch PDView on your mobile device.

3.

Tap the top-right icon

4.

The user credentials setup page opens.

(iOS) or(Android).

29

Chapter 3: Initial Installation and Configuration

▪

5.

▪

Raritan▪

Legrand▪

ServerTech (Server Technology)

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

30

Per default, three administrator user credentials are pre-configured forthree companies' products:

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

Chapter 3: Initial Installation and Configuration

Connecting the PX3 to a Computer
The PX3 can be connected to a computer for configuration via one of thefollowing ports.
•••

Ethernet port
USB-B port
RS-232 serial port (RJ-45)

Note that the port locations on your models may differ.
•

Zero U models:

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 thecomputer. The PX3 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 PX3
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 either Ethernet portof the PX3.

2.

Connect the other end to a computer's Ethernet port.

3.

On the connected computer, launch a web browser to access the PX3,
using either link-local addressing: pdu.local or 169.254.x.x. See Login (onpage 159).

31

Chapter 3: Initial Installation and Configuration

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

2.

Connect a USB cable between a computer's USB-A port and the USB-B portof PX3.

3.

Perform Initial Network Configuration via CLI (on page 796).
Note: Not all serial-to-USB converters work properly with the PX3 so
Raritan does not introduce the use of such converters.
Serial connection for "RJ-45" RS-232 connector:

1.

Connect the RJ-45 end of the RJ45-to-DB9 adapter cable to the RJ-45 port
labeled CONSOLE / MODEM on PX3.
▪

See RJ45-to-DB9 Cable Requirements for Computer Connections (onpage 32).

2.

Connect the DB9 end to your computer's RS-232 port (COM).

3.

Perform Initial Network Configuration via CLI (on page 796).

RJ45-to-DB9 Cable Requirements for Computer Connections

An RJ45-to-DB9 adapter/cable is required for connecting the PX3 to a computer,
if the use of a USB cable is not wanted.
A third party RJ45-to-DB9 adapter/cable needs to meet the following
requirements.
••

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

32

DB9 pin signal

DB9 pin No.

RJ-45 pin No.

RJ-45 pin signal

CTS

8

1

RTS

DSR

6

2

DTR

RxD

2

3

TxD

GND

5

4

GND

GND

5

5

GND

TxD

3

6

RxD

DTR

4

7

DSR

RTS

7

8

CTS

Chapter 3: Initial Installation and Configuration

DB9 pin signal

DB9 pin No.

DCD

1 (Not connected)

RI

9 (Not connected)

RJ-45 pin No.

RJ-45 pin signal
N/A

Note: The blue Cisco RJ-45 to DB9 adapter cable CANNOT be used forconnecting a modem. See RJ45-to-DB9 Cable Requirements for Modem
Connections (on page 772).

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

••

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

••

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

•

•

Curl command:
Requirement: Two files are required -- one is a configuration file in TXT andthe other is a devices list file in CSV. See config.txt (on page 648) anddevices.csv (on page 650).
Procedure: Upload both files to all of PX3 devices one by one, using theappropriate curl command.
See Upload via Curl (on page 681).

••

SCP or PSCP command:
Requirement: Two files are required -- one is a configuration file in TXT andthe other is a devices list file in CSV.
Procedure: Upload both files to all of PX3 devices one by one, using theappropriate SCP or PSCP command.
See Uploading or Downloading Raw Configuration Data (on page 629).

33

Chapter 3: Initial Installation and Configuration••

A USB flash drive:
Requirement: A FAT32- or supperfloppy-formatted USB flash drive
containing two special configuration files and one devices list file isrequired.
Procedure: Plug this USB drive into the PX3. When a happy smiley is shownon 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 641).

Cascading Multiple PX3 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 408).
You can have multiple PX3 devices share one Ethernet connection by cascadingthem via one of the interfaces below:••

USB interface
Ethernet interface

The first one in the cascade is the master device and all the other devices
follow it in the cascade. Only the master device is physically connected to the
LAN -- wired or wireless.
Each device in the cascade is accessible over the network, with Bridging orPort-Forwarding cascading mode activated on the master device. See Setting
the Cascading Mode (on page 270).
•••

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 thesame 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. DO NOT connect both Ethernet ports to the network(s)unless your network has the R/STP protocol enabled.
Note: The Port Forwarding mode does NOT have this restriction. In thismode, you can enable two wired and one wireless network connections.

34

Chapter 3: Initial Installation and Configuration••

Do NOT connect cascaded devices other than master to the LAN or WLAN.
(WIFI only) You must use Raritan's USB WIFI wireless LAN adapter insteadof 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 790).
Cascading All Devices via USB
You must set the cascading mode before establishing the chain. See Setting the
Cascading Mode (on page 270).
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 PX3 devices cascaded via USB.

35

Chapter 3: Initial Installation and Configuration

NumberDevice role
Master device
Slave 1
Slave 2
Slave 3

To cascade PX3 devices via USB:
1.

Make sure all Raritan devices are running firmware version 3.3.10 or later.

2.

Choose the appropriate one as the master device.
▪

3.

When the Port Forwarding mode over "wireless LAN" is intended, themaster device must be a Raritan product with two USB-A ports, suchas PX3, Smart Rack Controller, EMX2-888, PX3TS or BCM2.

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

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 surethe cascading role and downstream interface are also set correctly.

See Setting the Cascading Mode (on page 270).
4.

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

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

5.

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

6.

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

7.

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

8.

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

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.

▪

36

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

Chapter 3: Initial Installation and Configuration

A tip for USB cascading:
The "USB-cascading" chain can be a combination of diverse Raritan productsthat support the USB-cascading feature, including PX3, PXC, Smart Rack
Controller, transfer switch, PX2, BCM and EMX.

37

Chapter 3: Initial Installation and Configuration

Extended Cascading with PX3 Devices
PX3 supports cascading via either Ethernet or USB ports. This is because they
have "two" Ethernet ports.
You can use either Ethernet port on the PX3 PDU for cascading.
You must set the cascading mode before establishing the chain. See Setting the
Cascading Mode (on page 270).
Both cascading modes support a maximum of 16 devices in a chain.
When establishing a Port-Forwarding chain, make sure you follow theguidelines described in the section titled Restrictions of Port-Forwarding
Connections (on page 41).
You can mix Ethernet and USB cascading in the PX3 PDU chain if preferred. The
following diagram illustrates such a chain.
The distance between two Ethernet-cascaded devices can be up to 100 meters,
while the distance between two USB-cascaded devices supports up to 5 meters
only.

38

Chapter 3: Initial Installation and Configuration

NumberDevice role
Master device
Slave 1
Slave 2
Slave 339

Chapter 3: Initial Installation and Configuration

For instructions on USB cascading, see Cascading All Devices via USB (on page
35).

•
•

Suggestions for extended cascading:
Ethernet cascading is recommended because of the longer distance, lower
latency and more reliable connection it supports.
The "green" ETH1 port (ETH 10/100/1000) on a Raritan master device isrecommended for network connection because it supports up to 1000
Mbps.
To cascade PX3 PDUs via Ethernet ports:

1.

Make sure all Raritan devices are running firmware version 3.3.10 or later.

2.

Choose one PX3 as the master device.

3.

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

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 surethe cascading role and downstream interface are also set correctly.

See Setting the Cascading Mode (on page 270).
4.

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

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

5.

Connect the available Ethernet port of the master device to either
Ethernet port of another PX3 via a standard network patch cable. Thisadditional PX3 device is Slave 1.

6.

Connect Slave 1's available Ethernet port to either Ethernet port ofanother PX3 via a standard network patch cable. The second additional
device is Slave 2.

7.

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

8.

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

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.

▪

40

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

Chapter 3: Initial Installation and Configuration

Recommendations for cascade loops:
You can connect both the first and the last PDU to your network (cascadeloop) under the following conditions:a.

The remaining network MUST use R/STP to avoid network loops.
AND
Both the first and the last PDUs MUST either attach to the same switch or,if they are attached to two separate switches, you must configure both
ports of these switches so that the STP costs are high. This prevents the
STP protocol from sending unrelated traffic through the PDU cascade,which can cause bottlenecks that lead to connectivity issues in the wholenetwork.

Restrictions of Port-Forwarding Connections
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. That is, NO simultaneousconnection of USB and Ethernet cables between two cascaded devices.

The following diagrams illustrate cascading connections that are NOT
supported.

•

UNSUPPORTED connections:
One cascaded device has two upstream devices via Ethernet cables.

41

Chapter 3: Initial Installation and Configuration

42•

One cascaded device has two upstream devices via Ethernet and USB
cables.

•

One cascaded device has two downstream devices.

Chapter 3: Initial Installation and Configuration•

One device is connected to another device via two cascading cables - USB
and Ethernet cables.

Power-Sharing Restrictions and Connection
Two PX3 devices can share power supply to their controllers via EXPANSION
ports, so that when either PX3 controller fails to receive DC 12V power from its
inlet(s), it continues to receive backup power from another PX3 device whichfunctions properly and therefore remains to be accessible to users.
For documentation purpose, the term "power-sharing mode" is used todescribe the status when the 12V power supply from the inlet to a PX3
controller fails, causing that controller to receive power from another PX3
device.
Before making a power-sharing connection, first read Power-Sharing
Configurations and Restrictions (on page 45), and remove unsupported
equipment from BOTH PX3 PDUs.
After a PDU enters the power-sharing mode, some of its data/operations
remain to be available while other data/operations are no longer available.

•

Unavailable data or operations on the PDU that enters the power-sharingmode:
All outlets lose power, and enter the "disabled" state.
▪

No outlet switching can be performed if the PX3 is an outlet-switchingcapable PDU.

43

Chapter 3: Initial Installation and Configuration•

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

••

Communications with relay/meter boards are lost. Therefore, firmware
upgrade may fail due to this reason.
Available data or operations on the PDU that enters the power-sharing
mode:
Change software settings, such as customizing names, modifying network
settings, configuring thresholds, and so on.
Note: Outlet switching is not available because all outlets lose power.

•••

Monitor the status of connected Raritan environmental sensor packages,
or configure/control their settings.
Operate the front panel display.
Events that occur when entering the power-sharing mode:
The 12V power supply sensor enters the fault state. See +12V Power
Supply Sensor (on page 186).
Tip: You can set an event rule for sending a notification when this sensor
enters the fault state. See Event Rules and Actions (on page 316).

••

The above event is logged in the internal event log. See Default Log
Messages (on page 322).
To find whether a PX3 has entered the power-sharing mode:
Check the state of its +12V power supply sensor.

Tip: For SNMP, the sensor type for this +12V power supply is i1smpsStatus (46).
Making a Power-Sharing Connection
Make sure BOTH PX3 devices comply with the configuration limitations whenestablishing a power-sharing connection. See Power-Sharing Configurations
and Restrictions (on page 45).
The supported maximum power-sharing distance is 2 meters.
Make a power-sharing connection:
1.

Get a standard network patch cable (Cat5e/6), which can be up to 2
meters long.
▪

2.

Connect one end to a PX3 device's EXPANSION port, and the other end toanother one's EXPANSION port.
▪

44

Do NOT use a crossover cable.

Note that the EXPANSION port location on your PX3 may differ fromthe following images.

Chapter 3: Initial Installation and Configuration

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

•

Configuration limitations on "both" PDUs:
NO USB wireless LAN adapter is connected.
That is, you have to connect both PDUs to a "wired" network if LAN accessis wanted.

•••

No asset management strips can be connected simultaneously.
The maximum number of DX environmental sensor packages or door
handles that can be connected decreases. For details, see Supported
Sensor Configurations for Power Sharing (on page 46).
After either PDU enters the power-sharing mode, you must NOT physicallyremove or add any environmental sensor packages to BOTH PDUs.

45

Chapter 3: Initial Installation and Configuration

Supported Sensor Configurations for Power Sharing
All information and restrictions described in this section apply to BOTH PDUs
involved in the power-sharing configuration, unless otherwise specified.
•

•

•

•

There are no limitations for connecting Raritan's DPX or DPX2
environmental sensor packages to an iX7™ PDU in the power-sharing mode.
See DPX Sensor Packages (on page 57) or DPX2 Sensor Packages (on page54).
The maximum number of supported DPX3 environmental sensor packages
remains unchanged -- that is, 12 DPX3 packages. See DPX3 Sensor
Packages (on page 52).
The maximum number of supported DX environmental sensor packages
also remains unchanged as long as the DPX3-ENVHUB4 sensor hub is not
used -- that is, 12 DX sensor packages. See DX Sensor Packages (on page51).
The maximum number of supported DX2 environmental sensor packages
remains unchanged -- that is, 12 DX2 packages. See DX2 Sensor Packages(on page 49).

However, there are DX restrictions when DPX3-ENVHUB4 is used, and there arealso door handles-related restrictions.

••

DX sensor restrictions while DPX3-ENVHUB4 is involved:
A maximum of one DPX3-ENVHUB4 and a maximum of 10 DX sensor
packages are supported.
Door handle connection restrictions (via DX2-DH2C2 or DX-PD2C5):(Restriction only for DX2-DH2C2 manufactured before 2019) DO NOT
connect any "SouthCo H3-EM series" door handle(s) because of insufficient
power supply in the power-sharing mode.
Note: The latest generation of DX2-DH2C2 does NOT have this restriction
and can have SouthCo H3-EM series connected in the power-sharing mode.

••

A maximum of 2 door handles connected to a maximum of one
DX2-DH2C2 or one DX-PD2C5 package are supported.
All of the 2 door handles must be controlled by the same PDU so that you
can have "only one" handle opened at a time to avoid critical power
consumption. That is, ALL door handles must be connected to only one
PDU in the power-sharing connection, NOT both PDUs.
Note: It is strongly suggested to check and make sure the upper limit of"powered cry contact actuators" is set to 1 when making a power-sharing
connection. See Peripherals (on page 202).

46

Chapter 3: Initial Installation and Configuration

Other sensor restrictions when door handles are present:
First make sure the connection of door handles complies with the above
restrictions.
The following restrictions apply only to the PDU that has all the door handles
connected.
•••

When there are 2 door handles connected to the PDU (via DX2-DH2C2 or
DX-PD2C5), up to 10 sensor packages of DPX/DPX2/DPX3/DX2 or up to 2
additional DX sensor packages can be additionally connected. Raritan's
sensor hubs must NOT be used.
When there is only 1 handle connected, up to 12 sensor packages of
DPX/DPX2/DPX3/DX2 or up to 3 DX sensor packages can be additionallyconnected. Raritan's sensor hubs must NOT be used.
NO physical changes made to the number of connected sensor packages:
After either PDU enters the power-sharing mode, you must NOT physicallyremove or add any environmental sensor packages to BOTH PDUs.
Warning: The in-rush current of a newly added sensor package may cause
both PDUs to reboot.

For information on Raritan's sensor packages or hubs, see Connecting Raritan
Environmental Sensor Packages (on page 48).

47

Chapter 4

Connecting External Equipment(Optional)More features are available if you connect Raritan's or third-party external
equipment to your PX3.

In This Chapter
Connecting Raritan Environmental Sensor Packages .........................................48
Connecting Asset Management Strips ................................................................68
Connecting a Logitech Webcam .........................................................................78
Connecting a GSM Modem .................................................................................79
Connecting an Analog Modem ...........................................................................79
Connecting an External Beeper ..........................................................................80
Connecting a Schroff LHX/SHX Heat Exchanger..................................................80
Connecting a Modbus RTU Device or Bus...........................................................81

Connecting Raritan Environmental Sensor Packages
PX3 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 combinationof sensors and actuators.
PX3 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 49)
DX Sensor Packages (on page 51)
DPX3 Sensor Packages (on page 52)
DPX2 Sensor Packages (on page 54)
DPX Sensor Packages (on page 57)

48

Chapter 4: Connecting External Equipment (Optional)

Identifying the Sensor Port
Warning: If you purchase Raritan's environmental sensor packages, makesure you connect them to the correct port on the PX3, or damages may becaused to PX3 and/or connected sensor packages.

••

How to identify the SENSOR port:
The correct port is labeled SENSOR.
The SENSOR port is marked with YELLOW color, as shown below.

DX2 Sensor Packages
You can cascade up to 12 DX2 sensor packages.
When cascading DX2, remember that the PX3 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 PX3.
Tip: To manage the last several sensors/actuators after 32nd function, you canrelease some "managed" sensors or actuators, and then manually bring the last
several sensors/actuators into management. See Peripherals (on page 202).

Numbers

Components
RJ-45 ports, each of which is located on either
end of a DX2 sensor package.
LED, which indicates the sensor package's
status49

Chapter 4: Connecting External Equipment (Optional)

Connect DX2 to the PX3:
1.

Connect a standard network patch cable (CAT5e or higher) to either RJ-45
port on a DX2 sensor package.

2.

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 priorDX2 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.
Exception: You CANNOT cascade DX2-DH2C2 packages. A PX3 supports
only one DX2-DH2C2.

3.

Connect the first DX2 sensor package to the PX3 by plugging its cable's
connector into the RJ-45 SENSOR port of the PX3.

4.

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

Warning: DX2-DH2C2 and asset management strip(s) are mutually exclusive
so do NOT connect both of them to the PX3 simultaneously.

50

Chapter 4: Connecting External Equipment (Optional)

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 OnlineHelp) 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 PX3 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 PX3.
For example, if you cascade 12 DX packages, and each package contains 3
functions (a function is a sensor or actuator), the PX3 does NOT manage thelast 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 canrelease some "managed" sensors or actuators, and then manually bring the last
several sensors/actuators into management. See Peripherals (on page 202).

Numbers

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

Connect DX to the PX3:
1.

Connect a standard network patch cable (CAT5e or higher) to either RJ-45
port on a DX sensor package.

2.

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.

51

Chapter 4: Connecting External Equipment (Optional)

Exception: You CANNOT cascade DX-PD2C5 sensor packages. One PX3
supports only one DX-PD2C5.

3.

Connect the first DX sensor package to the PX3 by plugging its cable's
connector into the RJ-45 SENSOR port of the PX3.

4.

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

Warning: DX-PD2C5 or DX2-DH2C2, and asset management strip(s) aremutually exclusive so do NOT connect both of them to the PDU
simultaneously.

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.

Numbers

Components
RJ-45 ports, each of which is located oneither end of a DPX3 sensor package.
LED for indicating the sensor status.

To connect DPX3 to the PX3:

52

1.

Connect a standard network patch cable (CAT5e or higher) to either RJ-45
port on the DPX3 sensor package.

2.

If you want to cascade DPX3 sensor packages, get an additional standard
network patch cable (CAT5e or higher) and then:Chapter 4: Connecting External Equipment (Optional)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.

3.

Connect the first DPX3 sensor package to the PX3 by plugging its cable's
connector into the RJ-45 SENSOR port of the PX3.

4.

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

53

Chapter 4: Connecting External Equipment (Optional)

DPX2 Sensor Packages
A DPX2 sensor cable is shipped with a DPX2 sensor package. This cable is madeup of one RJ-12 connector and one to three head connectors. You have toconnect 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/).

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

54Chapter 4: Connecting External Equipment (Optional)

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 thefinal sensor package with a DPX2 sensor package.
To connect DPX2 to the PX3:
1.

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

2.

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

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

Use an RJ-12 to RJ-45 adapter to connect the DPX2 sensor package(s) to
the PX3.
a.

Connect the adapter's RJ-12 connector to the DPX2 sensor cable.

b.

Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of
the PX3.

55

Chapter 4: Connecting External Equipment (Optional)

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 56).
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 forconnecting DPX2 to the final DX2, DX or DPX3 in the chain.
The maximum number of DX2, DX or DPX3 sensor packages in the chain mustbe 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.

When connecting a DPX2 sensor package containing "two" DPX2 sensors:
A maximum of ten DX sensor packages can be cascaded because 12-2=10.

When connecting a DPX2 sensor package containing "one" DPX2 sensor:
A maximum of eleven DX sensor packages can be cascaded because
12-1=11.

56

Chapter 4: Connecting External Equipment (Optional)

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

For the cabling length restrictions, see Supported Maximum DPX Sensor
Distances (on page 61).
Warning: For proper operation, wait for 15-30 seconds between eachconnection operation or each disconnection operation of environmental
sensor packages.
To directly connect a DPX with a factory-installed sensor cable:
An RJ-12 to RJ-45 adapter is required to connect a DPX sensor package to PX3.
a.

Connect the adapter's RJ-12 connector to the DPX sensor cable.

b.

Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of
the PX3.

To directly connect a differential air pressure sensor:
1.

Connect a Raritan-provided phone cable to the IN port of a differential airpressure sensor.

2.

Get an RJ-12 to RJ-45 adapter. Connect the adapter's RJ-12 connector tothe other end of the phone cable.

3.

Connect this adapter's RJ-45 connector to the RJ-45 SENSOR port on the
PX3.

57

Chapter 4: Connecting External Equipment (Optional)

4.

If intended, connect one DPX sensor package to the OUT port of thedifferential air pressure sensor. It can be any DPX sensor package, such as a
DPX-T3H1.

The PX3
Raritan differential air pressure sensors
One DPX sensor package (optional)
RJ-12 to RJ-45 adapter

Using an Optional DPX-ENVHUB4 Sensor Hub

Optionally, you can connect a Raritan DPX-ENVHUB4 sensor hub to the PX3.
This allows you to connect up to four DPX sensor packages to the PX3 via thehub.
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 PX3.
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 62).
To connect DPX sensor packages via the DPX-ENVHUB4 hub:
1.

2.

58

Connect the DPX-ENVHUB4 sensor hub to the PX3.
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.

Get an RJ-12 to RJ-45 adapter. Connect this adapter's RJ-12 connector
to the other end of the phone cable.

c.

Connect this adapter's RJ-45 connector to the PDU's RJ-45 SENSOR
port.

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

Chapter 4: Connecting External Equipment (Optional)

This diagram illustrates a configuration with a sensor hub connected.

PX3
RJ-12 to RJ-45 adapter
Raritan-provided phone cable
DPX-ENVHUB4 sensor hub
DPX sensor packages

Using an Optional DPX-ENVHUB2 cable

A Raritan DPX-ENVHUB2 cable doubles the number of connectedenvironmental 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.

Use an RJ-12 to RJ-45 adapter to connect the DPX-ENVHUB2 cable to PX3.
a.

Connect the adapter's RJ-12 connector to the cable.

b.

Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port on
the PX3.

59

Chapter 4: Connecting External Equipment (Optional)

60

2.

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

3.

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

Chapter 4: Connecting External Equipment (Optional)

Supported Maximum DPX Sensor Distances

When connecting the following DPX sensor packages to the PX3, 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 PX3 using the sensor cable
pre-installed (or provided) by Raritan. You MUST NOT extend or modify thesensor 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 PX3
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 PX3 via a sensor hub.
•The sum of a DPX-T3H1 sensor cable's length is 16 feet (5 meters).

•

The total cabling length between the PX3 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.

PX333' (10 m)
cable

1 sensor hub

16' (5 m)cable

Up to 4 DPX-T3H1
sensor packages

61

Chapter 4: Connecting External Equipment (Optional)

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 PX3, except for the following differences:••

All ports on the DPX3-ENVHUB4 sensor hub are RJ-45 instead of RJ-12 asthe 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 63).
To connect Raritan sensor packages via the DPX3-ENVHUB4 hub:1.

2.

Connect the DPX3-ENVHUB4 sensor hub to the PX3 using a standard
network patch cable (CAT5e or higher).
a.

Plug one end of the cable into the IN port (Port 1) of the hub.

b.

Plug the other end of the cable into the RJ-45 SENSOR port of the PX3.

Connect the Raritan sensor packages to any of the four OUT ports on thehub.
▪

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.

PX3

62

Chapter 4: Connecting External Equipment (Optional)

A standard network cable
DPX3-ENVHUB4 sensor hub
Any Raritan sensor packages

Mixing Diverse Sensor Types
You can mix diverse sensor packages on one PX3 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 PX3 only supports a
maximum of 32 sensors/actuators.
PX3 does NOT support any other sensor-mixing combinations than thosedescribed in this section.
In most illustrations below, any DX or DPX3 sensor package can be replacedwith 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).

63Chapter 4: Connecting External Equipment (Optional)

•

•

64

1 DX + 1 DPX:
It is strongly recommended to use an RJ-12 to RJ-45 adapter to connect the
DPX sensor package to the DX sensor package.

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 thefollowing:▪

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

Chapter 4: Connecting External Equipment (Optional)••

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.

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

65

Chapter 4: Connecting External Equipment (Optional)

66

Chapter 4: Connecting External Equipment (Optional)

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.

67

Chapter 4: Connecting External Equipment (Optional)

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

Connecting Asset Management Strips
You can remotely track the locations of up to 64 IT devices in the rack byconnecting asset management strips (asset strips) to the PX3 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 PX3.
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.
Warning: DX-PD2C5 or DX2-DH2C2, and asset management strip(s) aremutually exclusive so do NOT connect both of them to the PDU
simultaneously.

68

Chapter 4: Connecting External Equipment (Optional)

Combining Regular Asset Strips
Each tag port on the regular asset strips corresponds to a rack unit and can beused 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.

8U MASTER asset strip with 8 tag ports
8U SLAVE asset strip with 8 tag ports
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.
▪

Plug the white male DIN connector of the slave strip into the whitefemale DIN connector of the master strip.

69

Chapter 4: Connecting External Equipment (Optional)▪

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.

2.

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

3.

Repeat the above step to connect more slave strips. The length of theasset strip assembly can be up to 64U.
▪

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

▪

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

4.

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

5.

The asset strips are automatically attracted to the rack because ofmagnetic stripes on the back.

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

70

Chapter 4: Connecting External Equipment (Optional)

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 PX3, and the asset tag transmits the ID andpositioning information to the asset strip.
The following diagram illustrates an asset tag. Note that there are two types ofasset tags: non-programmable and programmable tags. The only difference isthat 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.

Barcode (ID number), which is available on either
end of the "non-programmable" asset tagA

Tag connector

B

Adhesive area with the tapeC

Note: The barcode of each "non-programmable" asset tag is unique and isdisplayed in the PX3 device's web interface for identification.
Connecting Regular Asset Strips to PX3
The cabling distance between an asset strip assembly and the PX3 can be up to
10 meters.
To connect regular asset strips to the PX3 device: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 theasset strip.

3.

Connect the asset strip assembly to the PX3 device, using a network patch
cable (CAT5e or higher).
▪

Connect one end of the cable to the RJ-45 connector on the MASTER
asset strip.

▪

Connect the other end of the cable to the FEATURE port on the PX3
device.

71

Chapter 4: Connecting External Equipment (Optional)

The PX3 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
PX3. 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.

72

(A)

MASTER asset strip(B)

Asset tags(C)

IT devices

(D)

PX3

Chapter 4: Connecting External Equipment (Optional)

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 orcomposite 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
B
C

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

Note: A tag connector cable has a unique barcode, which is displayed in the PX3
device's web interface for identifying each blade extension strip where it isconnected.
Blade extension strip with 16 tag ports

73

Chapter 4: Connecting External Equipment (Optional)

Mylar section with the adhesive tapeD

Tag ports

E

Cable socket(s) for connecting the tag
connector cableF

Note: Each tag port on the blade extension strip is labeled a number, which isdisplayed as the slot number in the PX3 device's web interface.
To install a blade extension strip:
1.

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

2.

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 theadhesive tape in the back of the mylar section to help fix the strip in place.

3.

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

74

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

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

Chapter 4: Connecting External Equipment (Optional)b.

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

4.

Repeat the above step until all blade servers in the chassis are connectedto the blade extension strip via asset tags.

5.

Plug the tag connector of the blade extension strip into the closest tag portof the regular or composite asset strip on the rack.

6.

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 theasset strip, wait at least 1 second before re-connecting it back, or the PX3
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.

75

Chapter 4: Connecting External Equipment (Optional)

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.

Two RJ-45 connectors

A

Tag ports

B

Important: DO NOT hot swap or hot plug any AMS-Mx-Z in a composite asset
strip chain after connecting the chain to the PX3 device. Doing so may cause
the device's FEATURE port to malfunction.
To connect composite asset strips to the PX3 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 PX3 device. In this case, go to step 2. If there are morethan 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 77) for the
maximum number of composite asset strips supported per chain.

Note: Different types of composite asset strips can be mixed in a chain.
2.

Connect the composite asset strip(s) to the PX3 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 thecomposite asset strip.
▪

b.

76

For a composite asset strip chain, connect the cable to the "Input"
port of the first asset strip.

Connect the other end of the cable to the FEATURE port on the PX3
device.

Chapter 4: Connecting External Equipment (Optional)

3.

Affix an asset tag to the IT device. Then connect this asset tag to thecomposite asset strip by plugging the tag connector into the tag port on
the composite asset strip. For details, see Connecting Regular Asset Strips
to PX3 (on page 71).

4.

(Optional) For a chain, it is highly recommended using the cable ties tohelp hold the weight of all connecting cables.

5.

Repeat Step 3 to connect IT devices to the other composite asset strips inthe 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.
It is NOT supported to hot swap or hot plug any AMS-Mx-Z in a composite
asset strip chain that has been connected to Raritan's PDU, SRC, or PMC.
Therefore, first disconnect the chain from the device when you need toswap or add any AMS-Mx-Z to the chain.

Raritan devices

Maximum strips per chain

EMX2-111,

Up to 4 composite asset strips aresupported.

PX2 PDUs,
BCM1 (NOT BCM2 series)
Smart Rack Controller,
EMX2-888,

Up to 6 composite asset strips aresupported.

PX3 PDUs,

77

Chapter 4: Connecting External Equipment (Optional)

Raritan devices
PX3TS transfer switches

Maximum strips per chain

PMC (BCM2 series)
Note: In case you hot swap or hot plug any AMS-Mx-Z in a chain, causing the
FEATURE port of the PX3 to malfunction, you can power cycle or reset the PX3
to restore the FEATURE port.

Connecting a Logitech Webcam
Connect webcams to PX3 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 PX3 supports up to two webcams. After connecting a webcam, you canretrieve visual information from anywhere through the PX3 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 PX3. The PX3 automaticallydetects 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
PX3 web interface after the connection is complete. See Configuring Webcams
and Viewing Live Images (on page 427).

78

Chapter 4: Connecting External Equipment (Optional)

Connecting a GSM Modem
The following Cinterion® GSM modems can be connected to the PX3 in order tosend SMS messages containing event information.
•••

MC52iT
MC55iT
EHS6T

See Available Actions (on page 334) for more information on SMS messages.
Note: PX3 cannot receive SMS messages.
To connect the GSM modem:
1.

Connect the GSM modem to the serial port labeled CONSOLE / MODEM on
the PX3.
▪

A third party RJ-45 to "DB9 male" adapter/cable is required for thisconnection. See RJ45-to-DB9 Cable Requirements for Modem
Connections (on page 772).

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 PX3 to specify the modem's SIM
PIN number and the recipient phone number. See Configuring the SerialPort (on page 387).

Connecting an Analog Modem
The PX3 supports remote dial-in communications to access the CLI through ananalog modem. This dial-in feature provides an additional alternative to accessthe PX3 when the LAN access is not available. To dial in to the PX3, the remotecomputer must have a modem connected and dial the correct phone number.
Below are the analog modems that the PX3 supports for sure:••

NETCOMM IG6000 Industrial Grade SmartModem
US Robotics 56K modem

The PX3 may also support other analog modems which Raritan did not test.
Note that the PX3 does NOT support dial-out or dial-back operations via themodem.
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 PX3.

79

Chapter 4: Connecting External Equipment (Optional)▪

A third party RJ-45 to "DB9 male" adapter/cable is required for thisconnection. See RJ45-to-DB9 Cable Requirements for Modem
Connections (on page 772).

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

Connecting an External Beeper
The PX3 supports the use of an external beeper for audio alarms.
External beepers that are supported include but may not be limited to thefollowing:•

Mallory Sonalert MODEL SNP2R

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

Connect a standard network patch cable to the FEATURE port of the PX3.

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 fromthe PX3.

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 PX3 device, you must establish a connection
between the heat exchanger and the PX3 device.
For more information on the LHX/SHX heat exchanger, refer to the user
documentation accompanying that product.
To establish a connection between the PX3 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 PX3
device.

To enable the support of the LHX/SHX heat exchanger, see Miscellaneous (onpage 394).

80

Chapter 4: Connecting External Equipment (Optional)

Connecting a Modbus RTU Device or Bus
If connecting the Modbus RTU devices to PX3 and enabling the Modbus
Gateway feature, the Modbus TCP clients on your network will be able tocommunicate with those Modbus RTU devices attached to PX3.
To use the Modbus Gateway feature:
1.

2.

•

Connect a Modbus RTU device, or a Modbus bus with multiple RTU devices,to the PX3 via two adapters described below.
a.

Connect an isolated RS485-to-RS232 adapter to the Modbus RTU
device or Modbus bus.

b.

Connect an RS232-to-USB adapter (using FTDI's FT232 chip) to theRS485-to-RS232 adapter.

c.

Connect the RS232-to-USB adapter to the USB-A port on the PX3.

On the PX3, enable and properly configure the Modbus Gateway feature.
See Changing Modbus Settings (on page 285).
Communications between Modbus TCP and RTU devices:
The PX3 acts only as a message gateway for the Modbus TCP client.
Messages from the Modbus TCP client(s) are passed through the PX3 to theconnected Modbus RTU devices or Modbus bus.

•

The Modbus RTU devices on the bus are identified with their Modbus RTU
addresses using the Modbus unit identifier addresses in the Modbus TCP
protocol.
If the Modbus TCP client does not support unit identifier addressing, refer
to Changing Modbus Settings (on page 285).

•

The PX3 supports communications to multiple Modbus RTU devices. Notethat the connected Modbus RTU devices are invisible to the PX3.

81

Chapter 5

PDU Linking
The PDU Linking feature allows the linking configuration of a single master PDU
unit to multiple link units for faster and more efficient power management.
Only one master unit is connected to the network in PDU Linking, which allows
a cost-efficient PDU operation and networking infrastructure.
The master PDU is the first PDU in the chain with up to seven link units
connected in sequence in the chain. The master PDU has full knowledge of thelocation of the connected link units in the chain, as well as the power andenvironmental information of all link units.
When you create a master and link configuration in a chain, you log in to themaster unit with visibility to control both the master unit and the connected
link units from within the GUI, SNMP, and CLI.
The PDU Linking feature also allows the Raritan cascading technology, whichenables multiple PDUs to share network connectivity by cascading themthrough the USB or Ethernet interface.
The administrator privilege is required for all management actions (adding,configuring, releasing) of the PDU Linking feature. Each PDU in the chain can bemonitored and managed from anywhere by the network protocols HTTP(S),
SNMP, SSH, Telnet, and Modbus.
All units in the linked chain should be the same model PDU. All units must run
the same firmware version, which can be upgraded respectively for each unit in
the chain.

In This Chapter
FAQs ....................................................................................................................83
PDU Linking in the Web GUI ...............................................................................85
Displays for Master and Link Units ...................................................................111
PDU Linking in the CLI .......................................................................................113

82

Chapter 5: PDU Linking

FAQs
What’s the difference between a "master unit" and a "link unit"?
Master and link units are the same model PDUs that are equal to each other,and each has its own IP address. You designate a PDU as the master unit bylogging into the unit and then adding a link unit. The first unit becomes themaster, and when the first link unit is added, the master unit is automaticallyassigned PDU ID "1", which is reserved to identify a master unit only, and the ID"1" cannot be edited. A connection between the master and the link unit has
now occurred and the chain is formed.
As you continue to add link units to the chain as desired (up to seven link units),
you select Link ID "2" through "8" for the Link ID numbers. (PDU ID "1" wasreserved for the master). Note that the Link ID "2-8" is the sequential numberof each link unit that you select as you add the unit to the chain, and once
selected, the Link ID cannot be edited.
When the chain is established with a single master unit, and one or more linkunits, communication occurs with the master unit through its IP address. The
master unit, in turn, communicates to the other link units in the chain throughtheir individual IP addresses, which optimizes power monitoring and PDU
management.
Which Raritan PDUs can be linked?
With network connectivity, PDU Linking supports these Raritan products whenformed in a linked chain: PX3 with iX7 main controller and PX3TS with iX7 main
controller. All devices in the chain should be the same models.
Can master units be linked together?
No. Once a unit is designated as the master unit in a chain, it cannot be linked
to a master unit in another chain. A master unit can only be linked to one ormore link units in a chain.
How many units can be linked?
Including the master, a full chain can include a total of eight units. The first unit
added is designated as the master unit with the ID "1". Each unit you then add
to the chain is designated as a link unit, beginning with ID "2" and ending with
ID "8".
What is re-linking?
Re-linking is a required function when a link unit no longer recognizes or
responds to the master unit, most likely caused if the link unit was reset tofactory defaults. The status of the disassociated link unit will be displayed as"Access Denied". Selecting the link unit when in this status displays the Re-linkbutton that allows reconnection of the link unit in the chain for regaining
device control.

83

Chapter 5: PDU Linking

Note: Re-linking uses the same Link Unit ID and hostname, but you will need toreauthenticate with your login credentials.
What user privileges are required for managing the PDU Linking
configuration?
Administrative privileges are required for both the master unit and link unit. To
add a link, your administrative login account is required, but after that you only
log in to the master to manage the chain, as all link units in the chain are visible
in the user interface from the master unit view.
What happens if the connection is lost between the master and linkunits?
If the network connection is lost, these link unit functions will still work:
1.

energy accumulation2.

local display (regular metering values and alerts of raised thresholds)

3.

maintained outlet states

and these link unit functions will stop working:1.

event log entries are lost2.

event engine rules/alarms

3.

remote access to the link unit

4.

synchronization of master settings and time when not using NTPWhich system areas of the master and link units are automaticallysynchronized?

The master PDU periodically checks link unit reachability. You can define rules
to be alerted when communication with a link unit fails, such as a system alarm.
Some link unit settings are automatically synchronized with the master:84

1.

Peripheral device settings

2.

Front panel privileges and default view3.

USB host port lockdown

4.

Time and date settings

5.

General data logging settings

Chapter 5: PDU Linking

How are firmware updates handled?
Uploaded firmware images in the GUI are automatically distributed to all linkunits at the same time. Starting a firmware update requires the same image to
be uploaded to all units.
Does PDU Linking support mass deployment of PDUs?
Yes, mass deployment has been extended to support a setup for the PDU
Linking feature (multi-IP or single-IP) via the Raritan Mass Deployment Utility,
which provides the Excel spreadsheet process used for PDU bulk configuration.
For information about using the utility, see Configuration or Firmware
Upgrade with a USB Drive (on page 641).
Which network setup modes are supported by PDU Linking?
For the underlying network, the PDU Linking feature can use the typical
network setup modes:
Independent PDU Setup: All PDUs have their own regular IP address. They
don't need to be in a physical chain to be logically chained. You communicate
only to the master using its normal IP address. Configure networking of theunits, and then add link units using the Web GUI, CLI, or USB.
Bridged Setup: Same as Independent PDU Setup, but the PDUs are physicallyconnected as a chain, either by ethernet or USB. The configuration steps are
the same as with Independent PDU Setup.
Port Forwarding Cascade: The PDUs are physically connected as a chain (either
by Ethernet or USB). Only the first master PDU is connected to your networkwith the IP address you assigned. The other PDUs will get
automatically-assigned private IP addresses which are not visible; you canconfigure both PDUs at one time with a USB stick, or configure the network
first and then add link units.
Note: When referring to "cascading", or the physical chaining of units, although
the mixing of connection types (Ethernet and USB) is not recommended in the
cascade, the mixing is possible with these restrictions: In Port Forwarding mode,
you must build a single, linear chain where each unit has exactly one upstream
device and optionally one downstream device. In Bridging mode, you must notbuild any loops; in other words, multiple paths between two units.

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

85

Chapter 5: PDU Linking

Designating the Master Unit
Log in to the PDU you want to designate as the master unit. When you add thefirst link unit, a chain is established between the master and the new link, andthe master becomes ID "1".
To view and manage a link chain, log in to the master unit, as displayed on the
PDU page:

The PDU page displays the following information about the master PDU:
1.

Firmware version

2.

Model

3.

Serial number

4.

MAC address

5.

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

86Chapter 5: PDU Linking

Adding a Link Unit
A link unit (up to seven units) can be added to a single master unit.
On the PDU page, the master unit is displayed as highlighted in the following
screen example in red. Note the following section "Link PDUs", designed for the
PDU Linking feature, where multiple PDUs added to the chain are displayed as
the link units. The Add Link PDU button, highlighted in green in the screen
example, also displays in the Link PDUs section.

87

Chapter 5: PDU Linking

To add a link unit:
Log in to the master PDU as shown displayed above in the PDU page.
Click Add Link PDU. The following add box displays:

88

1.

The Link ID is populated as the next available ID number (2-8), assigned
sequentially as each link unit is added to the chain to identify the link unit
in the user interfaces. Note: From the drop-down, you can manually selectthe desired Link ID to order the link units in the chain as desired. Onceassociated with a link unit, the Link ID cannot be edited.

2.

Provide the IP address of the link unit.

3.

Provide the login credentials for the link unit. Note: If the link unit has
factory settings, you will be prompted to set the new password.

4.

Click Add.

Chapter 5: PDU Linking

The new link unit is added on the PDU page with the master unit, in a list in the
Link PDUs section. All link units added to the chain in this way are now
managed by the single master unit.

The PDU page displays the following information about the link unit:••••

Link ID
Host/IP address
Communication status
Firmware version

89

Chapter 5: PDU Linking

About the Link ID

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

Master Units Manage Link Units
The master unit manages the following functions for the entire chain of linked
units:
•
•

•

•
•

90

User management and authentication – configured only on the master.
Date and time – the master synchronizes its date and time settings to linkunits. If NTP is not used, then the synchronization interval is every 10
minutes.
Device settings – only the master device settings are configurable, except
for Network Settings. Some settings will be synced to link units. The serial
port is configurable for the master only; link units use the console.
Data model settings – such as outlet names, thresholds, peripherals, etc.,
are configured on the master and stored on link units.
Lua scripts – Communication with link units in a Lua script is possible.

Chapter 5: PDU Linking

Releasing a Link Unit
Releasing a link unit means the unit is separated from the chain and the unit
then becomes standalone. The master unit no longer has access to the released
link unit.
Note: If a release action is attempted on a link unit when the unit is an
unreachable state, a warning message displays, and the master will notrecognize the link unit. A factory reset will be required on the link unit.

91Chapter 5: PDU Linking

To release a link unit:
From the PDU page, in the Link PDUs section, click a link unit to select it.
Click Release Link PDU.
A confirmation prompts to cancel or release:

If released, the link unit is removed from the PDU page.
Switching to a Different PDU
Switching PDUs is a control function noted by the Switch control in the in theupper left corner of the PDU, Outlet, Outlet Groups, OCPs, and Feature Ports
pages, called out in the following screen example.
Displayed data in the GUI defaults to the master unit. The Switch control allows
you to switch quickly from a master page to a link unit page, and back again to
the master.

To switch to a different PDU:

92

1.

Click the Switch

control.

2.

Select one of the link PDUs from the drop-down list. Link number "2-8"appears in parentheses.

3.

The page displays data for the selected link PDU.

Chapter 5: PDU Linking

4.

To return to the PDU page for the master, select the master PDU. Masternumber "1" appears in parentheses.

Note: The Switch control is only available when there is at least one link unit in
the chain; otherwise, the page defaults to displaying only the data of themaster PDU.
Re-linking a Link Unit
In PDU Linking, Re-link is a required function when a link unit no longer
recognizes or responds to the master unit, most likely caused when the link
unit has been reset to factory defaults. Resetting to factory defaults causes thelinked unit in the chain to be unreachable, and it would have to be removed
from the chain manually.
If reset to factory defaults, the status of the disassociated link unit will be
displayed on the PDU page as "Access Denied", shown below.

To re-link a link unit:
1.

When you select the link unit in the "Access Denied" status, the Re-linkbutton displays, as noted above.

2.

To reconnect the link unit in the chain, and to regain full control of the unit,
click Re-link.

93

Chapter 5: PDU Linking

94

3.

Although re-linking uses the same Link Unit ID and hostname of theunreachable unit, you will need to reauthenticate with your login
credentials shown below.

4.

Click the Re-link button.

5.

The status of the link unit changes to "OK".

Chapter 5: PDU Linking

Viewing Link Unit Information
When a link unit is added to the chain, the master unit view (through the GUI)
allows full access to the operational data of the link unit. For example, using
the navigation tabs of the GUI, link unit data is displayed in several pages: theDashboard, PDUs, Inlets, Outlets, Outlet Groups, Peripherals, and Feature
Ports.
Dashboard
The Dashboard shows inlets, OCPs, alerted sensors, and inlet history for theentire linked chain.
In this example, data for the single inlet of the master "My PDU (1)" Inlet I1,
and the inlet of the link unit "My PDU (2)" Inlet I1, are displayed together. The
OCPs for the units are also available together on the Dashboard page.
Peripheral sensors are not shown on the dashboard by default. Only sensors(both PDU or peripheral) in warned or critical state are displayed in the Alerted
Sensors section.

95

Chapter 5: PDU Linking

96Chapter 5: PDU Linking

PDU Page
The PDU page displays the details and settings for the selected unit (master orlink). The Link PDUs section is only shown when the master unit is selected.

97

Chapter 5: PDU Linking

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

98

Chapter 5: PDU Linking

Outlets Page
The Outlets page defaults to display only the outlets of the master unit, in thisexample 30 outlets.

99Chapter 5: PDU Linking

Viewing Outlets for Link Units
On the Outlets page, you can switch from the master to the link.
1.

All outlets of the link unit display for viewing and a cces s exactly like the outlets of the ma ster unit.

100

From the Outlets page drop-down, select the link unit "My PDU (2)". Note:
To view outlets for a specific link unit, the link unit must be selected byname.

Chapter 5: PDU Linking

2.

You can switch back to the master unit by selecting "My PDU (1)".
Note: The Switch control is only available when there is at least one link
unit in the chain; otherwise, the page defaults to displaying only the outletsof the master.

101

Chapter 5: PDU Linking

3.

102

From the Outlets page (either master or link), select an outlet in the list toview operational details for the specific outlet and to configure outlet
settings.

Chapter 5: PDU Linking

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

103

Chapter 5: PDU Linking

104

Chapter 5: PDU Linking

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

105

Chapter 5: PDU Linking

To add an outlet group:1.

On the Outlet Groups page, click. The New Outlet Group page
displays, defaulting to the outlets in the master unit.

2.

Type a name for the new outlet group.

3.

Select individual member outlets for the master as shown in the default
page, or to select all outlets for the master, select My PDU (1).

4.

To select individual member outlets for the link unit My PDU (2), click Add
Outlets. To select all outlets for the link unit, select My PDU (2). Note: Link
units have to be selected by name to display their outlets.

5.

Click Save.
The following example shows the outlet group named "TEST 1" with alloutlet members selected for the master unit and outlet members 1-6
selected for the link unit.

106Chapter 5: PDU Linking

Controlling Outlets in Groups

1.

From the Outlet Groups page, select an outlet group by name.

2.

Click the desired control: On, Off, or Cycle. This example shows threeoutlets in status On. When Off is clicked, a prompt appears to confirm
applying the action to all outlets in the group.

3.

Click the Switch button.

4.

The status of the outlets in the group appears on the Outlets Group pageas Off.

107

Chapter 5: PDU Linking

Pairwise Outlet Groups
The PDU Linking feature offers the "pairwise" functionality for outlet grouping.
Pairwise lets you create auto-named pairs of outlet groups than span multiple
PDUs (master and link units) using the same outlet label. Pairwise simplifies
outlet switching up or down a server by automatically creating multiple outlet
groups, each containing one pair of outlets between PDUs that can becontrolled as a pair-related outlet group.
Example: Chain with master and a single link unit
PDU 1 (Master Unit)

Server LoadPDU 2 (Link Unit)

Outlet 1

Server 1

Outlet 1

Outlet 2

Server 2

Outlet 2

Outlet 3

Server 3

Outlet 3…

…

…

Outlet 20

Server 20

Outlet 20

Using the above example, to power up or down a server, you would typicallyswitch one outlet of PDU 1 and one outlet of PDU 2. With pairwise, you can
auto-create an outlet group named "Outlet pair 3", and the new group willautomatically contain Outlet 3 from PDU 1 (master) and Outlet 3 from PDU 2(link). Powering up or down the server only requires switching the "Outlet pair3" outlet group, allowing for improved accuracy and speed over outlet control.
Automatically Create Pairwise Outlet Groups

1.

108

From the Outlet Groups page, from the drop-down menu
Automatic Creation.

selectChapter 5: PDU Linking

2.

Confirm the pairwise creation.

3.

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

109

Chapter 5: PDU Linking

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

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

110

Chapter 5: PDU Linking

Feature Ports Page
The Feature Ports Page can display device Asset Strip information and theSwitch PDU control is available for the data from both the master and linkunits.

Displays for Master and Link Units
Each unit in a PDU Linking chain displays its own PDU data (inlets, outlets,
sensors, alerts, etc.)
Master unit:
From the following example of the master unit display, navigate the options fordisplaying Link PDU identification and status, and to confirm the master unitthat is controlling the link unit in the chain.
1.

Can show alarms, which may be triggered by link units.

111

Chapter 5: PDU Linking

2.

PDU information shows a list of link units with host name/IP address,
model, device name, serial number, firmware version, and communication
status.

Link units:

112

1.

No display of alarms (no event engine on link units)

2.

PDU information shows the master IP addressChapter 5: PDU Linking

PDU Linking in the CLI
For each PDU in a chain, you can list the PDUs, switch a PDU, add a new link
PDU, and release a link PDU. You can then use all regular PDU-relatedcommands as usual to access and control individual units, as with any
standalone PDU.
The CLI is disabled on link units. Access to the link unit via the CLI is available
only through the master CLI.
If any link units are configured, the CLI prompt includes the currently selected
PDU and Link ID, such as My Pdu (1) or My Pdu (2).
Some commands are not available for link units:
•
•
•
•
•

Authentication settings
EnergyWise settings
Security settings (login, role-based access control, user blocking, andstrong passwords.)
Server monitor
User management

113Chapter 5: PDU Linking

PDU Linking CLI Commands
PDU List
Displays the following information for each unit:• Link ID• Communication status (for link unit only)• Device name• Model name
• Serial number• Firmware version# pdu list
Switch PDU
Switch between the master and link units. The Link ID must be PDU 1 (master)or PDUs 2-8 (link units).
# pdu [id]Add a New Link PDU
Add a link unit to a master unit. Only available when PDU 1 (master) is selected.
The command can be used to re-establish a connection to an existing link unit if
the Link ID and host match exactly. The command requires admin privileges
and prompts for the user’s password.
# pdu link [id] [host] [login]• id: New link ID (PDUs 2-8)
• host: Host name or IP address• login: Name of user with admin privileges
Release a Link PDU
Release a link unit from a chain until the unit becomes standalone. The master
unit does not have access to a released link unit. The command is only available
when PDU 1 (master) is selected. The command requires admin privileges, andprompts for confirmation unless the “/y” is specified.
# pdu release [id] {/y}• id: Link ID of the unit to be released (PDUs 2-8).

114

Chapter 6

Introduction to PDU Components
This chapter explains how to use the PX3 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 ........................................................................................... 115
Circuit Breakers ................................................................................................ 151
Fuse .................................................................................................................. 153
Beeper .............................................................................................................. 156
Replaceable Controller ..................................................................................... 157
Threaded Grounding Point ............................................................................... 158

Panel Components
PX3 comes in Zero U, 1U, and 2U sizes. All types of models come with thefollowing components on the outer panels.
•
•
•
•
•

Inlet
Outlets
Connection ports
Dot-matrix LCD display
Reset button

Connection ports, the LCD display and reset button are located on a
replaceable controller of the PX3 model. See Replaceable Controller (on page
157).

115

Chapter 6: Introduction to PDU Components

Inlet
Most of PX3 PDUs are shipped with a locking line cord, which is ready to beplugged into the PDU's inlet and an appropriate receptacle for electricity
reception. Such devices cannot be rewired by the user.
A locking line cord helps secure the cord connection. For details, seeConnecting a PX3 Locking Line Cord (on page 14).
Connect each PX3 to an appropriately rated branch circuit. Refer to the label ornameplate affixed to your PX3 for appropriate input ratings or range of ratings.
There is no power switch on the PX3. To power cycle the PDU, unplug it fromthe branch circuit, wait 10 seconds and then plug it back in.
Besides, a PX3 "Zero U" model supports a relocatable inlet. See Zero U Models'
Relocatable Inlet (on page 116).
Zero U Models' Relocatable Inlet

You can easily change the inlet's location from the side to the top or from the
top to the side on a Zero U model.
To change a PX3 inlet's position:
1.

Power OFF the PDU.

2.

Remove the screws at two sides of the inlet to uninstall the inlet module.

3.

Re-install the inlet module in a manner that the inlet is located at thedesired position.
Inlet on the side

116

Inlet on the top

Chapter 6: Introduction to PDU Components

Outlets
The total number of outlets varies from model to model.
PX3-1000 Series

These models are NOT outlet-switching capable so all outlets are always in the
ON state.
Outlet LEDs are not available.
Connection Ports
Depending on the model you purchased, the total number of ports available
varies.
Zero U Connection Ports

A PX3 has 9 connection ports. Depending on the model you purchased, port
locations on your models may be different from the following image.

▪

CONSOLE/MODEM port x 1 (blue)▪

Sensor port x 1 (yellow)▪

USB-A port x 2▪

USB-B port x 1▪

Feature port x 1 (red)▪

Ethernet port x 2 (green and white)

Note: ETH 10/100/1000 (marked in green) supports up to 1000 Mbps.
This is "ETH1". ETH 10/100 (marked in white) supports up to 100 Mbps.
This is "ETH2".
▪

Expansion port x 1 (gray)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 most of the 1U and 2Umodels have the ports located respectively on the front and back panels.

117Chapter 6: Introduction to PDU Components

Connection Port Functions

The table below explains the function of each port.
Port

Used for...

USB-B

•
•

•

Cascading PX3 devices for sharing a network connection. See Cascading
All Devices via USB (on page 35).
Establishing a USB connection between a computer and the PX3 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
PX3.
▪

USB-A

This is a "host" port, which is powered, per USB 2.0 specifications.
•••

FEATURE

See Connecting a Mobile Device to PX3 (on page 25).

Connecting to an iOS mobile device for viewing or configuring the PX3.
See Connecting a Mobile Device to PX3 (on page 25).
Connecting a USB device, such as a Logitech® webcam or wireless LAN
adapter.
Cascading PX3 devices for sharing a network connection.

Connection to one of the following devices:▪

A Raritan access product, such as Dominion KX III KVM switch, withthe 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 thelocations of IT devices on the rack.

See Connecting External Equipment (Optional) (on page 48).
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(RJ-45)

Establishing a serial connection between the PX3 and a computer or modem.
You need a third-party RJ-45 to DB9 adapter/cable for the connection(s). Notethat the RJ-45 to DB9 adapter/cable for connecting a computer is different
from the one for connecting a modem. For details, refer to:▪ RJ45-to-DB9 Cable Requirements for Computer Connections (on page 32)▪ RJ45-to-DB9 Cable Requirements for Modem Connections (on page 772)

118

Chapter 6: Introduction to PDU Components

Port

Used for...

SENSOR

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

ETH 10/100/1000,
ETH 10/100▪

Raritan's environmental sensor package(s).

▪

Raritan's sensor hub, which expands the number of a sensor port tofour ports.

PX3 has two Ethernet ports.
▪

ETH 10/100/1000 (marked in green) supports up to 1000 Mbps. Thisis "ETH1".

▪

ETH 10/100 (marked in white) supports up to 100 Mbps. This is"ETH2".

Connecting the PX3 to your company's network via a standard network patch
cable (Cat5e/6). This connection is necessary to administer or access the PX3
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 that the yellow LED of the ETH 10/100 port has NO function so
it will not be lit regardless of the communication status.

You can use either Ethernet port for network connection or cascading. See
Extended Cascading with PX3 Devices (on page 38).
Note: Network connection to this port is not required if wireless connection ispreferred, or if the PX3 is a slave device in the cascading configuration.
EXPANSION

Connecting to the EXPANSION port of another PX3 so that the power supply
to either PX3 controller will continue whenever power failure occurs on theinlet of one PX3 PDU.
▪ See Power-Sharing Restrictions and Connection (on page 43).

Dot-Matrix LCD Display
The following diagram shows the dot-matrix LCD display panel on Zero Umodels.

119

Chapter 6: Introduction to PDU Components

You can use the LCD display to view the PDU information and even switch an
outlet. It consists of:••

A dot-matrix LCD display
Four control buttons

Zero U models automatically adjust the orientation of the content shown on
the dot-matrix LCD display after detecting the direction in which the PDU is
installed. 1U and 2U models do NOT adjust the content's orientation.
If the orientation of your Zero U model's LCD content does not meet your need,
you can manually change it and stick to the orientation. See Manually
Changing PX3's Zero U LCD Orientation (on page 146).
Note 1: All dot-matrix LCD display diagrams illustrated in the User Guide are for
Zero U models. Your dot-matrix LCD may look slightly different if it is on a
1U/2U model.
Note 2: For information on LCD displays of old PX3 models, see Old Generationsof PX3 Models (on page 704).

120

Chapter 6: Introduction to PDU Components

Automatic and Manual Modes

After powering on or resetting the PX3, the front panel LCD display first showssome dots, then Raritan logo and finally enters the automatic mode.
Automatic mode without alerts available:
In this mode, the LCD display cycles through the inlet information as long as
there are no alerts.
If overcurrent protectors are available on your PX3, the display cycles between
both the inlet and overcurrent protector information.
Note: You can make a PX3 with overcurrent protectors show the inlet
information only in the automatic mode. See Front Panel Settings (on page
386).
Manual mode:
To view more information or control outlets if your PX3 is outlet-switchingcapable, enter the manual mode.
Pressorto enter the manual mode, where the Main Menu is firstdisplayed. See Main Menu (on page 124).
To return to the automatic mode, press•

When an alert exists:
In the automatic mode, when an alert occurs, the LCD display stops cycling
through information, and warns you by showing the alerts notice in ayellow or red background. See Alerts Notice in a Yellow or Red Screen (onpage 147).
To enter the manual mode, press•

once or multiple times.

.

In the manual mode, both the top and bottom bars will turn yellow or red
to indicate the presence of any alert. See Operating the Dot-Matrix LCD
Display (on page 123).

121

Chapter 6: Introduction to PDU Components

Control Buttons

Use the control buttons to navigate to the menu in the manual mode.
ButtonFunction
Up
Down
OK
Back
-- OR -Switch between automatic and manual modes

122

Chapter 6: Introduction to PDU Components

Operating the Dot-Matrix LCD Display

Enter manual mode when you want to operate the dot-matrix LCD display. You
can use the dot-matrix LCD display to:
•
•

•

•

Show information of the PX3, built-in components, or connected
peripheral devices
Control actuators if any
Color changes of the display's top and bottom bars:
In the manual mode, both the top and bottom bars will turn yellow or red
to indicate the presence of any alert. For color definitions, see Yellow- or
Red-Highlighted Sensors (on page 208).
Screen with yellow bars

Screen with red bars

All alerts enter the warning level only.

Partial or all alerts enter the critical level.

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

123

Chapter 6: Introduction to PDU Components

Main Menu

The Main Menu contains 6 to 8 menu commands, depending on the model.
Control buttons that can be used and the system time are shown at the bottomof the LCD display.
The currently-selected item's number and total of menu items are indicated in
the top-right corner of the display.

If any alerts exist, the top and bottom bars on the LCD display change the color
from black to yellow or red. See Operating the Dot-Matrix LCD Display (onpage 123).
In the124

Chapter 6: Introduction to PDU Components

Menu command
AlertsFunction
Indicates all alerted sensors, if any. See Alerts (on page 125).
Shows the internal beeper's state, and, if it is on, the reason for turning on.

PDU

If your PDU has multiple inlets, this menu item also shows the total active
power and total active energy.
See PDU (on page 128).

Inlet I1
Residual Current

Shows the inlet I1's information. See Inlet (on page 131).
Available only on PX3 models supporting residual current monitoring. See
Front Panel Operations for RCM (on page 696).
Shows a list of overcurrent protector information. See OCPs (on page 132).

OCPs

Only the models with overcurrent protectors have this menu item.
Shows the information of connected Raritan environmental sensors or
actuators, such as the temperature sensor.

Peripherals

You can turn on or off a connected actuator with this command.
See Peripherals (on page 133).

AssetsShows the asset management information if Raritan asset management
equipment is connected to your PX3. See Assets (on page 137).

Device Info

Shows the device information, such as IP and MAC address. See Device Info (onpage 141).
Note: To return to the automatic mode, press
Modes (on page 121).

. See Automatic and Manual

AlertsThe "Alerts" menu command shows a list of the following alerted sensors,
including both internal and external sensors.
•••

Any numeric sensor that enters the warning or critical range if thethresholds have been enabledState sensors that enter the alarmed state
Any tripped circuit breakers or blown fuses

Tip: The same information is available in the web interface's Dashboard. See
Dashboard - Alerted Sensors (on page 176).
If there are no alerted sensors, the LCD display shows the message "No Alerts."
To view alerted sensors:
1.

Press

or

to select "Alerts" in the Main Menu, and press.

125Chapter 6: Introduction to PDU Components

2.

Alerted sensors, if any, are highlighted in either red or yellow. For color
definitions, see Yellow- or Red-Highlighted Sensors (on page 208).
▪

Number

The top and bottom bars on the LCD display may be yellow or red,depending on the type(s) of available alerts. See Operating the
Dot-Matrix LCD Display (on page 123).

Description
Alarm names.
The time the alarm occurred.
If the alarm occurred at least two times, then more information is shown.
▪ Number of alarms▪ The first occurrence time
▪ The last occurrence time
Alerted sensor names.
Sensor readings and/or states.
A numeric sensor shows both the reading and state. A state sensor or actuatorshows the state only.
Available states are listed below. For further information, see Sensor/Actuator
States (on page 211).
▪
▪
▪
▪
▪
▪

126

AlarmedLower Critical = below lower critical
Lower Warning = below lower warning
Upper Warning = above upper warning
Upper Critical = above upper criticalOpen (only available for Raritan PDUs with overcurrent protectors)

Chapter 6: Introduction to PDU Components

NumberDescription
The 'Details' command appears for alarms only.
▪ If your Alert List comprises alerted sensors only, then 'Details' is not shown.
3.

Press
or
to view additional pages. When there are multiple
pages, page numbers appear in the top-right corner of the display.

4.

(Optional) If there are alarms in the Alert List, you can perform thefollowing operations.
a.

Press

to view detailed information of the alarm.

b.

(Optional) If the alarm occurred more than one time, the numbers ofcurrent page and total pages are shown in the top-right corner, similar
to the above diagram. Pressother occurrences.

c.

or

To acknowledge all alarms now, press

to view the information of.

127

Chapter 6: Introduction to PDU Components

PDU

Depending on the model you purchased, the "PDU" menu command may show
one or all of the following data.
••••

Internal beeper states -- Active or Off
Total active power of the PX3 -- available on multi-inlet models and in-line
monitors only
Total active energy of the PX3 -- available on multi-inlet models and in-line
monitors only
12V power supply status

Tip: The internal beeper state information is also available in the PX3 web
interface. See PDU (on page 182).
To view or configure PDU information:

128

1.

Press

or

to select "PDU" in the Main Menu, and press

2.

The internal beeper state is shown: Active or Off.

.

▪

In the Active state, the reason of turning on the beeper is indicated,
and the top/bottom bars turn red.

▪

To mute the beep sound immediately, press
Internal Beeper (on page 130).

. See Muting theChapter 6: Introduction to PDU Components

3.

Press
to show the status of the 12V power supply to the controller.
For details on this sensor, see +12V Power Supply Sensor (on page 186).

4.

If your PX3 has more than one inlet, press
to show the informationof total active power (W) and total active energy (Wh).

5.

To return to the Main Menu, press.

129

Chapter 6: Introduction to PDU Components

Muting the Internal Beeper
After enabling the internal beeper's mute control function, you can choose tomute the beeper via the front panel whenever the beeper sounds for an alarm.
By default, the beeper's mute control feature via front panel is enabled.
Tip: To disable this feature, see Front Panel Settings (on page 386).
To mute the internal beeper during an alarm:

130

1.

Press

or

to select "PDU" in the Main Menu, and press

2.

Press

. A confirmation message appears.

3.

Press

to select Yes and then press.

.

Chapter 6: Introduction to PDU Components

4.

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

Note that the alarmed state remains unchanged yet for the moment.

Inlet

An inlet's information is divided into two pages. Page numbers are indicated in
the top-right corner of the LCD display.
To show the inlet information:
1.

Press

or

to select "Inlet I1" in the Main Menu, and press

2.

The first page shows the inlet's active power (W), apparent power (VA),
power factor (PF), and active energy (Wh).

.

131

Chapter 6: Introduction to PDU Components

3.

4.

To go to other page(s), press

or

.

▪

For a single-phase model, the second page shows the inlet's voltage (V),frequency (Hz) and current (A).

▪

For a three-phase model, the next several pages respectively show
unbalanced current's percentage, line frequency, and the current andvoltage values of each line.

To return to the Main Menu, press

.

OCPs

If your model has more overcurrent protectors (OCPs) than the LCD display canshow at a time, a page number appears in the top-right corner of the display.
Otherwise, no page numbers are available.
To show the overcurrent protector information:
1.

132

Press

or

to select "OCPs" in the Main Menu, and press.

Chapter 6: Introduction to PDU Components

2.

The LCD display shows a list of overcurrent protectors similar to thefollowing diagram.

NumberDescription
Overcurrent protector names.
Associated lines and rated current are displayed below each overcurrent
protector's name.
Current reading of the corresponding overcurrent protector.

3.

If the desired overcurrent protector is not visible, press
scroll up or down.

ortoNote: If any circuit breaker trips, the list of overcurrent protectors looks slightly
different from the above diagram. The tripped one will show "open" instead ofa current reading.

Peripherals

If there are no Raritan environmental sensor packages connected to your PX3,
the LCD display shows the message "No managed devices" for the "Peripherals"menu command.
If you have enabled the front panel actuator control function, you can switch
on or off a connected actuator using the LCD display. See Miscellaneous (onpage 394).
To show environmental sensor or actuator information:
1.

Press

or

to select "Peripherals" in the Main Menu, and press.

133Chapter 6: Introduction to PDU Components

2.

The display shows a list of environmental sensors/actuators.
▪

If the desired sensor or actuator is not visible, press
scroll up or down.

▪

When the list exceeds one page, the currently-selected
sensor/actuator's ID number and total of managed sensors/actuators
are indicated in the top-right corner of the display.

▪

If any sensor enters the warning, critical, or alarmed state, like 'Tamper
Detector 1' shown below, it is highlighted in yellow or red. For color
definitions, see Yellow- or Red-Highlighted Sensors (on page 208).

orto

The top and bottom bars also turn yellow or red. See Operating the
Dot-Matrix LCD Display (on page 123).

NumberDescription
Sensor or actuator names.

134

Chapter 6: Introduction to PDU Components

NumberDescription
Sensor or actuator states as listed below. For further information, seeSensor/Actuator States (on page 211).
▪
▪
▪
▪
▪
▪
▪
▪
▪
▪
▪

n/a = unavailable
NormalAlarmedLower Critical = below lower critical
Lower Warning = below lower warning
Upper Warning = above upper warning
Upper Critical = above upper critical
On
Off
Open
ClosedA numeric sensor shows both the reading and state. A state sensor or actuatorshows the state only.
3.

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

Number. A screen

Description
The ID number assigned to this sensor or actuator.
▪ A sensor shows "Peripheral Sensor x" (x is the ID number)▪ An actuator shows "Peripheral Actuator x"
Sensor or actuator name.

135

Chapter 6: Introduction to PDU Components

NumberDescription
The following information is listed.
▪ Serial number▪ Chain position, which involves the following information:▪

Port <N>: <N> is the number of the sensor port where this sensor or
actuator is connected. This number is always 1 for PX3.

▪

Chain Pos. <n>: <n> is the sensor or actuator's position in a sensor daisy
chain.

Note: Only Raritan's DX, DX2, DPX2 and DPX3 series provide the chain position
information.
▪ If this sensor or actuator is on a sensor package with multiple channels, such as
DX2-DH2C2, its channel number is indicated as "Channel x", where x is anumber.
Depending on the sensor type, any of the following information is displayed:▪ State of a state sensor: Normal, Alarmed, Open or Closed.
▪ State of an actuator: On or Off.
▪ Reading of a numeric sensor.
X, Y, and Z coordinates which you specify for this sensor or actuator. See Individual
Sensor/Actuator Pages (on page 217).
To switch on or off an actuator:
1.

136

Follow the above steps 1 to 3 to select an actuator.

Chapter 6: Introduction to PDU Components

2.

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

3.

Press

4.

Verify that the actuator status shown on the LCD display has beenchanged.

orto select Yes or No, and then press.

AssetsIf there are no Raritan asset management strips connected, the LCD display
shows the message "No asset strips connected" for the "Assets" menu
command.
After connecting asset strips, only the information of the rack units where asset
tags have been detected is shown on the LCD display.
To show asset strip information:
1.

Press

or

to select "Assets" in the Main Menu, and press.

2.

The display shows the available asset strip, and indicates how many rackunits and tags are detected on this strip.

137

Chapter 6: Introduction to PDU Components▪

3.

The number of tags includes both the tags attached to the asset strip
and those attached to the blade extension strip, if any.

Press

to show this asset strip's details, including:▪

State - strip status.

▪

Main Tags - number of the tags attached to the asset strip.
In the following diagram, this number is 30.

▪

Blade Tags - number of the tags attached to the blade extension
strip(s), if any.
In the following diagram, this number is 2.

Note: The 'Blade Tags' information appears only when there are tags
detected on the connected blade extension strip.

138▪

Type - the asset strip type.

▪

Numbering - the numbering mode. See Asset Strip (on page 225).

▪

Offset - the starting number of the rack unit numbering.

Chapter 6: Introduction to PDU Components▪

4.

Orientation - the strip's orientation.

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

▪

When the list exceeds one page, the currently-selected main tag andtotal of available main tags are indicated in the top-right corner of thedisplay.

▪

If the desired tag is not visible, press
down.

or

to scroll up or139

Chapter 6: Introduction to PDU Components

NumberDescription
Two numbers are displayed for each tag.
▪ Rack unit number: The number assigned to this tag based on the selected
numbering mode. See Asset Strip (on page 225).
▪ The index number in parentheses: The physical port number printed on theasset strip.
The asset tag's name if you have specified. This field does not show up when noname is available.
If the connected tag is the blade extension strip, it shows 'blade extension' andindicates how many tags and slots are available on this extension strip.
A color box, which represents the current LED color of the tag port where this asset
tag is connected. The default is green.
▪ You can customize the color. See Asset Strip (on page 225).
The connected asset tag's ID number (barcode).
5.

If any blade extension strip is connected to this asset strip, select it andPress
strip.

Numberto view a list of available tags and asset IDs on this extension

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

140

Rack unit number
Index number in parentheses
Current LED color of the tag port where it is connected
Extension strip's ID number (barcode)

Chapter 6: Introduction to PDU Components

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

Device Info

The display shows the device's information, network and IPv4/IPv6 settings
through various pages. Page numbers are indicated in the top-right corner ofthe LCD display.
To show the device information:
1.

Press

or

to select "Device Info" in the Main Menu, and press.
2.

NumberDevice information similar to the following diagram displays.

Description
Device name.
Firmware version, model name and serial number.
Device ratings, including rated voltage, frequency, current and power.

141

Chapter 6: Introduction to PDU Components

3.

NumberPress

to show the Network Common page.

Press

to show the Network Cascading page.

Description
DNS servers.
Default gateways.
4.

142

Chapter 6: Introduction to PDU Components

NumberDescription
Cascading status, which can be one of the following:▪ No Cascading: This device's cascading mode is set to None. See Setting the
Cascading Mode (on page 270).
▪ Network Bridge Enabled: This device's cascading mode is set to Bridging. Its IP
address is also displayed on this page.
▪ Port Forwarding Master: This device's cascading mode is set to Port Forwarding,and it is a master device.
▪

Slave Connected: Indicates whether the presence of a slave device is
detected - yes or no.

▪ Port Forwarding Slave: This device's cascading mode is set to Port Forwarding,and it is a slave device.
▪

Slave Connected: Indicates whether the presence of a slave device is
detected - yes or no.

▪

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

▪

A port forwarding slave device will also display the master device's IP
address on this page.
5.

Press

to show the Ethernet page.

143

Chapter 6: Introduction to PDU Components

A PX3 has two Ethernet pages -- ETH1 and ETH2.

NumberDescription
Ethernet interface information, including:▪ MAC address.
▪ Speed.
▪ Full or half duplex.

144

Chapter 6: Introduction to PDU Components

NumberDescription
IPv4/IPv6 network information, including:▪ Network configuration: DHCP (or Automatic), or Static. Static represents Static
IP.
▪ IP address.
▪ Prefix length, such as "/24".
Note: If you disable any Ethernet interface, a message 'Interface Disabled' isshown. See Ethernet Interface Settings (on page 257).
If you do not enable IPv4/IPv6 settings, an 'IPv4 (or IPv6) Disabled' message
is displayed.
6.

Press

to show the WIRELESS page.

145

Chapter 6: Introduction to PDU Components-- OR --

NumberDescription
If NO supported WLAN adapter is plugged or detected, the message "No Adapter
Detected" is shown.
If a supported WLAN adapter is detected and configured properly, wireless network
information is shown instead, including:▪ MAC address▪ SSID▪ IPv4/IPv6 network information -- for detailed explanation, refer to number
7.

To return to the Main Menu, press.

Manually Changing PX3's Zero U LCD Orientation

A Zero U model has a tilt sensor that can detect the orientation of its physicaldevice to automatically adjust ts LCD content's orientation.
If the LCD's orientation does not meet your need, you can manually configureit.
The factory default is automatic orientation.
To set up the LCD orientation:
1.

Press
or
Orientation".

2.

If the current LCD orientation does not meet your need, repeat the above
step until the orientation you preferred is displayed.
▪

146

simultaneously until you see the LCD shows "Fixed

If you want to return to the factory default, also repeat step 1 until the
LCD shows "Automatic Orientation".

Chapter 6: Introduction to PDU Components

Alerts Notice in a Yellow or Red Screen

In the automatic mode, if an alert occurs, the LCD display automatically showsa yellow or red screen which indicates the total number of alerted sensors andinformation of the latest transitions.
••

When all alerted sensors enter the warning levels, the screen's backgroundturns yellow.
When at least one of the alerted sensors enters the critical level or there isany "alarm", the screen's background turns red.

For color definitions, see Yellow- or Red-Highlighted Sensors (on page 208).
The following illustrates the alerts notices in red.
When there are only alerted sensors -- NO ALARMS are present:

NumberDescription
The total of alerted sensors in critical and warning levels.
A list of final alerted sensors that changed their readings or states.
The final time that each alerted sensor changed its readings or states.

147

Chapter 6: Introduction to PDU Components

When there is any alarm present:
The LCD display looks similar to the above diagram except that it shows thealarm(s) and the available command in the bottom-right corner is 'Actions'instead of 'Alert list'.

148

Chapter 6: Introduction to PDU Components

Available operations:•

For the notice listing alerted sensors only, press
alerted sensors. See Alerts (on page 125).

•

For the notice where at least an alarm is present, press
following:a.

Two options display. Press
press

or

to view a list of all. Then do theto select either option, and.

149

Chapter 6: Introduction to PDU Componentsb.

▪

Show alert list: This option lists all of alerted sensors and alarms.
You still can choose to acknowledge alarms after viewing the list.
See Alerts (on page 125).

▪

Acknowledge all alarms: This option immediately acknowledges all
existing alarms, without showing the list of alarms.

(Optional) If 'Acknowledge all alarms' is selected in the above step, a
confirmation prompt similar to the diagram below appears. Pressorto confirm or abort the operation, and press.

Showing the Firmware Upgrade Progress

When upgrading the PX3, the firmware upgrade progress will be displayed as apercentage on the LCD display, similar to the following diagram.

150

Chapter 6: Introduction to PDU Components

In the end, a message appears, indicating whether the firmware upgrade
succeeds or fails.
Reset Button
The reset button is located inside the small hole labeled RESET near the display
panel.
Pressing this reset button restarts the PX3 software without any loss of power
to outlets.
The PX3 can be reset to its factory default values using this button when aserial connection is available. See Resetting to Factory Defaults (on page 684).
The following images illustrate the locations of the reset button on Zero Umodels. Port locations may differ on your models.
PX3 Zero U diagram:

Circuit Breakers
PX3 models rated over 20A (North American) or 16A (international) containovercurrent 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 a circuit breaker switches off power, the LCD display shows open. To findwhich circuit breaker is open (trips), select Alerts or OCPs in the Main Menu.
See Operating the Dot-Matrix LCD Display (on page 123).
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 canresume normal operation.
Depending on the model you purchased, the circuit breaker may use a buttonor handle-reset mechanism.

151

Chapter 6: Introduction to PDU Components

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

Locate the breaker whose ON button is up, indicating that the breaker has
tripped.

2.

Examine your PX3 and the connected equipment to remove or resolve thecause that results in the overload or short circuit. This step is required, or
you cannot proceed with the next step.

3.

Press the ON button until it is completely down.

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

152

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.

Chapter 6: Introduction to PDU Components

3.

Examine your PX3 and the connected equipment to remove or resolve thecause that results in the overload or short circuit. This step is required, or
you cannot proceed with the next step.

4.

Pull up the operating handle until the colorful rectangle or triangle turns
RED.

Fuse
Some PX3 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 theoriginal one.
Use of inappropriately rated fuse results indamage 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.

153

Chapter 6: Introduction to PDU Components

154

2.

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

3.

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

4.

Take the fuse out of the holder.

5.

Insert a new fuse into the holder. There is no orientation limit for fuseinsertion.

6.

Close the fuse holder and the hinged cover in a reverse order.

Chapter 6: Introduction to PDU Components

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

NumberDescription
Fuse carrier
Fuse knob where a fuse is installed

To replace a fuse on 1U PDUs:
1.

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

2.

Remove the desired fuse from the PDU's fuse carrier using a flatscrewdriver.

3.

a.

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

b.

Take this knob out of the fuse carrier.

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 theoriginal one.

NumberDescription
Fuse knob

155

Chapter 6: Introduction to PDU Components

NumberDescription
Fuse

4.

5.

Install this knob along with the new fuse into the fuse carrier using a flatscrewdriver.
a.

Have this knob's slot inclined 45 degrees when inserting the knob into
the fuse carrier.

b.

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

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

NumberDescription
INAPPROPRIATE installations
Appropriate installation

6.

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

Beeper
The PX3 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 316).
Tip: To remotely check this beeper's state via the web interface, see PDU (onpage 182).

156

Chapter 6: Introduction to PDU Components

Replaceable Controller
A PX3 Zero U model provides flexibility for replacement of its controller. The
controller, which contains the dot-matrix LCD display and connection ports, isusually located in the middle of the PDU.
If the controller is broken, you can simply send the controller back to Raritan
for repair, or purchase a new controller from Raritan.
1U / 2U PDUs and all of PX3-3000 series do NOT support this feature.
To request a new controller:
Contact tech@raritan.com to request a new PX3 controller.
Include these details with your request:••••

The serial number of the PDU
The serial number of the controller board
The full model number of the PDU
The firmware version that the PDU is running (if known).
To replace a controller:

1.

PDU is NOT required to be powered off.

2.

Loosen the screws at two sides of the PX3 controller, and lift it up.
Note: Loosen the screws instead of removing them.

157

Chapter 6: Introduction to PDU Components

3.

Disconnect the PDU's controller cable from the controller.

4.

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

Threaded Grounding Point
If the PX3 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 PX3.

158

Chapter 7

Using the Web Interface
This chapter explains how to use the web interface to administer the PX3.

In This Chapter
Supported Web Browsers .................................................................................159
Login, Logout and Password Change ................................................................159
Web Interface Overview ...................................................................................164
Dashboard ........................................................................................................171
PDU ...................................................................................................................182
Inlet ...................................................................................................................187
Outlets ..............................................................................................................192
OCPs ..................................................................................................................195
Peripherals ........................................................................................................202
Feature Port ......................................................................................................223
User Management ............................................................................................240
Device Settings .................................................................................................251
Maintenance .....................................................................................................396
Webcam Management .....................................................................................425
SmartLock and Card Reader .............................................................................438

Supported Web Browsers
▪
▪
▪
▪
▪
▪

Internet Explorer® 11
Firefox® 52 and later
Safari® (Mac)
Google® Chrome® 52 and later
Android 4.2 and lateriOS 7.0 and later

Login, Logout and Password Change
The first time you log in to the PX3, 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 241).
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 PX3.

159

Chapter 7: Using the Web Interface▪

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

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

If any security alert message appears, accept it.

3.

The login screen displays. Type your user name and password. User
credentials are case sensitive.

4.

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

5.

160

Click Login or press Enter. The web interface of PX3 opens.

Chapter 7: Using the Web Interface

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. See Port Forwarding Examples (on page 275).

161

Chapter 7: Using the Web Interface

Changing Your Password
You need appropriate permissions to change your password. Refer to thefollowing for details.
To change other users' passwords, Administrator Privileges are required
instead. See Editing or Deleting Users (on page 244).
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 thischeckbox, then click Not Now.
Or enter the new password and click 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 page241).
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 246).

162

1.

Choose User Management > Change Password.

2.

First type the current password, and then the new password twice.
Passwords are case sensitive.

Chapter 7: Using the Web Interface▪

A password comprises 4 to 64 characters.

Remembering User Names and Passwords
PX3 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.
PX3 does NOT support other browser password managers.
LogoutAfter finishing your tasks, you should log out to prevent others from accessing
the PX3 web interface.

•

To log out without closing the web browser:
Click "Logout" on the top-right corner.
-- OR --•

Close the tab of PX3 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.

163

Chapter 7: Using the Web Interface

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

164

1.

Click any menu or submenu item in the area of.

2.

That item's data/setup page is then opened in the area of3.

Now you can view or configure settings on the opened page.

.

Chapter 7: Using the Web Interface

4.

NumberTo return to the main menu and the Dashboard page, clickon the top-left corner.

Web interface element
Menu (on page 167)
Data/setup page of the selected menu item.
▪ Left side:- PX3 device name.

165

Chapter 7: Using the Web Interface

NumberWeb interface element
Note: To customize the device name, see PDU (on page 182).
▪ Right side:- Displayed language, which is English (EN) by default. You can change it.
- Your login name, which you can click to view your user account settings.
- Logout button.
From top to bottom -▪ Your PX3 model.
▪ Current firmware version.
▪ Online Documentation: link to the online help of PX3.
- See Browsing through the Online Help (on page 810).
▪ 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.
▪ PX3 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.

166

Chapter 7: Using the Web Interface

Menu
Depending on your model and hardware configuration, your PX3 may show allor some menu items shown below.

Menu

Information shown

Dashboard

Summary of the PX3 status, including a list of alerted sensors and alarms, if any.
See Dashboard (on page 171).

PDU

Device data and settings, such as the device name and MAC address.
See PDU (on page 182).

Inlet

Inlet status and settings, such as inlet thresholds.
See Inlet (on page 187).

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

Peripherals

Status and settings of Raritan environmental sensor packages, if connected.
See Peripherals (on page 202).

167

Chapter 7: Using the Web Interface

Menu

Information shown

Feature Port

Status and settings of the device connected to the Feature port(s), which can beone of the following.

The name 'Feature
Port(s)' will be
replaced with oneof the device
names listed to
the right

▪
▪
▪
▪
▪
▪

Asset Strip
External Beeper
LHX 20
SHX 30
LHX 40Power CIM

See Feature Port (on page 223).
Webcams

The 'Webcams' menu item appears when there is any webcam(s) connected to
the PX3, or when there are snapshots saved onto the PX3 already.
Webcam live snapshots/video and webcam settings.
See Webcam Management (on page 425).

SmartLock-- and/or -Card Readers

Either or both menu items appear only when you connect Raritan's SmartLock
kit to this product. For details, refer to the user documentation accompanying
the SmartLock kit or download it from Raritan's Support page(http://www.raritan.com/support/).
▪ SmartLock: Configures and controls the door handles connected to this productvia DX2-DH2C2. Note that this page is not available if connecting the door
handles to other Raritan sensors than DX2-DH2C2.
▪ Card Readers: Lists the card readers connected to PX3 directly or indirectly.
See SmartLock and Card Reader (on page 438).

User Management

Data and settings of user accounts and groups, such as password change.
See User Management (on page 240).

Device Settings

Device-related settings, including network, security, system time, event rules andmore.
See Device Settings (on page 251).

MaintenanceDevice information and maintenance commands, such as firmware upgrade, device
backup and reset.
See Maintenance (on page 396).

168

Chapter 7: Using the Web Interface

If a menu item contains the submenu, the submenu is shown after clicking thatitem.
To return to the previous menu list, do any below:•

Click the topmost link with the symbol <. For example, click

•

Click

.

on the top-left corner to return to the main menu.

Quick Access to a Specific Page
If you often visit a specific page in the PX3 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 PX3 immediately
shows the wanted page rather than the Dashboard page.
Besides, you can also send the URL to other users so that they immediately seethat page after login, using their own user credentials.
URL examples:
In the following examples, it is assumed that the IP address of PX3 is192.168.84.118.
Page

URL

Peripherals

https://192.168.84.118/#/peripherals

Event Log

https://192.168.84.118/#/maintenance/eventLog/0

169

Chapter 7: Using the Web Interface

Sorting a List
If any list displays an arrow (or) in one of its column headers, you areallowed to resort the list by clicking any column header. The list will beresorted in the ascending or descending order based on the selected column.
Illustration -- Event Log:

170

1.

By default, the Event Log is sorted in the descending order based on the ID
column. Therefore, the arrowis displayed adjacent to the ID header.

2.

To have it resorted in the ascending order based on the same column, click
the ID header.

3.

The arrow turns toorder.

4.

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

5.

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

, indicating the list is sorted in the "ascending"Chapter 7: Using the Web Interface

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

171

Chapter 7: Using the Web Interface

NumberSectionInformation shown▪ Overview of inlet power data
▪ A current bar per phase, which changes colors to indicate the RMS
current state

Inlet I1

- green: normal- yellow: warning- red: critical
See Dashboard - Inlet I1 (on page 173).
This section is available only when your PX3 contains overcurrent
protectors (OCPs).

Overcurrent
Protectors▪ Overview of each OCP's status▪ A current bar per OCP, which changes colors to indicate the RMS
current state- green: normal- yellow: warning- red: critical
See Dashboard - OCP (on page 175).
Alerted Sensors▪ When no sensors enter the alarmed state, this section shows themessage "No Alerted Sensors."▪ When any sensor enters the alarmed state, this section lists all ofthem.
See Dashboard - Alerted Sensors (on page 176).

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

AlarmsThis 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 themessage "No Alarms."▪ When there are unacknowledged events, this section lists all of them.
See Dashboard - Alarms (on page 180).
The Hardware Failures section:
If PX3 detects any internal hardware issues, a section labeled "Hardware
Failures" will appear on the Dashboard page, listing all of current hardware
issues.

172

Chapter 7: Using the Web Interface

This section does NOT display as long as there are no hardware failures present.
See Hardware Issue Detection (on page 421).
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
I1' to go to the Inlet page. See Inlet (on page 187).

Left side - generic inlet power data:

173

Chapter 7: Using the Web Interface

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

Active power (kW or W)
Apparent power (kVA or VA)
Active energy (kWh or Wh)
Power factor
Line frequency (Hz)
Unbalanced current (%) - model dependent
Right side - inlet's current and voltage:

The right side shows the current and voltage data per phase. For a single-phasedevice, 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 187).
StatusBar colors

normalabove 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 thetwo thresholds for current levels.

174

Chapter 7: Using the Web Interface

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.

175

Chapter 7: Using the Web Interface•••

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 195).
StatusBar colors

normalabove 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 thetwo thresholds for current levels.
Dashboard - Alerted Sensors
When any internal sensors or environmental sensor packages connected to the
PX3 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 clickeach sensor's name to go to individual sensor pages. See Individual
Sensor/Actuator Pages (on page 217).
If wanted, you can resort the list by clicking the desired column header. See
Sorting a List (on page 170).

176

Chapter 7: Using the Web Interface

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

177

Chapter 7: Using the Web Interface

Dashboard - Inlet History• The Inlet History graph displays the history of the sensor values. Select a
different data type by clicking the selector•

178

below the diagram.

Chapter 7: Using the Web Interface▪

To retrieve the exact data at a particular time, hover your mouse overthe 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.

179

Chapter 7: Using the Web Interface▪

When both inlets are shown in the chart, simply hover your mouseover 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
316).
Only users with the 'Acknowledge Alarms' permission can manuallyacknowledge an alarm.

•180

To acknowledge an alarm:
Click Acknowledge, and that alarm then disappears from the Alarms
section.

Chapter 7: Using the Web Interface

This table explains each column of the alarms list.
Field

Description

Name

Custom name of the Alarm action.

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

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, otherreasons) triggering the same alert, the total number of
additional reasons is displayed. You can click it to viewa list of all events.

The date and time shown on the PX3 web interface are automaticallyconverted to your computer's time zone. To avoid time confusion, it issuggested to apply the same time zone settings as those of PX3 to yourcomputer or mobile device.
Tip: You can also acknowledge all alarms by operating the LCD display. Refer to
Alerts Notice in a Yellow or Red Screen (on page 147).

181

Chapter 7: Using the Web Interface

PDU
The PX3 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 167).

•
•
•
•
•
•

Device information shown:
Firmware version
Serial number
MAC address
RatingInternal Beeper State (on page 183)
Status of +12V Power Supply Sensor (on page 186)
To configure global settings:

1.

Click Edit Settings.

2.

In the Name field, type the name you prefer.

3.

Click Save.
To view total active energy and power on multi-inlet models:If your PX3 is a multi-inlet model, a "Power" section for showing the data of
total active energy and total active power is available on the PDU page.
For a regular PX3 model with multiple inlets:
•
•

182

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

Chapter 7: Using the Web Interface

To configure the thresholds of total active energy and power:
For a multi-inlet model or an in-line monitor, a "Thresholds" section is available
on the PDU page. See Setting Thresholds for Total Active Energy or Power (onpage 184).

Internal Beeper StateThe PDU page indicates the internal beeper state.

Available beeper states:
StatesDescription

Off

The beeper is turned off.

ActiveThe beeper is turned on.
"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 PX3, including fuses and circuit breakers,
has tripped or blown. See Beeper (on page 156).
You have set an event rule that turns on the internal beeper when aspecific event occurs, and that event occurs now. See Event Rules andActions (on page 316).
On the PX3 supporting residual current monitoring (RCM), the beeper also
sounds when an RCM alarm is detected.
Note that only the RCM sensor will cause the PDU to beep while RCM "DC"sensor does not cause the PDU to beep regardless of its sensor state.
For details, see PX3 Models with Residual Current Monitoring (on page
686).

183

Chapter 7: Using the Web Interface

Tip: To check the internal beeper state via CLI, see PDU Configuration (on page466).
Time Units
If you choose to type a new value in the time-related fields, such as the "Idle
timeout period" 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)ssecond(s)minminute(s)hhour(s)dday(s)

Setting Thresholds for Total Active Energy or PowerThis section applies only to multi-inlet models, including in-line monitors.
Thresholds for total active energy and total active power are disabled bydefault. 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 PX3 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.
▪

184

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

Chapter 7: Using the Web Interface

2.

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

3.

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

4.

Make changes as needed.
▪

To enable any threshold, select the corresponding checkbox.

▪

Type a new value in the accompanying text box.

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

Click Save.

185

Chapter 7: Using the Web Interface+12V Power Supply Sensor
The PX3's controller receives DC 12V power from its inlet. A sensor monitors
the power supply status and indicates it on the PDU page.

State

Description

OK

The PX3 controller is receiving power from its own inlet.

fault

The PX3 controller cannot receive power from its own
inlet because of a power failure on the inlet or a broken
12V power supply. Instead it is receiving power fromanother PX3 PDU. See Power-Sharing Restrictions andConnection (on page 43).
After entering the fault state, this sensor is listed in theAlerted Sensors section of the Dashboard. See
Dashboard (on page 171).

unavailable

•
•

186

The communication with the 12V power supply sensor is
lost.

Alternatives for checking the 12V power supply status:
Dot-matrix LCD panel. See PDU (on page 128).
CLI command: show pdu details. See Using the Command LineInterface (on page 456).

Chapter 7: Using the Web Interface

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 167).
Inlet thresholds, once enabled, help you identify whether the inlet enters thewarning or critical level. In addition, you can have PX3 automatically generate
alert notifications for any warning or critical status. See Event Rules andActions (on page 316).
Note: If your PX3 is a multi-inlet model, see Configuring a Multi-Inlet Model (onpage 190).

••

Generic inlet information shown:
Inlet power overview, which is the same as Dashboard - Inlet I1 (on page173).
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 208).
•

Inlet's power chart, which is the same as Dashboard - Inlet History (onpage 178)
To customize the inlet's name:1.

Click Edit Settings.

2.

Type a name for the inlet.
▪

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

3.

Click Save.

4.

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

187

Chapter 7: Using the Web Interface

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 PX3 has morethan one inlet.

1.
2.

Click

.

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 PX3, see PDU (on page 182).
To configure inlet thresholds:
Per default, there are pre-defined RMS voltage and current threshold values inrelated fields. See Default Voltage and Current Thresholds (on page 785). You
can modify them to meet your needs.
1.

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

2.

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

3.

Make changes as needed.
▪

188

To enable any threshold, select the corresponding checkbox.

Chapter 7: Using the Web Interface▪

Type a new value in the accompanying text box.

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

Click Save.
To configure residual current thresholds:

If your model supports residual current monitoring, a section titled "Residual
Current Monitor" is displayed on the Inlet page. See Web Interface Operations
for RCM (on page 690).

189

Chapter 7: Using the Web Interface

Configuring a Multi-Inlet Model
If the PX3 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.

2.

Now you can configure the selected inlet, such as enabling thresholds orresetting its energy. See Inlet (on page 187).
▪

To disable the inlet, see the following instructions.

To disable one or multiple inlets:

190

1.

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

2.

Select the "Disable this inlet" checkbox.

Chapter 7: Using the Web Interface

3.

Click Save.

4.

The inlet status now shows "Disabled."

5.

To disable additional inlets, repeat the above steps.
▪

If disabling an inlet will result in all inlets being disabled, a confirmation
dialog appears, 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 withthe disabled one are no longer available:•••

Sensor readings, states, warnings, alarms or event notifications associatedwith 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 withthe disabled inlet.

Exception: All active energy sensors continue to accumulate data regardless ofwhether 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.

191

Chapter 7: Using the Web Interface

Outlets
The Outlets page shows a list of all outlets and their data, such as each outlet's
associated lines. To open this page, click 'Outlets' in the Menu (on page 167).

•

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

If wanted, you can resort the list by clicking the desired column header. See
Sorting a List (on page 170).
To show or hide specific columns on the outlets overview page:

192

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

Chapter 7: Using the Web Interface

Available Data of the Outlets Overview Page
All of the following outlet data is displayed on the outlets overview page basedon your selection. To show or hide specific data, click
page 192).
••. See Outlets (onReceptacle typeLines associated with each outlet

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

The individual outlet's page shows this outlet's detailed information. See
Detailed Information on Outlet Pages (on page 194).
In addition, you can perform the following operations on this outlet page.
To configure this outlet:
1.

Click Edit Settings.

2.

Specify the outlet name.
▪

3.

Type an outlet name up to 64 characters long.

Click Save.

193

Chapter 7: Using the Web Interface

▪

•

•

The outlet's custom name, if available, is displayed in the outlets list,
following by its label in parentheses.

Other operations:
You can go to another outlet's data/setup page by clicking the outlet
selectoron 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.

Detailed Information on Outlet Pages

Each outlet's data page has the Details section for showing general outlet
information.
Details section:

194

Field

Description

Label

The physical outlet number

Receptacle typeThis outlet's receptacle type

Lines

Lines associated with this outlet

Inlet

Inlet associated with this outlet

Chapter 7: Using the Web Interface

Field
Overcurrent protector

Description
This information is available only when yourPX3 has overcurrent protectors.
Overcurrent protector associated with thisoutletOCPs
The OCPs page is available only when your PX3 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 208).
To open the OCPs page, click 'OCPs' in the Menu (on page 167).
You can go to each OCP's data/setup page by clicking its name on this page.

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

••

Overcurrent protector overview:
OCP status - open (tripped) or closed
Current drawn, rated current and current bar▪

The smaller, gray text adjacent to "current drawn" is the rated currentof each OCP.

195

Chapter 7: Using the Web Interface▪

The RMS current bars change colors to indicate the status if the OCP
thresholds have been configured and enabled.
StatusBar colors

normalabove upper warning
above upper critical
Note: The "below lower warning" and "below lower critical" states also
show yellow and red colors respectively. However, it is not meaningful toenable 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 PX3 automatically generate alert notifications for any warning or
critical status. See Event Rules and Actions (on page 316).
Note: By default, upper thresholds of an OCP's RMS current have been
configured. See Default Voltage and Current Thresholds (on page 785). You
can modify them as needed.
1.

Click

2.

Select one or multiple OCPs.
▪

To select all OCPs, simply click the topmost checkbox in the header
row.

3.

Click Edit Thresholds.

4.

Make changes as needed.
▪

196> Threshold Bulk Setup.

To enable any threshold, select the corresponding checkbox.

Chapter 7: Using the Web Interface▪

Type a new value in the accompanying text box.

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

Click Save.

Individual OCP Pages
An OCP's data/setup page is opened after clicking any OCP's name on the OCPs
or Dashboard page. See OCPs (on page 195) or Dashboard (on page 171).
General OCP information:
Field

Description

Label

This OCP's physical number.

Statusopen or closed.

Type

This OCP's type.

RatingThis OCP's rated current.

Lines

Lines associated with this OCP.

Protected outlets

Outlets associated with this OCP.

Inlet

Inlet associated with this OCP.
This information is useful only when yourPDU has multiple inlets.

197

Chapter 7: Using the Web Interface

Field

Description

RMS current

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

To customize this OCP's name:1.

Click Edit Settings.

2.

Type a name.

3.

Click Save.
To view this OCP's RMS current chart:

This OCP's data chart is shown in the Overcurrent Protector History section.

198

Chapter 7: Using the Web Interface▪

To retrieve the exact data at a particular time, hover your mouse overthe 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 785). 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 195).
1.

Click the Thresholds title bar at the bottom of the page to display thethreshold data.

2.

Click the RMS current sensor (required), and then click Edit Thresholds.

3.

Make changes as needed.
▪

To enable any threshold, select the corresponding checkbox.

199

Chapter 7: Using the Web Interface▪

Type a new value in the accompanying text box.

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

200

Click Save.

Chapter 7: Using the Web Interface••

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.

201

Chapter 7: Using the Web Interface

Peripherals
If there are Raritan environmental sensor packages connected to the PX3, they
are listed on the Peripherals page. See Connecting Raritan Environmental
Sensor Packages (on page 48).
An environmental sensor package comprises one or some of the following
sensors/actuators:•••

Numeric sensors: Detectors that show both readings and states, such astemperature 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.

PX3 communicates with managed sensors/actuators only and retrieves theirdata. It does not communicate with unmanaged ones. See Managed vsUnmanaged Sensors/Actuators (on page 210).
When the number of "managed" sensors/actuators has not reached the
maximum, PX3 automatically brings newly-detected sensors/actuators undermanagement by default.
One PX3 can manage a maximum of 32 sensors/actuators.
Note: To disable the automatic management function, refer to the final table inthis section. 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 page167). Then you can:•202

Perform actions on multiple sensors/actuators by using thecontrol/action icons on the top-right corner.

Chapter 7: Using the Web Interface•

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

If wanted, you can resort the list by clicking the desired column header. See
Sorting a List (on page 170).
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 208). An actuator is neverhighlighted.
ColumnDescription

Name

By default the PX3 assigns a name comprising thefollowing two elements to a newly-managed
sensor/actuator.
▪ Sensor/actuator type, such as "Temperature" or "DryContact."▪ 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 217).

Reading

Only managed 'numeric' sensors show this data, such astemperature and humidity sensors.

State

The data is available for all sensors and actuators. See
Sensor/Actuator States (on page 211).

Type

Sensor or actuator type.

Serial NumberThis is the serial number printed on the sensor package's
label. It helps to identify your Raritan sensors/actuators.
See Finding the Sensor's Serial Number (on page 212).

203

Chapter 7: Using the Web Interface

ColumnDescription

Position

The data indicates where this sensor or actuator is
located in the sensor chain.
See Identifying the Sensor Position and Channel (onpage 213).

Actuator

Indicates whether this sensor package is an actuator ornot. If yes, the symbol
is shown.

To release or manage sensors/actuators:
When the total of managed sensors/actuators reaches the maximum value,
you cannot manage additional ones. The only way to manage any
sensor/actuator is to release or replace the managed ones. To replace amanaged sensor/actuator, see Managing One Sensor or Actuator (on page215). 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 clickthat sensor/actuator without making the checkboxes appear.
2.

3.

Select multiple sensors/actuators.
▪

To release sensors/actuators, you must select "managed" ones only.
See Sensor/Actuator States (on page 211).

▪

To manage sensors/actuators, you must select "unmanaged" ones
only.

▪

To select ALL sensors/actuators, select the topmost checkbox in theheader row.

To release selected ones, click
To manage them, click204> Release.

> Manage.

Chapter 7: Using the Web Interface

4.

▪

The management action triggers a "Manage Peripheral Device" dialog.
Simply click Manage if you are managing multiple sensors/actuators.

▪

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

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

Click

▪

Adjust the numeric values.

▪

Select or deselect the checkbox.

to select an option.

Field

Function

Note

Peripheral device Z
coordinate format

Determines how to describe the verticallocations (Z coordinates) of Raritan
environmental sensor packages.

To specify the location of any
sensor/actuators in the data center, see
Individual Sensor/Actuator Pages (onpage 217).

▪ Options: Rack units and Free-form
See Z Coordinate Format (on page 222).
Peripheral device
auto management

Enables or disables the automaticmanagement feature for Raritan
environmental sensor packages.

See How the Automatic Management
Function Works (on page 215).

▪ The default is to enable it.

205Chapter 7: Using the Web Interface

Field
Altitude

Active powered dry
contact limit

Function

Note▪ The device's altitude is associatedSpecifies the altitude of PX3 above sea
with the altitude correction factor.
level when a Raritan's differential air
See Altitude Correction Factors (onpressure sensor is attached.
page 787).
▪ Range: -425 to 3000 meters (-1394 to▪ The default altitude measurement9842 feet)
unit is meter. See Setting Default▪ Note that it can be a negative value
Measurement Units (on page 250).
down to -425 meters (-1394 feet)▪
You can have the measurement unit
because some locations are below thevary between meter and footsea level.
according to user credentials. See
Setting Your Preferred Measurement
Units (on page 249).
Determines the maximum number of"active" powered dry contact actuatorsthat is permitted concurrently.
▪ Range: 0 to 24▪ Default: 1▪ An "active" actuator is the one that isturned 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
202).

3.

Click Save.

4.

To return to the sensor list on the Peripheral Devices page, click"Peripheral Devices" on the top.

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

206

Click

> Default Threshold Setup.

Chapter 7: Using the Web Interface

2.

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

3.

Make changes as needed.
▪

To enable any threshold, select the corresponding checkbox.

▪

Type a new value in the accompanying text box.

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

Click Save.

Tip: To customize the threshold settings on a per-sensor basis, go to Individual
Sensor/Actuator Pages (on page 217).
To turn on or off any actuator(s):1.

Select one or multiple actuators which are in the same status - on or off.

2.

To select multiple actuators, clickthen select desired actuators.

3.

Click the desired button.

to make checkboxes appear and207

Chapter 7: Using the Web Interface: 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 thesame time. To change this limitation of "powered dry contact" actuators,
modify the active powered dry contact setting. See Peripherals (on page
202).
4.

Confirm the operation when prompted.

If you select a DX2-DH2C2 door handle lock, then the Open and Close buttons
appear. For detailed operations, see Door Handle Status and Control (on page443).
Tip: If intending to control the actuator via the front panel, see Front Panel
Settings (on page 386).
Yellow- or Red-Highlighted Sensors
The PX3 highlights those sensors that enter the abnormal state with a yellow or
red color. Note that numeric sensors can change colors only after you haveenabled 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, seeSensor Threshold Settings (on page 777).

In the following table, "R" represents any numeric sensor's reading. The symbol<= means "smaller than" or "equal to."Sensor status
Unknown

208

Color

States shown in
the interface

Description

unavailable

Sensor state or readings cannot be detected.

Chapter 7: Using the Web Interface

Sensor status

NormalColorStates shown in
the interface

Description

unmanaged

Sensors are not being managed. See Managed vs Unmanaged
Sensors/Actuators (on page 210).

normal▪ Numeric or state sensors are within the normal range.
-- OR -▪ No thresholds have been enabled for numeric sensors.

above upper
warning

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

below lower
warning

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

above upper
criticalUpper Critical threshold < "R"

below lower
critical"R" < Lower Critical threshold

AlarmedalarmedState sensors enter the abnormal state.

OCP alarm

Open▪ Circuit breaker trips.

Warning

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

209

Chapter 7: Using the Web Interface

Managed vs Unmanaged Sensors/Actuators
To manually manage or unmanage/release a sensor or actuator, see
Peripherals (on page 202).

•
•
•

•
•

•
•

Managed sensors/actuators:
PX3 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.

They show one of the managed states. See Sensor/Actuator States (onpage 211).
For managed 'numeric' sensors, their readings are retrieved and displayed.
If any numeric sensor is disconnected or its reading cannot be retrieved, itshows "unavailable" for its reading.
Unmanaged sensors/actuators:
PX3 does NOT communicate with unmanaged sensors/actuators so theirdata is not retrieved.
Unmanaged sensors/actuators are listed only when they are physicallyconnected to PX3.
They disappear when they are no longer connected.

•
•

210

They do not have an ID number.
They show the "unmanaged" state.

Chapter 7: Using the Web Interface

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 208).
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
normalDescription▪ For numeric sensors, it means the readings arewithin the normal range.
▪ For state sensors, it means they enter thenormal 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 Criticalthreshold

above upper critical

Upper Critical threshold < "R"

alarmedThe state sensor enters the abnormal state.

unavailable▪ Communication with the managed sensor is
lost.
-- OR -▪ DX2 DX, DPX2 or DPX3 sensor packages are
upgrading their sensor firmware.

211

Chapter 7: Using the Web Interface

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

Descriptionon

The actuator is turned on.

off

The actuator is turned off.

unavailable▪ Communication with the managed actuator is
lost.
-- OR -▪ DX2 or DX sensor packages are upgrading their
sensor firmware.

Unmanaged sensor/actuator states:
State

Description

unmanaged

Sensors or actuators are physically connected to
the PX3 but not managed yet.

Note: Unmanaged sensors or actuators will disappear from the web interface
after they are no longer physically connected to the PX3. To manage asensor/actuator, go to Peripherals (on page 202).
Finding the Sensor's Serial Number
A DPX environmental sensor package includes a serial number tag on thesensor cable.

212

Chapter 7: Using the Web Interface

A DX2 DX, DPX2 or DPX3 sensor package has a serial number tag attached to its
rear side.

The serial number for each sensor or actuator appears listed in the webinterface after each sensor or actuator is detected by the PX3. Match the serial
number from the tag to those listed in the sensor table.

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 bedaisy chained.
PX3 can indicate where each sensor or actuator is connected on the Peripheral
Devices page.

•

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.

213

Chapter 7: Using the Web Interface•

If a Raritan DPX3-ENVHUB4 sensor hub is involved, the hub port
information is also indicated for DX2, DX, DPX2 and DPX3 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:

ExamplePort 1
Port 1,

Physical position
Connected to the sensor port #1.
▪ Connected to the sensor port #1.
▪ The sensor/actuator is the 2nd channel of the sensor package.

Channel 2
Port 1,▪ Connected to the sensor port #1.
▪ The sensor/actuator is located in the 4th sensor package of the sensor chain.

Chain Position 4
Port 1,
Chain Position 3,▪ 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.

Channel 2
Port 1,
Chain Position 1,
Hub Port 2,
Chain Position 3

214▪ Connected to the sensor port #1.
▪ Connected to the 2nd port of the DPX3-ENVHUB4 sensor hub, which shows thefollowing 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.

Chapter 7: Using the Web Interface

How the Automatic Management Function Works
This setting is configured on Peripherals (on page 202).
After enabling the automatic management function:
When the total number of managed sensors and actuators has not reached theupper limit yet, PX3 automatically brings newly-connected environmental
sensors and actuators under management after detecting them.
PX3 can manage up to 32 sensors/actuators.
After disabling the automatic management function:
PX3 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
202).
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,
you cannot manage additional ones. The only way to manage any
sensor/actuator is to release or replace the managed ones. To replace amanaged one, assign an ID number to it by following the procedure below. To
release any one, see Peripherals (on page 202).
To manage only one sensor/actuator:
1.

From the list of "unmanaged" sensors/actuators, click the one you want tomanage.

215

Chapter 7: Using the Web Interface

2.

The Manage Peripheral Device dialog appears.

▪

To let PX3 randomly assign an ID number to it, select "Automaticallyassign 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 andabsolute humidity values.

216▪

A relative humidity value is measured in percentage (%).

▪

An absolute humidity value is measured in grams per cubic meter(g/m3).

Chapter 7: Using the Web Interface

However, only relative humidity sensors are "automatically" managed if theautomatic 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 andposition.

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 202).
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 (onpage 208). In addition, you can have PX3 automatically generate alert
notifications for any warning or critical status. See Event Rules and Actions (onpage 316).
To configure a numeric sensor's threshold settings:
1.

Click Edit Thresholds.

Tip: The date and time shown on the PX3 web interface are automaticallyconverted to your computer's time zone. To avoid time confusion, it issuggested to apply the same time zone settings as those of PX3 to yourcomputer or mobile device.

217

Chapter 7: Using the Web Interface

2.

Select or deselect 'Use default thresholds' according to your needs.

▪

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 ofPeripherals (on page 202).

▪

To customize the threshold settings for this particular sensor, deselectthe 'Use default thresholds' checkbox, and then modify the thresholdfields below it.

Note: For concepts of thresholds, deassertion hysteresis and assertion
timeout, see Sensor Threshold Settings (on page 777).
3.

218

Click Save.

Chapter 7: Using the Web Interface

To set up a sensor's or actuator's physical location and additionalsettings:
1.

Click Edit Settings.

2.

Make changes to available fields, and then click Save.

FieldsDescription

Name

A name for the sensor or actuator.

Description

Any descriptive text you want.

Location (X, Y
and Z)

Describe the sensor's or actuator's location in the data center by typing alphanumericvalues for the X, Y and Z coordinates. See Sensor/Actuator Location Example (on page
223).
If the term "Rack Units" appears in parentheses in the Z location, you must type an
integer number. The Z coordinate's format is determined on the page of Peripherals (onpage 202).

Alarmed toNormal Delay

This field is available for the DX-PIR presence detector only.
It determines the wait time before the PX3 announces that the presence detector isback to normal after it already returns to normal.
Adjust the value in seconds.

Binary Sensor
SubtypeThis field is available for any Raritan contact closure sensor except for DX2-DH2C2's
contact closure sensors.
Determine the sensor type of your contact closure detector.
▪
▪
▪
▪

Contact Closure detects the door lock or door open/closed status.
Smoke Detection detects the appearance of smoke.
Water Detection detects the appearance of water on the floor.
Vibration detects the vibration of the floor.

219

Chapter 7: Using the Web Interface

FieldsSensor Polarity

Description
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. Notethat only a numeric sensor has this diagram. State sensors and actuators do nothave such data.

220

Chapter 7: Using the Web Interface▪

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

To turn on or off an actuator:
1.

Click the desired control button.

: Turn ON.
: Turn OFF.
2.

Confirm the operation on the confirmation message. An actuator's state ismarked in red when it is turned on.

221Chapter 7: Using the Web Interface

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 202).
Other operations:
You can go to another sensor's or actuator's data/setup page by clicking theselectoron the top-left corner.

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 todescribe Z coordinates.
For a Z coordinate example, see Sensor/Actuator Location Example (on page
223).
To configure Z coordinates:
1.

Determine the Z coordinate format on Peripherals (on page 202). Available
Z coordinate formats include:
FormatDescription

Rack units

The height of the Z coordinate is measured in standard
rack units.
When this is selected, you can type a numeric value inthe rack unit to describe the Z coordinate of any
environmental sensors or actuators.

222

Chapter 7: Using the Web Interface

2.

FormatDescription

Free-form

Any alphanumeric string can be used for specifying theZ coordinate. The value comprises 0 to 24 characters.

Configure Z coordinates on the Individual Sensor/Actuator Pages (on page
217).

Sensor/Actuator Location Example

Use the X, Y and Z coordinates to describe each sensor's or actuator's physicallocation in the data center. See Individual Sensor/Actuator Pages (on page217).
The X, Y and Z values act as additional attributes and are not tied to any specificmeasurement 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 anyalphanumeric value comprising 0 to 24 characters. See Peripherals (onpage 202).

Feature PortThe FEATURE port supports connection to the following devices.
DeviceDescription

Asset Strip

Raritan asset strips

External Beeper

An external beeper with the RJ-45 socket.

LHX 20Schroff® LHX-20 heat exchanger.

SHX 30Schroff® SHX-30 heat exchanger.

LHX 40Schroff® LHX-40 heat exchanger.

223

Chapter 7: Using the Web Interface

DeviceDescription

Power CIM

This type represents one of the following Raritan products:▪ Raritan power CIM, D2CIM-PWR. This CIM is used toconnect the PX3 to the Raritan digital KVM switch -Dominion KX II / III.
▪ Dominion KSX II▪ Dominion SX or SX IIWhen the PX3 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 225), External Beeper (on page233), Schroff LHX/SHX (on page 234) and Power CIM (on page 239).
When no devices are detected, the PX3 displays the name 'Feature Port" andthe Feature Port page shows the message "No device is currently connected."
Open the Feature Port page by clicking it in the Menu (on page 167). From thispage, you can enable or disable this port's detection capability, or force it toshow a specific device's data/settings even though no device is detected.
Note: You must enable the LHX/SHX support for the PX3 to detect the presenceof a supported Schroff® LHX/SHX heat exchanger. See Miscellaneous (on page394).
To configure the feature port:

224

1.

Click

on the top-right corner. The Feature Port Setup dialog appears.

2.

Click the Detection Mode field, and select one mode.
Mode

Description

AutoEnable the port to automatically detect the device
connection.

Disabled

Disable the port's detection capability.

Chapter 7: Using the Web Interface

Mode

Description

Asset Strip,

Force the PX3 to show the selected device's
data/setup page regardless of the physicalconnection status.

Raritan asset strips,
LHX 20,
SHX 30,
LHX 40,Power CIM

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 394).
Asset Strip
After connecting and detecting Raritan asset management strips (asset strips),
the PX3 shows 'Asset Strip' in place of 'Feature Port' in the menu.
Note: For connection instructions, see Connecting Asset Management Strips(on page 68).
To open the Asset Strip page, click it in the Menu (on page 167). 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 page 223).

on the top-right corner, see Feature Port

To configure asset strip and rack unit settings:
1.

Click Edit Settings.

2.

Make changes to the settings by directly typing a new value, or clicking
that field to select a different option.

225

Chapter 7: Using the Web Interface

Field

Description

Name

Name for this asset strip assembly.

Number of rackunits

Total of available tag ports on this asset strip
assembly, ranging between 8 and 64.
▪ For the current generation of asset strips, whichshow the suffix "G3" on its hardware label, thePX3 automatically detects the number of its tag
ports (rack units), and you cannot change thisvalue.
▪ For old "non-G3" asset strips, there is noautomatic 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 thehighest rack unit of a rack/cabinet.
▪ Bottom-Up: The numbering starts from thelowest 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 firstnumber is 3, the second number is 4, and so on.

Orientation

The asset strip's orientation by indicating thelocation of its RJ-45 connector.
▪ Top Connector: The RJ-45 connector is locatedon the top.
▪ Bottom Connector: The RJ-45 connector is
located on the bottom.
Asset strips can detect their strip orientation andshow it in this field.
You need to adjust this value only when your asset
strips are the oldest ones without tilt sensors
implemented.

Color withconnected 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.
▪

226

Click a color in the color palette.

Chapter 7: Using the Web Interface▪

3.

Type the hexadecimal RGB value of the color, such as #00FF00.

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 theasset strip, which is not configurable. However, its order will change toreflect the latest rack unit numbering.

▪

A blade extension strip and a programmable tag are marked with theword '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 170).

227

Chapter 7: Using the Web Interface

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 theselected one appears.

2.

Make changes to the information by typing a new value or clicking thatfield to select a different option.
Field

Description

Name

Name for this rack unit.
For example, you can name it based on theassociated 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 theasset tag's presence.
▪ Manual Override: This option differentiates thisrack unit's LED behavior.

228

Chapter 7: Using the Web Interface

Field

Description

LED ModeThis field is configurable only after the Operation
Mode is set to Manual Override.
Determine how the LED light behaves for thisparticular rack unit.
▪
▪
▪
▪

LED Color

On: The LED stays lit.
Off: The LED stays off.
Slow blinking: The LED blinks slowly.
Fast blinking: The LED blinks quickly.
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 theasset strip, wait at least 1 second before re-connecting it back, or the PX3
device may not detect it.
1.

Locate the rack unit (tag port) where the blade extension strip isconnected. Click its slot number, whose format is similar towhere N is the total number of its tag ports.

,

229

Chapter 7: Using the Web Interface

2.

All tag ports of the blade extension strip are listed below it. Their port
numbers are displayed in the Slot column.

▪

230

To hide the blade extension slots list, click.

Chapter 7: Using the Web Interface

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

Click Program Asset IDs.

2.

In the Asset/ID column, enter the customized asset IDs by typing values orscanning the barcode.
▪

When using a barcode reader, first click the desired rack unit, and thenscan the asset tag. Repeat this step for all desired rack units.

231

Chapter 7: Using the Web Interface▪

An asset ID contains up to 12 characters that comprise only numbers
and/or UPPER CASE alphabets. Lower case alphabets are NOT
accepted.

3.

Verify the correctness of customized asset IDs and modify as needed.

4.

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.

232Chapter 7: Using the Web Interface

Asset Strip Automatic Firmware Upgrade

After connecting the asset strip to the PX3, it automatically checks its own
firmware version against the version of the asset strip firmware stored in the
PX3 firmware. If two versions are different, the asset strip automatically starts
downloading the new firmware from the PX3 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 throughdiverse colors.
A firmware upgrade process is indicated in the PX3 web interface.
An SNMP trap is sent to indicate the firmware upgrade event.

External Beeper
After connecting and detecting a supported external beeper, the PX3 shows'External Beeper' in place of 'Feature Port' in the menu.
Note: For connection instructions, see Connecting an External Beeper (on page80).
To open the External Beeper page, click it in the Menu (on page 167). This pageshows 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
(on page 223).

on the top-right corner, see Feature Port

233

Chapter 7: Using the Web Interface

Schroff LHX/SHX
You must enable the LHX/SHX support for the PX3 to detect the presence of a
supported Schroff® LHX/SHX heat exchanger. See Miscellaneous (on page 394).
After enabling the LHX/SHX support and connecting a supported Schroff®
LHX/SHX heat exchanger to the PX3, the PX3 shows the connected device typein 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 80).
To open the LHX/SHX page, click 'LHX 20', 'LHX 40' or 'SHX 30' in the Menu (onpage 167). 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
PX3 port.

234

Chapter 7: Using the Web Interface

For the functionality of this icon
(on page 223).

on the top-right corner, see Feature PortTo view the LHX/SHX device state:
The Operation State field indicates whether the device is operating fine, andthe 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.

To turn on or off the LHX/SHX device:
1.

Click the desired power-control button on the top-right corner.

: Power ON.
: Power OFF.
2.

Confirm the operation on the confirmation message.

235

Chapter 7: Using the Web Interface

To configure LHX/SHX settings:
1.

Click Edit Settings.

2.

Configure the settings as needed.

3.

▪

Provide a customized name.

▪

Specify the desired air outlet setpoint temperature.

▪

Specify the default fan speed.

Click Save.
To view all sensor data and configure thresholds:

1.

Locate the Sensors section, which lists all air outlet/inlet temperatures andfan 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.

236

Click the desired sensor.

Chapter 7: Using the Web Interfaceb.

Click Edit Thresholds.

c.

Enable and set the desired thresholds and deassertion hysteresis.
Note that assertion timeout is NOT available on LHX/SHX.

d.
3.

Click Save.

After thresholds are enabled, sensors may be highlighted in yellow or red ifthey enter the warning or critical range. See Yellow- or Red-Highlighted
Sensors (on page 208).

Tip: You can also create event rules to notify you of the warning or critical levels.
See Event Rules and Actions (on page 316).
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.

237

Chapter 7: Using the Web Interface

2.

If any LHX sensors fail, they are indicated. Click Acknowledge toacknowledge the sensor failure.

3.

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 PX3 and turned on.
Available time units in the statistics -••h: hour(s)d: day(s)Request maximum cooling:
Only SHX 30 supports this feature. See SHX Request Maximum Cooling (onpage 239).

238

Chapter 7: Using the Web Interface

SHX Request Maximum Cooling

The PX3 allows you to remotely activate the Schroff SHX 30's maximum coolingfeature. Both LHX 20 and LHX 40 do not support remote activation of maximum
cooling.
The Request Maximum Cooling feature is available only after the PX3 detects
SHX 30. For additional information on the SHX 30 maximum cooling feature,refer to 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 PX3 shows 'Power
CIM' in place of 'Feature Port' in the menu. See Dominion KX II / III
Configuration (on page 812) or Dominion KSX II, SX or SX II Configuration (onpage 817).
Open the Power CIM page by clicking it in the Menu (on page 167). This pageshows 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
(on page 223).

on the top-right corner, see Feature Port

239

Chapter 7: Using the Web Interface

User Management
User Management menu deals with user accounts, permissions, and preferredmeasurement units on a per-user basis.
PX3 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
PX3 so you must assign one or multiple roles to each user.
Click 'User Management' in the Menu (on page 167), and the following
submenu displays.

240

Submenu command

Refer to...

Users

Creating Users (on page 241)

Roles

Creating Roles (on page 246)

Change Password

Changing Your Password (on page 162)

User Preferences

Setting Your Preferred Measurement Units (on page249)

Default Preferences

Setting Default Measurement Units (on page 250)

Chapter 7: Using the Web Interface

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

User information:
Field/setting

Description

User name

The name the user enters to log in to the PX3.

Full name▪

4 to 32 characters▪

Case sensitive▪

Colon character and spaces are NOT
permitted.

The user's first and last names.

Password,▪

4 to 64 characters

Confirm password▪

Case sensitive▪

Spaces are permitted.

Telephone number

The user's telephone number

Email address

The user's email address▪

Up to 128 characters▪

Case sensitive

EnableWhen selected, the user can log in to the PX3.

Force password
change on next login

When selected, a password change request
automatically appears the next time the user logs in.
For details, see Changing Your Password (on page
162).

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

Open the SSH public key with a text editor.

241

Chapter 7: Using the Web Interface

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 (onpage 281).

Security level

Click the field to select a preferred security level fromthe list:▪ None: No authentication and no privacy. This is thedefault.
▪ Authentication: Authentication and no privacy.
▪ Authentication & Privacy: Authentication andprivacy.

•

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 isidentical 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 printablecharacters.

•

242

Privacy Password: This section is configurable only when 'Authentication &Privacy' is selected.
Field/setting

Description

Same asauthentication
password

Select this checkbox if the privacy password isidentical to the authentication password.
To specify a different privacy password, disable thecheckbox.

Chapter 7: Using the Web Interface

Field/setting

Description

Password,

Type the privacy password if the 'Same as
Authentication Password' checkbox is deselected.

Confirm password

The password must consist of 8 to 32 ASCII printablecharacters.
•

Protocol: This section is configurable only when 'Authentication' or'Authentication & Privacy' is selected.
Field/setting

Description

Authentication

Click this field to select the desired authentication
protocol. Two protocols are available:

Privacy▪

MD5▪

SHA-1 (default)

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

Length unit

Preferred units for length or height -- Meter or Feet.

Pressure unit

Preferred units for pressure -- Pascal or Psi.

(Celsius) or▪ Pascal = one newton per square meter▪ Psi = pounds per square inch243

Chapter 7: Using the Web Interface

Note: Users can change the measurement units at any time by setting their own
preferences. See Setting Your Preferred Measurement Units (on page 249).
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, auser can have a maximum of 32 roles only.
If the built-in roles do not satisfy your needs, add new roles by clicking. This newly-created role will be then automaticallyassigned to the user account currently being created. See Creating Roles (onpage 246).
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
View Event Settings
View 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.

244

Chapter 7: Using the Web Interface

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

▪

To change the password, type a new password in the Password andConfirm Password fields. If the password field is left blank, thepassword remains unchanged.

▪

To delete this user, click, and confirm the operation.

Click Save.
To delete multiple user accounts:

1.

On the Users page, clicknames.

to make checkboxes appear in front of user

Tip: To delete only one user, you can simply click that user without making
the checkboxes appear. Refer to the above procedure.
2.

Select one or multiple users.
▪

To select all roles, except for the admin user, select the topmost
checkbox in the header row.

245

Chapter 7: Using the Web Interface

3.

Click

.

4.

Click Delete on the confirmation message.

Creating Roles
A role is a combination of permissions. Each user must have at least one role.
The PX3 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
View Event Settings
View Local Event Log

If the two do not satisfy your needs, add new roles. PX3 supports up to 64
roles.
To create a role:1.

246

Choose User Management > Roles >.

Chapter 7: Using the Web Interface

2.

Assign a role name.
▪

1 to 32 characters long▪

Case sensitive▪

Spaces are permitted

3.

Type a description for the role in the Description field.

4.

Select the desired privilege(s).

5.

▪

The 'Administrator Privileges' includes all privileges.

▪

The 'Unrestricted View Privileges' includes all 'View' privileges.

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 forthat 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, you can specify the actuators that users can switch on/off asshown below. To select all actuators, select the 'All Actuators' checkbox
instead.

6.

Click Save.

Now you can assign the role to any user. See Creating Users (on page 241) or
Editing or Deleting Users (on page 244).

247

Chapter 7: Using the Web Interface

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

The Admin role is not user-configurable so the lock icon
indicating that you are not allowed to configure it.

displays,

To edit a role:1.

On the Roles page, click the desired role. The Edit Role page opens.

2.

Make changes as needed.

3.

▪

The role name cannot be changed.

▪

To delete this role, click, and confirm the operation.

Click Save.
To delete any roles:

1.

On the Roles page, click

to make checkboxes appear in front of roles.

Tip: To delete only one role, you can simply click that role without making
the checkboxes appear. Refer to the above procedure.
2.

248

Select one or multiple roles.

Chapter 7: Using the Web Interface▪

To select all roles, except for the Admin role, select the topmost
checkbox in the header row.

3.

Click

on the top-right corner.

4.

Click Delete on the confirmation message.

Setting Your Preferred Measurement Units
You can change the measurement units shown in the PX3 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 244).
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 250).
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 -(Fahrenheit).

Length unit

Preferred units for length or height -- Meter or Feet.

Pressure unit

Preferred units for pressure -- Pascal or Psi.

(Celsius) or▪ Pascal = one newton per square meter▪ Psi = pounds per square inch3.

Click Save.

249

Chapter 7: Using the Web Interface

Setting Default Measurement Units
Default measurement units are applied to all PX3 user interfaces across allusers, including users accessing the PX3 via external authentication servers.
For a list of affected user interfaces, see User Interfaces Showing Default Units(on page 250). The front panel display also shows the default measurement
units.
Note: The preferred measurement units set by any individual user or by theadministrator on a per-user basis will override the default units in the webinterface and command line interface. See Setting Your Preferred
Measurement Units (on page 249) or Creating Users (on page 241).
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 -(Fahrenheit).

Length unit

Preferred units for length or height -- Meter or Feet.

Pressure unit

Preferred units for pressure -- Pascal or Psi.

(Celsius) or▪ Pascal = one newton per square meter▪ Psi = pounds per square inch3.

Click Save.

User Interfaces Showing Default Units

Default measurement units will apply to the following user interfaces or data:
•

•
•
•

250

Web interface for "newly-created" local users when they have notconfigured their own preferred measurement units. See Creating Users(on page 241).
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 345).
Front panel LCD display.

Chapter 7: Using the Web Interface

Device Settings
Click 'Device Settings' in the Menu (on page 167), and the following submenu
displays.

Menu command

Submenu command

Network
Network Services

Refer to...
Configuring Network Settings (on page 253)

HTTP

Changing HTTP(S) Settings (on page 279)

SNMP

Configuring SNMP Settings (on page 281)

251

Chapter 7: Using the Web Interface

Menu command

Security

252

Submenu command

Refer to...

SMTP Server

Configuring SMTP Settings (on page 283)

SSH

Changing SSH Settings (on page 284)

TelnetChanging Telnet Settings (on page 285)

ModbusChanging Modbus Settings (on page 285)

Server Advertising

Enabling Service Advertising (on page 288)

IP Access Control

Creating IP Access Control Rules (on page 290)

Role Based AccessControlCreating Role Based Access Control Rules (on page 294)

TLS Certificate

Setting Up a TLS Certificate (on page 296)

Authentication

Setting Up External Authentication (on page 301)

Login Settings

Configuring Login Settings (on page 308)

Password Policy

Configuring Password Policy (on page 309)

Service Agreement

Enabling the Restricted Service Agreement (on page 310)

Date/Time

Setting the Date and Time (on page 312)

Event Rules

Event Rules and Actions (on page 316)

Data Logging

Setting Data Logging (on page 372)

Data Push

Configuring Data Push Settings (on page 373)

Server Reachability

Monitoring Server Accessibility (on page 382)

Front Panel

Front Panel Settings (on page 386)

Serial Port

Configuring the Serial Port (on page 387)

Lua Scripts

Lua Scripts (on page 389)

Miscellaneous

Miscellaneous (on page 394)

Chapter 7: Using the Web Interface

Configuring Network Settings
Configure wired, wireless, and Internet protocol-related settings on the
Network page after Connecting the PX3 to Your Network (on page 22).
You can enable both the wired and wireless networking on PX3 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 PX3 enters the port forwarding mode so that PX3 hasmore than one IPv4 or IPv6 address in the port forwarding mode.
However, PX3 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 ETH1/ETH2 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 (onpage 256).
▪

3.

To configure IPv4/IPv6 settings for a wired network, click the ETH1/ETH2 or
BRIDGE section. See Wired Network Settings (on page 254).
▪

4.

Static routes and cascading mode are also in this section. You need toconfigure them only when there are such local requirements. See
Setting the Cascading Mode (on page 270) and Static Route Examples(on page 266).

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.

To configure IPv4/IPv6 settings for a wireless network, click the WIRELESS
section. See Wireless Network Settings (on page 260).
▪

You must connect a USB wireless LAN adapter to the PX3 for wirelessnetworking.

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

To configure the ETH1/ETH2 interface settings, see Ethernet Interface
Settings (on page 257).

6.

Click Save.

253

Chapter 7: Using the Web Interface

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
TelnetFTP
SSL/TLS
SNMP
SysLogNote: PX3 disables TLS 1.0 and 1.1 by default. It enables only TLS 1.2 and 1.3.
Wired Network Settings

On the Network page, click the ETH1/ETH2 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 270).
Enable Interface:
Make sure the Ethernet interface is enabled, or all networking through thisinterface fails. This setting is available in the ETH1/ETH2 section, but notavailable in the BRIDGE section.

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.
Preferred hostname

254

Enter the hostname you prefer for IPv4 connectivity

Chapter 7: Using the Web Interface••

DHCP settings: Optionally specify the preferred hostname, which mustmeet 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 "IPaddress/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.
Preferred hostname••▪ Enter the hostname you prefer for IPv6
connectivity

Automatic settings: Optionally specify the preferred hostname, whichmust meet the above requirements.
Static settings: Assign a static IPv6 address, which follows this syntax "IPaddress/prefix length".
Example: fd07:2fa:6cff:1111::0/128

255Chapter 7: Using the Web Interface•(Optional) To view the diagnostic log for EAP authentication:
Click Show EAP Authentication Log. See Diagnostic Log for Network
Connections (on page 265).

Common Network Settings

Common Network Settings are OPTIONAL, not required. Therefore, leave themunchanged if there are no specific local networking requirements.
Field

Description

Cascading mode

Leave it to the default "None" unless you areestablishing a cascading chain.
For more information, refer to:▪ Cascading Multiple PX3 Devices for Sharing
Ethernet Connectivity (on page 34)▪ Setting the Cascading Mode (on page 270)

DNS resolver
preference

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)

256

Specify a DNS suffix name if needed.

Chapter 7: Using the Web Interface

Field

Description

First/Second/Third
DNS server

Manually specify static DNS server(s).

IPv4/IPv6 routes

You need to configure these settings only when yourlocal network contains two subnets, and you want PX3
to communicate with the other subnet.

▪ 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 PX3 will use DHCP-assigned DNS
servers.

If so, make sure IP forwarding has been enabled inyour network, and then you can click 'Add Route' to
add static routes.
See Static Route Examples (on page 266).

Ethernet Interface Settings

By default both ETH1 and ETH2 interfaces on PX3 are enabled.
Enable Interface:
Make sure the Ethernet interface is enabled, or all networking through thisinterface fails. This setting is available in the ETH1/ETH2 section, but notavailable in the BRIDGE section.

Other Ethernet settings:
Field

Description

Speed

Select a LAN speed.
••••

DuplexAuto: System determines the optimum LAN speed
through auto-negotiation.
10 MBit/s: Speed is always 10 Mbps.
100 MBit/s: Speed is always 100 Mbps.
1 GBit/s: Speed is always 1 Gbps (1000 Mbps).

Select a duplex mode.
••

Auto: The PX3 selects the optimum transmission
mode through auto-negotiation.
Full: Data is transmitted in both directions

257

Chapter 7: Using the Web Interface

Field

Description•

simultaneously.
Half: Data is transmitted in one direction (to orfrom the PX3) at a time.

Current stateShow the LAN's current status, including the current
speed and duplex mode.

Authentication

Select an authentication method.
▪ No Authentication: No authentication data isrequired.
▪ EAP: Use Protected Extensible Authentication
Protocol. Enter required authentication data in thefields that appear.

Outer authentication

This field appears when 'EAP' is selected.
There are two authentication methods for EAP.
▪ PEAP: A TLS tunnel is established, and an innerauthentication method can be specified for thistunnel.
▪ TLS: Authentication between the client andauthentication server is performed using TLS
certificates.

Inner authentication

This field appears when both 'EAP' and 'PEAP' areselected.
▪ MS-CHAPv2: Authentication based on the given
password using MS-CHAPv2 protocol.
▪ TLS: Authentication between the client andauthentication server is performed using TLS
certificates.

IdentityThis field appears when 'EAP' is selected.
Type your user name.

Password

This field appears only when 'EAP', 'PEAP' and'MS-CHAPv2' are all selected.
Type your password.

258

Chapter 7: Using the Web Interface

Field

Description

Client certificate,This field appears when 'EAP', 'PEAP' and 'TLS' are
all selected.

Client private key,
Client private key
password

PEM encoded X.509 certificate and PEM encoded
private key are required for certification-based
authentication methods. Private key password is
optional.
▪ PX3 supports private keys of PKCS#1 and PKCS#8
formats.
▪ Client Private Key Password should be entered only
when your private key is encrypted with apassword.
▪ To view the uploaded certificate, click Show Client
Certificate.
▪ To remove the uploaded certificate and private
key, click 'Clear Key/Certificate selection'.

CA certificate

This field appears when 'EAP' is selected.
A third-party CA certificate may or may not be needed.
If needed, follow the steps below.

RADIUSauthentication server
nameThis field appears when 'EAP' is selected.
Type the name of the RADIUS server if it is present in
the TLS certificate.
▪ The name must match the fully qualified domainname (FQDN) of the host shown in the certificate.

Note: Auto-negotiation is disabled after setting both the speed and duplex
settings of the PX3 to NON-Auto values, which may result in a duplex mismatch.
•

Available settings for the CA Certificate:

If the required certificate file is a chain of certificates, and you are not sure
about the requirements of a certificate chain, see TLS Certificate Chain (onpage 804).
Field/setting

Description

Enable verification of Select this checkbox for the PX3 to verify the validity
TLS certificate chain of the TLS certificate that will be installed.
▪ For example, the PX3 will check the certificate's
validity period against the system time.

259

Chapter 7: Using the Web Interface

Field/setting

Description
Click this button to import a certificate file. Then you
can:▪ Click Show to view the certificate's content.
▪ Click Remove to delete the installed certificate if it
is inappropriate.

Allow expired andnot yet valid
certificates▪ Select this checkbox to make the authentication
succeed regardless of the certificate's validity
period.
▪ After deselecting this checkbox, the authentication
fails whenever any certificate in the selectedcertificate chain is outdated or not valid yet.

Allow connection if
system clock isincorrect

When this checkbox is deselected, and if the systemtime is incorrect, the installed TLS certificate isconsidered not valid yet and will cause the wirelessnetwork connection to fail.
When this checkbox is selected, it will make thewireless network connection successful when the PX3
system time is earlier than the firmware build before
synchronizing with any NTP server.
▪ The incorrect system time issue may occur when
the PX3 has once been powered off for a long time.

Wireless Network Settings

If the device's cascading mode is set to 'Bridging' or its role is set to 'Slave' inthe port forwarding mode, the wireless settings will be disabled. See Setting
the Cascading Mode (on page 270).
By default the wireless interface is disabled. You should enable it if wirelessnetworking is wanted.
On the Network page, click the WIRELESS section to configure wireless andIPv4/IPv6 settings.
Interface Settings:
Field/setting

Description

Enable interface

Enable or disable the wireless interface.
When disabled, the wireless networking fails.

Hardware state

260

Check this field to ensure that the PX3 has detected awireless USB LAN adapter. If not, verify whether theChapter 7: Using the Web Interface

Field/setting

Description
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 HighThroughput(802.11n)

Enable or disable 802.11n protocol.

Authentication

Select an authentication method.
▪ No Authentication: No authentication data isrequired.
▪ PSK: A Pre-Shared Key is required.
▪ EAP: Use Protected Extensible Authentication
Protocol. Enter required authentication data in thefields that appear.

Pre-Shared Key

This field appears only when PSK is selected.
Type the PSK string.

Outer authentication

This field appears when 'EAP' is selected.
There are two authentication methods for EAP.
▪ PEAP: A TLS tunnel is established, and an innerauthentication method can be specified for thistunnel.
▪ TLS: Authentication between the client andauthentication server is performed using TLS
certificates.

Inner authentication

This field appears when both 'EAP' and 'PEAP' areselected.
▪ MS-CHAPv2: Authentication based on the given
password using MS-CHAPv2 protocol.
▪ TLS: Authentication between the client andauthentication server is performed using TLS
certificates.

261

Chapter 7: Using the Web Interface

Field/setting
Identity

Description
This field appears when 'EAP' is selected.
Type your user name.

Password

This field appears only when 'EAP', 'PEAP' and'MS-CHAPv2' are all selected.
Type your password.

Client certificate,
Client private key,
Client private key
password

This field appears when 'EAP', 'PEAP' and 'TLS' are
all selected.
PEM encoded X.509 certificate and PEM encoded
private key are required for certification-based
authentication methods. Private key password is
optional.
▪ PX3 supports private keys of PKCS#1 and PKCS#8
formats.
▪ Client Private Key Password should be entered only
when your private key is encrypted with apassword.
▪ To view the uploaded certificate, click Show Client
Certificate.
▪ To remove the uploaded certificate and private
key, click 'Clear Key/Certificate selection'.

CA certificate

This field appears when 'EAP' is selected.
A third-party CA certificate may or may not be needed.
If needed, follow the steps below.

RADIUSauthentication server
nameThis field appears when 'EAP' is selected.
Type the name of the RADIUS server if it is present in
the TLS certificate.
▪ The name must match the fully qualified domainname (FQDN) of the host shown in the certificate.

262

Chapter 7: Using the Web Interface•

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 (onpage 804).
Field/setting

Description

Enable verification of Select this checkbox for the PX3 to verify the validity
TLS certificate chain of the TLS certificate that will be installed.
▪ For example, the PX3 will check the certificate's
validity period against the system time.
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 andnot yet valid
certificates▪ Select this checkbox to make the authentication
succeed regardless of the certificate's validity
period.
▪ After deselecting this checkbox, the authentication
fails whenever any certificate in the selectedcertificate chain is outdated or not valid yet.

Allow connection if
system clock isincorrect

When this checkbox is deselected, and if the systemtime is incorrect, the installed TLS certificate isconsidered not valid yet and will cause the wirelessnetwork connection to fail.
When this checkbox is selected, it will make thewireless network connection successful when the PX3
system time is earlier than the firmware build before
synchronizing with any NTP server.
▪ The incorrect system time issue may occur when
the PX3 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.
Preferred hostnameEnter the hostname you prefer for IPv4 connectivity

263

Chapter 7: Using the Web Interface••

DHCP settings: Optionally specify the preferred hostname, which mustmeet 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 "IPaddress/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.
Preferred hostname••▪ Enter the hostname you prefer for IPv6
connectivity

Automatic settings: Optionally specify the preferred hostname, whichmust meet the above requirements.
Static settings: Assign a static IPv6 address, which follows this syntax "IPaddress/prefix length".
Example: fd07:2fa:6cff:1111::0/128•

264(Optional) To view the wireless LAN diagnostic log:
Click Show WLAN Diagnostic Log. See Diagnostic Log for Network
Connections (on page 265).

Chapter 7: Using the Web Interface

Diagnostic Log for Network Connections

PX3 provides a diagnostic log for inspecting connection errors that occurred
during the EAP authentication or the wireless network connection. The
information is useful for technical support.
Note that the diagnostic log shows data only after connection errors aredetected.
Each entry in the log consists of:•••

ID number
Date and time
Description
To view the log:

1.

2.

Access the diagnostic log with either method below.
▪

Choose Device Settings > Network > ETH1/ETH2 > Show EAP
Authentication Log. See Configuring Network Settings (on page 253).

▪

Choose Device Settings > Network > WIRELESS > Show WLAN
Diagnostic Log.

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
▪

3.

.

To restore automatic update, click. Those new
events that have not been listed yet due to suspension will be
displayed in the log now.

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 thenext or previous five page numbers, if available.

4.

If wanted, you can resort the list by clicking the desired column header.
See Sorting a List (on page 170).
To clear the diagnostic log:

1.

On the top-right corner of the log, click>

2.

Click Clear Log on the confirmation message.

.

265

Chapter 7: Using the Web Interface

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 beenenabled. All of the NICs and PX3 devices in the examples use static IP
addresses.
Most of local multiple networks are not directly reachable and require the useof 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 ofentering an IP address. See Interface Names (on page 269).

•
•
•
•

266

IPv4 example:
Your PX3: 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

Chapter 7: Using the Web Interface

In this example, NIC-2 (192.168.100.88) is the next hop router for your PX3 tocommunicate 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.

267

Chapter 7: Using the Web Interface

Tip: If you have configured multiple static routes, you can click on any route andthen make changes, useorto re-sort the priority, or click

to delete it.

•
•
•
•

268

IPv6 example:
Your PX3: 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

Chapter 7: Using the Web Interface

In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for yourPX3 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.

Tip: If you have configured multiple static routes, you can click on any route andthen make changes, useorto re-sort the priority, or click

to delete it.

Interface Names

When your local multiple networks are "directly reachable", you should selectInterface for static routes. Then choose the interface where another network isconnected.

Interface list:
Interface name
BRIDGE

Description
When another wired network is connected to the
Ethernet port of your PX3, and your PX3 has been set
to the bridging mode, select this interface nameinstead of the Ethernet interface.

ETH1

When another wired network is connected to theETH1 port of your PX3, select this interface name.

ETH2

When another wired network is connected to theETH2 port of your PX3, select this interface name.

WIRELESS

When another wireless network is connected to yourPX3, select this interface name.

269

Chapter 7: Using the Web Interface

Setting the Cascading Mode

A maximum of 16 PX3 devices can be cascaded to share one Ethernet
connection. See Cascading Multiple PX3 Devices for Sharing Ethernet
Connectivity (on page 34).
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 272).
The cascading mode of all devices in the chain must be the same.
Only a user with the Change Network Settings permission can configure thecascading mode.
Note: PX3 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, orconnect it to a computer.
▪

For computer connection instructions, see Connecting the PX3 to a
Computer (on page 31).

▪

To find the IP address, see Device Info (on page 141).

2.

Log in to its web interface. See Login (on page 159).

3.

Choose Device Settings > Network.

4.

Select the preferred mode in the Cascading Mode field.
Mode
None

Description
No cascading mode is enabled. This is the default.

Bridging

Each device in the cascading chain is accessedwith a different IP address.

Port Forwarding

Each device in the cascading chain is accessedwith the same IP address(es) but with a different
port number assigned.
For details on port numbers, see Port Number
Syntax (on page 273).

Tip: If selecting Port Forwarding, the Device Information page will show alist of port numbers for all cascaded devices. Simply choose Maintenance >Device Information > Port Forwarding.
5.

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.

270

Chapter 7: Using the Web Interface

Field
Port forwarding role(available on all cascaded
devices)
Downstream interface(available on the maser
device only)

Description
Master or Slave.
This is to determine which device is themaster and which ones are slave devices.
USB or ETH1/ETH2.
This is to determine which port on themaster device is connected to Slave 1.
If ETH1 or ETH2 is selected as thedownstream interface, make sure theselected Ethernet interface is enabled.

6.

(Optional) Configure the network settings by clicking the BRIDGE,
ETH1/ETH2, or WIRELESS section on the same page.
▪

In the Bridging mode, each cascaded device can have different network
settings. You may need to configure each device's network settings in
the BRIDGE section.

▪

In the Port Forwarding mode, all cascaded devices share the masterdevice's network settings. You only need to configure the masterdevice's network settings in the ETH1/ETH2 and/or WIRELESS section.

See Wired Network Settings (on page 254) or Wireless Network Settings(on page 260)
Tip: You can enable/configure multiple network interfaces in the Port
Forwarding mode so that the cascading chain has multiple IP addresses.
7.

Click Save.

For information on accessing each cascaded device in the Port Forwarding
mode, see Port Forwarding Examples (on page 275).
Recommendations for cascade loops:
You can connect both the first and the last PDU to your network (cascadeloop) under the following conditions:a.

The remaining network MUST use R/STP to avoid network loops.
AND

Both the first and the last PDUs MUST either attach to the same switch or, if
they are attached to two separate switches, you must configure both ports ofthese switches so that the STP costs are high. This prevents the STP protocol
from sending unrelated traffic through the PDU cascade, which can cause
bottlenecks that lead to connectivity issues in the whole network.

271

Chapter 7: Using the Web Interface

Online cascading information:
For more information on cascading configurations and restrictions, refer to the
Cascading Guide on the Raritan 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 270).
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:

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 sameas accessing a standalone device in the network.
•"Port Forwarding" mode:

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 thesame IP address as the master device.

272

Chapter 7: Using the Web Interface

You must specify a 5XXXX port number (where X is a number) whenremotely accessing any slave device with the shared IP address. See Port
Number Syntax (on page 273).

•
•
•
•

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 canenable ETH1, ETH2 and WIRELESS interfaces so that thePort-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

273

Chapter 7: Using the Web Interface•

XX is a two-digit number representing the device position as shown below.
PositionXX

Master device

00
01

Slave 1

02

Slave 203

Slave 304

Slave 405

Slave 506

Slave 607

Slave 7

Position
Slave 8
Slave 9Slave 10
Slave 11
Slave 12
Slave 13
Slave 14
Slave 15

XX
08
09
10
11
12
13
14
15

For example, to access the Slave 4 device via Modbus/TCP, the port number is50604. See Port Forwarding Examples (on page 275) for further illustrations.
Tip: The full list of each cascaded device's port numbers can be retrieved fromthe web interface. Choose Maintenance > Device Information > Port
Forwarding.
Standard TCP/UDP ports:
The master device can be also accessed through standard TCP/UDP ports aslisted 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 tomodify the standard TCP/UDP port configuration, including HTTP, HTTPS, SSH,
Telnet and Modbus/TCP.

274

Chapter 7: Using the Web Interface

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 273) 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 aslisted 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:•

To access the master device via HTTP, the IP address is:https://192.168.84.77:443/
http://192.168.84.77:80/•

To access the master device via SSH, the command is:ssh -p 22 192.168.84.77

275

Chapter 7: Using the Web Interface

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

276

Chapter 7: Using the Web Interface

Adding, Removing or Swapping Cascaded Devices

Change a device's cascading mode first before adding that device to acascading 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 (onpage 790).
To add a device to an existing chain:
1.

Connect the device you will cascade to the LAN and find its IP address, orconnect it to a computer.

2.

Log in to this device and set its cascading mode to be the same as theexisting chain's cascading mode. See Setting the Cascading Mode (on page
270).

3.

(Optional) If this device will function as a slave device, disconnect it fromthe 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 anothercascading chain, set its cascading mode to be the same as the mode ofanother chain.

2.

•

•

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.

277

Chapter 7: Using the Web Interface▪

You must disconnect the LAN cable and ALL cascading cables
connected to the two devices first before swapping them, andthen 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

Configuring Network Services
PX3 supports the following network communication services.

278

Chapter 7: Using the Web Interface

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 LineInterface (on page 456).
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 andis thus insecure.
Submenu command

Refer to

HTTP

Changing HTTP(S) Settings (on page 279)

SNMP

Configuring SNMP Settings (on page 281)

SMTP Server

Configuring SMTP Settings (on page 283)

SSH

Changing SSH Settings (on page 284)

TelnetChanging Telnet Settings (on page 285)

ModbusChanging Modbus Settings (on page 285)

Server Advertising

Enabling Service Advertising (on page 288)

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 toand from the PX3 so it is a more secure protocol than HTTP. PX3 disables TLS
1.0 and 1.1 by default. It enables only TLS 1.2 and 1.3.
By default, any access to the PX3 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.

4.

To redirect the HTTP access to the PX3 to HTTPS, select the "Redirect HTTP
connections to HTTPS."▪

The redirection checkbox is configurable only when both HTTP andHTTPS have been enabled.

279

Chapter 7: Using the Web Interface

Special note for AES ciphers:
The PX3 device's TLS-based protocols support AES 128- and 256-bit ciphers. The
exact cipher to use is negotiated between PX3 and the client (such as a web
browser), which is impacted by the cipher priority of PX3 and the client's cipher
availability/settings.
Tip: To force PX3 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.

280

Chapter 7: Using the Web Interface

Configuring SNMP Settings

You can enable or disable SNMP communication between an SNMP manager
and the PX3. Enabling SNMP communication allows the manager to retrieveand 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 notbeen set yet. See Event Rules and Actions (on page 316).
To configure SNMP communication:
1.

Choose Device Settings > Network Services > SNMP.

281

Chapter 7: Using the Web Interface

2.

3.

4.

Enable or disable "SNMP v1 / v2c" and/or "SNMP v3" by clicking thecorresponding 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."

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

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 448)▪

SNMPv3 Notifications (on page 449)

Note: Any changes made to the 'SNMP Notifications' section on the SNMP
page will update the settings of the System SNMP Notification Action, andvice versa. See Available Actions (on page 334). To add more than three
SNMP destinations, you can create new SNMP notification actions. See
Send an SNMP Notification (on page 350).
5.

6.

282

You must download the SNMP MIB for your PX3 to use with your SNMP
manager.
a.

Click the Download MIBs title bar to show the download links.

b.

Click the PDU2-MIB download link. See Downloading SNMP MIB (onpage 452).

Click Save.

Chapter 7: Using the Web Interface

Configuring SMTP Settings

The PX3 can be configured to send alerts or event messages to a specificadministrator by email. See Event Rules and Actions (on page 316).
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 (onpage 405).
To set SMTP server settings:
1.

Choose Device Settings > Network Services > SMTP Server.

2.

Enter the information needed.
Field

Description

IP address/hostnameType the name or IP address of the mail server.

Port

Type the port number.
▪ Default is 25

Sender email address Type an email address for the sender.
Number of sending
retries

Type the number of email retries.

Time between
sending retries

Type the interval between email retries in minutes.

Server requires
authentication

Select this checkbox if your SMTP server requires
password authentication.

User name,

Type a user name and password for authentication
after selecting the above checkbox.

Password▪ Default is 2 retries▪ Default is 2 minutes.

▪ The length of user name and password ranges
between 4 and 64. Case sensitive.
▪ Spaces are not allowed for the user name, butallowed 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 (onpage 804).

283

Chapter 7: Using the Web Interface

Field/setting

Description
Click this button to import a certificate file. Then you
can:▪ Click Show to view the certificate's content.
▪ Click Remove to delete the installed certificate if it
is inappropriate.

Allow expired andnot yet valid
certificates3.

4.

▪ 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 selectedcertificate 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.

Click Save.

Special note for AES ciphers:
The PX3 device's TLS-based protocols support AES 128- and 256-bit ciphers. The
exact cipher to use is negotiated between PX3 and the client (such as a web
browser), which is impacted by the cipher priority of PX3 and the client's cipher
availability/settings.
Tip: To force PX3 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.
▪

284

Password authentication only: Enables the password-based login only.

Chapter 7: Using the Web Interface

5.

▪

Public key authentication only: Enables the public key-based login only.

▪

Password and public key authentication: Enables both the passwordand public key-based login. This is the default.

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 241).
Changing Telnet Settings

You can enable or disable the Telnet access to the command line interface, orchange 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

The PX3 supports both the Modbus/TCP and Modbus Gateway features. Enable
either or both Modbus features according to your needs.
Modbus/TCP Access:You can enable or disable the Modbus/TCP access to PX3, set it to theread-only mode, or change the TCP port.
1.

Choose Device Settings > Network Services > Modbus.

2.

To enable the Modbus/TCP access, select the "Enable 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 "Enableread-only mode" field. To enable the read-write mode, deselect it.

285

Chapter 7: Using the Web Interface

Modbus Gateway:
If connecting the Modbus RTU devices to PX3 and enabling the Modbus
Gateway feature, the Modbus TCP clients on your network will be able tocommunicate with those Modbus RTU devices attached to PX3. See Connecting
a Modbus RTU Device or Bus (on page 81).

286

1.

To allow the Modbus TCP clients on the network to communicate with the
Modbus RTU devices connected to the PX3, select the 'Enable Modbus
gateway' checkbox.

2.

Now configure the fields shown.

Chapter 7: Using the Web Interface

Field

Description

TCP port

Use the default port 503, or assign a different port. Valid range is
1 to 65535.
Note: Port 502 is the default Modbus/TCP port for PX3, so you
cannot use that port for the Modbus Gateway.

Parity,Use the default values, or update if the Modbus RTU devices areusing different communication parameters.

Line speed
Default
address

If the Modbus TCP client does not support Modbus RTU unit
identifier addressing, enter a Default Address.
If you must provide a unit identifier address:▪ Only one Modbus RTU device is supported.
▪ The unit identifier address you provide is applied to the
Modbus RTU device connected to PX3.
Note that each Modbus RTU device's unit identifier address must
be unique.
Warning: If the connected Modbus RTU device's address does notmatch the address entered in this field, communications between
the Modbus TCP clients and Modbus RTU device fail.

287

Chapter 7: Using the Web Interface

Enabling Service Advertising

The PX3 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
Modbusjson-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 canbe used as the zero configuration .local host name, that is,<preferred_host_name>.local, where <preferred_host_name> is the preferredhost name you have specified for PX3. 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 254).
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.

288

▪

To advertise via MDNS, select the Multicast DNS checkbox.

▪

To advertise via LLMNR, select the Link-Local Multicast Name
Resolution checkbox.

Click Save.

Chapter 7: Using the Web Interface

Configuring Security Settings
The PX3 provides tools to control access. You can enable the internal firewall,
create firewall rules, and set login limitations. In addition, you can create andinstall 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 PX3 to be redirected to HTTPS, see
Changing HTTP(S) Settings (on page 279).

Submenu command

Refer toIP Access Control

Creating IP Access Control Rules (on page 290)

Role Based AccessControlCreating Role Based Access Control Rules (on page 294)

TLS Certificate

Setting Up a TLS Certificate (on page 296)

Authentication

Setting Up External Authentication (on page 301)

Login Settings

Configuring Login Settings (on page 308)

Password Policy

Configuring Password Policy (on page 309)

Service Agreement

Enabling the Restricted Service Agreement (on page 310)

289

Chapter 7: Using the Web Interface

Creating IP Access Control Rules

IP access control rules (firewall rules) determine whether to accept or discard
traffic to/from the PX3, 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 PX3, the rules are executed innumerical 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. Thatis, BOTH the address and the prefix length are included. For example, tospecify 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.

5.

290

▪

Accept: Accepts traffic from all IPv4 addresses.

▪

Drop: Discards traffic from all IPv4 addresses, without sending any
failure notification to the source host.

▪

Reject: Discards traffic from all IPv4 addresses, and an ICMP message issent to the source host for failure notification.

Go to the Inbound Rules section or the Outbound Rules section according
to your needs.
▪

Inbound rules control the data sent to the PX3.

▪

Outbound rules control the data sent from the PX3.

Create rules. Refer to the tables below for different operations.

Chapter 7: Using the Web Interface

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

When finished, the rules are listed.

291

Chapter 7: Using the Web Interface

▪

7.

292

You can select any existing rule and then clickchange its priority.

Click Save. The rules are applied.

ortoChapter 7: Using the Web Interface

To configure IPv6 access control rules:
1.

On the same page, select the 'Enable IPv6 access control' checkbox toenable 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.
▪

4.

5.

Ensure the IPv4 or IPv6 checkbox has been selected, or you may notedit or delete any rule.

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 (onpage 290).

▪

Click

▪

To resort its order, click

to remove it.
or.

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.

293

Chapter 7: Using the Web Interface

Creating Role Based Access Control Rules

Role-based access control rules are similar to IP access control rules, exceptthat they are applied to members of a specific role. This enables you to grantsystem permissions to a specific role, based on their IP addresses.
Same as IP access control rules, the order of role-based access control rules isimportant, 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.

▪

Deny: Rejects any user's login attempt when no matching rules arepresent.

Create rules. Refer to the tables below for different operations.

ADD a rule to the end of the list
▪ Click Append.
▪ Type a starting IP address in the Start IP field.
▪ Type an ending IP address in the End IP field.
▪ Select a role in the Role field. This rule applies to members of this role only.
▪ Select an option in the Policy field.
▪

Accept: Accepts traffic from the specified IP address range when the user is a member ofthe specified role.

▪

Deny: Rejects the login attempt of a user from the specified IP address range when thatuser is a member of the specified role.

INSERT a rule between two rules▪ 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.
5.

294

When finished, the rules are listed on this page.

Chapter 7: Using the Web Interface▪

6.

You can select any existing rule and then clickchange its priority.

ortoClick 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 themwhen 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.
▪

4.

Ensure the IPv4 or IPv6 checkbox has been selected, or you may notedit or delete any rule.

Perform the desired action.

295

Chapter 7: Using the Web Interface

5.

▪

Make changes to the selected rule, and then click Save. For
information on each field, see Creating Role Based Access Control
Rules (on page 294).

▪

Click

▪

To resort its order, click

to remove it.
or.

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 a 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 a 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 PX3. See Creating a CSR(on page 297).

2.

Submit it to a certificate authority (CA). After the CA processes theinformation in the CSR, it provides you with a certificate.

3.

Import the CA-signed certificate onto the PX3. See Installing a CA-Signed
Certificate (on page 298).

Note: If you are using a certificate that is part of a chain of certificates, eachpart of the chain is signed during the validation process.

•
•

296

A CSR is not required in either scenario below:
Make the PX3 create a self-signed certificate. See Creating a Self-Signed
Certificate (on page 299).
Appropriate, valid certificate and key files are already available, and you
only need to import them. See Installing or Downloading Existing
Certificate and Key (on page 300).

Chapter 7: Using the Web Interface

Creating a CSR

Follow this procedure to create the CSR for your PX3.
Note that you must enter information in the fields showing the message'required.'To create a CSR:
1.

Choose Device Settings > Security > TLS Certificate.

2.

Provide the information requested.
▪

Subject:

Field

Description

Country

The country where your company is located. Use the standard ISO countrycode, which comprises two uppercase letters. For a list of ISO codes, google
ISO 3166 country codes.

State or province

The full name of the state or province where your company is located.

Locality

The city where your company is located.

Organization

The registered name of your company.

Organizational unit

The name of your department.

Common name

The fully qualified domain name (FQDN) of your PX3.

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 allof them.
Clickto add.
▪

▪

when there are more than one additional hosts
Examples of subject alternative names: support.raritan.com,
help.raritan.com, help.raritan.net, and 192.168.77.50.

Key Creation Parameters:

297

Chapter 7: Using the Web Interface

Field

Do thisKey length

Select an available key length (bits). A larger key length enhances the
security, but slows down the response of PX3.
▪ Only 2048 is available now.

Self-sign

For requesting a certificate signed by the CA, ensure this checkbox is NOT
selected.

Challenge,

Type a password. The password is used to protect the certificate or CSR.
This information is optional.

Confirm challenge

The value should be 4 to 64 characters long. Case sensitive.
3.

Click Create New TLS Key to create both the CSR and private key. This may
take several minutes to complete.

4.

Click Download Certificate Signing Request to download the CSR to yourcomputer.

5.

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.

To store the newly-created private key on your computer, click Download
Key in the New TLS Certificate section.
Note: The Download Key button in the Active TLS Certificate section is fordownloading the private key of the currently-installed certificate rather
than the newly-created one.
▪

6.

You are prompted to open or save the file. Click Save to save it onto
your computer.

After getting the CA-signed certificate, install it. See Installing a CA-Signed
Certificate (on page 298).

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 297).
After receiving the CA-signed certificate, install it onto the PX3.
To install the CA-signed certificate:

298

1.

Choose Device Settings > Security > TLS Certificate.

2.

Click

3.

Click Upload to install it.

to navigate to the CA-signed certificate file.

Chapter 7: Using the Web Interface

4.

To verify whether the certificate has been installed successfully, check thedata shown in the Active TLS Certificate section.

Creating a Self-Signed Certificate

When appropriate certificate and key files for PX3 are unavailable, thealternative, 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.'To create and install a self-signed certificate:1.

Choose Device Settings > Security > TLS Certificate.

2.

Enter information.

Field

Description

Country

The country where your company is located. Use the standard ISO countrycode, which comprises two uppercase letters. For a list of ISO codes, google
ISO 3166 country codes.

State or province

The full name of the state or province where your company is located.

Locality

The city where your company is located.

Organization

The registered name of your company.

Organizational unit

The name of your department.

Common name

The fully qualified domain name (FQDN) of your PX3.

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 PX3.
▪ Only 2048 is available now.

Self-sign

Ensure this checkbox is selected, which indicates that you are creating aself-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 andConfirm Challenge fields disappear.
3.

Click Create New TLS Key to create both the self-signed certificate andprivate key. This may take several minutes to complete.

4.

Once complete, do the following:299

Chapter 7: Using the Web Interfacea.

Double check the data shown in the New TLS Certificate section.

b.

If correct, click "Install Key and Certificate" to install the self-signed
certificate and private key.

Tip: To verify whether the certificate has been installed successfully, checkthe data shown in the Active TLS 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.
5.

(Optional) To download the self-signed certificate and/or private key, click
Download Certificate or Download Key in the New TLS Certificate section.
▪

You are prompted to open or save the file. Click Save to save it onto
your computer.

Note: The Download Key button in the Active TLS Certificate section is fordownloading 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
PX3 for backup or file transfer. For example, you can install the files onto a
replacement PX3, add the certificate to your browser and so on.
If valid certificate and private key files are already available, you can installthem on the PX3 without going through the process of creating a CSR or aself-signed certificate.
Note: If you are using a certificate that is part of a chain of certificates, eachpart of the chain is signed during the validation process.
To download active key and certificate files from PX3:
1.

Choose Device Settings > Security > TLS Certificate.

2.

In the Active TLS Certificate section, click Download Key and Download
Certificate respectively.
Note: The Download Key button in the New TLS Certificate section, if
present, is for downloading the newly-created private key rather than theone of the currently-installed certificate.

3.

You are prompted to open or save the file. Click Save to save it onto yourcomputer.
To install available key and certificate files onto PX3:

300

1.

Choose Device Settings > Security > TLS Certificate.

2.

Select the "Upload key and certificate" checkbox at the bottom of the
page.

3.

The 'Key File' and 'Certificate file' buttons appear. Click each button to
select the key and/or certificate file.

Chapter 7: Using the Web Interface

4.

Click Upload. The selected files are installed.

5.

To verify whether the certificate has been installed successfully, check thedata shown in the Active TLS Certificate section.

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 PX3 must be authenticated.
PX3 supports the following authentication mechanisms:•••

Local user database on the PX3Lightweight Directory Access Protocol (LDAP)
Remote Access Dial-In User Service (Radius) protocol

By default, PX3 is configured for local authentication. If you use this method,
you only need to create user accounts. See Creating Users (on page 241).
If you prefer external authentication, you must provide PX3 with information
about the external Authentication and Authorization (AA) server.
If both local and external authentication is needed, create user accounts on the
PX3 in addition to providing the external AA server data.
When configured for external authentication, all PX3 users must have an
account on the external AA server. Local-authentication-only users will have noaccess to the PX3 except for the admin, who always can access the PX3.
If the external authentication fails, an "Authentication failed" message isdisplayed. Details regarding the authentication failure are available in the event
log. See Viewing or Clearing the Local Event Log (on page 405).
Note that only users who have both the "Change Authentication Settings" and"Change Security Settings" permissions can configure or modify theauthentication settings.
To enable external authentication:
1.

Collect external AA server information. See Gathering LDAP/Radius
Information (on page 302).

2.

Enter required data for external AA server(s) on the PX3. See Adding
LDAP/LDAPS Servers (on page 303) or Adding Radius Servers (on page
306).
▪

3.

For illustrations, see LDAP Configuration Illustration (on page 721) or
RADIUS Configuration Illustration (on page 736).

If both the external and local authentication is needed, or you have toreturn to the local authentication only, see Managing External
Authentication Settings (on page 307).

301

Chapter 7: Using the Web Interface

Special note about the AES cipher:
The PX3 device's TLS-based protocols support AES 128- and 256-bit ciphers. The
exact cipher to use is negotiated between PX3 and the client (such as a web
browser), which is impacted by the cipher priority of PX3 and the client's cipher
availability/settings.
Tip: To force PX3 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 PX3 forexternal authentication. If you are not familiar with these settings, consult yourAA 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▪

▪

Microsoft Active Directory® (AD)
▪

•

302

If using an OpenLDAP server, consult the LDAP administrator for
the Bind Distinguished Name (DN) and password.
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

Chapter 7: Using the Web Interface

Adding LDAP/LDAPS Servers

To use LDAP authentication, enable it and enter the information you havegathered.
Note that you must enter information in the fields showing the message'required.'To add LDAP/LDAPS servers:

Field/setting

1.

Choose Device Settings > Security > Authentication.

2.

Click New in the LDAP Servers section.

3.

Enter information.

Description

IP address / hostname The IP address or hostname of your LDAP/LDAPS server.
▪ Without the encryption enabled, you can type either the domain nameor IP address in this field, but you must type the fully qualified domainname if the encryption is enabled.
Copy settings fromexisting LDAP serverThis checkbox appears only when there are existing AA server settings on
the PX3. To duplicate any existing AA server's settings, refer to the
duplicating procedure below.

Type of LDAP server

Choose one of the following options:▪ OpenLDAP▪ Microsoft 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 PX3 to communicate securely with the LDAPS
server.
Three options are available:▪ StartTLS▪ TLS▪ NonePort (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.

303

Chapter 7: Using the Web Interface

Field/setting

Description

Enable verification of Select this checkbox if it is required to validate the LDAP server's certificate
LDAP server certificate by the PX3 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.
Click

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 804).
Allow expired and not ▪ Select this checkbox to make the authentication succeed regardless ofthe certificate's validity period.
yet valid certificates▪ After deselecting this checkbox, the authentication fails whenever any
certificate in the selected certificate chain is outdated or not valid yet.
Anonymous bindUse this checkbox to enable or disable anonymous bind.
▪ 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,

Required after deselecting the Anonymous Bind checkbox.

Confirm bindpassword

Enter the Bind password.

Base DN for searchDistinguished 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.

304

Chapter 7: Using the Web Interface

Field/setting

Description

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 Directorydomain

The name of the Active Directory Domain.
▪ Example: testradius.com

4.

To verify if the authentication configuration is set correctly, click Test
Connection to check whether the PX3 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 307).

5.

Click Add Server. The new LDAP server is listed on the Authentication page.

6.

To add more servers, repeat the same steps.

7.

In the Authentication Type field, select LDAP. Otherwise, the LDAP
authentication does not work.

8.

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 PX3, 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.

305

Chapter 7: Using the Web Interface

Note: If the PX3 clock and the LDAP server clock are out of sync, the installed
TLS certificates, if any, may be considered expired. To ensure propersynchronization, administrators should configure the PX3 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 havegathered.
Note that you must enter information in the fields showing the message'required.'To add Radius servers:

Field/setting

1.

Choose Device Settings > Security > Authentication.

2.

Click New in the Radius Servers section.

3.

Enter information.

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 andpassword are encrypted, while in PAP they are transmitted in the clear.
MS-CHAPv2 provides stronger security than the above two. Selecting thisoption will support both MS-CHAPv1 and MS-CHAPv2.

Authentication port,

The defaults are standard ports -- 1812 and 1813.

Accounting port

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.

The shared secret is necessary to protect communication with the Radius
Confirm shared secret server.
Shared secret,306

Chapter 7: Using the Web Interface

4.

To verify if the authentication configuration is set correctly, click Test
Connection to check whether the PX3 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 307).

5.

Click Add Server. The new Radius server is listed on the Authentication
page.

6.

To add more servers, repeat the same steps.

7.

In the Authentication Type field, select Radius. Otherwise, the Radiusauthentication does not work.

8.

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.

2.

Perform the desired action.
▪

Click Edit to edit its settings, and click Modify Server to save changes.
For information on each field, see Adding LDAP/LDAPS Servers (onpage 303) or Adding Radius Servers (on page 306).

▪

Click Delete to delete the server, and then confirm the operation.

▪

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.

307Chapter 7: Using the Web Interface

Note: Whenever PX3 is successfully connected to one external
authentication server, it STOPS trying access to remaining servers in theauthentication 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 PX3 always tries external
authentication first. Whenever the external authentication fails, the PX3
switches to local authentication.

3.

Click Save.
To disable external authentication:

1.

In the 'Authentication type' field, 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.
▪

308

If you type a value, the value must be followed by a time unit, such as'4 min.' See Time Units (on page 184).

3.

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 isblocked from accessing the PX3.

4.

Click Save.

Chapter 7: Using the Web Interface

Tip: If any user blocking event occurs, you can unblock that user manually byusing the "unblock" CLI command over a local connection. See Unblocking a
User (on page 618).
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 atime option. This setting determines how long users are permitted to stayidle 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 184).

▪

Keep the idle timeout to 20 minutes or less if possible. This reduces thenumber of idle sessions connected, and the number of simultaneouscommands sent to the PX3.

2.

Select the 'Prevent concurrent login with same username' checkbox ifintending to prevent multiple persons from using the same login namesimultaneously.

3.

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 PX3.
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 atime option. This setting determines how often users are requested tochange their passwords.
▪

3.

If you type a value, the value must be followed by a time unit, such as'10 d.' See Time Units (on page 184).

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:

309

Chapter 7: Using the Web Interface

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 PX3 is 64 characters.
2.

Make changes to the default settings as needed.

3.

Click Save.

Enabling the Restricted Service Agreement

The restricted service agreement feature, if enabled, forces users to read asecurity agreement when they log in to the PX3.
Users must accept the agreement, or they cannot log in.
An event notifying you if a user has accepted or declined the agreement can begenerated. See Default Log Messages (on page 322)
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.
▪

4.

310

A maximum of 10,000 characters can be entered.

Click Save.

Chapter 7: Using the Web Interface

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.

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 andaccept the restricted service agreement" is displayed.

311

Chapter 7: Using the Web Interface

Setting the Date and Time
Set the internal clock on the PX3 manually, or link to a Network Time Protocol(NTP) server.
Note: If you are using Sunbird's Power IQ to manage the PX3, you must
configure Power IQ and the PX3 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 'Automaticdaylight saving time adjustment' checkbox is selected.
▪

4.

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

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
For details, see Calendar (on page 314).
▪ Determine the time format you want by clicking 12H or 24H button.
▪

12H represents the 12-hour format.

▪

24H represents the 24-hour format.

to select a date.

▪ If selecting 12-hour format, then determine the current period by clicking the AM or PM
button.

▪ Type values in the Time field using the hh:mm:ss format, or click▪

312

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.

Chapter 7: Using the Web Interface

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

PX3 follows the NTP server sanity check per the IETF RFC. If your PX3 has
problems synchronizing with a Windows NTP server, see Windows NTP Server
Synchronization Solution (on page 315).

313

Chapter 7: Using the Web Interface

Calendar

The calendar iconin the Date field is a convenient tool to select acustom date. Click it and a calendar similar to the following appears.

314

NumberItem

Description

1

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

Chapter 7: Using the Web Interface

Windows NTP Server Synchronization Solution

The NTP client on the PX3 follows the NTP RFC so the PX3 rejects any NTP
servers whose root dispersion is more than one second. An NTP server with adispersion of more than one second is considered an inaccurate NTP server by
the PX3.
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 PX3. 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\Co
nfig

2.

AnnounceFlags must be set to 0x05 or 0x06.
▪

0x05 = 0x01 (Always time server) and 0x04 (Always reliable time
server)▪

0x06 = 0x02 (Automatic time server) and 0x04 (Always reliable time
server)Note: Do NOT use 0x08 (Automatic reliable time server) because its
dispersion starts at a high value and then gradually decreases to one
second or lower.
3.

LocalClockDispersion must be set to 0.

315

Chapter 7: Using the Web Interface

Event Rules and Actions
A benefit of the product's intelligence is its ability to notify you of or react to achange 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 PX3 or a device connected to it
meets a certain condition. For example, the inlet's voltage reaches thewarning level.
Action: This is the response to the event. For example, the PX3 notifies thesystem administrator of the event via email.

If you want the PX3 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 PX3 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.
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 334).
3.

Click

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 PX3 to react.

d.

In the 'Available actions' field, select the desired action(s) to respondto the selected event.

e.

Click Create.

For details, see Built-in Rules and Rule Configuration (on page 317).
To create a scheduled action:
1.

If the needed action is not available yet, create it by clicking. See above.
Note: When creating scheduled actions, available actions are less thanusual because it is meaningless to schedule certain actions like "Alarm,""Log event message," "Send email," "Syslog message" and the like.

2.

316

Click

to schedule the desired action.

Chapter 7: Using the Web Interfacea.

Assign a name to this scheduled action.

b.

Make sure the Enabled checkbox is selected, or the PX3 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 354).
Built-in Rules and Rule Configuration

PX3 is shipped with four built-in event rules, which cannot be deleted. If thebuilt-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 PX3 to be recorded in the internallog. It is enabled by default.
Note: For the default log messages generated for each event, see Default
Log Messages (on page 322).

•

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 PX3. It is disabled by default.

•

System Tamper Detection Alarmed:
This causes the PX3 to send alarm notifications if a DX tamper sensor has
been connected and the PX3 detects that the tamper sensor enters thealarmed state. It is enabled by default.

•

System Tamper Detection Unavailable:
This causes the PX3 to send alarm notifications if a DX tamper sensor was
once connected or remains connected but then the PX3 does not detect
the presence of the tamper sensor. It is enabled by default.
Event rule configuration illustration:

1.

Choose Device Settings > Event Rules >2.

Click the Event field to select an event type.
▪

.

<Any sub-event> means all events shown on the list.

317

Chapter 7: Using the Web Interface▪

318<Any Numeric Sensor> means all numeric sensors of the PX3, includinginternal and environmental sensors. <Any Numeric Sensor> isespecially useful if you want to receive the notifications when any
numeric sensor's readings pass through a specific threshold.

3.

In this example, the Peripheral Device Slot is selected, which is related tothe environmental sensor packages. Then a sensor ID field for this event
type appears. Click this additional field to specify which sensor should be
the subject of this event.

4.

In this example, sensor ID 3 (Slot 3) is selected, which is a temperature
sensor. Then a new field for this sensor appears. Click this field to specify
the type of event(s) you want.

Chapter 7: Using the Web Interface

5.

In this example, Numeric Sensor is selected because we want to selectnumeric-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.

6.

In this example, 'Above upper critical threshold' is selected because wewant the PX3 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.

7.

Select the desired radio button to finish the event configuration. Refer tothe following table for different types of radio buttons.
▪

8.

If needed, you may refer to event rule examples in the section titled
Sample Event Rules (on page 367).

To select any action(s), select them one by one from the 'Available actions'list.
▪

To select all available actions, click Select All.

319

Chapter 7: Using the Web Interface

9.

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 theoccurrence of theselected event -- trueor false

Available radio buttons include "Asserted,""Deasserted" and "Both."State sensor statechangeAvailable radio buttons include"Alarmed/Open/On," "No longer
alarmed/Closed/Off" and "Both."▪ Asserted: PX3 takes the action only when theselected event occurs. That is, the status of theevent transits from FALSE to TRUE.
▪ Deasserted: PX3 takes the action only when theselected event disappears or stops. That is, thestatus of the selected event transits from TRUE
to FALSE.
▪ Both: PX3 takes the action both when the event
occurs (asserts) and when the event
stops/disappears (deasserts).

▪ Alarmed/Open/On: PX3 takes the action only
when the chosen sensor enters the alarmed,
open or on state.
▪ No longer alarmed/Closed/Off: PX3 takes theaction only when the chosen sensor returns to
the normal, closed, or off state.
▪ Both: PX3 takes the action whenever the chosensensor switches its state.
Sensor availability

Available radio buttons include "Unavailable,""Available" and "Both."▪ Unavailable: PX3 takes the action only when thechosen sensor is NOT detected and becomes
unavailable.
▪ Available: PX3 takes the action only when thechosen sensor is detected and becomes
available.
▪ Both: PX3 takes the action both when thechosen sensor becomes unavailable or available.

320Chapter 7: Using the Web Interface

Event types

Radio buttons
Network interface link ▪ Link state is up: PX3 takes the action only when
the network link state changes from down to up.
state▪ Link state is down: PX3 takes the action only
when the network link state changes from up to
down.
▪ Both: PX3 takes the action whenever the
network link state changes.
Function enabled or
disabled▪ Enabled: PX3 takes the action only when thechosen function is enabled.
▪ Disabled: PX3 takes the action only when thechosen function is disabled.
▪ Both: PX3 takes the action when the chosen
function is either enabled or disabled.

Restricted service
agreement▪ Accepted: PX3 takes the action only when thespecified user accepts the restricted service
agreement.
▪ Declined: PX3 takes the action only when thespecified user rejects the restricted service
agreement.
▪ Both: PX3 takes the action both when thespecified user accepts or rejects the restrictedservice agreement.

Server monitoringevent▪ Monitoring started: PX3 takes the action only
when the monitoring of any specified server
starts.
▪ Monitoring stopped: PX3 takes the action only
when the monitoring of any specified serverstops.
▪ Both: PX3 takes the action when the monitoringof any specified server starts or stops.

Server reachability▪ Unreachable: PX3 takes the action only when
any specified server becomes inaccessible.
▪ Reachable: PX3 takes the action only when any
specified server becomes accessible.
▪ Both: PX3 takes the action when any specified
server becomes either inaccessible or accessible.

321

Chapter 7: Using the Web Interface

Event types

Radio buttons
Device connection or ▪ Connected: PX3 takes the action only when theselected device is physically connected to it.
disconnection, such asa USB-cascaded slave ▪ Disconnected: PX3 takes the action only whendevicethe selected device is physically disconnectedfrom it.
▪ Both: PX3 takes the action both when theselected device is physically connected to it andwhen it is disconnected.
+12V Supply 1 Status

Available radio buttons include "Fault," "OK" and"Both."▪ Fault: PX3 takes the action only when theselected 12V power supply to the controller
enters the fault state.
▪ OK: PX3 takes the action only when when theselected 12V power supply to the controller
enters the OK state.
▪ Both: PX3 takes the action whenever theselected 12 power supply's status changes.

Default Log Messages

These default log messages are recorded internally and emailed to specified
recipients when PX3 events occur (are TRUE) or, in some cases, stop or become
unavailable (are FALSE). See Send Email (on page 343) to configure email
messages.

322

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

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE

Asset Management > Firmware
UpdateFirmware update for asset strip[AMSNUMBER] ('[AMSNAME]'): statuschanged to '[AMSSTATE]'.

Asset Management > Device
Config Changed

Config parameter '[CONFIGPARAM]' ofasset 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]').

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 > * > Card removed

Card of type '[SMARTCARDTYPE]' with ID'[SMARTCARDID]' removed 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.

Device > System started

System started.

Device > System reset

System reset performed by user'[USERNAME]' from host '[USERIP]'.

Device > Firmware validation
failedFirmware validation failed by user'[USERNAME]' from host '[USERIP]'.

Device > Firmware update started

Firmware upgrade started from version'[OLDVERSION]' to version '[VERSION]' byuser '[USERNAME]' from host '[USERIP]'.

Default message when the event =FALSEBlade extension overflow cleared forstrip [AMSNUMBER] ('[AMSNAME]').

323

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE

Device > Firmware update
completedFirmware upgraded successfully fromversion '[OLDVERSION]' to version'[VERSION]' by user '[USERNAME]' fromhost '[USERIP]'.

Device > Firmware update failed

Firmware upgrade failed from version'[OLDVERSION]' to version '[VERSION]' byuser '[USERNAME]' from host '[USERIP]'.

Device > Hardware failure present

Failure '[FAILURETYPESTR]' asserted forcomponent '[COMPONENTID]'.

Device > Device identification
changedConfig 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]'.

Default message when the event =FALSEFailure '[FAILURETYPESTR]' deasserted
for component '[COMPONENTID]'.

Device > Bulk configuration copied Bulk configuration copied by user'[USERNAME]' from host '[USERIP]'.

324

Device > Network interface linkstate is up

The [IFNAME] network interface link is
now up.

Device > Peripheral Device
Firmware Update

Firmware update for peripheral device[EXTSENSORSERIAL] from [OLDVERSION]
to [VERSION] [SENSORSTATENAME].

Device > Sending SMTP message
failedSending 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].

The [IFNAME] network interface link is
now down.

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE

Default message when the event =FALSE

Device > Sending Syslog message
failedSending Syslog message to server[SYSLOGSERVER]:[SYSLOGPORT]([SYSLOGTRANSPORTPROTO]) failed.
[ERRORDESC].

Device > Sending SMS message
failedSending 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
updatedRaw configuration updated by user'[USERNAME]' from host '[USERIP]'.

Device > Unknown peripheraldevice attachedAn unknown peripheral device with rom
code '[ROMCODE]' was attached at
position '[PERIPHDEVPOSITION]'.

Device > Slave connected

Slave connected.

Device > WLAN authentication
over TLS with incorrect systemclock

Established connection to wirelessnetwork '[SSID]' via Access Point with
BSSID '[BSSID]' using '[AUTHPROTO]'
authentication with incorrrect 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]' inslot '[EXTSENSORSLOT]' unavailable.

Peripheral device '[EXTSENSORNAME]'
in slot '[EXTSENSORSLOT]' available.

Peripheral Device Slot > * >Numeric Sensor > Above upper
critical threshold

Peripheral device '[EXTSENSORNAME]' inslot [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]' inslot [EXTSENSORSLOT] asserted 'above
upper warning' at [SENSORREADING][SENSORREADINGUNIT].

Peripheral device '[EXTSENSORNAME]'
in slot [EXTSENSORSLOT] deasserted'above upper warning' at[SENSORREADING][SENSORREADINGUNIT].

Slave disconnected.

325

Chapter 7: Using the Web Interface

326

Event/context

Default message when the event = TRUE

Default message when the event =FALSE

Peripheral Device Slot > * >Numeric Sensor > Below lower
warning threshold

Peripheral device '[EXTSENSORNAME]' inslot [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]' inslot [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]' inslot '[EXTSENSORSLOT]' unavailable.

Peripheral device '[EXTSENSORNAME]'
in slot '[EXTSENSORSLOT]' available.

Peripheral Device Slot > * > State
Sensor/Actuator >Alarmed/Open/On

Peripheral device '[EXTSENSORNAME]' inslot [EXTSENSORSLOT] is[SENSORSTATENAME].

Peripheral device '[EXTSENSORNAME]'
in slot [EXTSENSORSLOT] is[SENSORSTATENAME].

Peripheral Device Slot > * > State
Sensor/Actuator > Switched byuser

Peripheral device '[EXTSENSORNAME]' inslot [EXTSENSORSLOT] has been switched
to [SENSORSTATENAME] by user'[USERNAME]' from host.

Inlet > * > Enabled

Inlet '[INLET]' has been enabled by user'[USERNAME]' from host '[USERIP]'.

Inlet '[INLET]' has been disabled byuser '[USERNAME]' from host'[USERIP]'.

Inlet > * > Sensor > * > Unavailable Sensor '[INLETSENSOR]' on inlet '[INLET]'
unavailable.

Sensor '[INLETSENSOR]' on inlet'[INLET]' available.

Inlet > * > Sensor > * > Above
upper critical threshold

Sensor '[INLETSENSOR]' on inlet '[INLET]'
asserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT].

Sensor '[INLETSENSOR]' on inlet'[INLET]' deasserted 'above upper
critical' at [SENSORREADING][SENSORREADINGUNIT].

Inlet > * > Sensor > * > Above
upper warning threshold

Sensor '[INLETSENSOR]' on inlet '[INLET]'
asserted 'above upper warning' at[SENSORREADING][SENSORREADINGUNIT].

Sensor '[INLETSENSOR]' on inlet'[INLET]' deasserted 'above upper
warning' at [SENSORREADING][SENSORREADINGUNIT].

Inlet > * > Sensor > * > Below
lower warning threshold

Sensor '[INLETSENSOR]' on inlet '[INLET]'
asserted 'below lower warning' at[SENSORREADING][SENSORREADINGUNIT].

Sensor '[INLETSENSOR]' on inlet'[INLET]' deasserted 'below lower
warning' at [SENSORREADING][SENSORREADINGUNIT].

Inlet > * > Sensor > * > Below
lower critical threshold

Sensor '[INLETSENSOR]' on inlet '[INLET]'
asserted 'below lower critical' at[SENSORREADING]

Sensor '[INLETSENSOR]' on inlet'[INLET]' deasserted 'below lower
critical' at [SENSORREADING]

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE[SENSORREADINGUNIT].

Default message when the event =FALSE[SENSORREADINGUNIT].

Inlet > * > Sensor > * > Reset

Sensor '[INLETSENSOR]' on inlet '[INLET]'
has been reset by user '[USERNAME]' fromhost '[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 > * > CriticalSensor '[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.

Inlet > Pole > * > Sensor >Unavailable

Sensor '[PDUPOLESENSOR]' on pole
Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of inlet '[INLET]' unavailable. '[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].

327

Chapter 7: Using the Web Interface

328

Event/context

Default message when the event = TRUE

Default message when the event =FALSE

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]' enterednormal state.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of inlet '[INLET]' exited
normal state.

Inlet > Pole > * > Sensor > Failed

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of inlet '[INLET]' enteredfailed state.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of inlet '[INLET]' exited
failed state.

Inlet > Pole > * > Sensor > Warning Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of inlet '[INLET]' enteredwarning state.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of inlet '[INLET]' exitedwarning state.

Inlet > Pole > * > Sensor > CriticalSensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of inlet '[INLET]' exitedcritical state.

Sensor '[PDUPOLESENSOR]' on pole'[INLETPOLE]' of inlet '[INLET]' enteredcritical 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]' finishedself test.

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 > * > 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].

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE

Default message when the event =FALSEOutlet > * > 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][SENSORREADINGUNIT].

Sensor '[OUTLETSENSOR]' on outlet'[OUTLET]' deasserted 'below lower
critical' at [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.

Sensor '[POLESENSOR]' on pole'[OUTLETPOLE]' of outlet '[OUTLET]'
available.

Outlet > * > Pole > * > Sensor >Above upper critical threshold

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of outlet '[OUTLET]'
asserted 'above upper critical' at[SENSORREADING][SENSORREADINGUNIT].

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

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of outlet '[OUTLET]'
deasserted '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].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of outlet '[OUTLET]'
deasserted '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].

Sensor '[PDUPOLESENSOR]' on pole'[OUTLETPOLE]' of outlet '[OUTLET]'
deasserted 'below lower critical' at[SENSORREADING][SENSORREADINGUNIT].

Overcurrent Protector > * >Sensor > * > Unavailable

Sensor '[OCPSENSOR]' on overcurrent
protector '[OCP]' unavailable.

Sensor '[OCPSENSOR]' on overcurrent
protector '[OCP]' available.

329

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE

Default message when the event =FALSEOvercurrent Protector > * >Sensor > * > Above upper criticalthresholdSensor '[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 '[OCPSENSOR]' on overcurrent
Sensor > * > Above upper warning protector '[OCP]' asserted 'above upper
warning' at [SENSORREADING]
threshold[SENSORREADINGUNIT].

Sensor '[OCPSENSOR]' on overcurrent
protector '[OCP]' deasserted 'above
upper warning' at [SENSORREADING][SENSORREADINGUNIT].

Overcurrent Protector > * >Sensor > * > Below lower warning
thresholdSensor '[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 criticalthresholdSensor '[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
updateController '[CONTROLLER]' with board ID[BOARDID] has started firmware update

Controller '[CONTROLLER]' with board
ID [BOARDID] has completed firmware
updatePdu > Controller > * >Incompatible

Controller '[CONTROLLER]' with board ID[BOARDID] is incompatible.

Controller '[CONTROLLER]' with board
ID [BOARDID] is no longer
incompatible.

Pdu > Controller > * > OK

Controller '[CONTROLLER]' with board ID[BOARDID] is OK.

Controller '[CONTROLLER]' with board
ID [BOARDID] is no longer OK.

Pdu > Sensor > +12V Supply 1
Status > Fault

Global sensor '[PDUSENSOR]' entered
fault state.

Pdu > Sensor > +12V Supply 1 Status >Fault

Pdu > Sensor > +12V Supply 1
Status > Unavailable

Global sensor 'powerSupplyStatus 1'
unavailable.

Global sensor 'powerSupplyStatus 1'
available.

Server Monitoring > * > Error

Error monitoring server'[MONITOREDHOST]': [ERRORDESC]

Server Monitoring > * > Monitored Server '[MONITOREDHOST]' is now being
monitored.

330

Server '[MONITOREDHOST]' is nolonger being monitored.

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE

Server Monitoring >[MONITOREDHOST] > Power
control completed

Power control operation for'[MONITOREDHOST]' finished with result:[SERVERPOWERRESULT]

Server Monitoring >[MONITOREDHOST] > Power
control initiatedUser '[USERNAME]' initiated a power
control operation for'[MONITOREDHOST]':[SERVERPOWEROPERATION]

Server Monitoring > * >Unreachable

Server '[MONITOREDHOST]' isunreachable.

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

Default message when the event =FALSE

Server '[MONITOREDHOST]' isreachable.

User '[USERNAME]' from host'[USERIP]' logged out.

User '[USERNAME]' from host'[USERIP]" declined the Restricted
Service Agreement.

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]'.

User Administration > User
modified

User '[UMTARGETUSER]' modified by user'[USERNAME]' from host '[USERIP]'.

User Administration > User
deletedUser '[UMTARGETUSER]' deleted by user'[USERNAME]' from host '[USERIP]'.

User Administration > Password
changedPassword 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

Role '[UMTARGETROLE]' modified by user

331

Chapter 7: Using the Web Interface

332

Event/context

Default message when the event = TRUE

Default message when the event =FALSE

modified'[USERNAME]' from host '[USERIP]'.

User Administration > RoledeletedRole '[UMTARGETROLE]' deleted by user'[USERNAME]' from host '[USERIP]'.

Webcam Management > Image
upload started

A snapshot upload of webcam'[WEBCAMNAME]' to folder '[PATH]' wasstarted.

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]' settingschanged 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].

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE

Default message when the event =FALSE

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

LHX/SHX > Condenser Pump
FailureThe condenser pump on LHX at[PORTTYPE] port '[PORTID]' failed.

The condenser pump on LHX at[PORTTYPE] port '[PORTID]' is back tonormal.

LHX/SHX > Emergency Cooling

Emergency cooling on LHX at [PORTTYPE]
port '[PORTID]' was activated.

Emergency cooling on LHX at[PORTTYPE] port '[PORTID]' wasdeactivated.

LHX/SHX > Maximum coolingrequestMaximum cooling was requested for LHX
at [PORTTYPE] port '[PORTID]'.

Maximum cooling is not any morerequested 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 An ST-Bus communication error was
detected on LHX at [PORTTYPE] port
Error'[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.

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]'.

The door of LHX at [PORTTYPE] port'[PORTID]' was closed.

333

Chapter 7: Using the Web Interface

Event/context

Default message when the event = TRUE

Default message when the event =FALSE

LHX/SHX > Threshold Air Inlet

The air inlet temperature threshold on
LHX at [PORTTYPE] port '[PORTID]' wascrossed.

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]' wascrossed.

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]' wascrossed.

The water inlet temperature on LHX at[PORTTYPE] port '[PORTID]' is within
thresholds.

LHX/SHX > Threshold Water Outlet The water outlet temperature threshold
The water outlet temperature on LHX
on LHX at [PORTTYPE] port '[PORTID]' was at [PORTTYPE] port '[PORTID]' is withincrossed.
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 tonormal.

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 An external water cooling failure occurred
Failureon LHX at [PORTTYPE] port '[PORTID]'.
LHX/SHX > Water Leak

Water leakage was detected on LHX at[PORTTYPE] port '[PORTID]'.
The asterisk symbol (*) represents anything you select for the 'trigger' events.
Available Actions

The PX3 comes with three built-in actions, which cannot be deleted. You cancreate additional actions for responding to different events.

•

334

To test an action:
Click the Test button next to the Action. The action is triggered and you
can verify it.

Chapter 7: Using the Web Interface•

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 367). Any changes made to
the 'SNMP Notifications' section on the SNMP page will update the settingsof the System SNMP Notification Action, and vice versa. See Configuring
SNMP Settings (on page 281).

•

System Tamper Alarm:This action causes the PX3 to show the alarm for the Raritan 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 (onpage 180).
Actions you can create:

1.

Choose Device Settings > Event Rules >2.

Click the Action field to select an action type from the list.

3.

Below is the list of available actions.

.

ActionFunction

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 (onpage 337).

Execute an action
group

Creates a group of actions comprising existing
actions. See Action Group (on page 338).

External beeper

Enables or disables the connected external beeper,or causes it to enter an alarm cycle. See External
Beeper (on page 339).

335

Chapter 7: Using the Web Interface

ActionFunctionInternal beeper

Turns on or off the internal beeper. See Internal
Beeper (on page 339).

Log event message

Records the selected events in the internal log. See
Log an Event Message (on page 340).

Power control server

PX3-1000 does NOT support this feature.

Push out sensor
readings

Sends internal sensor log, environmental sensor log
or asset management strip data to a remote serverusing HTTP POST requests. See Push Out Sensor
Readings (on page 340).

Record snapshots to
webcam storage

Makes a connected webcam start or stop taking
snapshots. See Record Snapshots to Webcam
Storage (on page 340).

Request LHX/SHX
maximum cooling

Applies the maximum cooling to the LHX/SHX
device. See Request LHX/SHX Maximum Cooling(on page 342).
This option is available only when the Schroff
LHX/SHX support has been enabled.

Send email

Emails a textual message. See Send Email (on page343).

Send sensor report

Reports the readings or status of the selected
sensors, including internal or external sensors. See
Send Sensor Report (on page 345).

Send SMS message

Sends a message to a mobile phone. See Send SMS
Message (on page 347).

Send snapshots via
email

Emails the snapshots captured by a connected
Logitech® webcam (if available). See Send
Snapshots via Email (on page 348).

Send SNMP notification Sends SNMP traps or informs to one or multiple
SNMP destinations. See Send an SNMP
Notification (on page 350).
Start/stop Lua script336

If you are a developer who can create a Lua script,
you can upload it to the PX3, and have the PX3
automatically perform or stop the script in
response to an event. See Start or Stop a Lua
Script (on page 351).

Chapter 7: Using the Web Interface

ActionFunction

Switch LHX/SHX

Switches on or off the LHX/SHX device. See Switch
LHX/SHX (on page 352).
This option is available only when the Schroff
LHX/SHX support has been enabled.

Switch outlet group

PX3-1000 does NOT support this feature.

Switch peripheral
actuator

Switches on or off the mechanism or system
connected to the specified actuator. See Switch
Peripheral Actuator (on page 352).

Syslog message

Makes the PX3 automatically forward event
messages to the specified syslog server. See Syslog
Message (on page 353).

4.

Enter the information as needed and click Create.

5.

Then you can assign the newly-created action to an event rule or scheduleit. See Event Rules and Actions (on page 316).

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 PX3 resends or regenerates an alert
notification regularly until the alert is acknowledged or the maximum numberof alert notifications is sent.
For information on acknowledging an alert, see Dashboard (on page 171).
Operation:
1.

Choose Device Settings > Event Rules >2.

Select Alarm from the Action list.

3.

In the Alarm Notifications list box, specify one or multiple ways to issue thealert 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.

337

Chapter 7: Using the Web Interface

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

To enable the notification-resending feature, select the 'Enablere-scheduling of alarm notifications' checkbox.

5.

In the 'Re-scheduling period' field, specify the time interval (in minutes) at
which the alert notification is resent or regenerated regularly.

6.

In the 'Re-scheduling limit' field, specify the maximum number of times thealert notification is resent. Values range from 1 to infinite.

7.

(Optional) You can instruct the PX3 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
ones, or click Deselect All.

to remove unnecessary

Action GroupYou can create an action group that performs up to 32 actions. After creatingsuch an action group, you can easily assign this set of actions to any event rulerather 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 334).
Operation:
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.
▪

4.

To select all available actions, click Select All.

To remove any action(s) from the 'Selected actions' field, click that action's
.
▪

338

.

To remove all actions, click Deselect All.

Chapter 7: Using the Web Interface

External Beeper

This section applies to PX3 only.
If an external beeper is connected to the PX3, the PX3 can change the beeper's
behavior or status to respond to a certain event.
To control the connected external beeper:
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 isconnected. This port is the FEATURE port.

4.

In the 'Beeper action' field, select an action for the external beeper to carryout.
▪

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 itwhen an event causes it to beep, the beeper no longer beeps after it isre-connected even though the event triggering the beeping action remains
asserted.

Internal Beeper

This section applies to PX3 only.
You can have the built-in beeper of the PX3 turned on or off when a certain
event occurs.
Operation:
1.

Choose Device Settings > Event Rules >2.

Select 'Internal beeper' from the Action list.

3.

Select an option from the Operation field.

.

▪

Turn beeper on: Turns on the internal beeper to make it buzz.

▪

Turn beeper off: Turns off the internal beeper to make it stop buzzing.

339

Chapter 7: Using the Web Interface

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 thesection titled Default Log Messages (on page 322).

Push Out Sensor Readings

You can configure the PX3 to push sensor log to a remote server after a certain
event occurs, including logs of internal sensors, environmental sensors andactuators.
If you have connected Raritan's asset strips to the PX3, you can also configure
the PX3 to push the data to a server.
Before creating this action, make sure that you have properly defined thedestination servers and the data to be sent on the Data Push page. See
Configuring Data Push Settings (on page 373).
Tip: To send the data at a regular interval, schedule this action. See Schedulingan Action (on page 354). 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 >2.

Select 'Push out sensor readings' from the Action list.

3.

Select a server or host which receives the data in the Destination field.
▪

.

If the desired destination is not available yet, go to the Data Push pageto specify it.

Record Snapshots to Webcam Storage

This option allows you to define an action that starts or stops a specificwebcam from taking snapshots.
Per default the snapshots are stored on the PX3. See Viewing and Managing
Locally-Saved Snapshots (on page 432).
It is recommended to specify a remote server to store as many snapshots as
possible. See Changing Storage Settings (on page 434).
Operation:

340

1.

Choose Device Settings > Event Rules >.

2.

Select 'Record snapshots to webcam storage' from the Action list.

3.

Select a webcam in the Webcam field.

4.

Select the action to perform - 'Start recording' or 'Stop recording.'

Chapter 7: Using the Web Interface

If 'Start recording' is selected, adjust the values of the following:▪

Number of snapshots - the number of snapshots to be taken when theevent occurs.
The maximum amount of snapshots that can be stored on the PX3 is 10.
If you set it for a number greater than 10 and the storage location is on
the PX3, after the 10th snapshot is taken and stored, the oldest
snapshots are overwritten. Storing snapshots on a remote server does
not have such a limitation.

▪

Time before first snapshot - the amount of time in seconds between
when the event is triggered and the webcam begins taking snapshots.

▪

Time between snapshots - the amount of time in seconds between
when each snapshot is taken.

▪

Folder - names of the folders that will be automatically created tostore webcam snapshots after the recording action is triggered by therule you will configure.
Note that the Folder field is available only when the selected webcam
has been configured to store its snapshots on an "FTP" server. See
Changing Storage Settings (on page 434).

Folder name options

Definition

Serial number / Webcam nameTwo folders will be created.
▪ The parent folder's name is the serial number of PX3.
▪ The subfolder's name is the selected webcam's name.

Serial number / Webcam name /Rule nameThree folders will be created.

Serial number / Webcam name /Timestamp

Three folders will be created.

Serial number / Webcam name /Rule name / Timestamp

Four folders will be created.

▪ Definitions of the parent folder and first subfolder are the same as thefirst row.
▪ The final subfolder's name is the name of event rule that triggers thisrecording action.
▪ Definitions of the parent folder and first subfolder are the same as thefirst row.
▪ The final subfolder's name is the time when the recording event
occurs, which is the accumulated time in seconds since 1970/1/1.
▪ Definitions of the parent folder and first subfolder are the same as thefirst row.
▪ The second subfolder's name is the name of event rule that triggers
this recording action.
▪ The final subfolder's name is the time when the recording event
occurs, which is the accumulated time in seconds since 1970/1/1.

341

Chapter 7: Using the Web Interface

Folder name options

Definition

Serial number / Webcam name /Formatted timestamp

Three folders will be created.
▪ Definitions of the parent folder and first subfolder are the same as thefirst row.
▪ The final subfolder's name is the time when the recording event
occurs, which is a format comprising year, month, date, hour, minute,second and timezone.

Serial number / Webcam name /Four folders will be created.
Rule name / Formatted timestamp ▪ Definitions of the parent folder and first subfolder are the same as thefirst row.
▪ The second subfolder's name is the name of event rule that triggers
this recording action.
▪ The final subfolder's name is the time when the recording event
occurs, which is a format comprising year, month, date, hour, minute,second and timezone.
No matter which timestamp you choose, the timestamp is based on thetime you have configured on the PX3. See Setting the Date and Time (onpage 312).
To find the serial number of your PX3, see Device Information (on page398). To change the webcam's name, see Configuring Webcams andViewing Live Images (on page 427).
Tip: If you choose "Timestamp" as the final subfolder's name and do notunderstand the occurrence time indicated by the timestamp, you can always
easily convert it to a readable formatted time by googling Unix timestamp
converter.

Request LHX/SHX Maximum CoolingThis section applies to PX3 only.
If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will beavailable. See Miscellaneous (on page 394).
The 'Request LHX/SHX maximum cooling' action applies the maximum coolingto the SHX-30 device only. The LHX-20 and LHX-40 devices do not support thisfeature.
In the maximum cooling mode, an SHX-30 device runs at 100% fan speed andthe cold water valve is open 100%.
Operation:

342

1.

Choose Device Settings > Event Rules >.

2.

Select 'Request LHX/SHX maximum cooling' from the Action list.

Chapter 7: Using the Web Interface

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 thatdevice'sor click Deselect All.

Send EmailYou can configure emails to be sent when an event occurs and can customize
the message.
Messages consist of a combination of free text and PX3 placeholders. The
placeholders represent information which is pulled from the PX3 and inserted
into the message.
For example:[USERNAME] logged into the device on [TIMESTAMP]translates toMary 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 363).
Operation:
1.

Choose Device Settings > Event Rules >.

2.

Select 'Send email' from the Action list.

3.

In the 'Recipient email addresses' field, specify the email address(es) of therecipient(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 settings' radio
button. The fields for customized SMTP settings appear. For information oneach field, see Configuring SMTP Settings (on page 283).
Default messages are sent based on the event. For a list of default log
messages and events that trigger them, see Default Log Messages (onpage 322).

5.

If needed, you can customize the subject and messages sent via this email.
▪

Select the 'Custom subject' checkbox, and enter the text you prefer as
this email's subject.

▪

Select the 'Use custom log message' checkbox, and then create acustom message up to 1024 characters in the provided field.

343

Chapter 7: Using the Web Interface

When clicking anywhere inside the text box, the Event Context
Information displays, showing a list of placeholders and theirdefinitions. Just scroll down to select the desired placeholder. For
details, see Placeholders for Custom Messages (on page 363).

▪

To start a new line in the text box, press Enter.

Note: In case you need to type any square brackets "[" and "]" in thecustom 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.

344

Chapter 7: Using the Web Interface

Send Sensor Report

You may set the PX3 so that it automatically reports the latest readings orstates 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 orenvironmental sensors listed below.
•••

Inlet sensors, including RMS current, RMS voltage, active power, apparent
power, power factor and active energy.
Overcurrent protector sensors, including RMS current and tripping state.
Peripheral device sensors, which can be any Raritan environmental sensor
packages connected to the PX3, such as temperature or humidity sensors.

An example of this action is available in the section titled Send Sensor Report
Example (on page 357).
Operation:
1.

Choose Device Settings > Event Rules >.

2.

Select 'Send sensor report' from the Action list.

3.

In the 'Destination actions' section, select the method(s) to report sensor
readings or states. The number of available methods varies, depending on
how many messaging actions have been created.
The messaging action types include:4.

▪

Log event message▪

Syslog message▪

Send email▪

Send SMS message

If no messaging actions are available, create them now. See Available
Actions (on page 334).
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.
5.

In the 'Available sensors' field, select the desired target's sensor.
a.

Click the firstto select a target component from the list.

345

Chapter 7: Using the Web Interfaceb.

Click the second
the list.

c.

Click
box.

to select the specific sensor for the target fromto add the selected sensor to the Report Sensors list

For example, to monitor the current reading of the Inlet 1, select Inlet 1
from the left field, and then select RMS Current from the right field.
6.

To report additional sensors simultaneously, repeat the above step to add
more sensors.
▪

To remove any sensor from the 'Report sensors' list box, select it andclick. To make multiple selections, press Ctrl+click or
Shift+click to highlight multiple ones.

7.

To immediately send out the sensor report, click Send Report Now.

Tip: When intending to send a sensor report using custom messages, use theplaceholder [SENSORREPORT] to report sensor readings. See Placeholders for
Custom Messages (on page 363).

346

Chapter 7: Using the Web Interface

Send SMS Message

You can configure SMS messages to be sent when an event occurs and cancustomize the message.
Only the 7-bit ASCII charset is supported for SMS messages. Messages consistof a combination of free text and PX3 placeholders. The placeholders represent
information which is pulled from the PX3 and inserted into the message.
A supported modem, such as the Cinterion® GSM MC52i modem, must be
plugged into the PX3 in order to send SMS messages. See Connecting a GSM
Modem (on page 79).
Note: The PX3 cannot receive SMS messages.
For example:[USERNAME] logged into the device on [TIMESTAMP]translates toMary 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 363).
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 therecipient.

4.

Select the 'Use custom log message' checkbox, and then create a custom
message in the provided text box.

347

Chapter 7: Using the Web Interface▪

When clicking anywhere inside the text box, the Event Context
Information displays, showing a list of placeholders and theirdefinitions. Just scroll down to select the desired placeholder. For
details, see Placeholders for Custom Messages (on page 363).

▪

To start a new line in the text box, press Enter.

Note: In case you need to type any square brackets "[" and "]" in thecustom 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 EmailThis option notifies one or multiple persons for the selected events by emailingsnapshots 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 therecipient(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 283).

348

Chapter 7: Using the Web Interface

5.

Select the webcam that is capturing the images you want sent in the email.

6.

Adjust the values of the following:

7.

▪

Number of snapshots - the number of snapshots to be taken when theevent occurs. For example, you can specify 10 images be taken oncethe event triggers the action.

▪

Snapshots per mail - the number of snapshots to be sent at one time inthe 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.

If needed, you can customize the subject and messages sent via this email.
▪

Select the 'Custom subject' checkbox, and enter the text you prefer as
this email's subject.

▪

Select the 'Use custom log message' checkbox, and then create acustom message up to 1024 characters in the provided field.

▪

To start a new line in the text box, press Enter.

Note: In case you need to type any square brackets "[" and "]" in thecustom 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.

349

Chapter 7: Using the Web Interface

Send an SNMP Notification

This option sends an SNMP notification to one or multiple SNMP destinations.
Operation:
1.

Choose Device Settings > Event Rules >.

2.

Select 'Send SNMP notification' from the Action list.

3.

Select the type of SNMP notification. See either procedure below
according to your selection.
To send SNMP v2c notifications:1.

In the 'Notification type' field, select 'SNMPv2c trap' or 'SNMPv2c inform.'

2.

For SNMP INFORM communications, leave the resend settings at theirdefault or do the following:a.

In the Timeout field, specify the interval of time, in seconds, after
which a new inform communication is resent if the first is not received.
For example, resend a new inform communication once every 3
seconds.

b.

In the 'Number of retries' field, specify the number of times you want
to re-send the inform communication if it fails. For example, inform
communications are re-sent up to 5 times when the initialcommunication fails.

3.

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

4.

In the Port fields, enter the port number used to access the device(s).

5.

In the Community fields, enter the SNMP community string to access thedevice(s). The community is the group representing the PX3 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 theirdefault or do the following:a.

350

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.

Chapter 7: Using the Web Interfaceb.

4.

In the 'Number of retries' field, specify the number of times you want
to re-send the inform communication if it fails. For example, inform
communications are re-sent up to 5 times when the initialcommunication fails.

For both SNMP TRAPS and INFORMS, enter the following as needed andthen click OK to apply the settings:a.

Host nameb.

Port numberc.

User ID for accessing the host -- make sure the User ID has the
SNMPv3 permission.

d.

Select the host security level
Security level

Description"noAuthNoPriv"

Select this if no authorization or privacy protocols areneeded.

"authNoPriv"

Select this if authorization is required but no privacy
protocols are required.
••"authPriv"

Select the authentication protocol - MD5 or SHA
Enter the authentication passphrase and thenconfirm the authentication passphrase

Select this if authentication and privacy protocols are
required.
••••

Select the authentication protocol - MD5 or SHA
Enter the authentication passphrase and confirm
the authentication passphrase
Select the Privacy Protocol - DES or AES
Enter the privacy passphrase and then confirm theprivacy passphrase

Start or Stop a Lua Script

If you have created or loaded a Lua script file into the PX3, 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 389).
To automatically start or stop a Lua script:
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.'.

351

Chapter 7: Using the Web Interface

4.

In the Script field, select the script that you want it to be started or
stopped when an event occurs.
▪

5.

No script is available if you have not created or loaded it into the PX3.

To apply different arguments than the default, do the following. Note thatthe newly-added arguments will override this script's default arguments.

a.

Click

b.

Type the key and value.

c.

Repeat the same steps to enter more arguments as needed.
▪

.

To remove any existing argument, click

adjacent to it.

Switch LHX/SHXThis section applies to PX3 only.
If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will beavailable. See Miscellaneous (on page 394).
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.

Select 'Switch LHX/SHX' from the Action list.

3.

In the Operation field, select 'Turn LHX/SHX on' or 'Turn LHX/SHX off.'4.

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 thatdevice's. To remove all devices, click Deselect All.

Switch Peripheral Actuator

If you have any actuator connected to the PX3, you can set up the PX3 so it
automatically turns on or off the system controlled by the actuator when aspecific event occurs.
Note: For information on connecting actuators, see DX2 Sensor Packages (onpage 49).
Operation:

352

1.

Choose Device Settings > Event Rules >2.

Select 'Switch peripheral actuator' from the Action list.

.

Chapter 7: Using the Web Interface

3.

4.

In the Operation field, select an operation for the selected actuator(s).
▪

Turn on: Turns on the selected actuator(s).

▪

Turn off: Turns off the selected actuator(s).

To select the actuator(s) where this action will be applied, select them one
by one from the 'Available actuators' list.
▪

5.

To add all actuators, click Select All.

To remove any selected actuator from the 'Selected actuators' field, clickthat 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.
PX3 may or may not detect the syslog message transmission failure. If yes, itwill log this syslog failure as well as the failure reason in the event log. See
Viewing or Clearing the Local Event Log (on page 405).
Operation:

Transport
protocols

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.

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.

353

Chapter 7: Using the Web Interface

Transport
protocols

Next steps
A TLS certificate is required. Do the following:a.

Type an appropriate port number in the 'TCP port' field. Default is 6514.

b.

In the 'CA certificate' field, clickcertificate, you may:

TCP+TLSc.

to select a TLS certificate. After importing the▪

Click Show to view its contents.

▪

Click Remove to delete it if it is inappropriate.

Determine whether to select the 'Allow expired and not yet valid certificates' checkbox.
▪

To always send the event message to the specified syslog server as long as a TLS certificate
is available, select this checkbox.

▪

To prevent the event message from being sent to the specified syslog server when any TLS
certificate in the selected certificate chain is outdated or not valid yet, deselect thischeckbox.
Note: If the required certificate file is a chain of certificates, and you are notsure about the requirements of a certificate chain, see TLS Certificate Chain (onpage 804).

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 PX3 report thereading 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, thescheduled 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 334).
Operation:
1.

Choose Device Settings > Event Rules >.

2.

To select any action(s), select them one by one from the 'Available actions'
list.
▪

354

To select all available actions, click Select All.

Chapter 7: Using the Web Interface

3.

To remove any action(s) from the 'Selected actions' field, click that action's.
▪

4.

To remove all actions, click Deselect All.

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.

355

Chapter 7: Using the Web Interface

Execution time Frequency settings
MinutesHourlyClick 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.
Type a value in the Minute field, which is set to either of thefollowing:▪ 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.
WeeklyMonthly

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.
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 inparticular does not have the date 30 and probably even 29. Checkthe calendar when selecting 29, 30 or 31.

YearlyThis 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 mustcorrectly 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 357).

356

Chapter 7: Using the Web Interface

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
to create a 'Send email' action that sends anemail to the desired recipient(s). For details, see Send Email (on page 343).
▪

In this example, this action is named Email a Sensor Report.

357

Chapter 7: Using the Web Interface▪

358

If wanted, you can customize the subject and content of this email inthis action.

Chapter 7: Using the Web Interface

359

Chapter 7: Using the Web Interface

2.

Click
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 345).
▪

360

In this example, this action is named Send Temperature Sensor
Readings.

Chapter 7: Using the Web Interface▪

3.

You can specify more than one temperature sensor as needed in thisaction.

Clickto create a timer for
performing the 'Send Temperature Sensor Readings' action hourly. For
details, see Scheduling an Action (on page 354).

361

Chapter 7: Using the Web Interface▪

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, andso on, select Hourly, and set the Minute to 30.

Then the PX3 will send out an email containing the specified temperature
sensor readings hourly every day.
Whenever you want the PX3 to stop sending the temperature report, deselectthe Enabled checkbox in the timer.

362

Chapter 7: Using the Web Interface

Placeholders for Custom Messages

Actions of "Send email" and "Send SMS message" allow you to customize event
messages. See Send Email (on page 343) or Send SMS Message (on page 347).
In addition, you can add custom text message to the "Send snapshots via
email" action. See Send Snapshots via Email (on page 348).
When clicking anywhere inside the text box, the Event Context Information
displays, showing a list of placeholders and their definitions. Simply drag thescroll 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 thedesired placeholder.
Note that available placeholders are model dependent.

If wanted, you can resort the list by clicking the desired column header. See
Sorting a List (on page 170).
To make the Event Context Information disappear, click anywhere inside thebrowser's window.
The following are placeholders that can be used in custom messages.
Placeholder

Definition[AMSBLADESLOTPOSITION]

The (horizontal) slot position inside a blade extension[AMSLEDCOLOR]The RGB LED color[AMSLEDMODE]

The LED indication mode

[AMSLEDOPMODE]

The LED operating mode

363

Chapter 7: Using the Web Interface

364

Placeholder

Definition[AMSNAME]

The name of an asset strip[AMSNUMBER]

The numeric ID of an asset strip[AMSRACKUNITPOSITION]

The (vertical) rack unit position[AMSSTATE]

The human-readable state of an asset strip[AMSTAGID]

The asset tag ID[CARDREADERCHANNEL]

The channel number of a card reader[CARDREADERID]

The id of a card reader[CARDREADERMANUFACTURER]

The manufacturer of a card reader[CARDREADERPRODUCT]The product name of a card reader[CARDREADERSERIALNUMBER]

The serial number of a card reader[COMPONENTID]

The ID of a hardware component[CONFIGPARAM]

The name of a configuration parameter[CONFIGVALUE]

The new value of a parameter[DATETIME]

The human readable timestamp of the event occurrence[DEVICEIP]

The IP address of the device the event occurred on[DEVICENAME]

The name of the device the event occurred on[DEVICESERIAL]

The unit serial number of the device the event occurred on[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 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)Chapter 7: Using the Web Interface

Placeholder

Definition[LDAPERRORDESC]

The 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[MONITOREDHOST]

The name or IP address of a monitored host

[NETAUTHRESULTSTR]

The network authentication result string ('succeeded' or'failed')[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 the device is being upgraded from[OUTLET]The outlet label[OUTLETGROUPID]

The outlet group ID[OUTLETGROUPNAME]

The outlet group name

[OUTLETGROUPSENSOR]

The outlet group sensor name

[OUTLETNAME]

The outlet nameNote: If any outlet does not have a name, neither an outlet
name nor an outlet number will be shown in the custom
message for it. Therefore, it is recommended to check theavailability of all outlet names if intending to use thisplaceholder.

[OUTLETPOLE]

The outlet power line identifier[OUTLETSENSOR]

The outlet sensor name

[PDUPOLESENSOR]

The sensor name for a certain power line

[PDUSENSOR]

The PDU sensor name

[PERIPHDEVPOSITION]

The position of an attached peripheral device[PHONENUMBER]

The destination phone number of an outgoing SMS
message[PORTID]

The label of the external port the event-triggering device isconnected to365

Chapter 7: Using the Web Interface

Placeholder

Definition[PORTTYPE]

The type of the external port (e.g. 'feature' or 'auxiliary')
the event-triggering device is connected to[RADIUSERRORDESC]

The Radius error message[ROMCODE]The romcode of an attached peripheral device[SENSORREADING]

The value of a sensor reading[SENSORREADINGUNIT]

The unit of a sensor reading[SENSORREPORT]The formatted sensor report contents[SENSORSTATENAME]

The human readable state of a sensor[SENSORTHRESHOLDNAME]

The name of the threshold being crossed[SENSORTHRESHOLDVALUE]

The value of the threshold being crossed[SERVERPOWEROPERATION]

The power control operation that was initiated on a server(on/off)[SERVERPOWERRESULT]The result of a power control operation[SMARTCARDID]

The id of a smart card

[SMARTCARDTYPE]

The type of a smart card

[SMTPRECIPIENTS]

The list of recipients of an outgoing mail

[SMTPSERVER]

The name or IP address of an SMTP server[SYSCONTACT]SNMP MIB-II sysContact field[SYSLOCATION]

SNMP MIB-II sysLocation field[SYSNAME]

SNMP MIB-II sysName field[TIMEREVENTID]

The id of a timer event[TIMESTAMP]

The timestamp of the event occurrence[UMTARGETROLE]

The target role of a user management operation[UMTARGETUSER]

The target user of a user management operation[USERIP]The IP address a user connected from[USERNAME]

The user who performed an operation[VERSION]

The firmware version the device is upgrading toNote: 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 thesquare bracket. That is, \[ or \]. Otherwise, the message sent will not display thesquare brackets.

366

Chapter 7: Using the Web Interface

Editing or Deleting a Rule/Action

You can change the settings of an event rule, action or scheduled action, ordelete them.
Exception: Some settings of the built-in event rules or actions are notuser-configurable. You cannot delete built-in rules and actions. See Built-in
Rules and Rule Configuration (on page 317) or Available Actions (on page334).
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.
▪

To modify settings, make necessary changes and then click Save.

▪

To delete it, clickon the top-right corner. Then click
Delete on the confirmation message.

Sample Event Rules
Sample PDU-Level Event RuleIn this example, we want the PX3 to record the firmware upgrade failure in theinternal 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 PX3 responds to the event
related to firmware upgrade failure.

367

Chapter 7: Using the Web Interface

3.

To make PX3 record the firmware update failure event in the internal log,
select "System Event Log Action" in the 'Available actions' field.

Sample Outlet-Level Event RuleIn this example, we want the PX3 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:

368

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 thisoutlet 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 PX3 send SNMP notifications, select "System SNMP Notification
Action" in the 'Available actions' field.

Chapter 7: Using the Web Interface

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

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.

369

Chapter 7: Using the Web Interface

Sample Inlet-Level Event RuleIn this example, we want the PX3 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 PX3 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 447).

Then the SNMP notifications are sent when:370▪

Any numeric sensor's reading enters the warning or critical range.

▪

Any sensor reading or state returns to normal.

▪

Any sensor becomes unavailable.

Chapter 7: Using the Web Interface▪

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.

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 PX3 keeps busy because theaction or one of the actions taken for a certain event triggers an identical orsimilar event which will result in an action triggering one more event.
Example 1

This example illustrates an event rule which continuously causes the PX3 tosend out email messages.
Event selected

Action included

Device > Sending SMTP message failed

Send email

Example 2This example illustrates an event rule which continuously causes the PX3 tosend out SMTP messages when one of the selected events listed on the Device
menu occurs. Note that <Any sub-event> under the Device menu includes theevent "Sending SMTP message failed."
Event selected

Action included

Device > Any sub-event

Send email

Example 3This example illustrates a situation where two event rules combined regarding
the outlet state changes causes the PX3 to continuously power cycle outlets 1
and 2 in turn.
Event selected

Action included

Outlet > Outlet 1 > Sensor > Outlet State >On/Off > Both (trigger condition)

Cycle Outlet 2

Outlet > Outlet 2 > Sensor > Outlet State >On/Off > Both (trigger condition)

Cycle Outlet 1(Switch outlets --> Cycle Outlet --> Outlet
2)(Switch outlets --> Cycle Outlet --> Outlet
1)371

Chapter 7: Using the Web Interface

A Note about Untriggered Rules

In some cases, a measurement exceeds a threshold causing the PX3 togenerate an alert. The measurement then returns to a value within thethreshold, but the PX3 does not generate an alert message for the Deassertion
event. Such scenarios can occur due to the hysteresis tracking the PX3 uses.
See "To De-assert" and Deassertion Hysteresis (on page 782).
Setting Data Logging
The PX3 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 PX3 internal sensors aremeasured 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 thelog can store the last two hours of measurements before the oldest one in thelog 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 andmaximum measurement values are written to the log.
Note: The PX3 device's SNMP agent must be enabled for this feature to work.
See Enabling and Configuring SNMP (on page 447). 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 isfrom 1 to 600. The default is 60.

4.

Verify that all sensor logging is enabled. If not, click Enable All at thebottom of the page to have all sensors selected.
▪

372

You can also click the topmost checkbox labeled "Logging Enabled" inthe header row of each section to select all sensors of the same type.

Chapter 7: Using the Web Interface▪

5.

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 thefollowing diagram displays in this section, which you can click any
button to switch between pages.

Click Save. This button is located at the bottom of the page.

Important: Although it is possible to selectively enable/disable logging forindividual sensors on the PX3, 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 datasynchronization. The destination and authentication for data push have to be
configured properly on the PX3.
The data will be sent in JSON format using HTTP POST requests. For more
information on its format, see Data Push Format (on page 375).
For instructions on connecting asset strips, see Connecting Asset Management
Strips (on page 68).
After configuring the destination and authentication settings, do either or bothof 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 316).
To configure data push settings:

1.

Choose Device Settings > Data Push.

2.

To specify a destination, click3.

Do the following to set up the URL field.

4.

.

a.

Click

to select http or https.

b.

Type the URL or host name in the accompanying text box.

If selecting https, a CA certificate is required for making the connection.
Click

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

373

Chapter 7: Using the Web Interface

5.

6.

7.

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

In the 'Entry type' field, determine the data that will be transmitted.
▪

Asset management tag list: Transmit the information of the specified
asset strip(s), including the general status of the specified strip(s) anda list of asset tags. The asset tags list also includes the tags on blade
extension strips, if any.

▪

Asset management tag 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 372).

If 'Asset management tag list' is selected in the above step, specify theasset strip(s) whose information to send. For PX3 with only one FEATURE
port, only one asset strip is available.
▪

To specify the asset strip(s), select them one by one from the Available
AMS Ports list. Or click Select All to add all.

▪

To remove the asset strip(s), click that asset strip's
AMS Ports field. Or click Deselect All to remove all.

in the Selected

8.

Click Create.

9.

Repeat the same steps for additional destinations. Up to 64 destinations
are supported.
To immediately push out the data:

1.

On the Data Push page, choose the one whose data you want to push out.

2.

Click its.

To modify or delete data push settings:

374

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
confirmation message.

, and then confirm it on theChapter 7: Using the Web Interface

Data Push Format

Each push message contains exactly one JSON object. The data format isformally defined in IDL files, sharing several definitions from the JSON-RPC data
model.
IDL files are available by launching JSON-RPC online help
(https://help.raritan.com/json-rpc/pdu/v3.6.0/namespacedatapush.html).
To have an overview of the data format, see the following topic.
•••

Sensor Log (on page 375)
Asset Management Tag List (on page 378)
Asset Management Tag Log (on page 381)

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

375

Chapter 7: Using the Web Interface

Sensor Descriptors for Inlet Active PowerThe following illustrates a descriptor for an inlet active power sensor.
The metadata field is relevant only to numeric sensors so thereadingtype field is displayed twice in the illustration.
Note that a Raritan-provided explanation, which is the comment beginningwith // in each line, is added to the following illustration for you to understandit better.

376

Chapter 7: Using the Web Interface

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 beginningwith // in each line, is added to the following illustration for you to understandit better.

377

Chapter 7: Using the Web Interface

Asset Management Tag List

The root object of the asset management tag list message is an
AssetStripsMessage structure. It contains current data about allconnected asset management strips and tags, which is similar to the illustration
below.

378

Chapter 7: Using the Web Interface

379

Chapter 7: Using the Web Interface(Continued)

380

Chapter 7: Using the Web Interface

Asset Management Tag Log

The root object of the asset management log message is an
AssetLogPushMessage structure. It contains a list of tag or strip events
since the last successful push.
Note that a Raritan-provided explanation, which is the comment beginningwith // in each line, is added to the following illustration for you to understandit better.

381

Chapter 7: Using the Web Interface

Monitoring Server Accessibility
You can monitor whether specific IT devices are alive by having the PX3continuously ping them. An IT device's successful response to the pingcommands 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.
PX3 can monitor any IT device, such as database servers, remoteauthentication 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.
Tip: To make the PX3 automatically log, send notifications or perform otheractions for any server monitoring events, you can create event rules. See Event
Rules and Actions (on page 316). An example is available in Example: Ping
Monitoring and SNMP Notifications (on page 384).
To add IT equipment for ping monitoring:1.

Choose Device Settings > Server Reachability.

2.

Click

3.

By default, the "Enable ping monitoring for this server" checkbox isselected. 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
The number of successful pings required topings to enable feature declare that the monitored equipment is"Reachable." Valid range is 0 to 200.

382

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

Chapter 7: Using the Web Interface

Field

Description

Number of consecutive The number of consecutive pings without any
unsuccessful pings for response before the monitored equipment is
failuredeclared "Unreachable." Valid range is 1 to100.
Wait time before
resuming pinging after
failureThe wait time before the PX3 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 PX3 disables the ping monitoring featurefor it and shows "Waiting for reliable
connection." Valid range is 0 to 100.

5.

Click Create.

6.

To add more IT devices, repeat the same steps.

Server Status Checking

After adding IT equipment for monitoring, all IT devices are listed on the Server
Reachability page.

In the beginning, the status of the added IT equipment shows "Waiting for
reliable connection," which means the requested number of consecutive
successful or unsuccessful pings has not reached before PX3 can declare thatthe monitored device is reachable or unreachable.
To check the server monitoring states and results:
1.

The column labeled "Ping Enabled" indicates whether the monitoring forthe corresponding IT device is activated or not.

2.

The column labeled "Status" indicates the accessibility of monitoredequipment.

383

Chapter 7: Using the Web Interface

StatusDescription

Reachable

The monitored equipment is accessible.

Unreachable

The monitored equipment is inaccessible.

Waiting for reliable
connection

The connection between the PX3 device and themonitored equipment is not reliably established yet.

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 (onpage 382).

▪

To delete it, clickon the top-right corner.

Example: Ping Monitoring and SNMP Notifications

In this illustration, it is assumed that a significant PDU (IP address:
192.168.84.95) shall be monitored by your PX3 to make sure that PDU isproperly operating all the time, and the PX3 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 aredifferent between your PX3 and the monitored PDU.
This requires the following two steps.
Step 1: Set up the ping monitoring for the target PDU
1.

Choose Device Settings > Server Reachability.

2.

Click

3.

Ensure the "Enable ping monitoring for this server" checkbox is selected.

4.

Enter the data shown below.
▪

384

.

Enter the server's data.
Field

Data entered

IP address/hostname

192.168.84.95

Chapter 7: Using the Web Interface

▪

▪

▪

▪
5.

To make the PX3 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 ping5

To make the PX3 declare the inaccessibility of the monitored PDU
when that PDU becomes inaccessible for around 12 seconds (4seconds * 3 pings), enter the following data.
Field

Data entered

Wait time after unsuccessful ping4

Number of consecutive unsuccessful pings for
failure3

To make the PX3 stop pinging the target PDU for 60 seconds (1 minute)after the PDU inaccessibility is declared, enter the following data.
After 60 seconds, the PX3 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.

Click Create.
Step 2: Create an event rule to send SNMP notifications for the target
PDU

1.

Choose Device Settings > Event Rules.

2.

Click

3.

Select the Enabled checkbox to enable this new rule.

4.

Configure the following.

.

Field/setting

Data specified

Rule nameSend SNMP notifications for PDU(192.168.84.95) inaccessibility

Event

Choose Server Monitoring > 192.168.84.95 >Unreachable

Trigger condition

Select the Unreachable radio button

385

Chapter 7: Using the Web Interface

This will make the PX3 react only when the target PDU becomesinaccessible.
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 367).

Front Panel Settings
You can set up the default mode of the front panel display, and front panel
functions for actuator control, beeper mute or RCM self-test.
Note that available front panel settings are model dependent.
••••

Actuator control -- available on all models.
Internal beeper's mute function -- available on all PX3 models.
Default front panel mode setup -- available on all models.
RCM self-test -- available on those PX3 models which support residual
current monitoring. See PX3 Models with Residual Current Monitoring (onpage 686).
To configure the front panel settings:

1.

Choose Device Settings > Front Panel.

2.

Configure the following:▪

To configure the default view of the LCD display, select one mode
below.

Note: The default view is shown in the automatic mode. See Automatic andManual Modes (on page 121).
Mode

Data entered

Automatic mode

The LCD display cycles through both the inlet
and overcurrent protector information. This is
the default.
Overcurrent protector information is available
only when your PX3 has overcurrent
protectors.

Inlet overview

386

The LCD display cycles through the inlet
information only.

▪

To enable the front panel actuator-control function, select the'Peripheral actuator control' checkbox.

▪

The built-in beeper's mute control function is enabled per default. To
disable it, deselect the 'Mute beeper' checkbox.

Chapter 7: Using the Web Interface▪

3.

By default the front panel RCM self-test function, if available, isenabled. See Disabling or Enabling Front Panel RCM Self-Test (onpage 694).

Click Save.
If the 'Mute beeper' feature is enabled, you can operate the front panel tomute it whenever it beeps. See Muting the Internal Beeper (on page 130).
Or you can turn on or off actuators by operating the front panel. See
Peripherals (on page 133).

Configuring the Serial PortYou can change the bit rate of the serial port labeled CONSOLE / MODEM on
the PX3. The default bit rate for console and modem operation is 115200 bps.
The PX3 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 PX3 through the serial port, or there arecommunication problems.
Note: The serial port bit-rate change is required when the PX3 works inconjunction 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 PX3 can detect the device type, and automatically apply the preset
bit rate.
The PX3 will indicate the detected device in the Port State section of the SerialPort page.
To configure serial port and modem settings, choose Device Settings > SerialPort.
To change the serial port's baud rate settings:
1.

Click the 'Connected device' field to make the serial port enter anappropriate state.
Options

Description

Automatic detection

The PX3 automatically detects the type of the device
connected to the serial port.
Select this option unless your PX3 cannot correctly detectthe device type.

387

Chapter 7: Using the Web Interface

2.

Options

Description

Force console

The PX3 attempts to recognize that the connected device
is set for the console mode.

Force analog modem

The PX3 attempts to recognize that the connected device
is an analog modem.

Force GSM modem

The PX3 attempts to recognize that the connected device
is a GSM modem.

Click the 'Console baud rate' field to select the baud rate intended forconsole management.
Note: For a serial RS-232 or USB connection between a computer and the
PX3, leave it at the default (115200 bps).

3.

Click the 'Modem baud rate' field to select the baud rate for the modem
connected to the PX3.

The following modem settings/fields appear in the web interface after the PX3
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 accessvia a modem. Otherwise, deselect it.

2.

Type a value in the 'Number of rings before answering' field to determine
the number of rings the PX3 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.
▪

388

Enter the SMS center number in the 'SMS center' field.

3.

If needed, click Advanced Information to view detailed information about
the modem, SIM and mobile network.

4.

To test whether the PX3 can successfully send out SMS messages with themodem 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.

Chapter 7: Using the Web Interface

Lua Scripts
If you can write or obtain any Lua scripts, you can create or load them into the
PX3 to control its behaviors.
Raritan also provides some Lua scripts examples, which you can load asneeded.
Note: Not all Raritan Lua script examples can apply to your PX3 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 PX3.
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 anexisting script's codes. See Modifying or Deleting a Script (on page 393).
To write or load a Lua script:
1.

Choose Device Settings > Lua Scripts >.

2.

Type a name for this script. Its length ranges between 1 to 63 characters.
The name must contain the following characters only.
▪

Alphanumeric characters▪

Underscore (_)▪

Minus (-)

Note: Spaces are NOT permitted.
3.

Determine whether and when to automatically execute the loaded script.

Checkbox

Behavior when selectedStart automatically at
system bootWhenever the PX3 reboots, the script is automatically
executed.

Restart after termination The script is automatically executed each time after 10
seconds since the script execution finishes.
4.

(Optional) Determine the arguments that will be executed by default.

a.

Click

.

b.

Type the key and value.

c.

Repeat the same steps to enter more arguments as needed.

389

Chapter 7: Using the Web Interface▪

To remove any existing argument, click

adjacent to it.

Note: The above default arguments will be overridden by new arguments
specified with the "Start with Arguments" command or with any
Lua-script-related event rule. See Manually Starting or Stopping a Script(on page 391) or Start or Stop a Lua Script (on page 351).
5.

In the Source Code section, do one of the following. It is recommended toleave the Enable Syntax Highlighting checkbox selected unless you do notneed different text colors to identify diverse code syntaxes.
▪

To write a Lua script, type the codes in the Source Code section.

▪

To load an existing Lua script file, click Load Local File.

▪

To use one of 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.
6.

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 thecodes. If needed, modify the codes to meet your needs.

7.

Click Create.
Next steps:390•

To execute the newly-added script immediately, click

•

click
> Start With Arguments. See Manually Starting or Stopping a
Script (on page 391).
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 167), and then repeat theabove steps.

, orChapter 7: Using the Web Interface

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 PX3 automatically start or stop a script in response to an event,create an event rule. See Event Rules and Actions (on page 316) and Start or
Stop a Lua Script (on page 351).
To manually start a script:
1.

Choose Device Settings > Lua Scripts. The Lua scripts list displays.

2.

Click the desired script whose state is either 'Terminated' or 'New.' For
details, see Checking Lua Scripts States (on page 393).

3.

To start with default arguments, click.

To start with new arguments, click> Start With Arguments.
Newly-assigned arguments will override default ones.
4.

If you chose "Start With Arguments" in the above step, enter the key andvalue in the Start Lua Script dialog.
▪

Click

if needing additional arguments.

391

Chapter 7: Using the Web Interface

5.

Click Start.

6.

The script output will be shown in the Script Output section.
▪

If needed, click

to delete the existing output data.

To manually stop a script:

392

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

3.

Click

4.

Click Stop on the confirmation message.

•

To return to the scripts list:
Click "Lua Scripts" on the top of the page.

•

Or click "Lua Scripts" in the Menu (on page 167).

on the top-right corner.

Chapter 7: Using the Web Interface

Checking Lua Scripts States

Choose Device Settings > Lua Scripts to show the scripts list, which indicatesthe current state and settings of each script.

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 389).
Restart:This column indicates whether the checkbox labeled "Restart aftertermination" is enabled. See Writing or Loading a Lua Script (on page 389).
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 PX3.
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.

393

Chapter 7: Using the Web Interface

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 toselect a new script.

To delete a script:
1.

Choose Device Settings > Lua Scripts.

2.

Click the desired one in the scripts list.

3.

Click

4.

Click Delete on the confirmation message.

•

To return to the scripts list:
Click "Lua Scripts" on the top of the page.

•

Or click "Lua Scripts" in the Menu (on page 167).

> Delete.

Miscellaneous
By default, the Schroff LHX/SHX heat exchanger support and Cisco EnergyWise
feature implemented on the PX3 are disabled.
Support needs to be enabled for the LHX/SHX information to appear in the PX3
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 yourplace, you can enable the Cisco EnergyWise endpoint implemented on the PX3
so that this PX3 becomes part of the Cisco EnergyWise domain.
In addition, if you have to prevent others from accessing your PX3 via USB-A for
security reasons, you can disable all of USB-A ports on the PX3. 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:

394

1.

Select the LHX/SHX checkbox.

2.

Click Save in the Features section.

3.

Click Apply on the confirmation message.

4.

PX3 reboots.

Chapter 7: Using the Web Interface

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 PX3
belongs▪ Up 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 domain▪ Up to 127 printable ASCII characters are permitted.
▪ Spaces and asterisks are NOT acceptable.

Port

Type a User Datagram Protocol (UDP) port number forcommunications in the Cisco EnergyWise domain.
▪ Range from 1 to 65535.
▪ Default is 43440.

Polling interval

Type a polling interval to determine how often the PX3 isqueried in the Cisco EnergyWise domain.
▪ Range from 30 to 600 ms.
▪ Default is 180 ms.

3.

Click Save in the EnergyWise section.

For Raritan's PDU models of 3000, 4000, and 5000 series, the parent/childrelationship 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 theaccess to the USB-B port, you have to apply a mechanical method.

395

Chapter 7: Using the Web Interface

Maintenance
Click 'Maintenance' in the Menu (on page 167), and the following submenu
displays.

396

Submenu command

Refer to...

Device Information

Device Information (on page 398)

Connected Users

Viewing Connected Users (on page 403)

Event Log

Viewing or Clearing the Local Event Log (on page 405)

Update Firmware

Updating the PX3 Firmware (on page 406)

Firmware History

Viewing Firmware Update History (on page 410)

Chapter 7: Using the Web Interface

Submenu command

Refer to...

Bulk Configuration

Bulk Configuration (on page 411)

Backup/Restore

Backup and Restore of Device Settings (on page 418)

Network Diagnostic

Network Diagnostics (on page 420)

Download Diagnostic

Downloading Diagnostic Information (on page 421)

Hardware Failures

Hardware Issue Detection (on page 421)

Unit Reset▪ Rebooting the PX3 (on page 423)
▪ Resetting All Settings to Factory Defaults (on page 423)

About PDU

Retrieving Software Packages Information (on page 424)

397

Chapter 7: Using the Web Interface

Device Information
Using the web interface, you can retrieve hardware and software informationof components or peripheral devices connected to your PX3.
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.

2.

Click the desired section's title bar to show that section's information. For
example, click the Network section.

The number of available sections is model dependent.

398

Section title

Information shown

Information

General device information, such as modelChapter 7: Using the Web Interface

Section title

Information shown
name, serial number, firmware version,
hardware revision, MIB download link(s) and soon.
Note that the download link of LHX-MIB isavailable only after enabling the Schroff LHX/SHX
support. See Miscellaneous (on page 394).

Network

The network information, such as the current
networking mode, IPv4 and/or IPv6 addresses
and so on.
This tab also indicates whether the PX3 is part ofa cascading configuration. See Identifying
Cascaded Devices (on page 400).

Port Forwarding

If the port forwarding mode is activated, thissection 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.

InletsEach inlet's plug type, rated voltage and current.

Peripheral Devices

Serial numbers, model names, position andfirmware-related information of connected
Raritan's environmental sensor packages.

Asset Management

Each asset strip's ID, boot version, application
version and protocol version.

399

Chapter 7: Using the Web Interface

Identifying Cascaded Devices

For information on how to cascade PX3 devices, see Cascading Multiple PX3
Devices for Sharing Ethernet Connectivity (on page 34).
This section explains how to identify a cascaded device on the Device
Information page.
Note: For more information on cascading configurations and restrictions, referto the Cascading Guide on the Raritan Support page(http://www.raritan.com/support/).
To identify the cascading status:
1.

Choose Maintenance > Device Information.

2.

Click the Network title bar.

▪

•

400

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 thecascading status. Note that the cascading position is NOT available in the
Bridging mode.
FieldsDescription

Port forwarding

Indicates the Port Forwarding is disabled. See Setting
the Cascading Mode (on page 270).

BRIDGE section

Indicates the device is in the Bridging mode and its IP
address.

Chapter 7: Using the Web Interface•

Cascading information in the Port Forwarding mode:
The Common section contains three read-only fields for indicating thecascading status.
FieldsDescription

Port forwarding

Indicates the Port Forwarding is enabled. See Setting
the Cascading Mode (on page 270).

Cascade position

Indicates the position of the PX3 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.

401Chapter 7: Using the Web Interface▪

A master device shows 0 (zero) in the 'Cascade position' field and yes in
the 'Cascaded device connected' field.

▪

A slave device in the middle position shows a non-zero number whichindicates 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.

▪

402

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.

Chapter 7: Using the Web Interface

The following diagram shows 2, indicating it is the second slave device- Slave 2. The 'Cascaded device connected' field shows no, indicatingthat it is the final one in the chain.

•

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.

Viewing Connected Users
You can check which users have logged in to the PX3 and their status. If you
have administrator privileges, you can terminate any user's connection to thePX3.
To view and manage connected users:
1.

Choose Maintenance > Connected Users. A list of logged-in users displays.

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

403

Chapter 7: Using the Web Interface

ColumnDescription

User Name

The login name of each connected user.

IP Address

The IP address of each user's host.
For the login via a local connection (serial RS-232 or USB),<local> is displayed instead of an IP address.

Client TypeThe interface through which the user is being connected to
the PX3.
▪ 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 Time2.

The length of time for which a user remains idle.

To disconnect any user, click the correspondinga.

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 PrimaryStandalone Live Preview window and multiple Secondary Standalone Live
Preview windows, are identified as one single "<webcam>" user in theConnected Users list. You can disconnect a "<webcam>" user to terminate allsessions sharing the same URL.

The IP address refers to the IP address of the host where the PrimaryStandalone Live Preview window exists, NOT the IP address of the other two
associated sessions.
For more webcam information, see Webcam Management (on page 425).

404

Chapter 7: Using the Web Interface

Viewing or Clearing the Local Event Log
By default, the PX3 captures certain system events and saves them in a local(internal) event log.
You can view over 2000 historical events that occurred on the PX3 in the local
event log. When the log size exceeds 256KB, each new entry overwrites theoldest 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 PX3 web interface are automaticallyconverted to your computer's time zone. To avoid time confusion, it issuggested to apply the same time zone settings as those of PX3 to yourcomputer or mobile device.
▪

Event type▪

A description of the event

2.

To view a specific type of events only, select the desired event type in the'Filter event class' field.

3.

The log is refreshed automatically at a regular interval of five seconds. To
avoid any new events' interruption during data browsing, you can suspend
the automatic update by clicking▪

.

To restore automatic update, click. Those new
events that have not been listed yet due to suspension will be
displayed in the log now.

To clear the local log:
1.

Click

on the top-right corner.

2.

Click Clear Log on the confirmation message.

405

Chapter 7: Using the Web Interface

Updating the PX3 Firmware
Firmware files are available on Raritan website's Support page(http://www.raritan.com/support/).
When performing the firmware upgrade, the PX3 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 PX3 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 tosuccessfully upgrade its firmware.
Note that firmware upgrade via iOS mobile devices, such as iPad, requires theuse 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 PX3 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 408).
To update the firmware:

406

1.

Choose Maintenance > Update Firmware.

2.

Click

3.

Click Upload. A progress bar appears to indicate the upload process.

to select an appropriate firmware file.

Chapter 7: Using the Web Interface

4.

Once complete, information of both installed and uploaded firmware
versions as well as compatibility and signature-checking results are
displayed.
▪

5.

If anything is incorrect, click Discard Upload.

To proceed with the update, click Update Firmware.
Warning: Do NOT power off the PX3 during the update.

6.

7.

During the firmware update:▪

A progress bar appears on the web interface, indicating the update
status.

▪

The front panel display shows the firmware upgrade message. See
Showing the Firmware Upgrade Progress (on page 150).

▪

The outlet LEDs flash if the relay boards are being updated. If thefirmware update does not include the update of the relay board
firmware, outlet LEDs do NOT flash.

▪

No users can successfully log in to the PX3.

▪

Other users' operation, if any, is forced to suspend.

When the update is complete, the PX3 resets, and the Login page
re-appears.
▪

Other logged-in users are logged out when the firmware update iscomplete.

Important: If you are using the PX3 with an SNMP manager, download its MIB
again after the firmware update to ensure your SNMP manager has thecorrect MIB for the latest release you are using. See Using SNMP (on page
447).
Alternatives:
To use a different method to update the firmware, refer to:•••

Firmware Update via SCP (on page 624)
Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 655)
Firmware Upgrade via USB (on page 653)

407

Chapter 7: Using the Web Interface

Upgrade Guidelines for Existing Cascading Chains

You must obey the following guidelines when upgrading a chain. Otherwise, anetworking 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 andfeatures.

•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 soon until the master device. See Upgrade Sequence in an Existing
Cascading Chain (on page 408).

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 acascading 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 toaccess 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.

▪

408

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 onsome cascaded devices.

Chapter 7: Using the Web Interface

Exception: A few products, such as SRC, are developed much later so they may
not support older firmware versions, such as 3.5.0, 3.4.0, and so on. Therefore,
it is suggested to AVOID downgrading your cascading chain unless instructed by
Raritan or Legrand Technical Support. For minimum firmware versions, see
Cascading Restrictions in the Cascading Guide on the Support page(http://www.raritan.com/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 tocheck the latest revision of the Cascading Guide or your product's User
Guide/Online Help before performing the firmware upgrade. The otheralternative 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 (orLegrand) 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 arandom 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.

409

Chapter 7: Using the Web Interface

A Note about Firmware Upgrade TimeThe PDU firmware upgrade time varies from unit to unit, depending on various
external and internal factors.
External factors include, but are not limited to: network throughput, firmware
file size, and speed 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 PX3 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

For PX3 with iX7™, disaster recovery can be performed via the USB
connection only.
If the firmware upgrade fails, causing the PX3 to stop working, you can recoverit 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 PX3 firmware
file is required in the recovery procedure.
Note: For old PX3 without iX7™ controller, you can recover it via either a USB orserial RS-232 connection. See Old Generations of PX3 Models (on page 704).
Viewing Firmware Update History
The firmware upgrade history is permanently stored on the PX3. 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:410▪

Update date and time▪

Previous firmware version▪

Update firmware version▪

Update result

Chapter 7: Using the Web Interface2.

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

Bulk Configuration
The Bulk Configuration feature lets you save generic settings of a configured
PX3 device to your computer. You can use this configuration file to copy
common settings to other PX3 devices of the same model and firmware version.
See Bulk Configuration Restrictions (on page 412).
A source device is the PX3 device where the configuration file isdownloaded/saved. A target device is the PX3 device that loads theconfiguration 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 thatall 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 orenvironmental 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 803).
When the date and time settings are included in the bulk configuration file,
exercise caution when distributing that file to target devices located in adifferent 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 (onpage 418).
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 414).

2.

Perform the bulk configuration operation, which includes the following
steps. For details, see Performing Bulk Configuration (on page 415).
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.

411

Chapter 7: Using the Web Interface

Note: On startup, PX3 performs all of its functions, including event rules andlogs, 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 "Bulkconfiguration copied" event rule.
The last configuration-copying record:
If you once copied any bulk configuration or device backup file to the PX3, thelast record similar to the following is displayed at the bottom of both the Bulk
Configuration and Backup/Restore pages.

Tip: The date and time shown on the PX3 web interface are automaticallyconverted to your computer's time zone. To avoid time confusion, it issuggested to apply the same time zone settings as those of PX3 to yourcomputer or mobile device.
Alternatives:
To use a different bulk configuration method, refer to:••••

Bulk Configuration via SCP (on page 625)
Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 655)
Configuration or Firmware Upgrade with a USB Drive (on page 641)
Raw Configuration Upload and Download (on page 678)

Tip: Both methods of uploading 'bulk configuration' file or 'raw configuration'
file via SCP can serve the purpose of bulk configuration. The only difference isthat 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 thesource 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 andsource devices are only "mechanical" designs which are indicated in themodel 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).

412

Chapter 7: Using the Web Interface

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 thetable below, the bulk configuration remains feasible.
These mechanical designs are represented by suffixes added to the model
name of a PX3 device. In the table, x represents a number. For example, Ax canbe A1, A2, A3, and so on.
Suffix

Mechanical design

ExampleAx

The line cord's length in meters

A20 = 3.3 meters

Note: For a PX2 or PX3 inline monitor, it islikely two Ax's are added to the model
name for indicating the lengths of its
inlets' and outlets' line cords.
Bx

The line cord's color

B501 = bright redorangeCx

Cord types or options

C4 = power cordwith 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 mechanicalchangesOx

OCP brand options

Px

Special requests for device painting or
printing

Qx

Special requests for physical placement
arrangements

Ux

Different power plug brands

413

Chapter 7: Using the Web Interface

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 PX3, whose settings you want to download.

2.

Choose Maintenance > Bulk Configuration.

3.

Click

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

6.

in the Bulk Profiles section.

After setting any profile as the default, the original default profile will
no longer function as the default one.

Now decide which settings are wanted and which are not.
a.

Click

b.

When the pop-up menu appears, select one of the options.

of the setting which you want to configure.

Note that the two options 'Inherited' and 'Built-in' are mutually
exclusive.
OptionDescription

Excluded

The setting will not be downloaded.

Included

The setting will be downloaded.

Inherited

The setting will follow its parent setting (that is, the upper-levelsetting).
▪ If you select 'Excluded' for its upper-level setting, this setting willbe also excluded.
▪ If you select 'Included' for its upper-level setting, this setting willbe also included.
The option inherited from its parent setting will be enclosed inparentheses.

414

Chapter 7: Using the Web Interface

OptionDescription

Built-inThe setting will follow the same setting of Raritan's built-in profile.
▪ If 'Excluded' is selected in the built-in profile, this setting will bealso excluded.
▪ If 'Included' is selected in the built-in profile, this setting will bealso included.
The option inherited from the built-in profile will be enclosed inparentheses.
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.

7.

Click Save.

8.

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.

Step 1: Select the desired bulk configuration profile (optional)
1.

Log in to the source PX3, 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.

415

Chapter 7: Using the Web Interface

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 PX3 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.
OptionEncrypted

Cleartext

Description▪ Partial content is base64 encoded.
▪ Its content is encrypted using the AES-128 encryption algorithm.
▪ The file is saved to the TXT format▪ Content is displayed in clear text.
▪ The file is saved to the TXT format.

4.

Click Download Bulk Configuration.

5.

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 PX3, which is of the same model and runs the same
firmware as the source PX3.

2.

Choose Maintenance > Bulk Configuration.

3.

Click

4.

Click 'Upload & Restore Bulk Configuration' to copy it.

5.

A message appears, prompting you to confirm the operation and enter theadmin password.

to select the configuration file.

Enter the admin password, and click Restore.
6.

416

Wait until the PX3 resets and the login page re-appears.

Chapter 7: Using the Web Interface

Alternatives:
To use a different bulk configuration method, refer to:••••

Bulk Configuration via SCP (on page 625)
Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 655)
Configuration or Firmware Upgrade with a USB Drive (on page 641)
Raw Configuration Upload and Download (on page 678)

Tip: Both methods of uploading 'bulk configuration' file or 'raw configuration'
file via SCP can serve the purpose of bulk configuration. The only difference isthat 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 thendo 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

3.

Click Delete on the confirmation message.

on the top-right corner.

To remove one or multiple profiles:
1.

Click

to make checkboxes appear in front of profiles.

2.

Select one or multiple profiles.

417

Chapter 7: Using the Web Interface▪

To select ALL profiles, select the topmost checkbox in the header row.

3.

Click

on the top-right corner.

4.

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 PX3, you should perform the Backup/Restore
feature.
All PX3 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 PX3 devices, use the Bulk
Configuration feature instead. See Bulk Configuration (on page 411).
To download a backup PX3 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 yourneed, change it.
OptionEncrypted

Cleartext
3.

418

Description▪ Partial content is base64 encoded.
▪ Its content is encrypted using the AES-128 encryption algorithm.
▪ The file is saved to the TXT format▪ Content is displayed in clear text.
▪ The file is saved to the TXT format.

Click Download Device Settings. Save the file onto your computer.

Chapter 7: Using the Web Interface

To restore the PX3 using a backup file:
You must have the Administrator Privileges to restore the device settings.
1.

Choose Maintenance > Backup/Restore.

2.

Click

3.

Click 'Upload & Restore Device Settings' to upload the file.
▪

to select the backup file.

A message appears, prompting you to confirm the operation and enter
the admin password.

4.

Enter the admin password, then click Restore.

5.

Wait until the PX3 resets and the Login page re-appears, indicating that therestore is complete.

Note: On startup, PX3 performs all of its functions, including event rules andlogs, 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 "Bulkconfiguration copied" event rule.
The last configuration-copying record:
If you once copied any bulk configuration or device backup file to the PX3, thelast record similar to the following is displayed at the bottom of both the Bulk
Configuration and Backup/Restore pages.

Alternative:
To use a different method to perform backup/restore, refer to:•

Backup and Restore via SCP (on page 626)

419

Chapter 7: Using the Web Interface

Network Diagnostics
PX3 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 throughthe 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 619).
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 tocheck.

Number of requests A number up to 20.
This determines how many packets are sent for pinging
the host.
2.

Click Run Ping to ping the host. The Ping results are then displayed.
Trace Route:

1.

2.

Type values in the following fields.
Field/setting

Description

Hostname

The IP address or name of the host whose route youwant 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, selectthis checkbox.

Click Run. The Trace Route results are then displayed.
List TCP Connections:

1.

420

Click the List TCP Connections title bar to show the list.

Chapter 7: Using the Web Interface

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

2.

The system prompts you to save or open the file. Save the file then.

3.

E-mail this file as instructed by Raritan Technical Support.

Hardware Issue Detection
This page lists any internal hardware issues PX3 has detected, including current
events and historical records.
Choose Maintenance > Hardware Failures, and the page similar to either of thefollowing diagrams opens.
NO hardware failures detected:

Hardware failure(s) detected:

421

Chapter 7: Using the Web Interface

Hardware Failure alerts on the Dashboard page:
Note that current hardware failure events, if any, will also display on the
Dashboard (on page 171).
Hardware failure types:
Hardware issues
Network device not detected
I2C Bus stuck
Slave controller not reachable
Slave controller malfunction

Description
A specific networking interface of PX3 is NOT detected.
A specific I2C bus is stuck, which affects the communication withsensors.
Communication with a specific slave controller fails.
A specific slave controller does not work properly.

The physical power state of a specific outlet is different from the chosen
Outlet power state inconsistent power state set by the software.

422

Chapter 7: Using the Web Interface

Rebooting the PX3
You can remotely reboot the PX3 via the web interface.
Resetting the PX3 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 PX3 deletes all webcam snapshots that are saved
onto the PX3 locally. If needed, download important snapshots before
rebooting the device. See Viewing and Managing Locally-Saved Snapshots(on page 432).
To reboot the device:1.

Choose Maintenance > Unit Reset >.

2.

Click Reboot to restart the PX3.

3.

A message appears, with a countdown timer showing the remaining timeof the operation. It takes about one minute to complete.

4.

When the restart is complete, the login page opens.

Tip: If you are not redirected to the login page after the restart is complete, click
the text "this link" in the countdown message.
Note: Device reset will cause CLI communications over an "USB" connection to
be lost. Therefore, re-connect the USB cable after the reset is complete.
Resetting All Settings to Factory Defaults
You must have the Administrator Privileges to reset all settings of the PX3 tofactory defaults.
Important: Exercise caution before resetting the PX3 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.

423

Chapter 7: Using the Web Interface

To reset the device to factory defaults:
1.

Choose Maintenance > Unit Reset >2.

Type your password and then click Factory Reset to reset the PX3 tofactory defaults.

3.

A message appears, with a countdown timer showing the remaining timeof the operation. It takes about two minutes to complete.

4.

When the reset is complete, the login page opens.

Tip: If you are not redirected to the login page after the reset is complete, click
the text "this link" in the countdown message.
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 684).
Note: Device reset will cause CLI communications over an "USB" connection to
be lost. Therefore, re-connect the USB cable after the reset is complete.
Retrieving Software Packages Information
You can check the current firmware version and the information of all open
source packages embedded in the PX3 through the web interface.
To retrieve the embedded software packages information:

424

1.

Choose Maintenance > About PDU. A list of open source packages isdisplayed.

2.

You can click any link to access related information or download any
software package.

.

Chapter 7: Using the Web Interface

Webcam Management
The 'Webcams' menu item appears when there is any webcam(s) connected to
the PX3, or when there are snapshots saved onto the PX3 already. See
Connecting a Logitech Webcam (on page 78).

425

Chapter 7: Using the Web Interface

With a Logitech® webcam connected to the PX3, you can visually monitor theenvironment around the PX3 via snapshots or videos captured by the webcam.
Permissions required:
To do...

Permission(s) required

View snapshots andvideosEither permission below:

Configure webcam
settings

Change Webcam Configuration▪ Change Webcam Configuration▪ View Webcam Snapshots and Configuration

Additional webcam-related actions you can take:
ActionRefer to

Manually store snapshots taken from thewebcam onto the PX3 or a remote server▪ Configuring Webcams andViewing Live Images (onpage 427)▪ Changing Storage Settings(on page 434)

Send a snapshot or video session's link toother people via email or instant message

Sending Links to Snapshots orVideos (on page 430)

Create event rules to trigger emails
containing snapshots from a webcam

Available Actions (on page334)

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

426

Chapter 7: Using the Web Interface

Configuring Webcams and Viewing Live Images
To configure a webcam or view live snapshot/video sessions, choose Webcams
in the Menu (on page 167). Then click the desired webcam to open thatwebcam'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.

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

The default is to show live snapshots. Interval time and capture
date/time of the image are displayed on the top of the image.

427

Chapter 7: Using the Web Interface

Tip: The date and time shown on the PX3 web interface are automaticallyconverted to your computer's time zone. To avoid time confusion, it issuggested to apply the same time zone settings as those of PX3 to yourcomputer or mobile device.
2.

To save the current image onto PX3 or a remote server, click
.

3.

▪

The default storage location for snapshots is the PX3 device. To savethem onto a remote server, see Changing Storage Settings (on page
434).

▪

To download an image onto your computer, move your mouse to thatimage, right click on it, and choose Save Image As.

To have the same live session displayed in a separate window, click.
▪

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

Note: Make sure your browser does not block the pop-up window, or the
separate window does not show up.
4.

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) andthe video capture date/time are displayed on the top of the image.

Image Controls:
1.

Click the Image Controls title bar to expand it.

2.

Adjust the brightness, contrast, saturation and gain by modifying theirvalues or adjusting the corresponding slide bar.
▪

To customize the gain value, you must deselect the Auto Gaincheckbox first.

▪

To restore all settings to this webcam's factory defaults, click.

Settings:
1.

428

By default the Settings section is open. If not, click the Settings title bar.

Chapter 7: Using the Web Interface

2.

Click Edit Settings.

3.

Enter a name for the webcam. Up to 64 ASCII printable characters aresupported.

4.

▪

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 434) and Identifying
Snapshots Folders on Remote Servers (on page 436).

▪

It is suggested to customize a webcam's name "prior to" savingsnapshots on the remote server. In case you change the webcam's
name after saving any snapshots, PX3 will create a new folder with the
new webcam name while keeping the old folder with the old name.

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 thosesnapshots 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 PX3 to save snapshots onto aremote server.
5.

Select a resolution for the webcam.
▪

6.

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.

Select the webcam mode.
Mode
Video
Snapshot

Description
The webcam enters the video mode.
▪ Set the 'Framerate' (frames per second) as needed.
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.

7.

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.

•

Or click Webcams again in the Menu (on page 167).

429

Chapter 7: Using the Web Interface

Sending Links to Snapshots or Videos
When opening a Primary Standalone Live Preview window, a unique URL isgenerated for this window session. You can email or instant message this URL
to as many people as possible as long as your system resources permit.
Recipients can then click on the provided link and view live snapshots or videos
simultaneously in the Secondary Standalone Live Preview window(s).
Tip: All Live Preview window sessions sharing the same URL, including one
Primary Standalone Live Preview window and multiple Secondary Standalone
Live Preview windows, are identified as one single "<webcam>" user in theConnected Users list. You can disconnect a "<webcam>" user to terminate allsessions sharing the same URL. See Viewing Connected Users (on page 403).
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 432).

To send a snapshot or video link via email or instant message:
1.

Choose Webcams in the Menu (on page 167).

2.

Click the desired webcam to open the Webcam page.
▪

430

Note that default webcam names are determined by the detection
order. The one that is detected first is named Webcam, and the otherthat is detected later is named Webcam 2.

3.

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

4.

Copy the URL from that live preview window.

Chapter 7: Using the Web Interfacea.

Select the URL shown on the top of the image.

b.

Right click to copy the URL, or press CTRL+ C.

5.

Send the URL link through an email or instant message application to one
or multiple persons.

6.

Leave the live preview window open until the recipient(s) opens thesnapshot or video via the link.

431

Chapter 7: Using the Web Interface

How Long a Link Remains Accessible

For documentation purposes, the one who opens and sends the URL of thePrimary Standalone Live Preview window is called User A and the tworecipients 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 PX3 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 notexceeded two minutes yet after the final live preview window session wasclosed.

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 PX3
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 PX3 device by default. For
snapshot-saving operations, see Configuring Webcams and Viewing Live
Images (on page 427).
Up to 10 snapshots can be stored onto the PX3. 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 snapshotof the webcam "with the most snapshots" is overridden.
Tip: To save more than 10 snapshots, you must change the storage locationfrom the PX3 to an FTP or Common Internet File System (CIFS)/Samba server.
See Changing Storage Settings (on page 434).
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 PX3 deletes all webcam snapshots that are saved
onto the PX3 locally. If needed, download important snapshots before
rebooting the device.

432

Chapter 7: Using the Web Interface

To view saved snapshots:
1.

Choose Webcams >opens.

. The Snapshots page

2.

Click the snapshot you want to view from the list.

Tip: The date and time shown on the PX3 web interface are automaticallyconverted to your computer's time zone. To avoid time confusion, it issuggested to apply the same time zone settings as those of PX3 to yourcomputer or mobile device.
3.

The selected snapshot as well as its information, such as captured time andresolution, is displayed on the same page.

4.

If the latest saved snapshot is not listed yet, click.

To manually delete any snapshots:
1.

Click

2.

Select the checkboxes of the images you want to remove.
▪

to make checkboxes appear.

To select all images, select the topmost checkbox in the header row.

433

Chapter 7: Using the Web Interface

3.

On the top of the list, click.

4.

Click Delete on the confirmation message.

•

To download any image onto the computer:To download an image onto your computer, move your mouse to thatimage, right click on it, and choose Save Image As.

Changing Storage Settings
Important: The PX3 web interface only lists the snapshots stored locally on
the PX3 device, but does NOT list those saved onto remote servers. You
must launch appropriate third-party applications, such as an FTP client, toaccess and manage the snapshots stored on remote servers.
The default is to store snapshots onto the PX3 device, which has a limitation of
10 snapshots. Note that any operation involving device reboot will remove thesnapshots saved on the PX3, such as firmware upgrade.
If you have either or both needs below, you must save snapshots onto aremote server like FTP or CIFS/Samba, instead of the PX3.
••

Total number of saved snapshots will exceed 10.
Saved snapshots must be stored permanently, or at least should not be
removed by the PX3 device's reboot.
To configure the storage settings:

1.

Choose Webcams > Edit Settings.

2.

Click the Storage Type field to select the desired storage location andconfigure as needed.
Note: When entering user credentials for remote servers, make sure theuser credentials you enter have the write permission, or NO snapshots canbe successfully saved onto remote servers.

434

Chapter 7: Using the Web Interface

Storage location
Local

CIFS/Samba

Description'Local' means the PX3. 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 PX3. See Viewing and Managing
Locally-Saved Snapshots (on page 432).
▪ All snapshots are CLEARED when the PX3 isrebooted.
Snapshots are saved onto a Common Internet File
System/Samba.
▪ Total number of saved snapshots depends on theserver's capacity.
▪ All saved snapshots remain available after rebooting
the PX3.
▪ 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 theserver's capacity.
▪ All saved snapshots remain available after rebooting
the PX3.
▪ Configure the following fields:* Server URL - the FTP server's path
* Username - for server access* Password - for server accessTo find where the snapshots are saved on CIFS/Samba or FTP, see
Identifying Snapshots Folders on Remote Servers (on page 436).
3.

Click Save.

Warning: Before disconnecting or powering off any remote server where thewebcam snapshots are being stored, you must first change the storage
settings, or the connectivity issue of the remote server may degrade theperformance of the PX3 web interface. If this issue occurs, first restore theconnectivity of the remote server and then change the storage settings of the
webcam snapshots.

435

Chapter 7: Using the Web Interface

Tip for notifications showing the snapshots path on FTP:
If you are using SNMP to retrieve PX3 data, you can make PX3 automaticallysend a notification containing the full path or URL to the snapshots saved onto
FTP with this SNMP code: webcamStorageUploadStarted.
Identifying Snapshots Folders on Remote Servers

If saving snapshots onto a remote server, you can access those snapshots via an
appropriate third-party application, such as an FTP client.
All snapshots are saved as JPEG and named according to the date and time
when saving the snapshots. Note that the date and time of the filename arebased on the time zone of the PX3 rather than that of the computer or mobile
device you are operating.
Tip: To check the time zone of your PX3, choose Device Settings > Date/Time.
See Setting the Date and Time (on page 312).
The structure of a snapshots folder looks similar to the diagram below.

NumberFolder name description
User-defined parent directory, whose name depends your server
settings, such as your FTP configuration.
Serial number of your PX3 device where the webcam is connected.
For example, PH85350018.
▪ To find your PX3 serial number, see Device Information (on page
398).

436

Chapter 7: Using the Web Interface

NumberFolder name description
The name of the webcam that your PX3 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 thesnapshots folder's name.
See Configuring Webcams and Viewing Live Images (on page427).
▪ If the webcam's location is important, you can customize thewebcam's name based on its location when configuring PX3 tosave snapshots onto a remote server.
The name of the webcam that your PX3 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 thewebcam's name based on its location when configuring PX3 tosave snapshots onto a remote server.

Note: It is suggested to customize a webcam's name "prior to" saving snapshotson the remote server. In case you change the webcam's name after saving any
snapshots, PX3 will create a new folder with the new webcam name while
keeping the old folder with the old name.

437

Chapter 7: Using the Web Interface

SmartLock and Card Reader
Raritan's SmartLock kits provide several cabinet access control solutions.
If you have purchased a SmartLock kit with the door handle controller"DX2-DH2C2", both menu items "SmartLock" and "Card Readers" will appear in
the menu after connecting and configuring properly DX2-DH2C2 and the door
handles included in the kit.
Note: For more information on DX2-DH2C2, such as its hardware installation,refer to the SmartLock Quick Setup Guide accompanying the SmartLock kit or'Environmental Sensors and Actuators Guide' (or its Online Help version) on the
Raritan Support page (http://www.raritan.com/support/).

438

Chapter 7: Using the Web Interface

Note that "SmartLock" appears only when your door handles are connected to
PX3 via DX2-DH2C2, but "Card Readers" appears as long as PX3 detects thepresence of any card reader -- either a standalone USB card reader or a card
reader integrated with the door handles.

••"SmartLock" page:
Shows the information of all door handle controllers (that is, DX2-DH2C2
modules) attached to PX3.
Shows the status of the door handle-integrated card readers connected to
DX2-DH2C2.
Note: Data of "external" USB card readers is NOT shown on the SmartLock
page. It is shown on the Card Readers page instead.

•

•

•

You can control the door handles on this page. See SmartLock (on page
440).
"Card Readers" page:
Shows the information of all card readers connected to PX3, including:▪

Door handle-integrated card readers connected to the DX2-DH2C2
module.

▪

External USB card readers connected to the USB-A port of PX3.

See Card Readers (on page 445).

439

Chapter 7: Using the Web Interface

SmartLockTo open the SmartLock page, choose SmartLock in the Menu (on page 167).
The page shows information of all DX2-DH2C2 modules attached to PX3,
including its serial number, position and its door handle configuration.

On this page you can:•View the status of the cabinet door and card reader.
Note: Data of "external" USB card readers is NOT shown on the SmartLock
page. It is shown on the Card Readers page instead.

440

Chapter 7: Using the Web Interface••

Configure the door handles connected to DX2-DH2C2. You must set thisbecause PX3 cannot detect the types of connected door handles.
Control the door handles connected to DX2-DH2C2.
To configure the door handles:

There are two door handle sections per DX2-DH2C2 because a DX2-DH2C2 has
two door handle ports. Before you configure the connected door handle(s), a
lock icon is displayed on each door handle section's top-right corner, and boththe Door State and Card Reader sections are unavailable.

1.

Click Edit Settings in the Settings section.

2.

In the 'Door handle type' field, select the door handle type you are using.
▪

3.

If your specific Southco H3-EM model is listed, select it. For all othersupported Southco H3-EM models, select "Southco H3-EM".

Make changes to the remaining fields as needed.

441

Chapter 7: Using the Web Interface

SectionTimeout

Door sensor
polarity

4.

442

Click Save.

Description▪ Specify how long the door handle lock can remain
open after someone opens the door handle via a smart
card or via remote control using the software. Whenthe timeout expires, the door handle lock will be
automatically closed. Default is 600 seconds (that is, 10
minutes).
Choose the correct setting based on the type of contact
closure sensors used to monitor the door:▪ Normally closed: The contact is closed (conducting)when the door is closed and open (not conducting)when the door is open. This is the default.
▪ Normally open: The contact not conducting when thedoor is closed and conducting when the door is open.
▪ Note: For both normally closed and normally open
sensors, the reported state is "alarmed" when the door
is open and "normal" when the door is closed.

Chapter 7: Using the Web Interface

Door Handle Status and Control

After configuring the door handle type properly, two more sections are shownfor the configured door handle -- Door State and Card Reader.

443

Chapter 7: Using the Web Interface

To view the status of the door and card reader:
Section
Door State

Description
Shows all sensor states detected by DX2-DH2C2, including:▪ Door: States of contact closure sensors connected to
DX2-DH2C2. Contact closure sensors detect whether
the door is physically opened or closed.
▪ Door Lock: States of door locks integrated with thedoor handles.
▪ Door Handle Lock: States of the door handle locks.
Door locks and door handle locks are interrelated so theirstates are changed one after another. The door handle lockis opened first and then the door lock.
Exception: If you manually open the door lock with the key
shipped with your door handle, the Door Lock state willenter the open state while the Door Handle Lock stateremains closed.

Card Reader

Shows the data of the smart card scanned by the internalor external card reader accompanying each door handle
connected to DX2-DH2C2.
Note: It is not necessary to use the internal card reader
unless you are using a third-party application, such as
Power IQ, for access control. Refer to the user
documentation of your third-party application for more
information.

Tip: All sensors of the connected door handles are also listed on the page ofPeripherals (on page 202).
Note that the same Card Reader information is also available on the page ofCard Readers (on page 445).
To control the door handles:
Per default, only one door handle can be opened at the same time so you
must close one door handle before opening another door handle connectedto the same PX3. To increase the upper limit of concurrently opened door
handles, see Peripherals (on page 202).
1.

444

Make sure you have configured the door handle type properly in the above
procedure.

Chapter 7: Using the Web Interface

2.

Go to the proper door handle section, and click Open or Close to open or
close the door handle lock.

3.

Confirm the operation when prompted.

4.

Now you can physically open the cabinet door with the opened door
handle.

Tip: You can click Close to re-close the door handle lock when you change yourmind before the door is physically opened, or when the door handle lock is
mistakenly opened, or when someone opens it without pulling out the door
handle. If not, then PX3 will automatically close the door handle lock after its
timeout expires.

•

DX2-DH2C2 LED information:
For information on DX2-DH2C2 LED, refer to 'Environmental Sensors andActuators Guide' (or its Online Help version) on the Raritan Support page(http://www.raritan.com/support/).

Card Readers
To open the Card Readers page, choose Card Readers in the Menu (on page
167).
This page lists all card readers connected to PX3, including:••Standalone USB card readers
Card readers integrated with door handles

Note: To have card readers integrated with door handles display on this page,
you must first configure the door handle properly on the page of SmartLock (onpage 440).

445

Chapter 7: Using the Web Interface

When a user scans his/her smart card with the card reader, PX3 will retrieve
the card's type and ID and show them in the corresponding Card Type and Card
ID column. If no data is shown in the two columns, it means the scanned card
may not be supported by the card reader.
Tip: You can use a third-party application, such as Power IQ, to retrieve the
card's data from PX3 to perform security features like cabinet access control.
Refer to that application's user documentation for more information.
Listed card readers can be one or both of the following types.

•

Door handle-integrated card readers:This type of card reader is integrated in the door handle, which is any
series below:▪

Emka Agent E▪

SouthCo H3-EM▪

Dirak eLine MLR 2x00

Note: Not every SouthCo H3-EM door handle has a card reader integrated.
For example, H3-EM-60-100 requires an external card reader.
•••

It is connected to PX3 via the DX2-DH2C2 module.
The Channel column indicates which door handle port (channel) it isconnected to.
Note that the serial number displayed for this card reader is the same as
DX2-DH2C2's serial number.
Each DX2-PD2C2 module can show two card readers because they have
two ports for connecting two door handles with card readers integrated.

•
•

446

Standalone USB card readers:
It is directly connected to the USB-A port of PX3.
The Channel column does not show any data.

Chapter 8

Using SNMPThis SNMP section helps you set up the PX3 for use with an SNMP manager.
The PX3 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 configuresome basic settings.

In This Chapter
Enabling and Configuring SNMP .......................................................................447
Downloading SNMP MIB...................................................................................452
SNMP Gets and Sets .........................................................................................453

Enabling and Configuring SNMP
To communicate with an SNMP manager, you must enable SNMP protocols on
the PX3. By default the "read-only" mode of SNMP v1/v2c is enabled.
The SNMP v3 protocol allows for encrypted communication. To take advantageof this, you must configure the users with the SNMP v3 access permission andset Authentication Pass Phrase and Privacy Pass Phrase, which act as sharedsecrets between SNMP and the PX3.
Important: You must download the SNMP MIB for your PX3 to use with your
SNMP manager. See Downloading SNMP MIB (on page 452).
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, andconfigure 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 281).
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 241).
To enable SNMP notifications:
1.

Choose Device Settings > Network Services > SNMP.

447

Chapter 8: Using SNMP

2.

In the SNMP Notifications section, enable the SNMP notification feature,and configure related fields. For details, refer to:▪

SNMPv2c Notifications (on page 448)▪

SNMPv3 Notifications (on page 449)

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 334).
SNMPv2c Notifications
1.

Choose Device Settings > Network Services > SNMP.

2.

In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox isselected.

3.

In the SNMP Notifications section, make sure the 'Enable SNMP
notifications' checkbox is selected.

4.

Select 'SNMPv2c trap' or 'SNMPv2c inform' as the notification type.

5.

Type values in the following fields.
Field

Description

Timeout

The interval of time, in seconds, after which a new
inform communication is resent if the first is notreceived.
▪ For example, resend a new inform communication

448

Chapter 8: Using SNMP

Field

Description
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. Thisis the address to which notifications are sent by the
SNMP agent.
You can specify up to 3 SNMP destinations.

6.

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 PX3 andall SNMP management stations.

Click Save.

SNMPv3 Notifications
1.

Choose Device Settings > Network Services > SNMP.

2.

In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox isselected.

449

Chapter 8: Using SNMP

450

3.

In the SNMP Notifications section, make sure the 'Enable SNMP
notifications' checkbox is selected.

4.

Select 'SNMPv3 trap' or 'SNMPv3 inform' as the notification type.

5.

For SNMP TRAPs, the engine ID is prepopulated.

6.

Type values in the following fields.
Field

Description

Host

The IP address of the device(s) you want to access.

Chapter 8: Using SNMP

Field

Description
This is the address to which notifications are sent by
the SNMP agent.

Port

The port number used to access the device(s).

User ID

User name for accessing the device.
▪ Make sure the user has the SNMP v3 accesspermission.

Timeout

The interval of time, in seconds, after which a new
inform communication is resent if the first is notreceived.
▪ For example, resend a new inform communication
once every 3 seconds.

Number of retries

Specify the number of times you want to resend theinform 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,The three fields are available when the security level is
set to AuthNoPriv or authPriv.

Authentication
passphrase,▪ Select the authentication protocol - MD5 or SHA▪ Enter the authentication passphrase

Confirm
authentication
passphrase
Privacy protocol,
Privacy passphrase,
Confirm privacy
passphrase
7.

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 theprivacy passphrase

Click Save.

451

Chapter 8: Using SNMP

Downloading SNMP MIB
You must download an appropriate SNMP MIB file for successful SNMP
communications. Always use the latest SNMP MIB downloaded from thecurrent firmware of your PX3.
You can download the MIBs from two different pages of the web interface.
MIB download via the SNMP page:1.

Choose Device Settings > Network Services > SNMP.

2.

Click the Download MIBs title bar.

3.

Select the desired MIB file to download.

4.

▪

PDU2-MIB: The SNMP MIB file for PX3 management.

▪

ASSETMANAGEMENT-MIB: The SNMP MIB file for asset management.

▪

LHX-MIB: The SNMP MIB file for managing the LHX/SHX heatexchanger(s).

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:

3.

▪

PDU2-MIB▪

ASSETMANAGEMENT-MIB▪

LHX MIB

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

452

Chapter 8: Using SNMP

SNMP Gets and Sets
In addition to sending notifications, the PX3 is able to receive SNMP get and set
requests from third-party SNMP managers.
••

Get requests are used to retrieve information about the PX3, such as thesystem 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 PX3 device name. When you change
the SNMP system name, the device name shown in the web interface isalso changed.
The PX3 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 PX3 MIB.
The PX3 MIB
The SNMP MIB file is required for using your PX3 with an SNMP manager. An
SNMP MIB file describes the SNMP functions.

453

Chapter 8: Using SNMP

LayoutOpening the MIB reveals the custom objects that describe the PX3 system atthe 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, definedand described in detail.

For example, the measurementsGroup group contains objects for sensor
readings of PX3 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 cause the PX3 to generate awarning and send an SNMP notification when certain parameters are exceeded.
See Sensor Threshold Settings (on page 777) for a description of how
thresholds work.
Note: When configuring the thresholds via SNMP set commands, ensure thevalue of upper critical threshold is higher than that of upper warning threshold.

454

Chapter 8: Using SNMP

Configuring NTP Server Settings

Using SNMP, you can change the following NTP server-related settings in theunitConfigurationTable:••••

Enable or disable synchronization of the device's date and time with NTP
servers (synchronizeWithNTPServer)
Enable or disable the use of DHCP-assigned NTP servers if synchronization
with NTP servers is enabled (useDHCPProvidedNTPServer)
Manually assign the primary NTP server if the use of DHCP-assigned NTP
servers is disabled (firstNTPServerAddressType and firstNTPServerAddress)
Manually assign the secondary NTP server (optional)(secondNTPServerAddressType 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 531). For the web interface, see Setting theDate and Time (on page 312).
When using the SNMP SET command to specify or change NTP servers, it isrequired that both the NTP server's address type and address be set in thecommand line simultaneously.
For example, the SNMP command to change the primary NTP server's addressfrom 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"
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 toactually enabling them. Otherwise, you may get an error message.

455

Chapter 9

Using the Command Line Interface
This section explains how to use the command line interface (CLI) to administer
the PX3.
Note that available CLI commands are model dependent.
CLI commands are case sensitive.

In This Chapter
About the Interface ..........................................................................................456
Logging in to CLI ................................................................................................457
The ? Command for Showing Available Commands .........................................460
Querying Available Parameters for a Command ..............................................461
Showing Information ........................................................................................462
Clearing Information .........................................................................................492
Configuring the PX3 Device and Network.........................................................493
Actuator Control Operations ............................................................................616
Unblocking a User .............................................................................................618
Resetting the PX3..............................................................................................618
Network Troubleshooting .................................................................................619
Retrieving Previous Commands ........................................................................622
Automatically Completing a Command ............................................................622
Logging out of CLI .............................................................................................623

About the Interface
The PX3 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 PX3
Display the PX3 and network information, such as the device name,firmware version, IP address, and so on
Configure the PX3 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 andis thus insecure. To enable Telnet, see Changing Telnet Settings (on page 285).

456

Chapter 9: Using the Command Line Interface

Logging in to CLI
Logging in via HyperTerminal over a local connection is a little different thanlogging in using SSH or Telnet.
If a security login agreement has been enabled, you must accept theagreement 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 commandline 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.
3.

In the communications program, press Enter to send a carriage return to
the PX3. The Username prompt appears.

4.

Type a name and press Enter. The name is case sensitive. Then you areprompted to enter a password.

5.

Type a password and press Enter. The password is case sensitive.

457

Chapter 9: Using the Command Line Interface

After properly entering the password, the PDU name appears at the
prompt. See Different CLI Modes and Prompts (on page 459) 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.
6.

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 278) in the User Guide.

2.

Launch an SSH or Telnet client and open a console window. A login prompt
appears.

3.

Type a name and press Enter. The name is case sensitive.
Note: If using the SSH client, the name must NOT exceed 25 characters.
Otherwise, the login fails.
Then you are prompted to enter a password.

4.

Type a password and press Enter. The password is case sensitive.

5.

After properly entering the password, the PDU name appears at the
prompt. See Different CLI Modes and Prompts (on page 459) 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.

6.

458

You are now logged in to the command line interface and can begin
administering this product.

Chapter 9: Using the Command Line Interface

With an Analog Modem
The PX3 supports remote access to the CLI via a connected analog modem. Thisfeature is especially useful when the LAN access is not available.
To connect to the PX3 via the modem:
1.

Make sure the PX3 has an analog modem connected. See Connecting an
Analog Modem (on page 79).

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 PX3.
See Configuring the Serial Port (on page 387).

4.

Type the following AT command to make a connection with the PX3.
ATD<modem phone number>

5.

The CLI login prompt appears after the connection is establishedsuccessfully. Then type the user name and password to log in to the CLI.
To disconnect from the PX3:

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 PX3.
ATH

Different CLI Modes and Prompts
Depending on the login name you use and the mode you enter, the systemprompt in the CLI varies. The PDU name appears with the prompt.
•
•
•

•

User Mode: When you log in as a normal user, who may not have full
permissions to configure the PX3, the > prompt appears.
Administrator Mode: When you log in as an administrator, who has full
permissions to configure the PX3, the # prompt appears.
Configuration Mode: You can enter the configuration mode from theadministrator or user mode. In this mode, the prompt changes to config:#
or config:> and you can change PX3 device and network configurations.
See Entering Configuration Mode (on page 493).
Diagnostic Mode: You can enter the diagnostic mode from theadministrator or user mode. In this mode, the prompt changes to diag:# or
diag:> and you can perform the network troubleshooting commands, suchas the ping command. See Entering Diagnostic Mode (on page 619).

459

Chapter 9: Using the Command Line Interface

Closing a Local Connection
Close the window or terminal emulation program when you finish accessing
the PX3 over the local connection.
When accessing or upgrading multiple PX3 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 atanytime 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 461).
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 thecurrent mode is displayed.
Tip: To automatically complete a command after typing part of the fullcommand, see Automatically Completing a Command (on page 622). To
re-execute one of the previous commands, see Retrieving Previous Commands(on page 622).

460

Chapter 9: Using the Command Line Interface

Querying Available Parameters for a Command
If you are not sure what commands or parameters are available for a particular
type of CLI command or its syntax, you can have the CLI show them by adding aspace and the help command (?) or list command (ls) to the end of thatcommand. 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 fullcommand, see Automatically Completing a Command (on page 622). To
re-execute one of the previous commands, see Retrieving Previous Commands(on page 622).

461

Chapter 9: Using the Command Line Interface

Showing Information
You can use the show commands to view current settings or the status of thePX3 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 soon.
Some "show" commands have two formats: one with the parameter "details"
and the other without. The difference is that the command without theparameter "details" displays a shortened version of information while the otherdisplays 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 459).
Network Configuration
This command shows all network configuration and all network interfaces'
information, such as the IP address, MAC address, the Ethernet interfaces'
duplex mode, and the wireless interface's status/settings.
#

462

show network

Chapter 9: Using the Command Line Interface

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, see IPv4-Only or
IPv6-Only Configuration (on page 464).
#

show network ip common

To show the IP settings of a specific network interface, use the following
command.
#show network ip interface <ETH>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.
Interface

Description

eth1

Show the IP-related configuration of the ETH1
interface.

eth2

Show the IP-related configuration of the ETH2
interface.

wireless

Show the IP-related configuration of the WIRELESS
interface.

bridgeShow the IP-related configuration of the BRIDGE
interface.

all

Show the IP-related configuration of all interfaces.
Tip: You can also type the command without adding
this option "all" to get the same data. That is, show
network ip interface.

463

Chapter 9: Using the Command Line Interface

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, see IP Configuration (onpage 463).
To show IPv4 settings shared by all network interfaces, such as DNS androutes:#show network ipv4 common

To show IPv6 settings shared by all network interfaces, such as DNS androutes:#show network ipv6 common

To show the IPv4 configuration of a specific network interface:#show network ipv4 interface <ETH>

To show the IPv6 configuration of a specific network interface:#show network ipv6 interface <ETH>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

464

Interface

Description

eth1

Show the IPv4 or IPv6 configuration of the ETH1
interface.

eth2

Show the IPv4 or IPv6 configuration of the ETH2
interface.

wireless

Show the IPv4 or IPv6 configuration of the WIRELESS
interface.

Chapter 9: Using the Command Line Interface

Interface

Description

bridgeShow the IPv4 or IPv6 configuration of the BRIDGE
interface.

all

Show the IPv4 or IPv6 configuration of all interfaces.
Tip: You can also type the command without adding
this option "all" to get the same data. That is, show
network ipv4 interface.

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 andauthentication protocol.
#

show network interface <ETH>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.
Interface

Description

eth1

Show the ETH1 interface's non-IP settings.

eth2Show the ETH2 interface's non-IP settings.

wireless

Show the WIRELESS interface's non-IP settings.

bridgeShow the BRIDGE interface's non-IP settings.

allShow the non-IP settings of all interfaces.
Tip: You can also type the command without adding
this option "all" to get the same data. That is, show
network interface.

465

Chapter 9: Using the Command Line Interface

Network Service Settings

This command shows the network service settings only, including the Telnet
setting, TCP ports for HTTP, HTTPS, SSH and Modbus/TCP services, and SNMP
settings.
#

show network services <option>

Variables:•<option> is one of the options: all, http, https, telnet, ssh, snmp, modbus
and zeroconfig.
OptionDescription

all

Displays the settings of all network services, including
HTTP, HTTPS, Telnet, SSH and SNMP.
Tip: You can also type the command without adding
this option "all" to get the same data.

httpOnly displays the TCP port for the HTTP service.

https

Only displays the TCP port for the HTTPS service.

telnetOnly displays the settings of the Telnet service.

ssh

Only displays the settings of the SSH service.

snmp

Only displays the SNMP settings.

modbusOnly displays the settings of the Modbus/TCP service.

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 thecommand.
#466

show pdu details

Chapter 9: Using the Command Line Interface

Outlet Information
This command syntax shows the outlet information.
#

show outlets <n>

To show detailed information, add the parameter "details" to the end of thecommand.
#show outlets <n> details

Variables:•<n> is one of the options: all, or a number.
OptionDescription

all

Displays the information for all outlets.
Tip: You can also type the command without adding
this option "all" to get the same data.

A specific outlet
number

Displays the information for the specified outlet only.

Displayed information:••

Without the parameter "details," only the outlet name is displayed.
With the parameter "details," more outlet information is displayed inaddition to the outlet name, such as the outlet rating.

467

Chapter 9: Using the Command Line Interface

Inlet Information
This command syntax shows the inlet information.
#

show inlets <n>

To show detailed information, add the parameter "details" to the end of thecommand.
#show inlets <n> details

Variables:•<n> is one of the options: all, or a number.
OptionDescription

all

Displays the information for all inlets.
Tip: You can also type the command without adding
this option "all" to get the same data.

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

468

Without the parameter "details," only the inlet's name and RMS current
are displayed.
With the parameter "details," more inlet information is displayed inaddition to the inlet name and RMS current, such as the inlet's RMS
voltage, active power and active energy.

Chapter 9: Using the Command Line Interface

Overcurrent Protector Information
This command is only available for models with overcurrent protectors forprotecting outlets.
This command syntax shows the overcurrent protector information, such as a
circuit breaker or a fuse.
#show ocp <n>

To show detailed information, add the parameter "details" to the end of thecommand.
#show ocp <n> details

Variables:•<n> is one of the options: all, or a number.
OptionDescription

all

Displays the information for all overcurrent protectors.
Tip: You can also type the command without adding
this option "all" to get the same data.

A specificovercurrent
protector
number

Displays the information for the specified overcurrent
protector only.

Displayed information:••

Without the parameter "details," only the overcurrent protector status andname are displayed.
With the parameter "details," more overcurrent protector information isdisplayed in addition to status, such as the rating and RMS current value.

469

Chapter 9: Using the Command Line Interface

Date and Time Settings
This command shows the current date and time settings on the PX3.
#

show time

To show detailed information, add the parameter "details" to the end of thecommand.
#show time details

Default Measurement Units
This command shows the default measurement units applied to the PX3 web
and CLI interfaces across all users, especially those users authenticated throughremote authentication servers.
#

show user defaultPreferences

Note: If a user has set his/her own preferred measurement units or theadministrator has changed any user's preferred units, the web and CLIinterfaces show the preferred measurement units for that user instead of thedefault ones. See Existing User Profiles (on page 483) for the preferredmeasurement units for a specific user.

470

Chapter 9: Using the Command Line Interface

Environmental Sensor Information
This command syntax shows the environmental sensor's information.
show externalsensors <n>#

To show detailed information, add the parameter "details" to the end of thecommand.
show externalsensors <n> details#

Variables:•<n> is one of the options: all, or a number.
OptionDescription

all

Displays the information of all environmental sensors.
Tip: You can also type the command without adding
this option "all" to get the same data.

A specificenvironmental
sensor number*

Displays the information for the specified
environmental sensor only.

471

Chapter 9: Using the Command Line Interface* The environmental sensor number is the ID number assigned to the sensor,
which can be found on the Peripherals page of the PX3 web interface.
Displayed information:•

Without the parameter "details," only the sensor ID, sensor type andreading 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.

Environmental Sensor Package Information
Different from the "show externalsensors" commands, which show thereading, status and configuration of an individual environmental sensor, thefollowing command shows the information of all connected environmental
sensor packages, each of which may contain more than one sensor or actuator.
#

show peripheralDevicePackages

Information similar to the following is displayed. Peripheral Device Package
refers to an environmental sensor package.
Peripheral Device Package 1
Serial Number:

1GE7A00022

Package Type:

DX2-T1H1

Position:

Port 1, Chain Position 1

Package State:

operationalFirmware Version: 33.0
Peripheral Device Package 2
Serial Number:

1GE7A00021

Package Type:

DX2-T3H1

Position:

Port 1, Chain Position 2

Package State:

operationalFirmware Version: 33.0

472

Chapter 9: Using the Command Line Interface

Actuator Information
This command syntax shows an actuator's information.
#

show actuators <n>

To show detailed information, add the parameter "details" to the end of thecommand.
#show actuators <n> details

Variables:•<n> is one of the options: all, or a number.
OptionDescription

all

Displays the information for all actuators.
Tip: You can also type the command without adding
this option "all" to get the same data.

A specificactuator
number*

Displays the information for the specified actuator
only.

* The actuator number is the ID number assigned to the actuator. The ID
number can be found using the PX3 web interface or CLI. It is an integer
starting at 1.
Displayed information:••

Without the parameter "details," only the actuator ID, type and state aredisplayed.
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, andZ coordinates.

473

Chapter 9: Using the Command Line Interface

Inlet Sensor Threshold Information
This command syntax shows the specified inlet sensor's threshold-related
information.
#

show sensor inlet <n> <sensor type>

To show detailed information, add the parameter "details" to the end of thecommand.
#show sensor inlet <n> <sensor type> details

Variables:
•
•

474

<n> is the number of the inlet whose sensors you want to query. For asingle-inlet PDU, <n> is always 1.
<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

unbalancedCurrent

Unbalanced load sensor

lineFrequency

Line frequency sensor

Chapter 9: Using the Command Line Interface

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.

Additional sensors supported by specific models:Specific PX3 models support some or all of the following sensors. The CLI
command(s) listed above can be also applied to the following sensors. Notethat the measurement unit of current values in CLI is A, not mA.
Sensor type

Description

peakCurrent

Peak current sensor

Supported on PXC andLegrand PDU only

▪ three-phase models als
support pole-level peakcurrent▪ models with meteredbreakers also support
breaker-level peakcurrent
reactivePower

Reactive power sensor

displacementPowerFact
or

Displacement power factor sensor

residualCurrent

RCM current sensor▪

▪ For Type A, it is the sensor that detects
residual AC current.
▪ For Type B, it is the sensor that detects
both residual AC and DC current.
residualDCCurrent

RCM DC current sensor - detects residual DC
current only.
Available only on PDUs with RCM Type B.

Note: For information on RCM Type A and B sensors, see RCM Current Sensor(on page 686).

475

Chapter 9: Using the Command Line Interface

Inlet Pole Sensor Threshold Information
This command syntax shows the specified inlet pole sensor's threshold-related
information.
#

show sensor inletpole <n> <p> <sensor type>

To show detailed information, add the parameter "details" to the end of thecommand.
#show sensor inletpole <n> <p> <sensor type> details

Variables:
•
•

•

476

<n> is the number of the inlet whose pole sensors you want to query. For asingle-inlet PDU, <n> is always 1.
<p> is the label of the inlet pole whose sensors you want to query.
Pole

Label
<p>

Current sensor

Voltage sensor

1

L1

L1

L1 - L22

L2

L2

L2 - L33

L3

L3

L3 - L1<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

Chapter 9: Using the Command Line Interface

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.

Additional sensors supported by specific models:Specific PX3 models support some or all of the following sensors. The CLI
command(s) listed above can be also applied to the following sensors. Notethat the measurement unit of current values in CLI is A, not mA.
Sensor type

Description

peakCurrent

Peak current sensor

Supported on PXC andLegrand PDU only

▪ three-phase models als
support pole-level peakcurrent▪ models with meteredbreakers also support
breaker-level peakcurrent
reactivePower

Reactive power sensor

displacementPowerFact
or

Displacement power factor sensor

residualCurrent

RCM current sensor▪

▪ For Type A, it is the sensor that detects
residual AC current.
▪ For Type B, it is the sensor that detects
both residual AC and DC current.
residualDCCurrent

RCM DC current sensor - detects residual DC
current only.
Available only on PDUs with RCM Type B.

Note: For information on RCM Type A and B sensors, see RCM Current Sensor(on page 686).

477

Chapter 9: Using the Command Line Interface

Overcurrent Protector Sensor Threshold Information
This command is only available for models with overcurrent protectors forprotecting outlets.
This command syntax shows the specified overcurrent protector sensor's
threshold-related information.
#

show sensor ocp <n> <sensor type>

To show detailed information, add the parameter "details" to the end of thecommand.
#show sensor ocp <n> <sensor type> details

Variables:••<n> is the number of the overcurrent protector whose sensors you want toquery.
<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

Displayed information:
•

•

478

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.

Chapter 9: Using the Command Line Interface

Environmental Sensor Threshold Information
This command syntax shows the specified environmental sensor's
threshold-related information.
#

show sensor externalsensor <n>

To show detailed information, add the parameter "details" to the end of thecommand.
#show sensor externalsensor <n> details

479

Chapter 9: Using the Command Line Interface

Variables:•<n> is the environmental sensor number. The environmental sensor
number is the ID number assigned to the sensor, which can be found on
the Peripherals page of the PX3 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 <sensor type>

To show detailed information, add the parameter "details" to the end of thecommand.
#show defaultThresholds <sensor type> details

Variables:•

480<sensor type> is one of the following numeric sensor types:
Sensor types

Description

absoluteHumidity

Absolute humidity sensors

relativeHumidity

Relative humidity sensors

temperature

Temperature sensors

airPressure

Air pressure sensors

airFlow

Air flow sensors

vibration

Vibration sensors

Chapter 9: Using the Command Line Interface

Sensor types

Descriptionall

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 thespecified 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 PX3.
#

show security

To show detailed information, add the parameter "details" to the end of thecommand.
#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, suchas user blocking time, user idle timeout and front panel permissions (ifsupported by your model).

481

Chapter 9: Using the Command Line Interface

Authentication Settings
General authentication settings:
This command displays the authentication settings of the PX3, 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.
#show authentication ldapServer <server_num>-- OR -#

show authentication ldapServer <server_num>

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.
#show authentication radiusServer <server_num>-- OR-#

show authentication radiusServer <server_num> details

Variables:•<server_num> is the sequential number of the specified authentication
server on the LDAP or Radius server list.

Displayed information:
•
•
•

482

Without specifying any server, PX3 shows the authentication type and a listof 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 nameattribute, or a Radius server's timeout and retries values.

Chapter 9: Using the Command Line Interface

Existing User Profiles
This command shows the data of one or all existing user profiles.
#

show user <user_name>To show detailed information, add the parameter "details" to the end of thecommand.
#show user <user_name> details

Variables:•<user_name> 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.
OptionDescription

allThis option shows all existing user profiles.
Tip: You can also type the command without
adding this option "all" to get the same data.

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 aredisplayed: user name, user "Enabled" status, SNMP v3 access privilege, androle(s).
With the parameter "details," more user information is displayed, such as
the telephone number, e-mail address, preferred measurement units andso on.

483

Chapter 9: Using the Command Line Interface

Existing Roles
This command shows the data of one or all existing roles.
#

show roles <role_name>

Variables:•<role_name> is the name of the role whose permissions you want to query.
The variable can be one of the following options:
OptionDescription

allThis option shows all existing roles.
Tip: You can also type the command without
adding this option "all" to get the same data.

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.

Serial Port Settings
This command shows the baud rate setting of the serial port labeled CONSOLE/ MODEM on the PX3.
#

show serial

EnergyWise Settings
This command shows the PX3 device's current configuration for Cisco ®
EnergyWise.
#484

show energywiseChapter 9: Using the Command Line Interface

Asset Strip Settings
This command shows the asset strip settings, such as the total number of rackunits (tag ports), asset strip state, numbering mode, orientation, available tags
and LED color settings.
#

show assetStrip <n>Variables:•<n> is one of the options: all, or a number.
OptionDescription

all

Displays all asset strip information.
Tip: You can also type the command without adding
this option "all" to get the same data.

A specific asset
strip number

Displays the settings of the asset strip connected to thespecified FEATURE port number.
For the PX3 device with only one FEATURE port, thevalid number is always 1.

Rack Unit Settings of an Asset Strip
A rack unit refers to a tag port on the asset strips. This command shows thesettings of a specific rack unit or all rack units on an asset strip, such as a rackunit's LED color and LED mode.
#show rackUnit <n> <rack_unit>

Variables:••<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<rack_unit> is one of the options: all or a specific rack unit's index number.
OptionDescription

all

Displays the settings of all rack units on the specified
asset strip.
Tip: You can also type the command without adding
this option "all" to get the same data.

485

Chapter 9: Using the Command Line Interface

OptionDescription

A specificnumber

Displays the settings of the specified rack unit on thespecified 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.

Event Log
The command used to show the event log begins with show eventlog. You
can add either the limit or class parameters or both to show specific events.
Show the last 30 entries:#

show eventlog

Show a specific number of last entries in the event log:#

show eventlog limit <n>Show a specific type of events only:#

show eventlog class <event_type>Show a specific number of last entries associated with a specific type of
events only:#

show eventlog limit <n> class <event_type>

Variables:
•

•

486

<n> is one of the options: all or a number.
OptionDescription

all

Displays all entries in the event log.

An integer
number

Displays the specified number of last entries in theevent log. The number ranges between 1 to 10,000.

<event_type> is one of the following event types.
Event type

Descriptionall

All events.

deviceDevice-related events, such as system starting or
firmware upgrade event.

Chapter 9: Using the Command Line Interface

Event type

Description

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.

sensorInternal or external sensor events, such as statechanges of any sensors.

serverMonitor

Server-monitoring records, such as a server being
declared reachable or unreachable.

assetManagement

Raritan asset management events, such as asset
tag connections or disconnections.

lhx

Schroff® LHX/SHX heat exchanger events.

modem

Modem-related events.

timerEvent

Scheduled action events.

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

Network Connections Diagnostic Log
This command shows the diagnostic log for both the EAP authentication andwireless LAN connection.
#

show network diagLog

Server Reachability Information
This command shows all server reachability information with a list ofmonitored servers and status.
#

show serverReachability

487

Chapter 9: Using the Command Line Interface

Server Reachability Information for a Specific Server

To show the server reachability information for a certain IT device only, use thefollowing command.
#show serverReachability server <n>

To show detailed information, add the parameter "details" to the end of thecommand.
#show serverReachability server <n> details

Variables:•<n> is a number representing the sequence of the IT device in themonitored server list.
You can find each IT device's sequence number using the CLI command ofshow serverReachability as illustrated below.

Displayed information:••

Without the parameter "details," only the specified device's IP address,
monitoring enabled/disabled state and current status are displayed.
With the parameter "details," more settings for the specified device aredisplayed, 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:•

488

A list of commands that were previously entered in the current session isdisplayed.

Chapter 9: Using the Command Line Interface

Reliability Data
This command shows the reliability data.
#

show reliability data

Reliability Error Log
This command shows the reliability error log.
#

show reliability errorlog <n>Variables:•<n> is one of the options: 0 (zero) or any other integer number.
OptionDescription0

Displays all entries in the reliability error log.
Tip: You can also type the command without adding
this option "0" to get all data.

A specific integer Displays the specified number of last entries in thenumberreliability 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 421).
ExamplesThis section provides examples of the show command.

489

Chapter 9: Using the Command Line Interface

Example 1 - Basic Security Information

The diagram shows the output of the show security command.

490

Chapter 9: Using the Command Line Interface

Example 2 - In-Depth Security Information

More information is displayed when typing the show security details command.

Example 3 - Basic PDU Information

The diagram shows the output of the show pdu command.

491

Chapter 9: Using the Command Line Interface

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.

Clearing Information
You can use the clear commands to remove unnecessary data from the PX3.
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 459).
Clearing Event Log
This command removes all data from the event log.
#

clear eventlog-- OR --#

clear eventlog /yIf 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 theoperation.
If you type y, a message "Event log was cleared successfully" is displayed after
all data in the event log is deleted.

492

Chapter 9: Using the Command Line Interface

Clearing Diagnostic Log for Network Connections
This command removes all data from the diagnostic log for both the EAP
authentication and WLAN connection.
#clear networkDiagLog-- OR --#

clear networkDiagLog /yIf you entered the command without "/y," a message appears, prompting you
to confirm the operation. Type y to clear the log or n to abort the operation.

Configuring the PX3 Device and Network
To configure the PX3 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. Configurationcommands 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 459).

2.

Type config and press Enter.

3.

The config:# prompt appears, indicating that you have enteredconfiguration mode.

4.

Now you can type any configuration command and press Enter to change
the settings.

Important: To apply new configuration settings, you must issue the "apply"
command before closing the terminal emulation program. Closing the
program does not save any configuration changes. See Quitting Configuration
Mode (on page 494).

493

Chapter 9: Using the Command Line Interface

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:#

cancelThe # or > prompt appears after pressing Enter, indicating that you haveentered the administrator or user mode. See Different CLI Modes and Prompts(on page 459).

PDU Configuration Commands
One PDU configuration command begins with pdu. You can use the PDU
configuration commands to change the settings that apply to the whole PX3
device.
Configuration commands are case sensitive so ensure you capitalize themcorrectly.
Changing the PDU Name

This command changes the device name of PX3.
config:#pdu name "<name>"

Variables:•494<name> is a string comprising up to 64 ASCII printable characters. The<name> variable must be enclosed in quotes when it contains spaces.

Chapter 9: Using the Command Line Interface

Enabling or Disabling Data Logging

This command enables or disables the data logging feature.
config:#pdu dataRetrieval <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableEnables the data logging feature.

disableDisables the data logging feature.

For more information, see Setting Data Logging (on page 372).

Setting Data Logging Measurements Per Entry

This command defines the number of measurements accumulated per log
entry.
config:#pdu measurementsPerLogEntry <number>

Variables:•<number> is an integer between 1 and 600. The default is 60 samples perlog entry.

For more information, see Setting Data Logging (on page 372).

495

Chapter 9: Using the Command Line Interface

Specifying the Device Altitude

This command specifies the altitude of your PX3 above sea level (in meters).
You must specify the altitude of PX3 above sea level if a Raritan's differential airpressure sensor is attached. This is because the device's altitude is associatedwith the altitude correction factor. See Altitude Correction Factors (on page787).
config:#pdu deviceAltitude <altitude>

Variables:••<altitude> 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 theheight (Z coordinate) of environmental sensors.
config:#pdu externalSensorsZCoordinateFormat <option>

Variables:•<option> is one of the options: rackUnits or freeForm.
OptionDescription

rackUnits

The height of the Z coordinate is measured instandard rack units.
When this is selected, you can type a numeric value inthe 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 forit. See Setting the Z Coordinate (on page 585).

496

Chapter 9: Using the Command Line Interface

Enabling or Disabling Peripheral Device Auto Management

This command enables or disables the Peripheral Device Auto Management
feature.
config:#pdu peripheralDeviceAutoManagement <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableEnables the automatic management feature forenvironmental sensor packages.

disableDisables the automatic management feature forenvironmental sensor packages.

For more information, see How the Automatic Management Function Works(on page 215)..
Setting the Maximum Number of Active Powered Dry Contact Actuators

This command determines the upper limit of "active" powered dry contact
actuators on one PX3 device. You need either 'Change Peripheral Device
Configuration' privilege or 'Administrator Privileges' to change its upper limit.
config:#pdu activePoweredDryContactLimit <number>

Variables:•<number> 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.

ExamplesThis 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"497

Chapter 9: Using the Command Line Interface

Example 2 - Data Logging Enabled

The following command enables the data logging feature.
config:#pdu dataRetrieval enable

Network Configuration Commands
A network configuration command begins with network. A number of network
settings can be changed through the CLI, such as the IP address, transmission
speed, duplex mode, and so on.
Configuring IPv4 Parameters

An IPv4 configuration command begins with network ipv4.
Setting the IPv4 Configuration Mode

This command determines the IP configuration mode.
config:#network ipv4 interface <ETH> configMethod <mode>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

498

Interface

Description

eth1

Determine the IPv4 configuration mode of the ETH1
interface (wired networking).

eth2

Determine the IPv4 configuration mode of the ETH2
interface (wired networking).

wireless

Determine the IPv4 configuration mode of the
WIRELESS interface (that is, wireless networking).

bridgeDetermine the IPv4 configuration mode of the BRIDGE
interface (that is, bridging mode).

Chapter 9: Using the Command Line Interface•<mode> is one of the modes: dhcp or static.
Mode

Description

dhcp

The IPv4 configuration mode is set to DHCP.

staticThe IPv4 configuration mode is set to static IP address.

Setting the IPv4 Preferred Host Name

After selecting DHCP as the IPv4 configuration mode, you can specify thepreferred host name, which is optional. The following is the command:
config:#network ipv4 interface <ETH> preferredHostName <name>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

•Interface

Description

eth1

Determine the IPv4 preferred host name of the ETH1
interface (that is, wired networking).

eth2

Determine the IPv4 preferred host name of the ETH2
interface (that is, wired networking).

wireless

Determine the IPv4 preferred host name of the
WIRELESS interface (that is, wireless networking).

bridgeDetermine the IPv4 preferred host name of the
BRIDGE interface (that is, bridging mode).

<name> is a host name which:▪

Consists of alphanumeric characters and/or hyphens▪

Cannot begin or end with a hyphen▪

Cannot contain more than 63 characters▪

Cannot contain punctuation marks, spaces, and other symbols

499

Chapter 9: Using the Command Line Interface

Setting the IPv4 Address

After selecting the static IP configuration mode, you can use this command toassign a permanent IP address to the PX3.
config:#network ipv4 interface <ETH> address <ip address>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

•Interface

Description

eth1

Determine the IPv4 address of the ETH1 interface(that is, wired networking).

eth2

Determine the IPv4 address of the ETH2 interface(that is, wired networking).

wireless

Determine the IPv4 address of the WIRELESS interface(that is, wireless networking).

bridgeDetermine the IPv4 address of the BRIDGE interface(that is, the bridging mode).

<ip address> is the IP address being assigned to your PX3. Its format is "IPaddress/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 <ip address>

Variables:•500<ip address> is the IP address of the gateway. The value ranges from
0.0.0.0 to 255.255.255.255.

Chapter 9: Using the Command Line Interface

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 PX3 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 266).
Method 1: add a static route when the other network is NOT directly
reachable:
config:#network ipv4 staticRoutes add <dest-1> nextHop <hop>Method 2: add a static route when the other network is directly
reachable:
config:#network ipv4 staticRoutes add <dest-1> interface <ETH>

Delete an existing static route:config:#network ipv4 staticRoutes delete <route_ID>

Modify an existing static route:config:#network ipv4 staticRoutes modify <route_ID> dest <dest-2> nextHop <hop>-- OR --

501

Chapter 9: Using the Command Line Interface

config:#network ipv4 staticRoutes modify <route_ID> dest <dest-2> interface<ETH>

Variables:
•
•
•
•
•

<dest-1> is a combination of the IP address and subnet mask of the othersubnet. The format is IP address/subnet mask.
<hop> is the IP address of the next hop router.
<ETH> is one of the interfaces: ETH1/ETH2, WIRELESS and BRIDGE. Type"bridge" only when your PX3 is in the bridging mode.
<route_ID> is the ID number of the route setting which you want to delete
or modify.
<dest-2> is a modified route setting that will replace the original routesetting. Its format is IP address/subnet mask. You can modify either the IP
address or the subnet mask or both.

Configuring IPv6 Parameters

An IPv6 configuration command begins with network ipv6.
Setting the IPv6 Configuration Mode

This command determines the IP configuration mode.
config:#network ipv6 interface <ETH> configMethod <mode>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

502

Interface

Description

eth1

Determine the IPv6 configuration mode of the ETH1
interface (wired networking).

eth2

Determine the IPv6 configuration mode of the ETH2
interface (wired networking).

wireless

Determine the IPv6 configuration mode of the
WIRELESS interface (that is, wireless networking).

Chapter 9: Using the Command Line Interface•

Interface

Description

bridgeDetermine the IPv6 configuration mode of the BRIDGE
interface (that is, bridging mode).

<mode> is one of the modes: automatic or static.
Mode

Description

automatic

The IPv6 configuration mode is set to automatic.

staticThe IPv6 configuration mode is set to static IP address.

Setting the IPv6 Preferred Host Name

After selecting DHCP as the IPv6 configuration mode, you can specify thepreferred host name, which is optional. The following is the command:
config:#network ipv6 interface <ETH> preferredHostName <name>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

•Interface

Description

eth1

Determine the IPv6 preferred host name of the ETH1
interface (wired networking).

eth2

Determine the IPv6 preferred host name of the ETH2
interface (wired networking).

wireless

Determine the IPv6 preferred host name of the
WIRELESS interface (that is, wireless networking).

bridgeDetermine the IPv6 preferred host name of the
BRIDGE interface (that is, bridging mode).

<name> is a host name which:▪

Consists of alphanumeric characters and/or hyphens▪

Cannot begin or end with a hyphen▪

Cannot contain more than 63 characters503

Chapter 9: Using the Command Line Interface•

Cannot contain punctuation marks, spaces, and other symbols

Setting the IPv6 Address

After selecting the static IP configuration mode, you can use this command toassign a permanent IP address to the PX3.
config:#network ipv6 interface <ETH> address <ipaddress>

Variables:•<ETH> is one of the network interfaces: ETH1/ETH2, WIRELESS, or BRIDGE.
Note that you must choose/configure the bridge interface if your PX3 is set
to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interfacefunction. The IP parameters of ETH1/ETH2 and WIRELESS interfaces do NOT
function.

•

504

Interface

Description

eth1

Determine the IPv6 address of the ETH1 interface(wired networking).

eth2

Determine the IPv6 address of the ETH2 interface(wired networking).

wireless

Determine the IPv6 address of the WIRELESS interface(that is, wireless networking).

bridgeDetermine the IPv6 address of the BRIDGE interface(that is, the bridging mode).

<ip address> is the IP address being assigned to your PX3. This value uses
the IPv6 address format. Note that you must add /xx, which indicates aprefix length of bits such as /64, to the end of this IPv6 address.

Chapter 9: Using the Command Line Interface

Setting the IPv6 Gateway

After selecting the static IP configuration mode, you can use this command to
specify the gateway.
config:#network ipv6 gateway <ip address>

Variables:•<ip address> 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 PX3 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 266).
Method 1: add a static route when the other network is NOT directly
reachable:
config:#network ipv6 staticRoutes add <dest-1> nextHop <hop>Method 2: add a static route when the other network is directly
reachable:
config:#network ipv6 staticRoutes add <dest-1> interface <ETH>

Delete an existing static route:config:#network ipv6 staticRoutes delete <route_ID>

Modify an existing static route:config:#network ipv6 staticRoutes modify <route_ID> dest <dest-2>
nextHop <hop>-- OR --

505

Chapter 9: Using the Command Line Interface

config:#network ipv6 staticRoutes modify <route_ID> dest <dest-2> interface<ETH>

Variables:
•
•
•
•
•

<dest-1> is the IP address and prefix length of the subnet where the PX3
belongs. The format is IP address/prefix length.
<hop> is the IP address of the next hop router.
<ETH> is one of the interfaces: ETH1/ETH2, WIRELESS and BRIDGE. Type"bridge" only when your PX3 is in the bridging mode.
<route_ID> is the ID number of the route setting which you want to delete
or modify.
<dest-2> is a modified route setting that will replace the original routesetting. Its format is IP address/prefix length. You can modify either the IP
address or the prefix length or both.

Configuring DNS Parameters

Use the following commands to configure static DNS-related settings.
Specify the primary DNS server:
config:#network dns firstServer <ip address>

Specify the secondary DNS server:
config:#network dns secondServer <ip address>

Specify the third DNS server:
config:#network dns thirdServer <ip address>

Specify one or multiple optional DNS search suffixes:
config:#-- OR --

506

network dns searchSuffixes <suffix1>

Chapter 9: Using the Command Line Interface

config:#network dns searchSuffixes <suffix1>,<suffix2>,<suffix3>,...,<suffix6>

Determine which IP address is used when the DNS server returns both
IPv4 and IPv6 addresses:
config:#network dns resolverPreference <resolver>

Variables:•••<ip address> is the IP address of the DNS server.
<suffix1>, <suffix2>, and the like are the DNS suffixes that automatically
apply when searching for any device via PX3. For example, <suffix1> can be
raritan.com, and <suffix2> can be legrand.com. You can specify up to 6
suffixes by separating them with commas.
<resolver> is one of the options: preferV4 or preferV6.
OptionDescription

preferV4

Use the IPv4 addresses returned by the DNS server.

preferV6

Use the IPv6 addresses returned by the DNS server.

Setting LAN Interface Parameters

A LAN interface configuration command begins with network ethernet.
Enabling or Disabling the LAN Interface

This command enables or disables the LAN interface.
config:#network ethernet <ETH> enabled <option>

Variables:•<ETH> is one of the options -- eth1 or eth2.
OptionDescription

eth1

ETH1 port

eth2

ETH2 port

507

Chapter 9: Using the Command Line Interface•<option> is one of the options: true or false.
OptionDescriptiontrue

The specified network interface is enabled.

false

The specified network interface is disabled.

Changing the LAN Interface Speed

This command determines the LAN interface speed.
config:#network ethernet <ETH> speed <option>

Variables:
•

•

508

<ETH> is one of the options -- eth1 or eth2.
OptionDescription

eth1

ETH1 port

eth2

ETH2 port<option> is one of the options: auto, 10Mbps, 100Mbps or 1000Mbps.
OptionDescription

auto

System determines the optimum LAN speed throughauto-negotiation.

10MbpsThe LAN speed is always 10 Mbps.

100Mbps

The LAN speed is always 100 Mbps.

1000Mbps

The LAN speed is always 1000 Mbps.

Chapter 9: Using the Command Line Interface

Changing the LAN Duplex Mode

This command determines the LAN interface duplex mode.
config:#network ethernet <ETH> duplexMode <mode>

Variables:••<ETH> is one of the options -- eth1 or eth2.
OptionDescription

eth1

ETH1 port

eth2

ETH2 port<mode> is one of the modes: auto, half or full.
OptionDescription

auto

The PX3 selects the optimum transmission modethrough auto-negotiation.

half

Half duplex:
Data is transmitted in one direction (to or from thePX3) at a time.

full

Full duplex:
Data is transmitted in both directions simultaneously.

Setting the Ethernet Authentication Method

This command sets the authentication method for the selected Ethernet
interface to either none or Extensible Authentication Protocol (EAP).
config:#network ethernet <ETH> authMethod <method>

Variables:•<ETH> is one of the options -- eth1 or eth2.
OptionDescription

eth1

ETH1 port

eth2

ETH2 port

509

Chapter 9: Using the Command Line Interface•<method> is one of the authentication methods: NONE or EAP.
MethodDescription

NONE

The authentication method is set to NONE.

EAPThe authentication method is set to EAP.

Setting Ethernet EAP Parameters

When the selected Ethernet interface's authentication method is set to EAP,
you must configure EAP authentication parameters, including outer
authentication, inner authentication, EAP identity, client certificate, client
private key, password, CA certificate, and RADIUS authentication server. For
more information, see Ethernet Interface Settings (on page 257).
Determine the outer authentication protocol:
config:#network ethernet <ETH> eapOuterAuthentication <outer_auth>
Determine the inner authentication protocol for authentication set to"EAP + PEAP":

510

Chapter 9: Using the Command Line Interface

config:#network ethernet <ETH> eapInnerAuthentication <inner_auth>Set the EAP identity:
config:#network ethernet <ETH> eapIdentity <identity>

Set the EAP password:
config:#network ethernet <ETH> eapPassword

After performing the above command, the PX3 prompts you to enter the
password. Then type the password and press Enter.
Provide a client certificate for authentication set to "EAP + TLS" or "EAP +PEAP + TLS":
config:#network ethernet <ETH> eapClientCertificate

After performing any certificate or private key commands, including commands
for the client certificate, client private key, and CA certificate, the systemprompts you to enter the contents of the wanted certificate or key. For an
example with detailed procedure, see EAP CA Certificate Example (on page
513).
Provide a client private key for authentication set to "EAP + TLS" or "EAP+ PEAP + TLS":
config:#network ethernet <ETH> eapClientPrivateKey

Provide a CA TLS certificate for EAP:
config:#network ethernet <ETH> eapCACertificate

Eable or disable verification of the TLS certificate chain:config:#network ethernet <ETH> enableCertVerification <option1>
Allow expired and not yet valid TLS certificates:

config:#network ethernet <ETH> allowOffTimeRangeCerts <option2>
Allow network connection with incorrect system time:511

Chapter 9: Using the Command Line Interface

config:#network ethernet <ETH> allowConnectionWithIncorrectClock<option3>
Set the RADIUS authentication server for EAP:
config:#network ethernet <ETH> eapAuthServerName <FQDN>

Variables:
•

•

•

•
•

512

<ETH> is one of the options -- eth1 or eth2.
OptionDescription

eth1

ETH1 port

eth2

ETH2 port<outer_auth> is one of the options: PEAP or TLS.
OptionDescription

PEAP

Outer authentication is set to Protected Extensible
Authentication Protocol (PEAP).

TLS

Outer authentication is set to TLS.

<inner_auth> is one of the options: MS-CHAPv2 or TLS.
OptionDescription

MSCHAPv2

Inner authentication is set to Microsoft's Challenge
Authentication Protocol Version 2 (MS-CHAPv2).

TLS

Inner authentication is set to TLS.

<identity> is your user name for the EAP authentication.
<option1> is one of the options: true or false.
OptionDescription

true

Enables the verification of the TLS certificate chain.

false

Disables the verification of the TLS certificate chain.

Chapter 9: Using the Command Line Interface

•

•

•

<option2> is one of the options: true or false.
OptionDescription

true

Always make the network connection successful eventhough the TLS certificate chain contains any certificate
which is outdated or not valid yet.

false

The network connection is NOT successfully establishedwhen the TLS certificate chain contains any certificate
which is outdated or not valid yet.

<option3> is one of the options: true or false.
OptionDescription

true

Make the network connection successful when the PX3
system time is earlier than the firmware build before
synchronizing with the NTP server, causing the TLS
certificate to become invalid.

false

The network connection is NOT successfully establishedwhen the PX3 finds that the TLS certificate is not valid
due to incorrect system time.

<FQDN> is the name of the RADIUS server if it is present in the TLS
certificate. The name must match the fully qualified domain name (FQDN)of the host shown in the certificate.

EAP CA Certificate Example
This section provides a CA certificate example for the Ethernet interface "ETH1".
Your CA certificate contents should be different from the contents displayed inthis example.
In addition, the procedure of uploading the client certificate and client private
key in CLI is similar to the following example, except for the CLI command.
To provide a CA certificate:
1.

Make sure you have entered the configuration mode. See Entering
Configuration Mode (on page 493).

2.

Type the following command for ETH1 and press Enter.
config:#3.

network ethernet eth1 eapCACertificate

The system prompts you to enter the contents of the CA certificate.

513

Chapter 9: Using the Command Line Interface

4.

Open a CA certificate using a text editor. You should see certificate
contents similar to the following.

5.

Select and copy the contents as illustrated below, including the starting
line containing "BEGIN CERTIFICATE" and the ending line containing "ENDCERTIFICATE."

6.

Paste the contents in the terminal.

7.

Press Enter.

8.

Verify whether the system shows the following command prompt,
indicating the provided CA certificate is valid.
config:#Removing the Uploaded Certificate or Private Key
The procedures of removing an existing client certificate, client private key or
CA certificate in CLI are similar.
This section illustrates such a procedure for the Ethernet interface "ETH1."
To remove a certificate or private key for ETH1:
1.

Make sure you have entered the configuration mode. See Entering
Configuration Mode (on page 493).

2.

Type the appropriate command, depending on which file you want toremove, and press Enter.
▪

Client certificate:config:#▪

Client private key:
config:#514

network ethernet eth1 eapClientCertificate

network ethernet eth1 eapClientPrivateKey

Chapter 9: Using the Command Line Interface▪

CA certificate:config:#network ethernet eth1 eapCACertificate

3.

The system prompts you to enter the contents of the chosen certificate or
private key.

4.

Press Enter without typing any data.

5.

Verify whether the system shows the following command prompt,
indicating the existing certificate or private key has been removed.
config:#Setting Wireless Parameters

You must configure wireless parameters, including Service Set Identifier (SSID),
authentication method, Pre-Shared Key (PSK), and Basic Service Set Identifier(BSSID) after the wireless networking mode is enabled.
A wireless configuration command begins with network wireless.
Note: If wireless networking mode is not enabled, the SSID, PSK and BSSID
values are not applied until the wireless networking mode is enabled. In
addition, a message appears, indicating that the active network interface is not
wireless.

Setting the SSID

This command specifies the SSID string.
config:#network wireless SSID <ssid>

Variables:•<ssid> is the name of the wireless access point, which consists of:- Up to 32 ASCII characters- No spaces- ASCII codes 0x20 ~ 0x7E

515

Chapter 9: Using the Command Line Interface

Enabling or Disabling 802.11n High Throughput

This command enables or disables the 802.11n high throughput protocol.
config:#network wireless enableHT <option>

Variables:•<option> is one of the options: true or false.
OptionDescriptiontrue

802.11n is enabled.

false

802.11n is disabled.

Setting the Wireless Authentication Method

This command sets the wireless authentication method to either PSK or
Extensible Authentication Protocol (EAP).
config:#network wireless authMethod <method>

Variables:•<method> is one of the authentication methods: PSK or EAP.
MethodDescription

PSK

The authentication method is set to PSK.

EAPThe authentication method is set to EAP.

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 <psk>

Variables:•<psk> is a string or passphrase that consists of:- 8 to 63 characters- No spaces- ASCII codes 0x20 ~ 0x7E

516

Chapter 9: Using the Command Line Interface

Setting Wireless EAP Parameters

When the wireless authentication method is set to EAP, you must configure
EAP authentication parameters, including outer authentication, innerauthentication, EAP identity, client certificate, client private key, password, CA
certificate, and RADIUS authentication server. For more information, see
Wireless Network Settings (on page 260).
Determine the outer authentication protocol:
config:#network wireless eapOuterAuthentication <outer_auth>

Determine the inner authentication protocol for authentication set to"EAP + PEAP":
config:#network wireless eapInnerAuthentication <inner_auth>Set the EAP identity:
config:#network wireless eapIdentity <identity>

Set the EAP password:
config:#network wireless eapPassword

After performing the above command, the PX3 prompts you to enter the
password. Then type the password and press Enter.
Provide a Client Certificate for authentication set to "EAP + TLS" or "EAP+ PEAP + TLS":
config:#network wireless eapClientCertificate

After performing any certificate or private key commands, including commands
for the client certificate, client private key, and CA certificate, the systemprompts you to enter the contents of the wanted certificate or key. For an
example with detailed procedure, see EAP CA Certificate Example (on page
513).
Provide a Client Private Key for authentication set to "EAP + TLS" or "EAP+ PEAP + TLS":
config:#network wireless eapClientPrivateKey

Provide a CA TLS certificate for EAP:
config:#network wireless eapCACertificate

Eable or disable verification of the TLS certificate chain:config:#network wireless enableCertVerification <option1>

517

Chapter 9: Using the Command Line Interface

Allow expired and not yet valid TLS certificates:
config:#network wireless allowOffTimeRangeCerts <option2>

Allow wireless network connection with incorrect system time:
config:#network wireless allowConnectionWithIncorrectClock <option3>
Set the RADIUS authentication server for EAP:
config:#network wireless eapAuthServerName <FQDN>

Variables:
•

•

•
•

•

518

<outer_auth> is one of the options: PEAP or TLS.
OptionDescription

PEAP

Outer authentication is set to Protected Extensible
Authentication Protocol (PEAP).

TLS

Outer authentication is set to TLS.

<inner_auth> is one of the options: MS-CHAPv2 or TLS.
OptionDescription

MSCHAPv2

Inner authentication is set to Microsoft's Challenge
Authentication Protocol Version 2 (MS-CHAPv2).

TLS

Inner authentication is set to TLS.

<identity> is your user name for the EAP authentication.
<option1> is one of the options: true or false.
OptionDescription

true

Enables the verification of the TLS certificate chain.

false

Disables the verification of the TLS certificate chain.

<option2> is one of the options: true or false.
OptionDescription

true

Always make the network connection successful eventhough the TLS certificate chain contains any certificate
which is outdated or not valid yet.

Chapter 9: Using the Command Line Interface••

OptionDescription

false

The network connection is NOT successfully establishedwhen the TLS certificate chain contains any certificate
which is outdated or not valid yet.

<option3> is one of the options: true or false.
OptionDescription

true

Make the network connection successful when the PX3
system time is earlier than the firmware build before
synchronizing with the NTP server, causing the TLS
certificate to become invalid.

false

The network connection is NOT successfully establishedwhen the PX3 finds that the TLS certificate is not valid
due to incorrect system time.

<FQDN> is the name of the RADIUS server if it is present in the TLS
certificate. The name must match the fully qualified domain name (FQDN)of the host shown in the certificate.

Setting the BSSID

This command specifies the BSSID.
config:#network wireless BSSID <bssid>

Variables:•<bssid> 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 <mode> enabled <option1>

Variables:•<mode> is one of the following cascading modes.
Mode

Description

bridgeThe Bridging mode, where each cascaded
device is assigned a unique IP address.

519

Chapter 9: Using the Command Line Interface

Mode

Description

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 theother cascading mode is disabled, or the preferred cascading mode may not
be enabled successfully.
•<option1> is one of the following options:
OptionDescriptiontrue

The selected cascading mode is enabled.

false

The selected cascading mode is disabled.

If Port Forwarding mode is enabled, you must configure two moresettings to finish the configuration:
On ALL cascaded devices, you must configure the 'role' setting one by one.
config:#network portForwarding role <option2>

On the master device, you must configure the 'downstream interface' setting.
config:#network portForwarding
masterDownstreamInterface <option3>

Variables:
•

•

520

<option2> is one of the following cascading roles:
Role

Description

master

The device is a master device.

slave

The device is a slave device.

<option3> is one of the following options:
OptionDescription

ETH1/ETH2

ETH1/ETH2 port is the port where the 1st slave
device is connected.

Usb

USB port is the port where the 1st slave device
is connected.

Chapter 9: Using the Command Line Interface

Setting Network Service Parameters

A network service command begins with network services.
Setting the HTTP PortThe commands used to configure the HTTP port settings begin with network
services http.
Change the HTTP port:
config:#network services http port <n>Enable or disable the HTTP port:
config:#network services http enabled <option>

Enforce redirection from HTTP to HTTPS:
config:#network services http enforceHttps <option>

Variables:••<n> is a TCP port number between 1 and 65535. The default HTTP port is
80.
<option> is one of the options: true or false.
OptionDescription

true▪ The HTTP port is enabled.
- OR ▪ HTTP redirection to HTTPS is enabled.

false▪ The HTTP port is disabled.
- OR ▪ HTTP redirection to HTTPS is disabled.

521

Chapter 9: Using the Command Line Interface

Setting the HTTPS PortThe commands used to configure the HTTPS port settings begin with network
services https.
Change the HTTPS port:
config:#network services https port <n>Enable or disable the HTTPS access:config:#network services https enabled <option>

Variables:••<n> is a TCP port number between 1 and 65535. The default HTTPS port is443.
<option> is one of the options: true or false.
OptionDescription

true

Forces any access to the PX3 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 <option>

Variables:•

522<option> is one of the options: true or false.
OptionDescription

true

The Telnet service is enabled.

Chapter 9: Using the Command Line Interface

OptionDescription

false

The Telnet service is disabled.

Changing the Telnet PortThis command changes the Telnet port.
config:#network services telnet port <n>Variables:•<n> is a TCP port number between 1 and 65535. The default Telnet port is23.

Changing the SSH Configuration

You can enable or disable the SSH service, or change its TCP port using the CLI
commands.
An SSH command begins with network services ssh.
Enabling or Disabling SSH
This command enables or disables the SSH service.
config:#network services ssh enabled <option>

Variables:•<option> is one of the options: true or false.
OptionDescription

true

The SSH service is enabled.

false

The SSH service is disabled.

Changing the SSH PortThis command changes the SSH port.
config:#network services ssh port <n>Variables:•<n> is a TCP port number between 1 and 65535. The default SSH port is 22.

523

Chapter 9: Using the Command Line Interface

Determining the SSH Authentication Method
This command syntax determines the SSH authentication method.
config:#network services ssh authentication <auth_method>

Variables:•<option> is one of the options: passwordOnly, publicKeyOnly or
passwordOrPublicKey.
OptionDescription

passwordOnly

Enables the password-based login only.

publicKeyOnly

Enables the public key-based login only.

passwordOrPublicKey

Enables both the password- and public
key-based login. This is the default.

If the public key authentication is selected, you must enter a valid SSH public
key for each user profile to log in over the SSH connection. See Specifying the
SSH Public Key (on page 564).
Setting the SNMP Configuration

You can enable or disable the SNMP v1/v2c or v3 agent, configure the read andwrite 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 <option>

Variables:•

524<option> is one of the options: enable or disable.
OptionDescription

enableThe SNMP v1/v2c protocol is enabled.

disableThe SNMP v1/v2c protocol is disabled.

Chapter 9: Using the Command Line Interface

Enabling or Disabling SNMP v3
This command enables or disables the SNMP v3 protocol.
config:#network services snmp v3 <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableThe SNMP v3 protocol is enabled.

disableThe SNMP v3 protocol is disabled.

Setting the SNMP Read Community
This command sets the SNMP read-only community string.
config:#network services snmp readCommunity <string>

Variables:••<string> is a string comprising 4 to 64 ASCII printable characters.
The string CANNOT include spaces.

Setting the SNMP Write Community
This command sets the SNMP read/write community string.
config:#network services snmp writeCommunity <string>

Variables:••<string> is a string comprising 4 to 64 ASCII printable characters.
The string CANNOT include spaces.

Setting the sysContact Value
This command sets the SNMP MIB-II sysContact value.
config:#network services snmp sysContact <value>

Variables:•<value> is a string comprising 0 to 255 alphanumeric characters.

525

Chapter 9: Using the Command Line Interface

Setting the sysName Value
This command sets the SNMP MIB-II sysName value.
config:#network services snmp sysName <value>

Variables:•<value> is a string comprising 0 to 255 alphanumeric characters.

Setting the sysLocation Value
This command sets the SNMP MIB-II sysLocation value.
config:#network services snmp sysLocation <value>

Variables:<value> is a string comprising 0 to 255 alphanumeric characters.
Changing the Modbus Configuration

You can enable or disable the Modbus agent, configure its read-only capability,or change its TCP port.
A Modbus command begins with network services modbus.
Enabling or Disabling Modbus
This command enables or disables the Modbus protocol.
config:#network services modbus enabled <option>

Variables:•

526<option> is one of the options: true or false.
OptionDescription

true

The Modbus agent is enabled.

false

The Modbus agent is disabled.

Chapter 9: Using the Command Line Interface

Enabling or Disabling the Read-Only Mode
This command enables or disables the read-only mode for the Modbus agent.
config:#network services modbus readonly <option>

Variables:•<option> is one of the options: true or false.
OptionDescription

true

The read-only mode is enabled.

false

The read-only mode is disabled.

Changing the Modbus PortThis command changes the Modbus port.
config:#network services modbus port <n>Variables:•<n> is a TCP port number between 1 and 65535. The default Modbus port
is 502.

Enabling or Disabling Service AdvertisingThis command enables or disables the zero configuration protocol, whichenables advertising or auto discovery of network services. See Enabling Service
Advertising (on page 288) for details.
config:#network services zeroconfig <method> <option>

Variables:•<method> is one of the options: mdns or llmnr.
OptionDescription

mdns

Service advertisement via MDNS is enabled or
disabled.

llmnr

Service advertisement via LLMNR is enabled or
disabled.

527

Chapter 9: Using the Command Line Interface•<option> is one of the options: enable or disable.
OptionDescription

enableService advertisement via the selected method (MDNSor LLMNR) is enabled.

disableService advertisement via the selected method (MDNSor LLMNR) is disabled.

ExamplesThis section illustrates several network configuration examples.
Example 1 - Wireless Networking Mode

The following command enables the wireless networking mode.
config:#network wireless enabled true

Example 2 - Enabling IPv6 Protocol on the Ethernet Interface

The following command enables the IPv6 protocol on the ETH1 interface.
config:#network ipv6 interface eth1 enabled true

Example 3 - Wireless Authentication Method

The following command sets the wireless authentication method to PSK.
config:#network wireless authMethod PSKExample 4 - Static IPv4 Configuration

The following command enables the Static IPv4 configuration mode on the
ETH1 interface.
config:#network ipv4 interface eth1 configMethod staticTime Configuration Commands
A time configuration command begins with time.

528

Chapter 9: Using the Command Line Interface

Determining the Time Setup Method

This command determines the method to configure the system date and time.
config:#time method <method>

Variables:•<method> is one of the time setup options: manual or ntp.
Mode

Description

manualThe date and time settings are customized.

ntp

The date and time settings synchronize with a
specified NTP server.

529

Chapter 9: Using the Command Line Interface

Setting NTP Parameters

A time configuration command for NTP-related parameters begins with time
ntp.
Specify the primary time server:
config:#time ntp firstServer <first_server>

Specify the secondary time server:
config:#time ntp secondServer <second_server>

To delete the primary time server:
config:#time ntp firstServer ""To delete the secondary time server:
config:#time ntp secondServer ""Variables:
•
•

530

The <first_server> is the IP address or host name of the primary NTP
server.
The <second_server> is the IP address or host name of the secondary NTP
server.

Chapter 9: Using the Command Line Interface

Customizing the Date and TimeTo manually configure the date and time, use the following CLI commands tospecify them.
Note: You shall set the time configuration method to "manual" prior tocustomizing the date and time. See Determining the Time Setup Method (onpage 529).
Assign the date:config:#time set date <yyyy-mm-dd>

Assign the time:
config:#time set time <hh:mm:ss>

Variables:
Variable

Description<yyyy-mm-dd>

Type the date in the format of yyyy-mm-dd.
For example, type 2015-11-30 for November 30,
2015.
Type the time in the format of hh:mm:ss in the
24-hour format.

<hh:mm:ss>

For example, type 13:50:20 for 1:50:20 pm.
Setting the Time Zone

The CLI has a list of time zones to configure the date and time for PX3.
config:#time zone

After a list of time zones is displayed, type the index number of the time zone
or press Enter to cancel.
ExampleTo set the time zone:
1.

Type the time zone command as shown below and press Enter.
config:#2.

time zone

The system shows a list of time zones. Type the index number of thedesired time zone and press Enter.

531

Chapter 9: Using the Command Line Interface

3.

Type apply for the selected time zone to take effect.

Setting the Automatic Daylight Savings Time

This command determines whether the daylight saving time is applied to thetime settings.
config:#time autoDST <option>

Variables:•<option> is one of the options: enable or disable.
Mode

Description

enableDaylight savings time is enabled.

disableDaylight savings time is disabled.

ExamplesThis 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:#532

time ntp firstServer 192.168.80.66

Chapter 9: Using the Command Line Interface

Checking the Accessibility of NTP Servers
This command verifies the accessibility of NTP servers specified manually on
your PX3 and then shows the result. For instructions on specifying NTP servers
via CLI, see Setting NTP Parameters (on page 530).
To perform this command successfully, you must:••

Own the "Change Date/Time Settings" permission.
Customize NTP servers. See Setting NTP Parameters (on page 530).

This command is available either in the administrator/user mode or in theconfiguration mode. See Different CLI Modes and Prompts (on page 459).
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 PX3 from a specific ora range of IP addresses.
••

An IPv4 firewall configuration command begins with security
ipAccessControl ipv4.
An IPv6 firewall configuration command begins with security
ipAccessControl ipv6.

Modifying Firewall Control Parameters

There are different commands for modifying firewall control parameters.
•

IPv4 commands
Enable or disable the IPv4 firewall control feature:

config:#security ipAccessControl ipv4 enabled <option>

Determine the default IPv4 firewall control policy for inbound traffic:

533

Chapter 9: Using the Command Line Interface

config:#security ipAccessControl ipv4 defaultPolicyIn <policy>

Determine the default IPv4 firewall control policy for outbound traffic:
config:#security ipAccessControl ipv4 defaultPolicyOut <policy>•

IPv6 commands
Enable or disable the IPv6 firewall control feature:

config:#security ipAccessControl ipv6 enabled <option>

Determine the default IPv6 firewall control policy for inbound traffic:
config:#security ipAccessControl ipv6 defaultPolicyIn <policy>

Determine the default IPv6 firewall control policy for outbound traffic:
config:#security ipAccessControl ipv6 defaultPolicyOut <policy>

Variables:
•

•

534

<option> is one of the options: true or false.
OptionDescription

true

Enables the IP access control feature.

false

Disables the IP access control feature.

<policy> is one of the options: accept, drop or reject.
OptionDescription

acceptAccepts traffic from all IP addresses.

drop

Discards traffic from all IP addresses, without sending
any failure notification to the source host.

rejectDiscards traffic from all IP addresses, and an ICMP
message is sent to the source host for failure
notification.

Chapter 9: Using the Command Line Interface

Tip: You can combine both commands to modify all firewall control parametersat a time. See Multi-Command Syntax (on page 615).
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, thecommand for adding a rule varies.
•

IPv4 commands
Add a new rule to the bottom of the IPv4 rules list:

config:#security ipAccessControl ipv4 rule add <direction> <ip_mask> <policy>

Add a new IPv4 rule by inserting it above or below a specific rule:config:#security ipAccessControl ipv4 rule add <direction> <ip_mask> <policy> <insert><rule_number>-- OR --

config:#security ipAccessControl ipv4 rule add <direction> <insert> <rule_number><ip_mask> <policy>•

IPv6 commands
Add a new rule to the bottom of the IPv6 rules list:

config:#security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy>

Add a new IPv6 rule by inserting it above or below a specific rule:535

Chapter 9: Using the Command Line Interface

config:#security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy> <insert><rule_number>-- OR --

config:#security ipAccessControl ipv6 rule add <direction> <insert> <rule_number><ip_mask> <policy>

Variables:
•

•

•

•

<direction> is one of the options: in or out.
Direction

Descriptionin

Inbound traffic.

outOutbound traffic.

<ip_mask> is the combination of the IP address and subnet mask values (orprefix length), which are separated with a slash. For example, an IPv4
combination looks like this: 192.168.94.222/24.
<policy> is one of the options: accept, drop or reject.
PolicyDescription

acceptAccepts traffic from/to the specified IP address(es).

dropDiscards traffic from/to the specified IP address(es),without sending any failure notification to the sourceor destination host.

rejectDiscards traffic from/to the specified IP address(es),and an ICMP message is sent to the source ordestination host for failure notification.

<insert> is one of the options: insertAbove or insertBelow.
OptionDescription

insertAbove

Inserts the new rule above the specified rule number.
Then:
new rule's number = the specified rule number

insertBelow

Inserts the new rule below the specified rule number.
Then:
new rule's number = the specified rule number + 1•

536<rule_number> is the number of the existing rule which you want to insert
the new rule above or below.

Chapter 9: Using the Command Line Interface

Modifying a Firewall Rule
Depending on what to modify in an existing rule, the command varies.
•

IPv4 commands
Modify an IPv4 rule's IP address and/or subnet mask:

config:#security ipAccessControl ipv4 rule modify <direction> <rule_number> ipMask<ip_mask>

Modify an IPv4 rule's policy:
config:#security ipAccessControl ipv4 rule modify <direction> <rule_number> policy<policy>

Modify all contents of an existing IPv4 rule:config:#security ipAccessControl ipv4 rule modify <direction> <rule_number> ipMask<ip_mask> policy <policy>•

IPv6 commands
Modify an IPv6 rule's IP address and/or prefix length:

config:#security ipAccessControl ipv6 rule modify <direction> <rule_number> ipMask<ip_mask>

Modify an IPv6 rule's policy:
config:#security ipAccessControl ipv6 rule modify <direction> <rule_number> policy<policy>

Modify all contents of an IPv6 existing rule:config:#security ipAccessControl ipv6 rule modify <direction> <rule_number> ipMask<ip_mask> policy <policy>

Variables:•<direction> is one of the options: in or out.
Direction

Descriptionin

Inbound traffic.

537

Chapter 9: Using the Command Line Interface•••

Direction

DescriptionoutOutbound traffic.

<rule_number> is the number of the existing rule that you want to modify.
<ip_mask> is the combination of the IP address and subnet mask values (orprefix length), which are separated with a slash. For example, an IPv4
combination looks like this: 192.168.94.222/24.
<policy> is one of the options: accept, drop or reject.
OptionDescription

acceptAccepts traffic from/to the specified IP address(es).

dropDiscards traffic from/to the specified IP address(es),without sending any failure notification to the sourceor destination host.

rejectDiscards traffic from/to the specified IP address(es),and an ICMP message is sent to the source ordestination host for failure notification.

Deleting a Firewall Rule
The following commands remove a specific IPv4 or IPv6 rule from the list.
IPv4 commands
config:#security ipAccessControl ipv4 rule delete <direction> <rule_number>

IPv6 commands
config:#security ipAccessControl ipv6 rule delete <direction> <rule_number>

Variables:
•

•

538

<direction> is one of the options: in or out.
Direction

Descriptionin

Inbound traffic.

outOutbound traffic.

<rule_number> is the number of the existing rule that you want toremove.

Chapter 9: Using the Command Line Interface

Restricted Service Agreement

The CLI command used to set the Restricted Service Agreement feature begins
with security restrictedServiceAgreement,
Enabling or Disabling the Restricted Service Agreement

This command activates or deactivates the Restricted Service Agreement.
config:#security restrictedServiceAgreement enabled <option>

Variables:•<option> is one of the options: true or false.
OptionDescription

true

Enables the Restricted Service Agreement feature.

false

Disables the Restricted Service Agreement feature.

539

Chapter 9: Using the Command Line Interface

After the Restricted Service Agreement feature is enabled, the agreement's
content is displayed on the login screen.

Do either of the following, or the login fails:•

In the web interface, select the checkbox labeled "I understand and accept
the restricted service agreement."
Tip: To select the agreement checkbox using the keyboard, first press Tab
to go to the checkbox and then Enter.

•540

In the CLI, type y when the confirmation message "I understand andaccept the restricted service agreement" is displayed.

Chapter 9: Using the Command Line Interface

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 aftertyping the apply command. See Quitting Configuration Mode (on page 494).
ExampleThe 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 the PX3. If you are not
the system administrator, do NOT operate it or change
any settings without the permission of the systemadministrator.

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.

541

Chapter 9: Using the Command Line Interface

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

Single Login Limitation

This command enables or disables the single login feature, which controls
whether multiple logins using the same login name simultaneously ispermitted.
config:#security loginLimits singleLogin <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableEnables the single login feature.

disableDisables the single login feature.

Password Aging

This command enables or disables the password aging feature, which controls
whether the password should be changed at a regular interval:
config:#security loginLimits passwordAging <option>

Variables:•542<option> is one of the options: enable or disable.
OptionDescription

enableEnables the password aging feature.

disableDisables the password aging feature.

Chapter 9: Using the Command Line Interface

Password Aging IntervalThis command determines how often the password should be changed.
config:#security loginLimits passwordAgingInterval <value>

Variables:•<value> is a numeric value in days set for the password aging interval. Theinterval ranges from 7 to 365 days.

Idle Timeout

This command determines how long a user can remain idle before that user isforced to log out of the PX3 web interface or CLI.
config:#security loginLimits idleTimeout <value>

Variables:•<value> is a numeric value in minutes set for the idle timeout. The timeout
ranges from 1 to 1440 minutes (24 hours).

User Blocking

There are different commands for changing different user blocking parameters.
These commands begin with security userBlocking.
You can combine multiple commands to modify the user blocking parametersat a time. See Multi-Command Syntax (on page 615).
Determine the maximum number of failed logins before blocking a user:
config:#security userBlocking maximumNumberOfFailedLogins <value1>

Determine how long a user is blocked:
config:#security userBlocking blockTime <value2>

Variables:••<value1> is an integer between 3 and 10, or unlimited, which sets no limiton the maximum number of failed logins and thus disables the user
blocking function.
<value2> is a numeric value ranging from 1 to 1440 minutes (one day), or
infinite, which blocks the user all the time until the user is unblocked
manually.

543

Chapter 9: Using the Command Line Interface

Strong Passwords

The strong password commands determine whether a strong password isrequired 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 615).

Enabling or Disabling Strong Passwords

This command enables or disables the strong password feature.
config:#security strongPasswords enabled <option>

Variables:•<option> is one of the options: true or false.
OptionDescription

true

Enables the strong password feature.

false

Disables the strong password feature.

Minimum Password Length

This command determines the minimum length of the password.
config:#security strongPasswords minimumLength <value>

Variables:•<value> is an integer between 8 and 32.

Maximum Password Length

This command determines the maximum length of the password.
config:#security strongPasswords maximumLength <value>

Variables:•<value> is an integer between 16 and 64.

Lowercase Character Requirement

This command determines whether a strong password includes at least alowercase character.

544

Chapter 9: Using the Command Line Interface

config:#security strongPasswords enforceAtLeastOneLowerCaseCharacter <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableAt least one lowercase character is required.

disableNo lowercase character is required.

Uppercase Character Requirement

This command determines whether a strong password includes at least a
uppercase character.
config:#security strongPasswords enforceAtLeastOneUpperCaseCharacter <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableAt least one uppercase character is required.

disableNo uppercase character is required.

Numeric Character Requirement

This command determines whether a strong password includes at least anumeric character.
config:#security strongPasswords enforceAtLeastOneNumericCharacter <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableAt least one numeric character is required.

disableNo numeric character is required.

545

Chapter 9: Using the Command Line Interface

Special Character Requirement

This command determines whether a strong password includes at least a
special character.
config:#security strongPasswords enforceAtLeastOneSpecialCharacter <option>

Variables:•<option> is one of the options: enable or disable.
OptionDescription

enableAt least one special character is required.

disableNo special character is required.

Maximum Password History

This command determines the number of previous passwords that CANNOT be
repeated when changing the password.
config:#security strongPasswords passwordHistoryDepth <value>

Variables:•<value> is an integer between 1 and 12.

Role-Based Access Control

In addition to firewall access control based on IP addresses, you can configure
other access control 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:546

Chapter 9: Using the Command Line Interface

config:#security roleBasedAccessControl ipv4 enabled <option>

Determine the IPv4 role-based access control policy:
config:#security roleBasedAccessControl ipv4 defaultPolicy <policy>•

IPv6 commands
Enable or disable the IPv6 role-based access control feature:

config:#security roleBasedAccessControl ipv6 enabled <option>

Determine the IPv6 role-based access control policy:
config:#security roleBasedAccessControl ipv6 defaultPolicy <policy>

Variables:••<option> is one of the options: true or false.
OptionDescription

true

Enables the role-based access control feature.

false

Disables the role-based access control feature.

<policy> is one of the options: allow or deny.
PolicyDescription

allow

Accepts traffic from all IP addresses regardless of theuser's role.

deny

Drops traffic from all IP addresses regardless of theuser'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 615).

547

Chapter 9: Using the Command Line Interface

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 <start_ip> <end_ip> <role><policy>

Add a new IPv4 rule by inserting it above or below a specific rule:config:#security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip> <role><policy> <insert> <rule_number>•

IPv6 commands
Add a new rule to the bottom of the IPv6 rules list:

config:#security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role><policy>

Add a new IPv6 rule by inserting it above or below a specific rule:548

Chapter 9: Using the Command Line Interface

config:#security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role><policy> <insert> <rule_number>

Variables:
•
•
•
•

•

<start_ip> is the starting IP address.
<end_ip> is the ending IP address.
<role> is the role for which you want to create an access control rule.
<policy> is one of the options: allow or deny.
PolicyDescription

allow

Accepts traffic from the specified IP address range
when the user is a member of the specified roledeny

Drops traffic from the specified IP address range when
the user is a member of the specified role<insert> is one of the options: insertAbove or insertBelow.
OptionDescription

insertAbove

Inserts the new rule above the specified rule number.
Then:
new rule's number = the specified rule number

insertBelow

Inserts the new rule below the specified rule number.
Then:
new rule's number = the specified rule number + 1•<rule_number> is the number of the existing rule which you want to insert
the new rule above or below.

Modifying a Role-Based Access Control Rule
Depending on what to modify in an existing rule, the command syntax varies.
•

IPv4 commands
Modify a rule's IPv4 address range:

config:#security roleBasedAccessControl ipv4 rule modify <rule_number>startIpAddress <start_ip> endIpAddress <end_ip>

Modify an IPv4 rule's role:549

Chapter 9: Using the Command Line Interface

config:#security roleBasedAccessControl ipv4 rule modify <rule_number> role <role>

Modify an IPv4 rule's policy:
config:#security roleBasedAccessControl ipv4 rule modify <rule_number> policy<policy>

Modify all contents of an existing IPv4 rule:config:#security roleBasedAccessControl ipv4 rule modify <rule_number>startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy>•

IPv6 commands
Modify a rule's IPv6 address range:

config:#security roleBasedAccessControl ipv6 rule modify <rule_number>startIpAddress <start_ip> endIpAddress <end_ip>

Modify an IPv6 rule's role:
config:#security roleBasedAccessControl ipv6 rule modify <rule_number> role <role>

Modify an IPv6 rule's policy:
config:#security roleBasedAccessControl ipv6 rule modify <rule_number> policy<policy>

Modify all contents of an existing IPv6 rule:

550

Chapter 9: Using the Command Line Interface

config:#security roleBasedAccessControl ipv6 rule modify <rule_number>startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy>

Variables:
•
•
•
•
•

<rule_number> is the number of the existing rule that you want to modify.
<start_ip> is the starting IP address.
<end_ip> is the ending IP address.
<role> is one of the existing roles.
<policy> is one of the options: allow or deny.
PolicyDescription

allow

Accepts traffic from the specified IP address range
when the user is a member of the specified roledeny

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 <rule_number>

IPv6 commands
config:#security roleBasedAccessControl ipv6 rule delete <rule_number>

Variables:•<rule_number> is the number of the existing rule that you want toremove.

551

Chapter 9: Using the Command Line Interface

Enabling or Disabling Front Panel Actuator Control

The following CLI commands control whether you can turn on or off connected
actuator(s) by operating the front panel LCD display.
To enable the front panel actuator control feature:
config:#security frontPanelPermissions add switchActuator

To disable the front panel actuator control feature:
config:#security frontPanelPermissions remove switchActuator

Tip: If your PX3 supports multiple front panel permissions, you can combine
them into one command by adding a semicolon (;) between different
permissions. For example, the following CLI command enables both front panel
actuator control and the internal beeper-muting functions simultaneously.
security frontPanelPermissions add
switchActuator;muteBeeper
Enabling or Disabling Front Panel Beeper-Sound Control

The following CLI commands control whether you can mute the internal beeper
by operating the front panel LCD display when the beeper sounds.
To enable the front panel beeper sound control feature:
config:#security frontPanelPermissions add muteBeeper

To disable the front panel actuator control feature:
config:#security frontPanelPermissions remove muteBeeper

Tip: If your PX3 supports multiple front panel permissions, you can combine
them into one command by adding a semicolon (;) between different
permissions. For example, the following CLI command enables both front panel
actuator control and the the internal beeper-muting functions simultaneously.
security frontPanelPermissions add
switchActuator;muteBeeper
ExamplesThis section illustrates several security configuration examples.

552

Chapter 9: Using the Command Line Interface

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 in 192.168.84.123/24 accept
insertAbove 5

Results:••

A new IPv4 firewall control rule is added to accept all packets sent fromthe 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.

553

Chapter 9: Using the Command Line Interface

Example 4 - Adding an IPv4 Role-based Access Control Rule

The following command creates a newIPv4
specifies its location in the list.
config:#role-based access control rule andsecurity 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 newrule 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 <n> name "<name>"

Variables:••<n> is the number of the outlet that you want to configure.
<name> is a string comprising up to 64 ASCII printable characters. The<name> variable must be enclosed in quotes when it contains spaces.

Example - Outlet Naming

The following command assigns the name "Win XP" to outlet 8.
config:#outlet 8 name "Win XP"

Inlet Configuration Commands
An inlet configuration command begins with inlet. You can configure an inlet byusing the inlet configuration command.

554

Chapter 9: Using the Command Line Interface

Changing the Inlet Name

This command syntax names an inlet.
config:#inlet <n> name "<name>"

Variables:••<n> is the number of the inlet that you want to configure. For a single-inlet
PDU, <n> is always 1. The value is an integer between 1 and 50.
<name> is a string comprising up to 64 ASCII printable characters. The<name> variable must be enclosed in quotes when it contains spaces.

Enabling or Disabling an Inlet (for Multi-Inlet PDUs)

Enabling or disabling an inlet takes effect on a multi-inlet PDU only.
This command enables or disables an inlet.
config:#inlet <n> enabled <option>

Variables:••<n> is the number of the inlet that you want to configure. For a single-inlet
PDU, <n> is always 1. The value is an integer between 1 and 50.
<option> is one of the options: true or false.
OptionDescriptiontrue

The specified inlet is enabled.

false

The specified inlet is disabled.

Note: If performing this command causes all inlets to be disabled, a warning
message appears, prompting you to confirm. When this occurs, press y toconfirm or n to cancel the operation.
Example - Inlet Naming

The following command assigns the name "AC source" to the inlet 1. If yourPX3 contains multiple inlets, this command names the 1st inlet.
config:#inlet 1 name "AC source"555

Chapter 9: Using the Command Line Interface

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 yourPX3.
config:#ocp <n> name "<name>"

Variables:••<n> is the number of the overcurrent protector that you want to configure.
The value is an integer between 1 and 50.
<name> is a string comprising up to 64 ASCII printable characters. The<name> variable must be enclosed in quotes when it contains spaces.

Example - OCP Naming

The command assigns the name "Email servers CB" to the overcurrent
protector labeled 2.
config:#ocp 2 name "Email servers CB"

User Configuration Commands
Most user configuration commands begin with user except for the password
change command.

Creating a User Profile

This command creates a new user profile.
config:#user create <name> <option> <roles>

After performing the user creation command, the PX3 prompts you to assign apassword to the newly-created user. Then:

556

1.

Type the password and press Enter.

2.

Re-type the same password for confirmation and press Enter.

Chapter 9: Using the Command Line Interface

Variables:•••<name> is a string comprising up to 32 ASCII printable characters. The<name> variable CANNOT contain spaces.
<option> is one of the options: enable or disable.
OptionDescription

enableEnables the newly-created user profile.

disableDisables the newly-created user profile.

<roles> is a role or a list of comma-separated roles assigned to thespecified 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 615).

Changing a User's Password

This command allows you to change an existing user's password if you have theAdministrator Privileges.
config:#user modify <name> password

After performing the above command, PX3 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:•<name> is the name of the user whose settings you want to change.

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

557

Chapter 9: Using the Command Line Interface

2.

Type the following command to change the password for the user profile"May."
config:#user modify May password

3.

Type a new password when prompted, and press Enter.

4.

Type the same new password and press Enter.

5.

If the password change is completed successfully, the config:# prompt
appears.

Modifying a User's Personal Data

You can change a user's personal data, including the user's full name,telephone number, and email address.
Various commands can be combined to modify the parameters of a specificuser profile at a time. See Multi-Command Syntax (on page 615).
Change a user's full name:config:#user modify <name> fullName "<full_name>"

Change a user's telephone number:config:#user modify <name> telephoneNumber "<phone_number>"

Change a user's email address:
config:#user modify <name> eMailAddress <email_address>

Variables:
•
•
•

•

558

<name> is the name of the user whose settings you want to change.
<full_name> is a string comprising up to 64 ASCII printable characters. The<full_name> variable must be enclosed in quotes when it contains spaces.
<phone_number> is the phone number that can reach the specified user.
The <phone_number> variable must be enclosed in quotes when it
contains spaces.
<email_address> is the email address of the specified user.

Chapter 9: Using the Command Line Interface

Enabling or Disabling a User Profile

This command enables or disables a user profile. A user can log in to the PX3
only after that user's user profile is enabled.
config:#user modify <name> enabled <option>

Variables:••<name> is the name of the user whose settings you want to change.
<option> is one of the options: true or false.
OptionDescription

true

Enables the specified user profile.

false

Disables the specified user profile.

Forcing a Password ChangeThis command determines whether the password change is forced when a user
logs in to the specified user profile next time.
config:#user modify <name> forcePasswordChangeOnNextLogin <option>

Variables:••<name> is the name of the user whose settings you want to change.
<option> is one of the options: true or false.
OptionDescriptiontrue

A password change is forced on the user's next login.

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 specificuser profile. You can combine all of the following commands to modify the
SNMPv3 parameters at a time. See Multi-Command Syntax (on page 615).
Enable or disable the SNMP v3 access to PX3 for the specified user:

559

Chapter 9: Using the Command Line Interface

config:#user modify <name> snmpV3Access <option1>

Determine the security level:
config:#user modify <name> securityLevel <option2>

Determine whether the authentication passphrase is identical to thepassword:
config:#user modify <name> userPasswordAsAuthenticationPassphrase <option3>

Determine the authentication passphrase:
config:#user modify <name> authenticationPassPhrase
After performing the above command, PX3 prompts you to enter theauthentication passphrase.

Determine whether the privacy passphrase is identical to theauthentication passphrase:
config:#user modify <name> useAuthenticationPassPhraseAsPrivacyPassPhrase <option4>

Determine the privacy passphrase:
config:#user modify <name> privacyPassPhrase
After performing the above command, PX3 prompts you to enter the privacy
passphrase.

Determine the authentication protocol:
config:#user modify <name> authenticationProtocol <option5>

Determine the privacy protocol:

560

Chapter 9: Using the Command Line Interface

config:#user modify <name> privacyProtocol <option6>

Variables:
•
•

•

•

•

•

<name> is the name of the user whose settings you want to change.
<option1> is one of the options: enable or disable.
OptionDescription

enableEnables the SNMP v3 access permission for the
specified user.

disableDisables the SNMP v3 access permission for the
specified user.

<option2> is one of the options: noAuthNoPriv, authNoPriv or authPriv.
OptionDescription

noAuthNoPriv

No authentication and no privacy.

authNoPriv

Authentication and no privacy.

authPriv

Authentication and privacy.

<option3> is one of the options: true or false.
OptionDescription

trueAuthentication passphrase is identical to thepassword.

false

Authentication passphrase is different from thepassword.

<option4> is one of the options: true or false.
OptionDescriptiontrue

Privacy passphrase is identical to the authentication
passphrase.

false

Privacy passphrase is different from theauthentication passphrase.

<option5> is one of the options: MD5 or SHA-1.
OptionDescription

MD5

MD5 authentication protocol is applied.

561

Chapter 9: Using the Command Line Interface••

OptionDescription

SHA-1

SHA-1 authentication protocol is applied.

<option6> is one of the options: DES or AES-128.
OptionDescription

DES

DES privacy protocol is applied.

AES-128

AES-128 privacy protocol is applied.

An authentication or privacy passphrase is a string comprising 8 to 32 ASCII
printable characters.

Changing the Role(s)This command changes the role(s) of a specific user.
config:#user modify <name> roles <roles>

Variables:••<name> is the name of the user whose settings you want to change.
<roles> is a role or a list of comma-separated roles assigned to thespecified user profile. See All Privileges (on page 568).

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 615).
Note: The measurement unit change only applies to the web interface andcommand line interface.

562

Chapter 9: Using the Command Line Interface

Tip: To set the default measurement units applied to the PX3 user interfaces for
all users via CLI, see Setting Default Measurement Units (on page 565).
Set the preferred temperature unit:
config:#user modify <name> preferredTemperatureUnit <option1>

Set the preferred length unit:
config:#user modify <name> preferredLengthUnit <option2>

Set the preferred pressure unit:
config:#user modify <name> preferredPressureUnit <option3>

Variables:
•
•

•

•

<name> is the name of the user whose settings you want to change.
<option1> is one of the options: C or F.
OptionDescription

C

This option displays the temperature in Celsius.

F

This option displays the temperature in Fahrenheit.

<option2> is one of the options: meter or feet.
OptionDescription

meterThis option displays the length or height in meters.

feetThis option displays the length or height in feet.

<option3> is one of the options: pascal or psi.
OptionDescription

pascalThis option displays the pressure value in Pascals (Pa).

psiThis option displays the pressure value in psi.

563

Chapter 9: Using the Command Line Interface

Specifying the SSH Public Key

If the SSH key-based authentication is enabled, specify the SSH public key foreach 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:#2.

user modify <name> sshPublicKey

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.

ExampleThe following procedure illustrates how to change the SSH public key for theuser "assistant."
1.

Verify that you have entered the configuration mode. See Entering
Configuration Mode (on page 493).

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:#564

user delete <name>Chapter 9: Using the Command Line Interface

Changing Your Own Password

Every user can change their own password via this command if they have theChange Own Password privilege. Note that this command does not begin withuser.
config:#password

After performing this command, the PX3 prompts you to enter both current
and new passwords respectively.
Important: After the password is changed successfully, the new password iseffective immediately no matter you type the command "apply" or not tosave the changes.
ExampleThis procedure changes your own password:
1.

Verify that you have entered the configuration mode. See Entering
Configuration Mode (on page 493).

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 thefollowing prompt appears.
Re-type new password:

Setting Default Measurement Units

Default measurement units, including temperature, length, and pressure units,
apply to the PX3 user interfaces across all users except for those whose
preferred measurement units are set differently by themselves or theadministrator. Diverse measurement unit commands can be combined so thatyou can set all default measurement units at a time. To combine all commands,
see Multi-Command Syntax (on page 615).
Note: The measurement unit change only applies to the web interface andcommand line interface.

565

Chapter 9: Using the Command Line Interface

Tip: To change the preferred measurement units displayed in the PX3 userinterfaces for a specific user via CLI, see Changing Measurement Units (on page562).
Set the default temperature unit:
config:#user defaultpreferences preferredTemperatureUnit <option1>

Set the default length unit:
config:#user defaultpreferences preferredLengthUnit <option2>

Set the default pressure unit:
config:#user defaultpreferences preferredPressureUnit <option3>

Variables:•••<option1> is one of the options: C or F.
OptionDescription

C

This option displays the temperature in Celsius.

F

This option displays the temperature in Fahrenheit.

<option2> is one of the options: meter or feet.
OptionDescription

meterThis option displays the length or height in meters.

feetThis option displays the length or height in feet.

<option3> is one of the options: pascal or psi.
OptionDescription

pascalThis option displays the pressure value in Pascals (Pa).

psiThis option displays the pressure value in psi.

ExamplesThis section illustrates several user configuration examples.

566

Chapter 9: Using the Command Line Interface

Example 1 - Creating a User Profile

The following command creates a new user profile and sets two parameters forthe new user.
config:#user create Mary enable admin

Results:•••

A new user profile "Mary" is created.
The new user profile is enabled.
The admin role is assigned to the new user profile.

Example 2 - Modifying a User's RolesThe following command assigns two roles to the user "May."
config:#user modify Mary roles admin,tester

Results:•

The user Mary 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 feetpreferredPressureUnit 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.

567

Chapter 9: Using the Command Line Interface

Role Configuration Commands
A role configuration command begins with role.

Creating a Role

This command creates a new role, with a list of semicolon-separated privileges
assigned to the role.
config:#role create <name> <privilege1>;<privilege2>;<privilege3>...

If a specific privilege contains any arguments, that privilege should be followed
by a colon and the argument(s).
config:#role create <name> <privilege1>:<argument1>,<argument2>...;<privilege2>:<argument1>,<argument2>...;<privilege3>:<argument1>,<argument2>...;...

Variables:•••<name> is a string comprising up to 32 ASCII printable characters.
<privilege1>, <privilege2>, <privilege3> and the like are names of theprivileges assigned to the role. Separate each privilege with a semi-colon.
See All Privileges (on page 568).
<argument1>, <argument2> and the like are arguments set for a particularprivilege. Separate a privilege and its argument(s) with a colon, andseparate arguments with a comma if there are more than one argument
for a privilege.

All PrivilegesThis table lists all privileges. Note that available privileges vary according to themodel you purchased.

568

Privilege

Description

acknowledgeAlarms

Acknowledge Alarms

adminPrivilege

Administrator PrivilegeschangeAssetStripConfiguration

Change Asset Strip Configuration

changeAuthSettings

Change Authentication SettingschangeDataTimeSettings

Change Date/Time Settings

Chapter 9: Using the Command Line Interface

Privilege

DescriptionchangeExternalSensorsConfiguration

Change Peripheral Device
Configuration

changeLhxConfiguration

Change LHX/SHX Configuration

changeModemConfiguration

Change Modem Configuration

changeNetworkSettings

Change Network SettingschangePassword

Change Own Password

changePduConfiguration

Change Pdu, Inlet, Outlet &Overcurrent Protector
Configuration

changeSecuritySettings

Change Security SettingschangeSnmpSettings

Change SNMP SettingschangeUserSettings

Change Local User ManagementchangeWebcamSettings

Change Webcam Configuration

clearLog

Clear Local Event Log

firmwareUpdate

Firmware Update

performReset

Reset (Warm Start)

switchActuator*

Switch Actuator

viewAuthSettings

View Authentication Settings

viewEventSetup

View Event Settings

viewEverything

Unrestricted View Privileges

viewLog

View Local Event Log

viewSecuritySettings

View Security Settings

viewSnmpSettings

View SNMP Settings

viewUserSettings

View Local User Management

viewWebcamSettings

View Webcam Snapshots andConfiguration* The "switchActuator" privilege requires an argument that is separated with acolon. The argument could be:•

All actuators, that is,
switchActuator:all•

An actuator's ID number. For example:
switchActuator:1569

Chapter 9: Using the Command Line Interface

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 PX3 web interface. It
is an integer.

Modifying a Role

You can modify diverse parameters of an existing role, including its privileges.
Modify a role's description:
config:#role modify <name> description "<description>"

Add more privileges to a specific role:
config:#role modify <name> addPrivileges<privilege1>;<privilege2>;<privilege3>...

If a specific privilege contains any arguments, add a colon and theargument(s) after that privilege.
config:#role modify <name> addPrivileges<privilege1>:<argument1>,<argument2>...;<privilege2>:<argument1>,<argument2>...;<privilege3>:<argument1>,<argument2>...;...

Remove specific privileges from a role:
config:#role modify <name> removePrivileges<privilege1>;<privilege2>;<privilege3>...

If a specific privilege contains any arguments, add a colon and theargument(s) after that privilege.

570

Chapter 9: Using the Command Line Interface

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, thecommand fails to remove specified privileges that are not available.
Variables:
•
•
•

•

<name> is a string comprising up to 32 ASCII printable characters.
<description> is a description comprising alphanumeric characters. The<description> variable must be enclosed in quotes when it contains spaces.
<privilege1>, <privilege2>, <privilege3> and the like are names of theprivileges assigned to the role. Separate each privilege with a semi-colon.
See All Privileges (on page 568).
<argument1>, <argument2> and the like are arguments set for a particularprivilege. Separate a privilege and its argument(s) with a colon, andseparate arguments with a comma if there are more than one argument
for a privilege. For arguments syntax, see All Privileges (on page 568).

Deleting a Role

This command deletes an existing role.
config:#role delete <name>Example - Creating a RoleThe following command creates a new role and assigns privileges to the role.
config:#role create tester firmwareUpdate;viewEventSetup

Results:••

A new role "tester" is created.
Two privileges are assigned to the role: firmwareUpdate (Firmware Update)and viewEventSetup (View Event Settings).

Authentication Commands
An authentication configuration command begins with authentication.

571

Chapter 9: Using the Command Line Interface

Determining the Authentication Method

You can choose to set the authentication type only, or both set theauthentication type and determine whether to switch to local authentication incase the remote authentication is not available.
Determine the authentication type only:
config:#authentication type <option1>

Determine the authentication type and enable/disable the option ofswitching to local authentication:
config:#authentication type <option1> useLocalIfRemoteUnavailable <option2>
Note: You cannot enable or disable the option of switching to local
authentication without determining the authentication type in the CLI.
Therefore, always type "authentication type <option1>" when setting up"useLocalIfRemoteUnavailable".

Variables:
•

•

572

<option1> is one of the options: local , ldap or radius.
OptionDescription

local

Enable Local authentication only.

ldap

Enable LDAP authentication.

radiusEnable Radius authentication.

<option2> is one of the options: true or false.
OptionDescription

true

Remote authentication is the first priority. The device
will switch to local authentication when the remoteauthentication is not available.

false

Always stick to remote authentication regardless of
the availability of remote authentication.

Chapter 9: Using the Command Line Interface

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 577).
Add a new LDAP server:
config:#authentication ldap add <host> <port> <ldap_type> <security><bind_type> <base_DN> <login_name_att> <user_entry_class> "Optional
Parameters"
Note: "Optional Parameters" refer to one or multiple parameters listed in thesection Optional Parameters (on page 574). They are required only when yourserver settings need to specify these parameters. For example, if setting the<bind_type> to "authenticatedBind", then you must add the parameter"bindDN" to this command.
When the above command is successfully performed, a list of all LDAP servers,
including the newly-added one, will be displayed, which is similar to thefollowing diagram.

573

Chapter 9: Using the Command Line Interface

Tip: To verify all settings of a newly-added server, see Authentication Settings(on page 482).

Variables:
•
•
•

•

•

<host> is the IP address or host name of the LDAP server.
<port> is the port number assigned for communication with the LDAP
server.
<ldap_type> is one of the LDAP server types: openldap or activeDirectory.
Type
openldap

Description

activeDirectory

Microsoft Active Directory

OpenLDAP server<security> is one of the security options: none, startTls or tls.
Type
none

Description

startTls

StartTLS

tls

TLS

No security<bind_type> is one of the bind options: anonymouseBind, orauthenticatedBind.
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.

•••<base_DN> is the base DN for search.
<login_name_att> is the login name attribute.
<user_entry_class> is the User Entry Object Class.

Optional Parameters
You can add one or multiple "optional parameters", such as specifying the Bind
DN or certificate upload, to an LDAP-server-adding command as illustrated
below. If adding multiple optional parameters, you must add them to the END
of the command and separate them with a space.
▪

574

Example 1 -- Specify an Active Directory Domain's name:Chapter 9: Using the Command Line Interface

config:#authentication ldap add <host> <port> <ldap_type> <security><bind_type> <base_DN> <login_name_att> <user_entry_class> adDomain<AD_domain>▪

config:#Example 2 -- Set up the bind DN:

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
userSearchSubfilter <filter>

To configure

bindDN <bind_DN>bind DN

User search subfilter▪ The system will prompt you to enter andre-confirm the bind password after adding
this parameter to the command.
▪ For details, see Illustrations of Adding LDAP
Servers (on page 576).

adDomain <AD_domain>

Active Directory Domain nameverifyServerCertificate <verify_cert>

Certificate verification setting▪ After setting to true, the system will prompt
you to upload a certificate. For details, see
Illustrations of Adding LDAP Servers (on page576).

allowExpiredCertificate<allow_exp_cert>

Whether to accept expired or not valid yet
certificate

Variables:••••<filter> is the user search subfilter you specify.
<bind_DN> is bind DN.
<AD_domain> is the Active Directory Domain.
<verify_cert> is one of the options: true or false.
Optiontrue

Description

false

Disable the verification of the LDAP server certificate.

Enable the verification of the LDAP server certificate.

575

Chapter 9: Using the Command Line Interface•<allow_exp_cert> is one of the options: true or false.
OptionDescription

trueCertificates that are either expired or not valid yet are
all accepted.

false

Only valid certificates are accepted.

Illustrations of Adding LDAP Servers
This section shows several LDAP command examples. Those words highlighted
in bold are required for their respective examples.
An OpenLDAP server:
config:#authentication ldap add op-ldap.raritan.com 389 openldap noneanonymousBind dc=raritan,dc=com uid inetOrgPerson
A Microsoft Active Directory server:

config:#authentication ldap add ac-ldap.raritan.com 389 activeDirectory noneanonymousBind dc=raritan,dc=com sAMAccountName user adDomain
raritan.com
An LDAP server with a TLS certificate uploaded:a.

config:#Enter the CLI command with the following two TLS-related options set
and/or added:▪

<security> is set to tls or startTls.

▪

The "verifyServerCertificate" parameter is added to the commandand set to "true."authentication ldap add ldap.raritan.com 389 openldap startTls ...
inetOrgPerson verifyServerCertificate trueb.

The system now prompts you to enter the certificate's content.

c.

Type or copy the certificate's content in the CLI and press Enter.

Note: 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.
config:#576

Enter the CLI command with the "bindDN" parameter and its data
added.

authentication ldap add op-ldap.raritan.com 389 openldap none
authenticatedBind cn=Manager,dc=raritan,dc=com uid inetOrgPerson
bindDN user@raritan.com

Chapter 9: Using the Command Line Interfaceb.

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 <server_num> <host>

Variables:••<host> is the IP address or host name of the LDAP server.
<server_num> is the sequential number of the specified server shown on
the server list of the PX3. See Authentication Settings (on page 482).

Modifying an Existing LDAP Server

You can modify one or multiple parameters of an existing LDAP server, such asits IP address, TCP port number, Base DN and so on. Besides, you can alsochange 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 thefollowing:
config:#authentication ldap modify <server_num> "parameters"
Variables:••<server_num> is the sequential number of the specified server in the LDAP
server list.
Replace "parameters" with one or multiple commands in the following
table, depending on which parameter(s) you want to modify.
A list of "parameters":

577

Chapter 9: Using the Command Line Interface

Parameters
host <host>port <port>

serverType <ldap_type>securityType <security>

bindType <bind_type>searchBaseDN <base_DN>

loginNameAttribute<login_name_att>
userEntryObjectClass<user_entry_class>userSearchSubfilter<user_search_filter>
adDomain <AD_domain>
verifyServerCertificate<verify_cert>

578

Description
Change the IP address or host name.
▪ <host> is the new IP address or host name.
Change the TCP port number.
▪ <port> is the new TCP port number.
Change the server type.
▪ <ldap_type> is the new type of the LDAP server.
▪ <ldap_type> values include: openldap andactiveDirectory.
Change the security type.
▪ <security> is the new security type.
▪ <security> values include: none, startTls, and ssl
Change the bind type.
▪ <bind_type> is the new bind type.
▪ <bind_type> values include: anonymousBind andauthenticatedBind.
Change the base DN for search.
▪ <base_DN> is the new base DN for search.
Change the login name attribute.
▪ <login_name_att> is the new login name attribute.
Change the user entry object class.
▪ <user_entry_class> is the new user entry class.
Change the user search subfilter.
▪ <user_search_filter> is the new user search subfilter.
Change the Active Directory Domain name.
▪ <AD_domain> is the new domain name of the Active Directory.
Enable or disable the certificate verification.
▪ <verify_cert> enables or disables the certificate verification
feature.
▪ Available values include: true, false

Chapter 9: Using the Command Line Interface

Parameters

Description
Re-upload a different certificate.

certificatea.

First add the "certificate" parameter to the command, andpress 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.

Determine whether to accept a certificate which is expired or not
valid yet.

allowExpiredCertificate<allow_exp_cert>▪ <allow_exp_cert> determines whether to accept an expired or
not valid yet certificate▪ <allow_exp_cert> values include: true, and false
Change the bind DN.

bindDN <bind_DN>▪ <bind_DN> is the new bind DN.
Change the bind DN password.

bindPassworda.

First add the "bindPassword" parameter to the command, andpress Enter.

b.

The system prompts you for the input of the password.

c.

Type the password and press Enter.

Change the priority of the server (that is, resorting).

sortPosition <position>▪ <position> 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 (onpage 573).

•
config:#authentication ldap modify 1 host 192.168.3.3•
config:#Change both the IP address and TCP port of the 1st LDAP server

authentication ldap modify 1 host 192.168.3.3 port 633•
config:#Examples:Change the IP address of the 1st LDAP server

Change the IP address, TCP port and the type of the L1st DAP server

authentication ldap modify 1 host 192.168.3.3 port 633
serverType activeDirectory579

Chapter 9: Using the Command Line Interface

Removing an Existing LDAP ServerThis command removes an existing LDAP server from the server list.
config:#authentication ldap delete <server_num>

Variables:•<server_num> is the sequential number of the specified server in the LDAP
server list.

Radius Settings

All Radius-related commands begin with authentication radius.
If you enable Radius authentication, you must add at least one Radius server.
Later you can modify 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 <host> <rds_type> <auth_port> <acct_port> <timeout><retries>
Variables:
•
•

•
•
•
•

<host> is the IP address or host name of the Radius server.
<rds_type> is one of the Radius authentication types: pap, chap,
msChapV2.
Type

Description

chap

CHAP

pap

PAP

msChapV2

MSCHAP v2<auth_port> is the authentication port number.
<acct_port> is the accounting port number.
<timeout> is the timeout value in seconds. It ranges between 1 to 10
seconds.
<retries> is the number of retries. It ranges between 0 to 5.
To enter the shared secret:

580

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.

Chapter 9: Using the Command Line Interface

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, orchange the priority or sequence of existing servers in the server list.
Change the IP address or host name:config:#authentication radius modify <server_num> host <host>
Change the Radius authentication type:config:#authentication radius modify <server_num> authType <rds_type>
Change the authentication port:

config:#authentication radius modify <server_num> authPort <auth_port>
Change the accounting port:

config:#authentication radius modify <server_num> accountPort <acct_port>
Change the timeout value:

config:#authentication radius modify <server_num> timeout <timeout>
Change the number of retries:

config:#authentication radius modify <server_num> retries <retries>
Change the shared secret:config:#authentication radius modify <server_num> secret
Change the priority of the specified server:

581

Chapter 9: Using the Command Line Interface

config:#authentication radius modify <server_num> sortPositon <position>
Tip: You can add more than one parameters to the command. For example,"authentication radius modify <server_num> host <host>authType <rds_type> authPort <auth_port> accountPort<acct_port> ...".

Variables:
•
•
•
•
•
•
•

<server_num> is the sequential number of the specified server in the
Radius server list.
<host> is the new IP address or host name of the Radius server.
<rds_type> is one of the Radius authentication types: pap, chap,
msChapV2.
<auth_port> is the new authentication port number.
<acct_port> is the new accounting port number.
<timeout> is the new timeout value in seconds. It ranges between 1 to 10
seconds.
<retries> is the new number of retries. It ranges between 0 to 5.
To enter the shared secret:

1.

After executing the above Radius command, the system automatically
prompts you to enter 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 ServerThis command removes an existing Radius server from the server list.
config:#authentication radius delete <server_num>

Variables:•582<server_num> is the sequential number of the specified server in the
Radius server list.

Chapter 9: Using the Command Line Interface

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 (onpage 600).
Changing the Sensor Name

This command names an environmental sensor.
config:#externalsensor <n> name "<name>"

Variables:••<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
<name> is a string comprising up to 64 ASCII printable characters. The<name> variable must be enclosed in quotes when it contains spaces.

Note: To name an actuator, see Actuator Configuration Commands (on page
600).
Specifying the CC Sensor Type

Raritan's contact closure sensor supports the connection of diverse third-party.
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 <n> sensorSubType <sensor_type>

Variables:••<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
<sensor_type> is one of these types: contact, smokeDetection,waterDetection or vibration.
Type

Description

contact

The connected detector/switch is for detection ofdoor lock or door closed/open status.

583

Chapter 9: Using the Command Line Interface

Type

Description

smokeDetection

The connected detector/switch is for detection of thesmoke presence.

waterDetection

The connected detector/switch is for detection of thewater presence.

vibration

The connected detector/switch is for detection of thevibration.

Setting the X Coordinate

This command specifies the X coordinate of an environmental sensor.
config:#externalsensor <n> xlabel "<coordinate>"

Variables:••<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
<coordinate> is a string comprising up to 24 ASCII printable characters, andit must be enclosed in quotes.

Setting the Y Coordinate

This command specifies the Y coordinate of an environmental sensor.
config:#externalsensor <n> ylabel "<coordinate>"

Variables:
•

•

584

<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
<coordinate> is a string comprising up to 24 ASCII printable characters, andit must be enclosed in quotes.

Chapter 9: Using the Command Line Interface

Setting the Z Coordinate

This command specifies the Z coordinate of an environmental sensor.
config:#externalsensor <n> zlabel "<coordinate>"

Variables:••<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
Depending on the Z coordinate format you set, there are two types ofvalues for the <coordinate> variable:
Type

Description

Free form<coordinate> is a string comprising up to 24 ASCII
printable characters, and it must be enclosed inquotes.

Rack units<coordinate> is 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 496).
Changing the Sensor Description

This command provides a description for a specific environmental sensor.
config:#externalsensor <n> description "<description>"

Variables:••<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
<description> is a string comprising up to 64 ASCII printable characters,
and it must be enclosed in quotes when it contains spaces.

585

Chapter 9: Using the Command Line Interface

Using Default Thresholds

This command determines whether default thresholds, including thedeassertion hysteresis and assertion timeout, are applied to a specificenvironmental sensor.
config:#externalsensor <n> useDefaultThresholds <option>

Variables:••<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
<option> is one of the options: true or false.
OptionDescription

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-PIRThis command determines the value of the Alarmed to Normal Delay setting
for a Raritan presence detector.
config:#externalsensor <n> alarmedToNormalDelay <time>

Variables:••<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
<time> is an integer number in seconds, ranging between 0 and 300.

ExamplesThis section illustrates several environmental sensor configuration examples.

586

Chapter 9: Using the Command Line Interface

Example 1 - Environmental Sensor Naming

The following command assigns the name "Cabinet humidity" to theenvironmental sensor with the ID number 4.
config:#externalsensor 4 name "Cabinet humidity"

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:#externalsensor 1 useDefaultThresholds 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 typeat a time by combining multiple commands. See Multi-Command Syntax (onpage 615).
Set the Default Upper Critical Threshold for a specific sensor type:config:#defaultThresholds <sensor type> upperCritical <value>
Set the Default Upper Warning Threshold for a specific sensor type:config:#defaultThresholds <sensor type> upperWarning <value>
Set the Default Lower Critical Threshold for a specific sensor type:config:#defaultThresholds <sensor type> lowerCritical <value>
Set the Default Lower Warning Threshold for a specific sensor type:config:#defaultThresholds <sensor type> lowerWarning <value>
Set the Default Deassertion Hysteresis for a specific sensor type:587

Chapter 9: Using the Command Line Interface

config:#defaultThresholds <sensor type> hysteresis <hy_value>
Set the Default Assertion Timeout for a specific sensor type:config:#defaultThresholds <sensor type> assertionTimeout <as_value>

Variables:
•

•

•
•

588

<sensor type> is one of the following numeric sensor types:
Sensor types

Description

absoluteHumidity

Absolute humidity sensors

relativeHumidity

Relative humidity sensors

temperature

Temperature sensors

airPressure

Air pressure sensors

airFlow

Air flow sensors

vibration

Vibration sensors<value> is the value for the specified threshold of the specified sensor type.
Note that diverse sensor types use different measurement units.
Sensor types

Measurement units

absoluteHumidity

g/m^3 (that is, g/m3)

relativeHumidity%

temperature

Degrees Celsius ( ) or Fahrenheit (your measurement unit settings.

airPressure

Pascal (Pa) or psi, depending on your measurement
unit settings.

airFlowm/s

vibrationg), depending on<hy_value> is the deassertion hysteresis value applied to the specified
sensor type.
<as_value> is the assertion timeout value applied to the specified sensor
type. It ranges from 0 to 100 (samples).

Chapter 9: Using the Command Line Interface

Example - Default Upper Thresholds for Temperature

It is assumed that your preferred measurement unit for temperature is set todegrees Celsius. Then the following command sets the default Upper Warning
threshold to 20
and Upper Critical threshold to 24
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 thecommands to configure the threshold, hysteresis and assertion timeout values
for any sensor associated with the following items:▪

Inlets▪

Inlet poles (for three-phase PDUs only)▪

Overcurrent protectors▪

Environmental sensors

It is permitted to assign a new value to the threshold at any time regardless ofwhether the threshold has been enabled.
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 bycombining multiple commands. See Multi-Command Syntax (on page 615).
Set the Upper Critical threshold for an inlet sensor:
config:#sensor inlet <n> <sensor type> upperCritical <option>

Set the Upper Warning threshold for an inlet sensor:
config:#sensor inlet <n> <sensor type> upperWarning <option>

Set the Lower Critical threshold for an inlet sensor:
config:#sensor inlet <n> <sensor type> lowerCritical <option>

Set the Lower Warning threshold for an inlet sensor:589

Chapter 9: Using the Command Line Interface

config:#sensor inlet <n> <sensor type> lowerWarning <option>

Set the deassertion hysteresis for an inlet sensor:
config:#sensor inlet <n> <sensor type> hysteresis <hy_value>

Set the assertion timeout for an inlet sensor:
config:#sensor inlet <n> <sensor type> assertionTimeout <as_value>

Variables:••<n> is the number of the inlet that you want to configure. For a single-inlet
PDU, <n> is always 1.
<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

unbalancedCurrent

Unbalanced load sensor

lineFrequency

Line frequency sensor

phaseAngle

Inlet phase angle sensor

Note: If the requested sensor type is not supported, the "Sensor is notavailable" message is displayed.
•

590<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for a specific inlet
sensor.

disableDisables the specified threshold for a specific inlet
sensor.

Chapter 9: Using the Command Line Interface••

OptionDescription

A numeric value

Sets a value for the specified threshold of a specificinlet sensor and enables this threshold at the sametime.

<hy_value> is a numeric value that is assigned to the hysteresis for the
specified inlet sensor. See "To De-assert" and Deassertion Hysteresis (onpage 782).
<as_value> is a numeric value that is assigned to the assertion timeout forthe specified inlet sensor. See "To Assert" and Assertion Timeout (on page780).
Additional sensors supported by specific models:Specific PX3 models support some or all of the following sensors. The CLI
command(s) listed above can be also applied to the following sensors. Notethat the measurement unit of current values in CLI is A, not mA.
Sensor type

Description

peakCurrent

Peak current sensor

Supported on PXC andLegrand PDU only

▪ three-phase models als
support pole-level peakcurrent▪ models with meteredbreakers also support
breaker-level peakcurrent
reactivePower

Reactive power sensor

displacementPowerFact
or

Displacement power factor sensor

residualCurrent

RCM current sensor▪

▪ For Type A, it is the sensor that detects
residual AC current.
▪ For Type B, it is the sensor that detects
both residual AC and DC current.
residualDCCurrent

RCM DC current sensor - detects residual DC
current only.
Available only on PDUs with RCM Type B.

Note: For information on RCM Type A and B sensors, see RCM Current Sensor(on page 686).

591

Chapter 9: Using the Command Line Interface

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 bycombining multiple commands. See Multi-Command Syntax (on page 615).
Set the Upper Critical Threshold for an Inlet Pole:config:#sensor inletpole <n> <p> <sensor type> upperCritical <option>
Set the Upper Warning Threshold for an Inlet Pole:config:#sensor inletpole <n> <p> <sensor type> upperWarning <option>
Set the Lower Critical Threshold for an Inlet Pole:config:#sensor inletpole <n> <p> <sensor type> lowerCritical <option>
Set the Lower Warning Threshold for an Inlet Pole:config:#sensor inletpole <n> <p> <sensor type> lowerWarning <option>
Set the Inlet Pole's Deassertion Hysteresis:

config:#sensor inletpole <n> <p> <sensor type> hysteresis <hy_value>
Set the Inlet Pole's Assertion Timeout:config:#sensor inletpole <n> <p> <sensor type> assertionTimeout <as_value>

Variables:
•
•

592

<n> is the number of the inlet whose pole sensors you want to configure.
For a single-inlet PDU, <n> is always 1.
<p> is the label of the inlet pole that you want to configure.
Pole

Label
<p>

Current sensor

Voltage sensor

1

L1

L1

L1 - L22

L2

L2

L2 - L33

L3

L3

L3 - L1

Chapter 9: Using the Command Line Interface•<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

voltage

Voltage sensor

activePower

Active power sensor

apparentPower

Apparent power sensor

powerFactor

Power factor sensor

activeEnergy

Active energy sensor

unbalancedCurrent

Unbalanced load sensor

Note: If the requested sensor type is not supported, the "Sensor is notavailable" message is displayed.
•<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for the specified inlet
pole sensor.

disableDisables the specified threshold for the specified inlet
pole sensor.

A numeric value

Sets a value for the specified threshold of thespecified inlet pole sensor and enables this thresholdat the same time.

593

Chapter 9: Using the Command Line Interface••<hy_value> 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 782).
<as_value> 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 780).

Additional sensors supported by specific models:Specific PX3 models support some or all of the following sensors. The CLI
command(s) listed above can be also applied to the following sensors. Notethat the measurement unit of current values in CLI is A, not mA.
Sensor type

Description

peakCurrent

Peak current sensor

Supported on PXC andLegrand PDU only

▪ three-phase models als
support pole-level peakcurrent▪ models with meteredbreakers also support
breaker-level peakcurrent
reactivePower

Reactive power sensor

displacementPowerFact
or

Displacement power factor sensor

residualCurrent

RCM current sensor▪

▪ For Type A, it is the sensor that detects
residual AC current.
▪ For Type B, it is the sensor that detects
both residual AC and DC current.
residualDCCurrent

RCM DC current sensor - detects residual DC
current only.
Available only on PDUs with RCM Type B.

Note: For information on RCM Type A and B sensors, see RCM Current Sensor(on page 686).

594

Chapter 9: Using the Command Line Interface

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 bycombining multiple commands. See Multi-Command Syntax (on page 615).
Set the Upper Critical threshold for an overcurrent protector:
config:#sensor ocp <n> <sensor type> upperCritical <option>

Set the Upper Warning threshold for an overcurrent protector:
config:#sensor ocp <n> <sensor type> upperWarning <option>

Set the Lower Critical threshold for an overcurrent protector:
config:#sensor ocp <n> <sensor type> lowerCritical <option>

Set the Lower Warning threshold for an overcurrent protector:
config:#sensor ocp <n> <sensor type> lowerWarning <option>

Set the deassertion hysteresis for an overcurrent protector:
config:#sensor ocp <n> <sensor type> hysteresis <hy_value>

Set the assertion timeout for an overcurrent protector:
config:#sensor ocp <n> <sensor type> assertionTimeout <as_value>

Variables:••<n> is the number of the overcurrent protector that you want to configure.
<sensor type> is one of the following sensor types:
Sensor type

Description

current

Current sensor

Note: If the requested sensor type is not supported, the "Sensor is notavailable" message is displayed.

595

Chapter 9: Using the Command Line Interface

•

•

•

<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for the overcurrent
protector sensor.

disableDisables the specified threshold for the overcurrent
protector sensor.

A numeric value

Sets a value for the specified threshold of theovercurrent protector sensor and enables thisthreshold at the same time.

<hy_value> is a numeric value that is assigned to the hysteresis for the
specified overcurrent protector sensor. See "To De-assert" andDeassertion Hysteresis (on page 782).
<as_value> 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 780).

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 bycombining multiple commands. See Multi-Command Syntax (on page 615).
Set the Upper Critical threshold for an environmental sensor:
config:#sensor externalsensor <n> <sensor type> upperCritical <option>

Set the Upper Warning threshold for an environmental sensor:
config:#sensor externalsensor <n> <sensor type> upperWarning <option>

Set the Lower Critical threshold for an environmental sensor:
config:#sensor externalsensor <n> <sensor type> lowerCritical <option>

Set the Lower Warning threshold for an environmental sensor:
config:#sensor externalsensor <n> <sensor type> lowerWarning <option>

Set the deassertion hysteresis for an environmental sensor:

596

Chapter 9: Using the Command Line Interface

config:#sensor externalsensor <n> <sensor type> hysteresis <hy_value>

Set the assertion timeout for an environmental sensor:
config:#sensor externalsensor <n> <sensor type> assertionTimeout <as_value>

Variables:••<n> is the ID number of the environmental sensor that you want toconfigure. The ID number is available in the PX3 web interface or using thecommand "show externalsensors <n>" in the CLI. It is an integer
starting at 1.
<sensor type> is one of the following numeric sensor types:
Sensor types

Description

absoluteHumidity

Absolute humidity sensors

relativeHumidity

Relative humidity sensors

temperature

Temperature sensors

airPressure

Air pressure sensors

airFlow

Air flow sensors

vibration

Vibration sensors

Note: If the specified sensor type does not match the type of the specified
environmental sensor, this error message appears: "Specified sensor type
'XXX' does not match the sensor's type (<sensortype>)," where XXX is the
specified sensor type, and <sensortype> is the correct sensor type.
•<option> is one of the options: enable, disable or a numeric value.
OptionDescription

enableEnables the specified threshold for a specificenvironmental sensor.

disableDisables the specified threshold for a specificenvironmental sensor.

A numeric value

Sets a value for the specified threshold of a specificenvironmental sensor and enables this threshold at
the same time.

597

Chapter 9: Using the Command Line Interface••<hy_value> is a numeric value that is assigned to the hysteresis for the
specified environmental sensor. See "To De-assert" and Deassertion
Hysteresis (on page 782).
<as_value> is a number in samples that is assigned to the assertion
timeout for the specified environmental sensor. It ranges between 1 and100. See "To Assert" and Assertion Timeout (on page 780).

ExamplesThis 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 alsoenables 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 beenenabled 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 beenenabled 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.

598

Chapter 9: Using the Command Line Interface

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 thisthreshold has not been enabled yet.
The Upper Warning threshold for the 2nd overcurrent protector's RMS
current is enabled.

599

Chapter 9: Using the Command Line Interface

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 615).
Change the name:config:#actuator <n> name "<name>"

Set the X coordinate:config:#actuator <n> xlabel "<coordinate>"

Set the Y coordinate:config:#actuator <n> ylabel "<coordinate>"

Set the Z coordinate:config:#actuator <n> zlabel "<z_label>"

Modify the actuator's description:
config:#actuator <n> description "<description>"

Variables:••••<n> is the ID number assigned to the actuator. The ID number can befound using the PX3 web interface or CLI. It is an integer starting at 1.
<name> is a string comprising up to 64 ASCII printable characters. The<name> variable must be enclosed in quotes when it contains spaces.
<coordinate> is a string comprising up to 24 ASCII printable characters, andit must be enclosed in quotes.
There are two types of values for the <z_label> variable, depending on the
Z coordinate format you set:
Type

Description

Free form<coordinate> is a string comprising up to 24 ASCII
printable characters, and it must be enclosed inquotes.

Rack units<coordinate> is 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 496).

600

Chapter 9: Using the Command Line Interface•<description> is a string comprising up to 64 ASCII printable characters,
and it must be enclosed in quotes when it contains spaces.

Example - Actuator Naming

The following command assigns the name "Door lock of cabinet 3" to theactuator whose ID number is 9.
config:#actuator 9 name "Door lock of cabinet 3"

Server Reachability Configuration Commands
You can use the CLI to add or delete an IT device, such as a server, from theserver reachability list, or modify the settings for a monitored IT device. A
server reachability configuration command begins with serverReachability.
Adding a Monitored Device

This command adds a new IT device to the server reachability list.
config:#serverReachability add <IP_host> <enable> <succ_ping><fail_ping> <succ_wait> <fail_wait> <resume> <disable_count>

Variables:••<IP_host> is the IP address or host name of the IT device that you want toadd.
<enable> is one of the options: true or false.
OptionDescription

true

Enables the ping monitoring feature for the newly
added device.

false

Disables the ping monitoring feature for the newly
added device.

601

Chapter 9: Using the Command Line Interface

•
•
•
•
•
•

<succ_ping> is the number of successful pings for declaring the monitored
device "Reachable." Valid range is 0 to 200.
<fail_ping> is the number of consecutive unsuccessful pings for declaring
the monitored device "Unreachable." Valid range is 1 to 100.
<succ_wait> is the wait time to send the next ping after a successful ping.
Valid range is 5 to 600 (seconds).
<fail_wait> is the wait time to send the next ping after a unsuccessful ping.
Valid range is 3 to 600 (seconds).
<resume> is the wait time before the PX3 resumes pinging after declaring
the monitored device "Unreachable." Valid range is 5 to 120 (seconds).
<disable_count> is the number of consecutive "Unreachable" declarations
before the PX3 disables the ping monitoring feature for the monitored
device and returns to the "Waiting for reliable connection" state. Valid
range is 1 to 100 or unlimited.

Deleting a Monitored Device

This command removes a monitored IT device from the server reachability list.
config:#serverReachability delete <n>Variables:•<n> is a number representing the sequence of the IT device in themonitored server list.
You can find each IT device's sequence number using the CLI command ofshow serverReachability as illustrated below.

Modifying a Monitored Device's Settings

The command to modify a monitored IT device's settings begins with
serverReachability modify.
You can modify various settings for a monitored device at a time. See
Multi-Command Syntax (on page 615).
Modify a device's IP address or host name:config:#serverReachability modify <n> ipAddress <IP_host>Enable or disable the ping monitoring feature for the device:602

Chapter 9: Using the Command Line Interface

config:#serverReachability modify <n> pingMonitoringEnabled <option>
Modify the number of successful pings for declaring "Reachable":

config:#serverReachability modify <n> numberOfSuccessfulPingsToEnable<succ_number>
Modify the number of unsuccessful pings for declaring "Unreachable":

config:#serverReachability modify <n> numberOfUnsuccessfulPingsForFailure<fail_number>
Modify the wait time after a successful ping:config:#serverReachability modify <n> waitTimeAfterSuccessfulPing<succ_wait>
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:•••<n> is a number representing the sequence of the IT device in the server
monitoring list.
<IP_host> is the IP address or host name of the IT device whose settings
you want to modify.
<option> is one of the options: true or false.
OptionDescription

true

Enables the ping monitoring feature for the monitored
device.

false

Disables the ping monitoring feature for themonitored device.

603

Chapter 9: Using the Command Line Interface

•
•
•
•
•
•

<succ_number> is the number of successful pings for declaring themonitored device "Reachable." Valid range is 0 to 200.
<fail_number> is the number of consecutive unsuccessful pings fordeclaring the monitored device "Unreachable." Valid range is 1 to 100.
<succ_wait> is the wait time to send the next ping after a successful ping.
Valid range is 5 to 600 (seconds).
<fail_wait> is the wait time to send the next ping after a unsuccessful ping.
Valid range is 3 to 600 (seconds).
<resume> is the wait time before the PX3 resumes pinging after declaring
the monitored device "Unreachable." Valid range is 5 to 120 (seconds).
<disable_count> is the number of consecutive "Unreachable" declarations
before the PX3 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 thesecond server in the server reachability list.
config:#serverReachability modify 2 numberOfSuccessfulPingsToEnable 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 PX3 is enabled.
config:#energywise enabled <option>

Variables:•604<option> is one of the options: true or false.
OptionDescription

true

The Cisco EnergyWise feature is enabled.

false

The Cisco EnergyWise feature is disabled.

Chapter 9: Using the Command Line Interface

Specifying the EnergyWise Domain

This command syntax specifies to which Cisco® EnergyWise domain the PX3
belongs.
config:#energywise domain <name>

Variables:•<name> is a string comprising up to 127 ASCII printable characters. Spaces
and asterisks are NOT acceptable.

Specifying the EnergyWise SecretThis command syntax specifies the password (secret) to enter the Cisco ®
EnergyWise domain.
config:#energywise secret <password>

Variables:•<password> is a string comprising up to 127 ASCII printable characters.
Spaces and asterisks are NOT acceptable.

Changing the UDP PortThis command syntax specifies the UDP port for communications in the Cisco ®
EnergyWise domain.
config:#energywise port <port>

Variables:•<port> is the UDP port number ranging between 1 and 65535.

605

Chapter 9: Using the Command Line Interface

Setting the Polling IntervalThis command syntax determines the polling interval at which the Cisco ®
EnergyWise domain queries the PX3.
config:#energywise polling <timing>

Variables:•<timing> 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 PX3 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 withassetStrip.

606

Chapter 9: Using the Command Line Interface

Naming an Asset Strip

This command syntax names or changes the name of an asset strip connectedto the PX3 device.
config:#assetStrip <n> name "<name>"

Variables:••<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<name> is a string comprising up to 64 ASCII printable characters. The<name> variable must be enclosed in quotes when it contains spaces.

Specifying the Number of Rack Units

This command syntax specifies the total number of rack units on an asset strip
connected to the PX3 device.
config:#assetStrip <n> numberOfRackUnits <number>

Note: A rack unit refers to a tag port on the asset strips.
Variables:••<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<number> is the total number of rack units available on the connectedasset strip. This value ranges from 8 to 64.

607

Chapter 9: Using the Command Line Interface

Specifying the Rack Unit Numbering Mode

This command syntax specifies the numbering mode of rack units on the asset
strips connected to the PX3 device. The numbering mode changes the rack unit
numbers.
config:#assetStrip <n> rackUnitNumberingMode <mode>

Variables:••<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<mode> is one of the numbering modes: topDown or bottomUp.
Mode

Description

topDown

The rack units are numbered in the ascending orderfrom the highest to the lowest rack unit.

bottomUp

The rack units are numbered in the descending orderfrom 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 PX3 device.
config:#assetStrip <n> rackUnitNumberingOffset <number>

Variables:
•

•

608

<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<number> is a starting number for numbering rack units on the connectedasset strip. This value is an integer number.

Chapter 9: Using the Command Line Interface

Specifying the Asset Strip Orientation

This command syntax specifies the orientation of the asset strips connected to
the PX3 device. Usually you do not need to perform this command unless yourasset strips do NOT come with the tilt sensor, causing the PX3 unable to detect
the asset strips' orientation.
config:#assetStrip <n> assetStripOrientation <orientation>

Variables:••<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<orientation> is one of the options: topConnector or bottomConnector.
Orientation

Description

topConnector

This option indicates that the asset strip ismounted with the RJ-45 connector located on thetop.

bottomConnector

This option indicates that the asset strip ismounted with the RJ-45 connector located at thebottom.

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 <n> LEDColorForConnectedTags <color>

Variables:•<color> is the hexadecimal RGB value of a color in HTML format. The<color> variable ranges from #000000 to #FFFFFF.

609

Chapter 9: Using the Command Line Interface

Setting LED Colors for Disconnected Tags

This command syntax sets the LED color for all rack units on the connectedasset strip(s) to indicate the absence of a connected asset tag.
config:#assetStrip <n> LEDColorForDisconnectedTags <color>

Variables:•<color> is the hexadecimal RGB value of a color in HTML format. The<color> variable ranges from #000000 to #FFFFFF.

Rack Unit Configuration

A rack unit refers to a tag port on the asset strips. A rack unit configurationcommand 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 <n> <rack_unit> name "<name>"

Variables:
•

•

•

610

<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<rack_unit> 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 webinterface.
<name> is a string comprising up to 64 ASCII printable characters. The<name> variable must be enclosed in quotes when it contains spaces.

Chapter 9: Using the Command Line Interface

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 <n> <rack_unit> LEDOperationMode <mode>

Variables:•••<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<rack_unit> 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 webinterface.
<mode> 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 609) and Setting
LED Colors for Disconnected Tags (on page 610).
This is the default.

manualThis option enables selection of a different LED colorand LED mode for the specified rack unit.
When this option is selected, see Setting an LED Color
for a Rack Unit (on page 612) and Setting an LED
Mode for a Rack Unit (on page 612) to set different
LED settings.

611

Chapter 9: Using the Command Line Interface

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 <n> <rack_unit> LEDColor <color>

Variables:•••<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<rack_unit> 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 webinterface.
<color> is the hexadecimal RGB value of a color in HTML format. The<color> 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 609) and Setting LED
Colors for Disconnected Tags (on page 610).

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 <n> <rack_unit> LEDMode <mode>

Variables:
•

•

•

612

<n> is the number of the FEATURE port where the selected asset strip is
physically connected. For the PX3 device with only one FEATURE port, thenumber is always 1.
<rack_unit> 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 webinterface.
<mode> is one of the LED modes: on, off, blinkSlow or blinkFast.
Mode

Description

onThis mode has the LED stay lit permanently.

offThis mode has the LED stay off permanently.

Chapter 9: Using the Command Line Interface

Mode

Description

blinkSlow

This mode has the LED blink slowly.

blinkFast

This mode has the LED blink quickly.

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

613

Chapter 9: Using the Command Line Interface

Setting the Baud Rates

The following commands set the baud rate (bps) of the serial port labeled
CONSOLE / MODEM on the PX3 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 PX3 or power cycle the connected device for proper
communications.
Determine the CONSOLE baud rate:
config:#serial consoleBaudRate <baud_rate>

Note: The serial port bit-rate change is required when the PX3 works inconjunction 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 <baud_rate>

Variables:•<baud_rate> is one of the baud rate options: 1200, 2400, 4800, 9600,
19200, 38400, 57600, 115200.

Forcing the Device Detection Mode

This command forces the serial port on the PX3 to enter a specific device
detection mode.
config:#serial deviceDetectionType <mode>

Variables:•<mode> is one of the detection modes: automatic, forceConsole,forceAnalogModem, or forceGsmModem.
OptionDescription

automatic

The PX3 automatically detects the type of thedevice connected to the serial port.
Select this option unless your PX3 cannot
correctly detect the device type.

forceConsole

614

The PX3 attempts to recognize that theconnected device is set for the console mode.

Chapter 9: Using the Command Line Interface

OptionDescription

forceAnalogModem

The PX3 attempts to recognize that theconnected device is an analog modem.

forceGsmModem

The PX3 attempts to recognize that theconnected device is a GSM modem.

ExampleThe following command sets the CONSOLE baud rate of the PX3 device's serial
port to 9600 bps.
config:#serial consoleBaudRate 9600

Multi-Command Syntax
To shorten the configuration time, you can combine various configurationcommands in one command to perform all of them at a time. All combinedcommands must belong to the same configuration type, such as commands
prefixed with network, user modify, sensor externalsensor and so on.
A multi-command syntax looks like this:<configuration type> <setting 1> <value 1> <setting 2><value 2> <setting 3> <value 3> ...

Example 1 - Combination of ETH1's Activation, Configuration Method and IP

The following multi-command syntax configures IPv4 address, configuration
method and activation status for ETH1's network connectivity simultaneously.
config:#network ipv4 interface eth1 enabled true configMethod static
address 192.168.84.225/24

Results:•••

The ETH1 interface is enabled.
ETH1's configuration method is set to static IP address.
ETH1's IPv4 address is set to 192.168.84.225/24.

Example 2 - Combination of Upper Critical and Upper Warning Settings

The following multi-command syntax simultaneously configures Upper Criticaland Upper Warning thresholds for the RMS current of the 2nd overcurrent
protector.

615

Chapter 9: Using the Command Line Interface

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 parameterssimultaneously 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 Warningand 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 andenabled at the same time.

Actuator Control Operations
An actuator, which is connected to a dry contact signal channel of a Raritan
sensor package, 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 459).

616

Chapter 9: Using the Command Line Interface

Switching On an Actuator
This command syntax turns on one actuator.
#

control actuator <n> on

To quicken the operation, you can add the parameter "/y" to the end of thecommand, which confirms the operation.
#

control actuator <n> on /yVariables:•<n> is an actuator's ID number.
The ID number is available in the PX3 web interface or using the showcommand in the CLI. It is an integer starting at 1.

If you entered the command without "/y", a message appears, prompting you
to confirm the operation. Then:▪

Type y to confirm the operation, OR▪

Type n to abort the operation

Switching Off an Actuator
This command syntax turns off one actuator.
#

control actuator <n> off

To quicken the operation, you can add the parameter "/y" to the end of thecommand, which confirms the operation.
#

control actuator <n> off /yVariables:•<n> is an actuator's ID number.
The ID number is available in the PX3 web interface or using the showcommand in the CLI. It is an integer starting at 1.

If you entered the command without "/y", a message appears, prompting you
to confirm the operation. Then:▪

Type y to confirm the operation, OR

617

Chapter 9: Using the Command Line Interface▪

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 PX3, you can unblock them at the local
console.
To unblock a user:
1.

Access the CLI interface using any terminal program via a local connection.
See With HyperTerminal (on page 457).

2.

When the Username prompt appears, type unblock and press Enter.

3.

When the "Username to unblock" prompt appears, type the name of theblocked user and press Enter.

4.

A message appears, indicating that the specified user was unblocked
successfully.

Resetting the PX3
You can reset the PX3 to factory defaults or simply restart it using the CLI
commands.
Restarting the PDUThis command restarts the PX3. It is not a factory default reset.
To restart the PX3:
1.

Ensure you have entered administrator mode and the # prompt is
displayed.

2.

Type either of the following commands to restart the PX3.
#

reset unit-- OR --#

618

reset unit /yChapter 9: Using the Command Line Interface3.

If you entered the command without "/y" in Step 2, a message appears
prompting you to confirm the operation. Type y to confirm the reset.

4.

Wait until the reset is complete.

Note: Device reset will cause CLI communications over an "USB" connection to
be lost. Therefore, re-connect the USB cable after the reset is complete.
Resetting to Factory Defaults
The following commands restore all settings of the PX3 to factory defaults.
To reset PX3 settings after login, use either command:#

reset factorydefaults-- OR --#

reset factorydefaults /yTo reset PX3 settings before login:
Username:factorydefaults

See Using the CLI Command (on page 685) for details.
Note: Device reset will cause CLI communications over an "USB" connection to
be lost. Therefore, re-connect the USB cable after the reset is complete.

Network Troubleshooting
The PX3 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:▪

Administrator mode: The # prompt is displayed.

▪

User mode: The > prompt is displayed.

2.

Type diag and press Enter. The diag# or diag> prompt appears, indicatingthat you have entered the diagnostic mode.

3.

Now you can type any diagnostic commands for troubleshooting.

619

Chapter 9: Using the Command Line Interface

Quitting Diagnostic ModeTo quit the diagnostic mode, use this command:
diag>

exit

The # or > prompt appears after pressing Enter, indicating that you haveentered the administrator or user mode. See Different CLI Modes and Prompts(on page 459).
Diagnostic Commands
The diagnostic command syntax varies from command to command.

Querying DNS Servers

This command syntax queries Internet domain name server (DNS) informationof a network host.
diag>nslookup <host>

Variables:•<host> is the name or IP address of the host whose DNS information you
want to query.

Showing Network Connections

This command syntax displays network connections and/or status of ports.
diag>

netstat <option>

Variables:•

620<option> is one of the options: ports or connections.
OptionDescription

ports

Shows TCP/UDP ports.

connections

Shows network connections.

Chapter 9: Using the Command Line Interface

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 <host>

Variables:•<host> is the host name or IP address whose networking connectivity you
want to check.

Options:•

You can include any or all of additional options listed below in the pingcommand.
Options

Description

count <number1>

Determines the number of messages to be sent.
<number1> is an integer number between 1 and100.

size <number2>

Determines the packet size. <number2> is an
integer number in bytes between 1 and 65468.

timeout <number3>

Determines the waiting period before timeout.
<number3> is an integer number in seconds
ranging from 1 to 600.

The command looks like the following when it includes all options:diag>ping <host> count <number1> size <number2> timeout <number3>621

Chapter 9: Using the Command Line Interface

Tracing the RouteThis command syntax traces the network route between your PX3 and a
network host.
diag>

traceroute <host> <useICMP>

Variables:••<host> is the name or IP address of the host you want to trace.
<useICMP> is optional. It has only one value -- useICMP. Type useICMP
in the end of this command only when you want to use ICMP packets
rather than UDP packets.

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 thesame 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 acommand 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:

622

1.

Type initial letters or words of the desired command. Make sure the lettersor 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.

Chapter 9: Using the Command Line Interface

•

•

•

Examples:Example 1 (only one possible command):a.

Type the first word and the first letter of the second word of the"reset factorydefaults" command -- that is, reset f.

b.

Then press Tab or Ctrl+i to complete the second word.

Example 2 (only one possible command):a.

Type the first word and initial letters of the second word of the"security strongPasswords" command -- that is, security
str.

b.

Then press Tab or Ctrl+i to complete the second word.

Example 3 (more than one possible commands):a.

Type only the first two words of the "network ipv4 gateway
xxx.xxx.xxx.xxx" command -- that is, network ipv4.

b.

Then press Tab or Ctrl+i one or two times, a list of possible commands
displays as shown below.
gatewayc.

interfacestaticRoutes

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.

623

Chapter 10

Using SCP Commands
You can perform a Secure Copy (SCP) command to update the PX3 firmware,
do bulk configuration, or back up and restore the configuration.

In This Chapter
Firmware Update via SCP .................................................................................624
Bulk Configuration via SCP ................................................................................625
Backup and Restore via SCP..............................................................................626
Downloading Diagnostic Data via SCP ..............................................................627
Uploading or Downloading Raw Configuration Data ........................................629

Firmware Update via SCP
Same as any PX3 firmware update, all user management operations are
suspended and all login attempts fail during the SCP firmware update. For
details, see Updating the PX3 Firmware (on page 406).
Warning: Do NOT perform the firmware upgrade over a wireless network
connection.
To update the firmware via SCP:
1.

Type the following SCP command and press Enter.
scp <firmware file> <user name>@<device ip>:/fwupdate▪

<firmware file> is the PX3 firmware's filename. If the firmware file is
not in the current directory, you must include the path in thefilename.

▪

<user name> is the "admin" or any user profile with the Firmware
Update permission.

▪

<device ip> is the IP address or hostname of the PX3 where you want
to upload the specified file.

2.

Type the password when prompted, and press Enter.

3.

The system transmits the specified firmware file to the PX3, and shows thetransmission speed and percentage.

4.

When the transmission is complete, it shows the following message,
indicating that the PX3 starts to update its firmware now. Wait until the
upgrade completes.
Starting firmware update. The connection will be closed
now.

624

Chapter 10: Using SCP Commands

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

b.

Copy the configuration file to one or multiple destination PX3.

For detailed information on the bulk configuration requirements, see Bulk
Configuration (on page 411).
To save the configuration via SCP:
1.

Type the following SCP command and press Enter.
scp <user name>@<device ip>:/bulk_config.txt <filename>▪

<user name> is the "admin" or any user profile with Administrator
Privileges.

▪

<device ip> is the IP address or hostname of the PX3 whose
configuration you want to save.

▪

<filename> is the custom filename you assign to the "bulk_config.txt"
of the source PX3.

2.

Type the user password when prompted.

3.

The system saves the configuration from the PX3 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

2.

▪

<user name> is the "admin" or any user profile with Administrator
Privileges▪

<device ip> is the IP address of the PX3 whose configuration you wantto copy.

Type the user password when prompted.

625

Chapter 10: Using SCP Commands

3.

•

The system copies the configuration included in the file "bulk_config.txt"
to another PX3, and displays the following message.
Starting restore operation. The connection will beclosed now.
SCP examples:
Save operation:
scp admin@192.168.87.50:/bulk_config.txt today_config.txt•

Copy operation:
scp today_config.txt admin@192.168.87.47:/bulk_restore
Windows PSCP commands:

PSCP in Windows works in a similar way to the SCP.
•

Save operation:
pscp <user name>@<device ip>:/bulk_config.txt today_config.txt•

Copy operation:
pscp today_config.txt <user name>@<device ip>:/bulk_restore

Alternative of bulk configuration via SCP:
Both methods of uploading 'bulk configuration' file or 'raw configuration' file
via SCP can serve the purpose of bulk configuration. The only difference is thatyou 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 629)

Backup and Restore via SCP
To back up ALL settings of a PX3, including device-specific settings, you should
perform the backup operation instead of the bulk configuration.
You can restore all settings to previous ones after a backup file is available.
To back up the settings via SCP:
1.

Type the following SCP command and press Enter.
scp <user name>@<device ip>:/backup_settings.txt▪

626<user name> is the "admin" or any user profile with Administrator
PrivilegesChapter 10: Using SCP Commands▪

<device ip> is the IP address or hostname of the PX3 whose settings
you want to back up.

2.

Type the user password when prompted.

3.

The system saves the settings from the PX3 to a file named"backup_settings.txt."
To restore the settings via SCP:

1.

Type the following SCP command and press Enter.
scp backup_settings.txt <user name>@<device
ip>:/settings_restore▪

<user name> is the "admin" or any user profile with Administrator
Privileges▪

<device ip> is the IP address or hostname of the PX3 whose settings
you want to restore.

2.

Type the user password when prompted.

3.

The system copies the configuration included in the file"backup_settings.txt" to the PX3, and displays the following message.
Starting restore operation. The connection will beclosed 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 <user name>@<device ip>:/backup_settings.txt•

Restoration operation:
pscp backup_settings.txt <user name>@<device
ip>:/settings_restore

Downloading Diagnostic Data via SCP
You can download the diagnostic data via SCP.
To download the diagnostic data via SCP:
1.

Type one of the following SCP commands and press Enter.

627

Chapter 10: Using SCP Commands

Scenario 1: Use the default SCP port and default filename▪ SSH/SCP port is the default (22), and the accessed PX3 is a standalone device.
▪ The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot (.) in the endof the SCP command as shown below.
scp <user name>@<device ip>:/diag-data.zip .

Scenario 2: Specify a different SCP port but use the default filename▪ SSH/SCP port is NOT the default (22), or the accessed PX3 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 <port> <user name>@<device ip>:/diag-data.zip .

Scenario 3: Specify a new filename but use the default SCP port
▪ SSH/SCP port is the default (22), and the accessed PX3 is a standalone device.
▪ Renaming the diagnostic file is wanted.
scp <user name>@<device ip>:/diag-data.zip <filename>Scenario 4: Specify a different SCP port and a new filename▪ SSH/SCP port is NOT the default (22), or the accessed PX3 is a Port-Forwarding slave device.
▪ Renaming the diagnostic file is wanted.
scp -P <port> <user name>@<device ip>:/diag-data.zip <filename>628▪

<user name> is the "admin" or any user profile with Administrator
Privileges or "Unrestricted View Privileges" privileges.

▪

<device ip> is the IP address or hostname of the PX3 whose data you
want to download.

▪

<port> is the current SSH/SCP port number, or the port number of a
specific slave device in the Port-Forwarding chain.

▪

<filename> is the new filename of the downloaded file.

2.

Type the password when prompted.

3.

The system downloads the specified data from the PX3 onto yourcomputer.
▪

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.

Chapter 10: Using SCP Commands

SCP example:
scp admin@192.168.87.50:/diag-data.zip .
Windows PSCP command:
PSCP in Windows works in a similar way to the SCP.
▪

pscp -P <port> <user name>@<device
ip>:/diag-data.zip <filename>

Uploading or Downloading Raw Configuration Data
You can download the raw configuration data of a specific PX3 for review,
backup or modification.
After modifying or creating any raw configuration data, you can upload it to a
specific PX3 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 inthe config.txt file. See config.txt (on page 648).
Warning: Some configuration keys in the downloaded raw configuration arecommented out, and those must NOT be part of the configuration that will be
uploaded to any PX3. See Keys that Cannot Be Uploaded (on page 632).
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 PX3 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 <user name>@<device ip>:/raw_config.txt .

Scenario 2: Specify a different SCP port but use the default filename▪ SSH/SCP port is NOT the default (22), or the accessed PX3 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 <port> <user name>@<device ip>:/raw_config.txt .

629

Chapter 10: Using SCP Commands

Scenario 3: Specify a new filename but use the default SCP port
▪ SSH/SCP port is the default (22), and the accessed PX3 is a standalone device.
▪ Renaming the raw configuration file is wanted.
scp <user name>@<device ip>:/raw_config.txt <filename>Scenario 4: Specify a different SCP port and a new filename▪ SSH/SCP port is NOT the default (22), or the accessed PX3 is a Port-Forwarding slave device.
▪ Renaming the raw configuration file is wanted.
scp -P <port> <user name>@<device ip>:/raw_config.txt <filename>▪

<user name> is the "admin" or any user profile with Administrator
Privileges.

▪

<device ip> is the IP address or hostname of the PX3 whose data you
want to download.

▪

<port> is the current SSH/SCP port number, or the port number of a
specific slave device in the Port-Forwarding chain.

▪

<filename> is the new filename of the downloaded file.

2.

Type the password when prompted.

3.

The system downloads the specified data from the PX3 onto yourcomputer.
▪

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 PX3 to configure, with the default SCP port
▪ SSH/SCP port is the default (22), and the accessed PX3 is a standalone device.
▪ There is only one device to configure so a CSV file for device-specific settings is NOT needed.
scp <config file> <user name>@<device ip>:/raw_config_update

630

Chapter 10: Using SCP Commands

Scenario 2: Only one PX3 to configure, with a non-default SCP port
▪ SSH/SCP port is NOT the default (22), or the accessed PX3 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 <port> <config file> <user name>@<device ip>:/raw_config_update

Scenario 3: Multiple PX3 to configure, with the default SCP port
▪ SSH/SCP port is the default (22), and the accessed PX3 is a standalone device.
▪ There are multiple devices to configure so a CSV file for device-specific settings is needed
during the upload.
scp <dev_list file> <config file> <user name>@<device
ip>:/raw_config_update /match=<col>Scenario 4: Multiple PX3 to configure, with a non-default SCP port
▪ SSH/SCP port is NOT the default (22), or the accessed PX3 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 <port> <dev_list file> <config file> <user name>@<device
ip>:/raw_config_update /match=<dev_col>▪

<config file> is the filename of the custom raw configuration thatyou want to upload.

▪

<user name> is the "admin" or any user profile with Administrator
Privileges.

▪

<device ip> is the IP address or hostname of the PX3 where you want
to upload the specified file.

▪

<port> is the current SSH/SCP port number, or the port number of a
specific slave device in the Port-Forwarding chain.

▪

<dev_list file> is the name of the CSV file for configuringmultiple PX3 with device-specific settings. For this file's format, seedevices.csv (on page 650).
▪

▪

For device-specific settings in the <config file>, refer eachdevice-specific configuration key to a specific column in the<dev_list file>. See config.txt (on page 648).

<dev_col> comprises "serial:" or "mac:" and the number of thecolumn where the serial number or MAC address of each PX3 is in the
uploaded CSV file. This is the data based on which each device finds its
device-specific settings.
For example:

631

Chapter 10: Using SCP Commands•▪

If the second column contains each device's serial number, theparameter is then serial:2.

▪

If the seventh column contains each device's MAC address, theparameter is then mac:7.

SCP examples:
Raw configuration download example -scp admin@192.168.87.50:/raw_config.txt config.txt•

Raw configuration upload example with the configuration file only -scp config.txt
admin@192.168.87.50:/raw_config_update•

Raw configuration upload example with both configuration and device list
files -scp devices.csv config.txt
admin@192.168.87.50:/raw_config_update/match=serial:2
Windows PSCP commands:

PSCP in Windows works in a similar way to the SCP.
•

pscp -P <port> <user name>@<device ip>:/raw_config.txt<filename>•pscp -P <port> <CSV file> <config file> <username>@<device ip>:/raw_config_update /match=<col>
Alternative of bulk configuration via SCP:

Both methods of uploading 'bulk configuration' file or 'raw configuration' file
via SCP can serve the purpose of bulk configuration. The only difference is thatyou can configure device-specific settings with the upload of raw configuration
but not with the 'bulk configuration' file.
•

Bulk Configuration via SCP (on page 625)

Keys that Cannot Be Uploaded
The raw configuration downloaded from any PX3 contains a few configuration
keys that are commented out with either syntax below.

632

Comment syntax

Description#INTERNAL#

These keys are internal ones. They are NOT
user configurable settings.

#OLD/INVALID#

These keys are old or invalid ones.

Chapter 10: Using SCP Commands

Note that these configuration keys cannot be part of the configuration that you
will upload to any PX3. That is, they should be either not available or theyremain to be commented out in the configuration file you will upload.

633

Appendix A

Specifications

In This Chapter
Maximum Ambient Operating Temperature ....................................................634
Serial RS-232 "RJ-45" Port Pinouts ...................................................................634
Sensor RJ-45 Port Pinouts .................................................................................634
Feature RJ-45 Port Pinouts ...............................................................................635
Expansion RJ-45 Port Pinouts ...........................................................................636

Maximum Ambient Operating Temperature
The maximum ambient operating temperature (TMA) for PX3 is 60 degrees
Celsius.

Serial RS-232 "RJ-45" Port Pinouts
RJ-45 Pin/signal definition
Pin No.

SignalDirection

Description

1

RTS

OutputRequest to send

2

DTR

OutputData terminal ready3

TxD

OutputTransmit data

4

GND

―

Signal ground

5

DCD

Input

Data

6

RxD

Input

Receive data (data in)

7

DSR

Input

Data set ready

8

CTS

Input

Clear to send

Sensor RJ-45 Port Pinouts
RJ-45 Pin/signal definition
Pin No.

SignalDirection

Description

634

Appendix A: Specifications

RJ-45 Pin/signal definition
1

+12V

―

Power (fuse protected)

2

+12V

―

Power (fuse protected)

3

GND

―

Signal Ground4

RS485_DPbi-directional

Data Positive of the RS-485
bus

5

RS485_DN

bi-directional

Data Negative of the RS-485
bus

6

GND

―

Signal Ground7

1-wire―1-wire signal for Raritan
environmental sensor
packages

8

GND

―

Signal Ground

Note: A maximum of 500mA power is permitted for both pin 1 and pin 2
altogether.

Feature RJ-45 Port Pinouts
RJ-45 Pin/signal definition
Pin No.

SignalDirection

Description

1

DTR

OutputReserved

2

GND

―

Signal Ground

3

+5V

―

Power for CIM(200mA, fuse protected)
Warning: Pin 3 is only
intended for use with
Raritan devices.

4

TxD

OutputTransmit Data (Data out)

5

RxD

Input

Receive Data (Data in)

6

+12V

―

Warning: Pin 6 is only
intended for use with635

Appendix A: Specifications

RJ-45 Pin/signal definition
Pin No.

SignalDirection

Description
Raritan devices. Do NOT
connect.

7

GND

―

Signal Ground

8

DCD

Input

Reserved

Expansion RJ-45 Port Pinouts
RJ-45 Pin/signal definition

636

Pin No.

SignalDirection

Description

1

+12V

―

Power (fuse protected)

2

+12V

―

Power (fuse protected)

3

GND

―

Signal Ground4

RS485_DPbi-directional

Data Positive of the RS-485
bus

5

RS485_DN

bi-directional

Data Negative of the RS-485
bus

6

GND

―

Signal Ground

7

NC

―

No Connection

8

GND

―

Signal GroundAppendix B

Equipment Setup Worksheet
PX3 Series Model____________PX3 Series Serial Number____________OUTLET 1

OUTLET 2

OUTLET 3

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 4

OUTLET 5

OUTLET 6

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

MODEL

637

Appendix B: Equipment Setup Worksheet

638

OUTLET 7

OUTLET 8

OUTLET 9

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 10

OUTLET 11

OUTLET 12

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 13

OUTLET 14

OUTLET 15

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

Appendix B: Equipment Setup Worksheet

OUTLET 16

OUTLET 17

OUTLET 18

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

OUTLET 19

OUTLET 20

OUTLET 21

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

639

Appendix B: Equipment Setup Worksheet

OUTLET 22

OUTLET 23

OUTLET 24

MODEL

MODEL

MODEL

SERIAL NUMBERSERIAL NUMBERSERIAL NUMBER

USE

USE

USE

Types of adapters_________________________________________________________
Types of cables_________________________________________________________Name of software program_________________________________________________________

640

Appendix C

Configuration or Firmware Upgrade witha 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 PX3.
•••

Configuration changes
Firmware upgrade
Diagnostic data download

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 (onpage 655).

In This Chapter
Device Configuration/Upgrade Procedure .......................................................641
System and USB Requirements ........................................................................642
Configuration Files ............................................................................................643
Firmware Upgrade via USB ...............................................................................653

Device Configuration/Upgrade Procedure
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 644).
Therefore, firmware downgrade via USB is disallowed by default.
You can use one USB drive to configure or upgrade multiple PX3 devices one by
one as long as it contains valid configuration files.
To use a USB drive to configure the PX3 or upgrade firmware:
1.

Verify that both the USB drive and your PX3 meet the requirements. See
System and USB Requirements (on page 642).

2.

Prepare required configuration files. See Configuration Files (on page 643).

3.

Copy required configuration files to the root directory of the USB drive.
▪

For firmware upgrade, an appropriate firmware binary file is also
required.

4.

Plug the USB drive into the USB-A port of the PX3.

5.

The initial message shown on the front panel display depends on the firsttask performed by the PX3.

641

Appendix C: Configuration or Firmware Upgrade with a USB Drive▪

If no firmware upgrade task will be performed, a happy smiley isdisplayed 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 turngreen.

6.

▪

If the USB drive contains the firmware upgrade data, the PX3: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 653).

After the happy smiley appears, press one of the control buttons next tothe display for one second until the smiley disappears.
Tip: You can remove the USB drive and plug it into another PX3 device for
performing the same task(s) once the happy smiley or the firmware
upgrade message displays.

7.

Wait for several seconds until the PX3 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 theUSB 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.

••

PX3 system requirements:
There is at least one USB-A port available on your Raritan device.
Your PX3 must run firmware version 2.2.13 or later.
Note that the PX3 interpreted the USB drive's contents using the firmware
which was running when plugging the USB drive, not the new firmware
after firmware upgrade.

•
•

642

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

Appendix C: Configuration or Firmware Upgrade with a USB Drive

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

•

config.txt:
This file is used for configuring device settings. See config.txt (on page
648).

•

devices.csv:
This file is required only when there are device-specific settings to
configure for multiple PX3 devices. See devices.csv (on page 650).

Raritan provides a Mass Deployment Utility, which helps you quickly generate
all configuration files for your PX3. See Creating Configuration Files via Mass
Deployment Utility (on page 651).

643

Appendix C: Configuration or Firmware Upgrade with a USB Drive

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:

This section only explains common options in the file.
Note: To make sure all of the following options work fine, you must update yourPX3 to the latest firmware version.

•
•
•

user
A required option.
Specify the name of a user account with Administrator Privileges.
For PX3 with factory default configuration, set this option to admin.

•••

password
A required option.
Specify the password of the specified admin user.
For PX3 with factory default configuration, set this option to raritan.

Tip: You can add multiple user credentials to fwupdate.cfg. Each 'user' line
must be immediately followed by its 'password' line. PX3 will authenticate
listed user credentials one by one until one of them succeeds, or until all user
credentials fail.

644

Appendix C: Configuration or Firmware Upgrade with a USB Drive

•
•
•

•
•
•
•

•
•

•
•
•

•

logfileSpecify the name of a text file where the PX3 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 automaticallycreated.
If this option is not set, no log messages are recorded. The disadvantage isthat no feedback is available if the PX3 detects a problem with the USB
drive contents.
firmwareSpecify the name of a firmware binary file used to upgrade your PX3.
The specified firmware file must be compatible with your PX3 and have anofficial Raritan signature.
If the specified firmware file is the same as the current firmware version ofyour PX3, no firmware upgrade is performed.
The default is to NOT permit any firmware downgrade via USB drive 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.
configSpecify the name of the configuration file containing device settings.
The suggested filename is config.txt. See config.txt (on page 648).
device_list
Specify the name of the configuration file listing all PX3 devices toconfigure 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 650).
match
Specify a match condition for identifying a line or one PX3 device in thedevice 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 iseither serial for serial number or mac for MAC address.

▪

The number following the colon indicates a column in the devices.csv
file.

For example, mac:7 instructs the PX3 to search for the MAC address inthe 7th column of the "devices.csv" file.

645Appendix C: Configuration or Firmware Upgrade with a USB Drive••

The default value is serial:1, making the PX3 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 PX3 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 PX3.
Note: See Bulk Configuration (on page 411) 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
PX3.
Note: See Backup and Restore of Device Settings (on page 418) 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 PX3 is transmitted
to the USB drive.
The filename of the diagnostic data written into the USB drive is:diag_<unit-serial>.zip

646

Appendix C: Configuration or Firmware Upgrade with a USB Drive

•

•

•
•

•

•
•

•
•

•
•
•
•

•
•

The PX3 device beeps after it finishes writing the diagnostic data to theUSB drive.
tls_cert_file
Specify the filename of the wanted TLS server certificate. The filename cancontain a single placeholder ${SERIAL} that is replaced with the serial
number of the PX3.
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 cancontain a single placeholder ${SERIAL} that is replaced with the serial
number of the PX3.
This option should be used with tls_cert_file listed above.
This option is NOT supported by bulk configuration or backup/restore via
DHCP/TFTP.
execute_lua_script
Specify a Lua script file. For example:
execute_lua_script=my_script.lua
Script output will be recorded to a log file -<BASENAME_OF_SCRIPT>.<SERIAL_NUMBER>.log. Note this log file's size islimited on DHCP/TFTP.
A DHCP/TFTP-located script has a timeout of 60 seconds. After thatduration 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 threeseconds. Note that this is not implemented on DHCP/TFTP yet.
allow_downgradeThis parameter is required for any firmware downgrade via USB drive, orthe 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, suchas firmware downgrade via web interface.

647

Appendix C: Configuration or Firmware Upgrade with a USB Drive

config.txt
To perform device configuration using a USB drive, you must:••

Copy the device configuration file "config.txt" to the root directory of theUSB drive.
Reference the "config.txt" file in the config option of the "fwupdate.cfg"
file. See fwupdate.cfg (on page 644).

The file, config.txt, is a text file containing a number of configuration keys andvalues 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 PX3 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 PX3 model andfirmware version.
Tip: You can choose to encrypt important data in the "config.txt" file so thatpeople cannot easily recognize it, such as the SNMP write community string.
See Data Encryption in 'config.txt' (on page 652).

•

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 auser-chosen delimiter.
The following illustration declares a value in two lines. You can replace thedelimiter 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 theclosing EOF.

648

Appendix C: Configuration or Firmware Upgrade with a USB Drive

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 thefirmware'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 theUSB drive. See devices.csv (on page 650)

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 nameExample: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 652).
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_forwarding649

Appendix C: Configuration or Firmware Upgrade with a USB Drive

Tip:
You can also download "config.txt" from a specific PX3 or upload it to a specific
PX3 from anywhere in the world via Internet. See Raw Configuration Uploadand Download (on page 678).
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 PX3 device.
This file must be:•••

A CSV (comma-separated values) format file exported from a spreadsheet
application like Excel.
Copied to the root directory of USB drive.
Referenced in the device_list option of the "fwupdate.cfg" file. See
fwupdate.cfg (on page 644).

Every PX3 identifies its entry in the "devices.csv" file by comparing its serial
number or MAC address to one of the columns in the file.

•
•

•
•
•

Determine the column to identify PX3 devices:
By default, the PX3 searches for its serial number in the 1st column of"devices.csv".
To override the default, set the match option in the "fwupdate.cfg" file to adifferent 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 withanother 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

650

Appendix C: Configuration or Firmware Upgrade with a USB Drive

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.

2.

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 PX3 product section of Raritan website's Support
page (http://www.raritan.com/support/).

Launch Excel to open this utility.
Note: Other office suites, such as OpenOffice and LibreOffice, are notsupported.

3.

Read the instructions in the 1st worksheet of the utility, and make sure
Microsoft Excel's security level has been set to Medium or the equivalent
for executing unsigned macros of this utility.

4.

Enter information in the 2nd and 3rd worksheets.

5.

▪

The 2nd worksheet contains information required for fwupdate.cfg
and config.txt.

▪

The 3rd worksheet contains device-specific information for devices.csv.

Return to the 2nd worksheet to execute the export macro.
a.

In the Target Directory field, specify the folder where to generate theconfiguration files. For example, you can specify the root directory of aconnected USB drive.

b.

Click Export Lists to generate configuration files.

Verify that at least 3 configuration files are created - fwupdate.cfg, config.txt
and devices.csv. You are ready to configure or upgrade any PX3 with these files.
See Configuration or Firmware Upgrade with a USB Drive (on page 641).

651

Appendix C: Configuration or Firmware Upgrade with a USB Drive

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 andperformed by any PX3 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 651).

2.

Launch a terminal to log in to the CLI of any PX3 running version 3.2.20 orlater. See Logging in to CLI (on page 457).

3.

Type the encryption command and the value of the setting you want toencrypt.
▪

The value cannot contain any double quotes (") or backslashes (-).

▪

If the value contains spaces, it must be enclosed in double quotes.
# config encrypt <value>-- OR -# config encrypt "<value with spaces>"

4.

Press Enter. The CLI generates and displays the encrypted form of thetyped value.

5.

Go to the "config.txt" file and replace the chosen value with the encrypted
one by typing or copying the encrypted value from the CLI.

6.

Add the text "encrypted:" to the beginning of the encrypted setting.

7.

Repeat steps 3 to 6 for additional settings you intend to encrypt.

8.

Save the changes made to the "config.txt" file. Now you can use this file toconfigure any PX3 running version 3.2.20 or later. See Configuration or
Firmware Upgrade with a USB Drive (on page 641).
Illustration:
In this example, we will encrypt the word "private", which is the value ofthe SNMP write community in the "config.txt" file.

1.

652

In the CLI, type the following command to encrypt "private."

Appendix C: Configuration or Firmware Upgrade with a USB Drive

2.

The CLI generates and shows the encrypted form of "private."

3.

In the "config.txt" file, make the following changes to the SNMP write
community setting.
a.

Replace the word "private" with the encrypted value that CLI shows.

b.

Add "encrypted:" to the beginning of that setting.

Firmware Upgrade via USB
Firmware files are available on Raritan website's Support page(http://www.raritan.com/support/).
Note that if the firmware file used for firmware upgrade is the same as thefirmware version running on the PX3, 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 644).
To use a USB drive to upgrade the PX3:
1.

Copy the configuration file "fwupdate.cfg" and an appropriate firmware
file to the root directory of the USB drive.

2.

Reference the firmware file in the firmware option of the "fwupdate.cfg"
file.

3.

Plug the USB drive into the USB-A port on the PX3.

4.

The PX3 performs the firmware upgrade.
▪

The front panel display shows the firmware upgrade progress.

Tip: You can remove the USB drive and plug it into another PX3 forfirmware upgrade when the firmware upgrade message displays.
5.

It may take one to five minutes to complete the firmware upgrade,depending on your product.

6.

When the firmware upgrade finishes, the front panel display indicates thefirmware upgrade result.
▪

Happy smiley: Successful.
Depending on your product, the happy smiley looks like one of thefollowing. For the first diagram, its background color will turn green.

653

Appendix C: Configuration or Firmware Upgrade with a USB Drive▪

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, itsbackground color will turn red.

654

Appendix D

Bulk Configuration or Firmware Upgrade
via DHCP/TFTP
If a TFTP server is available, you can use it and appropriate configuration files toperform any or all of the following tasks for a large number of PX3 devices inthe same network.
••••

Initial deployment
Configuration changes
Firmware upgrade
Downloading diagnostic data

This feature is drastically useful if you have hundreds or even thousands of PX3
devices to configure or upgrade.
Warning: The feature of bulk configuration or firmware upgrade via
DHCP/TFTP only works on standalone PX3 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 641) or Raw Configuration Upload and Download (on page
678).

In This Chapter
Bulk Configuration/Upgrade Procedure ...........................................................656
TFTP Requirements ...........................................................................................657
DHCP IPv4 Configuration in Windows ..............................................................657
DHCP IPv6 Configuration in Windows ..............................................................667
DHCP IPv4 Configuration in Linux .....................................................................674
DHCP IPv6 Configuration in Linux .....................................................................676

655

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

Bulk Configuration/Upgrade Procedure
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 644).
Therefore, firmware "downgrade" via DHCP/TFTP is disallowed by default.
Steps of using DHCP/TFTP for bulk configuration/upgrade:1.

Create configuration files specific to your PX3 models and firmware
versions. See Configuration Files (on page 643) 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 basedon different firmware versions. If you have existing configuration files, it issuggested to double check with Raritan Technical Support for thecorrectness of these files prior to using this feature.
2.

Configure your TFTP server properly. See TFTP Requirements (on page
657).

3.

Copy ALL required configuration files into the TFTP root directory. If thetasks you will perform include firmware upgrade, an appropriate firmware
binary file is also required.

4.

Properly configure your DHCP server so that it refers to the file"fwupdate.cfg" on the TFTP server for your PX3.
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 657)▪

DHCP IPv6 Configuration in Windows (on page 667)▪

DHCP IPv4 Configuration in Linux (on page 674)▪

DHCP IPv6 Configuration in Linux (on page 676)

5.

Make sure all of the desired PX3 devices use DHCP as the IP configuration
method and have been directly connected to the network.

6.

Re-boot these PX3 devices. The DHCP server will execute the commands inthe "fwupdate.cfg" file on the TFTP server to configure or upgrade thosePX3 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.

656

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

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

If you are going to upload any PX3 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 andupload.
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 PX3 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 PX3 under IPv4.
a.

Right-click the IPv4 node in DHCP to select Define Vendor Classes.

657

Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTPb.

Click Add to add a new vendor class.

c.

Specify a unique name for this vendor class and type the binary codesof "Raritan PDU 1.0" in the New Class dialog.
The vendor class is named "Raritan PDU" in this illustration.

2.

658

Define one DHCP standard option - Vendor Class Identifier.

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

3.

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.

Add three options to the new vendor class "Raritan PDU" in the same
dialog.

659

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

660

a.

Select Raritan PDU in the "Option class" field.

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.

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

4.

c.

Click Add to add the second option. Type "pdu-update-control-file" inthe Name field, select String as the data type, and type 2 in the Codefield.

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.

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.

661

Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTPThe policy is named "PDU" in this illustration.

c.

662

Click Add to add a new condition.

Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTPd.

Select the vendor class "Raritan PDU" in the Value field, click Add andthen Ok.

e.

Click Next.

663

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

f.

664

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.

Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTPg.

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.

665

Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTPh.

Select "002 pdu-update-control-file" from the Available Options list,
and type the filename "fwupdate.cfg" in the "String value" field.

i.

Select "003 pdu-update-magic" from the Available Options list, andtype any string in the "String value" field. This third option/code is themagic 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 acombination of a date and a serial number.

666

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

Important: The magic cookie is transmitted to and stored in PX3 at the timeof executing the "fwupdate.cfg" commands. The DHCP/TFTP operation istriggered only when there is a mismatch between the magic cookie in DHCP
and the one stored in PX3. Therefore, you must modify the magic cookie'svalue in DHCP when intending to execute the "fwupdate.cfg" commands
next time.

DHCP IPv6 Configuration in Windows
For those PX3 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 PX3 under IPv6.

667

Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTPa.

Right-click the IPv6 node in DHCP to select Define Vendor Classes.

b.

Click Add to add a new vendor class.

c.

Specify a unique name for the vendor class, type "13742" in the"Vendor ID (IANA)" field, 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.

668

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

2.

Add three options to the "Raritan PDU 1.0" vendor class.
a.

Right-click the IPv6 node in DHCP to select Set Predefined Options.

669

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

670

b.

Select Raritan PDU 1.0 in the "Option class" field.

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.

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

3.

d.

Click Add to add the second option. Type "pdu-update-control-file" inthe Name field, select String as the data type, and type 2 in the Codefield.

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.

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.

671

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

c.

672

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.

Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTPd.

Select "00002 pdu-update-control-file" from the Available Options list,
and type the filename "fwupdate.cfg" in the "String value" field.

e.

Select "00003 pdu-update-magic" from the Available Options list, andtype any string in the "String value" field. This third option/code is themagic 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 acombination of a date and a serial number.

673

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

Important: The magic cookie is transmitted to and stored in PX3 at the timeof executing the "fwupdate.cfg" commands. The DHCP/TFTP operation istriggered only when there is a mismatch between the magic cookie in DHCP
and the one stored in PX3. Therefore, you must modify the magic cookie'svalue in DHCP when intending to execute the "fwupdate.cfg" commands
next time.

DHCP IPv4 Configuration in Linux
Modify the "dhcpd.conf" file for IPv4 settings when your DHCP server is runningLinux.
Required Linux IPv4 settings in DHCP:
1.

Locate and open the "dhcpd.conf" file of the DHCP server.

2.

The PX3 will provide the following value of the vendor-class-identifier
option (option 60).
▪

674

vendor-class-identifier = "Raritan PDU 1.0"

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

Configure the same option in DHCP accordingly. The PX3 accepts theconfiguration or firmware upgrade only when this value in DHCP matches.
3.

Set the following three sub-options in the "vendor-encapsulated-options"(option 43).
▪

code 1 (pdu-tftp-server) = the TFTP server's IPv4 address▪

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 acombination of a date and a serial number.

Important: The magic cookie is transmitted to and stored in PX3 at the timeof executing the "fwupdate.cfg" commands. The DHCP/TFTP operation istriggered only when there is a mismatch between the magic cookie in DHCP
and the one stored in PX3. Therefore, you must modify the magic cookie'svalue in DHCP when intending to execute the "fwupdate.cfg" commands
next time.

675Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP

IPv4 illustration example in dhcpd.conf:

DHCP IPv6 Configuration in Linux
Modify the "dhcpd6.conf" file for IPv6 settings when your DHCP server isrunning Linux.
Required Linux IPv6 settings in DHCP:
1.

Locate and open the "dhcpd6.conf" file of the DHCP server.

2.

The PX3 will provide the following values to the "vendor-class" option(option 16). Configure related settings in DHCP accordingly.

3.

676

▪

13742 (Raritan's IANA number)▪

Raritan PDU 1.0▪

15 (the length of the above string "Raritan PDU 1.0")

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"

Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP▪

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 acombination of a date and a serial number.

Important: The magic cookie is transmitted to and stored in PX3 at the timeof executing the "fwupdate.cfg" commands. The DHCP/TFTP operation istriggered only when there is a mismatch between the magic cookie in DHCP
and the one stored in PX3. Therefore, you must modify the magic cookie'svalue in DHCP when intending to execute the "fwupdate.cfg" commands
next time.
IPv6 illustration example in dhcpd6.conf:

677

Appendix E

Raw Configuration Upload and Download
You can modify any existing "config.txt", and then upload it to a specific PX3 formodifying 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 643) and config.txt(on page 648).
You download the raw configuration data from any PX3.

The downloaded raw configuration contains "almost" all of current settings on
your PX3.
Warning: Some configuration keys in the downloaded raw configuration arecommented out, and those must NOT be part of the configuration that will
be uploaded to any PX3. See Keys that Cannot Be Uploaded (on page 632).
Both configuration download and upload operations require the Administrator
Privileges.

In This Chapter
Downloading Raw Configuration ......................................................................678
Uploading Raw Configuration ...........................................................................680

Downloading Raw Configuration
There are three download methods:•••

Web browsers: See Download via Web Browsers (on page 678).
SCP or PSCP command: See Uploading or Downloading Raw Configuration
Data (on page 629).
CURL command: See Download via Curl (on page 679).

Download via Web Browsers
There are two scenarios by using web browsers.
URL containing login credentials:
To log in immediately while issuing the download request, type an URL
containing the login credentials in the web browser.
http(s)://<user>:<password>@<device IP>/cgi-bin/raw_config_download.cgi

678

Appendix E: Raw Configuration Upload and Download

Parameter

Description<user>

Any user name that has the Administrator Privileges.

<password>

The password of the specified user name.

<device IP>

Hostname or IP address of the PX3 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 thenprompt you to enter the login credentials.
http(s)://<device IP>/cgi-bin/raw_config_download.cgi▪

For example:

https://192.168.84.114/cgi-bin/raw_config_download.cgi

Download via Curl
If you have installed curl on your computer, you can download the raw
configuration from your PX3 by performing the curl command.
To download raw configuration from PX3 via curl:
1.

Type the following curl command in the command line interface.

curl -k https://<user>:<password>@<device
IP>/cgi-bin/raw_config_download.cgi > config.txt

Parameter

Description<user>

Any user name that has the Administrator Privileges.

679Appendix E: Raw Configuration Upload and Download

Parameter

Description<password>

The password of the specified user name.

<device IP>

Hostname or IP address of the PX3 whose raw
configuration you want to download.

2.

When the download is complete, a line indicates 100 in the first % column.

3.

Go to the directory where you perform the curl command to find the"config.txt" file.

Tip: In the above curl command, you can replace the filename "config.txt" withany filename you prefer.
Example:curl -k https://admin:raritan@192.168.84.114/cgi-bin/raw_config_download.cgi >config.txt

Uploading Raw Configuration
There are two upload methods:••

SCP or PSCP command: See Uploading or Downloading Raw Configuration
Data (on page 629).
CURL command: See Upload via Curl (on page 681).

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.

680

Appendix E: Raw Configuration Upload and Download

Upload via CurlIf curl is available on your computer, you can upload the raw configuration to
PX3 with the curl command.
There are two scenarios with the curl upload methods.
••

When there are NO device-specific settings involved, you upload theconfiguration file only, regardless of the number of PX3 devices to update.
When there are device-specific settings involved for updating more than
one PX3 devices, you must upload two files. including one configuration
file and one device list file.
To upload one configuration file only:

1.

Type the following curl command in the command line interface.

curl -k -F "config_file=@<config file>" https://<user>:<password>@<device
IP>/cgi-bin/raw_config_update.cgi

2.

Parameter

Description<user>

Any user name that has the Administrator Privileges.

<password>

The password of the specified user name.

<device IP>

Hostname or IP address of the PX3 whose raw
configuration you want to upload.

<config
file>

Filename of the configuration file.
▪ For the syntax, see config.txt (on page 648).

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

3.

After several seconds, PX3 reboots automatically. Changed settings takeeffect 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=@<config file>" -F "device_list_file=@<dev_list file>"
https://<user>:<password>@<device IP>/cgi-bin/raw_config_update.cgi?
match=<dev_col>681

Appendix E: Raw Configuration Upload and Download

Parameter

Description<user>,

Refer to the above table for explanation.

▪ For device-specific settings in the <config
file>, refer each device-specific configuration<device IP>,
key to a specific column in the <dev_list<configfile>. See config.txt (on page 648).
file><password>,<dev_list
file>

Filename of the device list file in CSV format.

<dev_col><dev_col> comprises "serial:" or "mac:" and thenumber of the column where the serial number or
MAC address of each PX3 is in the uploaded CSV file.
This is the data based on which each device finds its
device-specific settings.

▪ For the content format, see devices.csv (on page
650).

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

•

PX3 will reboot after Curl shows the return code 0. For details, refer toabove 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 681), curl will
return a code to indicate the result of the file upload.

682

Code

Description

0

Operation was successful.

Appendix E: Raw Configuration Upload and Download

Code

Description

1

An internal error occurred.

2

A parameter error occurred.

3

A raw configuration update operation is already running.

4

The file is too large.

5

Invalid raw configuration file provided.

6

Invalid device list file or match provided.

7

Device list file required but missing.

8

No matching entry in device list found.

9

Macro substitution error.

10

Decrypting value failed.

11

Unknown magic line.

12

Processing magic line failed.

683

Appendix F

Resetting to Factory Defaults
You can use either the reset button or the command line interface (CLI) to reset
the PX3.
Important: Exercise caution before resetting the PX3 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 423).

In This Chapter
Using the Reset Button .....................................................................................684
Using the CLI Command....................................................................................685

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 PX3. See Connecting the PX3 to a Computer(on page 31).

2.

Launch a terminal emulation program such as Kermit or PuTTY, and open awindow on the PX3. For information on the serial port configuration, see
Step 2 of Initial Network Configuration via CLI (on page 796).

3.

Press (and release) the Reset button of the PX3 device while pressing theEsc key of the keyboard several times in rapid succession. A prompt (=>)
should appear after about one second.

4.

Type defaults to reset the PX3 to its factory defaults.

5.

Wait until the reset is complete.
The following illustrates the reset button on Zero U PDUs. Port locations
may differ on your models.
▪

PX3 Zero U:

684

Appendix F: Resetting to Factory Defaults

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
PX3 to factory defaults. For information on CLI, see Using the Command LineInterface (on page 456).
To reset to factory defaults after logging in to the CLI:
1.

Connect to the PX3. See Logging in to CLI (on page 457) or Connecting the
PX3 to a Computer (on page 31).

2.

Launch a terminal emulation program such as HyperTerminal, Kermit, or
PuTTY, and open a window on the PX3. For information on the serial port
configuration, see Step 2 of Initial Network Configuration via CLI (on page
796).

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

reset factorydefaults-- OR --#

reset factorydefaults /y5.

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.

6.

Wait until the reset is complete.

To reset to factory defaults without logging in to the CLI:
The PX3 provides an easier way to reset the product to factory defaults in the
CLI prior to login.
1.

Connect to the PX3 and launch a terminal emulation program as describedin 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.

685

Appendix G

PX3 Models with Residual Current
Monitoring
PX3 models with residual current monitoring (RCM) detect and report residual
current - abnormal flow of current into the protective earth conductor.
Residual current is a safety issue since electrocution is possible if the rack or
any device within it is touched.
Depending on the model you purchase, some models report residual current by
inlet only, while some models report residual current by inlet pole. In addition,some models are able to report residual DC current in addition to the total
residual current.
Warning: PX3 RCM cannot disconnect power to stop residual current flow.
Devices like RCD and GFI disconnect power when residual current is
detected, but the PX3 with RCM are NOT RCD or GFI protected devices.

In This Chapter
RCM Current Sensor .........................................................................................686
RCM State Sensor .............................................................................................687
Compliance with IEC 62020 ..............................................................................688
RCM Self-Test....................................................................................................689
Web Interface Operations for RCM ..................................................................690
Front Panel Operations for RCM ......................................................................696
RCM SNMP Operations .....................................................................................699
CLI Operations for RCM ....................................................................................700

RCM Current Sensor
The RCM current sensor detects current imbalance which indicates current isflowing to ground. The sensor cannot determine the exact location. It justreports the sum of all residual current in the PDU and devices plugged into it,which is either per inlet or per inlet pole, depending on the model.
Most equipment leaks a small amount of current and the UL/IEC 60950-1
standard for IT equipment permits up to 3mA. For example, if a PDU has one
RCM sensor on its inlet and twenty plugged-in devices -- each leaking 1mA, theRCM sensor then reports the sum - 20mA.
Raritan offers two types of RCM sensors.

686

Appendix G: PX3 Models with Residual Current Monitoring

RCM sensor type

Description

PDU models

Type A

Detects AC leakage and is sensitive down to 6mA
leakage.

Models ending in
M5.

Type B

Detects AC and DC leakage and is sensitive down to
14mA.

Models ending in:Type B has an RCM "DC" sensor in addition to the RCM
sensor. Differences of the two sensors are described
below.

▪ M11
▪ M18

▪ RCM sensor reports the sum of all residual current,
including AC and DC current.
▪ RCM DC sensor reports the residual DC current only.
Important: When your PX3 enters the power-sharing mode, the RCM sensor
enters the 'unavailable' state and will not work until the power-sharing modeends. For information on power sharing, see Power-Sharing Restrictions andConnection (on page 43).

RCM State Sensor
The RCM state sensor reports events based on residual current thresholds or
RCM self-test failure.
The RCM state is always determined by the magnitude of "total" residual
current values per inlet or per inlet pole as explained below.
••

For Type A, it is the sum of residual AC current.
For Type B, it is the sum of residual AC and DC current.
In other words, the RCM state is NOT determined by the residual DC
current detected by the separate RCM "DC" sensor on Type B models.
RCM state

Description

normalResidual current is within normal range.

warning

Residual current is above warning level.

criticalResidual current is above critical level.
In addition to an event, the CRITICAL state causes the PX3 front
panel to display a special error message.

self-test active

RCM diagnostics are running.

failureRCM current sensor has malfunctioned. Contact Raritan TechnicalSupport.

Note: The factory default is to disable the Warning state. To define and enable
this state, see Setting RCM Current Thresholds (on page 692).

687

Appendix G: PX3 Models with Residual Current Monitoring

Important: When your PX3 enters the power-sharing mode, the RCM sensor
enters the 'unavailable' state and will not work until the power-sharing modeends. For information on power sharing, see Power-Sharing Restrictions andConnection (on page 43).

Compliance with IEC 62020
IEC 62020 is an international standard for Residual Current Monitors. All PX3
with RCM are IEC 62020 compliant.
IEC 62020 uses the term rated residual operating current (IΔn) to specify
residual current, equal to or above which causes an alarm. IEC 62020
recommends preferred values 6mA, 10mA, 30mA, 100mA, 300mA and 500mA.
In the PX3 with RCM, IΔn is specified using the Critical Rated Residual Operating
Current threshold.
IEC 62020 uses the term residual non-operating current (IΔno) to specify
residual current, below which does not cause an alarm. IEC 62020 specifies
IΔno be no higher than 0.5 IΔn. In PX3 with RCM, IΔno is set using the RCM
Deassertion Hysteresis and this value must be no higher than 0.5 the RCM
critical threshold.
PX3 with RCM allows you to establish an optional WARNING state, which is notpart of the IEC 62020 specification. PX3 RCM remains IEC 62020 compliant
when the RCM deassertion hysteresis is configured properly.
IEC 62020 specification

PX3 with RCM characteristics

Method of operation

Dependent on line voltage. RCM only functions if line
voltage is present.

Type of installation

PX3 with flexible line cords and plugs are for mobile
installation and corded connection.

Current paths

1-phase PX3 are two current paths RCM.
3-phase 3W+PE are three current paths RCM.
3-phase 4W+PE are four current paths RCM.

688

Ability to adjust residual
operating current

Adjustable.

Adjustable time delay

Non-adjustable time delay.

Protection against external
influence

Enclosed-type RCM.

Method of mounting

Panel board type RCM.

Method of connection

Not associated with mechanical mounting.

▪ Type A: 6mA-500mA.
▪ Type B: 14mA-300mA.

Appendix G: PX3 Models with Residual Current Monitoring

IEC 62020 specification

PX3 with RCM characteristics

Connection of load
conductors

Monitored line is directly connected.

Fault indicating means

Visual, with other output signals.

Ability to directly discriminate Directionally non-discriminating.
Rated residual operating
current

0.5A (highest value).

Residual currents with direct
current components

Model dependent.
▪ Models ending in M5 are Type A.
▪ Models ending in M11 or M18 are Type B.

RCM Self-Test
PX3 with RCM have a built-in self-test feature that performs these functions:•••

When residual current is less than 3mA, 15mA is momentarily added todetermine whether the low reading is due to a faulty sensor. The residual
current added is done in a safe manner which does not run current into
ground or pose operator risk.
The RCM state sensor changes to SELF-TEST and then back to its originalstate if self-test passes, or to the FAILURE state if self-test fails. These statechanges are useful to verify your monitoring systems (SNMP, syslog, oremail) are correctly set up to receive PX3 event notifications.
For Type B "M18" models, the self-test feature will perform tests on allpoles of the selected inlet simultaneously.

Note: If self-test fails, the FAILURE state persists until another self-test runs andpasses.

689

Appendix G: PX3 Models with Residual Current Monitoring

Web Interface Operations for RCM
The RCM on PX3 is either an inlet sensor or an inlet pole sensor. To view,
configure or run self-test, click Inlet in the Menu (on page 167).

Checking RCM State and Current
A section titled 'Residual Current Monitor' is available on the Inlet page,
showing both the present RCM state and residual current.
Important: When your PX3 enters the power-sharing mode, the RCM sensor
enters the 'unavailable' state and will not work until the power-sharing modeends. For information on power sharing, see Power-Sharing Restrictions andConnection (on page 43).
To check RCM state and current on the Inlet page:1.

690

Click Inlet.

Appendix G: PX3 Models with Residual Current Monitoring

2.

Locate the Residual Current Monitor section on the Inlet page.
▪

RCM State: There are five states - normal, warning, critical, self-test
active and failure. For more information, see RCM State Sensor (onpage 687).

▪

Residual Current:
For Type A, it is the sum of residual AC current.
For Type B, it is the sum of residual AC and DC current.

For Type B "M18" models, the listed fields are available per inlet pole asshown below. Besides, a Type B model, either "M11" or "M18", is able todisplay the residual DC current.

Note: To determine the RCM's normal, warning and critical levels, configure theRCM current thresholds. See Setting RCM Current Thresholds (on page 692). To
configure the residual DC current thresholds, see Setting RCM DC Current
Thresholds (on page 694).

691

Appendix G: PX3 Models with Residual Current Monitoring

RCM Critical State Alarm

When a PX3 device's RCM sensor enters the Critical state, the PX3 beeps andthis alarm is displayed in the Alerted Sensors section of the Dashboard page.
Note that only the RCM sensor will cause the PDU to beep while RCM "DC"sensor does not cause the PDU to beep regardless of its sensor state.
Warning: RCM sensors do not work in power-sharing mode. See
Power-Sharing Restrictions and Connection (on page 43).

NumberDescription
The magnitude of residual current reported by the RCM current
sensor.
Critical state reported by the RCM state sensor.

Tip: RCM critical state is also indicated on the Inlet page or the Internal Beeper
section of the PDU page. See Checking RCM State and Current (on page 690) orInternal Beeper State (on page 183).
Setting RCM Current Thresholds
The RCM current thresholds define the critical, warning and normal range ofresidual current.
••

For Type A, RCM current thresholds are the thresholds of residual AC
current.
For Type B, they are the thresholds of total residual current including AC
and DC current.

Tip: To configure the thresholds of residual DC current, if the RCM DC sensor isavailable on your PDU, see Setting RCM DC Current Thresholds (on page 694).
To configure RCM current thresholds and run self-test:
1.

692

Click Inlet to open the Inlet page.

Appendix G: PX3 Models with Residual Current Monitoring

2.

In the Residual Current Monitor section, click Setup.

3.

Set up RCM thresholds.

a.

Enable or disable the Residual Operating Current, which is the criticalthreshold. Residual current greater than this value triggers Critical
RCM state.

b.

Enable or disable the RCM warning threshold. Residual current greaterthan this value triggers Warning RCM state.

c.

Determine the residual current decrease to end Warning or Critical
RCM state.
For a model that detects residual current per inlet pole, the above
fields are available for each pole. Configure them one by one.

d.
4.

Click Save.

Click 'Start Self Test' to run RCM self-test.

Scheduling RCM Self-Test
You can have the PX3 run RCM self-test automatically at a regular time intervalor on a specific date and time. See Scheduling an Action (on page 354) for theprocedure and select "Start residual current monitor self test" to create thescheduled RCM self-test action.
Note: For Type B "M18" models, the self-test feature will perform tests on allpoles of the selected inlet simultaneously.

693

Appendix G: PX3 Models with Residual Current Monitoring

Disabling or Enabling Front Panel RCM Self-Test
You can enable or disable the function of performing the RCM self-test byoperating the front panel buttons. By default, this function is enabled.
To disable or enable the front panel RCM self-test:
1.

Choose Device Settings > Front Panel.

2.

Do either below:

3.

▪

To disable this function, deselect the "Perform RCM self-test"
checkbox.

▪

To enable this function, select the "Perform RCM self-test" checkbox.

Click Save.

Setting RCM DC Current Thresholds
RCM DC current sensors are available on Type B models only. See RCM
Current Sensor (on page 686).
You can also configure upper thresholds for RCM DC current sensors so that an
alarm will be displayed on the page of Dashboard (on page 171) when RCM DC
sensors enter an alerted state.
To configure RCM DC's upper thresholds:

694

1.

Click Inlet to open the Inlet page.

2.

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

Appendix G: PX3 Models with Residual Current Monitoring

3.

Click the desired sensor (required), and then click Edit Thresholds. For
example, select "L1 Residual DC Current".

4.

Make changes as needed.
▪

To enable any threshold, select the corresponding checkbox.

▪

Type a new value in the accompanying text box.

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

Click Save.

695

Appendix G: PX3 Models with Residual Current Monitoring

Front Panel Operations for RCM
The front panel LCD display shows an alarm message when the RCM enters thecritical state. Besides, you can operate the LCD display to check the RCM status.
This section introduces the RCM information shown on the dot-matrix LCD
display.
Note: For RCM information shown on the character LCD display of an old PX3model, see RCM Information (on page 718).
LCD Message for RCM Critical StateIn the RCM critical state, the PDU beeps and the LCD display indicates the RCM
critical state.
The RCM alarm information continues to display as long as RCM is in a criticalstate. The top and bottom bars on the display turn red at the same time.
RCM alarm information in the critical state:
1.

The LCD display shows two or three pieces of information for the inlet or
inlet pole with the RCM alarm:▪

RCM State: Critical.

▪

Residual Current: Residual current value in Amps.

▪

▪

For Type A, it is the sum of residual AC current.

▪

For Type B, it is the sum of residual AC and DC current.

Residual DC Current: If your PDU is an RCM Type B model, an
additional DC-only residual current value is also reported on the LCD.

If your PX3 has more than one inlet, only the inlet which has the RCM
alarm enters the critical state.

696

Appendix G: PX3 Models with Residual Current Monitoring

2.

If needed, you can press
to perform RCM self-test for this inlet. For
details, see steps 4 to 5 in the topic titled Running RCM Self-Test (on page698).

Checking RCM States and Current
You can retrieve RCM information from the LCD display.
To check RCM information:
1.

Press

or

to access the Main Menu (on page 124).

2.

Press

or

to select "Residual Current", and press

3.

The LCD display shows two or three pieces of information for Inlet 1 asshown below, or a list of inlet poles.
If a list of inlet poles displays, press
one inlet pole.

or, and then▪

RCM State: Normal or Warning.

▪

Residual Current: Residual current value in Amps.

▪

▪

For Type A, it is the sum of residual AC current.

▪

For Type B, it is the sum of residual AC and DC current.

.

to select

Residual DC Current: If your PDU is an RCM Type B model, an
additional DC-only residual current value is also reported on the LCD.

If your PX3 has more than one inlet, a list of inlets is displayed, along witheach inlet's RCM state and reading(s).
4.

To return to the Main Menu, press.

697

Appendix G: PX3 Models with Residual Current Monitoring

Running RCM Self-Test
You can perform the RCM self-test by operating the front panel buttons.
For Type B "M18" models, the self-test feature will perform tests on all poles ofthe selected inlet simultaneously.
To disable or enable this front panel function, see Disabling or Enabling Front
Panel RCM Self-Test (on page 694). By default, this function is enabled.
To run RCM self-test:
1.

Press

or

to access the Main Menu (on page 124).

2.

Press

or

to select "Residual Current," and press

3.

The LCD display shows the RCM information of the inlet(s) or inlet poles.
▪

If your PDU shows multiple inlets or inlet poles, press
select the desired inlet or inlet pole and press

4.

Press

5.

A confirmation message displays. By default, Yes is selected.

to perform RCM self-test on the selected inlet.

To execute the RCM self-test, press▪

To cancel the RCM self-test, do either of the following:- Press- Press

698

or

.

▪

.

.
or

to select No and then press

.

.

to

Appendix G: PX3 Models with Residual Current Monitoring

6.

After completing the RCM self-test, the LCD display indicates the RCM
self-test result: passed or failed.

7.

Press

8.

Do one of the following:or

to return to the RCM information page.

▪

To return to the Main Menu, press▪

To perform RCM self-test for additional inlets, press
select a different inlet and repeat the same steps.

.
or

to

RCM SNMP Operations
Make sure you have the correct version of SNMP MIB. The PX3 supports the
RCM feature as of firmware version 2.5.20. See Downloading SNMP MIB (onpage 452) for details.
RCM Trap
An InletSensorStateChange trap is sent when the RCM state sensor changes.
InletSensorStateChange is the generic trap sent for all inlet sensors. The specifictrap for RCM has the object typeOfSensor set to 27. Included with the trap aremeasurementsInletSensorValue (the residual current value) andmeasurementsInletSensorState (the RCM state that caused the trap).

699

Appendix G: PX3 Models with Residual Current Monitoring

RCM Residual Current and State Objects
The inletSensorMeasurementsTable contains entries for RCM residual current
and states.
Use index sensorType = 26 to retrieve the row for residual current. Column
measurementsInletSensorValue contains the residual current.
Use index sensorType = 27 to retrieve the row for RCM state. Column
measurementsInletSensorState contains the RCM state enumeration value.
Setting RCM Thresholds
The inletSensorConfigurationTable contains a row for configuring RCM
thresholds. Use index sensorType = 26 to reference the row. Columns
inletSensorUpperWarningThreshold, inletSensorUpperCriticalThreshold andinletSensorHysteresis set values for RCM warning, critical and deassertion
hysteresis respectively.
Running RCM Self-Test
To initiate RCM self-test using SNMP, set column rcmState to value 29 in table
rcmSelfTestTable.
For Type B "M18" models, the self-test feature will perform tests on all poles ofthe selected inlet simultaneously.

CLI Operations for RCM
For information on entering and using the CLI, see Using the Command LineInterface (on page 456).

700

Appendix G: PX3 Models with Residual Current Monitoring

Showing Residual Current Monitoring Information
This command syntax shows the residual current monitoring (RCM) information,
which is only available on the models with RCM. The information displayed
include the RCM current, state and thresholds.
For Type B "M18" models, this command shows the information of all RCM
sensors of the same inlet at a time.
#show residualCurrentMonitor <n>Variables:•<n> is one of the options: all, or a number.
OptionDescription

all

Displays the RCM information of all inlets.
Tip: You can also type the command without adding
this option "all" to get the same data.

A specific inlet
number

Displays the RCM information of the specified inlet
only.
An inlet number needs to be specified only when there
are more than 1 inlet on your PDU.

••

Tip -- other RCM-related "show" commands:
For models detecting residual current per inlet, see Inlet Sensor Threshold
Information (on page 474)
For models detecting residual current per inlet pole, see Inlet Pole Sensor
Threshold Information (on page 476)

Setting RCM Current Thresholds
Warning Rated Residual Operating Current is the upper warning threshold of
the PX3 RCM sensor, and Critical Rated Residual Operating Current is the upper
critical threshold of the RCM sensor. These thresholds are set in theconfiguration mode. See Entering Configuration Mode (on page 493).
Note: A residual current sensor's LOWER warning and LOWER critical thresholds
do NOT affect the operations of the RCM state sensor so you can ignore them.
For Type B "M18" models, this command configures all RCM sensors of thesame inlet simultaneously.
To configure the RCM's Critical level:701

Appendix G: PX3 Models with Residual Current Monitoring

config:#residualCurrentMonitor <n> criticalRatedResidualOperatingCurrent <value>
Note: The PX3 triggers events when residual current values are above (but notequal to) thresholds. For example, you would set the critical threshold to 29mA
to specify the IEC 62020 IΔn of 30mA. See Compliance with IEC 62020 (on page688).
To configure the RCM's Warning level:

config:#residualCurrentMonitor <n> warningRatedResidualOperatingCurrent <value>
To configure the RCM's deassertion hysteresis:

config:#residualCurrentMonitor <n> deassertionHysteresis <hy_value>

Variables:••<n> is the number of the inlet where the desired RCM current sensor ismounted. For a single-inlet PDU, this number is always 1.
<value> is one of the options: enable, disable or a numeric value measured
in amperes.
OptionDescription

enableEnables the specified RCM current threshold for the
specified inlet.

disableDisables the specified RCM current threshold for the
specified inlet.

A numeric value

Sets a value for the specified RCM current threshold of
the specified inlet and enables this thresholdsimultaneously.
Note that this value is measured in A, not mA.
Therefore, to set the value to 6mA, type 0.006.

•

•
•

702

<hy_value> is a numeric value measured in amperes (A), not milliamperes(mA). For example, to set the value to 15mA, type 0.015.

Tip -- other RCM-related "threshold-setting" commands:
For models detecting residual current per inlet, see Commands for Inlet
Sensors (on page 589)
For models detecting residual current per inlet pole, see Commands for
Inlet Pole Sensors (on page 592)

Appendix G: PX3 Models with Residual Current Monitoring

Setting Front Panel RCM Self-Test
You can enable or disable the front panel RCM self-test function via CLI in
addition to the web interface.
To enable the front panel RCM self-test:#

security frontPanelPermissions add rcmSelfTest

To disable the front panel RCM self-test:#

security frontPanelPermissions remove rcmSelfTest

Running RCM Self-Test
You can perform RCM self-test for a specific inlet via CLI. After the self-test
finishes, the test result is shown: pass or fail.
For Type B "M18" models, the self-test feature will perform tests on all poles ofthe selected inlet simultaneously.
To perform RCM self-test:#

rcm selfTest inlet <n>Variables:•<n> is the inlet's number. For a single-inlet PDU, <n> is always 1.

Degaussing RCM Type B Sensors
Only the models with RCM 'Type B' sensors support degaussing the RCM
sensors. Those with RCM Type A sensors do NOT support this feature.
You can degauss the RCM sensor after a current surge, such as a short circuit.
For Type B "M18" models, this command will degauss all RCM sensors
simultaneously.
To degauss RCM Type B sensors:#

rcm degauss703

Appendix H

Old Generations of PX3 Models
There are two types of old PX3 PDUs.
••

PX3 phase I models
PX3 phase II models

Old PX3 PDUs are different from PX3 with iX7™ controller in terms of thefollowing designs:••

RS-232 port is a DB9 connector.
Have only one Ethernet port.
▪

••

Therefore, the networking-related commands in CLI do not have theoptions of 'eth1' and 'eth2'. Instead it uses the option of 'ethernet' torefer to its ETHERNET port.

The controller is not replaceable.
Have no EXPANSION port for the power-sharing feature.

In This Chapter
PX3 'Phase II' Front Panel Display ..................................................................... 704
PX3 'Phase I' Front Panel Display ...................................................................... 705
Serial RS-232 "DB9" Port Pinouts ..................................................................... 720

PX3 'Phase II' Front Panel Display
The following diagram is the Zero U model of PX3 'phase II' PDUs.

The operation of its front panel button is similar to the front panel operation of
PX3 with iX7™ controller (PX3-iX7). See Operating the Dot-Matrix LCD Display(on page 123).
The major difference between PX3 'phase II' and PX3-iX7 is the symbols of theircontrol buttons.
•

functions the same as PX3-iX7's.

•

functions the same as PX3-iX7's.

•

functions the same as PX3-iX7's.

•

functions the same as PX3-iX7's.

704

Appendix H: Old Generations of PX3 Models

PX3 'Phase I' Front Panel Display
The following diagram is the Zero U model of PX3 'phase II' PDUs.

Its LCD display on the panel can show the reading or status of different
components on the PX3, or its MAC address and IP address.
It consists of:••

A character LCD display
Control buttons

Overview of the LCD Display
Different types of information are shown in different sections of the LCD
display. The diagram indicates the sections.

SectionInformation shown
The selected mode and target, such as INLET 1, OUTLET 1,
SENSOR 1, SENSOR 2, and so on.

705

Appendix H: Old Generations of PX3 Models

SectionInformation shown
The following information is displayed:••

Readings, data or state of the selected target.
During the firmware upgrade, "FUP" is displayed.

Two types of information may be displayed:••

The "ALARM" status of the selected target.
The selected inlet line number if your PX3 is a 3-phasemodel.

The measurement unit of the displayed data, such as % or.
This section indicates:••

The Asset Strip mode if an asset strip has been connectedto the PX3.
The device's USB-cascading state - MASTER or SLAVE. If it
is a standalone device, neither MASTER nor SLAVE isdisplayed.

Note: During the firmware upgrade, some PX3 models may show bx in thesection 1 to indicate the relay or meter board numbered x is being updated.
Control Buttons
There are four control buttons.

••

Up and Down buttons for selecting a specific target, which can be an inlet,
outlet, overcurrent protector, environmental sensor or a device setting
MODE button for switching between various modes, including:- Inlet mode
- Outlet mode
- Overcurrent Protector mode
- Device mode
- Sensor mode
- Asset Strip mode, indicated by the word ASSET, for showing the asset
strip information
See Overview of the LCD Display (on page 705) for details.

706

Appendix H: Old Generations of PX3 Models•

FUNC (Function) button for switching between different data of theselected target, such as the current, voltage or power readings of aparticular outlet

Operating the LCD Display
After powering on or resetting this product, the LCD display panel shows thecurrent reading of OUTLET 1 by default before you select a different target.
Outlet Information

The Outlet mode is displayed as "OUTLET" on the LCD display. By default thePX3 displays the current reading of OUTLET 1.
Below illustrates the outlet information shown on the LCD display.

SectionExample information
The selected target is OUTLET 3.
This outlet's current reading is 2 amps.
"MASTER" indicates the PX3 is the master device in acascading chain.
For a slave device, it shows "SLAVE" instead.
Note: "MASTER/SLAVE" information is only available in Port
Forwarding mode.
The measurement unit is A (Amp), indicating that the readingis the RMS current.

To display a single-phase outlet's information:
1.

By default this product enters the Outlet mode. If not, press the MODE
button until the word "OUTLET" is displayed.

2.

In the Outlet mode, press the Up or Down button until the desired outlet's
number is displayed at the top of the LCD display.

3.

Press the FUNC button to switch between voltage, active power andcurrent readings of the selected target.
▪

A is displayed for the current reading. A means Amp.

▪

V is displayed for the voltage reading. V means Volt.

707

Appendix H: Old Generations of PX3 Models▪

W is displayed for the power reading. W means Watt.

If the word "ALARM" appears below the reading, it means the currently
displayed reading already reaches or crosses the upper or lower
thresholds.
To display a 3-phase outlet's information
1.

In the Outlet mode, press the Up or Down button until the desired 3-phaseoutlet is selected.

2.

While that 3-phase outlet is being selected, press the Up or Down button
to switch between each line, indicated as L1, L2 or L3 at the bottom of thedisplay.

3.

When the desired line is being displayed, press the FUNC button to switch
between voltage, active power and current readings of this particular line.

4.

▪

A is displayed for the current reading. A means Amp.

▪

V is displayed for the voltage reading. V means Volt. When voltage isselected, L1-L2, L2-L3, or L3-L1 is displayed at the bottom of thedisplay.

▪

W is displayed for the power reading. W means Watt.

To show the unbalanced load and active power of this 3-phase outlet, do
the following:a.

Switch to the current reading of L1.

b.

Press the Down button until '%' or 'W' is displayed to the right of thedisplay. Make sure NONE of the lines (L1, L2, L3, L1-L2, L2-L3 or L3-L1)
is displayed at the bottom of the display.
▪

Unbalanced load - % is displayed for the unbalanced current value.

▪

Active power - W is displayed for the power reading. W means
Watt.

Inlet Information

The Inlet mode is displayed as "INLET" on the LCD display. Below illustrates theinlet information shown on the LCD display.

SectionExample information
The selected target is INLET 1.

708

Appendix H: Old Generations of PX3 Models

SectionExample information
This inlet's L1 current reading is 23 amps.
The selected inlet line is L1.
"MASTER" indicates the PX3 is the master device in acascading chain.
For a slave device, it shows "SLAVE" instead.
Note: "MASTER/SLAVE" information is only available in Port
Forwarding mode.
The measurement unit is A (ampere).

To display an inlet's information:
1.

Press the MODE button until the term "INLET" is displayed.

2.

On a multi-inlet model, press the Up or Down button until the desired
inlet's number is displayed at the top.

3.

If your PX3 is a 3-phase model, the selected inlet line is indicated below thereading. Press the Up or Down button until the desired inlet line's number(L1, L2, L3, L1-L2, L2-L3 or L3-L1) is shown.

4.

Press the FUNC button to switch between voltage, active power andcurrent readings of the selected target.
▪

A is displayed for the current reading. A means Amp.

▪

V is displayed for the voltage reading. V means Volt.

▪

W is displayed for the power reading. W means Watt.

If the word "ALARM" appears below the reading, it means the currently
displayed reading already reaches or crosses the upper or lower
thresholds.
To display the unbalanced load and active power of a 3-phase inlet:
1.

Switch to the current reading of any inlet line.

2.

Press the Up or Down button until "W" or "%" is displayed to the right of
the LCD display. Make sure NONE of the inlet's line number is displayed at
the bottom of the display.
▪

Unbalanced load - % is displayed for the unbalanced current value.

▪

Active power - W is displayed for the power reading. W means Watt.

709

Appendix H: Old Generations of PX3 Models

Overcurrent Protector Information

The Overcurrent Protector mode is displayed as either "CB" or "FUSE" on the
LCD display, which varies according to the type of overcurrent protector
implemented on your PX3. CB refers to the circuit breaker and FUSE refers to
the fuse.
Below illustrates an overcurrent protector's information.

SectionExample information
The selected target is the second circuit breaker (CB 2).
This circuit breaker's current reading is 0 amps.
The word "CLOSE" indicates that the state of the selectedcircuit breaker is closed.
"MASTER" indicates the PX3 is the master device in acascading chain.
For a slave device, it shows "SLAVE" instead.
Note: "MASTER/SLAVE" information is only available in Port
Forwarding mode.
The measurement unit is A (Amp), indicating that the readingis the current.

To display the overcurrent protector information:

710

1.

Press the MODE button until the word "CB" or "FUSE" is displayed.

2.

In the Overcurrent Protector mode, press the Up or Down button until thedesired overcurrent protector's number is displayed at the top of the LCD
display.

3.

Check the reading and the text shown below the reading: CLOSE or OPEN.
▪

CLOSE: The selected circuit breaker is closed, or the selected fuse isnormal.

▪

OPEN: The selected circuit breaker is open, or the selected fuse hasburned out. When this occurs, the term CbE is displayed in place ofthe reading and a blinking word "ALARM" appears next to the word
OPEN.

Appendix H: Old Generations of PX3 Models

IPv4 Address

The IP address is available in the Device mode, which is indicated by thealphabet 'd' shown at the top of the LCD display. Note that this type of LCD
display only shows the IPv4 address (if available).
Below illustrates the IP address information.

SectionExample information"d" means the LCD display has entered the Device
mode.
The LCD display is showing 192, which is one of thefour IP address octets. It will cycle through four octets.
"i4" indicates that the IP address shown on the LCD
display is an IPv4 address.
"MASTER" indicates the PX3 is the master device in acascading chain.
For a slave device, it shows "SLAVE" instead.
Note: "MASTER/SLAVE" information is only available in
Port Forwarding mode.

If you connect your PX3 to the wireless network, a Wi-Fi icon is displayed at thebottom-right corner.

711

Appendix H: Old Generations of PX3 Models

To retrieve the "IPv4" address on PX3:
1.

Press the MODE button to enter the Device mode, indicated by analphabet "d" at the top left of the display.

2.

The LCD display cycles between the four octets of the IPv4 address,
indicated by "i4" at the upper right corner of the display.
For example, 192.168.84.4 cycles in this sequence:
192 --> 168 --> 84 --> 4

MAC AddressThis product's MAC address is retrievable by operating the LCD display.
Below illustrates the MAC address information.

SectionExample information"d" means the LCD display has entered the Device mode.
"M" indicates that the displayed information is the MAC
address.
"MASTER" indicates the PX3 is the master device in acascading chain.
For a slave device, it shows "SLAVE" instead.
Note: "MASTER/SLAVE" information is only available in Port
Forwarding mode.
The LCD display is showing "03," which is part of the MAC
address.

To display the MAC address:

712

1.

Press the MODE button to enter the Device mode, indicated by a 'd' in at
the top left of the display.

2.

Press the FUNC button until the MAC address is displayed. The character"M" appears in the left side of the LCD display.

3.

The MAC address is displayed as "M:XX", where XX are two digits of the
MAC address. The LCD will cycle through the MAC address from the firsttwo digits to the final two.

Appendix H: Old Generations of PX3 Models

For example, if the MAC address is 00:0d:5d:03:5E:1A, the LCD display
shows the following information one after another:
M 00 --> M:0d --> M:5d --> M:03 --> M:5E --> M:1A
Note that 'M' is NOT followed by the colon symbol when showing the firsttwo digits of the MAC address.

Environmental Sensor Information

The environmental sensor mode is displayed as "SENSOR" on the LCD display.
Basic information about a specific environmental sensor is available, including
the sensor's reading or state, X, Y, Z coordinates and its serial number.
Below illustrates the environmental sensor information.

NumberExample information
The selected target is the environmental sensor whose ID
number is 9 (SENSOR 9).
The selected environmental sensor's reading is 22.

"MASTER" indicates the PX3 is the master device in a cascading
chain.
For a slave device, it shows "SLAVE" instead.
Note: "MASTER/SLAVE" information is only available in Port
Forwarding mode.
The measurement unit is(degrees in Celsius).

To display the environmental sensor information:
1.

Press the MODE button until this product enters the Sensor mode, as
indicated by "SENSOR" at the top of the LCD display.

2.

Press the Up or Down button until the desired environmental sensor's ID
number is displayed.

3.

For example, "SENSOR 1" refers to the sensor #1 listed on the PX3 web
interface.

4.

The LCD display shows the reading or state of the selected sensor in the
middle of the LCD display.

713

Appendix H: Old Generations of PX3 Models▪

When showing a numeric sensor's reading, the appropriate
measurement unit is displayed to the right of the reading.
Measurement
units

Sensor types%

A relative humidity sensor
A temperature sensor▪

m/s

An air flow sensor

Pa

An air pressure sensor

NO measurement
units

For an "absolute" humidity sensor, the measurement
unit is g/m3, which cannot be displayed on the LCD.

Available states for a state sensor:
StatesDescription

norNormal state.

ALA

Alarmed state.
▪ This state is accompanied with the word "ALARM" below
it.

▪

Available states for a dry contact signal actuator (DX sensor series):
StatesDescription

On

The actuator is turned on.

Off

The actuator is turned off.

Note: Numeric sensors show both numeric readings and sensor states toindicate environmental or internal conditions while state sensors show
sensor states only to indicate state changes.
5.

Press the FUNC button to show the sensor's port position. There are two
types of information.
▪

P:n (where n is the SENSOR port's number): This information indicatesthe SENSOR port number.

▪

C:x (where x is the sensor's position in a sensor chain): This information
indicates the sensor's position in a chain, which is available for DPX2,
DPX3 and DX sensors only. The LCD display will cycle between the port
information (P:n) and chain position information (C:x).
Note that if the DPX3-ENVHUB4 sensor hub is used to connect the
DPX2, DPX3 or DX sensors, the chain position information (C:x) is
displayed twice - the first one indicates the sensor hub's chain position,
which is always C:1, and the second one indicates the sensor's chain
position.

714

Appendix H: Old Generations of PX3 Models

6.

Press the FUNC button to display the X, Y and Z coordinates of the sensor
respectively.
▪

X coordinate is shown as "x:NN," where NN are the first two numeric
digits entered for the X coordinate in the web interface.

▪

Y coordinate is shown as "y:NN," where NN are the first two numeric
digits entered for the Y coordinate in the web interface.

▪

Z coordinate is shown as "z:NN," where NN are the first two numeric
digits entered for the Z coordinate in the web interface.

If one or both of the first two digits for a specific coordinate arealphabetical characters, these alphabetical characters are replaced withdashes (-).
7.

Press the FUNC button to display the serial number of the sensor, which isshown as "s:XX," where XX are two digits of the serial number. The LCD will
cycle through the serial number from the first two digits to the final two.
For example, if the serial number is AE17A00022, the LCD display shows
the following information one after another:s:AE --> s:17 --> s:A0 --> s:00 --> s:22
Note: Some alphabets cannot be properly displayed due to the LCD display
restriction. For example, Q looks like 9, Z looks like 2, and M looks like
Check the sensor's label or the web interface when you have doubts.

.

Asset Strip Information

If there is any asset strip connected to the PX3, you can enter the Asset Strip
mode to show the asset tag state of each rack unit on the asset strip. A rack
unit refers to a tag port on the asset strips.
When there are no asset strips connected, this mode is not available.
Below illustrates the asset strip information.

SectionExample information"1" refers to the asset strip connected to the first FEATURE
port.
This symbol
indicates that you can switch between diverse
rack units now by pressing the Up or Down button.

715

Appendix H: Old Generations of PX3 Models

SectionExample information"30" indicates that the selected target is the 30th rack unit.
"MASTER" indicates the PX3 is the master device in acascading chain.
For a slave device, it shows "SLAVE" instead.
Note: "MASTER/SLAVE" information is only available in Port
Forwarding mode.
"ASSET" means that the LCD display enters the Asset Strip
mode.

To display the asset management information:
1.

Press the MODE button until the PX3 enters the Asset Strip mode, as
indicated by "ASSET" to the right of the LCD.

2.

By default the PX3 selects the asset strip connected to the first FEATURE
port so it shows "1" at the top. Because the PX3 has only one FEATURE
port, "1" is the only option.

3.

Press the FUNC button. When a blinking double-arrow symbol
appears
to the left of the LCD display, press the Up or Down button to select thedesired rack unit on the asset strip. The rack unit number appears in the
middle of the LCD display.
Note: Press and hold the Up or Down button for at least two (2) seconds toquickly move through several items at once.

716▪

If the word "ALARM" appears below the rack unit number, it means noasset tag is physically connected to that rack unit.

▪

If the word "ALARM" does NOT appear, it means a connected asset tag
is detected on the rack unit.

Appendix H: Old Generations of PX3 Models

USB-Cascaded Device's Position

Note: As of release 3.3.10, the following cascading information is no longer
available in the Bridging mode, but remains available in the Port Forwardingmode.
A cascaded device's position is available by operating the LCD display.
Below illustrates a slave device's position.

SectionExample information"d" means the LCD display has entered the Device mode.
"CA" indicates that the cascading information is being
displayed.
"SLAVE" indicates that this PX3 is a slave device.
Note: For a master device, it shows the word "MASTER"
instead.
The number 1 means the device position is Slave 1.

To retrieve the device's cascading position information:
1.

Press the MODE button to enter the Device mode, indicated by a 'd' in at
the top left of the display.

2.

Press the FUNC button until "CA" is displayed at the top right of thedisplay.

3.

The device's position is represented by any number defined below:

717

Appendix H: Old Generations of PX3 Models

Number
0
1
2
3
4
5
6
7

Device position
Master device
Slave 1
Slave 2
Slave 3
Slave 4
Slave 5
Slave 6
Slave 7

Number
8
9
10
11
12
13
14
15

Device position
Slave 8
Slave 9Slave 10
Slave 11
Slave 12
Slave 13
Slave 14
Slave 15

RCM Information

If your "old" PX3 model supports residual current monitoring (RCM), thisinformation is available in the front panel LCD display. For more information on
RCM, see PX3 Models with Residual Current Monitoring (on page 686).
The front panel LCD display shows an alarm message when the RCM enters thecritical state. Besides, you can operate the LCD display to check the RCM status.
Note: For the RCM information shown on the dot-matrix LCD display, see Front
Panel Operations for RCM (on page 696).
RCM alarm information in the critical state:
In the RCM critical state, the PDU beeps and the LCD display indicates the RCM
critical state.
The RCM alarm information continues to display as long as RCM is in a criticalstate. The following RCM alarm messages are displayed one by one in thecritical state.
rCA --> rCA --> Residual current value (mA)
The diagram below illustrates the RCM alarm on the LCD display.

718

Appendix H: Old Generations of PX3 Models

To display the RCM current:
1.

Press the MODE button until the term "INLET" is displayed.

2.

Verify the LCD is showing the inlet's current, which is indicated by thepresence of the letter "A." If not, switch to current by pressing the FUNC
button.

3.

Depending on the type of your PX3, the procedure to display the residual
current slightly differs.
▪

Single-phase PDU: Press the Up or Down button until the word "LEAK"
displays.

▪

3-phase PDU: Press the Up button until the word "LEAK" displays.

Below illustrates the residual current information shown on the LCD
display.

SectionExample information
The inlet containing RCM sensor is INLET 1.
This residual current is 0 mA.
ALARM always displays for residual current sensor.
LEAK always displays for residual current sensor.
Measurement units are mA.

To run RCM self-test:
1.

Press the MODE button until the LCD alternates between "SLF" and "tSt,"
which means SELF TEST.

2.

Press the FUNC button to start RCM self-test.

3.

The LCD shows dash symbols during RCM self-test.

4.

Upon completion, RCM self-test results are displayed for 30 seconds, oruntil you press any button.
▪

PAS: Self-test passed.

▪

FAL: Self-test failed (the PX3 also beeps).

719

Appendix H: Old Generations of PX3 Models

Below illustrates the RCM self-test mode.

SectionExample information
The inlet containing RCM sensor is INLET 1.
The LCD alternates between "SLF" and "tSt" to indicate that
this is self-test mode.
ALARM always displays for residual current sensor.
LEAK always displays for residual current sensor.

Note: To disable or enable this front panel function, see Disabling or Enabling
Front Panel RCM Self-Test (on page 694). By default, this function is enabled.

Serial RS-232 "DB9" Port Pinouts
RS-232 Pin/signal definition

720

Pin No.

SignalDirection

Description

1

DCD

Input

Data

2

RxD

Input

Receive data (data in)

3

TxD

OutputTransmit data

4

DTR

OutputData terminal ready

5

GND

―

Signal ground

6

DSR

Input

Data set ready

7

RTS

OutputRequest to send

8

CTS

Input

Clear to send

9

RI

Input

Ring indicator

Appendix I

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

Create user groups for the PX3 on the AD serverc.

Configure LDAP authentication on the PX3d.

Configure roles on the PX3

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 ....................................................721
Step B. Configure User Groups on the AD Server .............................................722
Step C. Configure LDAP Authentication on the PX3 .........................................723
Step D. Configure Roles on the PX3 ..................................................................726

Step A. Determine User Accounts and Roles
Determine the user accounts and roles (groups) that are authenticated foraccessing the PX3. 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)

PX_Userusera
pxuser2

PX_Adminuserb
pxuserGroup permissions:••

The PX_User role will have neither system permissions nor outlet
permissions.
The PX_Admin role will have full system and outlet permissions.

721

Appendix I: LDAP Configuration Illustration

Step B. Configure User Groups on the AD Server
You must create the groups (roles) for the PX3 on the AD server, and thenmake appropriate users members of these groups.
In this illustration, we assume:••

The groups (roles) for the PX3 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.

722

2.

Add the pxuser2 and usera accounts to the PX_User group.

3.

Add the pxuser and userb accounts to the PX_Admin group.

4.

Verify whether each group comprises correct users.

Appendix I: LDAP Configuration Illustration

Step C. Configure LDAP Authentication on the PX3
You must enable and set up LDAP authentication properly on the PX3 to use
external authentication.
In the illustration, we assume:
•
•
•
•
•

The DNS server settings have been configured properly. See Wired
Network Settings (on page 254) and Role of a DNS Server (on page 790).
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 PX3 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 nameor IP address in this field, but you must type the fully qualified domainname if the encryption is enabled.

Copy settings from existing Leave the checkbox deselected unless the new LDAP server's settings are
LDAP server
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),

Skip the two fields since the TLS encryption is not enabled.

CA certificate
Anonymous bind

Select this checkbox because anonymous bind is used.

Bind DN,

Skip the three fields because of anonymous bind.

Bind password,
Confirm bind password
Base DN for search

Type dc=techadssl,dc=com as the starting point where your search
begins on the AD server.

723

Appendix I: LDAP Configuration Illustration

724

Field/setting

Do this...

Login Name Attribute

Ensure the field is set to sAMAccountName because the LDAP server isMicrosoft 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 filteringout additional objects in a large directory structure. In this example, weleave it blank.

Active Directory domain

Type techadssl.com.

Appendix I: LDAP Configuration Illustration

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.

725

Appendix I: LDAP Configuration Illustration

Note: If the PX3 clock and the LDAP server clock are out of sync, the installed
TLS certificates, if any, may be considered expired. To ensure propersynchronization, administrators should configure the PX3 and the LDAP server
to use the same NTP server(s).

Step D. Configure Roles on the PX3
A role on the PX3 determines the system and outlet permissions. You must
create the roles whose names are identical to the user groups created for the
PX3 on the AD server or authorization will fail. Therefore, we will create theroles named PX_User and PX_Admin on the PDU.
In this illustration, we assume:••

Users assigned to the PX_User role can view settings only, but they canneither configure PX3 nor access the outlets.
Users assigned to the PX_Admin role have the Administrator Privileges sothey can both configure PX3 and access the outlets.
To create the PX_User role with appropriate permissions assigned:

726

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 thisexample, we type "View PX settings" to describe the role.

Appendix I: LDAP Configuration Illustrationc.

In the Privileges list, select Unrestricted View Privileges, which
includes all View permissions. The Unrestricted View Privileges
permission lets users view all settings without the capability toconfigure or change them.

d.

Click Save.

3.

The PX_User role is created.

4.

Keep the Roles page open to create the PX_Admin role.
To create the PX_Admin role with full permissions assigned:

1.

Click

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.

727

Appendix I: LDAP Configuration Illustration

2.

728

c.

In the Privileges list, select Administrator Privileges. The Administrator
Privileges allows users to configure or change all PX3 settings.

d.

Click Save.

The PX_Admin role is created.

Appendix J

Updating the LDAP Schema

In This Chapter
Returning User Group Information ...................................................................729
Setting the Registry to Permit Write Operations to the Schema .....................730
Creating a New Attribute ..................................................................................730
Adding Attributes to the Class ..........................................................................731
Updating the Schema Cache .............................................................................733
Editing rciusergroup Attributes for User Members ..........................................733

Returning User Group Information
Use the information in this section to return User Group information (and assist
with authorization) once authentication is successful.
From LDAP/LDAPSWhen an LDAP/LDAPS authentication is successful, the PX3 determines thepermissions 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:
rciusergroupattribute type: string

This may require a schema extension on your LDAP/LDAPS server. Consult yourauthentication 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 Windows2000® operating system server requires updating the LDAP/LDAPS schema. Seeyour 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.

729

Appendix J: Updating the LDAP 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 thewindow and then click Operations Master. The Change Schema Master
dialog appears.

2.

Select the "Schema can be modified on this Domain Controller" checkbox.
Optional

3.

Click OK.

Creating a New Attribute
To create new attributes for the rciusergroup class:

730

1.

Click the + symbol before Active Directory® Schema in the left pane of thewindow.

2.

Right-click Attributes in the left pane.

Appendix J: Updating the LDAP Schema

3.

Click New and then choose Attribute. When the warning message appears,
click Continue and the Create New Attribute dialog appears.

4.

Type rciusergroup in the Common Name field.

5.

Type rciusergroup in the LDAP Display Name field.

6.

Type 1.3.6.1.4.1.13742.50 in the Unique x5000 Object ID field.

7.

Type a meaningful description in the Description field.

8.

Click the Syntax drop-down arrow and choose Case Insensitive String fromthe list.

9.

Type 1 in the Minimum field.

10. Type 24 in the Maximum field.
11. Click OK to create the new attribute.

Adding Attributes to the ClassTo add attributes to the class:1.

Click Classes in the left pane of the window.

731

Appendix J: Updating the LDAP Schema

732

2.

Scroll to the user class in the right pane and right-click it.

3.

Choose Properties from the menu. The user Properties dialog appears.

4.

Click the Attributes tab to open it.

5.

Click Add.

6.

Choose rciusergroup from the Select Schema Object list.

Appendix J: Updating the LDAP Schema

7.

Click OK in the Select Schema Object dialog.

8.

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

733

Appendix J: Updating the LDAP Schema

734

3.

Go to the directory where the support tools were installed. Run
adsiedit.msc. The ADSI Edit window opens.

4.

Open the Domain.

5.

In the left pane of the window, select the CN=Users folder.

Appendix J: Updating the LDAP Schema

6.

Locate the user name whose properties you want to adjust in the rightpane. Right-click the user name and select Properties.

7.

Click the Attribute Editor tab if it is not already open. Choose rciusergroupfrom the Attributes list.

8.

Click Edit. The String Attribute Editor dialog appears.

9.

Type the user role (created in the PX3) in the Edit Attribute field. Click OK.

735

Appendix K

RADIUS Configuration Illustration
This section provides illustrations for configuring RADIUS authentication. One
illustration is based on the Microsoft® Network Policy Server (NPS), and theother is based on a FreeRADIUS server.
The following steps are required for any RADIUS authentication:
1.

Configure RADIUS authentication on the PX3. See Adding Radius Servers(on page 306).

2.

Configure roles on the PX3. See Creating Roles (on page 246).

3.

Configure PX3 user credentials and roles on your RADIUS server.
▪

To configure using standard attributes, see Standard Attributes (onpage 736).

▪

To configure using vendor-specific attributes, see Vendor-Specific
Attributes (on page 755).

Note that we assume that the NPS is running on a Windows 2008 system in the
NPS illustrations.

In This Chapter
Standard Attributes ..........................................................................................736
Vendor-Specific Attributes ...............................................................................755
AD-Related Configuration .................................................................................768

Standard Attributes
The RADIUS standard attribute "Filter-ID" is used to convey the groupmembership, that is, roles.
••

If a user has multiple roles, configure multiple standard attributes for thisuser.
The syntax of a standard attribute is:
Raritan:G{role-name}For configuration on NPS, see NPS Standard Attribute Illustration (on page736).
For configuration on FreeRADIUS, see FreeRADIUS Standard Attribute
Illustration (on page 754).
NPS Standard Attribute Illustration
To configure Windows 2008 NPS with the standard attribute, you must:a.

Add your PX3 to NPS. See Step A: Add Your PX3 as a RADIUS Client (onpage 737).

736

Appendix K: RADIUS Configuration Illustrationb.

On the NPS, configure Connection Request Policies and the standard
attribute. See Step B: Configure Connection Policies and Standard
Attributes (on page 741).

Some configuration associated with Microsoft Active Directory (AD) is also
required for RADIUS authentication. See AD-Related Configuration (on page
768).

Step A: Add Your PX3 as a RADIUS Client

The RADIUS implementation on the PX3 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 PX3 = 192.168.56.29••

RADIUS authentication port specified for PX3: 1812
RADIUS accounting port specified for PX3: 1813
To add your PX3 to the RADIUS NPS:

1.

Choose Start > Administrative Tools > Network Policy Server. The Network
Policy Server console window opens.

737

Appendix K: RADIUS Configuration Illustration

2.

Right-click NPS (Local), and select Properties.

Verify the authentication and accounting port numbers shown in theproperties dialog are the same as those specified on your PX3. In thisexample, they are 1812 and 1813. Then close this dialog.

738

Appendix K: RADIUS Configuration Illustration

3.

Under "RADIUS Clients and Servers," right-click RADIUS Client and select
New RADIUS Client. The New RADIUS Client dialog appears.

4.

Do the following to add your PX3 to NPS:a.

Verify the "Enable this RADIUS client" checkbox is selected.

b.

Type a name for identifying your PX3 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.

739

Appendix K: RADIUS Configuration Illustration

f.

5.

740

Type the shared secret in the "Shared secret" and "Confirm sharedsecret" fields. The shared secret must be the same as the one
specified on your PX3.

Click OK.

Appendix K: RADIUS Configuration Illustration

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 PX3Connection request forwarding method
Authentication method(s)Standard RADIUS attributes•

Presumptions in the illustration:
IP address of your PX3 = 192.168.56.29••

Local NPS server is used
RADIUS protocol selected on your PX3 = CHAP•

Existing role of your PX3 = Admin
Illustration:

1.

Open the NPS console, and expand the Policies folder.

741

Appendix K: RADIUS Configuration Illustration

742

2.

Right-click Connection Request Policies and select New. The New
Connection Request Policy dialog appears.

3.

Type a descriptive name for identifying this policy in the "Policy name"field.

Appendix K: RADIUS Configuration Illustration▪

You can leave the "Type of network access server" field to the default-- Unspecified.

743

Appendix K: RADIUS Configuration Illustration

744

4.

Click Next to show the "Specify Conditions" screen. Click Add.

5.

The "Select condition" dialog appears. Click Add.

Appendix K: RADIUS Configuration Illustration

6.

The NAS IPv4 Address dialog appears. Type the PX3 IP address -192.168.56.29, and click OK.

7.

Click Next in the New Connection Request Policy dialog.

8.

Select "Authenticate requests on this server" because a local NPS server isused in this example. Then click Next.

745

Appendix K: RADIUS Configuration Illustration

Note: Connection Request Forwarding options must match yourenvironment.

9.

746

When the system prompts you to select the authentication method, selectthe following two options:▪

Override network policy authentication settings▪

CHAP -- the PX3 uses "CHAP" in this example

Appendix K: RADIUS Configuration Illustration

Note: If your PX3 uses PAP, then select "PAP."

747

Appendix K: RADIUS Configuration Illustration

10. Select Standard to the left of the dialog and then click Add.

748

Appendix K: RADIUS Configuration Illustration

11. Select Filter-Id from the list of attributes and click Add.

749

Appendix K: RADIUS Configuration Illustration

12. In the Attribute Information dialog, click Add.

13. Select String, type Raritan:G{Admin} in the text box, and then click OK.

750

Appendix K: RADIUS Configuration Illustration

Admin inside the curved brackets {} is the existing role on the PX3. It is
recommended to use the Admin role to test this configuration. The rolename is case sensitive.

751

Appendix K: RADIUS Configuration Illustration

14. The new attribute is added. Click OK.

752

Appendix K: RADIUS Configuration Illustration

15. Click Next to continue.

753

Appendix K: RADIUS Configuration Illustration

16. A summary showing connection request policy settings is displayed. Click
Finish to close the dialog.

FreeRADIUS Standard Attribute Illustration
With standard attributes, NO dictionary files are required. You simply add alluser 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:

754

1.

Go to this location: /etc/raddb/users.

2.

Add the data of the user "steve" by typing the following. Note that thevalues after the equal sign (=) must be enclosed in double quotes (").

Appendix K: RADIUS Configuration Illustration

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-specificattribute (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 755).
For configuration on FreeRADIUS, see FreeRADIUS VSA Illustration (on page767).

NPS VSA Illustration
To configure Windows 2008 NPS with the vendor-specific attribute, you must:a.

Add your PX3 to NPS. See Step A: Add Your PX3 as a RADIUS Client (onpage 737).

b.

On the NPS, configure connection request policies and the vendor-specificattribute. See Step B: Configure Connection Policies and Vendor-Specific
Attributes (on page 760).

Some configuration associated with Microsoft Active Directory (AD) is also
required for RADIUS authentication. See AD-Related Configuration (on page
768).

755

Appendix K: RADIUS Configuration Illustration

Step A: Add Your PX3 as a RADIUS Client

The RADIUS implementation on the PX3 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 PX3 = 192.168.56.29••

RADIUS authentication port specified for PX3: 1812
RADIUS accounting port specified for PX3: 1813
To add your PX3 to the RADIUS NPS:

1.

756

Choose Start > Administrative Tools > Network Policy Server. The Network
Policy Server console window opens.

Appendix K: RADIUS Configuration Illustration

2.

Right-click NPS (Local), and select Properties.

Verify the authentication and accounting port numbers shown in theproperties dialog are the same as those specified on your PX3. In thisexample, they are 1812 and 1813. Then close this dialog.

757

Appendix K: RADIUS Configuration Illustration

758

3.

Under "RADIUS Clients and Servers," right-click RADIUS Client and select
New RADIUS Client. The New RADIUS Client dialog appears.

4.

Do the following to add your PX3 to NPS:a.

Verify the "Enable this RADIUS client" checkbox is selected.

b.

Type a name for identifying your PX3 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.

Appendix K: RADIUS Configuration Illustrationf.

5.

Type the shared secret in the "Shared secret" and "Confirm sharedsecret" fields. The shared secret must be the same as the one
specified on your PX3.

Click OK.

759

Appendix K: RADIUS Configuration Illustration

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 PX3Connection request forwarding method
Authentication method(s)Standard RADIUS attributes•

Presumptions in the illustration:
IP address of your PX3 = 192.168.56.29••

Local NPS server is used
RADIUS protocol selected on your PX3 = CHAP•

Existing roles of your PX3 = Admin, User and SystemTester
Illustration:

1.

760

Open the NPS console, and expand the Policies folder.

Appendix K: RADIUS Configuration Illustration

2.

Right-click Connection Request Policies and select New. The New
Connection Request Policy dialog appears.

3.

Type a descriptive name for identifying this policy in the "Policy name"field.

761

Appendix K: RADIUS Configuration Illustration▪

762

You can leave the "Type of network access server" field to the default-- Unspecified.

Appendix K: RADIUS Configuration Illustration

4.

Click Next to show the "Specify Conditions" screen. Click Add.

5.

The "Select condition" dialog appears. Click Add.

763

Appendix K: RADIUS Configuration Illustration

764

6.

The NAS IPv4 Address dialog appears. Type the PX3 IP address -192.168.56.29, and click OK.

7.

Click Next in the New Connection Request Policy dialog.

8.

Select "Authenticate requests on this server" because a local NPS server isused in this example. Then click Next.

Appendix K: RADIUS Configuration Illustration

Note: Connection Request Forwarding options must match yourenvironment.

9.

When the system prompts you to select the authentication method, selectthe following two options:▪

Override network policy authentication settings▪

CHAP -- the PX3 uses "CHAP" in this example

765Appendix K: RADIUS Configuration Illustration

Note: If your PX3 uses PAP, then select "PAP."

10. Select Vendor Specific to the left of the dialog, and click Add. The Add
Vendor Specific Attribute dialog appears.
11. Select Custom in the Vendor field, and click Add. The Attribute Information
dialog appears.
12. Click Add, and the Vendor-Specific Attribute Information dialog appears.
13. Click "Enter Vendor Code" and type 13742.
14. Select "Yes, it conforms" to indicate that the custom attribute conforms to
the RADIUS Request For Comment (RFC).
15. Click Configure Attribute, and then:

766

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 {}.

Appendix K: RADIUS Configuration Illustration

Note that multiple roles are separated with a space.

16. Click OK.
FreeRADIUS VSA Illustration
A vendor-specific dictionary file is required for the vendor-specific-attributeconfiguration on FreeRADIUS. Therefore, there are two major configuration
steps.
a.

Use a dictionary to define the Raritan vendor-specific attributeb.

Add all user data, including user names, passwords, and roles•

Presumptions in the illustration:
Raritan attribute = Raritan-User-Roles•

User name = steve•

Steve's password = test123•

Steve's roles = Admin, User and 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.

767

Appendix K: RADIUS Configuration Illustration

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 thevalues 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 thefollowing 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.

768

Open the NPS console.

Appendix K: RADIUS Configuration Illustration

2.

Right-click NPS (Local) and select "Register server in Active Directory."

3.

Click OK, and then OK again.

To grant PX3 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 accesspermission.

769

Appendix K: RADIUS Configuration Illustration

3.

Click the Dial-in tab and select the "Allow access" checkbox.

To enable reversible encryption for CHAP authentication:

770

1.

Open Active Directory Users and Computers.

2.

Open the properties dialog of the user that you want to configure.

Appendix K: RADIUS Configuration Illustration

3.

Click the Account tab and select the "Store password using reversible
encryption" checkbox.

771

Appendix L

Additional PX3 Information

In This Chapter
RJ45-to-DB9 Cable Requirements for Modem Connections.............................772
Reserving IP Addresses in DHCP Servers ..........................................................773
Sensor Threshold Settings ................................................................................777
Default Voltage and Current Thresholds ..........................................................785
Altitude Correction Factors ..............................................................................787
Unbalanced Current Calculation .......................................................................787
Data for BTU Calculation ..................................................................................788
Ways to Probe Existing User Profiles ................................................................789
Raritan Training Website ..................................................................................789
Role of a DNS Server .........................................................................................790
Cascading Troubleshooting...............................................................................790
Installing the USB-to-Serial Driver (Optional) ...................................................795
Initial Network Configuration via CLI ................................................................796
Device-Specific Settings ....................................................................................803
TLS Certificate Chain .........................................................................................804
Browsing through the Online Help ...................................................................810

RJ45-to-DB9 Cable Requirements for Modem Connections
An RJ45-to-DB9 adapter/cable is required for connecting a modem to the PX3
device.
A third party RJ45-to-DB9 adapter/cable needs to meet the following
requirements.
•••

RJ-45 to "DB9 male"
RX/TX and according control pins are NOT crossed
With the following pin assignments:
Pin signal

DB9 pin No.

RJ-45 pin No.

DCD

1

5

RxD

2

6

TxD

3

3

DTR

4

2

GND

5

4

DSR

6

7

RTS

7

1

CTS

8

8

772

Appendix L: Additional PX3 Information

Pin signal

DB9 pin No.

RJ-45 pin No.

RIR

9

N/A

Note: The RJ45-to-DB9 adapter/cable used for connecting modems CANNOT be
used to connect the PX3 to a computer. See RJ45-to-DB9 Cable Requirements
for Computer Connections (on page 32).

Reserving IP Addresses in DHCP Servers
PX3 uses its serial number as the client identifier in the DHCP request.
Therefore, to successfully reserve an IP address for the PX3 in a DHCP server,
use the PX3 device's serial number as the unique ID instead of the MAC
address.
Since all network interfaces of the PX3 can be simultaneously enabled andconfigured 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 tablebelow lists the client identifiers of all network interfaces.
Interface

Client identifier

ETH1

serial number

ETH2

serial number plus the uppercase suffix "-ETH2"

WIRELESS

serial number plus the uppercase suffix "-WIRELESS"BRIDGE

serial number

You can reserve the IP addresses of more than one interfaces in the DHCP
server if preferred. Note that you must choose/configure the bridge interface ifyour PX3 is set to the bridging mode.
Important: In the bridging mode, only the IP parameters of the BRIDGE
interface function. The IP parameters of ETH1/ETH2 and WIRELESS interfaces
do NOT function.

773

Appendix L: Additional PX3 Information

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 773).
In the following illustration, it is assumed that the PX3 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

ETH1

PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

ETH2

PEG1A00003-ETH2 = 50 45 47 31 41 30 30 30 30 33 2D 45
54 48 32
▪ The suffix comprising the dash symbol and the word
"ETH2" is also converted.

WIRELESSPEG1A00003-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
2.

PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

In your DHCP server, bring up the New Reservation dialog, and separate
the converted ASCII codes with spaces.
For example, to reserve the ETH1 interface's IP address, enter the following
data in the dialog.

774

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.

Appendix L: Additional PX3 Information

Reserving IP in Linux
There are two methods to reserve the IP address of any network interface inthe standard Linux DHCP server (ISC DHCP server):••

Convert an interface's client identifier into hexadecimal ASCII codes.
Use an interface's original client identifier without converting it into ASCII
codes.

For each interface's client identifier, see Reserving IP Addresses in DHCP
Servers (on page 773).
In the following illustrations, it is assumed that the PX3 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

ETH1

PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

ETH2

PEG1A00003-ETH2 = 50 45 47 31 41 30 30 30 30 33 2D 45
54 48 32
▪ The suffix comprising the dash symbol and the word
"ETH2" is also converted.

775

Appendix L: Additional PX3 Information

Interface

Client identifier conversion

WIRELESSPEG1A00003-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
2.

PEG1A00003 = 50 45 47 31 41 30 30 30 30 33

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 ETH1 interface looks likethe following:
00:50:45:47:31:41:30:30:30:30:33

3.

Now enter the converted client identifier with the following syntax.
host mypx {option dhcp-client-identifier = 00:50:45:47:31:41:30:30:30:30:33;
fixed-address 192.168.20.1;}
Illustration without ASCII code conversion:

1.

Use the original client identifier of the desired network interface. DO NOT
convert them into ASCII codes.

2.

A prefix "\000" must be added to the beginning of the client identifier.
For example, the client identifier of the ETH1 interface looks like thefollowing:\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;}

776

Appendix L: Additional PX3 Information

Sensor Threshold Settings
This section explains the thresholds settings for a numeric sensor.

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 acertain sensor and the range of each sensor state. The diagram below shows
how each threshold relates to each state.

777

Appendix L: Additional PX3 Information

above upper critical
Upper Criticalabove upper warning
Upper WarningnormalLower Warning

below lower warning
Lower Critical

below lower critical

Available sensor states:

778

Appendix L: Additional PX3 Information

The more thresholds are enabled for a sensor, the more sensor states areavailable 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, andabove 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 statesthat require you to immediately handle.
Range of each available sensor state:
The value of each enabled threshold determines the reading range of eachavailable sensor state. For details, see Yellow- or Red-Highlighted Sensors (onpage 208).

779

Appendix L: Additional PX3 Information"To Assert" and Assertion Timeout
If multiple sensor states are available for a specific sensor, the PX3 asserts astate 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 PX3 to assert.
1. above upper warning --> above upper critical
2. normal --> above upper warning
3. normal --> below lower warning
4. below lower warning --> below lower critical

Assertion Timeout:780

Appendix L: Additional PX3 Information

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 PX3 triggers the "assertion" action. If that sensor changes its stateagain within the specified wait time, the PX3 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 isequal 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 PX3 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 fromthe "normal" range to the "above upper warning" range, the PX3 does NOT
immediately announce this warning state. Instead it waits for 5 seconds, andthen does either of the following:••

If the temperature remains above 25 degrees Celsius in the "above upper
warning" range for 5 seconds, the PX3 performs the "assertion" action toannounce the "above upper warning" state.
If the temperature drops below 25 degrees Celsius within 5 seconds, thePX3 does NOT perform the "assertion" action.

781

Appendix L: Additional PX3 Information"To De-assert" and Deassertion Hysteresis
After the PX3 asserts a worse state for a sensor, it may de-assert that statelater 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 PX3 to de-assert the previous
state.
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:782

Appendix L: Additional PX3 Information

783

Appendix L: Additional PX3 Information

In the threshold settings, the Deassertion Hysteresis field determines a newlevel to trigger the "deassertion" action.
This function is similar to a thermostat, which instructs the air conditioner toturn on the cooling system when the temperature exceeds a pre-determined
level. "Deassertion Hysteresis" instructs the PX3 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 eachthreshold. 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 eachthreshold is either "+2" or "-2" as illustrated below.
Threshold value

Deassertion value

Upper Critical = 33

Deassertion level = 31•

Upper Warning = 25

Deassertion level = 23•

Lower Critical = 10

25 - 2 = 23

Deassertion level = 12•

Lower Warning = 18

33 - 2 = 31

10 + 2 = 12

Deassertion level = 20•

18 + 2 = 20

To use each threshold as the "deassertion" level instead of determining a newlevel, set the Deassertion Hysteresis to 0 (zero).
Note: The difference between Upper Warning and Lower Warning must be atleast "two times" of the deassertion value.
How "Deassertion Hysteresis" is helpful:
If you have created an event rule that instructs the PX3 to send notifications fordeassertion 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

784

Appendix L: Additional PX3 Information

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 PX3 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 PX3 does
NOT perform the "deassertion" action.
If the temperature drops to 17 degrees Celsius or lower, the PX3 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

785

Appendix L: Additional PX3 Information

•

•

•

•

786

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

Hysteresis2%

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

Appendix L: Additional PX3 Information

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, thealtitude you enter for the device can serve as an altitude correction factor. Thatis, the reading of the differential air pressure sensor will be multiplied by thecorrection 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. Thissection explains how PX3 calculates the unbalanced current percentage.
Calculation:
1.

Calculate the average current of all 3 lines.
Average current = (L1+L2+L3) / 3

2.

Calculate each line's current unbalance by having each line current
subtracted and divided with the average current.

787

Appendix L: Additional PX3 Information

L1 current unbalance = (L1 - average current) / average
current
L2 current unbalance = (L2 - average current) / average
current
L3 current unbalance = (L3 - average current) / average
current3.

Determine the maximum absolute value among three lines' current
unbalance values.
Maximum (|L1 current unbalance|, |L2 current unbalance|,|L3 current unbalance|)

4.

Convert the maximum value to a percentage.
Unbalanced load percent = 100 * maximum current 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 PX3 device differs according to the model you
purchased. To calculate the heat (BTU/hr), use the following power dataaccording to your model type in the BTU calculation formula.

788

Model nameMaximum power (Watt)

1000 series

5Appendix L: Additional PX3 Information

Model nameMaximum power (Watt)

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

With SNMP v3 activated, you get the "user unknown" error when the username 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 associateduser 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 ausername and password through the Raritan training website. After you areverified, you can access the Raritan training website anytime.

789

Appendix L: Additional PX3 InformationRole 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 (hostnames) to corresponding IP addresses, or the PX3 may fail to connect to thegiven host.
Therefore, DNS server settings are important for external authentication. With
appropriate DNS settings, the PX3 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 301).

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 PX3 to acomputer if network access to that PX3 fails. See Connecting the PX3 to a
Computer (on page 31).

790

Appendix L: Additional PX3 Information

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 isincorrectly set as the downstream interface.

For the wireless networking, one of the following issues
occurs:▪

The USB wireless LAN adapter attached to the masterdevice is not the Raritan USB WIFI LAN adapter. See USB
Wireless LAN Adapters (on page 23).

▪

The wireless LAN configuration is not supported. See
Supported Wireless LAN Configuration (on page 23).

▪

The installed CA certificate chain contains any certificatethat has expired or is not valid yet.

791

Appendix L: Additional PX3 Information

Symptom

Probable cause

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 inquestion 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 theslave device in question or any upstream device is set toPort Forwarding.

•
•

•

792

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 incorrectlyset. For example, you use a USB cable to connect the 1stslave device, but select the Ethernet port as thedownstream 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.
See Port Number Syntax (on page 273).

▪

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

Appendix L: Additional PX3 Information

Tip: To determine which PX3 may be the failure point of network, you may pingeach PX3 in the cascading chain, or check the slave-related events in the eventlog of each PX3. See The Ping Tool (on page 794) and Slave Device Events in
the Log (on page 793).

•

•

•

For a cascading chain comprising only products with "dual" Ethernet
ports, also check the following:
Whether the Ethernet interface (ETH1 or ETH2) where the network or
cascading cable is connected is disabled on the cascaded device inquestion or any upstream device.
Whether the connection complies with the cascading guidelines, when set
to the Port Forwarding mode. See Restrictions of Port-Forwarding
Connections (on page 41).
Whether a newer product model, if involved in the chain, runs theappropriate minimum firmware version or later.

Slave Device Events in the Log
The log messages for connection/disconnection of a cascaded device aredifferent for USB-cascading and Ethernet-cascading chains.
Messages for the Ethernet-cascading chain:
Whenever the connection or disconnection of a master/slave device is
detected, both PX3 devices connected via that network cable record this eventin their internal logs.
There are two slave-related events:
Event

Description

The ETH1/2 network interface This log entry is generated when the PX3
detects the connection of the upstream orlink is now up.
downstream cascaded device on one of its
Ethernet ports.
The ETH1/2 network interface This log entry is generated when the PX3link is now down.
detects the disconnection of the upstream
or downstream cascaded device on one of
its Ethernet ports.

793

Appendix L: Additional PX3 Information

Messages for the USB-cascading chain:
In the Bridging mode, events regarding connection/disconnection of adownstream 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 PX3 at the
USB-A end of the USB cable logs it in the internal log. Note that the PX3 at theUSB-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 PX3 detects thepresence of a slave device on its USB-A port.

Slave disconnected This log entry is generated when it detects thedisconnection of a slave device from its USB-A port.

The Ping Tool
The PX3 provides a ping tool in the web interface and CLI so you can ping any
host or PX3 in your data center.
Ping via the Web Interface:
To log in to the web interface, see Login (on page 159).
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 PX3 or using
SSH/Telnet. See With SSH or Telnet (on page 458).

794

1.

You must perform the ping command in the diagnostic mode. See Entering
Diagnostic Mode (on page 619).

2.

Then perform the ping command. See Testing the Network Connectivity(on page 621).

Appendix L: Additional PX3 Information

Installing the USB-to-Serial Driver (Optional)
The PX3 can emulate a USB-to-serial converter over a USB connection. A
USB-to-serial driver named "Dominion PX2 Serial Console" is required forMicrosoft® 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-<n>.exe, where <n> represents the file's
version number.
There are two ways to install this driver: automatic and manual installation.
Automatic driver installation is highly recommended.
Automatic driver installation in Windows®:
1.

Make sure the PX3 is NOT connected to the computer via a USB cable.

2.

Run dominion-serial-setup-<n>.exe on the computer and follow online
instructions to install the driver.
Note: If any Windows security warning appears, accept it to continue theinstallation.

3.

Connect the PX3 to the computer via a USB cable. The driver is
automatically installed.
Manual driver installation in Windows®:

1.

Make sure the PX3 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.
▪

3.

If this dialog does not appear, choose Control Panel > System >Hardware > Device Manager, right-click the Dominion PX2 Serial
Console, and choose Update Driver.

Select the option of driver installation from a specific location, and thenspecify the location where both dominion-serial.inf and dominion-serial.cat
are stored.
Note: If any Windows security warning appears, accept it to continue theinstallation.

4.

Wait until the installation is complete.

795

Appendix L: Additional PX3 Information

Note: If the PX3 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
PX3 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 PX3 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 253).
To configure the PX3 device:1.

On the computer connected to the PX3, 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.
3.

In the communications program, press Enter to send a carriage return to
the PX3.

4.

The PX3 prompts you to log in. Both user name and password are casesensitive.

5.

796

a.

Username: adminb.

Default password: raritan (or a new password if you have changedit).

If prompted to change the default password, change or ignore it.

Appendix L: Additional PX3 Information▪

To change it, follow onscreen instructions to type your new password.

▪

To ignore it, simply press Enter.

6.

The # prompt appears.

7.

Type config and press Enter.

8.

To configure network settings, type appropriate commands and press
Enter. Refer to the following commands list. CLI commands are casesensitive.

9.

After finishing the network settings, type apply to save changes. To abort,
type cancel.
Commands for wired networking:The <ipvX> variable in the following commands is either ipv4 or ipv6,
depending on the type of IP protocol you are configuring.
For PX2 and "old" PX3 that have only one Ethernet port, replace the variable<ETH> with the word "ethernet". For PX3 that has two Ethernet ports, replace
the variable <ETH> with either 'ETH1' or 'ETH2', depending on which Ethernet
port you are configuring.
•

General IP settings:
To set or
enableUse this command

IPv4 or IPv6
protocolnetwork <ipvX> interface <ETH>
enabled <option><option> = true, or false

IPv4
configuration
methodnetwork ipv4 interface <ETH>
configMethod <mode>

IPv6
configuration
methodnetwork ipv6 interface <ETH>
configMethod <mode><mode> = dhcp (default) or static<mode> = automatic (default) or static

Preferred host network <ipvX> interface <ETH>name (optional) preferredHostName <name><name> = preferred host namenetwork dns resolverPreference
IP address
returned by the <resolver>
DNS server<resolver> = preferV4 or preferV6797

Appendix L: Additional PX3 Information•

Static IP configuration:
To setStatic IPv4 or
IPv6 address

Use this command
network <ipvX> interface <ETH>
address <ip address><ip address> = static IP address, with asyntax similar to the example below.
▪ Example: 192.168.7.9/24

Static IPv4 or
IPv6 gateway

network <ipvX> gateway <ipaddress><ip address> = gateway's IP address

IPv4 or IPv6
primary DNS
server

network dns firstServer <ip
address>

IPv4 or IPv6
secondary DNS
server

network dns secondServer <ip
address>

IPv4 or IPv6
third DNS
server

network dns thirdServer <ip
address><ip address> = DNS server's IP address<ip address> = DNS server's IP address<ip address> = DNS server's IP address

Commands for "Ethernet" authentication method:
To set or
enableUse this command

Authentication
methodnetwork ethernet <ETH>
authMethod <method><method> = none or eap

EAP outer
authentication

network ethernet <ETH>
eapOuterAuthentication<outer_auth><outer_auth> = PEAP or TLS

EAP inner
authentication

network ethernet <ETH>
eapInnerAuthentication<inner_auth><inner_auth> = MSCHAPv2 or TLS

798

Appendix L: Additional PX3 Information

To set or
enableUse this command

EAP identity

network ethernet <ETH>
eapIdentity <identity><identity> = your user name for EAPauthentication

EAP TLS clientcertificate

network ethernet <ETH>
eapClientCertificate
When prompted to enter the clientcertificate, open the certificate with a text
editor, copy and paste the content into
the communications program.

EAP TLS client
private key

network ethernet <ETH>
eapClientPrivateKey
When prompted to enter the private key,
open the key with a text editor, copy andpaste the content into thecommunications program.

EAP password

network ethernet <ETH>
eapPassword
When prompted to enter the password
for EAP authentication, type thepassword.

EAP CAcertificate

network ethernet <ETH>
eapCACertificate
When prompted to enter the CA
certificate, open the certificate with a text
editor, copy and paste the content into
the communications program.

Radiusauthentication
server's namenetwork ethernet <ETH>
eapAuthServerName <FQDN><FQDN> = Fully qualified domain name of
the Radius server name shown in the CA
certificate

799

Appendix L: Additional PX3 Information

The content to be copied from the CA certificate does NOT include the first line
containing "BEGIN CERTIFICATE" and the final line containing "ENDCERTIFICATE." If a certificate is installed, configure the following:
Whether to
Verify thecertificate

Use this command
network ethernet <ETH>
enableCertVerification<option1><option1> = true or false
Accept an
expired or
not valid
certificate

network ethernet <ETH>
allowOffTimeRangeCerts<option2><option2> = true or false

Make theconnection
successful
by ignoringthe"incorrect"
system time•

network ethernet <ETH>
allowConnectionWithIncorrectClo
ck <option3><option3> = true or false

Commands for wireless networking:General wireless settings:
To set or
enableUse this command

Wirelessinterface

network wireless enabled<option><option> = true, or false

SSID

network wireless SSID <ssid><ssid> = SSID string

BSSID

network wireless BSSID <bssid><bssid> = AP MAC address or none

802.11n
protocolnetwork wireless enableHT<option><option> = true, or false

800

Appendix L: Additional PX3 Information

To set or
enableUse this command

Wirelessauthentication
methodnetwork wireless authMethod<method>

PSK

network wireless PSK <psk><method> = psk or eap<psk> = PSK string
Wireless EAP
outerauthentication

network wireless
eapOuterAuthentication<outer_auth><outer_auth> = PEAP or TLS

Wireless EAP
innerauthentication

network wireless
eapInnerAuthentication<inner_auth><inner_auth> = MSCHAPv2 or TLS

Wireless EAP
identity

network wireless eapIdentity<identity><identity> = your user name for EAPauthentication

Wireless EAPTLS clientcertificate

network wireless
eapClientCertificate
When prompted to enter the clientcertificate, open the certificate with a text
editor, copy and paste the content into
the communications program.

Wireless EAPTLS client
private key

network wireless
eapClientPrivateKey
When prompted to enter the private key,
open the key with a text editor, copy andpaste the content into thecommunications program.

Wireless EAP
password

network wireless eapPassword
When prompted to enter the password
for EAP authentication, type thepassword.

801

Appendix L: Additional PX3 Information

To set or
enableUse this command

Wireless EAP
CA certificate

network wireless
eapCACertificate
When prompted to enter the CA
certificate, open the certificate with a text
editor, copy and paste the content into
the communications program.

Radiusauthentication
server's namefor wirelessconnection

network wireless
eapAuthServerName <FQDN><FQDN> = Fully qualified domain name of
the Radius server name shown in the CA
certificate

The content to be copied from the CA certificate does NOT include the first line
containing "BEGIN CERTIFICATE" and the final line containing "ENDCERTIFICATE." If a certificate is installed, configure the following:
Whether to
Verify thecertificate

Use this command
network wirelessenableCertVerification<option1><option1> = true or false

Accept an
expired or
not valid
certificate

network wirelessallowOffTimeRangeCerts<option2><option2> = true or false

Make theconnection
successful
by ignoringthe"incorrect"
system time802

network wirelessallowConnectionWithIncorrectClo
ck <option3><option3> = true or false

Appendix L: Additional PX3 Information•

Wireless IPv4 / IPv6 settings:

Commands for wireless IP settings are identical to those for wired networking.
Just replace the variable <ETH> with the word 'wireless'. The following
illustrates a few examples.
To set or
enableUse this command

IPv4
configuration
methodnetwork ipv4 interface WIRELESS
configMethod <mode>

IPv6
configuration
methodnetwork ipv6 interface WIRELESS
configMethod <mode><mode> = dhcp (default) or static<mode> = automatic (default) or static

To verify network settings:
After exiting the above configuration mode and the # prompt re-appears, typethis 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 likethe following list.
For further information, simply open the built-in bulk profile for a detailed listof '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 states803

Appendix L: Additional PX3 Information

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 thatserver'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 madeto 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 804).
For an example of creating and uploading a TLS certificate to PX3, see
Illustration - GMAIL SMTP Certificate Chain (on page 807).

What is a Certificate Chain
If you are familiar with a certificate chain, you can ignore this topic and referto Illustration - GMAIL SMTP Certificate Chain (on page 807).
A certificate or a chain of certificates is used for trusting a TLS server that you
want to connect.
The receiver, such as PX3, 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 anintermediate certificate.

804Appendix L: Additional PX3 Information•

Certificate A. The self-signed certificate issued by Issuer A. Issuer A is aroot CA.

The above three certificates form a certificate path, which is called the"certificate chain".

Each certificate in the chain is the issuer certificate of the certificate that
follows it. That is, A is the issuer certificate of B, and B is the issuer certificate ofC.
Note: In fact many certificate chains may comprise only the root certificate anda 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 PX3:
Because the TLS server provides only 'Certificate C', you need to upload a filecontaining the missing certificates of the chain (that is, 'Certificate A' and'Certificate B') to the receiver.

In reality some servers may provide a partial (or even a full) certificate chain
instead of a single server certificate. If your server provides a partial certificate
chain containing 'Certificate B' and 'Certificate C', then you only need to upload'Certificate A" to the receiver. If the server has a full certificate chain containing
Certificates 'A', 'B', and 'C', then you also need to upload the root certificate
'A".

805

Appendix L: Additional PX3 Information

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 PX3, it means you trust
each certificate in the chain to certify the authenticity of certificates a server
sends to PX3. Therefore, at least the root certificate must be authentic,
issued by a CA you trust, and downloaded from that CA over a securechannel. Never implicitly trust a root certificate that is sent by the serverwhich 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 thereceiver, the connection to the wanted TLS server will fail.

For PX3, if any required certificate is missing, a certificate error message similar
to the following is shown on the PX3 web interface.

806

Appendix L: Additional PX3 Information

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 thereceiver must look like the following.

•

The top is the final intermediate certificate of the chain "B" if you have to
upload a partial chain.
The bottom is always the root certificate "A".
When copying multiple certificates to a single file, make sure you also copy
the lines of BEGIN CERTIFICATE and END CERTIFICATE from eachcertificate.

••

Illustration - GMAIL SMTP Certificate Chain
If you will apply your company's SMTP service to PX3, ignore this GMAIL
illustration topic. Simply contact your IT department to retrieve theappropriate certificate (chain) file and upload it to the PX3.
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 byusing a Web browser, the method to find an SMTP server's certificate is moredifficult, which requires appropriate tools and sufficient technical knowledge.
For example, you may have to use the openssl command as illustrated below toretrieve 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 theserver 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 canremove the "-showcerts" option from the above command.

807

Appendix L: Additional PX3 Information

2.

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----MIIDfTCCAuagAwIBAgIDErvmMA0GCSqGSIb3DQEBBQUAME4xCzAJBgNVBAYTAlVT.
.
b8ravHNjkOR/ez4iyz0H7V84dJzjA1BOoa+Y7mHyhD8S-----END CERTIFICATE------Server certificate
subject=/C=US/ST=California/L=Mountain View/O=Google
Inc/CN=smtp.gmail.com
issuer=/C=US/O=Google Inc/CN=Google Internet Authority G2
.
.
.
3.

Onscreen information under the title 'Certificate chain' indicates that there
are three issuers and three certificates on this server.
▪

808

Each line beginning with the letter "i" indicates an issuer. They are:

Appendix L: Additional PX3 Information▪

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.

4.

The section titled "Server certificate" indicates that the issuer (CA) Google
Internet Authority G2 issues the server certificate.

5.

As the server has the server certificate and two intermediate certificates,
we conclude that this server sends a partial certificate chain to thereceiver.

6.

Check whether the issuer "Equifax Secure Certificate Authority" is the rootCA.
▪

If yes, you only need to upload the root certificate self-signed by
Equifax Secure Certificate Authority to PX3.

▪

If not, you need to find all missing issuer certificates, including the root
certificate, and upload them to PX3.

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 anauthentic source, which is usually its official website.
Important: To prevent the downloaded certificate from being modified ormanipulated, you must secure the download with TLS via a trusted
certificate.

3.

As it is found the Equifax Secure Certificate Authority's certificate is self
signed by 'Equifax Secure Certificate Authority', which indicates it is theroot CA, there are no more missing certificates to search for.
Step 3 -- Upload the missing certificate(s) to PX3:

1.

Paste the root certificate's content into a plain text file that will be
uploaded to PX3.
▪

Content copying must include the lines of "BEGIN CERTIFICATE" and"END CERTIFICATE".

2.

Save that file as a .pem, .crt or .cer file. In this example, it is named as"my-root.pem."

3.

Upload the file "my-root.pem" to PX3 for using the GMAIL SMTP service.

809

Appendix L: Additional PX3 Information

Note: If your SMTP server requires the upload of a certificate file comprisingmultiple certificates, make sure the order of these certificates is correct in the
file. See What is a Certificate Chain (on page 804).
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 todownload the root certificate from an authentic source, which is usually theroot CA's website, rather than from the server you want to connect.

Browsing through the Online Help
The PX3 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 PX3 online help:
1.

Click Online Documentation. See Web Interface Overview (on page 164).

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▪

To view the previous topic, click the Previous icon▪

To view the first topic, click the Home icon▪

.

To expand any topic, click the white arrow prior to the topic, or
double-click that topic. The arrow turns into a black, gradient arrowand sub-topics appear below the topic.
To collapse any expanded topic, click the black, gradient arrowprior to the topic, or double-click the expanded topic. The arrow thenturns into a white arrow , and all sub-topics below that topic
disappear.

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

The search results are displayed in the left pane.

810.

To expand or collapse a topic that contains sub-topics, do the following:▪

6.

in the toolbar.

,

Appendix L: Additional PX3 Information

7.

To have the left pane show the list of topics, click the Contents tab at thebottom.

8.

To show the Index page, click the Index tab.

9.

To email any URL link to the currently selected topic to any person, clickthe "Email this page" iconin the toolbar.

10. To email your comments or suggestions regarding the online help to
Raritan, click the "Send feedback" icon.

11. To print the currently selected topic, click the "Print this page" icon.

811

Appendix M Integration
The PX3 can work with certain Raritan or third-party products to provide
diverse power solutions.

In This Chapter
Dominion KX II / III Configuration .....................................................................812
Dominion KSX II, SX or SX II Configuration ........................................................817
Power IQ Configuration ....................................................................................822
dcTrack..............................................................................................................823

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) beconnected to a KX III at once since performance may be affected.

812

Appendix M: Integration

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▪

PX2, PX3 or PX3TS series: RJ-45 "FEATURE" port

2.

Connect the female RJ-45 connector of the D2CIM-PWR to any of theavailable female system port connectors on the KX III using a straight
through Cat5 cable.

3.

Attach an AC power cord to the target server and an available rack PDU
outlet.

4.

Connect the rack PDU to an AC power source.

5.

Power on the device.

Diagram key
PX rack PDU
D2CIM-PWR
KX III813

Appendix M: Integration

D2CIM-PWR to rack PDU connection
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 nameto the outlet.
To name the rack PDU and outlets:
Note: CommandCenter Secure Gateway does not recognize rack PDU names
containing spaces.

814

1.

Enter the Name of the rack PDU (if needed).

2.

Change the [Outlet] Name if desired. (Outlet names default to the outlet#.)

Appendix M: Integration

3.

Click OK.

815

Appendix M: Integration

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 nameis replaced by the target server name (even if you assigned another name to theoutlet).
1.

On the Port Configuration page, select the target server you areassociating 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 PowerTo 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 beturned on and its state will be displayed as 'on'.
To turn an outlet off:

816

1.

Click Off next to the outlet you want to power off.

2.

Click OK on the Power Off dialog.

Appendix M: Integration

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 Portdialog 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 thedialog.

Dominion KSX II, SX or SX II Configuration
Raritan PX3 support the integration with Raritan's serial access products Dominion KSX II, Dominion SX and Dominion SX II.
Cables used for connecting the PX3 to different Dominion access products aredifferent.
•••

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 PX3 via SX / SX II, treat the PX3 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 capablemodel.
Connecting a Rack PDU

To connect the Raritan PX to the KSX II:
1.

2.

Connect one end of a Cat5 cable to the following ports of different Raritan
PX.
▪

PX1 series: RJ-45 "SERIAL" port▪

PX2, PX3 or PX3TS series: RJ-45 "FEATURE" port

Connect the other end of the Cat5 cable to either the Power Ctrl. 1 orPower Ctrl. 2 ports on the back of the KSX II.

817

Appendix M: Integration

3.

Attach an AC power cord to the target server and an available rack PDU
outlet.

4.

Connect the rack PDU to an AC power source.

5.

Power on the 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 becorrectly detected, especially after swapping 8 and 20 outlet rack PDU
models.

Diagram key
KSX IIPX SERIAL or
FEATURE port

KSX II Power Ctrl.
1 Port or Power
Ctrl. 2 Port

Cat5 cable

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 816).
Dominion SX and SX II
By connecting to a Dominion SX or SX II device, you can associate one or more
outlets on a PX3 device to specific SX or SX II ports.

818

Appendix M: Integration

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

PX appliance
SX II

819

Appendix M: Integration

Dominion SX
Configuring a PX3 on Dominion SX

820

1.

Choose Setup > Power Strip Configuration.

2.

Click Add. The Power Strip Configuration screen appears.

3.

Type a name and description in the Name and Description fields.

4.

Select the number of outlets from the Number of Outlets drop-down
menu.

5.

Type the port number in the Port field.

6.

Click OK.

Appendix M: Integration

Power Control

1.

Choose Power Control > Power Strip Power Control. The Outlet Control
screen appears.

2.

Check the box of outlet number you wish to control, and click On/Off
buttons to power on/off the selected outlet(s).

3.

A confirmation message appears, indicating successful operation.

821

Appendix M: Integration

Checking Power Strip Status

1.

Choose Power Control > Power Strip Status.

2.

A status box appears, displaying details of the controlled PX3, 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 datafrom different PDUs installed in your server room or data center. With thissoftware, 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.

822

Appendix M: Integration

dcTrack
Sunbird's dcTrack® is a product that allows you to manage the data center. The
PX3 is categorized as a power item in dcTrack. dcTrack offers an import wizard
for conveniently adding the PX3 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 andhumidity
Optimize the data center growth

For more information on dcTrack, refer to the online help accessible from thedcTrack 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 anddeep visibility into the data center. It empowers data center managers to planfor growth and change by optimizing their current operations, assets, andinfrastructure.
With dcTrack, you can view everything in the data center from servers, blades,
virtual servers and applications to data networks, IP addressing space andcabling. dcTrack also allows you to track real-time power consumption andmanage 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 toimport AutoCAD® 2012 (and earlier) objects to build a data center map.
If you currently maintain data center information in spreadsheet format, thatdata can be imported into dcTrack using the Import wizard.
Isolate potential problems with end-to-end power and data circuits by visuallytracing them. This allows you to identify all intermediate circuit points andlocate problems.
By using dcTrack's workflow and change management feature, data center
managers are better able to enforce best practices across the enterprise andmeet 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 ® forpower and environmental monitoring.

823

Appendix M: Integration

Asset Management Strips and dcTrack
If any asset strips are connected to the PX3, the PX3 can transmit theirinformation to Sunbird's dcTrack. All you have to do is to add the PX3 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 AssetManagement Strips (on page 68).
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, theconnection/disconnection events are pulled into dcTrack, and displayed in the
dcTrack Web Client.

••

To poll and display asset management events in dcTrack
The PX3 that the asset strip is connected to must exist in dcTrack.
Each IT item connected to the asset strip via an asset tag must exist in
dcTrack.
You do not need to manually enter the asset tag IDs for IT items that
already exist in dcTrack as long as these items are in the Installed status.
Simply, plug the item's asset tag into an asset strip that is connected to the
PX3 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.

824

Index++12V Power Supply Sensor • 44, 129, 182, 186

1
1U and 2U Port Locations • 117
1U Products • 2

2
2U Products • 2

A
A Note about Enabling Thresholds • 455
A Note about Firmware Upgrade Time • 410
A Note about Infinite Loop • 371
A Note about Untriggered Rules • 372
About the Interface • 456
About the Link ID • 90
Action Group • 335, 338
Actuator Configuration Commands • 583, 600
Actuator Control Operations • 616
Actuator Information • 473
Adding a Firewall Rule • 535
Adding a Link Unit • 87
Adding a Monitored Device • 601
Adding a Radius Server • 580
Adding a Role-Based Access Control Rule • 548
Adding an LDAP Server • 573, 579
Adding Attributes to the Class • 731
Adding LDAP/LDAPS Servers • 301, 303, 307
Adding Radius Servers • 301, 306, 307, 736
Adding, Removing or Swapping Cascaded Devices• 277
Additional PX3 Information • 772
AD-Related Configuration • 737, 755, 768
Alarm • 335, 337
Alerts • 125, 149, 150
Alerts Notice in a Yellow or Red Screen • 121, 147,
181
All Privileges • 562, 568, 571
Altitude Correction Factors • 206, 496, 787
APIPA and Link-Local Addressing • 2, 31, 160, 270,
288
Applicable Models • xvii

Assertion Timeout Example for Temperature
Sensors • 781
Asset Management Commands • 606
Asset Management Strips and dcTrack • 824
Asset Management Tag List • 375, 378
Asset Management Tag Log • 375, 381
Asset Strip • 138, 140, 224, 225
Asset Strip Automatic Firmware Upgrade • 233
Asset Strip Information • 715
Asset Strip Management • 606
Asset Strip Settings • 485
Assets • 125, 137
Associating Outlets with Target Devices • 816
Authentication Commands • 571
Authentication Settings • 482, 574, 577
Automatic and Manual Modes • 121, 125, 386
Automatically Completing a Command • 460, 461,
622
Automatically Create Pairwise Outlet Groups • 108
Available Actions • 79, 282, 316, 334, 338, 345,
354, 367, 426, 448
Available Data of the Outlets Overview Page • 192,
193

B
Backup and Restore of Device Settings • 397, 411,
418, 646
Backup and Restore via SCP • 419, 626
Beeper • 156, 183
Before You Begin • 3
Browsing through the Online Help • 166, 810
Built-in Rules and Rule Configuration • 316, 317,
367
Bulk Configuration • 33, 397, 411, 418, 625, 646
Bulk Configuration Methods • 25, 33
Bulk Configuration or Firmware Upgrade via
DHCP/TFTP • 33, 407, 412, 417, 641, 655
Bulk Configuration Restrictions • 411, 412
Bulk Configuration via SCP • 412, 417, 625, 632
Bulk Configuration/Upgrade Procedure • 656, 657
Button-Type Locking Outlets • 20

C
Calendar • 312, 314
Card Readers • 439, 444, 445

825

IndexCascading All Devices via USB • 35, 40, 118
Cascading Multiple PX3 Devices for Sharing
Ethernet Connectivity • 22, 24, 34, 256, 270,
400
Cascading Troubleshooting • 35, 277, 790
Changing a User's Password • 557
Changing HTTP(S) Settings • 251, 279, 289
Changing Measurement Units • 562, 566
Changing Modbus Settings • 81, 252, 279, 285
Changing SSH Settings • 241, 252, 279, 284
Changing Storage Settings • 340, 341, 426, 428,
429, 432, 434
Changing Telnet Settings • 252, 279, 285, 456
Changing the Inlet Name • 555
Changing the LAN Duplex Mode • 509
Changing the LAN Interface Speed • 508
Changing the Modbus Configuration • 526
Changing the Modbus Port • 527
Changing the Outlet Name • 554
Changing the Overcurrent Protector Name • 556
Changing the PDU Name • 494
Changing the Role(s) • 562
Changing the Sensor Description • 585
Changing the Sensor Name • 583
Changing the SSH Configuration • 523
Changing the SSH Port • 523
Changing the Telnet Configuration • 522
Changing the Telnet Port • 523
Changing the UDP Port • 605
Changing Your Own Password • 565
Changing Your Password • 162, 240, 241
Checking Lua Scripts States • 391, 392, 393
Checking Power Strip Status • 822
Checking RCM State and Current • 690, 692
Checking RCM States and Current • 697
Checking the Accessibility of NTP Servers • 533
Checking the Branch Circuit Rating • 4
Circuit Breaker Orientation Limitation • 5, 6, 7, 8,
10, 11
Circuit Breakers • 151
Clearing Diagnostic Log for Network Connections •493
Clearing Event Log • 492
Clearing Information • 492
CLI Operations for RCM • 700
Closing a Local Connection • 460
Combining Regular Asset Strips • 69
Command History • 488

826

Commands for Environmental Sensors • 596
Commands for Inlet Pole Sensors • 592, 702
Commands for Inlet Sensors • 589, 702
Commands for Overcurrent Protector Sensors •595
Common Network Settings • 253, 256
Compliance with IEC 62020 • 688, 702
config.txt • 33, 629, 631, 643, 645, 648, 678, 681,
682
Configuration Files • 641, 643, 656, 678
Configuration or Firmware Upgrade with a USB
Drive • 34, 85, 412, 417, 641, 651, 652, 655
Configuring a Multi-Inlet Model • 187, 190
Configuring a PX3 on Dominion SX • 820
Configuring Data Push Settings • 252, 340, 373
Configuring DNS Parameters • 506
Configuring Environmental Sensors' Default
Thresholds • 587
Configuring IPv4 Parameters • 498
Configuring IPv6 Parameters • 502
Configuring Login Settings • 252, 289, 308
Configuring Network Services • 278, 458
Configuring Network Settings • 3, 23, 36, 40, 251,
253, 265, 796
Configuring NTP Server Settings • 455
Configuring Password Policy • 252, 289, 309
Configuring Rack PDU Targets • 812
Configuring Security Settings • 289
Configuring SMTP Settings • 252, 279, 283, 343,
348
Configuring SNMP Settings • 242, 251, 279, 281,
335, 447
Configuring the Cascading Mode • 519
Configuring the PX3 • 24
Configuring the PX3 Device and Network • 493
Configuring the Serial Port • 79, 80, 252, 387, 459
Configuring Webcams and Viewing Live Images •78, 342, 426, 427, 430, 432, 437
Connecting a DPX2 Sensor Package to DX2, DX or
DPX3 • 50, 52, 53, 56, 68
Connecting a GSM Modem • 79, 347
Connecting a Logitech Webcam • 78, 425
Connecting a Mobile Device to PX3 • 25, 118
Connecting a Modbus RTU Device or Bus • 81, 286
Connecting a PX PDU • 813
Connecting a PX3 Locking Line Cord • 14, 116
Connecting a Rack PDU • 817

IndexConnecting a Schroff LHX/SHX Heat Exchanger •80, 234
Connecting an Analog Modem • 79, 459
Connecting an External Beeper • 80, 233
Connecting Asset Management Strips • 68, 225,
373, 824
Connecting Blade Extension Strips • 73
Connecting Composite Asset Strips (AMS-Mx-Z) •75
Connecting External Equipment (Optional) • 48,
118
Connecting Raritan Environmental Sensor
Packages • 47, 48, 202
Connecting Regular Asset Strips to PX3 • 71, 77
Connecting the PDU to a Power Source • 21
Connecting the PX3 to a Computer • 2, 25, 31, 270,
684, 685, 790
Connecting the PX3 to Your Network • 22, 24, 253
Connection Port Functions • 24, 118
Connection Ports • 24, 117
Control Buttons • 122, 706
Controlling Outlets in Groups • 107
Copying an Existing Server's Settings • 573, 577
Creating a CSR • 296, 297, 298
Creating a New Attribute • 730
Creating a Role • 568
Creating a Self-Signed Certificate • 296, 299
Creating a User Profile • 556
Creating Configuration Files via Mass Deployment
Utility • 643, 651, 652
Creating IP Access Control Rules • 252, 289, 290,
293
Creating Role Based Access Control Rules • 252,
289, 294, 296
Creating Roles • 162, 240, 244, 246, 736
Creating Users • 159, 162, 240, 241, 245, 247, 250,
285, 301, 447
Curl Upload Return Codes • 681, 682
Customizing Bulk Configuration Profiles • 411, 414
Customizing the Date and Time • 531

D
Daisy-Chain Limitations of Composite Asset Strips• 76, 77
Dashboard • 167, 171, 186, 197, 337, 422, 694
Dashboard - Alarms • 172, 180, 335
Dashboard - Alerted Sensors • 125, 172, 176
Dashboard - Inlet History • 172, 178, 187

Dashboard - Inlet I1 • 172, 173, 187
Dashboard - OCP • 172, 175
Data Encryption in 'config.txt' • 648, 649, 652
Data for BTU Calculation • 788
Data Push Format • 373, 375
Date and Time Settings • 470
dcTrack • 823
dcTrack Overview • 823
Deassertion Hysteresis Example for Temperature
Sensors • 784
Default Log Messages • 44, 310, 317, 322, 340,
343
Default Measurement Units • 470
Default Voltage and Current Thresholds • 188, 196,
199, 785
Degaussing RCM Type B Sensors • 703
Deleting a Firewall Rule • 538
Deleting a Monitored Device • 602
Deleting a Role • 571
Deleting a Role-Based Access Control Rule • 551
Deleting a User Profile • 564
Designating the Master Unit • 86
Detailed Information on Outlet Pages • 193, 194
Determining the Authentication Method • 572
Determining the SSH Authentication Method • 524
Determining the Time Setup Method • 529, 531
Device Configuration/Upgrade Procedure • 641
Device Info • 3, 24, 25, 125, 141, 270
Device Information • 342, 396, 398, 436
Device Settings • 168, 251
devices.csv • 33, 631, 643, 645, 649, 650, 682
Device-Specific Settings • 411, 803
DHCP IPv4 Configuration in Linux • 656, 674
DHCP IPv4 Configuration in Windows • 656, 657
DHCP IPv6 Configuration in Linux • 656, 676
DHCP IPv6 Configuration in Windows • 656, 667
Diagnostic Commands • 620
Diagnostic Log for Network Connections • 256,
264, 265
Different CLI Modes and Prompts • 458, 459, 462,
492, 493, 494, 533, 616, 620
Disabling or Enabling Front Panel RCM Self-Test •387, 694, 698, 720
Disconnecting a PX3 Locking Line Cord • 15
Displays for Master and Link Units • 111
Dominion KSX II • 817
Dominion KSX II, SX or SX II Configuration • 239,
817

827

IndexDominion KX II / III Configuration • 239, 812
Dominion SX • 820
Dominion SX and SX II • 818
Dominion SX II • 819
Door Handle Status and Control • 208, 443
Dot-Matrix LCD Display • 119
Download via Curl • 678, 679
Download via Web Browsers • 678
Downloading Diagnostic Data via SCP • 627
Downloading Diagnostic Information • 397, 421
Downloading Raw Configuration • 678
Downloading SNMP MIB • 282, 447, 452, 699
DPX Sensor Packages • 46, 48, 57
DPX2 Sensor Packages • 46, 48, 54
DPX3 Sensor Packages • 46, 48, 52
Dual Ethernet Connection • 22, 24
DX Sensor Packages • 46, 48, 51
DX2 Sensor Packages • 46, 48, 49, 352

E
EAP CA Certificate Example • 511, 513, 517
Editing or Deleting a Rule/Action • 335, 367, 386
Editing or Deleting IP Access Control Rules • 293
Editing or Deleting Ping Monitoring Settings • 384
Editing or Deleting Role Based Access Control
Rules • 295
Editing or Deleting Roles • 248
Editing or Deleting Users • 162, 244, 247, 249
Editing rciusergroup Attributes for User Members• 733
Enabling and Configuring SNMP • 369, 370, 372,
447
Enabling or Disabling 802.11n High Throughput •516
Enabling or Disabling a User Profile • 559
Enabling or Disabling an Inlet (for Multi-Inlet PDUs)• 555
Enabling or Disabling Data Logging • 495
Enabling or Disabling EnergyWise • 604
Enabling or Disabling Front Panel Actuator Control• 552
Enabling or Disabling Front Panel Beeper-Sound
Control • 552
Enabling or Disabling Modbus • 526
Enabling or Disabling Peripheral Device AutoManagement • 497
Enabling or Disabling Service Advertising • 527
Enabling or Disabling SNMP v1/v2c • 524

828

Enabling or Disabling SNMP v3 • 525
Enabling or Disabling SSH • 523
Enabling or Disabling Strong Passwords • 544
Enabling or Disabling Telnet • 522
Enabling or Disabling the LAN Interface • 507
Enabling or Disabling the Read-Only Mode • 527
Enabling or Disabling the Restricted Service
Agreement • 539
Enabling Service Advertising • 252, 279, 288, 527
Enabling the Restricted Service Agreement • 160,
252, 289, 310
EnergyWise Configuration Commands • 604
EnergyWise Settings • 484
Entering Configuration Mode • 459, 493, 513, 514,
557, 564, 565, 701
Entering Diagnostic Mode • 459, 619, 794
Environmental Sensor Configuration Commands •583
Environmental Sensor Default Thresholds • 480
Environmental Sensor Information • 471, 713
Environmental Sensor Package Information • 472
Environmental Sensor Threshold Information •479
Equipment Setup Worksheet • 4, 637
Ethernet Interface Settings • 24, 145, 253, 257,
510
Event Log • 486
Event Rules and Actions • 44, 80, 156, 180, 183,
187, 196, 217, 237, 252, 281, 283, 316, 337, 373,
382, 391
Example • 531, 541, 557, 564, 565, 615
Ping Monitoring and SNMP Notifications • 382,
384
Example - Actuator Naming • 601
Example - Creating a Role • 571
Example - Default Upper Thresholds for
Temperature • 589
Example - Inlet Naming • 555
Example - OCP Naming • 556
Example - Outlet Naming • 554
Example - Ping Command • 622
Example - Server Settings Changed • 604
Example - Setting Up EnergyWise • 606
Example - Turning On a Specific Actuator • 618
Example 1 • 371
Example 1 - Asset Strip LED Colors for
Disconnected Tags • 613
Example 1 - Basic Security Information • 490

IndexExample 1 - Combination of ETH1's Activation,
Configuration Method and IP • 615
Example 1 - Creating a User Profile • 567
Example 1 - Environmental Sensor Naming • 587
Example 1 - IPv4 Firewall Control Configuration •553
Example 1 - PDU Naming • 497
Example 1 - Time Setup Method • 532
Example 1 - Upper Critical Threshold for a
Temperature Sensor • 598
Example 1 - Wireless Networking Mode • 528
Example 2 • 371
Example 2 - Adding an IPv4 Firewall Rule • 553
Example 2 - Combination of Upper Critical andUpper Warning Settings • 615
Example 2 - Data Logging Enabled • 498
Example 2 - Enabling IPv6 Protocol on the Ethernet
Interface • 528
Example 2 - In-Depth Security Information • 491
Example 2 - Modifying a User's Roles • 567
Example 2 - Primary NTP Server • 532
Example 2 - Rack Unit Naming • 613
Example 2 - Sensor Threshold Selection • 587
Example 2 - Warning Thresholds for Inlet Sensors •598
Example 3 • 371
Example 3 - Basic PDU Information • 491
Example 3 - Combination of SSID and PSKParameters • 616
Example 3 - Default Measurement Units • 567
Example 3 - Upper Thresholds for Overcurrent
Protector Sensors • 598
Example 3 - User Blocking • 553
Example 3 - Wireless Authentication Method • 528
Example 4 - Adding an IPv4 Role-based AccessControl Rule • 554
Example 4 - Combination of Upper Critical, Upper
Warning and Lower Warning Settings • 616
Example 4 - In-Depth PDU Information • 492
Example 4 - Static IPv4 Configuration • 528
Examples • 489, 497, 528, 532, 552, 566, 586, 598,
613
Existing Roles • 484
Existing User Profiles • 470, 483
Expansion RJ-45 Port Pinouts • 636
Extended Cascading with PX3 Devices • 38, 119External Beeper • 224, 233, 335, 339

F
FAQs • 83
Feature Port • 168, 223, 225, 233, 235, 239
Feature Ports Page • 111
Feature RJ-45 Port Pinouts • 635
Filling Out the Equipment Setup Worksheet • 4
Finding the Sensor's Serial Number • 203, 212
Firewall Control • 533
Firmware Update via SCP • 407, 624
Firmware Upgrade via USB • 407, 642, 653
Forcing a Password Change • 559
Forcing the Device Detection Mode • 614
FreeRADIUS Standard Attribute Illustration • 736,
754
FreeRADIUS VSA Illustration • 755, 767
From LDAP/LDAPS • 729
From Microsoft Active Directory • 729
Front Panel Operations for RCM • 125, 696, 718
Front Panel Settings • 121, 130, 208, 252, 386
Full Disaster Recovery • 410
Fuse • 153
Fuse Replacement on 1U Models • 155
Fuse Replacement on Zero U Models • 153
fwupdate.cfg • 641, 642, 643, 644, 648, 650, 653,
656

G
Gathering LDAP/Radius Information • 301, 302

H
Hardware Issue Detection • 173, 397, 421, 489
How Long a Link Remains Accessible • 430, 432
How the Automatic Management Function Works• 205, 215, 497

I
Identifying Cascaded Devices • 399, 400
Identifying Snapshots Folders on Remote Servers •429, 435, 436
Identifying the Sensor Port • 49
Identifying the Sensor Position and Channel • 204,
213
Idle Timeout • 543
Illustration - GMAIL SMTP Certificate Chain • 804,
807
Illustrations of Adding LDAP Servers • 575, 576

829

IndexIndividual OCP Pages • 197
Individual Outlet Pages • 192, 193
Individual Sensor/Actuator Pages • 136, 176, 203,
205, 206, 207, 217, 223
Initial Installation and Configuration • 21
Initial Network Configuration via CLI • 25, 32, 684,
685, 796
Inlet • 116, 125, 131, 167, 173, 174, 187, 190
Inlet Configuration Commands • 554
Inlet Information • 468, 708
Inlet Pole Sensor Threshold Information • 476, 701
Inlet Sensor Threshold Information • 474, 701
Installing a CA-Signed Certificate • 296, 298
Installing Cable Retention Clips on Outlets(Optional) • 17
Installing Cable Retention Clips on the Inlet(Optional) • 16
Installing or Downloading Existing Certificate andKey • 296, 300
Installing the USB-to-Serial Driver (Optional) • 32,
795
Integration • 812
Interface Names • 266, 269
Internal Beeper • 336, 339
Internal Beeper State • 182, 183, 692
Introduction • 1
Introduction to Asset Tags • 71
Introduction to PDU Components • 115
IP Configuration • 463, 464
IPv4 Address • 711
IPv4-Only or IPv6-Only Configuration • 463, 464

K
Keys that Cannot Be Uploaded • 629, 632, 678

L
Layout • 454
LCD Message for RCM Critical State • 696
LDAP Configuration Illustration • 301, 721
LDAP Settings • 573
Locking Outlets and Cords • 17, 18
Log an Event Message • 336, 340
Log Rows • 375, 377
Logging in to CLI • 457, 652, 685
Logging out of CLI • 623
Login • 25, 31, 159, 270, 794
Login Limitation • 542
Login, Logout and Password Change • 159

830

Logout • 163
Lowercase Character Requirement • 544
Lua Scripts • 252, 351, 389

M
MAC Address • 712
Main Menu • 121, 124, 697, 698
Maintenance • 168, 396
Make a Power Association • 816
Making a Power-Sharing Connection • 44
Managed vs Unmanaged Sensors/Actuators • 202,
209, 210
Managing External Authentication Settings • 301,
305, 307
Managing Firewall Rules • 535
Managing One Sensor or Actuator • 204, 205, 215
Managing Role-Based Access Control Rules • 548
Manually Changing PX3's Zero U LCD Orientation •120, 146
Manually Starting or Stopping a Script • 390, 391
Master Units Manage Link Units • 90
Maximum Ambient Operating Temperature • 3,
634
Maximum Password History • 546
Maximum Password Length • 544
Menu • 165, 167, 182, 187, 192, 195, 202, 224,
225, 233, 234, 239, 240, 251, 390, 392, 394, 396,
427, 429, 430, 440, 445, 690
Minimum Password Length • 544
Miscellaneous • 80, 133, 224, 225, 234, 252, 342,
352, 394, 399, 452
Mixing Diverse Sensor Types • 62, 63
Modifying a Firewall Rule • 537
Modifying a Monitored Device's Settings • 602
Modifying a Role • 570
Modifying a Role-Based Access Control Rule • 549
Modifying a User Profile • 557
Modifying a User's Personal Data • 558
Modifying an Existing LDAP Server • 577
Modifying an Existing Radius Server • 581
Modifying Firewall Control Parameters • 533
Modifying or Deleting a Script • 389, 393
Modifying or Removing Bulk Profiles • 417
Modifying Role-Based Access Control Parameters• 546
Modifying SNMPv3 Settings • 559
Monitoring Server Accessibility • 252, 382, 384
Mounting 1U or 2U Models • 12

IndexMounting Zero U Models Using Button Mount • 7
Mounting Zero U Models Using Claw-Foot
Brackets • 8
Mounting Zero U Models Using L-Brackets • 6
Mounting Zero U Models Using L-Brackets andButtons • 11
Mounting Zero U Models Using Two Rear Buttons• 10
Multi-Command Syntax • 535, 542, 543, 544, 547,
557, 558, 559, 562, 565, 587, 589, 592, 595, 596,
600, 602, 615
Muting the Internal Beeper • 128, 130, 387

N
Naming a Rack Unit • 610
Naming an Asset Strip • 607
Naming the Rack PDU (Port Page for Power Strips)• 814
Network Configuration • 462
Network Configuration Commands • 498
Network Connections Diagnostic Log • 487
Network Diagnostics • 397, 420
Network Interface Settings • 465
Network Service Settings • 466
Network Troubleshooting • 420, 619
NPS Standard Attribute Illustration • 736
NPS VSA Illustration • 755
Numeric Character Requirement • 545

O
OCPs • 125, 132, 167, 176, 195, 197, 199
OCPs Page • 110
Old Generations of PX3 Models • 120, 410, 704
Operating the Dot-Matrix LCD Display • 121, 123,
124, 126, 134, 151, 704
Operating the LCD Display • 707
Optional Parameters • 573, 574
Outlet Configuration Commands • 554
Outlet Groups • 103
Outlet Information • 467, 707
Outlets • 117, 192, 193
Overcurrent Protector Configuration Commands •556
Overcurrent Protector Information • 469, 710
Overcurrent Protector Sensor Threshold
Information • 478
Overview of the Cascading Modes • 270, 272
Overview of the LCD Display • 705, 706

P
Package Contents • 1, 3
Pairwise Outlet Groups • 108
Panel Components • 115
Password Aging • 542
Password Aging Interval • 543
PDU • 125, 128, 156, 166, 167, 182, 184, 186, 188
PDU Configuration • 184, 466
PDU Configuration Commands • 494
PDU Linking • xix, 82
PDU Linking CLI Commands • 114
PDU Linking in the CLI • 113
PDU Linking in the Web GUI • 85
Performing Bulk Configuration • 411, 415
Peripherals • 46, 49, 51, 125, 133, 167, 202, 206,
208, 210, 212, 215, 217, 218, 219, 222, 223, 387,
444
Peripherals Page • 110
Placeholders for Custom Messages • 343, 344, 346,
347, 348, 363
Port Forwarding Examples • 161, 271, 274, 275
Port Number Syntax • 270, 273, 275, 792
Possible Root Causes • 790
Power CIM • 224, 239
Power Control • 818, 821
Power IQ Configuration • 822
Power-Sharing Configurations and Restrictions •43, 44, 45
Power-Sharing Restrictions and Connection • 43,
119, 186, 687, 688, 690, 692
Preparing the Installation Site • 3
Product Models • 1
Push Out Sensor Readings • 336, 340
PX3 Models with Residual Current Monitoring •
183, 386, 686, 718
PX3 'Phase I' Front Panel Display • 705
PX3 'Phase II' Front Panel Display • 704
PX3-1000 Series • 117

Q
Querying Available Parameters for a Command •460, 461
Querying DNS Servers • 620
Quick Access to a Specific Page • 160, 169
Quitting Configuration Mode • 493, 494, 541
Quitting Diagnostic Mode • 620

831

IndexR
Rack Unit Configuration • 610
Rack Unit Settings of an Asset Strip • 485
Rackmount Safety Guidelines • 5
Rackmount, Inlet and Outlet Connections • 5
Rack-Mounting the PDU • 5
RADIUS Configuration Illustration • 301, 736
Radius Settings • 580
Raritan Training Website • 789
Raw Configuration Upload and Download • 412,
417, 650, 655, 678
RCM Critical State Alarm • 692
RCM Current Sensor • 475, 477, 591, 594, 686,
694
RCM Information • 696, 718
RCM Residual Current and State Objects • 700
RCM Self-Test • 689
RCM SNMP Operations • 699
RCM State Sensor • 687, 691
RCM Trap • 699
Rebooting the PX3 • 397, 423
Record Snapshots to Webcam Storage • 336, 340
Releasing a Link Unit • 91
Reliability Data • 489
Reliability Error Log • 489
Reliability Hardware Failures • 489
Re-linking a Link Unit • 93
Remembering User Names and Passwords • 163
Removing an Existing LDAP Server • 580
Removing an Existing Radius Server • 582
Removing the Uploaded Certificate or Private Key• 514
Replaceable Controller • 115, 157
Request LHX/SHX Maximum Cooling • 336, 342
Reserving IP Addresses in DHCP Servers • 773, 774,
775
Reserving IP in Linux • 775
Reserving IP in Windows • 774
Reset Button • 151
Resetting All Settings to Factory Defaults • 397,
423, 684
Resetting the Button-Type Circuit Breaker • 152
Resetting the Handle-Type Circuit Breaker • 152
Resetting the PX3 • 618
Resetting to Factory Defaults • 151, 424, 619, 684
Restarting the PDU • 618
Restricted Service Agreement • 539

832

Restrictions of Port-Forwarding Connections • 38,
41, 793Retrieving Previous Commands • 460, 461, 622
Retrieving Software Packages Information • 397,
424
Returning User Group Information • 729
RJ45-to-DB9 Cable Requirements for Computer
Connections • 32, 118, 773
RJ45-to-DB9 Cable Requirements for Modem
Connections • 33, 79, 80, 118, 772
Role Configuration Commands • 568
Role of a DNS Server • 723, 790
Role-Based Access Control • 546
Running RCM Self-Test • 697, 698, 700, 703

S
Safety Guidelines • ii
Safety Instructions • iii, 3Sample Event Rules • 319, 367
Sample Inlet-Level Event Rule • 370
Sample Outlet-Level Event Rule • 368
Sample PDU-Level Event Rule • 367
Saving User Credentials for PDView's Automatic
Login • 28, 29
Scheduling an Action • 317, 340, 354, 361, 693
Scheduling RCM Self-Test • 693
Schroff LHX/SHX • 224, 234
SecureLock™ Outlets and Cords • 18
Security Configuration Commands • 533
Security Settings • 481
Send an SNMP Notification • 282, 336, 350
Send Email • 322, 336, 343, 357, 363
Send Sensor Report • 250, 336, 345, 360
Send Sensor Report Example • 345, 356, 357
Send SMS Message • 336, 347, 363
Send Snapshots via Email • 336, 348, 363
Sending Links to Snapshots or Videos • 426, 428,
430
Sensor Descriptors for Inlet Active Power • 375,
376
Sensor Log • 375
Sensor RJ-45 Port Pinouts • 634
Sensor Threshold Configuration Commands • 589
Sensor Threshold Settings • 185, 189, 197, 200,
207, 208, 218, 454, 695, 777
Sensor/Actuator Location Example • 219, 222, 223
Sensor/Actuator States • 126, 135, 177, 203, 204,
210, 211

IndexSerial Port Configuration Commands • 613
Serial Port Settings • 484
Serial RS-232 • 634, 720Server Reachability Configuration Commands •601
Server Reachability Information • 487
Server Reachability Information for a SpecificServer • 488
Server Status Checking • 383
Setting an LED Color for a Rack Unit • 611, 612
Setting an LED Mode for a Rack Unit • 611, 612
Setting Data Logging • 252, 372, 374, 495
Setting Data Logging Measurements Per Entry •495
Setting Default Measurement Units • 206, 240,
249, 250, 563, 565
Setting Ethernet EAP Parameters • 510
Setting Front Panel RCM Self-Test • 703
Setting IPv4 Static Routes • 501
Setting IPv6 Static Routes • 505
Setting LAN Interface Parameters • 507
Setting LED Colors for Connected Tags • 609, 611,
612
Setting LED Colors for Disconnected Tags • 610,
611, 612
Setting Network Service Parameters • 521
Setting NTP Parameters • 530, 533
Setting RCM Current Thresholds • 687, 691, 692,
701
Setting RCM DC Current Thresholds • 691, 692,
694
Setting RCM Thresholds • 700
Setting the Alarmed to Normal Delay for DX-PIR •586
Setting the Automatic Daylight Savings Time • 532
Setting the Baud Rates • 614
Setting the BSSID • 519
Setting the Cascading Mode • 2, 24, 34, 35, 36, 38,
40, 143, 253, 254, 256, 260, 270, 272, 277, 400,
401
Setting the Date and Time • 252, 312, 342, 436,
455
Setting the Ethernet Authentication Method • 509
Setting the HTTP Port • 521
Setting the HTTPS Port • 522
Setting the IPv4 Address • 500
Setting the IPv4 Configuration Mode • 498
Setting the IPv4 Gateway • 500

Setting the IPv4 Preferred Host Name • 499
Setting the IPv6 Address • 504
Setting the IPv6 Configuration Mode • 502
Setting the IPv6 Gateway • 505
Setting the IPv6 Preferred Host Name • 503
Setting the LED Operation Mode • 611
Setting the Maximum Number of Active Powered
Dry Contact Actuators • 497
Setting the Polling Interval • 606
Setting the PSK • 516
Setting the Registry to Permit Write Operations to
the Schema • 730
Setting the SNMP Configuration • 524
Setting the SNMP Read Community • 525
Setting the SNMP Write Community • 525
Setting the SSID • 515
Setting the sysContact Value • 525
Setting the sysLocation Value • 526
Setting the sysName Value • 526
Setting the Time Zone • 455, 531
Setting the Wireless Authentication Method • 516
Setting the X Coordinate • 584
Setting the Y Coordinate • 584
Setting the Z Coordinate • 496, 585
Setting the Z Coordinate Format for Environmental
Sensors • 496, 585, 600
Setting Thresholds for Total Active Energy orPower • 183, 184
Setting Up a TLS Certificate • 252, 289, 296
Setting Up External Authentication • 252, 289, 301,
790
Setting Wireless EAP Parameters • 517
Setting Wireless Parameters • 515
Setting Your Preferred Measurement Units • 206,
240, 244, 249, 250
Showing Information • 462
Showing Network Connections • 620
Showing Residual Current Monitoring Information• 701
Showing the Firmware Upgrade Progress • 150,407
SHX Request Maximum Cooling • 238, 239
Single Login Limitation • 542
Slave Device Events in the Log • 793
SmartLock • 439, 440, 445
SmartLock and Card Reader • 168, 438
SNMP Gets and Sets • 453
SNMP Sets and Thresholds • 454

833

IndexSNMPv2c Notifications • 282, 448
SNMPv3 Notifications • 282, 448, 449
Sorting a List • 170, 176, 192, 195, 203, 227, 245,
248, 265, 363, 403, 411
Special Character Requirement • 546
Specifications • 5, 634
Specifying the Agreement Contents • 541
Specifying the Asset Strip Orientation • 609
Specifying the CC Sensor Type • 583
Specifying the Device Altitude • 496
Specifying the EnergyWise Domain • 605
Specifying the EnergyWise Secret • 605
Specifying the Number of Rack Units • 607
Specifying the Rack Unit Numbering Mode • 608
Specifying the Rack Unit Numbering Offset • 608
Specifying the SSH Public Key • 524, 564
Standard Attributes • 736
Start or Stop a Lua Script • 336, 351, 390, 391
Static Route Examples • 253, 257, 266, 501, 505
Step A
Add Your PX3 as a RADIUS Client • 736, 737,
755, 756
Step A. Determine User Accounts and Roles • 721
Step B
Configure Connection Policies and Standard
Attributes • 737, 741
Configure Connection Policies andVendor-Specific Attributes • 755, 760
Step B. Configure User Groups on the AD Server •722
Step C. Configure LDAP Authentication on the PX3• 723
Step D. Configure Roles on the PX3 • 726
Strong Passwords • 544
Supported Maximum DPX Sensor Distances • 57,
61
Supported Sensor Configurations for Power
Sharing • 45, 46
Supported Web Browsers • 159
Supported Wireless LAN Configuration • 23, 791
Switch LHX/SHX • 337, 352
Switch Peripheral Actuator • 337, 352
Switching Off an Actuator • 617
Switching On an Actuator • 617
Switching to a Different PDU • 92
Syslog Message • 337, 353
System and USB Requirements • 641, 642

834

T
Testing the Network Connectivity • 621, 794
TFTP Requirements • 656, 657
The ? Command for Showing Available Commands• 460
The Ping Tool • 793, 794
The PX3 MIB • 453
Threaded Grounding Point • 158
Thresholds and Sensor States • 777
Time Configuration Commands • 528
Time Units • 184, 308, 309
TLS Certificate Chain • 259, 263, 283, 304, 354,
373, 804
Tracing the Route • 622
Turning Outlets On/Off and Cycling Power • 816,
818

U
Unbalanced Current Calculation • 787
Unblocking a User • 309, 618
Unpacking the Product and Components • 3Updating the LDAP Schema • 729
Updating the PX3 Firmware • xix, 396, 406, 624
Updating the Schema Cache • 733
Upgrade Guidelines for Existing Cascading Chains •406, 408
Upgrade Sequence in an Existing Cascading Chain• 34, 408
Upload via Curl • 33, 680, 681, 682
Uploading or Downloading Raw Configuration
Data • 33, 626, 629, 678, 680
Uploading Raw Configuration • 680
Uppercase Character Requirement • 545
USB Wireless LAN Adapters • 23, 36, 40, 791
USB-Cascaded Device's Position • 717
User Blocking • 543
User Configuration Commands • 556
User Interfaces Showing Default Units • 250
User Management • 168, 240
Using an Optional DPX3-ENVHUB4 Sensor Hub •58, 62Using an Optional DPX-ENVHUB2 cable • 59
Using an Optional DPX-ENVHUB4 Sensor Hub • 58
Using Default Thresholds • 586
Using SCP Commands • 624
Using SNMP • 407, 447
Using the CLI Command • 619, 685

IndexUsing the Command Line Interface • 186, 279, 456,
685, 700
Using the Reset Button • 684
Using the Web Interface • 159

V
Vendor-Specific Attributes • 736, 755
Viewing and Managing Locally-Saved Snapshots •340, 423, 432, 435
Viewing Connected Users • 396, 403, 430
Viewing Firmware Update History • 396, 410
Viewing Link Unit Information • 95
Viewing or Clearing the Local Event Log • 283, 301,
353, 396, 405

W
Ways to Probe Existing User Profiles • 789
Web Interface Operations for RCM • 189, 690
Web Interface Overview • 164, 810
Webcam Management • 168, 404, 425
What is a Certificate Chain • 804, 810
What's New in the PX3 User Guide • xix
Windows NTP Server Synchronization Solution •313, 315
Wired Network Settings • 22, 24, 253, 254, 271,
288, 723
Wireless Network Settings • 253, 260, 271, 517
With an Analog Modem • 459
With HyperTerminal • 457, 618
With SSH or Telnet • 458, 794
Writing or Loading a Lua Script • 389, 393

Y
Yellow- or Red-Highlighted Sensors • 123, 126, 134,
147, 187, 195, 203, 208, 211, 217, 237, 779

Z
Z Coordinate Format • 205, 222
Zero U Connection Ports • 117
Zero U Models' Relocatable Inlet • 116
Zero U Products • 1835