Download Print this page

Raritan PX3-1000 series User Manual

Px3 series

Hide thumbs Also See for PX3-1000 series:

User manual (648 pages)

Table Of Contents

Table of Contents

Advertisement

Quick Links

Download this manual

PX3-1000/2000 Series

User Guide

Xerus

Firmware v3.3.10

™

Copyright © 2017 Raritan, Inc.

PX3-1000-1B-v3.3.10-E

March 2017

255-80-0034-00

Table of Contents

Advertisement

Table of Contents

Need help?

Need help?

Do you have a question about the PX3-1000 series and is the answer not in the manual?

Questions and answers

Summary of Contents for Raritan PX3-1000 series

Page 1 PX3-1000/2000 Series User Guide Xerus Firmware v3.3.10 ™ Copyright © 2017 Raritan, Inc. PX3-1000-1B-v3.3.10-E March 2017 255-80-0034-00...
Page 2 60950-1 or equivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury and death. WARNING! Do not use a Raritan product containing outlet relays to power large inductive loads such as motors or compressors. Attempting to power a large inductive load may result in damage to the relay.
Page 3: Safety Instructions
Safety Instructions 1. Installation of this product should only be performed by a person who has knowledge and experience with electric power. 2. Make sure the line cord is disconnected from power before physically mounting or moving the location of this product. 3.
Page 4 Raritan, Inc. © Copyright 2017 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.
Page 6: Table Of Contents
Contents Safety Guidelines Safety Instructions Applicable Models xvii What's New in the PX3 User Guide Chapter 1 Introduction Product Models..........................1 Package Contents..........................1 Zero U Products ........................2 1U Products..........................2 ...
Page 7 Contents Installing Cable Retention Clips on the Inlet (Optional) ..............18 Installing Cable Retention Clips on Outlets (Optional) ..............19 Locking Outlets and Cords ......................20 SecureLock™ Outlets and Cords..................21 Button-Type Locking Outlets ....................22 Chapter 3 Initial Installation and Configuration ...
Page 8 Contents Connecting a Logitech Webcam..................... 81 Connecting a GSM Modem ......................82 Connecting an Analog Modem ....................... 83 Connecting an External Beeper ..................... 83 Connecting a Schroff LHX/SHX Heat Exchanger ................84 Chapter 5 Introduction to PDU Components ...
Page 9 Contents Inrush Current and Inrush Guard Delay................151 Z Coordinate Format......................152 How the Automatic Management Function Works............152 Time Units .......................... 153 Setting Thresholds for Total Active Energy or Power ............153 +12V Power Supply Sensor (for iX7™ Only) ............... 154 ...
Page 10 Contents Front Panel Settings ......................324 Configuring the Serial Port....................325 Lua Scripts ......................... 327 Miscellaneous ........................332 Maintenance ..........................333 Device Information......................334 Viewing Connected Users ....................338 Viewing or Clearing the Local Event Log................339 ...
Page 11 Contents Outlet Information......................375 Inlet Information ........................ 376 Overcurrent Protector Information ................... 377 Date and Time Settings...................... 378 Default Measurement Units....................378 Environmental Sensor Information ................... 379 Environmental Sensor Package Information ..............380 ...
Page 12 Contents User Configuration Commands ..................467 Role Configuration Commands..................481 Environmental Sensor Configuration Commands ............486 Configuring Environmental Sensors' Default Thresholds ..........491 Sensor Threshold Configuration Commands..............493 Actuator Configuration Commands................... 504 Server Reachability Configuration Commands ..............505 ...
Page 13 Contents Retrieving Previous Commands....................533 Automatically Completing a Command ..................533 Logging out of CLI......................... 534 Chapter 9 Using SCP Commands Firmware Update via SCP ......................535 Bulk Configuration via SCP ......................536 Backup and Restore via SCP ......................
Page 14 Contents Firmware Upgrade via USB......................560 Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ..................562 TFTP Requirements........................563 DHCP IPv4 Configuration in Windows..................564 DHCP IPv6 Configuration in Windows..................574 ...
Page 15 Contents Appendix G Old PX3 Character LCD Display Overview of the LCD Display ......................603 Control Buttons ..........................604 Operating the LCD Display ......................604 Outlet Information......................604 Inlet Information ........................ 606 Overcurrent Protector Information ................... 607 ...
Page 16 Unbalanced Current Calculation....................685 Data for BTU Calculation......................686 Ways to Probe Existing User Profiles ..................687 Raritan Training Website......................687 Role of a DNS Server........................688 Cascading Troubleshooting......................688 Possible Root Causes ......................688 ...
Page 17 For example, PX2-4000, PX3-4000 series and PX3-iX7-4000 series are all inlet metered and outlet metered PDUs, but have different controller generations. Note: For information on other PX2, PX3 or PX3-iX7 models, see their respective Online Help or User Guide on the Raritan website's Support page http://www.raritan.com/support/...
Page 18 Chapter 1: Applicable Models Comparison between PX2, PX3 and PX3-iX7: * Only PX3 models with outlet switching have outlet latching relays. ** Only PX3 "Zero U" (phase II and iX7 ) have the replaceable controller. ™ *** PX3 phase I models do NOT support a replaceable controller and are NOT available for sale anymore.
Page 19 What's New in the PX3 User Guide The following sections have changed or information has been added to the PX3 User Guide based on enhancements and changes to the equipment and/or user documentation. Applicable Models (on page xvii) USB Wireless LAN Adapters (on page 25) Dual Ethernet Connection (for iX7 Only)
Page 20 Chapter 1: What's New in the PX3 User Guide Asset Strip (on page 195) Creating Users (on page 208) Creating Roles (on page 213) User Interfaces Showing Default Units (on page 216) Device Settings (on page 217) Configuring Network Settings (on page 218) Wired Network Settings (on page 219)
Page 21 What's New in the PX3 User Guide Configuring the Serial Port (on page 325) Lua Scripts (on page 327) Writing or Loading a Lua Script (on page 327) Manually Starting or Stopping a Script (on page 329) Checking Lua Scripts States (on page 331) Modifying or Deleting a Script (on page 331)
Page 22 Chapter 1: What's New in the PX3 User Guide Changing the LAN Duplex Mode (on page 423) Configuring the Cascading Mode (on page 429) Deleting an NTP Server (on page 440) RCM Critical State Alarm (on page 592) Setting RCM Current Thresholds (on page 592) IPv4 Address (on page 609)
Page 23: Chapter 1 Introduction
PX3-iX7 or iX7 in the User Guide. ™ Raritan PX3 is an intelligent power distribution unit (PDU) that allows you to reboot remote servers and other network devices and/or to monitor power in the data center. The intended use of the Raritan PX3 is distribution of power to...
Page 24: Zero U Products
Cable retention clips for outlets (for some models only)  An "optional" null-modem cable with DB9 connectors on both ends (Raritan number: 254-01-0006-00) -- for PX3 models For PX3-iX7, use a third party RJ45-to-DB9 adapter/cable instead of RJ45-to-DB9 Cable Requirements for the null-modem cable.
Page 25: Apipa And Link-Local Addressing
Chapter 1: Introduction APIPA and Link-Local Addressing The PX3 supports Automatic Private Internet Protocol Addressing (APIPA). With APIPA, your PX3 automatically configures a link-local IP address and a link-local host name when it cannot obtain a valid IP address from any DHCP server in the TCP/IP network.
Page 26: Before You Begin
Note: Not all PX3 devices have overcurrent protection mechanisms. Preparing the Installation Site 1. Make sure the installation area is clean and free of extreme temperatures and humidity. Note: If necessary, contact Raritan Technical Support for the maximum operating temperature for your model. See Maximum (on page 540).
Page 27: Filling Out The Equipment Setup Worksheet
Chapter 1: Introduction Filling Out the Equipment Setup Worksheet An Equipment Setup Worksheet is provided in this User Guide. See Equipment Setup Worksheet (on page 544). Use this worksheet to record the model, serial number, and use of each IT device connected to the PDU.
Page 28: Chapter 2 Rackmount, Inlet And Outlet Connections
This chapter describes how to rack mount a PX3 device. To mount a Zero U PX-1000 series PDU, you can use either two buttons or L-brackets that Raritan provided. Rackmount Safety Guidelines In Raritan products which require rack mounting, follow these precautions:  Operation temperature in a closed rack environment may be greater than room temperature.
Page 29: Mounting Zero U Models Using L-Brackets
Chapter 2: Rackmount, Inlet and Outlet Connections  Connect equipment to the supply circuit carefully to avoid overloading circuits.  Ground all equipment properly, especially supply connections, to the branch circuit. Mounting Zero U Models Using L-Brackets Circuit Breaker If your PDU has circuit breakers implemented, read Orientation Limitation (on page 6) before mounting it.
Page 30 Chapter 2: Rackmount, Inlet and Outlet Connections 3. Align the L-brackets with the baseplates so that the five screw-holes on the baseplates line up through the L-bracket's slots. The rackmount side of brackets should face either the left or right side of the PX3 device.
Page 31: Mounting Zero U Models Using Button Mount
Chapter 2: Rackmount, Inlet and Outlet Connections Mounting Zero U Models Using Button Mount If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 6) before mounting it. To mount Zero-U models using button mount: 1. Align the baseplates on the rear of the PX3 device. Leave at least 24 inches between the baseplates for stability.
Page 32: Mounting Zero U Models Using Claw-Foot Brackets
Chapter 2: Rackmount, Inlet and Outlet Connections 5. Loosen the hex socket screws until the mounting buttons are secured in their position. 6. Ensure that both buttons can engage their mounting holes simultaneously. 7. Press the PX3 device forward, pushing the mounting buttons through the mounting holes, then letting the device drop about 5/8".
Page 33 Chapter 2: Rackmount, Inlet and Outlet Connections 3. Align the claw-foot brackets with the baseplates so that the five screw-holes on the baseplates line up through the bracket's slots. The rackmount side of brackets should face either the left or right side of the PX3 device.
Page 34: Mounting Zero U Models Using Two Rear Buttons
Chapter 2: Rackmount, Inlet and Outlet Connections Mounting Zero U Models Using Two Rear Buttons The following describes how to mount a PDU using two buttons only. If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 6) before mounting it. To mount Zero U models using two buttons: 1.
Page 35: Mounting Zero U Models Using L-Brackets And Buttons
Chapter 2: Rackmount, Inlet and Outlet Connections 4. Screw a button in the screw hole near the top. The recommended torque for the button is 1.96 N·m (20 kgf·cm). 5. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously.
Page 36: Mounting 1U Or 2U Models
Chapter 2: Rackmount, Inlet and Outlet Connections 2. Screw the L-bracket to the device and ensure the bracket is fastened securely. 3. Repeat Steps 1 to 2 to screw another L-bracket to the bottom of the device. 4. After both L-brackets are installed, you can choose either of the following ways to mount the device in the rack.
Page 37 Chapter 2: Rackmount, Inlet and Outlet Connections 2. Insert the cable-support bar into rackmount brackets. 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners.
Page 38: Connecting A Locking Line Cord
Chapter 2: Rackmount, Inlet and Outlet Connections Connecting a Locking Line Cord The PX3 is shipped with either of the following locking line cords.  A line cord with locking clips: A locking inlet on the PDU is required for this cord. ...
Page 39: Disconnecting A Locking Line Cord
Chapter 2: Rackmount, Inlet and Outlet Connections To connect a cord with slide release buttons: Simply plug the cord's connector into the PDU's inlet. Number Item Slide release buttons Disconnecting a For information on removing the locking line cord, see Locking Line Cord (on page 17).
Page 40: Installing Cable Retention Clips On The Inlet (Optional)
Chapter 2: Rackmount, Inlet and Outlet Connections To disconnect a line cord with slide release buttons: Push both slide release buttons toward the cord while unplugging this cord. Installing Cable Retention Clips on the Inlet (Optional) If your PX3 device is designed to use a cable retention clip, install the clip before connecting a power cord.
Page 41: Installing Cable Retention Clips On Outlets (Optional)
Chapter 2: Rackmount, Inlet and Outlet Connections Zero U models 1U/2U models Installing Cable Retention Clips on Outlets (Optional) If your PX3 device is designed to use a cable retention clip, install the clip before connecting a power cord. A cable retention clip prevents the connected power cord from coming loose or falling off.
Page 42: Locking Outlets And Cords
IT equipment to the Raritan PDUs, including:  SecureLock outlets and cords ™  Button-type locking outlets Note that NOT all Raritan PDUs are implemented with any of the above locking outlets.
Page 43: Securelock™ Outlets And Cords
SecureLock™ Outlets and Cords SecureLock is an innovative mechanism designed by Raritan, which ™ securely holds C14 or C20 plugs that are plugged into Raritan PDUs in place. This method requires the following two components:  Raritan PDU with SecureLock outlets, which have a latch slot inside ™...
Page 44: Button-Type Locking Outlets
Chapter 2: Rackmount, Inlet and Outlet Connections To remove a SecureLock power cord from the PDU: ™ 1. Press and hold down the two latches on the cord's plug as illustrated in the diagram below. 2. Unplug the cord now. Button-Type Locking Outlets A button-type locking outlet has a button on it.
Page 45: Chapter 3 Initial Installation And Configuration
Chapter 3 Initial Installation and Configuration This chapter explains how to install a PX3 device and configure it for network connectivity. In This Chapter Connecting the PDU to a Power Source ........... 23 Connecting the PX3 to Your Network............24 Configuring the PX3...................
Page 46: Connecting The Px3 To Your Network
Chapter 3: Initial Installation and Configuration Connecting the PX3 to Your Network To remotely administer the PX3, you must connect the PX3 to your local area network (LAN). PX3 can be connected to a wired or wireless network. Note: If your PX3 will work as a master device in the bridging mode, make a wired connection.
Page 47: Usb Wireless Lan Adapters
LAN adapters. USB Wireless LAN Adapters The PX3 supports the following USB Wi-Fi LAN adapters. Wi-Fi LAN adapters Supported 802.11 protocols SparkLAN WUBR-508N A/B/G/N Proxim Orinoco 8494 A/B/G Zyxel NWD271N Edimax EW-7722UnD A/B/G/N TP-Link TL-WDN3200 v1 A/B/G/N Raritan USB WIFI A/B/G/N...
Page 48: Supported Wireless Lan Configuration
Chapter 3: Initial Installation and Configuration Note: To use the Edimax EW-7722UnD or Raritan USB WIFI wireless LAN adapter to connect to an 802.11n wireless network, the handshake timeout setting must be changed to 500 or greater, or the wireless connection will fail.
Page 49: Dual Ethernet Connection (For Ix7™ Only)
Chapter 3: Initial Installation and Configuration Dual Ethernet Connection (for iX7™ Only) An iX7 PDU has two Ethernet (LAN) ports: ™  green ETH 10/100/1000 (marked in ) supports up to 1000 Mbps. This is "ETH1".  ETH 10/100 (marked in white ) supports up to 100 Mbps.
Page 50: Connecting The Px3 To A Computer
Chapter 3: Initial Installation and Configuration 2. Retrieve the DHCP-assigned IPv4 address. Use the front panel LCD Device Info display to retrieve it. See (on page 111). Login 3. Launch a web browser to configure the PX3. See (on page 127).
Page 51 Chapter 3: Initial Installation and Configuration  PX3-iX7 models: To use the command line interface (CLI) for configuration, establish an RS-232 or USB connection. To use a web browser for configuration, make a network connection to the computer. The PX3 is automatically configured with the following link-local addressing in any network without DHCP available: ...
Page 52 3. Perform (on page 32). Note: Not all serial-to-USB converters work properly with the PX3 so Raritan does not introduce the use of such converters. Direct network connection: The Ethernet port must be enabled for this connection to work properly.
Page 53: Installing The Usb-To-Serial Driver (Optional)
The PX3 can emulate a USB-to-serial converter over a USB connection. A USB-to-serial driver named "Dominion PX2 Serial Console" is required for Microsoft Windows operating systems. ® ® Download the Windows driver for USB serial console from the Raritan website's Support page http://www.raritan.com/support/ ). The downloaded driver's name is dominion-serial-setup-<n>.exe , where <n>...
Page 54: Initial Network Configuration Via Cli
Chapter 3: Initial Installation and Configuration Note: If any Windows security warning appears, accept it to continue the installation. 4. Wait until the installation is complete. Note: If the PX3 enters the disaster recovery mode when the USB serial driver is not installed yet, it may be shown as a 'GPS camera' in the Device Manager on the computer connected to it.
Page 55 4. The PX3 prompts you to log in. Both user name and password are case sensitive. a. Username: admin b. Password: raritan (or a new password if you have changed it). 5. If prompted to change the default password, change or ignore it. ...
Page 56 Chapter 3: Initial Installation and Configuration To set or Use this command enable network dns resolverPreference IP address <resolver> returned by the DNS <resolver> = preferV4 preferV6 server  Static IP configuration: To set Use this command network <ipvX> interface <ETH> Static IPv4 or address <ip address>...
Page 57 Chapter 3: Initial Installation and Configuration Commands for wireless networking:  General wireless settings: To set or Use this command enable network wireless enabled Wireless <option> interface true false <option> = , or network wireless SSID <ssid> SSID <ssid> = SSID string network wireless BSSID <bssid>...
Page 58 Chapter 3: Initial Installation and Configuration To set or Use this command enable EAP password network wireless eapPassword When prompted to enter the password for EAP authentication, type the password. network wireless EAP CA eapCACertificate certificate When prompted to enter the CA certificate, open the certificate with a text editor, copy and paste the content into the communications program.
Page 59: Bulk Configuration Methods
Chapter 3: Initial Installation and Configuration  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 60: Cascading Multiple Px3 Devices For Sharing Ethernet Connectivity
Chapter 3: Initial Installation and Configuration Use a USB flash drive:  Requirement: A FAT32- or supperfloppy-formatted USB flash drive containing special configuration files is required.  Procedure: Plug this USB drive into the PX3. 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 61 USB-cascading tip: The "USB-cascading" configuration can be a combination of diverse Raritan products that support the USB-cascading feature, including PX2, PX3, PX3-iX7, transfer switch, BCM and EMX. Troubleshooting: When a networking issue occurs, check the cascading connection and/or Cascading software settings of all devices in the chain.
Page 62: Cascading The Px3 Via Usb
16 devices in a chain. For more information on the USB-cascading configuration, see the Cascading Guide Support , which is available from Raritan website's page http://www.raritan.com/support/ The following diagram illustrates PX3 PDUs cascaded via either USB.
Page 63 Device role Slave 2 Slave 3 To cascade PX3 devices via USB: 1. Make sure all Raritan devices to be cascaded are running firmware version 3.3.10 or later. 2. Select one as the master device.  When the port forwarding mode over wireless LAN is intended, the master device must be a Raritan product with two USB-A ports, such as PX3, EMX2-888, PX3TS or BCM2.
Page 64: Extended Cascading With Px3-Ix7 Models
Only PX3-iX7 PDUs support cascading via either Ethernet or USB ports. These PDUs support cascading via Ethernet ports because they have two Ethernet ports. Other Raritan products do NOT support Ethernet cascading. There is no restriction of using which Ethernet port of PX3-iX7 for...
Page 65 Chapter 3: Initial Installation and Configuration If wanted, you can mix Ethernet and USB cascading in a PX3-iX7 cascading chain. The following diagram illustrates such a chain. For instructions on USB cascading, see Cascading the PX3 via USB page 40). Number Device role Master device...
Page 66 Slave 2 Slave 3 To cascade iX7 PDUs via Ethernet ports: ™ 1. Make sure all Raritan devices to be cascaded are running firmware version 3.3.10 or later. 2. Choose one iX7 PDU as the master device. ™ 3. Log in to all devices one by one and select the same cascading mode.
Page 67: Unsupported Cascading Connections For Port Forwarding
Chapter 3: Initial Installation and Configuration Unsupported Cascading Connections for Port Forwarding The following guidelines must be obeyed for establishing a cascading chain in the port forwarding mode.  Each cascaded device, except for the master device, must have only one upstream device.
Page 68 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 69: Power-Sharing Restrictions And Connection (For Ix7™ Only)
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 (for iX7™ Only) Two iX7 PDUs can share power supply to their controllers via ™...
Page 70 Note: Outlet switching is not available because all outlets lose power.  Monitor the status of connected Raritan environmental sensor packages, or configure/control their settings.  Operate the front panel display. Exception: Operation of the front panel display is NOT available on a PX3 with residual current monitoring because it assumes that there is an RCM alarm when losing power supply from the inlet.
Page 71: Making A Power-Sharing Connection
Chapter 3: Initial Installation and Configuration Making a Power-Sharing Connection Make sure BOTH iX7 PDUs comply with the configuration limitations ™ before establishing a power-sharing connection. See Power-Sharing Configurations and Restrictions (on page 50). The supported maximum power-sharing distance is 2 meters. Make a power-sharing connection: 1.
Page 72: Power-Sharing Configurations And Restrictions
Chapter 3: Initial Installation and Configuration Power-Sharing Configurations and Restrictions When either iX7 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 iX7 PDUs when making a power-sharing ™...
Page 73 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 ™...
Page 74 BOTH PDUs. Warning: The in-rush current of a newly added sensor package may cause both PDUs to reboot. For information on Raritan's sensor packages or hubs, see Connecting Environmental Sensor Packages (on page 53).
Page 75: 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 PX3. In This Chapter Connecting Environmental Sensor Packages .......... 53 Connecting Asset Management Strips............72 Connecting a Logitech Webcam..............81 Connecting a GSM Modem ................
Page 76 Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of the PX3. To directly connect a differential air pressure sensor: 1. Connect a Raritan-provided phone cable to the IN port of a differential air pressure sensor. 2. Get an RJ-12 to RJ-45 adapter. Connect the adapter's RJ-12 connector to the other end of the phone cable.
Page 77 DPX2, DPX3 or DX sensor packages to it. DPX-ENVHUB4 sensor hubs CANNOT be cascaded. You can connect only one hub to each SENSOR port on the PX3. Tip: The Raritan sensor hub that supports ALL types of Raritan environmental sensor packages is . See...
Page 78: Dpx Sensor Packages
2. Connect DPX sensor packages to any of the four OUT ports on the hub. This diagram illustrates a configuration with a sensor hub connected. The PX3 device RJ-12 to RJ-45 adapter Raritan-provided phone cable DPX-ENVHUB4 sensor hub DPX sensor packages Using an Optional DPX-ENVHUB2 cable A Raritan...
Page 79 Chapter 4: Connecting External Equipment (Optional) 2. The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports. 3. Repeat the above steps if there are additional SENSOR ports on your PX3.
Page 80 Sensor connection restrictions:  Connect a DPX sensor package to the PX3 using the sensor cable pre-installed (or provided) by Raritan. You MUST NOT extend or modify the sensor cable's length by using any tool other than the Raritan's sensor hubs.
Page 81 RJ-12 connector and one to three head connectors. You have to connect DPX2 sensor packages to the sensor cable. For more information on DPX2 sensor packages, access the Environmental Sensors Guide or Online Help on Raritan website's Support page http://www.raritan.com/support/...
Page 82 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 83 Chapter 4: Connecting External Equipment (Optional) b. Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of the PX3. OR you can directly connect the DPX2 sensor package to a DX sensor Connecting a chain without using any RJ-12 to RJ-45 adapter. See DPX2 Sensor Package to DX (on page 65).
Page 84 Chapter 4: Connecting External Equipment (Optional) Repeat the same steps to cascade more DPX3 sensor packages. 3. Connect the first DPX3 sensor package to the PX3 by plugging its cable's connector into the RJ-45 SENSOR port of the PX3. Connecting a DPX2 Sensor Package to DPX3 You can connect only one DPX2 sensor package to the "end"...
Page 85: Dx Sensor Packages
Most DX sensor packages contain terminals for connecting detectors or actuators. For information on connecting actuators or detectors to DX terminals, refer to the Environmental Sensors Guide or Online Help on Raritan website's Support page http://www.raritan.com/support/ You can cascade up to 12 DX sensor packages.
Page 86 Chapter 4: Connecting External Equipment (Optional) Numbers Components Removable rackmount brackets. Connect DX sensor packages to the PX3: 1. Connect a standard network patch cable (CAT5e or higher) to either RJ-45 port on a DX sensor package. 2. If you want to cascade DX packages, get an additional standard network patch cable (CAT5e or higher) and then: a.
Page 87 Chapter 4: Connecting External Equipment (Optional) Connecting a DPX2 Sensor Package to DX You can connect only one DPX2 sensor package to the "end" of a DX sensor chain. It is strongly recommended to use an RJ-12 to RJ-45 adapter for connecting the DPX2 to the final DX in the chain. The maximum number of DX sensor packages in the chain must be less than 12 when a DPX2 sensor package is involved.
Page 88: Using An Optional Dpx3-Envhub4 Sensor Hub
Plug one end of the cable into the IN port (Port 1) of the hub. b. Plug the other end of the cable into the RJ-45 SENSOR port of the PX3. 2. Connect the Raritan sensor packages to any of the four OUT ports on the hub. ...
Page 89 Chapter 4: Connecting External Equipment (Optional) This diagram illustrates a configuration with a sensor hub connected. The PX3 A standard network cable DPX3-ENVHUB4 sensor hub Any Raritan sensor packages...
Page 90: Mixing Diverse Sensor Types
Chapter 4: Connecting External Equipment (Optional) Mixing Diverse Sensor Types You can mix DPX, DPX2, DPX3 and DX sensor packages on one PX3 according to the following sensor combinations. In some scenarios, the DPX3-ENVHUB4 sensor hub is required. The PX3 does NOT support any other sensor-mixing combinations than those described in this section.
Page 91 Chapter 4: Connecting External Equipment (Optional)  An RJ-12 to RJ-45 adapter is recommended to connect a DPX or DPX2 sensor package to DPX3-ENVHUB4.  In the following diagrams, the sensor package in "green" can be replaced by a DPX2 sensor package. The sensor package in "blue" can be one DPX2, DPX3 or DX sensor package.
Page 92 Chapter 4: Connecting External Equipment (Optional)
Page 93 Chapter 4: Connecting External Equipment (Optional) Mix DPX3 and DX in a sensor chain: Any DX sensor package in a chain can be replaced by a DPX3 sensor package, or vice versa. The total number of sensor packages in this chain cannot exceed 12.
Page 94: Connecting Asset Management Strips
The difference between the master and slave asset strips is that the master asset strip has an RJ-45 connector while the slave does not. The following diagram illustrates some asset strips. Note that Raritan provides more types of asset strips than the diagram.
Page 95 Chapter 4: Connecting External Equipment (Optional) 8U MASTER asset strip with 8 tag ports 8U SLAVE asset strip with 8 tag ports 5U "ending" SLAVE asset strip with 5 tag ports Note: Unlike general slave asset strips, which have one DIN connector respectively on either end, the ending slave asset strip has one DIN connector on only one end.
Page 96: Introduction To Asset Tags
Chapter 4: Connecting External Equipment (Optional) Note: The asset strip is implemented with a tilt sensor so it can be mounted upside down. Introduction to Asset Tags You need both asset strips and asset tags for tracking IT devices. Asset tags provide an ID number for each IT device. The asset tags are adhered to an IT device at one end and plugged in to an asset strip at the other.
Page 97 Chapter 4: Connecting External Equipment (Optional) 3. Connect the asset strip assembly to the PX3 device, using a network patch cable (CAT5e or higher).  Connect one end of the cable to the RJ-45 connector on the MASTER asset strip. ...
Page 98: 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 99 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 PX3 device's web interface. To install a blade extension strip: 1.
Page 100 Chapter 4: Connecting External Equipment (Optional) a. Affix the adhesive part of the asset tag to one side of a blade server through the tag's tape. b. Plug the tag connector of the asset tag into a tag port on the blade extension strip.
Page 101: Connecting Composite Asset Strips
Chapter 4: Connecting External Equipment (Optional) Connecting Composite Asset Strips A composite asset strip is named AMS-Mx-Z, where x is a number, such as AMS-M2-Z or AMS-M3-Z. It is a type of asset strip that functions the same as regular MASTER asset strips except for the following differences: ...
Page 102 The maximum cable length between composite asset strips is 2 meters, but the total cable length cannot exceed 10 meters.  The maximum number of composite asset strips that can be daisy chained depend on the Raritan product you purchased. Raritan devices Maximum strips per chain EMX2-111, Up to 4 composite asset strips are supported.
Page 103: Connecting A Logitech Webcam
Pro 9000, Model 960-000048 ® ® Other UVC-compliant webcams may also work. However, Raritan has neither tested them nor claimed that they will work properly. Tip: You can easily find a list of UVC-compliant webcams on the Internet. The PX3 supports up to two webcams. After connecting a webcam, you can retrieve visual information from anywhere through the PX3 web interface.
Page 104: Connecting A Gsm Modem
Chapter 4: Connecting External Equipment (Optional) Connecting a GSM Modem The following Cinterion GSM modems can be connected to the PX3 in ® order to send SMS messages containing event information.  MC52iT  MC55iT  EHS6 Available Actions (on page 289) for more information on SMS messages.
Page 105: Connecting An Analog Modem
 NETCOMM IG6000 Industrial Grade SmartModem  US Robotics 56K modem The PX3 may also support other analog modems which Raritan did not test. Note that the PX3 does NOT support dial-out or dial-back operations via the modem. To connect an analog modem: 1.
