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 Tip 1: The outlet (socket) shall be installed near the equipment and shall be easily accessible. Tip 2: For detailed information on any Raritan PDU's overcurrent protectors' design, refer to that model's product specification on Raritan website's PDU Product Selector page https://www.raritan.com/product-selector...
Page 4 Raritan, Inc. © Copyright 2018 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 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 Button-Type Locking Outlets ....................21 Chapter 3 Initial Installation and Configuration Connecting the PDU to a Power Source ..................22 Connecting the PX3 to Your Network..................... 23 USB Wireless LAN Adapters....................24 Supported Wireless LAN Configuration ................25 ...
Page 8 Contents Connecting a Logitech Webcam..................... 81 Connecting a GSM Modem ......................81 Connecting an Analog Modem ....................... 82 Connecting an External Beeper ..................... 83 Connecting a Schroff LHX/SHX Heat Exchanger ................83 Chapter 5 Introduction to PDU Components ...
Page 9 Contents Inrush Current and Inrush Guard Delay................163 Z Coordinate Format......................164 How the Automatic Management Function Works............164 Time Units .......................... 165 Setting Thresholds for Total Active Energy or Power ............165 +12V Power Supply Sensor (for iX7™ Only) ............... 167 ...
Page 10 Contents Configuring Data Push Settings ..................369 Monitoring Server Accessibility ..................371 Front Panel Settings ......................375 Configuring the Serial Port....................376 Lua Scripts ......................... 378 Miscellaneous ........................384 Maintenance ..........................386 Device Information......................
Page 11 Contents Different CLI Modes and Prompts ..................447 Closing a Local Connection ....................448 The ? Command for Showing Available Commands..............448 Querying Available Parameters for a Command ................. 449 Showing Information ........................450 Network Configuration.......................
Page 12 Contents Network Configuration Commands................... 493 Time Configuration Commands..................522 Checking the Accessibility of NTP Servers ............... 527 Security Configuration Commands..................527 Outlet Configuration Commands ..................548 Inlet Configuration Commands..................550 Overcurrent Protector Configuration Commands............. 552 ...
Page 13 Flexible Cord Selection...................... 640 Plug Selection ........................640 Receptacle Selection ......................640 Derating a Raritan Product....................641 Wiring of 3-Phase In-Line Monitors .................. 642 In-Line Monitor Unused Channels..................642 Step by Step Flexible Cord Installation ................642 ...
Page 14 Contents Appendix A Specifications Maximum Ambient Operating Temperature................656 Serial RS-232 "DB9" Port Pinouts ....................656 Serial RS-232 "RJ-45" Port Pinouts (for iX7™ Only)..............657 Sensor RJ-45 Port Pinouts......................657 Feature RJ-45 Port Pinouts ......................658 ...
Page 15 Contents Firmware Upgrade via USB......................676 Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ..................678 TFTP Requirements........................679 DHCP IPv4 Configuration in Windows..................680 DHCP IPv6 Configuration in Windows..................690 ...
Page 16 Contents Appendix G Old PX3 Character LCD Display Overview of the LCD Display ......................720 Control Buttons ..........................721 Operating the LCD Display ......................721 Outlet Information......................721 Inlet Information ........................ 723 Overcurrent Protector Information ................... 724 ...
Page 17 Unbalanced Current Calculation....................804 Data for BTU Calculation......................805 Ways to Probe Existing User Profiles ..................806 Raritan Training Website......................806 Role of a DNS Server........................806 Cascading Troubleshooting......................807 Possible Root Causes ......................807 ...
Page 18 Contents Index xviii...
Page 19 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 20 Chapter 1: Applicable Models Comparison between PX2, PX3 and PX3-iX7: PX3 with iX7 ™ Product models PX2 Series PX3 Series Controller Dot-matrix LCD Dot-matrix LCD LED display Front panel display display display Outlet latching relays Number of LAN ports Replaceable controller Number of USB-A ports 12 Mbps 12 Mbps...
Page 21 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 xix) Configuring the PX3 (on page 27) Connecting a Mobile Device to PX3 (on page 28)
Page 22 Chapter 1: What's New in the PX3 User Guide Schroff LHX/SHX (on page 231) User Management (on page 237) Creating Users (on page 238) Creating Roles (on page 244) Setting Your Preferred Measurement Units (on page 247) Device Settings (on page 249) Configuring Network Services (on page 274) Configuring Security Settings...
Page 23 What's New in the PX3 User Guide Identifying Snapshots Folders on Remote Servers (on page 425) SmartLock and Card Reader (on page 427) SmartLock (on page 428) Card Readers (on page 432) The ? Command for Showing Available Commands (on page 448) Querying Available Parameters for a Command (on page 449) IP Configuration...
Page 24 Chapter 1: What's New in the PX3 User Guide Removing an Existing LDAP Server (on page 580) Radius Settings (on page 580) Adding a Radius Server (on page 580) Modifying an Existing Radius Server (on page 581) Removing an Existing Radius Server (on page 583) Downloading Diagnostic Data via SCP (on page 635)
Page 25: 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 26: 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 27: 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 28: Before You Begin
Note: Not all PX3 devices have overcurrent protectors. Preparing the Installation Site 1. Make sure the installation area is clean and free of extreme temperatures and humidity. Note: If necessary, contact Raritan Technical Support for the maximum operating temperature for your model. See Maximum (on page 656).
Page 29: 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 660). Use this worksheet to record the model, serial number, and use of each IT device connected to the PDU.
Page 30: Chapter 2 Rackmount, Inlet And Outlet Connections
This chapter describes how to rack mount a PX3 device. Only the most common rackmount method is displayed. Follow the procedure suitable for your model. Rackmount Safety Guidelines In Raritan products which require rack mounting, follow these precautions:  Operation temperature in a closed rack environment may be greater than room temperature.
Page 31: 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 32 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 33: 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 34: 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 35 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 36: 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 37: Mounting 1U Or 2U Models
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 38 Chapter 2: Rackmount, Inlet and Outlet Connections 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners.
Page 39: 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 40: 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 For information on removing the locking line cord, see Disconnecting a Locking Line Cord (on page 16).
Page 41: 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 42: 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 43: 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 44: 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 45: 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 46: 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 ........... 22 Connecting the PX3 to Your Network............23 Configuring the PX3...................
Page 47: 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, you must make a wired connection.
Page 48: 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 49: 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 50: Dual Ethernet Connection (For Ix7™ Only)
Chapter 3: Initial Installation and Configuration Dual Ethernet Connection (for iX7™ Only) An iX7 device 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 51: Configuring The Px3
Chapter 3: Initial Installation and Configuration Configuring the PX3 You can initially configure the PX3 via one of the following:  A TCP/IP network that supports DHCP  A mobile device with PDView installed  A computer physically connected to the PX3 Configuration via a DHCP-enabled network: Connecting the PX3 1.
Page 52: Connecting A Mobile Device To Px3
Chapter 3: Initial Installation and Configuration Connecting a Mobile Device to PX3 Raritan's PDView is a free app that turns your iOS or Android mobile device into a local display for the PX3. PDView is especially helpful when your PX3 is not connected to the network but you need to check the PX3 status, retrieve its information, or change its settings.
Page 53 Chapter 3: Initial Installation and Configuration  Android : USB-B port Step 3: Launch PDView to access the PX3 1. Launch the PDView app from your mobile device. Below illustrate iPad's PDView screens. a. The "Disconnected" message displays first when PDView has not detected the PX3 yet.
Page 54 The PDView shows the "Connected" message when it detects the connected PX3. 2. If the factory-default user credentials "admin/raritan" remain unchanged, PDView automatically logs in to the PX3 web interface. If they have been changed, the login screen displays instead and you must enter appropriate user credentials for login.
Page 55 When PDView detects the PX3, it automatically tries to log in with the factory-default user credentials -- admin (user name) and raritan (password). If the factory-default user credentials have been modified, the automatic login fails and PDView will show the login screen for you to manually enter user credentials.
Page 56: Connecting The Px3 To A Computer
Chapter 3: Initial Installation and Configuration 4. The user credentials setup page opens. 5. Type the desired user credentials, and tap Save. Connecting the PX3 to a Computer The PX3 can be connected to a computer for configuration via one of the following ports.
Page 57 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 58 Chapter 3: Initial Installation and Configuration Note: Not all serial-to-USB converters work properly with the PX3 so Raritan does not introduce the use of such converters. Serial connection for "DB9" RS-232 connector on PX3: 1. Connect one end of the null-modem DB9 cable to the male "DB9"...
Page 59: Bulk Configuration Methods
Chapter 3: Initial Installation and Configuration DB9 pin signal DB9 pin No. RJ-45 pin No. RJ-45 pin signal 1 (Not connected) 9 (Not connected) Note: The blue Cisco RJ-45 to DB9 adapter cable CANNOT be used for connecting a modem. See RJ45-to-DB9 Cable Requirements for Modem Connections (for iX7 Only)
Page 60 Chapter 3: Initial Installation and Configuration pre-3.3.10 firmware version to version 3.3.10 or later, follow the Upgrade Sequence in an Existing Cascading Chain (on page 398). You can have multiple PX3 devices share one Ethernet connection by cascading them via one of the interfaces below: ...
Page 61  The cascading mode of all devices in the chain must be the same.  (WIFI only) You must use Raritan's USB WIFI wireless LAN adapter instead of other WIFI adapters for wireless network connection. Troubleshooting: When a networking issue occurs, check the cascading connection and/or Cascading software settings of all devices in the chain.
Page 62: Cascading Px3 Via Usb
Chapter 3: Initial Installation and Configuration Cascading PX3 via USB You must set the cascading mode before establishing the chain. See Setting the Cascading Mode (on page 265). Any certified USB 2.0 cable up to 5 meters (16 feet) long can be used. Both cascading modes support a maximum of 16 devices in a chain.
Page 63 Number Device role Slave 3 To cascade PX3 devices via USB: 1. Make sure all Raritan devices are running firmware version 3.3.10 or later. 2. Choose the appropriate one as the master device.  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 Port Forwarding mode: Only the master device's network settings should be configured. A tip for USB cascading: The "USB-cascading" chain can be a combination of diverse Raritan products that support the USB-cascading feature, including PX2, PX3, PX3-iX7, transfer switch, BCM and EMX.
Page 65: Extended Cascading With Px3-Ix7 Models
Chapter 3: Initial Installation and Configuration Extended Cascading with PX3-iX7 Models Only PX3-iX7 supports cascading via either Ethernet or USB ports because they have two Ethernet ports and two USB-A ports. You can use either Ethernet port on the iX7 device for cascading.
Page 66 Chapter 3: Initial Installation and Configuration Number Device role Master device Slave 1 Slave 2 Slave 3...
Page 67 1000 Mbps. To cascade iX7 PDUs via Ethernet ports: ™ 1. Make sure all Raritan devices are running firmware version 3.3.10 or later. 2. Choose one iX7 PDU as the master device. ™...
Page 68 Chapter 3: Initial Installation and Configuration  Bridging mode: Each cascaded device has its own network settings. For example, you can have some devices use DHCP-assigned IP addresses and the others use static IP addresses.  Port Forwarding mode: Only the master device's network settings should be configured.
Page 69: Unsupported Cascading Connections For Port Forwarding
USB and Ethernet cables between two cascaded devices. The following diagrams illustrate cascading connections that are NOT supported. Note: These diagrams are based on Raritan's PX3-iX7 Zero U PDUs, but the same guidelines apply to other Raritan iX7 products. ™...
Page 70 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 71: 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 devices can share power supply to their controllers via ™...
Page 72: Making A Power-Sharing Connection
Note: Outlet switching is not available because all outlets lose power.  Monitor the status of connected Raritan environmental sensor packages, or configure/control their settings.  Operate the front panel display. Events that occur when entering the power-sharing mode: ...
Page 73: Power-Sharing Configurations And Restrictions
Chapter 3: Initial Installation and Configuration 2. Connect one end to an iX7 device's EXPANSION port, and the other ™ end to another one's EXPANSION port.  Note that the EXPANSION port location on your iX7 may differ ™ from the following images. Power-Sharing Configurations and Restrictions When either iX7 PDU enters the power-sharing mode, BOTH PDUs...
Page 74: Supported Sensor Configurations For Power Sharing
All information and restrictions described in this section apply to BOTH PDUs involved in the power-sharing configuration, unless otherwise specified. There are no limitations for connecting Raritan's DPX or DPX2 environmental sensor packages to an iX7 PDU in the power-sharing ™...
Page 75 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 52).
Page 76: 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 .......... 52 Connecting Asset Management Strips............71 Connecting a Logitech Webcam..............81 Connecting a GSM Modem ................
Page 77: Identifying The Sensor Port
Chapter 4: Connecting External Equipment (Optional) Identifying the Sensor Port Warning: If you purchase Raritan's environmental sensor packages, make sure you connect them to the correct port on the PX3, or damages may be caused to the PX3 and/or connected sensor packages.
Page 78 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 79 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 80 DPX-ENVHUB4 sensor hub DPX sensor packages Using an Optional DPX-ENVHUB2 cable DPX-ENVHUB2 A Raritan cable doubles the number of connected environmental sensors per SENSOR port. This cable supports DPX sensor packages only. Do NOT connect DPX2, DPX3 or DX sensor packages to it.
Page 81 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 82: Dpx2 Sensor Packages
RJ-12 connector and one to three head connectors. You have to connect DPX2 sensor packages to the sensor cable. For more information on DPX2 sensor packages, access the Environmental Sensors and Actuators Guide (or Online Help) on Raritan Support page http://www.raritan.com/support/...
Page 83 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 84: Dpx3 Sensor Packages
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 64).
Page 85 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 86: Dx Or Dx2 Sensor Packages
For information on connecting actuators or detectors to DX terminals, refer to the Environmental Sensors and Actuators Guide (or Support page Online Help) on Raritan website's http://www.raritan.com/support/ You can cascade up to 12 DX sensor packages. When cascading DX, remember that the PX3 only supports a maximum of 32 sensors and/or actuators.
Page 87 Chapter 4: Connecting External Equipment (Optional) Numbers Components RJ-45 ports, each of which is located on either end of a DX sensor package. RJ-12 port, which is reserved for future use and now blocked. Removable rackmount brackets. Note: A DX2 sensor does not have the RJ-12 port and looks slightly different from the above image.
Page 88 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 89: 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 90 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 91: 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 92 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 93 Chapter 4: Connecting External Equipment (Optional)
Page 94 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 95: 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 96 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 97: 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 98 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 99: 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 100 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 101 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 102: Connecting Composite Asset Strips (Ams-Mx-Z)
Chapter 4: Connecting External Equipment (Optional) Connecting Composite Asset Strips (AMS-Mx-Z) A composite asset strip is named AMS-Mx-Z, where x is a number, such as AMS-M2-Z or AMS-M3-Z. It is a type of asset strip that functions the same as regular MASTER asset strips except for the following differences: ...
Page 103 Chapter 4: Connecting External Equipment (Optional) c. Connect the other end of the cable to the RJ-45 connector labeled "Input" on the secondary composite asset strip. d. Repeat the same steps to connect more composite asset strips. Daisy-Chain Limitations of Composite Asset Strips page 80) for the maximum number of composite asset strips supported per chain.
Page 104  It is NOT supported to hot swap or hot plug any AMS-Mx-Z in a composite asset strip chain that has been connected to Raritan's PDU (or PMC). Therefore, first disconnect the chain from the device when you need to swap or add any AMS-Mx-Z to the chain.
Page 105: 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 106: 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 107: Connecting An External Beeper
Chapter 4: Connecting External Equipment (Optional) Connecting an External Beeper The PX3 supports the use of an external beeper for audio alarms. External beepers that are supported include but may not be limited to the following:  Mallory Sonalert MODEL SNP2R After having an external beeper connected, you can create event rules for the PX3 to switch on or off the external beeper when specific events Event Rules and Actions...
Page 108: 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 109: 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 110: Outlets
Inlet on the side Inlet on the top Outlets The total number of outlets varies from model to model. PX3-3000 Series These models are NOT outlet-switching capable so all outlets are always in the ON state. Outlet LEDs are not available.
Page 111: Connection Ports
Chapter 5: Introduction to PDU Components LED state Outlet status What it means circuitry's power supply is broken. ON and LIVE LIVE power. The outlet is on and power is available. The current flowing through the outlet is greater Red flashing ON and LIVE than the upper warning (non-critical) threshold.
Page 112 Chapter 5: Introduction to PDU Components  CONSOLE/MODEM port x 1 (DB9)  Sensor port x 1 (yellow)  USB-A port x 2  USB-B port x 1  Feature port x 1 (red)  Ethernet port x 1 (green) 9 ports on PX3-iX7 models: ...
Page 113 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 114 Chapter 5: Introduction to PDU Components Port Used for... 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. There are two small LEDs adjacent to the port: ...
Page 115: Dot-Matrix Lcd Display
Chapter 5: Introduction to PDU Components Dot-Matrix LCD Display The following diagram shows the dot-matrix LCD display panel on different Zero U models. PX3 models: PX3-iX7 models: You can use the LCD display to view the PX3 information and even switch an outlet.
Page 116 Chapter 5: Introduction to PDU Components Automatic and Manual Modes After powering on or resetting the PX3, the front panel LCD display first shows the dots, then Raritan logo and finally enters the automatic mode. In all of the LCD operation topics: ...
Page 117 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 118 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 PX3 device, built-in components, or connected peripheral devices ...
Page 119 Chapter 5: Introduction to PDU Components Main Menu The Main Menu contains 7 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 120 If your PX3 supports outlet-switching, you can turn on, off or power cycle Outlets an outlet. Outlets (on page 103). 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. Peripherals (on page 109).
Page 121 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 122 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 208).
Page 123 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 PX3 is a PX3-4000 or PX3-5000 model, it supports the active energy pulse output.
Page 124 Chapter 5: Introduction to PDU Components b. Press to select an option. c. Press to confirm the selection, or to cancel. Note: All outlet LEDs on the PX3 turn OFF after enabling the energy pulsing. You still can turn on or off outlets during the pulsing period though outlet LEDs do not change their status.
Page 125 Chapter 5: Introduction to PDU Components 6. 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. To show the inlet information: 1.
Page 126 Chapter 5: Introduction to PDU Components  For a single-phase model, the second page shows the inlet's voltage (V), frequency (Hz) and current (A).  For a three-phase model, the next several pages respectively show unbalanced current's percentage, line frequency, the current and voltage values of each line.
Page 127 Chapter 5: Introduction to PDU Components 2. The LCD display shows a list of overcurrent protectors similar to the following diagram. Number Description Overcurrent protector names. Associated lines and rated current are displayed below each overcurrent protector's name. Current reading of the corresponding overcurrent protector. 3.
Page 128 Chapter 5: Introduction to PDU Components Showing an Outlet's Information Multiple outlet information can be displayed on the LCD display. Control buttons that can be used and the system time are shown at the bottom of the LCD display. To show an outlet's information: 1.
Page 129 Chapter 5: Introduction to PDU Components Note: In the following diagrams, N represents the selected outlet's number. 5. To go to the next page which shows the outlet's voltage (V), frequency (Hz) and current (A), press 6. To return to the Main Menu, press several times until the Main Menu is shown.
Page 130 Chapter 5: Introduction to PDU Components Power Control This section applies to outlet-switching capable models only. The front panel outlet control must be enabled for performing this power control function. The default is to disable this function. See Miscellaneous (on page 384). Available options for power control vary, based on the power state of the selected outlet.
Page 131 Chapter 5: Introduction to PDU Components 3. Press to select an outlet, and press If the desired outlet is not visible, press to scroll up or down. 4. The LCD display shows the selected outlet's information. For details, Showing an Outlet's Information (on page 104).
Page 132 Chapter 5: Introduction to PDU Components  When the selected outlet has been turned off, 'Switch On' replaces the option of 'Switch Off'. 6. Press to select the desired option, and press  Switch Off: Turn off the outlet.  Switch On: Turn on the outlet.
Page 133 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 134 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 208).  n/a = unavailable  Normal  Alarmed  Lower Critical = below lower critical ...
Page 135 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 136 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 is shown on the LCD display.
Page 137 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 138 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 139 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 221).  The index number in parentheses: The physical port number printed on the asset strip.
Page 140 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 141 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 142 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 265).  Network Bridge Enabled: This device's cascading mode is set to Bridging. Its IP address is also displayed on this page.
Page 143 Chapter 5: Introduction to PDU Components 5. Press to show the ETHERNET page.  For PX3-iX7, there are two Ethernet pages -- ETH1 and ETH2. Number Description Ethernet interface information, including:  MAC address.  Speed.  Full or half duplex.
Page 144 Chapter 5: Introduction to PDU Components Number Description IPv4/IPv6 network information, including:  Network configuration: DHCP (or Automatic), or Static. Static represents Static IP.  IP address.  Prefix length, such as "/24". Note: If you disable any Ethernet interface, a message 'Interface Disabled' is shown.
Page 145 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. ...
Page 146: 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 succeeds or fails.
Page 147: 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 148: 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 149: 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 150: 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 151 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 152: 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 153: Replaceable Controller
If the controller is broken, you can simply send the controller back to Raritan for repair, or purchase a new controller from Raritan. 1U / 2U PDUs and all of PX3-3000 series do NOT support this feature. To request a new controller: Contact tech@raritan.com to request a new PX3 controller.
Page 154 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 155: 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 ............... 131 Login, Logout and Password Change ............. 132 Web Interface Overview................136 Dashboard ....................144 PDU......................
Page 156: Login, Logout And Password Change
Chapter 6: Using the Web Interface Login, Logout and Password Change The first time you log in to the PX3, use the factory default "admin" user credentials. For details, see the Quick Setup Guide accompanying the product. After login, you can create user accounts for other users. See Creating Users (on page 238).
Page 157 Chapter 6: Using the Web Interface  To select the agreement checkbox using the keyboard, first press Tab to go to the checkbox and then Enter. Note: To configure the security agreement, see Enabling the Restricted Service Agreement (on page 306). 5.
Page 158: Changing Your Password
Chapter 6: Using the Web Interface Changing Your Password You must have the Change Own Password permission to change your own password. See Creating Roles (on page 244). You must have Administrator Privileges to change other users' Editing or Deleting Users passwords.
Page 159: Remembering User Names And Passwords
Chapter 6: Using the Web Interface  A password comprises 4 to 64 characters. Remembering User Names and Passwords The PX3 supports the password manager of common web browsers, including:  Microsoft Internet Explorer ®  Mozilla Firefox ®  Google Chrome ®...
Page 160: Web Interface Overview
Chapter 6: Using the Web Interface Web Interface Overview The web interface consists of four areas as shown below. Operation: 1. Click any menu or submenu item in the area of 2. That item's data/setup page is then opened in the area of 3.
Page 161 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 139) Data/setup page of the selected menu item.  Left side:...
Page 162 - See Browsing through the Online Help (on page 824).  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, which is converted to the time zone of your computer or mobile device.
Page 163: Menu
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 164 Either or both menu items appear only when you connect the equipment -- and/or -- included in a Raritan's SmartLock kit to PX3. For details, refer to the user Card Readers documentation accompanying the SmartLock kit or download it from Support page http://www.raritan.com/support/...
Page 165 Chapter 6: Using the Web Interface Menu Information shown Device Settings Device-related settings, including network, security, system time, event rules and more. Device Settings (on page 249). Maintenance Device information and maintenance commands, such as firmware upgrade, device backup and reset. Maintenance (on page 386).
Page 166: Quick Access To A Specific Page
Chapter 6: Using the Web Interface Quick Access to a Specific Page If you often visit a specific page in the PX3 web interface, you can note down its URL or bookmark it with your web browser. Next time, you can simply enter its URL in the address bar of the browser prior to login.
Page 167 Chapter 6: Using the Web Interface 3. The arrow turns to , indicating the list is sorted in the "ascending" order. 4. To resort the list based on a different column, click a different column header. In this example, the 'Event Class' column is clicked. 5.
Page 168: Dashboard
Chapter 6: Using the Web Interface Dashboard The Dashboard page contains four to five sections, depending on your model.
Page 169 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 146).
Page 170: 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 171 Chapter 6: Using the Web Interface The left side lists all or some of the following data. Available data is model dependent.  Active power (kW or W)  Apparent power (kVA or VA)  Active energy (kWh or Wh) ...
Page 172: Dashboard - Ocp
Chapter 6: Using the Web Interface  A bar showing the RMS current level  RMS voltage (V) The RMS current bars automatically change colors to indicate the current status if the thresholds have been enabled. To configure thresholds, see Inlet (on page 168).
Page 173 Chapter 6: Using the Web Interface Each OCP's power data: OCP data from top to bottom includes:  RMS current (A), and rated current  Smaller gray text adjacent to RMS current is each OCP's rated current, such as "16A" shown in the above diagram. ...
Page 174: 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 175 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 176: Dashboard - Inlet History
Chapter 6: Using the Web Interface Dashboard - Inlet History The power chart 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 chart of other inlet power data.
Page 177 Chapter 6: Using the Web Interface  To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. Inlet selection on multi-inlet models: If your PDU is a multi-inlet model, you can have one or multiple inlets show their power charts by selecting the checkbox(es) of the desired inlet(s).
Page 178 Chapter 6: Using the Web Interface  When multiple inlets are displayed in the chart, their colors differ. You can identify each inlet's data according to the colors of the selected inlet checkboxes.  When both inlets are shown in the chart, simply hover your mouse over either inlet's data line.
Page 179: Dashboard - Alarms
Chapter 6: Using the Web Interface Dashboard - Alarms If configuring any event rules which require users to take the acknowledgment action, the Alarms section will list any event which no one acknowledges yet since event occurrence. Note: For information on event rules, see Event Rules and Actions page 312).
Page 180 Chapter 6: Using the Web Interface Field Description More Alerts This field appears only when there are more than one type of events triggering this alert. If there are other types of events (that is, other reasons) triggering the same alert, the total number of additional reasons is displayed.
Page 181: 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 139). Device information shown:  Firmware version ...
Page 182 Chapter 6: Using the Web Interface  For time-related fields, if you do not prefer the option selection using , you can type a value manually which must include a Time Units time unit, such as '50 s'. See (on page 165). In the following table, those fields marked with * are available on an outlet-switching capable model only.
Page 183 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 803). attached.
Page 184 Chapter 6: Using the Web Interface 3. Click Save. To reset ALL active energy counters: An active energy reading is a value of total accumulated energy, which is never reset, even if the power fails or the PX3 is rebooted. However, you can manually reset this reading to restart the energy accumulation process.
Page 185: Internal Beeper State
Chapter 6: Using the Web Interface To configure the thresholds of total active energy and power: For a multi-inlet model or an in-line monitor, a "Thresholds" section is Setting Thresholds for Total Active also available on the PDU page. See Energy or Power (on page 165).
Page 186: 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 187: Initialization Delay Use Cases
Chapter 6: Using the Web Interface If you are configuring an individual outlet on Individual Outlet Pages page 183), there is one more outlet state option. Additional Function option PDU defined Follows the global outlet state setting, which is set (xxx) (on page 157).
Page 188: Z Coordinate Format
Chapter 6: Using the Web Interface Z Coordinate Format Z coordinates refer to vertical locations of environmental sensors and actuators. You can use either the number of rack units or a descriptive text to describe Z coordinates. Sensor/Actuator Location Example For a Z coordinate example, see page 219).
Page 189: 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 190 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 191: Power Supply Sensor (For Ix7™ Only)
Chapter 6: Using the Web Interface +12V Power Supply Sensor (for iX7™ Only) An iX7 PDU's controller receives DC 12V power from its inlet. A sensor ™ monitors the power supply status and indicates it on the PDU page. State Description The iX7 controller is receiving power from its inlet.
Page 192: Inlet
Chapter 6: Using the Web Interface Inlet You can view all inlet information, configure inlet-related settings, or reset the inlet active energy on the Inlet page. To open this page, click Menu 'Inlet' in the (on page 139). Inlet thresholds, when enabled, help you identify whether the inlet enters the warning or critical level.
Page 193 Chapter 6: Using the Web Interface To reset the inlet's active energy counter: Only users with the "Admin" role assigned can reset active energy readings. The energy reset feature per inlet is especially useful when your PX3 has more than one inlet. 1.
Page 194 Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 793). 4. Click Save. To configure residual current thresholds: If your model supports residual current monitoring, a section titled "Residual Current Monitor"...
Page 195: Configuring A Multi-Inlet Model
Chapter 6: Using the Web Interface Configuring a Multi-Inlet Model If the PX3 has more than one inlet, the Inlets page lists all inlets. To view or configure each inlet: 1. Click 'Show Details' of the desired inlet. 2. Now you can configure the selected inlet, such as enabling Inlet thresholds or resetting its energy.
Page 196 Chapter 6: Using the Web Interface 3. Click Save. 4. The inlet status now shows "Disabled." 5. To disable additional inlets, repeat the above steps.  If disabling an inlet will result in all inlets being disabled, a confirmation dialog appears, indicating that all inlets will be disabled.
Page 197: Outlets
Chapter 6: Using the Web Interface Outlets The Outlets page shows a list of all outlets and the overview of outlet Menu status and readings. To open this page, click 'Outlets' in the page 139). On this page, you can: ...
Page 198 Chapter 6: Using the Web Interface  Go to an individual outlet's data/setup page by clicking an Individual Outlet Pages outlet's name. See (on page 183). If wanted, you can resort the list by clicking the desired column header. Sorting a List (on page 142).
Page 199 Chapter 6: Using the Web Interface To power control or reset the active energy readings of multiple outlets: You can switch any outlet regardless of its current power state. That is, you can turn on any outlet that is already turned on, or turn off any outlet that is already turned off.
Page 200: Available Data Of The Outlets Overview Page
Chapter 6: Using the Web Interface Tip: To reset ALL active energy counters on the PX3, see page 157). You can also power control an outlet or reset its active energy from (on page 183). Individual Outlet Pages 4. When performing any outlet-switching operation, a 'Sequence running' message similar to the following displays before the outlet-switching process finishes.
Page 201: Bulk Configuration For Outlet Thresholds
Chapter 6: Using the Web Interface  RMS current (A)  Active power (W)  Power factor  Non-critical setting for indicating whether the outlet is a non-critical outlet. This information is available on outlet-switching capable models only. Non-critical setting Description true The outlet is a non-critical outlet, which will...
Page 202 Chapter 6: Using the Web Interface  To select ALL outlets, select the topmost checkbox in the header row. 4. Click Edit Thresholds. 5. Make changes as needed.  To enable any threshold, select the corresponding checkbox.  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings...
Page 203: Setting Outlet Power-On Sequence And Delay
Chapter 6: Using the Web Interface Setting Outlet Power-On Sequence and Delay By default, outlets are sequentially powered on in the ascending order from outlet 1 to the final when turning ON or power cycling all outlets on the PX3 device. You can change the order in which the outlets power ON. This is useful when there is a specific order in which some IT equipment should be powered up first.
Page 204: Setting Non-Critical Outlets
Chapter 6: Using the Web Interface The PX3 will insert a power-on delay between the configured outlet and the one following it during the power-on process. Setting Non-Critical Outlets Outlets that are turned off when load shedding is activated are called non-critical outlets.
Page 205: 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 outlets.
Page 206 Chapter 6: Using the Web Interface  The message "Load Shedding Active" appears next to the 'Outlets' title. Tip: To make the Non Critical column appear on the Outlets page. See Outlets (on page 173) or Available Data of the Outlets Overview Page (on page 176).
Page 207: Individual Outlet Pages
Chapter 6: Using the Web Interface Individual Outlet Pages An outlet's data/setup page is opened after clicking the outlet's name on the Outlets overview page. See Outlets (on page 173). The individual outlet's page shows this outlet's detailed information. See Detailed Information on Outlet Pages (on page 189).
Page 208 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. 2. Confirm it on the confirmation message. Tip: To switch an outlet using the front panel display, see Power Control (on page 106).
Page 209 Chapter 6: Using the Web Interface Field Descriptions *Power off period Select an option to determine how long this during power cycle outlet is turned off before turing back on.  Options: PDU defined or customized time. Power-Off Period Options for Individual Outlets (on page 190).
Page 210 Chapter 6: Using the Web Interface Tip: To reset ALL active energy counters on the PX3, see (on page 157). To view this outlet's power chart: By default this outlet's active power data within the past tens of minutes is shown in the power chart. You can click the selector below the chart to show a different data type for this outlet, including:...
Page 211 Chapter 6: Using the Web Interface  To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. To configure this outlet's threshold settings: Per default, there are pre-defined RMS voltage and current threshold Default Voltage and Current Thresholds values in related fields.
Page 212 Chapter 6: Using the Web Interface 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 (on page 793).
Page 213 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 214 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 Sensors section: ...
Page 215: Ocps
Chapter 6: Using the Web Interface OCPs The OCPs page is available only when your PX3 has overcurrent protectors, such as circuit breakers. The OCPs page lists all overcurrent protectors as well as their status. If any OCP trips or its current level enters the alarmed state, it is Yellow- or Red-Highlighted Sensors highlighted in red or yellow.
Page 216 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 the two thresholds for current levels. ...
Page 217: Individual Ocp Pages
Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 793). 5. Click Save. Individual OCP Pages An OCP's data/setup page is opened after clicking any OCP's name on OCPs Dashboard the OCPs or Dashboard page.
Page 218 Chapter 6: Using the Web Interface Field Description Protected Outlets Outlets associated with this OCP. Inlet Inlet associated with this OCP. This information is useful only when your PDU has multiple inlets. RMS current This OCP's current state and readings, including current drawn and current remaining.
Page 219 Chapter 6: Using the Web Interface  To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. To configure this OCP's threshold settings: By default, upper thresholds of an OCP's RMS current have been Default Voltage and Current Thresholds configured.
Page 220 Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 793). 4. Click Save.
Page 221 Chapter 6: Using the Web Interface Other operations:  You can go to another OCP's data/setup page by clicking the OCP selector on the top-left corner.  You can go to the associated Inlet's data page by clicking the Inlet link in the Details section.
Page 222: Possible Ocp-Tripped Root Cause
Chapter 6: Using the Web Interface Possible OCP-Tripped Root Cause This feature applies to PX3-5000 and PX3-4000 models only. As of release 3.4.0, outlet-metered models that support "outlet peak current" sensors can detect which outlet is LIKELY to cause the associated OCP to trip, and indicate it on several user interfaces, including the web interface, front panel display, and command line interface (CLI).
Page 223 Chapter 6: Using the Web Interface Front panel display: Only a dot-matrix LCD display can show this message, but a character LCD display cannot. The 'Likely trip cause' message will be displayed for an "open" OCP, OCPs indicating which outlet may cause the OCP-tripped event. See page 102).
Page 224: 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 52). An environmental sensor package comprises one or some of the following sensors/actuators: ...
Page 225 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 142). Sensor/actuator overview on this page: If any sensor enters the alarmed state, it is highlighted in yellow or red.
Page 226 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 210). Position The data indicates where this sensor or actuator is located in the sensor chain.
Page 227 Chapter 6: Using the Web Interface  To select ALL sensors/actuators, select the topmost checkbox in the header row. Figure 2: Select all checkboxes 3. To release selected ones, click > Release. To manage them, click > Manage.  The management action triggers a "Manage peripheral device" dialog.
Page 228 Chapter 6: Using the Web Interface To configure default threshold settings: Note that any changes made to default threshold settings not only re-determine the initial threshold values applying to newly-added sensors but also the threshold values of the already-managed sensors Individual where default thresholds are being used.
Page 229 Chapter 6: Using the Web Interface For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 793). 4. Click Save. Tip: To customize the threshold settings on a per-sensor basis, go to (on page 214). Individual Sensor/Actuator Pages To turn on or off any actuator(s): in the same status...
Page 230: Yellow- Or Red-Highlighted Sensors
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 231: Managed Vs Unmanaged Sensors/Actuators
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 232: Sensor/Actuator States
Chapter 6: Using the Web Interface  Sensor/Actuator States They show one of the managed states. See (on page 208).  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 233 Note that for a contact closure sensor, the normal state depends on the normal setting you have configured. Refer to the Environmental Sensors and Actuators Guide (or Online Help) for detailed information, which is Support page available on Raritan's http://www.raritan.com/support/ Managed actuator states: State Description The actuator is turned on.
Page 234: 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 235: Identifying The Sensor Position And Channel
Port 1, Chain Position 2 For example,  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. Hub Port 3 For example, ...
Page 236: 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 237 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 238: 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 239 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 own sensor type, select the Use Default Thresholds checkbox. The default threshold settings are configured on the page of Peripherals (on page 200).
Page 240 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 241 Chapter 6: Using the Web Interface To view a numeric sensor's chart This sensor's data within the past tens of minutes is shown in the chart. Note that only a numeric sensor has this diagram. State sensors and actuators do not have such data. ...
Page 242 Chapter 6: Using the Web Interface To turn on or off an actuator: 1. Click the desired control button. : Turn ON. : Turn OFF. 2. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on. Note: If you try to turn on more than one "powered dry contact"...
Page 243: Sensor/Actuator Location Example
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 244 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 221), External Beeper Schroff LHX/SHX Power CIM...
Page 245: Asset Strip
Miscellaneous (on page 384). 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 71).
Page 246 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 247 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 248 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 249 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 250 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 251 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 252 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 253 Chapter 6: Using the Web Interface Tip: Another way to abort changes is to click Rack Units. Refer to the diagram below. 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.
Page 254: External Beeper
Chapter 6: Using the Web Interface External Beeper After connecting and detecting a supported external beeper, the PX3 shows 'External Beeper' in place of 'Feature Port' in the menu. Note: For connection instructions, see Connecting an External Beeper (on page 83). Menu To open the External Beeper page, click it in the (on page 139).
Page 255: Schroff Lhx/Shx
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 384). After enabling the LHX/SHX support and connecting a supported Schroff ®...
Page 256 Chapter 6: Using the Web Interface For the functionality of this icon on the top-right corner, see Feature Port (on page 219). 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 257 Chapter 6: Using the Web Interface To configure LHX/SHX settings: 1. Click Edit Settings. 2. Configure the settings as needed.  Provide a customized name.  Specify the desired air outlet setpoint temperature.  Specify the default fan speed. 3. Click Save. To view all sensor data and configure thresholds: 1.
Page 258 Chapter 6: Using the Web Interface b. Click Edit Thresholds. c. Enable and set the desired thresholds and deassertion hysteresis. Note that assertion timeout is NOT available on LHX/SHX. d. Click Save. 3. After thresholds are enabled, sensors may be highlighted in yellow or red if they enter the warning or critical range.
Page 259 Chapter 6: Using the Web Interface 2. If any LHX sensors fail, they are indicated. Click Acknowledge to acknowledge the sensor failure. 3. To view the history of LHX events, click Show Event Log to go to the Event Log page. Operation time statistics: This section indicates the accumulative operation hours of the LHX/SHX device and its fans since the device is connected to the PX3 and turned...
Page 260: Power Cim
To stop maximum cooling:  Click Cancel Maximum Cooling. Power CIM After connecting and detecting a Raritan power CIM, the PX3 shows Dominion KX II / 'Power CIM' in place of 'Feature Port' in the menu. See III Configuration Dominion KSX II, SX or SX II...
Page 261: User Management
Chapter 6: Using the Web Interface User Management User Management menu deals with user accounts, permissions, and preferred measurement units on a per-user basis. The PX3 is shipped with one built-in administrator account: admin, which is ideal for initial login and system administration. You cannot delete 'admin' or change its permissions, but you can and should change its password.
Page 262: 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 263 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 134). SSH: You need to enter the SSH public key only if the public key authentication Changing SSH Settings for SSH is enabled.
Page 264 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 265 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 266: 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 267 Chapter 6: Using the Web Interface  To delete this user, click , and confirm the operation. 3. Click Save. To delete multiple user accounts: 1. On the Users page, click to make checkboxes appear in front of user names. Tip: To delete only one user, you can simply click that user without making the checkboxes appear.
Page 268: 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. Creating Users The PX3 provides two built-in roles. See (on page 238). Built-in role Description Admin Provide full permissions. Operator Provide frequently-used permissions, including: ...
Page 269: Editing Or Deleting Roles
Chapter 6: Using the Web Interface 5. If any privilege requires the argument setting, the symbol well as the text 'Add XXX' display on that privilege's row, where XXX is the privilege's name. To select such a privilege: a. Click on that privilege's row to display a list of available arguments for this privilege.
Page 270 Chapter 6: Using the Web Interface The Admin role is not user-configurable so the lock icon displays, indicating that you are not allowed to configure it. To edit a role: 1. On the Roles page, click the desired role. The Edit Role page opens. 2.
Page 271: Setting Your Preferred Measurement Units
Chapter 6: Using the Web Interface Setting Your Preferred Measurement Units You can change the measurement units shown in the PX3 user interface according to your own preferences regardless of the permissions you have. Tip: Preferences can also be changed by administrators for specific users on the Edit User page.
Page 272: Setting Default Measurement Units
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 248).
Page 273: Device Settings
Chapter 6: Using the Web Interface Device Settings Menu Click 'Device Settings' in the (on page 139), and the following submenu displays. Menu command Submenu command Refer to... Configuring Network Settings Network (on page 251) Changing HTTP(S) Settings Network Services HTTP (on page 275) Configuring SNMP Settings...
Page 274 Chapter 6: Using the Web Interface Menu command Submenu command Refer to... Configuring SMTP Settings SMTP Server (on page 278) Changing SSH Settings (on page 280) Changing Telnet Settings Telnet (on page 281) Changing Modbus Settings Modbus (on page 281) Enabling Service Advertising Server Advertising (on page 282)
Page 275: Configuring Network Settings
Chapter 6: Using the Web Interface Configuring Network Settings Configure wired, wireless, and Internet protocol-related settings on the Network page after connecting the PX3 to your network (on page 23). You can enable both the wired and wireless networking on the PX3 so that it has multiple IP addresses -- wired and wireless IP.
Page 276 Chapter 6: Using the Web Interface 5. To configure the ETHERNET (or ETH1/ETH2) interface settings, see Ethernet Interface Settings (on page 254). 6. Click Save. After enabling either or both Internet protocols: After enabling IPv4 and/or IPv6, all but not limited to the following protocols will be compliant with the selected Internet protocol(s): ...
Page 277 Chapter 6: Using the Web Interface Field/setting Description  Static : Manually configure the IPv4 settings.  DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements:  Consists of alphanumeric characters and/or hyphens  Cannot begin or end with a hyphen ...
Page 278 Chapter 6: Using the Web Interface Field Description DNS Resolver Determine which IP address is used when the Reference DNS resolver returns both IPv4 and IPv6 addresses.  IPv4 Address: Use the IPv4 addresses.  IPv6 Address: Use the IPv6 addresses. DNS Suffixes Specify a DNS suffix name if needed.
Page 279 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 280 Chapter 6: Using the Web Interface Field/setting Description Hardware State Check this field to ensure that the PX3 device has detected a wireless USB LAN adapter. If not, verify whether the USB LAN adapter is firmly connected or whether it is supported. Type the name of the wireless access point (AP) SSID Force AP BSSID...
Page 281 Chapter 6: Using the Web Interface  Available settings for the CA Certificate: If the required certificate file is a chain of certificates, and you are not TLS Certificate sure about the requirements of a certificate chain, see Chain (on page 817). Field/setting Description Enable verification...
Page 282 Chapter 6: Using the Web Interface Field/setting Description  DHCP Configuration : 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 283 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 284 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 285 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 enter the data as shown below.
Page 286 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:  Your PX3: fd07:2fa:6cff:2405::30 ...
Page 287 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 enter the data as shown below.
Page 288 Chapter 6: Using the Web Interface Interface list for PX3: Interface name Description When another wired network is connected to the BRIDGE Ethernet port of your PX3, and your PX3 has been set to the bridging mode, select this interface name instead of the Ethernet interface.
Page 289 Note: PX3 in the Port Forwarding mode does not support APIPA. See (on page 3). APIPA and Link-Local Addressing To configure the cascading mode: 1. Connect the Raritan device to the LAN and find its IP address, or connect it to a computer.  Connecting the PX3...
Page 290 Chapter 6: Using the Web Interface Note that if either setting below is incorrectly configured, a networking issue occurs. Field Description Master or Slave. Role This is to determine which device is the (available on all master and which ones are slave cascaded devices) devices.
Page 291 Online cascading information: For detailed information on the cascading configuration and restrictions, Cascading Guide see the , which is available from Raritan website's Support page http://www.raritan.com/support/ Overview of the Cascading Modes You must apply a cascading mode to the cascading chain. See...
Page 292 Chapter 6: Using the Web Interface In this mode, the DHCP server communicates with the master device alone and assigns one IP address to the master device. All slave devices share the same IP address as the master device. You must specify a 5XXXX port number (where X is a number) when remotely accessing any slave device with the shared IP address.
Page 293 Chapter 6: Using the Web Interface Protocols HTTP TELNET SNMP MODBUS  XX is a two-digit number representing the device position as shown below. Position Position Master device Slave 8 Slave 1 Slave 9 Slave 2 Slave 10 Slave 3 Slave 11 Slave 4 Slave 12...
Page 294 Slave device: Assign proper 5NNXX port numbers. Assumption: The Port Forwarding mode is applied to a cascading chain 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 295 Chapter 6: Using the Web Interface  To access the master device via SSH, the command is: ssh -p 50200 192.168.84.77 Examples using standard TCP/UDP ports:  To access the master device via HTTPS, the IP address is: https://192.168.84.77:443/  To access the master device via HTTP, the IP address is: http://192.168.84.77:80/ ...
Page 296 (on page 807). To add a device to an existing chain: 1. Connect the Raritan device to the LAN and find its IP address, or connect it to a computer. 2. Log in to this device and set its cascading mode to be the same as Setting the Cascading the existing chain's cascading mode.
Page 297 Chapter 6: Using the Web Interface To swap the master and slave device:  In the Bridging mode, you can swap the master and slave devices by simply disconnecting ALL cascading cables from them, and then reconnecting cascading cables. No changes to software settings are required.
Page 298: Configuring Network Services
Chapter 6: Using the Web Interface Configuring Network Services The PX3 supports the following network communication services. HTTPS and HTTP enable the access to the web interface. Telnet and SSH Using the enable the access to the command line interface. See Command Line Interface (on page 444).
Page 299 Enabling Service Advertising Service Advertising (on page 282) 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 300 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 301 Chapter 6: Using the Web Interface 2. Enable or disable "SNMP v1 / v2c" and/or "SNMP v3" by clicking the corresponding checkbox.  The SNMP v1/v2c read-only access is enabled by default. The default Read Community String is 'public.'  To enable read-write access, type the Write Community String.
Page 302 Chapter 6: Using the Web Interface  sysName - the name assigned to the system  sysLocation - the location of the system 4. To configure SNMP notifications: a. Select the Enable SNMP Notifications checkbox. b. Select a notification type -- SNMPv2c Trap, SNMPv2c Inform, SNMPv3 Trap, and SNMPv3 Inform.
Page 303 Chapter 6: Using the Web Interface Field Description Server Name Type the name or IP address of the mail server. Port Type the port number.  Default is 25 Sender Email Type an email address for the sender. Address Number of Sending Type the number of email retries.
Page 304 Chapter 6: Using the Web Interface Field/setting Description  Select this checkbox to make the Allow expired and authentication succeed regardless of the not yet valid certificate's validity period. certificates  After deselecting this checkbox, the authentication fails whenever any certificate in the selected certificate chain is outdated or not valid yet.
Page 305 Chapter 6: Using the Web Interface  Password authentication only: Enables the password-based login only.  Public key authentication only: Enables the public key-based login only.  Password and public key authentication: Enables both the password- and public key-based login. This is the default. 5.
Page 306 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 307: 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 308 Chapter 6: Using the Web Interface Creating IP Access Control Rules IP access control rules (firewall rules) determine whether to accept or discard traffic to/from the PX3, based on the IP address of the host sending or receiving the traffic. When creating rules, keep these principles in mind: ...
Page 309 Chapter 6: Using the Web Interface ADD a rule to the end of the list  Click Append.  Type an IP address and subnet mask in the IP/Mask field.  Select an option in the Policy field.  Accept: Accepts traffic from/to the specified IP address(es). ...
Page 310 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 311 Chapter 6: Using the Web Interface Editing or Deleting IP Access Control Rules When an existing IP access control rule requires updates of IP address range and/or policy, modify them accordingly. Or you can delete any unnecessary rules. To modify or delete a rule: 1.
Page 312 Chapter 6: Using the Web Interface  Deny: Rejects any user's login attempt when no matching rules are present. 4. Create rules. Refer to the tables below for different operations. ADD a rule to the end of the list  Click Append. ...
Page 313 Chapter 6: Using the Web Interface  You can select any existing rule and then click to change its priority. 6. Click Save. The rules are applied. To configure IPv6 access control rules: 1. On the same page, select the "Enable Role Based Access Control for IPv6"...
Page 314 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 315 IP addresses of the wanted hosts to this CSR so that a single certificate will be valid for all of them. Click when there are more than one additional hosts to add.  Examples of subject alternative names: support.raritan.com help.raritan.com help.raritan.net , and 192.168.77.50...
Page 316 Chapter 6: Using the Web Interface  Key Creation Parameters: Field Do this Key Length Select an available key length (bits). A larger key length enhances the security, but slows down the PX3 device's response.  Only 2048 is available now. Self Sign For requesting a certificate signed by the CA, ensure this checkbox is NOT selected.
Page 317 Chapter 6: Using the Web Interface 2. Click to navigate to the CA-signed certificate file. 3. Click Upload to install it. 4. To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section. 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...
Page 318 Chapter 6: Using the Web Interface Field Description Validity in days This field appears after the Self Sign checkbox is selected. Type the number of days for which the self-signed certificate will be valid. A password is not required for a self-signed certificate so the Challenge and Confirm Challenge fields disappear.
Page 319 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 320 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 321 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 322 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 323 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 324 Chapter 6: Using the Web Interface Field/setting Description Anonymous Bind Use this checkbox to enable or disable anonymous bind.  To use anonymous bind, select this checkbox.  When a Bind DN and password are required to bind to the external LDAP/LDAPS server, deselect this checkbox.
Page 325 Chapter 6: Using the Web Interface 5. Click Add Server. The new LDAP server is listed on the Authentication page. 6. To add more servers, repeat the same steps. 7. In the Authentication Type field, select LDAP. Otherwise, the LDAP authentication does not work.
Page 326 Chapter 6: Using the Web Interface Field/setting Description Type of RADIUS Select an authentication protocol. Authentication  PAP (Password Authentication Protocol)  CHAP (Challenge Handshake Authentication Protocol)  MS-CHAPv2 (Microsoft Challenge Handshake Authentication Protocol) CHAP is generally considered more secure because the user name and password are encrypted, while in PAP they are transmitted in the clear.
Page 327 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 328 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 329 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 625). Unblocking a User To set limitations for login timeout and use of identical login names: 1.
Page 330 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 331 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 on the login screen. Do either of the following, or the login fails:  In the web interface, select the checkbox labeled "I understand and accept the Restricted Service Agreement."...
Page 332: Setting The Date And Time
Chapter 6: Using the Web Interface Setting the Date and Time Set the internal clock on the PX3 device manually, or link to a Network Time Protocol (NTP) server. Note: If you are using Sunbird's Power IQ to manage the PX3, you must configure Power IQ and the PX3 to have the same date/time or NTP settings.
Page 333 Chapter 6: Using the Web Interface Use the NTP server  Select "Synchronize with NTP Server."  There are two ways to assign the NTP servers:  To use the DHCP-assigned NTP servers, DO NOT enter any NTP servers for the First and Second NTP Server.
Page 334 Chapter 6: Using the Web Interface Calendar The calendar icon in the Date field is a convenient tool to select a custom date. Click it and a calendar similar to the following appears. Number Item Description arrows Switch between months. dates All dates of the selected month.
Page 335 Chapter 6: Using the Web Interface Windows NTP Server Synchronization Solution The NTP client on the PX3 follows the NTP RFC so the PX3 rejects any NTP servers whose root dispersion is more than one second. An NTP server with a dispersion of more than one second is considered an inaccurate NTP server by the PX3.
Page 336: 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 337 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 338 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 339 Chapter 6: Using the Web Interface 5. In this example, Numeric Sensor is selected because we want to select numeric-sensor-related event(s). Then a field for numeric-sensor-related events appears. Click this field to select one of the numeric-sensor-related events from the list. 6.
Page 340 Chapter 6: Using the Web Interface  To select all available actions, click Select All. 9. To remove any action(s) from the Selected Actions field, click that action's  To remove all actions, click Deselect All. Radio buttons for different events: According to the event you select, the "Trigger condition"...
Page 341 Chapter 6: Using the Web Interface Event types Radio buttons Sensor availability Available radio buttons include "Unavailable," "Available" and "Both."  Unavailable: The PX3 takes the action only when the chosen sensor is NOT detected and becomes unavailable.  Available: The PX3 takes the action only when the chosen sensor is detected and becomes available.
Page 342 Chapter 6: Using the Web Interface Event types Radio buttons  Monitoring started: The PX3 takes the action Server monitoring only when the monitoring of any specified event server starts.  Monitoring stopped: The PX3 takes the action only when the monitoring of any specified server stops.
Page 343 Chapter 6: Using the Web Interface Default Log Messages These default log messages are recorded internally and emailed to specified recipients when PX3 events occur (are TRUE) or, in some cases, Send Email stop or become unavailable (are FALSE). See (on page 339) to configure email messages.
Page 344 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Asset Management > Composition changed on composite Composite Asset Strip asset strip [AMSNUMBER] Composition Changed ('[AMSNAME]'). Card Reader Management > Card Reader with id Card inserted '[CARDREADERID]' connected.
Page 345 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Device > Device settings Device settings restored from host restored '[USERIP]'. Device > Data push failed Data push to URL [DATAPUSH_URL] failed.
Page 346 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Device > Slave connected Slave connected. Slave disconnected. Device > WLAN authentication Established connection to wireless over TLS with incorrect system network '[SSID]' via Access Point with clock BSSID '[BSSID]' using '[AUTHPROTO]'...
Page 347 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 State Sensor/Actuator > '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot Unavailable '[EXTSENSORSLOT]' unavailable.
Page 348 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Inlet > * > Sensor > * > Warning Sensor '[INLETSENSOR]' on inlet Sensor '[INLETSENSOR]' on inlet '[INLET]' entered warning state. '[INLET]' exited warning state.
Page 349 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Inlet > Pole > * > Sensor > Sensor '[PDUPOLESENSOR]' on pole Sensor '[PDUPOLESENSOR]' on Warning '[INLETPOLE]' of inlet '[INLET]' pole '[INLETPOLE]' of inlet '[INLET]' entered warning state.
Page 350 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE [SENSORREADINGUNIT]. [SENSORREADINGUNIT]. Outlet > * > Sensor > * > Below Sensor '[OUTLETSENSOR]' on outlet Sensor '[OUTLETSENSOR]' on lower warning threshold '[OUTLET]' asserted 'below lower outlet '[OUTLET]' deasserted 'below warning' at [SENSORREADING]...
Page 351 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE [SENSORREADING] critical' at [SENSORREADING] [SENSORREADINGUNIT]. [SENSORREADINGUNIT]. Overcurrent Protector > * > Sensor '[OCPSENSOR]' on overcurrent Sensor '[OCPSENSOR]' on Sensor > * > Unavailable protector '[OCP]' unavailable.
Page 352 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE PDU > Controller > * > OK Controller '[CONTROLLER]' with board Controller '[CONTROLLER]' with ID [BOARDID] is OK. board ID [BOARDID] is no longer PDU >...
Page 353 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE '[USERIP]'. User Administration > User User '[UMTARGETUSER]' deleted by deleted user '[USERNAME]' from host '[USERIP]'. User Administration > Password of user '[UMTARGETUSER]' Password changed changed by user '[USERNAME]' from host '[USERIP]'.
Page 354 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > Sensor > Above Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX at upper critical threshold [PORTTYPE] port '[PORTID]' asserted [PORTTYPE] port '[PORTID]' 'above upper critical' at deasserted 'above upper critical' at...
Page 355 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > ST-Bus An ST-Bus communication error was Communication Error detected on LHX at [PORTTYPE] port '[PORTID]'. LHX/SHX > Collective fault A collective fault occurred on LHX at [PORTTYPE] port '[PORTID]'.
Page 356 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > External Water An external water cooling failure Cooling Failure occurred on LHX at [PORTTYPE] port '[PORTID]'. LHX/SHX > Water Leak Water leakage was detected on LHX at [PORTTYPE] port '[PORTID]'.
Page 357 Chapter 6: Using the Web Interface 2. Click the Action field to select an action type from the list. 3. Below is the list of available actions. Note: The "Change load shedding state" and "Switch outlets" options are only available for outlet-switching capable models. Action Function Alarm...
Page 358 Chapter 6: Using the Web Interface Action Function Send Email Send email Emails a textual message. See page 339). Send sensor report Reports the readings or status of the selected sensors, including internal or external sensors. See Send Sensor Report (on page 341).
Page 359 Chapter 6: Using the Web Interface Alarm The Alarm is an action that requires users to acknowledge an alert. This helps ensure that the user is aware of the alert. If the Alarm action has been included in a specific event rule and no one acknowledges that alert after it occurs, the PX3 resends or regenerates an alert notification regularly until the alert is acknowledged or the maximum number of alert notifications is sent.
Page 360 Chapter 6: Using the Web Interface a. In the Available field, select desired methods one by one, or click Select All. See step 3 for details. b. In the Selected field, click any method's to remove unnecessary ones, or click Deselect All. Action Group You can create an action group that performs up to 32 actions.
Page 361 Chapter 6: Using the Web Interface External Beeper If an external beeper is connected to the PX3, the PX3 can change the beeper's behavior or status to respond to a certain event. To control the connected external beeper: 1. Choose Device Settings > Event Rules > 2.
Page 362 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 363 Chapter 6: Using the Web Interface The maximum amount of snapshots that can be stored on the PX3 is 10. If you set it for a number greater than 10 and the storage location is on the PX3, after the 10th snapshot is taken and stored, the oldest snapshots are overwritten.
Page 364 Chapter 6: Using the Web Interface Placeholders for For a list and definition of available variables, see Custom Messages (on page 357). Operation: 1. Choose Device Settings > Event Rules > 2. Select "Send email" from the Action list. 3. In the "Recipient Email Addresses" field, specify the email address(es) of the recipient(s).
Page 365 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 366 Chapter 6: Using the Web Interface c. To delete any methods, click a method's in the Selected field. To remove all methods, simply click Deselect All. 4. In the Available Sensors field, select the desired target's sensor. a. Click the first to select a target component from the list.
Page 367 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 357). Placeholders for Custom Messages Send SMS Message You can configure SMS messages to be sent when an event occurs and can customize the message.
Page 368 Chapter 6: Using the Web Interface  When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 357).
Page 369 Chapter 6: Using the Web Interface To use a different SMTP server, select the "Use custom settings" radio button. The fields for customized SMTP settings appear. For Configuring SMTP Settings information on each field, see (on page 278). 5. Select the webcam that is capturing the images you want sent in the email.
Page 370 Chapter 6: Using the Web Interface 3. In the Host fields, enter the IP address of the device(s) you want to access. This is the address to which notifications are sent by the SNMP system agent. 4. In the Port fields, enter the port number used to access the device(s).
Page 371 Chapter 6: Using the Web Interface Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" Select this if authorization is required but no privacy protocols are required.  Select the authentication protocol - MD5 or ...
Page 372 Chapter 6: Using the Web Interface b. Type the key and value. c. Repeat the same steps to enter more arguments as needed.  To remove any existing argument, click adjacent to Switch LHX/SHX If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will Miscellaneous be available.
Page 373 Chapter 6: Using the Web Interface 6. If "Turn Outlet On" or "Cycle Outlet" is selected in step 3, you can choose to select the "Use sequence order and delays" checkbox so that all selected outlets will follow the power-on sequence defined on the page of Outlets (on page 173).
Page 374 Chapter 6: Using the Web Interface 4. In the Transport Protocol field, select one of the syslog protocols: TCP, UDP or TCP+TLS. The default is UDP. Transport Next steps protocols  In the UDP Port field, type an appropriate port number. Default is 514. ...
Page 375 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 376 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 377 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 378 Chapter 6: Using the Web Interface  If intended, you can customize the email messages in this action. 2. Click to create a 'Send sensor report' action that includes the 'Email a Sensor Report' action as its destination Send Sensor Report action.
Page 379 Chapter 6: Using the Web Interface  You can specify more than one temperature sensor as needed in this action. 3. Click to create a timer for performing the 'Send Temperature Sensor Readings' action hourly. Scheduling an Action For details, see (on page 351).
Page 380 Chapter 6: Using the Web Interface  To perform the specified action at 12:30 pm, 01:30 pm, 02:30 pm, and so on, select Hourly, and set the Minute to 30. Then the PX3 will send out an email containing the specified temperature sensor readings hourly every day.
Page 381 Chapter 6: Using the Web Interface Placeholders for Custom Messages Actions of "Send email" and "Send SMS message" allow you to customize event messages. See Send Email (on page 339) or Send SMS Message (on page 343). When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions.
Page 382 Chapter 6: Using the Web Interface Placeholder Definition [AMSNUMBER] The numeric ID of an asset strip [AMSRACKUNITPOSITION] The (vertical) rack unit position, an action applies to [AMSSTATE] The human readable state of an asset strip [AMSTAGID] The asset tag ID [CARDREADERID] The id of a card reader [CIRCUITCTRATING]...
Page 383 Chapter 6: Using the Web Interface Placeholder Definition [ISASSERTED] Boolean flag whether an event condition became true (1) or false (0) [LDAPERRORDESC] An LDAP error occurred [LHXFANID] The ID of a fan connected to an LHX/SHX [LHXPOWERSUPPLYID] The ID of an LHX/SHX power supply [LHXSENSORID] The ID of an LHX/SHX sensor probe [LOGMESSAGE]...
Page 384 Chapter 6: Using the Web Interface Placeholder Definition [POWERMETER] The PMC power meter ID [RADIUSERRORDESC] A Radius error occurred [ROMCODE] The rom code of an attached peripheral device [SENSORREADINGUNIT] The unit of a sensor reading [SENSORREADING] The value of a sensor reading [SENSORREPORT] The formatted sensor report contents [SENSORSTATENAME]...
Page 385 Chapter 6: Using the Web Interface Note: In case you need to type any square brackets "[" and "]" in the custom message for non-placeholder words, always add a backslash in front of the square bracket. That is, \[ or \]. Otherwise, the message sent will not display the square brackets.
Page 386 Chapter 6: Using the Web Interface 3. To make the PX3 record the firmware update failure event in the internal log, select "System Event Log Action" in the Available Actions field. Sample Outlet-Level Event Rule In this example, we want the PX3 to send SNMP notifications to the SNMP manager for any sensor change event of outlet 3.
Page 387 Chapter 6: Using the Web Interface Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for the System SNMP Notification Action. See (on page Enabling and Configuring SNMP 434). Then the SNMP notifications are sent when: ...
Page 388 Chapter 6: Using the Web Interface 3. Select "Any sub-event" to include all events related to all sensors of this inlet and all thresholds, such as current, voltage, upper critical threshold, upper warning threshold, lower critical threshold, lower warning threshold, and so on. 4.
Page 389 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 390 Chapter 6: Using the Web Interface 2. In this illustration, assign the name "Contact Closure Triggered Load Shedding" to the new rule. 3. In the Event field, select "Peripheral Device Slot" to indicate we are specifying an event related to the environmental sensor package. 4.
Page 391 Chapter 6: Using the Web Interface A Note about Infinite Loop You should avoid building an infinite loop when creating event rules. The infinite loop refers to a condition where the PX3 keeps busy because the action or one of the actions taken for a certain event triggers an identical or similar event which will result in an action triggering one more event.
Page 392: Setting Data Logging
Chapter 6: Using the Web Interface A Note about Untriggered Rules In some cases, a measurement exceeds a threshold causing the PX3 to generate an alert. The measurement then returns to a value within the threshold, but the PX3 does not generate an alert message for the Deassertion event.
Page 393: Configuring Data Push Settings
Chapter 6: Using the Web Interface  You can also click the topmost checkbox labeled "Logging Enabled" in the header row of each section to select all sensors of the same type.  If any section's number of sensors exceeds 35, the remaining sensors are listed on next page(s).
Page 394 Chapter 6: Using the Web Interface  Click Remove to delete the installed certificate if it is inappropriate. Note: If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see (on page 817).
Page 395: 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 396 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 397 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 398 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 399: Front Panel Settings
Actuator control -- available on all models.  Default front panel mode setup -- available on all models, except for the PX3-3000 series, which does NOT provide inlet sensor information.  RCM self-test -- available on those models which support residual current monitoring.
Page 400: 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 401 Chapter 6: Using the Web Interface Options Description Automatic detection The PX3 automatically detects the type of the device connected to the serial port. Select this option unless your PX3 cannot correctly detect the device type. Force console The PX3 attempts to recognize that the connected device is set for the console mode.
Page 402: 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 403 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 404 Chapter 6: Using the Web Interface Next steps:  To execute the newly-added script immediately, click , or click > Start with Arguments. See Manually Starting or Stopping a Script (on page 380).  To add more scripts, first return to the scripts list by clicking "Lua Menu Scripts"...
Page 405 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 406 Chapter 6: Using the Web Interface To return to the scripts list:  Click "Lua Scripts" on the top of the page.  Menu Or click "Lua Scripts" in the (on page 139). Checking Lua Scripts States Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state and settings of each script.
Page 407 Chapter 6: Using the Web Interface Modifying or Deleting a Script You can edit an existing script's codes or even replace it with a new script. Or you can simply remove a unnecessary script from the PX3. To modify or replace a script: 1.
Page 408: Miscellaneous
Chapter 6: Using the Web Interface Miscellaneous By default, the Schroff LHX/SHX heat exchanger support and Cisco EnergyWise feature implemented on the PX3 are disabled. Support needs to be enabled for the LHX/SHX information to appear in the PX3 web interface. Besides, Schroff LHX/SHX support must be enabled in order for the LHX-MIB to be accessible through SNMP.
Page 409 Chapter 6: Using the Web Interface Field Description Polling interval Type a polling interval to determine how often the PX3 is queried in the Cisco EnergyWise domain.  Range from 30 to 600 ms.  Default is 180 ms. EnergyWise 3.
Page 410: Maintenance
Chapter 6: Using the Web Interface Maintenance Menu Click 'Maintenance' in the (on page 139), and the following submenu displays. Submenu command Refer to... Device Information Device Information (on page 388) Viewing Connected Users Connected Users (on page 393) Event Log Viewing or Clearing the Local Event Log (on page 395) Updating the PX3 Firmware...
Page 411 Chapter 6: Using the Web Interface Submenu command Refer to... Bulk Configuration Bulk Configuration (on page 401) Backup and Restore of Device Settings Backup/Restore (on page 408) Network Diagnostics Network Diagnostic (on page 409) Downloading Diagnostic Information Download Diagnostic (on page 410) ...
Page 412: Device Information
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 413 Chapter 6: Using the Web Interface Section title Information shown Information General device information, such as model name, serial number, firmware version, hardware revision, MIB download link(s) and so on. Note that the download link of LHX-MIB is available only after enabling the Schroff Miscellaneous LHX/SHX support.
Page 414 This section explains how to identify a cascaded device on the Device Information page. Note: For detailed information on the cascading configuration and restrictions, see the Cascading Guide , which is available from Raritan website's Support page http://www.raritan.com/support/ To identify the USB-cascading status: 1.
Page 415 Chapter 6: Using the Web Interface Cascading information in the Port Forwarding mode:  The Common section contains three read-only fields for indicating the cascading status. Fields Description Port Forwarding Indicates the Port Forwarding is enabled. See Setting the Cascading Mode (on page 265).
Page 416 Chapter 6: Using the Web Interface  A master device shows (zero) in the Cascade Position field and in the Cascaded Device Connected field.  A slave device in the middle position shows a non-zero number which indicates its exact position in the Cascade Position field in the Cascaded Device Connected field.
Page 417: Viewing Connected Users
Chapter 6: Using the Web Interface The following diagram shows 2, indicating it is the second slave - Slave 2. The Cascaded Device Connected field shows indicating that it is the final one in the chain.  For a list of port numbers required for accessing each cascaded device in the Port Forwarding mode, click the Port Forwarding title bar on the same page.
Page 418 Chapter 6: Using the Web Interface Column Description User name The login name of each connected user. IP Address The IP address of each user's host. For the login via a local connection (serial RS-232 or USB), <local> is displayed instead of an IP address. Client Type The interface through which the user is being connected to the PX3.
Page 419: 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 420: 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 421 Chapter 6: Using the Web Interface  If anything is incorrect, click Discard Upload. 5. To proceed with the update, click Update Firmware. Warning: Do NOT power off the PX3 during the update. 6. During the firmware update:  A progress bar appears on the web interface, indicating the update status.
Page 422 Firmware version 3.3.10 is compatible with later firmware versions so you can upgrade all devices of the chain in a random order. Important: Raritan does not guarantee that no upgrade sequence limitation will be required for all future firmware versions. It is...
Page 423 . Note: Firmware downgrade in a cascading chain is NOT recommended. Consult Raritan Technical Support first if downgrade is needed. It is suggested to always stick to the same sequence as the above diagram. A Note about Firmware Upgrade Time The PDU firmware upgrade time varies from unit to unit, depending on various external and internal factors.
Page 424: Viewing Firmware Update History
Chapter 6: Using the Web Interface Viewing Firmware Update History The firmware upgrade history is permanently stored on the PX3. It remains available even though you perform a device reboot or any firmware update. To view the firmware update history: 1.
Page 425: Bulk Configuration
Chapter 6: Using the Web Interface Bulk Configuration The Bulk Configuration feature lets you save generic settings of a configured PX3 device to your computer. You can use this configuration file to copy common settings to other PX3 devices of the same model and firmware version.
Page 426 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 427 Chapter 6: Using the Web Interface Mechanical designs ignored by bulk configuration: When the source and target devices share the same technical specifications but are only different with any "mechanical designs" which are indicated in the table below, the bulk configuration remains feasible. These mechanical designs are represented by suffixes added to the model name of a PX3 device.
Page 428 Chapter 6: Using the Web Interface Customizing Bulk Configuration Profiles A bulk profile defines which settings are downloaded/saved from the source device and which are not. The default is to apply the built-in bulk profile, which downloads all settings from the source device except for device-specific data.
Page 429 Chapter 6: Using the Web Interface Option Description Built In The setting will follow the same setting in Raritan's built-in profile.  If "Excluded" is selected in the built-in profile, this setting will be also excluded.  If "Included" is selected in the built-in profile, this setting will be also included.
Page 430 Chapter 6: Using the Web Interface Step 2: Save a bulk configuration file You must have the Administrator Privileges or "Unrestricted View Privileges" to download the configuration. 1. Log in to the source PX3 if you have not yet. 2. Choose Maintenance > Bulk Configuration. 3.
Page 431 Chapter 6: Using the Web Interface Alternatives: To use a different method to perform bulk configuration, refer to:  Bulk Configuration via SCP (on page 633)  Bulk Configuration or Firmware Upgrade via DHCP/TFTP page 678)  Configuration or Firmware Upgrade with a USB Drive (on page 664) Modifying or Removing Bulk Profiles...
Page 432: Backup And Restore Of Device Settings
Chapter 6: Using the Web Interface 4. Click Delete on the confirmation message. Backup and Restore of Device Settings Unlike the bulk configuration file, the backup file contains ALL device settings, including device-specific data like device names and all network settings. To back up or restore a PX3 device's settings, you should perform the Backup/Restore feature.
Page 433: Network Diagnostics
Chapter 6: Using the Web Interface 4. Enter the admin password, then click Restore. 5. Wait until the PX3 device resets and the Login page re-appears, indicating that the restore is complete. 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 434: 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 435: 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 436: 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 437: Webcam Management
Chapter 6: Using the Web Interface 2. You can click any link to access related information or download any software package. Webcam Management The 'Webcams' menu item appears only when there is any webcam(s) connected to the PX3, or when there are snapshots saved onto the PX3 Connecting a Logitech Webcam already.
Page 438 Chapter 6: Using the Web Interface With a Logitech webcam connected to the PX3, you can visually monitor ® the environment around the PX3 via snapshots or videos captured by the webcam. Permissions required: To do... Permission(s) required Either permission below: View snapshots and videos ...
Page 439: Configuring Webcams And Viewing Live Images
Chapter 6: Using the Web Interface Configuring Webcams and Viewing Live Images To configure a webcam or view live snapshot/video sessions, choose Menu Webcams in the (on page 139). Then click the desired webcam to open that webcam's page. Note that default webcam names are determined by the detection order. Webcam The one that is detected first is named , and the other that is...
Page 440 Chapter 6: Using the Web Interface Tip: The date and time shown on the PX3 web interface are automatically converted to your computer's time zone. To avoid any time confusion, you can apply the same time zone settings as those of PX3 to your computer.
Page 441 Chapter 6: Using the Web Interface Settings: 1. By default the Settings section is open. If not, click the Settings title bar. 2. Click Edit Settings. 3. Enter a name for the webcam. Up to 64 ASCII printable characters are supported. ...
Page 442: Sending Links To Snapshots Or Videos
Chapter 6: Using the Web Interface To return to the Webcam Management page:  Click Webcam Management on the top of the page.  Menu Or click Webcams again in the (on page 139). Sending Links to Snapshots or Videos When opening a Primary Standalone Live Preview window, a unique URL is generated for this window session.
Page 443 Chapter 6: Using the Web Interface  Note that default webcam names are determined by the Webcam detection order. The one that is detected first is named Webcam 2 and the other that is detected later is named 3. Click in the Live Preview section.
Page 444: Viewing And Managing Locally-Saved Snapshots
Chapter 6: Using the Web Interface How Long a Link Remains Accessible For documentation purposes, the one who opens and sends the URL of the Primary Standalone Live Preview window is called User A and the two recipients of the same URL link are called User B User C is able to access the snapshot or video image via the link when the URL link remains valid, which can be one of these scenarios:...
Page 445 Chapter 6: Using the Web Interface saved on the PX3 locally. If needed, download important snapshots before rebooting the device. To view saved snapshots: 1. Choose Webcams > . The Snapshots page opens. 2. Click the snapshot you want to view from the list. Tip: The date and time shown on the PX3 web interface are automatically converted to your computer's time zone.
Page 446 Chapter 6: Using the Web Interface  To select all images, select the top-most checkbox in the header row. 3. On the top of the list, click 4. Click Delete on the confirmation message. To download any image onto the computer: ...
Page 447: Changing Storage Settings
Chapter 6: Using the Web Interface Changing Storage Settings Important: As of release 3.4.0, the PX3 web interface only lists the snapshots stored locally on the PX3 device, but no longer lists those saved on the remote servers. You must launch appropriate third-party applications, such as an FTP client, to access and manage the snapshots stored on remote servers.
Page 448 Chapter 6: Using the Web Interface Storage location Description 'Local' means the PX3. This is the default. Local  It can store a maximum of 10 snapshots only.  The web interface can list and display all Viewing and snapshots stored on the PX3. See Managing Locally-Saved Snapshots (on page 420).
Page 449 Chapter 6: Using the Web Interface Identifying Snapshots Folders on Remote Servers If saving snapshots onto a remote server, you can access those snapshots via an appropriate third-party application, such as an FTP client. All snapshots are saved as JPEG and named according to the date and time when saving the snapshots.
Page 450 Chapter 6: Using the Web Interface Number Folder name description The name of the webcam that PX3 detects later, if an additional webcam is connected. This is the folder where the snapshots captured by the second webcam are stored.  The second webcam's default name is "Webcam 2". ...
Page 451: Smartlock And Card Reader
DX2-DH2C2 and the door handles included in the kit. Note: For information on DX2-DH2C2, you can refer to either the user documentation accompanying the SmartLock kit or 'Environmental Sensors and Actuators Guide' (or Online Help) on Raritan website's Support page http://www.raritan.com/support/...
Page 452: Smartlock
Chapter 6: Using the Web Interface Note that "SmartLock" appears only when your door handles are connected via DX2-DH2C2 to PX3, but "Card Readers" appears as long as the PX3 detects any card reader -- directly connected to PX3, or indirectly connected via DX2-DH2C2.
Page 453 Chapter 6: Using the Web Interface You can click the desired DX2-DH2C2 to open its details page, and then do the following.  View the status of the cabinet door and card reader. Note: Data of "external" USB card readers is NOT shown on the SmartLock page.
Page 454 Chapter 6: Using the Web Interface Section Description Shows all sensor states detected by DX2-DH2C2, Door State including:  Door : States of contact closure sensors connected to DX2-DH2C2. Contact closure sensors detect whether the door is physically opened or closed. ...
Page 455 Chapter 6: Using the Web Interface  If no door handle is being connected to the door-handle port in question on the DX2-DH2C2, select or leave this field to "None." 3. Click Save. To control the door handles: 1. Make sure you have configured the door handle type properly in the above procedure.
Page 456: Card Readers
Chapter 6: Using the Web Interface Card Readers To open the Card Readers page, choose Card Readers in the Menu page 139). This page lists all card readers connected to PX3, indirectly or directly. When a user scans his/her smart card with the card reader, PX3 will retrieve the card 's type and ID and show them in the corresponding Card Type and Card ID column.
Page 457 Chapter 6: Using the Web Interface External USB card readers:  This is an external USB card reader.  It is directly connected to PX3 via USB.  The Channel column does not show any data.
Page 458: 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 459: 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 435) ...
Page 460: Snmpv3 Notifications
Chapter 7: Using SNMP Field Description Timeout The interval of time, in seconds, after which a new inform communication is resent if the first is not received.  For example, resend a new inform communication once every 3 seconds. Number of Retries The number of times you want to resend the inform communication if it fails.
Page 461 Chapter 7: Using SNMP 3. In the SNMP Notifications section, make sure the Enable SNMP Notifications checkbox is selected. 4. Select SNMPv3 Trap or SNMPv3 Inform as the notification type. 5. For SNMP TRAPs, the engine ID is prepopulated. 6. Type values in the following fields.
Page 462 Chapter 7: Using SNMP Field Description Host The IP address of the device(s) you want to access. This is the address to which notifications are sent by the SNMP agent. Port The port number used to access the device(s). User ID User name for accessing the device.
Page 463: Downloading Snmp Mib
Chapter 7: Using SNMP Downloading SNMP MIB You must download an appropriate SNMP MIB file for successful SNMP communications. Always use the latest SNMP MIB downloaded from the current firmware of your PX3. You can download the MIBs from two different pages of the web interface.
Page 464: Snmp Gets And Sets
Chapter 7: Using SNMP SNMP Gets and Sets In addition to sending notifications, the PX3 is able to receive SNMP get and set requests from third-party SNMP managers.  Get requests are used to retrieve information about the PX3, such as the system location, and the current on a specific outlet.
Page 465 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 466 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 467: Retrieving Energy Usage
Chapter 7: Using SNMP Retrieving Energy Usage You can discover how much energy an IT device consumes by retrieving the Active Energy for the outlet this IT device is plugged into. The Active Energy values are included in the outletSensorMeasurementsTable, along with other outlet sensor readings.
Page 468: 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.................. 444 Logging in to CLI..................445 The ? Command for Showing Available Commands.......
Page 469: 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 470: 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 447) in the User Guide for more information. Tip: The "Last Login" information, including the date and time, is also displayed if the same user account was used to log in to this product's web interface or CLI.
Page 471: 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 472: 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 473: Querying Available Parameters For A Command
Chapter 8: Using the Command Line Interface config:# In the diagnostic mode: diag:# Press Enter after pressing the ? command, and a list of main commands for the current mode is displayed. Tip: To automatically complete a command after typing part of the full command, see (on page 630).
Page 474: Showing Information
Chapter 8: Using the Command Line Interface config:# role create ? Tip: To automatically complete a command after typing part of the full command, see (on page 630). Automatically Completing a Command To re-execute one of the previous commands, see Retrieving Previous (on page 630).
Page 475 Chapter 8: Using the Command Line Interface IP Configuration This command shows the IP settings shared by all network interfaces, such as DNS and routes. Information shown will include both IPv4 and IPv6 configuration. Tip: To show IPv4-only and IPv6-only configuration data, see IPv4-Only (on page 452).
Page 476 Chapter 8: Using the Command Line Interface IPv4-Only or IPv6-Only Configuration To show IPv4-only or IPv6-only configuration, use any of the following commands. Tip: To show both IPv4 and IPv6 configuration data, see IP Configuration (on page 451). To show IPv4 settings shared by all network interfaces, such as DNS and routes: show network ipv4 common To show IPv6 settings shared by all network interfaces, such as...
Page 477 Chapter 8: Using the Command Line Interface Interface Description eth2 Show the IPv4 or IPv6 configuration of the ETH2 interface. (PX3-iX7) wireless Show the IPv4 or IPv6 configuration of the WIRELESS interface. bridge Show the IPv4 or IPv6 configuration of the BRIDGE interface.
Page 478 Chapter 8: Using the Command Line Interface Interface Description 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. Tip: You can also type the command without adding this option "all" to get the same data. That show network interface Network Service Settings This command shows the network service settings only, including the...
Page 479: 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 480: 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 481: Overcurrent Protector Information
RMS current value.  For Raritan's outlet-metered models that support "outlet peak current" sensors, information indicating which outlet MAY cause the Possible OCP-tripped event is available with this command. See OCP-Tripped Root Cause (on page 198).
Page 482: 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 483: 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 Variables: ...
Page 484: 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 485: 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 486: 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 487: 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>...
Page 488: 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 489: 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 490: 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 491 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 492: 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 493: 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 494: 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 495: Authentication Settings
Chapter 8: Using the Command Line Interface Authentication Settings General authentication settings: This command displays the authentication settings of the PX3, including both LDAP and Radius settings. show authentication One LDAP server's settings: To show the configuration of a specific LDAP server, assign the desired LDAP server with its sequential number in the command.
Page 496: Existing User Profiles
Chapter 8: Using the Command Line Interface  With the parameter "details" added, detailed information of the specified server is displayed, such as an LDAP server's bind DN and the login name attribute, or a Radius server's timeout and retries values.
Page 497: 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 498: 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 499: 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 500: 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 501: 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 502: 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 503 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 504: Command History
Chapter 8: Using the Command Line Interface Command History This command shows the command history for current connection session. show history Displayed information:  A list of commands that were previously entered in the current session is displayed. Reliability Data This command shows the reliability data.
Page 505 Chapter 8: Using the Command Line Interface Example 1 - Basic Security Information show security The diagram shows the output of the command. Example 2 - In-Depth Security Information show security details More information is displayed when typing the command.
Page 506: Clearing Information
Chapter 8: Using the Command Line Interface Example 3 - Basic PDU Information show pdu The diagram shows the output of the command. Example 4 - In-Depth PDU Information show pdu details More information is displayed when typing the command. Displayed information varies depending on the model you purchased.
Page 507: Clearing Event Log
Chapter 8: Using the Command Line Interface Clearing Event Log This command removes all data from the event log. clear eventlog -- OR -- clear eventlog /y If you entered the command without "/y," a message appears, prompting you to confirm the operation. Type y to clear the event log or n to abort the operation.
Page 508: Entering Configuration Mode
Chapter 8: Using the Command Line Interface Entering Configuration Mode Configuration commands function in configuration mode only. To enter configuration mode: 1. Ensure you have entered administrator mode and the # prompt is displayed. Note: If you enter configuration mode from user mode, you may have limited permissions to make configuration changes.
Page 509: Pdu Configuration Commands
Chapter 8: Using the Command Line Interface PDU Configuration Commands A PDU configuration command begins with . You can use the PDU configuration commands to change the settings that apply to the whole PX3 device. Changing the PDU Name This command changes the PX3 device's name. config:# pdu name "<name>"...
Page 510 Chapter 8: Using the Command Line Interface Setting the Outlet Power-On Sequence This section applies to outlet-switching capable models only. This command sets the outlet power-on sequence when the PDU powers config:# pdu outletSequence <option> Variables:  default <option> is one of the options: , or a comma-separated list of outlet numbers.
Page 511 Chapter 8: Using the Command Line Interface config:# pdu outletSequenceDelay <outlet1>:<delay1>;<outlet2>:<delay2>; <outlet3>:<delay3>;... Separate outlet numbers and their delay settings with a colon. Outlets followed by delays are separated with a semicolon. Variables:  <outlet1>, <outlet2>, <outlet3> and the like are individual outlet numbers or a range of outlets using a dash.
Page 512 Chapter 8: Using the Command Line Interface Note: This feature does NOT take effect and cannot be configured on a PX3 device after the outlet relay is set to the "Latching" mode. See Latching Relay Behavior (on page 162). Setting the PDU-Defined Cycling Power-Off Period This section applies to outlet-switching capable models only.
Page 513 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 157) for information on outlet initialization delay.
Page 514 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 515 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 803).
Page 516 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 517: Network Configuration Commands
Chapter 8: Using the Command Line Interface Example 2 - Outlet Sequence The following command causes a 10-outlet PDU to first power on the 8th to 6th outlets and then the rest of outlets in the ascending order after the PDU powers up.
Page 518 Chapter 8: Using the Command Line Interface Setting the IPv4 Configuration Mode This command determines the IP configuration mode. config:# network ipv4 interface <ETH> configMethod <mode> Variables:  <ETH> is one of the network interfaces: ethernet (or ETH1/ETH2) wireless , or bridge .
Page 519 Chapter 8: Using the Command Line Interface Setting the IPv4 Preferred Host Name After selecting DHCP as the IPv4 configuration mode, you can specify the preferred host name, which is optional. The following is the command: config:# network ipv4 interface <ETH> preferredHostName <name> Variables: ...
Page 520 Chapter 8: Using the Command Line Interface Setting the IPv4 Address After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX3 device. config:# network ipv4 interface <ETH> address <ip address> Variables: ...
Page 521 Chapter 8: Using the Command Line Interface Setting IPv4 Static Routes If the IPv4 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the PX3 and devices in the other subnet.
Page 522 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 523 Chapter 8: Using the Command Line Interface Interface Description eth2 Determine the IPv6 configuration mode of the ETH2 interface (wired networking). (PX3-iX7) 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 524 Chapter 8: Using the Command Line Interface Interface Description eth2 Determine the IPv6 preferred host name of the ETH2 interface (wired networking). (PX3-iX7) 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).
Page 525 Chapter 8: Using the Command Line Interface Interface Description wireless Determine the IPv6 address of the WIRELESS interface (that is, wireless networking). bridge Determine the IPv6 address of the BRIDGE interface (that is, the bridging mode).  <ip address> is the IP address being assigned to your PX3 device. This value uses the IPv6 address format.
Page 526 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 527 <suffix1>, <suffix2>, and the like are the DNS suffixes that automatically apply when searching for any device via PX3. For example, <suffix1> can be raritan.com , and <suffix2> can be legrand.com . You can specify up to 6 suffixes by separating them with commas.
Page 528 Chapter 8: Using the Command Line Interface Option Description preferV6 Use the IPv6 addresses returned by the DNS server. Setting LAN Interface Parameters network ethernet A LAN interface configuration command begins with Enabling or Disabling the LAN Interface This command enables or disables the LAN interface. config:# network ethernet <ETH>...
Page 529 Chapter 8: Using the Command Line Interface Changing the LAN Interface Speed This command determines the LAN interface speed. config:# network ethernet <ETH> speed <option> Variables:  <ETH> is one of the options -- ethernet eth1 or eth2 , which depends on your model.
Page 530 Chapter 8: Using the Command Line Interface Changing the LAN Duplex Mode This command determines the LAN interface duplex mode. config:# network ethernet <ETH> duplexMode <mode> Variables:  ethernet eth1 or eth2 <ETH> is one of the options -- , which depends on your model.
Page 531 Chapter 8: Using the Command Line Interface 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. network wireless A wireless configuration command begins with Note: If current networking mode is not wireless, the SSID, PSK and BSSID values are not applied until the networking mode is changed to...
Page 532 Chapter 8: Using the Command Line Interface Setting the PSK If the Pre-Shared Key (PSK) authentication method is selected, you must assign a PSK passphrase by using this command. config:# network wireless PSK <psk> Variables:  <psk> is a string or passphrase that consists of: - 8 to 63 characters - No spaces - ASCII codes 0x20 ~ 0x7E...
Page 533 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 534 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 535 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 536 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 537 Chapter 8: Using the Command Line Interface Configuring the Cascading Mode This command determines the cascading mode. config:# network <mode> enabled <option1> Variables:  <mode> is one of the following cascading modes. Mode Description bridge The Bridging mode, where each cascaded device is assigned a unique IP address.
Page 538 Chapter 8: Using the Command Line Interface If Port Forwarding mode is enabled, you must configure two more settings to finish the configuration: On ALL cascaded devices, you must configure the 'role' setting one by one. config:# network portForwarding role <option2> On the master device, you must configure the 'downstream interface' setting.
Page 539 Chapter 8: Using the Command Line Interface Setting the HTTP Port The commands used to configure the HTTP port settings begin with network services http Change the HTTP port: config:# network services http port <n> Enable or disable the HTTP port: config:# network services http enabled <option>...
Page 540 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 541 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 542 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 543 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 544 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 545 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 546: 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 547 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 548 Chapter 8: Using the Command Line Interface Setting NTP Parameters A time configuration command for NTP-related parameters begins with time ntp Specify the primary time server: config:# time ntp firstServer <first_server> Specify the secondary time server: config:# time ntp secondServer <second_server> To delete the primary time server: config:# time ntp firstServer ""...
Page 549 Chapter 8: Using the Command Line Interface Customizing the Date and Time If intending to manually configure the date and time, use the following CLI commands to specify them. Note: You shall set the time configuration method to "manual" prior to customizing the date and time.
Page 550 Chapter 8: Using the Command Line Interface 2. The system shows a list of time zones. Type the index number of the desired time zone and press Enter. 3. Type apply for the selected time zone to take effect. Setting the Automatic Daylight Savings Time This command determines whether the daylight savings time is applied to the time settings.
Page 551: 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 524).
Page 552 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 enabled <option> Determine the default IPv4 firewall control policy for inbound traffic: config:# security ipAccessControl ipv4 defaultPolicyIn <policy> Determine the default IPv4 firewall control policy for outbound traffic: config:# security ipAccessControl ipv4 defaultPolicyOut <policy>...
Page 553 Chapter 8: Using the Command Line Interface  <policy> is one of the options: accept, drop reject Option Description accept Accepts traffic from all IP addresses. drop Discards traffic from all IP addresses, without sending any failure notification to the source host. reject Discards traffic from all IP addresses, and an ICMP message is sent to the source host for...
Page 554 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 555 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 556 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 557 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 558 Chapter 8: Using the Command Line Interface After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen. Do either of the following, or the login fails:  In the web interface, select the checkbox labeled "I understand and accept the Restricted Service Agreement."...
Page 559 Chapter 8: Using the Command Line Interface Specifying the Agreement Contents This command allows you to create or modify contents of the Restricted Service Agreement. config:# security restrictedServiceAgreement bannerContent After performing the above command, do the following: 1. Type the text comprising up to 10,000 ASCII characters when the CLI prompts you to enter the content.
Page 560 Chapter 8: Using the Command Line Interface Login Limitation The login limitation feature controls login-related limitations, such as password aging, simultaneous logins using the same user name, and the idle time permitted before forcing a user to log out. security loginLimits A login limitation command begins with You can combine multiple commands to modify various login limitation Multi-Command Syntax...
Page 561 Chapter 8: Using the Command Line Interface Password Aging Interval This command determines how often the password should be changed. config:# security loginLimits passwordAgingInterval <value> Variables:  <value> is a numeric value in days set for the password aging interval. The interval ranges from 7 to 365 days. Idle Timeout This command determines how long a user can remain idle before that user is forced to log out of the PX3 web interface or CLI.
Page 562 Chapter 8: Using the Command Line Interface Strong Passwords The strong password commands determine whether a strong password is required for login, and what a strong password should contain at least. A strong password command begins with security strongPasswords. You can combine multiple strong password commands to modify different parameters at a time.
Page 563 Chapter 8: Using the Command Line Interface Lowercase Character Requirement This command determines whether a strong password includes at least a lowercase character. config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option> Variables:  enable disable <option> is one of the options: Option Description enable At least one lowercase character is required.
Page 564 Chapter 8: Using the Command Line Interface Option Description disable No numeric character is required. Special Character Requirement This command determines whether a strong password includes at least a special character. config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option> Variables:  enable disable <option>...
Page 565 Chapter 8: Using the Command Line Interface Modifying Role-Based Access Control Parameters There are different commands for modifying role-based access control parameters.  IPv4 commands Enable or disable the IPv4 role-based access control feature: config:# security roleBasedAccessControl ipv4 enabled <option> Determine the IPv4 role-based access control policy: config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>...
Page 566 Chapter 8: Using the Command Line Interface Tip: You can combine both commands to modify all role-based access control parameters at a time. See (on page Multi-Command Syntax 617). Managing Role-Based Access Control Rules You can add, delete or modify role-based access control rules. ...
Page 567 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role> <policy> <insert> <rule_number> Variables:  <start_ip> is the starting IP address.  <end_ip> is the ending IP address.  <role> is the role for which you want to create an access control rule.
Page 568 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> Modify an IPv4 rule's role: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role <role> Modify an IPv4 rule's policy: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy <policy>...
Page 569 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> Variables:  <rule_number> is the number of the existing rule that you want to modify.  <start_ip> is the starting IP address. ...
Page 570 Chapter 8: Using the Command Line Interface Enabling or Disabling Front Panel Outlet Switching This section applies to outlet-switching capable models only. The following CLI commands control whether you can turn on or off an outlet by operating the front panel display. To enable the front panel outlet control feature: config:# security frontPanelPermissions add switchOutlet...
Page 571 Chapter 8: Using the Command Line Interface Example 1 - IPv4 Firewall Control Configuration The following command sets up two parameters of the IPv4 access control feature. config:# security ipAccessControl ipv4 enabled true defaultPolicyIn accept defaultPolicyOut accept Results:  The IPv4 access control feature is enabled. ...
Page 572: Outlet Configuration Commands
Chapter 8: Using the Command Line Interface Example 4 - Adding an IPv4 Role-based Access Control Rule The following command creates a newIPv4 role-based access control rule and specifies its location in the list. config:# security roleBasedAccessControl ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertAbove 3 Results: ...
Page 573 Chapter 8: Using the Command Line Interface Changing an Outlet's Default State This section applies to outlet-switching capable models only. This command determines the initial power condition of an outlet after the PX3 powers up. config:# outlet <n> stateOnDeviceStartup <option> Variables: ...
Page 574: Inlet Configuration Commands
Chapter 8: Using the Command Line Interface Setting an Outlet's Cycling Power-Off Period This section applies to outlet-switching capable models only. This command determines the power-off period of the power cycling operation for a specific outlet. config:# outlet <n> cyclingPowerOffPeriod <timing> Variables: ...
Page 575 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 576: 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 577 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 578 Chapter 8: Using the Command Line Interface Changing a User's Password This command allows you to change an existing user's password if you have the Administrator Privileges. config:# user modify <name> password After performing the above command, PX3 prompts you to enter a new password.
Page 579 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 580 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 581 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 617).
Page 582 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 583 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 584 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 585 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 586 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 587 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 588 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 589 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 590: 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 591 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 592 Chapter 8: Using the Command Line Interface * The "switchActuator" privilege requires an argument that is separated with a colon. The argument could be:  All actuators, that is, switchActuator:all  An actuator's ID number. For example: switchActuator:1 switchActuator:2 switchActuator:3 ...
Page 593 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 594 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 595: Authentication 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 596 Chapter 8: Using the Command Line Interface config:# authentication type <option1> useLocalIfRemoteUnavailable <option2> Note: You cannot enable or disable the option of switching to local authentication without determining the authentication type in the CLI. Therefore, always type "authentication type <option1>" when setting up "useLocalIfRemoteUnavailable".
Page 597 Chapter 8: Using the Command Line Interface Adding an LDAP Server Adding an LDAP server requires the entry of quite a lot of parameters, such as the server's IP address, TCP port number, Base DN and so on. You can repeat the following CLI command to add more than one LDAP server.
Page 598 Chapter 8: Using the Command Line Interface Type Description activeDirectory Microsoft Active Directory  <security> is one of the security options: none startTls Type Description none No security startTls StartTLS  anonymouseBind <bind_type> is one of the bind options: , or authenticatedBind Type Description...
Page 599 Chapter 8: Using the Command Line Interface config:# authentication ldap add <host> <port> <ldap_type> <security> <bind_type> <base_DN> <login_name_att> <user_entry_class> bindDN <bind_DN> "Optional Parameters" table: Parameters To configure userSearchSubfilter <filter> User search subfilter bindDN <bind_DN> bind DN  The system will prompt you to enter and re-confirm the bind password after adding this parameter to the command.
Page 600 The "verifyServerCertificate" parameter is added to the command and set to "true." config:# authentication ldap add ldap.raritan.com 389 openldap startTls ... inetOrgPerson verifyServerCertificate true b. The system now prompts you to enter the certificate's content. c. Type or copy the certificate's content in the CLI and press Enter.
Page 601 Chapter 8: Using the Command Line Interface config:# authentication ldap add op-ldap.raritan.com 389 openldap none authenticatedBind cn=Manager,dc=raritan,dc=com uid inetOrgPerson bindDN user@raritan.com b. The system prompts you to specify the bind DN password. c. Type the password and press Enter. d. Re-type the same password.
Page 602 Chapter 8: Using the Command Line Interface Parameters Description Change the IP address or host name. host <host>  <host> is the new IP address or host name. Change the TCP port number. port <port>  <port> is the new TCP port number. Change the server type.
Page 603 Chapter 8: Using the Command Line Interface Parameters Description Re-upload a different certificate. certificate a. First add the "certificate" parameter to the command, and press Enter. b. The system prompts you for the input of the certificate. c. Type or copy the content of the certificate in the CLI and press Enter.
Page 604 Chapter 8: Using the Command Line Interface config:# authentication ldap modify 1 host 192.168.3.3 port 633 serverType activeDirectory Removing an Existing LDAP Server This command removes an existing LDAP server from the server list. config:# authentication ldap delete <server_num> Variables: ...
Page 605 Chapter 8: Using the Command Line Interface  <auth_port> is the authentication port number.  <acct_port> is the accounting port number.  <timeout> is the timeout value in seconds. It ranges between 1 to 10 seconds.  <retries> is the number of retries. It ranges between 0 to 5. To enter the shared secret: 1.
Page 606 Chapter 8: Using the Command Line Interface config:# authentication radius modify <server_num> retries <retries> Change the shared secret: config:# authentication radius modify <server_num> secret Change the priority of the specified server: config:# authentication radius modify <server_num> sortPositon <position> Tip: You can add more than one parameters to the command. For example, "...
Page 607: Environmental Sensor Configuration Commands
Chapter 8: Using the Command Line Interface Removing an Existing Radius Server This command removes an existing Radius server from the server list. config:# authentication radius delete <server_num> Variables:  <server_num> is the sequential number of the specified server in the Radius server list.
Page 608 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 609 Chapter 8: Using the Command Line Interface Setting the Y Coordinate This command specifies the Y coordinate of an environmental sensor. config:# externalsensor <n> ylabel "<coordinate>" Variables:  <n> is the ID number of the environmental sensor that you want to configure.
Page 610 Chapter 8: Using the Command Line Interface Changing the Sensor Description This command provides a description for a specific environmental sensor. config:# externalsensor <n> description "<description>" Variables:  <n> is the ID number of the environmental sensor that you want to configure.
Page 611 Chapter 8: Using the Command Line Interface Setting the Alarmed to Normal Delay for DX-PIR This command determines the value of the Alarmed to Normal Delay setting for a DX-PIR presence detector. config:# externalsensor <n> alarmedToNormalDelay <time> Variables:  <n> is the ID number of the environmental sensor that you want to configure.
Page 612: Configuring Environmental Sensors' Default Thresholds
Chapter 8: Using the Command Line Interface Configuring Environmental Sensors' Default Thresholds You can set the default values of upper and lower thresholds, deassertion hysteresis and assertion timeout on a sensor type basis, including temperature, humidity, air pressure and air flow sensors. The default thresholds automatically apply to all environmental sensors that are newly detected or added.
Page 613 Chapter 8: Using the Command Line Interface config:# defaultThresholds <sensor type> assertionTimeout <as_value> Variables:  <sensor type> is one of the following numeric sensor types: Sensor types Description absoluteHumidity Absolute humidity sensors relativeHumidity Relative humidity sensors temperature Temperature sensors airPressure Air pressure sensors airFlow Air flow sensors...
Page 614: Sensor Threshold Configuration Commands
Chapter 8: Using the Command Line Interface Example - Default Upper Thresholds for Temperature It is assumed that your preferred measurement unit for temperature is set to degrees Celsius. Then the following command sets the default Upper Warning threshold to 20 and Upper Critical threshold to 24 for all temperature sensors.
Page 615 Chapter 8: Using the Command Line Interface config:# sensor outlet <n> <sensor type> lowerCritical <option> Set the Lower Warning threshold for an outlet sensor: config:# sensor outlet <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an outlet sensor: config:# sensor outlet <n>...
Page 616 Chapter 8: Using the Command Line Interface Option Description A numeric Sets a value for the specified threshold of a value specific outlet sensor and enables this threshold at the same time.  <hy_value> is a numeric value that is assigned to the hysteresis for "To De-assert"...
Page 617 Chapter 8: Using the Command Line Interface config:# sensor inlet <n> <sensor type> assertionTimeout <as_value> Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always the number 1.  <sensor type>...
Page 618 Chapter 8: Using the Command Line Interface  <hy_value> is a numeric value that is assigned to the hysteresis for "To De-assert" and Deassertion the specified inlet sensor. See Hysteresis (on page 798).  <as_value> is a numeric value that is assigned to the assertion "To Assert"...
Page 619 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 620 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 798).  <as_value> is a number in samples that is assigned to the assertion "To Assert"...
Page 621 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 622 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 623 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 624 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 625: 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 617).
Page 626: 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 491).  <description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
Page 627 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 628 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 629 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 630: 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 631 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 632: 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 633 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 634 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 635 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 636 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 637 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 613) and an LED Mode for a Rack Unit...
Page 638 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 639: 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 640 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 641: 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 642: 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 643: 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 644: 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 645: 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 646: 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 647: 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 648: 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 649: 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 650: 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 651: 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 652: 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 447).
Page 653 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 654: 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 655: Logging Out Of Cli
Chapter 8: Using the Command Line Interface Examples:  Example 1 (only one possible command): a. Type the first word and the first letter of the second word of the "reset factorydefaults" command -- that is, reset f. b. Then press Tab or Ctrl+i to complete the second word. ...
Page 656: 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 ............... 632 Bulk Configuration via SCP ..............633 Backup and Restore via SCP..............
Page 657: 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 658: Backup And Restore Via Scp
Chapter 9: Using SCP Commands 3. The system copies the configuration included in the file "bulk_config.txt" to another PX3, and displays the following message. Starting restore operation. The connection will be closed now. SCP examples:  Save operation: scp admin@192.168.87.50:/bulk_config.txt ...
Page 659: Downloading Diagnostic Data Via Scp
Chapter 9: Using SCP Commands scp backup_settings.txt <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 660 Chapter 9: Using SCP Commands Scenario 2: Specify a different SCP port but use the default filename  SSH/SCP port is NOT the default (22), or the accessed PX3 is a Port-Forwarding slave device.  The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot in the end of the SCP command as shown below.
Page 661 Chapter 9: Using SCP Commands Windows PSCP command: PSCP in Windows works in a similar way to the SCP.  pscp -P <port> <user name>@<device ip>:/diag-data.zip <filename>...
Page 662: Chapter 10 In-Line Monitors
Chapter 10 In-Line Monitors The model name of a PX3 in-line monitor follows this format: PX-3nnn, where n is a number, such as PX-3411. Unlike most of PX3 devices, each inlet of an in-line monitor is connected to an outlet only, so an inlet's rating/power data is the same as an outlet's rating/power data.
Page 663: Flexible Cord Installation Instructions
Important: Complete and the most updated instructions on installing Raritan PX Power a flexible cord on Raritan PDUs are included in the Cord Installation Guide , which is available on the Raritan website's Support page http://www.raritan.com/support/...
Page 664: Flexible Cord Selection
 The rated ampacity of the flexible cord must be greater than or equal to the Raritan product’s rated ampacity marked on its nameplate. In the United States, relevant ampacity ratings for flexible cords can be found in NEC(2011) section 400.5.
