Page 2 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.
Page 3 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.
Page 5 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 2020 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.
Page 7: Table Of Contents
Contents Safety Guidelines Safety Instructions Applicable Models xviii Chapter 1 Introduction Product Models ............................1 PX3TS Overview ............................1 Front View ............................2 Rear View ............................4 Package Contents ............................6 APIPA and Link-Local Addressing........................6 Before You Begin ............................7 Unpacking the Product and Components ..................
Page 8 Contents Restrictions of Port-Forwarding Connections ................. 34 Power-Sharing Restrictions and Connection ....................36 Making a Power-Sharing Connection ....................37 Power-Sharing Configurations and Restrictions................38 Supported Sensor Configurations for Power Sharing ..............39 Chapter 4 Connecting External Equipment (Optional) Connecting Raritan Environmental Sensor Packages ................. 41 Identifying the Sensor Port ......................
Page 9 Contents Displays for Master and Link Units ......................104 PDU Linking in the CLI ..........................106 PDU Linking CLI Commands ......................107 Chapter 6 Using the PX3TS Power Transfer ............................108 Automatic Transfer ........................109 Automatic Retransfer ........................111 Manual Transfer ..........................112 Transfer Switch Indicator Lamps ......................
Page 10 Contents Quick Access to a Specific Page ..................... 178 Sorting a List ..........................179 Dashboard ..............................180 Dashboard - Transfer Switch ......................182 Dashboard - Inlet 1/2 ........................183 Dashboard - Alerted Sensors ......................185 Dashboard - Inlet History ......................187 Dashboard - Alarms ........................
Page 11 Contents Sensor/Actuator Location Example ....................278 Feature Port ............................. 279 Asset Strip ............................. 281 External Beeper ..........................289 Schroff LHX/SHX ..........................290 Power CIM ............................. 295 User Management ............................ 296 Creating Users ..........................297 Editing or Deleting Users ....................... 301 Creating Roles ..........................
Page 12 Contents Card Readers ..........................513 Chapter 8 Using SNMP Enabling and Configuring SNMP ....................... 515 SNMPv2c Notifications ........................516 SNMPv3 Notifications ........................517 Downloading SNMP MIB .......................... 520 SNMP Gets and Sets ..........................521 The PX3TS MIB ..........................521 Retrieving Energy Usage ....................... 523 A Note about Enabling Thresholds ....................
Page 13 Contents EnergyWise Settings ........................553 Asset Strip Settings ........................553 Rack Unit Settings of an Asset Strip ....................554 Blade Extension Strip Settings ....................... 555 Event Log ............................556 Network Connections Diagnostic Log ................... 557 Server Reachability Information ....................557 Command History .........................
Page 14 Contents Actuator Control Operations ........................702 Switching On an Actuator ......................702 Switching Off an Actuator ......................703 Example - Turning On a Specific Actuator ..................703 Unblocking a User ............................ 703 Resetting the PX3TS ..........................704 Restarting the PDU ........................704 Resetting Active Energy Readings ....................
Page 15 Contents Data Encryption in 'config.txt' ....................... 743 Firmware Upgrade via USB ........................744 Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ....................747 TFTP Requirements ..........................748 DHCP IPv4 Configuration in Windows ...................... 748 DHCP IPv6 Configuration in Windows ...................... 758 DHCP IPv4 Configuration in Linux ......................
Page 16 Contents Setting the Registry to Permit Write Operations to the Schema ............. 786 Creating a New Attribute ......................... 786 Adding Attributes to the Class ........................787 Updating the Schema Cache ........................789 Editing rciusergroup Attributes for User Members .................. 789 Appendix I RADIUS Configuration Illustration Standard Attributes ..........................
Page 17 Contents Browsing through the Online Help ......................865 Appendix K Integration Dominion KX II / III Configuration ......................867 Configuring Rack PDU Targets ....................... 867 Turning Outlets On/Off and Cycling Power ................... 871 Dominion KSX II, SX or SX II Configuration ....................872 Dominion KSX II ..........................
Page 18 Applicable Models This User Guide is applicable to all the following Transfer Switch Generations. • PX3TS Generation • PX3TS with iX7 Generation ™ Any PX3TS Generations can be associated with existing metering families called “Series”, including 200R series, 1000 series and 5000 series. For example, PX3TS-1000, and PX3TS-iX7-1000 series are all inlet metered models with receptacles, but have different controller generations.
Page 19 Applicable Models Product models PX3TS Series PX3TS with iX7 Controller ™ Character LCD Dot-matrix LCD display Front panel display Outlet latching relays Number of USB-A ports 12 Mbps 480 Mbps Maximum USB rate Number of LAN ports Expansion port RS-232 port Male DB9 Connector RJ-45 Connector (CONSOLE/MODEM)
Page 21: Chapter 1 Introduction
™ PX3TS-iX7) unless otherwise specified. 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.
Page 22: Front View
Chapter 1: Introduction Front View When PX3TS or PX3TS-iX7 models are rated over 20A (North America) or 16A (international), they have overcurrent protectors for controlling the current flowing through outlets. Note that the total number of available connection ports is different between PX3TS and PX3TS-iX7 models.
Page 23 Chapter 1: Introduction Transfer switch status indicators, including: ▪ Power quality indicator lamps ▪ Inlet configuration indicator lamps ▪ Active inlet indicator lamps Transfer switch alarm indicators Transfer switch control buttons Overcurrent protectors - one for each bank of outlets (available on some models only) PX3TS-iX7 Models 1U models:...
Page 24: Rear View
Chapter 1: Introduction LCD display and control buttons Transfer switch status indicators, including: ▪ Power quality indicator lamps ▪ Inlet configuration indicator lamps ▪ Active inlet indicator lamps Transfer switch alarm indicators Transfer switch control buttons Fuses Overcurrent protectors - one for each bank of outlets (available on some models only) Rear View Available connection ports are the same between PX3TS and PX3TS-iX7 models.
Page 25 Chapter 1: Introduction Outlets Two connection ports ▪ USB-A port ▪ CONSOLE port PX3TS-iX7 Models Inlets, outlets and fuses for the inlet transfer switch are located on the rear panel. 1U models: 2U models: Two inlets Two fuses for the inlet transfer switch - one per inlet (available on iX7 ™...
Page 26: Package Contents
Chapter 1: Introduction Package Contents • One PX3TS • 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.
Page 27: Before You Begin
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.
Page 28: Checking The Branch Circuit Rating
Chapter 1: Introduction Allow sufficient space around the PX3TS for cabling and outlet connections. 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.
Page 29: Chapter 2 Rackmount, Inlet And Outlet Connections
Chapter 2 Rackmount, Inlet and Outlet Connections In This Chapter Rackmount Safety Guidelines ................9 Mounting a PX3TS Device ..................9 Inlet and Outlet Power Connections ..............12 Rackmount Safety Guidelines In Raritan products which require rack mounting, follow these precautions: ▪...
Page 30 Chapter 2: Rackmount, Inlet and Outlet Connections Adjust slide-rail assemblies to match your rack posts and fasten them to the rack using your own fasteners. Line up the mounting brackets with slide-rails and push this product into rails.
Page 31 Chapter 2: Rackmount, Inlet and Outlet Connections Fasten front mounting ears to the rack using your own fasteners. To mount a PX3TS device which is short: 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.
Page 32: Inlet And Outlet Power Connections
Chapter 2: Rackmount, Inlet and Outlet Connections Secure with the provided end cap screws. On a 2U model, repeat the above steps to install another cable-support bar. 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.
Page 33: Chapter 3 Initial Installation And Configuration
Chapter 3 Initial Installation and Configuration This chapter explains how to install your PX3TS and configure it for network connectivity. In This Chapter Connecting Power and Equipment ..............13 Connecting the PX3TS to Your Network ............. 13 Configuring the PX3TS ..................16 Bulk Configuration Methods ................
Page 34 Chapter 3: Initial Installation and Configuration The "green" Ethernet port labeled "ETH 10/100/1000" supports up to 1000 Mbps so it is highly recommended for network connection. To make a wired connection: Connect a standard network patch cable to either or both Ethernet ports on the PX3TS.
Page 35: Usb Wireless Lan Adapters
Chapter 3: Initial Installation and Configuration ▪ 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. USB Wireless LAN Adapters (on page 15) for a list of supported wireless LAN adapters.
Page 36: Dual Ethernet Connection
Chapter 3: Initial Installation and Configuration Dual Ethernet Connection One PX3TS device has two Ethernet (LAN) ports: • ETH 10/100/1000 (marked in green) supports up to 1000 Mbps. This is "ETH1". • ETH 10/100 (marked in white) supports up to 100 Mbps. This is "ETH2". For more information on the two ports, see .
Page 37: Connecting A Mobile Device To Px3Ts
Chapter 3: Initial Installation and Configuration ▪ For PX3TS, see IPv4 Address (on page 131). ▪ For PX3TS-iX7, see Device Info (on page 155). Launch a web browser to configure the PX3TS. See Login (on page 170). Configuration via a connected mobile device: Download the PDView app to your mobile device.
Page 38 Chapter 3: Initial Installation and Configuration ▪ https://itunes.apple.com/app/raritan-pdview/id780382738 ▪ https://play.google.com/store/apps/details?id=com.raritan.android.pd view Install PDView. Step B: Connect the mobile device to PX3TS Get an appropriate USB cable for your mobile device. ▪ iOS: Use the regular USB cable shipped with your iOS mobile device. ▪...
Page 39 Chapter 3: Initial Installation and Configuration The "Disconnected" message displays first when PDView has not detected the PX3TS yet. A diagram in PDView indicates the appropriate USB port your mobile device should connect according to your mobile operating system. Note: PDView also shows the 'Disconnected' status during the firmware upgrade.
Page 40 Chapter 3: Initial Installation and Configuration b. The PDView shows the "Connected" message when it detects the connected PX3TS. If the factory-default user credentials "admin/raritan" remain unchanged, PDView automatically logs in to the web interface of PX3TS. If they have been changed, the login screen displays instead and you must enter appropriate user credentials for login.
Page 41 Chapter 3: Initial Installation and Configuration Saving User Credentials for PDView's Automatic Login When PDView detects PX3TS for the "first" time, it automatically attempts to log in with the factory-default user credentials -- admin (user name) and raritan (password). If you have modified the factory-default user credentials, PDView's automatic login fails and the login screen displays for you to manually enter user credentials.
Page 42 ▪ Per default, three administrator user credentials are pre-configured for three companies' products: ▪ Raritan ▪ Legrand ▪ ServerTech (Server Technology) Modify existing user credentials or type new ones, and tap Save. ▪ The pre-configured admin credentials can be removed or overwritten...
Page 43: Connecting The Px3Ts To A Computer
Chapter 3: Initial Installation and Configuration Connecting the PX3TS to a Computer The PX3TS can be connected to a computer for configuration via one of the following ports. • Ethernet ports • USB-B port • RS-232 serial port (RJ-45) The diagrams below indicate the port locations of different product models. •...
Page 44 Chapter 3: Initial Installation and Configuration • • PX3TS 1U back panel RS-232 port: PX3TS-iX7 1U back panel RS-232 port: 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.
Page 45 Chapter 3: Initial Installation and Configuration Connect the other end to your computer's RS-232 port (COM). Perform Initial Network Configuration via CLI (on page 851). Serial connection for "RJ-45" RS-232 connector: Connect the RJ-45 end of the RJ45-to-DB9 adapter cable to the RJ-45 port labeled CONSOLE / MODEM on PX3TS.
Page 46: Bulk Configuration Methods
Chapter 3: Initial Installation and Configuration 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. A bulk configuration file downloaded from PX3TS: • Requirement: All PX3TS devices to configure are of the same model and firmware.
Page 47: Cascading Multiple Px3Ts Devices For Sharing Ethernet Connectivity
Chapter 3: Initial Installation and Configuration A USB flash drive: • Requirement: A FAT32- or supperfloppy-formatted USB flash drive containing two special configuration files and one devices list file 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.
Page 48: Cascading All Devices Via Usb
Chapter 3: Initial Installation and Configuration • Do NOT connect cascaded devices other than master to the LAN or WLAN. • (WIFI only) You must use Raritan's USB WIFI wireless LAN adapter instead of other WIFI adapters for wireless network connection. Troubleshooting: When a networking issue occurs, check the cascading connection and/or software settings of all devices in the chain.
Page 49 Chapter 3: Initial Installation and Configuration Number Device role Master device Slave 1 Slave 2 Slave 3 To cascade PX3TS devices via USB: Make sure all Raritan devices are running firmware version 3.3.10 or later. Choose the appropriate one as the master device. ▪...
Page 50 Chapter 3: Initial Installation and Configuration A tip for USB cascading: The "USB-cascading" chain can be a combination of diverse Raritan products that support the USB-cascading feature, including PX3, PXC, Smart Rack Controller, transfer switch, PX2, BCM and EMX.
Page 51: Extended Cascading With Px3Ts Devices
Chapter 3: Initial Installation and Configuration Extended Cascading with PX3TS Devices PX3TS supports cascading via either Ethernet or USB ports. This is because they have "two" Ethernet ports. You can use either Ethernet port on the PX3TS PDU for cascading. You must set the cascading mode before establishing the chain.
Page 52 Chapter 3: Initial Installation and Configuration Number Device role Master device Slave 1 Slave 2 Slave 3...
Page 53 Chapter 3: Initial Installation and Configuration For instructions on USB cascading, see Cascading All Devices via USB (on page 28). Suggestions for extended cascading: • Ethernet cascading is recommended because of the longer distance, lower latency and more reliable connection it supports. •...
Page 54: Restrictions Of Port-Forwarding Connections
Chapter 3: Initial Installation and Configuration Recommendations for cascade loops: You can connect both the first and the last PDU to your network (cascade loop) under the following conditions: The remaining network MUST use R/STP to avoid network loops. Both the first and the last PDUs MUST either attach to the same switch or, if they are attached to two separate switches, you must configure both ports of these switches so that the STP costs are high.
Page 55 Chapter 3: Initial Installation and Configuration • One cascaded device has two upstream devices via Ethernet and USB cables. • One cascaded device has two downstream devices.
Page 56: Power-Sharing Restrictions And Connection
Chapter 3: Initial Installation and Configuration • One device is connected to another device via two cascading cables - USB and Ethernet cables. Power-Sharing Restrictions and Connection Two PX3TS devices can share power supply to their controllers via EXPANSION ports, so that when either PX3TS controller fails to receive DC 12V power from its inlet(s), it continues to receive backup power from another PX3TS device which functions properly and therefore remains to be accessible to users.
Page 57: Making A Power-Sharing Connection
Chapter 3: Initial Installation and Configuration • All internal sensors become "unavailable", including sensors of inlets, outlets, and OCPs. Exception: Only active energy data remains available. • Communications with relay/meter boards are lost. Therefore, firmware upgrade may fail due to this reason. Available data or operations on the PDU that enters the power-sharing mode: •...
Page 58: Power-Sharing Configurations And Restrictions
Chapter 3: Initial Installation and Configuration Power-Sharing Configurations and Restrictions When either PX3TS PDU enters the power-sharing mode, BOTH PDUs involved in the power-sharing connection support "less" external equipment than usual. It is strongly recommended to remove specific equipment from both PX3TS PDUs when making a power-sharing connection.
Page 59: Supported Sensor Configurations For Power Sharing
Chapter 3: Initial Installation and Configuration Supported Sensor Configurations for Power Sharing All information and restrictions described in this section apply to BOTH PDUs involved in the power-sharing configuration, unless otherwise specified. • There are no limitations for connecting Raritan's DPX or DPX2 environmental sensor packages to an iX7 PDU in the power-sharing mode.
Page 60 Chapter 3: Initial Installation and Configuration Other sensor restrictions when door handles are present: First make sure the connection of door handles complies with the above restrictions. The following restrictions apply only to the PDU that has all the door handles connected.
Page 61: Chapter 4 Connecting External Equipment (Optional)
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 Raritan Environmental Sensor Packages ......... 41 Before Connecting Equipment to Feature Port ..........62 Connecting Asset Management Strips ..............62 Connecting a Logitech Webcam .................
Page 62: Identifying The Sensor Port
Chapter 4: Connecting External Equipment (Optional) Identifying the Sensor Port Warning: If you purchase Raritan's environmental sensor packages, make sure you connect them to the correct port on the PX3TS, or damages may be caused to PX3TS and/or connected sensor packages. How to identify the SENSOR port: •...
Page 63: Dx2 Sensor Packages
Chapter 4: Connecting External Equipment (Optional) DX2 Sensor Packages You can cascade up to 12 DX2 sensor packages. When cascading DX2, 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.
Page 64 Chapter 4: Connecting External Equipment (Optional) Exception: You CANNOT cascade DX2-DH2C2 packages. A PX3TS supports only one DX2-DH2C2. Connect the first DX2 sensor package to the PX3TS by plugging its cable's connector into the RJ-45 SENSOR port of the PX3TS. If needed, connect a DPX2 sensor package to the end of the DX2 chain.
Page 65: Dx Sensor Packages
Chapter 4: Connecting External Equipment (Optional) DX Sensor Packages Most DX sensor packages contain terminals for connecting detectors or actuators. For information on connecting actuators or detectors to DX terminals, refer to the Environmental Sensors and Actuators Guide (or Online Help) on Raritan website's Support page (http://www.raritan.com/support/).
Page 66: Dpx3 Sensor Packages
Chapter 4: Connecting External Equipment (Optional) Exception: You CANNOT cascade DX-PD2C5 sensor packages. One PX3TS supports only one DX-PD2C5. Connect the first DX sensor package to the PX3TS by plugging its cable's connector into the RJ-45 SENSOR port of the PX3TS. If needed, connect a DPX2 sensor package to the end of the DX chain.
Page 67 Chapter 4: Connecting External Equipment (Optional) Plug one end of the cable into the remaining RJ-45 port on the prior DPX3. b. Plug the other end into either RJ-45 port on an additional DPX3. Repeat the same steps to cascade more DPX3 sensor packages. Connect the first DPX3 sensor package to the PX3TS by plugging its cable's connector into the RJ-45 SENSOR port of the PX3TS.
Page 68: Dpx2 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 and Actuators Guide (or Online Help) on Raritan website's Support...
Page 69 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.
Page 70 Chapter 4: Connecting External Equipment (Optional) OR you can directly connect the DPX2 sensor package to a DX sensor chain without using any RJ-12 to RJ-45 adapter. See Connecting a DPX2 Sensor Package to DX2, DX or DPX3 (on page 50). Connecting a DPX2 Sensor Package to DX2, DX or DPX3 You can connect one DPX2 sensor package to the "end"...
Page 71: Dpx Sensor Packages
Chapter 4: Connecting External Equipment (Optional) DPX Sensor Packages Most DPX sensor packages come with a factory-installed sensor cable, whose sensor connector is RJ-12. For the cabling length restrictions, see Supported Maximum DPX Sensor Distances (on page 55). Warning: For proper operation, wait for 15-30 seconds between each connection operation or each disconnection operation of environmental sensor packages.
Page 72 Chapter 4: Connecting External Equipment (Optional) 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 Raritan differential air pressure sensors One DPX sensor package (optional) RJ-12 to RJ-45 adapter Using an Optional DPX-ENVHUB4 Sensor Hub...
Page 73 Chapter 4: Connecting External Equipment (Optional) Connect this adapter's RJ-45 connector to the PDU's RJ-45 SENSOR port. Connect DPX sensor packages to any of the four OUT ports on the hub. This diagram illustrates a configuration with a sensor hub connected. The PX3TS device RJ-12 to RJ-45 adapter Raritan-provided phone cable...
Page 74 Chapter 4: Connecting External Equipment (Optional) The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports. Repeat the above steps if there are additional SENSOR ports on your PX3TS.
Page 75 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.
Page 76: Using An Optional Dpx3-Envhub4 Sensor Hub
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: •...
Page 77: Mixing Diverse Sensor Types
Chapter 4: Connecting External Equipment (Optional) DPX3-ENVHUB4 sensor hub Any Raritan sensor packages Mixing Diverse Sensor Types You can mix diverse sensor packages on one PX3TS according to the following sensor combination principles. In some scenarios, the DPX3-ENVHUB4 sensor hub is required. When mixing different sensor types, remember that the PX3TS only supports a maximum of 32 sensors/actuators.
Page 78 Chapter 4: Connecting External Equipment (Optional) Diverse combinations via the DPX3-ENVHUB4 sensor hub: • You must use the DPX3-ENVHUB4 sensor hub instead of the old DPX-ENVHUB4 sensor hub. Each port on the hub supports any of the following: ▪ One individual DX2 sensor package ▪...
Page 79 Chapter 4: Connecting External Equipment (Optional) • An RJ-12 to RJ-45 adapter is recommended to connect a DPX or DPX2 sensor package to DPX3-ENVHUB4. • In the following diagrams, the sensor package in "green" can be replaced by a DPX2 sensor package. The sensor package in "blue" can be one DPX2, DPX3, DX or DX2 sensor package.
Page 80 Chapter 4: Connecting External Equipment (Optional)
Page 81 Chapter 4: Connecting External Equipment (Optional) Mix DX2, DX and DPX3 in a sensor chain: Any DX or DX2 sensor package in a chain can be replaced by a DPX3 sensor package, or vice versa. The total number of sensor packages in this chain cannot exceed 12.
Page 82: Before Connecting Equipment To Feature Port
Chapter 4: Connecting External Equipment (Optional) You can add a DPX2 sensor package to the end of such a sensor-mixing chain if needed. See Connecting a DPX2 Sensor Package to DX2, DX or DPX3 (on page 50). Before Connecting Equipment to Feature Port PX3TS models have a cap plugged into the FEATURE port when shipping out of the factory.
Page 83: Combining Regular Asset Strips
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.
Page 84 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. Connect another 8U slave strip to the one being attached to the master strip in the same manner as Step 1.
Page 85: Introduction To Asset Tags
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.
Page 86 Chapter 4: Connecting External Equipment (Optional) 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.
Page 87: Connecting Blade Extension Strips
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.
Page 88 Chapter 4: Connecting External Equipment (Optional) Mylar section with the adhesive tape Tag ports 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: Connect the tag connector cable to the blade extension strip.
Page 89: Connecting Composite Asset Strips (Ams-Mx-Z)
Chapter 4: Connecting External Equipment (Optional) b. Plug the tag connector of the asset tag into a tag port on the blade extension strip. Repeat the above step until all blade servers in the chassis are connected to the blade extension strip via asset tags. Plug the tag connector of the blade extension strip into the closest tag port of the regular or composite asset strip on the rack.
Page 90 Chapter 4: Connecting External Equipment (Optional) The composite asset strip is especially useful for tracking large devices such as SAN boxes in the cabinet. The following diagram illustrates AMS-M3-Z. Two RJ-45 connectors Tag ports Important: DO NOT hot swap or hot plug any AMS-Mx-Z in a composite asset strip chain after connecting the chain to the PX3TS device.
Page 91 Chapter 4: Connecting External Equipment (Optional) Affix an asset tag to the IT device. Then connect this asset tag to the composite asset strip by plugging the tag connector into the tag port on the composite asset strip. For details, see Connecting Regular Asset Strips to PX3TS (on page 65).
Page 92: Connecting A Logitech Webcam
Chapter 4: Connecting External Equipment (Optional) Raritan devices Maximum strips per chain PX3 PDUs, PX3TS transfer switches PMC (BCM2 series) Note: In case you hot swap or hot plug any AMS-Mx-Z in a chain, causing the FEATURE port of the PX3TS to malfunction, you can power cycle or reset the PX3TS to restore the FEATURE port.
Page 93: Connecting A Gsm Modem
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 • EHS6T Available Actions (on page 394) for more information on SMS messages. Note: PX3TS cannot receive SMS messages.
Page 94: Connecting An External Beeper
Chapter 4: Connecting External Equipment (Optional) ▪ A third party RJ-45 to "DB9 male" adapter/cable is required for this connection. See RJ45-to-DB9 Cable Requirements for Modem Connections (on page 830). You need to enable the modem dial-in support to take advantage of this feature, see Configuring the Serial Port (on page 455).
Page 95: Chapter 5 Pdu Linking
Chapter 5 PDU Linking The PDU Linking feature allows the linking configuration of a single master PDU unit to multiple link units for faster and more efficient power management. Only one master unit is connected to the network in PDU Linking, which allows a cost-efficient PDU operation and networking infrastructure.
Page 96: Faqs
Chapter 5: PDU Linking FAQs What’s the difference between a "master unit" and a "link unit"? Master and link units are the same model PDUs that are equal to each other, and each has its own IP address. You designate a PDU as the master unit by logging into the unit and then adding a link unit.
Page 97 Chapter 5: PDU Linking Note: Re-linking uses the same Link Unit ID and hostname, but you will need to reauthenticate with your login credentials. What user privileges are required for managing the PDU Linking configuration? Administrative privileges are required for both the master unit and link unit. To add a link, your administrative login account is required, but after that you only log in to the master to manage the chain, as all link units in the chain are visible in the user interface from the master unit view.
Page 98: Pdu Linking In The Web Gui
Chapter 5: PDU Linking How are firmware updates handled? Uploaded firmware images in the GUI are automatically distributed to all link units at the same time. Starting a firmware update requires the same image to be uploaded to all units. Does PDU Linking support mass deployment of PDUs? Yes, mass deployment has been extended to support a setup for the PDU Linking feature (multi-IP or single-IP) via the Raritan Mass Deployment Utility,...
Page 99: Designating The Master Unit
Chapter 5: PDU Linking Designating the Master Unit Log in to the PDU you want to designate as the master unit. When you add the first link unit, a chain is established between the master and the new link, and the master becomes ID "1".
Page 100: Adding A Link Unit
Chapter 5: PDU Linking Adding a Link Unit A link unit (up to seven units) can be added to a single master unit. On the PDU page, the master unit is displayed as highlighted in the following screen example in red. Note the following section "Link PDUs", designed for the PDU Linking feature, where multiple PDUs added to the chain are displayed as the link units.
Page 101 Chapter 5: PDU Linking To add a link unit: Log in to the master PDU as shown displayed above in the PDU page. Click Add Link PDU. The following add box displays: The Link ID is populated as the next available ID number (2-8), assigned sequentially as each link unit is added to the chain to identify the link unit in the user interfaces.
Page 102 Chapter 5: PDU Linking The new link unit is added on the PDU page with the master unit, in a list in the Link PDUs section. All link units added to the chain in this way are now managed by the single master unit. The PDU page displays the following information about the link unit: •...
Page 103: Master Units Manage Link Units
Chapter 5: PDU Linking About the Link ID The PDU ID "1" is automated and reserved internally for the master unit. The master unit’s PDU ID "1" cannot be edited. The Link ID "2-8" is available for you to select as the ID for each of the link units you add to chain.
Page 104: Releasing A Link Unit
Chapter 5: PDU Linking Releasing a Link Unit Releasing a link unit means the unit is separated from the chain and the unit then becomes standalone. The master unit no longer has access to the released link unit. Note: If a release action is attempted on a link unit when the unit is an unreachable state, a warning message displays, and the master will not recognize the link unit.
Page 105: Switching To A Different Pdu
Chapter 5: PDU Linking To release a link unit: From the PDU page, in the Link PDUs section, click a link unit to select it. Click Release Link PDU. A confirmation prompts to cancel or release: If released, the link unit is removed from the PDU page. Switching to a Different PDU Switching PDUs is a control function noted by the Switch control in the in the upper left corner of the PDU, Outlet, Outlet Groups, OCPs, and Feature Ports...
Page 106: Re-Linking A Link Unit
Chapter 5: PDU Linking To return to the PDU page for the master, select the master PDU. Master number "1" appears in parentheses. Note: The Switch control is only available when there is at least one link unit in the chain; otherwise, the page defaults to displaying only the data of the master PDU.
Page 107 Chapter 5: PDU Linking Although re-linking uses the same Link Unit ID and hostname of the unreachable unit, you will need to reauthenticate with your login credentials shown below. Click the Re-link button. The status of the link unit changes to "OK".
Page 108: Viewing Link Unit Information
Chapter 5: PDU Linking Viewing Link Unit Information When a link unit is added to the chain, the master unit view (through the GUI) allows full access to the operational data of the link unit. For example, using the navigation tabs of the GUI, link unit data is displayed in several pages: the Dashboard, PDUs, Inlets, Outlets, Outlet Groups, Peripherals, and Feature Ports.
Page 109 Chapter 5: PDU Linking...
Page 110 Chapter 5: PDU Linking PDU Page The PDU page displays the details and settings for the selected unit (master or link). The Link PDUs section is only shown when the master unit is selected.
Page 111 Chapter 5: PDU Linking Inlets Page On the Inlets page, the master unit and link units are displayed together on the same page. In this example, data for the single inlet of the master "My PDU (1)" Inlet I1, and the inlet of the link unit "My PDU (2)" Inlet I1, are shown together on the Inlets page.
Page 112 Chapter 5: PDU Linking Outlets Page The Outlets page defaults to display only the outlets of the master unit, in this example 30 outlets.
Page 113 Chapter 5: PDU Linking Viewing Outlets for Link Units On the Outlets page, you can switch from the master to the link. From the Outlets page drop-down, select the link unit "My PDU (2)". Note: To view outlets for a specific link unit, the link unit must be selected by name.
Page 114 Chapter 5: PDU Linking You can switch back to the master unit by selecting "My PDU (1)". Note: The Switch control is only available when there is at least one link unit in the chain; otherwise, the page defaults to displaying only the outlets of the master.
Page 115 Chapter 5: PDU Linking From the Outlets page (either master or link), select an outlet in the list to view operational details for the specific outlet and to configure outlet settings.
Page 116: Outlet Groups
Chapter 5: PDU Linking Outlet Groups An outlet group is a named collection of selected outlets. When user-defined, an outlet group can contain outlets from different PDUs, including both master and link units. Outlet groups support fast and efficient outlet control actions (On, Off, Power Cycle) across multiple PDUs, and with PDU Linking, member outlets for the master and its link units can be collected in the same outlet group.
Page 117 Chapter 5: PDU Linking...
Page 118 Chapter 5: PDU Linking Viewing Outlet Group Details Click an outlet group name in the list to display operations details for the outlet group. From this page, you can issue the outlet control actions On, Off, and Cycle (power cycling to restore the outlet) for all member outlets in the outlet group.
Page 119 Chapter 5: PDU Linking To add an outlet group: On the Outlet Groups page, click . The New Outlet Group page displays, defaulting to the outlets in the master unit. Type a name for the new outlet group. Select individual member outlets for the master as shown in the default page, or to select all outlets for the master, select My PDU (1).
Page 120 Chapter 5: PDU Linking Controlling Outlets in Groups From the Outlet Groups page, select an outlet group by name. Click the desired control: On, Off, or Cycle. This example shows three outlets in status On. When Off is clicked, a prompt appears to confirm applying the action to all outlets in the group.
Page 121: Pairwise Outlet Groups
Chapter 5: PDU Linking Pairwise Outlet Groups The PDU Linking feature offers the "pairwise" functionality for outlet grouping. Pairwise lets you create auto-named pairs of outlet groups than span multiple PDUs (master and link units) using the same outlet label. Pairwise simplifies outlet switching up or down a server by automatically creating multiple outlet groups, each containing one pair of outlets between PDUs that can be controlled as a pair-related outlet group.
Page 122 Chapter 5: PDU Linking Confirm the pairwise creation. Pairwise outlet groups are created and named automatically for all outlets on the master and link unit, such as "Outlet pair 1", "Outlet pair 2", "Outlet pair 3", etc.
Page 123: Ocps Page
Chapter 5: PDU Linking OCPs Page Overcurrent protectors from both master and link PDUs are displayed together on the same OCPs page. If sensors are present on the units, sensor data for both master and link units will also appear on the page. Peripherals Page The Peripherals Page shows peripheral devices connected to the master or link unit.
Page 124: Feature Ports Page
Chapter 5: PDU Linking Feature Ports Page The Feature Ports Page can display device Asset Strip information and the Switch PDU control is available for the data from both the master and link units. Displays for Master and Link Units Each unit in a PDU Linking chain displays its own PDU data (inlets, outlets, sensors, alerts, etc.) Master unit:...
Page 125 Chapter 5: PDU Linking PDU information shows a list of link units with host name/IP address, model, device name, serial number, firmware version, and communication status. Link units: No display of alarms (no event engine on link units) PDU information shows the master IP address...
Page 126: Pdu Linking In The Cli
Chapter 5: PDU Linking PDU Linking in the CLI For each PDU in a chain, you can list the PDUs, switch a PDU, add a new link PDU, and release a link PDU. You can then use all regular PDU-related commands as usual to access and control individual units, as with any standalone PDU.
Page 127: Pdu Linking Cli Commands
Chapter 5: PDU Linking PDU Linking CLI Commands PDU List Displays the following information for each unit: • Link ID • Communication status (for link unit only) • Device name • Model name • Serial number • Firmware version # pdu list Switch PDU Switch between the master and link units.
Page 128: Chapter 6 Using The Px3Ts
Chapter 6 Using the PX3TS In This Chapter Power Transfer ....................108 Transfer Switch Indicator Lamps ..............114 Alarm Indicator Lamps ..................118 Control Push Buttons ..................119 Testing Indicator Lamps ..................120 Short Circuit Detection ..................120 Outlets ......................120 Connection Ports ....................
Page 129: Automatic Transfer
Chapter 6: Using the PX3TS 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.
Page 130 Chapter 6: Using the PX3TS Automatic Transfer Scenarios The PX3TS determines whether an automatic power transfer from the preferred to the alternate inlet can be performed based on the status or fault occurred on both inlets. The following tables indicate when an "automatic" transfer is allowed to occur. •...
Page 131: Automatic Retransfer
Chapter 6: Using the PX3TS ALTERNATE INLET STATES PREFERRED INLET STATES Switch open fault Switch short fault MOV fault Fuse alarm 12V SMPS fault Power Critical (red lamp) Power Warning (orange lamp) Switch Open fault MOV surge protector fault Fuse alarm 12V SMPS 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.
Page 132: Manual Transfer
Chapter 6: Using the PX3TS • 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 118). Tip: Per default the automatic retransfer can be performed only when both inlets are in phase.
Page 133 Chapter 6: 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.
Page 134: Transfer Switch Indicator Lamps
Chapter 6: 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.
Page 135 Chapter 6: Using the PX3TS These lamps are divided into 3 sections to indicate the inlet power status or configuration. Section Lamp type Function Power Quality Inlet power quality is shown using a tricolor LED. For details, see Power Quality Indicator Lamps page 116).
Page 136: Power Quality Indicator Lamps
Chapter 6: 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.
Page 137: Inlet Configuration Indicator Lamps
Chapter 6: 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"...
Page 138: Alarm Indicator Lamps
Chapter 6: 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.
Page 139: Control Push Buttons
Chapter 6: Using the PX3TS Indicator lamps Meaning when the lamp is on Overload Power to load is turned off due to a short circuit. Short Circuit Detection (on page 120). Control Push Buttons The PX3TS provides three buttons on the front panel to perform manual transfer or verify the transfer switch indicator lamps.
Page 140: Testing Indicator Lamps
Chapter 6: Using the PX3TS Testing Indicator Lamps Press the Lamp Test control button and visually verify that all transfer switch indicator lamps turn on. See Control Push Buttons (on page 119). 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.
Page 141: Connection Ports
Chapter 6: Using the PX3TS LED state Outlet status What it means ON and LIVE LIVE power. The outlet is on and power is available. The current flowing through the outlet is greater than Red flashing ON and LIVE the upper warning (non-critical) threshold. The outlet is turned off and power is available when the Green OFF and LIVE...
Page 142: Px3Ts Connection Ports
Chapter 6: Using the PX3TS PX3TS Connection Ports The PX3TS generation has 8 connection ports on the front and back panels respectively. Front panel ports: • 1 Console/Modem (DB9) • 1 Sensor (yellow) • 1 USB-B • 1 USB-A • 1 Ethernet (green) •...
Page 143: Connection Port Functions
Chapter 6: Using the PX3TS • 1 Feature (red) • 1 Expansion (gray) Back panel ports: • 1 USB-A • 1 Console Connection Port Functions 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. The table below explains the function of each port.
Page 144 Chapter 6: Using the PX3TS Port Used for... USB-A This is a "host" port, which is powered, per USB 2.0 specifications. • Connecting to an iOS mobile device for viewing or configuring the PX3TS. See Connecting a Mobile Device to PX3TS (on page 17).
Page 145: Front Lcd Display
Chapter 6: Using the PX3TS Port Used for USB-A, Same functions as above. USB-B, FEATURE, SENSOR CONSOLE/ Same function as the one on PX3TS models. See above. MODEM Note that the CONSOLE/MODEM port on the iX7 device is an RJ-45 ™...
Page 146: Px3Ts Character Lcd Display
Chapter 6: Using the PX3TS PX3TS Character LCD Display A PX3TS model comes a character LCD display. 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,...
Page 147 Chapter 6: Using the PX3TS Section Information shown 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.
Page 148 Chapter 6: Using the PX3TS 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.
Page 149 Chapter 6: Using the PX3TS 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.
Page 150 Chapter 6: Using the PX3TS 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 except to display an alarm when the fuse is blown.
Page 151 Chapter 6: Using the PX3TS ▪ 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.
Page 152 Chapter 6: Using the PX3TS To retrieve the "IPv4" address on PX3TS: Press the MODE button to enter the Device mode, indicated by an alphabet "d" at the top left of the display. The LCD display cycles between the four octets of the IPv4 address, indicated by "i4"...
Page 153 Chapter 6: Using the PX3TS 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.
Page 154 Chapter 6: Using the PX3TS ▪ When showing a numeric sensor's reading, the appropriate measurement unit is displayed to the right of the reading. Measurement Sensor types units A relative humidity sensor A temperature sensor An air flow sensor An air pressure sensor NO measurement For an "absolute"...
Page 155 Chapter 6: Using the PX3TS 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. ▪...
Page 156 Chapter 6: Using the PX3TS 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. To turn on the outlet, press the Up button.
Page 157 Chapter 6: Using the PX3TS 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.
Page 158 Chapter 6: Using the PX3TS 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.
Page 159: Px3Ts-Ix7 Dot-Matrix Lcd Display
Chapter 6: Using the PX3TS Number Device position Number Device position Master device Slave 8 Slave 1 Slave 9 Slave 2 Slave 10 Slave 3 Slave 11 Slave 4 Slave 12 Slave 5 Slave 13 Slave 6 Slave 14 Slave 7 Slave 15 PX3TS-iX7 Dot-Matrix LCD Display A PX3TS-iX7 model comes with a dot-matrix LCD display.
Page 160 Chapter 6: Using the PX3TS Automatic and Manual Modes After powering on or resetting the PX3TS, the front panel LCD display first shows some dots, then Raritan logo and finally enters the automatic mode. Automatic mode without alerts available: In this mode, the LCD display cycles through the transfer switch/inlet information as long as there are no alerts.
Page 161 Chapter 6: Using the PX3TS Control Buttons Use the control buttons to navigate to the menu in the manual mode. Button Function Down Back -- OR -- Switch between automatic and manual modes...
Page 162 Chapter 6: Using the PX3TS Operating the Dot-Matrix LCD Display Enter manual mode when you want to operate the dot-matrix LCD display. You can use the dot-matrix LCD display to: • Show information of the PX3TS, built-in components, or connected peripheral devices •...
Page 163 Chapter 6: Using the PX3TS Main Menu The Main Menu contains 6 to 8 menu commands, depending on the model. Tip: The top-right number in the corner of the display indicates the total number of menu commands. For example, there are 7 menu commands in total in the diagram below.
Page 164 Chapter 6: Using the PX3TS Menu command Function Indicates all alerted sensors, if any. See Alerts (on page 145). Alerts Shows the internal beeper's state, and, if it is on, the reason for turning on. Total active power and total active energy are also shown. (on page 145).
Page 165 Chapter 6: Using the PX3TS Alerts The "Alerts" menu command shows a list of the following alerted sensors, including both internal and external sensors. • Any numeric sensor that enters the warning or critical range if the thresholds have been enabled •...
Page 166 Chapter 6: Using the PX3TS If your PX3TS is a PX3TS-5000 model, it supports the active energy pulse output. Press to enter the Energy Pulse page. By default the energy pulsing is turned off. DO NOT enable this feature unless you have to use it. Note: This feature, once enabled, blink all outlet LEDs proportional to the energy consumption.
Page 167 Chapter 6: Using the PX3TS The first page shows the transfer switch status, including the operation status, current flow (A), active power (W), apparent power (VA) and so on. To go to other page(s), press ▪ Inlets page: This page indicates the active and preferred inlet, each inlet's and each fuse's status.
Page 168 Chapter 6: Using the PX3TS ▪ Transfer Log page: This page is available only after at least a power transfer event has occurred. To return to the Main Menu, press OCPs If your model has more overcurrent protectors (OCPs) than the LCD display can show at a time, a page number appears in the top-right corner of the display.
Page 169 Chapter 6: Using the PX3TS Showing an Outlet's Information Multiple outlet information can be displayed on the LCD display. Control buttons that can be used and the system time are shown at the bottom of the LCD display. To show an outlet's information: Press to select "Outlets"...
Page 170 Chapter 6: Using the PX3TS Power Control This section applies to outlet-switching capable models only. That is, PX3TS-5000 series. The front panel outlet control must be enabled for performing this power control function. The default is to disable this function. See Front Panel Settings (on page 454).
Page 171 Chapter 6: Using the PX3TS ▪ Cycle: Power cycle the outlet. The outlet is turned off and then on. A confirmation message appears. Press to select Yes or No, and then press ▪ Yes: Confirm the operation. ▪ No: Abort the operation. Verify that the selected outlet is switched on or off, depending on the option you selected in the above step.
Page 172 Chapter 6: Using the PX3TS The top and bottom bars also turn yellow or red. See Operating the Dot-Matrix LCD Display (on page 142). Number Description Sensor or actuator names. Sensor or actuator states as listed below. For further information, see Sensor/Actuator States (on page 267).
Page 173 Chapter 6: Using the PX3TS To view an environmental sensor or actuator's detailed information, press to select that sensor or actuator, and press Number Description The ID number assigned to this sensor or actuator. ▪ A sensor shows "Peripheral Sensor x" (x is the ID number) ▪...
Page 174 Chapter 6: Using the PX3TS To switch on or off an actuator: Follow the above steps 1 to 3 to select an actuator. Press to turn on or off the actuator. A confirmation message similar to the following is shown. Press to select Yes or No, and then press Verify that the actuator status shown on the LCD display has been...
Page 175 Chapter 6: Using the PX3TS ▪ The number of tags includes both the tags attached to the asset strip and those attached to the blade extension strip, if any. Press to show this asset strip's details, including: ▪ State - strip status. ▪...
Page 176 Chapter 6: Using the PX3TS Device information like the device name, model name, firmware version, and so on is displayed. Number Description Device name. Firmware version, model name and serial number. Device ratings, including rated voltage, frequency, current and power. Press to show the Network Common page.
Page 177 Chapter 6: Using the PX3TS Press to show the Network Cascading page. Number Description Cascading status, which can be one of the following: ▪ No Cascading: This device's cascading mode is set to None. See Setting the Cascading Mode (on page 328). ▪...
Page 178 Chapter 6: Using the PX3TS A PX3TS has two Ethernet pages -- ETH1 and ETH2. ▪ For PX3TS-iX7, there are two Ethernet pages -- ETH1 and ETH2. Number Description Ethernet interface information, including: ▪ MAC address. ▪ Speed. ▪ Full or half duplex. IPv4/IPv6 network information, including: ▪...
Page 179 Chapter 6: Using the PX3TS Press to show the WIRELESS page. Number Description If NO supported WLAN adapter is plugged or detected, the message "No Adapter Detected" is shown. If a supported WLAN adapter is detected and configured properly, wireless network information is shown instead, including: ▪...
Page 180 Chapter 6: Using the PX3TS Alerts Notice in a Yellow or Red Screen In the automatic mode, if an alert occurs, the LCD display automatically shows a yellow or red screen which indicates the total number of alerted sensors and information of the latest transitions.
Page 181 Chapter 6: Using the PX3TS When there is any alarm present: The LCD display looks similar to the above diagram except that it shows the alarm(s) and the available command in the bottom-right corner is 'Actions' instead of 'Alert list'. Available operations: •...
Page 182 Chapter 6: Using the PX3TS ▪ Show alert list: This option lists all of alerted sensors and alarms. You still can choose to acknowledge alarms after viewing the list. Alerts (on page 145). ▪ Acknowledge all alarms: This option immediately acknowledges all existing alarms, without showing the list of alarms.
Page 183: Reset Buttons
Chapter 6: Using the PX3TS 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. Pressing this reset button restarts the PX3TS software without any loss of power to outlets.
Page 184: Fuses For The Inlet Transfer Switch
Chapter 6: Using the PX3TS 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. If any fuse blows or malfunctions, the front panel indicates this situation by turning on the 'Fuse' indicator lamp.
Page 185 Chapter 6: Using the PX3TS Turn the holder counterclockwise to loosen it. b. Remove the holder. Separate the fuse from the holder. Insert a new fuse into the holder. Make sure the new fuse is identical to the original one. Install back the fuse holder to the PX3TS and turn it clockwise until it is tightened properly.
Page 186: Replacing A Fuse On 2U Models
Chapter 6: Using the PX3TS 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 Technical Specifications (on page 721) for correct fuse types. Replacing a "blown" fuse can be performed while both inlets remain connected to power.
Page 187: Overcurrent Protectors For Outlets
Chapter 6: Using the PX3TS 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. Manual Transfer (on page 112). 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.
Page 188: Beeper
Chapter 6: Using the PX3TS 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.
Page 189: Chapter 7 Using The Web Interface
Chapter 7 Using the Web Interface This chapter explains how to use the web interface to administer the PX3TS. In This Chapter Supported Web Browsers ................. 169 Login, Logout and Password Change ..............169 Web Interface Overview ................... 174 Dashboard ......................180 Transfer Switch ....................
Page 190: Login
Chapter 7: Using the Web Interface Login You must enable JavaScript in the web browser for proper operation. To log in to the web interface: Open a browser and type the IP address of your PX3TS. ▪ If the link-local addressing has been enabled, you can type pdu.local instead of an IP address.
Page 191 Chapter 7: Using the Web Interface Depending on your hardware configuration, your web interface shown onscreen may look slightly different from the image below. Note: The address to access a slave device in the Port Forwarding mode via non-standard ports is a combination of a protocol (http:// or https://), an IP address and a port number.
Page 192: Changing Your Password
Chapter 7: Using the Web Interface Changing Your Password You need appropriate permissions to change your password. Refer to the following for details. To change other users' passwords, Administrator Privileges are required instead. See Editing or Deleting Users (on page 301). 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...
Page 193: Remembering User Names And Passwords
Chapter 7: Using the Web Interface ▪ A password comprises 4 to 64 characters. Remembering User Names and Passwords PX3TS supports the password manager of common web browsers, including: • Microsoft Internet Explorer ® • Mozilla Firefox ® • Google Chrome ®...
Page 194: Web Interface Overview
Chapter 7: Using the Web Interface Web Interface Overview The web interface consists of four areas as shown below. Operation: Click any menu or submenu item in the area of That item's data/setup page is then opened in the area of Now you can view or configure settings on the opened page.
Page 195 Chapter 7: Using the Web Interface Number Web interface element Menu (on page 176) Data/setup page of the selected menu item. ▪ Left side: - PX3TS device name. Note: To customize the device name, see (on page 206). ▪ Right side: - Displayed language, which is English (EN) by default.
Page 196: Menu
Chapter 7: Using the Web Interface Menu Depending on your model and hardware configuration, your PX3TS may show all or some menu items shown below. Menu Information shown Dashboard Summary of the PX3TS status, including a list of alerted sensors and alarms, if any. Dashboard (on page 180).
Page 197 Chapter 7: Using the Web Interface Menu Information shown OCPs The OCPs menu item displays only when there are overcurrent protectors implemented on your model. OCP status and settings, such as OCP thresholds. OCPs (on page 249). Peripherals Status and settings of Raritan environmental sensor packages, if connected. Peripherals (on page 258).
Page 198: Quick Access To A Specific Page
Chapter 7: Using the Web Interface Menu Information shown Maintenance Device information and maintenance commands, such as firmware upgrade, device backup and reset. Maintenance (on page 464). If a menu item contains the submenu, the submenu is shown after clicking that item.
Page 199: Sorting A List
Chapter 7: Using the Web Interface Page Peripherals https://192.168.84.118/#/peripherals Event Log https://192.168.84.118/#/maintenance/eventLog/0 Sorting a List If any list displays an arrow ( ) 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.
Page 200: Dashboard
Chapter 7: Using the Web Interface Dashboard The Dashboard page contains five to six sections, based on the model you purchased.
Page 201 Chapter 7: Using the Web Interface Number Section Information shown Status of the inlet transfer switch. Transfer Switch Dashboard - Transfer Switch (on page 182). Overview of both inlets' power data. Inlet 1/2 Dashboard - Inlet 1/2 (on page 183). ▪...
Page 202: Dashboard - Transfer Switch
Chapter 7: 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 (on page 193). Generic power data of the transfer switch: Available data includes: •...
Page 203: Dashboard - Inlet 1/2
Chapter 7: 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 title 'Inlet 1' or 'Inlet 2' to go to each inlet's setup page.
Page 204 Chapter 7: Using the Web Interface Preferred and active inlet: The page indicates the preferred inlet and the active inlet using two icons. Icon Description This represents the preferred inlet. This represents the active inlet. is not shown on any inlet, neither inlet is powering the outlets, which is the "off"...
Page 205: Dashboard - Alerted Sensors
Chapter 7: Using the Web Interface 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.
Page 206 Chapter 7: 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 Numeric sensors: ▪ above upper warning ▪ below lower warning Numeric sensors: ▪...
Page 207: Dashboard - Inlet History
Chapter 7: Using the Web Interface Dashboard - Inlet History • The Inlet History graph displays the history of the sensor values. Select a different data type by clicking the selector below the diagram. •...
Page 208 Chapter 7: Using the Web Interface To show the charts of both inlets or the other inlet: The default is to show the power chart of Inlet 1. You can have it show the other inlet's or both inlets' data by selecting the checkbox(es) of the desired inlet(s).
Page 209 Chapter 7: Using the Web Interface ▪ To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. ▪ When both inlets are shown in the chart, simply hover your mouse over either inlet's data line.
Page 210: Dashboard - Alarms
Chapter 7: 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 375).
Page 211 Chapter 7: Using the Web Interface Field Description More Alerts This field appears only when there are more than one types of events triggering this alert. If there are other types of events (that is, other reasons) triggering the same alert, the total number of additional reasons is displayed.
Page 212: Dashboard - Ocp
Chapter 7: Using the Web Interface 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.
Page 213: Transfer Switch
Chapter 7: Using the Web Interface • A bar showing OCP current levels • OCP status -- open or closed • Associated line pair The RMS current bars automatically change colors to indicate the current status if OCP thresholds have been enabled. To configure thresholds, see OCPs (on page 249).
Page 214 Chapter 7: Using the Web Interface • Indicate which one is the 'preferred' inlet by showing either inlet's section For detailed information, see Transfer Switch and Inlet Status (on page 200). The same information is also available on the Dashboard page. See Dashboard - Transfer Switch (on page 182) and...
Page 215 Chapter 7: Using the Web Interface Verify both the icons are transferred to the other inlet, indicating that inlet becomes the active and preferred inlet now. Icon Description Preferred inlet, which is the first priority to power outlets in the normal state. Active inlet, which is the inlet being powering outlets.
Page 216 Chapter 7: Using the Web Interface To configure power quality settings: Click Edit Power Quality Parameters. Configure the power quality thresholds of both inlets. For details, see Power Quality Settings (on page 205). Note: Any changes made to power quality thresholds will change the voltage and frequency threshold values of both inlets.
Page 217 Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 834). To view the waveform of last transfer: On the Transfer Switch page, only the waveform of "the last" power transfer is displayed.
Page 218 Chapter 7: Using the Web Interface ▪ To retrieve the exact data at a particular time, hover your mouse over the line of either voltage or current waveform. The time, voltage value (blue) and current value (red) are all displayed as illustrated below.
Page 219 Chapter 7: Using the Web Interface To view the transfer log: The transfer log lists the last 10 power transfer events only, including automatic or manual transfer events. • To view the waveform or additional details of any transfer event, click that event in the transfer log.
Page 220: Transfer Switch And Inlet Status
Chapter 7: 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. See Transfer Switch (on page 193). Status of the transfer switch: One or some of the following messages are displayed for indicating the transfer switch state.
Page 221 Chapter 7: Using the Web Interface Message Status An overload is present. Overload Detected ▪ When the PX3TS device detects an overload condition on the outlet, it shuts down the outlet completely to protect the inlets. ▪ The state of the switch remains off as long as the overload alarm is present.
Page 222 Chapter 7: Using the Web Interface It may not be a problem when the inlets are out of sync. The PX3TS device can still work fine in that state. However, depending on your transfer settings, the 'out of sync' state may prevent an automatic retransfer from the standby inlet to the preferred inlet.
Page 223: Power Transfer Settings
Chapter 7: Using the Web Interface Data Description MOV Status Indicates whether each inlet's MOV surge protector works properly. ▪ If fine, "OK" is displayed. ▪ Otherwise, "fault" is displayed. In this case, contact Raritan for Return Merchandize Authorization (RMA) to fix the issue. +12V Supply Status The transfer switch receives DC 12V power from either inlet.
Page 224 Chapter 7: Using the Web Interface Field Description Allow Front Panel Enable/disable the front panel Manual Transfer 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. ▪...
Page 225: Power Quality Settings
Chapter 7: 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.
Page 226: Pdu
Chapter 7: Using the Web Interface ▪ Enter assertion times (seconds). See "To Assert" and Assertion Timeout (on page 837). ▪ Enter deassertion hysteresis values. To disable the deassertion hysteresis, type 0 (zero). See "To De-assert" and Deassertion Hysteresis (on page 839). Note: Any changes made to power quality thresholds will change the voltage and frequency threshold values of both inlets.
Page 227 Chapter 7: Using the Web Interface ▪ Click to select an option. ▪ Adjust the numeric values. ▪ Select or deselect the checkbox. ▪ For time-related fields, if you do not prefer the option selection using , you can type a value manually which must include a time unit, such as '50 s'.
Page 228 Chapter 7: Using the Web Interface Field Function Note ▪ See Initialization Delay Use Cases *Outlet initialization Determines how long the PX3TS waits page 213). delay on device before providing power to all outlets startup during power cycling or after recovering ▪...
Page 229 Chapter 7: Using the Web Interface 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 218) or Individual Outlet Pages (on page 232).
Page 230 Chapter 7: Using the Web Interface To view the active power's chart: You can check whether there were abnormal events through the device's active power chart. ▪ To retrieve the exact data at a particular time, hover your mouse over the data line in the chart.
Page 231: Internal Beeper State
Chapter 7: Using the Web Interface 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 (on page 215).
Page 232: Px3Ts Latching Relay Behavior
Chapter 7: 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.
Page 233: Initialization Delay Use Cases
Chapter 7: Using the Web Interface Additional Function option PDU defined Follows the global outlet state setting, which is set on (xxx) (on page 206). 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.
Page 234: How The Automatic Management Function Works
Chapter 7: Using the Web Interface Format Description Rack units The height of the Z coordinate is measured in standard rack units. When this is selected, you can type a numeric value in the rack unit to describe the Z coordinate of any environmental sensors or actuators.
Page 235: Setting Thresholds For Total Active Energy Or Power
Chapter 7: Using the Web Interface Unit Time 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.
Page 236: Inlets
Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 834). Click Save. Inlets The Inlets page lists both inlets, and the overview of each inlet's power data, including: •...
Page 237 Chapter 7: Using the Web Interface • 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 (on page 176).
Page 238: Individual Inlet Pages
Chapter 7: Using the Web Interface 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, once enabled, help you identify whether the inlet enters the warning or critical level.
Page 239 Chapter 7: Using the Web Interface Tip: To reset ALL active energy counters on the PX3TS, see (on page 206). To configure inlet thresholds: Per default, there are pre-defined RMS voltage and current threshold values in related fields. See Default Voltage and Current Thresholds (on page 842).
Page 240: Outlets
Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 834). Warning: The thresholds of voltage and line frequency of each inlet impact the power quality levels.
Page 241 Chapter 7: Using the Web Interface • Perform actions on all or multiple outlets simultaneously with setup/power-control commands on the top-right corner. Note that only outlet-switching capable models show the power-control buttons, and you must have the Switch Outlet permission to perform outlet-switching operations.
Page 242 Chapter 7: Using the Web Interface If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 179). To show or hide specific columns on the outlets overview page: Click to show a list of outlet data types. Select those you want to show, and deselect those you want to hide.
Page 243 Chapter 7: Using the Web Interface ▪ To select ALL outlets, select the topmost checkbox in the header row. Click or select the desired button or command. Button/command Action Power ON. Power OFF. Power cycle. ▪ Power cycling the outlet(s) turns the outlet(s) off and then back on.
Page 244: Available Data Of The Outlets Overview Page
Chapter 7: Using the Web Interface ▪ If needed, click to stop the outlet-switching operation. 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 .
Page 245: Bulk Configuration For Outlet Thresholds
Chapter 7: Using the Web Interface • Sequence order • Sequence delay (seconds) Note: To set critical and non-critical outlets, or set sequence-related settings, Outlets (on page 220). Bulk Configuration for Outlet Thresholds Outlet thresholds, if enabled, help you identify whether any outlet enters the warning or critical level.
Page 246: Setting Outlet Power-On Sequence And Delay
Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 834). 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.
Page 247: Setting Non-Critical Outlets
Chapter 7: Using the Web Interface Button Function 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.
Page 248 Chapter 7: Using the Web Interface ▪ To select ALL outlets, select the topmost checkbox in the header row. To turn non-critical outlets into critical ones, deselect their checkboxes. ▪ To deselect ALL outlets, deselect the topmost checkbox in the header row.
Page 249: Load Shedding Mode
Chapter 7: Using the Web Interface Load Shedding Mode When a UPS supplying power to 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.
Page 250 Chapter 7: Using the Web Interface Tip: The above two icons are switched if you manually perform any power operations on non-critical outlets during the load shedding mode. See and Lock Icons for Outlets (on page 231). ▪ The message "Load shedding active" appears next to the 'Outlets' title. ▪...
Page 251 Chapter 7: Using the Web Interface Off and Lock Icons for Outlets This section further explains the following two icons for outlets, which display in the load shedding mode. • Lock icon : It means the outlet WILL be automatically powered on after deactivating the load shedding mode.
Page 252: Individual Outlet Pages
Chapter 7: Using the Web Interface Individual Outlet Pages An outlet's data/setup page is opened after clicking the outlet's name on the Outlets overview page. See Outlets (on page 220). The individual outlet's page shows this outlet's detailed information. See Detailed Information on Outlet Pages (on page 238).
Page 253 Chapter 7: Using the Web Interface Button/command Action Power ON. Power OFF. Power cycle. ▪ Power cycling the outlet(s) turns the outlet(s) off and then back on. Confirm it on the confirmation message. Tip: To switch an outlet using the front panel display, see Outlet Switching page 135).
Page 254 Chapter 7: Using the Web Interface Field Description *Power off period Select an option to determine how long this outlet is during power cycle turned off before turning back on. ▪ Options: PDU defined or customized time. See Power-Off Period Options for Individual Outlets (on page 238).
Page 255 Chapter 7: Using the Web Interface Tip: To reset ALL active energy counters on the PX3TS, see (on page 206). To view this outlet's power chart: By default this outlet's active power data within the past tens of minutes is shown in the power chart.
Page 256 Chapter 7: Using the Web Interface ▪ To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. To configure this outlet's threshold settings: Per default, there are pre-defined RMS voltage and current threshold values in related fields.
Page 257 Chapter 7: Using the Web Interface ▪ 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, Sensor Threshold Settings (on page 834). Click Save.
Page 258 Chapter 7: Using the Web Interface Detailed Information on Outlet Pages Each outlet's data page has the Details section for showing general outlet information and Sensors section for showing the outlet sensor status. Details section: Field Description Label The physical outlet number Outlet status This information is only available on outlet-switching capable models.
Page 259: Outlet Groups
Chapter 7: Using the Web Interface Option Function If selecting this option, do either of the following: Customized time ▪ Click to select an existing time option. ▪ Type a new value with an appropriate time unit added. Time Units (on page 214).
Page 260: Creating An Outlet Group
Chapter 7: Using the Web Interface Then you can perform one of the following actions on one or multiple outlet groups: • Power on, off or cycle the selected group(s). See Outlet Group Power Control (on page 241). • Observe the power status of each outlet group and/or power status of each member outlet.
Page 261: Outlet Group Power Control
Chapter 7: Using the Web Interface Outlet Group Power Control You must have either permission below to power control any outlet groups. • Administrator Privileges • Switch Outlet Group You can switch one or multiple outlet groups at a time on the Outlet Groups page.
Page 262 Chapter 7: Using the Web Interface Button/command Action Power ON. Power OFF. Power cycle. ▪ Power cycling the outlet(s) turns the outlet(s) off and then back on. Confirm the operation when prompted. Verify that the outlet-switching result on the Outlet State column of the Outlet Groups page.
Page 263 Chapter 7: Using the Web Interface To switch one group on a specific outlet group's page: This method allows you to switch ONLY one outlet group at a time. Open a specific outlet group's page by clicking on its name. Click the desired power control button on the top-right corner.
Page 264: Modifying An Outlet Group
Chapter 7: Using the Web Interface Find the Switch Outlet Group permission, and re-select that newly-created outlet group in its outlet group list. Note: The above issue does not occur for any role which has "All Outlet Groups" selected for its Switch Outlet Group permission. Modifying an Outlet Group To modify an outlet group, you must have either permission below.
Page 265 Chapter 7: Using the Web Interface ▪ To select all available outlets, click Select All. ▪ To remove any outlet(s) from the Selected field, click that outlet's ▪ To remove all outlets, click Deselect All. Click Save. To change the group name: Click Edit Settings.
Page 266: Deleting An Outlet Group
Chapter 7: Using the Web Interface Deleting an Outlet Group To delete an outlet group, you must have either permission below. • Administrator Privileges • Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration You can delete one or multiple outlet groups at a time. To delete a single outlet group only, there are two methods -- either Outlet Groups page or individual group page.
Page 267: Visiting Other Pages From Current Group
Chapter 7: Using the Web Interface To delete a group on a specific outlet group's page: This method allows you to delete ONLY one outlet group at a time. Open a specific outlet group's page by clicking on its name. Click >...
Page 268 Chapter 7: Using the Web Interface To visit a different outlet group's page from the current page: • On an outlet group's individual page, you can go to another outlet group's page easily. Just click the outlet selector on the top-left corner.
Page 269: Ocps
Chapter 7: Using the Web Interface OCPs The OCPs 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.
Page 270 Chapter 7: Using the Web Interface Status Bar colors normal above upper warning above upper critical Note: The "below lower warning" and "below lower critical" states also show yellow and red colors respectively. However, it is not meaningful to enable the two thresholds for current levels. •...
Page 271: Individual Ocp Pages
Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 834). Click Save. Individual OCP Pages An OCP's data/setup page is opened after clicking any OCP's name on the OCPs or Dashboard page.
Page 272 Chapter 7: Using the Web Interface Field Description Protected outlets Outlets associated with this OCP. Inlet Inlet associated with this OCP. RMS current This OCP's current state and readings, including current drawn and current remaining. To customize this OCP's name: Click Edit Settings.
Page 273 Chapter 7: Using the Web Interface ▪ To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. To configure this OCP's threshold settings: By default, upper thresholds of an OCP's RMS current have been configured.
Page 274 Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 834). Click Save.
Page 275 Chapter 7: Using the Web Interface Other operations: • You can go to another OCP's data/setup page by clicking the OCP selector on the top-left corner. • You can go to the associated Inlet's data page by clicking the Inlet link in the Details section.
Page 276: Possible Ocp-Tripped Root Cause
Chapter 7: Using the Web Interface Possible OCP-Tripped Root Cause This feature applies to PX3TS-5000 models only. Outlet-metered models that support "outlet peak current" sensors can detect which outlet is LIKELY to cause the associated OCP to trip, and indicate it on several user interfaces, including the web interface, front panel display, and command line interface (CLI).
Page 277 Chapter 7: Using the Web Interface Front panel display: The 'Likely trip cause' message will be displayed for an "open" OCP, indicating which outlet may cause the OCP-tripped event. See OCPs (on page 148). CLI: • Perform the show ocp command in the CLI. If any OCP has tripped, then the outlet that may cause this event is shown in parentheses in the State field of the tripped OCP.
Page 278: Peripherals
Chapter 7: 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 Raritan Environmental Sensor Packages (on page 41). An environmental sensor package comprises one or some of the following sensors/actuators: •...
Page 279 Chapter 7: Using the Web Interface • Go to an individual sensor's or actuator's data/setup page by clicking its name. If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 179). Sensor/actuator overview on this page: If any sensor enters an alarmed state, it is highlighted in yellow or red.
Page 280 Chapter 7: Using the Web Interface Column Description Position The data indicates where this sensor or actuator is located in the sensor chain. Identifying the Sensor Position and Channel page 269). Actuator Indicates whether this sensor package is an actuator or not.
Page 281 Chapter 7: Using the Web Interface ▪ The management action triggers a "Manage Peripheral Device" dialog. Simply click Manage if you are managing multiple sensors/actuators. ▪ If you are managing only one sensor/actuator, you can choose to assign an ID number by selecting "Manually select a sensor number." Managing One Sensor or Actuator (on page 271).
Page 282 Chapter 7: Using the Web Interface Field Function Note ▪ The device's altitude is associated Altitude Specifies the altitude of PX3TS above sea with the altitude correction factor. level when a Raritan's differential air Altitude Correction Factors pressure sensor is attached. page 844).
Page 283 Chapter 7: Using the Web Interface Click the desired sensor type (required), and then click Edit Thresholds. 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, Sensor Threshold Settings (on page 834).
Page 284: Yellow- Or Red-Highlighted Sensors
Chapter 7: Using the Web Interface : Turn ON. : Turn OFF. Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered dry contact" actuator can be turned on at the same time.
Page 285 Chapter 7: Using the Web Interface Sensor status Color States shown in Description the interface unmanaged Sensors are not being managed. See Managed vs Unmanaged Sensors/Actuators (on page 266). ▪ Numeric or state sensors are within the normal range. Normal normal -- OR -- ▪...
Page 286: Managed Vs Unmanaged Sensors/Actuators
Chapter 7: Using the Web Interface Managed vs Unmanaged Sensors/Actuators To manually manage or unmanage/release a sensor or actuator, see Peripherals (on page 258). Managed sensors/actuators: • 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.
Page 287: Sensor/Actuator States
Chapter 7: Using the Web Interface Sensor/Actuator States An environmental sensor or actuator shows its real-time state after being managed. Available sensor states depend on the sensor type -- numeric or state sensors. For example, a contact closure sensor is a state sensor so it switches between three states only -- unavailable, alarmed and normal.
Page 288: Finding The Sensor's Serial Number
Chapter 7: Using the Web Interface Note that for a contact closure sensor, the normal state depends on the normal setting you have configured. Refer to the Environmental Sensors and Actuators Guide (or Online Help) for detailed information, which is available on Raritan's Support page (http://www.raritan.com/support/).
Page 289: Identifying The Sensor Position And Channel
Chapter 7: Using the Web Interface A DX2 DX, DPX2 or DPX3 sensor package has a serial number tag attached to its rear side. The serial number for each sensor or actuator appears listed in the 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.
Page 290 Chapter 7: Using the Web Interface • If a Raritan DPX3-ENVHUB4 sensor hub is involved, the hub port information is also indicated for DX2, DX, DPX2 and DPX3 series, but NOT indicated for DPX series. For example, Hub Port 3. •...
Page 291: Managing One Sensor Or Actuator
Chapter 7: Using the Web Interface Managing One Sensor or Actuator If you are managing only one sensor or actuator, you can assign the desired ID number to it. Note that you cannot assign ID numbers when managing multiple sensors/actuators at a time. Tip: When the total of managed sensors/actuators reaches the maximum value, you cannot manage additional ones.
Page 292 Chapter 7: Using the Web Interface 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 However, only relative humidity sensors are "automatically"...
Page 293: Individual Sensor/Actuator Pages
Chapter 7: Using the Web Interface Individual Sensor/Actuator Pages A sensor's or actuator's data/setup page is opened after clicking any sensor or actuator name on the Peripheral Devices page. See Peripherals (on page 258). Note that only a numeric sensor has threshold settings, while a state sensor or actuator has no thresholds.
Page 294 Chapter 7: Using the Web Interface Select or deselect 'Use default thresholds' according to your needs. ▪ To have this sensor follow the default threshold settings configured for its own sensor type, select the 'Use default thresholds' checkbox. The default threshold settings are configured on the page of Peripherals (on page 258).
Page 295 Chapter 7: Using the Web Interface To set up a sensor's or actuator's physical location and additional settings: Click Edit Settings. Make changes to available fields, and then click Save. Fields Description Name A name for the sensor or actuator. Description Any descriptive text you want.
Page 296 Chapter 7: Using the Web Interface Fields Description Sensor Polarity This field is available for DX2-CC2 contact closure sensors only. Determine the normal state of your DX2-CC2. ▪ Normal Open: The open status of the connected detector/switch is considered normal. An alarm is triggered when the detector/switch turns closed. ▪...
Page 297 Chapter 7: Using the Web Interface ▪ To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. To turn on or off an actuator: Click the desired control button.
Page 298: Sensor/Actuator Location Example
Chapter 7: Using the Web Interface Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered dry contact" actuator can be turned on at the same time. To change this limitation of "powered dry contact" actuators, modify the active powered dry contact setting.
Page 299: Feature Port
Chapter 7: Using the Web Interface 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.
Page 300 Chapter 7: 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 (on page 281), External Beeper (on page 289), Schroff LHX/SHX...
Page 301: Asset Strip
Chapter 7: Using the Web Interface 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 62).
Page 302 Chapter 7: Using the Web Interface Field Description 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.
Page 303 Chapter 7: Using the Web Interface ▪ Type the hexadecimal RGB value of the color, such as #00FF00. Click Ok. The rack unit numbering and LED color settings are immediately updated on the Rack Units list illustrated below. ▪ The 'Index' number is the physical tag port number printed on the asset strip, which is not configurable.
Page 304 Chapter 7: Using the Web Interface To customize a single rack unit's settings: You can make a specific rack unit's LED behave differently from the others on the asset strip, including the LED light and color. Click the desired rack unit on the Rack Units list. The setup dialog for the selected one appears.
Page 305 Chapter 7: Using the Web Interface Field Description LED Mode This field is configurable only after the Operation Mode is set to Manual Override. Determine how the LED light behaves for this particular rack unit. ▪ On: The LED stays lit. ▪...
Page 306 Chapter 7: Using the Web Interface 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...
Page 307 Chapter 7: Using the Web Interface To customize asset IDs on programmable asset tags: You can customize asset IDs only when the asset tags are "programmable" ones. Non-programmable tags do not support this feature. In addition, you can also customize the ID of a blade extension strip. If a barcode reader is intended, connect it to the computer you use to access the PX3TS.
Page 308 Chapter 7: Using the Web Interface ▪ An asset ID contains up to 12 characters that comprise only numbers and/or UPPER CASE alphabets. Lower case alphabets are NOT accepted. Verify the correctness of customized asset IDs and modify as needed. Click Apply at the bottom of the page to save changes.
Page 309: External Beeper
Chapter 7: 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.
Page 310: Schroff Lhx/Shx
Chapter 7: 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 (on page ® 462). After enabling the LHX/SHX support and connecting a supported Schroff ®...
Page 311 Chapter 7: Using the Web Interface For the functionality of this icon on the top-right corner, see Feature Port (on page 279). 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.
Page 312 Chapter 7: Using the Web Interface To configure LHX/SHX settings: Click Edit Settings. Configure the settings as needed. ▪ Provide a customized name. ▪ Specify the desired air outlet setpoint temperature. ▪ Specify the default fan speed. Click Save. To view all sensor data and configure thresholds: 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.
Page 313 Chapter 7: Using the Web Interface b. Click Edit Thresholds. Enable and set the desired thresholds and deassertion hysteresis. Note that assertion timeout is NOT available on LHX/SHX. d. Click Save. After thresholds are enabled, sensors may be highlighted in yellow or red if they enter the warning or critical range.
Page 314 Chapter 7: Using the Web Interface If any LHX sensors fail, they are indicated. Click Acknowledge to acknowledge the sensor failure. 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.
Page 315: Power Cim
Chapter 7: Using the Web Interface 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.
Page 316: User Management
Chapter 7: Using the Web Interface User Management User Management menu deals with user accounts, permissions, and preferred measurement units on a per-user basis. PX3TS is shipped with one built-in administrator account: admin, which is ideal for initial login and system administration. You cannot delete 'admin' or change its permissions, but you can and should change its password.
Page 317: Creating Users
Chapter 7: Using the Web Interface Creating Users All users must have a user account, containing the login name and password. Multiple users can log in simultaneously using the same login name. To add users, choose User Management > Users > User information: Field/setting Description...
Page 318 Chapter 7: Using the Web Interface Copy and paste all content in the text editor into the SSH Public Key field. SNMPv3: The SNMPv3 access permission is disabled by default. Field/setting Description Enable SNMPv3 Select this checkbox when intending to permit the SNMPv3 access by this user.
Page 319 Chapter 7: Using the Web Interface Field/setting Description Password, Type the privacy password if the 'Same as Authentication Password' checkbox is deselected. Confirm password The password must consist of 8 to 32 ASCII printable characters. • Protocol: This section is configurable only when 'Authentication' or 'Authentication &...
Page 320 Chapter 7: Using the Web Interface Note: Users can change the measurement units at any time by setting their own preferences. See Setting Your Preferred Measurement Units (on page 305). Roles: Select one or multiple roles to determine the user's permissions. To select all roles, select the topmost checkbox in the header row.
Page 321: Editing Or Deleting Users
Chapter 7: 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.
Page 322: Creating Roles
Chapter 7: Using the Web Interface Click Save. To delete multiple user accounts: On the Users page, click to make checkboxes appear in front of user names. Tip: To delete only one user, you can simply click that user without making the checkboxes appear.
Page 323 Chapter 7: Using the Web Interface Built-in role Description 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) • Switch Outlet Group (if your PX3TS is outlet-switching capable) •...
Page 324: Editing Or Deleting Roles
Chapter 7: Using the Web Interface ▪ To select all arguments, simply select the checkbox labeled 'All XXX'. Tip: The other way to select all arguments is to select that privilege's checkbox while the arguments list is not expanded yet. For example, on an outlet-switching capable model, you can specify the outlets that users can switch on/off as shown below.
Page 325: Setting Your Preferred Measurement Units
Chapter 7: Using the Web Interface ▪ To delete this role, click , and confirm the operation. Click Save. To delete any roles: On the Roles page, click to make checkboxes appear in front of roles. Tip: To delete only one role, you can simply click that role without making the checkboxes appear.
Page 326: Setting Default Measurement Units
Chapter 7: Using the Web Interface Field Description 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 Click Save.
Page 327 Chapter 7: Using the Web Interface User Interfaces Showing Default Units Default measurement units will apply to the following user interfaces or data: • Web interface for "newly-created" local users when they have not configured their own preferred measurement units. See Creating Users (on page 297).
Page 328: Device Settings
Chapter 7: Using the Web Interface Device Settings Click 'Device Settings' in the Menu (on page 176), and the following submenu displays. Menu command Submenu command Refer to... Network Configuring Network Settings (on page 310) Network Services HTTP Changing HTTP(S) Settings (on page 338) SNMP Configuring SNMP Settings...
Page 329 Chapter 7: Using the Web Interface Menu command Submenu command Refer to... SMTP Server Configuring SMTP Settings (on page 342) Changing SSH Settings (on page 343) Telnet Changing Telnet Settings (on page 344) Modbus Changing Modbus Settings (on page 344) Server Advertising Enabling Service Advertising (on page 347)
Page 330: Configuring Network Settings
Chapter 7: Using the Web Interface Configuring Network Settings Configure wired, wireless, and Internet protocol-related settings on the Network page after Connecting the PX3TS to Your Network (on page 13). You can enable both the wired and wireless networking on PX3TS so that it has multiple IP addresses -- wired and wireless IP.
Page 331 Chapter 7: Using the Web Interface After enabling either or both Internet protocols: After enabling IPv4 and/or IPv6, all but not limited to the following protocols will be compliant with the selected Internet protocol(s): • LDAP • • SMTP • •...
Page 332 Chapter 7: 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 ▪...
Page 333 Chapter 7: Using the Web Interface (Optional) To view the diagnostic log for EAP authentication: • Click Show EAP Authentication Log. See Diagnostic Log for Network Connections (on page 322). Common Network Settings Common Network Settings are OPTIONAL, not required. Therefore, leave them unchanged if there are no specific local networking requirements.
Page 334 Chapter 7: Using the Web Interface Field Description First/Second/Third Manually specify static DNS server(s). DNS server ▪ 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.
Page 335 Chapter 7: Using the Web Interface Field Description simultaneously. • Half: Data is transmitted in one direction (to or from the PX3TS) at a time. Show the LAN's current status, including the current Current state speed and duplex mode. Authentication Select an authentication method.
Page 336 Chapter 7: Using the Web Interface Field Description Client certificate, This field appears when 'EAP', 'PEAP' and 'TLS' are Client private key, all selected. Client private key password PEM encoded X.509 certificate and PEM encoded private key are required for certification-based authentication methods.
Page 337 Chapter 7: Using the Web Interface Field/setting Description Click this button to import a certificate file. Then you can: ▪ Click Show to view the certificate's content. ▪ Click Remove to delete the installed certificate if it is inappropriate. ▪ Select this checkbox to make the authentication Allow expired and succeed regardless of the certificate's validity not yet valid...
Page 338 Chapter 7: Using the Web Interface Field/setting Description Hardware state Check this field to ensure that the PX3TS has detected a wireless USB LAN adapter. If not, verify whether the USB LAN adapter is firmly connected or whether it is supported.
Page 339 Chapter 7: Using the Web Interface Field/setting Description Inner authentication This field appears when both 'EAP' and 'PEAP' are selected. ▪ MS-CHAPv2: Authentication based on the given password using MS-CHAPv2 protocol. ▪ TLS: Authentication between the client and authentication server is performed using TLS certificates.
Page 340 Chapter 7: Using the Web Interface Field/setting Description RADIUS This field appears when 'EAP' is selected. authentication server name Type the name of the RADIUS server if it is present in the TLS certificate. ▪ The name must match the fully qualified domain name (FQDN) of the host shown in the certificate.
Page 341 Chapter 7: Using the Web Interface IPv4 settings: Field/setting Description Enable IPv4 Enable or disable the IPv4 protocol. IP auto configuration Select the method to configure IPv4 settings. ▪ DHCP: Auto-configure IPv4 settings via DHCP servers. ▪ Static: Manually configure the IPv4 settings. Preferred hostname Enter the hostname you prefer for IPv4 connectivity •...
Page 342 Chapter 7: Using the Web Interface (Optional) To view the wireless LAN diagnostic log: • Click Show WLAN Diagnostic Log. See Diagnostic Log for Network Connections (on page 322). Diagnostic Log for Network Connections PX3TS provides a diagnostic log for inspecting connection errors that occurred during the EAP authentication or the wireless network connection.
Page 343 Chapter 7: Using the Web Interface ▪ When there are more than 5 pages and the page numbers listed does not show the desired one, click to have the bar show the next or previous five page numbers, if available. If wanted, you can resort the list by clicking the desired column header.
Page 344 Chapter 7: Using the Web Interface Static Route Examples This section describes two static route examples: IPv4 and IPv6. Both examples assume that two network interface controllers (NIC) have been installed in one network server, leading to two available subnets, and IP forwarding has been enabled.
Page 345 Chapter 7: 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 enter the data as shown below. Note that the address in the first field must be of the Classless Inter-Domain Routing (CIDR) notation.
Page 346 Chapter 7: Using the Web Interface Tip: If you have configured multiple static routes, you can click on any route and then make changes, use to re-sort the priority, or click to delete it. IPv6 example: • Your PX3TS: fd07:2fa:6cff:2405::30 •...
Page 347 Chapter 7: 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 enter the data as shown below. Note that the address in the first field must be of the Classless Inter-Domain Routing (CIDR) notation.
Page 348 Chapter 7: Using the Web Interface Interface list: Interface name Description When another wired network is connected to the BRIDGE 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 ETH1 ETH1 port of your PX3TS, select this interface name.
Page 349 Chapter 7: Using the Web Interface Mode Description No cascading mode is enabled. This is the default. None Each device in the cascading chain is accessed Bridging with a different IP address. Each device in the cascading chain is accessed Port Forwarding with the same IP address(es) but with a different port number assigned.
Page 350 Chapter 7: Using the Web Interface Tip: You can enable/configure multiple network interfaces in the Port Forwarding mode so that the cascading chain has multiple IP addresses. Click Save. For information on accessing each cascaded device in the Port Forwarding mode, see Port Forwarding Examples (on page 334).
Page 351 Chapter 7: Using the Web Interface 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.
Page 352 Chapter 7: Using the Web Interface Port Number Syntax In the Port Forwarding mode, all devices in the cascading chain share the same IP address(es). To access any cascaded device, you must assign an appropriate port number to it. • Master device: The port number is either 5NNXX or the standard TCP/UDP port.
Page 353 Chapter 7: Using the Web Interface • XX is a two-digit number representing the device position as shown below. Position Position Master device Slave 8 Slave 1 Slave 9 Slave 2 Slave 10 Slave 3 Slave 11 Slave 4 Slave 12 Slave 5 Slave 13 Slave 6...
Page 354 Chapter 7: Using the Web Interface Port Forwarding Examples To access a cascaded device in the Port Forwarding mode, assign a port number to the IP address. • Master device: Assign proper 5NNXX port numbers or standard TCP/UDP ports. See Port Number Syntax (on page 332) for details.
Page 355 Chapter 7: Using the Web Interface Slave 1 device: Position code for Slave 1 is '01' so each port number is 5NN01 as shown below. Protocols Port numbers HTTPS 50001 HTTP 50101 50201 TELNET 50301 SNMP 50501 MODBUS 50601 Examples: •...
Page 356 Chapter 7: Using the Web Interface Adding, Removing or Swapping Cascaded Devices Change a device's cascading mode first before adding that device to a cascading chain, or before disconnecting that device from the chain. If you only want to change the cascading mode of an existing chain, or swap the master and slave device, always start from the slave device.
Page 357: Configuring Network Services
Chapter 7: Using the Web Interface ▪ You must disconnect the LAN cable and ALL cascading cables connected to the two devices first before swapping them, and then reconnecting all cables. To change the cascading mode applied to a chain: Access the last slave device, and change its cascading mode.
Page 358 Chapter 7: Using the Web Interface HTTPS and HTTP enable the access to the web interface. Telnet and SSH enable the access to the command line interface. See Using the Command Line Interface (on page 524). By default, SSH is enabled, Telnet is disabled, and all TCP ports for supported services are set to standard ports.
Page 359 Chapter 7: Using the Web Interface Special note for AES ciphers: The PX3TS device's TLS-based protocols support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between PX3TS and the client (such as a web browser), which is impacted by the cipher priority of PX3TS and the client's cipher availability/settings.
Page 360 Chapter 7: Using the Web Interface Configuring SNMP Settings You can enable or disable SNMP communication between an SNMP manager and the PX3TS. 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"...
Page 361 Chapter 7: Using the Web Interface 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."...
Page 362 Chapter 7: Using the Web Interface 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 375). 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.
Page 363 Chapter 7: Using the Web Interface Field/setting Description Click this button to import a certificate file. Then you can: ▪ Click Show to view the certificate's content. ▪ Click Remove to delete the installed certificate if it is inappropriate. ▪ Select this checkbox to make the authentication Allow expired and succeed regardless of the certificate's validity not yet valid...
Page 364 Chapter 7: Using the Web Interface ▪ 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. 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.
Page 365 Chapter 7: Using the Web Interface Modbus Gateway: If connecting the Modbus RTU devices to PX3TS and enabling the Modbus Gateway feature, the Modbus TCP clients on your network will be able to communicate with those Modbus RTU devices attached to PX3TS. See Connecting a Modbus RTU Device or Bus.
Page 366 Chapter 7: Using the Web Interface Field Description Use the default port 503, or assign a different port. Valid range is TCP port 1 to 65535. Note: Port 502 is the default Modbus/TCP port for PX3TS, so you cannot use that port for the Modbus Gateway. Use the default values, or update if the Modbus RTU devices are Parity, using different communication parameters.
Page 367 Chapter 7: 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.
Page 368: Configuring Security Settings
Chapter 7: 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.
Page 369 Chapter 7: Using the Web Interface Creating IP Access Control Rules IP access control rules (firewall rules) determine whether to accept or discard traffic to/from the PX3TS, based on the IP address of the host sending or receiving the traffic. When creating rules, keep these principles in mind: •...
Page 370 Chapter 7: Using the Web Interface ADD a rule to the end of the list ▪ Click Append. ▪ Type an IP address and subnet mask in the IP/Mask field. ▪ Select an option in the Policy field. ▪ Accept: Accepts traffic from/to the specified IP address(es). ▪...
Page 371 Chapter 7: Using the Web Interface ▪ You can select any existing rule and then click change its priority. Click Save. The rules are applied.
Page 372 Chapter 7: Using the Web Interface To configure IPv6 access control rules: On the same page, select the 'Enable IPv6 access control' checkbox to enable IPv6 access control rules. Follow the same procedure as the above IPv4 rule setup to create IPv6 rules.
Page 373 Chapter 7: Using the Web Interface Creating Role Based Access Control Rules Role-based access control rules are similar to IP access control rules, except that they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses. Same as IP access control rules, the order of role-based access control rules is important, since the rules are executed in numerical order.
Page 374 Chapter 7: Using the Web Interface ▪ You can select any existing rule and then click change its priority. Click Save. The rules are applied. To configure IPv6 access control rules: On the same page, select the 'Enable role based access control for IPv6' checkbox to enable IPv6 access control rules.
Page 375 Chapter 7: Using the Web Interface ▪ Make changes to the selected rule, and then click Save. For information on each field, see Creating Role Based Access Control Rules (on page 353). ▪ Click to remove it. ▪ To resort its order, click Click Save.
Page 376 Chapter 7: Using the Web Interface Creating a CSR Follow this procedure to create the CSR for your PX3TS. Note that you must enter information in the fields showing the message 'required.' To create a CSR: Choose Device Settings > Security > TLS Certificate. Provide the information requested.
Page 377 Chapter 7: Using the Web Interface Field Do this Key length Select an available key length (bits). A larger key length enhances the security, but slows down the response of PX3TS. ▪ Only 2048 is available now. Self-sign For requesting a certificate signed by the CA, ensure this checkbox is NOT selected.
Page 378 Chapter 7: Using the Web Interface To verify whether the certificate has been installed successfully, check the data shown in the Active TLS Certificate section. Creating a Self-Signed Certificate When appropriate certificate and key files for PX3TS are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate.
Page 379 Chapter 7: Using the Web Interface Double check the data shown in the New TLS Certificate section. b. If correct, click "Install Key and Certificate" to install the self-signed certificate and private key. Tip: To verify whether the certificate has been installed successfully, check the data shown in the Active TLS Certificate section.
Page 380 Chapter 7: Using the Web Interface Click Upload. The selected files are installed. To verify whether the certificate has been installed successfully, check the data shown in the Active TLS Certificate section. Setting Up External Authentication Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0.
Page 381 Chapter 7: Using the Web Interface Special note about the AES cipher: The PX3TS device's TLS-based protocols support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between PX3TS and the client (such as a web browser), which is impacted by the cipher priority of PX3TS and the client's cipher availability/settings.
Page 382 Chapter 7: Using the Web Interface 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: Choose Device Settings > Security > Authentication. Click New in the LDAP Servers section.
Page 383 Chapter 7: Using the Web Interface Field/setting Description Enable verification of Select this checkbox if it is required to validate the LDAP server's certificate LDAP server certificate by the PX3TS prior to the connection. If the certificate validation fails, the connection is refused. CA certificate Consult your AA server administrator to get the CA certificate file for the LDAPS server.
Page 384 Chapter 7: Using the Web Interface Field/setting Description User entry object class The object class for user entries. ▪ Usually it is inetOrgPerson. User search subfilter Search criteria for finding LDAP user objects within the directory tree. Active Directory The name of the Active Directory Domain. domain ▪...
Page 385 Chapter 7: Using the Web Interface 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).
Page 386 Chapter 7: Using the Web Interface 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.
Page 387 Chapter 7: Using the Web Interface Note: Whenever PX3TS is successfully connected to one external authentication server, it STOPS trying access to remaining servers in the authentication list regardless of the user authentication result. To enable both external and local authentication: In the 'Authentication type' field, select the external authentication you want -- LDAP or RADIUS.
Page 388 Chapter 7: 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 703). To set limitations for login timeout and use of identical login names: In the "Idle timeout period"...
Page 389 Chapter 7: Using the Web Interface Minimum length = 8 characters Maximum length = 32 characters At least one lowercase character = Required At least one uppercase character = Required At least one numeric character = Required At least one special character = Required Number of forbidden previous passwords Note: The maximum password length accepted by PX3TS is 64 characters.
Page 390 Chapter 7: Using the Web Interface Login manner after enabling the service agreement: After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen. Do either of the following, or the login fails: • In the web interface, select the checkbox labeled "I understand and accept the restricted service agreement."...
Page 391: Setting The Date And Time
Chapter 7: Using the Web Interface Setting the Date and Time Set the internal clock on the PX3TS 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.
Page 392 Chapter 7: Using the Web Interface Use the NTP server ▪ Select "Synchronize with NTP server." ▪ There are two ways to assign the NTP servers: ▪ To use the DHCP-assigned NTP servers, DO NOT enter any NTP servers for the First and Second time server.
Page 393 Chapter 7: Using the Web Interface Calendar The calendar icon in the Date field is a convenient tool to select a custom date. Click it and a calendar similar to the following appears. Number Item Description arrows Switch between months. dates All dates of the selected month.
Page 394 Chapter 7: Using the Web Interface 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.
Page 395: Event Rules And Actions
Chapter 7: Using the Web Interface Event Rules and Actions A benefit of the product's intelligence is its ability to notify you of or react to a change in conditions. This event notification or reaction is an "event rule." An event rule consists of two parts: •...
Page 396 Chapter 7: Using the Web Interface Click to schedule the desired action. Assign a name to this scheduled action. b. Make sure the Enabled checkbox is selected, or the PX3TS does not perform this scheduled action. Set the interval time, which ranges from every minute to yearly. d.
Page 397 Chapter 7: Using the Web Interface ▪ <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. In this example, the Peripheral Device Slot is selected, which is related to the environmental sensor packages.
Page 398 Chapter 7: Using the Web Interface 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. 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.
Page 399 Chapter 7: Using the Web Interface To remove any action(s) from the 'Selected actions' field, click that action's ▪ To remove all actions, click Deselect All. Radio buttons for different events: According to the event you select, the "Trigger condition" field containing three radio buttons may or may not appear.
Page 400 Chapter 7: Using the Web Interface Event types Radio buttons ▪ Link state is up: PX3TS takes the action only Network interface link when the network link state changes from down state to up. ▪ Link state is down: PX3TS takes the action only when the network link state changes from up to down.
Page 401 Chapter 7: Using the Web Interface Event types Radio buttons ▪ Connected: PX3TS takes the action only when Device connection or the selected device is physically connected to it. disconnection, such as ▪ Disconnected: PX3TS takes the action only when a USB-cascaded slave device the selected device is physically disconnected...
Page 402 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Asset Management > Firmware Firmware update for asset strip Update [AMSNUMBER] ('[AMSNAME]'): status changed to '[AMSSTATE]'. Asset Management > Device Config parameter '[CONFIGPARAM]' of Config Changed asset strip [AMSNUMBER] ('[AMSNAME]')
Page 403 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Device > Firmware update Firmware upgraded successfully from completed version '[OLDVERSION]' to version '[VERSION]' by user '[USERNAME]' from host '[USERIP]'. Device >...
Page 404 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Device > Sending SMS message Sending SMS message to failed '[PHONENUMBER]' failed. Device > An LDAP error occurred An LDAP error occurred: [ERRORDESC]. Device >...
Page 405 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Peripheral Device Slot > * > Peripheral device '[EXTSENSORNAME]' in Peripheral device '[EXTSENSORNAME]' Numeric Sensor > Below lower slot [EXTSENSORSLOT] asserted 'below in slot [EXTSENSORSLOT] deasserted critical threshold lower critical' at [SENSORREADING]...
Page 406 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Inlet > * > Sensor > * > Reset Sensor '[INLETSENSOR]' on inlet '[INLET]' has been reset by user '[USERNAME]' from host '[USERIP]'.
Page 407 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE '[USERNAME]' from host '[USERIP]'. Outlet > * > Sensor > Outlet Outlet '[OUTLET]' state changed to on. Outlet '[OUTLET]' state changed to off. State >...
Page 408 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE [SENSORREADINGUNIT]. [SENSORREADINGUNIT]. Overcurrent Protector > * > Sensor '[OCPSENSOR]' on overcurrent Sensor '[OCPSENSOR]' on overcurrent Sensor > * > Below lower critical protector '[OCP]' asserted 'below lower protector '[OCP]' deasserted 'below threshold...
Page 409 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Pdu > Controller > * > Firmware Controller '[CONTROLLER]' with board ID Controller '[CONTROLLER]' with board update [BOARDID] has started firmware update ID [BOARDID] has completed firmware update Pdu >...
Page 410 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE [SENSORREADINGUNIT]. [SENSORREADINGUNIT]. Transfer Switch > Sensor > * > Sensor '[TRANSFERSWITCHSENSOR]' on Sensor '[TRANSFERSWITCHSENSOR]' on Unavailable transfer switch '[TRANSFERSWITCH]' transfer switch '[TRANSFERSWITCH]' unavailable.
Page 411 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE User Administration > User User '[UMTARGETUSER]' deleted by user deleted '[USERNAME]' from host '[USERIP]'. User Administration > Password Password of user '[UMTARGETUSER]' changed changed by user '[USERNAME]' from host '[USERIP]'.
Page 412 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE LHX/SHX > Sensor > Above upper Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX at warning threshold [PORTTYPE] port '[PORTID]' asserted [PORTTYPE] port '[PORTID]' deasserted 'above upper warning' at 'above upper warning' at...
Page 413 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE LHX/SHX > Sensor Failure A sensor failure (broken or short circuit) occurred on LHX at [PORTTYPE] port '[PORTID]' at sensor '[LHXSENSORID]'. LHX/SHX >...
Page 414 Chapter 7: 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. To test an action: • Click the Test button next to the Action. The action is triggered and you can verify it.
Page 415 Chapter 7: Using the Web Interface Note: The "Change load shedding state", "Power control server", "Switch outlets" and "Switch outlet group" options are only available for outlet-switching capable models. Action Function Alarm Requires the user to acknowledge the alert after it is generated.
Page 416 Chapter 7: Using the Web Interface Action Function Request LHX/SHX Applies the maximum cooling to the LHX/SHX maximum cooling device. See Request LHX/SHX Maximum Cooling (on page 403). This option is available only when the Schroff LHX/SHX support has been enabled. Send email Emails a textual message.
Page 417 Chapter 7: Using the Web Interface Enter the information as needed and click Create. Then you can assign the newly-created action to an event rule or schedule it. See Event Rules and Actions (on page 375). Alarm The Alarm is an action that requires users to acknowledge an alert. This helps ensure that the user is aware of the alert.
Page 418 Chapter 7: Using the Web Interface 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.
Page 419 Chapter 7: Using the Web Interface External Beeper This section applies to PX3 only. 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: Choose Device Settings >...
Page 420 Chapter 7: Using the Web Interface Log an Event Message The option 'Log event message' records the selected events in the internal log. The default log message generated for each type of event is available in the section titled Default Log Messages (on page 381).
Page 421 Chapter 7: Using the Web Interface 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.
Page 422 Chapter 7: Using the Web Interface 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.
Page 423 Chapter 7: Using the Web Interface Folder name options Definition Serial number / Webcam name / Three folders will be created. Formatted timestamp ▪ Definitions of the parent folder and first subfolder are the same as the first row. ▪ The final subfolder's name is the time when the recording event occurs, which is a format comprising year, month, date, hour, minute, second and timezone.
Page 424 Chapter 7: Using the Web Interface In the Available LHX/SHX field, select the desired SHX-30 device one by one, or click Select All. 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.
Page 425 Chapter 7: Using the Web Interface When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 425).
Page 426 Chapter 7: Using the Web Interface 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 listed below.
Page 427 Chapter 7: Using the Web Interface b. Click the second to select the specific sensor for the target from the list. Click to add the selected sensor to the Report Sensors list box. For example, to monitor the current reading of the Inlet 1, select Inlet 1 from the left field, and then select RMS Current from the right field.
Page 428 Chapter 7: Using the Web Interface Send SMS Message You can configure SMS messages to be sent when an event occurs and can customize the message. Only the 7-bit ASCII charset is supported for SMS messages. Messages consist of a combination of free text and PX3TS placeholders. The placeholders represent information which is pulled from the PX3TS and inserted into the message.
Page 429 Chapter 7: Using the Web Interface ▪ When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 425).
Page 430 Chapter 7: Using the Web Interface Select the webcam that is capturing the images you want sent in the email. Adjust the values of the following: ▪ Number of snapshots - the number of snapshots to be taken when the event occurs.
Page 431 Chapter 7: Using the Web Interface Send an SNMP Notification This option sends an SNMP notification to one or multiple SNMP destinations. Operation: Choose Device Settings > Event Rules > Select 'Send SNMP notification' from the Action list. Select the type of SNMP notification. See either procedure below according to your selection.
Page 432 Chapter 7: Using the Web Interface b. In the 'Number of retries' field, specify the number of times you want to re-send the inform communication if it fails. For example, inform communications are re-sent up to 5 times when the initial communication fails.
Page 433 Chapter 7: Using the Web Interface 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.
Page 434 Chapter 7: Using the Web Interface To specify the outlet group where this action will be applied, select it from the 'Group to switch' list. In the Operation field, select an operation for the selected outlet group. ▪ Turn on all outlets in group: Turns on the selected outlet group. ▪...
Page 435 Chapter 7: Using the Web Interface Select 'Switch peripheral actuator' from the Action list. In the Operation field, select an operation for the selected actuator(s). ▪ Turn on: Turns on the selected actuator(s). ▪ Turn off: Turns off the selected actuator(s). To select the actuator(s) where this action will be applied, select them one by one from the 'Available actuators' list.
Page 436 Chapter 7: Using the Web Interface Transport Next steps protocols A TLS certificate is required. Do the following: Type an appropriate port number in the 'TCP port' field. Default is 6514. b. In the 'CA certificate' field, click to select a TLS certificate. After importing the certificate, you may: ▪...
Page 437 Chapter 7: Using the Web Interface To remove any action(s) from the 'Selected actions' field, click that action's ▪ To remove all actions, click Deselect All. Select the desired frequency in the 'Execution time' field, and then specify the time interval or a specific date and time in the field(s) that appear.
Page 438 Chapter 7: Using the Web Interface Execution time Frequency settings Click the Frequency field to select an option. Minutes 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 Hourly following: ▪...
Page 439 Chapter 7: Using the Web Interface Send Sensor Report Example To create a scheduled action for emailing a temperature sensor report hourly, it requires: • A 'Send email' action • A 'Send sensor report' action • A timer - that is, the scheduled action Steps: Click to create a 'Send email' action that sends an...
Page 440 Chapter 7: Using the Web Interface ▪ If wanted, you can customize the subject and content of this email in this action.
Page 441 Chapter 7: Using the Web Interface...
Page 442 Chapter 7: Using the Web Interface Click to create a 'Send sensor report' action that includes the 'Email a Sensor Report' action as its destination action. For details, see Send Sensor Report (on page 406). ▪ In this example, this action is named Send Temperature Sensor Readings.
Page 443 Chapter 7: Using the Web Interface ▪ You can specify more than one temperature sensor as needed in this action. Click to create a timer for performing the 'Send Temperature Sensor Readings' action hourly. For details, see Scheduling an Action (on page 416).
Page 444 Chapter 7: Using the Web Interface ▪ In this example, the timer is named Hourly Temperature Sensor Reports. ▪ To perform the specified action at 12:30 pm, 01:30 pm, 02:30 pm, and so on, select Hourly, and set the Minute to 30. Then the PX3TS will send out an email containing the specified temperature sensor readings hourly every day.
Page 445 Chapter 7: Using the Web Interface Placeholders for Custom Messages Actions of "Send email" and "Send SMS message" allow you to customize event messages. See Send Email (on page 404) or Send SMS Message (on page 408). In addition, you can add custom text message to the "Send snapshots via email"...
Page 446 Chapter 7: Using the Web Interface Placeholder Definition [AMSNAME] The name of an asset strip [AMSNUMBER] The numeric ID of an asset strip [AMSRACKUNITPOSITION] The (vertical) rack unit position [AMSSTATE] The human-readable state of an asset strip [AMSTAGID] The asset tag ID [CARDREADERCHANNEL] The channel number of a card reader [CARDREADERID]...
Page 447 Chapter 7: Using the Web Interface Placeholder Definition [LDAPERRORDESC] The LDAP error occurred [LHXFANID] The ID of a fan connected to an LHX/SHX [LHXPOWERSUPPLYID] The ID of an LHX/SHX power supply [LHXSENSORID] The ID of an LHX/SHX sensor probe [LOGMESSAGE] The original log message [MONITOREDHOST] The name or IP address of a monitored host...
Page 448 Chapter 7: Using the Web Interface Placeholder Definition [PORTTYPE] The type of the external port (e.g. 'feature' or 'auxiliary') the event-triggering device is connected to [RADIUSERRORDESC] The Radius error message [ROMCODE] The romcode of an attached peripheral device [SENSORREADING] The value of a sensor reading [SENSORREADINGUNIT] The unit of a sensor reading [SENSORREPORT]...
Page 449 Chapter 7: Using the Web Interface Editing or Deleting a Rule/Action You can change the settings of an event rule, action or scheduled action, or delete them. Exception: Some settings of the built-in event rules or actions are not user-configurable. You cannot delete built-in rules and actions. See Built-in Rules and Rule Configuration (on page 376) or...
Page 450 Chapter 7: Using the Web Interface To make 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.
Page 451 Chapter 7: Using the Web Interface Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for the System SNMP Notification Action. See Enabling and Configuring SNMP (on page 515). Then the SNMP notifications are sent when: ▪...
Page 452 Chapter 7: Using the Web Interface 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 •...
Page 453 Chapter 7: Using the Web Interface ▪ The active energy sensor is reset. For example, when the Inlet I1's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again. Sample Environmental-Sensor-Level Event Rule This section applies to outlet-switching capable models only.
Page 454 Chapter 7: Using the Web Interface 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: •...
Page 455 Chapter 7: Using the Web Interface 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.
Page 456 Chapter 7: Using the Web Interface 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."...
Page 457: Setting Data Logging
Chapter 7: Using the Web Interface 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.
Page 458: Configuring Data Push Settings
Chapter 7: Using the Web Interface Configuring Data Push Settings You can push the sensor or asset strip data to a remote server for data synchronization. The destination and authentication for data push have to be configured properly on the PX3TS. The data will be sent in JSON format using HTTP POST requests.
Page 459 Chapter 7: Using the Web Interface ▪ Asset management tag log: Transmit the log of all asset strips, which is generated when there are changes made to asset tags and asset strips, including asset tag connection or disconnection events. ▪ Sensor log: Transmit the record of all logged sensors, including their sensor readings and/or status.
Page 460 Chapter 7: Using the Web Interface Sensor Log The root object of the message is a SensorLogPushMessage structure. It comprises a list of sensor descriptors and a list of log rows. Sensor descriptors: The sensor descriptor vector contains static information of all logged sensors, including: •...
Page 461 Chapter 7: Using the Web Interface Sensor Descriptors for Inlet Active Power The following illustrates a descriptor for an inlet active power sensor. The metadata field is relevant only to numeric sensors so the readingtype field is displayed twice in the illustration. Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.
Page 462 Chapter 7: Using the Web Interface Log Rows The following illustrates log rows with only one sensor record shown. The actual length and order of log rows will be the same as those of sensors descriptors. Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.
Page 463 Chapter 7: Using the Web Interface Asset Management Tag List The root object of the asset management tag list message is an AssetStripsMessage structure. It contains current data about all connected asset management strips and tags, which is similar to the illustration below.
Page 464 Chapter 7: Using the Web Interface...
Page 465 Chapter 7: Using the Web Interface (Continued)
Page 466 Chapter 7: Using the Web Interface Asset Management Tag Log The root object of the asset management log message is an AssetLogPushMessage structure. It contains a list of tag or strip events since the last successful push. Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.
Page 467: Monitoring Server Accessibility
Chapter 7: Using the Web Interface Monitoring Server Accessibility You can monitor whether specific IT devices are alive by having the PX3TS 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.
Page 468 Chapter 7: Using the Web Interface Field Description Number of successful The number of successful pings required to pings to enable feature declare that the monitored equipment is "Reachable." Valid range is 0 to 200. Wait time after The wait time before sending the next ping if successful ping the previous ping was successfully responded.
Page 469 Chapter 7: Using the Web Interface To configure the shutdown and power control settings: Restriction: To make the power control feature work properly, the power cord(s) of the monitored IT device must be connected to the "same" PDU which is monitoring the IT device. Field Description This is the command which is sent to the...
Page 470 Chapter 7: Using the Web Interface Field Description Method of checking This field determines when PX3TS will power off successful shutdown the outlet(s) that supplies power to the monitored device, after PX3TS issues the shutdown command to that device. ▪ Timer: PX3TS will power off the selected outlet or outlet group after the time specified in the 'Timer delay' field expires.
Page 471 Chapter 7: Using the Web Interface Status Description Reachable The monitored equipment is accessible. Unreachable The monitored equipment is inaccessible. Waiting for reliable The connection between the PX3TS device and the connection monitored equipment is not reliably established yet. If your PX3TS supports outlet switching, one more column displays -- Power Control.
Page 472 Chapter 7: Using the Web Interface Observe the Power Control status of the monitored device to make sure the power-on operation succeeds. Editing or Deleting Ping Monitoring Settings You can edit the ping monitoring settings of any IT device or simply delete it if no longer needed.
Page 473 Chapter 7: Using the Web Interface Field Data entered Wait time after successful ping ▪ 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 Data entered Wait time after unsuccessful ping...
Page 474: Front Panel Settings
Chapter 7: Using the Web Interface 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 429). Front Panel Settings You can set up the default mode of the front panel display, and front panel functions for actuator control, beeper mute or RCM self-test.
Page 475: Configuring The Serial Port
Chapter 7: Using the Web Interface Or you can turn on or off actuators by operating the front panel. See Peripherals (on page 151). Configuring the Serial Port You can change the bit rate of the serial port labeled CONSOLE / MODEM on the PX3TS.
Page 476: Lua Scripts
Chapter 7: Using the Web Interface 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). Click the 'Modem baud rate' field to select the baud rate for the modem connected to the PX3TS.
Page 477 Chapter 7: 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.
Page 478 Chapter 7: Using the Web Interface ▪ To write a Lua script, type the codes in the Source Code section. ▪ To load an existing Lua script file, click Load Local File. ▪ To use one of Raritan's Lua script examples, click Load Example. Warning: The newly-loaded script will overwrite all existing codes in the Source Code section.
Page 479 Chapter 7: Using the Web Interface Manually Starting or Stopping a Script You can manually start or stop an existing Lua script at any time. When starting a script, you can choose to start it either with its default arguments or with new arguments. Tip: To have the PX3TS automatically start or stop a script in response to an event, create an event rule.
Page 480 Chapter 7: Using the Web Interface Click Start. 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: Choose Device Settings > Lua Scripts. Click the desired script whose state is either 'Running' or 'Restarting.' For details, see Checking Lua Scripts States...
Page 481 Chapter 7: 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. State Description The script is never executed since the device boot. Running The script is currently being executed.
Page 482: Miscellaneous
Chapter 7: Using the Web Interface 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: Choose Device Settings >...
Page 483 Chapter 7: Using the Web Interface To set the Cisco EnergyWise configuration: Select the Enable EnergyWise checkbox. Configure the following: Field Description Domain name Type the name of a Cisco EnergyWise domain where the PX3TS belongs ▪ Up to 127 printable ASCII characters are permitted. ▪...
Page 484: Maintenance
Chapter 7: Using the Web Interface Maintenance Click 'Maintenance' in the Menu (on page 176), and the following submenu displays. Submenu command Refer to... Device Information Device Information (on page 466) Connected Users Viewing Connected Users (on page 471) Event Log Viewing or Clearing the Local Event Log (on page 473) Update Firmware...
Page 485 Chapter 7: Using the Web Interface Submenu command Refer to... Bulk Configuration Bulk Configuration (on page 479) Backup/Restore Backup and Restore of Device Settings (on page 486) Network Diagnostic Network Diagnostics (on page 488) Download Diagnostic Downloading Diagnostic Information (on page 489) Hardware Failures Hardware Issue Detection (on page 489)
Page 486: Device Information
Chapter 7: 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.
Page 487 Chapter 7: Using the Web Interface Section title Information shown name, serial number, firmware version, hardware revision, MIB download link(s) and so Note that the download link of LHX-MIB is available only after enabling the Schroff LHX/SHX support. See Miscellaneous (on page 462).
Page 488 Chapter 7: Using the Web Interface Identifying Cascaded Devices For information on how to cascade PX3TS devices, see Cascading Multiple PX3TS Devices for Sharing Ethernet Connectivity (on page 27). This section explains how to identify a cascaded device on the Device Information page.
Page 489 Chapter 7: Using the Web Interface Cascading information in the Port Forwarding mode: • The Common section contains three read-only fields for indicating the cascading status. Fields Description Port forwarding Indicates the Port Forwarding is enabled. See Setting the Cascading Mode (on page 328).
Page 490 Chapter 7: Using the Web Interface ▪ A master device shows 0 (zero) in the 'Cascade position' field and yes in the 'Cascaded device connected' field. ▪ A slave device in the middle position shows a non-zero number which indicates its exact position in the 'Cascade position' field and yes in the 'Cascaded device connected' field.
Page 491: Viewing Connected Users
Chapter 7: Using the Web Interface The following diagram shows 2, indicating it is the second slave device - Slave 2. The 'Cascaded device connected' field shows no, indicating that it is the final one in the chain. • For a list of port numbers required for accessing each cascaded device in the Port Forwarding mode, click the Port Forwarding title bar on the same page.
Page 492 Chapter 7: Using the Web Interface Column Description User Name The login name of each connected user. IP Address The IP address of each user's host. For the login via a local connection (serial RS-232 or USB), <local> is displayed instead of an IP address. Client Type The interface through which the user is being connected to the PX3TS.
Page 493: Viewing Or Clearing The Local Event Log
Chapter 7: 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.
Page 494: Updating The Px3Ts Firmware
Chapter 7: Using the Web Interface Updating the PX3TS Firmware Firmware files are available on Raritan website's Support page (http://www.raritan.com/support/). 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.
Page 495 Chapter 7: Using the Web Interface 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. To proceed with the update, click Update Firmware. Warning: Do NOT power off the PX3TS during the update.
Page 496 Chapter 7: Using the Web Interface Upgrade Guidelines for Existing Cascading Chains You must obey the following guidelines when upgrading a chain. Otherwise, a networking issue occurs. • Firmware version 3.3.10 or later is NOT compatible with pre-3.3.10 firmware versions in terms of the cascading feature so all Raritan devices in the cascading chain must run version 3.3.10 or later.
Page 497 3.5.0, 3.4.0, and so on. Therefore, it is suggested to AVOID downgrading your cascading chain unless instructed by Raritan or Legrand Technical Support. For minimum firmware versions, see Cascading Restrictions in the Cascading Guide on the Support page (http://www.raritan.com/support/).
Page 498: Viewing Firmware Update History
Chapter 7: 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.
Page 499: Bulk Configuration
Chapter 7: Using the Web Interface If wanted, you can resort the list by clicking the desired column header. Sorting a List (on page 179). 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.
Page 500 Chapter 7: Using the Web Interface Note: On startup, 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"...
Page 501 Chapter 7: Using the Web Interface Mechanical designs ignored by bulk configuration: When the source and target devices share the same technical specifications but are only different with any "mechanical designs" which are indicated in the table below, the bulk configuration remains feasible. These mechanical designs are represented by suffixes added to the model name of a PX3TS device.
Page 502 Chapter 7: Using the Web Interface Customizing Bulk Configuration Profiles A bulk profile defines which settings are downloaded/saved from the source device and which are not. The default is to apply the built-in bulk profile, which downloads all settings from the source device except for device-specific data. If the built-in profile does not meet your needs, you can create your own profile(s), and then apply the wanted profile before downloading/saving any settings from the source device.
Page 503 Chapter 7: Using the Web Interface Option Description Built-in The setting will follow the same setting of Raritan's built-in profile. ▪ If 'Excluded' is selected in the built-in profile, this setting will be also excluded. ▪ If 'Included' is selected in the built-in profile, this setting will be also included.
Page 504 Chapter 7: Using the Web Interface Step 2: Save a bulk configuration file You must have the Administrator Privileges or "Unrestricted View Privileges" to download the configuration. Log in to the source PX3TS if you have not yet. Choose Maintenance > Bulk Configuration. Check the 'Bulk format' field.
Page 505 Chapter 7: Using the Web Interface Alternatives: To use a different bulk configuration method, refer to: • Bulk Configuration via SCP (on page 712) • Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 746) • Configuration or Firmware Upgrade with a USB Drive (on page 731) •...
Page 506: Backup And Restore Of Device Settings
Chapter 7: Using the Web Interface ▪ To select ALL profiles, select the topmost checkbox in the header row. Click on the top-right corner. Click Delete on the confirmation message. Backup and Restore of Device Settings Unlike the bulk configuration file, the backup file contains ALL device settings, including device-specific data like device names and all network settings.
Page 507 Chapter 7: Using the Web Interface To restore the PX3TS using a backup file: You must have the Administrator Privileges to restore the device settings. Choose Maintenance > Backup/Restore. Click to select the backup file. Click 'Upload & Restore Device Settings' to upload the file. ▪...
Page 508: Network Diagnostics
Chapter 7: Using the Web Interface Network Diagnostics 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. •...
Page 509: Downloading Diagnostic Information
Chapter 7: Using the Web Interface Downloading Diagnostic Information Important: This function is for use by Raritan Field Engineers or when you are directed by Raritan Technical Support. You can download the diagnostic file from the PX3TS to a client machine. The file is compressed into a .tgz file and should be sent to Raritan Technical Support for interpretation.
Page 510 Chapter 7: Using the Web Interface Hardware Failure alerts on the Dashboard page: Note that current hardware failure events, if any, will also display on the Dashboard (on page 180). Hardware failure types: Hardware issues Description A specific networking interface of PX3TS is NOT detected. Network device not detected A specific I2C bus is stuck, which affects the communication with I2C Bus stuck...
Page 511: Rebooting The Px3Ts
Chapter 7: Using the Web Interface Rebooting the PX3TS You can remotely reboot the PX3TS 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.
Page 512: Retrieving Software Packages Information
Chapter 7: Using the Web Interface To reset the device to factory defaults: Choose Maintenance > Unit Reset > Type your password and then click Factory Reset to reset the PX3TS to factory defaults. A message appears, with a countdown timer showing the remaining time of the operation.
Page 513: Webcam Management
Chapter 7: Using the Web Interface Webcam Management The 'Webcams' menu item appears when there is any webcam(s) connected to the PX3TS, or when there are snapshots saved onto the PX3TS already. See Connecting a Logitech Webcam (on page 72).
Page 514 Chapter 7: Using the Web Interface 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. Permissions required: To do... Permission(s) required Either permission below: View snapshots and videos ▪...
Page 515: Configuring Webcams And Viewing Live Images
Chapter 7: Using the Web Interface Configuring Webcams and Viewing Live Images To configure a webcam or view live snapshot/video sessions, choose Webcams in the Menu (on page 176). Then click the desired webcam to open that webcam's page. Note that default webcam names are determined by the detection order. The one that is detected first is named Webcam, and the other that is detected later is named Webcam 2.
Page 516 Chapter 7: Using the Web Interface Tip: The date and time shown on the PX3TS web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of PX3TS to your computer or mobile device.
Page 517 Chapter 7: Using the Web Interface Click Edit Settings. Enter a name for the webcam. Up to 64 ASCII printable characters are supported. ▪ If configured to store snapshots on a remote server, the webcam's name determines the name of the folder where snapshots are stored. Changing Storage Settings (on page 502) and Identifying...
Page 518: Sending Links To Snapshots Or Videos
Chapter 7: Using the Web Interface Sending Links to Snapshots or Videos When opening a Primary Standalone Live Preview window, a unique URL is generated for this window session. You can email or instant message this URL to as many people as possible as long as your system resources permit. Recipients can then click on the provided link and view live snapshots or videos simultaneously in the Secondary Standalone Live Preview window(s).
Page 519 Chapter 7: Using the Web Interface Select the URL shown on the top of the image. b. Right click to copy the URL, or press CTRL+ C. Send the URL link through an email or instant message application to one or multiple persons.
Page 520: Viewing And Managing Locally-Saved Snapshots
Chapter 7: Using the Web Interface How Long a Link Remains Accessible For documentation purposes, the one who opens and sends the URL of the Primary Standalone Live Preview window is called User A and the two recipients of the same URL link are called User B and C. User C is able to access the snapshot or video image via the link when the URL link remains valid, which can be one of these scenarios: •...
Page 521 Chapter 7: Using the Web Interface To view saved snapshots: Choose Webcams > . The Snapshots page opens. Click the snapshot you want to view from the list. Tip: The date and time shown on the PX3TS web interface are automatically converted to your computer's time zone.
Page 522: Changing Storage Settings
Chapter 7: Using the Web Interface On the top of the list, click Click Delete on the confirmation message. To download any image onto the computer: • To download an image onto your computer, move your mouse to that image, right click on it, and choose Save Image As. Changing Storage Settings Important: The PX3TS web interface only lists the snapshots stored locally on the PX3TS device, but does NOT list those saved onto remote servers.
Page 523 Chapter 7: Using the Web Interface Storage location Description 'Local' means the PX3TS. This is the default. Local ▪ It can store a maximum of 10 snapshots only. ▪ The web interface can list and display all snapshots stored on the PX3TS. See Viewing and Managing Locally-Saved Snapshots (on page 500).
Page 524: Identifying Snapshots Folders On Remote Servers
Chapter 7: Using the Web Interface Tip for notifications showing the snapshots path on FTP: If you are using SNMP to retrieve PX3TS data, you can make PX3TS automatically send a notification containing the full path or URL to the snapshots saved onto FTP with this SNMP code: webcamStorageUploadStarted.
Page 525 Chapter 7: Using the Web Interface Number Folder name description The name of the webcam that your PX3TS detects first. This is the folder where the snapshots captured by the first webcam are stored. ▪ The first webcam's default name is "Webcam". ▪...
Page 526: Smartlock And Card Reader
Chapter 7: Using the Web Interface SmartLock and Card Reader Raritan's SmartLock kits provide several cabinet access control solutions. If you have purchased a SmartLock kit with the door handle controller "DX2-DH2C2", both menu items "SmartLock" and "Card Readers" will appear in the menu after connecting and configuring properly DX2-DH2C2 and the door handles included in the kit.
Page 527 Chapter 7: Using the Web Interface Note that "SmartLock" appears only when your door handles are connected to PX3TS via DX2-DH2C2, but "Card Readers" appears as long as PX3TS detects the presence of any card reader -- either a standalone USB card reader or a card reader integrated with the door handles.
Page 528: Smartlock
Chapter 7: Using the Web Interface SmartLock To open the SmartLock page, choose SmartLock in the Menu (on page 176). The page shows information of all DX2-DH2C2 modules attached to PX3TS, including its serial number, position and its door handle configuration. On this page you can: •...
Page 529 Chapter 7: Using the Web Interface • Configure the door handles connected to DX2-DH2C2. You must set this because PX3TS cannot detect the types of connected door handles. • Control the door handles connected to DX2-DH2C2. To configure the door handles: There are two door handle sections per DX2-DH2C2 because a DX2-DH2C2 has two door handle ports.
Page 530 Chapter 7: Using the Web Interface Section Description ▪ Specify how long the door handle lock can remain Timeout open after someone opens the door handle via a smart card or via remote control using the software. When the timeout expires, the door handle lock will be automatically closed.
Page 531 Chapter 7: Using the Web Interface Door Handle Status and Control After configuring the door handle type properly, two more sections are shown for the configured door handle -- Door State and Card Reader.
Page 532 Chapter 7: Using the Web Interface To view the status of the door and card reader: Section Description Shows all sensor states detected by DX2-DH2C2, including: Door State ▪ Door: States of contact closure sensors connected to DX2-DH2C2. Contact closure sensors detect whether the door is physically opened or closed.
Page 533: Card Readers
Chapter 7: Using the Web Interface Go to the proper door handle section, and click Open or Close to open or close the door handle lock. Confirm the operation when prompted. Now you can physically open the cabinet door with the opened door handle.
Page 534 Chapter 7: Using the Web Interface When a user scans his/her smart card with the card reader, PX3TS will retrieve the card's type and ID and show them in the corresponding Card Type and Card ID column. If no data is shown in the two columns, it means the scanned card may not be supported by the card reader.
Page 535: Chapter 8 Using Snmp
Chapter 8 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.
Page 536: Snmpv2C Notifications
Chapter 8: Using SNMP In the SNMP Notifications section, enable the SNMP notification feature, and configure related fields. For details, refer to: ▪ SNMPv2c Notifications (on page 516) ▪ SNMPv3 Notifications (on page 517) 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.
Page 537: Snmpv3 Notifications
Chapter 8: Using SNMP Field Description once every 3 seconds. Number of retries The number of times you want to resend the inform communication if it fails. ▪ For example, inform communications are resent up to 5 times when the initial communication fails. Host The IP address of the device(s) you want to access.
Page 538 Chapter 8: Using SNMP In the SNMP Notifications section, make sure the 'Enable SNMP notifications' checkbox is selected. Select 'SNMPv3 trap' or 'SNMPv3 inform' as the notification type. For SNMP TRAPs, the engine ID is prepopulated. Type values in the following fields. Field Description Host...
Page 539 Chapter 8: Using SNMP Field Description This is the address to which notifications are sent by the SNMP agent. Port The port number used to access the device(s). User ID User name for accessing the device. ▪ Make sure the user has the SNMP v3 access permission.
Page 540: Downloading Snmp Mib
Chapter 8: Using SNMP Downloading SNMP MIB You must download an appropriate SNMP MIB file for successful SNMP communications. Always use the latest SNMP MIB downloaded from 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: Choose Device Settings >...
Page 541: Snmp Gets And Sets
Chapter 8: Using SNMP 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.
Page 542 Chapter 8: 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.
Page 543: Retrieving Energy Usage
Chapter 8: Using SNMP 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) •...
Page 544: Chapter 9 Using The Command Line Interface
Chapter 9 Using the Command Line Interface This section explains how to use the command line interface (CLI) to administer the PX3TS. Note that available CLI commands are model dependent. CLI commands are case sensitive. In This Chapter About the Interface ..................524 Logging in to CLI ....................
Page 545: Logging In To Cli
Chapter 9: Using the Command Line Interface 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.
Page 546: With Ssh Or Telnet
Chapter 9: Using the Command Line Interface After properly entering the password, the PDU name appears at the prompt. See Different CLI Modes and Prompts (on page 527) in the User Guide for more information. Tip: The 'Last login' information, including the date and time, is also displayed if the same user account was used to log in to this product's web interface or CLI.
Page 547: With An Analog Modem
Chapter 9: Using the Command Line Interface 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: Make sure the PX3TS has an analog modem connected.
Page 548: Closing A Local Connection
Chapter 9: Using the Command Line Interface Closing a Local Connection Close the window or terminal emulation program when you finish accessing the PX3TS 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.
Page 549: Querying Available Parameters For A Command
Chapter 9: Using the Command Line Interface Querying Available Parameters for a Command If you are not sure what commands or parameters are available for a particular type of CLI command or its syntax, you can have the CLI show them by adding a space and the help command (?) or list command (ls) to the end of that command.
Page 550: Showing Information
Chapter 9: Using the Command Line Interface 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 Some "show"...
Page 551 Chapter 9: Using the Command Line Interface - 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.
Page 552: Network Configuration
Chapter 9: 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 interfaces' duplex mode, and the wireless interface's status/settings. show network IP Configuration This command shows the IP settings shared by all network interfaces, such as DNS and routes.
Page 553 Chapter 9: Using the Command Line Interface Interface Description Show the IP-related configuration of all interfaces. Tip: You can also type the command without adding this option "all" to get the same data. That is, show network ip interface. IPv4-Only or IPv6-Only Configuration To show IPv4-only or IPv6-only configuration, use any of the following commands.
Page 554 Chapter 9: Using the Command Line Interface Interface Description eth1 Show the IPv4 or IPv6 configuration of the ETH1 interface. eth2 Show the IPv4 or IPv6 configuration of the ETH2 interface. wireless Show the IPv4 or IPv6 configuration of the WIRELESS interface.
Page 555 Chapter 9: Using the Command Line Interface Interface Description Show the non-IP settings of all interfaces. Tip: You can also type the command without adding this option "all" to get the same data. That is, show network interface. Network Service Settings This command shows the network service settings only, including the Telnet setting, TCP ports for HTTP, HTTPS, SSH and Modbus/TCP services, and SNMP settings.
Page 556: Pdu Configuration
Chapter 9: Using the Command Line Interface PDU Configuration This command shows the PDU configuration, such as the device name, firmware version, model type and upper limit of active powered dry contact actuators. show pdu To show detailed information, add the parameter "details" to the end of the command.
Page 557: Outlet Group Information
Chapter 9: Using the Command Line Interface Outlet Group Information This command syntax shows the outlet group information. show outletgroups <n> To show detailed information, add the parameter "details" to the end of the command. show outletgroups <n> details Variables: •...
Page 558: Inlet Information
Chapter 9: Using the Command Line Interface Inlet Information This command syntax shows the inlet information. show inlets <n> To show detailed information, add the parameter "details" to the end of the command. show inlets <n> details Variables: • <n> is one of the options: all, or a number. Option Description Displays the information for all inlets.
Page 559: Overcurrent Protector Information
Chapter 9: 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"...
Page 560: Date And Time Settings
Chapter 9: Using the Command Line Interface Date and Time Settings This command shows the current date and time settings on the PX3TS. 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...
Page 561: Environmental Sensor Information
Chapter 9: Using the Command Line Interface Environmental Sensor Information This command syntax shows the environmental sensor's information. show externalsensors <n> To show detailed information, add the parameter "details" to the end of the command. show externalsensors <n> details Variables: •...
Page 562: Environmental Sensor Package Information
Chapter 9: Using the Command Line Interface * The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripherals page of the PX3TS web interface. Displayed information: • Without the parameter "details," only the sensor ID, sensor type and reading are displayed.
Page 563: Actuator Information
Chapter 9: Using the Command Line Interface Actuator Information This command syntax shows an actuator's information. show actuators <n> To show detailed information, add the parameter "details" to the end of the command. show actuators <n> details Variables: • <n> is one of the options: all, or a number. Option Description Displays the information for all actuators.
Page 564: Outlet Sensor Threshold Information
Chapter 9: 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.
Page 565: Inlet Sensor Threshold Information
Chapter 9: Using the Command Line Interface Inlet Sensor Threshold Information This command syntax shows the specified inlet sensor's threshold-related information. show sensor inlet <n> <sensor type> To show detailed information, add the parameter "details" to the end of the command.
Page 566: Overcurrent Protector Sensor Threshold Information
Chapter 9: 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"...
Page 567: Environmental Sensor Threshold Information
Chapter 9: Using the Command Line Interface Environmental Sensor Threshold Information This command syntax shows the specified environmental sensor's threshold-related information. show sensor externalsensor <n> To show detailed information, add the parameter "details" to the end of the command. show sensor externalsensor <n> details...
Page 568: Environmental Sensor Default Thresholds
Chapter 9: Using the Command Line Interface Variables: • <n> is the environmental sensor number. The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripherals page of the PX3TS web interface. Displayed information: •...
Page 569: Security Settings
Chapter 9: Using the Command Line Interface Sensor types Description All of the above numeric sensors Tip: You can also type the command without adding this option "all" to get the same data. Displayed information: • Without the parameter "details," only the default upper and lower thresholds, deassertion hysteresis and assertion timeout settings of the specified sensor type are displayed.
Page 570: Authentication Settings
Chapter 9: Using the Command Line Interface Authentication Settings General authentication settings: This command displays the authentication settings of the PX3TS, including both LDAP and Radius settings. show authentication One LDAP server's settings: To show the configuration of a specific LDAP server, assign the desired LDAP server with its sequential number in the command.
Page 571: Existing User Profiles
Chapter 9: Using the Command Line Interface Existing User Profiles This command shows the data of one or all existing user profiles. show user <user_name> To show detailed information, add the parameter "details" to the end of the command. show user <user_name> details Variables: •...
Page 572: Existing Roles
Chapter 9: Using the Command Line Interface Existing Roles This command shows the data of one or all existing roles. show roles <role_name> Variables: • <role_name> is the name of the role whose permissions you want to query. The variable can be one of the following options: Option Description This option shows all existing roles.
Page 573: Energywise Settings
Chapter 9: Using the Command Line Interface 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.
Page 574: Rack Unit Settings Of An Asset Strip
Chapter 9: 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.
Page 575: Blade Extension Strip Settings
Chapter 9: 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: •...
Page 576: Event Log
Chapter 9: Using the Command Line Interface Event Log The command used to show the event log begins with show eventlog. You can add either the limit or class parameters or both to show specific events. Show the last 30 entries: show eventlog Show a specific number of last entries in the event log: show eventlog limit <n>...
Page 577: Network Connections Diagnostic Log
Chapter 9: Using the Command Line Interface Event type Description serverMonitor Server-monitoring records, such as a server being declared reachable or unreachable. assetManagement Raritan asset management events, such as asset tag connections or disconnections. Schroff LHX/SHX heat exchanger events. ® modem Modem-related events.
Page 578: Command History
Chapter 9: Using the Command Line Interface Server Reachability Information for a Specific Server To show the server reachability information for a certain IT device only, use the following command. show serverReachability server <n> To show detailed information, add the parameter "details" to the end of the command.
Page 579: Reliability Data
Chapter 9: Using the Command Line Interface Reliability Data This command shows the reliability data. show reliability data Reliability Error Log This command shows the reliability error log. show reliability errorlog <n> Variables: • <n> is one of the options: 0 (zero) or any other integer number. Option Description Displays all entries in the reliability error log.
Page 580 Chapter 9: Using the Command Line Interface Example 1 - Basic Security Information The diagram shows the output of the show security command.
Page 581 Chapter 9: Using the Command Line Interface Example 2 - In-Depth Security Information More information is displayed when typing the show security details command. Example 3 - Basic PDU Information The diagram shows the output of the show pdu command.
Page 582: Clearing Information
Chapter 9: Using the Command Line Interface Example 4 - In-Depth PDU Information More information is displayed when typing the show pdu details command. Displayed information varies depending on the model you purchased. Clearing Information You can use the clear commands to remove unnecessary data from the PX3TS. After typing a "clear"...
Page 583: Clearing Diagnostic Log For Network Connections
Chapter 9: Using the Command Line Interface Clearing Diagnostic Log for Network Connections This command removes all data from the diagnostic log for both the EAP authentication and WLAN connection. clear networkDiagLog -- OR -- clear networkDiagLog /y If you entered the command without "/y," a message appears, prompting you to confirm the operation.
Page 584: Quitting Configuration Mode
Chapter 9: Using the Command Line Interface Quitting Configuration Mode Both of "apply" and "cancel" commands let you quit the configuration mode. The difference is that "apply" saves all changes you made in the configuration mode while "cancel" aborts all changes. To quit the configuration mode, use either command: config:# apply...
Page 585 Chapter 9: Using the Command Line Interface 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. Manual transfer may be prevented in certain scenarios. If so, a "Transfer failed"...
Page 586 Chapter 9: Using the Command Line Interface Configuring Power Transfer Features Enter the configuration mode to change the following power transfer settings. Entering Configuration Mode (on page 563). You can change various power transfer settings at a time by combining various commands.
Page 587 Chapter 9: Using the Command Line Interface • <option3> is an integer number up to 180 in seconds. • <option4> is one of the options: enable or disable. Option Description enable Automatic retransfer is performed only when inlets are in phase. disable Automatic retransfer is performed regardless of the phase angle difference.
Page 588 Chapter 9: Using the Command Line Interface 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>...
Page 589: Pdu Configuration Commands
Chapter 9: 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. •...
Page 590 Chapter 9: 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>...
Page 591 Chapter 9: 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>;...
Page 592 Chapter 9: Using the Command Line Interface Option Description lastKnownState Restores all outlets to the previous status before powering down the PX3TS 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"...
Page 593 Chapter 9: 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 (on page 206) for information on outlet initialization delay. config:# pdu outletInitializationDelayOnDeviceStartup <timing>...
Page 594 Chapter 9: Using the Command Line Interface Enabling or Disabling Data Logging This command enables or disables the data logging feature. config:# pdu dataRetrieval <option> Variables: • <option> is one of the options: enable or disable. Option Description enable Enables the data logging feature. disable Disables the data logging feature.
Page 595 Chapter 9: Using the Command Line Interface Specifying the Device Altitude This command specifies the altitude of your PX3TS above sea level (in meters). You must specify the altitude of PX3TS above sea level if a Raritan's differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor.
Page 596 Chapter 9: Using the Command Line Interface Enabling or Disabling Peripheral Device Auto Management This command enables or disables the Peripheral Device Auto Management feature. config:# pdu peripheralDeviceAutoManagement <option> Variables: • <option> is one of the options: enable or disable. Option Description enable...
Page 597: Network Configuration Commands
Chapter 9: Using the Command Line Interface 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.
Page 598 Chapter 9: Using the Command Line Interface Interface Description eth1 Determine the IPv4 configuration mode of the ETH1 interface (wired networking). eth2 Determine the IPv4 configuration mode of the ETH2 interface (wired networking). Determine the IPv4 configuration mode of the wireless WIRELESS interface (that is, wireless networking).
Page 599 Chapter 9: Using the Command Line Interface Interface Description 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 ▪...
Page 600 Chapter 9: Using the Command Line Interface 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.
Page 601 Chapter 9: Using the Command Line Interface config:# network ipv4 staticRoutes modify <route_ID> dest <dest-2> interface <ETH> Variables: • <dest-1> is a combination of the IP address and subnet mask of the other subnet. The format is IP address/subnet mask. •...
Page 602 Chapter 9: Using the Command Line Interface Interface Description bridge Determine the IPv6 configuration mode of the BRIDGE interface (that is, bridging mode). • <mode> is one of the modes: automatic or static. Mode Description automatic The IPv6 configuration mode is set to automatic. static The IPv6 configuration mode is set to static IP address.
Page 603 Chapter 9: Using the Command Line Interface • Cannot contain punctuation marks, spaces, and other symbols Setting the IPv6 Address After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX3TS. config:# network ipv6 interface <ETH>...
Page 604 Chapter 9: Using the Command Line Interface Setting the IPv6 Gateway After selecting the static IP configuration mode, you can use this command to specify the gateway. config:# network ipv6 gateway <ip address> Variables: • <ip address> is the IP address of the gateway. This value uses the IPv6 address format.
Page 605 Chapter 9: Using the Command Line Interface config:# network ipv6 staticRoutes modify <route_ID> dest <dest-2> interface <ETH> Variables: • <dest-1> is the IP address and prefix length of the subnet where the PX3TS belongs. The format is IP address/prefix length. •...
Page 606 <suffix1>, <suffix2>, and the like are the DNS suffixes that automatically apply when searching for any device via PX3TS. For example, <suffix1> can be raritan.com, and <suffix2> can be legrand.com. You can specify up to 6 suffixes by separating them with commas.
Page 607 Chapter 9: Using the Command Line Interface • <option> is one of the options: true or false. Option Description true The specified network interface is enabled. false The specified network interface is disabled. Changing the LAN Interface Speed This command determines the LAN interface speed. config:# network ethernet <ETH>...
Page 608 Chapter 9: Using the Command Line Interface Changing the LAN Duplex Mode This command determines the LAN interface duplex mode. config:# network ethernet <ETH> duplexMode <mode> Variables: • <ETH> is one of the options -- eth1 or eth2. Option Description eth1 ETH1 port eth2...
Page 609 Chapter 9: Using the Command Line Interface Setting the SSID This command specifies the SSID string. config:# network wireless SSID <ssid> Variables: • <ssid> is the name of the wireless access point, which consists of: - Up to 32 ASCII characters - No spaces - ASCII codes 0x20 ~ 0x7E Setting the Wireless Authentication Method...
Page 610 Chapter 9: Using the Command Line Interface Setting Wireless EAP Parameters When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, client certificate, client private key, password, CA certificate, and RADIUS authentication server.
Page 611 Chapter 9: Using the Command Line Interface Allow expired and not yet valid TLS certificates: config:# network wireless allowOffTimeRangeCerts <option2> Allow wireless network connection with incorrect system time: config:# network wireless allowConnectionWithIncorrectClock <option3> Set the RADIUS authentication server for EAP: config:# network wireless eapAuthServerName <FQDN>...
Page 612 Chapter 9: Using the Command Line Interface Option Description false The network connection is NOT successfully established when the TLS certificate chain contains any certificate which is outdated or not valid yet. • <option3> is one of the options: true or false. Option Description true...
Page 613 Chapter 9: Using the Command Line Interface Open a CA certificate using a text editor. You should see certificate contents similar to the following. Select and copy the contents as illustrated below, including the starting line containing "BEGIN CERTIFICATE" and the ending line containing "END CERTIFICATE."...
Page 614 Chapter 9: Using the Command Line Interface Configuring the Cascading Mode This command determines the cascading mode. config:# network <mode> enabled <option1> Variables: • <mode> is one of the following cascading modes. Mode Description bridge The Bridging mode, where each cascaded device is assigned a unique IP address.
Page 615 Chapter 9: Using the Command Line Interface 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.
Page 616 Chapter 9: Using the Command Line Interface 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>...
Page 617 Chapter 9: 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>...
Page 618 Chapter 9: Using the Command Line Interface Option Description false 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 Changing the SSH Configuration You can enable or disable the SSH service, or change its TCP port using the CLI commands.
Page 619 Chapter 9: Using the Command Line Interface Determining the SSH Authentication Method This command syntax determines the SSH authentication method. config:# network services ssh authentication <auth_method> Variables: • <option> is one of the options: passwordOnly, publicKeyOnly or passwordOrPublicKey. Option Description passwordOnly Enables the password-based login only.
Page 620 Chapter 9: Using the Command Line Interface Enabling or Disabling SNMP v3 This command enables or disables the SNMP v3 protocol. config:# network services snmp v3 <option> Variables: • <option> is one of the options: enable or disable. Option Description enable The SNMP v3 protocol is enabled.
Page 621 Chapter 9: Using the Command Line Interface Setting the sysName Value This command sets the SNMP MIB-II sysName value. config:# network services snmp sysName <value> Variables: • <value> is a string comprising 0 to 255 alphanumeric characters. Setting the sysLocation Value This command sets the SNMP MIB-II sysLocation value.
Page 622 Chapter 9: Using the Command Line Interface Enabling or Disabling the Read-Only Mode This command enables or disables the read-only mode for the Modbus agent. config:# network services modbus readonly <option> Variables: • <option> is one of the options: true or false. Option Description true...
Page 623: Time Configuration Commands
Chapter 9: Using the Command Line Interface • <option> is one of the options: enable or disable. Option Description enable Service advertisement via the selected method (MDNS or LLMNR) is enabled. disable Service advertisement via the selected method (MDNS or LLMNR) is disabled. Examples This section illustrates several network configuration examples.
Page 624 Chapter 9: Using the Command Line Interface Determining the Time Setup Method This command determines the method to configure the system date and time. config:# time method <method> Variables: • <method> is one of the time setup options: manual or ntp. Mode Description manual...
Page 625 Chapter 9: Using the Command Line Interface Setting NTP Parameters A time configuration command for NTP-related parameters begins with time ntp. Specify the primary time server: config:# time ntp firstServer <first_server> Specify the secondary time server: config:# time ntp secondServer <second_server> To delete the primary time server: config:# time ntp firstServer ""...
Page 626 Chapter 9: Using the Command Line Interface Customizing the Date and Time 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 page 604).
Page 627 Chapter 9: Using the Command Line Interface Type apply for the selected time zone to take effect. Setting the Automatic Daylight Savings Time This command determines whether the daylight saving time is applied to the time settings. config:# time autoDST <option> Variables: •...
Page 628: Checking The Accessibility Of Ntp Servers
Chapter 9: Using the Command Line Interface Checking the Accessibility of NTP Servers This command verifies the accessibility of NTP servers specified manually on your PX3TS and then shows the result. For instructions on specifying NTP servers via CLI, see Setting NTP Parameters (on page 605).
Page 629 Chapter 9: Using the Command Line Interface config:# security ipAccessControl ipv4 defaultPolicyIn <policy> Determine the default IPv4 firewall control policy for outbound traffic: config:# security ipAccessControl ipv4 defaultPolicyOut <policy> • IPv6 commands Enable or disable the IPv6 firewall control feature: config:# security ipAccessControl ipv6 enabled <option>...
Page 630 Chapter 9: Using the Command Line Interface Tip: You can combine both commands to modify all firewall control parameters at a time. See Multi-Command Syntax (on page 695). Managing Firewall Rules You can add, delete or modify firewall rules using the CLI commands. •...
Page 631 Chapter 9: Using the Command Line Interface config:# security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy> <insert> <rule_number> -- OR -- config:# security ipAccessControl ipv6 rule add <direction> <insert> <rule_number> <ip_mask> <policy> Variables: • <direction> is one of the options: in or out. Direction Description Inbound traffic.
Page 632 Chapter 9: Using the Command Line Interface Modifying a Firewall Rule Depending on what to modify in an existing rule, the command varies. • IPv4 commands Modify an IPv4 rule's IP address and/or subnet mask: config:# security ipAccessControl ipv4 rule modify <direction> <rule_number> ipMask <ip_mask>...
Page 633 Chapter 9: Using the Command Line Interface Direction Description 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.
Page 634 Chapter 9: Using the Command Line Interface Restricted Service Agreement The CLI command used to set the Restricted Service Agreement feature begins with security restrictedServiceAgreement, Enabling or Disabling the Restricted Service Agreement This command activates or deactivates the Restricted Service Agreement. config:# security restrictedServiceAgreement enabled <option>...
Page 635 Chapter 9: Using the Command Line Interface After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen. Do either of the following, or the login fails: • In the web interface, select the checkbox labeled "I understand and accept the restricted service agreement."...
Page 636 Chapter 9: Using the Command Line Interface Specifying the Agreement Contents This command allows you to create or modify contents of the Restricted Service Agreement. config:# security restrictedServiceAgreement bannerContent After performing the above command, do the following: Type the text comprising up to 10,000 ASCII characters when the CLI prompts you to enter the content.
Page 637 Chapter 9: Using the Command Line Interface Login Limitation The login limitation feature controls login-related limitations, such as password aging, simultaneous logins using the same user name, and the idle time permitted before forcing a user to log out. A login limitation command begins with security loginLimits. You can combine multiple commands to modify various login limitation parameters at a time.
Page 638 Chapter 9: Using the Command Line Interface 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.
Page 639 Chapter 9: Using the Command Line Interface 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.
Page 640 Chapter 9: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option> Variables: • <option> is one of the options: enable or disable. Option Description enable At least one lowercase character is required. disable No lowercase character is required. Uppercase Character Requirement This command determines whether a strong password includes at least a uppercase character.
Page 641 Chapter 9: Using the Command Line Interface Special Character Requirement This command determines whether a strong password includes at least a special character. config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option> Variables: • <option> is one of the options: enable or disable. Option Description enable At least one special character is required.
Page 642 Chapter 9: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 enabled <option> Determine the IPv4 role-based access control policy: config:# security roleBasedAccessControl ipv4 defaultPolicy <policy> • IPv6 commands Enable or disable the IPv6 role-based access control feature: config:# security roleBasedAccessControl ipv6 enabled <option> Determine the IPv6 role-based access control policy: config:# security roleBasedAccessControl ipv6 defaultPolicy <policy>...
Page 643 Chapter 9: Using the Command Line Interface Managing Role-Based Access Control Rules You can add, delete or modify role-based access control rules. • An IPv4 role-based access control command for managing rules begins with security roleBasedAccessControl ipv4 rule. • An IPv6 role-based access control command for managing rules begins with security roleBasedAccessControl ipv6 rule.
Page 644 Chapter 9: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role> <policy> <insert> <rule_number> Variables: • <start_ip> is the starting IP address. • <end_ip> is the ending IP address. • <role> is the role for which you want to create an access control rule. •...
Page 645 Chapter 9: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role <role> Modify an IPv4 rule's policy: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy <policy> Modify all contents of an existing IPv4 rule: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip>...
Page 646 Chapter 9: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> Variables: • <rule_number> is the number of the existing rule that you want to modify. • <start_ip> is the starting IP address. •...
Page 647 Chapter 9: Using the Command Line Interface 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...
Page 648 Chapter 9: Using the Command Line Interface Examples This section illustrates several security configuration examples. Example 1 - IPv4 Firewall Control Configuration The following command sets up two parameters of the IPv4 access control feature. config:# security ipAccessControl ipv4 enabled true defaultPolicyIn accept defaultPolicyOut accept Results: •...
Page 649: Outlet Configuration Commands
Chapter 9: Using the Command Line Interface config:# security userBlocking maximumNumberOfFailedLogins 5 blockTime 30 Results: • The maximum number of failed logins is set to 5. • The user blocking time is set to 30 minutes. Example 4 - Adding an IPv4 Role-based Access Control Rule The following command creates a newIPv4 role-based access control rule and specifies its location in the list.
Page 650 Chapter 9: 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: •...
Page 651: Outlet Group Configuration Commands
Chapter 9: 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: •...
Page 652 Chapter 9: Using the Command Line Interface • <members> is one or multiple member outlets' index numbers separated with commas. If the member outlets are consecutive outlets, you can type a hyphen between the initial and the final index number instead of using commas.
Page 653: Inlet Configuration Commands
Chapter 9: Using the Command Line Interface ▪ outletgroup modify 2 members 3-5,8,10 -- OR -- ▪ outletgroup modify 2 members 3,4,5,8,10 Powering On/Off/Cycle Outlet Groups This section applies to outlet-switching capable models only. You must perform this operation in the administrator mode. See Different CLI Modes and Prompts (on page 527).
Page 654: Overcurrent Protector Configuration Commands
Chapter 9: Using the Command Line Interface Changing the Inlet Name This command syntax names an inlet. config:# inlet <n> name "<name>" Variables: • <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always 1. The value is an integer between 1 and 50. •...
Page 655: User Configuration Commands
Chapter 9: Using the Command Line Interface Example - OCP Naming The command assigns the name "Email servers CB" to the overcurrent protector labeled 2. config:# ocp 2 name "Email servers CB" User Configuration Commands Most user configuration commands begin with user except for the password change command.
Page 656 Chapter 9: Using the Command Line Interface 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 695).
Page 657 Chapter 9: Using the Command Line Interface 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.
Page 658 Chapter 9: Using the Command Line Interface Option Description false Disables the specified user profile. Forcing a Password Change This command determines whether the password change is forced when a user logs in to the specified user profile next time. config:# user modify <name>...
Page 659 Chapter 9: Using the Command Line Interface config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3> Determine the authentication passphrase: config:# user modify <name> authenticationPassPhrase After performing the above command, PX3TS prompts you to enter the authentication passphrase. Determine whether the privacy passphrase is identical to the authentication passphrase: config:# user modify <name>...
Page 660 Chapter 9: Using the Command Line Interface Option Description disable Disables the SNMP v3 access permission for the specified user. • <option2> is one of the options: noAuthNoPriv, authNoPriv or authPriv. Option Description noAuthNoPriv No authentication and no privacy. authNoPriv Authentication and no privacy.
Page 661 Chapter 9: Using the Command Line Interface • An authentication or privacy passphrase is a string comprising 8 to 32 ASCII printable characters. Changing the Role(s) This command changes the role(s) of a specific user. config:# user modify <name> roles <roles> Variables: •...
Page 662 Chapter 9: Using the 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 644). Set the preferred temperature unit: config:# user modify <name> preferredTemperatureUnit <option1> Set the preferred length unit: config:# user modify <name>...
Page 663 Chapter 9: Using the Command Line Interface Specifying the SSH Public Key If the SSH key-based authentication is enabled, specify the SSH public key for each user profile using the following procedure. To specify or change the SSH public key for a specific user: Type the SSH public key command as shown below and press Enter.
Page 664 Chapter 9: Using the Command Line Interface 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.
Page 665 Chapter 9: Using the 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 641). Set the default temperature unit: config:# user defaultpreferences preferredTemperatureUnit <option1> Set the default length unit: config:# user defaultpreferences preferredLengthUnit <option2>...
Page 666 Chapter 9: Using the Command Line Interface Example 1 - Creating a User Profile The following command creates a new user profile and sets two parameters for the new user. config:# user create Mary enable admin Results: • A new user profile "Mary" is created. •...
Page 667: Role Configuration Commands
Chapter 9: Using the Command Line Interface Role Configuration Commands A role configuration command begins with role. Creating a Role This command creates a new role, with a list of semicolon-separated privileges assigned to the role. config:# role create <name> <privilege1>;<privilege2>;<privilege3>... If a specific privilege contains any arguments, that privilege should be followed by a colon and the argument(s).
Page 668 Chapter 9: Using the Command Line Interface Privilege Description changeDataTimeSettings Change Date/Time Settings changeExternalSensorsConfiguration Change Peripheral Device Configuration changeLhxConfiguration Change LHX/SHX Configuration changeModemConfiguration Change Modem Configuration changeNetworkSettings Change Network Settings changePassword Change Own Password changePduConfiguration Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration changeSecuritySettings...
Page 669 Chapter 9: Using the Command Line Interface • 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: •...
Page 670 Chapter 9: Using the Command Line Interface config:# role modify <name> addPrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Remove specific privileges from a role: config:# role modify <name> removePrivileges <privilege1>;<privilege2>;<privilege3>... If a specific privilege contains any arguments, add a colon and the argument(s) after that privilege. config:# role modify <name>...
Page 671: Authentication Commands
Chapter 9: Using the Command Line Interface 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).
Page 672 Chapter 9: Using the Command Line Interface Option Description radius Enable Radius authentication. • <option2> is one of the options: true or false. Option Description true Remote authentication is the first priority. The device will switch to local authentication when the remote authentication is not available.
Page 673 Chapter 9: Using the Command Line Interface config:# authentication ldap add <host> <port> <ldap_type> <security> <bind_type> <base_DN> <login_name_att> <user_entry_class> "Optional Parameters" Note: "Optional Parameters" refer to one or multiple parameters listed in the section Optional Parameters (on page 654). They are required only when your server settings need to specify these parameters.
Page 674 Chapter 9: Using the Command Line Interface • <bind_type> is one of the bind options: anonymouseBind, or authenticatedBind. Type Description anonymousBind Enable the anonymous Bind. Bind DN and password are NOT required. authenticatedBind Enable the Bind with authentication. Bind DN and password are required. •...
Page 675 Chapter 9: Using the Command Line Interface Parameters To configure verifyServerCertificate <verify_cert> Certificate verification setting ▪ After setting to true, the system will prompt you to upload a certificate. For details, see Illustrations of Adding LDAP Servers (on page 655). allowExpiredCertificate Whether to accept expired or not valid yet <allow_exp_cert>...
Page 676 Chapter 9: Using the Command Line Interface config:# authentication ldap add ac-ldap.raritan.com 389 activeDirectory none anonymousBind dc=raritan,dc=com sAMAccountName user adDomain raritan.com An LDAP server with a TLS certificate uploaded: Enter the CLI command with the following two TLS-related options set and/or added: ▪...
Page 677 Chapter 9: Using the Command Line Interface Modifying an Existing LDAP Server You can modify one or multiple parameters of an existing LDAP server, such as its IP address, TCP port number, Base DN and so on. Besides, you can also change the priority or sequence of existing LDAP servers in the server list.
Page 678 Chapter 9: Using the Command Line Interface Parameters Description Change the IP address or host name. host <host> ▪ <host> is the new IP address or host name. Change the TCP port number. port <port> ▪ <port> is the new TCP port number. Change the server type.
Page 679 Chapter 9: Using the Command Line Interface Parameters Description Re-upload a different certificate. certificate First add the "certificate" parameter to the command, and press Enter. b. The system prompts you for the input of the certificate. Type or copy the content of the certificate in the CLI and press Enter.
Page 680 Chapter 9: Using the Command Line Interface Removing an Existing LDAP Server This command removes an existing LDAP server from the server list. config:# authentication ldap delete <server_num> Variables: • <server_num> is the sequential number of the specified server in the LDAP server list.
Page 681 Chapter 9: Using the Command Line Interface Example: config:# authentication radius add 192.168.7.99 chap 1812 1813 10 3 Modifying an Existing Radius Server You can modify one or multiple parameters of an existing Radius server, or change the priority or sequence of existing servers in the server list. Change the IP address or host name: config:# authentication radius modify <server_num>...
Page 682 Chapter 9: Using the Command Line Interface config:# authentication radius modify <server_num> sortPositon <position> Tip: You can add more than one parameters to the command. For example, "authentication radius modify <server_num> host <host> authType <rds_type> authPort <auth_port> accountPort <acct_port> ...". Variables: •...
Page 683: Environmental Sensor Configuration Commands
Chapter 9: Using the Command Line Interface Environmental Sensor Configuration Commands An environmental sensor configuration command begins with externalsensor. You can configure the name and location parameters of an individual environmental sensor. Note: To configure an actuator, see Actuator Configuration Commands page 680).
Page 684 Chapter 9: Using the Command Line Interface Type Description smokeDetection The connected detector/switch is for detection of the smoke presence. waterDetection The connected detector/switch is for detection of the water presence. vibration The connected detector/switch is for detection of the vibration.
Page 685 Chapter 9: Using the Command Line Interface Setting the Z Coordinate This command specifies the Z coordinate of an environmental sensor. config:# externalsensor <n> zlabel "<coordinate>" Variables: • <n> is the ID number of the environmental sensor that you want to configure.
Page 686 Chapter 9: 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.
Page 687: Configuring Environmental Sensors' Default Thresholds
Chapter 9: 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.
Page 688 Chapter 9: Using the Command Line Interface config:# defaultThresholds <sensor type> hysteresis <hy_value> Set the Default Assertion Timeout for a specific sensor type: config:# defaultThresholds <sensor type> assertionTimeout <as_value> Variables: • <sensor type> is one of the following numeric sensor types: Sensor types Description absoluteHumidity...
Page 689: Sensor Threshold Configuration Commands
Chapter 9: Using the Command Line Interface Example - Default Upper Thresholds for Temperature It is assumed that your preferred measurement unit for temperature is set 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.
Page 690 Chapter 9: Using the Command Line Interface 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>...
Page 691 CLI is A, not mA. Sensor type Description Supported on PXC and peakCurrent Peak current sensor Legrand PDU only ▪ three-phase models als support pole-level peak current ▪ models with metered breakers also support...
Page 692 Chapter 9: Using the Command Line Interface Sensor type Description residualDCCurrent RCM DC current sensor - detects residual DC current only. Available only on PDUs with RCM Type B. Note: For information on RCM Type A and B sensors, see RCM Current Sensor. Commands for Outlet Sensors A sensor configuration command for outlets begins with sensor outlet.
Page 693 Chapter 9: Using the Command Line Interface config:# sensor outlet <n> <sensor type> assertionTimeout <as_value> Variables: • <n> is the number of the outlet that you want to configure. • <sensor type> is one of the following sensor types: Sensor type Description current Current sensor...
Page 694 Chapter 9: Using the Command Line Interface Commands for Overcurrent Protector Sensors A sensor configuration command for overcurrent protectors begins with sensor ocp. You can configure various overcurrent protector threshold settings at a time by combining multiple commands. See Multi-Command Syntax (on page 695).
Page 695 Chapter 9: Using the Command Line Interface • <option> is one of the options: enable, disable or a numeric value. Option Description enable Enables the specified threshold for the overcurrent protector sensor. Disables the specified threshold for the overcurrent disable protector sensor.
Page 696 Chapter 9: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> hysteresis <hy_value> Set the assertion timeout for an environmental sensor: config:# sensor externalsensor <n> <sensor type> assertionTimeout <as_value> Variables: • <n> is the ID number of the environmental sensor that you want to configure.
Page 697 Chapter 9: Using the Command Line Interface • <hy_value> is a numeric value that is assigned to the hysteresis for the specified environmental sensor. See "To De-assert" and Deassertion Hysteresis (on page 839). • <as_value> is a number in samples that is assigned to the assertion timeout for the specified environmental sensor.
Page 698 Chapter 9: 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 Description enable Enables the specified threshold for the inlet phase sync angle sensor. disable Disables the specified threshold for the inlet phase sync angle sensor.
Page 699 Chapter 9: 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.
Page 700: Actuator Configuration Commands
Chapter 9: Using the Command Line Interface Actuator Configuration Commands An actuator configuration command begins with actuator. You can configure the name and location parameters of an individual actuator. You can configure various parameters for one actuator at a time. See Multi-Command Syntax (on page 695).
Page 701: Server Reachability Configuration Commands
Chapter 9: Using the Command Line Interface • <description> is a string comprising up to 64 ASCII printable characters, and it must be enclosed in quotes when it contains spaces. Example - Actuator Naming The following command assigns the name "Door lock of cabinet 3" to the actuator whose ID number is 9.
Page 702 Chapter 9: Using the Command Line Interface • <succ_ping> is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200. • <fail_ping> is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to 100. •...
Page 703 Chapter 9: Using the Command Line Interface config:# serverReachability modify <n> pingMonitoringEnabled <option> Modify the number of successful pings for declaring "Reachable": config:# serverReachability modify <n> numberOfSuccessfulPingsToEnable <succ_number> Modify the number of unsuccessful pings for declaring "Unreachable": config:# serverReachability modify <n> numberOfUnsuccessfulPingsForFailure <fail_number>...
Page 704: Energywise Configuration Commands
Chapter 9: Using the Command Line Interface • <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. •...
Page 705 Chapter 9: Using the Command Line Interface Option Description false The Cisco EnergyWise feature is disabled. Specifying the EnergyWise Domain This command syntax specifies to which Cisco EnergyWise domain the PX3TS ® belongs. config:# energywise domain <name> Variables: • <name> is a string comprising up to 127 ASCII printable characters. Spaces and asterisks are NOT acceptable.
Page 706: Asset Management Commands
Chapter 9: Using the Command Line Interface Setting the Polling Interval This command syntax determines the polling interval at which the Cisco ® EnergyWise domain queries the PX3TS. config:# energywise polling <timing> Variables: • <timing> is an integer number in seconds. It ranges between 30 and 600 seconds.
Page 707 Chapter 9: Using the Command Line Interface 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.
Page 708 Chapter 9: Using the Command Line Interface Specifying the Rack Unit Numbering Mode This command syntax specifies the numbering mode of rack units on the asset strips connected to the PX3TS device. The numbering mode changes the rack unit numbers. config:# assetStrip <n>...
Page 709 Chapter 9: Using the Command Line Interface Specifying the Asset Strip Orientation This command syntax specifies the orientation of the asset strips connected to the 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.
Page 710 Chapter 9: Using the Command Line Interface Setting LED Colors for Disconnected Tags This command syntax sets the LED color for all rack units on the connected asset strip(s) to indicate the absence of a connected asset tag. config:# assetStrip <n> LEDColorForDisconnectedTags <color> Variables: •...
Page 711 Chapter 9: Using the Command Line Interface Setting the LED Operation Mode This command syntax determines whether a specific rack unit on the specified asset strip follows the global LED color settings. config:# rackUnit <n> <rack_unit> LEDOperationMode <mode> Variables: • <n>...
Page 712 Chapter 9: Using the Command Line Interface Setting an LED Color for a Rack Unit This command syntax sets the LED color for a specific rack unit on the specified asset strip. You need to set a rack unit's LED color only when the LED operation mode of this rack unit has been set to "manual."...
Page 713: Serial Port Configuration Commands
Chapter 9: Using the Command Line Interface Mode Description blinkSlow This mode has the LED blink slowly. blinkFast This mode has the LED blink quickly. 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.
Page 714 Chapter 9: Using the Command Line Interface Setting the Baud Rates The following commands set the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the 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.
Page 715: Multi-Command Syntax
Chapter 9: Using the Command Line Interface Option Description 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.
Page 716: Load Shedding Configuration Commands
Chapter 9: Using the Command Line Interface config:# sensor ocp 2 current upperCritical disable upperWarning 15 Results: • The Upper Critical threshold of the 2nd overcurrent protector's RMS current is disabled. • The Upper Warning threshold of the 2nd overcurrent protector's RMS current is set to 15A and enabled at the same time.
Page 717: Enabling Or Disabling Load Shedding
Chapter 9: 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.
Page 718: Power Control Operations
Chapter 9: Using the Command Line Interface Power Control Operations This section applies to outlet-switching capable models only. Outlets on the PX3TS 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.
Page 719: Turning Off The Outlet(S)
Chapter 9: 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 If you have configured outlet switching sequence and/or delay, PX3TS will prompt you with one more question: Should outlet sequence order and delays be used during switching?
Page 720: Power Cycling The Outlet(S)
Chapter 9: Using the Command Line Interface Option Description A range of Switches OFF multiple, consecutive outlets. outlets with a For example, to specify 6 consecutive outlets -- 3, 4, 5, hyphen in 6, 7, 8, type: between outlets 3-8. If you entered the command without "/y", a message appears, prompting you to confirm the operation.
Page 721: Canceling The Power-On Process
Chapter 9: Using the Command Line Interface Option Description A range of Power cycles multiple, consecutive outlets. outlets with a For example, to specify 6 consecutive outlets -- 3, 4, 5, hyphen in 6, 7, 8, type: between outlets 3-8. If you entered the command without "/y", a message appears, prompting you to confirm the operation.
Page 722: Actuator Control Operations
Chapter 9: Using the Command Line Interface Actuator Control Operations An actuator, which is connected to a dry contact signal channel of a Raritan sensor package, can control a mechanism or system. You can switch on or off that mechanism or system through the actuator control command in the CLI. Perform these commands in the administrator or user mode.
Page 723: Switching Off An Actuator
Chapter 9: Using the Command Line Interface 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>...
Page 724: Resetting The Px3Ts
Chapter 9: Using the Command Line Interface A message appears, indicating that the specified user was unblocked successfully. Resetting the PX3TS You can reset the PX3TS 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.
Page 725: Resetting To Factory Defaults
Chapter 9: Using the Command Line Interface To reset one outlet's active energy readings: reset activeEnergy outlet <outlet_n> -- OR -- reset activeEnergy outlet <outlet_n> /y To reset one outlet group's active energy readings: reset activeEnergy outletgroup <ID> -- OR -- reset activeEnergy outletgroup <ID>...
Page 726: Network Troubleshooting
Chapter 9: Using the Command Line Interface Network Troubleshooting The PX3TS provides 4 diagnostic commands for troubleshooting network problems: nslookup, netstat, ping, and traceroute. The diagnostic commands function as corresponding Linux commands and can get corresponding Linux outputs. Entering Diagnostic Mode Diagnostic commands function in the diagnostic mode only.
Page 727 Chapter 9: Using the Command Line Interface 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.
Page 728 Chapter 9: Using the Command Line Interface Testing the Network Connectivity This ping command sends the ICMP ECHO_REQUEST message to a network host for checking its network connectivity. If the output shows the host is responding properly, the network connectivity is good. If not, either the host is shut down or it is not being properly connected to the network.
Page 729: Retrieving Previous Commands
Chapter 9: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your PX3TS and a network host. diag> traceroute <host> <useICMP> Variables: • <host> is the name or IP address of the host you want to trace. •...
Page 730: Logging Out Of Cli
Chapter 9: Using the Command Line Interface Examples: • Example 1 (only one possible command): Type the first word and the first letter of the second word of the "reset factorydefaults" command -- that is, reset f. b. Then press Tab or Ctrl+i to complete the second word. •...
Page 731: Chapter 10 Using Scp Commands
Chapter 10 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 Firmware Update via SCP ................. 711 Bulk Configuration via SCP ................712 Backup and Restore via SCP ................
Page 732: Bulk Configuration Via Scp
Chapter 10: Using SCP Commands SCP example: scp pdu-px2-030410-44599.bin admin@192.168.87.50:/fwupdate Windows PSCP command: PSCP in Windows works in a similar way to the SCP. ▪ pscp <firmware file> <user name>@<device ip>:/fwupdate Bulk Configuration via SCP Like performing bulk configuration via the web interface, there are two steps with the bulk configuration using the SCP commands: Save a configuration from a source PX3TS.
Page 733: Backup And Restore Via Scp
Chapter 10: Using SCP Commands The system copies the configuration included in the file "bulk_config.txt" to another PX3TS, and displays the following message. Starting restore operation. The connection will be closed now. SCP examples: • Save operation: scp admin@192.168.87.50:/bulk_config.txt today_config.txt •...
Page 734: Downloading Diagnostic Data Via Scp
Chapter 10: Using SCP Commands ▪ <device ip> is the IP address or hostname of the PX3TS whose settings you want to back up. Type the user password when prompted. The system saves the settings from the PX3TS to a file named "backup_settings.txt."...
Page 735 Chapter 10: Using SCP Commands Scenario 1: Use the default SCP port and default filename ▪ SSH/SCP port is the default (22), and the accessed PX3TS is a standalone device. ▪ The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot (.) in the end of the SCP command as shown below.
Page 736: Uploading Or Downloading Raw Configuration Data
Chapter 10: Using SCP Commands ▪ If you specify a new filename in the command, such as Scenarios 3 or 4, the downloaded file is renamed accordingly. SCP example: scp admin@192.168.87.50:/diag-data.zip . Windows PSCP command: PSCP in Windows works in a similar way to the SCP. ▪...
Page 737 Chapter 10: Using SCP Commands Scenario 3: Specify a new filename but use the default SCP port ▪ SSH/SCP port is the default (22), and the accessed PX3TS is a standalone device. ▪ Renaming the raw configuration file is wanted. scp <user name>@<device ip>:/raw_config.txt <filename>...
Page 738 Chapter 10: Using SCP Commands Scenario 2: Only one PX3TS to configure, with a non-default SCP port ▪ SSH/SCP port is NOT the default (22), or the accessed PX3TS is a Port-Forwarding slave device. ▪ There is only one device to configure so a CSV file for device-specific settings is NOT needed. scp -P <port>...
Page 739: Keys That Cannot Be Uploaded
Chapter 10: Using SCP Commands ▪ If the second column contains each device's serial number, the parameter is then serial:2. ▪ If the seventh column contains each device's MAC address, the parameter is then mac:7. SCP examples: • Raw configuration download example -- scp admin@192.168.87.50:/raw_config.txt config.txt •...
Page 740 Chapter 10: Using SCP Commands Note that these configuration keys cannot be part of the configuration that you will upload to any PX3TS. That is, they should be either not available or they remain to be commented out in the configuration file you will upload.
Page 741: Appendix A Specifications
Appendix A Specifications In This Chapter Technical Specifications ..................721 Maximum Ambient Operating Temperature ............ 723 Serial RS-232 "RJ-45" Port Pinouts ..............723 Sensor RJ-45 Port Pinouts ................. 724 Feature RJ-45 Port Pinouts ................724 Expansion RJ-45 Port Pinouts ................725 Technical Specifications...
Page 742 Appendix A: Specifications See the label or nameplate on your PX3TS Rated voltage and current model 50/60Hz +/- 5Hz Rated frequency 0.60 to 1.00 (leading or lagging) Load power factor Rated current up to crest factor 3.5 Non-linear load 4-8 milliseconds Sense and transfer time None -- inlets may be any phase relationship Phase sync requirements...
Page 743: Maximum Ambient Operating Temperature
Appendix A: Specifications 10%-90% non-condensing Relative humidity 0 feet (0 m) to 8500 feet (2591 m) Operating altitude (above sea level) UL 60950-1 Compliance Different models use different fuse types. You Fuse types must use the fuses listed below or equivalent according to the rating of your models: ▪...
Page 744: Sensor Rj-45 Port Pinouts
Appendix A: Specifications RJ-45 Pin/signal definition Input Clear to send Sensor RJ-45 Port Pinouts RJ-45 Pin/signal definition Pin No. Signal Direction Description +12V ― Power (fuse protected) +12V ― Power (fuse protected) ― Signal Ground RS485_DP bi-directional Data Positive of the RS-485 RS485_DN bi-directional Data Negative of the RS-485...
Page 745: Expansion Rj-45 Port Pinouts
Appendix A: Specifications RJ-45 Pin/signal definition Pin No. Signal Direction Description Warning: Pin 3 is only intended for use with Raritan devices. Output Transmit Data (Data out) Input Receive Data (Data in) +12V ― Warning: Pin 6 is only intended for use with Raritan devices.
Page 746 Appendix A: Specifications...
Page 747: Appendix B Equipment Setup Worksheet
Appendix B Equipment Setup Worksheet PX3TS Series Model ____________ PX3TS Series Serial Number ____________ OUTLET 1 OUTLET 2 OUTLET 3 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER OUTLET 4 OUTLET 5 OUTLET 6 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER...
Page 748 Appendix B: Equipment Setup Worksheet OUTLET 7 OUTLET 8 OUTLET 9 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER OUTLET 10 OUTLET 11 OUTLET 12 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER OUTLET 13 OUTLET 14 OUTLET 15 MODEL MODEL MODEL...
Page 749 Appendix B: Equipment Setup Worksheet OUTLET 16 OUTLET 17 OUTLET 18 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER OUTLET 19 OUTLET 20 OUTLET 21 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER...
Page 750 Appendix B: Equipment Setup Worksheet OUTLET 22 OUTLET 23 OUTLET 24 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER Types of adapters _________________________________________________________ Types of cables _________________________________________________________ Name of software program _________________________________________________________...
Page 751: Appendix C Configuration Or Firmware Upgrade With A Usb Drive
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 •...
Page 752: System And Usb Requirements
Appendix C: Configuration or Firmware Upgrade with a USB Drive ▪ If no firmware upgrade task will be performed, a happy smiley is displayed after around 30 seconds. The happy smiley looks like one of the following, depending on your Raritan product.
Page 753: Configuration Files
Appendix C: Configuration or Firmware Upgrade with a USB Drive Configuration Files There are three types of configuration files. • fwupdate.cfg: This file MUST be always present for performing configuration or firmware upgrade tasks. See fwupdate.cfg (on page 734). • config.txt: This file is used for configuring device settings.
Page 754: Fwupdate.cfg
Appendix C: Configuration or Firmware Upgrade with a USB Drive fwupdate.cfg The configuration file, fwupdate.cfg, is an ASCII text file containing key-value pairs, one per line. Each value in the file must be separated by an equal sign (=), without any surrounding spaces.
Page 755 Appendix C: Configuration or Firmware Upgrade with a USB Drive 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.
Page 756 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. factory_reset •...
Page 757 Appendix C: Configuration or Firmware Upgrade with a USB Drive • The PX3TS device beeps after it finishes writing the diagnostic data to the USB drive. switch_outlets • This feature works on outlet-switching capable models only. • Switch on or off specific outlets. •...
Page 758: Config.txt
Appendix C: Configuration or Firmware Upgrade with a USB Drive • 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.
Page 759 Appendix C: Configuration or Firmware Upgrade with a USB Drive Note: Each value in the file must be separated by an equal sign (=), without any surrounding spaces. • Multi-line values are supported by using the Here Document Syntax with a user-chosen delimiter.
Page 760 Appendix C: Configuration or Firmware Upgrade with a USB Drive To rename the admin user: You can rename the admin user by adding the following configuration key: users[0].name=new admin name Example: users[0].name=May To encrypt any settings: You can encrypt the value of any setting in the config.txt. See Data Encryption in 'config.txt' (on page 743).
Page 761: Devices.csv
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 - devices.csv, to store unique data of each PX3TS device. This file must be: •...
Page 762: Creating Configuration Files Via Mass Deployment Utility
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.
Page 763: Data Encryption In 'Config.txt
Appendix C: Configuration or Firmware Upgrade with a USB Drive Data Encryption in 'config.txt' When intending to prevent people from identifying the values of any settings, you can encrypt them. Encrypted data still can be properly interpreted and performed by any PX3TS running firmware version 3.2.20 or later. Data encryption procedure: Open the "config.txt"...
Page 764: Firmware Upgrade Via Usb
Appendix C: Configuration or Firmware Upgrade with a USB Drive The CLI generates and shows the encrypted form of "private." In the "config.txt" file, make the following changes to the SNMP write community setting. Replace the word "private" with the encrypted value that CLI shows. b.
Page 765 Appendix C: Configuration or Firmware Upgrade with a USB Drive ▪ Sad smiley: Failed. Check the log file in the USB drive or contact Raritan Technical Support to look into the failure cause. The sad smiley looks like one of the following. For the first diagram, its background color will turn red.
Page 766: Appendix D Bulk Configuration Or Firmware Upgrade Via Dhcp/Tftp
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.
Page 767: Bulk Configuration/Upgrade Procedure
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure Any firmware downgrade using "fwupdate.cfg" is NOT supported by default. Only firmware upgrade is permitted with "fwupdate.cfg". A special parameter is required to permit firmware downgrade via "fwupdate.cfg". fwupdate.cfg (on page 734).
Page 768: Tftp Requirements
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP TFTP Requirements To perform bulk configuration or firmware upgrade successfully, your TFTP server must meet the following requirements: • The server is able to work with both IPv4 and IPv6. In Linux, remove any IPv4 or IPv6 flags from /etc/xinetd.d/tftp. Note: DHCP will execute the "fwupdate.cfg"...
Page 769 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Click Add to add a new vendor class. Specify a unique name for this vendor class and type the binary codes of "Raritan PDU 1.0" in the New Class dialog. The vendor class is named "Raritan PDU"...
Page 770 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Right-click the IPv4 node in DHCP to select Set Predefined Options. b. Select DHCP Standard Options in the "Option class" field, and Vendor Class Identifier in the "Option name" field. Leave the String field blank. Add three options to the new vendor class "Raritan PDU"...
Page 771 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Select Raritan PDU in the "Option class" field. b. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.
Page 772 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 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.
Page 773 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The policy is named "PDU" in this illustration. Click Add to add a new condition.
Page 774 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. Click Next.
Page 775 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 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.
Page 776 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 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.
Page 777 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. 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.
Page 778: Dhcp Ipv6 Configuration In Windows
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.
Page 779 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Right-click the IPv6 node in DHCP to select Define Vendor Classes. b. Click Add to add a new vendor class. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)"...
Page 780 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Add three options to the "Raritan PDU 1.0" vendor class. Right-click the IPv6 node in DHCP to select Set Predefined Options.
Page 781 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select Raritan PDU 1.0 in the "Option class" field. 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.
Page 782 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. 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.
Page 783 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 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.
Page 784 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. 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.
Page 785: Dhcp Ipv4 Configuration In Linux
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.
Page 786 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. Set the following three sub-options in the "vendor-encapsulated-options" (option 43). ▪...
Page 787: Dhcp Ipv6 Configuration In Linux
Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP IPv4 illustration example in dhcpd.conf: DHCP IPv6 Configuration in Linux Modify the "dhcpd6.conf" file for IPv6 settings when your DHCP server is running Linux. Required Linux IPv6 settings in DHCP: Locate and open the "dhcpd6.conf" file of the DHCP server. The PX3TS will provide the following values to the "vendor-class"...
Page 788 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.
Page 789: Appendix E Raw Configuration Upload And Download
Appendix E Raw Configuration Upload and Download You can modify any existing "config.txt", and then upload it to a specific PX3TS for modifying part or all of its settings. There are two ways to get one "config.txt": • You create this file by yourself, either using or not using the Mass Deployment Utility.
Page 790: Download Via Curl
Appendix E: Raw Configuration Upload and Download Parameter Description <user> Any user name that has the Administrator Privileges. <password> The password of the specified user name. <device IP> Hostname or IP address of the PX3TS whose raw configuration you want to download. ▪...
Page 791: Uploading Raw Configuration
Appendix E: Raw Configuration Upload and Download Parameter Description <password> The password of the specified user name. <device IP> Hostname or IP address of the PX3TS whose raw configuration you want to download. When the download is complete, a line indicates 100 in the first % column. Go to the directory where you perform the curl command to find the "config.txt"...
Page 792: Upload Via Curl
Appendix E: Raw Configuration Upload and Download Upload via Curl If curl is available on your computer, you can upload the raw configuration to PX3TS with the curl command. There are two scenarios with the curl upload methods. • When there are NO device-specific settings involved, you upload the configuration file only, regardless of the number of PX3TS devices to update.
Page 793: Curl Upload Return Codes
Appendix E: Raw Configuration Upload and Download Parameter Description <user>, Refer to the above table for explanation. ▪ For device-specific settings in the <config <password>, file>, refer each device-specific configuration <device IP>, key to a specific column in the <dev_list <config file>.
Page 794 Appendix E: Raw Configuration Upload and Download Code Description An internal error occurred. A parameter error occurred. A raw configuration update operation is already running. The file is too large. Invalid raw configuration file provided. Invalid device list file or match provided. Device list file required but missing.
Page 795: Appendix F Resetting To Factory Defaults
Appendix F 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.
Page 796: Using The Cli Command
Appendix F: Resetting to Factory Defaults Note: PuTTY is a free program you can download from the Internet. See PuTTY's documentation for details on configuration. Using the CLI Command The Command Line Interface (CLI) provides a reset command for restoring the PX3TS to factory defaults.
Page 797: Appendix Gldap Configuration Illustration
Appendix G LDAP Configuration Illustration This section provides an LDAP example for illustrating the configuration procedure using Microsoft Active Directory (AD). To configure LDAP ® authentication, four main steps are required: Determine user accounts and roles (groups) intended for the PX3TS b.
Page 798: Step B. Configure User Groups On The Ad Server
Appendix G: 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: •...
Page 799: Step C. Configure Ldap Authentication On The Px3Ts
Appendix G: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the PX3TS You must enable and set up LDAP authentication properly on the PX3TS to use external authentication. In the illustration, we assume: • The DNS server settings have been configured properly. See Wired Network Settings (on page 311) and...
Page 800 Appendix G: LDAP Configuration Illustration Field/setting Do this... Ensure the field is set to sAMAccountName because the LDAP server is Login Name Attribute Microsoft Active Directory. Ensure the field is set to user because the LDAP server is Microsoft Active User entry object class Directory.
Page 801 Appendix G: LDAP Configuration Illustration Click Add Server.The LDAP server is saved. In the Authentication Type field, select LDAP. Click Save. The LDAP authentication is activated.
Page 802: Step D. Configure Roles On The Px3Ts
Appendix G: LDAP Configuration Illustration 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).
Page 803 Appendix G: LDAP Configuration Illustration 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. The PX_User role is created. Keep the Roles page open to create the PX_Admin role.
Page 804 Appendix G: LDAP Configuration Illustration In the Privileges list, select Administrator Privileges. The Administrator Privileges allows users to configure or change all PX3TS settings. d. Click Save. The PX_Admin role is created.
Page 805: Appendix H Updating The Ldap Schema
Appendix H Updating the LDAP Schema In This Chapter Returning User Group Information ..............785 Setting the Registry to Permit Write Operations to the Schema ..... 786 Creating a New Attribute .................. 786 Adding Attributes to the Class ................787 Updating the Schema Cache ................
Page 806: Setting The Registry To Permit Write Operations To The Schema
Appendix H: 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: Right-click the Active Directory Schema root node in the left pane of the ®...
Page 807: Adding Attributes To The Class
Appendix H: Updating the LDAP Schema Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears. Type rciusergroup in the Common Name field. Type rciusergroup in the LDAP Display Name field. Type 1.3.6.1.4.1.13742.50 in the Unique x5000 Object ID field.
Page 808 Appendix H: Updating the LDAP Schema Scroll to the user class in the right pane and right-click it. Choose Properties from the menu. The user Properties dialog appears. Click the Attributes tab to open it. Click Add. Choose rciusergroup from the Select Schema Object list.
Page 809: Updating The Schema Cache
Appendix H: Updating the LDAP Schema Click OK in the Select Schema Object dialog. Click OK in the User Properties dialog. Updating the Schema Cache To update the schema cache: Right-click Active Directory Schema in the left pane of the window and ®...
Page 810 Appendix H: Updating the LDAP Schema Go to the directory where the support tools were installed. Run adsiedit.msc. The ADSI Edit window opens. Open the Domain. In the left pane of the window, select the CN=Users folder.
Page 811 Appendix H: Updating the LDAP Schema Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list.
Page 812: Appendix I Radius Configuration Illustration
Appendix I RADIUS Configuration Illustration This section provides illustrations for configuring RADIUS authentication. One illustration is based on the Microsoft Network Policy Server (NPS), and the ® other is based on a FreeRADIUS server. The following steps are required for any RADIUS authentication: Configure RADIUS authentication on the PX3TS.
Page 813 Appendix I: RADIUS Configuration Illustration b. On the NPS, configure Connection Request Policies and the standard attribute. See Step B: Configure Connection Policies and Standard Attributes (on page 797). Some configuration associated with Microsoft Active Directory (AD) is also required for RADIUS authentication. See AD-Related Configuration (on page 824).
Page 814 Appendix I: RADIUS Configuration Illustration 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.
Page 815 Appendix I: RADIUS Configuration Illustration Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. Do the following to add your PX3TS to NPS: Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 816 Appendix I: RADIUS Configuration Illustration 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. Click OK.
Page 817 Appendix I: 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) •...
Page 818 Appendix I: RADIUS Configuration Illustration Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. Type a descriptive name for identifying this policy in the "Policy name" field.
Page 819 Appendix I: RADIUS Configuration Illustration ▪ You can leave the "Type of network access server" field to the default -- Unspecified.
Page 820 Appendix I: RADIUS Configuration Illustration Click Next to show the "Specify Conditions" screen. Click Add. The "Select condition" dialog appears. Click Add.
Page 821 Appendix I: RADIUS Configuration Illustration The NAS IPv4 Address dialog appears. Type the PX3TS IP address -- 192.168.56.29, and click OK. Click Next in the New Connection Request Policy dialog. Select "Authenticate requests on this server" because a local NPS server is used in this example.
Page 822 Appendix I: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 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...
Page 823 Appendix I: RADIUS Configuration Illustration Note: If your PX3TS uses PAP, then select "PAP."...
Page 824 Appendix I: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
Page 825 Appendix I: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
Page 826 Appendix I: RADIUS Configuration Illustration 12. In the Attribute Information dialog, click Add. 13. Select String, type Raritan:G{Admin} in the text box, and then click OK.
Page 827 Appendix I: 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.
Page 828 Appendix I: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
Page 829 Appendix I: RADIUS Configuration Illustration 15. Click Next to continue.
Page 830: Freeradius Standard Attribute Illustration
Appendix I: RADIUS Configuration Illustration 16. A summary showing connection request policy settings is displayed. Click Finish to close the dialog. FreeRADIUS Standard Attribute Illustration With standard attributes, NO dictionary files are required. You simply add all user data, including user names, passwords, and roles, in the following FreeRADIUS path.
Page 831: Vendor-Specific Attributes
Appendix I: 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 •...
Page 832 Appendix I: RADIUS Configuration Illustration Step A: Add Your PX3TS as a RADIUS Client The RADIUS implementation on the 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: •...
Page 833 Appendix I: RADIUS Configuration Illustration 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.
Page 834 Appendix I: RADIUS Configuration Illustration Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. Do the following to add your PX3TS to NPS: Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 835 Appendix I: RADIUS Configuration Illustration 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. Click OK.
Page 836 Appendix I: 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) •...
Page 837 Appendix I: RADIUS Configuration Illustration Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. Type a descriptive name for identifying this policy in the "Policy name" field.
Page 838 Appendix I: RADIUS Configuration Illustration ▪ You can leave the "Type of network access server" field to the default -- Unspecified.
Page 839 Appendix I: RADIUS Configuration Illustration Click Next to show the "Specify Conditions" screen. Click Add. The "Select condition" dialog appears. Click Add.
Page 840 Appendix I: RADIUS Configuration Illustration The NAS IPv4 Address dialog appears. Type the PX3TS IP address -- 192.168.56.29, and click OK. Click Next in the New Connection Request Policy dialog. Select "Authenticate requests on this server" because a local NPS server is used in this example.
Page 841 Appendix I: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 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...
Page 842 Appendix I: RADIUS Configuration Illustration Note: If your PX3TS uses PAP, then select "PAP." 10. Select Vendor Specific to the left of the dialog, and click Add. The Add Vendor Specific Attribute dialog appears. 11. Select Custom in the Vendor field, and click Add. The Attribute Information dialog appears.
Page 843: Freeradius Vsa Illustration
Appendix I: 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. Use a dictionary to define the Raritan vendor-specific attribute b.
Page 844: Ad-Related Configuration
Appendix I: 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: Go to this location: /etc/raddb/users. 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 (").
Page 845 Appendix I: RADIUS Configuration Illustration Right-click NPS (Local) and select "Register server in Active Directory." Click OK, and then OK again. To grant PX3TS users remote access permission: Open Active Directory Users and Computers. Open the properties dialog of the user whom you want to grant the access permission.
Page 846 Appendix I: RADIUS Configuration Illustration Click the Dial-in tab and select the "Allow access" checkbox. To enable reversible encryption for CHAP authentication: Open Active Directory Users and Computers. Open the properties dialog of the user that you want to configure.
Page 847 Appendix I: RADIUS Configuration Illustration Click the Account tab and select the "Store password using reversible encryption" checkbox.
Page 848: Appendix J Additional Px3Ts Information
Appendix J Additional PX3TS Information In This Chapter SecureLock™ Outlets and Cords ............... 828 RJ45-to-DB9 Cable Requirements for Modem Connections......830 Reserving IP Addresses in DHCP Servers ............830 Sensor Threshold Settings ................834 Default Voltage and Current Thresholds ............842 Altitude Correction Factors ................
Page 849 Appendix J: 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 ™...
Page 850: Rj45-To-Db9 Cable Requirements For Modem Connections
Appendix J: Additional PX3TS Information RJ45-to-DB9 Cable Requirements for Modem Connections An RJ45-to-DB9 adapter/cable is required for connecting a modem to the PX3TS device. A third party RJ45-to-DB9 adapter/cable needs to meet the following requirements. • RJ-45 to "DB9 male" •...
Page 851: Reserving Ip In Windows
Appendix J: Additional PX3TS Information Interface Client identifier ETH2 serial number plus the uppercase suffix "-ETH2" WIRELESS serial number plus the uppercase suffix "-WIRELESS" BRIDGE serial number You can reserve the IP addresses of more than one interfaces in the DHCP server if preferred.
Page 852: Reserving Ip In Linux
Appendix J: Additional PX3TS Information Field Data entered IP address The IP address you want to reserve. MAC address The following ASCII codes. 50 45 47 31 41 30 30 30 30 33 Other fields Configure as needed. 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): •...
Page 853 Appendix J: Additional PX3TS Information Interface Client identifier conversion ETH1 PEG1A00003 = 50 45 47 31 41 30 30 30 30 33 ETH2 PEG1A00003-ETH2 = 50 45 47 31 41 30 30 30 30 33 2D 45 54 48 32 ▪...
Page 854: Sensor Threshold Settings
Appendix J: Additional PX3TS Information Sensor Threshold Settings This section explains the thresholds settings for a numeric sensor. Thresholds and Sensor States A numeric sensor has four thresholds: Lower Critical, Lower Warning, Upper Warning and Upper Critical. The threshold settings determine how many sensor states are available for a certain sensor and the range of each sensor state.
Page 855 Appendix J: 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:...
Page 856 Appendix J: 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.
Page 857: To Assert" And Assertion Timeout
Appendix J: 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.
Page 858 Appendix J: Additional PX3TS Information In the threshold settings, the Assertion Timeout field postpones the "assertion" action. It determines how long a sensor must remain in the "worse" new state before the 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.
Page 859: To De-Assert" And Deassertion Hysteresis
Appendix J: 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.
Page 860 Appendix J: Additional PX3TS Information...
Page 861 Appendix J: 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.
Page 862: Default Voltage And Current Thresholds
Appendix J: 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"...
Page 863 Appendix J: Additional PX3TS Information Multi-phase inlets or outlets: • Line-Line RMS voltage: Threshold Default value Lower critical -6% of minimum rating Lower warning -3% of minimum rating Upper warning +3% of maximum rating Upper critical +6% of maximum rating Hysteresis •...
Page 864: Altitude Correction Factors
Appendix J: Additional PX3TS Information Total residual current: Threshold Default value Upper critical 30mA Hysteresis 15mA Altitude Correction Factors If a Raritan differential air pressure sensor is attached to your device, 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.
Page 865: Ways To Probe Existing User Profiles
Appendix J: Additional PX3TS Information 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. •...
Page 866: Possible Root Causes
Appendix J: Additional PX3TS Information 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 (on page 23).
Page 867 Appendix J: Additional PX3TS Information Symptom Probable cause • One of the following issues occurs on the master device: Failure to access a slave device ▪ Network connection is lost. ▪ Power is lost. ▪ The Ethernet or wireless interface is disabled. •...
Page 868: Slave Device Events In The Log
Appendix J: Additional PX3TS Information 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 The Ping Tool (on page 849) and Slave Device Events in the Log...
Page 869: The Ping Tool
Appendix J: Additional PX3TS Information Messages for the USB-cascading chain: 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.
Page 870: Installing The Usb-To-Serial Driver (Optional)
Appendix J: Additional PX3TS Information 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/).
Page 871: Initial Network Configuration Via Cli
Appendix J: Additional PX3TS Information 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"...
Page 872 Appendix J: Additional PX3TS Information ▪ To change it, follow onscreen instructions to type your new password. ▪ To ignore it, simply press Enter. The # prompt appears. Type config and press Enter. To configure network settings, type appropriate commands and press Enter.
Page 873 Appendix J: Additional PX3TS Information • Static IP configuration: To set Use this command network <ipvX> interface <ETH> Static IPv4 or address <ip address> IPv6 address <ip address> = static IP address, with a syntax similar to the example below. ▪...
Page 874 Appendix J: Additional PX3TS Information To set or Use this command enable network ethernet <ETH> EAP identity eapIdentity <identity> <identity> = your user name for EAP authentication network ethernet <ETH> EAP TLS client eapClientCertificate certificate When prompted to enter the client certificate, open the certificate with a text editor, copy and paste the content into the communications program.
Page 875 Appendix J: Additional PX3TS Information 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 network ethernet <ETH>...
Page 876 Appendix J: Additional PX3TS Information To set or Use this command enable network wireless authMethod Wireless <method> authentication method <method> = psk or eap network wireless PSK <psk> <psk> = PSK string network wireless Wireless EAP eapOuterAuthentication outer <outer_auth> authentication <outer_auth>...
Page 877 Appendix J: Additional PX3TS Information To set or Use this command enable network wireless Wireless EAP eapCACertificate CA certificate When prompted to enter the CA certificate, open the certificate with a text editor, copy and paste the content into the communications program. network wireless Radius eapAuthServerName <FQDN>...
Page 878: Device-Specific Settings
Appendix J: Additional PX3TS Information • Wireless IPv4 / IPv6 settings: Commands for wireless IP settings are identical to those for wired networking. Just replace the variable <ETH> with the word 'wireless'. The following illustrates a few examples. To set or Use this command enable network ipv4 interface WIRELESS...
Page 879: Tls Certificate Chain
Appendix J: Additional PX3TS Information TLS Certificate Chain A TLS server sends out a certificate to any client attempting to connect to it. The receiver determines whether a TLS server can be trusted by verifying that server's certificate, using the certificate (chain) stored on the receiver. Therefore, to successfully connect to a TLS server, you must upload a valid certificate or (partial) certificate chain to the receiver.
Page 880 Appendix J: Additional PX3TS Information • Certificate A. The self-signed certificate issued by Issuer A. Issuer A is a root CA. The above three certificates form a certificate path, which is called the "certificate chain". Each certificate in the chain is the issuer certificate of the certificate that follows it.
Page 881 Appendix J: Additional PX3TS Information Warning: The certificate (chain) uploaded to the receiver must always contain the ROOT certificate even though the TLS server provides the root certificate. When uploading a (partial) chain onto the PX3TS, it means you trust each certificate in the chain to certify the authenticity of certificates a server sends to PX3TS.
Page 882: Illustration - Gmail Smtp Certificate Chain
Appendix J: Additional PX3TS Information It is NOT recommended to upload the server certificate to the receiver except when it is a self-signed certificate. Using self-signed server certificates is also not recommended and may not even work in all cases. Order of the chain in the certificate file: The order of a certificate chain's content in the certificate file uploaded to the receiver must look like the following.
Page 883 Appendix J: Additional PX3TS Information Information that shows the certificates the SMTP server has is displayed. Certificate chain 0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com i:/C=US/O=Google Inc/CN=Google Internet Authority G2 -----BEGIN CERTIFICATE----- MIIEdjCCA16gAwIBAgIIbzO9vIL2OXcwDQYJKoZIhvcNAQELBQAwSTELMAkGA1UE YHKKJH96sSNC+6dLpOOoRritL5z+jn2WFLcQkL2mRoWQi6pYTzPyXB4D -----END CERTIFICATE----- 1 s:/C=US/O=Google Inc/CN=Google Internet Authority G2 i:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA -----BEGIN CERTIFICATE----- MIIEKDCCAxCgAwIBAgIQAQAhJYiw+lmnd+8Fe2Yn3zANBgkqhkiG9w0BAQsFADBC MqO5tzHpCvX2HzLc...
Page 884 Appendix J: Additional PX3TS Information ▪ Google Internet Authority G2 ▪ GeoTrust Global CA ▪ Equifax Secure Certificate Authority ▪ Each certificate's content is located between the line of "BEGIN CERTIFICATE" and the line of "END CERTIFICATE". ▪ The topmost certificate is the server certificate. The section titled "Server certificate"...
Page 885: Browsing Through The Online Help
Appendix J: Additional PX3TS Information Note: If your SMTP server requires the upload of a certificate file comprising multiple certificates, make sure the order of these certificates is correct in the file. See What is a Certificate Chain (on page 859). IMPORTANT NOTE: If your SMTP server provides a full certificate chain, you should be suspicious whether any attacker fakes the certificate chain and doubt whether the root...
Page 886 Appendix J: Additional PX3TS Information To have the left pane show the list of topics, click the Contents tab at the bottom. To show the Index page, click the Index tab. To email any URL link to the currently selected topic to any person, click the "Email this page"...
Page 887: Appendix K Integration
Appendix K Integration The PX3TS can work with certain Raritan or third-party products to provide diverse power solutions. In This Chapter Dominion KX II / III Configuration ..............867 Dominion KSX II, SX or SX II Configuration ............872 Power IQ Configuration ..................877 dcTrack......................
Page 888 Appendix K: Integration Connecting a PX PDU Raritan PX series rack PDUs (power strips) are connected to the Dominion device using the D2CIM-PWR CIM. To connect the rack PDU: Connect the male RJ-45 of the D2CIM-PWR to the following female RJ-45 connector of the rack PDU.
Page 889 Appendix K: Integration D2CIM-PWR to rack PDU connection D2CIM-PWR to KX III target device port via Cat5 cable Naming the Rack PDU (Port Page for Power Strips) Note: PX rack PDUs (power strips) can be named in the PX as well as in the KX III.
Page 890 Appendix K: Integration Click OK.
Page 891: Turning Outlets On/Off And Cycling Power
Appendix K: 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.
Page 892: Dominion Ksx Ii, Sx Or Sx Ii Configuration
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.
Page 893: Dominion Sx And Sx Ii
Appendix K: Integration Attach an AC power cord to the target server and an available rack PDU outlet. Connect the rack PDU to an AC power source. 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.
Page 894 Appendix K: Integration Dominion SX II The way to use Dominion SX II to configure and control a Raritan PDU is similar to using Dominion KX III, but the connection method is different from KX III. Note: If using a CSCSPCS-1 cable for the connection, it must be "Rev.0C". If using a CSCSPCS-10 cable, it must be "Rev.0D".
Page 895 Appendix K: Integration Dominion SX Configuring a PX3TS on Dominion SX Choose Setup > Power Strip Configuration. Click Add. The Power Strip Configuration screen appears. Type a name and description in the Name and Description fields. Select the number of outlets from the Number of Outlets drop-down menu.
Page 896 Appendix K: Integration Power Control Choose Power Control > Power Strip Power Control. The Outlet Control screen appears. Check the box of outlet number you wish to control, and click On/Off buttons to power on/off the selected outlet(s). A confirmation message appears, indicating successful operation.
Page 897: Power Iq Configuration
Appendix K: Integration Checking Power Strip Status Choose Power Control > Power Strip Status. 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.
Page 898: Dctrack
Appendix K: 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.
Page 899: Asset Management Strips And Dctrack
Appendix K: 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...
Page 901: Index
Index Asset Strip Management • 686 Asset Strip Settings • 553 Assets • 144, 154 A Note about Enabling Thresholds • 523 Associating Outlets with Target Devices • 871 A Note about Firmware Upgrade Time • 478 Authentication Commands • 651 A Note about Infinite Loop •...
Page 902 Index Cascading Multiple PX3TS Devices for Sharing Commands for Transfer Switch Sensors • 677 Ethernet Connectivity • 13, 16, 27, 313, 328, Common Network Settings • 310, 313 config.txt • 26, 716, 718, 733, 735, 738, 769, 772, Cascading Troubleshooting • 28, 336, 845 Change Load Shedding State •...
Page 903 Index Connecting Composite Asset Strips (AMS-Mx-Z) • Data Encryption in 'config.txt' • 738, 740, 743 Data Push Format • 438, 439 Connecting External Equipment (Optional) • 41, Date and Time Settings • 540 dcTrack • 878 Connecting Power and Equipment • 13 dcTrack Overview •...
Page 904 Index Download via Web Browsers • 769 Enabling the Restricted Service Agreement • 170, Downloading Diagnostic Data via SCP • 714 309, 348, 369 Downloading Diagnostic Information • 465, 489 EnergyWise Configuration Commands • 684 Downloading Raw Configuration • 769 EnergyWise Settings •...
Page 905 Index Example 1 - Upper Critical Threshold for a Firmware Update via SCP • 475, 711 Temperature Sensor • 679 Firmware Upgrade via USB • 475, 732, 744 Example 1 - Wireless Networking Mode • 603 Forcing a Password Change • 638 Example 2 •...
Page 906 Index Initial Installation and Configuration • 13 Initial Network Configuration via CLI • 17, 24, 25, 775, 776, 851 MAC Address • 132 Initialization Delay Use Cases • 208, 213 Main Menu • 140, 143 Inlet and Outlet Power Connections • 12 Maintenance •...
Page 907 Index Monitoring Server Accessibility • 309, 400, 447, Overcurrent Protector Sensor Threshold Information • 546 Mounting a PX3TS Device • 9 Overcurrent Protectors for Outlets • 130, 164, 167 Multi-Command Syntax • 566, 567, 610, 617, 618, Overview of the Cascading Modes • 328, 330 619, 622, 632, 636, 637, 638, 641, 644, 667, 669, Overview of the LCD Display •...
Page 908 Index Power-Sharing Restrictions and Connection • 36, Replacing a Fuse on 2U Models • 166 Request LHX/SHX Maximum Cooling • 396, 403 Preparing the Installation Site • 7 Reserving IP Addresses in DHCP Servers • 830, 831, Product Models • 1 Push Out Sensor Readings •...
Page 909 Index Send Sensor Report • 307, 396, 406, 422 Setting the Baud Rates • 694 Send Sensor Report Example • 406, 418, 419 Setting the BSSID • 593 Send SMS Message • 396, 408, 425 Setting the Cascading Mode • 6, 16, 27, 28, 29, 31, Send Snapshots via Email •...
Page 910 Index Setting Thresholds for Total Active Energy or Step B Power • 211, 215 Configure Connection Policies and Standard Setting Up a TLS Certificate • 309, 348, 355 Attributes • 793, 797 Setting Up External Authentication • 309, 348, 360, Configure Connection Policies and Vendor-Specific Attributes •...
Page 911 Index Transfer Timing Statistics • 531 Viewing or Clearing the Local Event Log • 199, 342, Turning Off the Outlet(s) • 699 360, 415, 464, 473 Turning On the Outlet(s) • 698 Visiting Other Pages from Current Group • 247 Turning Outlets On/Off and Cycling Power •...

LEGRAND Raritan PX3TS User Manual

In this Chapter

Chapter 1 Introduction

Chapter 2 Rackmount, Inlet and Outlet Connections

Chapter 3 Initial Installation and Configuration

Chapter 4 Connecting External Equipment (Optional)

Chapter 5 PDU Linking

Chapter 6 Using the PX3TS

Chapter 7 Using the Web Interface

Chapter 8 Using SNMP

Chapter 9 Using the Command Line Interface

Quick Links

Troubleshooting

Related Manuals for LEGRAND Raritan PX3TS

Summary of Contents for LEGRAND Raritan PX3TS