advertisement
PX3TS Transfer Switch
User Guide
Xerus
™
Firmware v3.3.10
Copyright © 2017 Raritan, Inc.
PX3TS-1A-v3.3.10-E
March 2017
255-80-0033-00
Safety Guidelines
WARNING! Read and understand all sections in this guide before installing or operating this product.
WARNING! Connect this product to an AC power source whose voltage is within the range specified on the product's nameplate. Operating this product outside the nameplate voltage range may result in electric shock, fire, personal injury and death.
WARNING! Connect this product to an AC power source that is current limited by a suitably rated fuse or circuit breaker in accordance with national and local electrical codes. Operating this product without proper current limiting may result in electric shock, fire, personal injury and death.
WARNING! Connect this product to a protective earth ground. Never use a "ground lift adaptor" between the product's plug and the wall receptacle. Failure to connect to a protective earth ground may result in electric shock, fire, personal injury and death.
WARNING! This product contains no user serviceable parts. Do not open, alter or disassemble this product. All servicing must be performed by qualified personnel. Disconnect power before servicing this product. Failure to comply with this warning may result in electric shock, personal injury and death.
WARNING! Use this product in a dry location. Failure to use this product in a dry location may result in electric shock, personal injury and death.
WARNING! Do not rely on this product's receptacle lamps, receptacle relay switches or any other receptacle power on/off indicator to determine whether power is being supplied to a receptacle.
Unplug a device connected to this product before performing repair, maintenance or service on the device. Failure to unplug a device before servicing it may result in electric shock, fire, personal injury and death.
WARNING! Only use this product to power information technology equipment that has a UL/IEC
60950-1 or equivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury and death.
WARNING! Do not use a Raritan product containing outlet relays to power large inductive loads such as motors or compressors. Attempting to power a large inductive load may result in damage to the relay.
WARNING! Do not use this product to power critical patient care equipment, fire or smoke alarm systems. Use of this product to power such equipment may result in personal injury and death.
WARNING! This product contains a chemical known to the State of California to cause cancer, birth defects, or other reproductive harm.
Safety Instructions
1. Installation of this product should only be performed by a person who has knowledge and experience with electric power.
2. Make sure the line cord is disconnected from power before physically mounting or moving the location of this product.
3. This product is designed to be used within an electronic equipment rack. The metal case of this product is electrically bonded to the line cord ground wire. A threaded grounding point on the case may be used as an additional means of protectively grounding this product and the rack.
4. Examine the branch circuit receptacle that will supply electric power to this product. Make sure the receptacle’s power lines, neutral and protective earth ground pins are wired correctly and are the correct voltage and phase. Make sure the branch circuit receptacle is protected by a suitably rated fuse or circuit breaker.
5. If the product is a model that contains receptacles that can be switched on/off, electric power may still be present at a receptacle even when it is switched off.
This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated into another language without express prior written consent of Raritan, Inc.
© Copyright 2017 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.
FCC Information
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a commercial installation. This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential environment may cause harmful interference.
VCCI Information (Japan)
Raritan is not responsible for damage to this product resulting from accident, disaster, misuse, abuse, non-Raritan modification of the product, or other events outside of Raritan's reasonable control or not arising under normal operating conditions.
If a power cable is included with this product, it must be used exclusively for this product.
Contents
Safety Guidelines
Safety Instructions
What's New in the PX3TS User Guide xvii
Chapter 1 Introduction 1
Product Models .................................................................................................................................... 1
PX3TS Overview .................................................................................................................................... 2
Front View .................................................................................................................................. 2
Rear View ................................................................................................................................... 3
Package Contents ................................................................................................................................ 4
APIPA and Link-Local Addressing ...................................................................................................... 4
Before You Begin.................................................................................................................................. 5
Unpacking the Product and Components ................................................................................ 5
Preparing the Installation Site ................................................................................................. 6
Checking the Branch Circuit Rating ......................................................................................... 6
Filling Out the Equipment Setup Worksheet ........................................................................... 6
Chapter 2 Rackmount, Inlet and Outlet Connections 7
Rackmount Safety Guidelines ............................................................................................................. 7
Mounting a PX3TS Device .................................................................................................................... 7
Inlet and Outlet Power Connections ................................................................................................. 10
Chapter 3 Initial Installation and Configuration 11
Connecting Power and Equipment .................................................................................................... 11
Connecting the PX3TS to Your Network ........................................................................................... 11
USB Wireless LAN Adapters................................................................................................... 12
Supported Wireless LAN Configuration ................................................................................. 13
Configuring the PX3TS ....................................................................................................................... 13
Connecting the PX3TS to a Computer .................................................................................... 14
Installing the USB-to-Serial Driver (Optional) ...................................................................... 16
Initial Network Configuration via CLI ..................................................................................... 17
ii iii
vii
Contents
Bulk Configuration Methods .............................................................................................................. 22
Cascading Multiple PX3TS Devices for Sharing Ethernet Connectivity .......................................... 23
Cascading Guidelines for Port Forwarding ............................................................................ 24
Cascading the PX3TS via USB................................................................................................. 24
Chapter 4 Connecting External Equipment (Optional) 27
Connecting Environmental Sensor Packages .................................................................................. 27
DPX Sensor Packages ............................................................................................................. 28
DPX2 Sensor Packages ........................................................................................................... 33
DPX3 Sensor Packages ........................................................................................................... 35
DX Sensor Packages ............................................................................................................... 37
Using an Optional DPX3-ENVHUB4 Sensor Hub ................................................................... 40
Mixing Diverse Sensor Types .................................................................................................. 41
Before Connecting Equipment to Feature Port ................................................................................ 46
Connecting Asset Management Strips ............................................................................................. 46
Combining Regular Asset Strips ............................................................................................ 47
Introduction to Asset Tags ...................................................................................................... 49
Connecting Regular Asset Strips to PX3TS ............................................................................ 49
Connecting Blade Extension Strips ........................................................................................ 51
Connecting Composite Asset Strips (AMS-Mx-Z) .................................................................. 54
Connecting a Logitech Webcam ........................................................................................................ 56
Connecting a GSM Modem ................................................................................................................ 57
Connecting an Analog Modem........................................................................................................... 57
Connecting an External Beeper ........................................................................................................ 58
Connecting a Schroff LHX/SHX Heat Exchanger .............................................................................. 58
Chapter 5 Using the PX3TS 59
Power Transfer .................................................................................................................................. 60
Automatic Transfer ................................................................................................................. 61
Automatic Retransfer .............................................................................................................. 63
Manual Transfer ...................................................................................................................... 63
Transfer Switch Indicator Lamps ...................................................................................................... 66
Power Quality Indicator Lamps .............................................................................................. 68
Inlet Configuration Indicator Lamps ...................................................................................... 69
Active Inlet Indicator Lamps ................................................................................................... 69
Alarm Indicator Lamps ...................................................................................................................... 70
Control Push Buttons ........................................................................................................................ 71
Testing Indicator Lamps .................................................................................................................... 72
Short Circuit Detection ...................................................................................................................... 73
Outlets ................................................................................................................................................ 73
PX3TS-1000 Series .................................................................................................................. 73
PX3TS-5000 Series .................................................................................................................. 73 viii
Contents
Connection Port Functions ................................................................................................................ 75
LCD Display ........................................................................................................................................ 77
Overview of the LCD Display ................................................................................................... 77
Control Buttons ....................................................................................................................... 78
Operating the Character LCD Display .................................................................................... 79
Reset Buttons ..................................................................................................................................... 92
Fuses for the Inlet Transfer Switch .................................................................................................. 93
Replacing a Fuse on 1U Models ............................................................................................. 94
Replacing a Fuse on 2U Models ............................................................................................. 95
Overcurrent Protectors for Outlets ................................................................................................... 97
Resetting the Button-Type Circuit Breaker ........................................................................... 97
Beeper ................................................................................................................................................ 98
Power Cycling the PX3TS ................................................................................................................... 98
Chapter 6 Using the Web Interface 99
Supported Web Browsers .................................................................................................................. 99
Login, Logout and Password Change ............................................................................................. 100
Login ...................................................................................................................................... 100
Changing Your Password ...................................................................................................... 101
Remembering User Names and Passwords ....................................................................... 102
Logout .................................................................................................................................... 102
Web Interface Overview ................................................................................................................... 102
Menu ...................................................................................................................................... 105
Quick Access to a Specific Page ........................................................................................... 107
Sorting a List ......................................................................................................................... 108
Dashboard ........................................................................................................................................ 109
Dashboard - Transfer Switch ............................................................................................... 111
Dashboard - Inlet 1/2 ............................................................................................................ 112
Dashboard - Alerted Sensors ............................................................................................... 113
Dashboard - Inlet History ..................................................................................................... 115
Dashboard - Alarms .............................................................................................................. 117
Dashboard - OCP ................................................................................................................... 118
Transfer Switch ................................................................................................................................ 120
Transfer Switch and Inlet Status .......................................................................................... 126
Power Transfer Settings ....................................................................................................... 128
Power Quality Settings .......................................................................................................... 129
PDU ................................................................................................................................................... 130
Internal Beeper State ............................................................................................................ 134
PX3TS Latching Relay Behavior ........................................................................................... 136
Options for Outlet State on Startup ...................................................................................... 136
Initialization Delay Use Cases .............................................................................................. 137
Inrush Current and Inrush Guard Delay .............................................................................. 137
Z Coordinate Format ............................................................................................................. 138
How the Automatic Management Function Works .............................................................. 138 ix
x
Contents
Time Units .............................................................................................................................. 139
Setting Thresholds for Total Active Energy or Power ......................................................... 139
Inlets ................................................................................................................................................. 140
Individual Inlet Pages ............................................................................................................ 141
Outlets .............................................................................................................................................. 144
Available Data of the Outlets Overview Page ....................................................................... 148
Bulk Configuration for Outlet Thresholds ........................................................................... 149
Setting Outlet Power-On Sequence and Delay .................................................................... 149
Setting Non-Critical Outlets ................................................................................................. 150
Load Shedding Mode ............................................................................................................. 151
Individual Outlet Pages ......................................................................................................... 152
OCPs ................................................................................................................................................. 159
Individual OCP Pages ............................................................................................................ 161
Peripherals ....................................................................................................................................... 164
Yellow- or Red-Highlighted Sensors.................................................................................... 169
Managed vs Unmanaged Sensors/Actuators ...................................................................... 170
Sensor/Actuator States ......................................................................................................... 171
Finding the Sensor's Serial Number .................................................................................... 173
Identifying the Sensor Position and Channel ....................................................................... 174
Managing One Sensor or Actuator ....................................................................................... 175
Individual Sensor/Actuator Pages ........................................................................................ 177
Sensor/Actuator Location Example ..................................................................................... 181
Feature Port ..................................................................................................................................... 182
Asset Strip ............................................................................................................................. 184
External Beeper .................................................................................................................... 192
Schroff LHX/SHX ................................................................................................................... 193
Power CIM.............................................................................................................................. 196
User Management............................................................................................................................ 196
Creating Users ...................................................................................................................... 197
Editing or Deleting Users ...................................................................................................... 201
Creating Roles ....................................................................................................................... 202
Editing or Deleting Roles ...................................................................................................... 203
Setting Your Preferred Measurement Units ........................................................................ 204
Setting Default Measurement Units ..................................................................................... 205
Device Settings ................................................................................................................................. 206
Configuring Network Settings .............................................................................................. 207
Configuring Network Services .............................................................................................. 228
Configuring Security Settings ............................................................................................... 236
Setting the Date and Time .................................................................................................... 258
Event Rules and Actions ....................................................................................................... 261
Setting Data Logging ............................................................................................................. 309
Configuring Data Push Settings ........................................................................................... 310
Monitoring Server Accessibility ............................................................................................ 312
Front Panel Settings ............................................................................................................. 316
Configuring the Serial Port ................................................................................................... 317
Lua Scripts ............................................................................................................................. 318
Contents
Miscellaneous ........................................................................................................................ 324
Maintenance ..................................................................................................................................... 325
Device Information ................................................................................................................ 326
Viewing Connected Users ..................................................................................................... 330
Viewing or Clearing the Local Event Log ............................................................................. 332
Updating the PX3TS Firmware ............................................................................................. 333
Viewing Firmware Update History ........................................................................................ 335
Bulk Configuration ................................................................................................................ 336
Backup and Restore of Device Settings ............................................................................... 338
Network Diagnostics ............................................................................................................. 340
Downloading Diagnostic Information ................................................................................... 341
Rebooting the PX3TS Device ................................................................................................. 341
Resetting All Settings to Factory Defaults ........................................................................... 342
Retrieving Software Packages Information ......................................................................... 343
Webcam Management ..................................................................................................................... 343
Configuring Webcams and Viewing Live Images ................................................................. 344
Sending Snapshots or Videos in an Email or Instant Message .......................................... 346
Viewing Saved Snapshots and Managing Storage ............................................................... 347
Chapter 7 Using SNMP 349
Enabling and Configuring SNMP ..................................................................................................... 349
SNMPv2c Notifications .......................................................................................................... 350
SNMPv3 Notifications ........................................................................................................... 351
Downloading SNMP MIB .................................................................................................................. 352
SNMP Gets and Sets ........................................................................................................................ 353
The PX3TS MIB ...................................................................................................................... 353
Retrieving Energy Usage ...................................................................................................... 356
A Note about Enabling Thresholds ....................................................................................... 356
Chapter 8 Using the Command Line Interface 357
About the Interface .......................................................................................................................... 358
Logging in to CLI .............................................................................................................................. 358
With HyperTerminal .............................................................................................................. 358
With SSH or Telnet ................................................................................................................ 359
With an Analog Modem ......................................................................................................... 360
Different CLI Modes and Prompts ........................................................................................ 361
Closing a Local Connection .................................................................................................. 361
Help Command ................................................................................................................................ 362
Querying Available Parameters for a Command ........................................................................... 363
Showing Information ........................................................................................................................ 363
Transfer Switch Information ................................................................................................. 364
Network Configuration .......................................................................................................... 366
PDU Configuration................................................................................................................. 370 xi
xii
Contents
Outlet Information ................................................................................................................. 370
Inlet Information .................................................................................................................... 371
Overcurrent Protector Information ...................................................................................... 372
Date and Time Settings ......................................................................................................... 373
Default Measurement Units ................................................................................................. 373
Environmental Sensor Information ...................................................................................... 374
Environmental Sensor Package Information....................................................................... 375
Actuator Information ............................................................................................................. 376
Outlet Sensor Threshold Information .................................................................................. 377
Inlet Sensor Threshold Information ..................................................................................... 378
Overcurrent Protector Sensor Threshold Information ....................................................... 379
Environmental Sensor Threshold Information .................................................................... 380
Environmental Sensor Default Thresholds ......................................................................... 381
Security Settings ................................................................................................................... 382
Existing User Profiles ........................................................................................................... 383
Existing Roles ........................................................................................................................ 384
Load Shedding Settings ........................................................................................................ 384
Serial Port Settings ............................................................................................................... 385
EnergyWise Settings ............................................................................................................. 385
Asset Strip Settings ............................................................................................................... 385
Rack Unit Settings of an Asset Strip .................................................................................... 386
Blade Extension Strip Settings ............................................................................................. 387
Event Log ............................................................................................................................... 388
Wireless LAN Diagnostic Log ............................................................................................... 389
Server Reachability Information ........................................................................................... 389
Command History .................................................................................................................. 391
History Buffer Length ........................................................................................................... 391
Reliability Data ...................................................................................................................... 391
Reliability Error Log .............................................................................................................. 391
Examples ............................................................................................................................... 392
Clearing Information ........................................................................................................................ 394
Clearing Event Log ................................................................................................................ 394
Clearing WLAN Log ............................................................................................................... 395
Entering Configuration Mode .......................................................................................................... 395
Quitting Configuration Mode ........................................................................................................... 396
PX3TS Control and Configuration ................................................................................................... 396
Controlling the Transfer Switch ........................................................................................... 396
PDU Configuration Commands ............................................................................................ 401
Network Configuration Commands...................................................................................... 409
Time Configuration Commands ............................................................................................ 434
Checking the Accessibility of NTP Servers .......................................................................... 439
Security Configuration Commands ...................................................................................... 439
Outlet Configuration Commands .......................................................................................... 459
Inlet Configuration Commands ............................................................................................ 461
Overcurrent Protector Configuration Commands ............................................................... 462
User Configuration Commands ............................................................................................ 463
Contents
Role Configuration Commands ............................................................................................ 476
Environmental Sensor Configuration Commands............................................................... 481
Configuring Environmental Sensors' Default Thresholds .................................................. 486
Sensor Threshold Configuration Commands ...................................................................... 488
Actuator Configuration Commands...................................................................................... 499
Server Reachability Configuration Commands ................................................................... 500
EnergyWise Configuration Commands ................................................................................ 504
Asset Management Commands ........................................................................................... 506
Serial Port Configuration Commands .................................................................................. 513
Setting the History Buffer Length ........................................................................................ 514
Multi-Command Syntax ........................................................................................................ 515
Load Shedding Configuration Commands ...................................................................................... 516
Enabling or Disabling Load Shedding .................................................................................. 517
Power Control Operations ............................................................................................................... 518
Turning On the Outlet(s)........................................................................................................ 518
Turning Off the Outlet(s) ....................................................................................................... 519
Power Cycling the Outlet(s) .................................................................................................. 520
Canceling the Power-On Process ........................................................................................ 521
Example - Power Cycling Specific Outlets ........................................................................... 521
Actuator Control Operations ........................................................................................................... 521
Switching On an Actuator...................................................................................................... 522
Switching Off an Actuator ..................................................................................................... 522
Example - Turning On a Specific Actuator ........................................................................... 523
Unblocking a User ............................................................................................................................ 523
Resetting the PX3TS ........................................................................................................................ 523
Restarting the PDU ............................................................................................................... 524
Resetting Active Energy Readings........................................................................................ 524
Resetting to Factory Defaults ............................................................................................... 525
Network Troubleshooting ................................................................................................................ 525
Entering Diagnostic Mode ..................................................................................................... 525
Quitting Diagnostic Mode ...................................................................................................... 526
Diagnostic Commands .......................................................................................................... 526 xiii
Contents
Retrieving Previous Commands ...................................................................................................... 528
Automatically Completing a Command .......................................................................................... 528
Logging out of CLI ............................................................................................................................ 529
Chapter 9 Using SCP Commands 530
Firmware Update via SCP ................................................................................................................ 530
Bulk Configuration via SCP ............................................................................................................. 531
Backup and Restore via SCP ........................................................................................................... 532
Downloading Diagnostic Data via SCP ............................................................................................ 533
Appendix A Specifications 535
Technical Specifications .................................................................................................................. 535
Serial RS-232 "DB9" Port Pinouts .................................................................................................. 537
Sensor RJ-45 Port Pinouts .............................................................................................................. 538
Feature RJ-45 Port Pinouts ............................................................................................................. 538
Appendix B Equipment Setup Worksheet 540
Appendix C Configuration or Firmware Upgrade with a USB Drive 544
System and USB Requirements ...................................................................................................... 544
Configuration Files ........................................................................................................................... 545 fwupdate.cfg .......................................................................................................................... 546 config.txt ................................................................................................................................ 550 devices.csv ............................................................................................................................. 552
Creating Configuration Files via Mass Deployment Utility ................................................. 553
Data Encryption in 'config.txt' ............................................................................................... 554 xiv
Contents
Firmware Upgrade via USB ............................................................................................................. 555
Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP 557
Bulk Configuration/Upgrade Procedure ......................................................................................... 557
TFTP Requirements ......................................................................................................................... 558
DHCP IPv4 Configuration in Windows ............................................................................................. 559
DHCP IPv6 Configuration in Windows ............................................................................................. 569
DHCP IPv4 Configuration in Linux................................................................................................... 576
DHCP IPv6 Configuration in Linux................................................................................................... 578
Appendix E Resetting to Factory Defaults 580
Using the Reset Button .................................................................................................................... 580
Using the CLI Command .................................................................................................................. 581
Appendix F LDAP Configuration Illustration 583
Step A. Determine User Accounts and Roles ................................................................................. 583
Step B. Configure User Groups on the AD Server .......................................................................... 584
Step C. Configure LDAP Authentication on the PX3TS Device ...................................................... 585
Step D. Configure Roles on the PX3TS Device ............................................................................... 586
Appendix G Updating the LDAP Schema 589
Returning User Group Information ................................................................................................. 589
From LDAP/LDAPS ............................................................................................................... 589
From Microsoft Active Directory .......................................................................................... 589
Setting the Registry to Permit Write Operations to the Schema .................................................. 590
Creating a New Attribute ................................................................................................................. 590
Adding Attributes to the Class ........................................................................................................ 591
Updating the Schema Cache ........................................................................................................... 593
Editing rciusergroup Attributes for User Members ....................................................................... 593
Appendix H RADIUS Configuration Illustration 596
Standard Attributes.......................................................................................................................... 596
NPS Standard Attribute Illustration ..................................................................................... 596
FreeRADIUS Standard Attribute Illustration ....................................................................... 614
Vendor-Specific Attributes .............................................................................................................. 615
NPS VSA Illustration ............................................................................................................. 615
FreeRADIUS VSA Illustration ................................................................................................ 627 xv
Contents
AD-Related Configuration ............................................................................................................... 628
Appendix I Additional PX3TS Information 632
SecureLock™ Outlets and Cords .................................................................................................... 632
Reserving IP Addresses in DHCP Servers ...................................................................................... 634
Reserving IP in Windows ....................................................................................................... 634
Reserving IP in Linux ............................................................................................................ 636
Sensor Threshold Settings .............................................................................................................. 637
Thresholds and Sensor States ............................................................................................. 637
"To Assert" and Assertion Timeout ...................................................................................... 640
"To De-assert" and Deassertion Hysteresis ........................................................................ 642
PDView App for Viewing the PX3TS ................................................................................................. 644
Altitude Correction Factors ............................................................................................................. 646
Ways to Probe Existing User Profiles ............................................................................................. 647
Raritan Training Website ................................................................................................................. 647
Role of a DNS Server ....................................................................................................................... 648
Cascading Troubleshooting ............................................................................................................. 648
Possible Root Causes............................................................................................................ 648
Slave Connection and Disconnection Events ....................................................................... 651
The Ping Tool ......................................................................................................................... 651
Browsing through the Online Help.................................................................................................. 653
Appendix J Integration 655
Dominion KX II / III Configuration .................................................................................................... 655
Configuring Rack PDU Targets ............................................................................................. 656
Turning Outlets On/Off and Cycling Power .......................................................................... 659
Dominion KSX II, SX or SX II Configuration ..................................................................................... 660
Dominion KSX II ..................................................................................................................... 660
Dominion SX and SX II ........................................................................................................... 662
Power IQ Configuration .................................................................................................................... 665 dcTrack ............................................................................................................................................. 666 dcTrack Overview .................................................................................................................. 667
Asset Management Strips and dcTrack ............................................................................... 668
Index 669
xvi
What's New in the PX3TS User Guide
The following sections have changed or information has been added to the PX3TS User Guide based on enhancements and changes to the equipment and/or user documentation.
USB Wireless LAN Adapters
Connecting the PX3TS to a Computer
Initial Network Configuration via CLI
Cascading Multiple PX3TS Devices for Sharing Ethernet Connectivity
Cascading Guidelines for Port Forwarding
Cascading the PX3TS via USB
Introduction to Asset Tags
Connecting Regular Asset Strips to PX3TS
Connecting a Logitech Webcam
(on page 56)
IPv4 Address
(on page 82)
USB-Cascaded Device's Position
(on page 91)
Fuses for the Inlet Transfer Switch
The whole chapter of
Using the Web Interface
Network Configuration
(on page 366)
IP Configuration
(on page 366)
IPv4-Only or IPv6-Only Configuration
(on page 367)
Network Interface Settings
(on page 368)
Configuring IPv4 Parameters
Setting the IPv4 Configuration Mode
Setting the IPv4 Preferred Host Name
Setting the IPv4 Address
(on page 411)
Setting the IPv4 Gateway
Setting IPv4 Static Routes
Setting the IPv6 Configuration Mode
Setting the IPv6 Preferred Host Name
Setting the IPv6 Address
(on page 415)
Setting the IPv6 Gateway
Setting IPv6 Static Routes
Configuring DNS Parameters
xvii
xviii
Chapter 1: What's New in the PX3TS User Guide
Setting LAN Interface Parameters
Enabling or Disabling the LAN Interface
Changing the LAN Interface Speed
Changing the LAN Duplex Mode
Configuring the Cascading Mode
Deleting an NTP Server
Downloading Diagnostic Data via SCP
Firmware Upgrade via USB
Step C. Configure LDAP Authentication on the PX3TS Device
(on page
Reserving IP Addresses in DHCP Servers
Reserving IP in Windows
Reserving IP in Linux
"To Assert" and Assertion Timeout
"To De-assert" and Deassertion Hysteresis
Cascading Troubleshooting
Possible Root Causes
Slave Connection and Disconnection Events
Dominion SX II
Please see the Release Notes for a more detailed explanation of the changes applied to this version of PX3TS.
Chapter 1 Introduction
A Raritan PX3TS transfer switch has two inlets to connect two diverse AC power sources. When the primary, preferred power source fails or the power quality of the preferred source deteriorates to a unacceptable level, the PX3TS automatically transfers to the other power source to ensure the stability and reliability of power supply to connected equipment. Power transfer does not interrupt the operation of the connected equipment. The transfer time takes only 4-8 milliseconds (1/4
AC cycle).
The intended use of the Raritan PX3TS 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 PX3TS units -- some are outlet-switching capable, and some are not. With the outlet-switching function, you can recover systems remotely in the event of system failure and/or system lockup, eliminate the need to perform manual intervention or dispatch field personnel, reduce downtime and mean time to repair, and increase productivity.
Note: In this Online Help, PX3TS-1nnn series (where n is a number) is called PX3TS-1000, and PX3TS-5nnn series is called PX3TS-5000 for convenience.
In This Chapter
APIPA and Link-Local Addressing ............................................................... 4
Product Models
The PX3TS 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 PX3TS Data Sheet from Raritan's website, visit the
Product Selector page
(
http://www.findmypdu.com/
) on Raritan's website, or contact your local reseller for a list of available models.
1
Chapter 1: Introduction
PX3TS Overview
This section introduces the components shown on the front and rear panels of a PX3TS device.
Front View
All components on the front panel are the same on all PX3TS models except that those models rated over 20A (North America) or 16A
(international) contain overcurrent protectors for controlling the current flowing through outlets.
1U models:
2U models:
2
1. Six connection ports

CONSOLE/MODEM port

USB-B port

ETHERNET port

SENSOR port

USB-A port
Chapter 1: Introduction

FEATURE port
2. LCD display and control buttons
3. Transfer switch status indicators, including:

Power quality indicator lamps

Inlet configuration indicator lamps

Active inlet indicator lamps
4. Transfer switch alarm indicators
5. Transfer switch control buttons
6. Overcurrent protectors - one for each bank of outlets (available on some models only)
Rear View
Inlets, outlets and fuses for the inlet transfer switch are located on the rear panel.
1U models:
2U models:
1. Two inlets
2. Two fuses for the inlet transfer switch - one per inlet
3. Outlets
4. Two connection ports
3
4
Chapter 1: Introduction

USB-A port

CONSOLE port
Package Contents
•
The PX3TS device
•
Bracket pack and screws
•
Quick Setup Guide
•
Warranty card
• Two replacement fuses for the inlet transfer switch
Note: Depending on your PX3TS' ratings, appropriate fuse types vary.
You can order additional fuses from Raritan. See
Technical
Specifications
(on page 535) in the User Guide for appropriate fuse
types and Raritan part numbers for these fuses.
• A null-modem cable with DB9 connectors on both ends (Raritan number: 254-01-0006-00) (optional)
APIPA and Link-Local Addressing
The PX3TS supports Automatic Private Internet Protocol Addressing
(APIPA).
With APIPA, your PX3TS automatically configures a link-local IP address and a link-local host name when it cannot obtain a valid IP address from any DHCP server in the TCP/IP network.
Only IT devices connected to cannot access it.
the same subnet
can access the PX3TS using the link-local address/host name. Those in a different subnet
Exception: The PX3TS in the Port Forwarding mode does not support
APIPA. See
Setting the Cascading Mode
(on page 220).
Once the PX3TS can get a DHCP-assigned IP address, it stops using
APIPA and the link-local address is replaced by the DHCP-assigned address.
Scenarios where APIPA applies:
• DHCP is enabled on the PX3TS, but no IP address is assigned to the
PX3TS.
This may be caused by the absence or malfunction of DHCP servers in the network.
Note: Configuration by connecting the PX3TS to a computer using a network cable is an application of this scenario. See
Connecting the
PX3TS to a Computer
(on page 14).
Chapter 1: Introduction
• The PX3TS previously obtained an IP address from the DHCP server, but the lease of this IP address has expired, and the lease cannot be renewed, or no new IP address is available.
Link-local addressing:
•
IPv4 address:
Factory default is to enable IPv4 only. The link-local IPv4 address is
169.254.x.x/16
, which ranges between 169.254.1.0 and
169.254.254.255.
•
IPv6 address:
A link-local IPv6 address is available only after IPv6 is enabled on the
PX3TS. See
Configuring Network Settings
• Host name - pdu.local:
You can type
https://pdu.local
the link-local IP address.
to access the PX3TS instead of typing
Retrieval of the link-local IPv4 address:
• See
IPv4 Address
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 PX3TS device and other equipment from the box in which they were shipped. See
Package Contents
complete list of the contents of the box.
2. Compare the serial number of the equipment with the number on the packing slip located on the outside of the box and make sure they match.
3. Inspect the equipment carefully. If any of the equipment is damaged or missing, contact Raritan's Technical Support Department for assistance.
4. Verify that all circuit breakers on the PX3TS device are set to ON. If not, turn them ON.
Or make sure that all fuses are inserted and seated properly. If there are any fuse covers, ensure that they are closed.
5
6
Chapter 1: Introduction
Preparing the Installation Site
1. Make sure the installation area is clean and free of extreme temperatures and humidity. See
Technical Specifications
(on page
2. Allow sufficient space around the PX3TS device for cabling and outlet connections.
3. Review
Safety Instructions
(on page iii) listed in this User Guide.
Checking the Branch Circuit Rating
The rating of the branch circuit supplying power to the PDU shall be in accordance with national and local electrical codes.
Filling Out the Equipment Setup Worksheet
An Equipment Setup Worksheet is provided in this User Guide. See
Equipment Setup Worksheet
(on page 540). Use this worksheet to
record the model, serial number, and use of each IT device connected to the PDU.
As you add and remove devices, keep the worksheet up-to-date.
Chapter 2 Rackmount, Inlet and Outlet
Connections
In This Chapter
Rackmount Safety Guidelines ...................................................................... 7
Inlet and Outlet Power Connections .......................................................... 10
Rackmount Safety Guidelines
In Raritan products which require rack mounting, follow these precautions:

Operation temperature in a closed rack environment may be greater than room temperature. Do not exceed the rated maximum ambient temperature of the Power Distribution Units.
See
Specifications
(on page 535) in the User Guide.

Ensure sufficient airflow through the rack environment.

Mount equipment in the rack carefully to avoid uneven mechanical loading.

Connect equipment to the supply circuit carefully to avoid overloading circuits.

Ground all equipment properly, especially supply connections, to the branch circuit.
Mounting a PX3TS Device
Using appropriate brackets and tools, fasten the 1U or 2U PX3TS device to the rack or cabinet. The way to install a PX3TS device varies according to the device length.
To mount a PX3TS device which is long:
1. Attach mounting ears and mounting brackets to each side of the
PX3TS with provided screws.
7
Chapter 2: Rackmount, Inlet and Outlet Connections
2. Adjust slide-rail assemblies to match your rack posts and fasten them to the rack using your own fasteners.
8
3. Line up the mounting brackets with slide-rails and push this product into rails.
Chapter 2: Rackmount, Inlet and Outlet Connections
4. Fasten front mounting ears to the rack using your own fasteners.
To mount a PX3TS device which is short:
1. Attach a rackmount bracket to both sides of the PX3TS with the provided screws. For a 1U model, the total number and locations of screw holes are different from the following 2U diagram.
2. Insert the cable-support bar into rackmount brackets.
9
10
Chapter 2: Rackmount, Inlet and Outlet Connections
3. Secure with the provided end cap screws.
4. On a 2U model, repeat the above steps to install another cable-support bar.
5. Fasten the rackmount brackets' ears to the rack using your own fasteners.
Inlet and Outlet Power Connections
The PX3TS connects to two different, but identically rated, branch circuits.
The PX3TS will operate when the branch circuit voltages are out of phase, but works most reliably and fastest when in phase. The front panel
Phase Sync lamp lights if inlets are out of phase.
Chapter 3 Initial Installation and Configuration
This chapter explains how to install a PX3TS device and configure it for network connectivity.
In This Chapter
Connecting Power and Equipment ............................................................. 11
Connecting the PX3TS to Your Network .................................................... 11
Cascading Multiple PX3TS Devices for Sharing Ethernet Connectivity ... 23
Connecting Power and Equipment
Your PX3TS may have fuses and/or circuit breakers. Verify that all are firmly seated or set to ON before connecting power.
The PX3TS inlets are labeled INLET 1 (I1) and INLET 2 (I2). INLET 1 is the factory default preferred inlet, and INLET 2 is the factory default alternate inlet.
Tip: You can switch preferred and alternate inlets if needed. See
Manual
Transfer
(on page 63).
To make power connections:
1. Connect PX3TS inlets to branch circuits.
2. Connect loads to PX3TS outlets.
3. Apply power to branch circuits.
Connecting the PX3TS to Your Network
To remotely administer the PX3TS, you must connect the PX3TS to your local area network (LAN). PX3TS can be connected to a wired or wireless network.
Note: If your PX3TS will work as a master device in the bridging mode, make a wired connection. See
Cascading the PX3TS via USB
(on page
24).
To make a wired connection:
1. Connect a standard network patch cable to the ETHERNET port on the PX3TS.
2. Connect the other end of the cable to your LAN.
11
Chapter 3: Initial Installation and Configuration
The ETHERNET port:
12
Warning: Accidentally plugging an RS-232 RJ-45 connector into the
ETHERNET port can cause permanent damages to the Ethernet hardware.
To make a wireless connection:
Do one of the following:

Plug a supported USB wireless LAN adapter into the USB-A port on your PX3TS.

Connect a USB hub to the USB-A port on the PX3TS. Then plug the supported USB wireless LAN adapter into the appropriate
USB port on the hub.
See
USB Wireless LAN Adapters
wireless LAN adapters.
(on page 12) for a list of supported
USB Wireless LAN Adapters
The PX3TS supports the following USB Wi-Fi LAN adapters.
Wi-Fi LAN adapters
SparkLAN WUBR-508N
Proxim Orinoco 8494
Zyxel NWD271N
Edimax EW-7722UnD
TP-Link TL-WDN3200 v1
Raritan USB WIFI
Supported 802.11 protocols
A/B/G/N
A/B/G
B/G
A/B/G/N
A/B/G/N
A/B/G/N
Chapter 3: Initial Installation and Configuration
Note: To use the Edimax EW-7722UnD or Raritan USB WIFI wireless LAN adapter to connect to an
802.11n
wireless network, the handshake timeout setting must be changed to 500 or greater, or the wireless connection will fail.
Supported Wireless LAN Configuration
If wireless networking is preferred, ensure that the wireless LAN configuration of your PX3TS matches the access point. The following is the wireless LAN configuration that the PX3TS 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)
Important: Supported 802.11 network protocols vary according to the wireless LAN adapter being used with the PX3TS. See
USB Wireless
LAN Adapters
Configuring the PX3TS
You can initially configure the PX3TS by connecting it to a computer, or to a TCP/IP network that supports DHCP.
Configuration over a DHCP-enabled network:
1. Connect the PX3TS to a DHCP IPv4 network. See
Connecting the
PX3TS to Your Network
2. Retrieve the DHCP-assigned IPv4 address. Use the front panel LCD display to retrieve it. See
IPv4 Address
3. Launch a web browser to configure the PX3TS. See
Login
(on page
Configuration using a connected computer:
1. Connect the PX3TS to a computer. See
Connecting the PX3TS to a
Computer
2. Use the connected computer to configure the PX3TS via the command line or web interface.

Command line interface: See
Initial Network Configuration via
CLI
13
14
Chapter 3: Initial Installation and Configuration

Web interface: Launch the web browser on the computer, and type the link-local IP address or
See
Login
Address
pdu.local
to access the PX3TS.
(on page 100). For IP address retrieval, see
IPv4
Tip: To configure a number of PX3TS devices quickly, see
Bulk
Configuration Methods
(on page 22).
Connecting the PX3TS to a Computer
The PX3TS can be connected to a computer for configuration via one of the following ports.
•
USB-B port (male)
• ETHERNET port (female)
• RS-232 serial port (model dependent -- male DB9 or female RJ-45 connector)
1U front panel ports:
The PX3TS has two RS-232 serial ports on its front and back panels respectively. Both ports are functionally identical.
1U back panel RS-232 port:
Chapter 3: Initial Installation and Configuration
To use the command line interface (CLI) for configuration, establish an
RS-232 or USB connection.
To use a web browser for configuration, make a network connection to the computer. The PX3TS 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
Establish one of the following connections to a computer.
Serial connection for "DB9" RS-232 connector on PX3TS:
1. Connect one end of the null-modem DB9 cable to the male "DB9"
RS-232 port labeled CONSOLE / MODEM on the PX3TS.
2. Connect the other end to your computer's RS-232 port (COM).
3. Perform
Initial Network Configuration via CLI
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)
2. Connect a USB cable between the PX3TS device's USB-B port and a computer's USB-A port.
3. Perform
Initial Network Configuration via CLI
Note: Not all serial-to-USB converters work properly with the PX3TS so Raritan does not introduce the use of such converters.
Direct network connection:
1. Connect one end of a standard network patch cable to the
ETHERNET port of the PX3TS.
2. Connect the other end to a computer's Ethernet port.
3. On the connected computer, launch a web browser to access the
PX3TS, using either link-local addressing:
See
Login
pdu.local
or
169.254.x.x
.
15
16
Chapter 3: Initial Installation and Configuration
Installing the USB-to-Serial Driver (Optional)
The PX3TS can emulate a USB-to-serial converter over a USB connection. A USB-to-serial driver named "Dominion PX2 Serial
Console" is required for Microsoft
®
Windows
®
operating systems.
Download the Windows driver for USB serial console from the Raritan website's
Support page
(
http://www.raritan.com/support/
downloaded driver's name is represents the file's version number.
). The
dominion-serial-setup-<n>.exe
, where <n>
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 PX3TS 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 the installation.
3. Connect the PX3TS to the computer via a USB cable. The driver is automatically installed.
Manual driver installation in Windows
®
:
1. Make sure the PX3TS has been connected to the computer via a USB cable.
2. The computer detects the new device and the "Found New Hardware
Wizard" dialog appears.

If this dialog does not appear, choose Control Panel > System >
Hardware > Device Manager, right-click the
Dominion PX2 Serial
Console
, and choose Update Driver.
3. Select the option of driver installation from a specific location, and then specify the location where both
dominion-serial.inf
and
dominion-serial.cat
are stored.
Note: If any Windows security warning appears, accept it to continue the installation.
4. Wait until the installation is complete.
Chapter 3: Initial Installation and Configuration
Note: If the PX3TS 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 PX3TS 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 PX3TS 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
To configure the PX3TS device:
1. On the computer connected to the PX3TS, 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 PX3TS.
4. The PX3TS prompts you to log in. Both user name and password are case sensitive. a. Username: admin b. Password: raritan (or a new password if you have changed it).
17
18
Chapter 3: Initial Installation and Configuration
5. If prompted to change the default password, change or ignore it.

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 case sensitive.
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. Replace the
<ETH> variable with the word 'ethernet' when you are configuring the wired networking.
• General IP settings:
To set or enable
IPv4 or IPv6 protocol
Use this command network <ipvX> interface <ETH> enabled <option>
<option> =
true
, or
false
IPv4 configuration method network ipv4 interface <ETH> configMethod <mode>
<mode> =
dhcp
(default) or
static
IPv6 configuration method network ipv6 interface <ETH> configMethod <mode>
<mode> =
automatic
(default) or
static
Preferred host name
(optional) network <ipvX> interface <ETH> preferredHostName <name>
<name> = preferred host name
IP address returned by the DNS server network dns resolverPreference
<resolver>
<resolver> =
preferV4
or
preferV6
Chapter 3: Initial Installation and Configuration
• Static IP configuration:
To set
Static IPv4 or
IPv6 address
Static IPv4 or
IPv6 gateway
IPv4 or IPv6 primary DNS server
IPv4 or IPv6 secondary
DNS server
IPv4 or IPv6 third DNS server
Use this command network <ipvX> interface <ETH> address <ip address>
<ip address> = static IP address, with a syntax similar to the example below.

Example:
192.168.7.9/24
network <ipvX> gateway <ip address>
<ip address> = gateway's IP address network dns firstServer <ip address>
<ip address> = DNS server's IP address network dns secondServer <ip address>
<ip address> = DNS server's IP address network dns thirdServer <ip address>
<ip address> = DNS server's IP address
Commands for wireless networking:
•
General wireless settings:
Use this command To set or enable
Wireless interface
SSID
BSSID network wireless enabled
<option>
<option> =
true
, or
false
network wireless SSID <ssid>
<ssid> = SSID string network wireless BSSID <bssid>
<bssid> = AP MAC address or
none
19
20
Chapter 3: Initial Installation and Configuration
To set or enable
802.11n protocol
Use this command network wireless enableHT
<option>
<option> =
true
, or
false
Authentication method network wireless authMethod
<method>
<method> =
psk
or
eap
PSK network wireless PSK <psk>
<psk> = PSK string
EAP outer authentication network wireless eapOuterAuthentication
<outer_auth>
<outer_auth> =
PEAP
EAP inner authentication network wireless eapInnerAuthentication
<inner_auth>
<inner_auth> =
MSCHAPv2
EAP identity network wireless eapIdentity
<identity>
EAP CA certificate
<identity> = your user name for EAP authentication
EAP password network wireless eapPassword
When prompted to enter the password for EAP authentication, type the password. 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.
Chapter 3: Initial Installation and Configuration
The content to be copied from the CA certificate does NOT include the first line containing "BEGIN CERTIFICATE" and the final line containing
"END CERTIFICATE." If a certificate is installed, configure the following:
Whether to Use this command
Verify the certificate network wireless enableCertVerification
<option1>
<option1> =
true
or
false
Accept an expired or not valid certificate network wireless allowOffTimeRangeCerts
<option2>
<option2> =
true
or
false
Make the connection successful by ignoring the
"incorrect" system time network wireless allowConnectionWithIncorrectC lock <option3>
<option3> =
true
or
false
• 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 enable
IPv4 configuration method
IPv6 configuration method
Use this command network ipv4 interface
WIRELESS configMethod <mode>
<mode> =
dhcp
(default) or
static
network ipv6 interface
WIRELESS configMethod <mode>
<mode> =
automatic
(default) or
static
21
22
Chapter 3: Initial Installation and Configuration
To verify network settings:
After exiting the above configuration mode and the # prompt re-appears, type this command to verify all network settings.
• show network
The IP address configured may take seconds to take effect.
Bulk Configuration Methods
If you have to set up multiple PX3TS devices, you can use one of the following configuration methods to save your time.
Use a bulk configuration file:
•
Requirement: All PX3TS devices to configure are of the same model and firmware.
• Procedure: First finish configuring one PX3TS. Then save the bulk configuration file from it and copy this file to all of the other PX3TS devices.
See
Bulk Configuration
Use a TFTP server:
•
Requirement: DHCP is enabled in your network and a TFTP server is available.
•
Procedure: Prepare special configuration files, which must include
fwupdate.cfg
, and copy them to the root directory of the TFTP server.
Re-boot all PX3TS after connecting them to the network.
See
Bulk Configuration or Firmware Upgrade via DHCP/TFTP
(on
Use a USB flash drive:
• Requirement: A FAT32- or supperfloppy-formatted USB flash drive containing special configuration files is required.
•
Procedure: Plug this USB drive into the PX3TS. When a happy smiley is shown on the front panel display, press and hold one of the control buttons on the front panel until the display turns blank.
See
Configuration or Firmware Upgrade with a USB Drive
(on page
Chapter 3: Initial Installation and Configuration
Cascading Multiple PX3TS Devices for Sharing Ethernet Connectivity
You can have multiple PX3TS devices share one Ethernet connection by cascading them via USB.
Warning: To upgrade an existing USB-cascading chain from a version older than 3.3.10, you must start from the last slave device and so on until the master device. Otherwise, a networking issue occurs. See
Upgrade Guidelines for Existing USB-Cascading Chains
The first one in the cascading chain is the master device and all the other are slave devices. Only the master device is physically connected to the
LAN -- wired or wireless.
Each device in the chain is accessible over the network, with the bridging or port-forwarding cascading mode activated on the master device. See
Setting the Cascading Mode
• Bridging: Each device in the cascading chain is accessed with a different IP address.
•
Port Forwarding: Each device in the cascading chain is accessed with the same IP address but with a different port number assigned.
Cascading restrictions:
• In the bridging mode, the master device can have "only one" connection to the network.
Note: The port forwarding mode does NOT have such a restriction. In the port forwarding mode, you can enable both wired and wireless networking.
• Do NOT connect slave devices to the LAN via a standard network patch cable or a USB wireless LAN adapter.
•
An Ethernet-cascaded device must have its Ethernet interface enabled for the networking to work properly. By default the Ethernet interface is enabled.
USB-cascading tip:
The "USB-cascading" configuration can be a combination of diverse
Raritan products that support the USB-cascading feature, including PX2,
PX3, PX3-iX7, transfer switch, BCM and EMX.
Troubleshooting:
When a networking issue occurs, check the cascading connection and/or software settings of all devices in the chain. See
Cascading
Troubleshooting
23
24
Chapter 3: Initial Installation and Configuration
Cascading Guidelines for Port Forwarding
The following guidelines must be obeyed for establishing a cascading chain in the port forwarding mode.
•
Each cascaded device, except for the master device, must have only one upstream device.
•
Each cascaded device, except for the last slave device, must have only one downstream device.
• Use only one cable to cascade two devices.
Cascading the PX3TS via USB
Any certified USB 2.0 cable up to 16 feet (5 meters) long can be used.
Decide the cascading mode first before establishing the chain. All cascading modes support a maximum of 16 devices in a chain.
For more information on the USB-cascading configuration, see the
Cascading Guide
, which is available from Raritan website's
Support page
(
http://www.raritan.com/support/
).
To cascade PX3TS devices via USB:
1. Make sure all Raritan devices to be cascaded are running firmware version 3.3.10 or later.
2. Select one as the master device.

When the port forwarding mode over wireless LAN is intended, the master device must be a Raritan product with two USB-A ports, such as PX3, EMX2-888, PX3TS or BCM2.
3. Log in to all devices one by one and select the same cascading mode.
See
Setting the 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 sure the cascading role and downstream interface are also set correctly.
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 or a
Raritan USB WIFI wireless LAN adapter. For information on the
Raritan USB WIFI adapter, see
USB Wireless LAN Adapters
(on
Chapter 3: Initial Installation and Configuration
5. Connect the USB-A port of the master device to the USB-B port of an additional PX3TS 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
PX3TS via another USB cable. The second additional device is Slave
2.
7. Repeat the same step to connect more slave devices.
25
26
Chapter 3: Initial Installation and Configuration
Number Device role
Master device
Slave 1
Slave 2
Slave 3
8. Configure or change the network settings of the master and/or slave devices as needed.

Bridging: Each cascaded device has its own network settings. For example, some devices can have DHCP-assigned IP and the others can have static IP addresses.

Port forwarding: Only the master device's network settings should be configured.
Chapter 4 Connecting External Equipment
(Optional)
More features are available if you connect Raritan's or third-party external equipment to your PX3TS.
In This Chapter
Connecting Environmental Sensor Packages ........................................... 27
Before Connecting Equipment to Feature Port ......................................... 46
Connecting Asset Management Strips ...................................................... 46
Connecting a Logitech Webcam ................................................................. 56
Connecting a GSM Modem.......................................................................... 57
Connecting an Analog Modem .................................................................... 57
Connecting an External Beeper ................................................................. 58
Connecting a Schroff LHX/SHX Heat Exchanger ....................................... 58
Connecting Environmental Sensor Packages
•
•
•
•
(
The PX3TS supports all types of Raritan environmental sensor packages, including DPX, DPX2, DPX3 and DX sensor packages. For detailed information on each sensor package, refer to the Environmental Sensors
Guide or Online Help on the Raritan website's
http://www.raritan.com/support/
).
Support page
An environmental sensor package may comprise sensors only or a combination of sensors and actuators.
The PX3TS can manage a maximum of 32 sensors and/or actuators. The supported maximum cabling distance is 98 feet (30 m), except for DPX sensor packages.
For information on connecting different types of sensor packages, see:
DPX Sensor Packages
DPX2 Sensor Packages
DPX3 Sensor Packages
DX Sensor Packages
27
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.
28
For the cabling length restrictions, see
Supported Maximum DPX
Sensor Distances
Warning: For proper operation, wait for 15-30 seconds between each connection 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 the PX3TS. 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 PX3TS.
To directly connect a differential air pressure sensor:
1. Connect a Raritan-provided phone cable to the IN port of a differential air pressure sensor.
2. Get an RJ-12 to RJ-45 adapter. Connect the adapter's RJ-12 connector to the other end of the phone cable.
3. Connect this adapter's RJ-45 connector to the RJ-45 SENSOR port on the PX3TS.
Chapter 4: Connecting External Equipment (Optional)
4. If intended, connect one DPX sensor package to the OUT port of the differential air pressure sensor. It can be any DPX sensor package, such as a DPX-T3H1.
The PX3TS device
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
PX3TS via the hub.
DPX-ENVHUB4
sensor hub to the
PX3TS. This allows you to connect up to four DPX sensor packages to the
This sensor hub supports DPX sensor packages only. Do NOT connect
DPX2, DPX3 or DX sensor packages to it.
DPX-ENVHUB4 sensor hubs CANNOT be cascaded. You can connect only one hub to each SENSOR port on the PX3TS.
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 40).
To connect DPX sensor packages via the DPX-ENVHUB4 hub:
1. Connect the DPX-ENVHUB4 sensor hub to the PX3TS. 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.
29
Chapter 4: Connecting External Equipment (Optional) c. Connect this adapter's RJ-45 connector to the PDU's RJ-45
SENSOR port.
2. Connect DPX sensor packages to any of the four OUT ports on the hub.
This diagram illustrates a configuration with a sensor hub connected.
30
The PX3TS device
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 connected environmental sensors per SENSOR port.
This cable supports DPX sensor packages only. Do NOT connect DPX2,
DPX3 or DX 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 the PX3TS. a. Connect the adapter's RJ-12 connector to the cable.
Chapter 4: Connecting External Equipment (Optional) b. Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port on the PX3TS.
2. The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports.
3. Repeat the above steps if there are additional SENSOR ports on your
PX3TS.
31
Chapter 4: Connecting External Equipment (Optional)
Supported Maximum DPX Sensor Distances
When connecting the following DPX sensor packages to the PX3TS, 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 PX3TS using the sensor cable pre-installed (or provided) by Raritan. You MUST NOT extend or modify the sensor cable's length by using any tool other than the
Raritan's sensor hubs.
•
If using a DPX-ENVHUB4 sensor hub, the cabling distance between the PX3TS 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 a PX3TS via a sensor hub.
•
The sum of a DPX-T3H1 sensor cable's length is 16' (5 m).
32
PX3TS
33' (10 m) cable
•
The total cabling length between the PX3TS and one DPX-T3H1 is 49'
(15 m) as illustrated below.
Note that the length 16' (5 m) is the length of each DPX-T3H1 sensor cable, which is defined in the above diagram.
1 sensor hub 16' (5 m) cable
Up to 4 DPX-T3H1 sensor packages
Chapter 4: Connecting External Equipment (Optional)
DPX2 Sensor Packages
A DPX2 sensor cable is shipped with a DPX2 sensor package. This cable is made up of one RJ-12 connector and one to three head connectors.
You have to connect DPX2 sensor packages to the sensor cable.
For more information on DPX2 sensor packages, access the
Environmental Sensors 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
33
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 the final sensor package with a DPX2 sensor package.
To connect DPX2 sensor packages to the PX3TS:
1. Connect a DPX2 sensor package to the first head connector of the
DPX2 sensor cable.
34
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 of head connectors on your sensor cable, connect them to the first one or first two head connectors to ensure that there are NO free head connectors prior to the final DPX2 sensor package attached.
3. Use an RJ-12 to RJ-45 adapter to connect the DPX2 sensor package(s) to the PX3TS. a. Connect the adapter's RJ-12 connector to the DPX2 sensor cable.
Chapter 4: Connecting External Equipment (Optional) b. Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of the PX3TS.
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 DX
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 on either end of a DPX3 sensor package.
LED for indicating the sensor status.
To connect DPX3 sensor packages to the PX3TS:
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: 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.
35
Chapter 4: Connecting External Equipment (Optional)
Repeat the same steps to cascade more DPX3 sensor packages.
36
3. Connect the first DPX3 sensor package to the PX3TS by plugging its cable's connector into the RJ-45 SENSOR port of the PX3TS.
Connecting a DPX2 Sensor Package to DPX3
You can connect only one DPX2 sensor package to the "end" of a DPX3 sensor chain. It is strongly recommended to use an RJ-12 to RJ-45 adapter for connecting the DPX2 to the final DPX3 in the chain.
The maximum number of DPX3 sensor packages in the chain must be less than 12 when a DPX2 sensor package is involved.
When connecting a DPX2 sensor package containing three DPX2 sensors:
A maximum of nine DPX3 sensor packages can be cascaded because
12-3=9.
When connecting a DPX2 sensor package containing two DPX2 sensors:
A maximum of ten DPX3 sensor packages can be cascaded because
12-2=10.
Chapter 4: Connecting External Equipment (Optional)
When connecting a DPX2 sensor package containing one DPX2 sensor:
A maximum of eleven DPX3 sensor packages can be cascaded because 12-1=11.
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 Guide or Online Help on
Raritan website's
Support page
(
http://www.raritan.com/support/
).
You can cascade up to 12 DX sensor packages.
When cascading DX, remember that the PX3TS 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 PX3TS.
For example, if you cascade 12 DX packages, and each package contains
3 functions (a function is a sensor or actuator), the PX3TS does NOT manage the last 4 functions because the total 36 (12*3=36) exceeds 32 by
4.
Tip: To manage the last 4 functions, you can release 4 "managed" sensors or actuators, and then manually bring the last 4 functions into management. See
Peripherals
(on page 164).
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.
37
38
Chapter 4: Connecting External Equipment (Optional)
Numbers Components
Removable rackmount brackets.
Connect DX sensor packages to the PX3TS:
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.
Exception: You CANNOT cascade DX-PD2C5 sensor packages. A
PX3TS device supports only one DX-PD2C5.
3. Connect the first DX sensor package to the PX3TS by plugging its cable's connector into the RJ-45 SENSOR port of the PX3TS.
4. If needed, connect a DPX2 sensor package to the end of the DX chain.
See
Connecting a DPX2 Sensor Package to DX
Warning: The PX3TS does NOT support simultaneous connection of both DX-PD2C5 and asset management strip(s) so do NOT connect both of them at the same time.
Chapter 4: Connecting External Equipment (Optional)
Connecting a DPX2 Sensor Package to DX
You can connect only one DPX2 sensor package to the "end" of a DX sensor chain. It is strongly recommended to use an RJ-12 to RJ-45 adapter for connecting the DPX2 to the final DX in the chain.
The maximum number of DX sensor packages in the chain must be less than 12 when a DPX2 sensor package is involved.
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.
39
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 PX3TS, except for the following differences:
•
All ports on the DPX3-ENVHUB4 sensor hub are RJ-45 instead of
RJ-12 as the DPX-ENVHUB4 sensor hub.
• The DPX3-ENVHUB4 sensor hub supports all Raritan environmental sensor packages, including DPX, DPX2, DPX3 and DX 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
To connect DPX3 sensor packages via the DPX3-ENVHUB4 hub:
1. Connect the DPX3-ENVHUB4 sensor hub to the PX3TS 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 PX3TS.
2. Connect the Raritan sensor packages to any of the four OUT ports on the hub.

An RJ-12 to RJ-45 adapter is required for connecting a DPX or
DPX2 sensor package to the hub.
This diagram illustrates a configuration with a sensor hub connected.
40
The PX3TS
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 DPX, DPX2, DPX3 and DX sensor packages on one PX3TS according to the following sensor combinations. In some scenarios, the
DPX3-ENVHUB4 sensor hub is required.
The PX3TS does NOT support any other sensor-mixing combinations than those described in this section.
When mixing different sensor types, remember that the PX3TS supports a maximum of 32 sensors/actuators.
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 the following:

A DX sensor package

A chain of DX sensor packages

A DPX3 sensor package

A chain of DPX3 sensor packages
41
Chapter 4: Connecting External Equipment (Optional)

A DPX2 sensor package

A DPX sensor package
42
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 or DX sensor package.
This section only illustrations the following three combinations, but actually there are tens of different combinations by using the
DPX3-ENVHUB4 sensor hub.
43
Chapter 4: Connecting External Equipment (Optional)
44
Chapter 4: Connecting External Equipment (Optional)
Mix DPX3 and DX in a sensor chain:
Any DX 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 both DX and DPX3 sensor packages.
You can add a DPX2 sensor package to the end of such a sensor-mixing chain if intended. See
Connecting a DPX2 Sensor Package to DPX3
Connecting a DPX2 Sensor Package to DX
(on
45
46
Chapter 4: Connecting External Equipment (Optional)
Before Connecting Equipment to Feature Port
PX3TS models have a cap plugged into the FEATURE port when shipping out of the factory. The cap is intended to protect the port from connecting to inappropriate equipment. Remove this cap when you need to connect equipment to this port.
To remove the RJ-45 cap from the FEATURE port:
1. Locate the port labeled FEATURE.
2. Remove the cap.
Connecting Asset Management Strips
You can remotely track the locations of up to 64 IT devices in the rack by connecting asset management strips (asset strips) to the PX3TS 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 PX3TS.
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: The PX3TS does NOT support simultaneous connection of both DX-PD2C5 and asset management strip(s) so do NOT connect both of them at the same time.
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 be used to locate IT devices in a specific rack (or cabinet).
For each rack, you can attach asset strips up to 64U long, consisting of one MASTER and multiple SLAVE asset strips.
The difference between the master and slave asset strips is that the master asset strip has an RJ-45 connector while the slave does not.
The following diagram illustrates some asset strips. Note that Raritan provides more types of asset strips than the diagram.
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 white female DIN connector of the master strip.
47
48
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 strip. The length of the asset strip assembly can be up to 64U.

The final slave strip can be 8U or 5U, depending on the actual height of your 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 of magnetic stripes on the back.
Note: The asset strip is implemented with a tilt sensor so it can be mounted upside down.
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 PX3TS, and the asset tag transmits the ID and positioning information to the asset strip.
The following diagram illustrates an asset tag. Note that there are two types of asset tags: non-programmable and programmable tags. The only difference is that programmable asset tags allow you to customize each tag's ID or barcode number while non-programmable ones have factory default ID or barcode numbers, which you cannot change.
A
Barcode (ID number), which is available on either end of the "non-programmable" asset tag
Tag connector
B
Adhesive area with the tape
C
Note: The barcode of each "non-programmable" asset tag is unique and is displayed in the PX3TS device's web interface for identification.
Connecting Regular Asset Strips to PX3TS
The cabling distance between an asset strip assembly and the PX3TS can be up to 10 meters.
To connect regular asset strips to the PX3TS 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 the asset strip.
3. Connect the asset strip assembly to the PX3TS device, using a network patch cable (CAT5e or higher).
49
Chapter 4: Connecting External Equipment (Optional)

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
PX device.
The PX3TS 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 PX3TS. 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.
50
Letter Item
PX3TS
Asset strips
Asset tags
IT devices, such as servers
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 or composite asset strip. A blade extension strip contains 4 to 16 tag ports.
The following diagrams illustrate a tag connector cable and a blade extension strip with 16 tag ports.
Tag connector cable
A
Barcode (ID number) for the tag connector cable
Tag connector
B
C
Cable connector for connecting the blade extension strip
Note: A tag connector cable has a unique barcode, which is displayed in the PX3TS device's web interface for identifying each blade extension strip where it is connected.
Blade extension strip with 16 tag ports
51
Chapter 4: Connecting External Equipment (Optional)
Mylar section with the adhesive tape
D
E
Tag ports
F
Cable socket(s) for connecting the tag connector cable
Note: Each tag port on the blade extension strip is labeled a number, which is displayed as the slot number in the PX3TS device's web interface.
To install a blade extension strip:
1. Connect the tag connector cable to the blade extension strip.

Plug the cable's connector into the socket at either end of the blade extension strip.
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 the adhesive tape in the back of the mylar section to help fix the strip in place.
52
3. Connect one end of an asset tag to a blade server and the other end to the blade extension strip.
Chapter 4: Connecting External Equipment (Optional) a. Affix the adhesive part of the asset tag to one side of a blade server through the tag's tape. b. Plug the tag connector of the asset tag into a tag port on the blade extension strip.
4. Repeat the above step until all blade servers in the chassis are connected to the blade extension strip via asset tags.
5. Plug the tag connector of the blade extension strip into the closest tag port of 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 the asset strip, wait at least 1 second before re-connecting it back, or the PX3TS device may not detect it.
53
54
Chapter 4: Connecting External Equipment (Optional)
Connecting Composite Asset Strips (AMS-Mx-Z)
A composite asset strip is named AMS-Mx-Z, where x is a number, such as AMS-M2-Z or AMS-M3-Z. It is a type of asset strip that functions the same as regular MASTER asset strips except for the following differences:
•
It has two RJ-45 connectors.
• Multiple composite asset strips can be daisy chained.
• It contains less tag ports than regular asset strips.
For example, AMS-M2-Z contains two tag ports, and AMS-M3-Z contains three tag ports only.
The composite asset strip is especially useful for tracking large devices such as SAN boxes in the cabinet.
The following diagram illustrates AMS-M3-Z.
A
B
Two RJ-45 connectors
Tag ports
To connect composite asset strips to the PX3TS device:
1. Connect a composite asset strip to the PX3TS device via a standard network patch cable (CAT5e or higher). a. Connect one end of the cable to the RJ-45 port labeled "Input" on the composite asset strip. b. Connect the other end of the cable to the FEATURE port on the
PX3TS device.
2. Affix an asset tag to the IT device. Then connect this asset tag to the composite asset strip by plugging the tag connector into the tag port on the composite asset strip. For details, see
to PX
Connecting Regular
Asset Strips to the PX3TS
Connecting Regular Asset Strips
3. If necessary, daisy chain additional composite asset strips to track more IT devices. a. Get a standard network patch cable that is within 2 meters.
Chapter 4: Connecting External Equipment (Optional) b. Connect one end of the network cable to the RJ-45 connector labeled "Output" on the previous composite asset strip. c. Connect the other end of the cable to the RJ-45 connector labeled "Input" on the subsequent composite asset strip. d. Repeat the above steps to connect more composite asset strips.
See
Daisy-Chain Limitations of Composite Asset Strips
supported per chain.
(on
page 55) for the maximum number of composite asset strips
e. It is highly recommended using the cable ties to help hold the weight of all connecting cables.
4. Repeat Step 2 to connect IT devices to the other composite asset strips in the chain.
Important: Different types of composite asset strips can be mixed in a chain only when the PX3TS is upgraded to version 3.3.0 or later.
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 depend on the Raritan product you purchased.
Raritan devices
EMX2-111,
PX2 PDUs,
Maximum strips per chain
Up to 4 composite asset strips are supported.
55
56
Chapter 4: Connecting External Equipment (Optional)
Raritan devices
BCM1 (NOT BCM2 series)
EMX2-888,
PX3 PDUs,
PX3TS transfer switches
PMC (BCM2 series)
Maximum strips per chain
Up to 6 composite asset strips are supported.
Important: Different types of composite asset strips can be mixed in a chain as of release 3.3.0.
Connecting a Logitech Webcam
Connect webcams to PX3TS in order to view videos or snapshots of the webcam's surrounding area.
The following USB Video Class (UVC) compliant webcam is supported:
• 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 PX3TS supports up to two webcams. After connecting a webcam, you can retrieve visual information from anywhere through the PX3TS web interface. If your webcam supports audio, audio is available with videos.
For more information on the Logitech webcam, see the user documentation accompanying it.
To connect a webcam:
1. Connect the webcam to the USB-A port on the PX3TS device. The
PX3TS automatically detects the webcam.
2. Position the webcam properly.
Important: If a USB hub is used to connect the webcam, make sure it is a "powered" hub.
Snapshots or videos captured by the webcam are immediately displayed in the PX3TS web interface after the connection is complete. See
Configuring Webcams and Viewing Live Images
Chapter 4: Connecting External Equipment (Optional)
Connecting a GSM Modem
The following Cinterion
®
GSM modems can be connected to the PX3TS in order to send SMS messages containing event information.
•
MC52iT
•
MC55iT
•
EHS6
See
Available Actions
messages.
(on page 280) for more information on SMS
Note: PX3TS cannot receive SMS messages.
To connect the GSM modem:
1. Connect the GSM modem to the serial port labeled CONSOLE /
MODEM on the PX3TS.
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 PX3TS to specify the modem's SIM PIN number and the recipient phone number. See
Configuring the Serial Port
Connecting an Analog Modem
The PX3TS supports remote dial-in communications to access the CLI through an analog modem. This dial-in feature provides an additional alternative to access the PX3TS when the LAN access is not available. To dial in to the PX3TS, the remote computer must have a modem connected and dial the correct phone number.
Below are the analog modems that the PX3TS supports for sure:
•
NETCOMM IG6000 Industrial Grade SmartModem
•
US Robotics 56K modem
The PX3TS may also support other analog modems which Raritan did not test.
Note that the PX3TS does NOT support dial-out or dial-back operations via the modem.
To connect an analog modem:
1. Plug a telephone cord into the phone jack of the supported modem.
2. Plug the modem's RS-232 cable into the serial port labeled
CONSOLE / MODEM on the PX3TS.
57
58
Chapter 4: Connecting External Equipment (Optional)
You need to enable the modem dial-in support to take advantage of this feature, see
Configuring the Serial Port
Connecting an External Beeper
The PX3TS supports the use of an external beeper for audio alarms.
External beepers that are supported include but may not be limited to the following:
•
Mallory Sonalert MODEL SNP2R
After having an external beeper connected, you can create event rules for the PX3TS to switch on or off the external beeper when specific events occur. See
Event Rules and Actions
To connect an external beeper:
1. Connect a standard network patch cable to the FEATURE port of the
PX3TS.
2. Plug the other end of the cable into the external beeper's RJ-45 socket.
The beeper can be located at a distance up to 330 feet (100 m) away from the PX3TS.
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 PX3TS device, you must establish a connection between the heat exchanger and the PX3TS device.
For more information on the LHX/SHX heat exchanger, see the user documentation accompanying that product.
To establish a connection between the PDU and LHX/SHX heat exchanger, an RJ-45 to RS-232 adapter cable provided by Schroff is required.
To connect an LHX or SHX heat exchanger:
1. Plug the RS-232 DB9 end of the adapter cable into the RS-232 port on the Schroff LHX/SHX heat exchanger.
2. Plug the RJ-45 end of the cable into the port labeled FEATURE on your PX3TS device.
To enable the support of the LHX/SHX heat exchanger, see
Miscellaneous
Chapter 5 Using the PX3TS
In This Chapter
Transfer Switch Indicator Lamps ............................................................... 66
Fuses for the Inlet Transfer Switch ........................................................... 93
Overcurrent Protectors for Outlets ............................................................ 97
59
Chapter 5: Using the PX3TS
Power Transfer
The PX3TS has two inlets: INLET 1 and INLET 2. These inlets are to connect to diverse power sources. One inlet is configured as the primary
(preferred), and the other is configured as the standby (alternate). The factory default preferred power source is Inlet 1, and the default alternate source is Inlet 2.
When power is available from both sources and power quality is identical, the PX3TS selects the preferred inlet to power the load. If a power failure occurs on the preferred source or its power quality deteriorates below an acceptable level, the power can be transferred from one inlet to the other automatically or manually on the PX3TS. Power transfer does not interrupt the operation of the connected equipment. The transfer time takes only 4-8 milliseconds (1/4 AC cycle). See the diagram below.
60
Number Event
Power failure
Automatic power transfer
There are three types of power transfer mechanisms:
•
Automatic transfer
• Automatic retransfer
• Manual transfer
Tip: You can monitor the power quality of each inlet or the power transfer status by observing the Inlet Power indicator lamps. See
Transfer
Switch Indicator Lamps
(on page 66).
Chapter 5: Using the PX3TS
Automatic Transfer
Power is automatically transferred from the preferred inlet to the alternate because:
•
The preferred inlet's power fails, or
•
The preferred inlet's power quality (voltage or frequency) enters the critical level.
Power quality is indicated through the Power Quality indicator lamps.
See
Power Quality Indicator Lamps
The table below indicates which inlet the PX3TS selects when the power quality changes.
Inlet power quality
Preferred
Normal
Warning
Warning
Critical
Critical
Alternate
Normal
Warning
Critical
Warning
Critical
Normal
Normal
Warning
Critical
Active inlet
Preferred
Preferred
Preferred
Alternate
None
Automatic Transfer Scenarios
The PX3TS determines whether an automatic power transfer from the preferred to the alternate inlet should be performed based on the status or fault occurred on both inlets.
The following table indicates when an automatic transfer is allowed to occur.
• : A power transfer is performed.
• Blank: No power transfer is performed.
61
62
Chapter 5: Using the PX3TS
Alternate inlet states
Preferred inlet states
Power
Normal
(green lamp)
Power
Warning
(orange lamp)
Power
Critical
(red lamp)
Power
Critical
(red lamp)
Power
Warning
(orange lamp)
Switch
Open fault
MOV surge protector fault
Fuse alarm
12V SMPS fault
Phase
Sync alarm
Overload Switch open fault
Switch short fault
Note: Switch open/short, MOV, 12V SMPS faults are internal transfer switch faults, causing the Internal Failure indicator lamp on the front panel to turn on. See
Alarm Indicator Lamps
(on page 70).
MOV fault
Fuse alarm
12V
SMPS fault
Chapter 5: Using the PX3TS
Automatic Retransfer
When the preferred inlet's power quality restores to the normal level, an automatic retransfer from the alternate back to the preferred inlet occurs.
The automatic retransfer is
not
performed if:
•
Automatic retransfer is disabled.
• Inlets are out of phase.
Tip: To disable the inlet phase synchronization requirement, see
Transfer Switch
(on page 120) or
Power Transfer Settings
(on page
128).
•
An internal hardware malfunction on the preferred inlet's circuitry may lead to a less reliable power state.
Note: The PX3TS indicates an alarm through the Alarm indicator lamps.
See
Alarm Indicator Lamps
(on page 70).
Tip: Per default the automatic retransfer can be performed only when both inlets are in phase. You can disable this requirement. See
Transfer
Switch
(on page 120) or
Power Transfer Settings
(on page 128).
Manual Transfer
The Manual Transfer button transfers power from the active inlet to the other inlet.
In addition to performing a power transfer, a manual transfer redefines the newly-activated inlet as the preferred inlet. For example, if Inlet 1 is both the preferred and active inlet, pressing the Manual Transfer button causes:
•
Power transfer from Inlet 1 to Inlet 2.
•
Inlet 2, the newly-activated inlet, to be configured as the new preferred inlet.
63
Chapter 5: Using the PX3TS
Tip: To remotely perform manual transfer using the web interface, see
Transfer Switch
(on page 120). To transfer using the CLI, see
Performing Manual Transfer
(on page 396).
A manual transfer using the front panel button is prevented if:
• Manual Transfer button has been disabled.
• Inlets are out of phase.
•
The other inlet's power quality (voltage or frequency) enters the
Critical state, power is lost or there is any internal hardware malfunction.
Tip: To disable the Manual Transfer button or the inlet phase synchronization requirement, see
Transfer Switch
(on page 120) or
Power Transfer Settings
(on page 128).
64
Chapter 5: Using the PX3TS
Manual Transfer Scenarios
Manual transfer is prevented in specific scenarios. The following table indicates when a manual transfer can or cannot be performed. Certain scenarios require pressing the front panel Alarm Override button in addition to the Manual Transfer button to perform a manual transfer.
See
Manual Transfer When an Alarm is Present
Make sure the front panel Manual Transfer button has been enabled before using it. You can verify the button status via the Alarm indicator lamps. See
Alarm Indicator Lamps
• : A power transfer is performed.
• Blank: No power transfer is performed.
Inactive inlet's status
Power Critical (red light)
Manual Transfer Alarm Override +
Manual Transfer
Power Warning
(orange light)
Phase Sync alarm
Overload alarm
Switch open fault
Switch short fault
MOV surge protector fault
Fuse alarm
12V SMPS fault
Whenever the PX3TS prevents a manual transfer from being performed, it is disabled across all interfaces, including the front panel button, web interface and CLI command.
Note: Switch open/short, MOV, 12V SMPS faults are internal transfer switch faults, causing the Internal Failure indicator lamp on the front panel to turn on. See
Alarm Indicator Lamps
(on page 70).
65
66
Chapter 5: Using the PX3TS
Manual Transfer When an Alarm is Present
Manual transfer is prevented when the PX3TS enters an alarm state, such as the Phase Sync alarm. In certain scenarios, you still can force the PX3TS to perform a manual transfer by holding the Alarm Override button while pressing the Manual Transfer button. See
Manual Transfer
Scenarios
Note: The PX3TS indicates an alarm through the Alarm indicator lamps.
See
Alarm Indicator Lamps
(on page 70).
To perform a manual transfer in the alarm state:
1. Press and hold the Alarm Override button.
2. Press the Manual Transfer button.
Power is transferred from the active inlet to the other inlet now. You can verify the power transfer through the Active Inlet indicator lamps. See
Active Inlet Indicator Lamps
Transfer Switch Indicator Lamps
The Inlet Power indicator lamps are located to the left of the Alarm indicator lamps. On the indicator lamps, I1 refers to Inlet 1, I2 to Inlet 2, and O to the Output (outlets).
Chapter 5: Using the PX3TS
These lamps are divided into 3 sections to indicate the inlet power status or configuration.
Section Lamp type Function
A Power
Quality
Inlet power quality is shown using a tricolor LED.
For details, see
Power Quality Indicator Lamps
B Inlet
Configuration
A green LED indicates which inlet is the preferred one. The preferred inlet powers the outlets unless its power quality goes critical.
For details, see
Inlet Configuration Indicator
Lamps
C Active Inlet A green LED indicates which inlet is powering the outlets. Only one LED is on at a time.
For details, see
Active Inlet Indicator Lamps
(on
67
68
Chapter 5: Using the PX3TS
Power Quality Indicator Lamps
The PX3TS monitors AC voltage and frequency of both inlets and rates the power quality into 3 categories. When the power quality of any inlet changes, the corresponding Power Quality lamp, which is a tricolor LED, changes its colors.
Quality Lamp color Description
Normal green Power quality (voltage and frequency) is good.
Warning orange
Critical red
Power quality is not optimal but acceptable.
Power is not available or power quality is not acceptable.
Note: Voltage and frequency settings are configured via the web interface or CLI. See
Transfer Switch
(on page 120) or
Configuring
Power Quality Parameters
(on page 399).
Chapter 5: Using the PX3TS
Inlet Configuration Indicator Lamps
A green LED indicates which inlet is preferred. The default is Inlet 1.
A "Preferred" inlet is the power source that you prefer using for powering the PX3TS as long as this inlet's power is available and power quality is good. The other inlet is the "Alternate" inlet.
The preferred inlet may be changed with the Manual Transfer button.
See
Manual Transfer
Active Inlet Indicator Lamps
A green LED indicates which one is the active inlet.
An "Active" inlet is the one which is powering the outlets. The other inlet is the "Inactive" inlet. By default the "Preferred" inlet is active unless its power quality goes critical, leading to an automatic power transfer.
There are four operational states: normal, standby, non-redundant and off. See
Transfer Switch and Inlet Status
• In the "normal," "standby" or "non-redundant" operational state, a green LED is present to indicate the active inlet.
•
In the "off" operational state, neither LED is green.
69
70
Chapter 5: Using the PX3TS
Alarm Indicator Lamps
The PX3TS provides five Alarm indicator lamps, which are lit to alert you when the PX3TS detects unusual or abnormal transfer switch conditions.
Indicator lamps Meaning when the lamp is on
Manual Disabled The front panel Manual Transfer button is disabled.
See
Transfer Switch
Power Transfer Features
disable this button.
Configuring
Phase Sync
Fuse
Inlets are out of phase. This alarm is turned on when inlets' phase angle difference exceeds 15 degrees.
When this lamp is on, the manual transfer is prevented. See
Manual Transfer
Blown fuse.
The replacement fuse must be either the same as the
Raritan-provided fuse or equivalent.
To order fuses from Raritan, see
Technical
Specifications
(on page 535) in the User Guide for
appropriate fuse types and Raritan part numbers.
See
Fuses for the Inlet Transfer Switch
for replacement procedures.
Chapter 5: Using the PX3TS
Indicator lamps Meaning when the lamp is on
Internal Failure Internal hardware failure.
The internal failure can be any of the following, which is indicated on the web interface's Transfer Switch
Management.
•
Inlet transfer switch open/short fault
•
MOV surge protector failure
• 12V Switch Mode Power Supply (SMPS) power failure
Contact Raritan technical support. The web interface contains additional indicators for specific internal failures. See
Transfer Switch and Inlet Status
(on
Overload Power to load is turned off due to a short circuit.
This indicator lamp turns off when power is restored and normal current flows in the load.
See
Short Circuit Detection
Control Push Buttons
The PX3TS provides three buttons on the front panel to perform manual transfer or verify the transfer switch indicator lamps.
The table describes each button's function.
Button Description
Alarm Override Forces a manual transfer during an alarm condition.
See
Manual Transfer When an Alarm is Present
(on
71
72
Chapter 5: Using the PX3TS
Button
Lamp Test
Description
Turns on all transfer switch indicator lamps. Power
Quality LEDs turn orange.
See
Testing Indicator Lamps
Manual Transfer Transfers power to the other inlet. Newly-activated inlet becomes the preferred inlet.
See
Manual Transfer
Testing Indicator Lamps
Press the Lamp Test control button and visually verify that all transfer switch indicator lamps turn on. See
Control Push Buttons
Chapter 5: Using the PX3TS
Short Circuit Detection
A short circuit in the load results in a power failure on the active inlet.
The PX3TS monitors load current and does NOT perform an automatic power transfer if power fails because of an overload. Instead, the PX3TS activates the Overload alarm and turns on the Overload lamp. See
Alarm
Indicator Lamps
The Overload alarm is turned off after voltage is restored and normal current is detected in the load.
The overload threshold differs according to your model's rating.
Overload threshold = 2 * sqrt(2) * rating
Examples:
• PX3TS-1876R, which is rated at 16A:
2 * sqrt(2) * 16 = 45A
•
PX3TS-1869R, which is rated at 32A:
2 * sqrt(2) * 32 = 91A
Outlets
LED state
Not lit
The total number of outlets varies from model to model.
PX3TS-1000 Series
These models are NOT outlet-switching capable so all outlets are always in the ON state.
Outlet LEDs are not available.
PX3TS-5000 Series
These models are outlet-switching capable. A small LED adjacent to each outlet indicates the outlet or PDU state. The PDU is shipped from the factory with all outlets turned ON. The table below explains how to interpret different outlet LED states.
Outlet status
Powered OFF
What it means
The outlet is not connected to power, or the control circuitry's power supply is broken.
73
74
Chapter 5: Using the PX3TS
LED state
Red
Red flashing
Green
Green flashing
Outlet status
ON and LIVE
ON and LIVE
OFF and LIVE
OFF and NOT LIVE
Red and Green flashing alternatively ON and NOT LIVE
Cycling through Red,
Green and Yellow n/a
What it means
LIVE power. The outlet is on and power is available.
The current flowing through the outlet is greater than the upper warning (non-critical) threshold.
The outlet is turned off and power is available when the outlet is turned on.
The outlet is turned off and power is not available because the circuit breaker has tripped.
The outlet is turned on but power is not available because a circuit breaker has tripped.
The PX3TS device has just been plugged in and its management software is loading. LED color cycling does not interrupt power to outlets. It is an indication of firmware loading.
Note: When a PX3TS device powers up, it proceeds with the power-on self test and software loading for a few moments. At this time, the outlet
LEDs cycle through different colors. When the software has completed loading, the outlet LEDs show a steady color and the front panel display illuminates.
Chapter 5: Using the PX3TS
Connection Port Functions
A PX3TS model has 8 connection ports on the front and back panels respectively.
Front panel CONSOLE port is functionally identical to back panel
CONSOLE port, and front panel USB-A port is functionally identical to back panel USB-A port.
Front panel ports:
• 1 Console/Modem
• 1 Sensor
•
1 USB-B
•
1 USB-A
•
1 Ethernet
• 1 Feature
Back panel ports:
•
1 USB-A
• 1 Console
Port
USB-B
The table below explains the function of each port.
Used for...
•
Cascading the PX3TS devices for sharing a network connection. See
Cascading the PX3TS via USB
• Establishing a USB connection between a computer and the PX3TS for using the command line interface or performing the disaster recovery.
For disaster recovery instructions, contact Raritan Technical Support.
75
76
Chapter 5: Using the PX3TS
Port
USB-A
FEATURE
CONSOLE/
MODEM
(DB9)
SENSOR
(RJ-45)
ETHERNET
Used for...
This is a "host" port, which is powered, per USB 2.0 specifications.
• Connecting a USB device, such as a Logitech
®
webcam or wireless LAN adapter.
•
Cascading the PX3TS devices for sharing a network connection.
Connection to one of the following devices:

A Raritan access product, such as Dominion KX III KVM switch, with the use of a power CIM.

A Schroff
®
LHX-20, SHX-30 or LHX-40 device, using an RJ-45 to
RS-232 cable provided by Schroff.

An external beeper with the RJ-45 socket.

A Raritan asset management strip, which allows you to track the locations of IT devices on the rack.
See
Connecting External Equipment (Optional)
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.
Establishing a serial connection between the PX3TS and a computer or modem.
This is a standard DTE RS-232 port. You can use a null-modem cable with two DB9 connectors on both ends to connect the PX3TS to the computer.
Connection to one of the following devices:

Raritan's environmental sensor package(s).

Raritan's sensor hub, which expands the number of a sensor port to four ports.
Connecting the PX3TS to your company's network via a standard network patch cable (Cat5e/6). This connection is necessary to administer or access the PX3TS 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: Connection to this port is not required if wireless connection is preferred, or if the PX3TS is a slave device in the USB-cascading configuration. See
Cascading the PX3TS via USB
(on page 24).
LCD Display
Chapter 5: Using the PX3TS
A PX3TS series model uses an LCD display to show the device's data.
The following diagram shows the LCD display panel on a 1U model.
The LCD display can show the reading or status of different components on the PX3TS, or this device's 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.
Section Information shown
The selected mode and target, such as INLET 1, SENSOR
1, SENSOR 2, and so on.
The following information is displayed:
•
Readings, data or state of the selected target.
•
During the firmware upgrade, "FUP" is displayed.
77
78
Chapter 5: Using the PX3TS
Section Information shown
Two types of information may be displayed:
•
The "ALARM" status of the selected target.
•
The selected inlet line number if your PX3TS is a
3-phase model.
The measurement unit of the displayed data, such as % or .
This section indicates:
•
The Asset Strip mode if an asset strip has been connected to the PX3TS.
•
The device's USB-cascading state -
MASTER
or
SLAVE
. If it is a standalone device, neither MASTER nor SLAVE is displayed.
Control Buttons
There are four control buttons.
•
Up and Down buttons for selecting a specific target, which can be an inlet, overcurrent protector, environmental sensor or a device setting
• MODE button for switching between various modes, including
- Inlet mode
- Overcurrent Protector mode
- Device mode
- Sensor mode
- Asset Sensor mode, indicated by the word ASSET, for showing the asset sensor information
See
Overview of the LCD Display
• FUNC (Function) button for switching between different data of the selected target, such as the current, voltage or power readings of an inlet
Chapter 5: Using the PX3TS
Operating the Character LCD Display
After powering on or resetting this product, the LCD display panel shows the current reading of INLET 1 or OUTLET 1 by default before you select a different target. The default target varies according your model:
•
PX3TS-1000 series: INLET 1
•
PX3TS-5000 series: OUTLET 1
Inlet Information
The Inlet mode is displayed as "INLET" on the LCD display. Below illustrates the inlet information shown on the LCD display.
Section Example information
The selected target is INLET 1.
This inlet's L1 current reading is 23 amps.
The selected inlet line is L1.
The word "MASTER" indicates the PX3TS is the master device in a cascading configuration.
For a slave device, it shows "SLAVE" instead.
Note: As of release 3.3.10, the "MASTER/SLAVE" information is no longer available in the bridging mode, but remains available in the 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 PX3TS is a 3-phase model, the selected inlet line is indicated below the reading. 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.
79
80
Chapter 5: Using the PX3TS
4. Press the FUNC button to switch between voltage, active power and current 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.
Outlet Information
The outlet mode is NOT available for PX3TS-1000 series.
The Outlet mode is displayed as "OUTLET" on the LCD display. By default the PX3TS displays the current reading of OUTLET 1.
Below illustrates the outlet information shown on the LCD display.
Section Example information
The selected target is OUTLET 3.
This outlet's current reading is 2 amps.
The word "MASTER" indicates the PX3TS is the master device in a cascading configuration.
For a slave device, it shows "SLAVE" instead.
Note: As of release 3.3.10, the "MASTER/SLAVE" information is no longer available in the bridging mode, but remains available in the port forwarding mode.
The measurement unit is A (Amp), indicating that the reading is 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.
Chapter 5: Using the PX3TS
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 and current 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.
Overcurrent Protector Information
This section describes overcurrent protectors for outlets rather than fuses for the inlet transfer switch. The LCD display does not show information regarding fuses for the inlet transfer switch.
The Overcurrent Protector mode is displayed as "CB" on the LCD display.
CB refers to the circuit breaker.
The LCD display can show the information of overcurrent protectors for outlets, if available. See
Overcurrent Protectors for Outlets
(on page
Below illustrates an overcurrent protector's information.
Section Example 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 selected circuit breaker is closed.
81
82
Chapter 5: Using the PX3TS
Section Example information
The word "MASTER" indicates the PX3TS is the master device in a cascading configuration.
For a slave device, it shows "SLAVE" instead.
Note: As of release 3.3.10, the "MASTER/SLAVE" information is no longer available in the bridging mode, but remains available in the port forwarding mode.
The measurement unit is A (Amp), indicating that the reading is the current.
To display the overcurrent protector information:
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 the desired 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 is normal.

OPEN: The selected circuit breaker is open, or the selected fuse has burned out. When this occurs, the term CbE is displayed in place of the reading and a blinking word "ALARM" appears next to the word OPEN.
IPv4 Address
The IP address is available in the Device mode, which is indicated by the alphabet 'd' shown at the top of the LCD display. Note that the LCD display only shows the IPv4 address (if available).
Below illustrates the IP address information.
Chapter 5: Using the PX3TS
Section Example information
"d" means the LCD display has entered the Device mode.
The LCD display is showing 192, which is one of the four IP address octets. It will cycle through four octets.
"i4" indicates that the IP address shown on the
LCD display is an IPv4 address.
The word "MASTER" indicates the PX3TS is the master device in a cascading configuration.
For a slave device, it shows "SLAVE" instead.
Note: As of release 3.3.10, the "MASTER/SLAVE" information is no longer available in the bridging mode, but remains available in the port forwarding mode.
If you connect your PX3TS to the wireless network, a Wi-Fi icon is displayed at the bottom-right corner.
To display the IPv4 address:
1. Press the MODE button to enter the Device mode, indicated by an alphabet "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
83
84
Chapter 5: Using the PX3TS
MAC Address
This product's MAC address is retrievable by operating the LCD display.
Below illustrates the MAC address information.
Section Example information
"d" means the LCD display has entered the Device mode.
"M" indicates that the displayed information is the MAC address.
The word "MASTER" indicates the PX3TS is the master device in a cascading configuration.
For a slave device, it shows "SLAVE" instead.
Note: As of release 3.3.10, the "MASTER/SLAVE" information is no longer available in the bridging mode, but remains available in the port forwarding mode.
The LCD display is showing "03," which is part of the MAC address.
To display the MAC address:
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 first two digits to the final two.
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 first two digits of the MAC address.
Chapter 5: Using the PX3TS
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.
Number Example information
The selected target is the environmental sensor whose ID number is 9 (SENSOR 9).
The selected environmental sensor's reading is 22 .
The word "MASTER" indicates the PX3TS is the master device in a cascading configuration.
For a slave device, it shows "SLAVE" instead.
Note: As of release 3.3.10, the "MASTER/SLAVE" information is no longer available in the bridging mode, but remains available in the 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
PX3TS web interface.
4. The LCD display shows the reading or state of the selected sensor in the middle of the LCD display.

When showing a numeric sensor's reading, the appropriate measurement unit is displayed to the right of the reading.
85
86
Chapter 5: Using the PX3TS
Measurement units
% m/s
Sensor types
A relative humidity sensor
A temperature sensor
An air flow sensor
Pa An air pressure sensor
NO measurement units
For an "absolute" humidity sensor, the measurement unit is g/m
3
, which cannot be displayed on the LCD.

Available states for a state sensor:
States nor
Description
Normal 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):
States
On
Off
Description
The actuator is turned on.
The actuator is turned off.
Note: Numeric sensors show both numeric readings and sensor states to indicate 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 indicates the 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 ( information (
C:x
).
P:n
) and chain position
Chapter 5: Using the PX3TS
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 the sensor's chain position.
C:1
, and the second one indicates
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 are alphabetical characters, these alphabetical characters are replaced with dashes (-).
7. Press the FUNC button to display the serial number of the sensor, which is shown 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.
Outlet Switching
This section applies to outlet-switching capable models only.
You can turn on or off any outlet using the LCD display in the outlet switching mode. To do this, you must first enable the front panel outlet control function. See
Miscellaneous
To turn on or off an outlet:
1. Press the MODE button until the LCD display enters the outlet switching mode, which is indicated by the power state of OUTLET 1.
87
88
Chapter 5: Using the PX3TS

When outlet 1 has been powered on, the word 'on' is displayed as shown below.

When outlet 1 has been powered off, the word "oFF" is displayed instead.
2. Press the Up or Down button to select the desired outlet. The selected outlet's number is displayed at the top of the LCD display.
3. Press the FUNC button to perform the outlet switching operation.
The LCD display cycles between two messages as shown in the two diagrams below. In the following diagrams, X represents the selected outlet's number.
To cancel the outlet switching operation, press the FUNC button again.
4. To turn on the outlet, press the Up button. The "on?" confirmation message displays.
To turn off the outlet, press the Down button. The "oF?" confirmation message displays.
Chapter 5: Using the PX3TS
5. Press the same button as step 4 again to confirm the operation.
Note: If you press a different button in this step, for example, pressed the Down button in step 4 but the Up button in step 5, the outlet switching operation is not confirmed and the LCD display will return to the messages in step 3.
6. The outlet switching operation is confirmed now and the LCD display indicates the latest power state of the selected outlet.
 on: The outlet has been turned on.
 oFF: The outlet has been turned off.
7. You can verify the power state of the selected outlet by checking its
LED color. Green indicates the power off state and red indicates the power on state.
Asset Strip Information
If there is any asset strip connected to the PX3TS, 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.
Section Example 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.
"30" indicates that the selected target is the 30th rack unit.
89
90
Chapter 5: Using the PX3TS
Section Example information
The word "MASTER" indicates the PX3TS is the master device in a cascading configuration.
For a slave device, it shows "SLAVE" instead.
Note: As of release 3.3.10, the "MASTER/SLAVE" information is no longer available in the bridging mode, but remains available in the 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 PX3TS enters the Asset Strip mode, as indicated by "ASSET" to the right of the LCD.
2. By default the PX3TS selects the asset strip connected to the first
FEATURE port so it shows "1" at the top. Because the PX3TS 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 the desired 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 to quickly move through several items at once.

If the word "ALARM" appears below the rack unit number, it means no asset 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.
Chapter 5: Using the PX3TS
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 forwarding mode.
A cascaded device's position is available by operating the LCD display.
Below illustrates a slave device's position.
Section Example information
"d" means the LCD display has entered the Device mode.
"CA" indicates that the cascading information is being displayed.
"SLAVE" indicates that this PX3TS 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 USB-cascading position information:
1. Press the MODE button to enter the Device mode, indicated by a 'd' in at the top left of the display.
2. Press the FUNC button until "CA" is displayed at the top right of the display.
3. The device's position is represented by any number defined below:
Number
0
1
2
Device position
Master device
Slave 1
Slave 2
91
92
Chapter 5: Using the PX3TS
4
5
Number
3
Device position
Slave 3
Slave 4
Slave 5
6
7
Slave 6
Slave 7
As of release 3.3.10, the port forwarding mode supports up to 15 slave devices so the numbers 8 to 15 may be shown in this mode.
Reset Buttons
The PX3TS front panel has two reset buttons, which are functionally different.
"RESET" button near the LCD display:
The RESET button resets the control board associated with front panel connection ports and the LCD display.
The PX3TS device can be reset to its factory default values using this button when a serial connection is available. See
Resetting to Factory
Defaults
Without the serial connection, pressing this reset button restarts the
PX3TS device's software without any loss of power to outlets.
Chapter 5: Using the PX3TS
"RESET 2" button near the Alarm indicator lamps:
Pressing this button resets the inlet transfer switch and all inlet power indicator lamps without interrupting the operation of the connected equipment.
Fuses for the Inlet Transfer Switch
PX3TS models always contain two fuses for protecting the inlet transfer switch. These fuses blow when the current flowing through them exceeds the fuse rating.
When a fuse blows due to overload, transfer to the other inlet does NOT occur and the current output to all outlets switches OFF. Transfer to the other inlet will automatically occur only when the fuse malfunction is caused by other reasons than overload.
If any fuse blows or malfunctions, the front panel indicates this situation by turning on the 'Fuse' indicator lamp. See
Alarm Indicator Lamps
(on
At the same time, the internal beeper turns on. See
Beeper
To determine which fuse is blown or malfunctions, check the fuse status in the web interface. See
Dashboard
Transfer Switch
Comparison: Fuses for the inlet transfer switch protect the inlet transfer switch from overload. Overcurrent protectors for outlets, if available, protect associated outlets from overload. The rating of a fuse for the inlet transfer switch is higher than the rating of an overcurrent protector for outlets. See
Overcurrent Protectors for Outlets
(on page 97).
93
94
Chapter 5: Using the PX3TS
Replacing a Fuse on 1U Models
This section introduces how to replace a fuse on a 1U model.
To order replacement fuses from Raritan, see
(on page 535) for correct fuse types.
Technical Specifications
Replacing a "blown" fuse can be performed while both inlets remain connected to power.
To replace a fuse:
1. Identify the bad fuse by checking the fuse status using the LCD display or web interface. See
Overcurrent Protector Information
(on page 81) or Checking Inlet Component Status.
2. Examine your PX3TS and the connected equipment to remove or resolve the cause that results in the overload or short circuit. This step is required, or you cannot proceed with the next step.
3. When you are sure the overload does NOT exist, you can force transfer to the inlet with the good fuse to restore the current output to outlets. See
Manual Transfer When an Alarm is Present
(on

In case the good fuse blows after manual transfer, stop and repeat Step 2.
4. This step is recommended but not required -- disconnect the inlet with the bad fuse from power.
5. Uninstall the bad fuse's holder from the PX3TS. a. Turn the holder counterclockwise to loosen it. b. Remove the holder.
Chapter 5: Using the PX3TS
6. Separate the fuse from the holder.
7. Insert a new fuse into the holder. Make sure the new fuse is identical to the original one.
8. Install back the fuse holder to the PX3TS and turn it clockwise until it is tightened properly.
9. Reconnect the inlet with the fuse replaced to power, if it was disconnected in Step 4.
10. (Optional) You can perform manual transfer back to that inlet, if preferred. See
Manual Transfer
Replacing a Fuse on 2U Models
This section introduces how to replace a fuse on a 2U model.
To order replacement fuses from Raritan, see
(on page 535) for correct fuse types.
Technical Specifications
Replacing a "blown" fuse can be performed while both inlets remain connected to power.
To replace a fuse:
1. Identify the bad fuse by checking the fuse status using the LCD display or web interface. See
Overcurrent Protector Information
(on page 81) or Checking Inlet Component Status.
2. Examine your PX3TS and the connected equipment to remove or resolve the cause that results in the overload or short circuit. This step is required, or you cannot proceed with the next step.
3. When you are sure the overload does NOT exist, you can force transfer to the inlet with the good fuse to restore the current output to outlets. See
Manual Transfer When an Alarm is Present
(on

In case the good fuse blows after manual transfer, stop and repeat Step 2.
95
96
Chapter 5: Using the PX3TS
4. This step is recommended but not required -- disconnect the inlet with the bad fuse from power.
5. Locate the bad fuse's holder on the rear panel.
6. Open the fuse cover.
7. Remove the fuse inside the holder and re-install a new one. Make sure the new fuse is identical to the original one.
8. Close the fuse cover and verify that it is firmly closed.
9. Reconnect the inlet with the fuse replaced to power, if it was disconnected in Step 4.
10. (Optional) You can perform manual transfer back to that inlet, if preferred. See
Manual Transfer
Chapter 5: Using the PX3TS
Overcurrent Protectors for Outlets
PX3TS models rated over 20A (North American) or 16A (international) contain overcurrent protectors for outlets, which are usually branch circuit breakers. These circuit breakers automatically trip (disconnect power) when the current flowing through the circuit breaker exceeds its rating.
If the circuit breaker switches off power, the front panel display shows:
•
CbE
, which means "circuit breaker error." See
Overcurrent
Protector Information
At the same time, the internal beeper turns on. See
Beeper
When a circuit breaker trips, power flow ceases to all outlets connected to it. You must manually reset the circuit breaker so that affected outlets can resume normal operation.
Comparison: Fuses for the inlet transfer switch protect the inlet transfer switch from overload. Overcurrent protectors for outlets, if available, protect associated outlets from overload. The rating of a fuse for the inlet transfer switch is higher than the rating of an overcurrent protector for outlets. See
Fuses for the Inlet Transfer Switch
(on page 93).
Resetting the Button-Type Circuit Breaker
Your button-type circuit breakers may look slightly different from the images shown in this section, but the reset procedure remains the same.
To reset the button-type breakers:
1. Locate the breaker whose ON button is up, indicating that the breaker has tripped.
2. Examine your PX3TS and the connected equipment to remove or resolve the cause that results in the overload or short circuit. This step is required, or you cannot proceed with the next step.
97
98
Chapter 5: Using the PX3TS
3. Press the ON button until it is completely down.
Beeper
The PX3TS includes an internal beeper to issue an audible alarm for an overcurrent protector which is open. An overcurrent protector can be a fuse or a circuit breaker on the PX3TS.
•
The beeper sounds an alarm when any overcurrent protector trips, blows or malfunctions.
• The beeper stops after all tripped overcurrent protectors have been reset, or all blown or bad fuses are replaced with good ones.
Warning: You must power OFF the PX3TS prior to replacing a fuse, or a personal injury or death may be caused.
Tip: To remotely check this beeper's state via the web interface, see
PDU
(on page 130).
Power Cycling the PX3TS
There is no power switch on the PX3TS device. To power cycle the PX3TS, turn OFF
both
branch circuits supplying power to the PX3TS, wait 10 seconds, and then turn on both branch circuits.
Chapter 6 Using the Web Interface
This chapter explains how to use the web interface to administer a
PX3TS.
In This Chapter
Login, Logout and Password Change ...................................................... 100
Webcam Management .............................................................................. 343
Supported Web Browsers
•
Internet Explorer
®
11
• Windows Edge
• Firefox
®
25 and later
• Safari
®
(Mac)
•
®
Chrome
®
52 and later
•
Android 4.2 and later
• iOS 7.0 and later
Note: Depending on the browser you use, spin controls similar to may or may not appear in the numeric input fields. Clicking these adjusts numeric values by 1.
99
Chapter 6: Using the Web Interface
Login, Logout and Password Change
The first time you log in to the PX3TS, use the factory default "admin" user credentials. For details, see the Quick Setup Guide accompanying the product.
After login, you can create user accounts for other users. See
Creating
Users
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 the PX3TS.

If the link-local addressing has been enabled, you can type
pdu.local
instead of an IP address. See
APIPA and Link-Local
Addressing
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 107).
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.
100
4. (Optional) If a security agreement is displayed, accept it. Otherwise, you cannot log in.
Chapter 6: Using the Web Interface

To select the agreement checkbox using the keyboard, first press
Tab to go to the checkbox and then Enter.
Note: To configure the security agreement, see
Enabling the
Restricted Service Agreement
(on page 257).
5. Click Login or press Enter. The PX3TS web interface opens.
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 224).
Changing Your Password
You must have the Change Own Password permission to change your own password. See
Creating Roles
You must have Administrator Privileges to change other users' passwords. See
Editing or Deleting Users
Password change request on first login:
On
first login
, if you have both the Change Local User Management and
Change Security Settings permissions, you can choose to either change your password or ignore it.
•
•
Not Now
ignores the request for this time only.
Do not ask again
ignores the request permanently. If you select this checkbox, then click
Not Now
.
• Or enter the new password and click Ok.
Users without permissions listed must change password.
Note: This password change request also appears if the 'force password change' is enabled in the user account setting. See
Creating Users
(on page 197).
To change your password via the Change Password command:
1. Choose User Management > Change Password.
2. First type the current password, and then the new password twice.
Passwords are case sensitive.

A password comprises 4 to 64 characters.
101
102
Chapter 6: Using the Web Interface
Remembering User Names and Passwords
The PX3TS 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.
The PX3TS does NOT support other browser password managers.
Logout
After finishing your tasks, you should log out to prevent others from accessing the PX3TS web interface.
To log out without closing the web browser:
• Click "Logout" on the top-right corner.
-- OR --
•
Close the PX3TS tab while there are other tabs available in the browser.
To log out by closing the web browser:
•
Click on the top-right corner of the window.
-- OR --
•
Choose File > Close, or File > Exit.
Web Interface Overview
The web interface consists of four areas as shown below.
Operation:
1. Click any menu or submenu item in the area of .
2. That item's data/setup page is then opened in the area of
3. Now you can view or configure settings on the opened page.
.
Chapter 6: Using the Web Interface
4. To return to the main menu and the Dashboard page, click
on the top-left corner.
Number Web interface element
Menu
Data/setup page of the selected menu item

Left side:
- PX3TS device name
Note: To customize the device name, see
PDU
(on page 130).

Right side:
103
104
Chapter 6: Using the Web Interface
Number Web interface element
- Your login name, which you can click to view your user account settings
- Logout button
From top to bottom --

Your PX3TS model

Current firmware version

Online Documentation: link to the PX3TS online help.
- See
Browsing through the Online Help

Raritan Support: link to the Raritan Technical Support webpage.

Date and time of your user account's last login
- Click Last Login to view your login history.

PX3TS system time
- Click Device Time to open the Date/Time setup page.
Chapter 6: Using the Web Interface
Menu
Depending on your model and hardware configuration, your PX3TS may show all or some menu items shown below.
Menu
Dashboard
Information shown
Summary of the PX3TS status, including a list of alerted sensors and alarms, if any.
See
Dashboard
105
106
Chapter 6: Using the Web Interface
Menu
PDU
Inlets
Outlets
Information shown
Device data and settings, such as the device name and MAC address.
See
PDU
Inlet status and settings, such as inlet thresholds.
See
Inlet
Inlets
Outlet status, settings and outlet control if your model is outlet-switching capable.
See
Outlets
OCPs
The OCPs menu item appears only when there are overcurrent protectors implemented on your model.
Peripherals
Feature Port
The name
'Feature Port(s)' will be replaced with one of the device names listed to the right
OCP status and settings, such as OCP thresholds.
See
OCPs
Status and settings of Raritan environmental sensor packages, if connected.
See
Peripherals
Status and settings of the device connected to the Feature port(s), which can be one of the following.

Asset Strip

External Beeper

LHX 20

SHX 30

LHX 40

Power CIM
See
Feature Port
Webcam,
Webcam Snapshots
The webcam-related menu items appear only when there are webcam(s) connected to the PX3TS.
Webcam live snapshots/video and webcam settings.
See
Webcam Management
User Management Data and settings of user accounts and groups, such as password change.
See
User Management
Device Settings Device-related settings, including network, security, system time, event rules and more.
See
Device Settings
Menu
Maintenance
Page
Peripherals
Event Log
Chapter 6: Using the Web Interface
Information shown
Device information and maintenance commands, such as firmware upgrade, device backup and reset.
See
Maintenance
If a menu item contains the submenu, the submenu is shown after clicking that item.
To return to the previous menu list, do any below:
• Click the topmost link with the symbol >. For example, click
.
• Press Backspace on the keyboard.
•
OR click menu.
on the top-left corner to return to the main
Quick Access to a Specific Page
If you often visit a specific page in the PX3TS web interface, you can note down its URL or bookmark it with your web browser. Next time, you can simply enter its URL in the address bar of the browser prior to login.
After login, the PX3TS immediately shows the desired page rather than the Dashboard page.
If needed, you can even send the URL to other users so that they can immediately see that page after login, using their own user credentials.
URL examples:
In the following examples, it is assumed that the IP address of the PX3TS is 192.168.84.118.
URL https://192.168.84.118/#/peripherals https://192.168.84.118/#/maintenance/eventLog/0
107
108
Chapter 6: Using the Web Interface
Sorting a List
If any list displays this arrow in one of its column headers, you are allowed to resort the list by clicking any column header. The list will be resorted in the ascending or descending order based on the selected column.
Example:
1. By default, the Firmware Update History is sorted in the ascending order based on the Timestamp column. Therefore, the arrow is displayed adjacent to the Timestamp header.
2. To have it resorted in the descending order based on the same column, click the Timestamp header.
3. The arrow turns to , indicating the list is sorted in the
"descending" order.
4. To resort the list based on a different column, click a different column header.
5. The arrow now appears adjacent to the selected column header, indicating the list is sorted in the ascending order based on that column.
Dashboard
Chapter 6: Using the Web Interface
The Dashboard page contains five to six sections, based on the model you purchased.
109
110
Chapter 6: Using the Web Interface
Number Section
Transfer Switch
Information shown
Status of the inlet transfer switch.
See
Dashboard - Transfer Switch
Inlet 1/2
Alerted
Sensors
Overview of both inlets' power data.
See
Dashboard - Inlet 1/2

When no sensors enter the alarmed state, this section shows the message "No Alerted Sensors."

When any sensor enters the alarmed state, this section lists all of them.
See
Dashboard - Alerted Sensors
Alarms
This section can show data only after you have set event rules requiring users to take the acknowledgment action.
Inlet History

When there are no unacknowledged events, this section shows the message "No Alarms."

When there are unacknowledged events, this section lists all of them.
See
Dashboard - Alarms
The waveform of the inlet's active power history is displayed by default. You can make it show a different data type.
See
Dashboard - Inlet History
Overcurrent
Protectors
This section is available only when your PX3TS contains overcurrent protectors (OCPs).

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
Note that the Overcurrent Protectors section shows information of the circuit breakers for protecting outlets, NOT the fuses for protecting the inlet transfer switch.
Chapter 6: Using the Web Interface
Dashboard - Transfer Switch
Link to the Transfer Switch page:
To view more information or configure the transfer switch, click its section's title 'Transfer Switch' to go to that page. See
Transfer Switch
Generic power data of the transfer switch:
Available data includes:
•
Operational status -- for details, see
Transfer Switch
•
Inlet phase angle

If the phase angles are not synchronized between two inlets, it shows "out of sync" following the phase angle value.
• Active power (W)
•
Apparent power (VA)
•
RMS current (A)
•
Power factor
• Active energy (kWh or Wh)
111
Chapter 6: Using the Web Interface
Dashboard - Inlet 1/2
States of Inlet 1 and Inlet 2, including fuse states, preferred inlet and active inlet, are all available on the Dashboard page.
Link to the Inlet 1/2 pages:
To view more information or configure the inlet(s), click each inlet's section's title 'Inlet 1' or 'Inlet 2' to go to each inlet's page. See
Individual Inlet Pages
112
Preferred and active inlet:
This page indicates which inlet is the preferred inlet and which one is the active inlet, using the following two icons. If the "Active" icon is not shown on any inlet, neither inlet is powering the outlets, which is the
"off" state.
Chapter 6: Using the Web Interface
Tip: To manually perform the power transfer, go to
Transfer Switch
(on
page 120).
Generic inlet power data:
Each inlet's power data includes:
• RMS voltage (V)
• Line frequency (Hz)
•
Power quality
•
Fuse status
•
MOV status
•
12V supply status
For detailed information on power quality, fuse status, MOV status and
12V supply status, see
Transfer Switch and Inlet Status
Dashboard - Alerted Sensors
When any internal sensors or environmental sensor packages connected to the PX3TS enter an abnormal state, the Alerted Sensors section in the
Dashboard show them for alerting users. This section also lists tripped circuit breakers or blown fuses, if available.
To view detailed information or configure each alerted sensor, you can click each sensor's name to go to individual sensor pages. See
Individual
Sensor/Actuator Pages
If wanted, you can resort the list by clicking the desired column header.
See
Sorting a List
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.
113
114
Chapter 6: Using the Web Interface
• 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
For numeric sensors:
 above upper warning
 below lower warning
For numeric sensors:
 above upper critical
 below lower critical
For state sensors:
 alarmed state
For details, see
Sensor/Actuator States
Chapter 6: Using the Web Interface
Dashboard - Inlet History
The power waveform for the inlet helps you observe whether there were abnormal events within the past tens of minutes. The default is to show the inlet's active power data.
You can have it show the waveform of other inlet power data. Simply
below the select a different data type by clicking the selector diagram. Available data types include:
•
RMS current
• RMS voltage
• Active power
• Apparent power
115
116
Chapter 6: Using the Web Interface
To show the waveform of both inlets or the other inlet:
The default is to show the power waveform of Inlet 1. You can have it show the other inlet's or both inlets' waveforms by selecting the checkbox(es) of the desired inlet(s).

When multiple inlets are displayed, their waveform colors differ.
You can identify each waveform according to the colors of the selected inlet checkboxes as illustrated below.
Chapter 6: Using the Web Interface
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 261).
Only users with the Acknowledge Alarms permission can manually acknowledge an alarm.
To acknowledge an alarm:
•
Click Acknowledge, and that alarm then disappears from the Alarms section.
This table explains each column of the alarms list.
Field
Name
Description
The customized name of the Alarm action.
Reason The first event that triggers the alert.
First Appearance The date and time when the event indicated in the
Reason column occurred for the first time.
Last Appearance The date and time when the event indicated in the
Reason column occurred for the last time.
Count The number of times the event indicated in the
Reason column has occurred.
117
118
Chapter 6: Using the Web Interface
Field
More Alerts
Description
This field appears only when there are more than one type of events triggering this alert.
If there are other types of events (that is, other reasons) triggering the same alert, the total number of additional reasons is displayed. You can click it to view a list of all events triggering this alert.
Dashboard - OCP
Note that the Overcurrent Protectors section shows information of the circuit breakers for protecting outlets, NOT the fuses for protecting the inlet transfer switch.
Each overcurrent protector on the PX3TS draws power from the active inlet and delivers power to associated outlets. These overcurrent protectors prevent outlets from overload by controlling the input current flowing through associated outlets.
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.
Chapter 6: Using the Web Interface
Each OCP's power data:
OCP data from top to bottom includes:
•
RMS current (A)
•
A bar showing OCP current levels
•
OCP status -- open or closed
• Associated line pair, and the OCP current rating (A)
The RMS current bars automatically change colors to indicate the current status if OCP thresholds have been enabled. To configure thresholds, see
OCPs
Status normal above upper warning
Bar colors 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 these two thresholds for current levels.
119
120
Chapter 6: Using the Web Interface
Transfer Switch
On the Transfer Switch page, you can:
• View the transfer switch status, and the history of last several transfers, such as the transfer log.
•
Change power transfer settings.
•
Determine the power quality thresholds of voltage and frequency.
• Perform manual power transfer or re-transfer
Note: Whenever the PX3TS prevents a manual transfer from being performed, it is disabled across all interfaces, including the front panel button, web interface and CLI command.
To open the Transfer Switch page, click 'Transfer Switch' in the
Menu
(on
Transfer switch-related information shown:
•
Transfer switch status
•
Status of Inlet sensors related to the transfer switch
•
Indicate which one is the 'Active' inlet
If the "Active" icon is not shown on any inlet, neither inlet is powering the outlets, which is the "off" state.
Chapter 6: Using the Web Interface
• Indicate which one is the 'Preferred' inlet
For detailed information, see
Transfer Switch and Inlet Status
(on page
126). The same information is also available on the Dashboard page. See
Dashboard - Transfer Switch
Dashboard - Inlet 1/2
To perform manual power transfer or re-transfer:
Performing manual transfer remotely requires either of these permissions: "Switch Transfer Switch" or "Administrator Privileges."
1. Click . This button is functionally identical to the front panel Manual Transfer button.

In the standby state, when the preferred inlet restores to normal, this button is changed to
2. Click Transfer on the confirmation message.
.

If there is presence of any alarm for this power transfer, such as inlet phase sync alarm, a warning message appears. Click Force
Transfer if you decide to continue with the operation.
121
Chapter 6: Using the Web Interface
3. Verify both the "Active" and "Preferred" icons are transferred to the other inlet, indicating that inlet becomes the active and preferred inlet now.
Icon
Preferred
Active
Description
Indicates which one is the preferred inlet.
Indicates which inlet is the first priority to power outlets in the normal state.
Indicates which one is the active inlet, which is powering outlets.
If the "Active" icon is not shown on any inlet, neither inlet is powering the outlets, which is the
"off" state.

In the re-transfer scenario, only the "Active" icon switches to another inlet.
To configure transfer settings:
1. Click Edit Settings.
122
2. Configure the information shown. For details, see
Power transfer
Settings
To configure power quality settings:
1. Click Edit Power Quality Parameters.
Chapter 6: Using the Web Interface
2. Configure the power quality thresholds of both inlets. For details, see
Power Quality Settings
Note: Any changes made to power quality thresholds will change the voltage and frequency threshold values of both inlets. See
Individual
Inlet Pages
(on page 141).
To configure inlet phase angles settings (optional):
If thresholds for inlet phase angle difference are enabled/configured, the
PX3TS reports its values and states whenever a specific threshold is hit.
For example, if the upper warning threshold is enabled and reached, you will see the upper warning alarm and values of inlet phase angle difference in the Dashboard's Alerted Sensors list or event log. These threshold values do not affect phase sync detection or transfers/retransfers.
1. Click .
2. Select Threshold Setup. The "Edit Thresholds for Inlet Phase Angle" dialog appears.
3. Make changes as needed.

To enable any threshold, select the corresponding checkbox.
123
Chapter 6: Using the Web Interface

Type a new value in the accompanying text box.
4. For concepts of thresholds, deassertion hysteresis and assertion timeout, see
Sensor Threshold Settings
To view the waveform of last transfer:
The waveform diagram shows the waveform of the last power transfer.
Tip: To view the waveform of another previous power transfer event, go to the transfer log below the waveform.
124
Number Description
1 Voltage (V)
2 Time (ms)
3 Current (A)
Chapter 6: Using the Web Interface
To view the transfer log:
The transfer log lists the last 10 power transfer events only - automatic or manual. To view the waveform or additional details of any transfer event, click that event in the log.
Tip: To view more transfer events, go to the Event Log. See
Viewing or
Clearing the Local Event Log
(on page 332).
125
126
Chapter 6: Using the Web Interface
Transfer Switch and Inlet Status
On the Transfer Switch page, a normal state's text color is black, a warning state's is yellow, and a critical state's is red.
•
•
Status of the transfer switch:
One or some of the following messages are displayed for indicating the transfer switch state.
•
•
•
•
•
Normal Operation, Fully Redundant
: This is the "normal" state. the preferred inlet is powering the outlets and the alternate inlet is in the normal or warning state.
Standby Inlet Unavailable
: This is the "non-redundant" state. The preferred inlet is powering the outlets while the alternate inlet goes critical or is not connected to power.
Standby, Preferred Inlet Unavailable
: This is the "standby" state. The alternate inlet is powering the outlets while the preferred inlet goes critical or is not connected to power.
Standby, Retransfer Pending
: This is also the "standby" state. The alternate inlet is powering the outlets. The preferred inlet returns to normal, but automatic re-transfer is pending.
Standby, Retransfer Possible
: This is also the "standby" state. The alternate inlet is powering the outlets. The preferred inlet returns to normal and you can perform re-transfer manually.
Overload Detected
: An overload is present.
Internal Fault
: A switch open or switch short fault is detected on the
Inlet 1/2 switch.
Note: The "off" state is indicated by the absence of the "Active" icon on the Transfer Switch page. See
Transfer Switch
(on page 120).
Inlet Phase Angle:
•
•
Indicates the phase angles of both inlets are in synchronization or not, and the value of phase angle difference.
in sync
: In synchronization.
out of sync
: Out of synchronization.
Power data of transfer switch:
•
Active power (W)
•
Apparent power (VA)
• RMS current (A)
• Power Factor
• Active Energy (Wh or kWh)
Chapter 6: Using the Web Interface
Status of inlet sensors related to transfer switch:
Data
Preferred
Active
Power Quality Shows the power quality of both inlets, which is one of the following:
 normal
 warning
 critical
To configure power quality thresholds, see
Transfer Switch
RMS Voltage (V) Shows each inlet's voltage value.
Line Frequency
(Hz)
Shows each inlet's line frequency value.
Fuse Status
MOV Status
+12V Supply
Status
Description
Indicates which inlet is the first priority to power outlets in the normal state.
Indicates which inlet is powering outlets.
If the "Active" icon is not shown on any inlet, neither inlet is powering the outlets, which is the
"off" state.
Indicates whether each fuse works properly.
 open: The fuse works fine.
 closed: The fuse is blown or malfunctions.
 unavailable: The PX3TS cannot determine the fuse's status. For example, "unavailable" is shown when there is no inlet power available.
Indicates whether each inlet's MOV surge protector works properly. If yes, "OK" is displayed. Otherwise, "fault" is displayed.
The transfer switch receives DC 12V power from either inlet. The transfer switch works fine as long as one of the 12V power supplies works properly.
This +12V status field indicates whether each inlet's 12V power supply to the transfer switch functions properly. If yes, "OK" is displayed.
Otherwise, "fault" is displayed.
127
128
Chapter 6: Using the Web Interface
Power Transfer Settings
The following are the factory default transfer settings:
• The front panel Manual Transfer button is enabled.
•
Automatic retransfer is enabled.
•
Wait time prior to performing automatic retransfer is set to 15 seconds.
• Perform automatic retransfer only when inlets are in phase.
Field
Name
Allow Front Panel
Transfer
Description
Customize the PX3TS device name.
Enable/disable the front panel Manual
Transfer button.
If the Manual Transfer button is disabled, the Manual Disabled indicator lamp on the front panel is lit.
Automatic Retransfer Three options are available.



Never
: Disable automatic retransfer.
Always
: Enable automatic retransfer and inlet phase synchronization is NOT required.
Only if phases are in sync
: Automatic retransfer is performed only when inlets are in sync.
See
Automatic Retransfer
Retransfer Wait Time Enter the time (seconds) preferred inlet power must be in the normal state before retransfer occurs.
Chapter 6: Using the Web Interface
Power Quality Settings
Inlet power quality state (normal/warning/critical) is derived from the inlet's voltage and frequency quality - whichever is lower. If voltage or frequency is critical, power quality is critical. If either is warning, quality is warning. When both are normal, power quality is normal.
PX3TS transfers to standby operation when preferred inlet power quality goes critical and retransfers to normal operation when power quality returns to normal. The warning state does not cause transfers and is intended as an early warning indication of a possible problem.
When quality goes from better to worse, the state change is said to assert. You configure how long the quality must remain in the worse state before the state change actually occurs. When quality goes from worse to better, the state change is said to deassert. You configure the hysteresis - how much the quality must be better than the threshold - before the state change occurs.
To configure power quality thresholds for both inlets:
1. Choose Transfer Switch > Edit Power Quality Parameters. See
Transfer Switch
2. Both voltage and frequency thresholds are shown onscreen. The ways to configure them are identical.

Enter upper and lower thresholds for Warning and Critical power quality states.

Enter assertion times (seconds). See
"To Assert" and Assertion
Timeout

Enter deassertion hysteresis values. To disable the deassertion hysteresis, type 0 (zero). See
"To De-assert" and Deassertion
Hysteresis
129
Chapter 6: Using the Web Interface
Note: Any changes made to power quality thresholds will change the voltage and frequency threshold values of both inlets. See
Individual
Inlet Pages
(on page 141).
Example:
If you set the voltage's Lower Critical to 70V and Lower Warning to
80V, Inlet 1's power quality is shown as Critical when Inlet 1's voltage drops to or lower than 70V, and Inlet 2's power quality is shown as
Warning when Inlet 2's voltage falls between 70V and 80V.
PDU
The PX3TS device's generic information and PDU-level global settings are available on the PDU page.
To open the PDU page, click 'PDU' in the
Menu
Device information shown:
•
Firmware version
• Serial number
• MAC address
•
Rating
•
Internal beeper state
To configure global settings:
1. Click Edit Settings.
130
2. Now you can configure the fields.
Chapter 6: Using the Web Interface

Click to select an option.

Select or deselect the checkbox.

Adjust the numeric values.

For time-related fields, if option selection using is not preferred, the value must include a time unit, such as '50 s'. See
Time Units
In the following table, those fields marked with * are available on an outlet-switching capable model only.
Field
Name
*Relay behavior on power loss
*Outlet state on device startup
*Outlet initialization delay on device startup
Function
Customizes the device name.
Note
Selects an operating mode to determine the latching relay behavior when PDU power is lost.


Options: Non-latching and
Latching
Non-latching has all relays open at the power loss while latching may have the relays closed.
See
PX3TS Latching Relay Behavior
Determines the initial power state of
ALL outlets after the PX3TS device powers up.

Options: on, off, and last known
See
Options for Outlet State on
Startup

After removing power from the
PDU, you must wait for a minimum of 10 seconds before powering it up again. Otherwise, the default outlet state settings may not work properly.

You can override the global outlet state setting on a per-outlet basis so specific outlets behave differently on startup. See
Individual Outlet Pages
(on page
Determines how long the PX3TS device waits before providing power to all outlets during power cycling or after recovering from a temporary power loss.

Range: 1 second to 1 hour
See
Initialization Delay Use Cases
131
132
Chapter 6: Using the Web Interface
Field
*Power off period during power cycle
*Inrush Guard
Delay
Peripheral Device
Z Coordinate
Format
Function
Determines the power-off period after the outlet is switched OFF during a power cycle.

Range: 1 second to 1 hour
Note

Power cycling the outlet(s) turns the outlet(s) off and then back on.

You can override this global power cycle setting on a per-outlet basis so specific outlets' power-off period is different. See
Individual
Outlet Pages
Prevents a circuit breaker trip due to inrush current when many devices connected to the PDU are turned on.

Range: 100 milliseconds to 2 seconds
See
Inrush Current and Inrush
Guard Delay
Determines how to describe the vertical locations (Z coordinates) of
Raritan environmental sensor packages.

Options: Rack-Units and
Free-Form
See
Z Coordinate Format
(on page
To specify the location of any sensor/actuators in the data center, see
Individual Sensor/Actuator
Pages
Peripheral Device
Auto Management
Altitude
Enables or disables the automatic management feature for Raritan environmental sensor packages.

The default is to enable it.
Specifies the PX3TS device's altitude above sea level when a Raritan's DPX differential air pressure sensor is attached.

Range: 0 to 3000 meters (0 to 9842 feet)
See
How the Automatic
Management Function Works
(on

The device's altitude is associated with the altitude correction factor.
See
Altitude Correction Factors

The default altitude measurement unit is meter. See
Setting Default
Measurement Units
(on page

You can have the measurement unit vary between meter and foot according to user credentials. See
Setting Your Preferred
Measurement Units
(on page
3. Click Save.
Chapter 6: Using the Web Interface
To reset ALL active energy counters:
An active energy reading is a value of total accumulated energy, which is never reset, even if the power fails or the PX3TS is reset. However, you can manually reset this reading to restart the energy accumulation process.
Only users with the "Admin" role assigned can reset active energy readings.
1. Click .
2. Click Reset on the confirmation message.

All active energy readings on this PX3TS are reset to zero.
Tip: You can choose to reset the active energy reading of an individual inlet. PX3TS-5000 series even allows you to reset an individual outlet's active energy reading. See
Individual Inlet Pages
(on page 141) or
Individual Outlet Pages
(on page 152).
To view total active energy, active power and +12V supply:
A "Sensors" section shows the data of total active energy and total active power, and +12V power supply to the PX3TS controller (+12V Supply 1/2
Status). For information on +12V supply states, see
Transfer Switch and
Inlet Status
• Total active energy = Inlet 1 active energy + Inlet 2 active energy
• Total active power = Inlet 1 active power + Inlet 2 active power
133
Chapter 6: Using the Web Interface
To view waveform of active power:
You can check whether there were abnormal events through the device's active power waveform.
134
To configure the thresholds of total active energy and power:
Click the "Thresholds" section if you want to configure thresholds for total active energy and total active power. See
Setting Thresholds for
Total Active Energy or Power
Internal Beeper State
The PDU page indicates the internal beeper state.
Available beeper states:
States
Off
Description
The beeper is turned off.
Chapter 6: Using the Web Interface
States
Active
Description
The 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 PX3TS, including fuses and circuit breakers, has tripped or blown. See
Beeper
• You have set an event rule that turns on the internal beeper when a specific event occurs, and that event occurs. See
Event Rules and
Actions
Tip: To check the internal beeper state via CLI, see
PDU Configuration
(on page 370).
135
136
Chapter 6: Using the Web Interface
PX3TS Latching Relay Behavior
PX3TS incorporates latching relays in models with outlet switching.
Unlike non-latching relays, latching relays do NOT require power to keep their contacts closed.
PX3TS outlet switching can be configured to operate as a true latching relay or to simulate a non-latching relay. The operating mode determines the latching relay behavior when PDU power is lost.
Regardless of which mode is selected, power is not required to keep relay contacts closed.
Non-Latching Mode:
•
Relay always opens when power is lost. This insures all relays are open when power is applied to the PDU.
• Always select this mode if the combined in-rush current of the devices connected to the PDU trip circuit breakers when power is applied to the PDU.
•
This is the factory default operating mode.
Latching Mode:
•
Relay does not open when power is lost.
• This is the preferred operating mode ONLY if you are sure in-rush current does not trip circuit breakers when power is applied to the
PDU.
•
Power to the outlet is not disrupted if a PDU internal failure occurs.
•
In Latching mode, the following features are disabled.

PDU-level outlet state on startup: See
PDU

Outlet-level outlet state on startup: See
Individual Outlet Pages

PDU-level outlet initialization delay on startup: See
PDU
(on page
Options for Outlet State on Startup
The following are available options for initial power states of outlets after powering up the PX3TS device.
Option on off last known
Function
Turns on the outlet(s).
Turns off the outlet(s).
Restores the outlet(s) to the previous power state(s) before the PX3TS was powered off.
Chapter 6: Using the Web Interface
If you are configuring an individual outlet on
Individual Outlet Pages
page 152), there is one more outlet state option.
(on
Additional option
PDU defined
(xxx)
Function
Follows the global outlet state setting, which is set on
PDU
The value xxx in parentheses is the currently-selected global option - on, off, or last known.
Initialization Delay Use Cases
Apply the initialization delay in either of the following scenarios.
•
When power may not initially be stable after being restored
• When UPS batteries may be charging
Tip:
When there are a large number of outlets, set the value to a lower number so that you can avoid a long wait before all outlets are available.
Inrush Current and Inrush Guard Delay
Inrush current:
When electrical devices are turned on, they can initially draw a very large current known as inrush current. Inrush current typically lasts for 20-40 milliseconds.
Inrush guard delay:
The inrush guard delay feature helps prevent a circuit breaker trip due to the combined inrush current of many devices turned on at the same time.
For example, if the inrush guard delay is set to 100 milliseconds and two or more outlets are turned on at the same time, the PDU will sequentially turn the outlets on with a 100 millisecond delay occurring between each one.
137
138
Chapter 6: Using the Web Interface
Z Coordinate Format
You can use either the number of rack units or a descriptive text to describe the vertical locations (Z coordinates) of environmental sensors and actuators, which are configured on the
Individual Sensor/Actuator
Pages
The Z coordinate format is determined on
PDU
coordinate example, see
Sensor/Actuator Location Example
(on page
Available Z coordinate formats:
•
Rack Units: The height of the Z coordinate is measured in standard rack units. When this is selected, you can type a numeric value in the rack unit to describe the Z coordinate of any environmental sensors or actuators.
• Free-Form: Any alphanumeric string can be used for specifying the Z coordinate. The value can be 0 to 24 characters long.
How the Automatic Management Function Works
This setting is configured on
PDU
After enabling the automatic management function:
When the total number of managed sensors and actuators has not reached the upper limit yet, the PX3TS automatically brings newly-connected environmental sensors and actuators under management after detecting them.
A PX3TS can manage up to 32 sensors/actuators.
After disabling the automatic management function:
The PX3TS 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
Chapter 6: Using the Web Interface
Time Units
If you choose to type a new value in the time-related fields, such as the
Inrush Guard Delay field, you must add a time unit after the numeric value. For example, you can type '15 s' for 15 seconds.
Note that different fields have different range of valid values.
Time units:
Unit ms s min h d
Time millisecond(s) second(s) minute(s) hour(s) day(s)
Setting Thresholds for Total Active Energy or Power
This section applies only to multi-inlet models, including in-line monitors.
Thresholds for total active energy and total active power are disabled by default. You can enable and set them so that you are alerted when the total active energy or total active power hits a certain level.
For a regular PX3TS model with multiple inlets:
• Total active energy = sum of all inlets' active energy values
•
Total active power = sum of all inlets' active power values
To configure thresholds for total active energy and/or power:
1. Click PDU.

On the PDU page, you can also view the total active power and total active energy. See
PDU
2. Click the Thresholds title bar at the bottom of the page to display thresholds.
139
140
Chapter 6: Using the Web Interface
3. Click the desired sensor (required), and then click Edit Thresholds.
Inlets
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 637).
5. Click Save.
The Inlets page lists both inlets, and the overview of each inlet's power data, including:
• Active power (kW or W)
• Apparent power (kVA or VA)
•
Active energy (kWh or Wh)
•
Power factor
•
Line frequency (Hz)
To open this page, click 'Inlets' in the
Menu
Tip: The RMS current data of an inlet is identical to the power data of its fuse.
To view or configure each inlet:
1. Click 'Show Details' of the desired inlet.
Chapter 6: Using the Web Interface
2. Now you can configure the selected inlet, such as enabling thresholds or resetting its energy. See
Individual Inlet Pages
(on
Individual Inlet Pages
You can view all inlet information, configure inlet-related settings, or reset the inlet active energy on each individual inlet's page.
Inlet thresholds, when enabled, help you identify whether the inlet enters the warning or critical level. In addition, you can have the PX3TS automatically generate alert notifications for any warning or critical status. See
Event Rules and Actions
Generic inlet information shown:
• Inlet power overview, which is the same as
Inlets
•
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
141
142
Chapter 6: Using the Web Interface
• Inlet's power waveform, which is the same as
Dashboard - Inlet
History
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. The inlet's custom name is displayed on the Inlet or
Dashboard page, followed by its label in parentheses.
To disable either or both inlets:
1. Click Edit Settings.
2. Select the "Disable this inlet" checkbox.
3. Click Save.
4. The inlet status now shows "Disabled."
5. To disable additional inlets, repeat the above steps.

If disabling an inlet will result in all inlets being disabled, a confirmation dialog appears, indicating that all inlets will be disabled. Then click Yes to confirm this operation or No to abort it.
Chapter 6: Using the Web Interface
After disabling any inlet, the following information or features associated with the disabled one are no longer available:
•
Sensor readings, states, warnings, alarms or event notifications associated with the disabled inlet.
• Sensor readings, states, warnings, alarms or event notifications for all outlets and overcurrent protectors associated with the disabled inlet.
•
The outlet-switching capability, if available, for all outlets associated with the disabled inlet.
Exception: All active energy sensors continue to accumulate data regardless of whether any inlet has been disabled.
Warning: A disabled inlet, if remaining connected to a power source, continues to receive power from the connected power source and supplies power to the associated outlets and overcurrent protectors.
To reset this inlet's active energy:
Only users with the "Admin" role assigned can reset active energy readings.
1. Click .
2. Click Reset on the confirmation message.
This inlet's active energy reading is then reset to zero.
Tip: To reset ALL active energy counters on the PX3TS, see
PDU
(on page
130).
To configure inlet thresholds:
1. Click the Thresholds title bar at the bottom of the page to display inlet thresholds.
143
Chapter 6: Using the Web Interface
2. Click the desired sensor (required), and then click Edit Thresholds.
144
Outlets
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
Warning: The thresholds of voltage and line frequency of each inlet impact the power quality levels. Therefore, it is highly recommended to configure the voltage and line frequency thresholds on the
Transfer Switch page to avoid the power quality inconsistency between both inlets. See
Transfer Switch
(on page 120).
4. Click Save.
The Outlets page shows a list of all outlets and the overview of outlet status and readings. To open this page, click 'Outlets' in the
Menu
(on
On this page, you can:
•
View all outlets' status.
If any outlet sensor enters the alarmed state, it is highlighted in yellow or red. See
Yellow- or Red-Highlighted Sensors
(on page
Chapter 6: Using the Web Interface
• Perform actions on all or multiple outlets simultaneously by using the setup/power-control icons on the top-right corner.
Note that only outlet-switching capable models show the power-control buttons, and you must have the Switch Outlet permission for performing outlet-switching operations.
•
Go to an individual outlet's data/setup page by clicking an outlet's name. See
Individual Outlet Pages
If wanted, you can resort the list by clicking the desired column header.
See
Sorting a List
To show or hide specific columns on the outlets overview page:
1. Click to show a list of outlet data types.
145
146
Chapter 6: Using the Web Interface
2. Select those you want to show, and deselect those you want to hide.
See
Available Data of the Outlets Overview Page
To configure global outlet settings or perform the load-shedding command:
1. Click to show a list of commands.
2. Select the desired command. Note that only outlet-switching capable models show the commands marked with * in the table.
Command
Threshold Bulk Setup
*Sequence Setup
*Load Shedding Setup
Refer to
Bulk Configuration for Outlet
Thresholds
Setting Outlet Power-On Sequence and Delay
Setting Non-Critical Outlets
(on
Load Shedding Mode
*Activate Load Shedding
-- OR--
*Deactivate Load Shedding
To power control or reset the active energy readings of multiple outlets:
You can switch any outlet regardless of its current power state. That is, you can turn on any outlet that is already turned on, or turn off any outlet that is already turned off.
1. Click to make checkboxes appear in front of outlets.
Tip: To perform the desired action on only one outlet, you can simply click that outlet without making the checkboxes appear.
2. Select multiple outlets.

To select ALL outlets, select the topmost checkbox in the header row.
3. Click or select the desired button or command.
Chapter 6: Using the Web Interface
Button/command Action
Power ON.
Power OFF.
> Reset Active Energy
Power cycle.

Power cycling the outlet(s) turns the outlet(s) off and then back on.
Resets active energy readings of selected outlets.

Only users with the "Admin" role assigned can reset active energy readings.
Confirm the operation when prompted.
Tip: To reset ALL active energy counters on the PX3TS, see
PDU
(on
page 130). You can also power control an outlet or reset its active
energy from
Individual Outlet Pages
(on page 152).
4. When "multiple" outlets are involved in an outlet-switching operation, a 'Sequence running' message similar to the following displays before the outlet-switching process finishes.

It indicates how many selected outlets are NOT switched on/off or cycled yet.

If needed, click operation.
to stop the outlet-switching
147
148
Chapter 6: Using the Web Interface
Available Data of the Outlets Overview Page
All or some of the following outlet data is displayed on the outlets overview page based on your model and selection. To show or hide specific data, click . See
Outlets
• Outlet status, which is marked with either icon below. This information is available on outlet-switching capable models only.
Icon Outlet status
Outlet turned on
Outlet turned off
•
RMS current (A)
• Active power (W)
• Power factor
• Non-critical setting for indicating whether the outlet is a non-critical outlet. This information is available on outlet-switching capable models only.
Non-critical setting Description true The outlet is a non-critical outlet, which will be turned OFF in the load shedding mode.
See
Load Shedding Mode
false The outlet is a critical outlet, which will remain unchanged in the load shedding mode.
Note: To set critical and non-critical outlets, go to
Outlets
(on page 144).
Chapter 6: Using the Web Interface
Bulk Configuration for Outlet Thresholds
Outlet thresholds, if enabled, help you identify whether any outlet enters the warning or critical level. See
Yellow- or Red-Highlighted Sensors
(on page 169). In addition, you can have the PX3TS automatically
generate alert notifications for any warning or critical status. See
Event
Rules and Actions
You can configure the thresholds for multiple or all outlets simultaneously on the Outlets page.
To configure thresholds-related settings for multiple outlets:
1. On the Outlets page, click > Threshold Bulk Setup.
2. In the "Show Outlet Sensors of Type" field, select a sensor type.
3. Select one or multiple outlets.

To select ALL outlets, select the topmost checkbox in the header row.
4. Click Edit Thresholds.
5. 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
6. Click Save.
Setting Outlet Power-On Sequence and Delay
By default, outlets are sequentially powered on in the ascending order from outlet 1 to the final when turning ON or power cycling all outlets on the PX3TS device. You can change the order in which the outlets power
ON. This is useful when there is a specific order in which some IT equipment should be powered up first.
In addition, you can make a delay occur between two outlets that are turned on consecutively. For example, if the power-on sequence is Outlet
1 through Outlet 8, and you want the PX3TS to wait for 5 seconds after turning on Outlet 3 before turning on Outlet 4, assign a delay of 5 seconds to Outlet 3.
To set the outlet power-on sequence:
1. On the Outlets page, click > Sequence Setup.
2. Select one or multiple outlets by clicking them one by one in the
'Outlet' column.
149
150
Chapter 6: Using the Web Interface
3. Click the arrow buttons to change the outlet positions.
Button Function
Top
Up
Down
Bottom
Restores to the default sequence
Next time when power cycling the PX3TS, it will turn on all outlets based on the new outlet order.
The new order also applies when performing the power-on or power-cycling operation on partial outlets.
To set a power-on delay for any outlet:
1. On the same outlets list, click the 'Delay' column of the outlet that requires a wait after it is turned on.
2. Type a new value in seconds.
3. Click Save.
The PX3TS will insert a power-on delay between the configured outlet and the one following it during the power-on process.
Setting Non-Critical Outlets
Outlets that are turned off when load shedding is activated are called non-critical. Outlets that are not affected by load shedding are called critical outlets. See
Load Shedding Mode
Per default, all outlets are configured as critical.
To determine critical and non-critical outlets:
1. On the Outlets page, click > Load Shedding Setup.
2. To set non-critical outlets, select the checkboxes of those you want.

To select ALL outlets, select the topmost checkbox in the header row.
3. To turn non-critical outlets into critical ones, deselect their checkboxes.

To deselect ALL outlets, deselect the topmost checkbox in the header row.
Chapter 6: Using the Web Interface
4. Click Save.
Tip: You can also set up non-critical outlet setting by configuring outlets one by one. See
Individual Outlet Pages
(on page 152).
Load Shedding Mode
When a UPS supplying power to the PX3TS switches into battery backup operation, it may be desirable to switch off non-critical outlets to conserve UPS battery life. This feature is known as load shedding.
Outlets that are turned off when load shedding is activated are called non-critical. Outlets that are not affected by load shedding are called critical outlets. By default, all outlets are critical. To set non-critical ones, see
Setting Non-Critical Outlets
When load shedding is activated, the PX3TS turns off all non-critical outlets. When load shedding is deactivated, the PX3TS turns back on all non-critical outlets that were ON before entering the load shedding mode.
Activation of load shedding can be accomplished using the web interface,
SNMP or CLI, or triggered by the contact closure sensors.
Note: It is highly suggested to check the non-critical outlets prior to manually entering the load shedding mode. The non-critical information can be retrieved from the Outlets page. See
Outlets
(on page 144) or
Available Data of the Outlets Overview Page
(on page 148).
To enter the load shedding mode:
1. On the Outlets page, click > Activate Load Shedding.
2. Click Activate on the confirmation message.
In the load shedding mode:

The lock icon appears for all non-critical outlets on the
Outlets page, and you CANNOT turn on any of them.
151
152
Chapter 6: Using the Web Interface

The message "Load Shedding Active" appears next to the
'Outlets' title.
Tip: To make the Non Critical column appear on the Outlets page. See
Outlets
(on page 144) or
Available Data of the Outlets Overview Page
(on page 148).
To exit from the load shedding mode:
1. On the Outlets page, click > Deactivate Load Shedding.
2. Click Deactivate on the confirmation message.
Now you can turn on/off any outlets.
Individual Outlet Pages
An outlet's data/setup page is opened after clicking the outlet's name on the Outlets overview page. See
Outlets
Chapter 6: Using the Web Interface
The individual outlet's page shows this outlet's detailed information. See
Detailed Information on Outlet Pages
In addition, you can perform the following operations on this outlet page.
Note that only outlet-switching capable models show the power-control buttons, and you must have the Switch Outlet permission for performing outlet-switching operations.
To power control this outlet:
1. Click one of the power-control buttons.
Button/command Action
Power ON.
Power OFF.
Power cycle.

Power cycling the outlet(s) turns the outlet(s) off and then back on.
2. Confirm it on the confirmation message.
153
Chapter 6: Using the Web Interface
Tip: To switch an outlet using the front panel display, see
Outlet
Switching
(on page 87).
To configure this outlet:
1. Click Edit Settings.
154
2. Configure available fields. Note that the fields marked with * are only available on outlet-switching capable models.
Field
Name
*State on device startup
*Power off period during power cycle
*Non-critical
Descriptions
Type an outlet name up to 32 characters long.
Click this field to select this outlet's initial power state after the PX3TS powers up.

Options:
See
on
,
off
,
last known
and
PDU defined
Options for Outlet State on Startup
(on
.

Note that any option other than "PDU defined" will override the global outlet state setting on this particular outlet.
Select an option to determine how long this outlet is turned off before turing back on.

Options:
See
PDU defined
or customized time.
Power-Off Period Options for
Individual Outlets

Note that any time setting other than "PDU defined" will override the global power-off period setting on this particular outlet.
Select this checkbox only when you want this outlet to turn off in the load shedding mode. See
Load Shedding Mode
3. Click Save.
Chapter 6: Using the Web Interface
4. The outlet's custom name, if available, is displayed in the outlets list, following by its label in parentheses.
To reset this outlet's active energy reading:
Only users with the "Admin" role assigned can reset active energy readings.
1. Click .
2. Click Reset on the confirmation message.
Tip: To reset ALL active energy counters on the PX3TS, see
PDU
(on page
130).
To view this outlet's power waveform:
By default this outlet's active power data within the past tens of minutes is shown in the waveform diagram.
You can click the selector below the waveform diagram to show a different data type for this outlet, including:
•
RMS current
•
RMS voltage
•
Active power
• Apparent power
155
156
Chapter 6: Using the Web Interface
To configure this outlet's threshold settings:
Note that the threshold values set for an individual outlet will override the bulk threshold values stored on that outlet. See
Bulk Configuration for Outlet Thresholds
1. If the outlet's threshold data is invisible, click the Thresholds title bar to display it.
2. Click the desired sensor (required), and then click Edit Thresholds.
3. Make changes as needed.

To enable any threshold, select the corresponding checkbox.

Type a new value in the accompanying text box.
For concepts of thresholds, deassertion hysteresis and assertion timeout, see
Sensor Threshold Settings
4. Click Save.
Chapter 6: Using the Web Interface
Other operations:
•
You can go to another outlet's data/setup page by clicking the outlet selector on the top-left corner.
Detailed Information on Outlet Pages
Each outlet's data page has the Details section for showing general outlet information and Sensors section for showing the outlet sensor status.
Details section:
Field
Label
Outlet Status
Receptacle Type
Lines
Description
The physical outlet number
This information is only available on outlet-switching capable models.
On or Off
This outlet's receptacle type
Lines associated with this outlet
157
158
Chapter 6: Using the Web Interface
Field
Overcurrent Protector
Description
This information is available only when your PX3TS has overcurrent protectors.
Overcurrent protector associated with this outlet
Sensors section:
• RMS current (A)
• RMS voltage (V)
•
Active power (W)
•
Active energy (Wh)
• Apparent power (VA)
• Power factor
• Line frequency (Hz)
If any outlet sensor enters the alarmed state, it is highlighted in yellow or red. See
Yellow- or Red-Highlighted Sensors
Power-Off Period Options for Individual Outlets
There are two options for setting the power-off period during the power cycle on each individual outlet's page. See
Individual Outlet Pages
(on
Option
PDU defined
(xxx)
Customized time
Function
Follows the global power-off period setting, which is set on
PDU
(on page 130). The value xxx in
parentheses is the current global value.
If selecting this option, do either of the following:

Click to select an existing time option.

Type a new value
with an appropriate time unit added
. See
Time Units
OCPs
Chapter 6: Using the Web Interface
This page is available only when your PX3TS has overcurrent protectors, such as circuit breakers. Note that the Overcurrent
Protectors section shows information of the circuit breakers for protecting outlets, NOT the fuses for protecting the inlet transfer switch.
Each overcurrent protector on the PX3TS draws power from the active inlet and delivers power to associated outlets. These overcurrent protectors prevent outlets from overload by controlling the input current flowing through associated outlets.
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
To open the OCPs page, click 'OCPs' in the
Menu
You can go to each OCP's data/setup page by clicking its name on this page.
If wanted, you can resort the list by clicking the desired column header.
See
Sorting a List
Overcurrent protector overview:
•
OCP status - open (tripped) or closed
•
Current drawn and current bar
The RMS current bars change colors to indicate the status if the OCP thresholds have been configured and enabled.
159
160
Chapter 6: Using the Web Interface
Status normal
Bar colors above upper warning above upper critical
Note: The "below lower warning" and "below lower critical" states also show yellow and red colors respectively. However, it is not meaningful to enable these 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 the PX3TS automatically generate alert notifications for any warning or critical status. See
Event Rules and
Actions
1. Click > Threshold Bulk Setup.
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.

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
5. Click Save.
Chapter 6: Using the Web Interface
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
Dashboard
(on
General OCP information:
Field
Label
Status
Type
Rating
Lines
Protected Outlets
Inlet
RMS current
Description
This OCP's physical number open or closed
This OCP's type
This OCP's rated current
Lines associated with this OCP
Outlets associated with this OCP
Inlet associated with this OCP
This information is useful only when your
PDU has multiple inlets.
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.
161
Chapter 6: Using the Web Interface
To view this OCP's power waveform:
This OCP's RMS current data in waveform is shown in the Overcurrent
Protector History section.
162
To configure this OCP's threshold settings:
1. Click the Thresholds title bar at the bottom of the page to display the threshold 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.

Type a new value in the accompanying text box.
For concepts of thresholds, deassertion hysteresis and assertion timeout, see
Sensor Threshold Settings
4. Click Save.
Chapter 6: Using the Web Interface
Tip: To configure thresholds for multiple OCPs at a time, see
OCPs
(on
page 159).
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.
163
164
Chapter 6: Using the Web Interface
Peripherals
If there are Raritan environmental sensor packages connected to the
PX3TS, they are listed on the Peripherals page. See
Connecting
Environmental Sensor Packages
An environmental sensor package comprises one or some of the following sensors/actuators:
•
Numeric sensors: Detectors that show both readings and states, such as temperature sensors.
• State sensors: Detectors that show states only, such as contact closure sensors.
•
Actuators: An actuator controls a system or mechanism so it shows states only.
The PX3TS communicates with
managed
sensors/actuators only and retrieves their data. It does not communicate with unmanaged ones. See
Managed vs Unmanaged Sensors/Actuators
When the number of "managed" sensors/actuators has not reached the maximum, the PX3TS automatically brings newly-detected sensors/actuators under management by default.
One PX3TS can manage a maximum of 32 sensors/actuators.
Note: To disable the automatic management function, go to
PDU
(on
page 130). 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 Peripherals page by clicking Peripherals in the
Menu
(on page
•
Perform actions on multiple sensors/actuators by using the control/action icons on the top-right corner.
Chapter 6: 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
Sensor/actuator overview on this page:
If any sensor enters the alarmed state, it is highlighted in yellow or red.
See
Yellow- or Red-Highlighted Sensors
never highlighted.
Column
Name
Reading
State
Type
Description
By default the PX3TS assigns a name comprising the following two elements to a newly-managed sensor/actuator.

Sensor/actuator type, such as "Temperature" or
"Dry Contact."

Sequential number of the same sensor/actuator type, like 1, 2, 3 and so on.
You can customize the name. See
Individual
Sensor/Actuator Pages
Only managed 'numeric' sensors show this data, such as temperature and humidity sensors.
The data is available for all sensors and actuators.
See
Sensor/Actuator States
Sensor or actuator type.
165
166
Chapter 6: Using the Web Interface
Column Description
Serial Number This 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
Position The data indicates where this sensor or actuator is located in the sensor chain.
See
Identifying the Sensor Position and Channel
Actuator Indicates whether this sensor package is an actuator or not. If yes, the symbol is shown.
To release or manage sensors/actuators:
When the total of managed sensors/actuators reaches the maximum (32), you cannot manage additional ones. The only way to manage any sensor/actuator is to release or replace any managed ones. To replace a managed sensor/actuator, see
Managing One Sensor or Actuator
page 175). To release any one, follow this procedure.
(on
1. Click to make checkboxes appear in front of sensors/actuators.
Tip: To perform the desired action on only one sensor/actuator, simply click that sensor/actuator without making the checkboxes appear.
2. Select multiple sensors/actuators.

To release sensors/actuators, you must only select "managed" ones. See
Sensor/Actuator States

To manage sensors/actuators, you must only select
"unmanaged" ones.

To select ALL sensors/actuators, select the topmost checkbox in the header row.
3. To release selected ones, click
To manage them, click
> Release.
> Manage.
Chapter 6: Using the Web Interface

The management action triggers a "Manage peripheral device" dialog. Simply click Manage if you are managing sensors/actuators.
multiple

If you are managing only assign an ID number by selecting "Manually select a sensor number." See
one
sensor/actuator, you can choose to
Managing One Sensor or Actuator
4. Now released sensors/actuators become "unmanaged."
Managed ones show one of the managed states.
To configure default threshold settings:
Note that any changes made to default threshold settings not only re-determine the initial threshold values applying to newly-added sensors but also the threshold values of the already-managed sensors where default thresholds are being used. See
Individual
Sensor/Actuator Pages
1. Click > Default Threshold Setup.
167
Chapter 6: Using the Web Interface
2. Click the desired sensor type (required), and then click Edit
Thresholds.
168
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
4. Click Save.
Tip: To customize the threshold settings on a per-sensor basis, go to
Individual Sensor/Actuator Pages
(on page 177).
To turn on or off any actuator(s):
1. Select one or multiple actuators which are off.
in the same status
- on or

To select multiple actuators, click to make checkboxes appear and then select desired actuators.
2. Click the desired button.
: Turn ON.
: Turn OFF.
3. Confirm the operation when prompted.
Tip: If intending to control the actuator via the front panel, see
Front
Panel Settings
(on page 316).
Chapter 6: Using the Web Interface
Yellow- or Red-Highlighted Sensors
The PX3TS highlights those sensors that enter the abnormal state with a yellow or red color. Note that numeric sensors can change colors only after you have enabled their thresholds.
Tip: When an actuator is turned ON, it is also highlighted in red for drawing attention.
For concepts of thresholds, deassertion hysteresis and assertion timeout, see
Sensor Threshold Settings
Sensor status Color
Unknown
Normal
Warning
Critical
In the following table, "R" represents any numeric sensor's reading. The symbol <= means "smaller than" or "equal to."
States shown in the interface unavailable unmanaged normal above upper warning below lower warning above upper critical below lower critical
Description
Sensor state or readings cannot be detected.
Sensors are not being managed. See
Managed vs
Unmanaged Sensors/Actuators

Numeric or state sensors are within the normal range.
-- OR --

No thresholds have been enabled for numeric sensors.
Upper Warning threshold < "R" <= Upper Critical threshold
Lower Critical threshold <= "R" < Lower Warning threshold
Upper Critical threshold < "R"
"R" < Lower Critical threshold
169
170
Chapter 6: Using the Web Interface
Sensor status Color
Alarmed
OCP alarm
States shown in the interface alarmed
Description
State sensors enter the abnormal state.
Open 
Circuit breaker trips.
-- OR --

Fuse blown.
If you have connected a Schroff
®
LHX/SHX heat exchanger, when any sensor implemented on that device fails, it is also highlighted in red.
Managed vs Unmanaged Sensors/Actuators
To manually manage or unmanage/release a sensor or actuator, see
Peripherals
Managed sensors/actuators:
• The PX3TS 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.
Chapter 6: Using the Web Interface
• They show one of the managed states. See
Sensor/Actuator States
•
For managed 'numeric' sensors, their readings are retrieved and displayed. If any numeric sensor is disconnected or its reading cannot be retrieved, it shows "unavailable" for its reading.
Unmanaged sensors/actuators:
• The PX3TS neither communicates with unmanaged sensors/actuators nor retrieves their data.
•
Unmanaged sensors/actuators are listed only when they are physically connected to the PX3TS. They disappear when they are no longer connected.
• They do
not
have an ID number.
• They show the "unmanaged" state.
Sensor/Actuator States
An environmental sensor or actuator shows its real-time state after being managed.
Available sensor states depend on the sensor type -- numeric or state sensors. For example, a contact closure sensor is a state sensor so it switches between three states only --
unavailable
,
alarmed
and
normal
.
Sensors will be highlighted in yellow or red when they enter abnormal states. See
Yellow- or Red-Highlighted Sensors
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 normal
Description

For numeric sensors, it means the readings are within the normal range.

For state sensors, it means they enter the normal state.
"R" < Lower Critical threshold below lower critical below lower warning Lower Critical threshold <= "R" < Lower
Warning threshold above upper warning Upper Warning threshold < "R" <= Upper
Critical threshold above upper critical Upper Critical threshold < "R"
171
172
Chapter 6: Using the Web Interface
State alarmed unavailable
Description
The state sensor enters the abnormal state.

The communication with the managed sensor is lost.
-- OR --

DPX2, DPX3 or DX sensor packages are upgrading their sensor firmware.
Note that for a contact closure sensor, the normal state depends on the normal setting you have configured. Refer to the Environmental Sensors
Guide or Online Help for detailed information, which is available on
Raritan's
Support page
(
http://www.raritan.com/support/
).
Managed actuator states:
State on off unavailable
Description
The actuator is turned on.
The actuator is turned off.

The communication with the managed actuator is lost.
-- OR --

DX sensor packages are upgrading their sensor firmware.
Unmanaged sensor/actuator states:
State unmanaged
Description
Sensors or actuators are physically connected to the PX3TS but not managed yet.
Note: Unmanaged sensors or actuators will disappear from the web interface after they are no longer physically connected to the PX3TS. To manage a sensor/actuator, go to
Peripherals
(on page 164).
Chapter 6: Using the Web Interface
Finding the Sensor's Serial Number
A DPX environmental sensor package includes a serial number tag on the sensor cable.
A DPX2, DPX3 or DX sensor package has a serial number tag attached to its rear side.
The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the PX3TS. Match the serial number from the tag to those listed in the sensor table.
173
174
Chapter 6: Using the Web Interface
Identifying the Sensor Position and Channel
Raritan has developed four types of environmental sensor packages -
DPX, DPX2, DPX3 and DX series. Only DPX2, DPX3 and DX sensor packages can be daisy chained.
The PX3TS can indicate where each sensor or actuator is connected on the Peripheral Devices page.
•
DPX series only shows the sensor port number only.
For example,
Port 1
.
• DPX2, DPX3 and DX series show both the sensor port number and its position in a sensor chain.
For example,
Port 1, Chain Position 2
.
•
If a Raritan DPX3-ENVHUB4 sensor hub is involved, the hub port information is also indicated for DPX2, DPX3 and DX series, but NOT indicated for DPX series.
For example,
Hub Port 3
.
• If a sensor/actuator contains channels, such as a contact closure or dry contact sensor, the channel information is included in the position information.
For example,
Channel 1
.
Sensor/actuator position examples:
Chapter 6: Using the Web Interface
Example
Port 1
Port 1,
Channel 2
Port 1,
Chain Position 4
Port 1,
Chain Position 3,
Channel 2
Port 1,
Chain Position 1,
Hub Port 2,
Chain Position 3
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.

Connected to the sensor port #1.

The sensor/actuator is located in the 4th sensor package of the sensor chain.

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.

Connected to the sensor port #1.

Connected to the 2nd port of the DPX3-ENVHUB4 sensor hub, which shows the following two pieces of information:

The hub's position in the sensor chain -- "Chain Position 1"

The hub port where this particular sensor package is connected -- "Hub
Port 2"

The sensor/actuator is located in the 3rd sensor package of the sensor chain connected to the hub's port 2.
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 you are managing multiple sensors/actuators at a time.
Tip: When the total of managed sensors/actuators reaches the maximum
(32), you cannot manage additional ones. The only way to manage any sensor/actuator is to release or replace any managed ones. To replace a managed one, assign an ID number to it by following this procedure. To release any one, see
Peripherals
(on page 164).
To manage only one sensor/actuator:
1. From the list of "unmanaged" sensors/actuators, click the one you want to manage.
175
176
Chapter 6: Using the Web Interface
2. The "Manage peripheral device" dialog appears.

To let the PX3TS randomly assign an ID number to it, select
"Automatically assign a sensor number."
This method does not release any managed sensor or actuator.

To assign the desired ID number to it, 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 its serial number. Otherwise, it shows the word "unused."
3. Click Manage.
Special note for a Raritan humidity sensor:
A Raritan humidity sensor is able to provide two measurements - relative and absolute humidity values.

A relative humidity value is measured in percentage (%).

An absolute humidity value is measured in grams per cubic meter (g/m
3
).
Chapter 6: Using the Web Interface
However, only relative humidity sensors are "automatically" managed if the automatic management function is enabled. You must "manually" manage absolute humidity sensors as needed.
Note that relative and absolute values of the same humidity sensor do
NOT share the same ID number though they share the same serial number and position.
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
Note that only a numeric sensor has threshold settings, while a state sensor or actuator has no thresholds.
Threshold settings, if enabled, help you identify whether any numeric sensor enters the warning or critical level. See
Yellow- or
Red-Highlighted Sensors
(on page 169). In addition, you can have the
PX3TS automatically generate alert notifications for any warning or critical status. See
Event Rules and Actions
To configure a numeric sensor's threshold settings:
1. Click Edit Thresholds.
177
Chapter 6: Using the Web Interface
2. Select or deselect Use Default Thresholds according to your needs.
178

To have this sensor follow the default threshold settings configured for its sensor type, select the Use Default Thresholds checkbox.
The default threshold settings are configured on the page of
Peripherals

To customize the threshold settings for this particular sensor, deselect the Use Default Thresholds checkbox, and then modify the threshold fields below it.
Note: For concepts of thresholds, deassertion hysteresis and assertion timeout, see
Sensor Threshold Settings
(on page 637).
3. Click Save.
Chapter 6: Using the Web Interface
To set up a sensor's or actuator's physical location and additional settings:
1. Click Edit Settings.
2. Make changes to available fields, and then click Save.
Fields
Binary Sensor
Subtype
Name
Description
Location (X, Y and Z)
Description
This field is available for a contact closure sensor only.
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.
A name for the sensor or actuator.
Any descriptive text you want.
Describe the sensor's or actuator's location in the data center by typing alphanumeric values for the X, Y and Z coordinates. See
Sensor/Actuator
Location Example
If the term "Rack Units" appears in parentheses in the Z location, you must type an integer number. Note that the Z coordinate's format is determined on the page of
PDU
Alarmed to
Normal Delay
This field is available for the DX-PIR presence detector only.
It determines the wait time before the PX3TS announces that the presence detector is back to normal after it actually returns to normal.
Adjust the value in seconds.
179
Chapter 6: Using the Web Interface
To view a numeric sensor's readings waveform:
This sensor's data within the past tens of minutes is shown in the waveform diagram. Note that only a numeric sensor has this diagram.
State sensors and actuators do not show such data.
180
To turn on or off an actuator:
1. Click the desired control button.
: Turn ON.
: Turn OFF.
Chapter 6: Using the Web Interface
2. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on.
Other operations:
You can go to another sensor's or actuators's data/setup page by clicking the selector on the top-left corner.
Sensor/Actuator Location Example
Use the X, Y and Z coordinates to describe each sensor's or actuator's physical location in the data center. See
Individual Sensor/Actuator
Pages
The X, Y and Z values act as additional attributes and are not tied to any specific measurement scheme. Therefore, you can use non-measurement values.
Example:
X = Brown Cabinet Row
Y = Third Rack
Z = Top of Cabinet
Values of the X, Y and Z coordinates:
•
X and Y: They can be any alphanumeric values comprising 0 to 24 characters.
•
Z: When the Z coordinate format is set to
Rack Units
, it can be any number ranging from 0 to 60. When its format is set to
Free-Form
can be any alphanumeric value comprising 0 to 24 characters. See
, it
PDU
181
182
Chapter 6: Using the Web Interface
Feature Port
The FEATURE port supports connection to the following devices.
Device
Asset Strip
External
Beeper
LHX 20
SHX 30
LHX 40
Power CIM
Description
Raritan asset strips
An external beeper with the RJ-45 socket.
Schroff
Schroff
®
®
LHX-20 heat exchanger.
SHX-30 heat exchanger.
Schroff
®
LHX-40 heat exchanger.
This type represents one of the following Raritan products:

Raritan power CIM, D2CIM-PWR. This CIM is used to connect the PX3TS to the Raritan digital KVM switch -- Dominion KX II / III.

Dominion KSX II

Dominion SX or SX II
Chapter 6: Using the Web Interface
When the PX3TS 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
External
Beeper
Schroff LHX/SHX
Power CIM
When no devices are detected, the PX3TS displays the name 'Feature
Port" and the Feature Port page shows the message "No device is currently connected."
Open the Feature Port page by clicking it in the
Menu
From this page, you can enable or disable this port's detection capability, or force it to show a specific device's data/settings even though no device is detected.
Note: You must enable the LHX/SHX support for the PX3TS to detect the presence of a supported Schroff
®
LHX/SHX heat exchanger. See
Miscellaneous
(on page 324).
To configure the feature port:
1. Click appears.
on the top-right corner. The Feature Port Setup dialog
2. Click the Detection Mode field, and select one mode.
Mode
Auto
Disabled
Description
Enable the port to automatically detect the device connection.
Disable the port's detection capability.
183
Chapter 6: Using the Web Interface
Mode
Asset Strip,
Raritan asset strips,
LHX 20,
SHX 30,
LHX 40,
Power CIM
Description
Force the PX3TS to show the selected device's data/setup page regardless of the physical connection status.
Note: 'LHX 20', 'SHX 30', and 'LHX 40' are not available when the support of LHX/SHX heat exchangers is disabled. See
Miscellaneous
(on page
324).
Asset Strip
After connecting and detecting Raritan asset management strips (asset strips), the PX3TS shows 'Asset Strip' in place of 'Feature Port' in the menu.
Note: For connection instructions, see
Connecting Asset Management
Strips
(on page 46).
To open the Asset Strip page, click it in the
Menu
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
Feature Port
on the top-right corner, see
To configure asset strip and rack unit settings:
1. Click Edit Settings.
184
2. Make changes to the settings by directly typing a new value, or clicking that field to select a different option.
Chapter 6: Using the Web Interface
Field
Name
Description
Name for this asset strip assembly.
Number of Rack
Units
Total of available tag ports on this asset strip assembly, ranging between 8 and 64.

For the current generation of asset strips, which show the suffix "G3" on its hardware label, the PX3TS automatically detects the number of its tag ports (rack units), and you
cannot
change this value.

For old "non-G3" asset strips, there is no automatic detection for them so you must manually adjust this value.
Numbering Mode The rack unit numbering method in a rack/cabinet.


Top-Down
: The numbering starts from the highest rack unit of a rack/cabinet.
Bottom-Up
: The numbering starts from the lowest rack unit of a rack/cabinet.
Numbering Offset The start number in the rack unit numbering.
For example, if this value is set to 3, then the first number is 3, the second number is 4, and so on.
Orientation The asset strip's orientation by indicating the location of its RJ-45 connector.


Top Connector
: The RJ-45 connector is located on the top.
Bottom Connector
: The RJ-45 connector is located on the bottom.
Asset strips can detect their strip orientation and show it in this field.
You need to adjust this value only when your asset strips are the oldest ones without tilt sensors implemented.
Color with connected tag
Color without connected tag
Click this field to determine the LED color denoting the presence of an asset tag.

Default is green.
Click this field to determine the LED color denoting the absence of an asset tag.

Default is red.
185
Chapter 6: Using the Web Interface
For color settings, there are two ways to set the color.

Click a color in the color palette.

Type the hexadecimal RGB value of the color, such as #00FF00.
3. Click Ok. The rack unit numbering and LED color settings are immediately updated on the Rack Units list illustrated below.

The 'Index' number is the physical tag port number printed on the asset strip, which is not configurable. However, its order will change to reflect the latest rack unit numbering.
186

A blade extension strip and a
programmable
tag are marked with the word 'programmable' in the Asset/ID column. You can customize their Asset IDs. For instructions, refer to this section's last procedure below.

If wanted, you can resort the list by clicking the desired column header. See
Sorting a List
Chapter 6: 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 the selected one appears.
2. Make changes to the information by typing a new value or clicking that field to select a different option.
Field
Name
Description
Name for this rack unit.
For example, you can name it based on the associated IT device.
Operation Mode Determine whether this rack unit's LED behavior automatically changes according to the presence and absence of the asset tag.


Auto
: The LED behavior varies, based on the asset tag's presence.
Manual Override
: This option differentiates this rack unit's LED behavior.
187
188
Chapter 6: Using the Web Interface
Field
LED Mode
LED Color
Description
This field is configurable only after the
Operation Mode is set to Manual Override.
Determine how the LED light behaves for this particular rack unit.




On
: The LED stays lit.
Off
: The LED stays off.
Slow blinking
: The LED blinks slowly.
Fast blinking
: The LED blinks quickly.
This field is configurable only after the
Operation Mode is set to Manual Override.
Determine what LED color is shown for this rack unit if the LED is lit.
To expand a blade extension strip:
A blade extension strip, like an asset strip, has multiple tag ports. An extension strip is marked with a grayer color on the Asset Strip page, and its tag ports list is collapsed by default.
Note: If you need to temporarily disconnect the blade extension strip from the asset strip, wait at least 1 second before re-connecting it back, or the PX3TS device may not detect it.
1. Locate the rack unit (tag port) where the blade extension strip is connected. Click its slot number, whose format is similar to
, where N is the total number of its tag ports.
Chapter 6: 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.

To hide the blade extension slots list, click .
189
Chapter 6: 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 access the PX3TS.
1. Click Program Asset IDs.
190
2. In the Asset/ID column, enter the customized asset IDs by typing values or scanning the barcode.

When using a barcode reader, first click the desired rack unit, and then scan the asset tag. Repeat this step for all desired rack units.
Chapter 6: 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 or Rack Units (see below) to save changes.
191
192
Chapter 6: Using the Web Interface
Asset Strip Automatic Firmware Upgrade
After connecting the asset strip to the PX3TS, it automatically checks its own firmware version against the version of the asset strip firmware stored in the PX3TS firmware. If two versions are different, the asset strip automatically starts downloading the new firmware from the PX3TS to upgrade its own firmware.
During the firmware upgrade, the following events take place:
• The asset strip is completely lit up, with the blinking LEDs cycling through diverse colors.
•
A firmware upgrade process is indicated in the PX3TS web interface.
•
An SNMP trap is sent to indicate the firmware upgrade event.
External Beeper
After connecting and detecting a supported external beeper, the PX3TS shows 'External Beeper' in place of 'Feature Port' in the menu.
Note: For connection instructions, see
Connecting an External Beeper
(on page 58).
To open the External Beeper page, click it in the
Menu
This page shows an external beeper's status, including:
• Number of the FEATURE port where this external beeper is connected
•
Its device type
•
Its connection status
• The beeper's state - off or active
For the functionality of this icon
Feature Port
on the top-right corner, see
Chapter 6: Using the Web Interface
Schroff LHX/SHX
You must enable the LHX/SHX support for the PX3TS to detect the presence of a supported Schroff
®
LHX/SHX heat exchanger. See
Miscellaneous
After enabling the LHX/SHX support and connecting a supported Schroff
®
LHX/SHX heat exchanger to the PX3TS, the PX3TS shows the connected device type in place of 'Feature Port' in the menu -- LHX 20, LHX 40 or
SHX 30.
Note: For connection instructions, see
Connecting a Schroff LHX/SHX
Heat Exchanger
(on page 58).
To open the LHX/SHX page, click 'LHX 20', 'LHX 40' or 'SHX 30' in the
Menu
(on page 105). 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 PX3TS port.
193
194
Chapter 6: Using the Web Interface
For the functionality of this icon
Feature Port
on the top-right corner, see
To view the LHX/SHX device state:
The Operation State field indicates whether the device is operating fine, and the Switch State field indicates its power status.
If the device does not operate properly, such as some sensor failure, it shows "critical" and the symbol .
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.
To configure LHX/SHX settings:
1. Click Edit Settings.
2. Configure the settings as needed.

Provide a customized name.

Specify the desired air outlet setpoint temperature.

Specify the default fan speed.
3. Click Save.
To view all sensor data and configure thresholds:
1. Locate the Sensors section, which lists all air outlet/inlet temperatures and fan speeds, and indicates the door closed/open status of the LHX/SHX device.
2. To set the thresholds for any temperature or fan speed sensor implemented on the LHX/SHX device: a. Click the desired sensor. b. Click Edit Thresholds. c. Enable and set the desired thresholds and deassertion hysteresis.
Note that assertion timeout is NOT available on LHX/SHX. d. Click Save.
3. After thresholds are enabled, sensors may be highlighted in yellow or red if they enter the warning or critical range. See
Yellow- or
Red-Highlighted Sensors
Chapter 6: Using the Web Interface
Tip: You can also create event rules to notify you of the warning or critical levels. See
Event Rules and Actions
(on page 261).
To view sensor alerts and LHX event log:
Remote alert acknowledgment is supported by the LHX-20 and LHX-40.
The SHX-30 does not support this feature.
1. Locate the Alert States section.
2. If any LHX sensors fail, they are indicated. Click Acknowledge to acknowledge the sensor failure.
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 PX3TS 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
SHX Request Maximum Cooling
The PX3TS allows you to remotely activate the Schroff SHX 30's maximum cooling feature. Both LHX 20 and LHX 40 do not support remote activation of maximum cooling.
The Request Maximum Cooling feature is available only after the PX3TS detects SHX 30. For additional information on the SHX 30 maximum cooling feature, see the SHX 30 documentation.
To perform maximum cooling:
•
Go to the SHX page, and click Request Maximum Cooling.
Then the SHX 30 enters into emergency cooling mode and runs at its maximum cooling level of 100% in order to cool the device.
When maximum cooling is requested for an SHX 30, the message
"Maximum cooling requested" is displayed.
To stop maximum cooling:
•
Click Cancel Maximum Cooling.
195
196
Chapter 6: Using the Web Interface
Power CIM
After connecting and detecting a Raritan power CIM, the PX3TS shows
'Power CIM' in place of 'Feature Port' in the menu. See
Configuration
Dominion KX II /
III Configuration
Dominion KSX II, SX or SX II
Open the Power CIM page by clicking it in the
Menu
page shows the CIM's status, including:
• Number of the FEATURE port where this CIM is connected
•
Its device type
•
Its connection status
For the functionality of this icon
Feature Port
on the top-right corner, see
User Management
User Management menu deals with user accounts, permissions, and preferred measurement units on a per-user basis.
The PX3TS is shipped with one built-in administrator account: admin, which is ideal for initial login and system administrator. You can neither delete 'admin' nor change its permissions.
A "role" determines the tasks/actions a user is permitted to perform on the PX3TS so you must assign one or multiple roles to each user.
Click 'User Management' in the
Menu
(on page 105), and the following
submenu displays.
Submenu command Refer to...
Users
Creating Users
Roles
Change Password
Creating Roles
Changing Your Password
Preferences
Default Preferences
Setting Your Preferred Measurement Units
(on
Setting Default Measurement Units
(on page
Chapter 6: 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 > .
Note that you must enter information in the fields showing the message
'required.'
User information:
Field/setting
User Name
Description
The name the user enters to log in to the PX3TS.

4 to 32 characters

Case sensitive

Spaces are NOT permitted.
Full Name
Password,
Confirm Password
The user's first and last names.


4 to 64 characters
Case sensitive

Spaces are permitted.
Telephone Number The user's telephone number eMail Address The user's email address

Up to 64 characters

Case sensitive
Enable When selected, the user can log in to the PX3TS.
197
198
Chapter 6: Using the Web Interface
Field/setting
Force password change on next login
Description
When selected, a password change request automatically appears when next time the user logs in.
For details, see
Changing Your Password
(on
SSH:
You need to enter the SSH public key only if the public key authentication for SSH is enabled. See
Changing SSH Settings
1. Open the SSH public key with a text editor.
2. Copy and paste all content in the text editor into the SSH Public Key field.
SNMPv3:
The SNMPv3 access permission is disabled by default.
Field/setting
Enable SNMPv3
Description
Select this checkbox when intending to permit the
SNMPv3 access by this user.
Note: The SNMPv3 protocol must be enabled for
SNMPv3 access. See
Configuring SNMP Settings
(on page 230).
Security Level Click the field to select a preferred security level from the list:

None: No authentication and no privacy. This is the default.

Authentication: Authentication and no privacy.

Authentication & Privacy: Authentication and privacy.
• Authentication Password: This section is configurable only when
'Authentication' or 'Authentication & Privacy' is selected.
Field/setting
Same as User
Password
Description
Select this checkbox if the authentication password is identical to the user's password.
To specify a different authentication password, disable the checkbox.
Chapter 6: Using the Web Interface
Field/setting
Password,
Confirm Password
Description
Type the authentication password if the 'Same as
User Password' checkbox is deselected.
The password must consist of 8 to 32 ASCII printable characters.
•
Privacy Password: This section is configurable only when
'Authentication & Privacy' is selected.
Field/setting
Same as
Authentication
Password
Description
Select this checkbox if the privacy password is identical to the authentication password.
To specify a different privacy password, disable the checkbox.
Password,
Confirm Password
Type the privacy password if the 'Same as
Authentication Password' checkbox is deselected.
The password must consist of 8 to 32 ASCII printable characters.
• Protocol: This section is configurable only when 'Authentication' or
'Authentication & Privacy' is selected.
Field/setting
Authentication
Privacy
Description
Click this field to select the desired authentication protocol. Two protocols are available:

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 -- (Celsius) or (Fahrenheit).
199
200
Chapter 6: Using the Web Interface
Field
Length Unit
Pressure Unit
Description
Preferred units for length or height -- Meter or
Feet.
Preferred units for pressure -- Pascal or Psi.

Pascal = one newton per square meter

Psi = pounds per square inch
Note: Users can change the measurement units at any time by setting their own preferences. See
Setting Your Preferred Measurement Units
(on page 204).
Roles:
Select one or multiple roles to determine the user's permissions. To select all roles, select the top-most checkbox in the header row.
If the built-in roles do not satisfy your needs, add new roles by clicking
. See
Creating Roles
The Operator role is assigned to a newly-created user account by default.
Built-in role
Admin
Operator
Description
Provide full permissions.
Provide frequently-used permissions, including:
• Acknowledge Alarms
•
Change Own Password
•
Change Pdu, Inlet, Outlet & Overcurrent
Protector Configuration
• Switch Outlet (if your PX3TS is outlet-switching capable)
•
View Event Settings
•
View Local Event Log
Note: With multiple roles selected, a user has the union of all roles' permissions.
Chapter 6: Using the Web Interface
Editing or Deleting Users
To edit or delete users, choose User Management > Users to open the
Users page, which lists all users.
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
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.

For information on each field, see
Creating Users

To change the password, type a new password in the Password and Confirm Password fields. If the password field is left blank, the password remains unchanged.

To delete this user, click
3. Click Save.
, and confirm the operation.
To delete multiple user accounts:
1. On the Users page, click of user names.
to make checkboxes appear in front
Tip: To delete only one user, you can simply click that user without making the checkboxes appear. See the above procedure.
2. Select one or multiple users.

To select all roles, except for the admin role, select the top-most checkbox in the header row.
3. Click .
4. Click Delete on the confirmation message.
201
202
Chapter 6: Using the Web Interface
Creating Roles
A role is a combination of permissions. Each user must have at least one role.
The PX3TS provides two built-in roles. The Operator role is assigned to a newly-created user account per default. See
Creating Users
(on page
Built-in role
Admin
Description
Provide full permissions.
Operator Provide frequently-used permissions, including:
•
Acknowledge Alarms
• Change Own Password
• Change Pdu, Inlet, Outlet & Overcurrent
Protector Configuration
•
Switch Outlet (if your PX3TS is outlet-switching capable)
•
View Event Settings
• View Local Event Log
If the two do not satisfy your needs, add new roles.
To create a role:
1. Choose User Management > Roles > .
2. Assign a role name.

1 to 32 characters long

Case sensitive

Spaces are permitted as of release 3.3.0
3. Type a description for the role in the Description field.
4. Select the desired privilege(s).

The 'Administrator Privileges' includes all privileges.

The 'Unrestricted View Privileges' includes all 'View' privileges.
Chapter 6: Using the Web Interface
5. To select any privilege requiring the argument setting, click to select the desired arguments.

For example, on an outlet-switching capable model, you can specify the outlets that are allowed to be switched on/off for the
'Switch Outlet' privilege as shown below.
6. Click Save.
Now you can assign the role to any user. See
Creating Users
(on page
Editing or Deleting Users
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
The Admin role is not user-configurable so the lock icon displays, indicating that you are not allowed to configure it.
To edit a role:
1. On the Roles page, click the desired role. The Edit Role page opens.
2. Make changes as needed.

The role name cannot be changed.

To delete this role, click , and confirm the operation.
3. Click Save.
To delete any roles:
1. On the Roles page, click of roles.
to make checkboxes appear in front
203
204
Chapter 6: Using the Web Interface
Tip: To delete only one role, you can simply click that user without making the checkboxes appear. See the above procedure.
2. Select one or multiple roles.

To select all roles, except for the Admin role, select the top-most 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 PX3TS 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
201).
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
To select the measurement units you prefer:
1. Choose User Management > Preferences.
2. Make changes as needed.
Field Description
Temperature Unit
Preferred units for temperatures -- (Celsius) or (Fahrenheit).
Length Unit Preferred units for length or height -- Meter or
Feet.
Pressure Unit Preferred units for pressure -- Pascal or Psi.

Pascal = one newton per square meter

Psi = pounds per square inch
3. Click Save.
Chapter 6: Using the Web Interface
Setting Default Measurement Units
Default measurement units are applied to all PX3TS user interfaces across all users, including users accessing the PX3TS via external authentication servers. For a list of affected user interfaces, see also shows the default measurement units.
User
Interfaces Showing Default Units
(on page 205). The front panel display
Note: The preferred measurement units set by any individual user or by the administrator on a per-user basis will override the default units in the web interface and command line interface. See
Setting Your
Preferred Measurement Units
(on page 204) or
Creating Users
(on
page 197).
To set up default user preferences:
1. Click User Management > Default Preferences.
2. Make changes as needed.
Field Description
Temperature Unit Preferred units for temperatures -- (Celsius) or (Fahrenheit).
Length Unit
Pressure Unit
Preferred units for length or height -- Meter or
Feet.
Preferred units for pressure -- Pascal or Psi.

Pascal = one newton per square meter

Psi = pounds per square inch
3. Click Save.
User Interfaces Showing Default Units
Default measurement units will apply to the following user interfaces or information:
•
Web interface for "newly-created" local users when they have not configured their own preferred measurement units. See
Creating
Users
•
Web interface for users who are authenticated via LDAP/Radius servers.
• The sensor report sent because of the "Send Sensor Report" action.
See
Send Sensor Report
•
Front panel LCD display.
205
206
Chapter 6: Using the Web Interface
Device Settings
Click 'Device Settings' in the submenu displays.
Menu
(on page 105), and the following
Menu command Submenu command Refer to...
Network
Configuring Network Settings
Network Services HTTP
SNMP
SMTP Server
Changing HTTP(S) Settings
Configuring SNMP Settings
Configuring SMTP Settings
SSH
Changing SSH Settings
Telnet
Security
Modbus
Server Advertising
IP Access Control
Role Access Control
SSL Certificate
Authentication
Login Settings
Changing Telnet Settings
Changing Modbus Settings
Enabling Service Advertising
Creating IP Access Control Rules
Creating Role Access Control Rules
Setting Up an SSL/TLS Certificate
Setting Up External Authentication
Date/Time
Event Rules
Data Logging
Data Push
Password Policy
Service Agreement
Configuring Login Settings
Configuring Password Policy
Enabling the Restricted Service Agreement
(on
Setting the Date and Time
Event Rules and Actions
Setting Data Logging
Configuring Data Push Settings
Monitoring Server Accessibility
Server
Reachability
Front Panel*
Serial Port
Lua Scripts
Miscellaneous
Front Panel Settings
Configuring the Serial Port
Lua Scripts
Miscellaneous
Chapter 6: Using the Web Interface
* The availability of "Front Panel" depends on the model.
Configuring Network Settings
Configure wired, wireless, and Internet protocol-related settings on the
Network page after
connecting the PX3TS to your network
You can enable both the wired and wireless networking on the PX3TS 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 the
PX3TS enters the port forwarding mode so that the PX3TS has more than one IPv4 or IPv6 address in the port forwarding mode.
However, the PX3TS 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 the ETHERNET and
WIRELESS interfaces do NOT function.
To set up the network settings:
1. Choose Device Settings > Network.
2. To use DHCP-assigned DNS servers and gateway instead of static ones, go to step 3. To manually specify DNS servers and default gateway, configure the Common Network Settings section. See
Common Network Settings

Static routes and cascading mode are in this section. You need to configure them only when there are such local requirements.
See
Setting the Cascading Mode
Examples
Static Route
3. To configure IPv4/IPv6 settings for a
wired
network, click the
ETHERNET or BRIDGE section. See
Wired Network Settings
(on

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.
4. To configure IPv4/IPv6 settings for a
wireless
network, click the
WIRELESS section. See
Wireless Network Settings

You must connect a USB wireless LAN adapter to the PX3TS for wireless networking.
207
208
Chapter 6: Using the Web Interface
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 ETHERNET interface settings, see
Ethernet
Interface Settings
6. Click Save.
After enabling either or both Internet protocols:
After enabling IPv4 and/or IPv6, all but not limited to the following protocols will be compliant with the selected Internet protocol(s):
•
LDAP
• NTP
• SMTP
•
SSH
•
Telnet
•
FTP
•
SSL/TLS
• SNMP
• SysLog
Note: The PX3TS supports TLS
1.0
,
1.1
and
1.2
.
Wired Network Settings
On the Network page, click the ETHERNET section to configure IPv4/IPv6 settings.
If the device's cascading mode is set to 'Bridging', the BRIDGE section appears. Then you must click the BRIDGE section for IPv4/IPv6 settings.
See
Setting the Cascading Mode
Enable Interface:
Make sure the Ethernet interface is enabled, or all networking through this interface fails. This setting is available in the ETHERNET section, but not available in the BRIDGE section.
IPv4 settings:
Field/setting
Enable IPv4
Description
Enable or disable the IPv4 protocol.
Chapter 6: Using the Web Interface
Field/setting
IP Auto
Configuration
Description
Select the method to configure IPv4 settings.

DHCP: Auto-configure IPv4 settings via DHCP servers.

Static: Manually configure the IPv4 settings.
• DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements:

Consists of alphanumeric characters and/or hyphens

Cannot begin or end with a hyphen

Cannot contain more than 63 characters

Cannot contain punctuation marks, spaces, and other symbols
•
Static settings: Assign a static IPv4 address, which follows this syntax "IP address/prefix length".
Example:
192.168.84.99/24
IPv6 settings:
Field/setting
Enable IPv6
Description
Enable or disable the IPv6 protocol.
IP Auto
Configuration
Select the method to configure IPv6 settings.

Automatic: Auto-configure IPv6 settings via
DHCPv6.

Static: Manually configure the IPv6 settings.
• Automatic settings: Optionally specify the preferred hostname, which must meet the above requirements.
•
Static settings: Assign a static IPv6 address, which follows this syntax "IP address/prefix length".
Example:
fd07:2fa:6cff:1111::0/128
Common Network Settings
Common Network Settings are OPTIONAL, not required. Therefore, leave them unchanged if there are no specific local networking requirements.
Field
Cascading Mode
Description
Leave it to the default "None" unless you are establishing a cascading chain.
For more information, refer to:
209
210
Chapter 6: Using the Web Interface
Field
DNS Resolver
Reference
Description


Cascading Multiple PX3TS Devices for
Sharing Ethernet Connectivity
Setting the Cascading Mode
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.
Specify a DNS suffix name if needed. DNS Suffixes
(optional)
First/Second/Third
DNS Server
Manually specify static DNS server(s).

If any static DNS server is specified in these fields, it will override the DHCP-assigned DNS server.

If DHCP (or Automatic) is selected for
IPv4/IPv6 settings, and there are NO static
DNS servers specified, the PX3TS will use
DHCP-assigned DNS servers.
IPv4/IPv6 Routes You need to configure these settings only when your local network contains two subnets, and you want PX3TS to communicate with the other subnet.
If so, make sure IP forwarding has been enabled in your network, and then you can click 'Add
Route' to add static routes.
See
Static Route Examples
Ethernet Interface Settings
By default the Ethernet interface is enabled.
Enable Interface:
Make sure the Ethernet interface is enabled, or all networking through this interface fails. This setting is available in the ETHERNET section, but not available in the BRIDGE section.
Chapter 6: Using the Web Interface
Other Ethernet settings:
Field
Speed
Duplex
Current State
Description
Select a LAN speed.
•
Auto: System determines the optimum LAN speed through auto-negotiation.
• 10 MBit/s: Speed is always 10 Mbps.
• 100 MBit/s: Speed is always 100 Mbps.
Select a duplex mode.
•
Auto: The PX3TS selects the optimum transmission mode through auto-negotiation.
• Full: Data is transmitted in both directions simultaneously.
• Half: Data is transmitted in one direction (to or from the PX3TS device) at a time.
Show the LAN's current status, including the current speed and duplex mode.
Note: Auto-negotiation is disabled after setting both the speed and duplex settings of the PX3TS to NON-Auto values, which may result in a duplex mismatch.
Wireless Network Settings
If the device's cascading mode is set to 'Bridging' or its role is set to
'Slave' in the port forwarding mode, the wireless settings will be disabled.
See
Setting the Cascading Mode
By default the wireless interface is disabled. You should enable it if wireless networking is wanted.
Interface Settings:
Field/setting
Enable Interface
Hardware State
Description
Enable or disable the wireless interface.
When disabled, the wireless networking fails.
Check this field to ensure that the PX3TS device has detected a wireless USB LAN adapter. If not, verify whether the USB LAN adapter is firmly connected or whether it is supported.
211
212
Chapter 6: Using the Web Interface
Field/setting
SSID
Force AP BSSID
BSSID
Enable High
Throughput
(802.11n)
Authentication
Description
Type the name of the wireless access point (AP)
If the BSSID is available, select this checkbox
Type the MAC address of an access point
Enable or disable 802.11n protocol.
Pre-Shared Key
Identity
Password
CA Certificate
Select an authentication method.

No Authentication: No authentication data is required.

PSK: A Pre-Shared Key is required.

EAP - PEAP: Use Protected Extensible
Authentication Protocol. Only MSCHAPv2 is supported. Enter required authentication data in the fields that appear.
This field appears only when PSK is selected.
Type the PSK string
This field appears only when 'EAP - PEAP' is selected.
Type your user name.
This field appears only when 'EAP - PEAP' is selected.
Type your password.
This field appears only when 'EAP - PEAP' is selected.
A third-party CA certificate may or may not be needed. If needed, follow the steps below.
Chapter 6: Using the Web Interface
• Available settings for the CA Certificate:
Field/setting
Enable verification of TLS certificate chain
Allow expired and not yet valid certificates
Allow wireless connection if system clock is incorrect
Description
Select this checkbox for the PX3TS to verify the validity of the TLS certificate that will be installed.

For example, the PX3TS will check the certificate's validity period against the system time.
Click this button to install 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.

Select this checkbox to make the authentication succeed regardless of the certificate's validity period.

After deselecting this checkbox, the authentication fails whenever any certificate in the selected certificate chain is outdated or not valid yet.
When this checkbox is deselected, and if the system time is incorrect, the installed TLS certificate is considered not valid yet and will cause the wireless network connection to fail.
When this checkbox is selected, it will make the wireless network connection successful when the
PX3TS system time is earlier than the firmware build before synchronizing with any NTP server.

The incorrect system time issue may occur when the PX3TS has once been powered off for a long time.
IPv4 settings:
Field/setting
Enable IPv4
IP Auto
Configuration
Description
Enable or disable the IPv4 protocol.
Select the method to configure IPv4 settings.

DHCP: Auto-configure IPv4 settings via DHCP servers.

Static: Manually configure the IPv4 settings.
213
214
Chapter 6: Using the Web Interface
• DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements:

Consists of alphanumeric characters and/or hyphens

Cannot begin or end with a hyphen

Cannot contain more than 63 characters

Cannot contain punctuation marks, spaces, and other symbols
•
Static settings: Assign a static IPv4 address, which follows this syntax "IP address/prefix length".
Example:
192.168.84.99/24
IPv6 settings:
Field/setting
Enable IPv6
Description
Enable or disable the IPv6 protocol.
IP Auto
Configuration
Select the method to configure IPv6 settings.

Automatic: Auto-configure IPv6 settings via
DHCPv6.

Static: Manually configure the IPv6 settings.
• Automatic settings: Optionally specify the preferred hostname, which must meet the above requirements.
•
Static settings: Assign a static IPv6 address, which follows this syntax "IP address/prefix length".
Example:
fd07:2fa:6cff:1111::0/128
(Optional) To view the wireless LAN diagnostic log:
•
Click Show WLAN Diagnostic Log. See
Wireless LAN Diagnostic
Log
Chapter 6: Using the Web Interface
Wireless LAN Diagnostic Log
The PX3TS provides a diagnostic log for inspecting connection errors that occurred over the wireless network interface. The information is useful for technical support.
Note that the WLAN Diagnostic Log shows data only after the Network
Interface is set to Wireless.
Each entry in the log consists of:
•
ID number
•
Date and time
•
Description
To view the log:
1. Choose Device Settings > Network > WIRELESS > Show WLAN
Diagnostic Log. See
Configuring Network Settings
2. To go to other pages of the log, click the pagination bar at the bottom of the page.

If there are more than 5 pages and the page numbers displayed in the bar does not show the desired one, click to have it show the next or previous five page numbers, if available.
3. To refresh the diagnostic, click corner.
on the top-right
4. If wanted, you can resort the list by clicking the desired column header. See
Sorting a List
To clear the diagnostic log:
1. On the top-right corner of the log, click >
2. Click Clear Log on the confirmation message.
.
215
216
Chapter 6: 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 been enabled. All of the NICs and PX3TS devices in the examples use static IP addresses.
Most of local multiple networks are not directly reachable and require the use of a gateway. Therefore, we will select Gateway in the following examples. If your local multiple networks are directly reachable, you should select Interface rather than Gateway.
Note: If Interface is selected, you should select an interface name instead of entering an IP address. See
Interface Names
(on page 219).
IPv4 example:
•
Your PX3TS:
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
• Subnet mask:
24
Chapter 6: Using the Web Interface
In this example, NIC-2 (192.168.100.88) is the next hop router for your
PX3TS to communicate with any device in the other subnet 192.168.200.0.
In the IPv4 "Static Routes" section, you should specify:
217
218
Chapter 6: Using the Web Interface
Tip: If you have configured multiple static routes, you can click on any route and then make changes, use or to re-sort the priority, or click to delete it.
IPv6 example:
•
Your PX3TS:
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 6: Using the Web Interface
In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your PX3TS to communicate with any device in the other subnet fd07:2fa:6cff:1111::0. In the IPv6 "Static Routes" section, you should specify:
Tip: If you have configured multiple static routes, you can click on any route and then make changes, use or to re-sort the priority, or click to delete it.
Interface Names
When your local multiple networks are "directly reachable", you should select Interface for static routes. Then choose the interface where another network is connected.
Interface name
BRIDGE
ETHERNET
WIRELESS
Description
When another wired network is connected to the
Ethernet port of your PX3TS, and your PX3TS has been set to the bridging mode, select this interface name instead of the Ethernet interface.
When another wired network is connected to the
Ethernet port of your PX3TS, select this interface name.
When another wireless network is connected to your PX3TS, select this interface name.
219
220
Chapter 6: Using the Web Interface
Setting the Cascading Mode
A maximum of 16 PX3TS devices can be cascaded to share one Ethernet connection. See
Cascading Multiple PX3TS Devices for Sharing
Ethernet Connectivity
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
Only a user with the Change Network Settings can configure the cascading mode.
Note: The PX3TS in the Port Forwarding mode does not support APIPA.
See
APIPA and Link-Local Addressing
(on page 4).
To configure the cascading mode:
1. Connect the device that you will cascade to the LAN and find its IP address, or connect it to a computer.

For the computer connection instructions, see
Connecting the
PX3TS to a Computer

To find the IP address, see
IPv4 Address
2. Log in to its web interface.
3. Choose Device Settings > Network.
4. Select the preferred mode in the Cascading Mode field.

None: No cascading mode is enabled. This is the default.

Bridging: Each device in the cascading chain is accessed with a different IP address.

Port Forwarding: Each device in the cascading chain is accessed with the same IP address but with a different port number assigned. For details on port numbers, see
Port Number Syntax
Tip: If selecting Port Forwarding, the Device Information page will show a list of port numbers for all cascaded devices.
5. For the port forwarding mode, one to two more fields have to be configured. Note that if either setting is incorrectly configured, a networking issue occurs.

Role: Master or Slave. This is to determine which device is the master and which ones are slave devices.

Downstream interface: USB or Ethernet. This is to determine which port of the master device is connected to Slave 1. Always select USB.
Chapter 6: Using the Web Interface
6. Now you can configure the network settings.

Bridging mode: Click the BRIDGE section on the same page.

Port forwarding mode: Click the ETHERNET or WIRELESS section on the same page, depending on the networking method you prefer.
7. Click Save.
For information on accessing each cascaded device in the Port
Forwarding mode, see
Port Forwarding Examples
For information on wired or wireless network settings, see
Wired
Network Settings
Wireless Network Settings
(on page
Online USB-cascading information:
For more information on the USB-cascading configuration, see the
Cascading Guide
, which is available from Raritan website's
Support page
(
http://www.raritan.com/support/
).
Overview of the Cascading Modes
You must apply a cascading mode to the cascading configuration. See
Setting the Cascading Mode
Overview:
• The Bridging mode supports the wired network only, while the Port
Forwarding mode supports both wired and wireless networks.
• All cascading modes support a maximum of 16 devices in a chain.
•
All 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.
• Each cascaded device can be remotely accessed through the network regardless of the cascading mode.
Illustration:
In the following diagrams, it is assumed that users enable the DHCP networking in the cascading configuration comprising four devices.
"M" is the master device and "S" is the slave device.
221
222
Chapter 6: Using the Web Interface
• "Bridging" mode:
In this mode, the DHCP server communicates with every cascaded device respectively and assigns four
different
IP addresses. Each device has its own IP address. The way to remotely access each cascaded device is completely the same as accessing a standalone device in the network.
•
"Port Forwarding" mode:
In this mode, the DHCP server communicates with the master device alone and assigns only one IP address. All slave devices share the same IP address as the master device. You must specify a 5XXXX port number (where X is a number) when remotely accessing any slave device via the shared IP address. See
Port Number Syntax
(on page
Chapter 6: Using the Web Interface
Port Number Syntax
In the Port Forwarding mode, all devices in the USB-cascading configuration share the same IP address. 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
HTTPS
HTTP
SSH
TELNET
NN
00
01
02
03
SNMP 05
MODBUS 06
• XX is a two-digit number representing the device position as shown below.
The following table only lists 7 slave devices, but the port forwarding supports up to 15 slave devices.
Position
Master device
Slave 1
Slave 2
Slave 3
Slave 4
Slave 5
Slave 6
Slave 7
XX
00
01
02
03
04
05
06
07
223
224
Chapter 6: Using the Web Interface
For example, to access the Slave 4 device via Modbus/TCP, the port number is 50604. See further illustrations.
Port Forwarding Examples
Tip: The full list of each cascaded device's port numbers can be retrieved from the web interface. Choose Maintenance > Device Information > Port
Forwarding.
Standard TCP/UDP ports:
The master device can be also accessed through standard TCP/UDP ports as listed in the following table.
Protocols Port Numbers
HTTPS 443
HTTP
SSH
TELNET
SNMP
MODBUS
80
22
23
161
502
In the Port Forwarding mode, the PX3TS does NOT allow you to modify the standard TCP/UDP port configuration, including HTTP, HTTPS, SSH,
Telnet and Modbus/TCP.
Port Forwarding Examples
To access a cascaded device in the Port Forwarding mode, assign a port number to the IP address.
• Master device: Assign proper 5NNXX port numbers or standard
TCP/UDP ports. See
Port Number Syntax
•
Slave device: Assign proper 5NNXX port numbers.
Assumption:
The Port Forwarding mode is applied to a USB-cascading configuration comprising three Raritan devices. The IP address is
192.168.84.77.
Master device:
Position code for the master device is '00' so each port number is 5NN00 as listed below.
Protocols
HTTPS
Port numbers
50000
Chapter 6: Using the Web Interface
Protocols
HTTP
SSH
TELNET
SNMP
MODBUS
Port numbers
50100
50200
50300
50500
50600
Examples using "5NN00" ports:
• To access the master device via HTTPS, the IP address is:
https://192.168.84.77:50000/
•
To access the master device via HTTP, the IP address is:
http://192.168.84.77:50100/
• To access the master device via SSH, the command is:
ssh -p 50200 192.168.84.77
Examples using standard TCP/UDP ports:
•
To access the master device via HTTPS, the IP address is:
https://192.168.84.77:443/
• To access the master device via HTTP, the IP address is:
http://192.168.84.77:80/
•
To access the master device via SSH, the command is:
ssh -p 22 192.168.84.77
Slave 1 device:
Position code for Slave 1 is '01' so each port number is 5NN01 as shown below.
Protocols
HTTPS
HTTP
SSH
TELNET
SNMP
MODBUS
Port numbers
50001
50101
50201
50301
50501
50601
225
226
Chapter 6: Using the Web Interface
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
HTTPS
HTTP
SSH
TELNET
SNMP
MODBUS
Port numbers
50002
50102
50202
50302
50502
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
Chapter 6: Using the Web Interface
Adding, Removing or Swapping Cascaded Devices
Change the cascading mode first before adding any device to a cascading chain, or before disconnecting a cascaded device from the chain.
If you only want to change the cascading mode of an existing chain, or swap the master and slave device, always start from the slave device.
Note: If the following procedures are not followed, a networking issue occurs. When a networking issue occurs, check the cascading connection and/or software settings of all devices in the chain. See
Cascading Troubleshooting
(on page 648).
To add a device to an existing chain:
1. Connect the device that you will cascade to the LAN and find its IP address, or connect it to a computer.
2. Log in to this device and set its cascading mode to be the same as the existing chain's cascading mode. See
Setting the Cascading
Mode
3. Connect it to the chain, using either USB or Ethernet cable.
To remove a device from the chain:
1. Log in to the desired cascaded device, and change its cascading mode to None.
Exception: If you are going to connect the removed device to another cascading chain, set its cascading mode to be the same as the cascading mode of another 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. You must disconnect ALL cascading cables connected to the two devices first before swapping them and reconnecting cascading cables.
227
228
Chapter 6: Using the Web Interface
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.
Configuring Network Services
The PX3TS supports the following network communication services.
HTTPS and HTTP enable the access to the web interface. Telnet and SSH enable the access to the command line interface. See
Using the
Command Line Interface
By default, SSH is enabled, Telnet is disabled, and all TCP ports for supported services are set to standard ports. You can change default settings if necessary.
Note: Telnet access is disabled by default because it communicates openly and is thus insecure.
Submenu command Refer to
HTTP
Changing HTTP(S) Settings
SNMP
SMTP Server
Configuring SNMP Settings
Configuring SMTP Settings
SSH
Telnet
Modbus
Service Advertising
Changing SSH Settings
Changing Telnet Settings
Changing Modbus Settings
Enabling Service Advertising
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.
Chapter 6: Using the Web Interface
Changing HTTP(S) Settings
HTTPS uses Transport Layer Security (TLS) technology to encrypt all traffic to and from the PX3TS so it is a more secure protocol than HTTP.
The PX3TS supports TLS
1.0
,
1.1
and
1.2
.
By default, any access to the PX3TS 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 PX3TS to HTTPS, select the
"Redirect HTTP connections to HTTPS."

The redirection checkbox is configurable only when both HTTP and HTTPS have been enabled.
Special note for AES ciphers:
The PX3TS device's SSL/TLS-based protocols, including HTTPS, support
AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between the PX3TS and the client (such as a web browser), which is impacted by the cipher priority of the PX3TS and the client's cipher availability/settings.
Tip: If intending to force the PX3TS 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.
229
230
Chapter 6: Using the Web Interface
Configuring SNMP Settings
You can enable or disable SNMP communication between an SNMP manager and the PX3TS device. Enabling SNMP communication allows the manager to retrieve and even control the power status of each outlet.
Besides, you may need to configure the SNMP destination(s) if the built-in "System SNMP Notification Rule" is enabled and the SNMP destination has not been set yet. See
Event Rules and Actions
(on page
To configure SNMP communication:
1. Choose Device Settings > Network Services > SNMP.
2. Enable or disable "SNMP v1 / v2c" and/or "SNMP v3" by clicking the corresponding checkbox.

The SNMP v1/v2c read-only access is enabled by default. The default Read Community String is 'public.'

To enable read-write access, type the Write Community String.
Usually the string is 'private.'
3. Enter the MIB-II system group information, if applicable.
 sysContact - the contact person in charge of the system
 sysName - the name assigned to the system
 sysLocation - the location of the system
4. To configure SNMP notifications: a. Select the Enable SNMP Notifications checkbox. b. Select a notification type -- SNMPv2c Trap, SNMPv2c Inform,
SNMPv3 Trap, and SNMPv3 Inform. c. Specify the SNMP notification destinations and enter necessary information. For details, refer to:


SNMPv2c Notifications
SNMPv3 Notifications
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 280). To add
more than three SNMP destinations, you can create new SNMP notification actions. See
Send an SNMP Notification
(on page 292).
5. You must download the SNMP MIB for your PX3TS to use with your
SNMP manager.
Chapter 6: Using the Web Interface a. Click the Download MIBs title bar to show the download links. b. Click the PDU-MIB download link. See
Downloading SNMP MIB
6. Click Save.
Configuring SMTP Settings
The PX3TS can be configured to send alerts or event messages to a specific administrator by email. See
Event Rules and Actions
(on page
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
To set SMTP server settings:
1. Choose Device Settings > Network Services > SMTP Server.
2. Enter the information needed.
Field
Server Name
Port
Description
Type the name or IP address of the mail server.
Type the port number.

Default is 25
Type an email address for the sender. Sender Email
Address
Number of Sending
Retries
Time Between
Sending Retries
Server Requires
Authentication
Type the number of email retries.

Default is 2 retries
Type the interval between email retries in minutes.

Default is 2 minutes.
Select this checkbox if your SMTP server requires password authentication.
231
232
Chapter 6: Using the Web Interface
Field
User Name,
Password
Enable SMTP over
TLS (StartTLS)
Description
Type a user name and password for authentication after selecting the above checkbox.

The length of user name and password ranges between 4 and 64. Case sensitive.

Spaces are not allowed for the user name, but allowed for the password.
If your SMTP server supports the Transport Layer
Security (TLS), select this checkbox.

Settings for the CA Certificate:
Field/setting
Allow expired and not yet valid certificates
Description
Click this button to install 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.

Select this checkbox to make the authentication succeed regardless of the certificate's validity period.

After deselecting this checkbox, the authentication fails whenever any certificate in the selected certificate chain is outdated or not valid yet.
3. 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.
4. Click Save.
Chapter 6: Using the Web Interface
Special note for AES ciphers:
The PX3TS device's SSL/TLS-based protocols, including SMTP over
StartTLS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between the PX3TS and the client (such as a web browser), which is impacted by the cipher priority of the PX3TS and the client's cipher availability/settings.
Tip: If intending to force the PX3TS to use a specific AES cipher, refer to your client's user documentation for information on configuring AES settings.
Changing SSH Settings
You can enable or disable the SSH access to the command line interface, change the TCP port, or set a password or public key for login over the
SSH connection.
To change SSH settings:
1. Choose Device Settings > Network Services > SSH.
2. To enable or disable the SSH access, select or deselect the checkbox.
3. To use a different port, type a port number.
4. Select one of the authentication methods.

Password authentication only: Enables the password-based login only.

Public key authentication only: Enables the public key-based login only.

Password and public key authentication: Enables both the password- and public key-based login. This is the default.
5. Click Save.
If the public key authentication is selected, you must enter a valid SSH public key for each user profile to log in over the SSH connection. See
Creating Users
Changing Telnet Settings
You can enable or disable the Telnet access to the command line interface, or change the TCP port.
To change Telnet settings:
1. Choose Device Settings > Network Services > Telnet.
2. To enable the Telnet access, select the checkbox.
233
234
Chapter 6: Using the Web Interface
3. To use a different port, type a new port number.
4. Click Save.
Changing Modbus Settings
You can enable or disable the Modbus/TCP access to the PX3TS, set it to the read-only mode, or change the TCP port.
To change the Modbus/TCP settings:
1. Choose Device Settings > Network Services > Modbus.
2. To enable the Modbus/TCP access, select the "Modbus/TCP Access" checkbox.
3. To use a different port, type a new port number.
4. To enable the Modbus read-only mode, select the checkbox of the
"Read-only mode" field. To enable the read-write mode, deselect it.
Chapter 6: Using the Web Interface
Enabling Service Advertising
The PX3TS advertises all enabled services that are reachable using the
IP network. This feature uses DNS-SD (Domain Name System-Service
Discovery) and MDNS (Multicast DNS). The advertised services are discovered by clients that have implemented DNS-SD and MDNS.
The advertised services include the following:
• HTTP
•
HTTPS
•
Telnet
•
SSH
•
Modbus
• json-rpc
• SNMP
By default, this feature is enabled.
Enabling this feature also enables Link-Local Multicast Name Resolution
(LLMNR) and/or MDNS, which are required for resolving APIPA host names. See
APIPA and Link-Local Addressing
The service advertisement feature supports both IPv4 and IPv6 protocols.
If you have set a preferred host name for IPv4 and/or IPv6, that host name can be used as the zero configuration .local host name, that is,
<preferred_host_name>.local
, where <preferred_host_name> is the preferred host name you have specified for PX3TS. 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 208).
To enable or disable service advertising:
1. Choose Device Settings > Network Services > Service Advertising.
2. To enable the service advertising, select either or both checkboxes.

To advertise via MDNS, select the Multicast DNS checkbox.

To advertise via LLMNR, select the Link-Local Multicast Name
Resolution checkbox.
3. Click Save.
235
236
Chapter 6: Using the Web Interface
Configuring Security Settings
The PX3TS provides tools to control access. You can enable the internal firewall, create firewall rules, and set login limitations. In addition, you can create and install the certificate or set up external authentication servers for access control. This product supports the SHA-2 certificate.
Tip: To force all HTTP accesses to the PX3TS to be redirected to HTTPS, see
Changing HTTP(S) Settings
(on page 229).
Submenu command Refer to
IP Access Control
Creating IP Access Control Rules
Role Access Control
Creating Role Access Control Rules
SSL Certificate
Authentication
Login Settings
Password Policy
Service Agreement
Setting Up an SSL/TLS Certificate
Setting Up External Authentication
Configuring Login Settings
Configuring Password Policy
Enabling the Restricted Service Agreement
Creating IP Access Control Rules
IP access control rules (firewall rules) determine whether to accept or discard traffic to/from the PX3TS, 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 PX3TS device, the rules are executed in numerical order. Only the first rule that matches the IP address determines whether the traffic is accepted or discarded. Any subsequent rules matching the IP address are ignored.
•
Subnet mask is required.
When typing the IP address, you must specify BOTH the address and a subnet mask. For example, to specify a single address in a Class C network, use this format:
x.x.x.x/24
where
/24
= a subnet mask of 255.255.255.0.
To specify an entire subnet or range of addresses, change the subnet mask accordingly.
Chapter 6: Using the Web Interface
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.

Accept: Accepts traffic from all IPv4 addresses.

Drop: Discards traffic from all IPv4 addresses, without sending any failure notification to the source host.

Reject: Discards traffic from all IPv4 addresses, and an ICMP message is sent to the source host for failure notification.
4. Go to the Inbound Rules section or the Outbound Rules section according to your needs.

Inbound rules control the data sent to the PX3TS.

Outbound rules control the data sent from the PX3TS.
5. Create rules. See the tables for different operations.
ADD a rule to the end of the list

Click Append.

Type an IP address and subnet mask in the IP/Mask field.

Select an option in the Policy field.

Accept: Accepts traffic from/to the specified IP address(es).

Drop: Discards traffic from/to the specified IP address(es), without sending any failure notification to the source or destination host.

Reject: Discards traffic from/to the specified IP address(es), and an ICMP message is sent to the source or destination host for failure notification.
INSERT a rule between two rules

Select the rule above which you want to insert a new rule. For example, to insert a rule between rules #3 and #4, select #4.

Click Insert Above.

Type an IP address and subnet mask in the IP/Mask field.

Select Accept, Drop or Reject in the Policy field. See the above for their descriptions.
The system automatically numbers the rule.
6. When finished, the rules are listed.
237
238
Chapter 6: Using the Web Interface

You can select any existing rule and then click or
to change its priority.
7. Click Save. The rules are applied.
To configure IPv6 access control rules:
1. On the same page, select the Enable IPv6 Access Control checkbox to enable IPv6 access control rules.
2. Follow the same procedure as the above IPv4 rule setup to create
IPv6 rules.
3. Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are not saved.
Editing or Deleting IP Access Control Rules
When an existing IP access control rule requires updates of IP address range and/or policy, modify them accordingly. Or you can delete any unnecessary rules.
To modify or delete a rule:
1. Choose Device Settings > Security > IP Access Control.
2. Go to the IPv4 or IPv6 section.
3. Select the desired rule in the list.

Ensure the IPv4 or IPv6 checkbox has been selected, or you cannot edit or delete any rule.
4. 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

Click to remove it.

To resort its order, click
5. Click Save.
or .

IPv4 rules: Make sure you click the Save button in the IPv4 section, or the changes made to IPv4 rules are not saved.

IPv6 rules: Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are not saved.
Chapter 6: Using the Web Interface
Creating Role Access Control Rules
Role-based access control rules are similar to IP access control rules, except they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses.
Same as IP access control rules, the order of role-based access control rules is important, since the rules are executed in numerical order.
To create IPv4 role-based access control rules:
1. Choose Device Settings > Security > Role 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.

Allow: Accepts traffic from all IPv4 addresses regardless of the user's role.

Deny: Drops traffic from all IPv4 addresses regardless of the user's role.
4. Create rules. See the tables 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.

Allow: Accepts traffic from the specified IP address range when the user is a member of the specified role

Deny: Drops traffic from the specified IP address range when the user is a member of the specified role
239
240
Chapter 6: Using the Web Interface
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 Allow or Deny in the Policy field. See the above for their descriptions.
The system automatically numbers the rule.
5. When finished, the rules are listed on this page.

You can select any existing rule and then click or
to change its priority.
6. Click Save. The rules are applied.
To configure IPv6 access control rules:
1. On the same page, select the "Enable Role Based Access Control for
IPv6" checkbox to enable IPv6 access control rules.
2. Follow the same procedure as the above IPv4 rule setup to create
IPv6 rules.
3. Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are not saved.
Editing or Deleting Role Access Control Rules
You can modify existing rules to update their roles/IP addresses, or or delete them when they are no longer needed.
To modify a role-based access control rule:
1. Choose Device Settings > Security > Role Access Control.
2. Go to the IPv4 or IPv6 section.
3. Select the desired rule in the list.

Ensure the IPv4 or IPv6 checkbox has been selected, or you cannot select any rule.
4. Perform the desired action.

Make changes to the selected rule, and then click Save. For information on each field, see
Creating Role Access Control
Rules
Chapter 6: Using the Web Interface

Click to remove it.

To resort its order, click or .
5. Click Save.

IPv4 rules: Make sure you click the Save button in the IPv4 section, or the changes made to IPv4 rules are not saved.

IPv6 rules: Make sure you click the Save button in the IPv6 section, or the changes made to IPv6 rules are not saved.
Setting Up an SSL/TLS Certificate
Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than
SSL 3.0.
Having an X.509 digital certificate ensures that both parties in an
SSL/TLS connection are who they say they are.
To obtain a CA-signed certificate:
1. Create a Certificate Signing Request (CSR) on the PX3TS. See
Creating a CSR
2. Submit it to a certificate authority (CA). After the CA processes the information in the CSR, it provides you with a certificate.
3. Install the CA-signed certificate onto the PX3TS. See
Installing a
CA-Signed Certificate
Note: If you are using a certificate that is part of a chain of certificates, each part of the chain is signed during the validation process.
A CSR is not required in either scenario below:
•
Make the PX3TS create a
self-signed
certificate. See
Creating a
Self-Signed Certificate
•
Appropriate, valid certificate and key files are already available, and you just need to install them. See
Installing or Downloading
Existing Certificate and Key
241
242
Chapter 6: Using the Web Interface
Creating a CSR
Follow this procedure to create the CSR for your PX3TS device.
Note that you must enter information in the fields showing the message
'required.'
Self Sign
To create a CSR:
1. Choose Device Settings > Security > SSL Certificate.
2. Provide the information requested.

Subject:
Field
Country
State or Province
Locality
Organization
Description
(
The country where your company is located. Use the standard ISO country code. For a list of ISO codes, visit the
ISO website http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm
).
The full name of the state or province where your company is located.
The city where your company is located.
The registered name of your company.
Organizational Unit The name of your department.
Common Name The fully qualified domain name (FQDN) of your PX3TS device.
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.

Key Creation Parameters:
Field
Key Length
Do this
Select an available key length (bits). A larger key length enhances the security, but slows down the PX3TS device's response.

Only 2048 is available now.
For requesting a certificate signed by the CA, ensure this checkbox is NOT selected.
Chapter 6: Using the Web Interface
Field
Challenge,
Confirm Challenge
Do this
Type a password. The password is used to protect the certificate or
CSR. This information is optional.
The value should be 4 to 64 characters long. Case sensitive.
3. Click Create New SSL 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 your computer. a. You are prompted to open or save the file. Click Save to save it onto your computer. b. Submit it to a CA to obtain the digital certificate. c. If the CSR contains incorrect data, click Delete Certificate
Signing Request to remove it, and then repeat the above steps to re-create it.
5. To store the newly-created private key on your computer, click
Download Key in the New SSL Certificate section.
Note: The Download Key button in the Active
SSL Certificate
section is for downloading the private key of the currently-installed certificate rather than the newly-created one.

You are prompted to open or save the file. Click Save to save it onto your computer.
6. After getting the CA-signed certificate, install it. See
Installing a
CA-Signed Certificate
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
After receiving the CA-signed certificate, install it onto the PX3TS.
To install the CA-signed certificate:
1. Choose Device Settings > Security > SSL Certificate.
2. Click to navigate to the CA-signed certificate file.
3. Click Upload to install it.
4. To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section.
243
244
Chapter 6: Using the Web Interface
Creating a Self-Signed Certificate
When appropriate certificate and key files for the PX3TS device are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate.
Note that you must enter information in the fields showing the message
'required.'
To create and install a self-signed certificate:
1. Choose Device Settings > Security > SSL Certificate.
2. Enter information.
Field
Country
Description
(
The country where your company is located. Use the standard ISO country code. For a list of ISO codes, visit the
ISO website http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm
).
The full name of the state or province where your company is located. State or Province
Locality
Organization
The city where your company is located.
The registered name of your company.
Organizational Unit The name of your department.
Common Name The fully qualified domain name (FQDN) of your PX3TS device.
Email Address
Key Length
Self Sign
Validity in days
An email address where you or another administrative user can be reached.
Select an available key length (bits). A larger key length enhances the security, but slows down the PX3TS device's response.

Only 2048 is available now.
Ensure this checkbox is selected, which indicates that you are creating a self-signed certificate.
This field appears after the Self Sign checkbox is selected.
Type the number of days for which the self-signed certificate will be valid.
A password is not required for a self-signed certificate so the
Challenge and Confirm Challenge fields disappear.
3. Click Create New SSL Key to create both the self-signed certificate and private key. This may take several minutes to complete.
Chapter 6: Using the Web Interface
4. Once complete, do the following: a. Double check the data shown in the New SSL Certificate section. b. If correct, click "Install Key and Certificate" to install the self-signed certificate and private key.
Tip: To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section.
If incorrect, click "Delete Key and Certificate" to remove the self-signed certificate and private key, and then repeat the above steps to re-create them.
5. (Optional) To download the self-signed certificate and/or private key, click Download Certificate or Download Key in the New SSL
Certificate section.

You are prompted to open or save the file. Click Save to save it onto your computer.
Note: The Download Key button in the Active
SSL Certificate
section is for downloading the private key of the currently-installed certificate rather than the newly-created one.
Installing or Downloading Existing Certificate and Key
You can download the already-installed certificate and private key from any PX3TS for backup or file transfer. For example, you can install the files onto a replacement PX3TS device, add the certificate to your browser and so on.
If valid certificate and private key files are already available, you can install them on the PX3TS without going through the process of creating a CSR or a self-signed certificate.
Note: If you are using a certificate that is part of a chain of certificates, each part of the chain is signed during the validation process.
To download active key and certificate files from the PX3TS:
1. Choose Device Settings > Security > SSL Certificate.
2. In the
Active SSL Certificate
section, click Download Key and
Download Certificate respectively.
Note: The Download Key button in the New SSL Certificate section, if present, is for downloading the newly-created private key rather than the one of the currently-installed certificate.
3. You are prompted to open or save the file. Click Save to save it onto your computer.
245
246
Chapter 6: Using the Web Interface
To install available key and certificate files onto the PX3TS:
1. Choose Device Settings > Security > SSL Certificate.
2. Select the "Upload Key and Certificate" checkbox at the bottom of the page.
3. The Key File and Certificate File fields appear. Click to select the key and/or certificate file.
4. Click Upload. The selected files are installed.
5. To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section.
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.
Chapter 6: Using the Web Interface
For security purposes, users attempting to log in to the PX3TS must be authenticated. The PX3TS supports the following authentication mechanisms:
•
Local user database on the PX3TS
•
Lightweight Directory Access Protocol (LDAP)
• Remote Access Dial-In User Service (Radius) protocol
By default, the PX3TS is configured for local authentication. If you stay with this method, you only need to create user accounts. See
Creating
Users
If you prefer external authentication, you must provide the PX3TS with information about the external Authentication and Authorization (AA) server.
If both local and external authentication is needed, create user accounts on the PX3TS in addition to providing the external AA server data.
When configured for external authentication, all PX3TS users must have an account on the external AA server. Local-authentication-only users will have no access to the PX3TS except for the admin, who always can access the PX3TS.
If the external authentication fails, an "Authentication failed" message is displayed. Details regarding the authentication failure are available in the event log. See
Viewing or Clearing the Local Event Log
(on page
Note that only users who have both the "Change Authentication Settings" and "Change Security Settings" permissions can configure or modify the authentication settings.
To enable external authentication:
1. Collect external AA server information. See
Gathering LDAP/Radius
Information
2. Enter required data for external AA server(s) on the PX3TS. See
Adding LDAP/LDAPS Servers
Adding Radius
Servers

For illustrations, see
LDAP Configuration Illustration
(on page
Radius Configuration Illustration
3. If both the external and local authentication is needed, or you have to return to the local authentication only, see
Managing External
Authentication Settings
247
248
Chapter 6: Using the Web Interface
Special note about the AES cipher:
The PX3TS device's SSL/TLS-based protocols, including LDAPS, support
AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between the PX3TS and the client (such as a web browser), which is impacted by the cipher priority of the PX3TS and the client's cipher availability/settings.
Tip: If intending to force the PX3TS 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 PX3TS for external authentication. If you are not familiar with these settings, consult your AA server administrator for help.
Information needed for LDAP authentication:
• The IP address or hostname of the LDAP server
•
Whether the Secure LDAP protocol (LDAP over TLS) is being used

If Secure LDAP is in use, consult your LDAP administrator for the
CA certificate file.
• The network port used by the LDAP server
• The type of the LDAP server, usually one of the following options:

OpenLDAP


If using an OpenLDAP server, consult the LDAP administrator for the Bind Distinguished Name (DN) and password.
Microsoft Active Directory
®
(AD)
Chapter 6: Using the Web Interface

If using a Microsoft Active Directory server, consult your AD administrator for the name of the Active Directory Domain.
• Bind Distinguished Name (DN) and password (if anonymous bind is
NOT used)
• The Base DN of the server (used for searching for users)
•
The login name attribute (or AuthorizationString)
•
The user entry object class
•
The user search subfilter (or BaseSearch)
Information needed for Radius authentication:
• The IP address or host name of the Radius server
• Authentication protocol used by the Radius server
•
Shared secret for a secure communication
•
UDP authentication port and accounting port used by the Radius server
Adding LDAP/LDAPS Servers
To use LDAP authentication, enable it and enter the information you have gathered.
Note that you must enter information in the fields showing the message
'required.'
To add LDAP/LDAPS servers:
1. Choose Device Settings > Security > Authentication.
2. Click New in the LDAP Servers section.
3. Enter information.
Field/setting
IP Address /
Hostname
Description
The IP address or hostname of your LDAP/LDAPS server.

Important: Without the encryption enabled, you can type either the domain name or IP address in this field, but you must type the fully qualified domain name if the encryption is enabled.
Copy settings from existing LDAP server
This checkbox appears only when there are existing AA server settings on the PX3TS. To duplicate any existing AA server's settings, refer to the duplicating procedure below.
249
250
Chapter 6: Using the Web Interface
Field/setting Description
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
Port
(None/StartTLS)
Determine whether you would like to use Transport Layer Security
(TLS) encryption, which allows the PX3TS to communicate securely with the LDAPS server.
Three options are available:

StartTLS

TLS

None
The default Port is 389. Either use the standard LDAP TCP port or specify another port.
Port (TLS) Configurable only when "TLS" is selected in the Security field.
The default is 636. Either use the default port or specify another one.
Enable verification of LDAP Server
Certificate
CA Certificate
Select this checkbox if it is required to validate the LDAP server's certificate by the PX3TS prior to the connection.
If the certificate validation fails, the connection is refused.
Consult your AA server administrator to get the CA certificate file for the LDAPS server.
Allow expired and not yet valid certificates
Anonymous Bind
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.

Select this checkbox to make the authentication succeed regardless of the certificate's validity period.

After deselecting this checkbox, the authentication fails whenever any certificate in the selected certificate chain is outdated or not valid yet.
Use this checkbox to enable or disable anonymous bind.

To use anonymous bind, select this checkbox.

When a Bind DN and password are required to bind to the external
LDAP/LDAPS server, deselect this checkbox.
Chapter 6: Using the Web Interface
Field/setting
Bind DN
Description
Required after deselecting the Anonymous Bind checkbox.
Distinguished Name (DN) of the user who is permitted to search the
LDAP directory in the defined search base.
Bind Password,
Confirm Bind
Password
Required after deselecting the Anonymous Bind checkbox.
Enter the Bind password.
Base DN for Search Distinguished Name (DN) of the search base, which is the starting point of the LDAP search.

Example: ou=dev,dc=example,dc=com
Login Name
Attribute
The attribute of the LDAP user class which denotes the login name.

Usually it is the uid.
User Entry Object
Class
The object class for user entries.

Usually it is inetOrgPerson.
User Search
Subfilter
Search criteria for finding LDAP user objects within the directory tree.
Active Directory
Domain
The name of the Active Directory Domain.

Example: testradius.com
4. To verify if the authentication configuration is set correctly, click Test
Connection to check whether the PX3TS can connect to the new server successfully.
Tip: You can also test the connection on the Authentication page after finishing adding servers. See
Managing External Authentication
Settings
(on page 254).
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.
251
252
Chapter 6: Using the Web Interface
To duplicate LDAP/LDAPS server settings:
If you have added any LDAP/LDAPS server to the PX3TS, and the server you will add shares identical settings with an existing one, the most convenient way is to duplicate that LDAP/LDAPS server's data and then revise the IP address/host name.
1. Repeat Steps 1 to 2 in the above procedure.
2. Select the "Copy settings from existing LDAP server" checkbox.
3. Click the "Select LDAP Server" field to select the LDAP/LDAPS server whose settings you want to copy.
4. Modify the IP Address/Hostname field.
5. Click Add Server.
Note: If the PX3TS clock and the LDAP server clock are out of sync, the installed TLS certificates, if any, may be considered expired. To ensure proper synchronization, administrators should configure the PX3TS and the LDAP server to use the same NTP server(s).
Adding Radius Servers
To use Radius authentication, enable it and enter the information you have gathered.
Note that you must enter information in the fields showing the message
'required.'
Field/setting
IP Address /
Hostname
Type of RADIUS
Authentication
To add Radius servers:
1. Choose Device Settings > Security > Authentication.
2. Click New in the Radius section.
3. Enter information.
Description
The IP address or hostname of your Radius server.
Select an authentication protocol.

PAP (Password Authentication Protocol)

CHAP (Challenge Handshake Authentication Protocol)
CHAP is generally considered more secure because the user name and password are encrypted, while in PAP they are transmitted in the clear.
Chapter 6: Using the Web Interface
Field/setting
Authentication Port,
Accounting Port
Timeout
Retries
Shared Secret,
Confirm Shared
Secret
Description
The default are standard ports -- 1812 and 1813.
To use non-standard ports, type a new port number.
This sets the maximum amount of time to establish contact with the
Radius server before timing out.
Type the timeout period in seconds.
Type the number of retries.
The shared secret is necessary to protect communication with the
Radius server.
4. To verify if the authentication configuration is set correctly, click Test
Connection to check whether the PX3TS can connect to the new server successfully.
Tip: You can also test the connection on the Authentication page after finishing adding servers. See
Managing External Authentication
Settings
(on page 254).
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
Radius authentication does not work.
8. Click Save. Radius authentication is now in place.
253
254
Chapter 6: Using the Web Interface
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
Adding Radius Servers

Click Delete to delete the server, and then confirm the operation.

Click Test Connection to test the connection to the selected server. User credentials may be required.

Click or to change the server order, which determines the access priority, and click Save Order to save the new sequence.
Note: Whenever the PX3TS is successfully connected to one external authentication server, it STOPS trying to access the remaining servers in the authentication list regardless of the user authentication result.
To enable both the external and local authentication:
1. In the Authentication Type field, select the external authentication you want -- LDAP or Radius.
Chapter 6: Using the Web Interface
2. Select the following checkbox. Then the PX3TS always tries external authentication first. Whenever the external authentication fails, the
PX3TS switches to local authentication.
3. Click Save.
To disable external authentication:
1. In the Authentication Type, select Local.
2. Click Save.
Configuring Login Settings
Choose Device Settings > Security > Login Settings to open the Login
Settings page, where you can:
•
Configure the user blocking feature.
Note: The user blocking function applies only to local authentication instead of external authentication through AA servers.
•
Determine the timeout period for any inactive user.
•
Prevent simultaneous logins using the same login name.
To configure user blocking:
1. To enable the user blocking feature, select the "Block user on login failure" checkbox.
2. In the "Maximum number of failed logins" field, type a number. This is the maximum number of login failure the user is permitted before the user is blocked from accessing the PX3TS.
3. In the "Block timeout" field, type a value or click to select a time option. This setting determines how long the user is blocked.

If you type a value, the value must be followed by a time unit, such as '4 min.' See
Time Units
4. Click Save.
255
256
Chapter 6: Using the Web Interface
Tip: If any user blocking event occurs, you can unblock that user manually by using the "unblock" CLI command over a local connection.
See
Unblocking a User
(on page 523).
To set limitations for login timeout and use of identical login names:
1. In the "Idle timeout period" field, type a value or click to select a time option. This setting determines how long users are permitted to stay idle before being forced to log out.

If you type a value, the value must be followed by a time unit, such as '4 min.' See
Time Units

Keep the idle timeout to 20 minutes or less if possible. This reduces the number of idle sessions connected, and the number of simultaneous commands sent to the PX3TS.
2. Select the "Prevent concurrent login with same username" checkbox if intending to prevent multiple persons from using the same login name simultaneously.
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 PX3TS device.
To configure password aging:
1. Select the 'Enabled' checkbox of Password Aging.
2. In the Password Aging Interval field, type a value or click to select a time option. This setting determines how often users are requested to change their passwords.

If you type a value, the value must be followed by a time unit, such as '10 d.' See
Time Units
3. Click Save.
Chapter 6: Using the Web Interface
To force users to create strong passwords:
1. Select the 'Enabled' checkbox of Strong Passwords to activate the strong password feature. The following are the default settings:
Minimum length
Maximum length
= 8 characters
= 32 characters
At least one lowercase character
At least one uppercase character
= Required
= Required
At least one numeric character
At least one special character
= Required
= Required
Number of forbidden previous passwords = 5
Note: The maximum password length accepted by the PX3TS 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 a security agreement when they log in to the PX3TS.
Users must accept the agreement, or they cannot log in.
An event notifying you if a user has accepted or declined the agreement can be generated. See
Default Log Messages
To enable the service agreement:
1. Click Device Settings > Security > Service Agreement.
2. Select the Enforce Restricted Service Agreement checkbox.
3. Edit or paste the content as needed.

A maximum of 10,000 characters can be entered.
4. Click Save.
257
258
Chapter 6: 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 in 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 and accept the Restricted Service Agreement" is displayed.
Setting the Date and Time
Set the internal clock on the PX3TS device manually, or link to a Network
Time Protocol (NTP) server.
Note: If you are using Sunbird's Power IQ to manage the PX3TS, you must configure Power IQ and the PX3TS to have the same date/time or
NTP settings.
To set the date and time:
1. Choose Device Settings > Date/Time.
2. Click the Time Zone field to select your time zone from the list.
3. If the daylight saving time applies to your time zone, verify the
Automatic Daylight Saving Time Adjustment checkbox is selected.

If the daylight saving time rules are not available for the selected time zone, the checkbox is not configurable.
4. Select the method for setting the date and time.
Customize the date and time

Select User Specified Time.
Chapter 6: Using the Web Interface

Type values in the Date field using the yyyy-mm-dd format, or click a date. For details, see
Calendar

Type values in the Time field using the hh:mm:ss format, or click values.
to select
to adjust

The time is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM or PM button.
Use the NTP server

Select "Synchronize with NTP Server."

There are two ways to assign the NTP servers:

To use the DHCP-assigned NTP servers, DO NOT enter any NTP servers for the
First and Second NTP 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.
The PX3TS follows the NTP server sanity check per the IETF RFC. If your
PX3TS has problems synchronizing with a Windows NTP server, see
Windows NTP Server Synchronization Solution
Calendar
The calendar icon in the Date field is a convenient tool to select a custom date. Click it and a calendar appears.
Button arrows
Function
Switch between months.
259
260
Chapter 6: Using the Web Interface
Button dates
(01-31)
Today
Clear
Close
Function
Click a date.
Select today.
Clear the entry, if any, in the Date field.
Close the calendar.
Windows NTP Server Synchronization Solution
The NTP client on the PX3TS follows the NTP RFC so the PX3TS rejects any NTP servers whose root dispersion is more than one second. An NTP server with a dispersion of more than one second is considered an inaccurate NTP server by the PX3TS.
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 PX3TS. 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.
2.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32T ime\Config
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)
3.
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.
LocalClockDispersion
must be set to 0.
Chapter 6: 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 a change in conditions. This event notification or reaction is an "event rule."
An event rule consists of two parts:
•
Event: This is the situation where the PX3TS or a device connected to it meets a certain condition. For example, the inlet's voltage reaches the warning level.
•
Action: This is the response to the event. For example, the PX3TS notifies the system administrator of the event via email.
If you want the PX3TS 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 PX3TS 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
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 PX3TS to react. d. In the Available Actions field, select the desired action(s) to respond to the selected event. e. Click Create.
For details, see
Built-in Rules and Rule Configuration
(on page
To create a scheduled action:
1. If the needed action is not available yet, create it by clicking
. See above.
261
262
Chapter 6: Using the Web Interface
Note: When creating scheduled actions, available actions are less than usual because it is meaningless to schedule certain actions like
"Alarm," "Log event message," "Send email," "Syslog message" and the like.
2. Click action.
to schedule the desired a. Assign a name to this scheduled action. b. Make sure the Enabled checkbox is selected, or the PX3TS 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
Built-in Rules and Rule Configuration
The PX3TS is shipped with four built-in event rules, which cannot be deleted. If the built-in event rules do not satisfy your needs, create new rules.
•
Built-in rules:
System Event Log Rule:
This causes ANY event occurred to the PX3TS to be recorded in the internal log. It is enabled by default.
Note: For the default log messages generated for each event, see
Default Log Messages
(on page 267).
•
•
•
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 PX3TS. It is disabled by default.
System Tamper Detection Alarmed:
This causes the PX3TS to send alarm notifications if a DX tamper sensor has been connected and the PX3TS detects that the tamper sensor enters the alarmed state. It is enabled by default.
System Tamper Detection Unavailable:
This causes the PX3TS to send alarm notifications if a DX tamper sensor was once connected or remains connected but then the
PX3TS does not detect the presence of the tamper sensor. It is enabled by default.
Chapter 6: Using the Web Interface
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.

<Any Numeric Sensor> means all numeric sensors of the PX3TS, including internal and environmental sensors. <Any Numeric
Sensor> is especially useful if you want to receive the notifications when any numeric sensor's readings pass through a specific threshold.
3. In this example, the Peripheral Device Slot is selected, which is related to the environmental sensor packages. Then a sensor ID field for this event type appears. Click this additional field to specify which sensor should be the subject of this event.
4. In this example, sensor ID 2 (Slot 2) 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.
5. In this example, Numeric Sensor is selected because we want to select numeric-sensor-related event(s). Then a field for numeric-sensor-related events appears. Click this field to select one of the numeric-sensor-related events from the list.
263
Chapter 6: Using the Web Interface
6. In this example, 'Above upper critical threshold' is selected because we want the PX3TS 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.
264
7. Select the desired radio button to finish the event configuration.
Refer to the following table for different types of radio buttons.

If needed, you may refer to event rule examples in the section titled
Sample Event Rules
8. To select any action(s), select them one by one from the Available
Actions list.

To select all available actions, click Select All.
9. To remove any action(s) from the Selected Actions field, click that action's .

To remove all actions, click Deselect All.
Chapter 6: Using the Web Interface
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
Numeric sensor threshold-crossing events, or the occurrence of the selected event -- true or false
Radio buttons
Available radio buttons include "Asserted,"
"Deasserted" and "Both."

Asserted: The PX3TS takes the action only when the selected event occurs. That is, the status of the event transits from FALSE to
TRUE.

Deasserted: The PX3TS takes the action only when the selected event disappears or stops. That is, the status of the selected event transits from TRUE to FALSE.

Both: The PX3TS takes the action both when the event occurs (asserts) and when the event stops/disappears (deasserts).
State sensor state change
Available radio buttons include
"Alarmed/Open/On," "No longer alarmed/Closed/Off" and "Both."

Alarmed/Open/On: The PX3TS takes the action only when the chosen sensor enters the alarmed, open or on state.

No longer alarmed/Closed/Off: The PX3TS takes the action only when the chosen sensor returns to the normal, closed, or off state.

Both: The PX3TS takes the action whenever the chosen sensor switches its state.
Sensor availability Available radio buttons include "Unavailable,"
"Available" and "Both."

Unavailable: The PX3TS takes the action only when the chosen sensor is NOT detected and becomes unavailable.

Available: The PX3TS takes the action only when the chosen sensor is detected and becomes available.

Both: The PX3TS takes the action both when the chosen sensor becomes unavailable or available.
265
266
Chapter 6: Using the Web Interface
Event types
Network interface link state
Function enabled or disabled
Restricted service agreement
Server monitoring event
Radio buttons

Link state is up: The PX3TS takes the action only when the network link state changes from down to up.

Link state is down: The PX3TS takes the action only when the network link state changes from up to down.

Both: The PX3TS takes the action whenever the network link state changes.

Enabled: The PX3TS takes the action only when the chosen function is enabled.

Disabled: The PX3TS takes the action only when the chosen function is disabled.

Both: The PX3TS takes the action when the chosen function is either enabled or disabled.

Accepted: The PX3TS takes the action only when the specified user accepts the restricted service agreement.

Declined: The PX3TS takes the action only when the specified user rejects the restricted service agreement.

Both: The PX3TS takes the action both when the specified user accepts or rejects the restricted service agreement.

Monitoring started: The PX3TS takes the action only when the monitoring of any specified server starts.

Monitoring stopped: The PX3TS takes the action only when the monitoring of any specified server stops.

Both: The PX3TS takes the action when the monitoring of any specified server starts or stops.
Chapter 6: Using the Web Interface
Event types Radio buttons
Server reachability 
Unreachable: The PX3TS takes the action only when any specified server becomes inaccessible.

Reachable: The PX3TS takes the action only when any specified server becomes accessible.

Both: The PX3TS takes the action when any specified server becomes either inaccessible or accessible.
Device connection or disconnection, such as a USB-cascaded slave device

Connected: The PX3TS takes the action only when the selected device is physically connected to it.

Disconnected: The PX3TS takes the action only when the selected device is physically disconnected from it.

Both: The PX3TS takes the action both when the selected device is physically connected to it and when it is disconnected.
+12V Supply Status Available radio buttons include "Fault," "Ok" and "Both."

Fault: The PX3TS takes the action only when the selected 12V power supply to the controller enters the fault state.

Ok: The PX3TS takes the action only when when the selected 12V power supply to the controller enters the OK state.

Both: The PX3TS takes the action whenever the selected 12 power supply's status changes.
Default Log Messages
Following are default log messages recorded internally and emailed to specified recipients when PX3TS events occur (are TRUE) or, in some cases, stop or become unavailable (are FALSE). See
Send Email
(on
page 287) for information configuring email messages to be sent when
specified events occur.
267
268
Chapter 6: Using the Web Interface
Event/context
Asset Management > State
Asset Management > Rack
Unit > * > Tag Connected
Asset Management > Rack
Unit > * > Blade Extension
Connected
Default message when the event =
TRUE
State of asset strip [STRIPID]
('[STRIPNAME]') changed to '[STATE]'.
Asset tag with ID '[TAGID]' connected at rack unit [RACKUNIT], slot
[RACKSLOT] of asset strip [STRIPID]
('[STRIPNAME]').
Blade extension with ID '[TAGID]' connected at rack unit [RACKUNIT] of asset strip [STRIPID] ('[STRIPNAME]').
Default message when the event =
FALSE
Asset tag with ID '[TAGID]' disconnected at rack unit
[RACKUNIT], slot [RACKSLOT] of asset strip [STRIPID]
('[STRIPNAME]').
Blade extension with ID '[TAGID]' disconnected at rack unit
[RACKUNIT] of asset strip [STRIPID]
('[STRIPNAME]').
Asset Management > Firmware
Update
Asset Management > Device
Config Changed
Asset Management > Rack Unit
Config Changed
Asset Management > Blade
Extension Overflow
Asset Management >
Composite Asset Strip
Composition Changed
Card Reader Management >
Card inserted
Card Reader Management >
Card Reader attached
Firmware update for asset strip
[STRIPID] ('[STRIPNAME]'): status changed to '[STATE]'.
Config parameter '[PARAMETER]' of asset strip [STRIPID] ('[STRIPNAME]') changed to '[VALUE]' by user
'[USERNAME]'.
Config of rack unit [RACKUNIT] of asset strip [STRIPID] ('[STRIPNAME]') changed by user '[USERNAME]' to:
LED Operation Mode '[LEDOPMODE]',
LED Color '[LEDCOLOR]', LED Mode
'[LEDMODE]'
Blade extension overflow occurred on strip [STRIPID] ('[STRIPNAME]').
Composition changed on composite asset strip [STRIPID] ('[STRIPNAME]').
Card Reader with id
'[CARDREADERID]' connected.
Card Reader with id
'[CARDREADERID]' disconnected.
Blade extension overflow cleared for strip [STRIPID] ('[STRIPNAME]').
Card Reader Management >
Card Reader detached
Card of type '[SMARTCARDTYPE]' with
ID '[SMARTCARDID]' inserted.
Chapter 6: Using the Web Interface
Event/context
Card Reader Management >
Card removed
Default message when the event =
TRUE
Card of type '[SMARTCARDTYPE]' with
ID '[SMARTCARDID]' removed.
Device > System started
Device > System reset
Device > Firmware validation failed
Device > Firmware update started
Device > Firmware update completed
System started.
System reset performed by user
'[USERNAME]' from host '[USERIP]'.
Firmware validation failed by user
'[USERNAME]' from host '[USERIP]'.
Firmware upgrade started from version '[OLDVERSION]' to version
'[VERSION]' by user '[USERNAME]' from host '[USERIP]'.
Firmware upgraded successfully from version '[OLDVERSION]' to version
'[VERSION]' by user '[USERNAME]' from host '[USERIP]'.
Device > Firmware update failed
Device > Device identification changed
Firmware upgrade failed from version
'[OLDVERSION]' to version '[VERSION]' by user '[USERNAME]' from host
'[USERIP]'.
Config parameter '[PARAMETER]' changed to '[VALUE]' by user
'[USERNAME]' from host '[USERIP]'.
Device > Device settings saved Device settings saved from host
'[USERIP]'
Device > Device settings restored
Device > Data push failed
Device settings restored from host
'[USERIP]'.
Data push to URL [DATAPUSH_URL] failed. [ERRORDESC].
Device > Event log cleared
Device > Bulk configuration saved
Device > Bulk configuration copied
Event log cleared by user
'[USERNAME]' from host '[USERIP]'.
Bulk configuration saved from host
'[USERIP]'.
Bulk configuration copied from host
'[USERIP]'.
Default message when the event =
FALSE
269
270
Chapter 6: Using the Web Interface
Event/context
Device > Network interface link state is up
Device > Peripheral Device
Firmware Update
Device > Sending SMTP message failed
Device > Sending SNMP inform failed or no response
Device > Sending Syslog message failed
Default message when the event =
TRUE
The [IFNAME] network interface link is now up.
Default message when the event =
FALSE
The [IFNAME] network interface link is now down.
Firmware update for peripheral device
[EXTSENSORSERIAL] from
[OLDVERSION] to [VERSION]
[SENSORSTATENAME].
Sending SMTP message to
'[RECIPIENTS]' using server
'[SERVER]' failed.
Sending SNMP inform to manager
[SNMPMANAGER]:[SNMPMANAGERP
ORT] failed or no response.
[ERRORDESC].
Sending Syslog message to server
[SYSLOGSERVER]:[SYSLOGPORT]
([SYSLOGTRANSPORTPROTO]) failed.
[ERRORDESC].
Device > Sending SMS message failed
Sending SMS message to
'[PHONENUMBER]' failed.
Device > An LDAP error occurred
Device > An Radius error occurred
An LDAP error occurred:
[LDAPERRORDESC].
An Radius error occurred:
[RADIUSERRORDESC].
Device > Unknown peripheral device attached
An unknown peripheral device with rom code '[ROMCODE]' was attached at position '[PERIPHDEVPOSITION]'.
Device > USB slave connected USB slave connected.
Device > WLAN authentication over TLS with incorrect system clock
Energywise > Enabled
Established connection to wireless network '[SSID]' via Access Point with
BSSID '[BSSID]' using '[AUTHPROTO]' authentication with incorrrect system clock.
User '[USERNAME]' from host
'[USERIP]' enabled EnergyWise.
USB slave disconnected.
User '[USERNAME]' from host
'[USERIP]' disabled EnergyWise.
Chapter 6: Using the Web Interface
Event/context
Peripheral Device Slot > * >
Numeric Sensor > Unavailable
Peripheral Device Slot > * >
Numeric Sensor > Above upper critical threshold
Peripheral Device Slot > * >
Numeric Sensor > Above upper warning threshold
Peripheral Device Slot > * >
Numeric Sensor > Below lower warning threshold
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' asserted 'below lower warning' at [READING].
Peripheral Device Slot > * >
Numeric Sensor > Below lower critical threshold
Peripheral Device Slot > * >
State Sensor/Actuator >
Unavailable
Peripheral Device Slot > * >
State Sensor/Actuator >
Alarmed/Open/On
Inlet > * > Enabled
Inlet > * > Sensor > * >
Unavailable
Inlet > * > Sensor > * > Above upper critical threshold
Inlet > * > Sensor > * > Above
Default message when the event =
TRUE
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' unavailable.
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' asserted 'above upper critical' at [READING].
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' asserted 'above upper warning' at [READING].
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' asserted 'below lower critical' at [READING].
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' unavailable.
Peripheral device
'[EXTSENSORNAME]' in slot
[EXTSENSORSLOT] is
[SENSORSTATENAME].
Inlet '[INLET]' has been enabled by user '[USERNAME]' from host
'[USERIP]'.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' unavailable.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' asserted 'above upper critical'.
Sensor '[INLETSENSOR]' on inlet
Default message when the event =
FALSE
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' available.
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' deasserted
'above upper critical' at [READING].
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' deasserted
'above upper warning' at
[READING].
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' deasserted
'below lower warning' at
[READING].
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' deasserted
'below lower critical' at [READING].
Peripheral device
'[EXTSENSORNAME]' in slot
'[EXTSENSORSLOT]' available.
Peripheral device
'[EXTSENSORNAME]' in slot
[EXTSENSORSLOT] is
[SENSORSTATENAME].
Inlet '[INLET]' has been disabled by user '[USERNAME]' from host
'[USERIP]'.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' available.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' deasserted 'above upper critical'.
Sensor '[INLETSENSOR]' on inlet
271
272
Chapter 6: Using the Web Interface
Event/context upper warning threshold
Inlet > * > Sensor > * > Below lower warning threshold
Inlet > * > Sensor > * > Below lower critical threshold
Inlet > * > Sensor > Active
Energy > Reset
Modem > Dial-in link established
Modem > Modem attached
Default message when the event =
TRUE
'[INLET]' asserted 'above upper warning'.
Default message when the event =
FALSE
'[INLET]' deasserted 'above upper warning'.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' asserted 'below lower warning'.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' asserted 'below lower critical'.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' deasserted 'below lower warning'.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' deasserted 'below lower critical'.
Sensor '[INLETSENSOR]' on inlet
'[INLET]' has been reset by user
'[USERNAME]' from host '[USERIP]'.
An incoming call from caller
'[CALLERID]' was received.
A [MODEMTYPE] modem was attached.
The incoming call from caller
'[CALLERID]' was disconnected:
[CALLENDREASON].
Modem > Modem detached A [MODEMTYPE] modem was removed.
Outlet > * > Power control >
Powered on
Outlet > * > Power control >
Powered off
Outlet > * > Power control >
Power cycled
Outlet > * > Sensor > * >
Unavailable
Outlet > * > Sensor > * > Above upper critical threshold
Outlet > * > Sensor > * > Above upper warning threshold
Outlet '[OUTLET]' has been powered on by user '[USERNAME]' from host
'[USERIP]'.
Outlet '[OUTLET]' has been powered off by user '[USERNAME]' from host
'[USERIP]'.
Outlet '[OUTLET]' power cycle initiated by user '[USERNAME]' from host
'[USERIP]'.
Sensor '[OUTLETSENSOR]' on outlet
'[OUTLET]' unavailable.
Sensor '[OUTLETSENSOR]' on outlet
'[OUTLET]' asserted 'above upper critical'.
Sensor '[OUTLETSENSOR]' on outlet
'[OUTLET]' asserted 'above upper warning'.
Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' available.
Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'above upper critical'.
Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'above upper warning'.
Chapter 6: Using the Web Interface
Event/context
Outlet > * > Sensor > * > Below lower warning threshold
Outlet > * > Sensor > * > Below lower critical threshold
Outlet > * > Sensor > Active
Energy > Reset
Outlet > * > Sensor > Outlet
State > On
Outlet > * > Pole > * > Sensor >
Unavailable
Outlet > * > Pole > * > Sensor >
Above upper critical threshold
Outlet > * > Pole > * > Sensor >
Above upper warning threshold
Outlet > * > Pole > * > Sensor >
Below lower warning threshold
Outlet > * > Pole > * > Sensor >
Below lower critical threshold
Default message when the event =
TRUE
Sensor '[OUTLETSENSOR]' on outlet
'[OUTLET]' asserted 'below lower warning'.
Sensor '[OUTLETSENSOR]' on outlet
'[OUTLET]' asserted 'below lower critical'.
Sensor '[OUTLETSENSOR]' on outlet
'[OUTLET]' has been reset by user
'[USERNAME]' from host '[USERIP]'.
Default message when the event =
FALSE
Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'below lower warning'.
Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' deasserted 'below lower critical'.
Outlet '[OUTLET]' state changed to on. Outlet '[OUTLET]' state changed to off.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet '[OUTLET]' unavailable.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet
'[OUTLET]' available.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'above upper critical'.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'above upper warning'.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet
'[OUTLET]' deasserted 'above upper critical'.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet
'[OUTLET]' deasserted 'above upper warning'.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'below lower warning'.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet '[OUTLET]' asserted 'below lower critical'.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet
'[OUTLET]' deasserted 'below lower warning'.
Sensor '[POLESENSOR]' on pole
'[OUTLETPOLE]' of outlet
'[OUTLET]' deasserted 'below lower critical'.
Overcurrent Protector > * >
Sensor > * > Unavailable
Overcurrent Protector > * >
Sensor > * > Above upper critical threshold
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' unavailable.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' available.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'above upper critical'.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'above upper critical'.
273
274
Chapter 6: Using the Web Interface
Event/context
Overcurrent Protector > * >
Sensor > * > Above upper warning threshold
Overcurrent Protector > * >
Sensor > * > Below lower warning threshold
Overcurrent Protector > * >
Sensor > * > Below lower critical threshold
Overcurrent Protector > * >
Sensor > Trip > Open
Default message when the event =
TRUE
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'above upper warning'.
Default message when the event =
FALSE
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'above upper warning'.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'below lower warning'.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' asserted 'below lower critical'.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'below lower warning'.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' deasserted 'below lower critical'.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' is open.
Sensor '[OCPSENSOR]' on overcurrent protector '[OCP]' is closed.
PDU > Load Shedding > Started PX placed in Load Shedding Mode by user '[USERNAME]' from host
'[USERIP]'.
PDU > Sensor > +12V Supply
Status > fault
PDU > Sensor > +12V Supply
Status > Unavailable
PDU > Sensor > * > Reset
Global sensor 'powerSupplyStatus' entered fault state.
Global sensor 'powerSupplyStatus' unavailable.
Global sensor '[PDUSENSOR]' has been reset by user '[USERNAME]' from host '[USERIP]'.
PX removed from Load Shedding
Mode by user '[USERNAME]' from host '[USERIP]'.
Global sensor 'powerSupplyStatus' entered normal state.
Global sensor 'powerSupplyStatus' available.
PDU > Sensor > * > Unavailable Global sensor '[PDUSENSOR]'
PDU > Sensor > * > Above upper critical threshold
PDU > Sensor > * > Above upper warning threshold
PDU > Sensor > * > Below lower warning threshold
PDU > Sensor > * > Below lower critical threshold unavailable.
Global sensor '[PDUSENSOR]' asserted 'above upper critical'.
Global sensor '[PDUSENSOR]' asserted 'above upper warning'.
Global sensor '[PDUSENSOR]' asserted 'below lower warning'.
Global sensor '[PDUSENSOR]' asserted 'below lower critical'.
Server Monitoring > * > Error Error monitoring server
'[MONITOREDHOST]': [ERRORDESC]
Server Monitoring > * > Server '[SERVER]' is now being
Global sensor '[PDUSENSOR]' available.
Global sensor '[PDUSENSOR]' deasserted 'above upper critical'.
Global sensor '[PDUSENSOR]' deasserted 'above upper warning'.
Global sensor '[PDUSENSOR]' deasserted 'below lower warning'.
Global sensor '[PDUSENSOR]' deasserted 'below lower critical'.
Server '[SERVER]' is no longer
Chapter 6: Using the Web Interface
Event/context
Monitored
Server Monitoring > * >
Unreachable
Server Monitoring > * >
Unrecoverable
Transfer Switch > Transfer
Switch TS1 > Active Inlet
Transfer Switch > Transfer
Switch TS1 > Sensor > Inlet
Phase Sync Angle > Above upper critical
Transfer Switch > Transfer
Switch TS1 > Sensor > Inlet
Phase Sync Angle > Above upper warning
Transfer Switch > Transfer
Switch TS1 > Sensor > Inlet
Phase Sync Angle > Below lower warning
Transfer Switch > Transfer
Switch TS1 > Sensor > Inlet
Phase Sync Angle > Below lower critical
Transfer Switch > Transfer
Switch TS1 > Sensor >
Operational State > Normal
Default message when the event =
TRUE monitored.
Server '[SERVER]' is unreachable.
Default message when the event =
FALSE being monitored.
Server '[SERVER]' is reachable.
Connection to server
'[MONITOREDHOST]' could not be restored.
Active inlet on transfer switch '[NAME]' changed to '[INLET]' due to [REASON].
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' asserted
'above upper critical' at [READING].
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' asserted
'above upper warning' at [READING].
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' asserted
'below lower warning' at [READING].
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' deasserted 'above upper critical' at
[READING].
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' deasserted 'above upper warning' at [READING].
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' deasserted 'below lower warning' at [READING].
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' asserted
'below lower critical' at [READING].
Transfer Switch > Transfer
Switch TS1 > Sensor > Inlet
Phase Sync Angle > Unavailable
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' unavailable.
Operational state of transfer switch
'[NAME]' is now normal.
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' deasserted 'below lower critical' at
[READING].
Sensor 'Inlet Phase Sync Angle' on transfer switch '[NAME]' available.
Operational state of transfer switch
'[NAME]' is no longer normal.
Transfer Switch > Transfer
Switch TS1 > Sensor >
Operational State > Standby
Transfer Switch > Transfer
Switch TS1 > Sensor >
Operational State >
Non-redundant
Operational state of transfer switch
'[NAME]' is now standby.
Operational state of transfer switch
'[NAME]' is now non-redundant.
Operational state of transfer switch
'[NAME]' is no longer standby.
Operational state of transfer switch
'[NAME]' is no longer non-redundant.
275
276
Chapter 6: Using the Web Interface
Event/context
Transfer Switch > Transfer
Switch TS1 > Sensor >
Operational State > Off
Transfer Switch > Transfer
Switch TS1 > Sensor >
Operational State > Unavailable
Transfer Switch > Transfer
Switch TS1 > Sensor >
Overload > Fault
Default message when the event =
TRUE
Operational state of transfer switch
'[NAME]' is now off.
Operational state of transfer switch
'[NAME]' is now unavailable.
Sensor 'Overload' on transfer switch
'[NAME]' is fault.
Default message when the event =
FALSE
Operational state of transfer switch
'[NAME]' is no longer off.
Operational state of transfer switch
'[NAME]' is no longer unavailable.
Sensor 'Overload' on transfer switch '[NAME]' is ok.
Transfer Switch > Transfer
Switch TS1 > Sensor >
Overload > Unavailable
Transfer Switch > Transfer
Switch TS1 > Sensor > Phase
Sync > Out of Sync
Sensor 'Overload' on transfer switch
'[NAME]' is unavailable.
Sensor 'Phase Sync' on transfer switch
'[NAME]' is out of sync.
Sensor 'Overload' on transfer switch '[NAME]' is available.
Sensor 'Phase Sync' on transfer switch '[NAME]' is in sync.
Transfer Switch > Transfer
Switch TS1 > Sensor > Phase
Sync > Unavailable
Transfer Switch > Transfer
Switch TS1 > Sensor > Switch
Fault > Fault
Sensor 'Phase Sync' on transfer switch
'[NAME]' is unavailable.
Sensor 'Switch Fault' on transfer switch '[NAME]' is [INLET] open fault.
- OR -
Sensor 'Switch Fault' on transfer switch '[NAME]' is [INLET] short fault.
Sensor 'Switch Fault' on transfer switch '[NAME]' is unavailable.
Transfer Switch > Transfer
Switch TS1 > Sensor > Switch
Fault > Unavailable
User Activity > * > User logon state
User Activity > * >
Authentication failure
User '[USERNAME]' from host
'[USERIP]' logged in.
Authentication failed for user
'[USERNAME]' from host '[USERIP]'.
User Activity > * > User accepted the Restricted Service
Agreement
User '[USERNAME]' from host
'[USERIP]" accepted the Restricted
Service Agreement.
Sensor 'Phase Sync' on transfer switch '[NAME]' is available.
Sensor 'Switch Fault' on transfer switch '[NAME]' is ok.
Sensor 'Switch Fault' on transfer switch '[NAME]' is available.
User '[USERNAME]' from host
'[USERIP]" declined the Restricted
Service Agreement.
User Activity > * > User blocked User '[USERNAME]' from host
'[USERIP]' was blocked.
User Activity > * > Session Session of user '[USERNAME]' from
User '[USERNAME]' from host
'[USERIP]' logged out.
Chapter 6: Using the Web Interface
Event/context timeout
User Administration > User added
User Administration > User modified
User Administration > User deleted
User Administration >
Password changed
User Administration >
Password settings changed
User Administration > Role added
User Administration > Role modified
User Administration > Role deleted
Webcam Management >
Webcam attached
Webcam Management >
Webcam detached
Webcam Management >
Webcam settings changed
LHX/SHX > Connected
LHX/SHX > Operational State
LHX/SHX > Sensor >
Unavailable
Default message when the event =
TRUE host '[USERIP]' timed out.
User '[TARGETUSER]' added by user
'[USERNAME]' from host '[USERIP]'.
User '[TARGETUSER]' modified by user
'[USERNAME]' from host '[USERIP]'.
User '[TARGETUSER]' deleted by user
'[USERNAME]' from host '[USERIP]'.
Password of user '[TARGETUSER]' changed by user '[USERNAME]' from host '[USERIP]'.
Default message when the event =
FALSE
Password settings changed by user
'[USERNAME]' from host '[USERIP]'.
Role '[TARGETROLE]' added by user
'[USERNAME]' from host '[USERIP]'.
Role '[TARGETROLE]' modified by user
'[USERNAME]' from host '[USERIP]'.
Role '[TARGETROLE]' deleted by user
'[USERNAME]' from host '[USERIP]'.
Webcam '[WEBCAMNAME]'
('[WEBCAMUVCID]') added to port
'[WEBCAMUSBPORT]'.
Webcam '[WEBCAMNAME]'
('[WEBCAMUVCID]') removed from port
'[WEBCAMUSBPORT]'.
Webcam '[WEBCAMNAME]' settings changed by user '[USERNAME]'.
LHX has been connected to
[PORTTYPE] port [PORTID].
LHX connected to [PORTTYPE] port
[PORTID] has been switched on.
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' unavailable.
LHX has been disconnected from
[PORTTYPE] port [PORTID].
LHX connected to [PORTTYPE] port
[PORTID] has been switched off.
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' available.
277
278
Chapter 6: Using the Web Interface
Event/context
LHX/SHX > Sensor > Above upper critical threshold
LHX/SHX > Sensor > Above upper warning threshold
LHX/SHX > Sensor > Below lower warning threshold
LHX/SHX > Sensor > Below lower critical threshold
LHX/SHX > Base Electronics
Failure
LHX/SHX > Condenser Pump
Failure
LHX/SHX > Emergency Cooling Emergency cooling on LHX at
[PORTTYPE] port '[PORTID]' was
LHX/SHX > Maximum cooling request
LHX/SHX > Parameter Data
Loss
LHX/SHX > ST-Bus
Communication Error
LHX/SHX > Collective fault
LHX/SHX > Door Contact
Default message when the event =
TRUE
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' asserted
'above upper critical'.
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' asserted
'above upper warning'.
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' asserted
'below lower warning'.
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' asserted
'below lower critical'.
The base electronics on LHX at
[PORTTYPE] port '[PORTID]' failed.
The condenser pump on LHX at
[PORTTYPE] port '[PORTID]' failed. activated.
Maximum cooling was requested for
LHX at [PORTTYPE] port '[PORTID]'.
Data loss in parameter memory was detected on LHX at [PORTTYPE] port
'[PORTID]'.
An ST-Bus communication error was detected on LHX at [PORTTYPE] port
'[PORTID]'.
A collective fault occurred on LHX at
[PORTTYPE] port '[PORTID]'.
The door of LHX at [PORTTYPE] port
'[PORTID]' was opened.
Default message when the event =
FALSE
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' deasserted 'above upper critical'.
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' deasserted 'above upper warning'.
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' deasserted 'below lower warning'.
Sensor '[LHXSENSORID]' on LHX at
[PORTTYPE] port '[PORTID]' deasserted 'below lower critical'.
The condenser pump on LHX at
[PORTTYPE] port '[PORTID]' is back to normal.
Emergency cooling on LHX at
[PORTTYPE] port '[PORTID]' was deactivated.
Maximum cooling is not any more requested for LHX at [PORTTYPE] port '[PORTID]'.
The door of LHX at [PORTTYPE] port
'[PORTID]' was closed.
Chapter 6: Using the Web Interface
Event/context
LHX/SHX > Sensor Failure
LHX/SHX > Fan Failure
LHX/SHX > Power Supply
Failure
Default message when the event =
TRUE
A sensor failure (broken or short circuit) occurred on LHX at
[PORTTYPE] port '[PORTID]' at sensor
'[LHXSENSORID]'.
A fan motor failure occurred on LHX at
[PORTTYPE] port '[PORTID]' at fan
'[LHXFANID]'.
Default message when the event =
FALSE
A power supply failure occurred on
LHX at [PORTTYPE] port '[PORTID]' at power supply '[LHXPOWERSUPPLYID]'.
LHX/SHX > Threshold Air Inlet The air inlet temperature threshold on
LHX at [PORTTYPE] port '[PORTID]' was crossed.
LHX/SHX > Threshold Air Outlet The air outlet temperature threshold on LHX at [PORTTYPE] port '[PORTID]' was crossed.
LHX/SHX > Threshold Water
Inlet
LHX/SHX > Threshold Water
Outlet
LHX/SHX > Voltage Low
The water inlet temperature threshold on LHX at [PORTTYPE] port '[PORTID]' was crossed.
The water outlet temperature threshold on LHX at [PORTTYPE] port
'[PORTID]' was crossed.
The supply voltage on LHX at
[PORTTYPE] port '[PORTID]' is low.
The air inlet temperature on LHX at
[PORTTYPE] port '[PORTID]' is within thresholds.
The air outlet temperature on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
The water inlet temperature on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
The water outlet temperature on
LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
The supply voltage on LHX at
[PORTTYPE] port '[PORTID]' is back to normal.
The humidity on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
LHX/SHX > Threshold Humidity The humidity threshold on LHX at
[PORTTYPE] port '[PORTID]' was crossed.
LHX/SHX > External Water
Cooling Failure
An external water cooling failure occurred on 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.
279
280
Chapter 6: Using the Web Interface
Available Actions
The PX3TS comes with three built-in actions, which cannot be deleted.
You can create additional actions for responding to different events.
•
Built-in actions:
System Event Log Action:
•
This action records the selected event in the internal log when the event occurs.
System SNMP Notification Action:
This action sends SNMP notifications to one or multiple IP addresses after the selected event occurs.
•
Note: No IP addresses are specified for this notification action by default so you must enter IP addresses before applying this action to any event rule. See
Editing or Deleting a Rule/Action
(on page 304).
Any changes made to the 'SNMP Notifications' section on the SNMP page will update the settings of the System SNMP Notification Action, and vice versa. See
Configuring SNMP Settings
(on page 230).
System Tamper Alarm:
This action causes the PX3TS to show the alarm for the DX tamper sensor, if any, on the Dashboard page until a person acknowledges it.
By default, this action has been assigned to the built-in tamper detection event rules. For information on acknowledging an alarm, see
Dashboard - Alarms
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.
.
Note: The "Change load shedding state" and "Switch outlets" options are only available for outlet-switching capable models.
Action
Alarm
Change load shedding state
Function
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
Enters or quits the load shedding mode. See
Change Load Shedding State
Chapter 6: Using the Web Interface
Action
Execute an action group
External beeper
Function
Creates a group of actions comprising existing actions. See
Action Group
Enables or disables the connected external beeper, or causes it to enter an alarm cycle.
See
External Beeper
Internal beeper Turns on or off the internal beeper. See
Internal Beeper
Log event message Records the selected events in the internal log.
See
Log an Event Message
Push out sensor readings
Record snapshots to webcam storage
Request LHX/SHX maximum cooling
Send email
Sends internal sensor log, environmental sensor log or asset management strip data to a remote server using HTTP POST requests. See
Push Out Sensor Readings
Makes a connected webcam start or stop taking snapshots. See
Record Snapshots to
Webcam Storage
Applies the maximum cooling to the LHX/SHX device. See
Request LHX/SHX Maximum
Cooling
This option is available only when the Schroff
LHX/SHX support has been enabled.
Emails a textual message. See
Send Email
(on
Send sensor report Reports the readings or status of the selected sensors, including internal or external sensors. See
Send Sensor Report
(on page
Send SMS message Sends a message to a mobile phone. See
SMS Message
Send
Send snapshots via email
Send SNMP notification
Emails the snapshots captured by a connected
Logitech
®
webcam (if available). See
Snapshots via Email
Send
Sends SNMP traps or informs to one or multiple SNMP destinations. See
Send an
SNMP Notification
281
282
Chapter 6: Using the Web Interface
Action Function
Start/stop Lua script If you are a developer who can create a Lua script, you can upload it to the PX3TS, and have the PX3TS automatically perform or stop the script in response to an event. See
Start or
Stop a Lua Script
Switch LHX/SHX Switches on or off the LHX/SHX device. See
Switch LHX/SHX
This option is available only when the Schroff
LHX/SHX support has been enabled.
Switch outlets
Switch peripheral actuator
Syslog message
Switches on, off or cycles the power to the specified outlet(s). See
Switch Outlets
(on
Switches on or off the mechanism or system connected to the specified actuator. See
Switch Peripheral Actuator
Makes the PX3TS automatically forward event messages to the specified syslog server. See
Syslog Message
4. Enter the information as needed and click Create.
5. Then you can assign the newly-created action to an event rule or schedule it. See
Event Rules and Actions
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 PX3TS resends or regenerates an alert notification regularly until the alert is acknowledged or the maximum number of alert notifications is sent.
For information on acknowledging an alert, see
Dashboard
(on page
Operation:
1. Choose Device Settings > Event Rules >
2. Select Alarm from the Action list.
.
3. In the Alarm Notifications list box, specify one or multiple ways to issue the alert notifications. Available methods vary, depending on how many notification-based actions have been created.
Notification-based action types include:
Chapter 6: Using the Web Interface

External beeper

Syslog message

Send email

Send SMS message

Internal beeper
If no appropriate actions are available, create them first. a. To select any methods, select them one by one in the Available field.
To add all available methods, simply click Select All. b. To delete any methods, click a method's in the Selected field.
To remove all methods, simply click Deselect All.
4. To enable the notification-resending feature, select the "Enable
Re-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 the alert notification is resent. Values range from 1 to infinite.
7. (Optional) You can instruct the PX3TS to send the acknowledgment notification after the alarm is acknowledged in the Acknowledgment
Notifications field. Available methods are identical to those for generating alarm notifications. a. In the Available field, select desired methods one by one, or click
Select All. See step 3 for details. b. In the Selected field, click any method's to remove unnecessary ones, or click Deselect All.
Action Group
You can create an action group that performs up to 32 actions. After creating such an action group, you can easily assign this set of actions to any event rule rather than selecting all needed actions one by one per rule.
If the needed action is not available yet, create it first. See
Available
Actions
Operation:
1. Choose Device Settings > Event Rules >
2. Select "Execute an action group" from the Action list.
.
283
284
Chapter 6: Using the Web Interface
3. To select any action(s), select them one by one from the Available
Actions list.

To select all available actions, click Select All.
4. To remove any action(s) from the Selected Actions field, click that action's .

To remove all actions, click Deselect All.
Change Load Shedding State
The "Change load shedding state" action is available only when your
PX3TS is able to control outlet power. Use this action to activate or deactivate the load shedding mode for responding to a specific event. For additional informtion, see
Load Shedding Mode
Operation:
1. Choose Device Settings > Event Rules >
2. Select "Change load shedding state" from the Action list.
.
3. In the Operation field, select either one below:

Start Load Shedding: Enters the load shedding mode when the specified event occurs.

Stop Load Shedding: Quits the load shedding mode when the specified event occurs.
External Beeper
If an external beeper is connected to the PX3TS, the PX3TS 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 is connected. This port is the FEATURE port.
4. In the Beeper Action field, select an action for the external beeper to carry out.

Alarm: Causes the external beeper to sound an alarm cycle every
20 seconds - stays on for 0.7 seconds and then off for 19.3 seconds.

On: Turns on the external beeper so that it buzzes continuously.

Off: Turns off the external beeper so that it stops buzzing.
Chapter 6: Using the Web Interface
Warning: If you create an event rule for the external beeper but disconnect it when an event causes it to beep, the beeper no longer beeps after it is re-connected even though the event triggering the beeping action remains asserted.
Internal Beeper
You can have the built-in beeper of the PX3TS turned on or off when a certain event occurs.
Operation:
1. Choose Device Settings > Event Rules >
2. Select "Internal beeper" from the Action list.
3. Select an option from the Operation field.
.

Turn Beeper On: Turns on the internal beeper to make it buzz.

Turn Beeper Off: Turns off the internal beeper to make it stop buzzing.
Log an Event Message
The option "Log event message" records the selected events in the internal log.
The default log message generated for each type of event is available in the section titled
Default Log Messages
Push Out Sensor Readings
You can configure the PX3TS to push sensor log to a remote server after a certain event occurs, including logs of internal sensors, environmental sensors and actuators.
If you have connected Raritan's asset strips to the PX3TS, you can also configure the PX3TS to push the data to a server.
Before creating this action, make sure that you have properly defined the destination servers and the data to be sent on the Data Push page. See
Configuring Data Push Settings
Tip: To send the data at a regular interval, schedule this action. See
Scheduling an Action
(on page 297). 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 > .
285
286
Chapter 6: Using the Web Interface
2. Select "Push out sensor readings" from the Action list.
3. Select a server or host which receives the asset strip data or sensor log in the Destination field.

If the desired destination is not available yet, go to the Data Push page to specify it.
Record Snapshots to Webcam Storage
This option allows you to define an action that starts or stops a specific webcam from taking snapshots.
Per default the snapshots are stored on the PX3TS. You can specify a remote server to store snapshots. See
Viewing Saved Snapshots and
Managing Storage
Operation:
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."
If "Start recording" is selected, adjust the values of the following:

Number of Snapshots - the number of snapshots to be taken when the event occurs.
The maximum amount of snapshots that can be stored on the
PX3TS is 10. If you set it for a number greater than 10 and the storage location is on the PX3TS, 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.
Chapter 6: Using the Web Interface
Request LHX/SHX Maximum Cooling
If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will be available. See
Miscellaneous
The "Request LHX/SHX Maximum Cooling" action applies the maximum cooling to the SHX-30 device only. The LHX-20 and LHX-40 devices do not support this feature.
In the maximum cooling mode, an SHX-30 device runs at 100% fan speed and the cold water valve is open 100%.
Operation:
1. Choose Device Settings > Event Rules > .
2. Select "Request LHX/SHX Maximum Cooling" from the Action list.
3. In the Available LHX/SHX field, select the desired SHX-30 device one by one, or click Select All.
4. To remove any SHX-30 device from the Selected LHX/SHX field, click that device's or click Deselect All.
Send Email
You can configure emails to be sent when an event occurs and can customize the message.
Messages consist of a combination of free text and PX3TS placeholders.
The placeholders represent information is pulled from the PX3TS and inserted into the message.
For example:
[USERNAME] logged into the device on [TIMESTAMP] translates to
JQPublic logged into the device on 2012-January-30 21:00
For a list and definition of available variables, see
Email and SMS
Message Placeholders
Operation:
1. Choose Device Settings > Event Rules > .
2. Select "Send email" from the Action list.
3. In the "Recipient Email Addresses" field, specify the email address(es) of the recipient(s). Use a comma to separate multiple email addresses.
4. To use the SMTP server specified on the SMTP Server page, make sure the "Use custom SMTP Server" checkbox is NOT selected.
287
288
Chapter 6: Using the Web Interface
To use a different SMTP server, select this checkbox. The fields for customized SMTP settings appear. For information on each field, see
Configuring SMTP Settings
Default messages are sent based on the event. For a list of default log messages and events that trigger them, see
Default Log
Messages
5. If needed, select the Use Custom Log Message checkbox, and then create a custom message up to 1024 characters in the provided field.

When clicking anywhere inside the text box, the Event Context
Information displays, showing a list of placeholders and their definitions. Just click the desired placeholder. For details, see
Email and SMS Message Placeholders

To start a new line in the text box, press Enter.

If needed, you can resize the text box by dragging the bottom-right corner.
Send Sensor Report
You may set the PX3TS so that it automatically reports the latest readings or states of one or multiple sensors by sending a message or email or simply recording the report in a log. These sensors can be either internal or environmental sensors as listed below.
•
Inlet sensors, including RMS current, RMS voltage, active power, apparent power, power factor and active energy.
•
Outlet sensors, including RMS current, RMS voltage, active power, apparent power, power factor, active energy and outlet state (for outlet-switching capable PDUs only).
•
PDU sensors, including two DC 12V power supply sensors.
•
Transfer switch sensors, including inlet phase sync angle, active inlet, operational state, phase sync, overload and transfer switch status.
• Overcurrent protector sensors, including RMS current and tripping state.
•
Peripheral device sensors, which can be any Raritan environmental sensor packages connected to the PX3TS, such as temperature or humidity sensors.
An example of this action is available in the section titled
Send Sensor
Report Example
Operation:
1. Choose Device Settings > Event Rules >
2. Select "Send sensor report" from the Action list.
.
Chapter 6: Using the Web Interface
3. In the Destination Actions section, select the method(s) to report sensor readings or states. The number of available methods varies, depending on how many messaging actions have been created.
The messaging action types include:

Log event message

Syslog message

Send email

Send SMS message a. If no messaging actions are available, create them now. See
Available Actions
b. To select any methods, select them one by one in the Available field.
To add all available methods, simply click Select All. c. To delete any methods, click a method's in the Selected field.
To remove all methods, simply click Deselect All.
4. In the Available Sensors field, select the desired target's sensor. a. Click the first to select a target component from the list. b. Click the second from the list.
to select the specific sensor for the target c. Click list box.
to add the selected sensor to the Report Sensors
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.
5. To report additional sensors simultaneously, repeat the above step to add more sensors.
289
290
Chapter 6: Using the Web Interface

To remove any sensor from the Report Sensors list box, select it and click . To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
6. To immediately send out the sensor report, click Send Report Now.
Tip: When intending to send a sensor report using custom messages, use the placeholder [SENSORREPORT] to report sensor readings. See
Email and SMS Message Placeholders
(on page 301).
Send SMS Message
You can configure SMS messages to be sent when an event occurs and can customize the message.
Messages consist of a combination of free text and PX3TS placeholders.
The placeholders represent information which is pulled from the PX3TS and inserted into the message.
A supported modem, such as the Cinterion
®
GSM MC52i modem, must be plugged into the PX3TS in order to send SMS messages. See
Connecting a GSM Modem
Note: The PX3TS cannot receive SMS messages.
For example:
[USERNAME] logged into the device on [TIMESTAMP] translates to
JQPublic logged into the device on 2012-January-30 21:00
For a list and definition of available variables, see
Email and SMS
Message Placeholders
Operation:
1. Choose Device Settings > Event Rules >
2. Select "Send SMS message" from the Action list.
.
3. In the Recipient Phone Number field, specify the phone number of the recipient.
4. Select the Use Custom Log Message checkbox, and then create a custom message in the provided text box.

When clicking anywhere inside the text box, the Event Context
Information displays, showing a list of placeholders and their definitions. Just click the desired placeholder. For details, see
Email and SMS Message Placeholders

To start a new line in the text box, press Enter.
Chapter 6: Using the Web Interface

If needed, you can resize the text box by dragging the bottom-right corner.
Note: Only the 7-bit ASCII charset is supported for SMS messages.
Send Snapshots via Email
This option notifies one or multiple persons for the selected events by emailing snapshots or videos captured by a connected Logitech
® webcam.
Operation:
1. Choose Device Settings > Event Rules >
2. Select "Send snapshots via email" from the Action list.
.
3. In the "Recipient Email Addresses" field, specify the email address(es) of the recipient(s). Use a comma to separate multiple email addresses.
4. To use the SMTP server specified on the SMTP Server page, make sure the "Use custom SMTP Server" checkbox is NOT selected.
To use a different SMTP server, select this checkbox. The fields for customized SMTP settings appear. For information on each field, see
Configuring SMTP Settings
5. Select the webcam that is capturing the images you want sent in the email.
6. Adjust the values of the following:

Number of Snapshots - the number of snapshots to be taken when the event occurs. For example, you can specify 10 images be taken once the event triggers the action.

Snapshots per Mail - the number of snapshots to be sent at one time in the email.

Time Before First Snapshot - the amount of time in seconds between when the event is triggered and the webcam begins taking snapshots.

Time Between Snapshots - the amount of time in seconds between when each snapshot is taken.
291
292
Chapter 6: 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 their default or do the following: a. In the Timeout field, specify the interval of time, in seconds, after which a new inform communication is resent if the first is not received. For example, resend a new inform communication once every 3 seconds. b. In the Number of Retries field, specify the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails.
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 system agent.
4. In the Port fields, enter the port number used to access the device(s).
5. In the Community fields, enter the SNMP community string to access the device(s). The community is the group representing the PX3TS 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.
Chapter 6: Using the Web Interface
3. For SNMP INFORM communications, leave the resend settings at their default or do the following: a. In the Timeout field, specify the interval of time, in seconds, after which a new inform communication is resent if the first is not received. For example, resend a new inform communication once every 3 seconds. b. In the Number of Retries field, specify the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails.
4. For both SNMP TRAPS and INFORMS, enter the following as needed and then click OK to apply the settings: a. Host name b. Port number c. User ID for accessing the host -- make sure the User ID has the
SNMPv3 permission. d. Select the host security level
Security level Description
"noAuthNoPriv" Select this if no authorization or privacy protocols are needed.
"authNoPriv"
"authPriv"
Select this if authorization is required but no privacy protocols are required.
• Select the authentication protocol - MD5 or
SHA
•
Enter the authentication passphrase and then confirm the authentication passphrase
Select this if authentication and privacy protocols are required.
• Select the authentication protocol - MD5 or
SHA
•
Enter the authentication passphrase and confirm the authentication passphrase
• Select the Privacy Protocol - DES or AES
• Enter the privacy passphrase and then confirm the privacy passphrase
293
294
Chapter 6: Using the Web Interface
Start or Stop a Lua Script
If you have created or loaded a Lua script file into the PX3TS, 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
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.
.
4. In the Script field, select the script that you want it to be started or stopped when an event occurs.

No script is available if you have not created or loaded it into the
PX3TS.
5. To apply different arguments than the default, do the following. Note that the newly-added arguments will override this script's default arguments. a. Click b. Type the key and value.
. c. Repeat the same steps to enter more arguments as needed.

To remove any existing argument, click it.
adjacent to
Switch LHX/SHX
If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will be available. See
Miscellaneous
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 that device's . To remove all devices, click Deselect All.
Chapter 6: Using the Web Interface
Switch Outlets
The "Switch outlets" action is available only when your PX3TS is outlet-switching capable. This action turns on, off or power cycles a specific outlet.
Operation:
1. Choose Device Settings > Event Rules > .
2. Select "Switch outlets" from the Action list.
3. In the Operation field, select an operation for the selected outlet(s).

Turn Outlet On: Turns on the selected outlet(s).

Turn Outlet Off: Turns off the selected outlet(s).

Cycle Outlet: Cycles power to the selected outlet(s).
4. To specify the outlet(s) where this action will be applied, select them one by one from the Available Outlets list.

To add all outlets, click Select All.
5. To remove any outlets from the Selected Outlets field, click that outlet's .

To remove all outlets, click Deselect All.
6. If "Turn Outlet On" or "Cycle Outlet" is selected in step 3, you can choose to select the "Use sequence order and delays" checkbox so that all selected outlets will follow the power-on sequence defined on the page of
Outlets
Switch Peripheral Actuator
If you have any actuator connected to the PX3TS, you can set up the
PX3TS so it automatically turns on or off the system controlled by the actuator when a specific event occurs.
Note: For information on connecting actuators, see
DX Sensor
Packages
(on page 37).
Operation:
1. Choose Device Settings > Event Rules >
2. Select "Switch peripheral actuator" from the Action list.
3. In the Operation field, select an operation for the selected actuator(s).

Turn On: Turns on the selected actuator(s).

Turn Off: Turns off the selected actuator(s).
.
295
296
Chapter 6: Using the Web Interface
4. To select the actuator(s) where this action will be applied, select them one by one from the Available Actuators list.

To add all actuators, click Select All.
5. To remove any selected actuator from the Selected Actuators field, click that actuator's .

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.
The PX3TS may or may not detect the syslog message transmission failure. If yes, it will log this syslog failure as well as the failure reason in the event log. See
Viewing or Clearing the Local Event Log
(on page
Operation:
1. Choose Device Settings > Event Rules >
2. Select "Syslog message" from the Action list.
.
3. In the Syslog Server field, specify the IP address to which the syslog is forwarded.
4. In the Transport Protocol field, select one of the syslog protocols:
TCP, UDP or TCP+TLS. The default is UDP.
Transport protocols
UDP
TCP
Next steps

In the UDP Port field, type an appropriate port number. Default is 514.

Select the "Legacy BSD Syslog Protocol" checkbox if applicable.
NO TLS certificate is required. Type an appropriate port number in the TCP Port field.
Transport protocols
TCP+TLS
Chapter 6: Using the Web Interface
Next steps
A TLS certificate is required. Do the following: a. Type an appropriate port number in the "TCP Port" field. Default is 6514. b. In the CA Certificate field, click installing the certificate, you may:

Click Show to view its contents.
to select a TLS certificate. After

Click Remove to delete it if it is inappropriate. c. Determine whether to select the "Allow expired and not yet valid certificates" checkbox.

To always send the event message to the specified syslog server as long as a TLS certificate is available, select this checkbox.

To prevent the event message from being sent to the specified syslog server when any TLS certificate in the selected certificate chain is outdated or not valid yet, deselect this checkbox.
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
PX3TS report the reading or state of a specific sensor regularly by scheduling the "Send Sensor Report" action.
When scheduling an action, make sure you have a minimum of 1-minute buffer between this action's creation and first execution time. Otherwise, the scheduled action will NOT be performed at the specified time when the buffer time is too short. For example, if you want an action to be performed at 11:00 am, you should finish scheduling it at 10:59 am or earlier.
If the needed action is not available yet, create it first. See
Available
Actions
Operation:
1. Choose Device Settings > Event Rules >
.
2. To select any action(s), select them one by one from the Available
Actions list.

To select all available actions, click Select All.
3. To remove any action(s) from the Selected Actions field, click that action's .
297
Chapter 6: Using the Web Interface

To remove all actions, click Deselect All.
4. Select the desired frequency in the Execution Time field, and then specify the time interval or a specific date and time in the field(s) that appear.
298
Chapter 6: Using the Web Interface
Execution time
Minutes
Hourly
Daily
Frequency settings
Click the Frequency field to select an option.
The frequency ranges from every minute, every 5 minutes, every 10 minutes and so on until every 30 minutes.
Type a value in the Minute field, which is set to either of the following:

The Minute field is set to 0 (zero). Then the action is performed at 1:00 am, 2:00 am, 3:00 am and so on.

The Minute field is set to a non-zero value. For example, if it is set to 30, then the action is performed at 1:30 am,
2:30 am, 3:30 am and so on.
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.
Weekly
Monthly
For example, if you specify 01:30PM, the action is performed at 13:30 pm every day.
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 in particular does not have the date 30 and probably even 29.
Check the calendar when selecting 29, 30 or 31.
299
300
Chapter 6: Using the Web Interface
Execution time
Frequency settings
Yearly
This option requires three settings:

Month - January through December.

Day of month - 1 to 31.

Time - the value is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM/PM button.
An example of the scheduled action is available in the section titled
Send
Sensor Report Example
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 an email to the desired recipient(s). For details, see
Send Email
(on

In this example, this action is named
Email a Sensor Report
.

If intended, you can customize the email messages in this action.
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

In this example, this action is named
Send Temperature Sensor
Readings
.

You can specify more than one temperature sensor as needed in this action.
3. Click to create a timer for performing the 'Send Temperature Sensor Readings' action hourly.
For details, see
Scheduling an Action

In this example, the timer is named
Hourly Temperature Sensor
Reports
.

To perform the specified action at 12:30 pm, 01:30 pm, 02:30 pm, and so on, select Hourly, and set the Minute to 30.
Chapter 6: Using the Web Interface
Then the PX3TS will send out an email containing the specified temperature sensor readings hourly every day.
Whenever you want the PX3TS to stop sending the temperature report, simply deselect the Enabled checkbox in the timer.
Placeholder
[ACTIVEINLET]
[AMSBLADESLOTPOSITION]
[AMSLEDCOLOR]
[AMSLEDMODE]
[AMSLEDOPMODE]
[AMSNAME]
[AMSNUMBER]
[AMSRACKUNITPOSITION]
[AMSSTATE]
[AMSTAGID]
[CIRCUITCTRATING]
[CIRCUITCURRENTRATING]
[CIRCUITNAME]
[CIRCUITPOLE]
Email and SMS Message Placeholders
Actions of "Send email" and "Send SMS message" allow you to customize event messages. See
Send Email
Send SMS
Message
When clicking anywhere inside the text box, the Event Context
Information displays, showing a list of placeholders and their definitions.
Simply drag the scroll bar and then click the desired placeholder to insert it into the custom message. Or you can type a keyword in the
"search" box to quickly find the desired placeholder.
If wanted, you can resort the list by clicking the desired column header.
See
Sorting a List
To make the Event Context Information disappear, click anywhere outside its window.
Following are placeholders that can be used in custom messages.
Definition
The label of the newly activated inlet
The (horizontal) slot position, an action applies to
The RGB LED color
The LED indication mode
The LED operating mode
The name of an asset strip
The numeric ID of an asset strip
The (vertical) rack unit position, an action applies to
The human readable state of an asset strip
The asset tag ID
The circuit CT rating
The circuit current rating
The circuit name
The circuit power line identifier
301
302
Chapter 6: Using the Web Interface
Placeholder
[CIRCUITSENSOR]
[CIRCUIT]
[CONFIGPARAM]
[CONFIGVALUE]
[DATETIME]
[DEVICEIP]
[DEVICENAME]
[ERRORDESC]
[EVENTRULENAME]
[EXTSENSORNAME]
[EXTSENSORSLOT]
[EXTSENSOR]
[IFNAME]
[INLETPOLE]
[INLETSENSOR]
[INLET]
[ISASSERTED]
[LDAPERRORDESC]
[LHXFANID]
[LHXPOWERSUPPLYID]
[LHXSENSORID]
[MONITOREDHOST]
[OCPSENSOR]
[OCP]
[OLDVERSION]
Definition
The circuit sensor name
The circuit identifier
The name of a configuration parameter
The new value of a parameter
The human readable timestamp of the event occurrence
The IP address of the device, the event occurred on
The name of the device, the event occurred on
The error message
The name of the matching event rule
The name of a peripheral device
The ID of a peripheral device slot
The peripheral device identifier
The human readable name of a network interface
The inlet power line identifier
The inlet sensor name
The power inlet label
Boolean flag whether an event condition was entered
(1) or left (0)
An LDAP error occurred
The ID of a fan connected to an LHX/SHX
The ID of an LHX/SHX power supply
The ID of an LHX/SHX sensor probe
The name or IP address of a monitored host
The overcurrent protector sensor name
The overcurrent protector label
The firmware version the device is being upgraded from
Placeholder
[OUTLETNAME]
[OUTLETPOLE]
[OUTLETSENSOR]
[OUTLET]
[PDUPOLESENSOR]
[PDUSENSOR]
[PERIPHDEVPOSITION]
[PHONENUMBER]
[PORTID]
[PORTTYPE]
[POWERMETERPOLE]
[POWERMETERSENSOR]
[POWERMETER]
[RADIUSERRORDESC]
[ROMCODE]
[SENSORREADINGUNIT]
[SENSORREADING]
[SENSORREPORT]
[SENSORSTATENAME]
[SMTPRECIPIENTS]
[SMTPSERVER]
[SYSCONTACT]
[SYSLOCATION]
Chapter 6: Using the Web Interface
Definition
The outlet name
Note: If any outlet does not have a name, neither an outlet name nor an outlet number will be shown in the custom message for it. Therefore, it is recommended to check the availability of all outlet names if intending to use this placeholder.
The outlet power line identifier
The outlet sensor name
The outlet label
The sensor name for a certain power line
The PDU sensor name
The position of an attached peripheral device
The phone number an SMS was sent to
The label of the external port, the event triggering device is connected to
The type of the external port (for example, 'feature' or
'auxiliary'), the event triggering device is connected to
The PMC power meter line identifier
The PMC power meter sensor name
The PMC power meter ID
A Radius error occurred
The rom code of an attached peripheral device
The unit of a sensor reading
The value of a sensor reading
The formatted sensor report contents
The human readable state of a sensor
The list of recipients, an SMTP message was sent to
The name or IP address of an SMTP server
SysContact as configured for SNMP
SysLocation as configured for SNMP
303
304
Chapter 6: Using the Web Interface
Placeholder
[SYSNAME]
[TIMEREVENTID]
[TIMESTAMP]
[TRANSFERSWITCHREASON]
[TRANSFERSWITCHSENSOR]
[TRANSFERSWITCH]
[UMTARGETROLE]
[UMTARGETUSER]
[USERIP]
[USERNAME]
[VERSION]
Definition
SysName as configured for SNMP
The id of a timer event
The timestamp of the event occurrence
The transfer reason
The transfer switch sensor name
The transfer switch label
The name of a user management role, an action was applied on
The user, an action was triggered for
The IP address, a user connected from
The user who triggered an action
The firmware version the device is upgrading to
Editing or Deleting a Rule/Action
You can change the settings of an event rule, action or scheduled action, or delete them.
Exception: Some settings of the built-in event rules or actions are not user-configurable. Besides, you cannot delete built-in rules and actions.
See
Built-in Rules and Rule Configuration
(on page 262) or
Available
Actions
(on page 280).
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, click on the top-right corner. Then click Delete on the confirmation message.
Chapter 6: Using the Web Interface
Sample Event Rules
Sample PDU-Level Event Rule
In this example, we want the PX3TS to record the firmware upgrade failure in the internal log when it happens.
The event rule involves:
• Event: Device > Firmware update failed
• Action: System Event Log Action
To create this PDU-level event rule:
1. For an event at the PDU level, select "Device" in the Event field.
2. Select "Firmware update failed" so that the PX3TS responds to the event related to firmware upgrade failure.
3. To make the PX3TS record the firmware update failure event in the internal log, select "System Event Log Action" in the Available
Actions field.
Sample Outlet-Level Event Rule
In this example, we want the PX3TS to send SNMP notifications to the
SNMP manager for any sensor change event of outlet 3.
The event rule involves:
• Event: Outlet > Outlet 3 > Sensor > Any sub-event
•
Action: System SNMP Notification Action
To create this outlet-level event rule:
1. For an event at the outlet level, select "Outlet" in the Event field.
2. Select "Outlet 3" because that is the desired outlet.
3. Select "Sensor" to refer to sensor-related events.
4. Select "Any sub-event" to include all events related to all sensors of this outlet and all thresholds, such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold, lower warning threshold, and so on.
5. To make the PX3TS send SNMP notifications, select "System SNMP
Notification Action" in the Available Actions field.
Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for the System SNMP
Notification Action. See
Enabling and Configuring SNMP
(on page
349).
Then the SNMP notifications are sent when:

Any numeric sensor's reading enters the warning or critical range.
305
306
Chapter 6: Using the Web Interface

Any sensor reading or state returns to normal.

Any sensor becomes unavailable.

The active energy sensor is reset.

Any state sensor changes its state.
For example, when the outlet 3's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again.
Sample Inlet-Level Event Rule
In this example, we want the PX3TS 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 PX3TS 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
349).
Then the SNMP notifications are sent when:

Any numeric sensor's reading enters the warning or critical range.

Any sensor reading or state returns to normal.

Any sensor becomes unavailable.

The active energy sensor is reset.
For example, when the Inlet I1's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again.
Chapter 6: Using the Web Interface
Sample Environmental-Sensor-Level Event Rule
This section applies to outlet-switching capable models only.
In this example, we want PX3TS to activate the load shedding function when a contact closure sensor enters the alarmed state. This event rule requires creating a new action before creating the rule.
Step 1: create a new action for activating the load shedding
1. Choose Device Settings > Event Rules > .
2. In this illustration, assign the name "Activate Load Shedding" to the new action.
3. In the Action field, select "Change load shedding state."
4. In the Operation field, select Start Load Shedding.
5. Click Create to finish the creation.
After the new action is created, follow the procedure below to create an event rule that triggers the load shedding mode when the contact closure sensor enters the alarmed state. This event rule involves the following:
•
Event: Peripheral Device Slot > Slot 1 > State Sensor/Actuator >
Alarmed/Open/On
• Trigger condition: Alarmed
• Action: Activate Load Shedding
Step 2: create the contact closure-triggered load shedding event rule
1. Click on the Event Rules page.
2. In this illustration, assign the name "Contact Closure Triggered Load
Shedding" to the new rule.
3. In the Event field, select "Peripheral Device Slot" to indicate we are specifying an event related to the environmental sensor package.
4. Select the ID number of the desired contact closure sensor. In this illustration, the ID number of the desired contact closure sensor is 1, so select Slot 1.
Note: ID numbers of all sensors/actuators are available on the
Peripherals page. See
Peripherals
(on page 164).
5. Select "State Sensor/Actuator" because the contact closure sensor is a state sensor.
307
308
Chapter 6: Using the Web Interface
6. Select "Alarmed" since we want the PX3TS to respond when the selected contact closure sensor changes its state related to the
"alarmed" state.
7. In the "Trigger condition" field, select the Alarmed/Open/On radio button so that the action is taken only when the contact closure sensor enters the alarmed state.
8. Select "Activate Load Shedding" from the Available Actions list.
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 PX3TS keeps busy because the action or one of the actions taken for a certain event triggers an identical or similar event which will result in an action triggering one more event.
Example 1
This example illustrates an event rule which continuously causes the
PX3TS to send out email messages.
Event selected Action included
Device > Sending SMTP message failed Send email
Example 2
This example illustrates an event rule which continuously causes the
PX3TS to send 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 the event "Sending SMTP message failed."
Event selected
Device > Any sub-event
Action included
Send email
Example 3
This example illustrates a situation where two event rules combined regarding the outlet state changes causes the PX3TS to continuously power cycle outlets 1 and 2 in turn.
Event selected
Outlet > Outlet 1 > Sensor > Outlet
State > On/Off > Both (trigger condition)
Action included
Cycle Outlet 2
(Switch outlets --> Cycle Outlet -->
Outlet 2)
Chapter 6: Using the Web Interface
Event selected
Outlet > Outlet 2 > Sensor > Outlet
State > On/Off > Both (trigger condition)
Action included
Cycle Outlet 1
(Switch outlets --> Cycle Outlet -->
Outlet 1)
A Note about Untriggered Rules
In some cases, a measurement exceeds a threshold causing the PX3TS to generate an alert. The measurement then returns to a value within the threshold, but the PX3TS does not generate an alert message for the
Deassertion event. Such scenarios can occur due to the hysteresis tracking the PX3TS uses. See
"To De-assert" and Deassertion
Hysteresis
Setting Data Logging
The PX3TS 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 PX3TS internal sensors are measured every second, specifying a value of 60, for example, would cause measurements to be written to the data log once every minute. Since there are 120 measurements of storage per sensor, specifying a value of 60 means the log can store the last two hours of measurements before the oldest one in the log gets overwritten.
Whenever measurements are written to the log, three values for each sensor are written: the average, minimum and maximum values. For example, if measurements are written every minute, the average of all measurements that occurred during the preceding 60 seconds along with the minimum and maximum measurement values are written to the log.
Note: The PX3TS device's SNMP agent must be enabled for this feature to work. See
Enabling and Configuring SNMP
(on page 349). 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.
309
310
Chapter 6: Using the Web Interface
2. To enable the data logging feature, select the "Enable" checkbox in the General Settings section.
3. Type a number in the Measurements Per Log Entry field. Valid range is from 1 to 600. The default is 60.
4. Verify that all sensor logging is enabled. If not, click Enable All at the bottom of the page to have all sensors selected.

You can also click the topmost checkbox labeled "Logging
Enabled" in the header row of each section to select all sensors of the same type.

If any section's number of sensors exceeds 35, the remaining sensors are listed on next page(s). If so, a pagination bar similar to the following diagram displays in this section, which you can click any button to switch between pages.
5. Click Save. This button is located at the bottom of the page.
Important: Although it is possible to selectively enable/disable logging for individual sensors on the PX3TS, it is NOT recommended to do so.
Configuring Data Push Settings
You can push the sensor or asset strip data to a remote server for data synchronization. The data will be sent in JSON format using HTTP POST requests. You need to set up the destination and authentication for data push on the PX3TS.
For instructions on connecting asset strips, see
Connecting Asset
Management Strips
After configuring the destination and authentication settings, do either or both of the following:
• To perform the data push after the occurrence of a certain event, create the data push action and assign it to an event rule.
•
To push the data at a regular interval, schedule the data push action.
See
Event Rules and Actions
To configure data push settings:
1. Choose Device Settings > Data Push.
2. To specify a destination, click
3. Do the following to set up the URL field.
. a. Click to select
http
or
https
.
Chapter 6: Using the Web Interface b. Type the URL or host name in the accompanying text box.
4. If selecting https, a CA certificate is required for making the connection. Click to install it. Then you can:

Click Show to view the certificate's content.

Click Remove to delete the installed certificate if it is inappropriate.
5. If the destination server requires authentication, select the Use
Authentication checkbox, and enter the following data.

User name

Password
6. 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) and a list of asset tags. The asset tags list also includes those on blade extension strips, if any.

Asset management log: Transmit the log of all asset strips, which is generated when there are changes made to asset tags and asset strips, including asset tag connection or disconnection events.

Sensor log: Transmit the record of all logged sensors, including their sensor readings and/or status. Logged sensors refer to all internal and/or environmental sensors/actuators that you have selected on the Data Logging page. See
Setting Data Logging
7. If "Asset management tag list" is selected in the above step, specify the asset strip(s) whose information to send. For PX3TS 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 in the
Selected AMS Ports field. Or click Deselect All to remove all.
8. Click Create.
9. Repeat the same steps for additional destinations.
To modify or delete data push settings:
1. On the Data Push page, click the one you want in the list.
2. Perform either action below.

To modify settings, make necessary changes and then click Save.

To delete it, click confirmation message.
, and then confirm it on the
311
312
Chapter 6: Using the Web Interface
Monitoring Server Accessibility
You can monitor whether specific IT devices are alive by having the
PX3TS device continuously ping them. An IT device's successful response to the ping commands indicates that the IT device is still alive and can be remotely accessed.
This function is especially useful when you are not located in an area with Internet connectivity.
PX3TS can monitor the accessibility of any IT device, such as database servers, remote authentication servers, power distribution units (PDUs), and so on. It supports monitoring a maximum of 8 devices.
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 PX3TS automatically log, send notifications or perform other actions for any server monitoring events, you can create event rules. See
Event Rules and Actions
(on page 261). An example is
available in
Example: Ping Monitoring and SNMP Notifications
(on
page 314).
To add IT equipment for ping monitoring:
1. Choose Device Settings > Server Reachability.
2. Click .
3. By default, the "Enable ping monitoring for this server" checkbox is selected. If not, select it to enable this feature.
4. Configure the following.
Field Description
IP address/hostname IP address or host name of the IT equipment which you want to monitor.
Number of successful pings to enable feature
Wait time after successful ping
Wait time after unsuccessful ping
The number of successful pings required to declare that the monitored equipment is
"Reachable." Valid range is 0 to 200.
The wait time before sending the next ping if the previous ping was successfully responded. Valid range is 5 to 600
(seconds).
The wait time before sending the next ping if the previous ping was not responded.
Valid range is 3 to 600 (seconds).
Chapter 6: Using the Web Interface
Field
Number of consecutive unsuccessful pings for failure
Wait time before resuming pinging after failure
Number of consecutive failures before disabling feature (0 = unlimited)
Description
The number of consecutive pings without any response before the monitored equipment is declared "Unreachable."
Valid range is 1 to 100.
The wait time before the PX3TS resumes pinging after the monitored equipment is declared "Unreachable." Valid range is 1 to
1200 (seconds).
The number of times the monitored equipment is declared "Unreachable" consecutively before the PX3TS disables the ping monitoring feature for 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.
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 the PX3TS can declare that the monitored device is reachable or unreachable.
To check the server monitoring states and results:
1. After adding IT equipment for monitoring, all IT devices are listed on the Server Reachability page.
2. The column labeled "Ping Enabled" indicates whether the monitoring for the corresponding IT device is activated or not.
3. The column labeled "Status" indicates the accessibility of each monitored equipment.
Status
Reachable
Unreachable
Description
The monitored equipment is accessible.
The monitored equipment is inaccessible.
Waiting for reliable connection
The connection between the PX3TS device and the monitored equipment is not reliably established yet.
313
314
Chapter 6: Using the Web Interface
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

To delete it, click on the top-right corner.
Example: Ping Monitoring and SNMP Notifications
In this illustration, it is assumed that a significant PDU (IP address:
192.168.84.95) shall be monitored by your PX3TS to make sure that PDU is properly operating all the time, and the PX3TS must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or network failure. The prerequisite for this example is that the power sources are different between your PX3TS and the monitored
PDU.
This requires the following two steps.
Step 1: Set up the ping monitoring for the target PDU
1. Choose Device Settings > Server Reachability.
2. Click .
3. Ensure the "Enable ping monitoring for this server" checkbox is selected.
4. Enter the data shown below.

Enter the server's data.
Field
IP address/hostname
Data entered
192.168.84.95

To make the PX3TS declare the accessibility of the monitored
PDU every 15 seconds (3 pings * 5 seconds) when that PDU is accessible, enter the following data.
Chapter 6: Using the Web Interface
Field Data entered
Number of successful pings to enable feature 3
Wait time after successful ping 5

To make the PX3TS declare the inaccessibility of the monitored
PDU when that PDU becomes inaccessible for around 12 seconds (4 seconds * 3 pings), enter the following data.
Field
Wait time after unsuccessful ping
Data entered
4
Number of consecutive unsuccessful pings for failure
3

To make the PX3TS stop pinging the target PDU for 60 seconds (1 minute) after the PDU inaccessibility is declared. After 60 seconds, the PX3TS will re-ping the target PDU, enter the following data.
Field
Wait time before resuming pinging after failure
Data entered
60

The "Number of consecutive failures before disabling feature (0 = unlimited)" can be set to any value you want.
5. Click Create.
Step 2: Create an event rule to send SNMP notifications for the target PDU
1. Choose Device Settings > Event Rules.
2. Click .
3. Select the Enabled checkbox to enable this new rule.
4. Configure the following.
Field/setting
Rule name
Event
Trigger condition
Data specified
Send SNMP notifications for PDU
(192.168.84.95) inaccessibility
Choose Server Monitoring >
192.168.84.95 > Unreachable
Select the Unreachable radio button
315
316
Chapter 6: Using the Web Interface
This will make the PX3TS react only when the target PDU becomes inaccessible.
5. Select the System SNMP Notification Action.
Note: If you have not configured the System SNMP Notification Action to specify the SNMP destination(s), see
Editing or Deleting a Rule/Action
(on page 304).
Front Panel Settings
You can perform outlet switching via the front panel. Note that this feature is available on outlet-switching capable models only. By default this feature is disabled.
To enable the front panel outlet-switching feature:
1. Choose Device Settings > Front Panel.
2. To enable the front panel outlet-switching function, select the
"Outlet switching" checkbox.
3. Click Save.
Now you can turn on or off any outlets by operating the front panel. See
Outlet Switching
Chapter 6: Using the Web Interface
Configuring the Serial Port
You can change the bit rate of the serial port labeled CONSOLE / MODEM on the PX3TS. The default bit rate for both console and modem operation is 115200 bps.
The PX3TS supports using the following devices via the serial interface:
•
A computer or Raritan KVM product for console management.
• 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 PX3TS through the serial port, or there are communication problems.
Note: The serial port bit-rate change is required when the PX3TS works in conjunction with Raritan's Dominion LX KVM switch. Dominion LX only supports 19200 bps for communications over the serial interface.
You can set diverse bit-rate settings for console and modem operations.
Usually the PX3TS can detect the device type, and automatically apply the preset bit rate.
The PX3TS will indicate the detected device in the Port State section of the Serial Port page. For example, if an analog modem is detected, the
Port State section looks similar to the following.
To configure serial port or modem settings, choose Device Settings >
Serial Port.
To change the serial port baud rate settings:
1. Click the "Connected device" field to make the serial port enter an appropriate state.
Options
Automatic detection
Force console
Force analog modem
Force GSM modem
Description
The PX3TS automatically detects the type of the device connected to the serial port.
Select this option unless your PX3TS cannot correctly detect the device type.
The PX3TS attempts to recognize that the connected device is set for the console mode.
The PX3TS attempts to recognize that the connected device is an analog modem.
The PX3TS attempts to recognize that the connected device is a GSM modem.
317
318
Chapter 6: Using the Web Interface
2. Click the Console Baud Rate field to select the baud rate intended for console management.
Note: For a serial RS-232 or USB connection between a computer and the PX3TS, 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 PX3TS.
The following modem settings/fields appear in the web interface after the PX3TS detects the connection of an analog or GSM modem.
To configure the analog modem:
1. Select the "Answer incoming calls" checkbox to enable the remote access via a modem. Otherwise, deselect it.
2. Type a value in the "Number of rings before answering" field to determine the number of rings the PX3TS must wait before answering the call.
To configure the GSM modem:
1. Enter the SIM PIN code.
2. Select the "Use custom SMS center number" checkbox if a custom
SMS center will be used.

Enter the SMS center number in the "SMS center" field.
3. If needed, click Advanced Information to view detailed information about the modem, SIM and mobile network.
4. To test whether the PX3TS can successfully send out SMS messages with the modem settings: a. Enter the number of the recipient's phone in the Recipient Phone field. b. Click Send SMS Test to send a test SMS message.
Lua Scripts
If you can write or obtain any Lua scripts, you can create or load them into the PX3TS to control its behaviors.
Raritan also provides some Lua scripts examples, which you can load as needed.
Note: Not all Raritan Lua script examples can apply to your PX3TS model.
You should read each example's introduction before applying them.
You must have the Administrator Privileges to manage Lua scripts.
Chapter 6: Using the Web Interface
Writing or Loading a Lua Script
You can enter or load up to 4 scripts to the PX3TS.
Tip: If you can no longer enter or load a new script after reaching the upper limit, you can either delete any existing script or simply modify/replace an existing script's codes. See
Modifying or Deleting a
Script
(on page 323).
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
Start automatically at system boot
Behavior when selected
Whenever the PX3TS reboots, the script is automatically executed.
Restart after termination
The script is automatically executed each time after 10 seconds since the script execution finishes.
4. (Optional) Determine the arguments that will be executed by default. a. Click b. Type the key and value.
. c. Repeat the same steps to enter more arguments as needed.

To remove any existing argument, click it.
adjacent to
Note: Default arguments are overridden by the 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 321) or
Start or Stop a Lua Script
(on page 294).
319
Chapter 6: Using the Web Interface
5. In the Source Code section, do one of the following. It is recommended to leave the Enable Syntax Highlighting checkbox selected unless you do not need different text colors to identify diverse code syntaxes.

To write a Lua script, type the codes in the Source Code section.
320

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 the codes. If needed, modify the codes to meet your needs.
7. Click Create.
Next steps:
• To execute the newly-added script now, click
Start with Arguments. See
, or click
Manually Starting or Stopping a Script
•
To add more scripts, return to the scripts list by clicking "Lua
Scripts" again in the steps.
Menu
(on page 105), and then repeat the above
>
Chapter 6: 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 PX3TS automatically start or stop a script in response to an event, create an event rule. See
Event Rules and Actions
(on page
261) and
Start or Stop a Lua Script
(on page 294).
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
3. To start with default arguments, click .
To start with new arguments, click > Start with Arguments.
Newly-assigned arguments will override default ones.
4. If you chose "Start with Arguments" in the above step, enter the key and value in the Start Lua Script dialog.
321
322
Chapter 6: Using the Web Interface

Click if needing additional arguments.
5. Click Start.
6. The script output will be shown in the Script Output section.

If needed, click to delete the existing output data.
To manually stop a script:
1. Choose Device Settings > Lua Scripts.
2. Click the desired script whose state is either 'Running' or
'Restarting.' For details, see
Checking Lua Scripts States
(on page
3. Click on the top-right corner.
4. Click Stop on the confirmation message.
Chapter 6: Using the Web Interface
Checking Lua Scripts States
Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state and settings of each script.
State:
•
•
•
•
Four script states are available.
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
Restart:
This column indicates whether the checkbox labeled "Restart after termination" is enabled. See
Writing or Loading a Lua Script
(on page
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 PX3TS.
To modify or replace a script:
1. Choose Device Settings > Lua Scripts.
2. Click the desired one in the scripts list.
323
324
Chapter 6: Using the Web Interface
3. Click > Edit Script.
4. Make changes to the information shown, except for the script's name, which cannot be revised.

To replace the current script, click Load Local File or Load
Example to select a new script.
To delete a script:
1. Choose Device Settings > Lua Scripts.
2. Click the desired one in the scripts list.
3. Click > Delete.
4. Click Delete on the confirmation message.
Miscellaneous
By default, the Schroff LHX/SHX heat exchanger support and Cisco
EnergyWise feature implemented on the PX3TS are disabled.
Support needs to be enabled for the LHX/SHX information to appear in the PX3TS web interface. Besides, Schroff LHX/SHX support must be enabled in order for the LHX-MIB to be accessible through SNMP.
If a Cisco
®
EnergyWise energy management architecture is implemented in your place, you can enable the Cisco EnergyWise endpoint implemented on the PX3TS so that this PX3TS becomes part of the Cisco
EnergyWise domain.
To enable either feature, choose Device Settings > Miscellaneous.
To enable the support for Schroff LHX/SHX:
1. Select the Schroff LHX/SHX Support checkbox.
2. Click Save in the
Features
section.
3. Click Apply on the confirmation message.
4. The PX3TS reboots.
To set the Cisco EnergyWise configuration:
1. Select the Enable EnergyWise checkbox.
2. Configure the following:
Field
Domain name
Description
Type the name of a Cisco EnergyWise domain where the
PX3TS belongs

Up to 127 printable ASCII characters are permitted.

Spaces and asterisks are NOT acceptable.
Chapter 6: Using the Web Interface
Field
Domain password
Port
Description
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.
Type a User Datagram Protocol (UDP) port number for communications in the Cisco EnergyWise domain.

Range from 1 to 65535.

Default is 43440.
Polling interval Type a polling interval to determine how often the PX3TS is queried in the Cisco EnergyWise domain.

Range from 30 to 600 ms.

Default is 180 ms.
3. Click Save in the
EnergyWise
section.
Maintenance
Click 'Maintenance' in the submenu displays.
Menu
(on page 105), and the following
Submenu command Refer to...
Device Information
Device Information
Connected Users
Viewing Connected Users
Event Log
Update Firmware
Firmware History
Bulk Configuration
Viewing or Clearing the Local Event Log
Updating the PX3TS Firmware
Viewing Firmware Update History
Bulk Configuration
Backup/Restore
Network Diagnostic
Download Diagnostic
Unit Reset
About iPDU
Backup and Restore of Device Settings
Network Diagnostics


Downloading Diagnostic Information
Rebooting the PX3TS Device
Resetting All Settings to Factory Defaults
Retrieving Software Packages Information
325
326
Chapter 6: Using the Web Interface
Device Information
Using the web interface, you can retrieve hardware and software information of components or peripheral devices connected to your
PX3TS.
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.
Section title
Information
Network
Information shown
General device information, such as model name, serial number, firmware version, hardware revision, MIB download link(s) and so on.
Note that the download link of LHX-MIB is available only after enabling the Schroff
LHX/SHX support. See
Miscellaneous
(on
The network information, such as the current networking mode, IPv4 and/or IPv6 addresses and so on.
This tab also indicates whether the PX3TS is part of a cascading configuration. See
Identifying Cascaded Devices
Port Forwarding
Outlets
If the port forwarding mode is activated, this section will show a list of port numbers for all cascaded devices.
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.
Chapter 6: Using the Web Interface
Section title
Controllers
Inlets
Peripheral Devices
Asset Management
Information shown
Each inlet or outlet controller's serial number, board ID, firmware version and hardware version.
Each inlet's plug type, rated voltage and current.
Serial numbers, model names, position and firmware-related information of connected environmental sensor packages.
Each asset strip's ID, boot version, application version and protocol version.
Identifying Cascaded Devices
For information on how to cascade PX3TS devices, see
Cascading
Multiple PX3TS Devices for Sharing Ethernet Connectivity
(on page
This section explains how to identify a cascaded device on the Device
Information page.
Note: For more information on the USB-cascading configuration, see the
Cascading Guide page
(
, which is available from Raritan website's
http://www.raritan.com/support/
).
Support
To identify the USB-cascading status:
1. Choose Maintenance > Device Information.
2. Click the Network title bar.

If the information shown on this page does not match the latest status, press F5 to reload it.
327
Chapter 6: Using the Web Interface
Cascading information in the Bridging mode:
•
The Common section contains two read-only fields for indicating the cascading status. Note that the cascading position is NOT available in the bridging mode.
Fields Description
Port Forwarding Indicates the Port Forwarding is disabled. See
Setting the Cascading Mode
BRIDGE section
Indicates the device is in the bridging mode and its
IP address.
328
Cascading information in the Port Forwarding mode:
• The Common section contains three read-only fields for indicating the cascading status.
Fields Description
Port Forwarding Indicates the Port Forwarding is enabled. See
Setting the Cascading Mode
Cascade Position Indicates the position of the PX3TS in the cascading configuration.

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.
Chapter 6: Using the Web Interface
Fields
Cascaded Device
Connected
Description
Indicates whether a slave device is detected on the
USB-A or Ethernet port.
 yes: Connection to a slave device is detected.
 no: NO connection to a slave device is detected.

A master device shows
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 which indicates its exact position in the Cascade Position field and
yes
in the Cascaded Device Connected field.
The following diagram shows 1, indicating it is the first slave -
Slave 1.
329
Chapter 6: Using the Web Interface

The final slave device shows a non-zero number which indicates its position in the Cascade Position field and
Device Connected field.
no
in the Cascaded
The following diagram shows 2, indicating it is the second slave -
Slave 2. The Cascaded Device Connected field shows indicating that it is the final one in the chain.
no
,
330
•
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 PX3TS device and their status. If you have administrator privileges, you can terminate any user's connection to the PX3TS.
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
Column
User name
IP Address
Description
The login name of each connected user.
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.
Chapter 6: Using the Web Interface
Column
Client Type
Idle Time
Description
The interface through which the user is being connected to the PX3TS.

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 webcame image sessions. See below.
The length of time for which a user remains idle.
2. To disconnect any user, click the corresponding a. Click Disconnect on the confirmation message. b. The disconnected user is forced to log out.
.
If there are live webcam sessions:
All Live Preview sessions sharing the same URL, including one Primary
Standalone Live Preview window of the sender and two sessions of the remote recipients, are identified as one single "<webcam>" user in the
Connected Users list. You can disconnect a "<webcam>" user to terminate all of the three sessions of a specific URL.
The IP address refers to the IP address of the host where the Primary
Standalone Live Preview window exists, NOT the IP address of the other two associated sessions.
For more webcam information, see
Webcam Management
(on page
331
332
Chapter 6: Using the Web Interface
Viewing or Clearing the Local Event Log
By default, the PX3TS captures certain system events and saves them in a local (internal) event log.
You can view over 2000 historical events that occurred on the PX3TS in the local event log. When the log size exceeds 256KB, each new entry overwrites the oldest one.
To display the local log:
1. Choose Maintenance > Event Log.
Each event entry consists of:

ID number of the event

Date and time of the event

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.

To refresh the data, press F5 as needed.
3. To go to other pages of the log, click the pagination bar at the bottom of the page.

If there are more than 5 pages and the page numbers displayed in the bar does not show the desired one, click to have it show the next 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
To clear the local log:
1. Click on the top-right corner.
2. Click Clear Log on the confirmation message.
Chapter 6: Using the Web Interface
Updating the PX3TS Firmware
(
Firmware files are available on Raritan website's
http://www.raritan.com/support/
).
Support page
When performing the firmware upgrade, the PX3TS 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 PX3TS firmware.
Before starting the upgrade, read the release notes downloaded from the 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 (any model with X2 or X3 suffixes), all inlets must be connected to power for the PDU to successfully upgrade its firmware.
Note that firmware upgrade via some mobile devices, such as iPad, requires the use of a file manager app.
Warning: Do NOT perform the firmware upgrade over a wireless network connection.
Important: If you are upgrading an existing USB-cascading chain from a firmware version older than 3.3.10, you must follow specific guidelines to avoid networking issues. See
Upgrade Guidelines for
Existing USB-Cascading Chains
To update the firmware:
1. Choose Maintenance > Update Firmware.
2. Click to select an appropriate firmware file.
3. Click Upload. A progress bar appears to indicate the upload process.
4. Once complete, information of both installed and uploaded firmware versions as well as compatibility and signature-checking results are displayed.

If anything is incorrect, click Discard Upload.
5. To proceed with the update, click Update Firmware.
Warning: Do NOT power off the PX3TS during the update.
6. During the firmware update:
333
334
Chapter 6: Using the Web Interface

A progress bar appears on the web interface, indicating the update status.

The front panel display shows the firmware upgrade message.
See
Overview of the LCD Display

The outlet LEDs flash if the relay boards are being updated. If the firmware update does not include the update of the relay board firmware, outlet LEDs do NOT flash.

No users can successfully log in to the PX3TS.

Other users' operation, if any, is forced to suspend.
7. When the update is complete, the PX3TS resets, and the Login page re-appears.

Other logged-in users are logged out when the firmware update is complete.
Important: If you are using the PX3TS with an SNMP manager, download its MIB again after the firmware update to ensure your
SNMP manager has the correct MIB for the latest release you are using. See
Using SNMP
Alternatives:
•
•
To use a different method to update the firmware, refer to:
•
Firmware Update via SCP
Bulk Configuration or Firmware Upgrade via DHCP/TFTP
(on page
Firmware Upgrade via USB
Upgrade Guidelines for Existing USB-Cascading Chains
•
Firmware version 3.3.10 is NOT compatible with old firmware versions in terms of the USB-cascading feature so all devices in a chain must be running version 3.3.10 or later. Otherwise, a networking issue occurs.
Alternative: You can also choose to have an existing USB-cascading chain keep on running the old firmware without upgrading any device to 3.3.10 or later.
•
When upgrading an existing USB-cascading chain from any version prior to 3.3.10, the upgrade must start from the last slave device, then the second to last, the third to last, and so on until the master device. Any upgrade without following this sequence results in the networking failure of some cascaded devices.
Chapter 6: Using the Web Interface
A Note about Firmware Upgrade Time
The PDU firmware upgrade time varies from unit to unit, depending on various external and internal factors.
External factors include, but are not limited to: network throughput, firmware file size, and speed at which the firmware is retrieved from the storage location. Internal factors include: the necessity of upgrading the firmware on the microcontroller and the number of microcontrollers that require upgrade (which depends on the number of outlets). The microcontroller is upgraded only when required. Therefore, the length of firmware upgrade time ranges from approximately 3 minutes (without any microcontroller updated) to almost 7 minutes (with all microcontrollers for 48 outlets updated). Take the above factors into account when estimating the PDU's firmware upgrade time.
The time indicated in this note is for PX3TS web-interface-based upgrades. Upgrades through other management systems, such as
Sunbird's Power IQ, may take additional time beyond the control of the
PDU itself. This note does not address the upgrades using other management systems.
Full Disaster Recovery
If the firmware upgrade fails, causing the PX3TS device to stop working, you can recover it by using a special utility rather than returning the device to Raritan.
Contact Raritan Technical Support for the recovery utility, which works in
Windows XP/Vista/7/10 and Linux. In addition, an appropriate PX3TS firmware file is required in the recovery procedure.
Viewing Firmware Update History
The firmware upgrade history is permanently stored on the PX3TS. It remains available even though you perform a device reboot or any firmware update.
To view the firmware update history:
1. Choose Maintenance > Firmware History.
Each firmware update event consists of:

Update date and time

Previous firmware version

Update firmware version

Update result
335
336
Chapter 6: Using the Web Interface
2. If wanted, you can resort the list by clicking the desired column header. See
Sorting a List
Bulk Configuration
The Bulk Configuration feature lets you save generic settings of a configured PX3TS device to your computer. You can use this configuration file to copy common settings to other PX3TS devices of the same model and firmware version.
Note that NO device-specific data is saved to the bulk configuration file, such as environmental sensors or certain network settings. For a list of device-specific settings that are
not
saved, see
Device-Specific Settings
NOT Included
Because the date and time settings are saved in the configuration file, users should exercise caution when distributing the configuration file to the PX3TS devices in a different time zone than the source device.
Tip: To back up or restore "all" settings of a particular PX3TS device, use the Backup/Restore feature instead. See
Backup and Restore of Device
Settings
(on page 338).
To save a bulk configuration file:
You must have the Administrator Privileges or "Unrestricted View
Privileges" to download the configuration.
1. Log in to the PX3TS whose settings you want to copy.
2. Choose Maintenance > Bulk Configuration.
3. Click Download Bulk Configuration.
4. When prompted to open or save the configuration file, click Save.

The file is saved in the XML format, and its content is encrypted using the AES-128 encryption algorithm.
To perform bulk configuration:
You must have the Administrator Privileges to upload the configuration.
1. Log in to another PX3TS of the same model running the same firmware.
2. Choose Maintenance > Bulk Configuration.
3. Click to select the configuration file.
4. Click 'Upload & Restore Bulk Configuration' to copy it.
Chapter 6: Using the Web Interface
5. A message appears, prompting you to confirm the operation and enter the admin password.
Enter the admin password, and click Restore.
6. Wait until the PX3TS device resets and the login page re-appears.
Note: On startup, the PX3TS performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset. For example, the
"Bulk configuration copied" event is logged only when the new configuration file contains the "Bulk configuration copied" event rule.
The last configuration-copying record:
If you once copied any bulk configuration or device backup file to the
PX3TS, the last record similar to the following is displayed at the bottom of both the Bulk Configuration and Backup/Restore pages.
Alternatives:
•
•
To use a different method to perform bulk configuration, refer to:
•
Bulk Configuration via SCP
Bulk Configuration or Firmware Upgrade via DHCP/TFTP
(on page
Configuration or Firmware Upgrade with a USB Drive
(on page
337
338
Chapter 6: Using the Web Interface
Device-Specific Settings NOT Included
The settings saved in the bulk configuration file include user and role configurations, thresholds, event rules, security settings, date/time and so on.
Note: Because the date and time settings are saved in the configuration file, users should exercise caution when distributing the configuration file to the PX3TS devices in a different time zone than the source device.
The bulk configuration file does NOT contain device-specific information, including:
•
Device name
• SNMP system name, contact and location
• Network settings (IP address, gateway, netmask and so on)
•
Device logs
•
Names, states and values of environmental sensors and actuators
•
TLS certificate
• Server monitoring entries
• Asset strip names and rack unit names
•
Outlet names and states
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 network settings. To back up or restore a PX3TS device's settings, you should perform the Backup/Restore feature.
All PX3TS information is captured in the XML backup file except for the device logs and TLS certificate.
Note: To perform bulk configuration among multiple PX3TS devices, use the Bulk Configuration feature instead. See
Bulk Configuration
(on page
336).
To download a backup PX3TS XML file:
You must have the Administrator Privileges or "Unrestricted View
Privileges" to download a backup file.
1. Choose Maintenance > Backup/Restore.
2. Click Download Device Settings. Save the file to your computer.

The file is saved in the XML format, and its content is encrypted using the AES-128 encryption algorithm.
Chapter 6: Using the Web Interface
To restore the PX3TS using a backup XML file:
You must have the Administrator Privileges to restore the device settings.
1. Choose Maintenance > Backup/Restore.
2. Click to select the backup file.
3. Click 'Upload & Restore Device Settings' to upload the file.

A message appears, prompting you to confirm the operation and enter the admin password.
4. Enter the admin password, then click Restore.
5. Wait until the PX3TS device resets and the Login page re-appears, indicating that the restore is complete.
Note: On startup, the PX3TS performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset. For example, the
"Bulk configuration copied" event is logged only when the new configuration file contains the "Bulk configuration copied" event rule.
The last configuration-copying record:
If you once copied any bulk configuration or device backup file to the
PX3TS, the last 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
339
340
Chapter 6: Using the Web Interface
Network Diagnostics
The PX3TS provides the following tools in the web interface for diagnosing potential networking issues.
•
Ping: The tool is useful for checking whether a host is accessible through the network or Internet.
•
Trace Route: The tool lets you find out the route over the network between two hosts or systems.
• List TCP Connections: You can use this function to display a list of
TCP connections.
Tip: These network diagnostic tools are also available through CLI. See
Network Troubleshooting
(on page 525).
Choose Maintenance > Network Diagnostics, and then perform any function below.
Ping:
1. Type values in the following fields.
Field
Network Host
Description
The name or IP address of the host that you want to check.
Number of
Requests
A number up to 20.
This determines how many packets are sent for pinging the host.
2. Click Run Ping to ping the host. The Ping results are then displayed.
Trace Route:
1. Type values in the following fields.
Field/setting
Host Name
Description
The IP address or name of the host whose route you want to check.
Timeout(s) A timeout value in seconds to end the trace route operation.
Use ICMP Packets To use the Internet Control Message Protocol
(ICMP) packets to perform the trace route command, select this checkbox.
2. Click Run. The Trace Route results are then displayed.
Chapter 6: Using the Web Interface
List TCP Connections:
1. Click the List TCP Connections title bar to show the list.
Downloading Diagnostic Information
Important: This function is for use by Raritan Field Engineers or when you are directed by Raritan Technical Support.
You can download the diagnostic file from the PX3TS 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. Click Save.
3. E-mail this file as instructed by Raritan Technical Support.
Rebooting the PX3TS Device
You can remotely reboot the PX3TS device via the web interface.
Resetting the PX3TS 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 PX3TS deletes all webcam snapshots that are saved on the PX3TS locally. See
Viewing Saved Snapshots and
Managing Storage
To reboot the device:
1. Choose Maintenance > Unit Reset >
2. Click Reboot to restart the PX3TS.
.
3. A message appears, with a countdown timer showing the remaining time of the operation. It takes about one minute to complete.
4. When the restart is complete, the login page opens.
341
Chapter 6: Using the Web Interface
Note: If you are not redirected to the login page after the restart is complete, click the text "this link" in the countdown message.
Resetting All Settings to Factory Defaults
You must have the Administrator Privileges to reset all settings of the
PX3TS to factory defaults.
Important: Exercise caution before resetting the PX3TS to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on. Only active energy data and firmware upgrade history are retained.
To reset the device to factory defaults:
1. Choose Maintenance > Unit Reset >
.
342
2. Click Factory Reset to reset the PX3TS to factory defaults.
3. A message appears, with a countdown timer showing the remaining time of the operation. It takes about two minutes to complete.
4. When the reset is complete, the login page opens.
Note: If you are not redirected to the login page after the reset is complete, click the text "this link" in the countdown message.
Alternative:
There are two more methods to reset the device to factory defaults.
• Use the "mechanical" reset button
• Perform the CLI command
For details, see
Resetting to Factory Defaults
Chapter 6: Using the Web Interface
Retrieving Software Packages Information
You can check the current firmware version and the information of all open source packages embedded in the PX3TS device through the web interface.
To retrieve the embedded software packages information:
1. Choose Maintenance > About iPDU. A list of open source packages is displayed.
2. You can click any link to access related information or download any software package.
Webcam Management
The webcam-related menu items appear only when there are webcam(s) connected to the PX3TS. See
Connecting a Logitech Webcam
(on page
With a Logitech
®
webcam connected to the PX3TS, you can visually monitor the environment around the PX3TS via snapshots or videos captured by the webcam.
• To view snapshots and videos, you need the permission of either
"Change Webcam Configuration" or "View Webcam Snapshots and
Configuration."
•
To configure webcam settings, you need the "Change Webcam
Configuration" permission.
If your webcam supports audio transmission, audio will be available in live videos.
You can manually store snapshots taken from the webcam onto the
PX3TS or a remote server. See
Viewing Saved Snapshots and Managing
Storage
Links to snapshots or videos being captured by a webcam can be sent via email or instant message. See
Sending Snapshots or Videos in an
Email or Instant Message
You can create event rules to trigger emails containing snapshots from a webcam. See
Available Actions
For more information on the Logitech webcam, see the user documentation accompanying it.
343
344
Chapter 6: Using the Web Interface
Configuring Webcams and Viewing Live Images
To configure the webcam or view live snapshot/video sessions, choose
Webcam in the
Menu
Live Preview:
1. Click the Live Preview title bar to expand it.
2. The live snapshot/video session captured by the webcam is displayed.

The default is to show live snapshots. Interval time and the image captured time are displayed on the top of the image.
3. To save the current image, click Save Snapshot. See
Viewing Saved
Snapshots and Managing Storage
4. To have the live session also displayed in a Primary Standalone Live
Preview window, click New Live Preview Window.

You can send out this window's URL to share the live image with other users. See
Sending Snapshots or Videos in an Email or
Instant Message
5. To switch between snapshot and video modes, see the section below.
Settings

In the video mode, the number of frames to take per second (fps) and the captured 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 and saturation by adjusting the corresponding slide bar.

Or click "Set to Webcam Defaults" to restore all settings to this webcam's factory defaults.
Settings:
1. Click Edit Settings.
2. Enter a name for the webcam. Up to 64 characters are supported.
3. Type the location information in each location field if needed. Up to
63 characters are supported.
4. Select a resolution for the webcam.

If you connect two webcams to one USB-A port using a powered
USB hub, set the resolution to 352x288 or lower for optimal performance.
5. Select the webcam mode.
Chapter 6: Using the Web Interface

Video - the webcam enters the video mode. Set the Framerate
(frames per second) rate.

Snapshot - the webcam shows static images from the webcam.
Set the "Time Between Snapshots" rate as measured in seconds.
6. Click Save. The changes made to the settings are applied to the live session. See the above
Live Preview
section.
Note: The settings changes do not apply to those images captured prior to the changes.
345
346
Chapter 6: Using the Web Interface
Sending Snapshots or Videos in an Email or Instant Message
Whenever you open a Primary Standalone Live Preview window, a unique
URL is generated for this window session. A URL supports a maximum of three sessions. Therefore, you can email or instant message up to two persons this URL. Recipients can then click on the provided link and view live snapshots or videos simultaneously.
Tip: All Live Preview sessions sharing the same URL, including one
Primary Standalone Live Preview window of the sender and two sessions of the remote recipients, are identified as one single "<webcam>" user in the Connected Users list. You can disconnect a "<webcam>" user to terminate all of the three sessions of a specific URL. See
Viewing
Connected Users
(on page 330).
For explanation of this topic, the message sender is User A and the two recipients are User B and C.
User C is able to access the snapshot or video image via the link in any of the following scenarios:
• The Primary Standalone Live Preview window remains open on User
A's computer. If so, even though User A logs out of the web interface or the login session times out, the link remains available.
•
Another recipient's live preview session based on the same URL remains open. That is, User B's session remains. If so, even though
User A has closed the Primary Standalone Live Preview window, the link remains available.
• Neither User A's Primary Standalone Live Preview window nor User
B's session based on the same URL remains open, but the idle timeout period has not expired yet since the last live preview window session was closed. For information on idle timeout, see
Configuring Login Settings
Tip: When the idle timeout has not expired, the <webcam> user for that live preview URL remains shown on the Connected Users page.
Best Practice
As a best practice, User A should open the live snapshot or video session using a Primary Standalone Live Preview window and keep that window open at least until User C opens the live image session via the link.
Once User C opens the live session via the link, User A can close the
Primary Standalone Live Preview window.
User C should let User A know that the link has been opened.
To send a snapshot or video link via email or instant message:
1. Open the Webcam page by clicking it in the
Menu
Chapter 6: Using the Web Interface
2. Click Live Preview > New Live Preview Window. The live snapshot or video in a standalone live preview window opens. See
Configuring
Webcams and Viewing Live Images
3. Copy the URL from the live preview window, and send it through an email or instant message application.
4. Leave the live preview window open until the recipient opens the snapshot or video via the link.
Viewing Saved Snapshots and Managing Storage
Once a snapshot is saved, it is stored locally on the PX3TS by default. For instructions on saving snapshots, see
Configuring Webcams and
Viewing Live Images
Up to 10 images can be stored onto the PX3TS at once. Unless snapshots are deleted manually, the oldest snapshot is automatically overridden by the newest one when the total of snapshots exceeds 10.
To save more than 10 snapshots, you must save the images on a
Common Internet File System (CIFS)/Samba.
Snapshots are saved as JPG files, and named based on the sequential numbers, such as 1.jpg, 2.jpg, 3.jpg and so on.
Warning: Rebooting the PX3TS deletes all webcam snapshots that are saved on the PX3TS locally. See
Viewing Saved Snapshots and
Managing Storage
To view saved images or configure the storage settings, choose Webcam
Snapshots in the
Menu
To view and manage saved images:
1. Click the snapshot you want to view from the list.

If the list of snapshots saved in the specified CIFS/Samba server exceeds one page, you can switch between available pages by clicking the pagination bar on the top.
If there are more than 5 pages and the page numbers displayed in the bar does not show the desired one, click to have it show the next or previous five page numbers, if available.
2. The selected snapshot as well as its information, such as captured time and resolution, is displayed on the same page.
347
348
Chapter 6: Using the Web Interface
3. If the latest saved snapshot is not listed yet, click the top of the list.
> Refresh on
4. To manually delete any images: a. Select the checkboxes of the images you want to remove.

To select all images, select the top-most checkbox in the header row. b. On the top of the list, click > Delete Selected. c. Click Delete on the confirmation message.
To configure the storage settings:
1. Click > Settings.
2. Click the Storage Type field to select the desired storage location and configure as needed.
Storage location Description
Local Local means the PX3TS. This is default.
CIFS/Samba Snapshots will be saved on a Common Internet File
System/Samba. Configure the following fields for this server:

Server - the desired CIFS/Samba server

Share/Folder - this is the share drive/folder

Username - for server access

Password - for server access
3. In the Capacity field, type values to determine the maximum number of snapshots that can be saved on the selected storage location.
4. Click Save.
Chapter 7 Using SNMP
This SNMP section helps you set up the PX3TS for use with an SNMP manager. The PX3TS can be configured to send traps or informs to an
SNMP manager, as well as receive GET and SET commands in order to retrieve status and configure some basic settings.
In This Chapter
Enabling and Configuring SNMP .............................................................. 349
Downloading SNMP MIB ........................................................................... 352
Enabling and Configuring SNMP
To communicate with an SNMP manager, you must enable SNMP protocols on the PX3TS. By default the "read-only" mode of SNMP v1/v2c is enabled.
The SNMP v3 protocol allows for encrypted communication. To take advantage of this, you must configure the users with the SNMP v3 access permission and set Authentication Pass Phrase and Privacy Pass Phrase, which act as shared secrets between SNMP and the PX3TS.
Important: You must download the SNMP MIB for your PX3TS to use with your SNMP manager. See
Downloading SNMP MIB
To enable SNMP v1/v2c and/or v3 protocols:
1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Agent section, enable SNMP v1/v2c or SNMP v3, and configure related fields, such as the community strings.

If SNMP v3 is enabled, you must determine which users shall have the SNMP v3 access permission. See below.
For details, see
Configuring SNMP Settings
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
349
350
Chapter 7: Using SNMP
To enable SNMP notifications:
1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Notifications section, enable the SNMP notification feature, and configure related fields. For details, refer to:


SNMPv2c Notifications
SNMPv3 Notifications
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 280).
SNMPv2c Notifications
1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox is selected.
3. In the SNMP Notifications section, make sure the Enable SNMP
Notifications checkbox is selected.
4. Select SNMPv2c Trap or SNMPv2c Inform as the notification type.
5. Type values in the following fields.
Field
Timeout
Description
The interval of time, in seconds, after which a new inform communication is resent if the first is not received.

For example, resend a new inform communication once every 3 seconds.
Number of Retries The number of times you want to resend the inform communication if it fails.

For example, inform communications are resent up to 5 times when the initial communication fails.
Host The IP address of the device(s) you want to access.
This is the address to which notifications are sent by the SNMP agent.
You can specify up to 3 SNMP destinations.
Port The port number used to access the device(s).
Community The SNMP community string to access the device(s). The community is the group representing the PX3TS and all SNMP management stations.
Chapter 7: Using SNMP
6. Click Save.
SNMPv3 Notifications
1. Choose Device Settings > Network Services > SNMP.
2. In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox is selected.
3. In the SNMP Notifications section, make sure the Enable SNMP
Notifications checkbox is selected.
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
Host
Description
The IP address of the device(s) you want to access.
This is the address to which notifications are sent by the SNMP agent.
Port The port number used to access the device(s).
User ID
Timeout
User name for accessing the device.

Make sure the user has the SNMP v3 access permission.
The interval of time, in seconds, after which a new inform communication is resent if the first is not received.

For example, resend a new inform communication once every 3 seconds.
Number of Retries Specify the number of times you want to resend the inform communication if it fails.

For example, inform communications are resent up to 5 times when the initial communication fails.
Security Level Three types are available.
 noAuthNoPriv - neither authentication nor privacy protocols are needed.

AuthNoPriv - only authentication is required.
 authPriv - both authentication and privacy protocols are required.
351
352
Chapter 7: Using SNMP
Field
Authentication
Protocol,
Authentication
Passphrase,
Confirm
Authentication
Passphrase
Privacy Protocol,
Privacy
Passphrase,
Confirm Privacy
Passphrase
7. Click Save.
Description
The three fields are available when the security level is set to AuthNoPriv or authPriv.

Select the authentication protocol - MD5 or SHA

Enter the authentication passphrase
The three fields are available when the security level is set to authPriv.

Select the Privacy Protocol - DES or AES

Enter the privacy passphrase and then confirm the privacy passphrase
Downloading SNMP MIB
You must download an appropriate SNMP MIB file for successful SNMP communications. Always use the latest SNMP MIB downloaded from the current firmware of your PX3TS.
You can download the MIBs from two different pages of the web interface.
MIB download via the SNMP page:
1. Choose Device Settings > Network Services > SNMP.
2. Click the Download MIBs title bar.
3. Select the desired MIB file to download.

PDU2-MIB: The SNMP MIB file for PX3TS power management.

ASSETMANAGEMENT-MIB: The SNMP MIB file for asset management.

LHX-MIB: The SNMP MIB file for managing the LHX/SHX heat exchanger(s).
4. Click Save to save the file onto your computer.
Chapter 7: Using SNMP
MIB download via the Device Information page:
1. Choose Maintenance > Device Information.
2. In the Information section, click the desired download link:

PDU2-MIB

ASSETMANAGEMENT-MIB

LHX MIB
3. 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 324).
SNMP Gets and Sets
In addition to sending notifications, the PX3TS is able to receive SNMP get and set requests from third-party SNMP managers.
•
Get requests are used to retrieve information about the PX3TS, such as the system location, and the current on a specific outlet.
• Set requests are used to configure a subset of the information, such as the SNMP system name.
Note: The SNMP system name is the PX3TS device name. When you change the SNMP system name, the device name shown in the web interface is also changed.
The PX3TS 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 PX3TS MIB.
The PX3TS MIB
The SNMP MIB file is required for using your PX3TS device with an SNMP manager. An SNMP MIB file describes the SNMP functions.
353
Chapter 7: Using SNMP
Layout
Opening the MIB reveals the custom objects that describe the PX3TS system at the unit level as well as at the individual-outlet level.
As standard, these objects are first presented at the beginning of the file, listed under their parent group. The objects then appear again individually, defined and described in detail.
354
For example, the measurementsGroup group contains objects for sensor readings of PX3TS 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.
Chapter 7: Using SNMP
SNMP Sets and Thresholds
Some objects can be configured from the SNMP manager using SNMP set commands. Objects that can be configured have a MAX-ACCESS level of "read-write" in the MIB.
These objects include threshold objects, which causes the PX3TS to generate a warning and send an SNMP notification when certain parameters are exceeded. See
Sensor Threshold Settings
for a description of how thresholds work.
Note: When configuring the thresholds via SNMP set commands, ensure the value of upper critical threshold is higher than that of upper warning threshold.
Configuring NTP Server Settings
Using SNMP, you can change the following NTP server-related settings in the unitConfigurationTable:
•
Enable or disable synchronization of the device's date and time with
NTP servers (synchronizeWithNTPServer)
• Enable or disable the use of DHCP-assigned NTP servers if synchronization with NTP servers is enabled
(useDHCPProvidedNTPServer)
•
Manually assign the primary NTP server if the use of DHCP-assigned
NTP servers is disabled (primaryNTPServerAddressType and primaryNTPServerAddress)
• Manually assign the secondary NTP server (optional)
(secondaryNTPServerAddressType and secondaryNTPServerAddress)
Tip: To specify the time zone, use the CLI or web interface instead. For the CLI, see
Setting the Time Zone
(on page 436). For the web interface,
see
Setting the Date and Time
(on page 258).
When using the SNMP SET command to specify or change NTP servers, it is required that both the NTP server's address type and address be set in the command line simultaneously.
For example, the SNMP command to change the primary NTP server's address from IPv4 (192.168.84.84) to host name looks similar to the following: snmpset -v2c -c private 192.168.84.84 firstNTPServerAddressType = dns firstNTPServerAddress =
"angu.pep.com"
355
356
Chapter 7: Using SNMP
Retrieving Energy Usage
You can discover how much energy an IT device consumes by retrieving the Active Energy for the outlet this IT device is plugged into. The Active
Energy values are included in the outletSensorMeasurementsTable, along with other outlet sensor readings.
Note: PX3TS-1000 series does not support this functionality.
A Note about Enabling Thresholds
When enabling previously disabled thresholds via SNMP, make sure you set a correct value for all thresholds that are supposed to be enabled prior to actually enabling them. Otherwise, you may get an error message.
Chapter 8 Using the Command Line Interface
This section explains how to use the command line interface (CLI) to administer a PX3TS device.
CLI commands are case sensitive.
In This Chapter
Querying Available Parameters for a Command .................................... 363
Entering Configuration Mode ................................................................... 395
Quitting Configuration Mode .................................................................... 396
PX3TS Control and Configuration ............................................................ 396
Load Shedding Configuration Commands ............................................... 516
Actuator Control Operations .................................................................... 521
Retrieving Previous Commands ............................................................... 528
Automatically Completing a Command ................................................... 528
357
358
Chapter 8: Using the Command Line Interface
About the Interface
The PX3TS 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 PX3TS device
•
Display the PX3TS and network information, such as the device name, firmware version, IP address, and so on
• Configure the PX3TS and network settings
• Troubleshoot network problems
You can access the interface over a local connection using a terminal emulation program such as HyperTerminal, or via a Telnet or SSH client such as PuTTY.
Note: Telnet access is disabled by default because it communicates openly and is thus insecure. To enable Telnet, see
Changing Telnet
Settings
(on page 233).
Logging in to CLI
Logging in via HyperTerminal over a local connection is a little different than logging in using SSH or Telnet.
If a security login agreement has been enabled, you must accept the agreement in order to complete the login. Users are authenticated first and the security banner is checked afterwards.
With HyperTerminal
You can use any terminal emulation programs for local access to the command line interface.
This section illustrates HyperTerminal, which is part of Windows operating systems prior to Windows Vista.
To log in using HyperTerminal:
1. Connect your computer to the PX3TS via a local connection.
2. Launch HyperTerminal on your computer and open a console window. When the window first opens, it is blank.
Make sure the COM port settings use this configuration:

Bits per second = 115200 (115.2Kbps)

Data bits = 8

Stop bits = 1

Parity = None
Chapter 8: Using the Command Line Interface

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 PX3TS. The Username prompt appears.
4. Type a name and press Enter. The name is case sensitive. Then you are prompted to enter a password.
5. Type a password and press Enter. The password is case sensitive.
After properly entering the password, the # or > system prompt appears. See
Different CLI Modes and Prompts
User Guide for more information.
Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile 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 the PX3TS.
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. See
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 228) 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.
359
360
Chapter 8: Using the Command Line Interface
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 # or > system prompt appears. See
Different CLI Modes and Prompts
User Guide for more information.
Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile 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 the PX3TS.
With an Analog Modem
The PX3TS supports remote access to the CLI via a connected analog modem. This feature is especially useful when the LAN access is not available.
To connect to the PX3TS via the modem:
1. Make sure the PX3TS has an analog modem connected. See
Connecting an Analog Modem
2. Make sure the computer you are using has an appropriate modem connected.
3. Launch a terminal emulation program, and configure its baud rate settings according to the baud rate set for the analog modem connected to the PX3TS. See
Configuring the Serial Port
(on page
4. Type the following AT command to make a connection with the
PX3TS.
ATD<modem phone number>
5. The CLI login prompt appears after the connection is established successfully. Then type the user name and password to log in to the
CLI.
To disconnect from the PX3TS:
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 PX3TS.
Chapter 8: Using the Command Line Interface
ATH
Different CLI Modes and Prompts
Depending on the login name you use and the mode you enter, the system prompt in the CLI varies.
•
User Mode: When you log in as a normal user, who may not have full permissions to configure the PX3TS device, the > prompt appears.
• Administrator Mode: When you log in as an administrator, who has full permissions to configure the PX3TS device, the # prompt appears.
•
Configuration Mode: You can enter the configuration mode from the administrator or user mode. In this mode, the prompt changes to config:# or config:> and you can change PX3TS device and network configurations. See
Entering Configuration Mode
•
Diagnostic Mode: You can enter the diagnostic mode from the administrator or user mode. In this mode, the prompt changes to diag:# or diag:> and you can perform the network troubleshooting commands, such as the ping command. See
Entering Diagnostic
Mode
Closing a Local Connection
Close the window or terminal emulation program when you finish accessing a PX3TS device over the local connection.
When accessing or upgrading multiple PX3TS devices, do not transfer the local connection cable from one device to another without closing the local connection window first.
361
362
Chapter 8: Using the Command Line Interface
Help Command
The help (?) command shows a list of main CLI commands available for the current mode. This is helpful when you are not familiar with CLI commands.
Help command under the administrator mode:
#
?
Help command under the configuration mode: config:#
?
Help command under the diagnostic mode: diag:#
?
Press Enter after typing the help command, and a list of main commands for the current mode is displayed.
Tip: You can check what parameters are available for a specific CLI command by adding the help command to the end of the queried command. See
Querying Available Parameters for a Command
(on
page 363).
Chapter 8: 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 a space and the help command (?) to the end of that command. A list of available parameters and their descriptions will be displayed.
The following shows a few query examples.
To query available parameters for the "show" command:
# show ?
To query available parameters for the "show user" command:
# show user ?
To query available network configuration parameters: config:# network ?
To query available role configuration parameters: config:# role ?
To query available parameters for the "role create" command: config:# role create ?
Showing Information
You can use the show commands to view current settings or the status of the PX3TS device or part of it, such as the IP address, networking mode, firmware version, states or readings of internal or external sensors, user profiles, and so on.
Some "show" commands have two formats: one with the parameter
"details" and the other without. The difference is that the command without the parameter "details" displays a shortened version of information while the other displays in-depth information.
After typing a "show" command, press Enter to execute it.
Note: Depending on your login name, the # prompt may be replaced by the > prompt. See
Different CLI Modes and Prompts
(on page 361).
363
364
Chapter 8: Using the Command Line Interface
Transfer Switch Information
This command shows the transfer switch-related information of the
PX3TS device.
# show ts
To show detailed information, add the parameter "details" to the end of the command.
# show ts details
Displayed information includes:
• Transfer switch label and custom name in parentheses
•
Operational state
•
Preferred inlet
•
Active inlet
• Inlet phase sync status
• Inlet phase angle and state
• Overload status
•
Transfer switch status
•
The following information for each inlet:
- Fuse status
- Power quality
- RMS voltage and state*
- Line frequency and state*
- 12V power supply state*
- Surge protector state*
•
Automatic retransfer enabled or disabled*
- Phase sync required or not*
- Wait time for automatic retransfer*
• Front panel Manual Transfer button enabled or disabled*
The above information marked with * is retrievable with the "show ts details" command only.
Chapter 8: Using the Command Line Interface
Power Quality Settings
This command shows the power quality criteria of the PX3TS device, including voltage and frequency thresholds per inlet.
# show ts powerQualityParameters
Transfer Timing Statistics
This command shows statistics on how long a power transfer takes, including power failure detection time, relay open time and total transfer time (in milliseconds).
# show ts transferTimingStatistics
Inlet Phase Sync Angle Information
This command syntax shows the inlet phase sync angle sensor's information.
# show sensor ts inletPhaseSyncAngle
To show detailed information, add the parameter "details" to the end of the command.
# show sensor ts inletPhaseSyncAngle
details
Displayed information:
• Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the inlet phase sync angle are displayed.
•
With the parameter "details," more sensor information is displayed, including resolution and range.
365
366
Chapter 8: Using the Command Line Interface
Network Configuration
This command shows all network configuration and all network interfaces' information, such as the IP address, MAC address, the
Ethernet interface's duplex mode, and the wireless interface's status/settings.
# show network
IP Configuration
This command shows the IP-related configuration only, such as IPv4 and
IPv6 configuration, address(es), gateway, and subnet mask.
Tip: To show IPv4-only and IPv6-only configuration data, see
IPv4-Only or IPv6-Only Configuration
(on page 367).
# show network ip common
To show the IP-related configuration of a specific network interface, use the following command.
# show network ip interface <ETH>
Variables:
•
<ETH> is one of the network interfaces:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Option ethernet wireless bridge
Description
Show the IP-related configuration of the
ETHERNET interface.
Show the IP-related configuration of the
WIRELESS interface.
Show the IP-related configuration of the BRIDGE interface.
Chapter 8: Using the Command Line Interface
Option all
Description
Show the IP-related configuration of all interfaces.
You can type the CLI command without the word
'all.' For example,
show network ip interface
.
IPv4-Only or IPv6-Only Configuration
To show IPv4-only configuration or IPv6-only configuration, use any of the following commands.
Tip: To show both IPv4 and IPv6 configuration data, see
IP Configuration
(on page 366).
To show all IPv4 configuration:
# show network ipv4 common
To show all IPv6 configuration:
# 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:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
367
368
Chapter 8: Using the Command Line Interface
Option ethernet wireless bridge all
Description
Show the IPv4 or IPv6 configuration of the
ETHERNET interface.
Show the IPv4 or IPv6 configuration of the
WIRELESS interface.
Show the IPv4 or IPv6 configuration of the BRIDGE interface.
Show the IPv4 or IPv6 configuration of all interfaces.
You can type the CLI command without the word
'all.' For example,
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 and authentication protocol.
# show network interface <ETH>
Variables:
•
<ETH> is one of the network interfaces:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Option ethernet wireless bridge all
Description
Show the ETHERNET interface's non-IP settings.
Show the WIRELESS interface's non-IP settings.
Show the BRIDGE interface's non-IP settings.
Show the non-IP settings of all interfaces.
You can type the CLI command without the word
'all.' For example,
show network interface
.
Chapter 8: 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
.
Option all http https telnet ssh snmp modbus zeroconfig
Description
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.
Only displays the TCP port for the HTTP service.
Only displays the TCP port for the HTTPS service.
Only displays the settings of the Telnet service.
Only displays the settings of the SSH service.
Only displays the SNMP settings.
Only displays the settings of the Modbus/TCP service.
Only displays the settings of the zero configuration advertising.
369
370
Chapter 8: Using the Command Line Interface
PDU Configuration
This command shows the PDU configuration, such as the device name, firmware version and model type.
# show pdu
To show detailed information, add the parameter "details" to the end of the command.
# show pdu
details
Outlet Information
This command syntax shows the outlet information.
# show outlets <n>
To show detailed information, add the parameter "details" to the end of the command.
# show outlets <n>
details
Variables:
• <n> is one of the options:
all
, or a number.
Option all
Description
Displays the information for all outlets.
Tip: You can also type the command without adding this option "all" to get the same data.
A specific outlet number
Displays the information for the specified outlet only.
Displayed information:
•
Without the parameter "details," only the outlet name is displayed.
For an outlet-switching capable model, both the outlet name and state are displayed.
• With the parameter "details," more outlet information is displayed in addition to the outlet name, such as the outlet rating.
Chapter 8: 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 the command.
# show inlets <n>
details
Variables:
• <n> is one of the options:
all
, or a number.
Option all
Description
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:
•
Without the parameter "details," only the inlet's name and RMS current are displayed.
• With the parameter "details," more inlet information is displayed in addition to the inlet name and RMS current, such as the inlet's RMS voltage, active power and active energy.
371
372
Chapter 8: Using the Command Line Interface
Overcurrent Protector Information
This command is only available for models with overcurrent protectors for protecting outlets.
This command syntax shows the overcurrent protector information, such as a circuit breaker or a fuse.
# show ocp <n>
To show detailed information, add the parameter "details" to the end of the command.
# show ocp <n>
details
Variables:
• <n> is one of the options:
all
, or a number.
Option all
Description
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 specific overcurrent protector number
Displays the information for the specified overcurrent protector only.
Displayed information:
• Without the parameter "details," only the overcurrent protector status and name are displayed.
•
With the parameter "details," more overcurrent protector information is displayed in addition to status, such as the rating and
RMS current value.
Chapter 8: Using the Command Line Interface
Date and Time Settings
This command shows the current date and time settings on the PX3TS device.
# show time
To show detailed information, add the parameter "details" to the end of the command.
# show time
details
Default Measurement Units
This command shows the default measurement units applied to the
PX3TS web and CLI interfaces across all users, especially those users authenticated through remote authentication servers.
# show user defaultPreferences
Note: If a user has set his/her own preferred measurement units or the administrator has changed any user's preferred units, the web and CLI interfaces show the preferred measurement units for that user instead of the default ones after that user logs in to the PX3TS. See
Existing
User Profiles
(on page 383) for the preferred measurement units for a
specific user.
373
374
Chapter 8: 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 the command.
# show externalsensors <n>
details
External sensor 3 ('Temperature 1')
Sensor type: Temperature
Reading: 31.8 deg C (normal)
Serial number: AEI0950133
Description: Not configured
Location: X Not configured
Y Not configured
Z Not configured
Position: Port 1
Using default thresholds: yes
Variables:
•
<n> is one of the options:
all
, or a number.
Option all
A specific environmental sensor number*
Description
Displays the information of all environmental sensors.
Tip: You can also type the command without adding this option "all" to get the same data.
Displays the information for the specified environmental sensor only.
Chapter 8: 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 PX3TS web interface.
Displayed information:
• Without the parameter "details," only the sensor ID, sensor type and reading are displayed.
Note: A state sensor displays the sensor state instead of the reading.
•
With the parameter "details," more information is displayed in addition to the ID number and sensor reading, such as the serial number, sensor position, and X, Y, and Z coordinates.
Note: DPX sensor packages do not provide chain position information.
Environmental Sensor Package Information
Different from the "show externalsensors" commands, which show the reading, status and configuration of an individual environmental sensor, the following command shows the information of all connected environmental sensor packages, each of which may contain more than one sensor or actuator.
# show peripheralDevicePackages
Information similar to the following is displayed. An environmental sensor package is a peripheral device package.
Peripheral Device Package 1
Serial Number:
Package Type:
AEI7A00022
DPX-T1H1
Position:
Package State:
Port 1 operational
Firmware Version: Not available
Peripheral Device Package 2
Serial Number:
Package Type:
AEI7A00021
DPX-T3H1
Position:
Package State:
Port 1 operational
Firmware Version: Not available
375
376
Chapter 8: 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 the command.
# show actuators <n>
details
Variables:
• <n> is one of the options:
all
, or a number.
Option all
Description
Displays the information for all actuators.
Tip: You can also type the command without adding this option "all" to get the same data.
A specific actuator number*
Displays the information for the specified actuator only.
* The actuator number is the ID number assigned to the actuator. The ID number can be found using the PX3TS web interface or CLI. It is an integer starting at 1.
Displayed information:
•
Without the parameter "details," only the actuator ID, type and state are displayed.
• With the parameter "details," more information is displayed in addition to the ID number and actuator state, such as the serial number and X, Y, and Z coordinates.
Chapter 8: Using the Command Line Interface
Outlet Sensor Threshold Information
This command syntax shows the specified outlet sensor's threshold-related information.
# show sensor outlet <n> <sensor type>
To show detailed information, add the parameter "details" to the end of the command.
# show sensor outlet <n> <sensor type>
details
Variables:
• <n> is the number of the outlet whose sensors you want to query.
•
<sensor type> is one of the following sensor types:
Sensor type current voltage activePower apparentPower powerFactor activeEnergy lineFrequency
Description
Current sensor
Voltage sensor
Active power sensor
Apparent power sensor
Power factor sensor
Active energy sensor
Line frequency sensor
Displayed information:
•
Without the parameter "details," only the sensor reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified outlet sensor are displayed.
•
With the parameter "details," more sensor information is displayed, including resolution and range.
• If the requested sensor type is not supported, the "Sensor is not available" message is displayed.
377
378
Chapter 8: 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 the command.
# show sensor inlet <n> <sensor type>
details
Variables:
• <n> is the number of the inlet whose sensors you want to query. For a single-inlet PDU, <n> is always the number 1.
•
<sensor type> is one of the following sensor types:
Sensor type current voltage activePower apparentPower powerFactor activeEnergy unbalancedCurrent lineFrequency
Description
Current sensor
Voltage sensor
Active power sensor
Apparent power sensor
Power factor sensor
Active energy sensor
Unbalanced load sensor
Line frequency sensor
Displayed information:
•
Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified inlet sensor are displayed.
• With the parameter "details," more sensor information is displayed, including resolution and range.
•
If the requested sensor type is not supported, the "Sensor is not available" message is displayed.
Chapter 8: Using the Command Line Interface
Overcurrent Protector Sensor Threshold Information
This command is only available for models with overcurrent protectors for protecting outlets.
This command syntax shows the specified overcurrent protector sensor's threshold-related information.
# show sensor ocp <n> <sensor type>
To show detailed information, add the parameter "details" to the end of the command.
# show sensor ocp <n> <sensor type>
details
Variables:
• <n> is the number of the overcurrent protector whose sensors you want to query.
• <sensor type> is one of the following sensor types:
Sensor type current
Description
Current sensor
Displayed information:
•
Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified overcurrent protector sensor are displayed.
•
With the parameter "details," more sensor information is displayed, including resolution and range.
379
380
Chapter 8: 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 the command.
# show sensor externalsensor <n>
details
External sensor 3 (Temperature):
Reading: 31.8 deg C
State: normal
Active Thresholds: Sensor specific thresholds
Default Thresholds for Temperature sensors:
Lower critical threshold: 10.0 deg C
Lower warning threshold: 15.0 deg C
Upper warning threshold: 30.0 deg C
Upper critical threshold: 35.0 deg C
Deassertion hysteresis: 1.0 deg C
Assertion timeout: 0 samples
Sensor Specific Thresholds:
Lower critical threshold: 8.0 deg C
Lower warning threshold: 13.0 deg C
Upper warning threshold: 28.0 deg C
Upper critical threshold: 33.0 deg C
Deassertion hysteresis: 1.0 deg C
Assertion timeout: 0 samples
Variables:
• <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 PX3TS web interface.
Chapter 8: Using the Command Line 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 the command.
# show defaultThresholds <sensor type>
details
Variables:
•
<sensor type> is one of the following numeric sensor types:
Sensor types absoluteHumidity relativeHumidity temperature airPressure airFlow vibration all
Description
Absolute humidity sensors
Relative humidity sensors
Temperature sensors
Air pressure sensors
Air flow sensors
Vibration sensors
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:
381
382
Chapter 8: Using the Command Line Interface
• Without the parameter "details," only the default upper and lower thresholds, deassertion hysteresis and assertion timeout settings of the specified sensor type are displayed.
•
With the parameter "details," the threshold range is displayed in addition to default thresholds settings.
Security Settings
This command shows the security settings of the PX3TS.
# show security
To show detailed information, add the parameter "details" to the end of the command.
# show security
details
Displayed information:
• Without the parameter "details," the information including IP access control, role-based access control, password policy, and HTTPS encryption is displayed.
•
With the parameter "details," more security information is displayed, such as user blocking time, user idle timeout and front panel permissions (if supported by your model).
Chapter 8: 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 the command.
# 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.
Option all
Description
This 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 are displayed: user name, user "Enabled" status, SNMP v3 access privilege, and role(s).
• With the parameter "details," more user information is displayed, such as the telephone number, e-mail address, preferred measurement units and so on.
383
384
Chapter 8: 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:
Option all
Description
This 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.
Load Shedding Settings
This section applies to outlet-switching capable models only.
This command shows the load shedding settings.
# show loadshedding
Displayed information:
• The load shedding state is displayed along with non-critical outlets.
Note: The load shedding mode is associated with critical and non-critical outlets. To specify critical and non-critical outlets through CLI, see
Specifying Non-Critical Outlets
(on page 405).
Chapter 8: Using the Command Line Interface
Serial Port Settings
This command shows the baud rate setting of the serial port labeled
CONSOLE / MODEM on the PX3TS device.
# show serial
EnergyWise Settings
This command shows the PX3TS device's current configuration for
Cisco
®
EnergyWise.
# show energywise
Asset Strip Settings
This command shows the asset strip settings, such as the total number of rack units (tag ports), asset strip state, numbering mode, orientation, available tags and LED color settings.
# show assetStrip <n>
Variables:
• <n> is one of the options:
all
, or a number.
Option all
Description
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 the specified FEATURE port number.
For the PX3TS device with only one FEATURE port, the valid number is always 1.
385
386
Chapter 8: Using the Command Line Interface
Rack Unit Settings of an Asset Strip
A rack unit refers to a tag port on the asset strips. This command shows the settings of a specific rack unit or all rack units on an asset strip, such as a rack unit's LED color and LED mode.
# show rackUnit <n> <rack_unit>
Variables:
• <n> is the number of the FEATURE port where the selected asset strip is physically connected. For the PX3TS device with only one
FEATURE port, the number is always 1.
•
<rack_unit> is one of the options: number.
all
or a specific rack unit's index
Option all
A specific number
Description
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.
Displays the settings of the specified rack unit on the specified asset strip.
Use the index number to specify the rack unit. The index number is available on the asset strip or the
Asset Strip page of the web interface.
Chapter 8: Using the Command Line Interface
Blade Extension Strip Settings
This command shows the information of a blade extension strip, including the total number of tag ports, and if available, the ID (barcode) number of any connected tag.
# show bladeSlot <n> <rack_unit> <slot>
Variables:
• <n> is the number of the FEATURE port where the selected asset strip is physically connected. For the PX3TS device with only one
FEATURE port, the number is always 1.
•
<rack_unit> is the index number of the desired rack unit (tag port) on the selected asset strip. The index number is available on the asset strip or the Asset Strip page of the web interface.
• <slot> is one of the options: the blade extension strip.
all
or a specific number of a tag port on
Option all
A specific number
Description
Displays the information of all tag ports on the specified blade extension strip connected to a particular rack unit.
Tip: You can also type the command without adding this option "all" to get the same data.
Displays the information of the specified tag port on the blade extension strip connected to a particular rack unit.
The number of each tag port on the blade extension strip is available on the Asset Strip page.
387
388
Chapter 8: Using the Command Line Interface
Event Log
The command used to show the event log begins with show eventlog.
You can add either the events.
limit
or
class
parameters or both to show specific
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:
•
<n> is one of the options:
all
or a number.
Option all
Description
Displays all entries in the event log.
An integer number
Displays the specified number of last entries in the event log. The number ranges between 1 to 10,000.
• <event_type> is one of the following event types.
Event type all device
Description
All events.
Device-related events, such as system starting or firmware upgrade event. userAdministration User management events, such as a new user profile or a new role. userActivity pdu
User activities, such as login or logout.
Displays PDU-related events, such as entry or exit of the load shedding mode.
Chapter 8: Using the Command Line Interface
Event type sensor serverMonitor
Description
Internal or external sensor events, such as state changes of any sensors.
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 modem
Schroff
®
LHX/SHX heat exchanger events.
Modem-related events. timerEvent webcam cardReader transferSwitch energywise
Scheduled action events.
Events for webcam management, if available.
Events for card reader management, if available.
Transfer switch events.
Cisco EnergyWise-related events, such as enabling the support of the EnergyWise function.
Note: You can ignore the powerLogic event type in the CLI because the
PX3TS does not support it.
Wireless LAN Diagnostic Log
This command shows the diagnostic log for the wireless LAN connection.
# show wlanlog
Server Reachability Information
This command shows all server reachability information with a list of monitored servers and status.
# show serverReachability
389
390
Chapter 8: 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 the following command.
# show serverReachability
server <n>
To show detailed information, add the parameter "details" to the end of the command.
# show serverReachability
server <n> details
Variables:
•
<n> is a number representing the sequence of the IT device in the monitored server list.
You can find each IT device's sequence number using the CLI command of show serverReachability as illustrated below.
Displayed information:
• Without the parameter "details," only the specified device's IP address, monitoring enabled/disabled state and current status are displayed.
•
With the parameter "details," more settings for the specified device are displayed, such as number of pings and wait time prior to the next ping.
Chapter 8: Using the Command Line Interface
Command History
This command syntax shows the command history for current connection session.
# show history
Displayed information:
•
A list of commands that were previously entered in the current session is displayed.
History Buffer Length
This command syntax shows the length of the history buffer for storing history commands.
# show history bufferlength
Displayed information:
•
The current history buffer length is displayed.
Reliability Data
This command shows the reliability data.
# show reliability data
Reliability Error Log
This command shows the reliability error log.
# show reliability errorlog <n>
Variables:
•
<n> is one of the options:
0
(zero) or any other integer number.
Option
0
Description
Displays all entries in the reliability error log.
Tip: You can also type the command without adding this option "0" to get all data.
391
392
Chapter 8: Using the Command Line Interface
Option
A specific integer number
Description
Displays the specified number of last entries in the reliability error log.
Examples
This section provides examples of the show command.
Example 1 - Basic Security Information
The diagram shows the output of the
show security
command.
Chapter 8: Using the Command Line Interface
Example 2 - In-Depth Security Information
More information is displayed when typing the command.
show security details
Example 3 - Basic PDU Information
The diagram shows the output of the
show pdu
command.
393
Chapter 8: Using the Command Line Interface
Example 4 - In-Depth PDU Information
More information is displayed when typing the purchased.
show pdu details
command. Displayed information varies depending on the model you
394
Clearing Information
You can use the clear commands to remove unnecessary data from the
PX3TS.
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 361).
Clearing Event Log
This command removes all data from the event log.
# clear eventlog
-- OR --
# clear eventlog
/y
If you entered the command without "/y," a message appears, prompting you to confirm the operation. Type y to clear the event log or n
to abort the operation.
If you type y, a message "Event log was cleared successfully" is displayed after all data in the event log is deleted.
Chapter 8: Using the Command Line Interface
Clearing WLAN Log
This command removes all data from the diagnostic log for the wireless
LAN (WLAN) connection.
# clear wlanlog
-- OR --
# clear wlanlog /y
If you entered the command without "/y," a message appears, prompting you to confirm the operation. Type y to clear the WLAN log or n
to abort the operation.
If you type y, a message "WLAN log was cleared successfully" is displayed to indicate all data in the WLAN log has been deleted.
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 361).
2. Type config and press Enter.
3. The config:# prompt appears, indicating that you have entered configuration mode.
4. Now you can type any configuration command and press Enter to change the settings.
Important: To apply new configuration settings, you must issue the
"apply" command before closing the terminal emulation program.
Closing the program does not save any configuration changes. See
Quitting Configuration Mode
395
396
Chapter 8: 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:# cancel
The # or > prompt appears after pressing Enter, indicating that you have entered the administrator or user mode. See
Different CLI Modes and
Prompts
PX3TS Control and Configuration
To configure the PX3TS device or network settings through the CLI, it is highly recommended to log in as the administrator so that you have full permissions.
To configure any settings, enter the configuration mode. Configuration commands are case sensitive so ensure you capitalize them correctly.
Controlling the Transfer Switch
A transfer switch command begins with settings.
ts
. You can use these commands to control the power transfer behavior or manage power transfer
Performing Manual Transfer
Performing manual transfer remotely requires either of these permissions: "Switch Transfer Switch" or "Administrator Privileges."
To verify the current active inlet and preferred inlet configuration via CLI, see
Transfer Switch Information
To perform manual transfer via CLI:
1. Ensure that the current mode is the administrator or user mode. See
Different CLI Modes and Prompts
2. Type either of the following commands and press Enter.
# ts transfer <inlet>
Chapter 8: Using the Command Line Interface
#
OR ts transfer <inlet> /y
<inlet> is one of the inlet numbers: 1 or 2.
3. If you entered the command without "/y" in the above step, a confirmation message appears. Type y to perform the manual transfer or n to abort.
4. Manual transfer may be prevented in certain scenarios. If so, a
"Transfer failed" message is displayed.
Note: Whenever the PX3TS prevents a manual transfer from being performed, it is disabled across all interfaces, including the front panel button, web interface and CLI command. See
Manual Transfer
Scenarios
(on page 65).
397
398
Chapter 8: Using the Command Line Interface
Configuring Power Transfer Features
Enter the configuration mode to change the following power transfer settings. See
Entering Configuration Mode
You can change various power transfer settings at a time by combining various commands. See
Multi-Command Syntax
Enable or disable the front panel Manual Transfer button: config:# ts manualTransferButton <option1>
Enable or disable automatic retransfer: config:# ts autoRetransfer <option2>
Determine the wait time for automatic retransfer after the preferred inlet restores to normal: config:# ts autoRetransferWaitTime <option3>
Enable or disable the phase sync requirement for automatic retransfer: config:# ts noAutoRetransferOnPhaseDifferenceFault <option4>
Name the transfer switch: config:# ts name "<name>"
Variables:
• <option1> is one of the options:
enable
or
disable
.
Option enable
Description
The Manual Transfer button is enabled. disable The Manual Transfer button is disabled.
• <option2> is one of the options:
enable
or
disable
.
Option enable
Description
Enables the automatic retransfer.
Chapter 8: Using the Command Line Interface
Option disable
Description
Disables the automatic retransfer.
•
<option3> is an integer number up to 180 in seconds.
• <option4> is one of the options:
enable
or
disable
.
Option enable
Description
Automatic retransfer is performed only when inlets are in phase. disable Automatic retransfer is performed regardless of the phase angle difference.
•
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
Example
The following command disables the front panel Manual Transfer button and enables the Auto Retransfer feature. config:# ts manualTransferButton disable autoRetransfer enable
Configuring Power Quality Parameters
All CLI commands used to configure power quality parameters begin with
ts powerQualityParameters
. Enter the configuration mode before performing any of these commands. See
Entering Configuration Mode
You can configure all of the following power quality parameters at a time by combining all commands. See
Multi-Command Syntax
Set the Lower Critical voltage threshold: config:# ts powerQualityParameters lowerCriticalVoltage
<threshold_volts> config:#
Set the Lower Warning voltage threshold: ts powerQualityParameters lowerWarningVoltage <threshold_volts>
Set the Upper Critical voltage threshold:
399
400
Chapter 8: Using the Command Line Interface config:# ts powerQualityParameters upperCriticalVoltage <threshold_volts>
Set the Upper Warning voltage threshold: config:# ts powerQualityParameters upperWarningVoltage <threshold_volts>
Set the Voltage deassertion hysteresis: config:# ts powerQualityParameters voltageHysteresis <volt_hysteresis>
Set the Voltage assertion timeout: config:# ts powerQualityParameters voltageAssertionTimeout <volt_timeout>
Set the Lower Critical frequency threshold: config:# ts powerQualityParameters lowerCriticalFrequency <threshold_Hz>
Set the Lower Warning frequency threshold: config:# ts powerQualityParameters lowerWarningFrequency <threshold_Hz>
Set the Upper Critical frequency threshold: config:# ts powerQualityParameters upperCriticalFrequency <threshold_Hz>
Set the Upper Warning frequency threshold: config:# ts powerQualityParameters upperWarningFrequency <threshold_Hz>
Set the frequency deassertion hysteresis: config:# ts powerQualityParameters frequencyHysteresis <freq_hysteresis>
Set the frequency assertion timeout:
Chapter 8: Using the Command Line Interface config:# ts powerQualityParameters frequencyAssertionTimeout <freq_timeout>
Variables:
•
<threshold_volts> is an integer number up to 500 in Volt.
•
<volt_hysteresis> is an integer number up to 500 in Volt.
•
<volt_timeout> is an integer number up to 100 in seconds.
•
<threshold_Hz> is either an integer number or a number with one decimal digit in Hz.
• <freq_hysteresis> is either an integer number or a number with one decimal digit in Hz.
•
<freq_timeout> is an integer number up to 100 in seconds.
Example
The following command sets the Upper Critical voltage threshold to 250 volts and Lower Warning frequency threshold to 45 Hz. config:# ts powerQualityParameters upperCriticalVoltage 250 lowerWarningFrequency 45
PDU Configuration Commands
A PDU configuration command begins with
PX3TS device.
pdu
. You can use the PDU configuration commands to change the settings that apply to the whole
Changing the PDU Name
This command changes the PX3TS device's name. config:# pdu name "<name>"
Variables:
•
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
401
402
Chapter 8: Using the Command Line Interface
Setting the Outlet Relay Behavior
This section applies to outlet-switching capable models only.
This command syntax determines the relay behavior of all outlets on a
PX3TS model. config:# pdu relayBehaviorOnPowerLoss <option>
Variables:
•
<option> is one of the options:
latching
or
nonLatching
.
Note: For more information on the outlet relay behavior, see
PX3TS
Latching Relay Behavior
(on page 136).
Setting the Outlet Power-On Sequence
This section applies to outlet-switching capable models only.
This command sets the outlet power-on sequence when the PDU powers up. config:# pdu outletSequence <option>
Variables:
•
<option> is one of the options: outlet numbers.
default
, or a comma-separated list of
Option default
A comma- separated list of outlet numbers
Description
All outlets are switched ON in the ASCENDING order (from outlet 1 to the final outlet) when the
PX3TS device powers up.
All outlets are switched ON in the order you specify using the comma-separated list.
The list must include all outlets on the PDU.
Note: Power-on sequencing is disabled in the latching mode. See
PX3TS
Latching Relay Behavior
(on page 136).
Chapter 8: Using the Command Line Interface
Setting the Outlet Power-On Sequence Delay
This section applies to outlet-switching capable models only.
This command sets the delays (in seconds) for outlets when turning on all outlets in sequence. config:# pdu outletSequenceDelay <outlet1>:<delay1>;<outlet2>:<delay2>;
<outlet3>:<delay3>;...
Separate outlet numbers and their delay settings with a colon. Outlets followed by delays are separated with a semicolon.
Variables:
• <outlet1>, <outlet2>, <outlet3> and the like are individual outlet numbers or a range of outlets using a dash. For example, represents outlets 3 to 8.
3-8
•
<delay1>, <delay2>, <delay3> and the like are the delay time in seconds.
Note: Power-on sequencing is disabled in the latching mode. See
PX3TS
Latching Relay Behavior
(on page 136).
Setting the PDU-Defined Default Outlet State
This section applies to outlet-switching capable models only.
This command determines the initial power condition of all outlets after powering up the PDU. config:# pdu outletStateOnDeviceStartup <option>
Variables:
•
<option> is one of the options:
off
,
on
or
lastKnownState
.
Option off on
Description
Switches OFF all outlets when the PX3TS device powers up.
Switches ON all outlets when the PX3TS device powers up.
403
404
Chapter 8: Using the Command Line Interface
Option Description lastKnownState Restores all outlets to the previous status before powering down the PX3TS device when the PDU powers up again.
Note: This feature does NOT take effect and cannot be configured on a
PX3TS device after the outlet relay is set to the "Latching" mode. See
PX3TS Latching Relay Behavior
(on page 136).
Setting the PDU-Defined Cycling Power-Off Period
This section applies to outlet-switching capable models only.
This command sets the power-off period of the power cycling operation for all outlets. config:# pdu cyclingPowerOffPeriod <timing>
Variables:
• <timing> is the time of the cycling power-off period in seconds, which is an integer between 0 and 3600, or the PDU-defined timing.
pduDefined
for following
Setting the Inrush Guard Delay Time
This section applies to outlet-switching capable models only.
This command sets the inrush guard delay. config:# pdu inrushGuardDelay <timing>
Variables:
• <timing> is a delay time between 100 and 100000 milliseconds.
Chapter 8: Using the Command Line Interface
Setting the Outlet Initialization Delay
This section applies to outlet-switching capable models only.
This command determines the outlet initialization delay timing on device startup. See
PDU
(on page 130) for information on outlet initialization
delay. config:# pdu outletInitializationDelayOnDeviceStartup <timing>
Variables:
•
<timing> is a delay time between 1 and 3600 seconds.
Note: This feature does NOT take effect and cannot be configured on a
PX3TS device after the outlet relay is set to the "Latching" mode. See
PX3TS Latching Relay Behavior
(on page 136).
Specifying Non-Critical Outlets
This section applies to outlet-switching capable models only.
This command determines critical and non-critical outlets. It is associated with the load shedding mode. See
Load Shedding Mode
(on config:# pdu nonCriticalOutlets <outlets1>:false;<outlets2>:true
Separate outlet numbers and their settings with a colon. Separate each
"false" and "true" setting with a semicolon.
Variables:
•
<outlets1> is one or multiple outlet numbers to be set as critical outlets. Use commas to separate outlet numbers.
Use a dash for a range of consecutive outlets. For example, represents outlets 3 to 8.
3-8
• <outlets2> is one or multiple outlet numbers to be set as
NON-critical outlets. Use commas to separate outlet numbers.
Use a dash for a range of consecutive outlets. For example, represents outlets 3 to 8.
3-8
405
406
Chapter 8: 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
.
Option enable disable
Description
Enables the data logging feature.
Disables the data logging feature.
For more information, see
Setting Data Logging
Setting Data Logging Measurements Per Entry
This command defines the number of measurements accumulated per log entry. config:# pdu measurementsPerLogEntry <number>
Variables:
• <number> is an integer between 1 and 600. The default is 60 samples per log entry.
For more information, see
Setting Data Logging
Chapter 8: Using the Command Line Interface
Specifying the Device Altitude
This command specifies your PX3TS device's altitude above sea level (in meters). You must specify the PX3TS device's altitude above sea level if a
Raritan's DPX differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor. See
Altitude Correction Factors
config:# pdu deviceAltitude <altitude>
Variables:
•
<altitude> is an integer between 1 and 3000 meters.
Setting the Z Coordinate Format for Environmental Sensors
This command enables or disables the use of rack units for specifying the height (Z coordinate) of environmental sensors. config:# pdu externalSensorsZCoordinateFormat <option>
Variables:
•
<option> is one of the options:
rackUnits
or
freeForm
.
Option rackUnits freeForm
Description
The height of the Z coordinate is measured in standard rack units. When this is selected, you can type a numeric value in the rack unit to describe the Z coordinate of any environmental sensors or actuators.
Any alphanumeric string can be used for specifying the Z coordinate.
Note: After determining the format for the Z coordinate, you can set a value for it. See
Setting the Z Coordinate
(on page 484).
407
408
Chapter 8: 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
.
Option enable disable
Description
Enables the automatic management feature for environmental sensor packages.
Disables the automatic management feature for environmental sensor packages.
For more information, see
How the Automatic Management Function
Works
Examples
This section illustrates several PDU configuration examples.
Example 1 - PDU Naming
The following command assigns the name "my px12" to the PDU. config:# pdu name "my px12"
Example 2 - Data Logging Enabled
The following command enables the data logging feature. config:# pdu dataRetrieval enable
Example 3 - Outlet Sequence Delay
The following command determines that the outlet 1's delay is 2.5 seconds, outlet 2's delay is 3 seconds, and the delay for outlets 3 through
5 is 10 seconds. config:# pdu outletSequenceDelay 1:2.5;2:3;3-5:10
Chapter 8: Using the Command Line Interface
Example 4 - Non-Critical Outlets
The following command sets outlets 1, 2, 3, 7, and 9 to be critical outlets, and 4, 5, 6, 8, 10, 11 and 12 to be non-critical outlets on a 12-outlet
PX3TS. config:# pdu nonCriticalOutlets 1-3,7,9:false;4-6,8,10-12:true
Network Configuration Commands
A network configuration command begins with transmission speed, duplex mode, and so on.
network
. A number of network settings can be changed through the CLI, such as the IP address,
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:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Interface ethernet wireless bridge
Description
Determine the IPv4 configuration mode of the
ETHERNET interface (that is, wired networking).
Determine the IPv4 configuration mode of the
WIRELESS interface (that is, wireless networking).
Determine the IPv4 configuration mode of the
BRIDGE interface (that is, bridging mode).
409
410
Chapter 8: Using the Command Line Interface
• <mode> is one of the modes:
dhcp
or
static
.
Mode dhcp
Description
The IPv4 configuration mode is set to DHCP. static The IPv4 configuration mode is set to static IP address.
Setting the IPv4 Preferred Host Name
After selecting DHCP as the IPv4 configuration mode, you can specify the preferred host name, which is optional. The following is the command: config:# network ipv4 interface <ETH> preferredHostName <name>
Variables:
•
<ETH> is one of the network interfaces:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Interface ethernet wireless
Description
Determine the IPv4 preferred host name of the
ETHERNET interface (that is, wired networking).
Determine the IPv4 preferred host name of the
WIRELESS interface (that is, wireless networking). bridge Determine the IPv4 preferred host name of the
BRIDGE interface (that is, bridging mode).
•
<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
Chapter 8: Using the Command Line Interface
Setting the IPv4 Address
After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX3TS device. config:# network ipv4 interface <ETH> address <ip address>
Variables:
• <ETH> is one of the network interfaces:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Interface ethernet wireless
Description
Determine the IPv4 address of the ETHERNET interface (that is, wired networking).
Determine the IPv4 address of the WIRELESS interface (that is, wireless networking). bridge Determine the IPv4 address of the BRIDGE interface (that is, the bridging mode).
• <ip address> is the IP address being assigned to your PX3TS device.
Its format is "IP address/prefix". For example,
192.168.84.99/32
.
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:
•
<ip address> is the IP address of the gateway. The value ranges from
0.0.0.0 to 255.255.255.255.
411
412
Chapter 8: 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 PX3TS 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
Method 1: add a static route when the other network is NOT directly reachable: config:# network ipv4 staticRoutes add <dest-1> <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-2> <hop>
-- OR --
Chapter 8: Using the Command Line Interface config:# network ipv4 staticRoutes modify <route_ID> <dest-2> interface <ETH>
Variables:
•
<dest-1> is a combination of the IP address and subnet mask of the other subnet. The format is
IP address/subnet mask
.
•
<hop> is the IP address of the next hop router.
• <ETH> is one of the interfaces:
ethernet
,
wireless
and
bridge
"bridge" only when your PX3TS is in the bridging mode.
. Type
• <route_ID> is the ID number of the route setting which you want to delete or modify.
•
<dest-2> is a modified route setting that will replace the original route setting. Its format is
IP address/subnet mask
. You can modify either the IP address or the subnet mask or both.
Configuring IPv6 Parameters
An IPv6 configuration command begins with
network ipv6
.
Setting the IPv6 Configuration Mode
This command determines the IP configuration mode. config:# network ipv6 interface <ETH> configMethod <mode>
Variables:
• <ETH> is one of the network interfaces:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Interface ethernet wireless bridge
Description
Determine the IPv6 configuration mode of the
ETHERNET interface (that is, wired networking).
Determine the IPv6 configuration mode of the
WIRELESS interface (that is, wireless networking).
Determine the IPv6 configuration mode of the
BRIDGE interface (that is, bridging mode).
413
414
Chapter 8: Using the Command Line Interface
• <mode> is one of the modes:
automatic
or
static
.
Mode automatic
Description
The IPv6 configuration mode is set to automatic. static The 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 the preferred host name, which is optional. The following is the command: config:# network ipv6 interface <ETH> preferredHostName <name>
Variables:
•
<ETH> is one of the network interfaces:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Interface ethernet wireless
Description
Determine the IPv6 preferred host name of the
ETHERNET interface (that is, wired networking).
Determine the IPv6 preferred host name of the
WIRELESS interface (that is, wireless networking). bridge Determine the IPv6 preferred host name of the
BRIDGE interface (that is, bridging mode).
•
<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
Chapter 8: Using the Command Line Interface
Setting the IPv6 Address
After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX3TS device. config:# network ipv6 interface <ETH> address <ip address>
Variables:
• <ETH> is one of the network interfaces:
ethernet
,
wireless
,
bridge
or
all
. Note that you must choose/configure the bridge interface if your
PX3TS is set to the bridging mode.
Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Interface ethernet wireless
Description
Determine the IPv6 address of the ETHERNET interface (that is, wired networking).
Determine the IPv6 address of the WIRELESS interface (that is, wireless networking). bridge Determine the IPv6 address of the BRIDGE interface (that is, the bridging mode).
• <ip address> is the IP address being assigned to your PX3TS device.
This value uses the IPv6 address format. Note that you must add
/xx
which indicates a prefix length of bits such as /64, to the end of this
IPv6 address.
,
Setting the IPv6 Gateway
After selecting the static IP configuration mode, you can use this command to specify the gateway. config:# network ipv6 gateway <ip address>
Variables:
•
<ip address> is the IP address of the gateway. This value uses the
IPv6 address format.
415
416
Chapter 8: Using the Command Line Interface
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 PX3TS 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
Method 1: add a static route when the other network is NOT directly reachable: config:# network ipv6 staticRoutes add <dest-1> <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-2> <hop>
-- OR --
Chapter 8: Using the Command Line Interface config:# network ipv6 staticRoutes modify <route_ID> <dest-2> interface <ETH>
Variables:
•
<dest-1> is the IP address and prefix length of the subnet where the
PX3TS belongs. The format is
IP address/prefix length
.
•
<hop> is the IP address of the next hop router.
• <ETH> is one of the interfaces:
ethernet
,
wireless
and
bridge
"bridge" only when your PX3TS is in the bridging mode.
. Type
• <route_ID> is the ID number of the route setting which you want to delete or modify.
•
<dest-2> is a modified route setting that will replace the original route setting. Its format is
IP address/prefix length
. You can modify either the IP address or the prefix length or both.
417
418
Chapter 8: Using the Command Line Interface
Configuring DNS Parameters
Use the following commands to configure 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>
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.
• <resolver> is one of the options:
preferV4
or
preferV6.
Option preferV4 preferV6
Description
Use the IPv4 addresses returned by the DNS server.
Use the IPv6 addresses returned by the DNS server.
Setting LAN Interface Parameters
A LAN interface configuration command begins with
network ethernet
.
Chapter 8: Using the Command Line Interface
Enabling or Disabling the LAN Interface
This command enables or disables the LAN interface. config:# network ethernet ETHERNET enabled <option>
Variables:
•
<option> is one of the options:
true or false
.
Option true false
Description
The specified network interface is enabled.
The specified network interface is disabled.
Changing the LAN Interface Speed
This command determines the LAN interface speed. config:# network ethernet ETHERNET speed <option>
Variables:
• <option> is one of the options:
auto
,
10Mbps
, and
100Mbps
.
Option auto
10Mbps
100Mbps
Description
System determines the optimum LAN speed through auto-negotiation.
The LAN speed is always 10 Mbps.
The LAN speed is always 100 Mbps.
419
420
Chapter 8: Using the Command Line Interface
Changing the LAN Duplex Mode
This command determines the LAN interface duplex mode. config:# network ethernet ETHERNET duplexMode <mode>
Variables:
•
<mode> is one of the modes:
auto
,
half
or
full
.
Option auto half full
Description
The PX3TS selects the optimum transmission mode through auto-negotiation.
Half duplex:
Data is transmitted in one direction (to or from the PX3TS device) at a time.
Full duplex:
Data is transmitted in both directions simultaneously.
Setting Wireless Parameters
You must configure wireless parameters, including Service Set Identifier
(SSID), authentication method, Pre-Shared Key (PSK), and Basic Service
Set Identifier (BSSID) after the wireless networking mode is enabled.
A wireless configuration command begins with
network wireless
.
Note: If current networking mode is not wireless, the SSID, PSK and
BSSID values are not applied until the networking mode is changed to
"wireless." In addition, a message appears, indicating that the active network interface is not wireless.
Setting the SSID
This command specifies the SSID string. config:# network wireless SSID <ssid>
Variables:
•
<ssid> is the name of the wireless access point, which consists of:
- Up to 32 ASCII characters
- No spaces
Chapter 8: Using the Command Line Interface
- ASCII codes 0x20 ~ 0x7E
Setting the Authentication Method
This command sets the wireless authentication method to either PSK or
Extensible Authentication Protocol (EAP). config:# network wireless authMethod <method>
Variables:
•
<method> is one of the authentication methods:
PSK
or
EAP
.
Method
PSK
EAP
Description
The wireless authentication method is set to PSK.
The wireless authentication method is set to EAP.
Setting the PSK
If the Pre-Shared Key (PSK) authentication method is selected, you must assign a PSK passphrase by using this command. config:# network wireless PSK <psk>
Variables:
•
<psk> is a string or passphrase that consists of:
- 8 to 63 characters
- No spaces
- ASCII codes 0x20 ~ 0x7E
421
422
Chapter 8: Using the Command Line Interface
Setting EAP Parameters
When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, password, and CA certificate.
Determine the outer authentication protocol: config:# network wireless eapOuterAuthentication <outer_auth>
Determine the inner authentication protocol: 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 PX3TS prompts you to enter the password. Then type the password and press Enter.
Provide a CA TLS certificate: config:# network wireless eapCACertificate
After performing the above command, the system prompts you to enter the CA certificate's contents. For details, see
EAP CA Certificate
Example
Enable or disable verification of the TLS certificate chain: config:# network wireless enableCertVerification <option1>
Allow expired and not yet valid TLS certificates: config:# network wireless allowOffTimeRangeCerts <option2>
Allow wireless network connection with incorrect system time:
Chapter 8: Using the Command Line Interface config:# network wireless allowConnectionWithIncorrectClock <option3>
Variables:
•
The value of <outer_auth> is authentication.
PEAP
because PX3TS only supports
Protected Extensible Authentication Protocol (PEAP) as the outer
• The value of <inner_auth> is
MSCHAPv2
because PX3TS only supports Microsoft's Challenge Authentication Protocol Version 2
(MSCHAPv2) as the inner authentication.
•
<identity> is your user name for the EAP authentication.
•
<option1> is one of the options:
true
or
false
.
Option true
Description
Enables the verification of the TLS certificate chain. false Disables the verification of the TLS certificate chain.
• <option2> is one of the options:
true
or
false
.
Option true
Description
Always make the wireless network connection successful even though the TLS certificate chain contains any certificate which is outdated or not valid yet. false The wireless network connection is NOT successfully established when the TLS certificate chain contains any certificate which is outdated or not valid yet.
• <option3> is one of the options:
true
or
false
.
Option true
Description
Make the wireless network connection successful when the PX3TS system time is earlier than the firmware build before synchronizing with the NTP server, causing the TLS certificate to become invalid.
423
Chapter 8: Using the Command Line Interface
Option false
Description
The wireless network connection is NOT successfully established when the PX3TS finds that the TLS certificate is not valid due to incorrect system time.
EAP CA Certificate Example
This section provides a CA certificate example only. Your CA certificate contents should be different from the contents displayed in this example.
To provide a CA certificate:
1. Make sure you have entered the configuration mode. See
Entering
Configuration Mode
2. Type the following command and press Enter. config:# network wireless eapCACertificate
3. The system prompts you to enter the contents of the CA certificate.
4. Open a CA certificate using a text editor. You should see certificate contents similar to the following.
424
5. Select and copy the contents as illustrated below, excluding the starting line containing "BEGIN CERTIFICATE" and the ending line containing "END CERTIFICATE."
Chapter 8: Using the Command Line Interface
MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk
GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW
NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE
BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw
YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYwNAYDVQ
QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta
W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w
C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA wDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/
A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOH
H21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atOb
EuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZ ita+z4IBO
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:#
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.
Important: When enabling either cascading mode, you must make sure the other cascading mode is disabled, or the preferred
425
426
Chapter 8: Using the Command Line Interface cascading mode may not be enabled successfully.
Mode bridge
Description
The network bridging mode, where each cascaded device is assigned a unique IP address. portForwarding The port forwarding mode, where every cascaded device in the chain shares the same IP address, with diverse port numbers assigned.
• <option1> is one of the following options:
Option true false
Description
The selected cascading mode is enabled.
The selected cascading mode is disabled.
If Port Forwarding mode is enabled, you must configure two more settings to finish the configuration:
On ALL cascaded devices, you must configure the 'role' setting one by one. config:# network portForwarding role <option2>
On the master device, you must configure the 'downstream interface' setting. config:# network portForwarding masterDownstreamInterface <option3>
Variables:
• <option2> is one of the following cascading roles:
Role master slave
Description
The device is a master device.
The device is a slave device.
Chapter 8: Using the Command Line Interface
• <option3> is one of the following options:
Option
Ethernet
Usb
Description
Ethernet port is the port where the 1st slave device is connected.
USB port is the port where the 1st slave device is connected.
Setting Network Service Parameters
A network service command begins with
network services
.
Setting the HTTP Port
The commands used to configure the HTTP port settings begin with
network services http
.
Change the HTTP port: config:# network services http port <n>
Enable or disable the HTTP port: config:# network services http enabled <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
.
Option true false
Description
The HTTP port is enabled.
The HTTP port is disabled.
427
428
Chapter 8: Using the Command Line Interface
Setting the HTTPS Port
The commands used to configure the HTTPS port settings begin with
network services https
.
Change the HTTPS port: config:# network services https port <n>
Enable or disable the HTTPS access: config:# network services https enabled <option>
Variables:
•
<n> is a TCP port number between 1 and 65535. The default HTTPS port is 443.
•
<option> is one of the options:
true
or
false
.
Option true false
Description
Forces any access to the PX3TS via HTTP to be redirected to HTTPS.
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:
•
<option> is one of the options:
true
or
false
.
Option true
Description
The Telnet service is enabled.
Chapter 8: Using the Command Line Interface
Option false
Description
The Telnet service is disabled.
Changing the Telnet Port
This command changes the Telnet port. config:# network services telnet port <n>
Variables:
•
<n> is a TCP port number between 1 and 65535. The default Telnet port is 23.
Changing the SSH Configuration
You can enable or disable the SSH service, or change its TCP port using the CLI commands.
An SSH command begins with
network services ssh
.
Enabling or Disabling SSH
This command enables or disables the SSH service. config:# network services ssh
enabled <option>
Variables:
•
<option> is one of the options:
true
or
false
.
Option true false
Description
The SSH service is enabled.
The SSH service is disabled.
Changing the SSH Port
This 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.
429
430
Chapter 8: 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
.
Option passwordOnly
Description
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
Setting the SNMP Configuration
You can enable or disable the SNMP v1/v2c or v3 agent, configure the read and write community strings, or set the MIB-II parameters, such as sysContact, using the CLI commands.
An SNMP command begins with
network services snmp
.
Enabling or Disabling SNMP v1/v2c
This command enables or disables the SNMP v1/v2c protocol. config:# network services snmp v1/v2c <option>
Variables:
•
<option> is one of the options:
enable
or
disable
.
Option enable disable
Description
The SNMP v1/v2c protocol is enabled.
The SNMP v1/v2c protocol is disabled.
Chapter 8: 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
.
Option enable disable
Description
The SNMP v3 protocol is enabled.
The SNMP v3 protocol is disabled.
Setting the SNMP Read Community
This command sets the SNMP read-only community string. config:# network services snmp readCommunity <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.
431
432
Chapter 8: 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:
• <option> is one of the options:
true
or
false
.
Option true false
Description
The Modbus agent is enabled.
The Modbus agent is disabled.
Chapter 8: 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
.
Option true false
Description
The read-only mode is enabled.
The read-only mode is disabled.
Changing the Modbus Port
This 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 Advertising
This command enables or disables the zero configuration protocol, which enables advertising or auto discovery of network services. See
Enabling Service Advertising
config:# network services zeroconfig enabled <option>
Variables:
•
<option> is one of the options:
true
or
false
.
Option true false
Description
The zero configuration protocol is enabled.
The zero configuration protocol is disabled.
433
434
Chapter 8: Using the Command Line Interface
Examples
This section illustrates several network configuration examples.
Example 1 - Networking Mode
The following command enables the wired networking mode. config:# network mode wired
Example 2 - Enabling Both IP Protocols
The following command determines that both IPv4 and IPv6 protocols are enabled. config:# network ip proto both
Example 3 - Wireless Authentication Method
The following command sets the wireless authentication method to PSK. config:# network wireless authMethod PSK
Example 4 - Static IPv4 Configuration
The following command enables the Static IP configuration mode. config:# network ipv4 ipConfigurationMode static
Time Configuration Commands
A time configuration command begins with
time
.
Chapter 8: 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 manual ntp
Description
The date and time settings are customized.
The date and time settings synchronize with a specified NTP server.
Setting NTP Parameters
A time configuration command that is used to set the NTP parameters begins with
time ntp
.
Specifying the Primary NTP Server
This command specifies the primary time server if synchronization with the NTP server is enabled. config:# time ntp firstServer <first_server>
Variables:
• The <first_server> is the IP address or host name of the primary NTP server.
Specifying the Secondary NTP Server
This command specifies the primary time server if synchronization with the NTP server is enabled. config:# time ntp secondServer <second_server>
Variables:
•
The <second_server> is the IP address or host name of the secondary NTP server.
435
436
Chapter 8: Using the Command Line Interface
Overriding DHCP-Assigned NTP Servers
This command determines whether the customized NTP server settings override the DHCP-specified NTP servers. config:# time ntp overrideDHCPProvidedServer <option>
Variables:
• <option> is one of these options:
true
or
false
.
Mode true false
Description
Customized NTP server settings override the
DHCP-specified NTP servers.
Customized NTP server settings do NOT override the DHCP-specified NTP servers.
Deleting an NTP Server
The following commands delete the primary and/or secondary time server(s).
To delete the primary time server: config:# time ntp firstServer ""
To delete the secondary time server: config:# time ntp secondServer ""
Setting the Time Zone
The CLI has a list of time zones to configure the date and time for the
PX3TS. config:# time zone
After a list of time zones is displayed, type the index number of the time zone or press Enter to cancel.
Chapter 8: Using the Command Line Interface
Example
To set the time zone:
1. Type the time zone command as shown below and press Enter. config:# time zone
2. The system shows a list of time zones. Type the index number of the desired time zone and press Enter.
3. Type apply for the selected time zone to take effect.
Customizing the Date and Time
If intending to manually configure the date and time, use the following
CLI commands to specify them.
Note: You shall set the time configuration method to "manual" prior to customizing the date and time. See
Determining the Time Setup
Method
(on page 435).
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.
2015-11-30
for November 30,
<hh:mm:ss> Type the time in the format of hh:mm:ss in the
24-hour format.
For example, type
13:50:20
for 1:50:20 pm.
437
438
Chapter 8: Using the Command Line Interface
Setting the Automatic Daylight Savings Time
This command determines whether the daylight savings time is applied to the time settings. config:# time autoDST <option>
Variables:
• <option> is one of the options:
enable
or
disable
.
Mode enable disable
Description
Daylight savings time is enabled.
Daylight savings time is disabled.
Examples
This section illustrates several time configuration examples.
Example 1 - Time Setup Method
The following command sets the date and time settings by using the NTP servers. config:# time method ntp
Example 2 - Primary NTP Server
The following command sets the primary time server to 192.168.80.66. config:# time ntp firstServer 192.168.80.66
Chapter 8: Using the Command Line Interface
Checking the Accessibility of NTP Servers
This command verifies the accessibility of NTP servers specified manually on your PX3TS and then shows the result. For instructions on specifying NTP servers via CLI, see
Setting NTP Parameters
(on page
To perform this command successfully, you must:
• Own the "Change Date/Time Settings" permission.
• Customize NTP servers. See
Setting NTP Parameters
(on page
•
Make the customized NTP servers override the DHCP-assigned ones.
See
Overriding DHCP-Assigned NTP Servers
This command is available either in the administrator/user mode or in the configuration mode. See
Different CLI Modes and Prompts
(on page
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 PX3TS device from a specific or a range of IP addresses.
•
An IPv4 firewall configuration command begins with
security ipAccessControl ipv4
.
• An IPv6 firewall configuration command begins with
security ipAccessControl ipv6
.
439
440
Chapter 8: Using the Command Line Interface
Modifying Firewall Control Parameters
There are different commands for modifying firewall control parameters.
•
IPv4 commands
Enable or disable the IPv4 firewall control feature: config:# security ipAccessControl ipv4 enabled <option>
Determine the default IPv4 firewall control policy for inbound traffic: config:# security ipAccessControl ipv4 defaultPolicyIn <policy>
Determine the default IPv4 firewall control policy for outbound traffic: config:# security ipAccessControl ipv4 defaultPolicyOut <policy>
•
IPv6 commands
Enable or disable the IPv6 firewall control feature: config:# security ipAccessControl ipv6 enabled <option>
Determine the default IPv6 firewall control policy for inbound traffic: config:# security ipAccessControl ipv6 defaultPolicyIn <policy>
Determine the default IPv6 firewall control policy for outbound traffic: config:# security ipAccessControl ipv6 defaultPolicyOut <policy>
Variables:
• <option> is one of the options:
true
or
false
.
Option true
Description
Enables the IP access control feature.
Chapter 8: Using the Command Line Interface
Option false
Description
Disables the IP access control feature.
•
<policy> is one of the options:
accept, drop
or
reject
.
Option accept drop reject
Description
Accepts traffic from all IP addresses.
Discards traffic from all IP addresses, without sending any failure notification to the source host.
Discards traffic from all IP addresses, and an
ICMP message is sent to the source host for failure notification.
Tip: You can combine both commands to modify all firewall control parameters at a time. See
Multi-Command Syntax
(on page 515).
Managing Firewall Rules
You can add, delete or modify firewall rules using the CLI commands.
• An IPv4 firewall control rule command begins with
security ipAccessControl ipv4 rule
.
• An IPv6 firewall control rule command begins with
security ipAccessControl ipv6 rule
.
Adding a Firewall Rule
Depending on where you want to add a new firewall rule in the list, the command for adding a rule varies.
•
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 --
441
442
Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add <direction> <insert> <rule_number>
<ip_mask> <policy>
•
IPv6 commands
Add a new rule to the bottom of the IPv6 rules list: config:# security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy>
Add a new IPv6 rule by inserting it above or below a specific rule: config:# security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy>
<insert> <rule_number>
-- OR -- config:# security ipAccessControl ipv6 rule add <direction> <insert> <rule_number>
<ip_mask> <policy>
Variables:
• <direction> is one of the options:
in
or
out
.
Direction in
Description
Inbound traffic. out Outbound traffic.
•
<ip_mask> is the combination of the IP address and subnet mask values (or prefix length), which are separated with a slash. For example, an IPv4 combination looks like this:
192.168.94.222/24
.
•
<policy> is one of the options:
accept, drop
or
reject
.
Policy accept drop reject
Description
Accepts traffic from/to the specified IP address(es).
Discards traffic from/to the specified IP address(es), without sending any failure notification to the source or destination host.
Discards traffic from/to the specified IP address(es), and an ICMP message is sent to the source or destination host for failure notification.
Chapter 8: Using the Command Line Interface
• <insert> is one of the options:
insertAbove
or
insertBelow
.
Option insertAbove
Description
Inserts the new rule above the specified rule number. Then:
new rule's number = the specified rule number
insertBelow Inserts the new rule below the specified rule number. Then:
new rule's number = the specified rule number +
1
• <rule_number> is the number of the existing rule which you want to insert the new rule above or below.
Modifying a Firewall Rule
Depending on what to modify in an existing rule, the command varies.
•
IPv4 commands
Modify an IPv4 rule's IP address and/or subnet mask: config:# security ipAccessControl ipv4 rule modify <direction> <rule_number> ipMask
<ip_mask>
Modify an IPv4 rule's policy: config:# security ipAccessControl ipv4 rule modify <direction> <rule_number> policy
<policy>
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:
443
444
Chapter 8: Using the Command Line Interface 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 in
Description
Inbound traffic. out Outbound traffic.
• <rule_number> is the number of the existing rule that you want to modify.
• <ip_mask> is the combination of the IP address and subnet mask values (or prefix length), which 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
.
Option accept drop reject
Description
Accepts traffic from/to the specified IP address(es).
Discards traffic from/to the specified IP address(es), without sending any failure notification to the source or destination host.
Discards traffic from/to the specified IP address(es), and an ICMP message is sent to the source or destination host for failure notification.
Deleting a Firewall Rule
The following commands remove a specific IPv4 or IPv6 rule from the list.
IPv4 commands
Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule delete <direction> <rule_number>
IPv6 commands config:# security ipAccessControl ipv6 rule delete <direction> <rule_number>
Variables:
•
<direction> is one of the options:
in
or
out
.
Direction in
Description
Inbound traffic. out Outbound traffic.
• <rule_number> is the number of the existing rule that you want to remove.
Restricted Service Agreement
The CLI command used to set the Restricted Service Agreement feature begins with security restrictedServiceAgreement,
Enabling or Disabling the Restricted Service Agreement
This command activates or deactivates the Restricted Service
Agreement. config:# security restrictedServiceAgreement enabled <option>
Variables:
•
<option> is one of the options:
true
or
false
.
Option true false
Description
Enables the Restricted Service Agreement feature.
Disables the Restricted Service Agreement feature.
445
446
Chapter 8: Using the Command Line Interface
After the Restricted Service Agreement feature is enabled, the agreement's content is displayed in 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 and accept the Restricted Service Agreement" is displayed.
Specifying the Agreement Contents
This command allows you to create or modify contents of the Restricted
Service Agreement. config:# security restrictedServiceAgreement bannerContent
After performing the above command, do the following:
1. Type the text comprising up to 10,000 ASCII characters when the CLI prompts you to enter the content.
2. To end the content: a. Press Enter. b. Type --END-- to indicate the end of the content. c. Press Enter again.
If the content is successfully entered, the CLI displays this message
"Successfully entered Restricted Service Agreement" followed by the total number of entered characters in parentheses.
Note: The new content of Restricted Service Agreement is saved only after typing the
apply
command. See
Quitting Configuration Mode
(on
page 396).
Example
The following example illustrates how to specify the content of the
Restricted Service Agreement.
1. Type the following command and press Enter to start entering the content. config:# security restrictedServiceAgreement bannerContent
2. Type the following content when the CLI prompts you to enter the content.
Chapter 8: Using the Command Line Interface
IMPORTANT!! You are accessing a PDU. If you are not the system administrator, do NOT power off or power cycle any outlet without the permission of the system administrator.
3. Press Enter.
4. Type the following:
--END--
5. Press Enter again.
6. Verify that the message "Successfully entered Restricted Service
Agreement" is displayed, indicating that the content input is successful.
Login Limitation
The login limitation feature controls login-related limitations, such as password aging, simultaneous logins using the same user name, and the idle time permitted before forcing a user to log out.
A login limitation command begins with
security loginLimits
.
You can combine multiple commands to modify various login limitation parameters at a time. See
Multi-Command Syntax
Single Login Limitation
This command enables or disables the single login feature, which controls whether multiple logins using the same login name simultaneously is permitted. config:# security loginLimits singleLogin <option>
Variables:
•
<option> is one of the options:
enable
or
disable
.
Option enable disable
Description
Enables the single login feature.
Disables the single login feature.
447
448
Chapter 8: Using the Command Line Interface
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:
• <option> is one of the options:
enable
or
disable
.
Option enable disable
Description
Enables the password aging feature.
Disables the password aging feature.
Password Aging Interval
This command determines how often the password should be changed. config:# security loginLimits passwordAgingInterval <value>
Variables:
• <value> is a numeric value in days set for the password aging interval. The interval ranges from 7 to 365 days.
Idle Timeout
This command determines how long a user can remain idle before that user is forced to log out of the PX3TS 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).
Chapter 8: Using the Command Line Interface config:#
User Blocking
There are different commands for changing different user blocking parameters. These commands begin with security userBlocking.
You can combine multiple commands to modify the user blocking parameters at a time. See
Multi-Command Syntax
Determine the maximum number of failed logins before blocking a user: 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 user blocking function.
unlimited
, which sets no limit on the maximum number of failed logins and thus disables the
•
<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.
Strong Passwords
The strong password commands determine whether a strong password is required for login, and what a strong password should contain at least.
A strong password command begins with security strongPasswords
.
You can combine multiple strong password commands to modify different parameters at a time. See
Multi-Command Syntax
(on page
449
450
Chapter 8: Using the Command Line Interface
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
. config:#
Option true false
Description
Enables the strong password feature.
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 a lowercase character. security strongPasswords enforceAtLeastOneLowerCaseCharacter <option>
Variables:
•
<option> is one of the options:
enable
or
disable
.
Option enable
Description
At least one lowercase character is required.
Chapter 8: Using the Command Line Interface
Option disable
Description
No lowercase character is required.
Uppercase Character Requirement
This command determines whether a strong password includes at least a uppercase character. config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter <option>
Variables:
•
<option> is one of the options:
enable
or
disable
.
Option enable disable
Description
At least one uppercase character is required.
No uppercase character is required.
Numeric Character Requirement
This command determines whether a strong password includes at least a numeric character. config:# security strongPasswords enforceAtLeastOneNumericCharacter <option>
Variables:
• <option> is one of the options:
enable
or
disable
.
Option enable disable
Description
At least one numeric character is required.
No numeric character is required.
Special Character Requirement
This command determines whether a strong password includes at least a special character.
451
452
Chapter 8: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option>
Variables:
•
<option> is one of the options:
enable
or
disable
.
Option enable disable
Description
At least one special character is required.
No special character is required.
Maximum Password History
This command determines the number of previous passwords that
CANNOT be repeated when changing the password. config:# security strongPasswords passwordHistoryDepth <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: config:# security roleBasedAccessControl ipv4 enabled <option>
Determine the IPv4 role-based access control policy:
Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>
•
IPv6 commands
config:#
Enable or disable the IPv6 role-based access control feature: 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
.
Option true
Description
Enables the role-based access control feature. false Disables the role-based access control feature.
• <policy> is one of the options:
allow
or
deny
.
Policy allow deny
Description
Accepts traffic from all IP addresses regardless of the user's role.
Drops traffic from all IP addresses regardless of the user's role.
Tip: You can combine both commands to modify all role-based access control parameters at a time. See
Multi-Command Syntax
(on page
515).
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
.
453
454
Chapter 8: Using the Command Line Interface
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: config:#
security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role>
<policy> <insert> <rule_number>
Variables:
• <start_ip> is the starting IP address.
• <end_ip> is the ending IP address.
•
<role> is the role for which you want to create an access control rule.
•
<policy> is one of the options:
allow
or
deny
.
Policy allow deny
Description
Accepts traffic from the specified IP address range when the user is a member of the specified role
Drops traffic from the specified IP address range when the user is a member of the specified role
Chapter 8: Using the Command Line Interface
• <insert> is one of the options:
insertAbove
or
insertBelow
.
Option insertAbove
Description
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: 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:
455
456
Chapter 8: Using the Command Line Interface 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: config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy
<policy>
Variables:
•
<rule_number> is the number of the existing rule that you want to modify.
•
<start_ip> is the starting IP address.
• <end_ip> is the ending IP address.
• <role> is one of the existing roles.
• <policy> is one of the options:
allow
or
deny
.
Policy allow
Description
Accepts traffic from the specified IP address range when the user is a member of the specified role
Chapter 8: Using the Command Line Interface
Policy deny
Description
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 to remove.
Enabling or Disabling Front Panel Outlet Switching
This section applies to outlet-switching capable models only.
The following CLI commands control whether you can turn on or off an outlet by operating the front panel display.
To enable the front panel outlet control feature: config:# security frontPanelPermissions add switchOutlet
To disable the front panel outlet control feature: config:# security frontPanelPermissions remove switchOutlet
Examples
This section illustrates several security configuration examples.
457
458
Chapter 8: 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 192.168.84.123/24 accept insertAbove 5
Results:
•
A new IPv4 firewall control rule is added to accept all packets sent from the IPv4 address 192.168.84.123.
• The newly-added rule is inserted above the 5th rule. That is, the new rule becomes the 5th rule, and the original 5th rule becomes the 6th rule.
Example 3 - User Blocking
The following command sets up two user blocking parameters. config:# security userBlocking maximumNumberOfFailedLogins 5 blockTime 30
Results:
• The maximum number of failed logins is set to 5.
•
The user blocking time is set to 30 minutes.
Chapter 8: Using the Command Line Interface
Example 4 - Adding an IPv4 Role-based Access Control Rule
The following command creates a newIPv4 role-based access control rule and specifies its location in the list. config:# security roleBasedAccessControl ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertAbove 3
Results:
•
A new IPv4 role-based access control rule is added, dropping all packets from any IPv4 address between 192.168.78.50 and
192.168.90.100 when the user is a member of the role "admin."
• The newly-added IPv4 rule is inserted above the 3rd rule. That is, the new rule becomes the 3rd rule, and the original 3rd rule becomes the 4th rule.
Outlet Configuration Commands
An outlet configuration command begins with allows you to configure an individual outlet.
outlet
. Such a command
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 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
459
460
Chapter 8: Using the Command Line Interface
Changing an Outlet's Default State
This section applies to outlet-switching capable models only.
This command determines the initial power condition of an outlet after the PX3TS powers up. config:# outlet <n> stateOnDeviceStartup <option>
Variables:
•
<n> is the number of the outlet that you want to configure.
•
<option> is one of the options:
off
,
on, lastKnownState
and
pduDefined.
Option off
Description
Turn off the outlet. on Turn on the outlet. lastKnownState Restore the outlet to the state prior to last PDU power down. pduDefined PDU-defined setting.
Note: Setting the outlet's default state to an option other than
pduDefined
overrides the PDU-defined default state on that outlet. See
Setting the PDU-Defined Default Outlet State
(on page 403).
Chapter 8: Using the Command Line Interface
Setting an Outlet's Cycling Power-Off Period
This section applies to outlet-switching capable models only.
This command determines the power-off period of the power cycling operation for a specific outlet. config:# outlet <n> cyclingPowerOffPeriod <timing>
Variables:
•
<n> is the number of the outlet that you want to configure.
•
<timing> is the time of the cycling power-off period in seconds, which is an integer between 0 and 3600, or the PDU-defined timing.
pduDefined
for following
Note: This setting overrides the PDU-defined cycling power-off period on a particular outlet. See
Setting the PDU-Defined Cycling Power-Off
Period
(on page 404).
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
inlet by using the inlet configuration command.
. You can configure an
461
462
Chapter 8: 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 the number 1. The value is an integer between 1 and 50.
•
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
Example - Inlet Naming
The following command assigns the name "AC source" to the inlet 1. If your PX3TS device contains multiple inlets, this command names the 1st inlet. config:# inlet 1 name "AC source"
Overcurrent Protector Configuration Commands
An overcurrent protector configuration command begins with
ocp.
The command configures an individual circuit breaker or fuse which protects outlets.
Chapter 8: Using the Command Line Interface
Changing the Overcurrent Protector Name
This command names a circuit breaker or a fuse which protects outlets on your PX3TS. 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 32 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 password change command.
user
except for the
Creating a User Profile
This command creates a new user profile. config:# user create <name> <option> <roles>
After performing the user creation command, the PX3TS prompts you to assign a password to the newly-created user. Then:
1. Type the password and press Enter.
2. Re-type the same password for confirmation and press Enter.
463
464
Chapter 8: 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
.
Option enable
Description
Enables the newly-created user profile. disable Disables the newly-created user profile.
•
<roles> is a role or a list of comma-separated roles assigned to the specified user profile.
Modifying a User Profile
A user profile contains various parameters that you can modify.
Tip: You can combine all commands to modify the parameters of a specific user profile at a time. See
Multi-Command Syntax
(on page
515).
Changing a User's Password
This command allows you to change an existing user's password if you have the Administrator Privileges. config:# user modify <name> password
After performing the above command, PX3TS 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.
Example
The following procedure illustrates how to change the password of the user "May."
1. Verify that you have entered the configuration mode. See
Entering
Configuration Mode
Chapter 8: 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 specific user profile at a time. See
Multi-Command Syntax
(on page
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:
•
<name> is the name of the user whose settings you want to change.
•
<full_name> is a string comprising up to 32 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.
465
466
Chapter 8: 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
PX3TS device 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
.
Option true false
Description
Enables the specified user profile.
Disables the specified user profile.
Forcing a Password Change
This command determines whether the password change is forced when a user logs in to the specified user profile next time. config:# user modify <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
.
Option true false
Description
A password change is forced on the user's next login.
No password change is forced on the user's next login.
Chapter 8: Using the Command Line Interface
Modifying SNMPv3 Settings
There are different commands to modify the SNMPv3 parameters of a specific user profile. You can combine all of the following commands to modify the SNMPv3 parameters at a time. See
Multi-Command Syntax
Enable or disable the SNMP v3 access to PX3TS for the specified user: config:# user modify <name> snmpV3Access <option1>
Variables:
•
<name> is the name of the user whose settings you want to change.
•
<option1> is one of the options:
enable
or
disable
.
Option enable disable
Description
Enables the SNMP v3 access permission for the specified user.
Disables the SNMP v3 access permission for the specified user.
Determine the security level: config:# user modify <name> securityLevel <option2>
Variables:
• <name> is the name of the user whose settings you want to change.
• <option2> is one of the options:
noAuthNoPriv
,
authNoPriv
or
authPriv
.
Option Description noAuthNoPriv No authentication and no privacy. authNoPriv Authentication and no privacy. authPriv Authentication and privacy.
Determine whether the authentication passphrase is identical to the password:
467
468
Chapter 8: Using the Command Line Interface config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3>
Variables:
•
<name> is the name of the user whose settings you want to change.
•
<option3> is one of the options:
true
or
false
.
Option true false
Description
Authentication passphrase is identical to the password.
Authentication passphrase is different from the password. config:#
Determine the authentication passphrase: user modify <name> authenticationPassPhrase <authentication_passphrase>
Variables:
•
<name> is the name of the user whose settings you want to change.
• <authentication_passphrase> is a string used as an authentication passphrase, comprising 8 to 32 ASCII printable characters.
Determine whether the privacy passphrase is identical to the authentication passphrase: config:# user modify <name> useAuthenticationPassPhraseAsPrivacyPassPhrase
<option4>
Variables:
• <name> is the name of the user whose settings you want to change.
• <option4> is one of the options:
true
or
false
.
Option true false
Description
Privacy passphrase is identical to the authentication passphrase.
Privacy passphrase is different from the authentication passphrase.
Chapter 8: Using the Command Line Interface
Determine the privacy passphrase: config:# user modify <name> privacyPassPhrase <privacy_passphrase>
Variables:
•
<name> is the name of the user whose settings you want to change.
• <privacy_passphrase> is a string used as a privacy passphrase, comprising 8 to 32 ASCII printable characters.
Determine the authentication protocol: config:# user modify <name> authenticationProtocol <option5>
Variables:
• <name> is the name of the user whose settings you want to change.
• <option5> is one of the options:
MD5
or
SHA-1
.
Option
MD5
SHA-1
Description
MD5 authentication protocol is applied.
SHA-1 authentication protocol is applied.
Determine the privacy protocol: config:# user modify <name> privacyProtocol <option6>
Variables:
• <name> is the name of the user whose settings you want to change.
• <option6> is one of the options:
DES
or
AES-128
.
Option
DES
AES-128
Description
DES privacy protocol is applied.
AES-128 privacy protocol is applied.
469
470
Chapter 8: Using the Command Line Interface
Changing the Role(s)
This command changes the role(s) of a specific user. config:# user modify <name> roles <roles>
Variables:
•
<name> is the name of the user whose settings you want to change.
• <roles> is a role or a list of comma-separated roles assigned to the specified user profile. See
All Privileges
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
Note: The measurement unit change only applies to the web interface and command line interface.
Tip: To set the default measurement units applied to the PX3TS user interfaces for all users via CLI, see
Setting Default Measurement Units
(on page 473).
Set the preferred temperature unit: config:# user modify <name> preferredTemperatureUnit <option1>
Variables:
• <name> is the name of the user whose settings you want to change.
• <option1> is one of the options:
C
or
F
.
Option
C
F
Description
This option displays the temperature in Celsius.
This option displays the temperature in
Fahrenheit.
Chapter 8: Using the Command Line Interface
Set the preferred length unit: config:# user modify <name> preferredLengthUnit <option2>
Variables:
•
<name> is the name of the user whose settings you want to change.
•
<option2> is one of the options:
meter
or
feet
.
Option meter feet
Description
This option displays the length or height in meters.
This option displays the length or height in feet.
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.
• <option3> is one of the options:
pascal
or
psi
.
Option pascal psi
Description
This option displays the pressure value in Pascals
(Pa).
This option displays the pressure value in psi.
Specifying the SSH Public Key
If the SSH key-based authentication is enabled, specify the SSH public key for each user profile using the following procedure.
To specify or change the SSH public key for a specific user:
1. Type the SSH public key command as shown below and press Enter. config:# user modify <name> sshPublicKey
2. The system prompts you to enter the contents of the SSH public key.
Do the following to input the contents: a. Open your SSH public key with a text editor. b. Copy all contents in the text editor. c. Paste the contents into the terminal.
471
472
Chapter 8: Using the Command Line Interface d. Press Enter.
To remove an existing SSH public key:
1. Type the same command as shown above.
2. When the system prompts you to input the contents, press Enter without typing or pasting anything.
Example
The following procedure illustrates how to change the SSH public key for the user "assistant."
1. Verify that you have entered the configuration mode. See
Entering
Configuration Mode
2. Type the following command and press Enter. config:# user modify assistant sshPublicKey
3. You are prompted to enter a new SSH public key.
4. Type the new key and press Enter.
Deleting a User Profile
This command deletes an existing user profile. config:# user delete <name>
Changing Your Own Password
Every user can change their own password via this command if they have the Change Own Password privilege. Note that this command does not begin with
user
. config:# password
After performing this command, the PX3TS prompts you to enter both current and new passwords respectively.
Important: After the password is changed successfully, the new password is effective immediately no matter you type the command
"apply" or not to save the changes.
Example
This procedure changes your own password:
1. Verify that you have entered the configuration mode. See
Entering
Configuration Mode
2. Type the following command and press Enter.
Chapter 8: Using the Command Line Interface config:# password
3. Type the existing password and press Enter when the following prompt appears.
Current password:
4. Type the new password and press Enter when the following prompt appears.
Enter new password:
5. Re-type the new password for confirmation and press Enter when the following prompt appears.
Re-type new password:
Setting Default Measurement Units
Default measurement units, including temperature, length, and pressure units, apply to the PX3TS user interfaces across all users except for those whose preferred measurement units are set differently by themselves or the administrator. Diverse measurement unit commands can be combined so that you can set all default measurement units at a time. To combine all commands, see
Multi-Command Syntax
(on page
Note: The measurement unit change only applies to the web interface and command line interface.
Tip: To change the preferred measurement units displayed in the PX3TS user interfaces for a specific user via CLI, see
Changing Measurement
Units
(on page 470).
Set the default temperature unit: config:# user defaultpreferences preferredTemperatureUnit <option1>
Variables:
• <option1> is one of the options:
C
or
F
.
Option
C
F
Description
This option displays the temperature in Celsius.
This option displays the temperature in
Fahrenheit.
Set the default length unit:
473
474
Chapter 8: Using the Command Line Interface config:# user defaultpreferences preferredLengthUnit <option2>
Variables:
•
<option2> is one of the options:
meter
or
feet
.
Option meter feet
Description
This option displays the length or height in meters.
This option displays the length or height in feet.
Set the default pressure unit: config:# user defaultpreferences preferredPressureUnit <option3>
Variables:
• <option3> is one of the options:
pascal
or
psi
.
Option pascal psi
Description
This option displays the pressure value in Pascals
(Pa).
This option displays the pressure value in psi.
Examples
This section illustrates several user configuration examples.
Chapter 8: Using the Command Line Interface
Example 1 - Creating a User Profile
The following command creates a new user profile and sets two parameters for the new user. config:# user create May enable admin
Results:
• A new user profile "May" is created.
• The new user profile is enabled.
•
The admin role is assigned to the new user profile.
Example 2 - Modifying a User's Roles
The following command assigns two roles to the user "May." config:# user modify May roles admin,tester
Results:
•
The user May has the union of all privileges of "admin" and "tester."
Example 3 - Default Measurement Units
The following command sets all default measurement units at a time. config:# user defaultpreferences preferredTemperatureUnit F preferredLengthUnit feet preferredPressureUnit psi
Results:
• The default temperature unit is set to Fahrenheit.
• The default length unit is set to feet.
• The default pressure unit is set to psi.
475
476
Chapter 8: 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 the privileges assigned to the role. Separate each privilege with a semi-colon. See
All Privileges
• <argument1>, <argument2> and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.
All Privileges
This table lists all privileges. Note that available privileges vary according to the model you purchased. For example, a PX3TS device without the outlet switching function does not have the privilege
"switchOutlet."
Privilege acknowledgeAlarms adminPrivilege changeAssetStripConfiguration
Description
Acknowledge Alarms
Administrator Privileges
Change Asset Strip
Configuration
Chapter 8: Using the Command Line Interface
Privilege changeAuthSettings
Description
Change Authentication Settings changeDataTimeSettings Change Date/Time Settings changeExternalSensorsConfiguration Change Peripheral Device
Configuration changeLhxConfiguration changeModemConfiguration changeNetworkSettings
Change LHX/SHX Configuration
Change Modem Configuration
Change Network Settings changePassword changePduConfiguration changeSecuritySettings changeSnmpSettings changeUserSettings
Change Own Password
Change Pdu, Inlet, Outlet &
Overcurrent Protector
Configuration
Change Security Settings
Change SNMP Settings
Change Local User
Management changeWebcamSettings clearLog firmwareUpdate performReset switchOutlet* switchActuator** switchTransferSwitch viewEventSetup viewEverything viewLog viewSecuritySettings viewSnmpSettings viewUserSettings viewWebcamSettings
Change Webcam Configuration
Clear Local Event Log
Firmware Update
Reset (Warm Start)
Switch Outlet
Switch Actuator
Switch Transfer Switch
View Event Settings
Unrestricted View Privileges
View Local Event Log
View Security Settings
View SNMP Settings
View Local User Management
View Webcam Snapshots and
Configuration
477
478
Chapter 8: Using the Command Line Interface
* The "switchOutlet" privilege requires an argument that is separated with a colon. The argument could be:
• All outlets, that is, switchOutlet:all
• An outlet number. For example: switchOutlet:1 switchOutlet:2 switchOutlet:3
•
A list of comma-separated outlets. For example: switchOutlet:1,3,5,7,8,9
** The "switchActuator" privilege requires an argument that is separated with a colon. The argument could be:
•
All actuators, that is, switchActuator:all
•
An actuator's ID number. For example: switchActuator:1 switchActuator:2 switchActuator:3
•
A list of comma-separated ID numbers of different actuators. For example: switchActuator:1,3,6
Note: The ID number of each actuator is shown in the PX3TS web interface. It is an integer between 1 and 32.
Chapter 8: Using the Command Line Interface
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>"
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.
Add more privileges to a specific role: config:# role modify <name> addPrivileges
<privilege1>;<privilege2>;<privilege3>...
If a specific privilege contains any arguments, add a colon and the argument(s) after that privilege.
479
480
Chapter 8: Using the Command Line Interface config:# role modify <name> addPrivileges
<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 the privileges assigned to the role. Separate each privilege with a semi-colon. See
All Privileges
• <argument1>, <argument2> and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.
Remove specific privileges from a role: config:# role modify <name> removePrivileges
<privilege1>;<privilege2>;<privilege3>...
If a specific privilege contains any arguments, add a colon and the argument(s) after that privilege. config:# role modify <name> removePrivileges
<privilege1>:<argument1>,<argument2>...;
<privilege2>:<argument1>,<argument2>...;
<privilege3>:<argument1>,<argument2>...;
...
Note: When removing privileges from a role, make sure the specified privileges and arguments (if any) exactly match those assigned to the role. Otherwise, the command fails to remove specified privileges that are not available.
Variables:
• <name> is a string comprising up to 32 ASCII printable characters.
•
<privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See
All Privileges
•
<argument1>, <argument2> and the like are arguments set for a particular privilege. Separate a privilege and its argument(s) with a colon, and separate arguments with a comma if there are more than one argument for a privilege.
Chapter 8: Using the Command Line Interface
Deleting a Role
This command deletes an existing role. config:# role delete <name>
Example - Creating a Role
The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup
Results:
•
A new role "tester" is created.
•
Two privileges are assigned to the role: firmwareUpdate (Firmware
Update) and viewEventSetup (View Event Settings).
Environmental Sensor Configuration Commands
An environmental sensor configuration command begins with
externalsensor
. You can configure the name and location parameters of an individual environmental sensor.
Note: To configure an actuator, see
Actuator Configuration Commands
(on page 499).
481
482
Chapter 8: Using the Command Line Interface
Changing the Sensor Name
This command names an environmental sensor. config:# externalsensor <n> name "<name>"
Variables:
•
<n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
•
<name> is a string comprising up to 32 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 499).
Specifying the CC Sensor Type
Raritan's contact closure sensor (DPX-CC2-TR) supports the connection of diverse third-party or Raritan's detectors/switches. You must specify the type of connected detector/switch for proper operation. Use this command when you need to specify the sensor type. config:# externalsensor <n> sensorSubType <sensor_type>
Variables:
•
<n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
• <sensor_type> is one of these types:
contact
,
smokeDetection
,
waterDetection
or
vibration
.
Type contact
Description
The connected detector/switch is for detection of door lock or door closed/open status. smokeDetection The connected detector/switch is for detection of the smoke presence. waterDetection The connected detector/switch is for detection of the water presence.
Chapter 8: Using the Command Line Interface
Type vibration
Description
The connected detector/switch is for detection of the vibration.
Setting the X Coordinate
This command specifies the X coordinate of an environmental sensor. config:# externalsensor <n> xlabel "<coordinate>"
Variables:
• <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
•
<coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
Setting the Y Coordinate
This command specifies the Y coordinate of an environmental sensor. config:# externalsensor <n> ylabel "<coordinate>"
Variables:
•
<n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
• <coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
483
484
Chapter 8: 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 to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
•
Depending on the Z coordinate format you set, there are two types of values for the <coordinate> variable:
Type
Free form
Description
<coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
<coordinate> is an integer number in rack units. Rack units
Note: To specify the Z coordinate using the rack units, see
Setting the Z
Coordinate Format for Environmental Sensors
(on page 407).
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 to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
• <description> is a string comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
Chapter 8: Using the Command Line Interface
Using Default Thresholds
This command determines whether default thresholds, including the deassertion hysteresis and assertion timeout, are applied to a specific environmental sensor. config:# externalsensor <n> useDefaultThresholds <option>
Variables:
• <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
•
<option> is one of the options:
true
or
false
.
Option true false
Description
Default thresholds are selected as the threshold option for the specified sensor.
Sensor-specific thresholds are selected as the threshold option for the specified sensor.
Setting the Alarmed to Normal Delay for DX-PIR
This command determines the value of the Alarmed to Normal Delay setting for a DX-PIR presence detector. config:# externalsensor <n> alarmedToNormalDelay <time>
Variables:
•
<n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
• <time> is an integer number in seconds, ranging between 0 and 300.
Examples
This section illustrates several environmental sensor configuration examples.
485
486
Chapter 8: Using the Command Line Interface
Example 1 - Environmental Sensor Naming
The following command assigns the name "Cabinet humidity" to the environmental 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 type at a time by combining multiple commands. See
Multi-Command
Syntax
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:
Chapter 8: Using the Command Line Interface config:# defaultThresholds <sensor type> lowerWarning <value>
Set the Default Deassertion Hysteresis for a specific sensor type: config:# defaultThresholds <sensor type> hysteresis <hy_value> config:#
Set the Default Assertion Timeout for a specific sensor type: defaultThresholds <sensor type> assertionTimeout <as_value>
Variables:
•
<sensor type> is one of the following numeric sensor types:
Sensor types absoluteHumidity relativeHumidity temperature airPressure
Description
Absolute humidity sensors
Relative humidity sensors
Temperature sensors
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 absoluteHumidity relativeHumidity temperature airPressure airFlow
Measurement units g/m^3 (that is, g/m
3
)
%
Degrees Celsius ( ) or Fahrenheit ( ), depending on your measurement unit settings.
Pascal (Pa) or psi, depending on your measurement unit settings. m/s
487
488
Chapter 8: Using the Command Line Interface
Sensor types vibration
Measurement units g
• <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).
Example - Default Upper Thresholds for Temperature
It is assumed that your preferred measurement unit for temperature is set to degrees Celsius. Then the following command sets the default
Upper Warning threshold to 20 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 the commands to configure the threshold, hysteresis and assertion timeout values for any sensor associated with the following items:

Inlets

Outlets (only available for models with outlet switching)

Overcurrent protectors

Environmental sensors

Transfer switch sensors
It is permitted to assign a new value to the threshold at any time regardless of whether the threshold has been enabled.
Commands for Inlet Sensors
A sensor configuration command for inlets begins with
sensor inlet
.
You can configure various inlet sensor threshold settings at a time by combining multiple commands. See
Multi-Command Syntax
(on page
Set the Upper Critical threshold for an inlet sensor:
Chapter 8: Using the Command Line Interface 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: 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 the number 1.
• <sensor type> is one of the following sensor types:
Sensor type current peakCurrent voltage activePower apparentPower powerFactor activeEnergy
Description
Current sensor
Peak current sensor
Voltage sensor
Active power sensor
Apparent power sensor
Power factor sensor
Active energy sensor
489
490
Chapter 8: Using the Command Line Interface config:#
Sensor type unbalancedCurrent lineFrequency residualCurrent phaseAngle
Description
Unbalanced load sensor
Line frequency sensor
Residual current sensor
Inlet phase angle sensor
Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.
• <option> is one of the options:
enable
,
disable
or a numeric value.
Option enable
Description
Enables the specified threshold for a specific inlet sensor. disable Disables the specified threshold for a specific inlet sensor.
A numeric value
Sets a value for the specified threshold of a specific inlet sensor and enables this threshold at the same time.
•
<hy_value> is a numeric value that is assigned to the hysteresis for the specified inlet sensor. See
"To De-assert" and Deassertion
Hysteresis
• <as_value> is a numeric value that is assigned to the assertion timeout for the specified inlet sensor. See
"To Assert" and
Assertion Timeout
Commands for Outlet Sensors
A sensor configuration command for outlets begins with
sensor outlet
.
You can configure various outlet sensor threshold settings at a time by combining multiple commands. See
Multi-Command Syntax
(on page
Set the Upper Critical threshold for an outlet sensor: sensor outlet <n> <sensor type> upperCritical <option>
Set the Upper Warning threshold for an outlet sensor:
Chapter 8: Using the Command Line Interface config:# sensor outlet <n> <sensor type> upperWarning <option>
Set the Lower Critical threshold for an outlet sensor: config:# sensor outlet <n> <sensor type> lowerCritical <option>
Set the Lower Warning threshold for an outlet sensor: config:# sensor outlet <n> <sensor type> lowerWarning <option>
Set the deassertion hysteresis for an outlet sensor: config:# sensor outlet <n> <sensor type> hysteresis <hy_value>
Set the assertion timeout for an outlet sensor: config:# sensor outlet <n> <sensor type> assertionTimeout <as_value>
Variables:
•
<n> is the number of the outlet that you want to configure.
•
<sensor type> is one of the following sensor types:
Sensor type current voltage activePower apparentPower powerFactor activeEnergy lineFrequency
Description
Current sensor
Voltage sensor
Active power sensor
Apparent power sensor
Power factor sensor
Active energy sensor
Line frequency sensor
Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.
491
492
Chapter 8: Using the Command Line Interface
• <option> is one of the options:
enable
,
disable
or a numeric value.
Option enable disable
Description
Enables the specified threshold for a specific outlet sensor.
Disables the specified threshold for a specific outlet sensor.
A numeric value
Sets a value for the specified threshold of a specific outlet sensor and enables this threshold at the same time.
•
<hy_value> is a numeric value that is assigned to the hysteresis for the specified outlet sensor. See
"To De-assert" and Deassertion
Hysteresis
•
<as_value> is a number in samples that is assigned to the assertion timeout for the specified outlet sensor. See
"To Assert" and
Assertion Timeout
Commands for Overcurrent Protector Sensors
A sensor configuration command for overcurrent protectors begins with
sensor ocp
.
You can configure various overcurrent protector threshold settings at a time by combining multiple commands. See
Multi-Command Syntax
(on config:#
Set the Upper Critical threshold for an overcurrent protector: 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:
Chapter 8: Using the Command Line Interface 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 current
Description
Current sensor
Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.
•
<option> is one of the options:
enable
,
disable
or a numeric value.
Option enable disable
Description
Enables the specified threshold for the overcurrent protector sensor.
Disables the specified threshold for the overcurrent protector sensor.
A numeric value
Sets a value for the specified threshold of the overcurrent protector sensor and enables this threshold at the same time.
• <hy_value> is a numeric value that is assigned to the hysteresis for the specified overcurrent protector sensor. See
"To De-assert" and
Deassertion Hysteresis
•
<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
493
494
Chapter 8: Using the Command Line Interface
Commands for Environmental Sensors
A sensor threshold configuration command for environmental sensors begins with
sensor externalsensor
.
You can configure various environmental sensor threshold settings at a time by combining multiple commands. See
Multi-Command Syntax
(on
Set the Upper Critical threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> upperCritical <option>
Set the Upper Warning threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> upperWarning <option>
Set the Lower Critical threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> lowerCritical <option>
Set the Lower Warning threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> lowerWarning <option>
Set the deassertion hysteresis for an environmental sensor: config:# sensor externalsensor <n> <sensor type> hysteresis <hy_value>
Set the assertion timeout for an environmental sensor:
Chapter 8: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> assertionTimeout <as_value>
Variables:
•
<n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PX3TS web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
• <sensor type> is one of these sensor types:
temperature, absoluteHumidity, relativeHumidity, airPressure, airFlow
or
vibration
.
Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears:
"Specified sensor type 'XXX' does not match the sensor's type
(<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.
Option enable disable
Description
Enables the specified threshold for a specific environmental sensor.
Disables the specified threshold for a specific environmental sensor.
A numeric value
Sets a value for the specified threshold of a specific environmental sensor and enables this threshold at the same time.
• <hy_value> is a numeric value that is assigned to the hysteresis for the specified environmental sensor. See
"To De-assert" and
Deassertion Hysteresis
• <as_value> is a number in samples that is assigned to the assertion timeout for the specified environmental sensor. It ranges between 1 and 100. See
"To Assert" and Assertion Timeout
495
496
Chapter 8: Using the Command Line Interface
Commands for Transfer Switch Sensors
A sensor threshold configuration command for transfer switch sensors begins with
sensor ts
be configured.
. Currently only inlet phase sync angle settings can
You can configure various inlet phase sync angle settings at a time by combining multiple commands. See
Multi-Command Syntax
(on page
Set the Upper Critical threshold for the inlet phase sync angle: config:# sensor ts inletPhaseSyncAngle upperCritical <option>
Set the Upper Warning threshold for the inlet phase sync angle: config:# sensor ts inletPhaseSyncAngle upperWarning <option>
Set the Lower Critical threshold for the inlet phase sync angle: config:# sensor ts inletPhaseSyncAngle lowerCritical <option>
Set the Lower Warning threshold for the inlet phase sync angle: config:# sensor ts inletPhaseSyncAngle lowerWarning <option>
Set the deassertion hysteresis for the inlet phase sync angle: config:# sensor ts inletPhaseSyncAngle hysteresis <hy_value>
Set the assertion timeout for the inlet phase sync angle:
Chapter 8: Using the Command Line Interface config:# sensor ts inletPhaseSyncAngle assertionTimeout <as_value>
Variables:
•
<option> is one of the options:
enable
,
disable
or a numeric value.
Option enable
Description
Enables the specified threshold for the inlet phase sync angle sensor. disable Disables the specified threshold for the inlet phase sync angle sensor.
A numeric value
Sets a value for the specified threshold of the inlet phase sync angle sensor and enables this threshold at the same time.
•
<hy_value> is a numeric value that is assigned to the hysteresis for the inlet phase sync angle sensor. See
Deassertion Hysteresis
"To De-assert" and
• <as_value> is a number in samples that is assigned to the assertion timeout for the inlet phase sync angle sensor. It ranges between 1 and 100. See
"To Assert" and Assertion Timeout
Examples
This section illustrates several environmental sensor threshold configuration examples.
Example 2 - Warning Thresholds for Inlet Sensors
The following command sets both the Upper Warning and Lower
Warning thresholds for the inlet 1 RMS current. config:# sensor inlet 1 current upperWarning 20 lowerWarning 12
Results:
• The Upper Warning threshold for the inlet 1 RMS current is set to
20A. It also enables the upper warning threshold if this threshold has not been enabled yet.
•
The Lower Warning threshold for the inlet 1 RMS current is set to
12A. It also enables the lower warning threshold if this threshold has not been enabled yet.
497
498
Chapter 8: Using the Command Line Interface
Example 1 - Upper Critical Threshold for a Temperature Sensor
The following command sets the Upper Critical threshold of the environmental "temperature" sensor with the ID number 2 to 40 degrees
Celsius. It also enables the upper critical threshold if this threshold has not been enabled yet. config:# sensor externalsensor 2 temperature upperCritical 40
Example 3 - Upper Thresholds for Overcurrent Protector Sensors
The following command sets both the Upper Critical and Upper Warning thresholds for the 2nd overcurrent protector. config:# sensor ocp 2 current upperWarning enable upperCritical 16
Results:
• The Upper Critical threshold for the 2nd overcurrent protector's
RMS current is set to 16A. It also enables the upper critical threshold if this threshold has not been enabled yet.
•
The Upper Warning threshold for the 2nd overcurrent protector's
RMS current is enabled.
Chapter 8: 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
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 be found using the PX3TS web interface or CLI. It is an integer starting at 1.
•
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
• <coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
• There are two types of values for the <z_label> variable, depending on the Z coordinate format you set:
Type
Free form
Rack units
Description
<coordinate> is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
<coordinate> is an integer number in rack units.
499
500
Chapter 8: Using the Command Line Interface
Note: To specify the Z coordinate using the rack units, see
Setting the Z Coordinate Format for Environmental Sensors
(on page 407).
•
<description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
Example - Actuator Naming
The following command assigns the name "Door lock" to the actuator whose ID number is 9. config:# actuator 9 name "Door lock"
Server Reachability Configuration Commands
You can use the CLI to add or delete an IT device, such as a server, from the server reachability list, or modify the settings for a monitored IT device. A server reachability configuration command begins with
serverReachability
.
Adding a Monitored Device
This command adds a new IT device to the server reachability list. config:# serverReachability add <IP_host> <enable> <succ_ping>
<fail_ping> <succ_wait> <fail_wait> <resume> <disable_count>
Variables:
• <IP_host> is the IP address or host name of the IT device that you want to add.
• <enable> is one of the options:
true
or
false
.
Option true false
Description
Enables the ping monitoring feature for the newly added device.
Disables the ping monitoring feature for the newly added device.
Chapter 8: 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 PX3TS 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 PX3TS 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 the monitored server list.
You can find each IT device's sequence number using the CLI command of show serverReachability as illustrated below.
Modifying a Monitored Device's Settings
The command to modify a monitored IT device's settings begins with
serverReachability modify
.
You can modify various settings for a monitored device at a time. See
Multi-Command Syntax
Modify a device's IP address or host name:
501
502
Chapter 8: Using the Command Line Interface config:# serverReachability modify <n> ipAddress <IP_host>
Enable or disable the ping monitoring feature for the device: config:# serverReachability modify <n> pingMonitoringEnabled <option>
Modify the number of successful pings for declaring "Reachable": config:# serverReachability modify <n> 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:
Chapter 8: Using the Command Line Interface 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
.
Option true
Description
Enables the ping monitoring feature for the monitored device. false Disables the ping monitoring feature for the monitored device.
•
<succ_number> is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200.
• <fail_number> is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to
100.
•
<succ_wait> is the wait time to send the next ping after a successful ping. Valid range is 5 to 600 (seconds).
•
<fail_wait> is the wait time to send the next ping after a unsuccessful ping. Valid range is 3 to 600 (seconds).
• <resume> is the wait time before the PX3TS 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 PX3TS disables the ping monitoring feature for the monitored device and returns to the "Waiting for reliable connection" state. Valid range is 1 to 100 or
unlimited
.
Example - Server Settings Changed
The following command modifies several ping monitoring settings for the second server in the server reachability list. config:# serverReachability modify 2 numberOfSuccessfulPingsToEnable 10 numberOfUnsuccessfulPingsForFailure 8 waitTimeAfterSuccessfulPing 30
503
504
Chapter 8: Using the Command Line Interface
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 PX3TS device is enabled. config:# energywise enabled <option>
Variables:
•
<option> is one of the options:
true
or
false
.
Option true false
Description
The Cisco EnergyWise feature is enabled.
The Cisco EnergyWise feature is disabled.
Specifying the EnergyWise Domain
This command syntax specifies to which Cisco
®
EnergyWise domain the
PX3TS device belongs. config:# energywise domain <name>
Variables:
•
<name> is a string comprising up to 127 ASCII printable characters.
Spaces and asterisks are NOT acceptable.
Chapter 8: Using the Command Line Interface
Specifying the EnergyWise Secret
This 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 Port
This 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.
Setting the Polling Interval
This command syntax determines the polling interval at which the Cisco
®
EnergyWise domain queries the PX3TS device. config:# energywise polling <timing>
Variables:
•
<timing> is an integer number in seconds. It ranges between 30 and
600 seconds.
505
506
Chapter 8: Using the Command Line Interface
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 PX3TS is enabled.
• The UDP port is set to 10288.
Asset Management Commands
You can use the CLI commands to change the settings of the connected asset strip (if any) or the settings of LEDs on the asset strip.
Asset Strip Management
An asset strip management configuration command begins with assetStrip
.
Naming an Asset Strip
This command syntax names or changes the name of an asset strip connected to the PX3TS 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 PX3TS device with only one
FEATURE port, the number is always 1.
•
<name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
Chapter 8: Using the Command Line Interface
Specifying the Number of Rack Units
This command syntax specifies the total number of rack units on an asset strip connected to the PX3TS 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 PX3TS device with only one
FEATURE port, the number is always 1.
•
<number> is the total number of rack units available on the connected asset strip. This value ranges from 8 to 64.
Specifying the Rack Unit Numbering Mode
This command syntax specifies the numbering mode of rack units on the asset strips connected to the PX3TS 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 PX3TS device with only one
FEATURE port, the number is always 1.
•
<mode> is one of the numbering modes:
topDown
or
bottomUp
.
Mode topDown bottomUp
Description
The rack units are numbered in the ascending order from the highest to the lowest rack unit.
The rack units are numbered in the descending order from the highest to the lowest rack unit.
507
508
Chapter 8: Using the Command Line Interface
Specifying the Rack Unit Numbering Offset
This command syntax specifies the starting number of rack units on the asset strips connected to the PX3TS device. config:# assetStrip <n> rackUnitNumberingOffset <number>
Variables:
• <n> is the number of the FEATURE port where the selected asset strip is physically connected. For the PX3TS device with only one
FEATURE port, the number is always 1.
•
<number> is a starting number for numbering rack units on the connected asset strip. This value is an integer number.
Specifying the Asset Strip Orientation
This command syntax specifies the orientation of the asset strips connected to the PX3TS device. Usually you do not need to perform this command unless your asset strips do NOT come with the tilt sensor, causing the PX3TS 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 PX3TS device with only one
FEATURE port, the number is always 1.
•
<orientation> is one of the options:
topConnector
or
bottomConnector
.
Orientation topConnector
Description
This option indicates that the asset sensor is mounted with the RJ-45 connector located on the top. bottomConnector This option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom.
Chapter 8: Using the Command Line Interface
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.
Setting LED Colors for Disconnected Tags
This command syntax sets the LED color for all rack units on the connected asset strip(s) to indicate the absence of a connected asset tag. config:# assetStrip <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 configuration command begins with rackUnit.
509
510
Chapter 8: Using the Command Line Interface
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:
• <n> is the number of the FEATURE port where the selected asset strip is physically connected. For the PX3TS device with only one
FEATURE port, the number 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 web interface.
• <name> is a string comprising up to 32 ASCII printable characters.
The <name> variable must be enclosed in quotes when it contains spaces.
Setting the LED Operation Mode
This command syntax determines whether a specific rack unit on the specified asset strip follows the global LED color settings. config:# rackUnit <n> <rack_unit> LEDOperationMode <mode>
Variables:
•
<n> is the number of the FEATURE port where the selected asset strip is physically connected. For the PX3TS device with only one
FEATURE port, the number 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 web interface.
•
<mode> is one of the LED modes:
automatic
or
manual
.
Mode automatic
Description
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
Setting LED Colors for Disconnected
Tags
This is the default.
Chapter 8: Using the Command Line Interface
Mode manual
Description
This option enables selection of a different LED color and LED mode for the specified rack unit.
When this option is selected, see
Setting an LED
Color for a Rack Unit
Setting an LED Mode for a Rack Unit
different LED settings.
Setting an LED Color for a Rack Unit
This command syntax sets the LED color for a specific rack unit on the specified asset strip. You need to set a rack unit's LED color only when the LED operation mode of this rack unit has been set to "manual." config:# rackUnit <n> <rack_unit> LEDColor <color>
Variables:
•
<n> is the number of the FEATURE port where the selected asset strip is physically connected. For the PX3TS device with only one
FEATURE port, the number 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 web interface.
•
<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 509)
and
Setting LED Colors for Disconnected Tags
(on page 509).
511
512
Chapter 8: Using the Command Line Interface
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:
• <n> is the number of the FEATURE port where the selected asset strip is physically connected. For the PX3TS device with only one
FEATURE port, the number 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 web interface.
• <mode> is one of the LED modes:
on
,
off
,
blinkSlow
or
blinkFast
.
Mode on off blinkSlow blinkFast
Description
This mode has the LED stay lit permanently.
This mode has the LED stay off permanently.
This mode has the LED blink slowly.
This mode has the LED blink quickly.
Examples
This section illustrates several asset management examples.
Example 1 - Asset Strip LED Colors for Disconnected Tags
This command syntax sets the LED color for all rack units on the asset sensor #1 to BLACK (that is, 000000) to indicate the absence of a connected asset tag. config:# assetStrip 1 LEDColorForDisconnectedTags #000000
Note: Black color causes the LEDs to stay off.
Chapter 8: Using the Command Line Interface
Example 2 - Rack Unit Naming
The following command assigns the name "Linux server" to the rack unit whose index number is 25 on the asset sensor#1. config:# rackUnit 1 25 name "Linux server"
Serial Port Configuration Commands
A serial port configuration command begins with
serial
.
Setting the Baud Rates
The following commands set the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the PX3TS 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 PX3TS 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 PX3TS works in conjunction with Raritan's Dominion LX KVM switch. Dominion LX only supports 19200 bps for communications over the serial interface.
Determine the MODEM baud rate: config:# serial modemBaudRate <baud_rate>
Variables:
•
<baud_rate> is one of the baud rate options:
1200
,
2400
,
4800
,
9600
,
19200
,
38400
,
57600
,
115200
.
513
514
Chapter 8: Using the Command Line Interface
Forcing the Device Detection Mode
This command forces the serial port on the PX3TS to enter a specific device detection mode. config:# serial deviceDetectionType <mode>
Variables:
• <mode> is one of the detection modes:
automatic
,
forceConsole
,
forceAnalogModem,
or
forceGsmModem
.
Option automatic forceConsole
Description
The PX3TS automatically detects the type of the device connected to the serial port.
Select this option unless your PX3TS cannot correctly detect the device type.
The PX3TS attempts to recognize that the connected device is set for the console mode. forceAnalogModem The PX3TS attempts to recognize that the connected device is an analog modem. forceGsmModem The PX3TS attempts to recognize that the connected device is a GSM modem.
Example
The following command sets the CONSOLE baud rate of the PX3TS device's serial port to 9600 bps. config:# serial consoleBaudRate 9600
Setting the History Buffer Length
This command syntax sets the history buffer length, which determines the amount of history commands that can be retained in the buffer. The default length is 25. config:# history length <n>
Variables:
• <n> is an integer number between 1 and 250.
Chapter 8: Using the Command Line Interface
Multi-Command Syntax
To shorten the configuration time, you can combine various configuration commands in one command to perform all of them at a time. All combined commands must belong to the same configuration type, such as commands prefixed with and so on.
network
,
user modify
,
sensor externalsensor
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 IP, Subnet Mask and Gateway Parameters
The following multi-command syntax configures IPv4 address, subnet mask and gateway for the network connectivity simultaneously. config:# network ipv4 ipAddress 192.168.84.225 subnetMask
255.255.255.0 gateway 192.168.84.0
Results:
• The IP address is set to 192.168.84.225.
• The subnet mask is set to 255.255.255.0.
•
The gateway is set to 192.168.84.0.
Example 2 - Combination of Upper Critical and Upper Warning Settings
The following multi-command syntax simultaneously configures Upper
Critical and Upper Warning thresholds for the RMS current of the 2nd overcurrent protector. config:# sensor ocp 2 current upperCritical disable upperWarning 15
Results:
•
The Upper Critical threshold of the 2nd overcurrent protector's RMS current is disabled.
• The Upper Warning threshold of the 2nd overcurrent protector's
RMS current is set to 15A and enabled at the same time.
515
516
Chapter 8: Using the Command Line Interface
Example 3 - Combination of SSID and PSK Parameters
This multi-command syntax configures both SSID and PSK parameters simultaneously for the wireless feature. config:# network wireless SSID myssid PSK encryp_key
Results:
• The SSID value is set to myssid.
• The PSK value is set to encryp_key.
Load Shedding Configuration Commands
This section applies to outlet-switching capable models only.
A load shedding configuration command begins with
loadshedding
.
Unlike other CLI configuration commands, the load shedding configuration command is performed in the than the configuration mode. See
administrator mode
rather
Different CLI Modes and Prompts
(on
Chapter 8: Using the Command Line Interface
Enabling or Disabling Load Shedding
This section applies to outlet-switching capable models only.
This command determines whether to enter or exit from the load shedding mode.
# loadshedding <option>
After performing the above command, PX3TS prompts you to confirm the operation. Press y to confirm or n to abort the operation.
To skip the confirmation step, you can add the "/y" parameter to the end of the command so that the operation is executed immediately.
# loadshedding <option> /y
Variables:
• <option> is one of the options:
enable
or
disable
.
Option start stop
Description
Enter the load shedding mode.
Quit the load shedding mode.
Example
The following command has the PX3TS enter the load shedding mode. config:# loadshedding start
517
518
Chapter 8: Using the Command Line Interface
Power Control Operations
This section applies to outlet-switching capable models only.
Outlets on the PX3TS device can be turned on or off or power cycled through the CLI.
Besides, you can cancel the power-on process while the PX3TS is powering on ALL outlets.
You must perform this operation in the
administrator mode
. See
Different CLI Modes and Prompts
Turning On the Outlet(s)
This section applies to outlet-switching capable models only.
This command turns on one or multiple outlets.
# power outlets <numbers> on
To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.
# power outlets <numbers> on
/y
Variables:
•
<numbers> is one of the options:
all
, an outlet number, a list or a range of outlets.
Option all
Description
Switches ON all outlets.
A specific outlet number
Switches ON the specified outlet.
A comma- separated list of outlets
A range of outlets with an en dash in between
Switches ON multiple, inconsecutive or consecutive outlets.
For example, to specify 7 outlets -- 2, 4, 9, 11, 12,
13 and 15, type outlets 2,4,9,11-13,15.
Switches ON multiple, consecutive outlets.
For example, to specify 6 consecutive outlets -- 3,
4, 5, 6, 7, 8, type outlets 3-8.
Chapter 8: Using the Command Line Interface
If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:

Type y to confirm the operation, OR

Type n to abort the operation
Turning Off the Outlet(s)
This section applies to outlet-switching capable models only.
This command turns off one or multiple outlets.
# power outlets <numbers> off
To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.
# power outlets <numbers> off
/y
Variables:
• <numbers> is one of the options: range of outlets.
all
, an outlet number, a list or a
Option all
Description
Switches OFF all outlets.
A specific outlet number
Switches OFF the specified outlet.
A comma- separated list of outlets
A range of outlets with an en dash in between
Switches OFF multiple, inconsecutive or consecutive outlets.
For example, to specify 7 outlets -- 2, 4, 9, 11, 12,
13 and 15, type outlets 2,4,9,11-13,15.
Switches OFF multiple, consecutive outlets.
For example, to specify 6 consecutive outlets -- 3,
4, 5, 6, 7, 8, type outlets 3-8.
519
520
Chapter 8: Using the Command Line Interface
If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:

Type y to confirm the operation, OR

Type n to abort the operation
Power Cycling the Outlet(s)
This section applies to outlet-switching capable models only.
This command power cycles one or multiple outlets.
# power outlets <numbers> cycle
To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.
# power outlets <numbers> cycle
/y
Variables:
• <numbers> is one of the options: range of outlets.
all
, an outlet number, a list or a
Option all
Description
Power cycles all outlets.
A specific outlet number
Power cycles the specified outlet.
A comma- separated list of outlets
A range of outlets with an en dash in between
Power cycles multiple, inconsecutive or consecutive outlets.
For example, to specify 7 outlets -- 2, 4, 9, 11, 12,
13 and 15, type outlets 2,4,9,11-13,15.
Power cycles multiple, consecutive outlets.
For example, to specify 6 consecutive outlets -- 3,
4, 5, 6, 7, 8, type outlets 3-8.
Chapter 8: Using the Command Line Interface
If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:

Type y to confirm the operation, OR

Type n to abort the operation
Canceling the Power-On Process
This section applies to outlet-switching capable models only.
After issuing the command to power on ALL outlets, you can use the following command to stop the power-on process.
# power cancelSequence
To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.
# power cancelSequence /y
Example - Power Cycling Specific Outlets
The following command power cycles these outlets: 2, 6, 7, 8, 10, 13, 14,
15 and 16.
# power outlets 2,6-8,10,13-16 cycle
Actuator Control Operations
An actuator, which is connected to a dry contact signal channel of a DX sensor, can control a mechanism or system. You can switch on or off that mechanism or system through the actuator control command in the CLI.
Perform these commands in the administrator or user mode. See
Different CLI Modes and Prompts
521
522
Chapter 8: 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 the command, which confirms the operation.
# control actuator <n> on
/y
Variables:
• <n> is an actuator's ID number.
The ID number is available in the PX3TS web interface or using the show command in the CLI. It is an integer between 1 and 32.
If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:

Type y to confirm the operation, OR

Type n to abort the operation
Switching Off an Actuator
This command syntax turns off one actuator.
# control actuator <n> off
To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.
# control actuator <n> off
/y
Variables:
•
<n> is an actuator's ID number.
The ID number is available in the PX3TS web interface or using the show command in the CLI. It is an integer between 1 and 32.
Chapter 8: Using the Command Line Interface
If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:

Type y to confirm the operation, OR

Type n to abort the operation
Example - Turning On a Specific Actuator
The following command turns on the actuator whose ID number is 8.
# control actuator 8 on
Unblocking a User
If any user is blocked from accessing the PX3TS, you can unblock them at the local console.
To unblock a user:
1. Log in to the CLI interface using any terminal program via a local connection. See
With HyperTerminal
2. When the Username prompt appears, type unblock and press
Enter.
3. When the "Username to unblock" prompt appears, type the name of the blocked user and press Enter.
4. A message appears, indicating that the specified user was unblocked successfully.
Resetting the PX3TS
You can reset the PX3TS device to factory defaults or simply restart it using the CLI commands. In addition, you can reset active energy readings via CLI.
All of these commands begin with
reset
.
523
524
Chapter 8: Using the Command Line Interface
Restarting the PDU
This command restarts the PX3TS device. It is not a factory default reset.
To restart the PX3TS device:
1. Ensure you have entered administrator mode and the # prompt is displayed.
2. Type either of the following commands to restart the PX3TS device.
# reset unit
-- OR --
# reset unit
/y
3. If you entered the command without "/y" in Step 2, a message appears prompting you to confirm the operation. Type y to confirm the reset.
4. Wait until the Username prompt appears, indicating the reset is complete.
Note: If you are performing this command over a USB connection, re-connect the USB cable after the reset is completed, or the CLI communications are lost.
Resetting Active Energy Readings
You can reset either one active energy sensor or all active energy sensors at a time to restart the energy accumulation process.
Only users with the "Admin" role assigned can reset active energy readings.
To reset all active energy readings of the PX3TS:
# reset activeEnergy pdu
-- OR --
# reset activeEnergy pdu /y
To reset one inlet's active energy readings:
# reset activeEnergy inlet <n>
-- OR --
# reset activeEnergy inlet <n> /y
To reset one outlet's active energy readings:
# reset activeEnergy outlet <outlet_n>
Chapter 8: Using the Command Line Interface
-- OR --
# reset activeEnergy outlet <outlet_n> /y
If you entered the command without "/y", a message appears prompting you to confirm the operation. Type y to confirm the reset or n to abort it.
Variables:
• <n> is the inlet number.
• <outlet_n> is an outlet number.
Note: The outlet active energy reset feature is only available for models with outlet switching.
Resetting to Factory Defaults
The following commands restore all settings of the PX3TS device to factory defaults.
To reset PX3TS settings after login, use either command:
# reset factorydefaults
-- OR --
# reset factorydefaults
/y
To reset PX3TS settings before login:
Username: factorydefaults
See
Using the CLI Command
Network Troubleshooting
The PX3TS provides 4 diagnostic commands for troubleshooting network problems:
nslookup
,
netstat
, corresponding Linux outputs.
ping
, and
traceroute
. The diagnostic commands function as corresponding Linux commands and can get
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.
525
526
Chapter 8: Using the Command Line Interface
2. Type diag and press Enter. The diag# or diag> prompt appears, indicating that you have entered the diagnostic mode.
3. Now you can type any diagnostic commands for troubleshooting.
Quitting Diagnostic Mode
To quit the diagnostic mode, use this command: diag> exit
The # or > prompt appears after pressing Enter, indicating that you have entered the administrator or user mode. See
Different CLI Modes and
Prompts
Diagnostic Commands
The diagnostic command syntax varies from command to command.
Querying DNS Servers
This command syntax queries Internet domain name server (DNS) information of a network host. diag> nslookup <host>
Variables:
• <host> is the name or IP address of the host whose DNS information you want to query.
Showing Network Connections
This command syntax displays network connections and/or status of ports. diag> netstat <option>
Variables:
•
<option> is one of the options:
ports
or
connections
.
Option ports
Description
Shows TCP/UDP ports.
diag>
Chapter 8: Using the Command Line Interface
Option connections
Description
Shows network connections.
Testing the Network Connectivity
This ping command sends the ICMP ECHO_REQUEST message to a network host for checking its network connectivity. If the output shows the host is responding properly, the network connectivity is good. If not, either the host is shut down or it is not being properly connected to the network. diag> ping <host>
Variables:
•
<host> is the host name or IP address whose networking connectivity you want to check.
Options:
• You can include any or all of additional options listed below in the ping command.
Options count <number1>
Description
Determines the number of messages to be sent. <number1> is an integer number between 1 and 100. 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: ping <host> count <number1> size <number2> timeout <number3>
527
528
Chapter 8: Using the Command Line Interface
Tracing the Route
This command syntax traces the network route between your PX3TS device and a network host. diag> traceroute <host>
Variables:
• <host> is the name or IP address of the host you want to trace.
Example - Ping Command
The following command checks the network connectivity of the host
192.168.84.222 by sending the ICMP ECHO_REQUEST message to the host for 5 times. diag> ping 192.168.84.222 count 5
Retrieving Previous Commands
If you would like to retrieve any command that was previously typed in the same connection session, press the Up arrow ( ) on the keyboard until the desired command is displayed.
Automatically Completing a Command
A CLI command always consists of several words. You can easily enter a command by typing first word(s) or letter(s) and then pressing Tab or
Ctrl+i instead of typing the whole command word by word.
To have a command completed automatically:
1. Type initial letters or words of the desired command. Make sure the letters or words you typed are unique so that the CLI can identify the command you want.
2. Press Tab or Ctrl+i until the complete command appears.
Chapter 8: Using the Command Line Interface
Example 1:
Type the first word and the first letter of the second word of the "reset factorydefaults
" command, that is, reset f. Then press Tab or
Ctrl+i to complete the second word.
Example 2:
Type the first word and initial letters of the second word of the
"security enforceHttpsForWebAccess" command, that is, security enf
. Then press Tab or Ctrl+i to complete the second word.
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.
529
Chapter 9 Using SCP Commands
You can perform a Secure Copy (SCP) command to update the PX3TS firmware, do bulk configuration, or back up and restore the configuration.
In This Chapter
Backup and Restore via SCP .................................................................... 532
Downloading Diagnostic Data via SCP ..................................................... 533
Firmware Update via SCP
Same as any PX3TS firmware update, all user management operations are suspended and all login attempts fail during the SCP firmware update. For details, see
Updating the PX3TS Firmware
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 PX3TS firmware's filename. If the firmware file is not in the current directory, you must include the path in the filename.
<user name>
is the "admin" or any user profile with the
Firmware Update permission.
<device ip>
is the IP address of the PX3TS that you want to update.
2. When the system prompts you to enter the password for the specified user profile, type it and press Enter.
3. The system transmits the specified firmware file to the PX3TS, and shows the transmission speed and percentage.
4. When the transmission is complete, it shows the following message, indicating that the PX3TS starts to update its firmware now. Wait until the upgrade completes.
Starting firmware update. The connection will be closed now.
530
Chapter 9: Using SCP Commands
SCP example: scp pdu-px2-030000-41270.bin [email protected]:/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 PX3TS. b. Copy the configuration file to one or multiple destination PX3TS.
For detailed information on the bulk configuration requirements, see
Bulk Configuration
To save the configuration via SCP:
1. Type the following SCP command and press Enter. scp <user name>@<device ip>:/bulk_config.xml


<user name>
is the "admin" or any user profile with the administrator privileges.
<device ip>
is the IP address of the PX3TS whose configuration you want to save.
2. Type the user password when prompted.
3. The system saves the configuration from the PX3TS to a file named
"bulk_config.xml."
To copy the configuration via SCP:
1. Type the following SCP command and press Enter. scp bulk_config.xml <user name>@<device ip>:/bulk_restore


<user name>
is the "admin" or any user profile with the administrator privileges.
<device ip>
is the IP address of the PX3TS whose configuration you want to copy.
2. Type the user password when prompted.
531
532
Chapter 9: Using SCP Commands
3. The system copies the configuration included in the file
"bulk_config.xml" to another PX3TS, and displays the following message.
Starting restore operation. The connection will be closed now.
SCP examples:
• Save operation: scp [email protected]:/bulk_config.xml
•
Copy operation: scp bulk_config.xml [email protected]:/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.xml
•
Copy operation: pscp bulk_config.xml <user name>@<device ip>:/bulk_restore
Backup and Restore via SCP
To back up ALL settings of a PX3TS, 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.xml


<user name>
is the "admin" or any user profile with the administrator privileges.
<device ip>
is the IP address of the PX3TS whose settings you want to back up.
2. Type the user password when prompted.
3. The system saves the settings from the PX3TS to a file named
"backup_settings.xml."
Chapter 9: Using SCP Commands
To restore the settings via SCP:
1. Type the following SCP command and press Enter. scp backup_settings.xml <user name>@<device ip>:/settings_restore


<user name>
is the "admin" or any user profile with the administrator privileges.
<device ip>
is the IP address of the PX3TS 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.xml" to the PX3TS, and displays the following message.
Starting restore operation. The connection will be closed now.
SCP examples:
•
Backup operation: scp [email protected]:/backup_settings.xml
•
Restoration operation: scp backup_settings.xml [email protected]:/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.xml
• Restoration operation: pscp backup_settings.xml <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 the following SCP command and press Enter. scp <user name>@<device ip>:/diag-data.tgz

<user name>
is the "admin" or any user profile with the
Administrator or "Unrestricted View Privileges" privileges.
533
Chapter 9: Using SCP Commands

<device ip>
is the IP address of the PX3TS whose diagnostic data you want to download.
2. Type the password when the system prompts you to type it.
3. The system saves the diagnostic data from the PX3TS to a file named
"diag-data.tgz."
SCP example: scp [email protected]:/diag-data.tgz
Windows PSCP command:
PSCP in Windows works in a similar way to the SCP.
 pscp <user name>@<device ip>:/diag-data.tgz
534
Appendix A Specifications
In This Chapter
Serial RS-232 "DB9" Port Pinouts ........................................................... 537
Technical Specifications
535
536
Appendix A: Specifications
Rated voltage and current
Rated frequency
Load power factor
Non-linear load
Sense and transfer time
Phase sync requirements
Phase sync resolution
Redundancy
SCR derating
SCR protection
Internal fault monitoring
Short circuit detection
Operating temperature
See the label or nameplate on your PX3TS model
50/60Hz +/- 5Hz
0.60 to 1.00 (leading or lagging)
Rated current up to crest factor 3.5
4-8 milliseconds
None -- inlets may be any phase relationship
+/- 5 degrees
Two power supplies.
The PX3TS continues to function on one power supply.
At maximum continuous load, SCR switches are running at 30% of the full rated current and are running 50 degrees cooler than rated semiconductor junction temperature
MOV (Metal Oxide Varistor) voltage transient protection

Switch open or short fault

MOV surge protector failure

Internal DC 12V power supply failure

Overcurrent protector blow or trip detection
The short circuit threshold varies depending on the rating:

16A models, such as PX3TS-1876R: around 45A

24A models, such as PX3TS-1464R: around 68A

32A models, such as PX3TS-1469R: around 91A
For details on the threshold calculation, see
Short Circuit Detection
50°F (10°C) to 122°F (50°C)
Appendix A: Specifications
Storage temperature
Relative humidity
Operating altitude (above sea level)
Compliance
Fuse types
14°F (-10°C) to 140°F (60°C)
10%-90% non-condensing
0 feet (0 m) to 8500 feet (2591 m)
UL 60950-1
Different models use different fuse types.
You must use the fuses listed below or equivalent according to the rating of your models:

16A models: Bussmann FWC-32A10F
(32A/600V)
Raritan part number: 557-90-0036-00

24A or 32A models: Bussmann
FWP-50A14F (50A/660V)
Raritan part number: 557-90-0038-00
You can also find the appropriate fuse types by checking the model names shown on the Raritan-provided fuses accompanying your PX3TS models.
Serial RS-232 "DB9" Port Pinouts
6
7
8
4
5
2
3
RS-232 Pin/signal definition
Pin No. Signal Direction Description
1 DCD Input Data
RxD
TxD
DTR
GND
DSR
RTS
CTS
Input
Output
Output
―
Input
Output
Input
Receive data (data in)
Transmit data
Data terminal ready
Signal ground
Data set ready
Request to send
Clear to send
537
538
Appendix A: Specifications
RS-232 Pin/signal definition
9 RI Input Ring indicator
Sensor RJ-45 Port Pinouts
1
2
3
RJ-45 Pin/signal definition
Pin No. Signal Direction
+12V
+12V
GND
―
―
―
Description
Power (fuse protected)
Power (fuse protected)
Signal Ground
4
5
6
7
8
RS485_DP bi-directiona l
Data Positive of the
RS-485 bus
RS485_DN bi-directiona l
Data Negative of the
RS-485 bus
GND
1-wire
GND
―
―
―
Signal Ground
Used for Feature Port
Signal Ground
Note: A maximum of 500mA power is permitted for both pin 1 and pin 2 altogether.
Feature RJ-45 Port Pinouts
1
2
3
RJ-45 Pin/signal definition
Pin No. Signal Direction Description
DTR
GND
+5V
Output
―
―
Reserved
Signal Ground
Power for CIM
(200mA, fuse protected)
Warning: Pin 3 is only intended for use with
Raritan devices.
Appendix A: Specifications
7
8
4
5
6
RJ-45 Pin/signal definition
Pin No. Signal Direction Description
TxD
RxD
+12V
Output
Input
―
Transmit Data (Data out)
Receive Data (Data in)
Warning: Pin 6 is only intended for use with
Raritan devices. Do NOT connect.
GND
DCD
―
Input
Signal Ground
Reserved
539
OUTLET 1
MODEL
SERIAL NUMBER
USE
OUTLET 4
MODEL
SERIAL NUMBER
USE
Appendix B Equipment Setup Worksheet
PX3TS Series Model ____________
PX3TS Series Serial Number ____________
OUTLET 2 OUTLET 3
MODEL
MODEL
SERIAL NUMBER
USE
SERIAL NUMBER
USE
OUTLET 5
MODEL
SERIAL NUMBER
USE
OUTLET 6
MODEL
SERIAL NUMBER
USE
540
OUTLET 7
MODEL
SERIAL NUMBER
USE
OUTLET 10
MODEL
SERIAL NUMBER
USE
OUTLET 13
MODEL
SERIAL NUMBER
USE
OUTLET 8
MODEL
SERIAL NUMBER
USE
OUTLET 11
MODEL
SERIAL NUMBER
USE
OUTLET 14
MODEL
SERIAL NUMBER
USE
OUTLET 9
Appendix B: Equipment Setup Worksheet
MODEL
SERIAL NUMBER
USE
OUTLET 12
MODEL
SERIAL NUMBER
USE
OUTLET 15
MODEL
SERIAL NUMBER
USE
541
542
Appendix B: Equipment Setup Worksheet
OUTLET 17 OUTLET 16
MODEL
SERIAL NUMBER
USE
OUTLET 19
MODEL
SERIAL NUMBER
USE
MODEL
USE
SERIAL NUMBER
USE
MODEL
SERIAL NUMBER
OUTLET 20
OUTLET 18
MODEL
SERIAL NUMBER
USE
OUTLET 21
MODEL
SERIAL NUMBER
USE
OUTLET 22
MODEL
SERIAL NUMBER
USE
OUTLET 23
MODEL
SERIAL NUMBER
USE
Appendix B: Equipment Setup Worksheet
OUTLET 24
MODEL
SERIAL NUMBER
USE
Types of adapters
_________________________________________________________
Types of cables
_________________________________________________________
Name of software program
_________________________________________________________
543
Appendix C Configuration or Firmware Upgrade with a USB Drive
You can accomplish part or all of the following tasks simultaneously by plugging a USB flash drive which contains one or several special configuration files into the PX3TS.
•
Configuration changes
• Firmware upgrade
• Downloading diagnostic data
Tip: You can also accomplish the same tasks via the TFTP server in a
DHCP network. See
Bulk Configuration or Firmware Upgrade via
DHCP/TFTP
(on page 557).
In This Chapter
System and USB Requirements ............................................................... 544
Firmware Upgrade via USB ...................................................................... 555
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.
PX3TS system requirements:
• There is at least one USB-A port available on your Raritan device.
• Your PX3TS must be version 2.2.13 or later.
Note that the PX3TS interpreted the USB drive's contents using the firmware which was running when plugging the USB drive, not the new firmware after firmware upgrade.
USB drive requirements:
•
The drive contains either a single partition formatted as a Windows
FAT32 filesystem, or NO partition tables (that is, a superfloppy-formatted drive).
• The drive contains a configuration file called directory. See
fwupdate.cfg
fwupdate.cfg
in its root
544
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
• config.txt:
This file is used for configuring device settings. See
config.txt
(on
• devices.csv:
This file is required only when there are device-specific settings to configure for multiple PX3TS devices. See
devices.csv
Raritan provides a Mass Deployment Utility, which helps you to quickly generate all configuration files for your PX3TS. See
Creating
Configuration Files via Mass Deployment Utility
545
546
Appendix C: Configuration or Firmware Upgrade with a USB Drive fwupdate.cfg
The configuration file,
fwupdate.cfg
key-value pairs, one per line.
, is an ASCII text file containing
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 use any options developed after version 2.2.13, the firmware version running on your PX3TS must be able to support them.
user
• A required option.
• Specify the name of a user account with Administrator Privileges.
• For a PX3TS with factory default configuration, set this option to admin
. password
•
A required option.
• Specify the password of the specified admin user.
• For a PX3TS with factory default configuration, set this option to raritan.
logfile
•
Specify the name of a text file where the PX3TS will append the log messages when interpreting the USB drive contents.
•
If the specified file does not exist in the USB drive, it will be automatically created.
• If this option is not set, no log message are recorded. The disadvantage is that no feedback is available if the PX3TS detects a problem with the USB drive contents. firmware
•
Specify the name of a firmware binary file used to upgrade your
PX3TS.
Appendix C: Configuration or Firmware Upgrade with a USB Drive
• The specified firmware file must be compatible with your PX3TS and have an official Raritan signature.
•
If the specified firmware file is the same as the current firmware version of your PX3TS, no firmware upgrade is performed unless you have set the option "force_update" to true. force_update
•
If this option is set to true, the firmware upgrade is always performed even though your PX3TS is running the same firmware version as the specified firmware file.
•
This option CANNOT break other constraints like the minimum downgrade version. config
• Supported as of release 2.4.0.
• Specify the name of the configuration file containing device settings.
• The suggested filename is
config.txt
. See
config.txt
device_list
•
Specify the name of the configuration file listing all PX3TS devices to configure and their device-specific settings.
• This file is required if any macros are used in the device configuration file "config.txt."
• The suggested filename is
devices.csv
. See
devices.csv
(on page match
•
Specify a match condition for identifying a line or a PX3TS device in the device configuration file "devices.csv."
The option's value comprises one word and one number as explained below:

The word prior to the colon is an identification property, which is either serial for serial number or mac for MAC address.

The number following the colon indicates a column in the
devices.csv
file.
For example, mac:7 instructs the PX3TS to search for the MAC address in the 7th column of the "devices.csv" file.
547
548
Appendix C: Configuration or Firmware Upgrade with a USB Drive
•
The default value is serial:1, making the PX3TS search for its serial number in the first column.
•
This option is used only if the "device_list" option has been set. collect_diag
• If this option is set to true, the diagnostic data of the PX3TS is downloaded to the USB drive.
• The filename of the diagnostic data written into the USB drive varies, depending on the PX3TS firmware version:

Filename prior to version 3.0.0:
diag_<unit-serial>.zip
<unit-serial> is the serial number of the PX3TS.
, where

Filename as of version 3.0.0:
diag_<unit-serial>.tgz
•
The PX3TS utters a short beep when writing the diagnostic data to the USB drive. factory_reset
•
Supported as of release 3.0.0.
•
If this option is set to true, the PX3TS 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
• Supported as of release 3.1.0.
• Specify the name of the bulk configuration file used to configure or restore the PX3TS.
Note: See
Bulk Configuration
(on page 336) for instructions on
generating a bulk configuration file.
Appendix C: Configuration or Firmware Upgrade with a USB Drive
• Additional configuration keys set via the
config.txt
after performing the bulk restore operation.
file will be applied
•
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
• Supported as of release 3.1.0.
•
Specify the name of the full configuration backup file used to restore the PX3TS.
Note: See
Backup and Restore of Device Settings
(on page 338) 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. execute_lua_script
•
Supported as of release 3.3.0.
•
Specify a LUA binding script file. For example: execute_lua_script=my_script.lua
•
Script output will be recorded to a log file --
<BASENAME_OF_SCRIPT>.<SERIAL_NUMBER>.log. Note this log file's size is limited on dhcp/tftp.
•
A dhcp/tftp-located script has a timeout of 60 seconds. After that duration the script will be removed.
•
If you unplug the USB drive while the LUA script is still running, the script will be removed.
• An exit handler can be used but the execution time is limited to three seconds. Note that this is not implemented on dhcp/tftp yet.
•
This feature can be used to manage LuaService, such as upload, start, get output, and so on.
549
550
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 the USB drive.
•
Reference the "config.txt" file in the
"fwupdate.cfg" file. See
config
option of the
fwupdate.cfg
The file,
config.txt
, is a text file containing a number of configuration keys and values to configure or update.
This section only introduces the device configuration file in brief, and does not document all configuration keys, which vary according to the firmware version and your PX3TS 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 PX3TS model and firmware version.
Tip: As of release 3.2.20, you can choose to encrypt important data in the
"config.txt" file so that people cannot easily recognize it, such as the
SNMP write community string. See
Data Encryption in 'config.txt'
(on
page 554).
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.
• As of release 3.1.0, multi-line values are supported by using the
Here Document Syntax
with a user-chosen delimiter.
The following illustration declares a value in two lines. You can replace the delimiter EOF with other delimiter strings. key<<EOF value line 1 value line 2
EOF
Note: The line break before the closing EOF is not part of the value. If a line break is required in the value, insert an additional empty line before the closing EOF.
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 the firmware's internal encryption/hashing algorithms is implemented as of release 2.2.13.
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 as of release 2.4.0.
Examples: magic:users[1].snmp_v3.auth_phrase=swordfish magic:users[1].snmp_v3.priv_phrase=opensesame
To configure device-specific settings:
1. Make sure the device list configuration file "devices.csv" is available in the USB drive. See
devices.csv
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: network.interfaces[eth0].ipaddr=${2} pdu.name=${16}
To rename the admin user:
As of release 3.1.0, you can rename the admin user by adding the following configuration key: users[0].name=new admin name
Example: users[0].name=May
551
552
Appendix C: Configuration or Firmware Upgrade with a USB Drive devices.csv
If there are device-specific settings to configure, you must create a device list configuration file -
PX3TS.
devices.csv
, to store unique data of each
This file must be:
•
An excel file in the CSV format.
• Copied to the root directory.
• Referenced in the
device_list
option of the "fwupdate.cfg" file. See
fwupdate.cfg
Every PX3TS identifies its entry in the "devicelist.csv" file by comparing its serial number or MAC address to one of the columns in the file.
Determine the column to identify PX3TS devices:
• By default, a PX3TS searches for its serial number in the 1st column.
• To override the default, set the file to a different column.
match
option in the "fwupdate.cfg"
Syntax:
•
Prior to release 3.1.0, only single-line values containing NO commas are supported. A comma is considered a field delimiter.
For example:
Value-1,Value-2,Value-3
•
As of release 3.1.0, values containing commas, line breaks or double quotes are all supported. The commas and line breaks to be included in the values must be enclosed in double quotes. Every double quote to be included in the value must be escaped with another double quote.
For example:
Value-1,"Value-2,with,three,commas",Value-3
Value-1,"Value-2,""with""three""double-quotes",Valu e-3
Value-1,"Value-2 with a line break", Value-3
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. Download the Mass Deployment Utility from the Raritan website.

The utility is named
mass_deployment-xxx
firmware version number).
(where xxx is the

It is available on the PX3TS section of the
(
http://www.raritan.com/support/
).
Support page
2. Launch Excel to open this utility.
Note: Other office suites, such as OpenOffice and LibreOffice, are not supported.
3. Read the instructions in the 1st worksheet of the utility, and make sure Microsoft Excel's security level has been set to Medium or the equivalent for executing unsigned macros of this utility.
4. Enter information in the 2nd and 3rd worksheets.

The 2nd worksheet contains information required for
fwupdate.cfg
and
config.txt
.

The 3rd worksheet contains device-specific information for
devices.csv
.
5. Return to the 2nd worksheet to execute the export macro. a. In the Target Directory field, specify the folder where to generate the configuration files. For example, you can specify the root directory of a connected USB drive. b. Click Export Lists to generate configuration files.
553
554
Appendix C: Configuration or Firmware Upgrade with a USB Drive
6. Verify that at least 3 configuration files are created -
fwupdate.cfg
,
config.txt
and
devices.csv
. You are ready to configure or upgrade any
PX3TS with these files. See
Configuration or Firmware Upgrade with a USB Drive
Data Encryption in 'config.txt'
Encryption for any settings in the file "config.txt" is supported as of release 3.2.20.
When intending to prevent people from identifying the values of any settings, you can encrypt them. Encrypted data still can be properly interpreted and performed by any PX3TS 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
2. Launch a terminal to log in to the CLI of any PX3TS running version
3.2.20 or later. See
Logging in to CLI
3. Type the encryption command and the value of the setting you want to encrypt.

The value
(-).
cannot
contain any double quotes (") or backslashes

If the value contains spaces, it must be enclosed in double quotes.
# config encrypt <value>
-- OR --
# config encrypt "<value with spaces>"
4. Press Enter. The CLI generates and displays the encrypted form of the typed value.
5. Go to the "config.txt" file and replace the chosen value with the encrypted one by typing or copying the encrypted value from the CLI.
6. Add the text "encrypted:" to the beginning of the encrypted setting.
7. Repeat steps 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 to configure any PX3TS running version 3.2.20 or later. See
Configuration or Firmware Upgrade with a USB Drive
(on page
Appendix C: Configuration or Firmware Upgrade with a USB Drive
Illustration:
In this example, we will encrypt the word "private", which is the value of the SNMP write community in the "config.txt" file.
1. In the CLI, type the following command to encrypt "private."
2. The CLI generates and shows the encrypted form of "private."
3. In the "config.txt" file, make the following changes to the SNMP write community setting. a. Replace the word "private" with the encrypted value that CLI shows. b. Add "encrypted:" to the beginning of that setting.
Firmware Upgrade via USB
(
Firmware files are available on Raritan website's
http://www.raritan.com/support/
).
Support page
Note that if the firmware file used for firmware upgrade is the same as the firmware version running on the PX3TS, no firmware upgrade will be performed unless you have set the
"fwupdate.cfg" file. See
force_update fwupdate.cfg
option to true in the
To use a USB drive to upgrade the PX3TS:
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 file.
image
option of the "fwupdate.cfg"
3. Plug the USB drive into the USB-A port on the PX3TS.
555
556
Appendix C: Configuration or Firmware Upgrade with a USB Drive
4. The PX3TS performs the firmware upgrade. The firmware upgrade message "FUP" is displayed on the front panel display.
Tip: You can remove the USB drive and plug it into another PX3TS for firmware upgrade when the firmware upgrade message displays.
5. It may take one to five minutes to complete the firmware upgrade, depending on your product.
6. When the firmware upgrade finishes, the front panel display indicates the firmware upgrade result.

Happy smiley: Successful.
Depending on your product, the happy smiley looks like one of the following.

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.
Appendix D Bulk Configuration or Firmware
Upgrade via DHCP/TFTP
If a TFTP server is available, you can use it and appropriate configuration files to perform any or all of the following tasks for a large number of
PX3TS devices in the same network.
•
Initial deployment
• Configuration changes
• Firmware upgrade
•
Downloading diagnostic data
This feature is drastically useful if you have hundreds or even thousands of PX3TS devices to configure or upgrade.
Warning: The feature of bulk configuration or firmware upgrade via
DHCP/TFTP only works on standalone PX3TS devices directly connected to the network. This feature does NOT work for slave devices in the USB-cascading configuration.
Tip: For the other alternative, see
Configuration or Firmware Upgrade with a USB Drive
(on page 544).
In This Chapter
Bulk Configuration/Upgrade Procedure .................................................. 557
DHCP IPv4 Configuration in Windows ...................................................... 559
DHCP IPv6 Configuration in Windows ...................................................... 569
DHCP IPv4 Configuration in Linux ............................................................ 576
DHCP IPv6 Configuration in Linux ............................................................ 578
Bulk Configuration/Upgrade Procedure
The DHCP/TFTP feature is supported as of release 3.1.0 so make sure that all PX3TS devices which you want to configure or upgrade are running firmware version 3.1.0 or later.
Steps of using DHCP/TFTP for bulk configuration/upgrade:
1. Create configuration files specific to your PX3TS models and firmware versions. See
Configuration Files
Raritan Technical Support to properly prepare some or all of the following files:

fwupdate.cfg (always required)
557
558
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP


config.txt
devices.csv
Note: Supported syntax of "fwupdate.cfg" and "config.txt" may vary based on different firmware versions. If you have existing configuration files, it is suggested to double check with Raritan
Technical Support for the correctness of these files prior to using this feature.
2. Configure your TFTP server properly. See
TFTP Requirements
(on
3. Copy ALL required configuration files into the TFTP root directory. If the tasks you will perform include firmware upgrade, an appropriate firmware binary file is also required.
4. Properly configure your DHCP server so that it refers to the file
"fwupdate.cfg" on the TFTP server for your PX3TS.
Click one or more of the following links for detailed DHCP configuration instructions, based on your system and the IP address type.




DHCP IPv4 Configuration in Windows
DHCP IPv6 Configuration in Windows
DHCP IPv4 Configuration in Linux
DHCP IPv6 Configuration in Linux
5. Make sure all of the desired PX3TS devices use DHCP as the IP configuration method and have been network.
directly
connected to the
6. Re-boot these PX3TS devices. The DHCP server will execute the commands in the "fwupdate.cfg" file on the TFTP server to configure or upgrade those PX3TS devices supporting DHCP in the same network.
DHCP will execute the "fwupdate.cfg" commands once for IPv4 and once for IPv6 respectively if both IPv4 and IPv6 settings are configured properly in DHCP.
TFTP Requirements
To perform bulk configuration or firmware upgrade successfully, your
TFTP server must meet the following requirements:
•
The server is able to work with both IPv4 and IPv6.
In Linux, remove any IPv4 or IPv6 flags from
/etc/xinetd.d/tftp
.
Note: DHCP will execute the "fwupdate.cfg" commands once for IPv4 and once for IPv6 respectively if both IPv4 and IPv6 settings are configured properly in DHCP.
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP
• All required configuration files are available in the TFTP root directory. See
Bulk Configuration/Upgrade Procedure
(on page
If you are going to upload any PX3TS diagnostic file or create a log file in the TFTP server, the first of the following requirements is also required.
• The TFTP server supports the write operation, including file creation and upload.
In Linux, provide the option "-c" for write support.
•
Required for uploading the diagnostic file only - the timeout for file upload is set to one minute or larger.
DHCP IPv4 Configuration in Windows
For those PX3TS 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 PX3TS under IPv4. a. Right-click the IPv4 node in DHCP to select Define Vendor
Classes. b. Click Add to add a new vendor class. c. Specify a unique name for this vendor class and type the binary codes of "Raritan PDU 1.0" in the New Class dialog.
559
560
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP
The vendor class is named "Raritan PDU" in this illustration.
2. Define one DHCP standard option - Vendor Class Identifier. a. Right-click the IPv4 node in DHCP to select Set Predefined
Options.
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select DHCP Standard Options in the "Option class" field, and
Vendor Class Identifier in the "Option name" field. Leave the
String field blank.
3. Add three options to the new vendor class "Raritan PDU" in the same dialog.
561
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Select Raritan PDU in the "Option class" field.
562 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 c. Click Add to add the second option. Type
"pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field. 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.
4. Create a new policy associated with the "Raritan PDU" vendor class. a. Right-click the Policies node under IPv4 to select New Policy. b. Specify a policy name, and click Next.
563
564
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP
The policy is named "PDU" in this illustration. c. Click Add to add a new condition.
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select the vendor class "Raritan PDU" in the Value field, click
Add and then Ok. e. Click Next.
565
566
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP f. Select DHCP Standard Options in the "Vendor class" field, select
"060 Vendor Class Identifier" from the Available Options list, and type "Raritan PDU 1.0" in the "String value" field.
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP g. Select the "Raritan PDU" in the "Vendor class" field, select "001 pdu-tftp-server" from the Available Options list, and type your
TFTP server's IPv4 address in the "IP address" field.
567
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP h. Select "002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field.
568 i. Select "003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third option/code is the magic cookie to prevent the
fwupdate.cfg
commands from being executed repeatedly. It does NOT matter whether the IPv4 magic cookie is identical to or different from the IPv6 magic cookie.
The magic cookie is a string comprising numerical and/or alphabetical digits in any format. In the following illustration diagram, it is a combination of a date and a serial number.
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP
Important: The magic cookie is transmitted to and stored in PX3TS at the time of executing the "fwupdate.cfg" commands. The
DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX3TS.
Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg" commands next time.
DHCP IPv6 Configuration in Windows
For those PX3TS 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 PX3TS under IPv6.
569
570
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Right-click the IPv6 node in DHCP to select Define Vendor
Classes. b. Click Add to add a new vendor class. c. Specify a unique name for the vendor class, type "13742" in the
"Vendor ID (IANA)" field, 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.
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.
571
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select Raritan PDU 1.0 in the "Option class" field.
572 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 d. Click Add to add the second option. Type
"pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field. 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.
3. Configure server options associated with the "Raritan PDU 1.0" vendor class. a. Right-click the Server Options node under IPv6 to select
Configure Options. b. Click the Advanced tab.
573
574
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP c. Select "Raritan PDU 1.0" in the "Vendor class" field, select
"00001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv6 address in the "IPv6 address" field.
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. 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, and type any string in the "String value" field. This third option/code is the magic cookie to prevent the
fwupdate.cfg
commands from being executed repeatedly. It does NOT matter whether the IPv6 magic cookie is identical to or different from the IPv4 magic cookie.
The magic cookie is a string comprising numerical and/or alphabetical digits in any format. In the following illustration diagram, it is a combination of a date and a serial number.
575
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP
Important: The magic cookie is transmitted to and stored in PX3TS at the time of executing the "fwupdate.cfg" commands. The
DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX3TS.
Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg" commands next time.
576
DHCP IPv4 Configuration in Linux
Modify the "dhcpd.conf" file for IPv4 settings when your DHCP server is running Linux.
Required Linux IPv4 settings in DHCP:
1. Locate and open the "dhcpd.conf" file of the DHCP server.
2. The PX3TS will provide the following value of the vendor-class-identifier option (option 60).
 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 PX3TS accepts the configuration 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 a combination of a date and a serial number.
Important: The magic cookie is transmitted to and stored in PX3TS at the time of executing the "fwupdate.cfg" commands. The
DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX3TS.
Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg" commands next time.
577
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP
IPv4 illustration example in dhcpd.conf:
578
DHCP IPv6 Configuration in Linux
Modify the "dhcpd6.conf" file for IPv6 settings when your DHCP server is running Linux.
Required Linux IPv6 settings in DHCP:
1. Locate and open the "dhcpd6.conf" file of the DHCP server.
2. The PX3TS will provide the following values to the "vendor-class" option (option 16). Configure related settings in DHCP accordingly.

13742 (Raritan's IANA number)

Raritan PDU 1.0

15 (the length of the above string "Raritan PDU 1.0")
3. Set the following three sub-options in the "vendor-opts" (option 17).
 code 1 (pdu-tftp-server) = the TFTP server's IPv6 address
 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 a combination of a date and a serial number.
Important: The magic cookie is transmitted to and stored in PX3TS at the time of executing the "fwupdate.cfg" commands. The
DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX3TS.
Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg" commands next time.
IPv6 illustration example in dhcpd6.conf:
579
Appendix E Resetting to Factory Defaults
You can use either the reset button or the command line interface (CLI) to reset the PX3TS.
Important: Exercise caution before resetting the PX3TS 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
In This Chapter
Using the Reset Button
The reset button described in this section is the one near the LCD display.
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 PX3TS device. See
Connecting the PX3TS to a Computer
2. Launch a terminal emulation program such as HyperTerminal,
Kermit, or PuTTY, and open a window on the PX3TS. For information on the serial port configuration, see Step 2 of
Initial Network
Configuration via CLI
3. Press (and release) the Reset button of the PX3TS device while pressing the Esc key of the keyboard several times in rapid succession. A prompt (=>) should appear after about one second.
4. Type
defaults
to reset the PX3TS to its factory defaults.
580
Appendix E: Resetting to Factory Defaults
5. Wait until the Username prompt appears, indicating the reset is complete.
Note: HyperTerminal is available on Windows operating systems prior to
Windows Vista. For Windows Vista or later versions, you may use PuTTY, which is a free program you can download from the Internet. See
PuTTY's documentation for details on configuration.
Using the CLI Command
The Command Line Interface (CLI) provides a reset command for restoring the PX3TS to factory defaults. For information on CLI, see
Using the Command Line Interface
To reset to factory defaults after logging in to the CLI:
1. Connect to the PX3TS device. See
Logging in to CLI
Connecting the PX3TS to a Computer
2. Launch a terminal emulation program such as HyperTerminal,
Kermit, or PuTTY, and open a window on the PX3TS. For information on the serial port configuration, see Step 2 of
Initial Network
Configuration via CLI
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
/y
5. 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 Username prompt appears, indicating the reset is complete.
To reset to factory defaults without logging in to the CLI:
The PX3TS provides an easier way to reset the product to factory defaults in the CLI prior to login.
1. Connect to the PX3TS and launch a terminal emulation program as described in the above procedure.
2. At the Username prompt in the CLI, type "factorydefaults" and press
Enter.
581
Appendix E: Resetting to Factory Defaults
Username:
factorydefaults
3. Type y on a confirmation message to perform the reset.
582
Appendix F 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 PX3TS b. Create user groups for the PX3TS on the AD server c. Configure LDAP authentication on the PX3TS device d. Configure roles on the PX3TS device
Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4,
3.0.20 and later releases 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 .......................................... 583
Step B. Configure User Groups on the AD Server ................................... 584
Step C. Configure LDAP Authentication on the PX3TS Device ............... 585
Step D. Configure Roles on the PX3TS Device......................................... 586
Step A. Determine User Accounts and Roles
Determine the user accounts and roles (groups) that are authenticated for accessing the PX3TS. 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
PX_User
PX_Admin
User accounts (members) usera pxuser2 userb pxuser
Group permissions:
• The PX_User role will have neither system permissions nor outlet permissions.
•
The PX_Admin role will have full system and outlet permissions.
583
584
Appendix F: LDAP Configuration Illustration
Step B. Configure User Groups on the AD Server
You must create the groups (roles) for the PX3TS on the AD server, and then make appropriate users members of these groups.
In this illustration, we assume:
•
The groups (roles) for the PX3TS 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: See the documentation or online help accompanying Microsoft
AD for detailed instructions.
2. Add the
pxuser2
and
usera
accounts to the PX_User group.
3. Add the
pxuser
and
userb
accounts to the PX_Admin group.
4. Verify whether each group comprises correct users.
Appendix F: LDAP Configuration Illustration
Step C. Configure LDAP Authentication on the PX3TS Device
You must enable and set up LDAP authentication properly on the PX3TS device to use external authentication.
In the illustration, we assume:
•
The DNS server settings have been configured properly. See
Wired
Network Settings
Role of a DNS Server
(on page
• 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 PX3TS 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
.
Important: Without the encryption enabled, you can type either the domain name or IP address in this field, but you must type the fully qualified domain name if the encryption is enabled.
Copy settings from existing LDAP server
Type of LDAP Server
Security
Port (None/StartTLS)
Port (TLS),
CA Certificate
Anonymous Bind
Leave the checkbox deselected unless the new LDAP server's settings are similar to any existing LDAP settings.
Select "Microsoft Active Directory."
Select "None" since the TLS encryption is not applied in this example.
Ensure the field is set to 389.
Skip the two fields since the TLS encryption is not enabled.
Select this checkbox because anonymous bind is used.
585
586
Appendix F: LDAP Configuration Illustration
Field/setting
Bind DN,
Bind Password,
Confirm Bind Password
Base DN for Search
Do this...
Skip the three fields because of anonymous bind.
Type dc=techadssl,dc=com as the starting point where your search begins on the AD server.
Login Name Attribute
Ensure the field is set to sAMAccountName because the LDAP server is Microsoft Active Directory.
User Entry Object Class Ensure the field is set to user because the LDAP server is Microsoft
Active Directory.
User Search Subfilter The field is optional. The subfilter information is also useful for filtering out additional objects in a large directory structure. In this example, we leave it blank.
Active Directory Domain Type techadssl.com.
4. Click Add Server.The LDAP server is saved.
5. In the Authentication Type field, select LDAP.
6. Click Save. The LDAP authentication is activated.
Note: If the PX3TS clock and the LDAP server clock are out of sync, the installed TLS certificates, if any, may be considered expired. To ensure proper synchronization, administrators should configure the PX3TS and the LDAP server to use the same NTP server(s).
Step D. Configure Roles on the PX3TS Device
A role on the PX3TS device determines the system and outlet permissions. You must create the roles whose names are identical to the user groups created for the PX3TS on the AD server or authorization will fail. Therefore, we will create the roles named on the PDU.
PX_User
and
PX_Admin
In this illustration, we assume:
• Users assigned to the
PX_User
role can view settings only, but they can neither configure PX3TS nor access the outlets.
• Users assigned to the
PX_Admin
role have the Administrator
Privileges so they can both configure PX3TS and access the outlets.
To create the PX_User role with appropriate permissions assigned:
1. Choose User Management > Roles.
Appendix F: LDAP Configuration Illustration
2. Click to add a new role. a. Type PX_User in the Role Name field. b. Type a description for the PX_User role in the Description field.
In this example, we type "View PX settings" to describe the role. c. In the Privileges list, select Unrestricted View Privileges, which includes all View permissions. The Unrestricted View Privileges permission lets users view all settings without the capability to configure or change them. d. Click Save.
3. The PX_User role is created.
4. Keep the Roles page open to create the PX_Admin role.
587
Appendix F: LDAP Configuration Illustration
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. c. In the Privileges list, select Administrator Privileges. The
Administrator Privileges allows users to configure or change all
PX3TS settings.
588 d. Click Save.
2. The PX_Admin role is created.
Appendix G Updating the LDAP Schema
In This Chapter
Returning User Group Information .......................................................... 589
Setting the Registry to Permit Write Operations to the Schema ........... 590
Adding Attributes to the Class.................................................................. 591
Updating the Schema Cache .................................................................... 593
Editing rciusergroup Attributes for User Members ................................ 593
Returning User Group Information
Use the information in this section to return User Group information (and assist with authorization) once authentication is successful.
From LDAP/LDAPS
When an LDAP/LDAPS authentication is successful, the PX3TS determines the permissions for a given user based on the permissions of the user's role. Your remote LDAP server can provide these user role names by returning an attribute named as follows: rciusergroup attribute type: string
This may require a schema extension on your LDAP/LDAPS server.
Consult your authentication server administrator to enable this attribute.
In addition, for Microsoft
®
Active Directory
®
, the standard LDAP memberOf is used.
From Microsoft Active Directory
Note: This should be attempted only by an experienced Active Directory
®
administrator.
Returning user role information from Microsoft's
®
Active Directory for
Windows 2000
®
operating system server requires updating the
LDAP/LDAPS schema. See your Microsoft documentation for details.
1. Install the schema plug-in for Active Directory. See Microsoft Active
Directory documentation for instructions.
2. Run Active Directory Console and select Active Directory Schema.
589
Appendix G: 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 the window and then click Operations Master. The Change Schema
Master dialog appears.
590
2. Select the "Schema can be modified on this Domain Controller" checkbox. Optional
3. Click OK.
Creating a New Attribute
To create new attributes for the rciusergroup class:
1. Click the + symbol before Active Directory
®
Schema in the left pane of the window.
2. Right-click Attributes in the left pane.
Appendix G: 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 from the list.
9. Type
1
in the Minimum field.
10. Type
24
in the Maximum field.
11. Click OK to create the new attribute.
Adding Attributes to the Class
To add attributes to the class:
1. Click Classes in the left pane of the window.
591
Appendix G: Updating the LDAP Schema
2. Scroll to the user class in the right pane and right-click it.
592
3. Choose Properties from the menu. The user Properties dialog appears.
4. Click the Attributes tab to open it.
5. Click Add.
Appendix G: Updating the LDAP Schema
6. Choose rciusergroup from the Select Schema Object list.
7. Click OK in the Select Schema Object dialog.
8. Click OK in the User Properties dialog.
Updating the Schema Cache
To update the schema cache:
1. Right-click Active Directory
®
Schema in the left pane of the window and select Reload the Schema.
2. Minimize the Active Directory Schema MMC (Microsoft
®
Management
Console) console.
Editing rciusergroup Attributes for User Members
To run the Active Directory
®
script on a Windows 2003
®
server, use the script provided by Microsoft
®
(available on the Windows 2003 server installation CD). These scripts are loaded onto your system with a
Microsoft
®
Windows 2003 installation. ADSI (Active Directory Service
Interface) acts as a low-level editor for Active Directory, allowing you to perform common administrative tasks such as adding, deleting, and moving objects with a directory service.
To edit the individual user attributes within the group rciusergroup:
1. From the installation CD, choose Support > Tools.
2. Double-click SUPTOOLS.MSI to install the support tools.
593
594
Appendix G: Updating the LDAP Schema
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 G: Updating the LDAP Schema
6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties.
7. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list.
8. Click Edit. The String Attribute Editor dialog appears.
9. Type the user role (created in the PX3TS) in the Edit Attribute field.
Click OK.
595
Appendix H RADIUS Configuration Illustration
This section provides illustrations for configuring RADIUS authentication.
One illustration is based on the Microsoft
®
Network Policy Server (NPS), and the other is based on a FreeRADIUS server.
The following steps are required for any RADIUS authentication:
1. Configure RADIUS authentication on the PX3TS. See
Adding Radius
Servers
2. Configure roles on the PX3TS. See
Creating Roles
3. Configure PX3TS user credentials and roles on your RADIUS server.

To configure using standard attributes, see
Standard Attributes

To configure using vendor-specific attributes, see
Vendor-Specific Attributes
Note that we assume that the NPS is running on a Windows 2008 system in the NPS illustrations.
In This Chapter
Standard Attributes
The RADIUS standard attribute "Filter-ID" is used to convey the group membership, that is, roles.
• If a user has multiple roles, configure multiple standard attributes for this user.
•
The syntax of a standard attribute is:
Raritan:G{role-name}
For configuration on NPS, see
NPS Standard Attribute Illustration
(on
For configuration on FreeRADIUS, see
FreeRADIUS Standard Attribute
Illustration
NPS Standard Attribute Illustration
To configure Windows 2008 NPS with the
standard attribute
, you must: a. Add your PX3TS to NPS. See
Step A: Add Your PX3TS as a RADIUS
Client
596
Appendix H: RADIUS Configuration Illustration b. On the NPS, configure Connection Request Policies and the standard attribute. See
Step B: Configure Connection Policies and Standard
Attributes
Some configuration associated with Microsoft Active Directory (AD) is also required for RADIUS authentication. See
AD-Related Configuration
Step A: Add Your PX3TS as a RADIUS Client
The RADIUS implementation on a PX3TS 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 PX3TS = 192.168.56.29
•
RADIUS authentication port specified for PX3TS:
1812
•
RADIUS accounting port specified for PX3TS:
1813
To add your PX3TS to the RADIUS NPS:
1. Choose Start > Administrative Tools > Network Policy Server. The
Network Policy Server console window opens.
597
Appendix H: RADIUS Configuration Illustration
2. Right-click NPS (Local), and select Properties.
598
Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX3TS. In this example, they are 1812 and 1813. Then close this dialog.
Appendix H: 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 PX3TS to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b. Type a name for identifying your PX3TS 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.
599
Appendix H: RADIUS Configuration Illustration f. Type the shared secret in the "Shared secret" and "Confirm shared secret" fields. The shared secret must be the same as the one specified on your PX3TS.
600
5. Click OK.
Appendix H: 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 PX3TS
•
Connection request forwarding method
• Authentication method(s)
• Standard RADIUS attributes
Presumptions in the illustration:
•
IP address of your PX3TS = 192.168.56.29
•
Local
NPS server is used
• RADIUS protocol selected on your PX3TS = CHAP
• Existing role of your PX3TS = Admin
Illustration:
1. Open the NPS console, and expand the Policies folder.
601
602
Appendix H: 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.
Appendix H: RADIUS Configuration Illustration

You can leave the "Type of network access server" field to the default -- Unspecified.
603
Appendix H: RADIUS Configuration Illustration
4. Click Next to show the "Specify Conditions" screen. Click Add.
604
5. The "Select condition" dialog appears. Click Add.
Appendix H: RADIUS Configuration Illustration
6. The NAS IPv4 Address dialog appears. Type the PX3TS 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 is used in this example. Then click Next.
605
Appendix H: RADIUS Configuration Illustration
Note: Connection Request Forwarding options must match your environment.
606
9. When the system prompts you to select the authentication method, select the following two options:

Override network policy authentication settings

CHAP -- the PX3TS uses "CHAP" in this example
Appendix H: RADIUS Configuration Illustration
Note: If your PX3TS uses PAP, then select "PAP."
607
608
Appendix H: RADIUS Configuration Illustration
10. Select Standard to the left of the dialog and then click Add.
Appendix H: RADIUS Configuration Illustration
11. Select Filter-Id from the list of attributes and click Add.
609
610
Appendix H: RADIUS Configuration Illustration
12. In the Attribute Information dialog, click Add.
13. Select String, type
OK.
Raritan:G{Admin}
in the text box, and then click
Appendix H: RADIUS Configuration Illustration
Admin
inside the curved brackets {} is the existing role on the PX3TS.
It is recommended to use the Admin role to test this configuration.
The role name is case sensitive.
611
Appendix H: RADIUS Configuration Illustration
14. The new attribute is added. Click OK.
612
15. Click Next to continue.
Appendix H: RADIUS Configuration Illustration
613
Appendix H: RADIUS Configuration Illustration
16. A summary showing connection request policy settings is displayed.
Click Finish to close the dialog.
614
FreeRADIUS Standard Attribute Illustration
With standard attributes, NO dictionary files are required. You simply add all user data, including user names, passwords, and roles, in the following FreeRADIUS path.
/etc/raddb/users
Presumptions in the illustration:
•
User name = steve
•
Steve's password = test123
•
Steve's roles = Admin and SystemTester
To create a user profile for "steve" in FreeRADIUS:
1. Go to this location: /etc/raddb/users.
2. Add the data of the user "steve" by typing the following. Note that the values after the equal sign (=) must be enclosed in double quotes (").
Appendix H: 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-specific attribute (VSA).
• Vendor code = 13742
• Vendor-assigned attribute number = 26
•
Attribute format = String
The syntax of the vendor-specific attribute for specifying one or multiple roles is:
Raritan:G{role-name1 role-name2 role-name3}
For configuration on NPS, see
NPS VSA Illustration
For configuration on FreeRADIUS, see
FreeRADIUS VSA Illustration
(on
NPS VSA Illustration
To configure Windows 2008 NPS with the must:
vendor-specific attribute
, you a. Add your PX3TS to NPS. See
Step A: Add Your PX3TS as a RADIUS
Client
b. On the NPS, configure connection request policies and the vendor-specific attribute. See
Step B: Configure Connection
Policies and Vendor-Specific Attributes
Some configuration associated with Microsoft Active Directory (AD) is also required for RADIUS authentication. See
AD-Related Configuration
615
616
Appendix H: RADIUS Configuration Illustration
Step A: Add Your PX3TS as a RADIUS Client
The RADIUS implementation on a PX3TS 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 PX3TS = 192.168.56.29
• RADIUS authentication port specified for PX3TS:
1812
•
RADIUS accounting port specified for PX3TS:
1813
To add your PX3TS to the RADIUS NPS:
1. Choose Start > Administrative Tools > Network Policy Server. The
Network Policy Server console window opens.
Appendix H: RADIUS Configuration Illustration
2. Right-click NPS (Local), and select Properties.
Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX3TS. In this example, they are 1812 and 1813. Then close this dialog.
617
618
Appendix H: 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 PX3TS to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b. Type a name for identifying your PX3TS 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 H: RADIUS Configuration Illustration f. Type the shared secret in the "Shared secret" and "Confirm shared secret" fields. The shared secret must be the same as the one specified on your PX3TS.
5. Click OK.
619
620
Appendix H: 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 PX3TS
•
Connection request forwarding method
• Authentication method(s)
• Standard RADIUS attributes
Presumptions in the illustration:
•
IP address of your PX3TS = 192.168.56.29
•
Local
NPS server is used
• RADIUS protocol selected on your PX3TS = CHAP
• Existing roles of your PX3TS = Admin, User and SystemTester
Illustration:
1. Open the NPS console, and expand the Policies folder.
Appendix H: 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.
621
622
Appendix H: RADIUS Configuration Illustration

You can leave the "Type of network access server" field to the default -- Unspecified.
Appendix H: RADIUS Configuration Illustration
4. Click Next to show the "Specify Conditions" screen. Click Add.
5. The "Select condition" dialog appears. Click Add.
623
624
Appendix H: RADIUS Configuration Illustration
6. The NAS IPv4 Address dialog appears. Type the PX3TS 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 is used in this example. Then click Next.
Appendix H: RADIUS Configuration Illustration
Note: Connection Request Forwarding options must match your environment.
9. When the system prompts you to select the authentication method, select the following two options:

Override network policy authentication settings

CHAP -- the PX3TS uses "CHAP" in this example
625
Appendix H: RADIUS Configuration Illustration
Note: If your PX3TS uses PAP, then select "PAP."
626
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: 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 H: 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-attribute configuration on FreeRADIUS. Therefore, there are two major configuration steps. a. Use a dictionary to define the Raritan vendor-specific attribute b. Add all user data, including user names, passwords, and roles
Presumptions in the illustration:
•
Raritan attribute = Raritan-User-Roles
•
User name = steve
•
Steve's password = test123
•
Steve's roles = Admin, User and SystemTester
Step A -- define the vendor-specific attribute in FreeRADIUS:
1. Go to this location: /etc/raddb/dictionary.
2. Type the following in the Raritan dictionary file.
627
628
Appendix H: 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 the values after the equal sign (=) must be enclosed in double quotes ("). steve Cleartext-Password := "test123"
Raritan-PDU-User-Roles = "Raritan:G{Admin User SystemTester}"
AD-Related Configuration
When RADIUS authentication is intended, make sure you also configure the following settings related to Microsoft Active Directory (AD):
• Register the NPS server in AD
• Configure remote access permission for users in AD
The NPS server is registered in AD only when NPS is configured for the
FIRST time and user accounts are created in AD.
If CHAP authentication is used, you must enable the following feature for user accounts created in AD:
• Store password using reversible encryption
Important: Reset the user password if the password is set before you enable the "Store password using reversible encryption" feature.
To register NPS:
1. Open the NPS console.
Appendix H: RADIUS Configuration Illustration
2. Right-click NPS (Local) and select "Register server in Active
Directory."
3. Click OK, and then OK again.
To grant PX3TS users remote access permission:
1. Open Active Directory Users and Computers.
629
Appendix H: RADIUS Configuration Illustration
2. Open the properties dialog of the user whom you want to grant the access permission.
3. Click the Dial-in tab and select the "Allow access" checkbox.
630
To enable reversible encryption for CHAP authentication:
1. Open Active Directory Users and Computers.
2. Open the properties dialog of the user that you want to configure.
Appendix H: RADIUS Configuration Illustration
3. Click the Account tab and select the "Store password using reversible encryption" checkbox.
631
Appendix I Additional PX3TS Information
In This Chapter
SecureLock™ Outlets and Cords ............................................................. 632
Reserving IP Addresses in DHCP Servers ............................................... 634
PDView App for Viewing the PX3TS .......................................................... 644
Ways to Probe Existing User Profiles ...................................................... 647
Cascading Troubleshooting ...................................................................... 648
Browsing through the Online Help ........................................................... 653
SecureLock™ Outlets and Cords
SecureLock
™
is an innovative mechanism designed by Raritan, which securely holds C14 or C20 plugs that are plugged into Raritan PDUs in place. This method requires the following two components:
• Raritan PDU with SecureLock
™
outlets, which have a latch slot inside either side of the outlet.
•
SecureLock
™
cords, which is a power cord with a locking latch on each side of its plug. The following diagram illustrates such a plug.
Item
A
Description
Latches on the SecureLock
™
cord's plug
632
Appendix I: Additional PX3TS Information
Only specific PDUs are implemented with the SecureLock
™
mechanism.
If your PDU does not have this design, do NOT use the SecureLock
™
cords with it.
Tip: The SecureLock
™
outlets can accept regular power cords for power distribution but the SecureLock
™
mechanism does not take effect.
To lock a power cord using the SecureLock
™
mechanism:
1. Verify that the SecureLock
™
cord you purchased meets your needs.

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.
2. Connect the SecureLock
™
cord between the IT equipment and your
PDU.

Plug the female socket end of the cord into the power socket of the desired 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 slots of the outlet.
To remove a SecureLock
™
power cord from the PDU:
1. Press and hold down the two latches on the cord's plug as illustrated in the diagram below.
2. Unplug the cord now.
633
634
Appendix I: Additional PX3TS Information
Reserving IP Addresses in DHCP Servers
The PX3TS uses its serial number as the client identifier in the DHCP request. Therefore, to successfully reserve an IP address for the PX3TS in a DHCP server, use the PX3TS device's serial number as the unique ID instead of the MAC address.
Since all network interfaces of the PX3TS can be simultaneously enabled and configured with diverse static IP addresses, the client identifier of each network interface is different. The main difference is the absence/presence of a suffix, which is the interface name added to the end of the serial number. The table below lists the client identifiers of all network interfaces.
Interface
ETHERNET
WIRELESS
BRIDGE
Client Identifier serial number serial number plus the uppercase suffix "-WIRELESS" serial number
You can reserve the IP addresses of more than one interfaces in the
DHCP server if preferred. Note that you must choose/configure the bridge interface if your PX3TS is set to the bridging mode.
Important: In the bridging mode, only the IP parameters of the
BRIDGE interface function. The IP parameters of the ETHERNET and
WIRELESS interfaces do NOT function.
Reserving IP in Windows
To reserve the IP address of any network interface in the Windows DHCP server, you must convert that interface's client identifier into
hexadecimal
ASCII codes.
For each interface's client identifier, see
Reserving IP Addresses in
DHCP Servers
In the following illustration, it is assumed that the PX3TS serial number is PEG1A00003.
Windows IP address reservation illustration:
1. Convert the client identifier of the desired network interface into
ASCII codes (
hexadecimal
).
Interface
ETHERNET
Client identifier conversion
PEG1A00003 = 50 45 47 31 41 30 30 30 30 33
Appendix I: Additional PX3TS Information
Interface
WIRELESS
Client identifier conversion
PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30
33 2D 57 49 52 45 4C 45 53 53

The suffix comprising the dash symbol and the word "WIRELESS" is also converted.
PEG1A00003 = 50 45 47 31 41 30 30 30 30 33 BRIDGE
2. In your DHCP server, bring up the New Reservation dialog, and separate the converted ASCII codes with spaces.
For example, to reserve the IP address of the ETHERNET interface, enter the following data in the dialog.
Field
IP address
MAC address
Other fields
Data entered
The IP address you want to reserve.
The following ASCII codes.
50 45 47 31 41 30 30 30 30 33
Configure as needed.
635
636
Appendix I: Additional PX3TS Information
Reserving IP in Linux
There are two methods to reserve the IP address of any network interface in the standard Linux DHCP server (ISC DHCP server):
•
Convert an interface's client identifier into
hexadecimal
ASCII codes.
•
Use an interface's original client identifier without converting it into
ASCII codes.
For each interface's client identifier, see
Reserving IP Addresses in
DHCP Servers
In the following illustrations, it is assumed that the PX3TS 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
ETHERNET
WIRELESS
Client identifier conversion
PEG1A00003 = 50 45 47 31 41 30 30 30 30 33
PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30
33 2D 57 49 52 45 4C 45 53 53

The suffix comprising the dash symbol and the word "WIRELESS" is also converted.
PEG1A00003 = 50 45 47 31 41 30 30 30 30 33 BRIDGE
2. Separate the converted ASCII codes with a colon, and a prefix "00:" must be added to the beginning of the converted codes.
For example, the
converted
client identifier of the ETHERNET interface looks like the following:
00:50:45:47:31:41:30:30:30:30:33
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.
Appendix I: Additional PX3TS Information
For example, the client identifier of the ETHERNET interface looks like the following:
\000
PEG1A00003
3. Now enter the original client identifier with the following syntax. The client identifier is enclosed in quotation marks. host mypx { option dhcp-client-identifier = "\000PEG1A00003"; fixed-address 192.168.20.1;
}
Sensor Threshold Settings
This section explains the thresholds settings for a numeric sensor.
Thresholds and Sensor States
A numeric sensor has four thresholds: Lower Critical, Lower Warning,
Upper Warning and Upper Critical.
The threshold settings determine how many sensor states are available for a certain sensor and the range of each sensor state. The diagram below shows how each threshold relates to each state.
637
638
Appendix I: Additional PX3TS Information
above upper critical
Upper Critical
above upper warning
Upper Warning
normal
Lower Warning
below lower warning
Lower Critical
below lower critical
Available sensor states:
Appendix I: Additional PX3TS Information
The more thresholds are enabled for a sensor, the more sensor states are available for it. The "normal' state is always available regardless of whether any threshold is enabled.
For example:
•
When a sensor only has the Upper Critical threshold enabled, it has two sensor states: normal and above upper critical.
• When a sensor has both the Upper Critical and Upper Warning thresholds enabled, it has three sensor states: normal, above upper warning, and above upper critical.
States of "above upper warning" and "below lower warning" are warning states to call for your attention.
States of "above upper critical" and "below lower critical" are critical states that require you to immediately handle.
Range of each available sensor state:
The value of each enabled threshold determines the reading range of each available sensor state. For details, see
Yellow- or Red-Highlighted
Sensors
639
640
Appendix I: Additional PX3TS Information
"To Assert" and Assertion Timeout
If multiple sensor states are available for a specific sensor, the PX3TS asserts a state for it whenever a bad state change occurs.
To assert a state:
To assert a state is to announce a new, "worse" state.
Below are bad state changes that cause the PX3TS 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:
Appendix I: Additional PX3TS Information
In the threshold settings, the Assertion Timeout field postpones or even cancels the "assertion" action. It determines how long a sensor must be in the "worse" new state before the PX3TS triggers the "assertion" action.
If that sensor changes its state again within the specified wait time, the
PX3TS does NOT assert the worse state.
To disable the assertion timeout, set it to 0 (zero).
Note: For most sensors, the measurement unit in the "Assertion
Timeout" field is sample. Sensors are measured every second, so the timing of a sample is equal to a second. 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 PX3TS to send notifications for assertion events, setting the "Assertion Timeout" is helpful for eliminating a number of notifications that you may receive in case the sensor's readings fluctuate around a certain threshold.
Assertion Timeout Example for Temperature Sensors
Assumption:
Upper Warning threshold is enabled.
Upper Warning = 25 (degrees Celsius)
Assertion Timeout = 5 samples (that is, 5 seconds)
When a temperature sensor's reading exceeds 25 degrees Celsius, moving from the "normal" range to the "above upper warning" range, the
PX3TS does NOT immediately announce this warning state. Instead it waits for 5 seconds, and then does either of the following:
•
If the temperature remains above 25 degrees Celsius in the "above upper warning" range for 5 seconds, the PX3TS performs the
"assertion" action to announce the "above upper warning" state.
• If the temperature drops below 25 degrees Celsius within 5 seconds, the PX3TS does NOT perform the "assertion" action.
641
642
Appendix I: Additional PX3TS Information
"To De-assert" and Deassertion Hysteresis
After the PX3TS asserts a worse state for a sensor, it may de-assert that state later on if the readings improve.
To de-assert a state:
To de-assert a state is to announce the end of the previously-asserted worse state.
Below are good state changes that cause the PX3TS 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:
Appendix I: Additional PX3TS Information
In the threshold settings, the Deassertion Hysteresis field determines a new level to trigger the "deassertion" action.
This function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system when the temperature exceeds a pre-determined level. "Deassertion Hysteresis" instructs the PX3TS to de-assert the worse state for a sensor only when that sensor's reading reaches the pre-determined "deassertion" level.
For upper thresholds, this "deassertion" level is a decrease against each threshold. For lower thresholds, this level is an increase to each threshold. The absolute value of the decrease/increase is exactly the hysteresis value.
For example, if Deassertion Hysteresis = 2, then:
• Upper Critical = 33, so its "deassertion" level = 33 - 2 = 31.
•
Upper Warning = 25, so its "deassertion" level = 25 - 2 = 23.
•
Lower Critical = 10, so its "deassertion" level = 10 + 2 = 12.
• Lower Warning = 18, so its "deassertion" level = 18 + 2 = 20.
To use each threshold as the "deassertion" level instead of determining a new level, set the Deassertion Hysteresis to 0 (zero).
How "Deassertion Hysteresis" is helpful:
If you have created an event rule that instructs the PX3TS to send notifications for deassertion events, setting the "Deassertion Hysteresis" is helpful for eliminating a number of notifications that you may receive in case a sensor's readings fluctuate around a certain threshold.
Deassertion Hysteresis Example for Temperature Sensors
643
644
Appendix I: Additional PX3TS 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 PX3TS 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
PX3TS does NOT perform the "deassertion" action.
•
If the temperature drops to 17 degrees Celsius or lower, the PX3TS performs the "deassertion" action to announce the end of the "above upper warning" state.
PDView App for Viewing the PX3TS
Raritan has developed an app that can turn your iOS or Android mobile device into a local display for the PX3TS.
This app is called PDView and it can be downloaded for free.
PDView is especially helpful when your PX3TS is not connected to the network but you need to check the PX3TS status, retrieve basic information, or even change network settings.
Requirements for using PDView:
• The PX3TS is running firmware version 3.0.0 or later.
• If you are using an Android device, it must support USB "On-The-Go"
(OTG).
•
An appropriate USB cable is required.

For Android, you need an USB OTG adapter cable.

For iOS, use the USB cable shipped with your iOS mobile device.
To install PDView:
1. Use your mobile device to download the PDView app from the Google
Play or Apple's App Store.
Appendix I: Additional PX3TS Information
2. After installing the PDView, launch it. Below illustrates the PDView screen for Android devices.
3. Connect your mobile device to the USB port of the PX3TS.
Your mobile device type determines which USB port on the PX3TS shall be used to connect the mobile device. The PDView will automatically detect and indicate the appropriate USB port for connecting your mobile device.
645
Appendix I: Additional PX3TS Information
The PDView shows a "Connected" message when it detects the physical connection to the PX3TS.
646
4. Log in to the PDView app at the login prompt. Now you can view limited PX3TS information or even change some settings.
Tip: To skip the final login step, you can click the upper right icon of
PDView to save one or multiple user credentials. Next time the app automatically logs in when it detects the PX3TS.
Altitude Correction Factors
If a Raritan differential air pressure sensor is attached to your device, the altitude you enter for the device can serve as an altitude correction factor. That is, the reading of the differential air pressure sensor will be multiplied by the correction factor to get a correct reading.
This table shows the relationship between different altitudes and correction factors.
Altitude (meters)
0
250
Altitude (feet)
0
820
Correction factor
0.95
0.98
Appendix I: Additional PX3TS Information
Altitude (meters)
425
500
740
1500
2250
3000
Altitude (feet)
1394
1640
2428
4921
7382
9842
Correction factor
1.00
1.01
1.04
1.15
1.26
1.38
Ways to Probe Existing User Profiles
This section indicates available ways to query existing user accounts on the PX3TS.
•
With SNMP v3 activated, you get the "user unknown" error when the user name used to authenticate does not exist.
• Any user with the permission to view event rules can query all local existing users via JSON RPC.
•
Any user with the permission to view the event log may get information about existing users from the log entries.
•
Any authenticated users can query currently-existing connection sessions, including Webcam-Live-Preview sessions, which show a list of associated user names.
Raritan Training Website
Raritan offers free training materials for various Raritan products on the
Raritan training website http://www.raritantraining.com
. The Raritan products introduced on this website include the intelligent PDU, dcTrack
®
, Power IQ, KVM, EMX, BCM and CommandCenter Secure
Gateway (CC-SG). Raritan would update the training materials irregularly according to the latest development of Raritan products.
To get access to these training materials or courses, you need to apply for a username and password through the Raritan training website. After you are verified, you can access the Raritan training website anytime.
Having access to the training website could be helpful for learning or getting some ideas regarding Raritan products and making correct decisions on purchasing them. For example, you can take the dcTrack video training before implementing or using it.
647
648
Appendix I: Additional PX3TS Information
Role of a DNS Server
As Internet communications are carried out on the basis of IP addresses, appropriate DNS server settings are required for mapping domain names (host names) to corresponding IP addresses, or the PX3TS may fail to connect to the given host.
Therefore, DNS server settings are important for external authentication.
With appropriate DNS settings, the PX3TS can resolve the external authentication server's name to an IP address for establishing a connection. If the
SSL/TLS encryption
used for specifying the LDAP server.
is enabled, the DNS server settings become critical since only fully qualified domain name can be
For information on external authentication, see
Setting Up External
Authentication
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
PX3TS to a computer if network access to that PX3TS fails. See
Connecting the PX3TS to a Computer
Appendix I: Additional PX3TS Information
Symptom
Failure to access the master device
Probable cause
•
Network connection to the master device is lost.
•
No power is supplied to the master device.
• The Ethernet or wireless interface on the master device is disabled.
• IPv4 (or IPv6) settings are disabled on the master device.
•
In the port forwarding mode, the master device's role is incorrectly set to 'Slave'.
•
In the port forwarding mode, the interface where the network is connected is incorrectly selected as the downstream interface.
• For the wireless networking, one of the following may lead to the accessibility failure:

The USB wireless LAN adapter attached to the master device is not the Raritan USB WIFI LAN adapter. See
USB Wireless LAN Adapters
(on page

The wireless LAN configuration is not supported. See
Supported Wireless LAN Configuration
(on page

The installed CA certificate chain contains any certificate that has expired or is not valid yet.
649
650
Appendix I: Additional PX3TS Information
Symptom Probable cause
Failure to access a slave device
•
Network connection to the master device is lost.
•
The cascading cable connected to the slave device in question or any upstream device (if available) is loose or lost.
• No power is supplied to the slave device in question or any upstream devices.
•
The Ethernet or wireless interface on the master device is disabled.
•
IPv4 (or IPv6) settings are disabled on the slave device in question.
• The cascading mode of the slave device in question or any upstream device is set incorrectly. For example, the master device is set to Bridging, but one of the slave devices is set to Port Forwarding.
•
In the port forwarding mode, the master device's role is incorrectly set to 'Slave'.
• In the port forwarding mode, the master device's downstream interface is incorrectly set. For example, you use a USB cable to connect the 1st slave device, but select the Ethernet port as the downstream interface.
• In the port forwarding mode, the role of the slave device in question or any upstream device is set to 'Master' instead of 'Slave'.
•
In the port forwarding mode, the port number you added to the IP address is incorrect. See
Port Number Syntax
• The firmware version of the slave device in question or any upstream device is older than 3.3.10.
Tip: To determine which PX3TS may be the failure point of network, you may ping each PX3TS in the cascading chain, or check the slave-related events in the event log of each PX3TS. See
Slave Connection and
Disconnection Events
(on page 651).
Appendix I: Additional PX3TS Information
Slave Connection and Disconnection Events
In the bridging mode, events regarding connection/disconnection of a downstream slave device via USB is NOT logged.
However, in the port forwarding mode, whenever the connection or disconnection of a downstream slave device via USB is detected, the
PX3TS at the USB-A end of the USB cable logs it in the internal log. Note that the PX3TS at the USB-B end of the cable does NOT log these events.
There are two slave-related events:
Event Description
Slave connected This log entry is generated when a PX3TS detects the presence of a slave device on its USB-A port.
Slave disconnected
This log entry is generated when it detects the disconnection of a slave device from its USB-A port.
The Ping Tool
The PX3TS provides a ping tool in the web interface and CLI so you can ping any host or PX3TS in your data center.
Ping via the Web Interface
To log in to the web interface, see
HTTP/HTTPS Access
Login
The Ping tool is useful for checking whether a host is accessible through the network or Internet.
To ping a host:
1. Choose Maintenance > Network Diagnostics.
2. Type values in the following fields.
Field
Network Host
Description
The name or IP address of the host that you want to check.
Number of
Requests
A number up to 20.
This determines how many packets are sent for pinging the host.
3. Click Run Ping to ping the host. The Ping results are then displayed.
651
652
Appendix I: Additional PX3TS Information
Ping via the CLI
You can access the CLI interface by connecting a computer to the PX3TS or using SSH/Telnet. See
SSH/Telnet Access
With SSH or Telnet
You must perform the ping command in the diagnostic mode. To enter the diagnostic mode, type the following command and press Ener.
# diag
After the diag> or diag# prompt appears, you can perform the ping command.
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 ping command.
Options count <number1> size <number2>
Description
Determines the number of messages to be sent. <number1> is an integer number between 1 and 100.
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>
Appendix I: Additional PX3TS Information ping <host> count <number1> size <number2> timeout <number3>
Browsing through the Online Help
The PX3TS Online Help is accessible over the Internet.
To use online help, Active Content must be enabled in your browser. If you are using Internet Explorer 7, you must enable Scriplets. Consult your browser help for information on enabling these features.
To use the PX3TS online help:
1. Click Online Documentation. See
Web Interface Overview
(on page
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:

To view the next topic, click the Next icon in the toolbar.

To view the previous topic, click the Previous icon .

To view the first topic, click the Home icon .
5. To expand or collapse a topic that contains sub-topics, do the following:

To expand any topic, click the white arrow prior to the topic, or double-click that topic. The arrow turns into a black, gradient arrow , and sub-topics appear below the topic.

To collapse any expanded topic, click the black, gradient arrow prior to the topic, or double-click the expanded topic. The arrow then turns into a white arrow , and all sub-topics below that topic disappear.
6. To search for specific information, type the key word(s) or string(s) in the Search text box, and press Enter or click the Search icon to start the search.

If necessary, select the "Match partial words" checkbox to include information matching part of the words entered in the
Search text box.
The search results are displayed in the left pane.
7. To have the left pane show the list of topics, click the Contents tab at the bottom.
8. To show the Index page, click the Index tab.
653
Appendix I: Additional PX3TS Information
9. To email any URL link to the currently selected topic to any person, click the "Email this page" icon in 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
.
654
Appendix J Integration
The PX3TS device can work with certain Raritan products to provide diverse power solutions.
In This Chapter
Dominion KX II / III Configuration ............................................................. 655
Dominion KSX II, SX or SX II Configuration .............................................. 660
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.
655
656
Appendix J: Integration
Configuring Rack PDU Targets
KX III allows you to connect rack PDUs (power strips) to KX III ports.
KX III rack PDU configuration is done from the KX III Port Configuration page.
Note: Raritan recommends no more than eight (8) rack PDUs (power strips) be connected to a KX III at once since performance may be affected.
Connecting a PX PDU
Raritan PX series rack PDUs (power strips) are connected to the
Dominion device using the D2CIM-PWR CIM.
To connect the rack PDU:
1. Connect the male RJ-45 of the D2CIM-PWR to the following female
RJ-45 connector of the rack PDU.

PX1 series: RJ-45 "SERIAL" port

PX2 or PX3 series: RJ-45 "FEATURE" port
2. Connect the female RJ-45 connector of the D2CIM-PWR to any of the available female system port connectors on the KX III using a straight through Cat5 cable.
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.
Appendix J: Integration
Diagram key
PX rack PDU
D2CIM-PWR
KX III
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 name to the outlet.
To name the rack PDU and outlets:
Note: CommandCenter Secure Gateway does not recognize rack PDU names containing spaces.
1. Enter the Name of the rack PDU (if needed).
2. Change the [Outlet] Name if desired. (Outlet names default to the outlet #.)
657
Appendix J: Integration
3. Click OK.
658
Appendix J: 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 name is replaced by the target server name (even if you assigned another name to the outlet).
1. On the Port Configuration page, select the target server you are associating the PDU with.
2. Choose the rack PDU from the Power Strip Name drop-down list.
3. For that rack PDU, choose the outlet from the Outlet Name drop-down list.
4. Repeat steps 1 and 2 for all desired power associations.
5. Click OK. A confirmation message is displayed.
Turning Outlets On/Off and Cycling Power
To turn an outlet on:
1. Click the Power menu to access the Powerstrip page.
2. From the Powerstrip drop-down, select the PX rack PDU (power strip) you want to turn on.
3. Click Refresh to view the power controls.
4. Click On next to the outlet you want to power on.
5. Click OK to close the Power On confirmation dialog. The outlet will be turned on and its state will be displayed as 'on'.
659
660
Appendix J: Integration
To turn an outlet off:
1. Click Off next to the outlet you want to power off.
2. Click OK on the Power Off dialog.
3. Click OK on the Power Off confirmation dialog. The outlet will be turned off and its state will be displayed as 'off'.
To cycle the power of an outlet:
1. Click Cycle next to the outlet you want to cycle. The Power Cycle Port dialog opens.
2. Click OK. The outlet will then cycle (note that this may take a few seconds).
3. Once the cycling is complete the dialog will open. Click OK to close the dialog.
Dominion KSX II, SX or SX II Configuration
Raritan PX3TS support the integration with Raritan's serial access products - Dominion KSX II, Dominion SX and Dominion SX II.
Cables used for connecting the PX3TS to different Dominion access products are different.
•
KSX II - a standard network patch cable (CAT5 or higher)
• SX - a CSCSPCS cable
• SX II - a CSCSPCS cable
Note: To only access the CLI of the PX3TS via SX / SX II, treat the PX3TS 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
(
http://www.raritan.com/support/
)
Support page
•
KSX II, SX or SX II Online Help on the
(
Product Online Help page http://www.raritan.com/support/online-help/
)
Dominion KSX II
After connecting a Dominion KSX II to the Raritan PDU, you can monitor the PDU and even control its outlets if the PDU is an outlet-switching capable model.
Appendix J: Integration
Connecting a Rack PDU
To connect the Raritan PX to the KSX II:
1. Connect one end of a Cat5 cable to the following ports of different
Raritan PX.

PX1 series: RJ-45 "SERIAL" port

PX2 or PX3 series: RJ-45 "FEATURE" port
2. Connect the other end of the Cat5 cable to either the Power Ctrl. 1 or
Power Ctrl. 2 ports on the back of the KSX II.
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 be correctly detected, especially after swapping 8 and 20 outlet rack PDU models.
Diagram key
KSX II
KSX II Power
Ctrl. 1 Port or
Power Ctrl. 2
Port
PX
PX SERIAL or
FEATURE port
Cat5 cable
661
662
Appendix J: Integration
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
Dominion SX and SX II
By connecting to a Dominion SX or SX II device, you can associate one or more outlets on a PX3TS device to specific SX or SX II ports.
Dominion SX II
The way to use Dominion SX II to configure and control a Raritan PDU is similar to using Dominion KX III, but the connection method is different from KX III.
Note: If using a CSCSPCS-1 cable for the connection, it must be "Rev.0C".
If using a CSCSPCS-10 cable, it must be "Rev.0D".
Note that the appliances used in the diagram may not match your specific models. However, the connections and ports used are the same across models.
To connect the SX II to the Feature port on the PX:
1. Connect the gray end of the CSCSPCS crossover Cat5 cable into the
Feature port on the PX.
2. Connect the yellow end of the CSCSPCS crossover Cat5 cable into a port on the SX II.
3. Power on the PX (if it is not already).
Appendix J: Integration
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
Dominion SX
Configuring a PX3TS on Dominion SX
1. Choose Setup > Power Strip Configuration.
2. Click Add. The Power Strip Configuration screen appears.
663
Appendix J: Integration
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.
Power Control
1. Choose Power Control > Power Strip Power Control. The Outlet
Control screen appears.
664
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.
Checking Power Strip Status
1. Choose Power Control > Power Strip Status.
Appendix J: Integration
2. A status box appears, displaying details of the controlled PX3TS, including power state of each outlet on the device.
Power IQ Configuration
Sunbird's Power IQ is a software application that collects and manages the data from different PDUs installed in your server room or data center.
With this software, you can:
•
Do bulk configuration for multiple PDUs
•
Name outlets on different PDUs
• Switch on/off outlets on outlet-switching capable PDUs
For more information on Power IQ, refer to the Power IQ online help on the Sunbird website:
http://support.sunbirddcim.com.
665
666
Appendix J: Integration
dcTrack
Sunbird's dcTrack
®
is a product that allows you to manage the data center. The PX3TS is categorized as a power item in dcTrack. dcTrack offers an import wizard for conveniently adding the PX3TS as well as other IT equipment to dcTrack for management.
You can use dcTrack to:
•
Record and manage the data center infrastructure and assets
• Monitor the electrical consumption of the data center
• Track environmental factors in the data center, such as temperature and humidity
•
Optimize the data center growth
For more information on dcTrack, refer to the online help accessible from the dcTrack application, or user documentation available on the
Sunbird's website:
http://support.sunbirddcim.com
.
Appendix J: Integration dcTrack Overview dcTrack
®
is a powerful and intelligent data center management and automation application.
It has been designed by data center and IT professionals to provide broad and deep visibility into the data center. It empowers data center managers to plan for growth and change by optimizing their current operations, assets, and infrastructure.
With dcTrack, you can view everything in the data center from servers, blades, virtual servers and applications to data networks, IP addressing space and cabling. dcTrack also allows you to track real-time power consumption and manage raised floor space and rack elevations.
Use dcTrack to build your floor map data center map directly in the application, or import an existing floor map into the dcTrack. Further, dcTrack allows you to import AutoCAD
®
2012 (and earlier) objects to build a data center map.
If you currently maintain data center information in spreadsheet format, that data can be imported into dcTrack using the Import wizard.
Isolate potential problems with end-to-end power and data circuits by visually tracing them. This allows you to identify all intermediate circuit points and locate problems.
By using dcTrack's workflow and change management feature, data center managers are better able to enforce best practices across the enterprise and meet ITIL framework guidelines. You can also opt to skip the Change Control workflow process and work in Request Bypass so requests are processed immediately. dcTrack
®
can be used as a standalone product or integrated with Power
IQ
®
for power and environmental monitoring.
667
668
Appendix J: Integration
Asset Management Strips and dcTrack
If any asset strips are connected to the PX3TS, the PX3TS can transmit their information to Sunbird's dcTrack. All you have to do is to add the
PX3TS to dcTrack, and also add each IT item where an asset tag is attached to dcTrack.
Note: For instructions on connecting asset strips, see
Connecting Asset
Management Strips
(on page 46).
If SNMP is enabled, event information can be transmitted to dcTrack.
Specifically, Sunbird's Power IQ detects when an asset tag is connected or disconnected from an asset strip. Power IQ then generates a connection or disconnection event. When dcTrack polls Power IQ, the connection/disconnection events are pulled into dcTrack, and displayed in the dcTrack Web Client.
To poll and display asset management events in dcTrack
•
The PX3TS that the asset strip is connected to must exist in dcTrack.
EMX devices are identified as probes in dcTrack; Raritan PDUs are identified as sensors.
• Each IT item connected to the asset strip via an asset tag must exist in dcTrack.
You do not need to manually enter the asset tag IDs for IT items that already exist in dcTrack as long as these items are in the Installed status.
Simply, plug the item's asset tag into an asset strip that is connected to the PX3TS that exists in dcTrack. dcTrack automatically assigns the asset tag ID to the existing IT item.
Note: If needed, the asset tag number can be overwritten.
For more information on dcTrack as well as how asset strips work with dcTrack, contact Sunbird Professional Services and Support from the http://support.sunbirddcim.com.
Index
A
A Note about Enabling Thresholds • 357
A Note about Firmware Upgrade Time • 336
A Note about Infinite Loop • 309
A Note about Untriggered Rules • 310
About the Interface • 359
Action Group • 282, 284
Active Inlet Indicator Lamps • 67, 68, 70
Actuator Configuration Commands • 482, 483,
500
Actuator Control Operations • 522
Actuator Information • 377
Adding a Firewall Rule • 442
Adding a Monitored Device • 501
Adding a Role-Based Access Control Rule •
455
Adding Attributes to the Class • 592
Adding LDAP/LDAPS Servers • 248, 250, 255
Adding Radius Servers • 248, 253, 255, 597
Adding, Removing or Swapping Cascaded
Devices • 228
Additional PX3TS Information • 633
AD-Related Configuration • 598, 616, 629
Alarm • 281, 283
Alarm Indicator Lamps • 63, 64, 66, 67, 71, 74,
94
All Privileges • 471, 477, 481
Altitude Correction Factors • 133, 408, 647
APIPA and Link-Local Addressing • 4, 101, 221,
236
Assertion Timeout Example for Temperature
Sensors • 642
Asset Management Commands • 507
Asset Management Strips and dcTrack • 669
Asset Strip • 184, 185
Asset Strip Automatic Firmware Upgrade •
193
Asset Strip Information • 90
Asset Strip Management • 507
Asset Strip Settings • 386
Associating Outlets with Target Devices • 660
Automatic Retransfer • 64, 129
Automatic Transfer • 62
Automatic Transfer Scenarios • 62
Automatically Completing a Command • 529
Available Actions • 58, 231, 262, 281, 284, 290,
298, 305, 344, 351
Available Data of the Outlets Overview Page •
147, 149, 152, 153
B
Backup and Restore of Device Settings • 326,
337, 339, 550
Backup and Restore via SCP • 340, 533
Beeper • 94, 98, 99, 136
Before Connecting Equipment to Feature Port
• 47
Before You Begin • 5
Blade Extension Strip Settings • 388
Browsing through the Online Help • 105, 654
Built-in Rules and Rule Configuration • 262,
263, 305
Bulk Configuration • 22, 326, 337, 339, 532,
549
Bulk Configuration for Outlet Thresholds • 147,
150, 157
Bulk Configuration Methods • 14, 22
Bulk Configuration or Firmware Upgrade via
DHCP/TFTP • 22, 335, 338, 545, 558
Bulk Configuration via SCP • 338, 532
Bulk Configuration/Upgrade Procedure • 558,
560
C
Calendar • 260
Canceling the Power-On Process • 522
Cascading Guidelines for Port Forwarding • xvii, 24
Cascading Multiple PX3TS Devices for Sharing
Ethernet Connectivity • xvii, 23, 210, 221,
328
Cascading the PX3TS via USB • xvii, 11, 24, 76,
77
Cascading Troubleshooting • xviii, 24, 228, 649
Change Load Shedding State • 281, 285
669
Index
Changing a User's Password • 465
Changing an Outlet's Default State • 461
Changing HTTP(S) Settings • 207, 229, 230,
237
Changing Measurement Units • 471, 474
Changing Modbus Settings • 207, 229, 235
Changing SSH Settings • 199, 207, 229, 234
Changing Telnet Settings • 207, 229, 234, 359
Changing the Inlet Name • 463
Changing the LAN Duplex Mode • xviii, 421
Changing the LAN Interface Speed • xviii, 420
Changing the Modbus Configuration • 433
Changing the Modbus Port • 434
Changing the Outlet Name • 460
Changing the Overcurrent Protector Name •
464
Changing the PDU Name • 402
Changing the Role(s) • 471
Changing the Sensor Description • 485
Changing the Sensor Name • 483
Changing the SSH Configuration • 430
Changing the SSH Port • 430
Changing the Telnet Configuration • 429
Changing the Telnet Port • 430
Changing the UDP Port • 506
Changing Your Own Password • 473
Changing Your Password • 102, 197, 199
Checking Lua Scripts States • 322, 323, 324
Checking Power Strip Status • 666
Checking the Accessibility of NTP Servers •
440
Checking the Branch Circuit Rating • 6
Clearing Event Log • 395
Clearing Information • 395
Clearing WLAN Log • 396
Closing a Local Connection • 362
Combining Regular Asset Strips • 48
Command History • 392
Commands for Environmental Sensors • 495
Commands for Inlet Sensors • 489
Commands for Outlet Sensors • 491
Commands for Overcurrent Protector Sensors
• 493
Commands for Transfer Switch Sensors • 497
Common Network Settings • 208, 210 config.txt • 546, 548, 551
670
Configuration Files • 546, 558
Configuration or Firmware Upgrade with a
USB Drive • 22, 338, 545, 555, 558
Configuring a PX3TS on Dominion SX • 664
Configuring Data Push Settings • 207, 286, 311
Configuring DNS Parameters • xvii, 419
Configuring Environmental Sensors' Default
Thresholds • 487
Configuring IPv4 Parameters • xvii, 410
Configuring IPv6 Parameters • 414
Configuring Login Settings • 207, 237, 256, 347
Configuring Network Services • 229, 360
Configuring Network Settings • 5, 17, 207, 208,
216
Configuring NTP Server Settings • 356
Configuring Password Policy • 207, 237, 257
Configuring Power Quality Parameters • 69,
400
Configuring Power Transfer Features • 71,
399
Configuring Rack PDU Targets • 657
Configuring Security Settings • 237
Configuring SMTP Settings • 207, 229, 232,
289, 292
Configuring SNMP Settings • 199, 207, 229,
231, 281, 350
Configuring the Cascading Mode • xviii, 426
Configuring the PX3TS • 13
Configuring the Serial Port • 58, 59, 207, 318,
361
Configuring Webcams and Viewing Live
Images • 57, 345, 348
Connecting a DPX2 Sensor Package to DPX3 •
37, 46
Connecting a DPX2 Sensor Package to DX • 36,
39, 40, 46
Connecting a GSM Modem • 58, 291
Connecting a Logitech Webcam • xvii, 57, 344
Connecting a PX PDU • 657
Connecting a Rack PDU • 662
Connecting a Schroff LHX/SHX Heat
Exchanger • 59, 194
Connecting an Analog Modem • 58, 361
Connecting an External Beeper • 59, 193
Connecting Asset Management Strips • 47,
185, 311, 669
Connecting Blade Extension Strips • 52
Connecting Composite Asset Strips
(AMS-Mx-Z) • 55
Connecting Environmental Sensor Packages •
28, 165
Connecting External Equipment (Optional) • 28,
77
Connecting Power and Equipment • 11
Connecting Regular Asset Strips to PX • xvii,
50, 55
Connecting the PX3TS to a Computer • xvii, 4,
13, 14, 221, 581, 582, 649
Connecting the PX3TS to Your Network • 11,
13, 208
Connection Port Functions • 76
Control Buttons • 79
Control Push Buttons • 72, 73
Controlling the Transfer Switch • 397
Creating a CSR • 242, 243, 244
Creating a New Attribute • 591
Creating a Role • 477
Creating a Self-Signed Certificate • 242, 245
Creating a User Profile • 464
Creating Configuration Files via Mass
Deployment Utility • 546, 554, 555
Creating IP Access Control Rules • 207, 237,
239
Creating Role Access Control Rules • 207, 237,
240, 241
Creating Roles • 102, 197, 201, 203, 597
Creating Users • 101, 102, 197, 198, 202, 203,
204, 206, 234, 248, 350
Customizing the Date and Time • 438
D
Daisy-Chain Limitations of Composite Asset
Strips • 56
Dashboard • 94, 106, 110, 162, 283
Dashboard - Alarms • 111, 118, 281
Dashboard - Alerted Sensors • 111, 114
Dashboard - Inlet 1/2 • 111, 113, 122
Dashboard - Inlet History • 111, 116, 143
Dashboard - OCP • 111, 119
Dashboard - Transfer Switch • 111, 112, 122
Data Encryption in 'config.txt' • 551, 555
Date and Time Settings • 374
Index dcTrack • 667 dcTrack Overview • 668
Deassertion Hysteresis Example for
Temperature Sensors • 644
Default Log Messages • 258, 263, 268, 286,
289
Default Measurement Units • 374
Deleting a Firewall Rule • 445
Deleting a Monitored Device • 502
Deleting a Role • 482
Deleting a Role-Based Access Control Rule •
457
Deleting a User Profile • 473
Deleting an NTP Server • xviii, 437
Detailed Information on Outlet Pages • 154,
158
Determining the SSH Authentication Method •
431
Determining the Time Setup Method • 436,
438
Device Information • 326, 327
Device Settings • 107, 207 devices.csv • 546, 548, 552, 553
Device-Specific Settings NOT Included • 337,
339
DHCP IPv4 Configuration in Linux • 559, 577
DHCP IPv4 Configuration in Windows • 559,
560
DHCP IPv6 Configuration in Linux • 559, 579
DHCP IPv6 Configuration in Windows • 559,
570
Diagnostic Commands • 527
Different CLI Modes and Prompts • 360, 361,
362, 364, 395, 396, 397, 440, 517, 519, 522,
527
Dominion KSX II • 661
Dominion KSX II, SX or SX II Configuration •
197, 661
Dominion KX II / III Configuration • 197, 656
Dominion SX • 664
Dominion SX and SX II • 663
Dominion SX II • xviii, 663
Downloading Diagnostic Data via SCP • xviii,
534
Downloading Diagnostic Information • 326,
342
671
Index
Downloading SNMP MIB • 232, 350, 353
DPX Sensor Packages • 28, 29
DPX2 Sensor Packages • 28, 34
DPX3 Sensor Packages • 28, 36
DX Sensor Packages • 28, 38, 296
E
EAP CA Certificate Example • 423, 425
Editing or Deleting a Rule/Action • 281, 305,
317
Editing or Deleting IP Access Control Rules •
239
Editing or Deleting Ping Monitoring Settings •
315
Editing or Deleting Role Access Control Rules
• 241
Editing or Deleting Roles • 204
Editing or Deleting Users • 102, 202, 204, 205
Editing rciusergroup Attributes for User
Members • 594
Email and SMS Message Placeholders • 288,
289, 291, 302
Enabling and Configuring SNMP • 306, 307,
310, 350
Enabling or Disabling a User Profile • 467
Enabling or Disabling Data Logging • 407
Enabling or Disabling EnergyWise • 505
Enabling or Disabling Front Panel Outlet
Switching • 458
Enabling or Disabling Load Shedding • 518
Enabling or Disabling Modbus • 433
Enabling or Disabling Peripheral Device Auto
Management • 409
Enabling or Disabling Service Advertising •
434
Enabling or Disabling SNMP v1/v2c • 431
Enabling or Disabling SNMP v3 • 432
Enabling or Disabling SSH • 430
Enabling or Disabling Strong Passwords • 451
Enabling or Disabling Telnet • 429
Enabling or Disabling the LAN Interface • xviii,
420
Enabling or Disabling the Read-Only Mode •
434
Enabling or Disabling the Restricted Service
Agreement • 446
672
Enabling Service Advertising • 207, 229, 236,
434
Enabling the Restricted Service Agreement •
102, 207, 237, 258
EnergyWise Configuration Commands • 505
EnergyWise Settings • 386
Entering Configuration Mode • 362, 396, 399,
400, 425, 465, 473
Entering Diagnostic Mode • 362, 526
Environmental Sensor Configuration
Commands • 482
Environmental Sensor Default Thresholds •
382
Environmental Sensor Information • 86, 375
Environmental Sensor Package Information •
376
Environmental Sensor Threshold Information
• 381
Equipment Setup Worksheet • 6, 541
Ethernet Interface Settings • 209, 211
Event Log • 389
Event Rules and Actions • 59, 118, 136, 142,
150, 161, 178, 196, 207, 231, 232, 262, 283,
311, 313, 322
Example • 400, 402, 438, 447, 465, 473, 515,
518
Ping Monitoring and SNMP Notifications •
313, 315
Example - Actuator Naming • 501
Example - Creating a Role • 482
Example - Default Upper Thresholds for
Temperature • 489
Example - Inlet Naming • 463
Example - OCP Naming • 464
Example - Outlet Naming • 462
Example - Ping Command • 529
Example - Power Cycling Specific Outlets •
522
Example - Server Settings Changed • 504
Example - Setting Up EnergyWise • 507
Example - Turning On a Specific Actuator •
524
Example 1 • 309
Example 1 - Asset Strip LED Colors for
Disconnected Tags • 513
Example 1 - Basic Security Information • 393
Example 1 - Combination of IP, Subnet Mask and Gateway Parameters • 516
Example 1 - Creating a User Profile • 476
Example 1 - Environmental Sensor Naming •
487
Example 1 - IPv4 Firewall Control
Configuration • 458
Example 1 - Networking Mode • 435
Example 1 - PDU Naming • 409
Example 1 - Time Setup Method • 439
Example 1 - Upper Critical Threshold for a
Temperature Sensor • 499
Example 2 • 309
Example 2 - Adding an IPv4 Firewall Rule •
459
Example 2 - Combination of Upper Critical and
Upper Warning Settings • 516
Example 2 - Data Logging Enabled • 409
Example 2 - Enabling Both IP Protocols • 435
Example 2 - In-Depth Security Information •
394
Example 2 - Modifying a User's Roles • 476
Example 2 - Primary NTP Server • 439
Example 2 - Rack Unit Naming • 514
Example 2 - Sensor Threshold Selection • 487
Example 2 - Warning Thresholds for Inlet
Sensors • 498
Example 3 • 309
Example 3 - Basic PDU Information • 394
Example 3 - Combination of SSID and PSK
Parameters • 517
Example 3 - Default Measurement Units • 476
Example 3 - Outlet Sequence Delay • 409
Example 3 - Upper Thresholds for Overcurrent
Protector Sensors • 499
Example 3 - User Blocking • 459
Example 3 - Wireless Authentication Method •
435
Example 4 - Adding an IPv4 Role-based
Access Control Rule • 459
Example 4 - In-Depth PDU Information • 395
Example 4 - Non-Critical Outlets • 410
Example 4 - Static IPv4 Configuration • 435
Examples • 393, 409, 435, 439, 458, 475, 486,
498, 513
Existing Roles • 385
Index
Existing User Profiles • 374, 384
External Beeper • 184, 193, 282, 285
F
Feature Port • 107, 183, 185, 193, 195, 197
Feature RJ-45 Port Pinouts • 539
Filling Out the Equipment Setup Worksheet •
6
Finding the Sensor's Serial Number • 167, 174
Firewall Control • 440
Firmware Update via SCP • 335, 531
Firmware Upgrade via USB • xviii, 335, 556
Forcing a Password Change • 467
Forcing the Device Detection Mode • 515
FreeRADIUS Standard Attribute Illustration •
597, 615
FreeRADIUS VSA Illustration • 616, 628
From LDAP/LDAPS • 590
From Microsoft Active Directory • 590
Front Panel Settings • 169, 207, 317
Front View • 2
Full Disaster Recovery • 336
Fuses for the Inlet Transfer Switch • xvii, 71,
94, 98 fwupdate.cfg • 545, 546, 547, 551, 553, 556
G
Gathering LDAP/Radius Information • 248, 249
H
Help Command • 363
History Buffer Length • 392
How the Automatic Management Function
Works • 133, 139, 409
I
Identifying Cascaded Devices • 327, 328
Identifying the Sensor Position and Channel •
167, 175
Idle Timeout • 449
Individual Inlet Pages • 113, 124, 131, 134, 142
Individual OCP Pages • 162
Individual Outlet Pages • 132, 133, 134, 137,
138, 146, 148, 152, 153, 159
673
Index
Individual Sensor/Actuator Pages • 114, 133,
139, 166, 168, 169, 178, 182
Initial Installation and Configuration • 11
Initial Network Configuration via CLI • xvii, 13,
15, 17, 581, 582
Initialization Delay Use Cases • 132, 138
Inlet and Outlet Power Connections • 10
Inlet Configuration Commands • 462
Inlet Configuration Indicator Lamps • 68, 70
Inlet Information • 80, 372
Inlet Phase Sync Angle Information • 366
Inlet Sensor Threshold Information • 379
Inlets • 107, 141, 142
Inrush Current and Inrush Guard Delay • 133,
138
Installing a CA-Signed Certificate • 242, 244
Installing or Downloading Existing Certificate and Key • 242, 246
Installing the USB-to-Serial Driver (Optional) •
15, 16
Integration • 656
Interface Names • 217, 220
Internal Beeper • 282, 286
Internal Beeper State • 131, 135
Introduction • 1
Introduction to Asset Tags • xvii, 50
IP Configuration • xvii, 367, 368
IPv4 Address • xvii, 5, 13, 14, 83, 221
IPv4-Only or IPv6-Only Configuration • xvii,
367, 368
L
Layout • 355
LCD Display • 78
LDAP Configuration Illustration • 248, 584
Load Shedding Configuration Commands •
517
Load Shedding Mode • 147, 149, 151, 152, 155,
285, 406
Load Shedding Settings • 385
Log an Event Message • 282, 286
Logging in to CLI • 359, 555, 582
Logging out of CLI • 530
Login • 13, 14, 15, 101, 652
Login Limitation • 448
Login, Logout and Password Change • 101
674
Logout • 103
Lowercase Character Requirement • 451
Lua Scripts • 207, 295, 319
M
MAC Address • 85
Maintenance • 108, 326
Make a Power Association • 660
Managed vs Unmanaged Sensors/Actuators •
165, 170, 171
Managing External Authentication Settings •
248, 252, 254, 255
Managing Firewall Rules • 442
Managing One Sensor or Actuator • 167, 168,
176
Managing Role-Based Access Control Rules •
454
Manual Transfer • 11, 64, 70, 71, 73, 96, 97
Manual Transfer Scenarios • 66, 67, 398
Manual Transfer When an Alarm is Present •
66, 67, 72, 95, 96
Manually Starting or Stopping a Script • 320,
321, 322
Maximum Password History • 453
Maximum Password Length • 451
Menu • 104, 106, 121, 131, 141, 145, 160, 165,
184, 185, 193, 194, 197, 207, 321, 326, 345,
347, 348
Minimum Password Length • 451
Miscellaneous • 59, 88, 184, 185, 194, 207, 288,
295, 325, 327, 354
Mixing Diverse Sensor Types • 41, 42
Modifying a Firewall Rule • 444
Modifying a Monitored Device's Settings • 502
Modifying a Role • 480
Modifying a Role-Based Access Control Rule •
456
Modifying a User Profile • 465
Modifying a User's Personal Data • 466
Modifying Firewall Control Parameters • 441
Modifying or Deleting a Script • 320, 324
Modifying Role-Based Access Control
Parameters • 453
Modifying SNMPv3 Settings • 468
Monitoring Server Accessibility • 207, 313, 315
Mounting a PX3TS Device • 7
Multi-Command Syntax • 399, 400, 442, 448,
450, 454, 465, 466, 468, 471, 474, 487, 489,
491, 493, 495, 497, 500, 502, 516
N
Naming a Rack Unit • 511
Naming an Asset Strip • 507
Naming the Rack PDU (Port Page for Power
Strips) • 658
Network Configuration • xvii, 367
Network Configuration Commands • 410
Network Diagnostics • 326, 341
Network Interface Settings • xvii, 369
Network Service Settings • 370
Network Troubleshooting • 341, 526
NPS Standard Attribute Illustration • 597
NPS VSA Illustration • 616
Numeric Character Requirement • 452
O
OCPs • 107, 120, 160, 162, 164
Operating the Character LCD Display • 80
Options for Outlet State on Startup • 132, 137,
155
Outlet Configuration Commands • 460
Outlet Information • 81, 371
Outlet Sensor Threshold Information • 378
Outlet Switching • 88, 155, 317
Outlets • 74, 107, 145, 149, 152, 153, 296
Overcurrent Protector Configuration
Commands • 463
Overcurrent Protector Information • 82, 95, 96,
98, 373
Overcurrent Protector Sensor Threshold
Information • 380
Overcurrent Protectors for Outlets • 82, 94, 98
Overriding DHCP-Assigned NTP Servers • 437,
440
Overview of the Cascading Modes • 221, 222
Overview of the LCD Display • 78, 79, 335
P
Package Contents • 4, 5
Password Aging • 449
Password Aging Interval • 449
Index
PDU • 99, 104, 107, 131, 137, 138, 139, 140,
144, 148, 156, 159, 165, 180, 182, 406
PDU Configuration • 136, 371
PDU Configuration Commands • 402
PDView App for Viewing the PX3TS • 645
Performing Manual Transfer • 65, 397
Peripherals • 38, 107, 139, 165, 171, 173, 176,
178, 179, 308
Ping via the CLI • 653
Ping via the Web Interface • 652
Port Forwarding Examples • 102, 222, 225
Port Number Syntax • 221, 223, 224, 225, 651
Possible Root Causes • xviii, 649
Power CIM • 184, 197
Power Control • 663, 665
Power Control Operations • 519
Power Cycling the Outlet(s) • 521
Power Cycling the PX3TS • 99
Power IQ Configuration • 666
Power Quality Indicator Lamps • 62, 68, 69
Power Quality Settings • 124, 130, 366
Power Transfer • 61
Power Transfer Settings • 64, 65, 123, 129
Power-Off Period Options for Individual
Outlets • 155, 159
Preparing the Installation Site • 6
Product Models • 1
Push Out Sensor Readings • 282, 286
PX3TS Control and Configuration • 397
PX3TS Latching Relay Behavior • 132, 137, 403,
404, 405, 406
PX3TS Overview • 2
PX3TS-1000 Series • 74
PX3TS-5000 Series • 74
Q
Querying Available Parameters for a
Command • 363, 364
Querying DNS Servers • 527
Quick Access to a Specific Page • 101, 108
Quitting Configuration Mode • 396, 397, 447
Quitting Diagnostic Mode • 527
R
Rack Unit Configuration • 510
675
Index
Rack Unit Settings of an Asset Strip • 387
Rackmount Safety Guidelines • 7
Rackmount, Inlet and Outlet Connections • 7
RADIUS Configuration Illustration • 248, 597
Raritan Training Website • 648
Rear View • 3
Rebooting the PX3TS Device • 326, 342
Record Snapshots to Webcam Storage • 282,
287
Reliability Data • 392
Reliability Error Log • 392
Remembering User Names and Passwords •
103
Replacing a Fuse on 1U Models • 95
Replacing a Fuse on 2U Models • 96
Request LHX/SHX Maximum Cooling • 282,
288
Reserving IP Addresses in DHCP Servers • xviii, 635, 637
Reserving IP in Linux • xviii, 637
Reserving IP in Windows • xviii, 635
Reset Buttons • 93
Resetting Active Energy Readings • 525
Resetting All Settings to Factory Defaults •
326, 343, 581
Resetting the Button-Type Circuit Breaker •
98
Resetting the PX3TS • 524
Resetting to Factory Defaults • 93, 343, 526,
581
Restarting the PDU • 525
Restricted Service Agreement • 446
Retrieving Energy Usage • 357
Retrieving Previous Commands • 529
Retrieving Software Packages Information •
326, 344
Returning User Group Information • 590
Role Configuration Commands • 477
Role of a DNS Server • 586, 649
Role-Based Access Control • 453
S
Safety Guidelines • ii
Safety Instructions • iii, 6
Sample Environmental-Sensor-Level Event
Rule • 308
676
Sample Event Rules • 265, 306
Sample Inlet-Level Event Rule • 307
Sample Outlet-Level Event Rule • 306
Sample PDU-Level Event Rule • 306
Scheduling an Action • 263, 286, 298, 301
Schroff LHX/SHX • 184, 194
SecureLock™ Outlets and Cords • 633
Security Configuration Commands • 440
Security Settings • 383
Send an SNMP Notification • 231, 282, 293
Send Email • 268, 282, 288, 301, 302
Send Sensor Report • 206, 282, 289, 301
Send Sensor Report Example • 289, 301
Send SMS Message • 282, 291, 302
Send Snapshots via Email • 282, 292
Sending Snapshots or Videos in an Email or
Instant Message • 344, 345, 347
Sensor RJ-45 Port Pinouts • 539
Sensor Threshold Configuration Commands •
489
Sensor Threshold Settings • 125, 141, 145, 150,
157, 161, 163, 169, 170, 179, 356, 638
Sensor/Actuator Location Example • 139, 180,
182
Sensor/Actuator States • 115, 166, 167, 172
Serial Port Configuration Commands • 514
Serial Port Settings • 386
Serial RS-232 • 538
Server Reachability Configuration Commands
• 501
Server Reachability Information • 390
Server Reachability Information for a Specific
Server • 391
Setting an LED Color for a Rack Unit • 512
Setting an LED Mode for a Rack Unit • 512,
513
Setting an Outlet's Cycling Power-Off Period •
462
Setting Data Logging • 207, 310, 312, 407
Setting Data Logging Measurements Per Entry
• 407
Setting Default Measurement Units • 133, 197,
205, 206, 471, 474
Setting EAP Parameters • 423
Setting IPv4 Static Routes • xvii, 413
Setting IPv6 Static Routes • xvii, 417
Setting LAN Interface Parameters • xviii, 419
Setting LED Colors for Connected Tags • 510,
511, 512
Setting LED Colors for Disconnected Tags •
510, 511, 512
Setting Network Service Parameters • 428
Setting Non-Critical Outlets • 147, 151, 152
Setting NTP Parameters • 436, 440
Setting Outlet Power-On Sequence and Delay
• 147, 150
Setting the Alarmed to Normal Delay for
DX-PIR • 486
Setting the Authentication Method • 422
Setting the Automatic Daylight Savings Time •
439
Setting the Baud Rates • 514
Setting the BSSID • 426
Setting the Cascading Mode • 4, 23, 25, 208,
209, 210, 212, 221, 222, 228, 329
Setting the Date and Time • 207, 259, 356
Setting the History Buffer Length • 515
Setting the HTTP Port • 428
Setting the HTTPS Port • 429
Setting the Inrush Guard Delay Time • 405
Setting the IPv4 Address • xvii, 412
Setting the IPv4 Configuration Mode • xvii, 410
Setting the IPv4 Gateway • xvii, 412
Setting the IPv4 Preferred Host Name • xvii,
411
Setting the IPv6 Address • xvii, 416
Setting the IPv6 Configuration Mode • xvii, 414
Setting the IPv6 Gateway • xvii, 416
Setting the IPv6 Preferred Host Name • xvii,
415
Setting the LED Operation Mode • 511
Setting the Outlet Initialization Delay • 406
Setting the Outlet Power-On Sequence • 403
Setting the Outlet Power-On Sequence Delay •
404
Setting the Outlet Relay Behavior • 403
Setting the PDU-Defined Cycling Power-Off
Period • 405, 462
Setting the PDU-Defined Default Outlet State •
404, 461
Setting the Polling Interval • 506
Setting the PSK • 422
Index
Setting the Registry to Permit Write
Operations to the Schema • 591
Setting the SNMP Configuration • 431
Setting the SNMP Read Community • 432
Setting the SNMP Write Community • 432
Setting the SSID • 421
Setting the sysContact Value • 432
Setting the sysLocation Value • 433
Setting the sysName Value • 433
Setting the Time Zone • 356, 437
Setting the X Coordinate • 484
Setting the Y Coordinate • 484
Setting the Z Coordinate • 408, 485
Setting the Z Coordinate Format for
Environmental Sensors • 408, 485, 501
Setting Thresholds for Total Active Energy or
Power • 135, 140
Setting Up an SSL/TLS Certificate • 207, 237,
242
Setting Up External Authentication • 207, 237,
247, 649
Setting Wireless Parameters • 421
Setting Your Preferred Measurement Units •
133, 197, 201, 205, 206
Short Circuit Detection • 72, 74, 537
Showing Information • 364
Showing Network Connections • 527
SHX Request Maximum Cooling • 196
Single Login Limitation • 448
Slave Connection and Disconnection Events • xviii, 651, 652
SNMP Gets and Sets • 354
SNMP Sets and Thresholds • 356
SNMPv2c Notifications • 231, 351
SNMPv3 Notifications • 231, 351, 352
Sorting a List • 109, 114, 146, 160, 166, 187,
202, 204, 216, 302, 331, 333, 337
Special Character Requirement • 452
Specifications • 7, 536
Specifying Non-Critical Outlets • 385, 406
Specifying the Agreement Contents • 447
Specifying the Asset Strip Orientation • 509
Specifying the CC Sensor Type • 483
Specifying the Device Altitude • 408
Specifying the EnergyWise Domain • 505
Specifying the EnergyWise Secret • 506
677
Index
Specifying the Number of Rack Units • 508
Specifying the Primary NTP Server • 436
Specifying the Rack Unit Numbering Mode •
508
Specifying the Rack Unit Numbering Offset •
509
Specifying the Secondary NTP Server • 436
Specifying the SSH Public Key • 431, 472
Standard Attributes • 597
Start or Stop a Lua Script • 283, 295, 320, 322
Static Route Examples • 208, 211, 217, 413,
417
Step A
Add Your PX3TS as a RADIUS Client • 597,
598, 616, 617
Step A. Determine User Accounts and Roles •
584
Step B
Configure Connection Policies and
Standard Attributes • 598, 602
Configure Connection Policies and
Vendor-Specific Attributes • 616, 621
Step B. Configure User Groups on the AD
Server • 585
Step C. Configure LDAP Authentication on the
PX3TS Device • xviii, 586
Step D. Configure Roles on the PX3TS Device •
587
Strong Passwords • 450
Supported Maximum DPX Sensor Distances •
29, 33
Supported Web Browsers • 100
Supported Wireless LAN Configuration • 13,
650
Switch LHX/SHX • 283, 295
Switch Outlets • 283, 296
Switch Peripheral Actuator • 283, 296
Switching Off an Actuator • 523
Switching On an Actuator • 523
Syslog Message • 283, 297
System and USB Requirements • 545
T
Technical Specifications • 4, 6, 71, 95, 96, 536
Testing Indicator Lamps • 73
Testing the Network Connectivity • 528
678
TFTP Requirements • 559
The Ping Tool • 652
The PX3TS MIB • 354
Thresholds and Sensor States • 638
Time Configuration Commands • 435
Time Units • 132, 140, 159, 256, 257
Tracing the Route • 529
Transfer Switch • 64, 65, 69, 71, 94, 112, 114,
121, 127, 128, 130, 145
Transfer Switch and Inlet Status • 70, 72, 114,
122, 127, 134
Transfer Switch Indicator Lamps • 61, 67
Transfer Switch Information • 365, 397
Transfer Timing Statistics • 366
Turning Off the Outlet(s) • 520
Turning On the Outlet(s) • 519
Turning Outlets On/Off and Cycling Power •
660, 663
U
Unblocking a User • 257, 524
Unpacking the Product and Components • 5
Updating the LDAP Schema • 590
Updating the PX3TS Firmware • 326, 334, 531
Updating the Schema Cache • 594
Upgrade Guidelines for Existing
USB-Cascading Chains • 23, 334, 335
Uppercase Character Requirement • 452
USB Wireless LAN Adapters • xvii, 12, 13, 25,
650
USB-Cascaded Device's Position • xvii, 92
User Blocking • 450
User Configuration Commands • 464
User Interfaces Showing Default Units • 206
User Management • 107, 197
Using an Optional DPX3-ENVHUB4 Sensor
Hub • 30, 41
Using an Optional DPX-ENVHUB2 cable • 31
Using an Optional DPX-ENVHUB4 Sensor Hub
• 30
Using Default Thresholds • 486
Using SCP Commands • 531
Using SNMP • 335, 350
Using the CLI Command • 526, 582
Using the Command Line Interface • 229, 358,
582
Using the PX3TS • 60
Using the Reset Button • 581
Using the Web Interface • xvii, 100
V
Vendor-Specific Attributes • 597, 616
Viewing Connected Users • 326, 331, 347
Viewing Firmware Update History • 326, 336
Viewing or Clearing the Local Event Log • 126,
232, 248, 297, 326, 333
Viewing Saved Snapshots and Managing
Storage • 287, 342, 344, 345, 348
W
Ways to Probe Existing User Profiles • 648
Web Interface Overview • 103, 654
Webcam Management • 107, 332, 344
What's New in the PX3TS User Guide • xvii
Windows NTP Server Synchronization Solution
• 260, 261
Wired Network Settings • 208, 209, 222, 236,
586
Wireless LAN Diagnostic Log • 215, 216, 390
Wireless Network Settings • 208, 212, 222
With an Analog Modem • 361
With HyperTerminal • 359, 524
With SSH or Telnet • 360, 653
Writing or Loading a Lua Script • 320, 324
Y
Yellow- or Red-Highlighted Sensors • 142, 145,
150, 159, 160, 166, 170, 172, 178, 195, 640
Z
Z Coordinate Format • 133, 139
Index
679
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project