Page 106: Connecting A Schroff Lhx/Shx Heat Exchanger
Chapter 4: Connecting External Equipment (Optional) The beeper can be located at a distance up to 330 feet (100 m) away from the PX3. Connecting a Schroff LHX/SHX Heat Exchanger To remotely monitor and administer the Schroff LHX-20, LHX-40 and ®...
Page 107: Chapter 5 Introduction To Pdu Components
Chapter 5 Introduction to PDU Components This chapter explains how to use the PX3 device, including:  Introduction to the LEDs and ports on the PDU  Operation of the front panel display  The overcurrent protector's behavior  The internal beeper's behavior ...
Page 108: Inlet
Chapter 5: Introduction to PDU Components Inlet Most of PX3 PDUs are shipped with a locking line cord, which is ready to be plugged into the PDU's inlet and an appropriate receptacle for electricity reception. Such devices cannot be rewired by the user. A locking line cord helps secure the cord connection.
Page 109: Outlets
Inlet on the side Inlet on the top Outlets The total number of outlets varies from model to model. PX3-1000 Series These models are NOT outlet-switching capable so all outlets are always in the ON state. Outlet LEDs are not available.
Page 110: Connection Ports
Chapter 5: Introduction to PDU Components Connection Ports Depending on the model you purchased, the total number of ports available varies. Zero U Connection Ports The total number of connection ports depends on the model you purchased. Note that port locations on your models may be different from these images.
Page 111 Cascading the PX3 devices for sharing a network connection. FEATURE Connection to one of the following devices:  A Raritan access product, such as Dominion KX III KVM switch, with the use of a power CIM.  A Schroff LHX-20, SHX-30 or LHX-40 device, using an RJ-45 to ®...
Page 112  (RJ-45) Raritan's environmental sensor package(s).  Raritan's sensor hub, which expands the number of a sensor port to four ports. ETHERNET Connecting the PX3 to your company's network via a standard network patch cable (Cat5e/6). This connection is necessary to administer or access the PX3 remotely.
Page 113: Dot-Matrix Lcd Display
Chapter 5: Introduction to PDU Components Port Used for ETH 10/100/1000, has two Ethernet ports. ™  green ETH 10/100 ETH 10/100/1000 (marked in ) supports up to 1000 Mbps. This is "ETH1".  white ETH 10/100 (marked in ) supports up to 100 Mbps. This is "ETH2".
Page 114 Chapter 5: Introduction to PDU Components You can use the LCD display to view the PX3 information and even switch an outlet. It consists of:  A dot-matrix LCD display  Four control buttons Note 1: All dot-matrix LCD display diagrams illustrated in the User Guide are for Zero U models.
Page 115 Automatic and Manual Modes After powering on or resetting the PX3, the front panel LCD display first shows the Raritan logo, and then enters the automatic mode. Automatic mode without alerts available: In this mode, the LCD display cycles through the inlet information as long as there are no alerts.
Page 116 Chapter 5: Introduction to PDU Components Control Buttons Use the control buttons to navigate to the menu in the manual mode. PX3 button PX3-iX7 button Function Down Back -- OR -- Switch between automatic and manual modes...
Page 117 Chapter 5: Introduction to PDU Components Operating the Dot-Matrix LCD Display Enter manual mode when you want to operate the dot-matrix LCD display. You can use the dot-matrix LCD display to:  Show information of the PDU, built-in components, or connected peripheral devices ...
Page 118 Chapter 5: Introduction to PDU Components Main Menu The Main Menu contains 6 to 9 menu commands, depending on the model. Control buttons that can be used and the system time are shown at the bottom of the LCD display. If any alerts exist, the top and bottom bars on the LCD display change the Operating the Dot-Matrix LCD color from black to yellow or red.
Page 119 If your PX3 supports outlet-switching, you can turn on, off or power cycle an outlet. See Outlets. Shows the information of connected Raritan environmental sensors or actuators, such as the temperature sensor. Peripherals You can turn on or off a connected actuator with this command.
Page 120 Chapter 5: Introduction to PDU Components 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 121 Chapter 5: Introduction to PDU Components Number Description Sensor names. Sensor readings and/or states. A numeric sensor shows both the reading and state. A state sensor or actuator shows the state only. Available states are listed below. For further information, see Sensor/Actuator States (on page 182).
Page 122 Chapter 5: Introduction to PDU Components  In the Active state, the reason of turning on the beeper is indicated, and the top/bottom bars turn red. 3. If your PDU is a PX3 with iX7 controller, press to show the ™...
Page 123 Chapter 5: Introduction to PDU Components 4. If your PX3 has more than one inlet, press to show the information of total active power (W) and total active energy (Wh). 5. To return to the Main Menu, press Inlet An inlet's information is separated into two pages. Page numbers are indicated in the top-right corner of the LCD display.
Page 124 Chapter 5: Introduction to PDU Components 2. The first page shows the inlet's active power (W), apparent power (VA), power factor (PF), and active energy (Wh). 3. To go to other page(s), press  For a single-phase model, the second page shows the inlet's voltage (V), frequency (Hz) and current (A).
Page 125 Chapter 5: Introduction to PDU Components 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. Otherwise, no page numbers are available. To show the overcurrent protector information: 1.
Page 126 Chapter 5: Introduction to PDU Components Peripherals If there are no Raritan environmental sensor packages connected to your PX3, the LCD display shows the message "No managed devices" for the "Peripherals" menu command. If you have enabled the front panel actuator control function, you can switch on or off a connected actuator using the LCD display.
Page 127 Chapter 5: Introduction to PDU Components Number Description Sensor or actuator names. Sensor or actuator states as listed below. For further information, see Sensor/Actuator States (on page 182).  n/a = unavailable  Normal  Alarmed  Lower Critical = below lower critical ...
Page 128 Chapter 5: Introduction to PDU Components Number Description Sensor or actuator name. The following information is listed.  Serial number  Chain position, which involves the following information: Port <N>: <N> is the number of the sensor port where this sensor or actuator is connected.
Page 129 4. Verify that the actuator status shown on the LCD display has been changed. Assets If there are no Raritan asset management strips connected, the LCD display shows the message "No asset strips connected" for the "Assets" menu command. After connecting asset strips, only the information of the rack units where asset tags have been detected are shown on the LCD display.
Page 130 Chapter 5: Introduction to PDU Components  The number of tags includes both the tags attached to the asset strip and those attached to the blade extension strip, if any. 3. Press to show this asset strip's details, including:  State - strip status.
Page 131 Chapter 5: Introduction to PDU Components  Orientation - the strip's orientation. 4. Press again to show a list of available tags and their information.  When the list exceeds one page, the currently-selected main tag and total of available main tags are indicated in the top-right corner of the display.
Page 132 Chapter 5: Introduction to PDU Components Number Description Two numbers are displayed for each tag.  Rack unit number: The number assigned to this tag based on the Asset Strip selected numbering mode. See (on page 195).  The index number in parentheses: The physical port number printed on the asset strip.
Page 133 Chapter 5: Introduction to PDU Components Number Description The information of the selected blade extension strip, including:  Rack unit number  Index number in parentheses  Current LED color of the tag port where it is connected  Extension strip's ID number (barcode) The slot number of each asset tag The connected asset tag's ID number (barcode).
Page 134 Chapter 5: Introduction to PDU Components Number Description Device ratings, including rated voltage, frequency, current and power. 3. Press to show the Network Common page. Number Description DNS servers. Default gateways. 4. Press to show the Network Cascading page.
Page 135 Chapter 5: Introduction to PDU Components 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 231).  Network Bridge Enabled: This device's cascading mode is set to Bridging. Its IP address is also displayed on this page.
Page 136 Chapter 5: Introduction to PDU Components 5. Press to show the ETHERNET page.  For PX3-iX7 PDUs, there are two Ethernet pages -- ETH1 and ETH2. Number Description Ethernet interface information, including:  MAC address.  Speed.  Full or half duplex.
Page 137 Chapter 5: Introduction to PDU Components IPv4/IPv6 network information, including:  Network configuration: DHCP (or Automatic), or Static. Static represents Static IP.  IP address.  Netmask or prefix length, such as "/24". Note: If you disable any Ethernet interface, a message 'Interface Disabled' is shown.
Page 138 Chapter 5: Introduction to PDU Components 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. When all alerted sensors enter the warning levels, the screen's background is yellow.
Page 139: Reset Button
Chapter 5: Introduction to PDU Components Showing the Firmware Upgrade Progress When upgrading the PX3, the firmware upgrade progress will be displayed as a percentage on the LCD display, similar to the following diagram. In the end, a message appears, indicating whether the firmware upgrade is successful or fails.
Page 140: Circuit Breakers
Chapter 5: Introduction to PDU Components PX3-iX7 models: Circuit Breakers PX3 models rated over 20A (North American) or 16A (international) contain overcurrent protectors for outlets, which are usually branch circuit breakers. These circuit breakers automatically trip (disconnect power) when the current flowing through the circuit breaker exceeds its rating.
Page 141: Resetting The Handle-Type Circuit Breaker
Chapter 5: Introduction to PDU Components 3. Press the ON button until it is completely down. Resetting the Handle-Type Circuit Breaker Your handle-type circuit breakers may look slightly different from the images shown in this section, but the reset procedure remains the same. To reset the handle-type breakers: 1.
Page 142: Fuse
Chapter 5: Introduction to PDU Components Fuse Some PX3 devices may be implemented with fuses instead of circuit breakers. A fuse blows to protect associated outlets if it detects the overload. If your PDU uses fuses, you must replace it with a new one when it blows or malfunctions.
Page 143: Fuse Replacement On 1U Models
Chapter 5: Introduction to PDU Components 3. Push the cover of the fuse holder to expose the fuse. 4. Take the fuse out of the holder. 5. Insert a new fuse into the holder. There is no orientation limit for fuse insertion.
Page 144 Chapter 5: Introduction to PDU Components To replace a fuse on 1U PDUs: 1. Disconnect the PDU's power cord from the power source. 2. Remove the desired fuse from the PDU's fuse carrier using a flat screwdriver. a. Rotate the fuse knob counterclockwise until its slot is inclined to 45 degrees.
Page 145: Beeper
Chapter 5: Introduction to PDU Components 5. Verify whether this knob's head is aligned with the fuse carrier. If its head is higher or lower than the fuse carrier, re-install it. Number Description INAPPROPRIATE installations Appropriate installation 6. Connect the PDU's power cord to the power source and verify that the corresponding fuse LED is lit, indicating that the fuse works properly.
Page 146: Replaceable Controller
PDU. If the controller is broken, you can simply send the controller back to Raritan for repair, or purchase a new controller from Raritan. 1U / 2U PDUs and all of PX3-3000 series do NOT support this feature.
Page 147 Chapter 5: Introduction to PDU Components 3. Disconnect the PDU's controller cable from the controller. 4. Get a new PX3 controller and install it back into the PDU in the reverse order.
Page 148: Chapter 6 Using The Web Interface
Chapter 6 Using the Web Interface This chapter explains how to use the web interface to administer a PX3. In This Chapter Supported Web Browsers ............... 126 Login, Logout and Password Change ............. 126 Web Interface Overview................129 Dashboard ....................135 PDU......................
Page 149: Login
Chapter 6: Using the Web Interface Login You must enable JavaScript in the web browser for proper operation. To log in to the web interface: 1. Open a browser and type the IP address of the PX3.  If the link-local addressing has been enabled, you can type pdu.local APIPA and Link-Local instead of an IP address.
Page 150: Changing Your Password
Chapter 6: Using the Web Interface Note: The address to access a slave device in the port forwarding mode via non-standard ports is a combination of a protocol (http:// or https://), an IP address and a port number. See Port Forwarding Examples page 236).
Page 151: Remembering User Names And Passwords
Chapter 6: Using the Web Interface Remembering User Names and Passwords The PX3 supports the password manager of common web browsers, including:  Microsoft Internet Explorer ®  Mozilla Firefox ®  Google Chrome ® You can save the login name and password when these browsers ask whether to remember them.
Page 152: Menu
Chapter 6: Using the Web Interface 4. To return to the main menu and the Dashboard page, click on the top-left corner. Number Web interface element Menu (on page 132) Data/setup page of the selected menu item  Left side: - PX3 device name...
Page 153 Browsing through the Online Help - See (on page 694).  Raritan Support: link to the Raritan Technical Support webpage.  Date and time of your user account's last login - Click Last Login to view your login history.  PX3 system time...
Page 154: Dashboard
Chapter 6: Using the Web Interface Menu Depending on your model and hardware configuration, your PX3 may show all or some menu items shown below. Menu Information shown Dashboard Summary of the PX3 status, including a list of alerted sensors and alarms, if any.
Page 155 OCP status and settings, such as OCP thresholds. OCPs (on page 170). Peripherals Status and settings of Raritan environmental sensor packages, if connected. Peripherals (on page 175). Feature Port Status and settings of the device connected to the Feature port(s), which can be one of the following.
Page 156: Quick Access To A Specific Page
Chapter 6: Using the Web Interface If a menu item contains the submenu, the submenu is shown after clicking that item. To return to the previous menu list, do any below:  Click the topmost link with the symbol >. For example, click ...
Page 157: Dashboard
Chapter 6: Using the Web Interface 2. To have it resorted in the descending order based on the same column, click the Timestamp header. 3. The arrow turns to , indicating the list is sorted in the "descending" order. 4. To resort the list based on a different column, click a different column header.
Page 158 Chapter 6: Using the Web Interface Number Section Information shown  Overview of inlet power data Inlet I1  A current bar per phase, which changes colors to indicate the RMS current state - green: normal - yellow: warning - red: critical Dashboard - Inlet I1 (on page 137).
Page 159: Dashboard - Inlet I1
Chapter 6: Using the Web Interface Dashboard - Inlet I1 The number of phases shown in the Inlet section varies, depending on the model. Link to the Inlet page: To view more information or configure the inlet(s), click this section's title 'Inlet I1' to go to the Inlet page.
Page 160 Chapter 6: Using the Web Interface Left side - generic inlet power data: The left side lists all or some of the following data. Available data is model dependent.  Active power (kW or W)  Apparent power (kVA or VA) ...
Page 161: Dashboard - Ocp
Chapter 6: Using the Web Interface Dashboard - OCP Availability and total number of OCPs depend on the models. Each OCP's link: To view more information or configure individual OCPs, click the desired OCP's index number, which is C1, C2 and the like, to go to its setup page. Each OCP's power data: OCP data from top to bottom includes: ...
Page 162: Dashboard - Alerted Sensors
Chapter 6: Using the Web Interface Dashboard - Alerted Sensors When any internal sensors or environmental sensor packages connected to the PX3 enter an abnormal state, the Alerted Sensors section in the Dashboard show them for alerting users. This section also lists tripped circuit breakers or blown fuses, if available.
Page 163 Chapter 6: Using the Web Interface  1 Warned: 1 'numeric' sensor enters the warning state. List of alerted sensors: Two icons are used to indicate various sensor states. Icons Sensor states For numeric sensors:  above upper warning  below lower warning For numeric sensors: ...
Page 164: Dashboard - Inlet History
Chapter 6: Using the Web Interface Dashboard - Inlet History The power waveform for the inlet helps you observe whether there were abnormal events within the past tens of minutes. The default is to show the inlet's active power data. You can have it show the waveform of other inlet power data.
Page 165: Dashboard - Alarms
Chapter 6: Using the Web Interface Inlet selection on multi-inlet models: If your PDU is a multi-inlet model, you can have one or multiple inlets show their power waveforms by selecting the checkbox(es) of the desired inlet(s).  When multiple inlets are displayed, their waveform colors differ. You can identify each waveform according to the colors of the selected inlet checkboxes as illustrated below.
Page 166 Chapter 6: Using the Web Interface This table explains each column of the alarms list. Field Description Name The customized name of the Alarm action. Reason The first event that triggers the alert. First Appearance The date and time when the event indicated in the Reason column occurred for the first time.
Page 167: Pdu
Chapter 6: Using the Web Interface The PX3 device's generic information and PDU-level global settings are available on the PDU page. Menu To open the PDU page, click 'PDU' in the (on page 132). Device information shown:  Firmware version ...
Page 168 Chapter 6: Using the Web Interface In the following table, those fields marked with * are available on an outlet-switching capable model only. Field Function Note Name Customizes the device name. PX3 Latching Relay Behavior *Relay behavior Selects an operating mode to on power loss determine the latching relay behavior page 150).
Page 169 The default is to enable it.  The device's altitude is associated Altitude Specifies the PX3 device's altitude with the altitude correction factor. above sea level when a Raritan's DPX Altitude Correction Factors differential air pressure sensor is (on page 684). attached.
Page 170 Chapter 6: Using the Web Interface To reset ALL active energy counters: An active energy reading is a value of total accumulated energy, which is never reset, even if the power fails or the PX3 is reset. However, you can manually reset this reading to restart the energy accumulation process.
Page 171 Chapter 6: Using the Web Interface Internal Beeper State The PDU page indicates the internal beeper state. Available beeper states: States Description The beeper is turned off. Active The beeper is turned on. "Activation Reason" is displayed, indicating why the beeper sounds an alarm. For example, if the beeper is turned on because of a specific event rule "XXX,"...
Page 172: Px3 Latching Relay Behavior
Chapter 6: Using the Web Interface PX3 Latching Relay Behavior PX3 incorporates latching relays in models with outlet switching. Unlike non-latching relays, latching relays do NOT require power to keep their contacts closed. PX3 outlet switching can be configured to operate as a true latching relay or to simulate a non-latching relay.
Page 173: Initialization Delay Use Cases
Chapter 6: Using the Web Interface If you are configuring an individual outlet on Individual Outlet Pages page 165), there is one more outlet state option. Additional Function option PDU defined Follows the global outlet state setting, which is set (xxx) (on page 145).
Page 174: Z Coordinate Format
Chapter 6: Using the Web Interface Z Coordinate Format You can use either the number of rack units or a descriptive text to describe the vertical locations (Z coordinates) of environmental sensors and actuators, which are configured on the Individual Sensor/Actuator Pages (on page 188).
Page 175: Time Units
Chapter 6: Using the Web Interface Time Units If you choose to type a new value in the time-related fields, such as the Inrush Guard Delay field, you must add a time unit after the numeric value. For example, you can type '15 s' for 15 seconds. Note that different fields have different range of valid values.
Page 176: Power Supply Sensor (For Ix7™ Only)
Chapter 6: Using the Web Interface 2. Click the Thresholds title bar at the bottom of the page to display thresholds. 3. Click the desired sensor (required), and then click Edit Thresholds. 4. Make changes as needed.  To enable any threshold, select the corresponding checkbox. ...
Page 177: Inlet
Chapter 6: Using the Web Interface State Description fault The iX7 controller cannot receive power from its ™ inlet because of a power failure on the inlet or a broken 12V power supply. Instead it receives power Power-Sharing from another iX7 PDU.
Page 178 Chapter 6: Using the Web Interface  Dashboard - Inlet Inlet's power waveform, which is the same as History (on page 142) To customize the inlet's name: 1. Click Edit Settings. 2. Type a name for the inlet.  For example, you can name it to identify the power source. 3.
Page 179: Configuring A Multi-Inlet Model
Chapter 6: Using the Web Interface 2. Click the desired sensor (required), and then click Edit Thresholds. 3. Make changes as needed.  To enable any threshold, select the corresponding checkbox.  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see...
Page 180: Outlets
Chapter 6: Using the Web Interface  If disabling an inlet will result in all inlets being disabled, a confirmation dialog appears, indicating that all inlets will be disabled. Then click Yes to confirm this operation or No to abort After disabling any inlet, the following information or features associated with the disabled one are no longer available: ...
Page 181: Available Data Of The Outlets Overview Page
Chapter 6: Using the Web Interface  Perform actions on all or multiple outlets simultaneously by using the setup/power-control icons on the top-right corner. Note that only outlet-switching capable models show the power-control buttons, and you must have the Switch Outlet permission for performing outlet-switching operations.
Page 182: Setting Outlet Power-On Sequence And Delay
Chapter 6: Using the Web Interface PX3-1000 series does NOT support the following features. To configure global outlet settings or perform the load-shedding command: 1. Click to show a list of commands. 2. Select the desired command. Note that only outlet-switching capable models show the commands marked with * in the table.
Page 183 Chapter 6: 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. Resets active energy readings > Reset Active Energy of selected outlets.  Only users with the "Admin" role assigned can reset active energy readings.
Page 184 Chapter 6: Using the Web Interface Available Data of the Outlets Overview Page All of the following outlet data is displayed on the outlets overview page based on your selection. To show or hide specific data, click . See Outlets (on page 158).
Page 185: Setting Non-Critical Outlets
Chapter 6: Using the Web Interface Next time when power cycling the PX3, it will turn on all outlets based on the new outlet order. The new order also applies when performing the power-on or power-cycling operation on partial outlets. To set a power-on delay for any outlet: 1.
Page 186: Load Shedding Mode
Chapter 6: Using the Web Interface Load Shedding Mode When a UPS supplying power to the PX3 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.
Page 187: Individual Outlet Pages
Chapter 6: Using the Web Interface Tip: To make the Non Critical column appear on the Outlets page. See (on page 158) or Outlets Available Data of the Outlets Overview Page (on page 162). To exit from the load shedding mode: 1.
Page 188 In addition, you can perform the following operations on this outlet page. Note that only outlet-switching capable models show the power-control buttons, and you must have the Switch Outlet permission for performing outlet-switching operations. Therefore, PX3-1000 series does not support the following power control operation. To power control this outlet: 1.
Page 189 Chapter 6: Using the Web Interface Tip: To switch an outlet using the front panel display, see Power Control. To configure this outlet: 1. Click Edit Settings. 2. Configure available fields. Note that the fields marked with * are only available on outlet-switching capable models.
Page 190 Chapter 6: Using the Web Interface Other operations:  You can go to another outlet's data/setup page by clicking the outlet selector on the top-left corner.  You can go to the associated Inlet's or overcurrent protector's data pages by clicking the Inlet or Overcurrent Protector links in the Details section.
Page 191 Chapter 6: Using the Web Interface Field Description Inlet This information is useful when there are multiple inlets on your PDU. Inlet associated with this outlet Overcurrent Protector This information is available only when your PX3 has overcurrent protectors. Overcurrent protector associated with this outlet Power-Off Period Options for Individual Outlets There are two options for setting the power-off period during the power...
Page 192: Ocps
Chapter 6: Using the Web Interface OCPs This page is available only when your PX3 has overcurrent protectors, such as circuit breakers. The OCPs page lists all overcurrent protectors as well as their status. If any OCP trips or its current level enters the alarmed state, it is Yellow- or Red-Highlighted Sensors highlighted in red or yellow.
Page 193 Chapter 6: 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 these two thresholds for current levels. ...
Page 194: Individual Ocp Pages
Chapter 6: Using the Web Interface Individual OCP Pages An OCP's data/setup page is opened after clicking any OCP's name on the OCPs or Dashboard page. See OCPs (on page 170) or Dashboard page 135). General OCP information: Field Description Label This OCP's physical number Status...
Page 195 Chapter 6: Using the Web Interface To view this OCP's power waveform: This OCP's RMS current data in waveform is shown in the Overcurrent Protector History section. To configure this OCP's threshold settings: 1. Click the Thresholds title bar at the bottom of the page to display the threshold data.
Page 196 Chapter 6: Using the Web Interface Tip: To configure thresholds for multiple OCPs at a time, see OCPs page 170). Other operations:  You can go to another OCP's data/setup page by clicking the OCP selector on the top-left corner. ...
Page 197: Peripherals
Chapter 6: Using the Web Interface Peripherals If there are Raritan environmental sensor packages connected to the Connecting PX3, they are listed on the Peripherals page. See Environmental Sensor Packages (on page 53). An environmental sensor package comprises one or some of the following sensors/actuators: ...
Page 198 Chapter 6: Using the Web Interface  Go to an individual sensor's or actuator's data/setup page by clicking its name. If wanted, you can resort the list by clicking the desired column header. Sorting a List (on page 134). Sensor/actuator overview on this page: If any sensor enters the alarmed state, it is highlighted in yellow or red.
Page 199 Chapter 6: Using the Web Interface Column Description Serial Number This is the serial number printed on the sensor package's label. It helps to identify your Raritan Finding the Sensor's Serial sensors/actuators. See Number (on page 184). Position The data indicates where this sensor or actuator is located in the sensor chain.
Page 200 Chapter 6: Using the Web Interface  The management action triggers a "Manage peripheral device" multiple dialog. Simply click Manage if you are managing sensors/actuators.  If you are managing only sensor/actuator, you can choose to assign an ID number by selecting "Manually select a sensor Managing One Sensor or Actuator number."...
Page 201 Chapter 6: Using the Web Interface 2. Click the desired sensor type (required), and then click Edit Thresholds. 3. Make changes as needed.  To enable any threshold, select the corresponding checkbox.  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see...
Page 202 Chapter 6: Using the Web Interface Yellow- or Red-Highlighted Sensors The PX3 highlights those sensors that enter the abnormal state with a yellow or red color. Note that numeric sensors can change colors only after you have enabled their thresholds. Tip: When an actuator is turned ON, it is also highlighted in red for drawing attention.
Page 203 Chapter 6: Using the Web Interface Sensor status Color States shown in Description the interface alarmed State sensors enter the abnormal state. Alarmed  Circuit breaker trips. OCP alarm Open -- OR --  Fuse blown. If you have connected a Schroff LHX/SHX heat exchanger, when any ®...
Page 204: Sensor/Actuator States
Chapter 6: Using the Web Interface  Sensor/Actuator States They show one of the managed states. See (on page 182).  For managed 'numeric' sensors, their readings are retrieved and displayed. If any numeric sensor is disconnected or its reading cannot be retrieved, it shows "unavailable"...
Page 205 Note that for a contact closure sensor, the normal state depends on the normal setting you have configured. Refer to the Environmental Sensors Guide or Online Help for detailed information, which is available on Support page http://www.raritan.com/support/ Raritan's Managed actuator states: State Description The actuator is turned on.
Page 206: Finding The Sensor's Serial Number
Chapter 6: Using the Web Interface Finding the Sensor's Serial Number A DPX environmental sensor package includes a serial number tag on the sensor cable. A DPX2, DPX3 or DX sensor package has a serial number tag attached to its rear side. The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the PX3.
Page 207: Identifying The Sensor Position And Channel
For example, Port 1, Chain Position 2  If a Raritan DPX3-ENVHUB4 sensor hub is involved, the hub port information is also indicated for DPX2, DPX3 and DX series, but NOT indicated for DPX series. For example, Hub Port 3 ...
Page 208: Managing One Sensor Or Actuator
Chapter 6: Using the Web Interface Example Physical position Connected to the sensor port #1. Port 1  Connected to the sensor port #1. Port 1,  The sensor/actuator is the 2nd channel of the sensor package. Channel 2  Connected to the sensor port #1. Port 1, ...
Page 209 Otherwise, it shows the word "unused." 3. Click Manage. Special note for a Raritan humidity sensor: A Raritan humidity sensor is able to provide two measurements - relative and absolute humidity values.  A relative humidity value is measured in percentage (%).
Page 210: Individual Sensor/Actuator Pages
Chapter 6: Using the Web Interface However, only relative humidity sensors are "automatically" managed if the automatic management function is enabled. You must "manually" manage absolute humidity sensors as needed. Note that relative and absolute values of the same humidity sensor do NOT share the same ID number though they share the same serial number and position.
Page 211 Chapter 6: Using the Web Interface 2. Select or deselect Use Default Thresholds according to your needs.  To have this sensor follow the default threshold settings configured for its sensor type, select the Use Default Thresholds checkbox. The default threshold settings are configured on the page of Peripherals (on page 175).
Page 212 Chapter 6: Using the Web Interface To set up a sensor's or actuator's physical location and additional settings: 1. Click Edit Settings. 2. Make changes to available fields, and then click Save. Fields Description Binary Sensor This field is available for a contact closure sensor only. Subtype Determine the sensor type of your contact closure detector.
Page 213 Chapter 6: Using the Web Interface To view a numeric sensor's readings waveform: This sensor's data within the past tens of minutes is shown in the waveform diagram. Note that only a numeric sensor has this diagram. State sensors and actuators do not show such data. To turn on or off an actuator: 1.
Page 214: Sensor/Actuator Location Example
Chapter 6: Using the Web Interface 2. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on. Other operations: You can go to another sensor's or actuators's data/setup page by clicking the selector on the top-left corner.
Page 215: Feature Port
Power CIM This type represents one of the following Raritan products:  Raritan power CIM, D2CIM-PWR. This CIM is used to connect the PX3 to the Raritan digital KVM switch -- Dominion KX II / III.  Dominion KSX II...
Page 216: Asset Strip
Chapter 6: Using the Web Interface When the PX3 detects the connection of any listed device, it replaces 'Feature Port' in the menu with that device's name and shows that device's data/settings instead. See Asset Strip (on page 195), External Beeper Schroff LHX/SHX Power CIM...
Page 217: Power Cim
Miscellaneous (on page 332). Asset Strip After connecting and detecting Raritan asset management strips (asset strips), the PX3 shows 'Asset Strip' in place of 'Feature Port' in the menu. Note: For connection instructions, see Connecting Asset Management (on page 72).
Page 218 Chapter 6: Using the Web Interface Field Description Name Name for this asset strip assembly. Number of Rack Total of available tag ports on this asset strip Units assembly, ranging between 8 and 64.  For the current generation of asset strips, which show the suffix "G3"...
Page 219 Chapter 6: Using the Web Interface For color settings, there are two ways to set the color.  Click a color in the color palette.  Type the hexadecimal RGB value of the color, such as #00FF00. 3. Click Ok. The rack unit numbering and LED color settings are immediately updated on the Rack Units list illustrated below.
Page 220 Chapter 6: Using the Web Interface To customize a single rack unit's settings: You can make a specific rack unit's LED behave differently from the others on the asset strip, including the LED light and color. 1. Click the desired rack unit on the Rack Units list. The setup dialog for the selected one appears.
Page 221 Chapter 6: 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.  : The LED stays lit. ...
Page 222 Chapter 6: Using the Web Interface 2. All tag ports of the blade extension strip are listed below it. Their port numbers are displayed in the Slot column.  To hide the blade extension slots list, click...
Page 223 Chapter 6: Using the Web Interface To customize asset IDs on programmable asset tags: You can customize asset IDs only when the asset tags are "programmable" ones. Non-programmable tags do not support this feature. In addition, you can also customize the ID of a blade extension strip.
Page 224 Chapter 6: Using the Web Interface  An asset ID contains up to 12 characters that comprise only numbers and/or UPPER CASE alphabets. Lower case alphabets are NOT accepted. 3. Verify the correctness of customized asset IDs and modify as needed.
Page 225 Chapter 6: Using the Web Interface Asset Strip Automatic Firmware Upgrade After connecting the asset strip to the PX3, it automatically checks its own firmware version against the version of the asset strip firmware stored in the PX3 firmware. If two versions are different, the asset strip automatically starts downloading the new firmware from the PX3 to upgrade its own firmware.
Page 226 Chapter 6: Using the Web Interface Schroff LHX/SHX You must enable the LHX/SHX support for the PX3 to detect the presence of a supported Schroff LHX/SHX heat exchanger. See Miscellaneous ® (on page 332). After enabling the LHX/SHX support and connecting a supported Schroff ®...
Page 227 Chapter 6: Using the Web Interface For the functionality of this icon on the top-right corner, see Feature Port (on page 193). To view the LHX/SHX device state: The Operation State field indicates whether the device is operating fine, and the Switch State field indicates its power status. If the device does not operate properly, such as some sensor failure, it shows "critical"...
Page 228 Chapter 6: Using the Web Interface Tip: You can also create event rules to notify you of the warning or critical levels. See (on page 272). Event Rules and Actions To view sensor alerts and LHX event log: Remote alert acknowledgment is supported by the LHX-20 and LHX-40. The SHX-30 does not support this feature.
Page 229: User Management
Chapter 6: Using the Web Interface Power CIM After connecting and detecting a Raritan power CIM, the PX3 shows 'Power CIM' in place of 'Feature Port' in the menu. See Dominion KX II / III Configuration (on page 696) or...
Page 230: Creating Users
Chapter 6: Using the Web Interface Creating Users All users must have a user account, containing the login name and password. Multiple users can log in simultaneously using the same login name. To add users, choose User Management > Users > Note that you must enter information in the fields showing the message 'required.' User information:...
Page 231 Chapter 6: Using the Web Interface Field/setting Description Force password When selected, a password change request change on next automatically appears when next time the user login logs in. Changing Your Password For details, see page 128). SSH: You need to enter the SSH public key only if the public key authentication Changing SSH Settings for SSH is enabled.
Page 232 Chapter 6: Using the Web Interface Field/setting Description Password, Type the authentication password if the 'Same as User Password' checkbox is deselected. Confirm Password The password must consist of 8 to 32 ASCII printable characters.  Privacy Password: This section is configurable only when 'Authentication &...
Page 233 Chapter 6: 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 Note: Users can change the measurement units at any time by setting their own preferences.
Page 234: Editing Or Deleting Users
Chapter 6: Using the Web Interface Editing or Deleting Users To edit or delete users, choose User Management > Users to open the Users page, which lists all users. In the Enabled column:  : The user is enabled.  : The user is disabled.
Page 235: Creating Roles
Chapter 6: Using the Web Interface Creating Roles A role is a combination of permissions. Each user must have at least one role. The PX3 provides two built-in roles. The Operator role is assigned to a Creating Users newly-created user account per default. See (on page 208).
Page 236: Editing Or Deleting Roles
Chapter 6: Using the Web Interface 5. To select any privilege requiring the argument setting, click to select the desired arguments.  For example, on an outlet-switching capable model, you can specify the outlets that are allowed to be switched on/off for the 'Switch Outlet' privilege as shown below.
Page 237: Setting Your Preferred Measurement Units
Chapter 6: Using the Web Interface Tip: To delete only one role, you can simply click that user without making the checkboxes appear. See the above procedure. 2. Select one or multiple roles.  To select all roles, except for the Admin role, select the top-most checkbox in the header row.
Page 238 Chapter 6: Using the Web Interface Setting Default Measurement Units Default measurement units are applied to all PX3 user interfaces across all users, including users accessing the PX3 via external authentication servers. For a list of affected user interfaces, see User Interfaces Showing Default Units (on page 216).
Page 239: Device Settings
Chapter 6: Using the Web Interface Device Settings Menu Click 'Device Settings' in the (on page 132), and the following submenu displays. Menu command Submenu command Refer to... Network Configuring Network Settings (on page 218) Changing HTTP(S) Settings Network Services HTTP (on page 240) Configuring SNMP Settings...
Page 240 Chapter 6: Using the Web Interface * The availability of "Front Panel" depends on the model. Configuring Network Settings Configure wired, wireless, and Internet protocol-related settings on the connecting the PX3 to your network Network page after (on page 24). You can enable both the wired and wireless networking on the PX3 so that it has multiple IP addresses -- wired and wireless IP.
Page 241 Chapter 6: Using the Web Interface Note: If the device's cascading mode is set to 'Bridging' or its role is set to 'Slave' in the port forwarding mode, the wireless settings will be disabled. 5. To configure the ETHERNET (or ETH1/ETH2) interface settings, see Ethernet Interface Settings (on page 221).
Page 242 Chapter 6: Using the Web Interface Field/setting Description IP Auto Select the method to configure IPv4 settings. Configuration  DHCP: Auto-configure IPv4 settings via DHCP servers.  Static: Manually configure the IPv4 settings.  DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements: ...
Page 243 Chapter 6: Using the Web Interface Field Description  Cascading Multiple PX3 Devices for Sharing Ethernet Connectivity (on page 38)  Setting the Cascading Mode (on page 231) DNS Resolver Determine which IP address is used when the Reference DNS resolver returns both IPv4 and IPv6 addresses.
Page 244 Chapter 6: Using the Web Interface Other Ethernet settings: Field Description Speed Select a LAN speed.  Auto: System determines the optimum LAN speed through auto-negotiation.  10 MBit/s: Speed is always 10 Mbps.  100 MBit/s: Speed is always 100 Mbps. ...
Page 245 Chapter 6: Using the Web Interface Field/setting Description connected or whether it is supported. Type the name of the wireless access point (AP) SSID Force AP BSSID If the BSSID is available, select this checkbox BSSID Type the MAC address of an access point Enable High Enable or disable 802.11n protocol.
Page 246 Chapter 6: Using the Web Interface  Available settings for the CA Certificate: Field/setting Description Enable verification Select this checkbox for the PX3 to verify the of TLS certificate validity of the TLS certificate that will be installed. chain  For example, the PX3 will check the certificate's validity period against the system time.
Page 247 Chapter 6: Using the Web Interface  DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements:  Consists of alphanumeric characters and/or hyphens  Cannot begin or end with a hyphen  Cannot contain more than 63 characters ...
Page 248 Chapter 6: Using the Web Interface Wireless LAN Diagnostic Log The PX3 provides a diagnostic log for inspecting connection errors that occurred over the wireless network interface. The information is useful for technical support. Note that the WLAN Diagnostic Log shows data only after the Network Interface is set to Wireless.
Page 249 Chapter 6: Using the Web Interface Static Route Examples This section describes two static route examples: IPv4 and IPv6. Both examples assume that two network interface controllers (NIC) have been installed in one network server, leading to two available subnets, and IP forwarding has been enabled.
Page 250 Chapter 6: Using the Web Interface In this example, NIC-2 (192.168.100.88) is the next hop router for your PX3 to communicate with any device in the other subnet 192.168.200.0. In the IPv4 "Static Routes" section, you should specify:...
Page 251 Chapter 6: Using the Web Interface Tip: If you have configured multiple static routes, you can click on any route and then make changes, use to re-sort the priority, or click to delete it. IPv6 example:  fd07:2fa:6cff:2405::30 Your PX3: ...
Page 252 Chapter 6: Using the Web Interface In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your PX3 to communicate with any device in the other subnet fd07:2fa:6cff:1111::0. In the IPv6 "Static Routes" section, you should specify: Tip: If you have configured multiple static routes, you can click on any route and then make changes, use to re-sort the priority, or click...
Page 253 Chapter 6: Using the Web Interface Interface name Description set to the bridging mode, select this interface name instead of the Ethernet interface. ETH1 When another wired network is connected to the ETH1 port of your PX3, select this interface name. ETH2 When another wired network is connected to the ETH2 port of your PX3, select this interface name.
Page 254 R/STP enabled if using a cascade loop (bridging mode) or else network loops may occur. Online USB-cascading information: For more information on the USB-cascading configuration, see the Cascading Guide Support , which is available from Raritan website's page http://www.raritan.com/support/...
Page 255 Chapter 6: Using the Web Interface Overview of the Cascading Modes You must apply a cascading mode to the cascading configuration. See Setting the Cascading Mode (on page 231). Overview:  The Bridging mode supports the wired network only, while the Port Forwarding mode supports both wired and wireless networks.
Page 256 Chapter 6: Using the Web Interface  "Port Forwarding" mode: In this mode, the DHCP server communicates with the master device alone and assigns only one IP address. All slave devices share the same IP address as the master device. You must specify a 5XXXX port number (where X is a number) when remotely accessing any slave Port Number Syntax device via the shared IP address.
Page 257 Chapter 6: Using the Web Interface Position Master device Slave 1 Slave 2 Slave 3 Slave 4 Slave 5 Slave 6 Slave 7 For example, to access the Slave 4 device via Modbus/TCP, the port Port Forwarding Examples number is 50604. See (on page 236) for further illustrations.
Page 258 Slave device: Assign proper 5NNXX port numbers. The Port Forwarding mode is applied to a USB-cascading Assumption: configuration comprising three Raritan devices. The IP address is 192.168.84.77. Master device: Position code for the master device is '00' so each port number is 5NN00 as listed below.
Page 259 Chapter 6: 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 260 Chapter 6: Using the Web Interface  To access Slave 2 via HTTP, the IP address is: http://192.168.84.77:50102/  To access Slave 2 via SSH, the command is: ssh -p 50202 192.168.84.77 Adding, Removing or Swapping Cascaded Devices Change the cascading mode first before adding any device to a cascading chain, or before disconnecting a cascaded device from the chain.
Page 261: Configuring Network Services
Service Advertising Enabling Service Advertising (on page 246) Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
Page 262 Chapter 6: Using the Web Interface Changing HTTP(S) Settings HTTPS uses Transport Layer Security (TLS) technology to encrypt all traffic to and from the PX3 so it is a more secure protocol than HTTP. The PX3 supports TLS By default, any access to the PX3 via HTTP is automatically redirected to HTTPS.
Page 263 Chapter 6: Using the Web Interface Configuring SNMP Settings You can enable or disable SNMP communication between an SNMP manager and the PX3 device. Enabling SNMP communication allows the manager to retrieve and even control the power status of each outlet. Besides, you may need to configure the SNMP destination(s) if the built-in "System SNMP Notification Rule"...
Page 264 Chapter 6: Using the Web Interface a. Click the Download MIBs title bar to show the download links. Downloading SNMP b. Click the PDU2-MIB download link. See (on page 360). 6. Click Save. Configuring SMTP Settings The PX3 can be configured to send alerts or event messages to a specific administrator by email.
Page 265 Chapter 6: Using the Web Interface Field Description User Name, Type a user name and password for authentication after selecting the above checkbox. Password  The length of user name and password ranges between 4 and 64. Case sensitive.  Spaces are not allowed for the user name, but allowed for the password.
Page 266 Chapter 6: Using the Web Interface Special note for AES ciphers: The PX3 device's SSL/TLS-based protocols, including SMTP over StartTLS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between the PX3 and the client (such as a web browser), which is impacted by the cipher priority of the PX3 and the client's cipher availability/settings.
Page 267 Chapter 6: Using the Web Interface 3. To use a different port, type a new port number. 4. Click Save. Changing Modbus Settings You can enable or disable the Modbus/TCP access to the PX3, set it to the read-only mode, or change the TCP port. To change the Modbus/TCP settings: 1.
Page 268 Chapter 6: Using the Web Interface Enabling Service Advertising The PX3 advertises all enabled services that are reachable using the IP network. This feature uses DNS-SD (Domain Name System-Service Discovery) and MDNS (Multicast DNS). The advertised services are discovered by clients that have implemented DNS-SD and MDNS. The advertised services include the following: ...
Page 269: Configuring Security Settings
Chapter 6: Using the Web Interface Configuring Security Settings The PX3 provides tools to control access. You can enable the internal firewall, create firewall rules, and set login limitations. In addition, you can create and install the certificate or set up external authentication servers for access control.
Page 270 Chapter 6: Using the Web Interface Note: Valid IPv4 addresses range from 0.0.0.0 through 255.255.255.255. To configure IPv4 access control rules: 1. Choose Device Settings > Security > IP Access Control. 2. Select the Enable IPv4 Access Control checkbox to enable IPv4 access control rules.
Page 271 Chapter 6: Using the Web Interface  You can select any existing rule and then click to change its priority. 7. Click Save. The rules are applied. To configure IPv6 access control rules: 1. On the same page, select the Enable IPv6 Access Control checkbox to enable IPv6 access control rules.
Page 272 Chapter 6: Using the Web Interface Creating Role Access Control Rules Role-based access control rules are similar to IP access control rules, except they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses.
Page 273 Chapter 6: Using the Web Interface INSERT a rule between two rules  Select the rule above which you want to insert a new rule. For example, to insert a rule between rules #3 and #4, select #4.  Click Insert Above. ...
Page 274 IPv6 rules are not saved. Setting Up an SSL/TLS Certificate Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
Page 275 Chapter 6: Using the Web Interface Creating a CSR Follow this procedure to create the CSR for your PX3 device. Note that you must enter information in the fields showing the message 'required.' To create a CSR: 1. Choose Device Settings > Security > SSL Certificate. 2.
Page 276 Chapter 6: Using the Web Interface Field Do this Challenge, Type a password. The password is used to protect the certificate or CSR. This information is optional. Confirm Challenge The value should be 4 to 64 characters long. Case sensitive. 3.
Page 277 Chapter 6: Using the Web Interface Creating a Self-Signed Certificate When appropriate certificate and key files for the PX3 device are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate. Note that you must enter information in the fields showing the message 'required.' To create and install a self-signed certificate: 1.
Page 278 Chapter 6: Using the Web Interface 4. Once complete, do the following: a. Double check the data shown in the New SSL Certificate section. b. If correct, click "Install Key and Certificate" to install the self-signed certificate and private key. Tip: To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section.
Page 279 Active SSL Certificate section. Setting Up External Authentication Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather...
Page 280 Chapter 6: Using the Web Interface For security purposes, users attempting to log in to the PX3 must be authenticated. The PX3 supports the following authentication mechanisms:  Local user database on the PX3  Lightweight Directory Access Protocol (LDAP) ...
Page 281 Chapter 6: Using the Web Interface Special note about the AES cipher: The PX3 device's SSL/TLS-based protocols, including LDAPS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between the PX3 and the client (such as a web browser), which is impacted by the cipher priority of the PX3 and the client's cipher availability/settings.
Page 282 Chapter 6: Using the Web Interface  If using a Microsoft Active Directory server, consult your AD administrator for the name of the Active Directory Domain.  Bind Distinguished Name (DN) and password (if anonymous bind is NOT used)  The Base DN of the server (used for searching for users) ...
Page 283 Chapter 6: Using the Web Interface Field/setting Description Type of LDAP Server Choose one of the following options:  OpenLDAP  Microsoft Active Directory. Active Directory is an implementation of LDAP/LDAPS directory services by Microsoft for use in Windows environments. Security Determine whether you would like to use Transport Layer Security (TLS) encryption, which allows the PX3 to communicate securely with...
Page 284 Chapter 6: Using the Web Interface Field/setting Description Bind DN Required after deselecting the Anonymous Bind checkbox. Distinguished Name (DN) of the user who is permitted to search the LDAP directory in the defined search base. Bind Password, Required after deselecting the Anonymous Bind checkbox. Confirm Bind Enter the Bind password.
Page 285 Chapter 6: Using the Web Interface To duplicate LDAP/LDAPS server settings: If you have added any LDAP/LDAPS server to the PX3, and the server you will add shares identical settings with an existing one, the most convenient way is to duplicate that LDAP/LDAPS server's data and then revise the IP address/host name.
Page 286 Chapter 6: Using the Web Interface Field/setting Description Authentication Port, The default are standard ports -- 1812 and 1813. Accounting Port To use non-standard ports, type a new port number. Timeout This sets the maximum amount of time to establish contact with the Radius server before timing out.
Page 287 Chapter 6: Using the Web Interface Managing External Authentication Settings Choose Device Settings > Security > Authentication to open the Authentication page, where you can:  Enable both the external and local authentication  Edit or delete a server  Resort the access order of servers ...
Page 288 Chapter 6: Using the Web Interface 2. Select the following checkbox. Then the PX3 always tries external authentication first. Whenever the external authentication fails, the PX3 switches to local authentication. 3. Click Save. To disable external authentication: 1. In the Authentication Type, select Local. 2.
Page 289 Chapter 6: Using the Web Interface Tip: If any user blocking event occurs, you can unblock that user manually by using the "unblock" CLI command over a local connection. (on page 528). Unblocking a User To set limitations for login timeout and use of identical login names: 1.
Page 290 Chapter 6: Using the Web Interface To force users to create strong passwords: 1. Select the 'Enabled' checkbox of Strong Passwords to activate the strong password feature. The following are the default settings: Minimum length = 8 characters Maximum length = 32 characters At least one lowercase character = Required...
Page 291: Setting The Date And Time
Chapter 6: Using the Web Interface Login manner after enabling the service agreement: After the Restricted Service Agreement feature is enabled, the agreement's content is displayed in the login screen. Do either of the following, or the login fails:  In the web interface, select the checkbox labeled "I understand and accept the Restricted Service Agreement."...
Page 292 Chapter 6: Using the Web Interface Customize the date and time  Select User Specified Time.  Type values in the Date field using the yyyy-mm-dd format, or click to select Calendar a date. For details, see (on page 270). ...
Page 293 Chapter 6: Using the Web Interface Button Function dates Click a date. (01-31) Today Select today. Clear Clear the entry, if any, in the Date field. Close Close the calendar. Windows NTP Server Synchronization Solution The NTP client on the PX3 follows the NTP RFC so the PX3 rejects any NTP servers whose root dispersion is more than one second.
Page 294: Event Rules And Actions
Chapter 6: Using the Web Interface Event Rules and Actions A benefit of the product's intelligence is its ability to notify you of or react to a change in conditions. This event notification or reaction is an "event rule." An event rule consists of two parts: ...
Page 295 Chapter 6: Using the Web Interface Note: When creating scheduled actions, available actions are less than usual because it is meaningless to schedule certain actions like "Alarm," "Log event message," "Send email," "Syslog message" and the like. 2. Click to schedule the desired action.
Page 296 Chapter 6: Using the Web Interface Event rule configuration illustration: 1. Choose Device Settings > Event Rules > 2. Click the Event field to select an event type.  <Any sub-event> means all events shown on the list.  <Any Numeric Sensor> means all numeric sensors of the PX3, including internal and environmental sensors.
Page 297 Chapter 6: Using the Web Interface 6. In this example, 'Above upper critical threshold' is selected because we want the PX3 to react only when the selected temperature sensor's reading enters the upper critical range. A "Trigger condition" field appears, requiring you to define the "exact" condition related to the "upper critical"...
Page 298 Chapter 6: Using the Web Interface Radio buttons for different events: According to the event you select, the "Trigger condition" field containing three radio buttons may or may not appear. Event types Radio buttons Numeric sensor Available radio buttons include "Asserted," threshold-crossing "Deasserted"...
Page 299 Chapter 6: Using the Web Interface Event types Radio buttons  Link state is up: The PX3 takes the action Network interface only when the network link state changes link state from down to up.  Link state is down: The PX3 takes the action only when the network link state changes from up to down.
Page 300 Chapter 6: Using the Web Interface Event types Radio buttons  Unreachable: The PX3 takes the action only Server reachability when any specified server becomes inaccessible.  Reachable: The PX3 takes the action only when any specified server becomes accessible. ...
Page 301 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Asset Management > State State of asset strip [STRIPID] ('[STRIPNAME]') changed to '[STATE]'. Asset Management > Rack Unit Asset tag with ID '[TAGID]' connected Asset tag with ID '[TAGID]' >...
Page 302 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Card Reader Management > Card of type '[SMARTCARDTYPE]' with Card removed ID '[SMARTCARDID]' removed. Device > System started System started. Device >...
Page 303 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Device > Network interface link The [IFNAME] network interface link is The [IFNAME] network interface state is up now up. link is now down.
Page 304 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Peripheral Device Slot > * > Peripheral device Peripheral device Numeric Sensor > Unavailable '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot '[EXTSENSORSLOT]' unavailable.
Page 305 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE upper warning threshold '[INLET]' asserted 'above upper '[INLET]' deasserted 'above upper warning'. warning'. Inlet > * > Sensor > * > Below Sensor '[INLETSENSOR]' on inlet Sensor '[INLETSENSOR]' on inlet lower warning threshold...
Page 306 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Outlet > * > Sensor > * > Below Sensor '[OUTLETSENSOR]' on outlet Sensor '[OUTLETSENSOR]' on lower warning threshold '[OUTLET]' asserted 'below lower outlet '[OUTLET]' deasserted 'below warning'.
Page 307 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Overcurrent Protector > * > Sensor '[OCPSENSOR]' on overcurrent Sensor '[OCPSENSOR]' on Sensor > * > Above upper protector '[OCP]' asserted 'above overcurrent protector '[OCP]' warning threshold upper warning'.
Page 308: Webcam Management
Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE User Activity > * > User blocked User '[USERNAME]' from host '[USERIP]' was blocked. User Activity > * > Session Session of user '[USERNAME]' from timeout host '[USERIP]' timed out.
Page 309 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > Sensor > Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX at Unavailable [PORTTYPE] port '[PORTID]' [PORTTYPE] port '[PORTID]' unavailable.
Page 310 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > Sensor Failure A sensor failure (broken or short circuit) occurred on LHX at [PORTTYPE] port '[PORTID]' at sensor '[LHXSENSORID]'.
Page 311 Chapter 6: Using the Web Interface Available Actions The PX3 comes with three built-in actions, which cannot be deleted. You can create additional actions for responding to different events. Built-in actions:  System Event Log Action: This action records the selected event in the internal log when the event occurs.
Page 312 Chapter 6: Using the Web Interface Action Function Execute an action Creates a group of actions comprising existing Action Group group actions. See (on page 292). External beeper Enables or disables the connected external beeper, or causes it to enter an alarm cycle. External Beeper (on page 293).
Page 313 Chapter 6: Using the Web Interface Action Function Start/stop Lua script If you are a developer who can create a Lua script, you can upload it to the PX3, and have the PX3 automatically perform or stop the Start or script in response to an event.
Page 314 Chapter 6: Using the Web Interface  External beeper  Syslog message  Send email  Send SMS message  Internal beeper If no appropriate actions are available, create them first. a. To select any methods, select them one by one in the Available field.
Page 315 Chapter 6: Using the Web Interface 3. To select any action(s), select them one by one from the Available Actions list.  To select all available actions, click Select All. 4. To remove any action(s) from the Selected Actions field, click that action's ...
Page 316 If you have connected Raritan's asset strips to the PX3, you can also configure the PX3 to push the data to a server. Before creating this action, make sure that you have properly defined the destination servers and the data to be sent on the Data Push page.
Page 317 Chapter 6: Using the Web Interface 2. Select "Push out sensor readings" from the Action list. 3. Select a server or host which receives the asset strip data or sensor log in the Destination field.  If the desired destination is not available yet, go to the Data Push page to specify it.
Page 318 Chapter 6: Using the Web Interface Request LHX/SHX Maximum Cooling If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will Miscellaneous be available. See (on page 332). The "Request LHX/SHX Maximum Cooling" action applies the maximum cooling to the SHX-30 device only. The LHX-20 and LHX-40 devices do not support this feature.
Page 319 Overcurrent protector sensors, including RMS current and tripping state.  Peripheral device sensors, which can be any Raritan environmental sensor packages connected to the PX3, such as temperature or humidity sensors. An example of this action is available in the section titled...
Page 320 Chapter 6: Using the Web Interface  Syslog message  Send email  Send SMS message a. If no messaging actions are available, create them now. See Available Actions (on page 289). b. To select any methods, select them one by one in the Available field.
Page 321 Chapter 6: Using the Web Interface Tip: When intending to send a sensor report using custom messages, use the placeholder [SENSORREPORT] to report sensor readings. See (on page 309). Email and SMS Message Placeholders Send SMS Message You can configure SMS messages to be sent when an event occurs and can customize the message.
Page 322 Chapter 6: Using the Web Interface Send Snapshots via Email This option notifies one or multiple persons for the selected events by emailing snapshots or videos captured by a connected Logitech ® webcam. Operation: 1. Choose Device Settings > Event Rules > 2.
Page 323 Chapter 6: Using the Web Interface To send SNMP v2c notifications: 1. In the Notification Type field, select SNMPv2c Trap or SNMPv2c Inform. 2. For SNMP INFORM communications, leave the resend settings at their default or do the following: a. In the Timeout field, specify the interval of time, in seconds, after which a new inform communication is resent if the first is not received.
Page 324 Chapter 6: Using the Web Interface 4. For both SNMP TRAPS and INFORMS, enter the following as needed and then click OK to apply the settings: a. Host name b. Port number c. User ID for accessing the host -- make sure the User ID has the SNMPv3 permission.
Page 325 Chapter 6: Using the Web Interface  No script is available if you have not created or loaded it into the PX3. 5. To apply different arguments than the default, do the following. Note that the newly-added arguments will override this script's default arguments.
Page 326 Chapter 6: Using the Web Interface  Cycle Outlet: Cycles power to the selected outlet(s). 4. To specify the outlet(s) where this action will be applied, select them one by one from the Available Outlets list.  To add all outlets, click Select All. 5.
Page 327 Chapter 6: Using the Web Interface Syslog Message Use this action to automatically forward event messages to the specified syslog server. Determine the syslog transmission mechanism you prefer when setting it up - UDP, TCP or TLS over TCP. The PX3 may or may not detect the syslog message transmission failure. If yes, it will log this syslog failure as well as the failure reason in the Viewing or Clearing the Local Event Log event log.
Page 328 Chapter 6: Using the Web Interface Scheduling an Action An action can be regularly performed at a preset time interval instead of being triggered by a specific event. For example, you can make the PX3 report the reading or state of a specific sensor regularly by scheduling the "Send Sensor Report"...
Page 329 Chapter 6: Using the Web Interface Execution Frequency settings time 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 330 Chapter 6: Using the Web Interface Execution Frequency settings time This option requires three settings: Yearly  Month - January through December.  Day of month - 1 to 31.  Time - the value is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM/PM button.
Page 331 Chapter 6: Using the Web Interface Then the PX3 will send out an email containing the specified temperature sensor readings hourly every day. Whenever you want the PX3 to stop sending the temperature report, simply deselect the Enabled checkbox in the timer. Email and SMS Message Placeholders Actions of "Send email"...
Page 332 Chapter 6: Using the Web Interface Placeholder Definition [CIRCUITSENSOR] The circuit sensor name [CIRCUIT] The circuit identifier [CONFIGPARAM] The name of a configuration parameter [CONFIGVALUE] The new value of a parameter [DATETIME] The human readable timestamp of the event occurrence [DEVICEIP] The IP address of the device, the event occurred on [DEVICENAME]...
Page 333 Chapter 6: Using the Web Interface Placeholder Definition [OUTLETNAME] The outlet name Note: If any outlet does not have a name, neither an outlet name nor an outlet number will be shown in the custom message for it. Therefore, it is recommended to check the availability of all outlet names if intending to use this placeholder.
Page 334 Chapter 6: Using the Web Interface Placeholder Definition [SYSNAME] SysName as configured for SNMP [TIMEREVENTID] The id of a timer event The timestamp of the event occurrence [TIMESTAMP] [TRANSFERSWITCHREASON] The transfer reason [TRANSFERSWITCHSENSOR] The transfer switch sensor name [TRANSFERSWITCH] The transfer switch label [UMTARGETROLE] The name of a user management role, an action was applied on...
Page 335 Chapter 6: Using the Web Interface Sample Event Rules Sample PDU-Level Event Rule In this example, we want the PX3 to record the firmware upgrade failure in the internal log when it happens. The event rule involves:  Event: Device > Firmware update failed ...
Page 336 Chapter 6: Using the Web Interface  Any sensor reading or state returns to normal.  Any sensor becomes unavailable.  The active energy sensor is reset.  Any state sensor changes its state. For example, when the outlet 3's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again.
Page 337 Chapter 6: Using the Web Interface Sample Environmental-Sensor-Level Event Rule This section applies to outlet-switching capable models only. In this example, we want PX3 to activate the load shedding function when a contact closure sensor enters the alarmed state. This event rule requires creating a new action before creating the rule.
Page 338 Chapter 6: Using the Web Interface 6. Select "Alarmed" since we want the PX3 to respond when the selected contact closure sensor changes its state related to the "alarmed" state. 7. In the "Trigger condition" field, select the Alarmed/Open/On radio button so that the action is taken only when the contact closure sensor enters the alarmed state.
Page 339: Setting Data Logging
Chapter 6: Using the Web Interface Event selected Action included Outlet > Outlet 2 > Sensor > Outlet Cycle Outlet 1 State > On/Off > Both (trigger condition) (Switch outlets --> Cycle Outlet --> Outlet 1) A Note about Untriggered Rules In some cases, a measurement exceeds a threshold causing the PX3 to generate an alert.
Page 340: Configuring Data Push Settings
Chapter 6: Using the Web Interface 2. To enable the data logging feature, select the "Enable" checkbox in the General Settings section. 3. Type a number in the Measurements Per Log Entry field. Valid range is from 1 to 600. The default is 60. 4.
Page 341 Chapter 6: Using the Web Interface b. Type the URL or host name in the accompanying text box. 4. If selecting https, a CA certificate is required for making the connection. Click to install it. Then you can:  Click Show to view the certificate's content. ...
Page 342: Monitoring Server Accessibility
Chapter 6: Using the Web Interface Monitoring Server Accessibility You can monitor whether specific IT devices are alive by having the PX3 device continuously ping them. An IT device's successful response to the ping commands indicates that the IT device is still alive and can be remotely accessed.
Page 343 Chapter 6: Using the Web Interface Field Description Number of The number of consecutive pings without consecutive any response before the monitored unsuccessful pings equipment is declared "Unreachable." for failure Valid range is 1 to 100. Wait time before The wait time before the PX3 resumes resuming pinging pinging after the monitored equipment is after failure...
Page 344 Chapter 6: Using the Web Interface Editing or Deleting Ping Monitoring Settings You can edit the ping monitoring settings of any IT device or simply delete it if no longer needed. To modify or delete any monitored IT device: 1. Choose Device Settings > Server Reachability. 2.
Page 345 Chapter 6: Using the Web Interface Field Data entered Wait time after successful ping  To make the PX3 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 346: Front Panel Settings
Chapter 6: Using the Web Interface 5. Select the System SNMP Notification Action. Note: If you have not configured the System SNMP Notification Action to specify the SNMP destination(s), see Editing or Deleting a Rule/Action (on page 312). Front Panel Settings You can set up the default mode of the front panel display, and front panel functions for outlet switching, actuator control, or RCM self-test.
Page 347: Configuring The Serial Port
Note: The serial port bit-rate change is required when the PX3 works in conjunction with Raritan's Dominion LX KVM switch. Dominion LX only supports 19200 bps for communications over the serial interface. You can set diverse bit-rate settings for console and modem operations.
Page 348 Chapter 6: Using the Web Interface Options Description Force console The PX3 attempts to recognize that the connected device is set for the console mode. Force analog modem The PX3 attempts to recognize that the connected device is an analog modem. Force GSM modem The PX3 attempts to recognize that the connected device is a GSM modem.
Page 349: Lua Scripts
Raritan also provides some Lua scripts examples, which you can load as needed. Note: Not all Raritan Lua script examples can apply to your PX3 model. You should read each example's introduction before applying them. You must have the Administrator Privileges to manage Lua scripts.
Page 350 Source Code section. Therefore, do not load a new script if the current script meets your needs. 6. If you chose to load a script or Raritan's example in the previous step, its codes are then displayed in the Source Code section. Double check the codes.
Page 351 Chapter 6: Using the Web Interface Next steps:  To execute the newly-added script now, click , or Manually Starting or click > Start with Arguments. See Stopping a Script (on page 329).  To add more scripts, return to the scripts list by clicking "Lua Scripts"...
Page 352 Chapter 6: Using the Web Interface  Click if needing additional arguments. 5. Click Start. 6. The script output will be shown in the Script Output section.  If needed, click to delete the existing output data. To manually stop a script: 1.
Page 353 Chapter 6: Using the Web Interface Checking Lua Scripts States Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state and settings of each script. State: Four script states are available.  : The script is never executed since the device boot. ...
Page 354: Miscellaneous
Chapter 6: Using the Web Interface 3. Click > Edit Script. 4. Make changes to the information shown, except for the script's name, which cannot be revised.  To replace the current script, click Load Local File or Load Example to select a new script. To delete a script: 1.
Page 355: Maintenance
Chapter 6: Using the Web Interface Field Description Domain password Type the authentication password (secret) for entering the Cisco EnergyWise domain  Up to 127 printable ASCII characters are permitted.  Spaces and asterisks are NOT acceptable. Port Type a User Datagram Protocol (UDP) port number for communications in the Cisco EnergyWise domain.
Page 356 Chapter 6: Using the Web Interface Device Information Using the web interface, you can retrieve hardware and software information of components or peripheral devices connected to your PX3. Tip: If the information shown on this page does not match the latest status, press F5 to reload it.
Page 357 PX3 Devices for Sharing Ethernet Connectivity (on page 38). This section explains how to identify a cascaded device on the Device Information page. Note: For more information on the USB-cascading configuration, see the , which is available from Raritan website's Cascading Guide Support page http://www.raritan.com/support/ To identify the USB-cascading status: 1.
Page 358 Chapter 6: Using the Web Interface Cascading information in the Bridging mode:  The Common section contains two read-only fields for indicating the cascading status. Note that the cascading position is NOT available in the bridging mode. Fields Description Port Forwarding Indicates the Port Forwarding is disabled.
Page 359 Chapter 6: Using the Web Interface Fields Description Cascaded Device Indicates whether a slave device is detected on the Connected USB-A or Ethernet port.  yes: Connection to a slave device is detected.  no: NO connection to a slave device is detected. ...
Page 360 Chapter 6: Using the Web Interface  The final slave device shows a non-zero number which indicates its position in the Cascade Position field and in the Cascaded Device Connected field. The following diagram shows 2, indicating it is the second slave - Slave 2.
Page 361 Chapter 6: Using the Web Interface Column Description Client Type The interface through which the user is being connected to the PX3.  Web GUI: Refers to the web interface.  CLI: Refers to the command line interface (CLI). The information in parentheses following "CLI" indicates how this user is connected to the CLI.
Page 362: Viewing Or Clearing The Local Event Log
Chapter 6: Using the Web Interface Viewing or Clearing the Local Event Log By default, the PX3 captures certain system events and saves them in a local (internal) event log. You can view over 2000 historical events that occurred on the PX3 in the local event log.
Page 363: Updating The Px3 Firmware
Support page http://www.raritan.com/support/ the Raritan website's If you have any questions or concerns about the upgrade, contact Raritan Technical Support BEFORE upgrading. On a multi-inlet PDU (any model with X2 or X3 suffixes), all inlets must be connected to power for the PDU to successfully upgrade its firmware.
Page 364 Chapter 6: Using the Web Interface  A progress bar appears on the web interface, indicating the update status.  The front panel display shows the firmware upgrade message. Showing the Firmware Upgrade Progress (on page 117).  The outlet LEDs flash if the relay boards are being updated. If the firmware update does not include the update of the relay board firmware, outlet LEDs do NOT flash.
Page 365: Viewing Firmware Update History
Raritan. Contact Raritan Technical Support for the recovery utility, which works in Windows XP/Vista/7/10 and Linux. In addition, an appropriate PX3 firmware file is required in the recovery procedure.
Page 366: Bulk Configuration
Chapter 6: Using the Web Interface  Update result 2. If wanted, you can resort the list by clicking the desired column Sorting a List header. See (on page 134). Bulk Configuration The Bulk Configuration feature lets you save generic settings of a configured PX3 device to your computer.
Page 367 Chapter 6: Using the Web Interface 4. Click 'Upload & Restore Bulk Configuration' to copy it. 5. A message appears, prompting you to confirm the operation and enter the admin password. Enter the admin password, and click Restore. 6. Wait until the PX3 device resets and the login page re-appears. Note: On startup, the PX3 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.
Page 368 - Line cord length (meters), which is indicated as , such as A0 and - Line cord length (centimeters), which is indicated as Example: You can perform bulk configuration between Raritan's PX2-4724-E2N1K2 and PX2-4724-E2N1K9.  Reason: The two models share the same technical specifications, and the only difference is their chassis colors represented by K2 (blue) and K9 (gray).
Page 369: Backup And Restore Of Device Settings
Chapter 6: Using the Web Interface Backup and Restore of Device Settings Unlike the bulk configuration file, the backup file contains ALL device settings, including device-specific data like device names and network settings. To back up or restore a PX3 device's settings, you should perform the Backup/Restore feature.
Page 370: Network Diagnostics
Chapter 6: Using the Web Interface Note: On startup, the PX3 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 371: Downloading Diagnostic Information
Raritan Technical Support. You can download the diagnostic file from the PX3 to a client machine. The file is compressed into a .tgz file and should be sent to Raritan Technical Support for interpretation. This feature is accessible only by users with Administrative Privileges or Unrestricted View Privileges.
Page 372: Rebooting The Px3 Device
Chapter 6: Using the Web Interface Rebooting the PX3 Device You can remotely reboot the PX3 device via the web interface. Resetting the PX3 does not interrupt the operation of connected servers because there is no loss of power to outlets. During and after the reboot, outlets that have been powered on prior to the reboot remain powered on, and outlets that have been powered off remain powered off.
Page 373: Retrieving Software Packages Information
Chapter 6: Using the Web Interface To reset the device to factory defaults: 1. Choose Maintenance > Unit Reset > 2. Click Factory Reset to reset the PX3 to factory defaults. 3. A message appears, with a countdown timer showing the remaining time of the operation.
Page 374: Webcam Management
Chapter 6: Using the Web Interface Webcam Management The webcam-related menu items appear only when there are webcam(s) Connecting a Logitech Webcam connected to the PX3. See (on page 81). With a Logitech webcam connected to the PX3, you can visually monitor ®...
Page 375 Chapter 6: Using the Web Interface  You can send out this window's URL to share the live image with Sending Snapshots or Videos in an Email or other users. See Instant Message (on page 354). Settings 5. To switch between snapshot and video modes, see the section below.
Page 376: Sending Snapshots Or Videos In An Email Or Instant Message
Chapter 6: Using the Web Interface Sending Snapshots or Videos in an Email or Instant Message Whenever you open a Primary Standalone Live Preview window, a unique URL is generated for this window session. A URL supports a maximum of three sessions.
Page 377: Viewing Saved Snapshots And Managing Storage
Chapter 6: Using the Web Interface 2. Click Live Preview > New Live Preview Window. The live snapshot or Configuring video in a standalone live preview window opens. See Webcams and Viewing Live Images (on page 352). 3. Copy the URL from the live preview window, and send it through an email or instant message application.
Page 378 Chapter 6: Using the Web Interface 3. If the latest saved snapshot is not listed yet, click > Refresh on the top of the list. 4. To manually delete any images: a. Select the checkboxes of the images you want to remove. ...
Page 379: Chapter 7 Using Snmp
Chapter 7 Using SNMP This SNMP section helps you set up the PX3 for use with an SNMP manager. The PX3 can be configured to send traps or informs to an SNMP manager, as well as receive GET and SET commands in order to retrieve status and configure some basic settings.
Page 380: Snmpv2C Notifications
Chapter 7: Using SNMP To enable SNMP notifications: 1. Choose Device Settings > Network Services > SNMP. 2. In the SNMP Notifications section, enable the SNMP notification feature, and configure related fields. For details, refer to:  SNMPv2c Notifications (on page 358) ...
Page 381 Chapter 7: Using SNMP 6. Click Save. SNMPv3 Notifications 1. Choose Device Settings > Network Services > SNMP. 2. In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox is selected. 3. In the SNMP Notifications section, make sure the Enable SNMP Notifications checkbox is selected.
Page 382: Downloading Snmp Mib
Chapter 7: Using SNMP Field Description Authentication The three fields are available when the security Protocol, level is set to AuthNoPriv or authPriv.  Select the authentication protocol - MD5 or SHA Authentication Passphrase,  Enter the authentication passphrase Confirm Authentication Passphrase Privacy Protocol,...
Page 383: Snmp Gets And Sets
Chapter 7: Using SNMP MIB download via the Device Information page: 1. Choose Maintenance > Device Information. 2. In the Information section, click the desired download link:  EMD2-MIB  ASSETMANAGEMENT-MIB  LHX MIB 3. Click Save to save the file onto your computer. Note: LHX-MIB is available only after the LHX/SHX support has been enabled.
Page 384 Chapter 7: Using SNMP Layout Opening the MIB reveals the custom objects that describe the PX3 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 385 Chapter 7: Using SNMP SNMP Sets and Thresholds Some objects can be configured from the SNMP manager using SNMP set commands. Objects that can be configured have a MAX-ACCESS level of "read-write" in the MIB. These objects include threshold objects, which causes the PX3 to generate a warning and send an SNMP notification when certain Sensor Threshold Settings parameters are exceeded.
Page 386: A Note About Enabling Thresholds
Chapter 7: Using SNMP A Note about Enabling Thresholds When enabling previously disabled thresholds via SNMP, make sure you set a correct value for all thresholds that are supposed to be enabled prior to actually enabling them. Otherwise, you may get an error message.
Page 387: Chapter 8 Using The Command Line Interface
Chapter 8 Using the Command Line Interface This section explains how to use the command line interface (CLI) to administer a PX3 device. CLI commands are case sensitive. In This Chapter About the Interface.................. 365 Logging in to CLI..................366 Help Command..................
Page 388: Logging In To Cli
Chapter 8: 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 389: With Ssh Or Telnet
Chapter 8: Using the Command Line Interface After properly entering the password, the # or > system prompt Different CLI Modes and Prompts appears. See (on page 368) in the User Guide for more information. Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile was used to log in to this product's web interface or CLI.
Page 390: With An Analog Modem
Chapter 8: Using the Command Line Interface With an Analog Modem The PX3 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 PX3 via the modem: 1.
Page 391: Different Cli Modes And Prompts
Chapter 8: Using the Command Line Interface Different CLI Modes and Prompts Depending on the login name you use and the mode you enter, the system prompt in the CLI varies.  User Mode: When you log in as a normal user, who may not have full permissions to configure the PX3 device, the >...
Page 392: Help Command
Chapter 8: Using the Command Line Interface Help Command The help (?) command shows a list of main CLI commands available for the current mode. This is helpful when you are not familiar with CLI commands. Help command under the administrator mode: Help command under the configuration mode: config:# Help command under the diagnostic mode:...
Page 393: Querying Available Parameters For A Command
Chapter 8: Using the Command Line Interface Querying Available Parameters for a Command If you are not sure what commands or parameters are available for a particular type of CLI command or its syntax, you can have the CLI show them by adding a space and the help command (?) to the end of that command.
Page 394: Network Configuration
Chapter 8: Using the Command Line Interface Network Configuration This command shows all network configuration and all network interfaces' information, such as the IP address, MAC address, the Ethernet interface's duplex mode, and the wireless interface's status/settings. show network IP Configuration This command shows the IP-related configuration only, such as IPv4 and IPv6 configuration, address(es), gateway, and subnet mask.
Page 395 Chapter 8: Using the Command Line Interface Option Description bridge Show the IP-related configuration of the BRIDGE interface. Show the IP-related configuration of all interfaces. You can type the CLI command without the word show network ip interface 'all.' For example, IPv4-Only or IPv6-Only Configuration To show IPv4-only configuration or IPv6-only configuration, use any of the following commands.
Page 396 Chapter 8: Using the Command Line Interface Option Description ethernet (PX3) Show the IPv4 or IPv6 configuration of the ETHERNET interface. eth1 (PX3-iX7) Show the IPv4 or IPv6 configuration of the ETH1 interface. eth2 (PX3-iX7) Show the IPv4 or IPv6 configuration of the ETH2 interface.
Page 397 Chapter 8: Using the Command Line Interface Option Description eth2 (PX3-iX7) Show the ETH2 interface's non-IP settings. wireless Show the WIRELESS interface's non-IP settings. bridge Show the BRIDGE interface's non-IP settings. Show the non-IP settings of all interfaces. You can type the CLI command without the word show network interface 'all.' For example, Network Service Settings...
Page 398: Pdu Configuration
Chapter 8: Using the Command Line Interface PDU Configuration This command shows the PDU configuration, such as the device name, firmware version and model type. show pdu To show detailed information, add the parameter "details" to the end of the command. show pdu details Outlet Information This command syntax shows the outlet information.
Page 399: Inlet Information
Chapter 8: Using the Command Line Interface Inlet Information This command syntax shows the inlet information. show inlets <n> To show detailed information, add the parameter "details" to the end of the command. show inlets <n> details Variables:  <n> is one of the options: , or a number.
Page 400: Overcurrent Protector Information
Chapter 8: Using the Command Line Interface Overcurrent Protector Information This command is only available for models with overcurrent protectors for protecting outlets. This command syntax shows the overcurrent protector information, such as a circuit breaker or a fuse. show ocp <n> To show detailed information, add the parameter "details"...
Page 401: Date And Time Settings
Chapter 8: Using the Command Line Interface Date and Time Settings This command shows the current date and time settings on the PX3 device. show time To show detailed information, add the parameter "details" to the end of the command. show time details Default Measurement Units This command shows the default measurement units applied to the PX3...
Page 402: Environmental Sensor Information
Chapter 8: Using the Command Line Interface Environmental Sensor Information This command syntax shows the environmental sensor's information. show externalsensors <n> To show detailed information, add the parameter "details" to the end of the command. show externalsensors <n> details External sensor 3 ('Temperature 1') Sensor type: Temperature Reading: 31.8 deg C (normal)
Page 403: Environmental Sensor Package Information
Chapter 8: Using the Command Line Interface * The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripherals page of the PX3 web interface. Displayed information:  Without the parameter "details," only the sensor ID, sensor type and reading are displayed.
Page 404: Actuator Information
Chapter 8: Using the Command Line Interface Actuator Information This command syntax shows an actuator's information. show actuators <n> To show detailed information, add the parameter "details" to the end of the command. show actuators <n> details Variables:  <n> is one of the options: , or a number.
Page 405: Outlet Sensor Threshold Information
Chapter 8: Using the Command Line Interface Outlet Sensor Threshold Information This command syntax shows the specified outlet sensor's threshold-related information. show sensor outlet <n> <sensor type> To show detailed information, add the parameter "details" to the end of the command. show sensor outlet <n>...
Page 406: Outlet Pole Sensor Threshold Information
Chapter 8: Using the Command Line Interface Outlet Pole Sensor Threshold Information This command is available for an in-line monitor only, including PX2-3000 and PX3-3000 series. This command syntax shows the specified outlet pole sensor's threshold-related information. show sensor outletpole <n> <p> <sensor type> To show detailed information, add the parameter "details"...
Page 407: Inlet Sensor Threshold Information
Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion delay settings of the specified outlet pole sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.
Page 408: Inlet Pole Sensor Threshold Information
Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified inlet sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.
Page 409: Overcurrent Protector Sensor Threshold Information
Chapter 8: Using the Command Line Interface Sensor type Description apparentPower Apparent power sensor powerFactor Power factor sensor activeEnergy Active energy sensor Displayed information:  Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified inlet pole sensor are displayed.
Page 410 Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified overcurrent protector sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.
Page 411: Environmental Sensor Threshold Information
Chapter 8: Using the Command Line Interface Environmental Sensor Threshold Information This command syntax shows the specified environmental sensor's threshold-related information. show sensor externalsensor <n> To show detailed information, add the parameter "details" to the end of the command. show sensor externalsensor <n> details External sensor 3 (Temperature): Reading: 31.8 deg C State:...
Page 412: Environmental Sensor Default Thresholds
Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the reading, threshold, deassertion hysteresis and assertion timeout settings of the specified environmental sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.
Page 413: Security Settings
Chapter 8: Using the Command Line Interface  Without the parameter "details," only the default upper and lower thresholds, deassertion hysteresis and assertion timeout settings of the specified sensor type are displayed.  With the parameter "details," the threshold range is displayed in addition to default thresholds settings.
Page 414: Existing User Profiles
Chapter 8: Using the Command Line Interface Existing User Profiles This command shows the data of one or all existing user profiles. show user <user_name> To show detailed information, add the parameter "details" to the end of the command. show user <user_name> details Variables: ...
Page 415: Existing Roles
Chapter 8: Using the Command Line Interface Existing Roles This command shows the data of one or all existing roles. show roles <role_name> Variables:  <role_name> is the name of the role whose permissions you want to query. The variable can be one of the following options: Option Description This option shows all existing roles.
Page 416: Serial Port Settings
Chapter 8: Using the Command Line Interface Serial Port Settings This command shows the baud rate setting of the serial port labeled CONSOLE / MODEM on the PX3 device. show serial EnergyWise Settings This command shows the PX3 device's current configuration for Cisco ®...
Page 417: Rack Unit Settings Of An Asset Strip
Chapter 8: Using the Command Line Interface Rack Unit Settings of an Asset Strip A rack unit refers to a tag port on the asset strips. This command shows the settings of a specific rack unit or all rack units on an asset strip, such as a rack unit's LED color and LED mode.
Page 418: Blade Extension Strip Settings
Chapter 8: Using the Command Line Interface Blade Extension Strip Settings This command shows the information of a blade extension strip, including the total number of tag ports, and if available, the ID (barcode) number of any connected tag. show bladeSlot <n> <rack_unit> <slot> Variables: ...
Page 419: Event Log
Chapter 8: Using the Command Line Interface Event Log The command used to show the event log begins with show eventlog. You can add either the limit 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 420: Wireless Lan Diagnostic Log
Internal or external sensor events, such as state changes of any sensors. serverMonitor Server-monitoring records, such as a server being declared reachable or unreachable. assetManagement Raritan asset management events, such as asset tag connections or disconnections. Schroff LHX/SHX heat exchanger events. ® modem Modem-related events.
Page 421 Chapter 8: Using the Command Line Interface Server Reachability Information for a Specific Server To show the server reachability information for a certain IT device only, use the following command. show serverReachability server <n> To show detailed information, add the parameter "details" to the end of the command.
Page 422: Command History
Chapter 8: Using the Command Line Interface Command History This command syntax shows the command history for current connection session. show history Displayed information:  A list of commands that were previously entered in the current session is displayed. History Buffer Length This command syntax shows the length of the history buffer for storing history commands.
Page 423: Examples
Chapter 8: Using the Command Line Interface Option Description A specific Displays the specified number of last entries in the integer number reliability error log. Examples This section provides examples of the show command. Example 1 - Basic Security Information The diagram shows the output of the show security command.
Page 424 Chapter 8: 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 show pdu The diagram shows the output of the command.
Page 425: Clearing Information
Chapter 8: Using the Command Line Interface Example 4 - In-Depth PDU Information More information is displayed when typing the show pdu details command. Displayed information varies depending on the model you purchased. Clearing Information You can use the clear commands to remove unnecessary data from the PX3.
Page 426: Clearing Wlan Log
Chapter 8: Using the Command Line Interface Clearing WLAN Log This command removes all data from the diagnostic log for the wireless LAN (WLAN) connection. clear wlanlog -- OR -- clear wlanlog /y If you entered the command without "/y," a message appears, prompting you to confirm the operation.
Page 427: Quitting Configuration Mode
Chapter 8: Using the Command Line Interface "apply" command before closing the terminal emulation program. Closing the program does not save any configuration changes. See Quitting Configuration Mode (on page 404). Quitting Configuration Mode Both of "apply" and "cancel" commands let you quit the configuration mode.
Page 428 Chapter 8: Using the Command Line Interface Setting the Outlet Relay Behavior This section applies to outlet-switching capable models only. This command syntax determines the relay behavior of all outlets on a PX3 model. config:# pdu relayBehaviorOnPowerLoss <option> Variables:  <option>...
Page 429 Chapter 8: Using the Command Line Interface Setting the Outlet Power-On Sequence Delay This section applies to outlet-switching capable models only. This command sets the delays (in seconds) for outlets when turning on all outlets in sequence. config:# pdu outletSequenceDelay <outlet1>:<delay1>;<outlet2>:<delay2>; <outlet3>:<delay3>;...
Page 430 Chapter 8: Using the Command Line Interface Option Description lastKnownState Restores all outlets to the previous status before powering down the PX3 device when the PDU powers up again. Note: This feature does NOT take effect and cannot be configured on a PX3 device after the outlet relay is set to the "Latching"...
Page 431 Chapter 8: Using the Command Line Interface Setting the Outlet Initialization Delay This section applies to outlet-switching capable models only. This command determines the outlet initialization delay timing on device startup. See (on page 145) for information on outlet initialization delay.
Page 432 Chapter 8: Using the Command Line Interface Enabling or Disabling Data Logging This command enables or disables the data logging feature. config:# pdu dataRetrieval <option> Variables:  enable disable <option> is one of the options: Option Description enable Enables the data logging feature. disable Disables the data logging feature.
Page 433 This command specifies your PX3 device's altitude above sea level (in meters). You must specify the PX3 device's altitude above sea level if a Raritan's DPX differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction Altitude Correction Factors (on page 684).
Page 434 Chapter 8: Using the Command Line Interface Enabling or Disabling Peripheral Device Auto Management This command enables or disables the Peripheral Device Auto Management feature. config:# pdu peripheralDeviceAutoManagement <option> Variables:  <option> is one of the options: enable disable Option Description enable Enables the automatic management feature for...
Page 435: Network Configuration Commands
Chapter 8: Using the Command Line Interface Example 4 - Non-Critical Outlets The following command sets outlets 1, 2, 3, 7, and 9 to be critical outlets, and 4, 5, 6, 8, 10, 11 and 12 to be non-critical outlets on a 12-outlet PX3. config:# pdu nonCriticalOutlets 1-3,7,9:false;4-6,8,10-12:true Network Configuration Commands...
Page 436 Chapter 8: Using the Command Line Interface Interface Description bridge Determine the IPv4 configuration mode of the BRIDGE interface (that is, bridging mode).  <mode> is one of the modes: dhcp static Mode Description dhcp The IPv4 configuration mode is set to DHCP. static The IPv4 configuration mode is set to static IP address.
Page 437 Chapter 8: Using the Command Line Interface  <name> is a host name which:  Consists of alphanumeric characters and/or hyphens  Cannot begin or end with a hyphen  Cannot contain more than 63 characters  Cannot contain punctuation marks, spaces, and other symbols Setting the IPv4 Address After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX3 device.
Page 438 Chapter 8: 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 439 Chapter 8: Using the Command Line Interface config:# network ipv4 staticRoutes modify <route_ID> <dest-2> interface <ETH> Variables:  <dest-1> is a combination of the IP address and subnet mask of the IP address/subnet mask other subnet. The format is  <hop>...
Page 440 Chapter 8: Using the Command Line Interface Interface Description Determine the IPv6 configuration mode of the eth2 (PX3-iX7) ETH2 interface (wired networking). wireless Determine the IPv6 configuration mode of the WIRELESS interface (that is, wireless networking). bridge Determine the IPv6 configuration mode of the BRIDGE interface (that is, bridging mode).
Page 441 Chapter 8: Using the Command Line Interface Interface Description wireless Determine the IPv6 preferred host name of the WIRELESS interface (that is, wireless networking). bridge Determine the IPv6 preferred host name of the BRIDGE interface (that is, bridging mode).  <name>...
Page 442 Chapter 8: Using the Command Line Interface Interface Description bridge Determine the IPv6 address of the BRIDGE interface (that is, the bridging mode).  <ip address> is the IP address being assigned to your PX3 device. This value uses the IPv6 address format. Note that you must add which indicates a prefix length of bits such as /64, to the end of this IPv6 address.
Page 443 Chapter 8: Using the Command Line Interface config:# network ipv6 staticRoutes add <dest-1> interface <ETH> Delete an existing static route: config:# network ipv6 staticRoutes delete <route_ID> Modify an existing static route: config:# network ipv6 staticRoutes modify <route_ID> <dest-2> <hop> -- OR -- config:# network ipv6 staticRoutes modify <route_ID>...
Page 444 Chapter 8: Using the Command Line Interface Configuring DNS Parameters Use the following commands to configure DNS-related settings. Specify the primary DNS server: config:# network dns firstServer <ip address> Specify the secondary DNS server: config:# network dns secondServer <ip address> Specify the third DNS server: config:# network dns thirdServer <ip address>...
Page 445 Chapter 8: Using the Command Line Interface Enabling or Disabling the LAN Interface This command enables or disables the LAN interface. config:# network ethernet <ETH> enabled <option> Variables:  <ETH> is one of the options -- ethernet eth1 or eth2 , which depends on your model.
Page 446 Chapter 8: Using the Command Line Interface  auto 10Mbps 100Mbps or 1000Mbps <option> is one of the options: Option Description auto System determines the optimum LAN speed through auto-negotiation. 10Mbps The LAN speed is always 10 Mbps. 100Mbps The LAN speed is always 100 Mbps. 1000Mbps This option is only available on PX3-iX7 models or specific PX3 models with the suffix "-G1".
Page 447 Chapter 8: Using the Command Line Interface Option Description full Full duplex: Data is transmitted in both directions simultaneously. Setting Wireless Parameters You must configure wireless parameters, including Service Set Identifier (SSID), authentication method, Pre-Shared Key (PSK), and Basic Service Set Identifier (BSSID) after the wireless networking mode is enabled.
Page 448 Chapter 8: Using the Command Line Interface Method Description The wireless authentication method is set to EAP. Setting the PSK If the Pre-Shared Key (PSK) authentication method is selected, you must assign a PSK passphrase by using this command. config:# network wireless PSK <psk>...
Page 449 Chapter 8: Using the Command Line Interface Setting EAP Parameters When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, password, and CA certificate. Determine the outer authentication protocol: config:# network wireless eapOuterAuthentication <outer_auth>...
Page 450 Chapter 8: Using the Command Line Interface config:# network wireless allowConnectionWithIncorrectClock <option3> Variables:  PEAP The value of <outer_auth> is because PX3 only supports Protected Extensible Authentication Protocol (PEAP) as the outer authentication.  MSCHAPv2 The value of <inner_auth> is because PX3 only supports Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) as the inner authentication.
Page 451 Chapter 8: Using the Command Line Interface Option Description false The wireless network connection is NOT successfully established when the PX3 finds that the TLS certificate is not valid due to incorrect system time. EAP CA Certificate Example This section provides a CA certificate example only. Your CA certificate contents should be different from the contents displayed in this example.
Page 452 Chapter 8: Using the Command Line Interface MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYwNAYDVQ QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA wDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/ A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOH H21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atOb EuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZ ita+z4IBO 6. Paste the contents in the terminal. 7. Press Enter. 8. Verify whether the system shows the following command prompt, indicating the provided CA certificate is valid.
Page 453 Chapter 8: Using the Command Line Interface cascading mode may not be enabled successfully. Mode Description bridge The network bridging mode, where each cascaded device is assigned a unique IP address. portForwarding The port forwarding mode, where every cascaded device in the chain shares the same IP address, with diverse port numbers assigned.
Page 454 Chapter 8: Using the Command Line Interface  <option3> is one of the following options: Option Description Ethernet (or Ethernet (or ETH1/ETH2) port is the port ETH1/ETH2) where the 1st slave device is connected. USB port is the port where the 1st slave device is connected.
Page 455 Chapter 8: Using the Command Line Interface Setting the HTTPS Port The commands used to configure the HTTPS port settings begin with network services https Change the HTTPS port: config:# network services https port <n> Enable or disable the HTTPS access: config:# network services https enabled <option>...
Page 456 Chapter 8: 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 23.
Page 457 Chapter 8: Using the Command Line Interface Determining the SSH Authentication Method This command syntax determines the SSH authentication method. config:# network services ssh authentication <auth_method> Variables:  <option> is one of the options: passwordOnly publicKeyOnly passwordOrPublicKey Option Description passwordOnly Enables the password-based login only.
Page 458 Chapter 8: Using the Command Line Interface Enabling or Disabling SNMP v3 This command enables or disables the SNMP v3 protocol. config:# network services snmp v3 <option> Variables:  <option> is one of the options: enable disable Option Description enable The SNMP v3 protocol is enabled.
Page 459 Chapter 8: Using the Command Line Interface Setting the sysName Value This command sets the SNMP MIB-II sysName value. config:# network services snmp sysName <value> Variables:  <value> is a string comprising 0 to 255 alphanumeric characters. Setting the sysLocation Value This command sets the SNMP MIB-II sysLocation value.
Page 460 Chapter 8: Using the Command Line Interface Enabling or Disabling the Read-Only Mode This command enables or disables the read-only mode for the Modbus agent. config:# network services modbus readonly <option> Variables:  <option> is one of the options: true false Option Description...
Page 461: Time Configuration Commands
Chapter 8: Using the Command Line Interface Examples This section illustrates several network configuration examples. Example 1 - Networking Mode The following command enables the wired networking mode. config:# network mode wired Example 2 - Enabling Both IP Protocols The following command determines that both IPv4 and IPv6 protocols are enabled.
Page 462 Chapter 8: Using the Command Line Interface Determining the Time Setup Method This command determines the method to configure the system date and time. config:# time method <method> Variables:  <method> is one of the time setup options: manual Mode Description manual The date and time settings are customized.
Page 463 Chapter 8: Using the Command Line Interface Overriding DHCP-Assigned NTP Servers This command determines whether the customized NTP server settings override the DHCP-specified NTP servers. config:# time ntp overrideDHCPProvidedServer <option> Variables:  <option> is one of these options: true false Mode Description true...
Page 464 Chapter 8: Using the Command Line Interface Example To set the time zone: 1. Type the time zone command as shown below and press Enter. config:# time zone 2. The system shows a list of time zones. Type the index number of the desired time zone and press Enter.
Page 465 Chapter 8: Using the Command Line Interface Setting the Automatic Daylight Savings Time This command determines whether the daylight savings time is applied to the time settings. config:# time autoDST <option> Variables:  <option> is one of the options: enable disable Mode Description...
Page 466: Checking The Accessibility Of Ntp Servers
Chapter 8: Using the Command Line Interface Checking the Accessibility of NTP Servers This command verifies the accessibility of NTP servers specified manually on your PX3 and then shows the result. For instructions on specifying NTP servers via CLI, see Setting NTP Parameters (on page 439).
Page 467 Chapter 8: Using the Command Line Interface Modifying Firewall Control Parameters There are different commands for modifying firewall control parameters.  IPv4 commands Enable or disable the IPv4 firewall control feature: config:# security ipAccessControl ipv4 enabled <option> Determine the default IPv4 firewall control policy for inbound traffic: config:# security ipAccessControl ipv4 defaultPolicyIn <policy>...
Page 468 Chapter 8: Using the Command Line Interface Option Description false Disables the IP access control feature.  accept, drop reject <policy> is one of the options: Option Description accept Accepts traffic from all IP addresses. drop Discards traffic from all IP addresses, without sending any failure notification to the source host.
Page 469 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add <direction> <insert> <rule_number> <ip_mask> <policy>  IPv6 commands Add a new rule to the bottom of the IPv6 rules list: config:# security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy> Add a new IPv6 rule by inserting it above or below a specific rule: config:# security ipAccessControl ipv6 rule add <direction>...
Page 470 Chapter 8: Using the Command Line Interface  <insert> is one of the options: insertAbove insertBelow Option Description insertAbove Inserts the new rule above the specified rule number. Then: new rule's number = the specified rule number insertBelow Inserts the new rule below the specified rule number.
Page 471 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> policy <policy> Modify all contents of an IPv6 existing rule: config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> ipMask <ip_mask> policy <policy> Variables:  <direction> is one of the options: Direction Description Inbound traffic.
Page 472 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule delete <direction> <rule_number> IPv6 commands config:# security ipAccessControl ipv6 rule delete <direction> <rule_number> Variables:  <direction> is one of the options: Direction Description Inbound traffic. Outbound traffic.  <rule_number>...
Page 473 Chapter 8: Using the Command Line Interface After the Restricted Service Agreement feature is enabled, the agreement's content is displayed in the login screen. Do either of the following, or the login fails:  In the web interface, select the checkbox labeled "I understand and accept the Restricted Service Agreement."...
Page 474 Chapter 8: Using the Command Line Interface IMPORTANT!! You are accessing a PDU. If you are not the system administrator, do NOT power off or power cycle any outlet without the permission of the system administrator. 3. Press Enter. 4. Type the following: --END-- 5.
Page 475 Chapter 8: Using the Command Line Interface Password Aging This command enables or disables the password aging feature, which controls whether the password should be changed at a regular interval: config:# security loginLimits passwordAging <option> Variables:  <option> is one of the options: enable disable Option...
Page 476 Chapter 8: Using the Command Line Interface User Blocking There are different commands for changing different user blocking parameters. These commands begin with security userBlocking. You can combine multiple commands to modify the user blocking Multi-Command Syntax parameters at a time. See (on page 520).
Page 477 Chapter 8: Using the Command Line Interface Enabling or Disabling Strong Passwords This command enables or disables the strong password feature. config:# security strongPasswords enabled <option> Variables:  <option> is one of the options: true false Option Description true Enables the strong password feature. false Disables the strong password feature.
Page 478 Chapter 8: Using the Command Line Interface Option Description disable No lowercase character is required. Uppercase Character Requirement This command determines whether a strong password includes at least a uppercase character. config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter <option> Variables:  <option> is one of the options: enable disable Option...
Page 479 Chapter 8: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option> Variables:  enable disable <option> is one of the options: Option Description enable At least one special character is required. disable No special character is required. Maximum Password History This command determines the number of previous passwords that CANNOT be repeated when changing the password.
Page 480 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>  IPv6 commands Enable or disable the IPv6 role-based access control feature: config:# security roleBasedAccessControl ipv6 enabled <option> Determine the IPv6 role-based access control policy: config:# security roleBasedAccessControl ipv6 defaultPolicy <policy> Variables: ...
Page 481 Chapter 8: Using the Command Line Interface Adding a Role-Based Access Control Rule Depending on where you want to add a new rule in the list, the command syntax for adding a rule varies.  IPv4 commands Add a new rule to the bottom of the IPv4 rules list: config:# security roleBasedAccessControl ipv4 rule add <start_ip>...
Page 482 Chapter 8: Using the Command Line Interface  <insert> is one of the options: insertAbove insertBelow Option Description insertAbove Inserts the new rule above the specified rule number. Then: new rule's number = the specified rule number insertBelow Inserts the new rule below the specified rule number.
Page 483 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> Modify an IPv6 rule's role: config:# security roleBasedAccessControl ipv6 rule modify <rule_number> role <role> Modify an IPv6 rule's policy: config:# security roleBasedAccessControl ipv6 rule modify <rule_number> policy <policy>...
Page 484 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule delete <rule_number> IPv6 commands config:# security roleBasedAccessControl ipv6 rule delete <rule_number> Variables:  <rule_number> is the number of the existing rule that you want to remove. Enabling or Disabling Front Panel Outlet Switching This section applies to outlet-switching capable models only.
Page 485 Chapter 8: Using the Command Line Interface Enabling or Disabling Front Panel Actuator Control The following CLI commands control whether you can turn on or off a connected actuator by operating the front panel LCD display. To enable the front panel actuator control feature: config:# security frontPanelPermissions add switchActuator To disable the front panel actuator control feature:...
Page 486 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add 192.168.84.123/24 accept insertAbove 5 Results:  A new IPv4 firewall control rule is added to accept all packets sent from the IPv4 address 192.168.84.123.  The newly-added rule is inserted above the 5th rule. That is, the new rule becomes the 5th rule, and the original 5th rule becomes the 6th rule.
Page 487: Outlet Configuration Commands
Chapter 8: Using the Command Line Interface Outlet Configuration Commands An outlet configuration command begins with outlet . Such a command allows you to configure an individual outlet. Changing the Outlet Name This command names an outlet. config:# outlet <n> name "<name>" Variables: ...
Page 488: Inlet Configuration Commands
Chapter 8: Using the Command Line Interface Note: Setting the outlet's default state to an option other than pduDefined overrides the PDU-defined default state on that outlet. See Setting the PDU-Defined Default Outlet State (on page 406). Setting an Outlet's Cycling Power-Off Period This section applies to outlet-switching capable models only.
Page 489 Chapter 8: Using the Command Line Interface Changing the Inlet Name This command syntax names an inlet. config:# inlet <n> name "<name>" Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always the number 1. The value is an integer between 1 and 50.
Page 490: Overcurrent Protector Configuration Commands
Chapter 8: Using the Command Line Interface Example - Inlet Naming The following command assigns the name "AC source" to the inlet 1. If your PX3 device contains multiple inlets, this command names the 1st inlet. config:# inlet 1 name "AC source" Overcurrent Protector Configuration Commands ocp.
Page 491 Chapter 8: Using the Command Line Interface Creating a User Profile This command creates a new user profile. config:# user create <name> <option> <roles> After performing the user creation command, the PX3 prompts you to assign a password to the newly-created user. Then: 1.
Page 492 Chapter 8: Using the Command Line Interface 2. Re-type the new password for confirmation and press Enter. Variables:  <name> is the name of the user whose settings you want to change. Example The following procedure illustrates how to change the password of the user "May."...
Page 493 Chapter 8: 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 Multi-Command Syntax specific user profile at a time.
Page 494 Chapter 8: Using the Command Line Interface Enabling or Disabling a User Profile This command enables or disables a user profile. A user can log in to the PX3 device only after that user's user profile is enabled. config:# user modify <name> enabled <option> Variables: ...
Page 495 Chapter 8: Using the Command Line Interface Modifying SNMPv3 Settings There are different commands to modify the SNMPv3 parameters of a specific user profile. You can combine all of the following commands to modify the SNMPv3 parameters at a time. See Multi-Command Syntax (on page 520).
Page 496 Chapter 8: Using the Command Line Interface config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3> Variables:  <name> is the name of the user whose settings you want to change.  <option3> is one of the options: true false Option Description true Authentication passphrase is identical to the password.
Page 497 Chapter 8: Using the Command Line Interface Determine the privacy passphrase: config:# user modify <name> privacyPassPhrase <privacy_passphrase> Variables:  <name> is the name of the user whose settings you want to change.  <privacy_passphrase> is a string used as a privacy passphrase, comprising 8 to 32 ASCII printable characters.
Page 498 Chapter 8: Using the Command Line Interface Changing the Role(s) This command changes the role(s) of a specific user. config:# user modify <name> roles <roles> Variables:  <name> is the name of the user whose settings you want to change. ...
Page 499 Chapter 8: Using the Command Line Interface Set the preferred length unit: config:# user modify <name> preferredLengthUnit <option2> Variables:  <name> is the name of the user whose settings you want to change.  <option2> is one of the options: meter feet Option...
Page 500 Chapter 8: Using the Command Line Interface d. Press Enter. To remove an existing SSH public key: 1. Type the same command as shown above. 2. When the system prompts you to input the contents, press Enter without typing or pasting anything. Example The following procedure illustrates how to change the SSH public key for the user "assistant."...
Page 501 Chapter 8: Using the Command Line Interface config:# password 3. Type the existing password and press Enter when the following prompt appears. Current password: 4. Type the new password and press Enter when the following prompt appears. Enter new password: 5.
Page 502 Chapter 8: Using the Command Line Interface config:# user defaultpreferences preferredLengthUnit <option2> Variables:  meter feet <option2> is one of the options: Option Description meter This option displays the length or height in meters. feet This option displays the length or height in feet. Set the default pressure unit: config:# user defaultpreferences preferredPressureUnit <option3>...
Page 503 Chapter 8: Using the Command Line Interface Example 1 - Creating a User Profile The following command creates a new user profile and sets two parameters for the new user. config:# user create May enable admin Results:  A new user profile "May" is created. ...
Page 504: Role Configuration Commands
Chapter 8: Using the Command Line Interface Role Configuration Commands A role configuration command begins with role Creating a Role This command creates a new role, with a list of semicolon-separated privileges assigned to the role. config:# role create <name> <privilege1>;<privilege2>;<privilege3>... If a specific privilege contains any arguments, that privilege should be followed by a colon and the argument(s).
Page 505 Chapter 8: Using the Command Line Interface Privilege Description changeAuthSettings Change Authentication Settings changeDataTimeSettings Change Date/Time Settings changeExternalSensorsConfiguration Change Peripheral Device Configuration changeLhxConfiguration Change LHX/SHX Configuration changeModemConfiguration Change Modem Configuration changeNetworkSettings Change Network Settings changePassword Change Own Password changePduConfiguration Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration changeSecuritySettings...
Page 506 Chapter 8: Using the Command Line Interface * The "switchOutlet" privilege requires an argument that is separated with a colon. The argument could be:  All outlets, that is, switchOutlet:all  An outlet number. For example: switchOutlet:1 switchOutlet:2 switchOutlet:3  A list of comma-separated outlets.
Page 507 Chapter 8: Using the Command Line Interface Modifying a Role You can modify diverse parameters of an existing role, including its privileges. Modify a role's description: config:# role modify <name> description "<description>" Variables:  <name> is a string comprising up to 32 ASCII printable characters. ...
Page 508 Chapter 8: Using the Command Line Interface config:# role modify <name> addPrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon.
Page 509: Environmental Sensor Configuration Commands
Chapter 8: Using the Command Line Interface Deleting a Role This command deletes an existing role. config:# role delete <name> Example - Creating a Role The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup Results: ...
Page 510 Specifying the CC Sensor Type Raritan's contact closure sensor (DPX-CC2-TR) supports the connection of diverse third-party or Raritan's detectors/switches. You must specify the type of connected detector/switch for proper operation. Use this command when you need to specify the sensor type.
Page 511 Chapter 8: Using the Command Line Interface Type Description vibration The connected detector/switch is for detection of the vibration. Setting the X Coordinate This command specifies the X coordinate of an environmental sensor. config:# externalsensor <n> xlabel "<coordinate>" Variables:  <n>...
Page 512 Chapter 8: Using the Command Line Interface Setting the Z Coordinate This command specifies the Z coordinate of an environmental sensor. config:# externalsensor <n> zlabel "<coordinate>" Variables:  <n> is the ID number of the environmental sensor that you want to configure.
Page 513 Chapter 8: Using the Command Line Interface Using Default Thresholds This command determines whether default thresholds, including the deassertion hysteresis and assertion timeout, are applied to a specific environmental sensor. config:# externalsensor <n> useDefaultThresholds <option> Variables:  <n> is the ID number of the environmental sensor that you want to configure.
Page 514: Configuring Environmental Sensors' Default Thresholds
Chapter 8: Using the Command Line Interface Example 1 - Environmental Sensor Naming The following command assigns the name "Cabinet humidity" to the environmental sensor with the ID number 4. config:# externalsensor 4 name "Cabinet humidity" Example 2 - Sensor Threshold Selection The following command sets the environmental sensor #1 to use the default thresholds, including the deassertion hysteresis and assertion timeout, as its threshold settings.
Page 515 Chapter 8: Using the Command Line Interface config:# defaultThresholds <sensor type> lowerWarning <value> Set the Default Deassertion Hysteresis for a specific sensor type: config:# defaultThresholds <sensor type> hysteresis <hy_value> Set the Default Assertion Timeout for a specific sensor type: config:# defaultThresholds <sensor type>...
Page 516: Sensor Threshold Configuration Commands
Chapter 8: Using the Command Line Interface Sensor types Measurement units vibration  <hy_value> is the deassertion hysteresis value applied to the specified sensor type.  <as_value> is the assertion timeout value applied to the specified sensor type. It ranges from 0 to 100 (samples). Example - Default Upper Thresholds for Temperature It is assumed that your preferred measurement unit for temperature is set to degrees Celsius.
Page 517 Chapter 8: Using the Command Line Interface config:# sensor outlet <n> <sensor type> upperCritical <option> Set the Upper Warning threshold for an outlet sensor: config:# sensor outlet <n> <sensor type> upperWarning <option> Set the Lower Critical threshold for an outlet sensor: config:# sensor outlet <n>...
Page 518 Chapter 8: Using the Command Line Interface Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.  enable disable <option> is one of the options: or a numeric value. Option Description enable Enables the specified threshold for a specific outlet sensor.
Page 519 Chapter 8: Using the Command Line Interface config:# sensor inlet <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an inlet sensor: config:# sensor inlet <n> <sensor type> hysteresis <hy_value> Set the assertion timeout for an inlet sensor: config:# sensor inlet <n>...
Page 520 Chapter 8: Using the Command Line Interface Option Description disable Disables the specified threshold for a specific inlet sensor. A numeric Sets a value for the specified threshold of a value specific inlet sensor and enables this threshold at the same time. ...
Page 521 Chapter 8: Using the Command Line Interface config:# sensor inletpole <n> <p> <sensor type> assertionTimeout <as_value> Variables:  <n> is the number of the inlet whose pole sensors you want to configure.  <p> is the label of the inlet pole that you want to configure. Pole Label Current sensor...
Page 522 Chapter 8: Using the Command Line Interface  <hy_value> is a numeric value that is assigned to the hysteresis for "To De-assert" and the specified inlet pole sensor. See Deassertion Hysteresis (on page 680).  <as_value> is a number in samples that is assigned to the assertion "To Assert"...
Page 523 Chapter 8: Using the Command Line Interface config:# sensor ocp <n> <sensor type> assertionTimeout <as_value> Variables:  <n> is the number of the overcurrent protector that you want to configure.  <sensor type> is one of the following sensor types: Sensor type Description current...
Page 524 Chapter 8: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> upperCritical <option> Set the Upper Warning threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> upperWarning <option> Set the Lower Critical threshold for an environmental sensor: config:# sensor externalsensor <n>...
Page 525 Chapter 8: Using the Command Line Interface  enable disable <option> is one of the options: or a numeric value. Option Description enable Enables the specified threshold for a specific environmental sensor. disable Disables the specified threshold for a specific environmental sensor.
Page 526 Chapter 8: Using the Command Line Interface config:# sensor inlet 1 current upperWarning 20 lowerWarning 12 Results:  The Upper Warning threshold for the inlet 1 RMS current is set to 20A. It also enables the upper warning threshold if this threshold has not been enabled yet.
Page 527: Actuator Configuration Commands
Chapter 8: Using the Command Line Interface Actuator Configuration Commands An actuator configuration command begins with actuator . You can configure the name and location parameters of an individual actuator. You can configure various parameters for one actuator at a time. See Multi-Command Syntax (on page 520).
Page 528: Server Reachability Configuration Commands
Chapter 8: Using the Command Line Interface Note: To specify the Z coordinate using the rack units, see Setting the Z Coordinate Format for Environmental Sensors (on page 410).  <description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
Page 529 Chapter 8: Using the Command Line Interface  <succ_ping> is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200.  <fail_ping> is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to 100.
Page 530 Chapter 8: Using the Command Line Interface config:# serverReachability modify <n> ipAddress <IP_host> Enable or disable the ping monitoring feature for the device: config:# serverReachability modify <n> pingMonitoringEnabled <option> Modify the number of successful pings for declaring "Reachable": config:# serverReachability modify <n> numberOfSuccessfulPingsToEnable <succ_number>...
Page 531 Chapter 8: Using the Command Line Interface config:# serverReachability modify <n> numberOfFailuresToDisable <disable_count> Variables:  <n> is a number representing the sequence of the IT device in the server monitoring list.  <IP_host> is the IP address or host name of the IT device whose settings you want to modify.
Page 532: Energywise Configuration Commands
Chapter 8: Using the Command Line Interface EnergyWise Configuration Commands An EnergyWise configuration command begins with energywise Enabling or Disabling EnergyWise This command syntax determines whether the Cisco EnergyWise ® endpoint implemented on the PX3 device is enabled. config:# energywise enabled <option> Variables: ...
Page 533 Chapter 8: Using the Command Line Interface Specifying the EnergyWise Secret This command syntax specifies the password (secret) to enter the Cisco ® EnergyWise domain. config:# energywise secret <password> Variables:  <password> is a string comprising up to 127 ASCII printable characters.
Page 534: Asset Management Commands
Chapter 8: Using the Command Line Interface Example - Setting Up EnergyWise The following command sets up two Cisco EnergyWise-related features. ® config:# energywise enabled true port 10288 Results:  The EnergyWise feature implemented on the PX3 is enabled.  The UDP port is set to 10288.
Page 535 Chapter 8: Using the Command Line Interface Specifying the Number of Rack Units This command syntax specifies the total number of rack units on an asset strip connected to the PX3 device. config:# assetStrip <n> numberOfRackUnits <number> Note: A rack unit refers to a tag port on the asset strips. Variables: ...
Page 536 Chapter 8: Using the Command Line Interface Specifying the Rack Unit Numbering Offset This command syntax specifies the starting number of rack units on the asset strips connected to the PX3 device. config:# assetStrip <n> rackUnitNumberingOffset <number> Variables:  <n> is the number of the FEATURE port where the selected asset strip is physically connected.
Page 537 Chapter 8: Using the Command Line Interface Setting LED Colors for Connected Tags This command syntax sets the LED color for all rack units on the asset strip #1 to indicate the presence of a connected asset tag. config:# assetStrip <n> LEDColorForConnectedTags <color> Variables: ...
Page 538 Chapter 8: Using the Command Line Interface Naming a Rack Unit This command syntax assigns or changes the name of the specified rack unit on the specified asset strip. config:# rackUnit <n> <rack_unit> name "<name>" Variables:  <n> is the number of the FEATURE port where the selected asset strip is physically connected.
Page 539 Chapter 8: Using the Command Line Interface Mode Description manual This option enables selection of a different LED color and LED mode for the specified rack unit. Setting an LED When this option is selected, see Color for a Rack Unit Setting (on page 516) and an LED Mode for a Rack Unit...
Page 540 Chapter 8: Using the Command Line Interface Setting an LED Mode for a Rack Unit This command syntax sets the LED mode for a specific rack unit on the specified asset strip. You need to set a rack unit's LED mode only when the LED operation mode of this rack unit has been set to "manual."...
Page 541: Serial Port Configuration Commands
CONSOLE / MODEM on the PX3 device. Change the baud rate before connecting it to the desired device, such as a computer, a Raritan's P2CIM-SER, or a modem, through the serial port, or there are communications errors. If you change the baud rate dynamically after the connection has been made, you must reset the PX3 or power cycle the connected device for proper communications.
Page 542: Setting The History Buffer Length
Chapter 8: Using the Command Line Interface Forcing the Device Detection Mode This command forces the serial port on the PX3 to enter a specific device detection mode. config:# serial deviceDetectionType <mode> Variables:  <mode> is one of the detection modes: automatic forceConsole forceAnalogModem,...
Page 543: Multi-Command Syntax
Chapter 8: Using the Command Line Interface Multi-Command Syntax To shorten the configuration time, you can combine various configuration commands in one command to perform all of them at a time. All combined commands must belong to the same configuration type, such network user modify sensor externalsensor...
Page 544: Load Shedding Configuration Commands
Chapter 8: Using the Command Line Interface Example 3 - Combination of SSID and PSK Parameters This multi-command syntax configures both SSID and PSK parameters simultaneously for the wireless feature. config:# network wireless SSID myssid PSK encryp_key Results:  The SSID value is set to myssid. ...
Page 545: Enabling Or Disabling Load Shedding
Chapter 8: Using the Command Line Interface Enabling or Disabling Load Shedding This section applies to outlet-switching capable models only. This command determines whether to enter or exit from the load shedding mode. loadshedding <option> After performing the above command, PX3 prompts you to confirm the operation.
Page 546: Power Control Operations
Chapter 8: Using the Command Line Interface Power Control Operations This section applies to outlet-switching capable models only. Outlets on the PX3 device can be turned on or off or power cycled through the CLI. Besides, you can cancel the power-on process while the PX3 is powering on ALL outlets.
Page 547: Turning Off The Outlet(S)
Chapter 8: Using the Command Line Interface If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:  Type y to confirm the operation, OR  Type n to abort the operation Turning Off the Outlet(s) This section applies to outlet-switching capable models only.
Page 548: Power Cycling The Outlet(S)
Chapter 8: Using the Command Line Interface If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:  Type y to confirm the operation, OR  Type n to abort the operation Power Cycling the Outlet(s) This section applies to outlet-switching capable models only.
Page 549: Canceling The Power-On Process
Chapter 8: Using the Command Line Interface If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:  Type y to confirm the operation, OR  Type n to abort the operation Canceling the Power-On Process This section applies to outlet-switching capable models only.
Page 550: Switching On An Actuator
Chapter 8: Using the Command Line Interface Switching On an Actuator This command syntax turns on one actuator. control actuator <n> on To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation. control actuator <n>...
Page 551: Example - Turning On A Specific Actuator
Chapter 8: Using the Command Line Interface If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then:  Type y to confirm the operation, OR  Type n to abort the operation Example - Turning On a Specific Actuator The following command turns on the actuator whose ID number is 8.
Page 552: Restarting The Pdu
Chapter 8: Using the Command Line Interface Restarting the PDU This command restarts the PX3 device. It is not a factory default reset. To restart the PX3 device: 1. Ensure you have entered administrator mode and the # prompt is displayed.
Page 553: Resetting To Factory Defaults
Chapter 8: Using the Command Line Interface -- OR -- reset activeEnergy outlet <outlet_n> /y If you entered the command without "/y", a message appears prompting you to confirm the operation. Type y to confirm the reset or n to abort it. Variables: ...
Page 554: Quitting Diagnostic Mode
Chapter 8: Using the Command Line Interface Quitting Diagnostic Mode To quit the diagnostic mode, use this command: diag> exit The # or > prompt appears after pressing Enter, indicating that you have entered the administrator or user mode. See Different CLI Modes and Prompts (on page 368).
Page 555 Chapter 8: 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 556: Retrieving Previous Commands
Chapter 8: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your PX3 device and a network host. diag> traceroute <host> Variables:  <host> is the name or IP address of the host you want to trace. Example - Ping Command The following command checks the network connectivity of the host 192.168.84.222 by sending the ICMP ECHO_REQUEST message to the...
Page 557: Logging Out Of Cli
Chapter 8: Using the Command Line Interface Example 1: Type the first word and the first letter of the second word of the "reset factorydefaults" command, that is, reset f. Then press Tab or Ctrl+i to complete the second word. Example 2: Type the first word and initial letters of the second word of the "security enforceHttpsForWebAccess"...
Page 558: Chapter 9 Using Scp Commands
Chapter 9 Using SCP Commands You can perform a Secure Copy (SCP) command to update the PX3 firmware, do bulk configuration, or back up and restore the configuration. In This Chapter Firmware Update via SCP ............... 535 Bulk Configuration via SCP ..............536 Backup and Restore via SCP..............
Page 559: Bulk Configuration Via Scp
Chapter 9: Using SCP Commands SCP example: scp pdu-px2-030000-41270.bin admin@192.168.87.50:/fwupdate Windows PSCP command: PSCP in Windows works in a similar way to the SCP.  pscp <firmware file> <user name>@<device ip>:/fwupdate Bulk Configuration via SCP Like performing bulk configuration via the web interface, there are two steps with the bulk configuration using the SCP commands: a.
Page 560: Backup And Restore Via Scp
Chapter 9: Using SCP Commands 3. The system copies the configuration included in the file "bulk_config.xml" to another PX3, 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.xml ...
Page 561: Downloading Diagnostic Data Via Scp
Chapter 9: Using SCP Commands scp backup_settings.xml <user name>@<device ip>:/settings_restore  <user name> is the "admin" or any user profile with the administrator privileges.  <device ip> is the IP address of the PX3 whose settings you want to restore. 2.
Page 562 Chapter 9: Using SCP Commands 3. The system saves the diagnostic data from the PX3 to a file named "diag-data.tgz." SCP example: scp admin@192.168.87.50:/diag-data.tgz Windows PSCP command: PSCP in Windows works in a similar way to the SCP.  pscp <user name>@<device ip>:/diag-data.tgz...
Page 563: Appendix A Specifications
Maximum Ambient Operating Temperature The maximum ambient operating temperature (TMA) for PX3 varies from 50 to 60 degrees Celsius, depending on the model and certification standard (CE or UL). If necessary, contact Raritan Technical Support for this information for your model. Measure...
Page 564: Serial Rs-232 "Rj-45" Port Pinouts (For Ix7™ Only)
Appendix A: Specifications Serial RS-232 "RJ-45" Port Pinouts (for iX7™ Only) RJ-45 Pin/signal definition Pin No. Signal Direction Description Output Request to send Output Data terminal ready Output Transmit data ― Signal ground Input Data Input Receive data (data in) Input Data set ready Input...
Page 565: Feature Rj-45 Port Pinouts
Transmit Data (Data out) Input Receive Data (Data in) +12V ― Warning: Pin 6 is only intended for use with Raritan devices. Do NOT connect. ― Signal Ground Input Reserved Expansion RJ-45 Port Pinouts (for iX7™ Only) RJ-45 Pin/signal definition Pin No.
Page 566 Appendix A: Specifications RJ-45 Pin/signal definition RS485_DP bi-directional Data Positive of the RS-485 bus RS485_DN bi-directional Data Negative of the RS-485 bus ― Signal Ground ― No Connection ― Signal Ground...
Page 567: Appendix B Equipment Setup Worksheet
Appendix B Equipment Setup Worksheet PX3 Series Model ____________ PX3 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 568 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 569 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 570 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 571: 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 PX3.  Configuration changes ...
Page 572: System And Usb Requirements
PX3 system requirements:  There is at least one USB-A port available on your Raritan device.  Your PX3 must be version 2.2.13 or later. Note that the PX3 interpreted the USB drive's contents using the firmware which was running when plugging the USB drive, not the new firmware after firmware upgrade.
Page 573: Configuration Files
This file is required only when there are device-specific settings to devices.csv configure for multiple PX3 devices. See (on page 557). Raritan provides a Mass Deployment Utility, which helps you to quickly Creating Configuration generate all configuration files for your PX3. See Files via Mass Deployment Utility...
Page 574 PX3 detects a problem with the USB drive contents. firmware  Specify the name of a firmware binary file used to upgrade your PX3.  The specified firmware file must be compatible with your PX3 and have an official Raritan signature.
Page 575 Appendix C: Configuration or Firmware Upgrade with a USB Drive  If the specified firmware file is the same as the current firmware version of your PX3, no firmware upgrade is performed unless you have set the option "force_update" to true. force_update ...
Page 576 Appendix C: Configuration or Firmware Upgrade with a USB Drive  The default value is serial:1, making the PX3 search for its serial number in the first column.  This option is used only if the "device_list" option has been set. collect_diag ...
Page 577 Appendix C: Configuration or Firmware Upgrade with a USB Drive  config.txt Additional configuration keys set via the file will be applied after performing the configuration restore operation.  This option CANNOT be used with the option "bulk_config_restore."  If a firmware upgrade will be performed at the same time, you must generate the full configuration backup file based on the NEW firmware version instead of the current firmware version.
Page 578 PX3 model. You can use Raritan's Mass Deployment Utility to create this file by yourself, or contact Raritan to get a device configuration file specific to your PX3 model and firmware version.
Page 579 Appendix C: Configuration or Firmware Upgrade with a USB Drive Special configuration keys: There are 3 special configuration keys that are prefixed with magic:.  A special key that sets a user account's password without knowing the firmware's internal encryption/hashing algorithms is implemented as of release 2.2.13.
Page 580 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 PX3. This file must be: ...
Page 581: Creating Configuration Files Via Mass Deployment Utility
After entering required information, you can generate all configuration fwupdate.cfg config.txt files with only one click, including devices.csv To use the Mass Deployment Utility: 1. Download the Mass Deployment Utility from the Raritan website.  mass_deployment-xxx The utility is named (where xxx is the firmware version number).
Page 582: Data Encryption In 'Config.txt
Appendix C: Configuration or Firmware Upgrade with a USB Drive fwupdate.cfg 6. Verify that at least 3 configuration files are created - config.txt devices.csv . You are ready to configure or upgrade any Configuration or Firmware Upgrade with PX3 with these files. See a USB Drive (on page 548).
Page 583: Firmware Upgrade Via Usb
Add "encrypted:" to the beginning of that setting. Firmware Upgrade via USB Support page Firmware files are available on Raritan website's http://www.raritan.com/support/ Note that if the firmware file used for firmware upgrade is the same as the firmware version running on the PX3, no firmware upgrade will be...
Page 584 Depending on your product, the happy smiley looks like one of the following.  Sad smiley: Failed. Check the log file in the USB drive or contact Raritan Technical Support to look into the failure cause. The sad smiley looks like one of the following.
Page 585: Bulk Configuration/Upgrade Procedure
Steps of using DHCP/TFTP for bulk configuration/upgrade: 1. Create configuration files specific to your PX3 models and firmware Configuration Files versions. See (on page 550) or contact Raritan Technical Support to properly prepare some or all of the following files: ...
Page 586: Tftp Requirements
Note: Supported syntax of "fwupdate.cfg" and "config.txt" may vary based on different firmware versions. If you have existing configuration files, it is suggested to double check with Raritan Technical Support for the correctness of these files prior to using this feature.
Page 587: Dhcp Ipv4 Configuration In Windows
Windows Server 2012 system. ® Required Windows IPv4 settings in DHCP: 1. Add a new vendor class for Raritan PX3 under IPv4. a. Right-click the IPv4 node in DHCP to select Define Vendor Classes. b. Click Add to add a new vendor class.
Page 588 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The vendor class is named "Raritan PDU" in this illustration. 2. Define one DHCP standard option - Vendor Class Identifier. a. Right-click the IPv4 node in DHCP to select Set Predefined...
Page 589 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select DHCP Standard Options in the "Option class" field, and Vendor Class Identifier in the "Option name" field. Leave the String field blank. 3. Add three options to the new vendor class "Raritan PDU" in the same dialog.
Page 590 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Select Raritan PDU in the "Option class" field. b. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the...
Page 591 Name field, select String as the data type, and type 3 in the Code field. 4. Create a new policy associated with the "Raritan PDU" vendor class. a. Right-click the Policies node under IPv4 to select New Policy. b. Specify a policy name, and click Next.
Page 592 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The policy is named "PDU" in this illustration. c. Click Add to add a new condition.
Page 593 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select the vendor class "Raritan PDU" in the Value field, click Add and then Ok. e. Click Next.
Page 594 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 595 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP g. Select the "Raritan PDU" in the "Vendor class" field, select "001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv4 address in the "IP address" field.
Page 596 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 fwupdate.cfg option/code is the magic cookie to prevent the commands from being executed repeatedly.
Page 597: Dhcp Ipv6 Configuration In Windows
For those PX3 devices using IPv6 addresses, follow this procedure to configure your DHCP server. The following illustration is based on Microsoft Windows Server 2012 system. ® Required Windows IPv6 settings in DHCP: 1. Add a new vendor class for Raritan PX3 under IPv6.
Page 598 Click Add to add a new vendor class. c. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)" field, and type the binary codes of "Raritan PDU 1.0" in the New Class dialog.
Page 599 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 2. Add three options to the "Raritan PDU 1.0" vendor class. a. Right-click the IPv6 node in DHCP to select Set Predefined Options.
Page 600 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select Raritan PDU 1.0 in the "Option class" field. c. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the...
Page 601 Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field. 3. Configure server options associated with the "Raritan PDU 1.0" vendor class. a. Right-click the Server Options node under IPv6 to select Configure Options.
Page 602 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP c. Select "Raritan PDU 1.0" in the "Vendor class" field, select "00001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv6 address in the "IPv6 address" field.
Page 603 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select "00002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. e. Select "00003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third fwupdate.cfg option/code is the magic cookie to prevent the commands from being executed repeatedly.
Page 604: Dhcp Ipv4 Configuration In Linux
Modify the "dhcpd.conf" file for IPv4 settings when your DHCP server is running Linux. Required Linux IPv4 settings in DHCP: 1. Locate and open the "dhcpd.conf" file of the DHCP server. 2. The PX3 will provide the following value of the vendor-class-identifier option (option 60).  vendor-class-identifier = "Raritan PDU 1.0"...
Page 605 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Configure the same option in DHCP accordingly. The PX3 accepts the configuration or firmware upgrade only when this value in DHCP matches. 3. Set the following three sub-options in the "vendor-encapsulated-options" (option 43). ...
Page 606: Dhcp Ipv6 Configuration In Linux
13742 (Raritan's IANA number)  Raritan PDU 1.0  15 (the length of the above string "Raritan PDU 1.0") 3. Set the following three sub-options in the "vendor-opts" (option 17).  code 1 (pdu-tftp-server) = the TFTP server's IPv6 address ...
Page 607 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 608: Appendix E Resetting To Factory Defaults
Appendix E Resetting to Factory Defaults You can use either the reset button or the command line interface (CLI) to reset the PX3. Important: Exercise caution before resetting the PX3 to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on.
Page 609: Using The Cli Command
Appendix E: Resetting to Factory Defaults  PX3 models:  PX3-iX7 models: Note: HyperTerminal is available on Windows operating systems prior to Windows Vista. For Windows Vista or later versions, you may use PuTTY, which is a free program you can download from the Internet. See PuTTY's documentation for details on configuration.
Page 610 Appendix E: Resetting to Factory Defaults 6. Wait until the Username prompt appears, indicating the reset is complete. To reset to factory defaults without logging in to the CLI: The PX3 provides an easier way to reset the product to factory defaults in the CLI prior to login.
Page 611: Appendix F Px3 Models With Residual Current Monitoring
IT equipment permits up to 3mA. The RCM reports the sum so if twenty plugged-in devices - each leaking 1mA, the RCM sensor reports 20mA. Raritan offers two types of RCM sensors.  Type A: Detects AC leakage and is sensitive down to 6mA leakage.
Page 612: Rcm State Sensor
CRITICAL state causes the PX3 front panel to display a special error message. Self-test active RCM diagnostics are running. Failure RCM current sensor has malfunctioned. Contact Raritan Technical Support. Note: The factory default is to disable the Warning state. To define and enable this state, see Setting RCM Current Thresholds (on page 592).
Page 613: Compliance With Iec 62020
Appendix F: PX3 Models with Residual Current Monitoring Compliance with IEC 62020 IEC 62020 is an international standard for Residual Current Monitors. All PX3 with RCM are IEC 62020 compliant. rated residual operating current IEC 62020 uses the term (IΔn) to specify residual current, equal to or above which causes an alarm.
Page 614: Rcm Self-Test
Appendix F: PX3 Models with Residual Current Monitoring IEC 62020 specification PX3 with RCM characteristics Connection of load Monitored line is directly connected. conductors Fault indicating means Visual, with other output signals. Ability to directly Directionally non-discriminating. discriminate Rated residual operating 0.5A (highest value).
Page 615: Setting Rcm Current Thresholds
Appendix F: PX3 Models with Residual Current Monitoring  RCM State: There are five states - normal, warning, critical, self-test active and failure. For more information, see State Sensor (on page 589).  Residual Operating Current: The magnitude of residual current detected.
Page 616: Scheduling Rcm Self-Test
Appendix F: PX3 Models with Residual Current Monitoring 3. Set up RCM thresholds. a. Enable or disable the RCM critical threshold. Residual current greater than this value triggers Critical RCM state. b. Enable or disable the RCM warning threshold. Residual current greater than this value triggers Warning RCM state.
Page 617: Front Panel Operations For Rcm
Appendix F: PX3 Models with Residual Current Monitoring Front Panel Operations for RCM The front panel LCD display shows an alarm message when the RCM enters the critical state. Besides, you can operate the LCD display to check the RCM status. This section introduces the RCM information shown on the dot-matrix LCD display.
Page 618: Checking Rcm States And Current
Appendix F: PX3 Models with Residual Current Monitoring 2. If needed, you can press to perform RCM self-test for this inlet. For details, see steps 4 to 5 in the topic titled Running RCM Self-Test (on page 596). Checking RCM States and Current You can retrieve RCM information from the LCD display.
Page 619: Running Rcm Self-Test
Appendix F: PX3 Models with Residual Current Monitoring Running RCM Self-Test You can perform the RCM self-test by operating the front panel buttons. Disabling or Enabling To disable or enable this front panel function, see Front Panel RCM Self-Test (on page 593). By default, this function is enabled.
Page 620: Rcm Snmp Operations
Appendix F: PX3 Models with Residual Current Monitoring 6. After completing the RCM self-test, the LCD display indicates the RCM self-test result: passed or failed. 7. Press to return to the RCM information page. 8. Do one of the following: ...
Page 621: Rcm Residual Current And State Objects
Appendix F: PX3 Models with Residual Current Monitoring RCM Residual Current and State Objects inletSensorMeasurementsTable contains entries for RCM residual current and states. sensorType Use index = 26 to retrieve the row for residual current. measurementsInletSensorValue Column contains the residual current. sensorType Use index = 27 to retrieve the row for RCM state.
Page 622: Showing Residual Current Monitor Information
Appendix F: PX3 Models with Residual Current Monitoring Showing Residual Current Monitor Information This command syntax shows the residual current monitoring (RCM) information, which is only available on the models with RCM. The information displayed include the RCM current, state and thresholds. show residualCurrentMonitor <n>...
Page 623: Setting Front Panel Rcm Self-Test
Appendix F: PX3 Models with Residual Current Monitoring config:# residualCurrentMonitor <n> warningRatedResidualOperatingCurrent <value> To configure the RCM's deassertion hysteresis: config:# residualCurrentMonitor <n> deassertionHysteresis <hy_value> Variables:  <n> is the number of the inlet where the desired RCM current sensor is mounted. For a single-inlet PDU, this number is always 1. ...
Page 624: Running Rcm Self-Test
Appendix F: PX3 Models with Residual Current Monitoring Running RCM Self-Test You can perform RCM self-test for a specific inlet via CLI. After the self-test finishes, the test result is shown: pass or fail. To perform RCM self-test: rcm selfTest inlet <n> Variables: ...
Page 625: Appendix G Old Px3 Character Lcd Display
Appendix G Old PX3 Character LCD Display The following diagram shows the front panel on an "old" Zero U PX3 model, which is the first generation of PX3 models. The LCD display on the panel can show the reading or status of different components on the PX3, or its MAC address and IP address.
Page 626: Overview Of The Lcd Display
Appendix G: Old PX3 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, OUTLET 1, SENSOR 1, SENSOR 2, and so on.
Page 627: Control Buttons
Appendix G: Old PX3 Character LCD Display Control Buttons There are four control buttons.  Up and Down buttons for selecting a specific target, which can be an inlet, outlet, overcurrent protector, environmental sensor or a device setting  MODE button for switching between various modes, including: - Inlet mode - Outlet mode - Overcurrent Protector mode...
Page 628 Appendix G: Old PX3 Character LCD Display Section Example information The selected target is OUTLET 3. This outlet's current reading is 2 amps. The word "MASTER" indicates the PX3 is the master device in a cascading configuration. For a slave device, it shows "SLAVE" instead. Note: As of release 3.3.10, the "MASTER/SLAVE"...
Page 629: Inlet Information
Appendix G: Old PX3 Character LCD Display  W is displayed for the power reading. W means Watt. 4. To show the unbalanced load and active power of this 3-phase outlet, do the following: a. Switch to the current reading of L1. b.
Page 630: Overcurrent Protector Information
Appendix G: Old PX3 Character LCD Display 2. On a multi-inlet model, press the Up or Down button until the desired inlet's number is displayed at the top. 3. If your PX3 is a 3-phase model, the selected inlet line is indicated below the reading.
Page 631 Appendix G: Old PX3 Character LCD Display Section Example information The selected target is the second circuit breaker (CB 2). This circuit breaker's current reading is 0 amps. The word "CLOSE" indicates that the state of the selected circuit breaker is closed. The word "MASTER"...
Page 632: Ipv4 Address
Appendix G: Old PX3 Character LCD Display IPv4 Address The IP address is available in the Device mode, which is indicated by the alphabet 'd' shown at the top of the LCD display. Note that the LCD display only shows the IPv4 address (if available). Below illustrates the IP address information.
Page 633: Mac Address
Appendix G: Old PX3 Character LCD Display To display the IPv4 address: 1. Press the MODE button to enter the Device mode, indicated by an alphabet "d" at the top left of the display. 2. The LCD display cycles between the four octets of the IPv4 address, indicated by "i4"...
Page 634: Outlet Switching
Appendix G: Old PX3 Character LCD Display 3. The MAC address is displayed as "M:XX", where XX are two digits of the MAC address. The LCD will cycle through the MAC address from the first two digits to the final two. For example, if the MAC address is 00:0d:5d:03:5E:1A, the LCD display shows the following information one after another: M 00 -->...
Page 635 Appendix G: Old PX3 Character LCD Display To cancel the outlet switching operation, press the FUNC button again. 4. To turn on the outlet, press the Up button. The "on?" confirmation message displays. To turn off the outlet, press the Down button. The "oF?" confirmation message displays.
Page 636: Environmental Sensor Information
Appendix G: Old PX3 Character LCD Display Environmental Sensor Information The environmental sensor mode is displayed as "SENSOR" on the LCD display. Basic information about a specific environmental sensor is available, including the sensor's reading or state, X, Y, Z coordinates and its serial number.
Page 637 Appendix G: Old PX3 Character LCD Display Measurement Sensor types units A relative humidity sensor A temperature sensor An air flow sensor An air pressure sensor NO measurement For an "absolute" humidity sensor, the units measurement unit is g/m , which cannot be displayed on the LCD.
Page 638: Asset Strip Information
Appendix G: Old PX3 Character LCD Display Note that if the DPX3-ENVHUB4 sensor hub is used to connect the DPX2, DPX3 or DX sensors, the chain position information (C:x) is displayed twice - the first one indicates the sensor hub's chain position, which is always , and the second one indicates the sensor's chain position.
Page 639 Appendix G: Old PX3 Character LCD Display Section Example information "1" refers to the asset strip connected to the first FEATURE port. This symbol indicates that you can switch between diverse rack units now by pressing the Up or Down button.
Page 640: Usb-Cascaded Device's Position
Appendix G: Old PX3 Character LCD Display USB-Cascaded Device's Position Note: As of release 3.3.10, the following cascading information is no longer available in the bridging mode, but remains available in the port forwarding mode. A cascaded device's position is available by operating the LCD display. Below illustrates a slave device's position.
Page 641: Rcm Information
Appendix G: Old PX3 Character LCD Display Number Device position Slave 3 Slave 4 Slave 5 Slave 6 Slave 7 As of release 3.3.10, the port forwarding mode supports up to 15 slave devices so the numbers 8 to 15 may be shown in this mode. RCM Information If your "old"...
Page 642 Appendix G: Old PX3 Character LCD Display 2. Verify the LCD is showing the inlet's current, which is indicated by the presence of the letter "A." If not, switch to current by pressing the FUNC button. 3. Depending on the type of your PX3, the procedure to display the residual current slightly differs.
Page 643 Appendix G: Old PX3 Character LCD Display Below illustrates the RCM self-test mode. Section Example information The inlet containing RCM sensor is INLET 1. The LCD alternates between "SLF" and "tSt" to indicate that this is self-test mode. ALARM always displays for residual current sensor. LEAK always displays for residual current sensor.
Page 644: Appendix H Ldap Configuration Illustration
Configure LDAP authentication on the PX3 device d. Configure roles on the PX3 device Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
Page 645: Step B. Configure User Groups On The Ad Server
Appendix H: LDAP Configuration Illustration Step B. Configure User Groups on the AD Server You must create the groups (roles) for the PX3 on the AD server, and then make appropriate users members of these groups. In this illustration, we assume: ...
Page 646: Step C. Configure Ldap Authentication On The Px3 Device
Appendix H: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the PX3 Device You must enable and set up LDAP authentication properly on the PX3 device to use external authentication. In the illustration, we assume:  Wired The DNS server settings have been configured properly. See Network Settings Role of a DNS Server (on page 219) and...
Page 647: Step D. Configure Roles On The Px3 Device
Appendix H: LDAP Configuration Illustration Field/setting Do this... Bind DN, Skip the three fields because of anonymous bind. Bind Password, Confirm Bind Password Base DN for Search Type dc=techadssl,dc=com as the starting point where your search begins on the AD server. Login Name Attribute Ensure the field is set to sAMAccountName because the LDAP server is Microsoft Active Directory.
Page 648 Appendix H: LDAP Configuration Illustration 2. Click to add a new role. a. Type PX_User in the Role Name field. b. Type a description for the PX_User role in the Description field. In this example, we type "View PX settings" to describe the role. c.
Page 649 Appendix H: LDAP Configuration Illustration To create the PX_Admin role with full permissions assigned: 1. Click to add another role. a. Type PX_Admin in the Role Name field. b. Type a description for the PX_Admin role in the Description field. In this example, we type "Includes all PX privileges"...
Page 650: Returning User Group Information
Appendix I Updating the LDAP Schema In This Chapter Returning User Group Information ............627 Setting the Registry to Permit Write Operations to the Schema ... 628 Creating a New Attribute................. 628 Adding Attributes to the Class ..............629 Updating the Schema Cache ..............631 Editing rciusergroup Attributes for User Members .......
Page 651: Setting The Registry To Permit Write Operations To The Schema
Appendix I: Updating the LDAP Schema Setting the Registry to Permit Write Operations to the Schema To allow a domain controller to write to the schema, you must set a registry entry that permits schema updates. To permit write operations to the schema: 1.
Page 652: Adding Attributes To The Class
Appendix I: Updating the LDAP Schema 3. Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears. 4. Type rciusergroup in the Common Name field. rciusergroup 5. Type in the LDAP Display Name field. 6.
Page 653 Appendix I: Updating the LDAP Schema 2. Scroll to the user class in the right pane and right-click it. 3. Choose Properties from the menu. The user Properties dialog appears. 4. Click the Attributes tab to open it. 5. Click Add.
Page 654: Updating The Schema Cache
Appendix I: Updating the LDAP Schema 6. Choose rciusergroup from the Select Schema Object list. 7. Click OK in the Select Schema Object dialog. 8. Click OK in the User Properties dialog. Updating the Schema Cache To update the schema cache: 1.
Page 655 Appendix I: Updating the LDAP Schema 3. Go to the directory where the support tools were installed. Run adsiedit.msc. The ADSI Edit window opens. 4. Open the Domain. 5. In the left pane of the window, select the CN=Users folder.
Page 656 Appendix I: Updating the LDAP Schema 6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties. 7. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list.
Page 657: Appendix J Radius Configuration Illustration
 If a user has multiple roles, configure multiple standard attributes for this user.  The syntax of a standard attribute is: Raritan:G{role-name} NPS Standard Attribute Illustration For configuration on NPS, see page 634). FreeRADIUS Standard Attribute For configuration on FreeRADIUS, see Illustration (on page 652).
