Page 2: Safety Guidelines
60950-1 or equivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury and death. WARNING! Do not use a Raritan product containing outlet relays to power large inductive loads such as motors or compressors. Attempting to power a large inductive load may result in damage to the relay.
Page 3: Safety Instructions
Safety Instructions 1. Installation of this product should only be performed by a person who has knowledge and experience with electric power. 2. Make sure the line cord is disconnected from power before physically mounting or moving the location of this product. 3.
Page 4 Raritan, Inc. © Copyright 2017 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.
Page 6: Table Of Contents
Contents Safety Guidelines Safety Instructions Applicable Models What's New in the PX2 User Guide xvii Chapter 1 Introduction Product Models ............................ 1 Package Contents ..........................1 Zero U Products ........................2 1U Products ..........................2 2U Products ..........................2 APIPA and Link-Local Addressing ...................... 3 Before You Begin..........................
Page 7 Contents Chapter 3 Initial Installation and Configuration Connecting the PDU to a Power Source ................... 21 Connecting the PX2 to Your Network ....................21 USB Wireless LAN Adapters....................22 Supported Wireless LAN Configuration ................. 23 Configuring the PX2 ........................... 23 Connecting the PX2 to a Computer ..................
Page 8 Contents LED Display ..........................80 Reset Button ..........................85 Circuit Breakers ..........................85 Resetting the Button-Type Circuit Breaker ................86 Resetting the Handle-Type Circuit Breaker ................86 Fuse ..............................87 Fuse Replacement on Zero U Models ..................88 Fuse Replacement on 1U Models ................... 89 Beeper ..............................
Page 9 Contents OCPs ..............................133 Individual OCP Pages ......................135 Peripherals ............................138 Yellow- or Red-Highlighted Sensors..................143 Managed vs Unmanaged Sensors/Actuators ..............144 Sensor/Actuator States ......................145 Finding the Sensor's Serial Number ..................147 Identifying the Sensor Position and Channel ............... 148 Managing One Sensor or Actuator ..................
Page 10 Contents Rebooting the PX2 Device ..................... 315 Resetting All Settings to Factory Defaults ................315 Retrieving Software Packages Information ................. 316 Webcam Management ........................317 Configuring Webcams and Viewing Live Images ..............317 Sending Snapshots or Videos in an Email or Instant Message .......... 319 Viewing Saved Snapshots and Managing Storage ...............
Page 11 Contents Existing User Profiles ......................354 Existing Roles ........................355 Load Shedding Settings ......................355 Serial Port Settings ....................... 356 EnergyWise Settings ......................356 Asset Strip Settings ....................... 356 Rack Unit Settings of an Asset Strip ..................357 Blade Extension Strip Settings ..................... 358 Event Log ..........................
Page 12 Contents Turning Off the Outlet(s) ....................... 484 Power Cycling the Outlet(s) ....................485 Canceling the Power-On Process ..................486 Example - Power Cycling Specific Outlets ................486 Actuator Control Operations ......................486 Switching On an Actuator...................... 487 Switching Off an Actuator ..................... 487 Example - Turning On a Specific Actuator ................
Page 13 Contents Creating Configuration Files via Mass Deployment Utility ..........515 Data Encryption in 'config.txt' ....................516 Firmware Upgrade via USB ......................517 Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ..................519 TFTP Requirements ......................... 520 DHCP IPv4 Configuration in Windows .....................
Page 14 Altitude Correction Factors ......................607 Unbalanced Current Calculation ..................... 608 Data for BTU Calculation ......................... 609 Ways to Probe Existing User Profiles ..................... 610 Raritan Training Website ......................... 610 Role of a DNS Server ........................611 Cascading Troubleshooting ......................611 Possible Root Causes......................611 Slave Connection and Disconnection Events ...............
Page 15: Applicable Models
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 16 Chapter 1: Applicable Models Comparison between PX2, PX3 and PX3-iX7: * Only PX3 models with outlet switching have outlet latching relays. ** Only PX3 "Zero U" (phase II and iX7 ) have the replaceable controller. ™ *** PX3 phase I models do NOT support a replaceable controller and are NOT available for sale anymore.
Page 17: What's New In The Px2 User Guide
What's New in the PX2 User Guide The following sections have changed or information has been added to the PX2 User Guide based on enhancements and changes to the equipment and/or user documentation. Applicable Models (on page xv) USB Wireless LAN Adapters (on page 22) Connecting the PX2 to a Computer (on page 24)
Page 18 Chapter 1: What's New in the PX2 User Guide Changing the LAN Duplex Mode (on page 386) Configuring the Cascading Mode (on page 391) Deleting an NTP Server (on page 402) Downloading Diagnostic Data via SCP (on page 498) Step C. Configure LDAP Authentication on the PX2 Device (on page 547) Reserving IP Addresses in DHCP Servers...
Page 19: Chapter 1 Introduction
Chapter 1 Introduction Raritan PX2 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 PX2 is distribution of power to...
Page 20: Zero U Products
Screws, brackets and/or buttons for Zero U • An "optional" null-modem cable with DB9 connectors on both ends • (Raritan number: 254-01-0006-00) Cable retention clips for the inlet (for some models only) • • Cable retention clips for outlets (for some models only)
Page 21: Apipa And Link-Local Addressing
Chapter 1: Introduction APIPA and Link-Local Addressing The PX2 supports Automatic Private Internet Protocol Addressing (APIPA). With APIPA, your PX2 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 22: Before You Begin
Note: Not all PX2 devices have overcurrent protection mechanisms. Preparing the Installation Site 1. Make sure the installation area is clean and free of extreme temperatures and humidity. Note: If necessary, contact Raritan Technical Support for the maximum operating temperature for your model. See Maximum (on page 500).
Page 23: Checking The Branch Circuit Rating
Chapter 1: Introduction Checking the Branch Circuit Rating The rating of the branch circuit supplying power to the PDU shall be in accordance with national and local electrical codes. Filling Out the Equipment Setup Worksheet An Equipment Setup Worksheet is provided in this User Guide. See Equipment Setup Worksheet (on page 502).
Page 24: Chapter 2 Rackmount, Inlet And Outlet Connections
This chapter describes how to rack mount a PX2 device. To mount a Zero U PX-1000 series PDU, you can use either two buttons or L-brackets that Raritan provided. Rackmount Safety Guidelines In Raritan products which require rack mounting, follow these precautions: Operation temperature in a closed rack environment may be ...
Page 25: 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 26 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 PX2 device.
Page 27: Mounting Zero U Models Using Button Mount
Chapter 2: Rackmount, Inlet and Outlet Connections Mounting Zero U Models Using Button Mount Circuit Breaker If your PDU has circuit breakers implemented, read 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 PX2 device. Leave at least 24 inches between the baseplates for stability.
Page 28: 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 PX2 device forward, pushing the mounting buttons through the mounting holes, then letting the device drop about 5/8".
Page 29 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 PX2 device.
Page 30: 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 Circuit Breaker your PDU has circuit breakers implemented, read Orientation Limitation (on page 6) before mounting it. To mount Zero U models using two buttons: 1.
Page 31: Mounting Zero U Models Using L-Brackets And Buttons
Chapter 2: Rackmount, Inlet and Outlet Connections 4. Screw a button in the screw hole near the top. The recommended torque for the button is 1.96 N·m (20 kgf·cm). 5. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously.
Page 32: Mounting 1U Or 2U Models
Chapter 2: Rackmount, Inlet and Outlet Connections 2. Screw the L-bracket to the device and ensure the bracket is fastened securely. 3. Repeat Steps 1 to 2 to screw another L-bracket to the bottom of the device. 4. After both L-brackets are installed, you can choose either of the following ways to mount the device in the rack.
Page 33: Installing Cable Retention Clips On The Inlet (Optional)
Chapter 2: Rackmount, Inlet and Outlet Connections 2. Insert the cable-support bar into rackmount brackets. 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners. Installing Cable Retention Clips on the Inlet (Optional) If your PX2 device is designed to use a cable retention clip, install the clip before connecting a power cord.
Page 34 Chapter 2: Rackmount, Inlet and Outlet Connections To install and use a cable retention clip on the inlet: 1. Locate two tiny holes adjacent to the inlet. 2. Install the cable retention clip by inserting two ends of the clip into the tiny holes.
Page 35: Installing Cable Retention Clips On Outlets (Optional)
Chapter 2: Rackmount, Inlet and Outlet Connections Installing Cable Retention Clips on Outlets (Optional) If your PX2 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 36: Locking Outlets And Cords
SecureLock outlets and cords • ™ Button-type locking outlets • Note that NOT all Raritan PDUs are implemented with any of the above locking outlets. SecureLock™ Outlets and Cords SecureLock is an innovative mechanism designed by Raritan, which ™ securely holds C14 or C20 plugs that are plugged into Raritan PDUs in place.
Page 37 Chapter 2: Rackmount, Inlet and Outlet Connections Item Description Latches on the SecureLock cord's plug ™ Only specific PDUs are implemented with the SecureLock mechanism. ™ If your PDU does not have this design, do NOT use the SecureLock cords ™...
Page 38: Button-Type Locking Outlets
Chapter 2: Rackmount, Inlet and Outlet Connections Button-Type Locking Outlets A button-type locking outlet has a button on it. Such outlets do not require any special power cords to achieve the locking purpose. All you need to do is simply plug a regular power cord into the locking outlet and the outlet automatically locks the cord.
Page 39: Chapter 3 Initial Installation And Configuration
Chapter 3 Initial Installation and Configuration This chapter explains how to install a PX2 device and configure it for network connectivity. In This Chapter Connecting the PDU to a Power Source ............ 21 Connecting the PX2 to Your Network ............21 Configuring the PX2 ..................
Page 40: Usb Wireless Lan Adapters
Chapter 3: Initial Installation and Configuration 2. Connect the other end of the cable to your LAN. Below indicates the ETHERNET port on PX Zero U models: For 1U/2U models, the ETHERNET port is usually located on the back except for a few models.
Page 41: Supported Wireless Lan Configuration
TP-Link TL-WDN3200 v1 A/B/G/N Raritan USB WIFI A/B/G/N Note: To use the Edimax EW-7722UnD or Raritan USB WIFI wireless LAN adapter to connect to an wireless network, the handshake 802.11n timeout setting must be changed to 500 or greater, or the wireless connection will fail.
Page 42: Connecting The Px2 To A Computer
Chapter 3: Initial Installation and Configuration Note: For details on the link-local addressing, see APIPA and (on page 3). Link-Local Addressing Configuration over a DHCP-enabled network: Connecting the PX2 1. Connect the PX2 to a DHCP IPv4 network. See to Your Network (on page 21).
Page 43 3. Perform (on page 27). Note: Not all serial-to-USB converters work properly with the PX2 so Raritan does not introduce the use of such converters. Direct network connection: 1. Connect one end of a standard network patch cable to the ETHERNET port of the PX2.
Page 44: Installing The Usb-To-Serial Driver (Optional)
The PX2 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 Support page http://www.raritan.com/support/ website's ). The dominion-serial-setup-<n>.exe downloaded driver's name is , where <n>...
Page 45: Initial Network Configuration Via Cli
3. In the communications program, press Enter to send a carriage return to the PX2. 4. The PX2 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 46 Chapter 3: Initial Installation and Configuration 5. If prompted to change the default password, change or ignore it. To change it, follow onscreen instructions to type your new  password. To ignore it, simply press Enter.  6. The # prompt appears. 7.
Page 47 Chapter 3: Initial Installation and Configuration • Static IP configuration: To set Use this command Static IPv4 or network <ipvX> interface <ETH> IPv6 address address <ip address> <ip address> = static IP address, with a syntax similar to the example below. 192.168.7.9/24 ...
Page 48 Chapter 3: Initial Installation and Configuration To set or Use this command enable 802.11n network wireless enableHT protocol <option> true false <option> = , or Authentication network wireless authMethod method <method> <method> = network wireless PSK <psk> <psk> = PSK string EAP outer network wireless authentication...
Page 49 Chapter 3: Initial Installation and Configuration The content to be copied from the CA certificate does NOT include the first line containing "BEGIN CERTIFICATE" and the final line containing "END CERTIFICATE." If a certificate is installed, configure the following: Whether to Use this command Verify the network wireless...
Page 50: Bulk Configuration Methods
Chapter 3: Initial Installation and Configuration To verify network settings: After exiting the above configuration mode and the # prompt re-appears, type this command to verify all network settings. • show network The IP address configured may take seconds to take effect. Bulk Configuration Methods If you have to set up multiple PX2 devices, you can use one of the following configuration methods to save your time.
Page 51: Cascading Multiple Px2 Devices For Sharing Ethernet Connectivity
USB-cascading tip: The "USB-cascading" configuration can be a combination of diverse Raritan products that support the USB-cascading feature, including PX2, PX3, PX3-iX7, transfer switch, BCM and EMX. Troubleshooting: When a networking issue occurs, check the cascading connection and/or Cascading software settings of all devices in the chain.
Page 52: Cascading Guidelines For Port Forwarding
Chapter 3: Initial Installation and Configuration Cascading Guidelines for Port Forwarding The following guidelines must be obeyed for establishing a cascading chain in the port forwarding mode. • Each cascaded device, except for the master device, must have only one upstream device. •...
Page 53: Cascading The Px2 Via Usb
16 devices in a chain. For more information on the USB-cascading configuration, see the Cascading Guide Support , which is available from Raritan website's page http://www.raritan.com/support/ The following diagram illustrates PX2 PDUs cascaded via either USB.
Page 54 Slave 2 Slave 3 To cascade PX2 devices via USB: 1. Make sure all Raritan devices to be cascaded are running firmware version 3.3.10 or later. 2. Select one as the master device. When the port forwarding mode over wireless LAN is intended, ...
Page 55: 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 PX2. In This Chapter Connecting Environmental Sensor Packages ........... 37 Connecting Asset Management Strips ............58 Connecting a Logitech Webcam ..............73 Connecting a GSM Modem................
Page 56: Dpx Sensor Packages
PX2. To connect a DPX differential air pressure sensor: 1. Plug one end of a Raritan-provided phone cable into the IN port of a differential air pressure sensor. 2. Plug the other end of this phone cable into the RJ-12 SENSOR port...
Page 57 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 PX2. Tip: The Raritan sensor hub that supports ALL types of Raritan environmental sensor packages is . See...
Page 58 Chapter 4: Connecting External Equipment (Optional) This diagram illustrates a configuration with a sensor hub connected. The PX2 device Raritan-provided phone cable DPX-ENVHUB4 sensor hub DPX sensor packages...
Page 59 Chapter 4: Connecting External Equipment (Optional) 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 60 Chapter 4: Connecting External Equipment (Optional) 2. The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports. 3. Repeat the above steps if there are additional SENSOR ports on your PX2.
Page 61 Sensor connection restrictions: Connect a DPX sensor package to the PX2 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 62: 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 Guide or Online Help on Raritan website's Support page http://www.raritan.com/support/...
Page 63 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 64: Dpx3 Sensor Packages
Chapter 4: Connecting External Equipment (Optional) 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 50). Note: If your PX2 has "two" RJ-12 SENSOR ports, see Guidelines for PX2 (on page 57) for sensor connection restrictions.
Page 65 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 PX2. Plug the adapter cable's RJ-12 connector into the RJ-12 SENSOR  port on the PX2. Note: If your PX2 has "two"...
Page 66 Chapter 4: Connecting External Equipment (Optional) When connecting a DPX2 sensor package containing two DPX2 sensors: A maximum of ten DPX3 sensor packages can be cascaded because 12-2=10. When connecting a DPX2 sensor package containing one DPX2 sensor: A maximum of eleven DPX3 sensor packages can be cascaded because 12-1=11.
Page 67: Dx Sensor Packages
Environmental Sensors Guide or Online Help on Support page http://www.raritan.com/support/ Raritan website's You can cascade up to 12 DX sensor packages. When cascading DX, remember that the PX2 only supports a maximum of 32 sensors and/or actuators.
Page 68 Chapter 4: Connecting External Equipment (Optional) a. Plug one end of the cable into the remaining RJ-45 port on the prior DX package. b. Plug the other end into either RJ-45 port on an additional DX package. Repeat the same steps to cascade more DX packages. 3.
Page 69: Using An Optional Dpx3-Envhub4 Sensor Hub
A maximum of eleven DX sensor packages can be cascaded because 12-1=11. Using an Optional DPX3-ENVHUB4 Sensor Hub A Raritan DPX3-ENVHUB4 sensor hub is physically and functionally similar to the DPX-ENVHUB4 sensor hub, which increases the number of sensor ports for the PX2, except for the following differences: All ports on the DPX3-ENVHUB4 sensor hub are RJ-45 instead of •...
Page 70 Chapter 4: Connecting External Equipment (Optional) 2. Connect the Raritan sensor packages to any of the four OUT ports on the hub. An RJ-12 to RJ-45 adapter is required for connecting a DPX or  DPX2 sensor package to the hub.
Page 71: 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 PX2 according to the following sensor combinations. In some scenarios, the DPX3-ENVHUB4 sensor hub is required. The PX2 does NOT support any other sensor-mixing combinations than those described in this section.
Page 72 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 73 Chapter 4: Connecting External Equipment (Optional)
Page 74 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 75: Guidelines For Px2 With Two Sensor Ports
Chapter 4: Connecting External Equipment (Optional) Guidelines for PX2 with Two Sensor Ports You CANNOT simultaneously connect Raritan environmental sensor packages to both sensor ports of the PX2 models with "two" sensor ports, unless only DPX sensor packages are connected.
Page 76: Connecting Asset Management Strips
(asset strips) to the PX2 after IT devices are tagged electronically. To use the asset management feature, you need the following items: Raritan asset strips • : An asset strip transmits the asset management tag's ID and positioning information to the PX2.
Page 77: Combining Regular Asset Strips
The difference between the master and slave asset strips is that the master asset strip has an RJ-45 connector while the slave does not. The following diagram illustrates some asset strips. Note that Raritan provides more types of asset strips than the diagram.
Page 78 Chapter 4: Connecting External Equipment (Optional) Make sure that the U-shaped sheet metal adjacent to the male  DIN connector is inserted into the rear slot of the master strip. Screw up the U-shaped sheet metal to reinforce the connection. 2.
Page 79: Introduction To Asset Tags
The FEATURE port of PX2 supports 5 volts of power only, which is insufficient for connecting the latest generation (G3) of asset strips. Therefore, the use of a Raritan X cable is required for PX2 to connect current asset strips, or PX2 cannot detect them.
Page 80 5th rack unit. 3. Connect the MASTER asset strip's RJ-45 connector to the male RJ-45 connector at the longer end of the Raritan X cable. 4. Connect the X cable to the PX2.
Page 81 Chapter 4: Connecting External Equipment (Optional) MASTER asset strip Asset tags IT devices Raritan X cable...
Page 82: 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 83 Chapter 4: Connecting External Equipment (Optional) Barcode (ID number) for the tag connector cable Tag connector Cable connector for connecting the blade extension strip Note: A tag connector cable has a unique barcode, which is displayed in the PX2 device's web interface for identifying each blade extension strip where it is connected.
Page 84 Chapter 4: Connecting External Equipment (Optional) 2. Move the blade extension strip toward the bottom of the blade chassis until its mylar section is fully under the chassis, and verify that the blade extension strip does not fall off easily. If necessary, you may use the adhesive tape in the back of the mylar section to help fix the strip in place.
Page 85: Connecting Composite Asset Strips
Chapter 4: Connecting External Equipment (Optional) 5. Plug the tag connector of the blade extension strip into the closest tag port of the regular or composite asset strip on the rack. 6. Repeat the above steps to connect additional blade extension strips. Up to 128 asset tags on blade extension strips are supported per FEATURE port.
Page 86 Chapter 4: Connecting External Equipment (Optional) Two RJ-45 connectors Tag ports To connect composite asset strips to the PX2 device: 1. Connect a composite asset strip to the PX2 device via a standard network patch cable (CAT5e or higher). a. Connect one end of the cable to the RJ-45 port labeled "Input" on the composite asset strip.
Page 87 • meters, but the total cable length cannot exceed 10 meters. The maximum number of composite asset strips that can be daisy • chained depend on the Raritan product you purchased. Raritan devices Maximum strips per chain EMX2-111, Up to 4 composite asset strips are supported.
Page 88 Chapter 4: Connecting External Equipment (Optional) Tip: To increase the maximum number of composite asset strips attached to a Raritan PX2 PDU, EMX2-111 or BCM1, use Raritan's X cable to enhance the power supply to the asset strip chain. See Using an X (on page 70).
Page 89 Chapter 4: Connecting External Equipment (Optional) 2. Plug the male RJ-12 phone connector at the shorter end of the X cable into the RJ-12 SENSOR port on the PX2 device. This step is required for enhancing the power supply to asset strips. 3.
Page 90 Chapter 4: Connecting External Equipment (Optional) 4. Connect any Raritan environmental sensor package or sensor hub to the female RJ-12 sensor port of the X cable if environmental sensor packages are needed. Note that a DX or DPX3 sensor requires an Connecting RJ-12 to RJ-45 adapter to connect the X cable.
Page 91: 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 PX2 supports up to two webcams. You can use a "powered" USB hub to connect webcams if needed.
Page 92: Connecting A Gsm Modem
NETCOMM IG6000 Industrial Grade SmartModem • • US Robotics 56K modem The PX2 may also support other analog modems which Raritan did not test. Note that the PX2 does NOT support dial-out or dial-back operations via the modem. To connect an analog modem: 1.
Page 93: Connecting An External Beeper
Chapter 4: Connecting External Equipment (Optional) You need to enable the modem dial-in support to take advantage of this Configuring the Serial Port feature, see (on page 289). Connecting an External Beeper The PX2 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...
Page 94: Chapter 5 Introduction To Pdu Components
Chapter 5 Introduction to PDU Components This chapter explains how to use the PX2 device, including: • Introduction to the LEDs and ports on the PDU Operation of the front panel display • The overcurrent protector's behavior • • The internal beeper's behavior The reset button •...
Page 95: Connection Ports
Chapter 5: Introduction to PDU Components PX2-1000 Series These models are NOT outlet-switching capable so all outlets are always in the ON state. Outlet LEDs are not available. PX2-2000 Series These models are outlet-switching capable. A small LED is adjacent to each outlet to indicate the state of the relay board.
Page 96 Cascading the PX2 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 97 Connection to one of the following devices: (RJ-45) Raritan's environmental sensor package(s).  Raritan's sensor hub, which expands the number of a sensor port to  four ports. ETHERNET Connecting the PX2 to your company's network via a standard network patch cable (Cat5e/6).
Page 98: Led Display
Chapter 5: Introduction to PDU Components LED Display The LED display is located on the side where outlets are available. These diagrams show the LED display on different types of PDUs. Note that the LED display might slightly vary according to the PDU you purchased.
Page 99 Chapter 5: Introduction to PDU Components The LED display consists of: • A row displaying three digits A row displaying two digits • Up and Down buttons • • Five LEDs for measurement units A Zero U model can detect its own orientation through the built-in tilt sensor and automatically changes the direction of the alphanumeric digits shown on the LED display for readability.
Page 100 Chapter 5: Introduction to PDU Components LEDs for Measurement Units Five small LED indicators are on the LED display: four measurement units LEDs and one Sensor LED. The measurement units vary according to the readings that appear in the three-digit row. They are: Amp (A) for current •...
Page 101 Chapter 5: Introduction to PDU Components AP: This indicates the selected inlet's active power. • UL: This represents the selected inlet or outlet's Unbalanced Load, • which is only available for a three-phase PDU. ix: This refers to the selected inlet on a multi-inlet PDU, where x is •...
Page 102 Chapter 5: Introduction to PDU Components Manual Mode You can press the Up or Down button to enter the Manual Mode so that a particular line or circuit breaker can be selected to show specific readings. In addition, you can select a particular inlet if your PDU has more than one inlet.
Page 103: Reset Button
Chapter 5: Introduction to PDU Components When the active power is displayed, the POWER(kW) LED is lit.  Note: The LED display returns to the Automatic Mode after 20 seconds elapse since the last time any button was pressed. Reset Button The reset button is located inside the small hole near the display panel on the PDU.
Page 104: Resetting The Button-Type Circuit Breaker
Chapter 5: Introduction to PDU Components Resetting the Button-Type Circuit Breaker Your button-type circuit breakers may look slightly different from the images shown in this section, but the reset procedure remains the same. To reset the button-type breakers: 1. Locate the breaker whose ON button is up, indicating that the breaker has tripped.
Page 105: Fuse
Chapter 5: Introduction to PDU Components 3. Examine your PX2 and the connected equipment to remove or resolve the cause that results in the overload or short circuit. This step is required, or you cannot proceed with the next step. 4.
Page 106: Fuse Replacement On Zero U Models
Chapter 5: Introduction to PDU Components Fuse Replacement on Zero U Models This section only applies to a Zero U PDU with "replaceable" fuses. To replace a fuse on Zero U models: 1. Lift the hinged cover over the fuse. 2.
Page 107: Fuse Replacement On 1U Models
Chapter 5: Introduction to PDU Components 4. Take the fuse out of the holder. 5. Insert a new fuse into the holder. There is no orientation limit for fuse insertion. 6. Close the fuse holder and the hinged cover in a reverse order. Fuse Replacement on 1U Models On the 1U model, a fuse is installed in a fuse knob, which fits into the PDU's fuse carrier.
Page 108 Chapter 5: Introduction to PDU Components 3. Remove the original fuse from this knob, and insert either end of a new one into the knob. Make sure the new fuse's rating is the same as the original one. Number Description Fuse knob Fuse 4.
Page 109: Beeper
Chapter 5: Introduction to PDU Components 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. Beeper The PX2 includes an internal beeper to issue an audible alarm for an overcurrent protector which is open.
Page 110: Chapter 6 Using The Web Interface
Chapter 6 Using the Web Interface This chapter explains how to use the web interface to administer a PX2. In This Chapter Supported Web Browsers ................92 Login, Logout and Password Change ............92 Web Interface Overview ................95 Dashboard ....................101 PDU ......................
Page 111: Login
Chapter 6: Using the Web Interface Login You must enable JavaScript in the web browser for proper operation. To log in to the web interface: 1. Open a browser and type the IP address of the PX2. If the link-local addressing has been enabled, you can type ...
Page 112: Changing Your Password
Chapter 6: Using the Web Interface Note: The address to access a slave device in the port forwarding mode via non-standard ports is a combination of a protocol (http:// or https://), an IP address and a port number. See Port Forwarding Examples page 199).
Page 113: Remembering User Names And Passwords
Chapter 6: Using the Web Interface Remembering User Names and Passwords The PX2 supports the password manager of common web browsers, including: • Microsoft Internet Explorer ® Mozilla Firefox • ® Google Chrome • ® You can save the login name and password when these browsers ask whether to remember them.
Page 114 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 98) Data/setup page of the selected menu item  Left side: - PX2 device name...
Page 115 Browsing through the Online Help - See (on page 616).  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.  PX2 system time...
Page 116: Menu
Chapter 6: Using the Web Interface Menu Depending on your model and hardware configuration, your PX2 may show all or some menu items shown below. Menu Information shown Dashboard Summary of the PX2 status, including a list of alerted sensors and alarms, if any.
Page 117 OCP status and settings, such as OCP thresholds. OCPs (on page 133). Peripherals Status and settings of Raritan environmental sensor packages, if connected. Peripherals (on page 138). Feature Port Status and settings of the device connected to the Feature port(s), which can be one of the following.
Page 118: Quick Access To A Specific Page
Chapter 6: Using the Web Interface If a menu item contains the submenu, the submenu is shown after clicking that item. To return to the previous menu list, do any below: Click the topmost link with the symbol >. For example, click •...
Page 119: Dashboard
Chapter 6: Using the Web Interface 2. To have it resorted in the descending order based on the same column, click the Timestamp header. 3. The arrow turns to , indicating the list is sorted in the "descending" order. 4. To resort the list based on a different column, click a different column header.
Page 120 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 103).
Page 121: 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 Inlet title 'Inlet I1' to go to the Inlet page.
Page 122 Chapter 6: Using the Web Interface Left side - generic inlet power data: The left side lists all or some of the following data. Available data is model dependent. Active power (kW or W) • Apparent power (kVA or VA) •...
Page 123: Dashboard - Ocp
Chapter 6: Using the Web Interface Dashboard - OCP Availability and total number of OCPs depend on the models. Each OCP's link: To view more information or configure individual OCPs, click the desired OCP's index number, which is C1, C2 and the like, to go to its setup page. Each OCP's power data: OCP data from top to bottom includes: RMS current (A)
Page 124: Dashboard - Alerted Sensors
Chapter 6: Using the Web Interface Dashboard - Alerted Sensors When any internal sensors or environmental sensor packages connected to the PX2 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 125 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 126: Dashboard - Inlet History
Chapter 6: Using the Web Interface Dashboard - Inlet History The power waveform for the inlet helps you observe whether there were abnormal events within the past tens of minutes. The default is to show the inlet's active power data. You can have it show the waveform of other inlet power data.
Page 127: Dashboard - Alarms
Chapter 6: Using the Web Interface Inlet selection on multi-inlet models: If your PDU is a multi-inlet model, you can have one or multiple inlets show their power waveforms by selecting the checkbox(es) of the desired inlet(s). When multiple inlets are displayed, their waveform colors differ. ...
Page 128 Chapter 6: Using the Web Interface This table explains each column of the alarms list. Field Description Name The customized name of the Alarm action. Reason The first event that triggers the alert. First Appearance The date and time when the event indicated in the Reason column occurred for the first time.
Page 129: Pdu
Chapter 6: Using the Web Interface The PX2 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 98). Device information shown: • Firmware version Serial number •...
Page 130 Determines how to describe the To specify the location of any Z Coordinate vertical locations (Z coordinates) of sensor/actuators in the data center, Individual Sensor/Actuator Format Raritan environmental sensor Pages packages. (on page 151). Options: Rack-Units and  Free-Form Z Coordinate Format (on page 116).
Page 131   The device's altitude is associated Altitude Specifies the PX2 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 607). attached.  The default altitude measurement Range: 0 to 3000 meters (0 to 9842 ...
Page 132: Internal Beeper State
Chapter 6: Using the Web Interface Tip: You can choose to reset the active energy reading of an individual inlet only. See (on page 119). Inlet To view total active energy and power on multi-inlet models: If your PX2 is a multi-inlet model, a "Power" section for showing the data of total active energy and total active power is available on the PDU page.
Page 133: Options For Outlet State On Startup
Chapter 6: Using the Web Interface States Description "Activation Reason" is displayed, indicating why the beeper sounds an alarm. For example, if the beeper is turned on because of a specific event rule "XXX," the activation reason looks like: Event Action triggered by rule: XXX Scenarios when the beeper sounds an alarm: Any overcurrent protector on the PX2, including fuses and circuit •...
Page 134: Initialization Delay Use Cases
Chapter 6: Using the Web Interface Initialization Delay Use Cases Apply the initialization delay in either of the following scenarios. • When power may not initially be stable after being restored When UPS batteries may be charging • Tip: When there are a large number of outlets, set the value to a lower number so that you can avoid a long wait before all outlets are available.
Page 135: How The Automatic Management Function Works
Chapter 6: Using the Web Interface How the Automatic Management Function Works This setting is configured on (on page 111). After enabling the automatic management function: When the total number of managed sensors and actuators has not reached the upper limit yet, the PX2 automatically brings newly-connected environmental sensors and actuators under management after detecting them.
Page 136: Setting Thresholds For Total Active Energy Or Power
Chapter 6: Using the Web Interface Setting Thresholds for Total Active Energy or Power This section applies only to multi-inlet models, including in-line monitors. Thresholds for total active energy and total active power are disabled by default. You can enable and set them so that you are alerted when the total active energy or total active power hits a certain level.
Page 137: 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 98). Inlet thresholds, when enabled, help you identify whether the inlet enters the warning or critical level.
Page 138 Chapter 6: Using the Web Interface 3. Click Save. 4. The inlet's custom name is displayed on the Inlet or Dashboard page, followed by its label in parentheses. To reset the inlet's active energy counter: Only users with the "Admin" role assigned can reset active energy readings.
Page 139: Configuring A Multi-Inlet Model
Chapter 6: Using the Web Interface 4. Click Save. Configuring a Multi-Inlet Model If the PX2 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.
Page 140: 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 98). On this page, you can: •...
Page 141 2. Select those you want to show, and deselect those you want to hide. Available Data of the Outlets Overview Page (on page 125). PX2-1000 series does NOT support the following features. To configure global outlet settings or perform the load-shedding command: 1.
Page 142 Chapter 6: Using the Web Interface To power control 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 143: Available Data Of The Outlets Overview Page
Chapter 6: Using the Web Interface If needed, click to stop the outlet-switching  operation. Available Data of the Outlets Overview Page All of the following outlet data is displayed on the outlets overview page based on your selection. To show or hide specific data, click .
Page 144: Setting Non-Critical Outlets
Chapter 6: Using the Web Interface Button Function Down Bottom Restores to the default sequence Next time when power cycling the PX2, it will turn on all outlets based on the new outlet order. The new order also applies when performing the power-on or power-cycling operation on partial outlets.
Page 145: Load Shedding Mode
Chapter 6: Using the Web Interface Tip: You can also set up non-critical outlet setting by configuring outlets one by one. See (on page 128). Individual Outlet Pages Load Shedding Mode When a UPS supplying power to the PX2 switches into battery backup operation, it may be desirable to switch off non-critical outlets to conserve UPS battery life.
Page 146: Individual Outlet Pages
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 (on page 122) or Outlets Available Data of the Outlets Overview Page (on page 125).
Page 147 In addition, you can perform the following operations on this outlet page. Note that only outlet-switching capable models show the power-control buttons, and you must have the Switch Outlet permission for performing outlet-switching operations. Therefore, PX2-1000 series does not support the following power control operation. To power control this outlet: 1.
Page 148 Chapter 6: Using the Web Interface To configure this outlet: 1. Click Edit Settings. 2. Configure available fields. Note that the fields marked with * are only available on outlet-switching capable models. Field Descriptions Name Type an outlet name up to 32 characters long. *State on device Click this field to select this outlet's initial startup...
Page 149 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 150 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 PX2 has overcurrent protectors. Overcurrent protector associated with this outlet Power-Off Period Options for Individual Outlets There are two options for setting the power-off period during the power...
Page 151: Ocps
Chapter 6: Using the Web Interface OCPs This page is available only when your PX2 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 152 Chapter 6: Using the Web Interface Status Bar colors normal above upper warning above upper critical Note: The "below lower warning" and "below lower critical" states also show yellow and red colors respectively. However, it is not meaningful to enable these two thresholds for current levels. Protected outlets, which are indicated with outlet numbers •...
Page 153: Individual Ocp
Chapter 6: Using the Web Interface 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. See (on page 133) or page 101). General OCP information: Field Description Label This OCP's physical number Status...
Page 154 Chapter 6: Using the Web Interface To view this OCP's power waveform: This OCP's RMS current data in waveform is shown in the Overcurrent Protector History section. To configure this OCP's threshold settings: 1. Click the Thresholds title bar at the bottom of the page to display the threshold data.
Page 155 Chapter 6: Using the Web Interface Tip: To configure thresholds for multiple OCPs at a time, see OCPs page 133). Other operations: You can go to another OCP's data/setup page by clicking the OCP • selector on the top-left corner. •...
Page 156: Peripherals
Chapter 6: Using the Web Interface Peripherals If there are Raritan environmental sensor packages connected to the Connecting PX2, they are listed on the Peripherals page. See Environmental Sensor Packages (on page 37). An environmental sensor package comprises one or some of the following sensors/actuators: •...
Page 157 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 100). Sensor/actuator overview on this page: If any sensor enters the alarmed state, it is highlighted in yellow or red.
Page 158 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 147). Position The data indicates where this sensor or actuator is located in the sensor chain.
Page 159 Chapter 6: Using the Web Interface The management action triggers a "Manage peripheral device"  multiple dialog. Simply click Manage if you are managing sensors/actuators. If you are managing only sensor/actuator, you can choose to  assign an ID number by selecting "Manually select a sensor Managing One Sensor or Actuator number."...
Page 160 Chapter 6: Using the Web Interface 2. Click the desired sensor type (required), and then click Edit Thresholds. 3. Make changes as needed. To enable any threshold, select the corresponding checkbox.  Type a new value in the accompanying text box. ...
Page 161: Yellow- Or Red-Highlighted Sensors
Chapter 6: Using the Web Interface Yellow- or Red-Highlighted Sensors The PX2 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 162: 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 163: Sensor/Actuator States
Chapter 6: Using the Web Interface Sensor/Actuator States They show one of the managed states. See • (on page 145). 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 164 Note that for a contact closure sensor, the normal state depends on the normal setting you have configured. Refer to the Environmental Sensors Guide or Online Help for detailed information, which is available on Support page http://www.raritan.com/support/ Raritan's Managed actuator states: State Description The actuator is turned on.
Page 165: 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 PX2.
Page 166: 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.
Page 167: 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 168 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 169: 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 170 Chapter 6: Using the Web Interface 2. Select or deselect Use Default Thresholds according to your needs. To have this sensor follow the default threshold settings  configured for its sensor type, select the Use Default Thresholds checkbox. The default threshold settings are configured on the page of Peripherals (on page 138).
Page 171 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 172 Chapter 6: Using the Web Interface To view a numeric sensor's readings waveform: This sensor's data within the past tens of minutes is shown in the waveform diagram. Note that only a numeric sensor has this diagram. State sensors and actuators do not show such data. To turn on or off an actuator: 1.
Page 173: Sensor/Actuator Location Example
Chapter 6: Using the Web Interface 2. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on. Other operations: You can go to another sensor's or actuators's data/setup page by clicking the selector on the top-left corner.
Page 174: Feature Port
Power CIM This type represents one of the following Raritan products:  Raritan power CIM, D2CIM-PWR. This CIM is used to connect the PX2 to the Raritan digital KVM switch -- Dominion KX II / III.  Dominion KSX II...
Page 175 Chapter 6: Using the Web Interface When the PX2 detects the connection of any listed device, it replaces 'Feature Port' in the menu with that device's name and shows that Asset Strip External device's data/settings instead. See (on page 158), Beeper Schroff LHX/SHX Power CIM...
Page 176: Asset Strip
(on page Miscellaneous 296). Asset Strip After connecting and detecting Raritan asset management strips (asset strips), the PX2 shows 'Asset Strip' in place of 'Feature Port' in the menu. Note: For connection instructions, see Connecting Asset Management (on page 58).
Page 177 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 178 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 179 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 180 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 181 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 182 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 183 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 184: External Beeper
Chapter 6: Using the Web Interface Asset Strip Automatic Firmware Upgrade After connecting the asset strip to the PX2, it automatically checks its own firmware version against the version of the asset strip firmware stored in the PX2 firmware. If two versions are different, the asset strip automatically starts downloading the new firmware from the PX2 to upgrade its own firmware.
Page 185: Schroff Lhx/Shx
Chapter 6: Using the Web Interface Schroff LHX/SHX You must enable the LHX/SHX support for the PX2 to detect the presence Miscellaneous of a supported Schroff LHX/SHX heat exchanger. See ® (on page 296). After enabling the LHX/SHX support and connecting a supported Schroff ®...
Page 186 Chapter 6: Using the Web Interface For the functionality of this icon on the top-right corner, see Feature Port (on page 156). 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 187 Chapter 6: Using the Web Interface Tip: You can also create event rules to notify you of the warning or critical levels. See (on page 236). Event Rules and Actions To view sensor alerts and LHX event log: Remote alert acknowledgment is supported by the LHX-20 and LHX-40. The SHX-30 does not support this feature.
Page 188: Power Cim
Chapter 6: Using the Web Interface Power CIM After connecting and detecting a Raritan power CIM, the PX2 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 189: 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 190 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 94). SSH: You need to enter the SSH public key only if the public key authentication Changing SSH Settings for SSH is enabled.
Page 191 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 •...
Page 192 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 193: 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 194: Creating Roles
Chapter 6: Using the Web Interface Creating Roles A role is a combination of permissions. Each user must have at least one role. The PX2 provides two built-in roles. The Operator role is assigned to a Creating Users newly-created user account per default. See (on page 171).
Page 195: Editing Or Deleting Roles
Chapter 6: Using the Web Interface 5. To select any privilege requiring the argument setting, click to select the desired arguments. For example, on an outlet-switching capable model, you can  specify the outlets that are allowed to be switched on/off for the 'Switch Outlet' privilege as shown below.
Page 196: Setting Your Preferred Measurement Units
Chapter 6: Using the Web Interface Tip: To delete only one role, you can simply click that user without making the checkboxes appear. See the above procedure. 2. Select one or multiple roles. To select all roles, except for the Admin role, select the top-most ...
Page 197: Setting Default Measurement Units
Chapter 6: Using the Web Interface Setting Default Measurement Units Default measurement units are applied to all PX2 user interfaces across all users, including users accessing the PX2 via external authentication User Interfaces servers. For a list of affected user interfaces, see Showing Default Units (on page 179).
Page 198: Device Settings
Chapter 6: Using the Web Interface Device Settings Menu Click 'Device Settings' in the (on page 98), and the following submenu displays. Menu command Submenu command Refer to... Configuring Network Settings Network (on page 181) Changing HTTP(S) Settings Network Services HTTP (on page 204) Configuring SNMP Settings...
Page 199: Configuring Network Settings
Chapter 6: Using the Web Interface Menu command Submenu command Refer to... Miscellaneous Miscellaneous (on page 296) * The availability of "Front Panel" depends on the model. Configuring Network Settings Configure wired, wireless, and Internet protocol-related settings on the connecting the PX2 to your network Network page after (on page 21).
Page 200 Chapter 6: Using the Web Interface You must connect a USB wireless LAN adapter to the PX2 for  wireless networking. Note: If the device's cascading mode is set to 'Bridging' or its role is set to 'Slave' in the port forwarding mode, the wireless settings will be disabled.
Page 201 Chapter 6: Using the Web Interface IPv4 settings: Field/setting Description Enable IPv4 Enable or disable the IPv4 protocol. IP Auto Select the method to configure IPv4 settings. Configuration  DHCP: Auto-configure IPv4 settings via DHCP servers.  Static: Manually configure the IPv4 settings. •...
Page 202 Chapter 6: Using the Web Interface Common Network Settings Common Network Settings are OPTIONAL, not required. Therefore, leave them unchanged if there are no specific local networking requirements. Field Description Cascading Mode Leave it to the default "None" unless you are establishing a cascading chain.
Page 203 Chapter 6: Using the Web Interface Ethernet Interface Settings By default the Ethernet interface is enabled. Enable Interface: Make sure the Ethernet interface is enabled, or all networking through this interface fails. This setting is available in the ETHERNET section, but not available in the BRIDGE section.
Page 204 Chapter 6: Using the Web Interface Wireless Network Settings If the device's cascading mode is set to 'Bridging' or its role is set to 'Slave' in the port forwarding mode, the wireless settings will be disabled. Setting the Cascading Mode (on page 195).
Page 205 Chapter 6: Using the Web Interface Field/setting Description Identity This field appears only when 'EAP - PEAP' is selected. Type your user name. Password This field appears only when 'EAP - PEAP' is selected. Type your password. CA Certificate This field appears only when 'EAP - PEAP' is selected.
Page 206 Chapter 6: Using the Web Interface Field/setting Description Allow wireless When this checkbox is deselected, and if the connection if system time is incorrect, the installed TLS system clock is certificate is considered not valid yet and will incorrect cause the wireless network connection to fail. When this checkbox is selected, it will make the wireless network connection successful when the PX2 system time is earlier than the firmware build...
Page 207 Chapter 6: Using the Web Interface Automatic settings: Optionally specify the preferred hostname, • which must meet the above requirements. • Static settings: Assign a static IPv6 address, which follows this syntax "IP address/prefix length". fd07:2fa:6cff:1111::0/128 Example: (Optional) To view the wireless LAN diagnostic log: Wireless LAN Diagnostic •...
Page 208 Chapter 6: Using the Web Interface 2. Click Clear Log on the confirmation message.
Page 209 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 210 Chapter 6: Using the Web Interface In this example, NIC-2 (192.168.100.88) is the next hop router for your PX2 to communicate with any device in the other subnet 192.168.200.0. In the IPv4 "Static Routes" section, you should specify:...
Page 211 Chapter 6: Using the Web Interface Tip: If you have configured multiple static routes, you can click on any route and then make changes, use to re-sort the priority, or click to delete it. IPv6 example: fd07:2fa:6cff:2405::30 • Your PX2: fd07:2fa:6cff:1111::50 fd07:2fa:6cff:2405::80 Two NICs:...
Page 212 Chapter 6: Using the Web Interface In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your PX2 to communicate with any device in the other subnet fd07:2fa:6cff:1111::0. In the IPv6 "Static Routes" section, you should specify: Tip: If you have configured multiple static routes, you can click on any route and then make changes, use to re-sort the priority, or click...
Page 213 Chapter 6: Using the Web Interface Setting the Cascading Mode A maximum of 16 PX2 devices can be cascaded to share one Ethernet Cascading Multiple PX2 Devices for Sharing Ethernet connection. See Connectivity (on page 33). The cascading mode configured on the master device determines the Ethernet sharing method, which is either network bridging or port Overview of the Cascading Modes forwarding.
Page 214 Online USB-cascading information: For more information on the USB-cascading configuration, see the Cascading Guide Support , which is available from Raritan website's page http://www.raritan.com/support/ Overview of the Cascading Modes You must apply a cascading mode to the cascading configuration. See Setting the Cascading Mode (on page 195).
Page 215 Chapter 6: Using the Web Interface "Bridging" mode: • In this mode, the DHCP server communicates with every cascaded different device respectively and assigns four IP addresses. Each device has its own IP address. The way to remotely access each cascaded device is completely the same as accessing a standalone device in the network.
Page 216 Chapter 6: Using the Web Interface Port Number Syntax In the Port Forwarding mode, all devices in the USB-cascading configuration share the same IP address. To access any cascaded device, you must assign an appropriate port number to it. 5NNXX •...
Page 217 Slave device: Assign proper 5NNXX port numbers. • The Port Forwarding mode is applied to a USB-cascading Assumption: configuration comprising three Raritan devices. The IP address is 192.168.84.77. Master device: Position code for the master device is '00' so each port number is 5NN00 as listed below.
Page 218 Chapter 6: Using the Web Interface Protocols Port numbers HTTP 50100 50200 TELNET 50300 SNMP 50500 MODBUS 50600 Examples using "5NN00" ports: • To access the master device via HTTPS, the IP address is: https://192.168.84.77:50000/ To access the master device via HTTP, the IP address is: •...
Page 219 Chapter 6: Using the Web Interface Examples: • To access Slave 1 via HTTPS, the IP address is: https://192.168.84.77:50001/ • To access Slave 1 via HTTP, the IP address is: http://192.168.84.77:50101/ • To access Slave 1 via SSH, the command is: ssh -p 50201 192.168.84.77 Slave 2 device: Position code for Slave 2 is '02' so each port number is 5NN02 as shown...
Page 220 Chapter 6: Using the Web Interface Adding, Removing or Swapping Cascaded Devices Change the cascading mode first before adding any device to a cascading chain, or before disconnecting a cascaded device from the chain. If you only want to change the cascading mode of an existing chain, or swap the master and slave device, always start from the slave device.
Page 221: Configuring Network Services
Enabling Service Advertising Service Advertising (on page 210) 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 222 Chapter 6: Using the Web Interface Changing HTTP(S) Settings HTTPS uses Transport Layer Security (TLS) technology to encrypt all traffic to and from the PX2 so it is a more secure protocol than HTTP. The PX2 supports TLS By default, any access to the PX2 via HTTP is automatically redirected to HTTPS.
Page 223 Chapter 6: Using the Web Interface Configuring SNMP Settings You can enable or disable SNMP communication between an SNMP manager and the PX2 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 224 Chapter 6: Using the Web Interface a. Click the Download MIBs title bar to show the download links. Downloading SNMP b. Click the PDU2-MIB download link. See (on page 325). 6. Click Save. Configuring SMTP Settings The PX2 can be configured to send alerts or event messages to a specific Event Rules and Actions administrator by email.
Page 225 Chapter 6: Using the Web Interface Field Description User Name, Type a user name and password for authentication after selecting the above checkbox. Password  The length of user name and password ranges between 4 and 64. Case sensitive.  Spaces are not allowed for the user name, but allowed for the password.
Page 226 Chapter 6: Using the Web Interface Special note for AES ciphers: The PX2 device's SSL/TLS-based protocols, including SMTP over StartTLS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between the PX2 and the client (such as a web browser), which is impacted by the cipher priority of the PX2 and the client's cipher availability/settings.
Page 227 Chapter 6: Using the Web Interface 3. To use a different port, type a new port number. 4. Click Save. Changing Modbus Settings You can enable or disable the Modbus/TCP access to the PX2, set it to the read-only mode, or change the TCP port. To change the Modbus/TCP settings: 1.
Page 228 Chapter 6: Using the Web Interface Enabling Service Advertising The PX2 advertises all enabled services that are reachable using the IP network. This feature uses DNS-SD (Domain Name System-Service Discovery) and MDNS (Multicast DNS). The advertised services are discovered by clients that have implemented DNS-SD and MDNS. The advertised services include the following: HTTP •...
Page 229: Configuring Security Settings
Chapter 6: Using the Web Interface Configuring Security Settings The PX2 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 230 Chapter 6: Using the Web Interface Note: Valid IPv4 addresses range from 0.0.0.0 through 255.255.255.255. To configure IPv4 access control rules: 1. Choose Device Settings > Security > IP Access Control. 2. Select the Enable IPv4 Access Control checkbox to enable IPv4 access control rules.
Page 231 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 232 Chapter 6: Using the Web Interface Creating Role Access Control Rules Role-based access control rules are similar to IP access control rules, except they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses.
Page 233 Chapter 6: Using the Web Interface INSERT a rule between two rules  Select the rule above which you want to insert a new rule. For example, to insert a rule between rules #3 and #4, select #4.  Click Insert Above. ...
Page 234 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 235 Chapter 6: Using the Web Interface Creating a CSR Follow this procedure to create the CSR for your PX2 device. Note that you must enter information in the fields showing the message 'required.' To create a CSR: 1. Choose Device Settings > Security > SSL Certificate. 2.
Page 236 Chapter 6: Using the Web Interface Field Do this Challenge, Type a password. The password is used to protect the certificate or CSR. This information is optional. Confirm Challenge The value should be 4 to 64 characters long. Case sensitive. 3.
Page 237 Chapter 6: Using the Web Interface Creating a Self-Signed Certificate When appropriate certificate and key files for the PX2 device are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate. Note that you must enter information in the fields showing the message 'required.' To create and install a self-signed certificate: 1.
Page 238 Chapter 6: Using the Web Interface 4. Once complete, do the following: a. Double check the data shown in the New SSL Certificate section. b. If correct, click "Install Key and Certificate" to install the self-signed certificate and private key. Tip: To verify whether the certificate has been installed successfully, check the data shown in the Active SSL Certificate section.
Page 239 Active SSL Certificate section. Setting Up External Authentication Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than...
Page 240 Chapter 6: Using the Web Interface For security purposes, users attempting to log in to the PX2 must be authenticated. The PX2 supports the following authentication mechanisms: • Local user database on the PX2 Lightweight Directory Access Protocol (LDAP) • Remote Access Dial-In User Service (Radius) protocol •...
Page 241 Chapter 6: Using the Web Interface Special note about the AES cipher: The PX2 device's SSL/TLS-based protocols, including LDAPS, support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between the PX2 and the client (such as a web browser), which is impacted by the cipher priority of the PX2 and the client's cipher availability/settings.
Page 242 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 243 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 PX2 to communicate securely with...
Page 244 Chapter 6: Using the Web Interface Field/setting Description Bind DN Required after deselecting the Anonymous Bind checkbox. Distinguished Name (DN) of the user who is permitted to search the LDAP directory in the defined search base. Bind Password, Required after deselecting the Anonymous Bind checkbox. Confirm Bind Enter the Bind password.
Page 245 Chapter 6: Using the Web Interface To duplicate LDAP/LDAPS server settings: If you have added any LDAP/LDAPS server to the PX2, and the server you will add shares identical settings with an existing one, the most convenient way is to duplicate that LDAP/LDAPS server's data and then revise the IP address/host name.
Page 246 Chapter 6: Using the Web Interface Field/setting Description Authentication Port, The default are standard ports -- 1812 and 1813. Accounting Port To use non-standard ports, type a new port number. Timeout This sets the maximum amount of time to establish contact with the Radius server before timing out.
Page 247 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 248 Chapter 6: Using the Web Interface 2. Select the following checkbox. Then the PX2 always tries external authentication first. Whenever the external authentication fails, the PX2 switches to local authentication. 3. Click Save. To disable external authentication: 1. In the Authentication Type, select Local. 2.
Page 249 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 488). Unblocking a User To set limitations for login timeout and use of identical login names: 1.
Page 250 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 251: Setting The Date And Time
Chapter 6: Using the Web Interface Login manner after enabling the service agreement: After the Restricted Service Agreement feature is enabled, the agreement's content is displayed in the login screen. Do either of the following, or the login fails: In the web interface, select the checkbox labeled "I understand and •...
Page 252 Chapter 6: Using the Web Interface Customize the date and time  Select User Specified Time.  Type values in the Date field using the yyyy-mm-dd format, or click to select Calendar a date. For details, see (on page 234). ...
Page 253 Chapter 6: Using the Web Interface Button Function dates Click a date. (01-31) Today Select today. Clear Clear the entry, if any, in the Date field. Close Close the calendar. Windows NTP Server Synchronization Solution The NTP client on the PX2 follows the NTP RFC so the PX2 rejects any NTP servers whose root dispersion is more than one second.
Page 254: 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: Event: This is the situation where the PX2 or a device connected to it •...
Page 255 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 256 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 PX2, ...
Page 257 Chapter 6: Using the Web Interface 6. In this example, 'Above upper critical threshold' is selected because we want the PX2 to react only when the selected temperature sensor's reading enters the upper critical range. A "Trigger condition" field appears, requiring you to define the "exact" condition related to the "upper critical"...
Page 258 Chapter 6: Using the Web Interface Radio buttons for different events: According to the event you select, the "Trigger condition" field containing three radio buttons may or may not appear. Event types Radio buttons Numeric sensor Available radio buttons include "Asserted," threshold-crossing "Deasserted"...
Page 259 Chapter 6: Using the Web Interface Event types Radio buttons  Link state is up: The PX2 takes the action Network interface only when the network link state changes link state from down to up.  Link state is down: The PX2 takes the action only when the network link state changes from up to down.
Page 260 Chapter 6: Using the Web Interface Event types Radio buttons  Unreachable: The PX2 takes the action only Server reachability when any specified server becomes inaccessible.  Reachable: The PX2 takes the action only when any specified server becomes accessible. ...
Page 261 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Asset Management > Firmware Firmware update for asset strip Update [STRIPID] ('[STRIPNAME]'): status changed to '[STATE]'. Asset Management > Device Config parameter '[PARAMETER]' of Config Changed asset strip [STRIPID] ('[STRIPNAME]')
Page 262 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Device > Firmware update Firmware upgrade started from started version '[OLDVERSION]' to version '[VERSION]' by user '[USERNAME]' from host '[USERIP]'. Device >...
Page 263 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Device > Sending SNMP inform Sending SNMP inform to manager failed or no response [SNMPMANAGER]:[SNMPMANAGERP ORT] failed or no response. [ERRORDESC].
Page 264 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Peripheral Device Slot > * > Peripheral device Peripheral device Numeric Sensor > Below lower '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot warning threshold '[EXTSENSORSLOT]' asserted 'below '[EXTSENSORSLOT]' deasserted...
Page 265 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Modem > Dial-in link An incoming call from caller The incoming call from caller established '[CALLERID]' was received. '[CALLERID]' was disconnected: [CALLENDREASON].
Page 266 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE Outlet > * > Pole > * > Sensor > Sensor '[POLESENSOR]' on pole Sensor '[POLESENSOR]' on pole Unavailable '[OUTLETPOLE]' of outlet '[OUTLET]' '[OUTLETPOLE]' of outlet unavailable.
Page 267 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE PDU > Load Shedding > Started PX placed in Load Shedding Mode by PX removed from Load Shedding user '[USERNAME]' from host Mode by user '[USERNAME]' from '[USERIP]'.
Page 268 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE User Administration > Role Role '[TARGETROLE]' added by user added '[USERNAME]' from host '[USERIP]'. User Administration > Role Role '[TARGETROLE]' modified by user modified '[USERNAME]' from host '[USERIP]'.
Page 269 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE LHX/SHX > Condenser Pump The condenser pump on LHX at The condenser pump on LHX at Failure [PORTTYPE] port '[PORTID]' failed. [PORTTYPE] port '[PORTID]' is back to normal.
Page 270 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event = TRUE FALSE LHX/SHX > Threshold Water The water inlet temperature threshold The water inlet temperature on LHX Inlet on LHX at [PORTTYPE] port '[PORTID]' at [PORTTYPE] port '[PORTID]' is was crossed.
Page 271 Chapter 6: Using the Web Interface System Tamper Alarm: • This action causes the PX2 to show the alarm for the DX tamper sensor, if any, on the Dashboard page until a person acknowledges it. By default, this action has been assigned to the built-in tamper detection event rules.
Page 272 Chapter 6: Using the Web Interface Action Function Request LHX/SHX Applies the maximum cooling to the LHX/SHX Request LHX/SHX Maximum maximum cooling device. See Cooling (on page 259). This option is available only when the Schroff LHX/SHX support has been enabled. Send Email Send email Emails a textual message.
Page 273 Chapter 6: Using the Web Interface 4. Enter the information as needed and click Create. 5. Then you can assign the newly-created action to an event rule or Event Rules and Actions schedule it. See (on page 236). Alarm The Alarm is an action that requires users to acknowledge an alert. This helps ensure that the user is aware of the alert.
Page 274 Chapter 6: Using the Web Interface 7. (Optional) You can instruct the PX2 to send the acknowledgment notification after the alarm is acknowledged in the Acknowledgment Notifications field. Available methods are identical to those for generating alarm notifications. a. In the Available field, select desired methods one by one, or click Select All.
Page 275 Chapter 6: Using the Web Interface Stop Load Shedding: Quits the load shedding mode when the  specified event occurs. External Beeper If an external beeper is connected to the PX2, the PX2 can change the beeper's behavior or status to respond to a certain event. To control the connected external beeper: 1.
Page 276 If you have connected Raritan's asset strips to the PX2, you can also configure the PX2 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 277 Chapter 6: Using the Web Interface If "Start recording" is selected, adjust the values of the following: Number of Snapshots - the number of snapshots to be taken  when the event occurs. The maximum amount of snapshots that can be stored on the PX2 is 10.
Page 278 Chapter 6: Using the Web Interface Send Email You can configure emails to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and PX2 placeholders. The placeholders represent information is pulled from the PX2 and inserted into the message.
Page 279 (for outlet-switching capable PDUs only). Overcurrent protector sensors, including RMS current and tripping • state. Peripheral device sensors, which can be any Raritan environmental • sensor packages connected to the PX2, such as temperature or humidity sensors. Send Sensor...
Page 280 Chapter 6: Using the Web Interface a. Click the first to select a target component from the list. b. Click the second to select the specific sensor for the target from the list. c. Click to add the selected sensor to the Report Sensors list box.
Page 281 Chapter 6: Using the Web Interface Send SMS Message You can configure SMS messages to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and PX2 placeholders. The placeholders represent information which is pulled from the PX2 and inserted into the message.
Page 282 Chapter 6: Using the Web Interface Send Snapshots via Email This option notifies one or multiple persons for the selected events by emailing snapshots or videos captured by a connected Logitech ® webcam. Operation: 1. Choose Device Settings > Event Rules > 2.
Page 283 Chapter 6: Using the Web Interface To send SNMP v2c notifications: 1. In the Notification Type field, select SNMPv2c Trap or SNMPv2c Inform. 2. For SNMP INFORM communications, leave the resend settings at their default or do the following: a. In the Timeout field, specify the interval of time, in seconds, after which a new inform communication is resent if the first is not received.
Page 284 Chapter 6: Using the Web Interface 4. For both SNMP TRAPS and INFORMS, enter the following as needed and then click OK to apply the settings: a. Host name b. Port number c. User ID for accessing the host -- make sure the User ID has the SNMPv3 permission.
Page 285 Chapter 6: Using the Web Interface No script is available if you have not created or loaded it into the  PX2. 5. To apply different arguments than the default, do the following. Note that the newly-added arguments will override this script's default arguments.
Page 286 Chapter 6: Using the Web Interface Cycle Outlet: Cycles power to the selected outlet(s).  4. To specify the outlet(s) where this action will be applied, select them one by one from the Available Outlets list. To add all outlets, click Select All. ...
Page 287 Chapter 6: Using the Web Interface Syslog Message Use this action to automatically forward event messages to the specified syslog server. Determine the syslog transmission mechanism you prefer when setting it up - UDP, TCP or TLS over TCP. The PX2 may or may not detect the syslog message transmission failure. If yes, it will log this syslog failure as well as the failure reason in the Viewing or Clearing the Local Event Log event log.
Page 288 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 PX2 report the reading or state of a specific sensor regularly by scheduling the "Send Sensor Report"...
Page 289 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 290 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 291 Chapter 6: Using the Web Interface Then the PX2 will send out an email containing the specified temperature sensor readings hourly every day. Whenever you want the PX2 to stop sending the temperature report, simply deselect the Enabled checkbox in the timer. Email and SMS Message Placeholders Actions of "Send email"...
Page 292 Chapter 6: Using the Web Interface Placeholder Definition [CIRCUITSENSOR] The circuit sensor name [CIRCUIT] The circuit identifier [CONFIGPARAM] The name of a configuration parameter [CONFIGVALUE] The new value of a parameter [DATETIME] The human readable timestamp of the event occurrence [DEVICEIP] The IP address of the device, the event occurred on [DEVICENAME]...
Page 293 Chapter 6: Using the Web Interface Placeholder Definition [OUTLETNAME] The outlet name Note: If any outlet does not have a name, neither an outlet name nor an outlet number will be shown in the custom message for it. Therefore, it is recommended to check the availability of all outlet names if intending to use this placeholder.
Page 294 Chapter 6: Using the Web Interface Placeholder Definition [SYSNAME] SysName as configured for SNMP [TIMEREVENTID] The id of a timer event The timestamp of the event occurrence [TIMESTAMP] [TRANSFERSWITCHREASON] The transfer reason [TRANSFERSWITCHSENSOR] The transfer switch sensor name [TRANSFERSWITCH] The transfer switch label [UMTARGETROLE] The name of a user management role, an action was applied on...
Page 295 Chapter 6: Using the Web Interface Sample Event Rules Sample PDU-Level Event Rule In this example, we want the PX2 to record the firmware upgrade failure in the internal log when it happens. The event rule involves: Event: Device > Firmware update failed •...
Page 296 Chapter 6: Using the Web Interface Any sensor becomes unavailable.  The active energy sensor is reset.  For example, when the Inlet I1's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again.
Page 297 Chapter 6: Using the Web Interface Note: ID numbers of all sensors/actuators are available on the Peripherals page. See (on page 138). Peripherals 5. Select "State Sensor/Actuator" because the contact closure sensor is a state sensor. 6. Select "Alarmed" since we want the PX2 to respond when the selected contact closure sensor changes its state related to the "alarmed"...
Page 298 Chapter 6: Using the Web Interface Example 3 This example illustrates a situation where two event rules combined regarding the outlet state changes causes the PX2 to continuously power cycle outlets 1 and 2 in turn. Event selected Action included Outlet >...
Page 299: Setting Data Logging
Chapter 6: Using the Web Interface Setting Data Logging The PX2 can store 120 measurements for each sensor in a memory buffer. This memory buffer is known as the data log. Sensor readings in the data log can be retrieved using SNMP. You can configure how often measurements are written into the data log using the Measurements Per Log Entry field.
Page 300: Configuring Data Push Settings
Chapter 6: Using the Web Interface If any section's number of sensors exceeds 35, the remaining  sensors are listed on next page(s). If so, a pagination bar similar to the following diagram displays in this section, which you can click any button to switch between pages.
Page 301 Chapter 6: Using the Web Interface 5. If the destination server requires authentication, select the Use Authentication checkbox, and enter the following data. User name  Password  6. In the Entry Type field, determine the data that will be transmitted. Asset management tag list: Transmit the information of the ...
Page 302: Monitoring Server Accessibility
Chapter 6: Using the Web Interface Monitoring Server Accessibility You can monitor whether specific IT devices are alive by having the PX2 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 303 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 PX2 resumes resuming pinging pinging after the monitored equipment is after failure...
Page 304 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 305 Chapter 6: Using the Web Interface Field Data entered Wait time after successful ping To make the PX2 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 306: No Support For Front Panel Outlet Switching
Chapter 6: Using the Web Interface 5. Select the System SNMP Notification Action. Note: If you have not configured the System SNMP Notification Action to specify the SNMP destination(s), see Editing or Deleting a Rule/Action (on page 276). No Support for Front Panel Outlet Switching PX2-1000 models do NOT support the outlet-switching function.
Page 307: Configuring The Serial Port
Note: The serial port bit-rate change is required when the PX2 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 308: 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 PX2 model. You should read each example's introduction before applying them. You must have the Administrator Privileges to manage Lua scripts.
Page 309 Chapter 6: Using the Web Interface Writing or Loading a Lua Script You can enter or load up to 4 scripts to the PX2. Tip: If you can no longer enter or load a new script after reaching the upper limit, you can either delete any existing script or simply modify/replace an existing script's codes.
Page 310 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 311 Chapter 6: Using the Web Interface Manually Starting or Stopping a Script You can manually start or stop an existing Lua script at any time. When starting a script, you can choose to start it either with its default arguments or with new arguments. Tip: To have the PX2 automatically start or stop a script in response to an event, create an event rule.
Page 312 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 313 Chapter 6: Using the Web Interface Checking Lua Scripts States Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state and settings of each script. State: Four script states are available. : The script is never executed since the device boot. •...
Page 314: Miscellaneous
Chapter 6: Using the Web Interface 3. Click > Edit Script. 4. Make changes to the information shown, except for the script's name, which cannot be revised. To replace the current script, click Load Local File or Load  Example to select a new script. To delete a script: 1.
Page 315: Maintenance
Chapter 6: Using the Web Interface Field Description Domain password Type the authentication password (secret) for entering the Cisco EnergyWise domain  Up to 127 printable ASCII characters are permitted.  Spaces and asterisks are NOT acceptable. Port Type a User Datagram Protocol (UDP) port number for communications in the Cisco EnergyWise domain.
Page 316: 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 PX2. Tip: If the information shown on this page does not match the latest status, press F5 to reload it.
Page 317 PX2 Devices for Sharing Ethernet Connectivity (on page 33). This section explains how to identify a cascaded device on the Device Information page. Note: For more information on the USB-cascading configuration, see the , which is available from Raritan website's Cascading Guide Support page http://www.raritan.com/support/ To identify the USB-cascading status: 1.
Page 318 Chapter 6: Using the Web Interface Cascading information in the Bridging mode: The Common section contains two read-only fields for indicating the • cascading status. Note that the cascading position is NOT available in the bridging mode. Fields Description Port Forwarding Indicates the Port Forwarding is disabled.
Page 319 Chapter 6: Using the Web Interface Fields Description Cascaded Device Indicates whether a slave device is detected on the Connected USB-A or Ethernet port.  yes: Connection to a slave device is detected.  no: NO connection to a slave device is detected. A master device shows (zero) in the Cascade Position field and ...
Page 320: Viewing Connected Users
Chapter 6: Using the Web Interface The final slave device shows a non-zero number which indicates  its position in the Cascade Position field and in the Cascaded Device Connected field. The following diagram shows 2, indicating it is the second slave - Slave 2.
Page 321 Chapter 6: Using the Web Interface Column Description Client Type The interface through which the user is being connected to the PX2.  Web GUI: Refers to the web interface.  CLI: Refers to the command line interface (CLI). The information in parentheses following "CLI" indicates how this user is connected to the CLI.
Page 322: Viewing Or Clearing The Local Event Log
Chapter 6: Using the Web Interface Viewing or Clearing the Local Event Log By default, the PX2 captures certain system events and saves them in a local (internal) event log. You can view over 2000 historical events that occurred on the PX2 in the local event log.
Page 323: Updating The Px2 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 324 Chapter 6: Using the Web Interface A progress bar appears on the web interface, indicating the  update status. The front panel display shows the firmware upgrade message.  Three-Digit Row (on page 81). The outlet LEDs flash if the relay boards are being updated. If the ...
Page 325 Raritan. Contact Raritan Technical Support for the recovery utility, which works in Windows XP/Vista/7/10 and Linux. In addition, an appropriate PX2 firmware file is required in the recovery procedure.
Page 326: Viewing Firmware Update History
Chapter 6: Using the Web Interface STM32 Bootloader Update Failure The information in this section only applies to the PDU running a firmware version earlier than 2.1.6. When you are upgrading (or downgrading) the PX2-1000 or PX2-2000 series from any firmware version prior to version 2.1.6 to another version, there is possibility that a bootloader update failure message similar to the following appears at the end of the firmware update process.
Page 327: Bulk Configuration
Chapter 6: Using the Web Interface Bulk Configuration The Bulk Configuration feature lets you save generic settings of a configured PX2 device to your computer. You can use this configuration file to copy common settings to other PX2 devices of the same model and Bulk Configuration Restrictions firmware version.
Page 328 Chapter 6: Using the Web Interface Enter the admin password, and click Restore. 6. Wait until the PX2 device resets and the login page re-appears. Note: On startup, the PX2 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 329 Chapter 6: Using the Web Interface Device-Specific Settings NOT Included The settings saved in the bulk configuration file include user and role configurations, thresholds, event rules, security settings, date/time and so on. Note: Because the date and time settings are saved in the configuration file, users should exercise caution when distributing the configuration file to the PX2 devices in a different time zone than the source device.
Page 330: Backup And Restore Of Device Settings
Chapter 6: Using the Web Interface Example: You can perform bulk configuration between Raritan's PX2-4724-E2N1K2 and PX2-4724-E2N1K9. Reason: The two models share the same technical specifications, • and the only difference is their chassis colors represented by K2 (blue) and K9 (gray).
Page 331: Network Diagnostics
Chapter 6: Using the Web Interface Note: On startup, the PX2 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 332: Downloading Diagnostic Information
Raritan Technical Support. You can download the diagnostic file from the PX2 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 333: Rebooting The Px2 Device
Chapter 6: Using the Web Interface Rebooting the PX2 Device You can remotely reboot the PX2 device via the web interface. Resetting the PX2 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 334: 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 PX2 to factory defaults. 3. A message appears, with a countdown timer showing the remaining time of the operation.
Page 335: Webcam Management
Chapter 6: Using the Web Interface Webcam Management The webcam-related menu items appear only when there are webcam(s) Connecting a Logitech Webcam connected to the PX2. See (on page 73). With a Logitech webcam connected to the PX2, you can visually monitor ®...
Page 336 Chapter 6: Using the Web Interface You can send out this window's URL to share the live image with  Sending Snapshots or Videos in an Email or other users. See Instant Message (on page 319). Settings 5. To switch between snapshot and video modes, see the section below.
Page 337: Sending Snapshots Or Videos In An Email Or Instant Message
Chapter 6: Using the Web Interface Sending Snapshots or Videos in an Email or Instant Message Whenever you open a Primary Standalone Live Preview window, a unique URL is generated for this window session. A URL supports a maximum of three sessions.
Page 338: Viewing Saved Snapshots And Managing Storage
Chapter 6: Using the Web Interface 2. Click Live Preview > New Live Preview Window. The live snapshot or Configuring video in a standalone live preview window opens. See Webcams and Viewing Live Images (on page 317). 3. Copy the URL from the live preview window, and send it through an email or instant message application.
Page 339 Chapter 6: Using the Web Interface 3. If the latest saved snapshot is not listed yet, click > Refresh on the top of the list. 4. To manually delete any images: a. Select the checkboxes of the images you want to remove. ...
Page 340: Chapter 7 Using Snmp
Chapter 7 Using SNMP This SNMP section helps you set up the PX2 for use with an SNMP manager. The PX2 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 341: 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 323) ...
Page 342: Snmpv3 Notifications
Chapter 7: Using SNMP 6. Click Save. SNMPv3 Notifications 1. Choose Device Settings > Network Services > SNMP. 2. In the SNMP Agent, make sure the Enable SNMP v1/v2c checkbox is selected. 3. In the SNMP Notifications section, make sure the Enable SNMP Notifications checkbox is selected.
Page 343: Downloading Snmp Mib
Chapter 7: Using SNMP Field Description Authentication The three fields are available when the security Protocol, level is set to AuthNoPriv or authPriv. Authentication  Select the authentication protocol - MD5 or SHA Passphrase,  Enter the authentication passphrase Confirm Authentication Passphrase Privacy Protocol,...
Page 344: Snmp Gets And Sets
Chapter 7: Using SNMP MIB download via the Device Information page: 1. Choose Maintenance > Device Information. 2. In the Information section, click the desired download link: PDU2-MIB  ASSETMANAGEMENT-MIB  LHX MIB  3. Click Save to save the file onto your computer. Note: LHX-MIB is available only after the LHX/SHX support has been enabled.
Page 345 Chapter 7: Using SNMP Layout Opening the MIB reveals the custom objects that describe the PX2 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 346 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 PX2 to generate a warning and send an SNMP notification when certain Sensor Threshold Settings parameters are exceeded.
Page 347: A Note About Enabling Thresholds
Chapter 7: Using SNMP A Note about Enabling Thresholds When enabling previously disabled thresholds via SNMP, make sure you set a correct value for all thresholds that are supposed to be enabled prior to actually enabling them. Otherwise, you may get an error message.
Page 348: 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 PX2 device. CLI commands are case sensitive. In This Chapter About the Interface ................... 330 Logging in to CLI ..................331 Help Command..................
Page 349: 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 350: 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 334) in the User Guide for more information. Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile was used to log in to this product's web interface or CLI.
Page 351: With An Analog Modem
Chapter 8: Using the Command Line Interface With an Analog Modem The PX2 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 PX2 via the modem: 1.
Page 352: 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 PX2 device, the >...
Page 353: Help Command
Chapter 8: Using the Command Line Interface Help Command The help (?) command shows a list of main CLI commands available for the current mode. This is helpful when you are not familiar with CLI commands. Help command under the administrator mode: Help command under the configuration mode: config:# Help command under the diagnostic mode:...
Page 354: Querying Available Parameters For A Command
Chapter 8: Using the Command Line Interface Querying Available Parameters for a Command If you are not sure what commands or parameters are available for a particular type of CLI command or its syntax, you can have the CLI show them by adding a space and the help command (?) to the end of that command.
Page 355: Network Configuration
Chapter 8: Using the Command Line Interface Network Configuration This command shows all network configuration and all network interfaces' information, such as the IP address, MAC address, the Ethernet interface's duplex mode, and the wireless interface's status/settings. show network IP Configuration This command shows the IP-related configuration only, such as IPv4 and IPv6 configuration, address(es), gateway, and subnet mask.
Page 356 Chapter 8: Using the Command Line Interface Option Description Show the IP-related configuration of all interfaces. You can type the CLI command without the word show network ip interface 'all.' For example, IPv4-Only or IPv6-Only Configuration To show IPv4-only configuration or IPv6-only configuration, use any of the following commands.
Page 357 Chapter 8: Using the Command Line Interface Option Description ethernet Show the IPv4 or IPv6 configuration of the ETHERNET interface. wireless Show the IPv4 or IPv6 configuration of the WIRELESS interface. bridge Show the IPv4 or IPv6 configuration of the BRIDGE interface.
Page 358 Chapter 8: Using the Command Line Interface Network Service Settings This command shows the network service settings only, including the Telnet setting, TCP ports for HTTP, HTTPS, SSH and Modbus/TCP services, and SNMP settings. show network services <option> Variables: http https telnet snmp...
Page 359: 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 360: 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 361: Overcurrent Protector Information
Chapter 8: Using the Command Line Interface Overcurrent Protector Information This command is only available for models with overcurrent protectors for protecting outlets. This command syntax shows the overcurrent protector information, such as a circuit breaker or a fuse. show ocp <n> To show detailed information, add the parameter "details"...
Page 362: 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 PX2 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 PX2...
Page 363: Environmental Sensor Information
Chapter 8: Using the Command Line Interface Environmental Sensor Information This command syntax shows the environmental sensor's information. show externalsensors <n> To show detailed information, add the parameter "details" to the end of the command. show externalsensors <n> details External sensor 3 ('Temperature 1') Sensor type: Temperature Reading: 31.8 deg C (normal)
Page 364: 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 PX2 web interface. Displayed information: • Without the parameter "details," only the sensor ID, sensor type and reading are displayed.
Page 365: 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 366: Inlet Sensor Threshold Information
Chapter 8: Using the Command Line Interface Inlet Sensor Threshold Information This command syntax shows the specified inlet sensor's threshold-related information. show sensor inlet <n> <sensor type> To show detailed information, add the parameter "details" to the end of the command. show sensor inlet <n>...
Page 367: Inlet Pole Sensor Threshold Information
Chapter 8: Using the Command Line Interface Inlet Pole Sensor Threshold Information This command is only available for a three-phase PDU except for an in-line monitor (PX-3000 series). This command syntax shows the specified inlet pole sensor's threshold-related information. show sensor inletpole <n> <p> <sensor type> To show detailed information, add the parameter "details"...
Page 368: Overcurrent Protector 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 pole sensor are displayed. • With the parameter "details," more sensor information is displayed, including resolution and range.
Page 369: 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 370: 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, •...
Page 371: 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 •...
Page 372: Existing User Profiles
Chapter 8: Using the Command Line Interface Existing User Profiles This command shows the data of one or all existing user profiles. show user <user_name> To show detailed information, add the parameter "details" to the end of the command. show user <user_name> details Variables: <user_name>...
Page 373: 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 374: 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 PX2 device. show serial EnergyWise Settings This command shows the PX2 device's current configuration for Cisco ®...
Page 375: 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 376: 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 377: Event Log
Chapter 8: Using the Command Line Interface Event Log The command used to show the event log begins with show eventlog. limit class You can add either the 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 378: 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 379 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 380: Command History
Chapter 8: Using the Command Line Interface Command History This command syntax shows the command history for current connection session. show history Displayed information: A list of commands that were previously entered in the current • session is displayed. History Buffer Length This command syntax shows the length of the history buffer for storing history commands.
Page 381: Examples
Chapter 8: Using the Command Line Interface Option Description A specific Displays the specified number of last entries in the integer number reliability error log. Examples This section provides examples of the show command. Example 1 - Basic Security Information show security The diagram shows the output of the command.
Page 382 Chapter 8: Using the Command Line Interface Example 2 - In-Depth Security Information show security details More information is displayed when typing the command. Example 3 - Basic PDU Information show pdu The diagram shows the output of the command.
Page 383: Clearing Information
Chapter 8: Using the Command Line Interface 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. Clearing Information You can use the clear commands to remove unnecessary data from the PX2.
Page 384: Clearing Wlan Log
Chapter 8: Using the Command Line Interface Clearing WLAN Log This command removes all data from the diagnostic log for the wireless LAN (WLAN) connection. clear wlanlog -- OR -- clear wlanlog /y If you entered the command without "/y," a message appears, prompting you to confirm the operation.
Page 385: Quitting Configuration Mode
Chapter 8: Using the Command Line Interface "apply" command before closing the terminal emulation program. Closing the program does not save any configuration changes. See Quitting Configuration Mode (on page 367). Quitting Configuration Mode Both of "apply" and "cancel" commands let you quit the configuration mode.
Page 386 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 •...
Page 387 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 •...
Page 388 Chapter 8: Using the Command Line Interface Setting the PDU-Defined Cycling Power-Off Period This section applies to outlet-switching capable models only. This command sets the power-off period of the power cycling operation for all outlets. config:# pdu cyclingPowerOffPeriod <timing> Variables: <timing>...
Page 389 Chapter 8: Using the Command Line Interface Specifying Non-Critical Outlets This section applies to outlet-switching capable models only. This command determines critical and non-critical outlets. It is Load Shedding Mode associated with the load shedding mode. See page 127). config:# pdu nonCriticalOutlets <outlets1>:false;<outlets2>:true Separate outlet numbers and their settings with a colon.
Page 390 This command specifies your PX2 device's altitude above sea level (in meters). You must specify the PX2 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 factor.
Page 391 Chapter 8: Using the Command Line Interface Setting the Z Coordinate Format for Environmental Sensors This command enables or disables the use of rack units for specifying the height (Z coordinate) of environmental sensors. config:# pdu externalSensorsZCoordinateFormat <option> Variables: rackUnits freeForm •...
Page 392: Network Configuration Commands
Chapter 8: Using the Command Line Interface Examples This section illustrates several PDU configuration examples. Example 1 - PDU Naming The following command assigns the name "my px12" to the PDU. config:# pdu name "my px12" Example 2 - 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 393 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: ethernet wireless bridge <ETH> is one of the network interfaces: • . Note that you must choose/configure the bridge interface if your PX2 is set to the bridging mode.
Page 394 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: ethernet wireless...
Page 395 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 PX2 device. config:# network ipv4 interface <ETH> address <ip address> Variables: ethernet wireless...
Page 396 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 PX2 and devices in the other subnet.
Page 397 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 398 Chapter 8: Using the Command Line Interface automatic static <mode> is one of the modes: • Mode Description automatic The IPv6 configuration mode is set to automatic. static The IPv6 configuration mode is set to static IP address. Setting the IPv6 Preferred Host Name After selecting DHCP as the IPv6 configuration mode, you can specify the preferred host name, which is optional.
Page 399 Chapter 8: Using the Command Line Interface Setting the IPv6 Address After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX2 device. config:# network ipv6 interface <ETH> address <ip address>...
Page 400 Chapter 8: Using the Command Line Interface Setting IPv6 Static Routes If the IPv6 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the PX2 and devices in the other subnet.
Page 401 Chapter 8: Using the Command Line Interface config:# network ipv6 staticRoutes modify <route_ID> <dest-2> interface <ETH> Variables: <dest-1> is the IP address and prefix length of the subnet where the • IP address/prefix length PX2 belongs. The format is • <hop>...
Page 402 Chapter 8: Using the Command Line Interface Configuring DNS Parameters Use the following commands to configure DNS-related settings. Specify the primary DNS server: config:# network dns firstServer <ip address> Specify the secondary DNS server: config:# network dns secondServer <ip address> Specify the third DNS server: config:# network dns thirdServer <ip address>...
Page 403 Chapter 8: Using the Command Line Interface Enabling or Disabling the LAN Interface This command enables or disables the LAN interface. config:# network ethernet ETHERNET enabled <option> Variables: true or false <option> is one of the options: • Option Description true The specified network interface is enabled.
Page 404 Chapter 8: Using the Command Line Interface Changing the LAN Duplex Mode This command determines the LAN interface duplex mode. config:# network ethernet ETHERNET duplexMode <mode> Variables: auto half full <mode> is one of the modes: • Option Description auto The PX2 selects the optimum transmission mode through auto-negotiation.
Page 405 Chapter 8: Using the Command Line Interface - ASCII codes 0x20 ~ 0x7E Setting the Authentication Method This command sets the wireless authentication method to either PSK or Extensible Authentication Protocol (EAP). config:# network wireless authMethod <method> Variables: <method> is one of the authentication methods: •...
Page 406 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 407 Chapter 8: Using the Command Line Interface config:# network wireless allowConnectionWithIncorrectClock <option3> Variables: PEAP The value of <outer_auth> is because PX2 only supports • Protected Extensible Authentication Protocol (PEAP) as the outer authentication. MSCHAPv2 • The value of <inner_auth> is because PX2 only supports Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) as the inner authentication.
Page 408 Chapter 8: Using the Command Line Interface Option Description false The wireless network connection is NOT successfully established when the PX2 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 409 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 410 Chapter 8: Using the Command Line Interface cascading mode may not be enabled successfully. Mode Description bridge The network bridging mode, where each cascaded device is assigned a unique IP address. portForwarding The port forwarding mode, where every cascaded device in the chain shares the same IP address, with diverse port numbers assigned.
Page 411 Chapter 8: Using the Command Line Interface • <option3> is one of the following options: Option Description Ethernet Ethernet port is the port where the 1st slave device is connected. USB port is the port where the 1st slave device is connected. Setting Network Service Parameters network services A network service command begins with...
Page 412 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 413 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 •...
Page 414 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: passwordOnly publicKeyOnly <option> is one of the options: • passwordOrPublicKey Option Description passwordOnly Enables the password-based login only.
Page 415 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: enable disable <option> is one of the options: • Option Description enable The SNMP v3 protocol is enabled.
Page 416 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 417 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: true false • <option> is one of the options: Option Description true...
Page 418: 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 419 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: manual • <method> is one of the time setup options: Mode Description manual The date and time settings are customized.
Page 420 Chapter 8: Using the Command Line Interface Overriding DHCP-Assigned NTP Servers This command determines whether the customized NTP server settings override the DHCP-specified NTP servers. config:# time ntp overrideDHCPProvidedServer <option> Variables: true false • <option> is one of these options: Mode Description true...
Page 421 Chapter 8: Using the Command Line Interface Example To set the time zone: 1. Type the time zone command as shown below and press Enter. config:# time zone 2. The system shows a list of time zones. Type the index number of the desired time zone and press Enter.
Page 422 Chapter 8: Using the Command Line Interface Setting the Automatic Daylight Savings Time This command determines whether the daylight savings time is applied to the time settings. config:# time autoDST <option> Variables: enable disable • <option> is one of the options: Mode Description enable...
Page 423: 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 PX2 and then shows the result. For instructions on Setting NTP Parameters specifying NTP servers via CLI, see (on page 401).
Page 424 Chapter 8: Using the Command Line Interface Modifying Firewall Control Parameters There are different commands for modifying firewall control parameters. IPv4 commands • Enable or disable the IPv4 firewall control feature: config:# security ipAccessControl ipv4 enabled <option> Determine the default IPv4 firewall control policy for inbound traffic: config:# security ipAccessControl ipv4 defaultPolicyIn <policy>...
Page 425 Chapter 8: Using the Command Line Interface Option Description false Disables the IP access control feature. accept, drop reject • <policy> is one of the options: Option Description accept Accepts traffic from all IP addresses. drop Discards traffic from all IP addresses, without sending any failure notification to the source host.
Page 426 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 427 Chapter 8: Using the Command Line Interface insertAbove insertBelow • <insert> is one of the options: 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 428 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 429 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 430 Chapter 8: Using the Command Line Interface After the Restricted Service Agreement feature is enabled, the agreement's content is displayed in the login screen. Do either of the following, or the login fails: In the web interface, select the checkbox labeled "I understand and •...
Page 431 Chapter 8: Using the Command Line Interface IMPORTANT!! You are accessing a PDU. If you are not the system administrator, do NOT power off or power cycle any outlet without the permission of the system administrator. 3. Press Enter. 4. Type the following: --END-- 5.
Page 432 Chapter 8: Using the Command Line Interface Password Aging This command enables or disables the password aging feature, which controls whether the password should be changed at a regular interval: config:# security loginLimits passwordAging <option> Variables: enable disable • <option> is one of the options: Option Description enable...
Page 433 Chapter 8: Using the Command Line Interface User Blocking There are different commands for changing different user blocking parameters. These commands begin with security userBlocking. You can combine multiple commands to modify the user blocking Multi-Command Syntax parameters at a time. See (on page 480).
Page 434 Chapter 8: Using the Command Line Interface Enabling or Disabling Strong Passwords This command enables or disables the strong password feature. config:# security strongPasswords enabled <option> Variables: true false <option> is one of the options: • Option Description true Enables the strong password feature. false Disables the strong password feature.
Page 435 Chapter 8: Using the Command Line Interface Option Description disable No lowercase character is required. Uppercase Character Requirement This command determines whether a strong password includes at least a uppercase character. config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter <option> Variables: enable disable • <option>...
Page 436 Chapter 8: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option> Variables: enable disable <option> is one of the options: • Option Description enable At least one special character is required. disable No special character is required. Maximum Password History This command determines the number of previous passwords that CANNOT be repeated when changing the password.
Page 437 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 defaultPolicy <policy> IPv6 commands • Enable or disable the IPv6 role-based access control feature: config:# security roleBasedAccessControl ipv6 enabled <option> Determine the IPv6 role-based access control policy: config:# security roleBasedAccessControl ipv6 defaultPolicy <policy> Variables: true false...
Page 438 Chapter 8: Using the Command Line Interface Adding a Role-Based Access Control Rule Depending on where you want to add a new rule in the list, the command syntax for adding a rule varies. IPv4 commands • Add a new rule to the bottom of the IPv4 rules list: config:# security roleBasedAccessControl ipv4 rule add <start_ip>...
Page 439 Chapter 8: Using the Command Line Interface insertAbove insertBelow • <insert> is one of the options: 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 440 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> IPv6 commands • Modify a rule's IPv6 address range: config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> Modify an IPv6 rule's role: config:# security roleBasedAccessControl ipv6 rule modify <rule_number>...
Page 441 Chapter 8: Using the Command Line Interface Policy Description deny Drops traffic from the specified IP address range when the user is a member of the specified role Deleting a Role-Based Access Control Rule These commands remove a specific rule from the list. IPv4 commands config:# security roleBasedAccessControl ipv4 rule delete <rule_number>...
Page 442 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. security ipAccessControl ipv4 enabled true defaultPolicyIn accept config:# defaultPolicyOut accept Results: The IPv4 access control feature is enabled. •...
Page 443: 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 444 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 PX2 powers up. config:# outlet <n> stateOnDeviceStartup <option> Variables: <n>...
Page 445: 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: <n>...
Page 446 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 447: 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 PX2 device contains multiple inlets, this command names the 1st inlet. config:# inlet 1 name "AC source" Overcurrent Protector Configuration Commands ocp.
Page 448 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 PX2 prompts you to assign a password to the newly-created user. Then: 1.
Page 449 Chapter 8: Using the Command Line Interface 2. Re-type the new password for confirmation and press Enter. Variables: <name> is the name of the user whose settings you want to change. • Example The following procedure illustrates how to change the password of the user "May."...
Page 450 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 451 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 PX2 device only after that user's user profile is enabled. config:# user modify <name> enabled <option> Variables: •...
Page 452 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 Multi-Command Syntax modify the SNMPv3 parameters at a time. See (on page 480).
Page 453 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. • true false • <option3> is one of the options: Option Description true Authentication passphrase is identical to the password.
Page 454 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, •...
Page 455 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 456 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. • meter feet • <option2> is one of the options: Option Description meter...
Page 457 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 458 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 459 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 460 Chapter 8: Using the Command Line Interface Example 1 - Creating a User Profile The following command creates a new user profile and sets two parameters for the new user. config:# user create May enable admin Results: • A new user profile "May" is created. The new user profile is enabled.
Page 461: Role Configuration Commands
Chapter 8: Using the Command Line Interface Role Configuration Commands role A role configuration command begins with 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 462 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 463 Chapter 8: Using the Command Line Interface * The "switchOutlet" privilege requires an argument that is separated with a colon. The argument could be: All outlets, that is, • switchOutlet:all • An outlet number. For example: switchOutlet:1 switchOutlet:2 switchOutlet:3 A list of comma-separated outlets. For example: •...
Page 464 Chapter 8: Using the Command Line Interface Modifying a Role You can modify diverse parameters of an existing role, including its privileges. Modify a role's description: config:# role modify <name> description "<description>" Variables: • <name> is a string comprising up to 32 ASCII printable characters. <description>...
Page 465 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 All Privileges semi-colon.
Page 466: Environmental Sensor Configuration Commands
Chapter 8: Using the Command Line Interface Deleting a Role This command deletes an existing role. config:# role delete <name> Example - Creating a Role The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup Results: A new role "tester"...
Page 467 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 468 Chapter 8: Using the Command Line Interface Type Description vibration The connected detector/switch is for detection of the vibration. Setting the X Coordinate This command specifies the X coordinate of an environmental sensor. config:# externalsensor <n> xlabel "<coordinate>" Variables: <n> is the ID number of the environmental sensor that you want to •...
Page 469 Chapter 8: Using the Command Line Interface Setting the Z Coordinate This command specifies the Z coordinate of an environmental sensor. config:# externalsensor <n> zlabel "<coordinate>" Variables: <n> is the ID number of the environmental sensor that you want to •...
Page 470 Chapter 8: Using the Command Line Interface Using Default Thresholds This command determines whether default thresholds, including the deassertion hysteresis and assertion timeout, are applied to a specific environmental sensor. config:# externalsensor <n> useDefaultThresholds <option> Variables: • <n> is the ID number of the environmental sensor that you want to configure.
Page 471: Configuring Environmental Sensors' Default Thresholds
Chapter 8: Using the Command Line Interface Example 1 - Environmental Sensor Naming The following command assigns the name "Cabinet humidity" to the environmental sensor with the ID number 4. config:# externalsensor 4 name "Cabinet humidity" Example 2 - Sensor Threshold Selection The following command sets the environmental sensor #1 to use the default thresholds, including the deassertion hysteresis and assertion timeout, as its threshold settings.
Page 472 Chapter 8: Using the Command Line Interface config:# defaultThresholds <sensor type> lowerWarning <value> Set the Default Deassertion Hysteresis for a specific sensor type: config:# defaultThresholds <sensor type> hysteresis <hy_value> Set the Default Assertion Timeout for a specific sensor type: config:# defaultThresholds <sensor type>...
Page 473: Sensor Threshold Configuration Commands
Chapter 8: Using the Command Line Interface Sensor types Measurement units vibration <hy_value> is the deassertion hysteresis value applied to the • specified sensor type. • <as_value> is the assertion timeout value applied to the specified sensor type. It ranges from 0 to 100 (samples). Example - Default Upper Thresholds for Temperature It is assumed that your preferred measurement unit for temperature is set to degrees Celsius.
Page 474 Chapter 8: Using the Command Line Interface config:# sensor inlet <n> <sensor type> upperCritical <option> Set the Upper Warning threshold for an inlet sensor: config:# sensor inlet <n> <sensor type> upperWarning <option> Set the Lower Critical threshold for an inlet sensor: config:# sensor inlet <n>...
Page 475 Chapter 8: Using the Command Line Interface Sensor type Description unbalancedCurrent Unbalanced load sensor lineFrequency Line frequency sensor residualCurrent Residual current sensor phaseAngle Inlet phase angle sensor Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed. enable disable <option>...
Page 476 Chapter 8: Using the Command Line Interface config:# sensor inletpole <n> <p> <sensor type> upperWarning <option> Set the Lower Critical Threshold for an Inlet Pole: config:# sensor inletpole <n> <p> <sensor type> lowerCritical <option> Set the Lower Warning Threshold for an Inlet Pole: config:# sensor inletpole <n>...
Page 477 Chapter 8: Using the Command Line Interface Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed. enable disable • <option> is one of the options: or a numeric value. Option Description enable Enables the specified threshold for the specified inlet pole sensor.
Page 478 Chapter 8: Using the Command Line Interface config:# sensor ocp <n> <sensor type> lowerCritical <option> Set the Lower Warning threshold for an overcurrent protector: config:# sensor ocp <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an overcurrent protector: config:# sensor ocp <n>...
Page 479 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 overcurrent protector sensor. See Deassertion Hysteresis (on page 603). • <as_value> is a number in samples that is assigned to the assertion "To timeout for the specified overcurrent protector sensor.
Page 480 Chapter 8: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> assertionTimeout <as_value> Variables: <n> is the ID number of the environmental sensor that you want to • configure. The ID number is available in the PX2 web interface or using the command "show externalsensors <n>"...
Page 481 Chapter 8: Using the Command Line Interface Example 1 - Upper Critical Threshold for a Temperature Sensor The following command sets the Upper Critical threshold of the environmental "temperature" sensor with the ID number 2 to 40 degrees Celsius. It also enables the upper critical threshold if this threshold has not been enabled yet.
Page 482: Actuator Configuration Commands
Chapter 8: Using the Command Line Interface Actuator Configuration Commands actuator An actuator configuration command begins with . 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 480).
Page 483: Server Reachability Configuration Commands
Chapter 8: Using the Command Line Interface Note: To specify the Z coordinate using the rack units, see Setting (on page 373). the Z Coordinate Format for Environmental Sensors • <description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
Page 484 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 485 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 486 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 •...
Page 487: Energywise Configuration Commands
Chapter 8: Using the Command Line Interface EnergyWise Configuration Commands energywise An EnergyWise configuration command begins with Enabling or Disabling EnergyWise This command syntax determines whether the Cisco EnergyWise ® endpoint implemented on the PX2 device is enabled. config:# energywise enabled <option> Variables: true false...
Page 488 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 489: 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 PX2 is enabled. • The UDP port is set to 10288. •...
Page 490 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 PX2 device. config:# assetStrip <n> numberOfRackUnits <number> Note: A rack unit refers to a tag port on the asset strips. Variables: <n>...
Page 491 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 PX2 device. config:# assetStrip <n> rackUnitNumberingOffset <number> Variables: • <n> is the number of the FEATURE port where the selected asset strip is physically connected.
Page 492 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 493 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 494 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 476) and an LED Mode for a Rack Unit...
Page 495 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 496: Serial Port Configuration Commands
CONSOLE / MODEM on the PX2 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 PX2 or power cycle the connected device for proper communications.
Page 497: Setting The History Buffer Length
Chapter 8: Using the Command Line Interface Forcing the Device Detection Mode This command forces the serial port on the PX2 to enter a specific device detection mode. config:# serial deviceDetectionType <mode> Variables: automatic forceConsole • <mode> is one of the detection modes: forceAnalogModem, forceGsmModem Option...
Page 498: 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 499: 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. The PSK value is set to encryp_key.
Page 500: 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, PX2 prompts you to confirm the operation.
Page 501: 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 PX2 device can be turned on or off or power cycled through the CLI. Besides, you can cancel the power-on process while the PX2 is powering on ALL outlets.
Page 502: 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 503: 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 504: 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 505: 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 506: 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 507: Restarting The Pdu
Chapter 8: Using the Command Line Interface Restarting the PDU This command restarts the PX2 device. It is not a factory default reset. To restart the PX2 device: 1. Ensure you have entered administrator mode and the # prompt is displayed.
Page 508: Resetting To Factory Defaults
Chapter 8: Using the Command Line Interface If you entered the command without "/y", a message appears prompting you to confirm the operation. Type y to confirm the reset or n to abort it. Variables: <n> is the inlet number. •...
Page 509: 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 Different CLI Modes and entered the administrator or user mode. See Prompts (on page 334).
Page 510 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 511: Retrieving Previous Commands
Chapter 8: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your PX2 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 512: Logging Out Of Cli
Chapter 8: Using the Command Line Interface Example 1: Type the first word and the first letter of the second word of the "reset factorydefaults" command, that is, reset f. Then press Tab or Ctrl+i to complete the second word. Example 2: Type the first word and initial letters of the second word of the "security enforceHttpsForWebAccess"...
Page 513: Chapter 9 Using Scp Commands
Chapter 9 Using SCP Commands You can perform a Secure Copy (SCP) command to update the PX2 firmware, do bulk configuration, or back up and restore the configuration. In This Chapter Firmware Update via SCP ................. 495 Bulk Configuration via SCP ..............496 Backup and Restore via SCP ..............
Page 514: 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 515: Backup And Restore Via Scp
Chapter 9: Using SCP Commands 3. The system copies the configuration included in the file "bulk_config.xml" to another PX2, and displays the following message. Starting restore operation. The connection will be closed now. SCP examples: Save operation: • scp admin@192.168.87.50:/bulk_config.xml Copy operation: •...
Page 516: Downloading Diagnostic Data Via Scp
Chapter 9: Using SCP Commands scp backup_settings.xml <user name>@<device ip>:/settings_restore <user name> is the "admin" or any user profile with the  administrator privileges. <device ip> is the IP address of the PX2 whose settings you want  to restore. 2.
Page 517 Chapter 9: Using SCP Commands 3. The system saves the diagnostic data from the PX2 to a file named "diag-data.tgz." SCP example: scp admin@192.168.87.50:/diag-data.tgz Windows PSCP command: PSCP in Windows works in a similar way to the SCP.  pscp <user name>@<device ip>:/diag-data.tgz...
Page 518: Appendix A Specifications
Maximum Ambient Operating Temperature The maximum ambient operating temperature (TMA) for PX2 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 519: Feature Rj-45 Port Pinouts
Output Reserved ― Signal Ground ― Power for CIM (200mA, fuse protected) Warning: Pin 3 is only intended for use with Raritan devices. Output Transmit Data (Data out) Input Receive Data (Data in) No Connection ― Signal Ground Input Reserved...
Page 520: Appendix B Equipment Setup Worksheet
Appendix B Equipment Setup Worksheet PX2 Series Model ____________ PX2 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 521 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 522 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 523 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 524: Appendix C Configuration Or Firmware Upgrade With A Usb Drive
PX2 system requirements: • There is at least one USB-A port available on your Raritan device. Your PX2 must be version 2.2.13 or later. • Note that the PX2 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 525: Configuration Files
This file is required only when there are device-specific settings to devices.csv configure for multiple PX2 devices. See (on page 514). Raritan provides a Mass Deployment Utility, which helps you to quickly Creating Configuration generate all configuration files for your PX2. See Files via Mass Deployment Utility...
Page 526: Fwupdate.cfg
PX2 detects a problem with the USB drive contents. firmware Specify the name of a firmware binary file used to upgrade your PX2. • The specified firmware file must be compatible with your PX2 and • have an official Raritan signature.
Page 527 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 PX2, no firmware upgrade is performed unless you have set the option "force_update" to true. force_update If this option is set to true, the firmware upgrade is always •...
Page 528 Appendix C: Configuration or Firmware Upgrade with a USB Drive • The default value is serial:1, making the PX2 search for its serial number in the first column. This option is used only if the "device_list" option has been set. •...
Page 529 Appendix C: Configuration or Firmware Upgrade with a USB Drive config.txt Additional configuration keys set via the file will be applied • after performing the configuration restore operation. This option CANNOT be used with the option "bulk_config_restore." • • If a firmware upgrade will be performed at the same time, you must generate the full configuration backup file based on the NEW firmware version instead of the current firmware version.
Page 530: Config.txt
PX2 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 PX2 model and firmware version.
Page 531 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 532: 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 devices.csv device list configuration file - , to store unique data of each PX2. This file must be: An excel file in the CSV format.
Page 533: 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 534: 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 PX2 with these files. See a USB Drive (on page 506).
Page 535: 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 PX2, no firmware upgrade will be...
Page 536 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 537: 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 PX2 models and firmware Configuration Files versions. See (on page 507) or contact Raritan Technical Support to properly prepare some or all of the following files: fwupdate.cfg (always required)
Page 538: 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 539: Dhcp Ipv4 Configuration In Windows
Windows Server 2012 system. ® Required Windows IPv4 settings in DHCP: 1. Add a new vendor class for Raritan PX2 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 540 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 541 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 542 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 543 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 544 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 545 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 546 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 547 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 548 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 549: Dhcp Ipv6 Configuration In Windows
For those PX2 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 PX2 under IPv6.
Page 550 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 551 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 552 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 553 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 554 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 555 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 556: 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 PX2 will provide the following value of the vendor-class-identifier option (option 60). vendor-class-identifier = "Raritan PDU 1.0" ...
Page 557 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Configure the same option in DHCP accordingly. The PX2 accepts the configuration or firmware upgrade only when this value in DHCP matches. 3. Set the following three sub-options in the "vendor-encapsulated-options" (option 43). code 1 (pdu-tftp-server) = the TFTP server's IPv4 address ...
Page 558: 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 559 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 560: 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 PX2. Important: Exercise caution before resetting the PX2 to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on.
Page 561: Using The Cli Command
Appendix E: Resetting to Factory Defaults This diagram shows the location of the reset button on Zero U models. This diagram shows the location of the reset button on 1U models. This diagram shows the location of the reset button on 2U models. Note: HyperTerminal is available on Windows operating systems prior to Windows Vista.
Page 562 Appendix E: Resetting to Factory Defaults 3. Log in to the CLI by typing the user name "admin" and its password. 4. After the # system prompt appears, type either of the following commands and press Enter. reset factorydefaults -- OR -- reset factorydefaults /y 5.
Page 563: Appendix F Ldap Configuration Illustration
Configure LDAP authentication on the PX2 device d. Configure roles on the PX2 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 564: Step B. Configure User Groups On The Ad Server
Appendix F: LDAP Configuration Illustration Step B. Configure User Groups on the AD Server You must create the groups (roles) for the PX2 on the AD server, and then make appropriate users members of these groups. In this illustration, we assume: PX_Admin PX_User •...
Page 565: Step C. Configure Ldap Authentication On The Px2 Device
Appendix F: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the PX2 Device You must enable and set up LDAP authentication properly on the PX2 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 182) and...
Page 566: Step D. Configure Roles On The Px2 Device
Appendix F: 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 567 Appendix F: LDAP Configuration Illustration 2. Click to add a new role. a. Type PX_User in the Role Name field. b. Type a description for the PX_User role in the Description field. In this example, we type "View PX settings" to describe the role. c.
Page 568 Appendix F: LDAP Configuration Illustration To create the PX_Admin role with full permissions assigned: 1. Click to add another role. a. Type PX_Admin in the Role Name field. b. Type a description for the PX_Admin role in the Description field. In this example, we type "Includes all PX privileges"...
Page 569: Appendix G Updating The Ldap Schema
Appendix G Updating the LDAP Schema In This Chapter Returning User Group Information ............551 Setting the Registry to Permit Write Operations to the Schema ... 552 Creating a New Attribute ................552 Adding Attributes to the Class..............553 Updating the Schema Cache ..............555 Editing rciusergroup Attributes for User Members ........
Page 570: Setting The Registry To Permit Write Operations To The Schema
Appendix G: Updating the LDAP Schema Setting the Registry to Permit Write Operations to the Schema To allow a domain controller to write to the schema, you must set a registry entry that permits schema updates. To permit write operations to the schema: 1.
Page 571: Adding Attributes To The Class
Appendix G: Updating the LDAP Schema 3. Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears. rciusergroup 4. Type in the Common Name field. rciusergroup 5. Type in the LDAP Display Name field. 1.3.6.1.4.1.13742.50 6.
Page 572 Appendix G: 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 573: Updating The Schema Cache
Appendix G: Updating the LDAP Schema 6. Choose rciusergroup from the Select Schema Object list. 7. Click OK in the Select Schema Object dialog. 8. Click OK in the User Properties dialog. Updating the Schema Cache To update the schema cache: 1.
Page 574 Appendix G: Updating the LDAP Schema 3. Go to the directory where the support tools were installed. Run adsiedit.msc. The ADSI Edit window opens. 4. Open the Domain. 5. In the left pane of the window, select the CN=Users folder.
Page 575 Appendix G: Updating the LDAP Schema 6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties. 7. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list.
Page 576: Appendix H 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 558). FreeRADIUS Standard Attribute For configuration on FreeRADIUS, see Illustration (on page 576).
Page 577 Appendix H: 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 563). Some configuration associated with Microsoft Active Directory (AD) is AD-Related Configuration also required for RADIUS authentication.
Page 578 Appendix H: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX2. In this example, they are 1812 and 1813. Then close this dialog.
Page 579 Appendix H: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PX2 to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 580 Appendix H: 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 PX2. 5. Click OK.
Page 581 Appendix H: RADIUS Configuration Illustration Step B: Configure Connection Policies and Standard Attributes You need to configure the following for connection request policies: • IP address or host name of the PX2 • Connection request forwarding method Authentication method(s) • •...
Page 582 Appendix H: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
Page 583 Appendix H: RADIUS Configuration Illustration You can leave the "Type of network access server" field to the  default -- Unspecified.
Page 584 Appendix H: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
Page 585 Appendix H: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the PX2 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 586 Appendix H: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options: Override network policy authentication settings  CHAP -- the PX2 uses "CHAP" in this example ...
Page 587 Appendix H: RADIUS Configuration Illustration Note: If your PX2 uses PAP, then select "PAP."...
Page 588 Appendix H: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
Page 589 Appendix H: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
Page 590 Appendix H: RADIUS Configuration Illustration 12. In the Attribute Information dialog, click Add. Raritan:G{Admin} 13. Select String, type in the text box, and then click...
Page 591 Appendix H: RADIUS Configuration Illustration Admin inside the curved brackets {} is the existing role on the PX2. It is recommended to use the Admin role to test this configuration. The role name is case sensitive.
Page 592 Appendix H: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
Page 593 Appendix H: RADIUS Configuration Illustration 15. Click Next to continue.
Page 594: Freeradius Standard Attribute Illustration
Appendix H: 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 595: Vendor-Specific Attributes
Appendix H: RADIUS Configuration Illustration steve Cleartext-Password := "test123" Filter-ID = "Raritan:G{Admin}", Filter-ID = "Raritan:G{SystemTester}" Vendor-Specific Attributes You must specify the following properties when using a RADIUS vendor-specific attribute (VSA). Vendor code = 13742 • Vendor-assigned attribute number = 26 •...
Page 596 Appendix H: RADIUS Configuration Illustration Step A: Add Your PX2 as a RADIUS Client The RADIUS implementation on a PX2 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 597 Appendix H: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX2. In this example, they are 1812 and 1813. Then close this dialog.
Page 598 Appendix H: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PX2 to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
Page 599 Appendix H: 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 PX2. 5. Click OK.
Page 600 Appendix H: RADIUS Configuration Illustration Step B: Configure Connection Policies and Vendor-Specific Attributes You need to configure the following for connection request policies: • IP address or host name of the PX2 • Connection request forwarding method Authentication method(s) • •...
Page 601 Appendix H: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
Page 602 Appendix H: RADIUS Configuration Illustration You can leave the "Type of network access server" field to the  default -- Unspecified.
Page 603 Appendix H: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
Page 604 Appendix H: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the PX2 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 605 Appendix H: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options: Override network policy authentication settings  CHAP -- the PX2 uses "CHAP" in this example ...
Page 606 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 607: Freeradius Vsa Illustration
A vendor-specific dictionary file is required for the vendor-specific-attribute configuration on FreeRADIUS. Therefore, there are two major configuration steps. a. Use a dictionary to define the Raritan vendor-specific attribute b. Add all user data, including user names, passwords, and roles Presumptions in the illustration: Raritan attribute = Raritan-User-Roles •...
Page 608: 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...
Page 609 Appendix H: RADIUS Configuration Illustration 2. Right-click NPS (Local) and select "Register server in Active Directory." 3. Click OK, and then OK again. To grant PX2 users remote access permission: 1. Open Active Directory Users and Computers.
Page 610 Appendix H: RADIUS Configuration Illustration 2. Open the properties dialog of the user whom you want to grant the access permission. 3. Click the Dial-in tab and select the "Allow access" checkbox. To enable reversible encryption for CHAP authentication: 1. Open Active Directory Users and Computers. 2.
Page 611 Appendix H: RADIUS Configuration Illustration 3. Click the Account tab and select the "Store password using reversible encryption" checkbox.
Page 612: Appendix I Additional Px2 Information
Unbalanced Current Calculation .............. 608 Data for BTU Calculation ................609 Ways to Probe Existing User Profiles ............610 Raritan Training Website ................610 Role of a DNS Server ................611 Cascading Troubleshooting ..............611 Browsing through the Online Help ............616...
Page 613: Reserving Ip Addresses In Dhcp Servers
Appendix I: Additional PX2 Information Reserving IP Addresses in DHCP Servers The PX2 uses its serial number as the client identifier in the DHCP request. Therefore, to successfully reserve an IP address for the PX2 in a DHCP server, use the PX2 device's serial number as the unique ID instead of the MAC address.
Page 614 Appendix I: Additional PX2 Information Interface Client identifier conversion WIRELESS PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45 53 53  The suffix comprising the dash symbol and the word "WIRELESS"...
Page 615: Reserving Ip In Linux
Appendix I: Additional PX2 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. Use an interface's original client identifier without converting it into •...
Page 616: Sensor Threshold Settings
Appendix I: Additional PX2 Information For example, the client identifier of the ETHERNET interface looks like the following: \000PEG1A00003 3. Now enter the original client identifier with the following syntax. The client identifier is enclosed in quotation marks. host mypx { option dhcp-client-identifier = "\000PEG1A00003";...
Page 617 Appendix I: Additional PX2 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 618 Appendix I: Additional PX2 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 619: To Assert" And Assertion Timeout
Appendix I: Additional PX2 Information "To Assert" and Assertion Timeout If multiple sensor states are available for a specific sensor, the PX2 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 PX2 to assert.
Page 620 Appendix I: Additional PX2 Information In the threshold settings, the Assertion Timeout field postpones or even cancels the "assertion" action. It determines how long a sensor must be in the "worse" new state before the PX2 triggers the "assertion" action. If that sensor changes its state again within the specified wait time, the PX2 does NOT assert the worse state.
Page 621: To De-Assert" And Deassertion Hysteresis
Appendix I: Additional PX2 Information "To De-assert" and Deassertion Hysteresis After the PX2 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 622 Appendix I: Additional PX2 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 623: Pdview App For Viewing The Px2
PDView App for Viewing the PX2 Raritan has developed an app that can turn your iOS or Android mobile device into a local display for the PX2. This app is called PDView and it can be downloaded for free.
Page 624 Appendix I: Additional PX2 Information 2. After installing the PDView, launch it. Below illustrates the PDView screen for Android devices. 3. Connect your mobile device to the USB port of the PX2. Your mobile device type determines which USB port on the PX2 shall be used to connect the mobile device.
Page 625: Altitude Correction Factors
PX2. 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 626: Unbalanced Current Calculation
Appendix I: Additional PX2 Information Altitude (meters) Altitude (feet) Correction factor 1394 1.00 1640 1.01 2428 1.04 1500 4921 1.15 2250 7382 1.26 3000 9842 1.38 Unbalanced Current Calculation Unbalanced current information is available on 3-phase models only. This section explains how the PX2 calculates the unbalanced current percentage.
Page 627: Data For Btu Calculation
Appendix I: Additional PX2 Information Example: Each line's current: • L1 = 5.5 amps L2 = 5.2 amps L3 = 4.0 amps Average current: (5.5+5.2+4.0) / 3 = 4.9 amps • • L1 current unbalance: (5.5 - 4.9) / 4.9 = 0.1224 L2 current unbalance: (5.2 - 4.9) / 4.9 = 0.0612 •...
Page 628: Ways To Probe Existing User Profiles
Webcam-Live-Preview sessions, which show a list of associated user names. Raritan Training Website Raritan offers free training materials for various Raritan products on the Raritan training website http://www.raritantraining.com . The Raritan products introduced on this website include the intelligent PDU,...
Page 629: Role Of A Dns Server
Appendix I: Additional PX2 Information Role of a DNS Server As Internet communications are carried out on the basis of IP addresses, appropriate DNS server settings are required for mapping domain names (host names) to corresponding IP addresses, or the PX2 may fail to connect to the given host.
Page 630 For the wireless networking, one of the following may lead to the accessibility failure: The USB wireless LAN adapter attached to the  master device is not the Raritan USB WIFI LAN USB Wireless LAN Adapters adapter. See (on page 22).
Page 631 Appendix I: Additional PX2 Information Symptom Probable cause Network connection to the master device is lost. • Failure to access a slave device The cascading cable connected to the slave device in • question or any upstream device (if available) is loose or lost.
Page 632: Slave Connection And Disconnection Events
Appendix I: Additional PX2 Information Slave Connection and Disconnection Events In the bridging mode, events regarding connection/disconnection of a downstream slave device via USB is NOT logged. However, in the port forwarding mode, whenever the connection or disconnection of a downstream slave device via USB is detected, the PX2 at the USB-A end of the USB cable logs it in the internal log.
Page 633 Appendix I: Additional PX2 Information Ping via the CLI You can access the CLI interface by connecting a computer to the PX2 or SSH/Telnet Access With SSH or Telnet using SSH/Telnet. See (see " " on page 332) for details. You must perform the ping command in the diagnostic mode.
Page 634: Browsing Through The Online Help
Appendix I: Additional PX2 Information diag> ping <host> count <number1> size <number2> timeout <number3> Browsing through the Online Help The PX2 Online Help is accessible over the Internet. To use online help, Active Content must be enabled in your browser. If you are using Internet Explorer 7, you must enable Scriplets.
Page 635 "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 636: Appendix J Integration
Appendix J Integration The PX2 device can work with certain Raritan products to provide diverse power solutions. In This Chapter Dominion KX II / III Configuration ............. 618 Dominion KSX II, SX or SX II Configuration ..........623 Power IQ Configuration ................628 dcTrack ......................
Page 637: 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 638 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 639 Appendix J: Integration 3. Click OK.
Page 640: Turning Outlets On/Off And Cycling Power
PDU (power strip) with each. From this page, you can define those associations so that you can power on, power off, and power cycle the server from the Port Access page. To use this feature, you will need: Raritan remote rack PDU(s) • • Power CIMs (D2CIM-PWR)
Page 641: 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 642 Appendix J: Integration Connecting a Rack PDU To connect the Raritan PX to the KSX II: 1. Connect one end of a Cat5 cable to the following ports of different Raritan PX. PX1 series: RJ-45 "SERIAL" port  PX2 or PX3 series: RJ-45 "FEATURE" port ...
Page 643: Dominion Sx And Sx Ii
PX2 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 644 Appendix J: Integration 4. You can now add the PX as a managed power strip to the SX II. See Configure Power Strips from the Remote Console or Configure Power Strips Using CLI in the SX II User Guide or Online Help. PX appliance SX II Dominion SX...
Page 645 Appendix J: Integration 3. Type a name and description in the Name and Description fields. 4. Select the number of outlets from the Number of Outlets drop-down menu. 5. Type the port number in the Port field. 6. Click OK. Power Control 1.
Page 646: Power Iq Configuration
Appendix J: Integration Checking Power Strip Status 1. Choose Power Control > Power Strip Status. 2. A status box appears, displaying details of the controlled PX2, 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 647: Dctrack
Appendix J: Integration dcTrack Sunbird's dcTrack is a product that allows you to manage the data ® center. The PX2 is categorized as a power item in dcTrack. dcTrack offers an import wizard for conveniently adding the PX2 as well as other IT equipment to dcTrack for management.
Page 648: Dctrack Overview
Appendix J: Integration dcTrack Overview dcTrack is a powerful and intelligent data center management and ® automation application. It has been designed by data center and IT professionals to provide broad and deep visibility into the data center. It empowers data center managers to plan for growth and change by optimizing their current operations, assets, and infrastructure.
Page 649: Asset Management Strips And Dctrack
The PX2 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 •...
Page 651: Index
Index Asset Strip Management • 471 Asset Strip Settings • 356 Associating Outlets with Target Devices • 622 1U and 2U Port Locations • 78 Automatic Mode • 83 1U Products • 2 Automatically Completing a Command • 493 Available Actions • 74, 205, 236, 252, 256, 261, 270, 276, 317, 323 2U Products •...
Page 652 Index Changing an Outlet's Default State • 426 config.txt • 507, 509, 512 Changing HTTP(S) Settings • 180, 203, 204, Configuration Files • 507, 519 Configuration or Firmware Upgrade with a Changing Measurement Units • 437, 440 USB Drive • 32, 310, 506, 516, 519 Configuring a Multi-Inlet Model •...
Page 653 Index Connecting Composite Asset Strips • 67, 71 Default Log Messages • 232, 237, 242, 258, Connecting Environmental Sensor Packages • 37, 72, 138 Default Measurement Units • 344 Connecting External Equipment (Optional) • 37, Deleting a Firewall Rule • 410 Deleting a Monitored Device •...
Page 654 Index Enabling the Restricted Service Agreement • 93, 180, 211, 232 EnergyWise Configuration Commands • 469 EAP CA Certificate Example • 388, 390 EnergyWise Settings • 356 Editing or Deleting a Rule/Action • 252, 276, Entering Configuration Mode • 334, 366, 390, 431, 439 Editing or Deleting IP Access Control Rules •...
Page 655 Index Example 1 - Environmental Sensor Naming • Example 1 - IPv4 Firewall Control Feature Port • 99, 156, 158, 166, 168, 170 Configuration • 423 Feature RJ-45 Port Pinouts • 501 Example 1 - Networking Mode • 400 Filling Out the Equipment Setup Worksheet • Example 1 - PDU Naming •...
Page 656 Index Initial Network Configuration via CLI • xvii, 4, Login, Logout and Password Change • 92 23, 24, 25, 27, 195, 542, 543 Logout • 95 Initialization Delay Use Cases • 112, 116 Lowercase Character Requirement • 416 Inlet • 98, 103, 104, 114, 119, 121 Lua Scripts •...
Page 657 Product Models • 1 Numeric Character Requirement • 417 Push Out Sensor Readings • 253, 258 PX2-1000 Series • 77 PX2-2000 Series • 77 OCPs • 99, 105, 133, 135, 137 Options for Outlet State on Startup • 112, 115, Querying Available Parameters for a Outlet Configuration Commands •...
Page 658 Rack-Mounting the PDU • 6 Schroff LHX/SHX • 157, 167 RADIUS Configuration Illustration • 222, 558 SecureLock™ Outlets and Cords • 18 Raritan Training Website • 610 Security Configuration Commands • 405 Rebooting the PX2 Device • 297, 315 Security Settings • 353 Record Snapshots to Webcam Storage •...
Page 659 Index Setting Network Service Parameters • 393 Setting the sysContact Value • 397 Setting Non-Critical Outlets • 123, 126, 127 Setting the sysLocation Value • 398 Setting NTP Parameters • 401, 405 Setting the sysName Value • 398 Setting Outlet Power-On Sequence and Delay Setting the Time Zone •...
Page 660 Index Specifying the SSH Public Key • 396, 438 Turning Off the Outlet(s) • 484 Standard Attributes • 558 Turning On the Outlet(s) • 483 Start or Stop a Lua Script • 254, 266, 291, 293 Turning Outlets On/Off and Cycling Power • Static Route Examples •...
Page 661 Index Ways to Probe Existing User Profiles • 610 Web Interface Overview • 95, 616 Webcam Management • 99, 303, 317 What's New in the PX2 User Guide • xvii Windows NTP Server Synchronization Solution • 234, 235 Wired Network Settings • 181, 182, 196, 210, Wireless LAN Diagnostic Log •...

This manual is also suitable for:

Px2-2000 series

Raritan PX2-1000 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

Appendix A Specifications

Appendix B Equipment Setup Worksheet

Appendix C Configuration or Firmware Upgrade with a USB Drive

Appendix D Bulk Configuration or Firmware Upgrade Via DHCP/TFTP

Appendix E Resetting to Factory Defaults

Quick Links

User Guide

Troubleshooting

Related Manuals for Raritan PX2-1000 SERIES

Summary of Contents for Raritan PX2-1000 SERIES