The PX is an intelligent rack Power Distribution Unit (iPDU) that allows users to monitor power and environmental conditions such as temperature and humidity.

It can be used as a stand-alone power distribution unit, or integrated with Raritan’s Power IQ® energy management software, KVM switches and CommandCenter® Secure Gateway (CC-SG).

No. On the contrary, Raritan has been in the rack power distribution business since 2003.

Yes. It can be used either as a stand-alone power management unit or it can be integrated with Raritan’s access and management products, including Power IQ and CommandCenter Secure Gateway.

Yes. PX is deployable as part of an enterprise-wide management solution with Raritan’s CommandCenter Secure Gateway. Hundreds of PX units can be managed via CommandCenter Secure Gateway directly or through Dominion SX (serial only), KX and Paragon® II.

The Raritan Power IQ software manages rack PDUs, providing a single Web interface for outlet, rack and data center power, current, voltage, temperature and humidity monitoring and remote outlet switching. Power IQ manages the PX and third-party rack PDUs, and can also be integrated with data warehouse and enterprise reporting systems.

Raritan’s CommandCenter Secure Gateway is designed specifically to provide centralized management. It is the ideal solution if you are looking to consolidate management of devices such as PX with other Raritan network-based products.

For IP-based consolidation, SNMP or external Command Line Interface (CLI), scripting may be considered.

PX offers additional features such as outlet-level power monitoring, access via both Ethernet (TCP IP) and serial for remote access, an intuitive browser-based GUI, support for optional temperature and humidity sensors and other flexible access methods.

Yes. The architecture of the PX enables easy firmware upgrades via updates from Raritan.com so you can have the latest functionality without having to buy new hardware.

Yes. Currently all firmware upgrades are free.

For access using a Web browser, the PX does not require any software to be loaded on the client; however, the browser does have to be JavaTM-enabled. When using SSH/TELNET, the customer has to provide an SSH/TELNET client. In some operating systems, like Linux®, an SSH client is included in the distribution. Also, OpenSSH.org has an SSH client that can be downloaded free of charge. PuTTY is one of the most popular SSH clients for Windows® and can also be downloaded free from the Internet.

Yes. There are currently hundreds of PX models. Additional models of the PX family are introduced on a regular basis.

Yes. Note that lead times will vary depending on the level of customization required.

The PX comes in two form factors:

• Horizontal rack mount – 1U, 2U models
• Vertical mount – Zero U models

All five mounting positions are supported with APC racks.

The PX horizontal (rack mount) units come standard with a complete ready-to-install 19" rack mount kit.

PX uses UL 489 circuit breakers for branch circuit protection in North America and most of the world. Some PX models, however, have been made available with outlet fuses at customers’ requests, typically outside North America.

A 20 amp or less rack PDU (1- or 3-phase) is always connected to a branch circuit that is protected by a 20 amp circuit breaker in a panelboard (aka building PDU, RPP). This breaker trips when the total of all the outlets in a rack PDU exceeds 20 amps.

North American 208V 3-phase PDUs have the outlets divided into 3 banks. Each bank is wired across two phase legs (L1-L2, L2-L3, L3-L1). NEC requires that if a PDU input is rated greater than 20 amps, then a 2-pole 20 amp circuit breaker must be used to protect each bank of outlets. When each bank draws 20 amps, the total amps on each input line is 35 amps.
In general, we design PDUs using the following rules:

• If a PDU is rated 20 amps or less (or 16 amps internationally), then no circuit breakers are used (per UL 60950-1).
• If a PDU is rated greater than 20 amps (or greater than 16 amps internationally), then outlets are divided into banks and each bank is over-current protected by a 20 amp (or 16 amp) circuit breaker.

No. In PX PDUs, the control circuitry is in front of all circuit breakers, so tripping any one or more breakers has no affect on power delivered to the controller. In PX 3-phase PDUs, power for the controller is derived from all 3 phases, so even loss of any 2 of 3 phases will not affect power delivered to the controller.

No. The PX is designed to continue to run with NO change to the power outlets in the case of an electronics malfunction. The outlets that are on will remain on and the outlets that are off will remain off.

By factory default all the outlets are enabled – that is to say, they are turned “on.” For models without switching, e.g., PX-4000 and PX-1000 series, all outlets are always on.

In the world of power, RED indicates that the power is running (outlet is “live” or “hot”) to that outlet. GREEN indicates it is NOT running or that the outlet is not enabled. For PX models without switching, all outlets are always enabled.

Yes. Just ensure that both interfaces are enabled and configured.

Yes.

Yes. But it can also be set to run at 100Mbps.

This connector (labeled “feature” on some models and “sensor” on others) is for adding Raritan’s optional but fully integrated environmental monitoring sensors.

Yes. Optional but fully integrated environmental sensors are available.

Clicks from a PX that supports switching are typically relays opening and closing which is normal. When a circuit breaker (CB) trips, the LED will blink yellow because internal relay boards will not be receiving voltage from the tripped CBs. Also, the CB handle will be physically in the “off” position. Using the LED panel on the PDU to view outlet voltages (press up/down keys together to toggle from current readings to voltage readings), the voltages will be zero or near zero if the CBs have tripped.