Page 665: Derating A Raritan Product
For example, using a 16A plug would result in a derated ampacity of 16A. 2. The derated ampacity must be marked on the Raritan product so the new reduced rating can be easily identified. 3. For in-line monitors, the receptacles used must have the same voltage and ampacity rating as the plug chosen in step 1.
Page 666: Wiring Of 3-Phase In-Line Monitors
Chapter 10: In-Line Monitors Wiring of 3-Phase In-Line Monitors 3-phase in-line monitors contain 4-pole wiring terminal blocks (L1, L2, L3, N) to monitor 5-wire (4P+PE) 3-phase wye connections. Delta wired 4-wire (3P+PE) 3-phase connections are also permitted (no wire connected to the terminal block neutral “N”). No additional hardware or firmware configuration is required to specify whether the connection is 5-wire wye or 4-wire delta.
Page 667 Chapter 10: In-Line Monitors One-channel in-line monitor Zero U PDU Make sure to locate the ground wire mounting stud(s). There is a separate ground wire mounting stud for each terminal block. Each flexible cord MUST have its green (or green/yellow) ground wire bonded to a ground wire mounting stud.
Page 668 Use the following to help determine how much jacket to remove:  In the finished assembly, the outer jacket should protrude inside the Raritan product.  The wires will have ring terminals crimped onto them. ...
Page 669 A sealing ring for smaller diameter line cords may have been included with the Raritan product, or can be requested from Raritan, to reduce the inside diameter of the cable gland.
Page 670 Use the following guidelines to help terminal block wiring.  In single-phase Raritan products with world-wide ratings, the terminals are labeled L1 and L2. L1 is the phase wire. L2 is either the neutral (120/230V installations) or another phase wire (208V installations).
Page 671 CT labeled L1 and then connect it to the L1 terminal block.  For Raritan in-line monitors, where there is a one to one correspondence between plug and receptacle, maintain the same wire colors for inlet and outlet flexible cords.
Page 672: In-Line Monitor's Web Interface
Chapter 10: In-Line Monitors 8. Re-install the PDU wiring access panel or in-line monitor cover plate. This completes internal wiring of the Raritan product. 9. For in-line monitors, fasten the receptacles to the outlet flexible cords following the manufacturer’s instructions.
Page 673: Dashboard Page
Chapter 10: In-Line Monitors Dashboard Page An in-line monitor's Dashboard page looks slightly different from a regular PX3 device's Dashboard page. Note: Depending on your model, elements shown on your page may appear slightly different from this image.
Page 674 Chapter 10: In-Line Monitors Number Section Content  Overview of each outlet's power data -- in the above diagram, Outlet(s) there are 4 outlets.  A current bar per outlet, which changes colors to indicate the RMS current state -- normal (green), warning (yellow) or critical (red).
Page 675 Chapter 10: In-Line Monitors 2. Click its title, such as Inlet/Outlet 1, Inlet/Outlet 2, and the like. The selected outlet's page opens. To view the inlet power chart: 1. To view the power chart of one or multiple outlets, select one or multiple outlet checkboxes below the diagram.
Page 676 Chapter 10: In-Line Monitors  Available data types include RMS current, RMS voltage, active power and apparent power.  To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below.
Page 677 Chapter 10: In-Line Monitors  When the data of multiple outlets is shown in the chart, simply hover your mouse over any outlet's data line. Values of outlets display simultaneously, marked with corresponding colors.
Page 678: Inlets/Outlets Page
Chapter 10: In-Line Monitors Inlets/Outlets Page On the Inlets/Outlets page, you can:  View each outlet's power data (which is also each inlet's power data)  Configure each inlet/outlet as needed, such as customizing outlet names, setting thresholds or resetting energy. Outlet thresholds, when enabled, help you identify whether the outlet enters the warning or critical level.
Page 679 Chapter 10: In-Line Monitors 2. A list of inlets/outlets is displayed. Click "Show Details" of the desired inlet/outlet. 3. The individual inlet/outlet page opens. On this page, you can:  View details, such as its receptacle type  View all of its sensors data ...
Page 680: 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 681: 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 682: 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 683 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 684: 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 685 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 686 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 687 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 688: 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 689: 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 690: Configuration Files
This file is required only when there are device-specific settings to devices.csv configure for multiple PX3 devices. See (on page 673). 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 691: Fwupdate.cfg
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 692 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. config  Specify the name of the configuration file containing device settings. ...
Page 693 Appendix C: Configuration or Firmware Upgrade with a USB Drive  The PX3 beeps after it finishes writing the diagnostic data to the USB drive. factory_reset  If this option is set to true, the PX3 will be reset to factory defaults. ...
Page 694 Appendix C: Configuration or Firmware Upgrade with a USB Drive  If all outlets will share the same "on" or "off" setting, replace the outlet numbers with the word "all".  Examples:  Turn on outlets 1 to 3, and 10, and turn off outlets 4 to 9. switch_outlets=1,2,3:on;4-9:off;10:on ...
Page 695: Config.txt
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 696 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 697: Devices.csv
Appendix C: Configuration or Firmware Upgrade with a USB Drive devices.csv If there are device-specific settings to configure, you must create a device list configuration file - devices.csv , to store unique data of each PX3. This file must be: ...
Page 698: 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 699: 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 664).
Page 700: 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 701 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 702: Appendix D Bulk Configuration Or Firmware Upgrade Via Dhcp/Tftp
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 666) or contact Raritan Technical Support to properly prepare some or all of the following files: ...
Page 703: 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 704: 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 705 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 706 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 707 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 708 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 709 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 710 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 711 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 712 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 713 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 714: 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 715 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 716 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 717 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 718 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 719 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 720 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 721: 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 722 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 723: 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 724 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 725: 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 726: 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 727 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 728: 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. Models ending in -M5.
Page 729: 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 (on page 710).
Page 730: 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 731: 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 732: Web Interface Operations For Rcm
Appendix F: PX3 Models with Residual Current Monitoring Web Interface Operations for RCM The RCM is a PX3 inlet sensor. To view, configure or run self-test, click Menu Inlet in the (on page 139). Checking RCM State and Current A section titled 'Residual Current Monitor' is available on the Inlet page, showing both the present RCM state and residual current.
Page 733 Appendix F: PX3 Models with Residual Current Monitoring To check RCM state and current on the Inlet page: 1. Click Inlet. See Web Interface Operations for RCM (on page 708). 2. Locate the Residual Current Monitor section on the Inlet page. ...
Page 734: Setting Rcm Current Thresholds
Appendix F: PX3 Models with Residual Current Monitoring Setting RCM Current Thresholds The RCM current thresholds define the critical, warning and normal range of residual current. To configure the RCM current thresholds and run self-test: 1. Click Inlet to open the Inlet page. 2.
Page 735: Disabling Or Enabling Front Panel Rcm Self-Test
Appendix F: PX3 Models with Residual Current Monitoring Disabling or Enabling Front Panel RCM Self-Test You can enable or disable the function of performing the RCM self-test by operating the front panel buttons. By default, this function is enabled. To disable or enable the front panel RCM self-test: 1.
Page 736: Checking Rcm States And Current
Appendix F: PX3 Models with Residual Current Monitoring  Residual Current: Residual current value in Amps. If your PX3 has more than one inlet, only the inlet which has the RCM alarm enters the critical state. 2. If needed, you can press to perform RCM self-test for this Running RCM inlet.
Page 737: Running Rcm Self-Test
Appendix F: PX3 Models with Residual Current Monitoring  RCM reading: Residual current value in Amps. If your PX3 has more than one inlet, a list of inlets is displayed, along with each inlet's RCM state and reading. 4. To return to the Main Menu, press Running RCM Self-Test You can perform the RCM self-test by operating the front panel buttons.
Page 738 Appendix F: PX3 Models with Residual Current Monitoring - Press - Press to select No and then press 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.
Page 739: Rcm Snmp Operations
Appendix F: PX3 Models with Residual Current Monitoring  To perform RCM self-test for additional inlets, press to select a different inlet and repeat the same steps. RCM SNMP Operations Make sure you have the correct version of SNMP MIB. The PX3 supports Downloading SNMP the RCM feature as of firmware version 2.5.20.
Page 740: Cli Operations For Rcm
Appendix F: PX3 Models with Residual Current Monitoring CLI Operations for RCM Using the Command For information on entering and using the CLI, see Line Interface (on page 444). Showing Residual Current Monitor Information This command syntax shows the residual current monitoring (RCM) information, which is only available on the models with RCM.
Page 741 Appendix F: PX3 Models with Residual Current Monitoring config:# residualCurrentMonitor <n> criticalRatedResidualOperatingCurrent <value> Note: The PX3 triggers events when residual current values are above (but not equal to) thresholds. For example, you would set the critical threshold to 29mA to specify the IEC 62020 IΔn of 30mA. See Compliance with IEC 62020 (on page 706).
Page 742: Setting Front Panel Rcm Self-Test
Appendix F: PX3 Models with Residual Current Monitoring Setting Front Panel RCM Self-Test You can enable or disable the front panel RCM self-test function via CLI in addition to the web interface. To enable the front panel RCM self-test: security frontPanelPermissions add rcmSelfTest To disable the front panel RCM self-test: security frontPanelPermissions remove rcmSelfTest Running RCM Self-Test...
Page 743: 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 744: 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 745: 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 746 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 chain. For a slave device, it shows "SLAVE" instead. Note: As of release 3.3.10, the "MASTER/SLAVE"...
Page 747: 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 748: 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 749 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 750: 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 this type of LCD display only shows the IPv4 address (if available). Below illustrates the IP address information.
Page 751: Mac Address
Appendix G: Old PX3 Character LCD Display To retrieve the "IPv4" address on PX3: 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 752: 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 753 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 754: 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 755 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 756: 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 757 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 758: 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 759 Appendix G: Old PX3 Character LCD Display Number Device position Number Device position Master device Slave 8 Slave 1 Slave 9 Slave 2 Slave 10 Slave 3 Slave 11 Slave 4 Slave 12 Slave 5 Slave 13 Slave 6 Slave 14 Slave 7 Slave 15...
Page 760: Rcm Information
Appendix G: Old PX3 Character LCD Display RCM Information If your "old" PX3 model supports residual current monitoring (RCM), this information is available in the front panel LCD display. For more information on RCM, see PX3 Models with Residual Current Monitoring (on page 704).
Page 761 Appendix G: Old PX3 Character LCD Display Below illustrates the residual current information shown on the LCD display. Section Example information The inlet containing RCM sensor is INLET 1. This residual current is 0 mA. ALARM always displays for residual current sensor. LEAK always displays for residual current sensor.
Page 762 Appendix G: Old PX3 Character LCD Display Section Example information The LCD alternates between "SLF" and "tSt" to indicate that this is self-test mode. ALARM always displays for residual current sensor. LEAK always displays for residual current sensor. Note: To disable or enable this front panel function, see Disabling or (on page 711).
Page 763: 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 764: 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 765: 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 252) and...
Page 766: 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 767 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 768 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 769: Appendix I Updating The Ldap Schema
Appendix I Updating the LDAP Schema In This Chapter Returning User Group Information ............745 Setting the Registry to Permit Write Operations to the Schema ... 746 Creating a New Attribute................. 746 Adding Attributes to the Class ..............747 Updating the Schema Cache ..............749 Editing rciusergroup Attributes for User Members .......
Page 770: 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 771: 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 772 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 773: 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 774 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 775 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 776: 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 752). FreeRADIUS Standard Attribute For configuration on FreeRADIUS, see Illustration (on page 770).
Page 777 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 757). Some configuration associated with Microsoft Active Directory (AD) is AD-Related Configuration also required for RADIUS authentication.
Page 778 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 779 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 780 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 781 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 782 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 783 Appendix J: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
Page 784 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 785 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 786 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 787 Appendix J: RADIUS Configuration Illustration Note: If your PX3 uses PAP, then select "PAP."...
Page 788 Appendix J: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
Page 789 Appendix J: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
Page 790 Appendix J: RADIUS Configuration Illustration 12. In the Attribute Information dialog, click Add. 13. Select String, type Raritan:G{Admin} in the text box, and then click...
Page 791 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 792 Appendix J: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
Page 793 Appendix J: RADIUS Configuration Illustration 15. Click Next to continue.
Page 794: 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 795: 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 796 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 797 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 798 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 799 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 800 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 801 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 802 Appendix J: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
Page 803 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 804 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 805 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 806 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 807: 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 808: 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 809 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 810 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 811 Appendix J: RADIUS Configuration Illustration 3. Click the Account tab and select the "Store password using reversible encryption" checkbox.
Page 812: Appendix K Additional Px3 Information
Altitude Correction Factors..............803 Unbalanced Current Calculation ............804 Data for BTU Calculation................. 805 Ways to Probe Existing User Profiles ............. 806 Raritan Training Website................. 806 Role of a DNS Server................806 Cascading Troubleshooting..............807 Installing the USB-to-Serial Driver (Optional)........811 Initial Network Configuration via CLI............
Page 813: Reserving Ip Addresses In Dhcp Servers
Appendix K: Additional PX3 Information Pin signal DB9 pin No. RJ-45 pin No. 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 814: 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 789).
Page 815: 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 816 Appendix K: Additional PX3 Information Interface Client identifier conversion ETH2 PEG1A00003-ETH2 = 50 45 47 31 41 30 30 30 30 33 2D 45 54 48 32 (PX3-iX7)  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 817: 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 818 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 819 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 820: 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 821 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 remain 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 822: 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 823 Appendix K: Additional PX3 Information...
Page 824 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 825: Default Voltage And Current Thresholds
The following are factory-default voltage and current thresholds applied lower to a Raritan power product. There are no default values set for current thresholds because lower thresholds are not useful. Availability of diverse thresholds depends on the capability of the model you purchased.
Page 826 Appendix K: Additional PX3 Information Threshold Default value Hysteresis Multi-phase inlets or outlets:  Line-Line RMS voltage: Threshold Default value Lower critical -6% of minimum rating Lower warning -3% of minimum rating Upper warning +3% of maximum rating Upper critical +6% of maximum rating Hysteresis ...
Page 827: Altitude Correction Factors
15mA Altitude Correction Factors If a Raritan differential air pressure sensor is attached to your device, the altitude you enter for the device can serve as an altitude correction factor. That is, the reading of the differential air pressure sensor will be multiplied by the correction factor to get a correct reading.
Page 828: Unbalanced Current Calculation
Appendix K: Additional PX3 Information Unbalanced Current Calculation Unbalanced current information is available on 3-phase models only. This section explains how the PX3 calculates the unbalanced current percentage. Calculation: 1. Calculate the average current of all 3 lines. Average current = (L1+L2+L3) / 3 2.
Page 829: Data For Btu Calculation
Appendix K: Additional PX3 Information  Average current: (5.5+5.2+4.0) / 3 = 4.9 amps  L1 current unbalance: (5.5 - 4.9) / 4.9 = 0.1224  L2 current unbalance: (5.2 - 4.9) / 4.9 = 0.0612  L3 current unbalance: (4.0 - 4.9) / 4.9 = -0.1837 ...
Page 830: 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 intelligent PDU, KVM, EMX, BCM, and CommandCenter Secure Gateway (CC-SG).
Page 831: Cascading Troubleshooting
 For the wireless networking, one of the following issues occurs:  The USB wireless LAN adapter attached to the master device is not the Raritan USB WIFI LAN USB Wireless LAN Adapters adapter. See (on page 24). ...