Page 658 Appendix J: RADIUS Configuration Illustration b. On the NPS, configure Connection Request Policies and the standard Step B: Configure Connection Policies and Standard attribute. See Attributes (on page 639). Some configuration associated with Microsoft Active Directory (AD) is AD-Related Configuration also required for RADIUS authentication.
Page 659 Appendix J: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX3. In this example, they are 1812 and 1813. Then close this dialog.
Page 660 Appendix J: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PX3 to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 661 Appendix J: 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 PX3. 5. Click OK.
Page 662 Appendix J: 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 PX3  Connection request forwarding method  Authentication method(s) ...
Page 663 Appendix J: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
Page 664 Appendix J: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
Page 665 Appendix J: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
Page 666 Appendix J: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the PX3 IP address -- 192.168.56.29 , and click OK. 7. Click Next in the New Connection Request Policy dialog. 8. Select "Authenticate requests on this server" because a local NPS server is used in this example.
Page 667 Appendix J: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options:  Override network policy authentication settings  CHAP -- the PX3 uses "CHAP" in this example...
Page 668 Appendix J: RADIUS Configuration Illustration Note: If your PX3 uses PAP, then select "PAP."...
Page 669 Appendix J: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
Page 670 Appendix J: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
Page 671 Appendix J: RADIUS Configuration Illustration 12. In the Attribute Information dialog, click Add. Raritan:G{Admin} 13. Select String, type in the text box, and then click...
Page 672 Appendix J: RADIUS Configuration Illustration Admin inside the curved brackets {} is the existing role on the PX3. It is recommended to use the Admin role to test this configuration. The role name is case sensitive.
Page 673 Appendix J: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
Page 674 Appendix J: RADIUS Configuration Illustration 15. Click Next to continue.
Page 675: Freeradius Standard Attribute Illustration
Appendix J: 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 676: Vendor-Specific Attributes
Appendix J: 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 677 Appendix J: RADIUS Configuration Illustration Step A: Add Your PX3 as a RADIUS Client The RADIUS implementation on a PX3 follows the standard RADIUS Internet Engineering Task Force (IETF) specification so you must select "RADIUS Standard" as its vendor name when configuring the NPS server.
Page 678 Appendix J: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX3. In this example, they are 1812 and 1813. Then close this dialog.
Page 679 Appendix J: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PX3 to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 680 Appendix J: 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 PX3. 5. Click OK.
Page 681 Appendix J: 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 PX3  Connection request forwarding method  Authentication method(s) ...
Page 682 Appendix J: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
Page 683 Appendix J: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
Page 684 Appendix J: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
Page 685 Appendix J: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the PX3 IP address -- 192.168.56.29 , and click OK. 7. Click Next in the New Connection Request Policy dialog. 8. Select "Authenticate requests on this server" because a local NPS server is used in this example.
Page 686 Appendix J: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options:  Override network policy authentication settings  CHAP -- the PX3 uses "CHAP" in this example...
Page 687 15. Click Configure Attribute, and then: a. Type in the "Vendor-assigned attribute number" field. b. Select String in the "Attribute format" field. Raritan:G{Admin User SystemTester} c. Type in the "Attribute value" field. In this example, three roles 'Admin,' 'User' and...
Page 688: Freeradius Vsa Illustration
A vendor-specific dictionary file is required for the vendor-specific-attribute configuration on FreeRADIUS. Therefore, there are two major configuration steps. a. Use a dictionary to define the Raritan vendor-specific attribute b. Add all user data, including user names, passwords, and roles Presumptions in the illustration: ...
Page 689: Ad-Related Configuration
2. Add the data of the user "steve" by typing the following. Note that the values after the equal sign (=) must be enclosed in double quotes ("). steve Cleartext-Password := "test123" Raritan-PDU-User-Roles = "Raritan:G{Admin User SystemTester}" AD-Related Configuration When RADIUS authentication is intended, make sure you also configure the following settings related to Microsoft Active Directory (AD): ...
Page 690 Appendix J: RADIUS Configuration Illustration 2. Right-click NPS (Local) and select "Register server in Active Directory." 3. Click OK, and then OK again. To grant PX3 users remote access permission: 1. Open Active Directory Users and Computers.
Page 691 Appendix J: RADIUS Configuration Illustration 2. Open the properties dialog of the user whom you want to grant the access permission. 3. Click the Dial-in tab and select the "Allow access" checkbox. To enable reversible encryption for CHAP authentication: 1. Open Active Directory Users and Computers. 2.
Page 692 Appendix J: RADIUS Configuration Illustration 3. Click the Account tab and select the "Store password using reversible encryption" checkbox.
Page 693: Appendix K Additional Px3 Information
Altitude Correction Factors..............684 Unbalanced Current Calculation ............685 Data for BTU Calculation................. 686 Ways to Probe Existing User Profiles ............. 687 Raritan Training Website................. 687 Role of a DNS Server................688 Cascading Troubleshooting..............688 Browsing through the Online Help ............694 RJ45-to-DB9 Cable Requirements for Modem Connections (for iX7™...
Page 694: Reserving Ip Addresses In Dhcp Servers
Appendix K: Additional PX3 Information Note: The RJ45-to-DB9 adapter/cable used for connecting modems CANNOT be used to connect the iX7 to a computer. See RJ45-to-DB9 ™ Cable Requirements for Computer Connections (for iX7 Only) ™ page 30). Reserving IP Addresses in DHCP Servers The PX3 uses its serial number as the client identifier in the DHCP request.
Page 695: Reserving Ip In Windows
Appendix K: Additional PX3 Information Reserving IP in Windows To reserve the IP address of any network interface in the Windows DHCP server, you must convert that interface's client identifier into hexadecimal ASCII codes. Reserving IP Addresses in For each interface's client identifier, see DHCP Servers (on page 671).
Page 696: Reserving Ip In Linux
Appendix K: Additional PX3 Information Reserving IP in Linux There are two methods to reserve the IP address of any network interface in the standard Linux DHCP server (ISC DHCP server):  hexadecimal Convert an interface's client identifier into ASCII codes. ...
Page 697 Appendix K: Additional PX3 Information Interface Client identifier conversion ETH2 (PX3-iX7) PEG1A00003-ETH2 = 50 45 47 31 41 30 30 30 30 33 2D 45 54 48 32  The suffix comprising the dash symbol and the word "ETH2" is also converted. WIRELESS PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45 53 53...
Page 698: Sensor Threshold Settings
Appendix K: Additional PX3 Information Sensor Threshold Settings This section explains the thresholds settings for a numeric sensor. Thresholds and Sensor States A numeric sensor has four thresholds: Lower Critical, Lower Warning, Upper Warning and Upper Critical. The threshold settings determine how many sensor states are available for a certain sensor and the range of each sensor state.
Page 699 Appendix K: Additional PX3 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 700 Appendix K: Additional PX3 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 701: To Assert" And Assertion Timeout
Appendix K: Additional PX3 Information "To Assert" and Assertion Timeout If multiple sensor states are available for a specific sensor, the PX3 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 PX3 to assert.
Page 702 Appendix K: Additional PX3 Information In the threshold settings, the Assertion Timeout field postpones or even cancels the "assertion" action. It determines how long a sensor must be in the "worse" new state before the PX3 triggers the "assertion" action. If that sensor changes its state again within the specified wait time, the PX3 does NOT assert the worse state.
Page 703: To De-Assert" And Deassertion Hysteresis
Appendix K: Additional PX3 Information "To De-assert" and Deassertion Hysteresis After the PX3 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 704 Appendix K: Additional PX3 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 705: Pdview App For Viewing The Px3
PDView App for Viewing the PX3 Raritan has developed an app that can turn your iOS or Android mobile device into a local display for the PX3. This app is called PDView and it can be downloaded for free.
Page 706 Appendix K: Additional PX3 Information 2. After installing the PDView, launch it. Below illustrates the PDView screen for Android devices. 3. Connect your mobile device to the USB port of the PX3. Your mobile device type determines which USB port on the PX3 shall be used to connect the mobile device.
Page 707: Altitude Correction Factors
PX3. 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 708: Unbalanced Current Calculation
Appendix K: Additional PX3 Information Altitude (meters) Altitude (feet) Correction factor 1394 1.00 1640 1.01 2428 1.04 1500 4921 1.15 2250 7382 1.26 3000 9842 1.38 Unbalanced Current Calculation Unbalanced current information is available on 3-phase models only. This section explains how the PX3 calculates the unbalanced current percentage.
Page 709: Data For Btu Calculation
Appendix K: Additional PX3 Information L2 = 5.2 amps L3 = 4.0 amps  Average current: (5.5+5.2+4.0) / 3 = 4.9 amps  L1 current unbalance: (5.5 - 4.9) / 4.9 = 0.1224  L2 current unbalance: (5.2 - 4.9) / 4.9 = 0.0612 ...
Page 710: Ways To Probe Existing User Profiles
Webcam-Live-Preview sessions, which show a list of associated user names. Raritan Training Website Raritan offers free training materials for various Raritan products on the Raritan training website http://www.raritantraining.com . The Raritan products introduced on this website include the intelligent PDU,...
Page 711: Role Of A Dns Server
Appendix K: Additional PX3 Information Role of a DNS Server As Internet communications are carried out on the basis of IP addresses, appropriate DNS server settings are required for mapping domain names (host names) to corresponding IP addresses, or the PX3 may fail to connect to the given host.
Page 712 For the wireless networking, one of the following may lead to the accessibility failure:  The USB wireless LAN adapter attached to the master device is not the Raritan USB WIFI LAN USB Wireless LAN Adapters adapter. See (on page 25).
Page 713 Appendix K: Additional PX3 Information Symptom Probable cause  Network connection to the master device is lost. Failure to access a slave device  The cascading cable connected to the slave device in question or any upstream device (if available) is loose or lost.
Page 714: Slave Connection And Disconnection Events
Appendix K: Additional PX3 Information Slave Connection and Disconnection Events The log messages for connection/disconnection of a cascaded device are different for USB-cascading and Ethernet-cascading chains. Messages for the Ethernet-cascading chain: Whenever the connection or disconnection of a master/slave device is detected, both PX3 devices connected via that network cable record this event in their internal logs.
Page 715: The Ping Tool
Appendix K: Additional PX3 Information The Ping Tool The PX3 provides a ping tool in the web interface and CLI so you can ping any host or PX3 in your data center. Ping via the Web Interface To log in to the web interface, see HTTP/HTTPS Access (see "...
Page 716 Appendix K: Additional PX3 Information Ping via the CLI You can access the CLI interface by connecting a computer to the PX3 or using SSH/Telnet. See SSH/Telnet Access (see " With SSH or Telnet " on page 367) for details. You must perform the ping command in the diagnostic mode.
Page 717: Browsing Through The Online Help
Appendix K: Additional PX3 Information diag> ping <host> count <number1> size <number2> timeout <number3> Browsing through the Online Help The PX3 Online Help is accessible over the Internet. To use online help, Active Content must be enabled in your browser. If you are using Internet Explorer 7, you must enable Scriplets.
Page 718 "Email this page" icon in the toolbar. 10. To email your comments or suggestions regarding the online help to Raritan, click the "Send feedback" icon 11. To print the currently selected topic, click the "Print this page" icon...
Page 719: Appendix L Integration
Appendix L Integration The PX3 device can work with certain Raritan products to provide diverse power solutions. In This Chapter Dominion KX II / III Configuration............696 Dominion KSX II, SX or SX II Configuration ..........701 Power IQ Configuration ................706 dcTrack ....................
Page 720: Configuring Rack Pdu Targets
KX III allows you to connect rack PDUs (power strips) to KX III ports. KX III rack PDU configuration is done from the KX III Port Configuration page. Note: Raritan recommends no more than eight (8) rack PDUs (power strips) be connected to a KX III at once since performance may be affected.
Page 721 Note: PX rack PDUs (power strips) can be named in the PX as well as in the KX III. Once a Raritan remote rack PDU is connected to the KX III, it will appear on the Port Configuration page. Click on the power port name on that page to access it.
Page 722 Appendix L: Integration 3. Click OK.
Page 723: Turning Outlets On/Off And Cycling Power
Port Access page. To use this feature, you will need:  Raritan remote rack PDU(s)  Power CIMs (D2CIM-PWR) Make a Power Association...
Page 724: Dominion Ksx Ii, Sx Or Sx Ii Configuration
KSX II, SX or SX II Online Help on the http://www.raritan.com/support/online-help/ Dominion KSX II After connecting a Dominion KSX II to the Raritan PDU, you can monitor the PDU and even control its outlets if the PDU is an outlet-switching capable model.
Page 725 Appendix L: Integration Connecting a Rack PDU To connect the Raritan PX to the KSX II: 1. Connect one end of a Cat5 cable to the following ports of different Raritan PX.  PX1 series: RJ-45 "SERIAL" port  PX2 or PX3 series: RJ-45 "FEATURE" port 2.
Page 726: Dominion Sx And Sx Ii
PX3 device to specific SX or SX II ports. Dominion SX II The way to use Dominion SX II to configure and control a Raritan PDU is similar to using Dominion KX III, but the connection method is different from KX III.
Page 727 Appendix L: Integration 4. You can now add the PX as a managed power strip to the SX II. See Configure Power Strips from the Remote Console or Configure Power Strips Using CLI in the SX II User Guide or Online Help. PX appliance SX II Dominion SX...
Page 728 Appendix L: Integration 3. Type a name and description in the Name and Description fields. 4. Select the number of outlets from the Number of Outlets drop-down menu. 5. Type the port number in the Port field. 6. Click OK. Power Control 1.
Page 729: Power Iq Configuration
Appendix L: Integration Checking Power Strip Status 1. Choose Power Control > Power Strip Status. 2. A status box appears, displaying details of the controlled PX3, including power state of each outlet on the device. Power IQ Configuration Sunbird's Power IQ is a software application that collects and manages the data from different PDUs installed in your server room or data center.
Page 730: Dctrack
Appendix L: Integration dcTrack Sunbird's dcTrack is a product that allows you to manage the data ® center. The PX3 is categorized as a power item in dcTrack. dcTrack offers an import wizard for conveniently adding the PX3 as well as other IT equipment to dcTrack for management.
Page 731: Dctrack Overview
Appendix L: Integration dcTrack Overview dcTrack is a powerful and intelligent data center management and ® automation application. It has been designed by data center and IT professionals to provide broad and deep visibility into the data center. It empowers data center managers to plan for growth and change by optimizing their current operations, assets, and infrastructure.
Page 732: Asset Management Strips And Dctrack
To poll and display asset management events in dcTrack  The PX3 that the asset strip is connected to must exist in dcTrack. EMX devices are identified as probes in dcTrack; Raritan PDUs are identified as sensors.  Each IT item connected to the asset strip via an asset tag must exist in dcTrack.
Page 733: Index
Index Applicable Models • xvii, xix + Assertion Timeout Example for Temperature Sensors • 680 +12V Power Supply Sensor (for iX7™ Only) • Asset Management Commands • 512 xix, 48, 100, 145, 154 Asset Management Strips and dcTrack • 710 1 ...
Page 734 Index Canceling the Power-On Process • 527 Clearing Event Log • 403 Cascading Multiple PX3 Devices for Sharing Clearing Information • 403 Ethernet Connectivity • xix, 27, 38, 220, 231, Clearing WLAN Log • 404 CLI Operations for RCM • 599 Cascading the PX3 via USB •...
Page 735 Index Configuring Webcams and Viewing Live Creating Users • xx, 126, 128, 207, 208, 212, Images • 81, 352, 355 213, 214, 216, 244, 258, 357 Connecting a DPX2 Sensor Package to DPX3 • Customizing the Date and Time • 442 62, 71 D ...
Page 736 Index DHCP IPv4 Configuration in Windows • 564, Enabling and Configuring SNMP • 313, 314, 317, 357 DHCP IPv6 Configuration in Linux • 564, 584 Enabling or Disabling a User Profile • 472 DHCP IPv6 Configuration in Windows • 564, Enabling or Disabling an Inlet (for Multi-Inlet PDUs) •...
Page 737 Index Equipment Setup Worksheet • 5, 545 Example 2 - In-Depth Security Information • Ethernet Interface Settings • xx, 27, 115, 219, Example 2 - Modifying a User's Roles • 481 Event Log • 397 Example 2 - Outlet Sequence • 412 Event Rules and Actions •...
Page 738 Index Firmware Upgrade via USB • 342, 550, 561 Inrush Current and Inrush Guard Delay • 147, Forcing a Password Change • 472 Forcing the Device Detection Mode • 520 Installing a CA-Signed Certificate • xx, 252, FreeRADIUS Standard Attribute Illustration • 635, 653 Installing Cable Retention Clips on Outlets FreeRADIUS VSA Illustration •...
Page 739 Index Mounting Zero U Models Using Claw-Foot M Brackets • 10 Mounting Zero U Models Using L-Brackets • 7 MAC Address • 611 Mounting Zero U Models Using L-Brackets Main Menu • 93, 96, 596, 597 and Buttons • 13 Maintenance •...
Page 740 PDU Configuration • 149, 376 RADIUS Configuration Illustration • 258, 635 PDU Configuration Commands • 405 Raritan Training Website • 688 PDView App for Viewing the PX3 • 683 RCM Critical State Alarm • xxii, 593 Peripherals • 63, 97, 104, 133, 152, 175, 181, RCM Current Sensor •...
Page 741 Index Resetting the Button-Type Circuit Breaker • Sensor RJ-45 Port Pinouts • 542 Sensor Threshold Configuration Commands • Resetting the Handle-Type Circuit Breaker • Sensor Threshold Settings • 154, 157, 171, 173, Resetting the PX3 • 529 179, 180, 189, 363, 676 Resetting to Factory Defaults •...
Page 742 Index Setting the Alarmed to Normal Delay for Setting the Time Zone • 363, 441 DX-PIR • 491 Setting the X Coordinate • 489 Setting the Authentication Method • 425 Setting the Y Coordinate • 489 Setting the Automatic Daylight Savings Time • Setting the Z Coordinate •...
Page 743 Index Specifying the Secondary NTP Server • 440 Time Units • 145, 153, 169, 266, 267 Specifying the SSH Public Key • 435, 477 Tracing the Route • 534 Standard Attributes • 635 Turning Off the Outlet(s) • 525 Start or Stop a Lua Script • xx, 291, 302, 328, Turning On the Outlet(s) •...
Page 744 Index Viewing or Clearing the Local Event Log • 242, 258, 305, 333, 340 Viewing Saved Snapshots and Managing Storage • 295, 350, 352, 355 W Ways to Probe Existing User Profiles • 688 Web Interface Operations for RCM • 157, 592 Web Interface Overview •...

This manual is also suitable for:

Px3-2000 series