PX ships from the factory with Dynamic Host Configuration Protocol (DHCP) enabled. DHCP is a protocol used by networked devices (clients) to obtain various parameters necessary for the clients to operate in an Internet Protocol (IP) network. DHCP automates the assignment of IP addresses, subnet masks, default gateway and other IP parameters. If a PX is moved to a new location, with DHCP still enabled (the factory default setting), DHCP will again automatically assign the PX an IP address, subnet mask, etc. If the IT administrator tries to access the PX using the IP address assigned at the previous location, the PX will not respond because the PX now has a different IP address. When moving a PX, IT administrators should 1) leave DHCP enabled and then access the serial port of the PX to find the new IP address (see Quick Start Guide), 2) disable DHCP prior to moving the PX so it retains the same IP address or 3) if possible, configure DHCP to assign a specific IP address to the PX.

Yes, for outlet metered, outlet switched and outlet metered only models. Outlet monitoring is supported when using the GUI (HTML interface) and SNMP (via the Ethernet port) and via the Command Line Interface (CLI) – Ethernet or serial.

For all PX models, reporting occurs at three levels: 1) phase level,
2) PDU level and 3) circuit breaker level. For PX-5000 and PX-4000 models, power is also reported at the outlet level.

Yes, Raritan’s Power IQ supports outlet grouping associations across PDUs.

Yes, SSH connections are supported.

Yes, PX supports TELNET, but it is disabled by factory default.

PX supports enabling of the TELNET daemon. However, because TELNET sends all information “in the clear,” enabling TELNET is at the customer’s own discretion. Raritan strongly suggests the use of SSH as a safer alternative to TELNET, since all data is encrypted, including the login sequence.

Yes. Up to two external NTP servers can be supported by the PX.

Yes. Up to two DNS servers can be supported by the PX.

Yes.

Yes. The SMASH CLP­based CLI allows management and configuration of very granular features, like per-outlet IP access control list (ACL). On all models with a model number which looks like PX2-nnnn (where nnnn are numbers), the CLI is JSON-RPC.

Yes. PX supports SNMP TRAPs, SETs and GETs via an Enterprise MIB. Dominion PX supports SNMP v1, v2 and v3.

Yes. PX supports syslog – to primary and secondary servers.

Yes.

Yes. The PX supports SMTP server authentication.

Port 443 (for https); optionally, port 80 (http) for user sessions. When using SSH, port 22 needs to be open. For TELNET, port 23 needs to be open.

Yes, but only if you use the Dominion SX or other console server that supports this capability.

Yes, the PX supports local port access. Default parameters are 9600-N-8-1. The local port on the PX is an RJ-45 female. An RJ-45 male to DB9F (female) null-modem cable is provided with each PX for setup and crash-cart applications.

Models that have part number PX2-nnnn (where nnnn are numbers), the default speed for the port is 115.2Kbps (N-8-1), and the serial port on the units is a DB9M (male).

A hardware reset button (recessed pinhole) is provided to allow access to a software (CLI command) mode to restore the unit to factory default. It can also be restored to factory default from the HTML GUI using a Web browser. For safety and security reasons it is not possible to restore the unit to factory default otherwise.

The PX hardware supports up to 256-bit AES encryption DPC and DPX models, and all models with a model number PX-nnnn (e.g. PX-5000, PX-4000, PX-3000). Models with model number PX2-nnnn support AES via software.

PX is a secure appliance. Therefore, NO access is possible to the operating system.

For security reasons, PX does not have any “backdoor” usernames or passwords. Restoring the unit to factory default will reset it to the factory default username and password.

Yes. Full support is provided for strong password options, for example, lockout on retries, password length and character control and a host of other options.

Yes, PX fits into most network configurations utilizing TCP/IP. Set up the VPN (typically IPSec) connection, then start the Web browser and enter the URL for the PX unit, or use SSH or Telnet. The session to the PX runs transparently over the VPN tunnel.

Yes.

Yes.

Yes.

DPC and DPX models, and all models with a model number PX-nnnn (e.g.,       PX-5000, PX-4000, PX-3000) support local database, RADIUS, LDAP/S and Active Directory®.

Models with model number PX2-nnnn support AES via software, local database, LDAP/S and Active Directory.

Yes. PX can support authorization at a per­port level – via the local database, RADIUS, LDAP/S and Active Directory.

Yes.

Yes.

Dominion SX release 3.1 and above fully supports the PX.

For control via the serial port of the PX, CommandCenter Secure Gateway release 3.1.1 or higher is required.

No. The old PowerBoard applet is not compatible with Dominion SX  3.0 and newer releases. Upgrade the Dominion SX unit to release 3.1 or higher for support of the PX when the Dominion SX is used in a stand-alone mode to manage the PX. When using the CommandCenter Secure Gateway with a Dominion SX, CC-SG can be used to provide the On/Off/Recycle commands to the PX via the Dominion SX.

This is limited only by the maximum number of serial ports on a Dominion SX. For example, a 16-port Dominion SX unit can be used to control 16 PX units, and a 32-port Dominion SX unit can be used to manage 32 PX units. See the PX User Guide for more details on interoperability and maximum units supported by other Dominion series products.

Yes. See the PX User Guide for more details on interoperability and maximum units supported by other Dominion series products.

Yes. The PX is RoHS compliant.