Page 832 Appendix K: Additional PX3 Information Symptom Probable cause  One of the following issues occurs on the master device: Failure to access a slave device  Network connection is lost.  The Ethernet or wireless interface is disabled.  One of the following issues occurs on the slave device in question or any upstream device (if available): ...
Page 833: Slave Device Events In The Log
Appendix K: Additional PX3 Information Tip: To determine which PX3 may be the failure point of network, you may ping each PX3 in the cascading chain, or check the slave-related events in the event log of each PX3. See The Ping Tool (on page 810) and Slave Device Events in the Log (on page 809).
Page 834: The Ping Tool
Appendix K: Additional PX3 Information Messages for the USB-cascading chain: In the Bridging mode, events regarding connection/disconnection of a downstream slave device via USB is NOT logged. However, in the Port Forwarding mode, whenever the connection or disconnection of a downstream slave device via USB is detected, the PX3 at the USB-A end of the USB cable logs it in the internal log.
Page 835: 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 836: Initial Network Configuration Via Cli
3. In the communications program, press Enter to send a carriage return to the PX3. 4. The PX3 prompts you to log in. Both user name and password are case sensitive. a. Username: admin b. Password: raritan (or a new password if you have changed it).
Page 837 Appendix K: Additional PX3 Information 5. If prompted to change the default password, change or ignore it.  To change it, follow onscreen instructions to type your new password.  To ignore it, simply press Enter. 6. The # prompt appears. 7.
Page 838 Appendix K: Additional PX3 Information  Static IP configuration: To set Use this command network <ipvX> interface <ETH> Static IPv4 or address <ip address> IPv6 address <ip address> = static IP address, with a syntax similar to the example below. ...
Page 839 Appendix K: Additional PX3 Information To set or Use this command enable network wireless enableHT 802.11n <option> protocol true false <option> = , or network wireless authMethod Authentication <method> method <method> = network wireless PSK <psk> <psk> = PSK string network wireless EAP outer eapOuterAuthentication...
Page 840 Appendix K: Additional PX3 Information The content to be copied from the CA certificate does NOT include the first line containing "BEGIN CERTIFICATE" and the final line containing "END CERTIFICATE." If a certificate is installed, configure the following: Whether to Use this command network wireless Verify the...
Page 841: Device-Specific Settings
Appendix K: Additional PX3 Information The IP address configured may take seconds to take effect. Device-Specific Settings A bulk configuration file will NOT contain any device-specific information like the following list. For further information, simply open the built-in bulk profile for a detailed list of 'excluded' settings.
Page 842: What Is A Certificate Chain
Appendix K: Additional PX3 Information What is a Certificate Chain If you are familiar with a certificate chain, you can ignore this topic Illustration - GMAIL SMTP Certificate Chain and refer to (on page 821). A certificate or a chain of certificates is used for trusting a TLS server that you want to connect.
Page 843 Appendix K: Additional PX3 Information Each certificate in the chain is the issuer certificate of the certificate that follows it. That is, A is the issuer certificate of B, and B is the issuer certificate of C. Note: In fact many certificate chains may comprise only the root certificate and a TLS server's certificate and do not have any intermediate certificate(s) like 'Certificate B' involved.
Page 844 Appendix K: Additional PX3 Information Warning: The certificate (chain) uploaded to the receiver must always contain the ROOT certificate even though the TLS server provides the root certificate. When uploading a (partial) chain onto the PX3, it means you trust each certificate in the chain to certify the authenticity of certificates a server sends to PX3.
Page 845: Illustration - Gmail Smtp Certificate Chain
Appendix K: Additional PX3 Information It is NOT recommended to upload the server certificate to the receiver except when it is a self-signed certificate. Using self-signed server certificates is also not recommended and may not even work in all cases. Order of the chain in the certificate file: The order of a certificate chain's content in the certificate file uploaded to the receiver must look like the following.
Page 846 Appendix K: Additional PX3 Information openssl s_client -showcerts -connect smtp.gmail.com:465 Alternative: To view the certificate chain instead of all certificates, you can remove the "-showcerts" option from the above command. 2. Information that shows the certificates the SMTP server has is displayed.
Page 847 Appendix K: Additional PX3 Information 3. Onscreen information under the title 'Certificate chain' indicates that there are three issuers and three certificates on this server.  Each line beginning with the letter "i" indicates an issuer. They are:  Google Internet Authority G2 ...
Page 848: Browsing Through The Online Help
Appendix K: Additional PX3 Information  Content copying must include the lines of "BEGIN CERTIFICATE" and "END CERTIFICATE". .pem .crt .cer 2. Save that file as a file. In this example, it is named as "my-root.pem." 3. Upload the file "my-root.pem" to PX3 for using the GMAIL SMTP service.
Page 849 "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 850: 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............826 Dominion KSX II, SX or SX II Configuration ..........831 Power IQ Configuration ................836 dcTrack ....................
Page 851: 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 852 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 853 Appendix L: Integration 3. Click OK.
Page 854: 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 855: 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 856 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, PX3 or PX3TS series: RJ-45 "FEATURE" port 2.
Page 857: 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 858 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 859 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 860: 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 861: 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 862: 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 863: 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 864 Index APIPA and Link-Local Addressing • 3, 33, 132, + 265, 282 Applicable Models • xix, xxi +12V Power Supply Sensor (for iX7™ Only) • 48, Assertion Timeout Example for Temperature 100, 157, 167 Sensors • 797 1 Asset Management Commands • 608 Asset Management Strips and dcTrack •...
Page 865 Index Bulk Configuration via SCP • 402, 407, 633 Checking RCM State and Current • xxiv, 708, Bulk Configuration/Upgrade Procedure • 678, Checking RCM States and Current • 712 Button-Type Locking Outlets • 21 Checking the Accessibility of NTP Servers • C ...
Page 866 Index Configuring SMTP Settings • 250, 274, 278, Creating a New Attribute • 746 340, 345 Creating a Role • 566 Configuring SNMP Settings • 239, 249, 274, Creating a Self-Signed Certificate • 290, 293 276, 332, 434 Creating a User Profile • 553 Configuring the Cascading Mode •...
Page 867 Index Deleting a User Profile • 562 Dual Ethernet Connection (for iX7™ Only) • 23, Derating a Raritan Product • 641 Detailed Information on Outlet Pages • 183, DX or DX2 Sensor Packages • xxi, 50, 52, 62, Determining the Authentication Method • xxiii, E ...
Page 868 Index Enabling or Disabling the Restricted Service Example 1 - Basic Security Information • 481 Agreement • 533 Example 1 - Combination of IP, Subnet Mask Enabling Service Advertising • 250, 275, 282, and Gateway Parameters • 617 Example 1 - Creating a User Profile • 565 Enabling the Restricted Service Agreement •...
Page 869 Index Example 4 - Static IPv4 Configuration • 522 How the Automatic Management Function Examples • 480, 492, 522, 526, 546, 564, 587, Works • 159, 164, 492 599, 614 I Existing Roles • 473 Existing User Profiles • 458, 472 Identifying Cascaded Devices •...
Page 870 Index Internal Beeper • 333, 337 Managing Role-Based Access Control Rules • Internal Beeper State • 157, 161, 709 Introduction • 1 Manually Starting or Stopping a Script • xxii, Introduction to Asset Tags • 73 379, 380 Introduction to PDU Components • 84 Maximum Ambient Operating Temperature •...
Page 871 Overcurrent Protector Information • xxiii, 199, PX3 Models with Residual Current Monitoring 457, 724 • 161, 375, 704, 736 Overcurrent Protector Sensor Threshold PX3-3000 Series • 86 Information • 466 PX3-4000 Series • 86 Overview • 638 PX3-5000 Series • 86 Overview of the Cascading Modes •...
Page 872 RADIUS Configuration Illustration • 296, 752 387, 412 Radius Settings • xxiv, 580 Returning User Group Information • 745 Raritan Training Website • 806 RJ45-to-DB9 Cable Requirements for RCM Critical State Alarm • xxiv, 709 Computer Connections (for iX7™ Only) • 2, RCM Current Sensor •...
Page 873 Index Sensor Threshold Configuration Commands • Setting the Automatic Daylight Savings Time • Sensor Threshold Settings • 166, 170, 178, 188, Setting the Baud Rates • 615 193, 196, 205, 206, 215, 442, 793 Setting the BSSID • 512 Sensor/Actuator Location Example • 164, 216, Setting the Cascading Mode •...
Page 874 Index Setting the Time Zone • 442, 525 Specifying the Rack Unit Numbering Offset • Setting the X Coordinate • 584 Setting the Y Coordinate • 585 Specifying the SSH Public Key • 518, 561 Setting the Z Coordinate • 491, 585 Standard Attributes •...
Page 875 Index The PX3 MIB • 440 Using the Web Interface • 131, 648 Thresholds and Sensor States • 793 V Time Configuration Commands • 522 Time Units • 158, 165, 190, 304, 305 Vendor-Specific Attributes • 752, 771 TLS Certificate Chain • xxiv, 257, 279, 299, 350, Viewing and Managing Locally-Saved 370, 817 Snapshots •...

This manual is also suitable for:

Px3-4000 series Px3-5000 series

Raritan PX3-3000 Series User Manual

Chapter 1 Introduction

Chapter 2 Rackmount, Inlet and Outlet Connections

Chapter 3 Initial Installation and Configuration

Chapter 4 Connecting External Equipment (Optional)

Chapter 5 Introduction to PDU Components

Chapter 6 Using the Web Interface

Chapter 7 Using SNMP

Chapter 8 Using the Command Line Interface

Chapter 9 Using SCP Commands

Chapter 10 In-Line Monitors

Quick Links

Troubleshooting

Related Manuals for Raritan PX3-3000 Series

Summary of Contents for Raritan PX3-3000 Series