Raritan PXE User Manual
  1. Manuals
  2. Brands
  3. Raritan Manuals
  4. Power distribution unit
  5. PXE
  6. User manual

Raritan PXE User Manual

Hide thumbs Also See for PXE:
Table of Contents

Advertisement

Quick Links

Download this manual
Raritan PXE
User Guide
Release 3.0
Copyright © 2014 Raritan, Inc.
PXE-0C-v3.0-E
August 2014
255-80-0008-00

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PXE and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Raritan PXE

Summary of Contents for Raritan PXE

  • Page 1 Raritan PXE User Guide Release 3.0 Copyright © 2014 Raritan, Inc. PXE-0C-v3.0-E August 2014 255-80-0008-00...
  • Page 2 60950-1 or equivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury and death. WARNING! Do not use a Raritan product containing outlet relays to power large inductive loads such as motors or compressors. Attempting to power a large inductive load may result in damage to the relay.
  • Page 3 Safety Instructions 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 2014 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 5: Table Of Contents

    Contents Safety Guidelines Safety Instructions What's New in the PXE User Guide xiii Chapter 1 Introduction Product Models ..........................1 Package Contents.......................... 1 Zero U Products........................1 1U Products ......................... 1 Chapter 2 Rack-Mounting the PDU Rackmount Safety Guidelines ....................... 2 Circuit Breaker Orientation Limitation ....................
  • Page 6 Installing Cable Retention Clips on Outlets (Optional) ..............16 Chapter 4 Connecting Environmental Sensor Packages (Optional) DPX Sensor Packages ........................ 18 Using an Optional Sensor Hub ..................19 Using a Raritan Y cable.....................21 Supported Maximum DPX Sensor Distances..............22 DPX2 Sensor Packages ......................23 DX Sensor Packages........................25 Chapter 5 Using the PDU Panel Components ........................
  • Page 7 Specifying the Device Altitude ...................73 Setting Data Logging ......................74 Configuring SMTP Settings ....................75 Setting the EnergyWise Configuration ................76 Rebooting the PXE Device ....................77 Resetting All Active Energy Readings................77 Internal Beeper State......................78 User Management ........................78 Creating a User Profile ......................78 Modifying a User Profile ....................81...
  • Page 8 Disabling the Automatic Management Function..............172 Controlling Actuators .......................172 Bulk Configuration........................173 Saving the PXE Configuration ..................174 Copying the PXE Configuration..................175 Backup and Restore of PXE Device Settings................176 Network Diagnostics ........................177 Pinging a Host .........................177 Tracing the Network Route....................177 Listing TCP Connections ....................178 Downloading Diagnostic Information ..................178...
  • Page 9 Reliability Error Log ......................215 Command History......................216 History Buffer Length.......................216 Examples .........................216 Clearing Information........................218 Clearing Event Log ......................218 Configuring the PXE Device and Network.................219 Entering Configuration Mode...................219 Quitting Configuration Mode....................219 PDU Configuration Commands ..................220 Network Configuration Commands..................223 Time Configuration Commands..................241 Security Configuration Commands..................244 Outlet Configuration Commands ..................264...
  • Page 10 Actuator Control Operations ......................312 Switching On the Actuator(s)...................313 Switching Off the Actuator(s)...................314 Example - Turning On a Specific Actuator ..............314 Unblocking a User........................315 Resetting the PXE........................315 Restarting the PDU......................315 Resetting Active Energy Readings ..................316 Resetting to Factory Defaults ..................316 Network Troubleshooting......................317 Entering Diagnostic Mode ....................317...
  • Page 11 Step A. Determine User Accounts and Groups .................330 Step B. Configure User Groups on the AD Server ..............331 Step C. Configure LDAP Authentication on the PXE Device ............332 Step D. Configure User Groups on the PXE Device ..............334 Appendix E Integration Power IQ Configuration ......................338...
  • Page 12 Contents "To Assert" and Assertion Timeout..................352 "To De-assert" and Deassertion Hysteresis ..............354 Index...
  • Page 13 What's New in the PXE User Guide The following sections have changed or information has been added to the PXE Online Help based on enhancements and changes to the equipment and/or user documentation. (on page 9) Checking the Branch Circuit Rating...
  • Page 14 Chapter 1: What's New in the PXE User Guide (on page 88) Changing the Default Policy (on page 89) Creating Firewall Rules (on page 96) Enabling and Editing the Security Banner (on page 97) Enabling the Feature (on page 98)
  • Page 15 What's New in the PXE User Guide (on page 171) Unmanaging Environmental Sensors or Actuators (on page 172) Disabling the Automatic Management Function (on page 172) Controlling Actuators (on page 175) Copying the PXE Configuration (on page 176) Backup and Restore of PXE Device Settings...

  • Page 17: Chapter 1 Introduction

    Product Models..................1 Package Contents ..................1 Product Models The PXE comes in several models that are built to stock and can be obtained almost immediately. Raritan also offers custom models that are built to order and can only be obtained on request.

  • Page 18: Chapter 2 Rack-Mounting The Pdu

    Rack-Mounting the PDU Chapter 2 This chapter describes how to rack mount a PXE device. In This Chapter Rackmount Safety Guidelines ..............2 Circuit Breaker Orientation Limitation............2 Mounting 1U Models Using L-Brackets and Buttons.........3 Mounting Zero U Models Using Two Rear Buttons........4 Mounting Zero U Models Using L-Brackets and Buttons ......6...

  • Page 19: Mounting 1U Models Using L-Brackets And Buttons

    Chapter 2: Rack-Mounting the PDU Mounting 1U Models Using L-Brackets and Buttons This section describes how to mount a 1U PXE device using L-brackets and two buttons. To mount 1U models using L-brackets and two buttons: 1. Align the two edge slots of the L-bracket with the two screw holes on the top of the PXE device.

  • Page 20: Mounting Zero U Models Using Two Rear Buttons

    Chapter 2: Rack-Mounting the PDU  Mount the device by screwing a mounting button in the back center of each L-bracket and then having both buttons engage the mounting holes in the rack. The recommended torque for the button is 1.96 N·m (20 kgf·cm). Mounting Zero U Models Using Two Rear Buttons The following describes how to mount a PDU using two buttons only.
  • Page 21 5. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously. 6. Press the PXE device forward, pushing the mounting buttons through the mounting holes, then letting the device drop slightly. This secures the PXE device in place and completes the installation.

  • Page 22: Mounting Zero U Models Using L-Brackets And Buttons

    To mount Zero U models using L-brackets and two buttons: 1. Align the two central holes of the L-bracket with the two screw holes on the top of the PXE device. 2. Screw the L-bracket to the device and ensure the bracket is fastened securely.
  • Page 23 Chapter 2: Rack-Mounting the PDU 4. After both L-brackets are installed on the device, you can choose either of the following ways to mount the device in the rack.  Using rack screws, fasten the device to the rack through two identical holes near the edge of each L-bracket.

  • Page 24: Chapter 3 Installation And Configuration

    Raritan's Technical Support Department for assistance. 4. Verify that all circuit breakers on the PXE device are set to ON. If not, turn them ON. Or make sure that all fuses are inserted and seated properly. If there are any fuse covers, ensure that they are closed.

  • Page 25: Filling Out The Equipment Setup Worksheet

    Connecting the PDU to a Power Source 1. Verify that all circuit breakers on the PXE device are set to ON. If not, turn them ON. Or make sure that all fuses are inserted and seated properly. If there are any fuse covers, ensure that they are closed.

  • Page 26: Installing The Usb-To-Serial Driver (Optional)

    Automatic driver installation is highly recommended. ® Automatic driver installation in Windows 1. Make sure the PXE is NOT connected to the computer via a USB cable. 2. Run dominion-serial-setup-2.0.exe on the computer and follow online instructions to install the driver.

  • Page 27: Connecting The Pxe To A Computer

    Chapter 3: Installation and Configuration 4. Wait until the installation is complete. Note: If the PXE enters the disaster recovery mode when the USB serial driver is not installed yet, it may be shown as a 'GPS camera' in the Device Manager on the computer connected to it.

  • Page 28: Connecting The Pxe To Your Network

    See this diagram for the ETHERNET port location. Initial Network Configuration via CLI After the PXE is connected to your network, you must provide it with an IP address and some additional networking information. This section describes the initial configuration via the USB connection.
  • Page 29 3. In the communications program, press Enter to send a carriage return to the PXE. 4. The PXE prompts you to log in. Both user name and password are case sensitive. a. At the Username prompt, type admin and press Enter.
  • Page 30 Chapter 3: Installation and Configuration To set Use this command IP address network ip returned by dnsResolverPreference the DNS <resolver> server <resolver> = preferV4 or preferV6 d. After enabling the IPv4 or IPv6 protocol in the earlier step, configure the IPv4 or IPv6 network parameters. To set Use this command IPv4...
  • Page 31 Chapter 3: Installation and Configuration  For the static IP configuration, configure these parameters. To set Use this command Static IPv4 or network <version> ipAddress <ip IPv6 address address> <ip address> = static IP address IPv4 subnet network ipv4 subnetMask mask <netmask>...

  • Page 32: Installing Cable Retention Clips On Outlets (Optional)

    Chapter 3: Installation and Configuration 11. If all are correct, type exit to log out of the PXE. If any are incorrect, repeat Steps 7 to 10 to change network settings. The IP address configured may take seconds to take effect.
  • Page 33 Chapter 3: Installation and Configuration 3. Plug the power cord into the outlet, and press the clip toward the power cord until it holds the cord firmly. The clip's central part holding the plug should face downwards toward the ground, like an inverted "U".

  • Page 34: Chapter 4 Connecting Environmental Sensor Packages (Optional)

    SENSOR port on the PXE. 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 35: Using An Optional Sensor Hub

    DX to the hub. To connect DPX sensor packages via an optional sensor hub: 1. Connect a Raritan sensor hub to the PXE device. a. Plug one end of the Raritan-provided phone cable (4-wire, 6-pin, RJ-12) into the IN port (Port 1) of the hub.
  • Page 36 Chapter 4: Connecting Environmental Sensor Packages (Optional) Raritan sensor hubs CANNOT be cascaded so at most a sensor hub can be connected to each SENSOR port on the PXE device. This diagram illustrates a configuration with a sensor hub connected.

  • Page 37: Using A Raritan Y Cable

    Chapter 4: Connecting Environmental Sensor Packages (Optional) Using a Raritan Y cable A Raritan Y cable doubles the number of connected environmental sensors per SENSOR port. It supports DPX sensor packages only. Do NOT connect DPX2 or DX. To connect DPX sensor packages via a Raritan Y cable: 1.

  • Page 38: Supported Maximum Dpx Sensor Distances

    3. Repeat the above steps if there are additional SENSOR ports on your PXE. Supported Maximum DPX Sensor Distances A maximum connection distance of 98' (30 m) is supported when connecting the following DPX packages to the PXE. This maximum includes the 16' (5 m) sensor cable length:  DPX-CC2-TR ...

  • Page 39: Dpx2 Sensor Packages

    RJ-12 connector and several (one to three) head connectors. You need to manually connect DPX2 sensors to the sensor cable. For more information on DPX2, download the Environmental Sensors Guide from Raritan website's PX2 Support Files page (https://www.raritan.com/support/product/px2/px2-support-files). Number...
  • Page 40 Therefore, always occupy all head connectors prior to the final sensor with a DPX2 sensor. To connect a DPX2 sensor package to the PXE: 1. Connect a DPX2 sensor to the first head connector of the DPX2 sensor cable.

  • Page 41: Dx Sensor Packages

    32nd one. For example, if you cascade 12 DX packages, and each package contains 3 functions (a function is a sensor or actuator), because the total 36 (12*3=36) exceeds 32 by 4, the PXE ignores the last 4 functions.
  • Page 42 Plug the other end into either RJ-45 port on an additional DX package. Repeat the same steps to cascade more DX packages. 3. Connect the first DX sensor package to the PXE.  Plug the adapter cable's RJ-12 connector into the RJ-12...

  • Page 43: Chapter 5 Using The Pdu

    How the overcurrent protector (a circuit breaker) works In This Chapter Panel Components ................. 27 Circuit Breakers..................32 Panel Components The PXE comes in Zero U, 1U, and 2U sizes. All types of models come with the following components on the outer panels.  Power cord ...

  • Page 44: Connection Ports

    Port Used for... USB-B Establishing a USB connection between a computer and the PXE device. This port can be used for disaster recovery of the PXE device. Contact Raritan Technical Support for instructions. RS-485 Reserved for a future release. *SENSOR Connection to Raritan's environmental sensors.

  • Page 45: Led Display

    Up and Down buttons  Five LEDs for measurement units Note: When a PXE device powers up, it proceeds with the power-on self test and software loading for a few moments. When the software has completed loading, the LED display illuminates.
  • Page 46 One of the measurement unit LEDs will be lit to indicate the unit for the value currently shown in the three-digit row. The Sensor LED is lit only when PXE detects the physical connection of any environmental sensor. The five LEDs look similar to this diagram but may slightly vary according to the model you purchased.
  • Page 47 Chapter 5: Using the PDU Manual Mode You can press the Up or Down button to enter the Manual Mode so that a particular line or the inlet's active power is selected to show specific readings. To operate the LED display: 1.

  • Page 48: Reset Button

    The reset button is located inside the small hole near the display panel on the PDU. Pressing this reset button restarts the PXE device's software without any loss of power to outlets. This operation also power cycles the LED display, causing the LED display to go blank and then return to normal.

  • Page 49: Resetting The Handle-Type Circuit Breaker

    Chapter 5: Using the PDU 2. Examine your PXE device 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.
  • Page 50 Chapter 5: Using the PDU 4. Pull up the operating handle until the colorful rectangle or triangle turns RED.

  • Page 51: Chapter 6 Using The Web Interface

    Using the Web Interface Chapter 6 This chapter explains how to use the web interface to administer a PXE. In This Chapter Supported Web Browsers................35 Logging in to the Web Interface ..............36 Logout......................39 Introduction to the Web Interface ............40 Viewing the Dashboard ................51 Device Management................53...

  • Page 52: Logging In To The Web Interface

    To log in to the web interface, you must enter a user name and password. The first time you log in to the PXE, use the default user name (admin) and password (raritan). You are then prompted to change the password for security purposes.
  • Page 53 Note: If you do not accept the security agreement, you cannot log in successfully. 5. Click Login or press Enter. The PXE page opens. Note: Depending on your hardware configuration, elements shown on the web interface may appear slightly different from this image.

  • Page 54: Changing Your Password

    If you are the administrator (admin), the PXE web interface automatically prompts you to change the password if this is your first time to log in to the PXE. If you have the Administrator Privileges, you can change other users' passwords, as well. See (on page 81).

  • Page 55: Logout

    Chapter 6: Using the Web Interface Logout After finishing your tasks with the PXE, you should log out to prevent others from accessing the web interface. To log out of the web interface: 1. Do one of these:  Click "logout" on the top-right corner of the web interface.

  • Page 56: Introduction To The Web Interface

    Chapter 6: Using the Web Interface Introduction to the Web Interface The web interface provides two panes, a menu bar, a status bar, an Add Page icon, and a logout button throughout every page. Number Web interface element Menus PX Explorer pane Setup button* Status bar Add Page icon...

  • Page 57: Menus

    PX Explorer Pane The hierarchical tree to the left displays the PXE device you are accessing as well as all physical components embedded on or connected to this product, such as inlets, outlets, and environmental sensors.
  • Page 58 (on page 45). Expanding the Tree The icons representing all components implemented on or connected to the PXE device are expanded by default. If they are hidden, you may expand the tree manually to show all component icons. To expand the tree: 1.

  • Page 59: Setup Button

    Chapter 6: Using the Web Interface Collapsing the Tree You can collapse the whole tree structure or a specific component group to hide all or partial tree items. To collapse the whole tree:  Click the black, gradient arrow prior to the PDU folder icon, or double-click the folder.
  • Page 60 Chapter 6: Using the Web Interface This is the name assigned to the PXE device. The default is "my PX." (on page 55). Naming the PDU 2. IP address: The numbers enclosed in parentheses is the IP address assigned to the PXE device.

  • Page 61: Add Page Icon

    Chapter 6: Using the Web Interface Add Page Icon The Add Page icon , located on the top of the data pane, lets you open data pages of multiple tree items without overriding any opened page. To open new data pages: 1.

  • Page 62: More Information

    Chapter 6: Using the Web Interface 2. When the mouse pointer turns into a two-way arrow, drag the border horizontally to widen or shrink the pane. More Information This section explains additional web interface elements or operations that are useful. Warning Icon If the value you entered in a specific field is invalid, a red warning icon appears to the right and the field in question is surrounded by a red...
  • Page 63 Chapter 6: Using the Web Interface Color State The meaning of the red color varies depending on the sensor type:  For a numeric sensor, this color indicates the reading drops below the lower critical threshold or rises above the upper critical threshold. ...
  • Page 64 Chapter 6: Using the Web Interface Changing the View of a List Some dialogs and data pages contain a list or table, such as the Manage Users dialog shown below. You may change the number of displayed columns or re-sort the list for better viewing the data. Note the column or sorting changes are not saved when quitting the dialog or data page.
  • Page 65 Chapter 6: Using the Web Interface 2. When the mouse pointer turns to a two-way arrow, drag the border horizontally to widen or shrink the column. Changing the Sorting By default, a list or table is sorted against the first column in the ascending order.
  • Page 66 Browser-Defined Shortcut Menu A shortcut menu, which is built in the web browser, may appear when right-clicking anywhere in the PXE web interface. The shortcut menu functions are defined by the browser. For example, the Back command on the Internet Explorer (IE) shortcut menu works ®...

  • Page 67: Viewing The Dashboard

    Viewing the Dashboard When you log in to the web interface, the Dashboard page is displayed by default. This page provides an overview of the PXE device's status. The page is divided into various sections according to the component type, such as inlet and peripheral devices.

  • Page 68: Alarms List

    Chapter 6: Using the Web Interface For the background color meanings in this section, see The Yellow- or (on page 46). Red-Highlighted Sensors Alarms List You can create event rules that request users to acknowledge certain alerts, and resend alert notifications if the acknowledgment action is not taken yet.

  • Page 69: Device Management

    (on page 48). Device Management Using the web interface, you can retrieve basic hardware and software information, give the PXE a new device name, set the system date and time, and modify network settings that were entered during the initial configuration process.

  • Page 70: Displaying Pdu Information

    Chapter 6: Using the Web Interface Displaying PDU Information To display information specific to the PXE device that you are using, such as inlet or outlet types, trigger the Device Information dialog. To display the PDU-specific information: 1. Choose Maintenance > Device Information. The Device Information dialog appears.

  • Page 71: Naming The Pdu

    Tip: The firmware version is also available by clicking the PDU folder in the PX Explorer pane. Naming the PDU The default name for PXE is my PX. You may give it a unique device name. To change the device name: 1.
  • Page 72  Full: Data is transmitted in both directions simultaneously.  Half: Data is transmitted in one direction (to or from the PXE device) at a time. 6. Click OK. Tip: You can check the LAN status in the Current State field, including the speed and duplex mode.
  • Page 73 Chapter 6: Using the Web Interface Selecting the Internet Protocol The PXE device supports two types of Internet protocols -- IPv4 and IPv6. You can enable either or both protocols. After enabling the desired Internet protocol(s), all but not limited to the following protocols will be compliant with the enabled Internet protocol(s): ...
  • Page 74 If your local network contains two subnets and IP forwarding has been enabled, you can click Append to add static routes so that your PXE can communicate with the other subnet. Each static route requires:  Destination: IP address of the other subnet and subnet mask using the format "IP address/subnet mask."...
  • Page 75 Chapter 6: Using the Web Interface Note: The PXE supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the PXE only uses the primary IPv4 and IPv6 DNS servers. Modifying IPv6 Settings You must enable the IPv6 protocol before you can modify the IPv6 network settings.
  • Page 76 (on page 61) for illustrations. Static Route Examples 4. Click OK. Note: The PXE supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the PXE only uses the primary IPv4 and IPv6 DNS servers.
  • Page 77 (NIC) have been installed in one network server, leading to two available subnets, and IP forwarding has been enabled. All of the NICs and PXE devices in the examples use static IP addresses.
  • Page 78 Chapter 6: Using the Web Interface In this example, NIC-2 (192.168.100.88) is the next hop router for your PXE to communicate with any device in the other subnet 192.168.200.0. In the IPv4 'Append new Route' dialog, you should specify: ...

  • Page 79: Modifying Network Service Settings

    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 PXE may fail to connect to the given host. Therefore, DNS server settings are important for external authentication.
  • Page 80 Changing HTTP(S) Settings HTTPS uses Secure Sockets Layer (SSL) technology to encrypt all traffic to and from the PXE device so it is a more secure protocol than HTTP. By default, any access to the PXE device via HTTP is automatically redirected to HTTPS.
  • Page 81 Chapter 6: Using the Web Interface 3. To enable the SSH application, select the Enable SSH Access checkbox. To disable it, deselect the checkbox. 4. To select a different authentication method, select one of the checkboxes. Password authentication only: Enables the password-based login ...
  • Page 82 3. Select the "enable" checkbox in the "SNMP v3" field to enable communication with an SNMP manager using SNMP v3 protocol. Tip: You can permit or disallow a user to access the PXE via the SNMP v3 protocol. See Configuring Users for Encrypted SNMP...
  • Page 83 - the name assigned to the system c. sysLocation - the location of the system 5. Select the MIB to be downloaded. The SNMP MIB for your PXE is used by the SNMP manager. Important: You must download the SNMP MIB for your PXE to use with your SNMP manager.
  • Page 84 .local host name, that is, <preferred_host_name>.local, where <preferred_host_name> is the preferred host name you have specified for PXE. The IPv4 host name is the first priority. If an IPv4 host name is not available, then use the IPv6 host name.

  • Page 85: Setting The Date And Time

    Setting the Date and Time Set the internal clock on the PXE device manually, or link to a Network Time Protocol (NTP) server and let it set the date and time for the PXE. To set the date and time: 1.
  • Page 86 First and Second Time Server will be overridden. 5. Click OK. The PXE follows the NTP server sanity check per the IETF RFC. If your PXE has problems synchronizing with a Windows NTP server, see (on page 72).
  • Page 87 Chapter 6: Using the Web Interface  Press Ctrl+Up arrow or Ctrl+Down arrow to switch between years. Click , which is adjacent to the year, to show a list of years  and months. Select the desired year from the list to the right and click OK.
  • Page 88 Chapter 6: Using the Web Interface Windows NTP Server Synchronization Solution The NTP client on the PXE follows the NTP RFC so the PXE rejects any NTP servers whose root dispersion is more than one second. An NTP server with a dispersion of more than one second is considered an inaccurate NTP server by the PXE.

  • Page 89: Setting Default Measurement Units

    3. Click OK. Specifying the Device Altitude You must specify the PXE device's altitude above sea level if a Raritan differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor. See Altitude (on page 347).

  • Page 90: Setting Data Logging

    Note that the outlet-level measurement data is NOT available for Raritan models described in this online help. Note: The PXE device's SNMP agent must be enabled for this feature to work. See Enabling SNMP (on page 185) for more details.

  • Page 91: Configuring Smtp Settings

    Chapter 6: Using the Web Interface Important: Although it is possible to selectively enable/disable logging for individual sensors on the PXE in Step 4, it is NOT recommended and this capability may be removed in the future. Configuring SMTP Settings The PXE can be configured to send alerts or event messages to a specific administrator by email.

  • Page 92: Setting The Energywise Configuration

    EnergyWise energy management architecture is implemented ® in your place, you can enable the Cisco EnergyWise endpoint implemented on the PXE device so that this device becomes part of the Cisco EnergyWise domain. The Cisco EnergyWise feature implemented on the PXE is disabled by default.

  • Page 93: Rebooting The Pxe Device

    Resetting All Active Energy Readings An active energy reading is a value of total accumulated energy, which is never reset, even if the power fails or the PXE is reset. However, you can manually reset this reading to restart the energy accumulation process.

  • Page 94: Internal Beeper State

    PDU page always shows "Off." User Management The PXE is shipped with one built-in user profile: admin, which is used for initial login and configuration. This profile has full permissions, and should be reserved for the system administrator. It cannot be deleted and its permissions are not user-configurable except for the SNMP v3 permission.
  • Page 95 It is case sensitive. 4. Select the Enabled checkbox. This is required so the user can log in to the PXE device. 5. Select the "Force password change on next login" checkbox if you prefer a password change by the user when the user logs in for the first time after this checkbox is enabled.
  • Page 96 Chapter 6: Using the Web Interface Field Description Authentication Type the authentication pass phrase in this field if Pass Phrase the "Use Password as Authentication Pass Phrase" checkbox is disabled. The pass phrase must consist of 8 to 32 ASCII printable characters.

  • Page 97: Modifying A User Profile

    Chapter 6: Using the Web Interface 9. Select one or multiple roles by selecting corresponding checkboxes.  The Admin role provides full permissions.  The Operator role provides limited permissions for frequently-used functions. See (on page 83) Setting Up Roles for the scope of permissions.

  • Page 98: Deleting A User Profile

    Chapter 6: Using the Web Interface 4. Make all necessary changes to the information shown. To change the password, type a new password in the Password and Confirm Password fields. If the password field is left blank, the password is not changed. 5.

  • Page 99: Setting Up Your Preferred Measurement Units

    Chapter 6: Using the Web Interface Setting Up Your Preferred Measurement Units The measurement units used in your PXE user interfaces can be changed according to your own preferences regardless of the permissions you have. Tip: Preferences can also be changed by administrators for specific users from the Preferences tab of the Manage Users dialog.

  • Page 100: Creating A Role

    Chapter 6: Using the Web Interface - Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration - Change Own Password The Operator role is assigned to a newly created user profile by default. See (on page 78). Creating a User Profile Creating a Role Create a new role when you need a new combination of permissions.
  • Page 101 Chapter 6: Using the Web Interface 3. Click Edit or double-click the role. The Edit Role 'XXX' dialog appears, where XXX is the role name. Tip: You can also access the Edit Role 'XXX' dialog by clicking the Edit Role button in the Edit User 'XXX' dialog. 4.

  • Page 102: Deleting A Role

    You may re-sort the list for better viewing the data. See Changing the (on page 48). View of a List Forcing HTTPS Encryption You can force all accesses to the PXE via HTTP to be redirected to HTTPS. See (on page 64). Changing HTTP(S) Settings Access Security Control The PXE provides tools to control access.

  • Page 103: Configuring The Firewall

    Chapter 6: Using the Web Interface Configuring the Firewall The PXE has a firewall that you can configure to prevent specific IP addresses and ranges of IP addresses from accessing the PXE device or to prevent them from receiving any data from the PXE.
  • Page 104 After enabling the firewall, the default policy is to accept traffic from/to all IP addresses. This means only IP addresses discarded by a specific rule will NOT be permitted to access the PXE or receive any data from the PXE.
  • Page 105 Creating Firewall Rules Firewall rules determine whether to accept or discard traffic to/from the PXE, based on the IP address of the host sending or receiving the traffic. When creating firewall rules, keep these principles in mind:  Rule order is important.
  • Page 106 Chapter 6: Using the Web Interface 4. To set rules for inbound traffic, go to the Inbound Rules section. To set rules for outbound traffic, go to the Outbound Rules section. 5. Create specific rules. See the table for different operations. Action Procedure Add a rule to the end of...
  • Page 107 Chapter 6: Using the Web Interface 6. When finished, the rules appear in the Configure IP Access Control Settings dialog. 7. Click OK. The rules are applied. Editing Firewall Rules When an existing firewall rule requires updates of IP address range and/or policy, modify them accordingly.
  • Page 108 Chapter 6: Using the Web Interface 2. To modify the IPv4 firewall rules, click the IPv4 tab. To modify the IPv6 firewall rules, click the IPv6 tab. 3. Ensure the Enable IPv4 Access Control checkbox is selected on the IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.

  • Page 109: Setting Up User Login Controls

    You can set up login controls to make it more difficult for hackers to access the PXE and the devices connected to it. You can arrange to lock persons out after a specified number of failed logins, limit the number of persons who log in using the same user name at the same time, and force users to create strong passwords.
  • Page 110 "Prevent concurrent login with same username" checkbox. 4. To adjust how long users can remain idle before they are forcibly logged out by the PXE, select a time option in the Idle Timeout Period field. The default is 10 minutes. ...
  • Page 111 = Required At least one special character = Required Number of restricted passwords in history Note: The maximum password length accepted by the PXE is 64 characters. 3. Make necessary changes to the default settings. 4. Click OK. Enabling Password Aging Password Aging determines whether users are required to change passwords at regular intervals.
  • Page 112 9 days. 4. Click OK. Enabling and Editing the Security Banner Use the PXE restricted service agreement (security banner) if you want to require users to read and accept a security agreement when they log in to the PXE.

  • Page 113: Setting Up Role-Based Access Control Rules

    Chapter 6: Using the Web Interface If the Restricted Service Agreement feature is enabled, the Restricted Service Agreement is displayed when any user logs in to the PXE. Do either of the following, or you cannot successfully log in to the PXE: ...
  • Page 114 Chapter 6: Using the Web Interface Changing the Default Policy The default policy is to accept all traffic from all IP addresses regardless of the role applied to the user. To change the default policy: 1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
  • Page 115 Chapter 6: Using the Web Interface 3. Ensure the "Enable Role Based Access Control for IPv4" checkbox is selected on the IPv4 tab, or the "Enable Role Based Access Control for IPv6" checkbox is selected on the IPv6 tab. 4. Create specific rules: Action Do this...
  • Page 116 Chapter 6: Using the Web Interface Action Do this...  Click OK. The system inserts the rule and automatically renumbers the following rules. 5. Click OK. Editing Role-Based Access Control Rules You can modify existing rules when these rules do not meet your needs. To modify a role-based access control rule: 1.

  • Page 117: Setting Up An Ssl Certificate

    Having an X.509 digital certificate ensures that both parties in an SSL connection are who they say they are. To obtain a certificate for the PXE, create a Certificate Signing Request (CSR) and submit it to a certificate authority (CA). After the CA processes the information in the CSR, it provides you with an SSL certificate, which you must install on the PXE device.

  • Page 118: Certificate Signing Request

    Certificate Signing Request When appropriate certificate and key files for the PXE are NOT available, one of the alternatives is to create a CSR and private key on the PXE device, and send the CSR to a CA for signing the certificate.
  • Page 119 3. In the Certificate File field, click Browse to select the certificate file provided by the CA. 4. Click Upload. The certificate is installed on the PXE device. Tip: To verify whether the certificate has been installed successfully, click the Active SSL Certificate tab.

  • Page 120: Creating A Self-Signed Certificate

    Chapter 6: Using the Web Interface Creating a Self-Signed Certificate When appropriate certificate and key files for the PXE device are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate. To create and install a self-signed certificate: 1.

  • Page 121: Installing Existing Key And Certificate Files

    4. In the Key File field, click Browse to select the private key file. 5. In the Certificate File field, click Browse to select the certificate file. 6. Click Upload. The selected files are installed on the PXE device. Tip: To verify whether the certificate has been installed successfully, click the Active SSL Certificate tab.

  • Page 122: Downloading Key And Certificate Files

    2. The Active SSL Certificate tab should open. If not, click it. 3. Click Download Key to download the private key file installed on the PXE device. You are prompted to open or save the file. Click Save to save it onto your computer.

  • Page 123: Gathering The External Authentication Information

    Gathering the LDAP Information It requires knowledge of your LDAP server and directory settings to configure the PXE for LDAP authentication. If you are not familiar with the settings, consult your LDAP administrator for help. To configure LDAP authentication, you need to check: ...

  • Page 124: Adding Authentication Servers

    UDP accounting port used by the RADIUS server Adding Authentication Servers Add all external authentication servers that you want to use to the PXE. Later you can use the sequence of the server list to control the authentication servers' access priority.
  • Page 125 9. Enable verification of LDAP Server Certificate - Select this checkbox if you would like the PXE to verify whether the selected LDAP server certificate is valid. 10. CA Certificate - Consult your authentication server administrator to get the CA certificate file for the LDAP/LDAPS server.
  • Page 126 LDAP/LDAPS server whose settings you want to copy. 4. Click OK. Note: If the PXE clock and the LDAP server clock are out of sync, the certificates are considered expired and users are unable to authenticate using LDAP. To ensure proper synchronization, administrators should configure the PXE and the LDAP server to use the same NTP server.
  • Page 127 RADIUS server. 10. To verify if the authentication configuration is set correctly, you may click Test Connection to check whether the PXE can connect to the remote authentication server successfully. Tip: You can also do this by using the Test Connection button in the Authentication Settings dialog.

  • Page 128: Sorting The Access Order

    The PXE first tries to access the top server in the list for authentication, then the next one if the access to the first one fails, and so on until the PXE device successfully connects to one of the listed servers.

  • Page 129: Deleting Authentication Server Settings

    5. Click OK. Disabling External Authentication When the remote authentication service is disabled, the PXE authenticates users against the local database stored on the PXE device. To disable the external authentication service: 1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears.

  • Page 130: Enabling External And Local Authentication Services

    4. Click OK. Outlet Management The PXE allows you to remotely customize the name of each outlet or check the receptacle type of each outlet through the web interface. Naming Outlets You can give each outlet a unique name up to 32 characters long to identify the equipment connected to it.

  • Page 131: Checking Outlet-Specific Data

    Chapter 6: Using the Web Interface 4. Type a name in the Outlet Name field. 5. Click OK. Checking Outlet-Specific Data To find out each outlet's name, label, and receptacle type, you can check the Outlets page or each individual outlet's page. Tip: More outlet information is available by choosing Maintenance >...

  • Page 132: Naming The Inlet

    The customized name is followed by the label in parentheses. Note: In this context, the label refers to the inlet number, such as I1. This function is especially useful if there are multiple inlets on your PXE device. To name the inlet: 1.

  • Page 133: Naming Overcurrent Protectors

    Only users with the 'Admin' role assigned can reset active energy readings. To reset active energy readings of one inlet: 1. If your PXE has multiple inlets, expand the Inlet folder in the PX Explorer pane to show all inlets . See (on page Expanding the Tree 42).

  • Page 134: Disabling An Inlet (For Multi-Inlet Pdus)

    (on page 77). Disabling an Inlet (for Multi-Inlet PDUs) The PXE, if it has more than one inlet, enables all inlets by default so that the PXE detects and displays all sensors' readings and states, and reports or shows warnings, events or alarm notifications associated with all inlets, outlets and overcurrent protectors (if available).

  • Page 135: Setting Power Thresholds

    Then click Yes to confirm this operation or No to abort it. Setting Power Thresholds Setting and enabling the thresholds causes the PXE to generate alert notifications when it detects that any component's power state crosses the thresholds. See...
  • Page 136 Chapter 6: Using the Web Interface 5. Configure the Lower Critical, Lower Warning, Upper Warning and Upper Critical thresholds respectively.  To enable any threshold, select the corresponding checkbox. To disable a threshold, deselect the checkbox.  After any threshold is enabled, type an appropriate numeric value in the accompanying text box.

  • Page 137: Event Rules And Actions

    An event rule defines what the PXE does in certain situations and is composed of two parts:  Event: This is the situation where the PXE or part of it meets a certain condition. For example, the inlet's voltage exceeds the warning threshold.

  • Page 138: Creating An Event Rule

    IP addresses after the selected event occurs.  System Tamper Alarm: This action causes the PXE to show the alarm for the DX-PIR tamper sensor in the Alarms section of the Dashboard until a person acknowledges it. By default, this action has been assigned to the built-in tamper detection event rules.
  • Page 139 See (on page 132). Switch Peripheral Actuator Note: The PXE does NOT support the connection of an external beeper, modem, or webcam so do NOT select unsupported actions, including "External Beeper," "Send Snapshots via SMTP," "Send SMS Message"...
  • Page 140 Chapter 6: Using the Web Interface Action Group You can create an action group that performs up to 32 actions. After creating such an action group, you can easily assign this set of actions to an event rule rather than selecting all needed actions one by one per rule.
  • Page 141 If the Alarm action has been included in a specific event rule and no one acknowledges that alert after it occurs, the PXE resends or regenerates an alert notification regularly until the alert is acknowledged or it reaches the maximum number of alert notifications.
  • Page 142 In the "Max. numbers" field, specify the maximum number of times the alert notification is resent. Values range from 1 to infinite. 7. If needed, you can instruct the PXE to send the acknowledgment notification after the alarm is acknowledged in the Acknowledgment Notifications list box. (Optional) a.
  • Page 143 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 PXE placeholders. The placeholders represent information is pulled from the PXE and inserted into the message.
  • Page 144 Chapter 6: Using the Web Interface Click the Information icon to open the Event Context Information dialog, which contains a list of placeholders and their definitions. See (on page 144) for more Email and SMS Message Placeholders details. 9. Click OK. Send an SNMP Notification This option sends an SNMP notification to one or multiple SNMP destinations.
  • Page 145 Chapter 6: Using the Web Interface 5. In the Community fields, enter the SNMP community string to access the device(s). The community is the group representing the PXE and all SNMP management stations. Tip: An SNMP v2c notification action only permits entering a maximum of three SNMP destinations.
  • Page 146 Chapter 6: Using the Web Interface Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" Select this if authorization is required but no privacy protocols are required.  Select the authentication protocol - MD5 or ...
  • Page 147 Chapter 6: Using the Web Interface Send Sensor Report You may set the PXE so that it automatically reports the latest readings or states of one or multiple sensors by sending a message or email or simply recording the report in a log. These sensors can be either internal or environmental sensors as listed below.
  • Page 148 Email and SMS Message Placeholders (on page 144). Switch Peripheral Actuator If you have any actuator connected to the PXE, you can set up the PXE so it automatically turns on or off the system controlled by this actuator when a specific event occurs.
  • Page 149 After required actions are available, you can create event rules to determine what actions are taken to respond to specific events. By default, the PXE provides four built-in event rules - System Event Log Rule, System SNMP Notification Rule, System Tamper Detection Alarmed, and System Tamper Detection Unavailable.
  • Page 150 This means the status of the described event transits from TRUE to FALSE.  Both: The PXE takes the action both when the event occurs (asserts) and when the event condition disappears (deasserts). Discrete (on/off) Available radio buttons include "Alarmed,"...
  • Page 151 Available radio buttons include "Link state is link state up," "Link state is down" and "Both."  Link state is up: The PXE takes the action only when the network link state changes from down to up.  Link state is down: The PXE takes the action only when the network link state changes from up to down.
  • Page 152  Both: PXE takes the action both when the selected device is physically connected to it and when it is disconnected. Note: The PXE does NOT support events related to asset management, modem, webcam, USB-cascading and Schroff LHX/SHX devices. 7. In the Actions field, select the desired action from the "Available actions"...
  • Page 153 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 PXE report the reading or state of a specific environmental sensor regularly by scheduling the "Send Sensor Report"...
  • Page 154 Chapter 6: Using the Web Interface 6. Select the desired time frequency from the Execution Time field and then specify the time interval or a specific date and time in the Time field. Time options Frequency settings The frequency in minutes ranges from every minute, every 5 Minutes minutes, every 10 minutes and so on until every 30 minutes.
  • Page 155 9. Click OK. Default Log Messages Following are default log messages triggered and emailed to specified recipients when PXE events occur (are TRUE) or, in some cases, do not occur (are FALSE). See (on page 127) for information Send EMail configuring email messages to be sent when specified events occur.
  • Page 156 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Card Reader Management > Card Reader with id Card Reader attached '[CARDREADERID]' disconnected. Card Reader Management > Card of type '[SMARTCARDTYPE]' Card Reader detached with ID '[SMARTCARDID]' inserted.
  • Page 157 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Device > Peripheral Device Firmware update for peripheral device Firmware Update [EXTSENSORSERIAL] from [OLDVERSION] to [VERSION] [SENSORSTATENAME]. Device >...
  • Page 158 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Peripheral Device Slot > * > Peripheral device Peripheral device Numeric Sensor > Below lower '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot critical threshold '[EXTSENSORSLOT]' asserted 'below...
  • Page 159 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* threshold asserted 'above upper warning'. warning'. Inlet > * > Pole > * > Sensor > * Sensor '[POLESENSOR]' on pole Sensor '[POLESENSOR]' on pole >...
  • Page 160 Webcam settings changed changed by user '[USERNAME]'. *Note: Not set for 'trigger' events. Note: The PXE does NOT support events related to asset management, modem, webcam, USB-cascading and Schroff LHX/SHX devices. Email and SMS Message Placeholders Following are placeholders that can be used in custom event email messages.
  • Page 161 Chapter 6: Using the Web Interface Placeholder Definition [ACTIVEINLET] The label of the newly activated inlet [AMSBLADESLOTPOSITION] The (horizontal) slot position, an action applies to [AMSLEDCOLOR] The RGB LED color [AMSLEDMODE] The LED indication mode [AMSLEDOPMODE] The LED operating mode [AMSNAME] The name of an asset strip [AMSNUMBER]...
  • Page 162 Chapter 6: Using the Web Interface Placeholder Definition [OCPSENSOR] The overcurrent protector sensor name [OCP] The overcurrent protector label [OLDVERSION] The firmware version the device is being upgraded from [OUTLETPOLE] The outlet power line identifier [OUTLETSENSOR] The outlet sensor name [OUTLET] The outlet label [PDUPOLESENSOR]...

  • Page 163: Sample Event Rules

    The firmware version the device is upgrading to Sample Event Rules Sample PDU-Level Event Rule In this example, we want the PXE to record the firmware upgrade failure in the internal log when it happens. The sample event rule looks like this: ...

  • Page 164: A Note About Infinite Loop

    Chapter 6: Using the Web Interface 5. Select "System SNMP Notification Action" to send SNMP notifications to respond to the specified event. Then the SNMP notifications are sent when:  Any numeric sensor's reading moves past any threshold into the warning or critical range.

  • Page 165: Modifying An Event Rule

    Chapter 6: Using the Web Interface Modifying an Event Rule You can change an event rule's event, action, trigger condition and other settings, if any. Exception: Events and actions selected in the built-in event rules are not changeable, including System Event Log Rule, System SNMP Notification Rule, System Tamper Detection Alarmed, and System Tamper Detection Unavailable.

  • Page 166: Modifying An Action

    Chapter 6: Using the Web Interface Note: If you do not click OK before quitting the current settings page, a message appears. Then click Yes to save the changes, Discard to abort or Cancel to return to the current settings page. 8.

  • Page 167: A Note About Untriggered Rules

    (on page 354). Hysteresis Managing Event Logging By default, the PXE captures certain system events and saves them in a local (internal) event log. Viewing the Local Event Log You can view up to 2,000 historical events that occurred to the PXE device in the local event log.

  • Page 168: Clearing Event Entries

    2. Click Clear Event Log. 3. Click Yes on the confirmation message. Viewing Connected Users You can see which users are connected to the PXE device and their status. If you have administrator privileges, you can terminate any user's connection to the PXE device.

  • Page 169: Monitoring Server Accessibility

    4. Click Close to quit the dialog. Monitoring Server Accessibility You can monitor whether specific IT devices are alive by having the PXE 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...

  • Page 170: Adding It Devices For Ping Monitoring

    Chapter 6: Using the Web Interface Adding IT Devices for Ping Monitoring You can have the PXE monitor the accessibility of any IT equipment, such as DB servers, remote authentication servers or any power distribution unit (PDU). The PXE supports monitoring a maximum of 8 devices.

  • Page 171: Editing Ping Monitoring Settings

    PXE can declare that the monitored device is reachable or unreachable. Editing Ping Monitoring Settings You can edit the ping monitoring settings for any IT device whenever needed.

  • Page 172: Checking Server Monitoring States

    The PXE can monitor the environmental conditions, such as temperature and humidity, where environmental sensors are placed. If an actuator is connected to the PXE, you can use it to control a system or mechanism. To add environmental sensors and actuators: 1.

  • Page 173: Identifying Environmental Sensors And Actuators

    Chapter 6: Using the Web Interface 2. Log in to the PXE web interface. The PXE should have detected the connected sensors and actuators, and display them in the web interface. 3. Identify each sensor and actuator. See Identifying Environmental (on page 157).
  • Page 174 A DPX2 or DX sensor 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 PXE. To identify each detected environmental sensor or actuator via serial numbers: 1.
  • Page 175 Chapter 6: Using the Web Interface Matching the Position Both DPX2 and DX sensor packages can be daisy chained. The PXE can indicate each sensor or actuator's position by showing the sensor port where the environmental sensor package is connected as well as its sequence in a sensor daisy chain.

  • Page 176: Managing Environmental Sensors Or Actuators

    4. There are two ways to manage a sensor or actuator:  To manage it by letting the PXE assign a number to it, select "Automatically assign a sensor number." This method does not release any managed sensors or actuators.
  • Page 177 The manual assignment method is unavailable if you selected multiple sensors or actuators in Step 2. 5. Click OK. The PXE starts to display the managed sensor or actuator's reading and state. 6. To manage additional ones, repeat Steps 2 to 5.

  • Page 178: Configuring Environmental Sensors Or Actuators

    Setup in the right pane. 4. If the selected environmental sensor is the Raritan contact closure sensor connected with a third-party detector/switch, select the appropriate sensor type in the Binary Sensor Subtype field.
  • Page 179 Chapter 6: Using the Web Interface 8. If the selected environmental sensor is a numeric sensor, its threshold settings are displayed in the dialog. See Sensor (on page 349) for detailed information. Threshold Settings There are two types of thresholds: sensor-specific thresholds and default thresholds.
  • Page 180 For Z when the Z coordinate format is set to Free-Form, any alphanumeric characters from 0 to 24 characters. Tip: To configure and retrieve these coordinate values over SNMP, see the PXE MIB. To configure and retrieve these values over the CLI, see Using the Command Line Interface (on page 191).
  • Page 181 Chapter 6: Using the Web Interface Changing Default Thresholds The default thresholds are the initial threshold values that automatically apply to numeric environmental sensors. These values are configured on a sensor type basis, which include:  Temperature sensors  Humidity sensors ...
  • Page 182 Chapter 6: Using the Web Interface Setting Thresholds for Multiple Sensors You can configure thresholds for multiple environmental sensors of the same type at a time. For example, if you want all temperature sensors to have identical upper and lower thresholds, follow the procedure below to set up all temperature sensors together.

  • Page 183: Viewing Sensor Or Actuator Data

    Chapter 6: Using the Web Interface Viewing Sensor or Actuator Data Readings and states of the environmental sensors or actuators will display in the web interface after the sensors and actuators are properly connected and managed. The Dashboard page shows the information of managed environmental sensors and actuators only, while the Peripheral Devices page shows the information of both managed and unmanaged ones.
  • Page 184 Chapter 6: Using the Web Interface  Position  Serial number  Type  Channel (for a sensor package with contact closure or dry contact channels)  Whether the sensor is an 'Actuator' or not (if yes, this icon appears in the Actuator column) ...
  • Page 185 The unavailable state means the connectivity or communications with the sensor is lost. The PXE pings all managed sensors at regular intervals in seconds. If it does not detect a particular sensor for three consecutive scans, the unavailable state is displayed for that sensor.
  • Page 186 If the normal state is set to Normally Open, the alarmed state means the contact closure switch is closed. For a Raritan's floor water sensor, the normal state must be set to Normally Closed, which means no water is detected. The alarmed state indicates that the presence of water is detected.

  • Page 187: Unmanaging Environmental Sensors Or Actuators

    When it is unnecessary to monitor a particular environmental factor, you can unmanage or release the corresponding environmental sensor so that the PXE device stops retrieving the sensor's reading and/or state. This procedure also applies if you want to unmanage an actuator.

  • Page 188: Disabling The Automatic Management Function

    The factory default is to enable the automatic management feature for environmental sensors and actuators. Therefore, when the total number of managed sensors and actuators has not reached 32 yet, the PXE automatically brings newly-connected environmental sensors and actuators under management after detecting the connection of these sensors and actuators.

  • Page 189: Bulk Configuration

    Bulk Configuration The Bulk Configuration feature lets you save the settings of a configured PXE device to your PC. You can use this configuration file to copy that configuration to other PXE devices of the same model and firmware version.

  • Page 190: Saving The Pxe Configuration

    Chapter 6: Using the Web Interface Saving the PXE Configuration A source device is an already configured PXE device that is used to create a configuration file containing the settings that can be shared between PXE devices. These settings include user and role configurations, thresholds, event rules, security settings, and so on.

  • Page 191: Copying The Pxe Configuration

    The target PXE device must be running the same firmware version as the source PXE device.  The target PXE device must be of the same model type as the source PXE device. Bulk configuration is permitted if the differences between the target and source device are only mechanical designs which are indicated in a model name's suffix as listed below.

  • Page 192: Backup And Restore Of Pxe Device Settings

    To back up or restore PXE device settings, you should perform the Backup/Restore feature. All PXE information is captured in the XML backup file except for the device logs and SSL certificate. Note: To perform the bulk configuration among multiple PXE devices, perform the Bulk Configuration feature instead.

  • Page 193: Network Diagnostics

    Chapter 6: Using the Web Interface Network Diagnostics The PXE provides the following tools in the web interface for diagnosing potential networking issues.  Ping  Trace Route  List TCP Connections Tip: These network diagnostic tools are also available through CLI. See Network Troubleshooting (on page 317).

  • Page 194: Listing Tcp Connections

    Important: This function is for use by Raritan Field Engineers or when you are directed by Raritan Technical Support. You can download the diagnostic file from the PXE device to a client machine. The file is compressed into a .tgz file and should be sent to Raritan Technical Support for interpretation.

  • Page 195: Updating The Pxe Firmware

    (on page 180) Firmware Update via SCP Firmware Update via Web Interface After downloading the latest firmware, log in to the PXE web interface to upgrade the firmware. To update the firmware using the web interface: 1. Choose Maintenance > Update Firmware. The Update Firmware dialog appears.
  • Page 196 7. When the update is complete, a message appears, indicating the update is successful. 8. The PXE resets, and the Login page re-appears. You can now log in and resume your operation. Note 1: The other logged-in users are also logged out when the firmware update is complete.

  • Page 197: Viewing Firmware Update History

    48 outlets updated). Take the above factors into account when estimating the PDU's firmware upgrade time. The time indicated in this note is for PXE web-interface-based upgrades. Upgrades through other management systems, such as Raritan's Power IQ, may take additional time beyond the control of the PDU itself. This note does not address the upgrades using other management systems.

  • Page 198: Full Disaster Recovery

    4. Click Close to quit the dialog. Full Disaster Recovery If the firmware upgrade fails, causing the PXE device to stop working, you can recover it by using a special utility rather than returning the device to Raritan. Contact Raritan Technical Support for the recovery utility, which works in Windows XP/Vista/7 and Linux.

  • Page 199: Browsing Through The Online Help

    Chapter 6: Using the Web Interface Browsing through the Online Help The PXE 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. Consult your browser help for information on enabling these features.
  • Page 200 Chapter 6: Using the Web Interface 10. To print the currently selected topic, click the "Print this page" icon...

  • Page 201: Chapter 7 Using Snmp

    Using SNMP Chapter 7 This SNMP section helps you set up the PXE for use with an SNMP manager. The PXE 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 202: Configuring Users For Encrypted Snmp V3

    3. Select the "enable" checkbox in the "SNMP v3" field to enable communication with an SNMP manager using SNMP v3 protocol. Tip: You can permit or disallow a user to access the PXE via the SNMP v3 protocol. See Configuring Users for Encrypted SNMP (on page 186).

  • Page 203: Configuring Snmp Notifications

    5. Click OK. The user is now set up for encrypted SNMP v3 communication. Configuring SNMP Notifications The PXE automatically keeps an internal log of events that occur. See (on page 121). These events can also be Event Rules and Actions used to send SNMP v2c or v3 notifications to a third-party destination.

  • Page 204: Snmp Gets And Sets

    Chapter 7: Using SNMP SNMP Gets and Sets In addition to sending traps, the PXE is able to receive SNMP get and set requests from third-party SNMP managers.  Get requests are used to retrieve information about the PXE, such as the system location, and the current on a specific outlet.
  • Page 205 For example, the measurementsGroup group contains objects for sensor readings of PXE as a whole. One object listed under this group, measurementsUnitSensorValue, is described later in the MIB as "The sensor value". pduRatedCurrent, part of the configGroup group,...

  • Page 206: A Note About Enabling Thresholds

    Objects that can be configured have a MAX-ACCESS level of "read-write" in the MIB. These objects include threshold objects, which causes the PXE to generate a warning and send an SNMP notification when certain parameters are exceeded. See...

  • Page 207: Chapter 8 Using The Command Line Interface

    Network Troubleshooting...............317 Retrieving Previous Commands............320 Automatically Completing a Command ..........320 About the Interface The PXE provides a command line interface that enables data center administrators to perform some basic management tasks. Using this interface, you can do the following: ...

  • Page 208: Logging In To Cli

    Windows Vista. To log in using HyperTerminal: 1. Connect your computer to the PXE via a local connection. 2. Launch HyperTerminal on your computer and open a console window. When the window first opens, it is blank.

  • Page 209: With Ssh Or Telnet

    CLI. 6. You are now logged in to the command line interface and can begin administering the PXE. With SSH or Telnet You can remotely log in to the command line interface using an SSH or Telnet client, such as PuTTY.

  • Page 210: Different Cli Modes And Prompts

    PXE device, the > prompt appears.  Administrator Mode: When you log in as an administrator, who has full permissions to configure the PXE device, the # prompt appears.  Configuration Mode: You can enter the configuration mode from the administrator or user mode.

  • Page 211: 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 212: Querying Available Parameters For A Command

    Showing Information You can use the show commands to view current settings or status of the PXE device or part of it, such as the IP address, networking mode, firmware version, states or readings of internal or external sensors, user profiles, and so on.

  • Page 213: Network Configuration

    Chapter 8: Using the Command Line Interface Network Configuration This command shows all network configuration, such as the IP address, networking mode, and MAC address. 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 214 This command shows whether the current networking mode is wired or wireless. show network mode Note: If the PXE is a slave device connected to the LAN via the master PXE device, the show network mode command displays wired(USB) instead of wired.

  • Page 215: 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 216: 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: all, or a number. Option Description Displays the information for all inlets.

  • Page 217: Overcurrent Protector Information

    Chapter 8: Using the Command Line Interface Overcurrent Protector Information This command is only available for PDUs 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 218: 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 PXE device. show time To show detailed information, add the parameter "details" to the end of the command.

  • Page 219: 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 220: Actuator 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 Peripheral Devices page of the PXE web interface. Displayed information:  Without the parameter "details," only the sensor ID, sensor type and reading are displayed.

  • Page 221: Environmental Sensor Package Information

    Chapter 8: Using the Command Line Interface * The actuator number is the ID number assigned to the actuator, which can be found on the Peripheral Devices page of the PXE web interface. Displayed information:  Without the parameter "details," only the actuator ID, type and state are displayed.

  • Page 222: 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 223: 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. 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" to the end of the command.
  • Page 224 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 225: 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 226: Environmental Sensor Default Thresholds

     <n> is the environmental sensor number. The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripheral Devices page of the PXE web interface. Displayed information:  Without the parameter "details," only the reading, threshold, deassertion hysteresis and assertion timeout settings of the specified environmental sensor are displayed.

  • Page 227: Security Settings

    With the parameter "details," the threshold range is displayed in addition to default thresholds settings. Security Settings This command shows the security settings of the PXE. show security To show detailed information, add the parameter "details" to the end of the command.

  • Page 228: Existing User Profiles

    Chapter 8: Using the Command Line Interface Existing User Profiles This command shows the data of one or all existing user profiles. show user <user_name> To show detailed information, add the parameter "details" to the end of the command. show user <user_name> details Variables: ...

  • Page 229: Existing Roles

    This option shows the data of the specified role only. Displayed information:  Role settings are displayed, including the role description and privileges. EnergyWise Settings This command shows the PXE device's current configuration for Cisco ® EnergyWise. show energywise...

  • Page 230: Event Log

    Chapter 8: Using the Command Line Interface Event Log The command used to show the event log begins with show eventlog. You can add either the limit or class parameters or both to show specific events. Show the last 30 entries: show eventlog Show a specific number of last entries in the event log: show eventlog limit <n>...

  • Page 231: Reliability Data

    EnergyWise function. timerEvent Scheduled action events. Note: You can ignore the following event types in the CLI because the PXE does not support them: assetManagement, cardReader, lhx, modem, transferSwitch and webcam. Reliability Data This command shows the reliability data.

  • Page 232: 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 233 Chapter 8: Using the Command Line Interface Example 2 - In-Depth Security Information More information is displayed when typing the show security details command. Example 3 - Basic PDU Information The diagram shows the output of the show pdu command.

  • Page 234: Clearing Information

    Clearing Information You can use the clear commands to remove unnecessary data from the PXE. After typing a "clear" command, press Enter to execute it. Note: Depending on your login name, the # prompt may be replaced by the > prompt. See Different CLI Modes and Prompts (on page 194).

  • Page 235: Configuring The Pxe Device And Network

    Chapter 8: Using the Command Line Interface Configuring the PXE Device and Network To configure the PXE device or network settings through the CLI, it is highly recommended to log in as the administrator so that you have full permissions.

  • Page 236: Pdu Configuration Commands

    A PDU configuration command begins with pdu. You can use the PDU configuration commands to change the settings that apply to the whole PXE device. Changing the PDU Name This command syntax changes the PXE device's name. config:# pdu name "<name>" Variables: ...
  • Page 237 Specifying the Device Altitude This command syntax specifies your PXE device's altitude above sea level (in meters). You must specify the PXE device's altitude above sea level if a Raritan differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor.
  • Page 238 Chapter 8: Using the Command Line Interface Option Description freeForm Any alphanumeric string can be used for specifying the Z coordinate. Note: After determining the format for the Z coordinate, you can set a value for it. See Setting the Z Coordinate (on page 286).

  • Page 239: Network Configuration Commands

    Enables the wireless networking mode. Note: If you enable the wireless networking mode, and the PXE does not detect any wireless USB LAN adapter or the connected wireless USB LAN adapter is not supported, the message "Supported Wireless device not found"...
  • Page 240 This command syntax determines which IP address is used when the DNS server returns both of IPv4 and IPv6 addresses. You need to configure this setting only after both of IPv4 and IPv6 protocols are enabled on the PXE. config:# network ip dnsResolverPreference <resolver>...
  • Page 241 Cannot contain punctuation marks, spaces, and other symbols Setting the IPv4 Address After selecting the static IP configuration mode, you can use this command syntax to assign a permanent IP address to the PXE device. config:# network ipv4 ipAddress <ip address>...
  • Page 242 Chapter 8: Using the Command Line Interface Setting the IPv4 Subnet Mask After selecting the static IP configuration mode, you can use this command syntax to define the subnet mask. config:# network ipv4 subnetMask <netmask> Variables:  <netmask> is the subnet mask address. The value ranges from 0.0.0.0 to 255.255.255.255.
  • Page 243 <ip address> is the IP address of the secondary DNS server. The value ranges from 0.0.0.0 to 255.255.255.255. Note: The PXE supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the PXE only uses the primary IPv4 and IPv6 DNS servers.
  • Page 244 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 PXE and devices in the other subnet. These commands are prefixed with network ipv4 staticRoutes.
  • Page 245 Chapter 8: Using the Command Line Interface Setting the IPv6 Configuration Mode This command syntax determines the IP configuration mode. config:# network ipv6 ipConfigurationMode <mode> Variables:  <mode> is one of the modes: automatic or static. Mode Description automatic The IPv6 configuration mode is set to automatic. static The IPv6 configuration mode is set to static IP address.
  • Page 246 Chapter 8: Using the Command Line Interface Setting the IPv6 Address After selecting the static IP configuration mode, you can use this command syntax to assign a permanent IP address to the PXE device. config:# network ipv6 ipAddress <ip address>...
  • Page 247 <ip address> is the IP address of the secondary DNS server. This value uses the IPv6 address format. Note: The PXE supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the PXE only uses the primary IPv4 and IPv6 DNS servers.
  • Page 248 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 PXE and devices in the other subnet. These commands are prefixed with network ipv6 staticRoutes.
  • Page 249  <mode> is one of the modes: auto, half or full. Option Description auto The PXE selects the optimum transmission mode through auto-negotiation. half Half duplex: Data is transmitted in one direction (to or from the PXE device) at a time.
  • Page 250 Chapter 8: Using the Command Line Interface Setting the HTTP Port The commands used to configure the HTTP port settings begin with network services http. Change the HTTP port: config:# network services http port <n> Enable or disable the HTTP port: config:# network services http enabled <option>...
  • Page 251  <option> is one of the options: true or false. Option Description true Forces any access to the PXE via HTTP to be redirected to HTTPS. false No HTTP access is redirected to HTTPS. Changing the Telnet Configuration You can enable or disable the Telnet service, or change its TCP port using the CLI commands.
  • Page 252 Chapter 8: Using the Command Line Interface Option Description false The Telnet service is disabled. Changing the Telnet Port This command syntax changes the Telnet port. config:# network services telnet port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default Telnet port is 23.
  • Page 253 Chapter 8: Using the Command Line Interface Changing the SSH Port This command syntax changes the SSH port. config:# network services ssh port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default SSH port is 22. Setting the SNMP Configuration You can enable or disable the SNMP v1/v2c or v3 agent, configure the read and write community strings, or set the MIB-II parameters, such as...
  • Page 254 Chapter 8: Using the Command Line Interface Setting the SNMP Read Community This command syntax sets the SNMP read-only community string. config:# network services snmp readCommunity <string> Variables:  <string> is a string comprising 4 to 64 ASCII printable characters. ...
  • Page 255 Chapter 8: Using the Command Line Interface Setting the sysLocation Value This command syntax sets the SNMP MIB-II sysLocation value. config:# network services snmp sysLocation <value> Variables:  <value> is a string comprising 0 to 255 alphanumeric characters. Changing the Modbus Configuration You can enable or disable the Modbus agent, configure its read-only capability, or change its TCP port.
  • Page 256 Chapter 8: Using the Command Line Interface Changing the Modbus Port This command syntax changes the Modbus port. config:# network services modbus port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default Modbus port is 502. Enabling or Disabling the Service Advertisement This command syntax enables or disables the zero configuration protocol, which enables advertising or auto discovery of network services.

  • Page 257: Time Configuration Commands

    Chapter 8: Using the Command Line Interface Example 2 - Enabling Both IP Protocols The following command determines that both IPv4 and IPv6 protocols are enabled. config:# network ip proto both Example 3 - Static IPv4 Configuration The following command enables the Static IP configuration mode. config:# network ipv4 ipConfigurationMode static Time Configuration Commands...
  • Page 258 Chapter 8: Using the Command Line Interface Specifying the Primary NTP Server This command syntax specifies the primary time server if synchronization with the NTP server is enabled. config:# time ntp firstServer <first_server> Variables:  The <first_server> is the IP address or host name of the primary NTP server.
  • Page 259 Chapter 8: Using the Command Line Interface Setting the Time Zone In addition to the web interface, the CLI also provides a list of time zones for you to configure the date and time for your PXE device. config:# time zone...

  • Page 260: Security Configuration Commands

    A security configuration command begins with security. Firewall Control You can manage firewall control features through the CLI. The firewall control lets you set up rules that permit or disallow access to the PXE device from a specific or a range of IP addresses. ...
  • Page 261 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 262 Chapter 8: Using the Command Line Interface Option Description false Disables the IP access control feature.  <policy> is one of the options: accept, drop or reject. Option Description accept Accepts traffic from all IP addresses. drop Discards traffic from all IP addresses, without sending any failure notification to the source host.
  • Page 263 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:#...
  • Page 264 Chapter 8: Using the Command Line Interface  <insert> is one of the options: insertAbove or insertBelow. Option Description insertAbove Inserts the new rule above the specified rule number. Then: new rule's number = the specified rule number insertBelow Inserts the new rule below the specified rule number.
  • Page 265 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> ipMask <ip_mask> Modify an IPv6 rule's policy: 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>...
  • Page 266 Chapter 8: Using the Command Line Interface Deleting a Firewall Rule The following commands remove a specific IPv4 or IPv6 rule from the list.  IPv4 commands config:# security ipAccessControl ipv4 rule delete <direction> <rule_number>  IPv6 commands config:# security ipAccessControl ipv6 rule delete <direction> <rule_number> Variables: ...
  • Page 267 Chapter 8: Using the Command Line Interface If the Restricted Service Agreement feature is enabled, the Restricted Service Agreement is displayed when any user logs in to the PXE. Do either of the following, or you cannot successfully log in to the PXE: ...
  • Page 268 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 269 The interval ranges from 7 to 365 days. Idle Timeout This command syntax determines how long a user can remain idle before that user is forced to log out of the PXE web interface or CLI. config:# security loginLimits idleTimeout <value>...
  • Page 270 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 parameters at a time. See (on page 311).
  • Page 271 Chapter 8: Using the Command Line Interface Enabling or Disabling Strong Passwords This command syntax enables or disables the strong password feature. config:# security strongPasswords enabled <option> Variables:  <option> is one of the options: true or false. Option Description true Enables the strong password feature.
  • Page 272 Chapter 8: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option> Variables:  <option> is one of the options: enable or disable. Option Description enable At least one lowercase character is required. disable No lowercase character is required. Uppercase Character Requirement This command syntax determines whether a strong password includes at least a uppercase character.
  • Page 273 Chapter 8: Using the Command Line Interface Special Character Requirement This command syntax determines whether a strong password includes at least a special character. config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option> Variables:  <option> is one of the options: enable or disable. Option Description enable...
  • Page 274 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 enabled <option> Determine the IPv4 role-based access control policy: config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>  IPv6 commands Enable or disable the IPv6 role-based access control feature: config:# security roleBasedAccessControl ipv6 enabled <option> Determine the IPv6 role-based access control policy: config:# security roleBasedAccessControl ipv6 defaultPolicy <policy>...
  • Page 275 Chapter 8: Using the Command Line Interface Managing Role-Based Access Control Rules You can add, delete or modify role-based access control rules.  An IPv4 role-based access control command for managing rules begins with security roleBasedAccessControl ipv4 rule.  An IPv6 role-based access control command for managing rules begins with security roleBasedAccessControl ipv6 rule.
  • Page 276 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role> <policy> <insert> <rule_number> Variables:  <start_ip> is the starting IP address.  <end_ip> is the ending IP address.  <role> is the role for which you want to create an access control rule. ...
  • Page 277 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role <role> Modify an IPv4 rule's policy: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy <policy> Modify all contents of an existing IPv4 rule: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip>...
  • Page 278 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> Variables:  <rule_number> is the number of the existing rule that you want to modify.  <start_ip> is the starting IP address. ...
  • Page 279 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 enabled true defaultPolicyIn accept defaultPolicyOut accept Results:  The IPv4 access control feature is enabled.  The default policy for inbound traffic is set to "accept."  The default policy for outbound traffic is set to "accept." Example 2 - Adding an IPv4 Firewall Rule The following command adds a new IPv4 access control rule and specifies its location in the list.

  • Page 280: 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 281: Inlet Configuration Commands

    Chapter 8: Using the Command Line Interface Inlet Configuration Commands An inlet configuration command begins with inlet. You can configure an inlet by using the inlet configuration command. Changing the Inlet Name This command syntax names an inlet. config:# inlet <n> name "<name>" Variables: ...

  • Page 282: Overcurrent Protector Configuration Commands

    An overcurrent protector configuration command begins with ocp. The command configures an individual circuit breaker or fuse which protects outlets. Changing the Overcurrent Protector Name This command syntax names a circuit breaker or a fuse on your PXE. config:# ocp <n> name "<name>" Variables: ...
  • Page 283 This command syntax allows you to change an existing user's password if you have the Administrator Privileges. config:# user modify <name> password After performing the above command, PXE prompts you to enter a new password. Then: 1. Type a new password and press Enter.
  • Page 284 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 285 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 specific user profile at a time.
  • Page 286 Chapter 8: Using the Command Line Interface Enabling or Disabling a User Profile This command syntax enables or disables a user profile. A user can log in to the PXE device only after that user's user profile is enabled. config:# user modify <name> enabled <option>...
  • Page 287 You can combine all of the following commands to modify the SNMPv3 parameters at a time. See Multi-Command Syntax (on page 311). Enable or disable the SNMP v3 access to PXE for the specified user: config:# user modify <name> snmpV3Access <option1>...
  • Page 288 Chapter 8: Using the Command Line Interface config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3> Variables:  <name> is the name of the user whose settings you want to change.  <option3> is one of the options: true or false. Option Description true Authentication passphrase is identical to the password.
  • Page 289 Chapter 8: Using the Command Line Interface Determine the privacy passphrase: config:# user modify <name> privacyPassPhrase <privacy_passphrase> Variables:  <name> is the name of the user whose settings you want to change.  <privacy_passphrase> is a string used as a privacy passphrase, comprising 8 to 32 ASCII printable characters.
  • Page 290 (on page 311). Note: The measurement unit change only applies to the web interface and command line interface. Tip: To set the default measurement units applied to the PXE user interfaces for all users via CLI, see Setting Up User Preferences (Units...
  • Page 291 Chapter 8: Using the Command Line Interface Set the preferred length unit: config:# user modify <name> preferredLengthUnit <option2> Variables:  <name> is the name of the user whose settings you want to change.  <option2> is one of the options: meter or feet. Option Description meter...
  • Page 292 After performing this command, the PXE prompts you to enter both current and new passwords respectively. Important: After the password is changed successfully, the new password is effective immediately no matter you type the command "apply"...
  • Page 293 Setting Default Measurement Units Default measurement units, including temperature, length, and pressure units, apply to the PXE user interfaces across all users except for those whose preferred measurement units are set differently by themselves or the administrator. Diverse measurement unit commands can be combined so that you can set all default measurement units at a time.
  • Page 294 Chapter 8: Using the Command Line Interface config:# user defaultpreferences preferredLengthUnit <option2> Variables:  <option2> is one of the options: meter or feet. 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 295: Role Configuration Commands

    Chapter 8: Using the Command Line Interface Example 2 - Modifying a User's Roles The following command assigns two roles to the user "May." config:# user modify May roles admin,tester Results:  The user May has the union of all privileges of "admin" and "tester." Example 3 - Default Measurement Units The following command sets all default measurement units at a time.
  • Page 296 Chapter 8: Using the Command Line Interface config:# role create <name> <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon.
  • Page 297 Chapter 8: Using the Command Line Interface Privilege Description changeUserSettings Change Local User Management clearLog Clear Local Event Log firmwareUpdate Firmware Update performReset Reset (Warm Start) viewDataRetrieval View Data Logging Settings viewEventSetup View Event Settings viewLog View Local Event Log viewSecuritySettings View Security Settings viewSnmpSettings...
  • Page 298 Chapter 8: Using the Command Line Interface config:# role modify <name> addPrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon.
  • Page 299 Chapter 8: Using the Command Line Interface config:# role modify <name> removePrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Note: When removing privileges from a role, make sure the specified privileges and arguments (if any) exactly match those assigned to the role. Otherwise, the command fails to remove specified privileges that are not available.

  • Page 300: Environmental Sensor Configuration Commands

     <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...
  • Page 301  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...
  • Page 302  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...
  • Page 303  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...

  • Page 304: Sensor Threshold Configuration Commands

    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 305 Chapter 8: Using the Command Line Interface Setting the Inlet's Upper Critical Threshold This command syntax configures the Upper Critical threshold of an inlet. config:# sensor inlet <n> <sensor type> upperCritical <option> Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n>...
  • Page 306 Chapter 8: Using the Command Line Interface Setting the Inlet's Upper Warning Threshold This command syntax configures the Upper Warning threshold of an inlet. config:# sensor inlet <n> <sensor type> upperWarning <option> Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n>...
  • Page 307 Chapter 8: Using the Command Line Interface Setting the Inlet's Lower Critical Threshold This command syntax configures the Lower Critical threshold of an inlet. config:# sensor inlet <n> <sensor type> lowerCritical <option> Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n>...
  • Page 308 Chapter 8: Using the Command Line Interface Setting the Inlet's Lower Warning Threshold This command syntax configures the Lower Warning threshold of an inlet. config:# sensor inlet <n> <sensor type> lowerWarning <option> Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n>...
  • Page 309 Chapter 8: Using the Command Line Interface Setting the Inlet's Deassertion Hysteresis This command syntax configures the deassertion hysteresis value of an inlet. config:# sensor inlet <n> <sensor type> hysteresis <value> Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n>...
  • Page 310 Chapter 8: Using the Command Line Interface Setting the Inlet's Assertion Timeout This command syntax configures the assertion timeout value of an inlet. config:# sensor inlet <n> <sensor type> assertionTimeout <value> Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n>...
  • Page 311 Chapter 8: Using the Command Line Interface config:# sensor inletpole <n> <p> <sensor type> upperCritical <option> Variables:  <n> is the number of the inlet whose pole sensors you want to configure.  <p> is the label of the inlet pole that you want to configure. Pole Label Current sensor...
  • Page 312 Chapter 8: Using the Command Line Interface Setting the Upper Warning Threshold for an Inlet Pole This command syntax configures the Upper Warning threshold of an inlet pole. config:# sensor inletpole <n> <p> <sensor type> upperWarning <option> Variables:  <n> is the number of the inlet whose pole sensors you want to configure.
  • Page 313 Chapter 8: Using the Command Line Interface Option Description A numeric Sets a value for the upper warning threshold of value the specified inlet pole sensor and enables this threshold at the same time. Setting the Lower Critical Threshold for an Inlet Pole This command syntax configures the Lower Critical threshold of an inlet pole.
  • Page 314 Chapter 8: Using the Command Line Interface  <option> is one of the options: enable, disable or a numeric value. Option Description enable Enables the lower critical threshold for the specified inlet pole sensor. disable Disables the lower critical threshold for the specified inlet pole sensor.
  • Page 315 Chapter 8: Using the Command Line Interface Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.  <option> is one of the options: enable, disable or a numeric value. Option Description enable Enables the lower warning threshold for the specified inlet pole sensor.
  • Page 316 Chapter 8: Using the Command Line Interface Sensor type Description unbalancedCurrent Unbalanced load sensor Note: If the requested sensor type is not supported, the "Sensor is not available" message is displayed.  <value> is a numeric value that is assigned to the hysteresis for the specified inlet pole sensor.
  • Page 317  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...
  • Page 318  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...
  • Page 319  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...
  • Page 320  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...
  • Page 321  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and ...

  • Page 322: Actuator Configuration Commands

    Chapter 8: Using the Command Line Interface Examples This section illustrates several environmental sensor threshold configuration examples. Example 1 - Warning Thresholds for Inlet Sensors The following command sets both the Upper Warning and Lower Warning thresholds for the inlet 1 RMS current. config:# sensor inlet 1 current upperWarning 20 lowerWarning 12 Results:...
  • Page 323 Variables:  <n> is the ID number of the actuator that you want to configure. The ID number is assigned and shown in the PXE web interface. It is an integer starting at 1.  <name> is a string comprising up to 32 ASCII printable characters.
  • Page 324 Variables:  <n> is the ID number of the actuator that you want to configure. The ID number is assigned and shown in the PXE web interface. It is an integer starting at 1.  Depending on the Z coordinate format you set, there are two types of values for the <coordinate>...

  • Page 325: Energywise Configuration Commands

    An EnergyWise configuration command begins with energywise. Enabling or Disabling EnergyWise This command syntax determines whether the Cisco EnergyWise ® endpoint implemented on the PXE device is enabled. config:# energywise enabled <option> Variables:  <option> is one of the options: true or false.
  • Page 326  <port> is the UDP port number ranging between 1 and 65535. Setting the Polling Interval This command syntax determines the polling interval at which the Cisco ® EnergyWise domain queries the PXE device. config:# energywise polling <timing> Variables: ...

  • Page 327: Setting The History Buffer Length

    10288 Results:  The EnergyWise feature implemented on the PXE is enabled.  The UDP port is set to 10288. Setting the History Buffer Length This command syntax sets the history buffer length, which determines the amount of history commands that can be retained in the buffer.

  • Page 328: Actuator Control Operations

    Chapter 8: Using the Command Line Interface config:# network ipv4 ipAddress 192.168.84.225 subnetMask 255.255.255.0 gateway 192.168.84.0 Results:  The IP address is set to 192.168.84.225.  The subnet mask is set to 255.255.255.0.  The gateway is set to 192.168.84.0. Example 2 - Combination of Upper Critical and Upper Warning Settings The following multi-command syntax simultaneously configures Upper Critical and Upper Warning thresholds for the RMS current of the inlet.

  • Page 329: Switching On The Actuator(S)

    Switches ON all actuators. A specific Switches ON the specified actuator. actuator's ID The ID number is available in the PXE web number interface or using the show command in the CLI. It is an integer between 1 and 32.

  • Page 330: Switching Off The Actuator(S)

    Switches OFF all actuators. A specific Switches OFF the specified actuator. actuator's ID The ID number is available in the PXE web number interface or using the show command in the CLI. It is an integer between 1 and 32.

  • Page 331: Unblocking A User

    Chapter 8: Using the Command Line Interface Unblocking a User If any user is blocked from accessing the PXE, you can unblock them at the local console. To unblock a user: 1. Log in to the CLI interface using any terminal program via a local connection.

  • Page 332: Resetting Active Energy Readings

     <n> is the inlet number. For a single-inlet PDU, the number is always Resetting to Factory Defaults The following commands restore all settings of the PXE device to factory defaults. To reset PXE settings after login, use either command:...

  • Page 333: Network Troubleshooting

    Chapter 8: Using the Command Line Interface Network Troubleshooting The PXE provides 4 diagnostic commands for troubleshooting network problems: nslookup, netstat, ping, and traceroute. The diagnostic commands function as corresponding Linux commands and can get corresponding Linux outputs. Entering Diagnostic Mode Diagnostic commands function in the diagnostic mode only.
  • Page 334 Chapter 8: Using the Command Line Interface Querying DNS Servers This command syntax queries Internet domain name server (DNS) information of a network host. diag> nslookup <host> Variables:  <host> is the name or IP address of the host whose DNS information you want to query.
  • Page 335 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 336: Retrieving Previous Commands

    Chapter 8: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your PXE device and a network host. diag> traceroute <host> Variables:  <host> is the name or IP address of the host you want to trace.
  • Page 337 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 338: Appendix A Specifications

    In This Chapter Maximum Ambient Operating Temperature ..........322 Sensor RJ-12 Port Pinouts ..............322 RS-485 Port Pinouts................322 Maximum Ambient Operating Temperature The maximum ambient operating temperature (TMA) for the PXE is the same for all models. Measure Specification Max Ambient Temperature...
  • Page 339 Appendix A: Specifications RS-485 Pin/signal definition ― ― ― ― ― ― bi-direction Data - ― ― ― ― ― ―...

  • Page 340: Appendix B Equipment Setup Worksheet

    Appendix B Equipment Setup Worksheet PXE Series Model ____________ PXE 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...
  • Page 341 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 342 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 343 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 344: Appendix C Resetting To Factory Defaults

    (on page 11). Connecting the PXE to a Computer 2. Launch a terminal emulation program such as HyperTerminal, Kermit, or PuTTY, and open a window on the PXE. For information on the serial port configuration, see Step 2 of Initial Network (on page 12).
  • Page 345 Appendix C: Resetting to Factory Defaults To reset to factory defaults without logging in to the CLI: The PXE provides an easier way to reset the product to factory defaults in the CLI prior to login. 1. Connect to the PXE and launch a terminal emulation program as described in the above procedure.

  • Page 346: Appendix D Ldap Configuration Illustration

    Step A. Determine User Accounts and Groups Determine the user accounts and groups that are authenticated for accessing the PXE. In this example, we will create two user groups with different permissions. Each group will consist of two user accounts available on the AD server.

  • Page 347: Step B. Configure User Groups On The Ad Server

    Appendix D: LDAP Configuration Illustration Step B. Configure User Groups on the AD Server You must create the groups for the PXE on the AD server, and then make appropriate users members of these groups. In this illustration, we assume: ...

  • Page 348: Step C. Configure Ldap Authentication On The Pxe Device

    Appendix D: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the PXE Device You must enable and set up LDAP authentication properly on the PXE device to use external authentication. In the illustration, we assume:  The DNS server settings have been configured properly. See...
  • Page 349 Appendix D: LDAP Configuration Illustration 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 350: Step D. Configure User Groups On The Pxe Device

    Appendix D: LDAP Configuration Illustration 6. Click OK. The LDAP authentication is activated. Note: If the PXE clock and the LDAP server clock are out of sync, the certificates are considered expired and users are unable to authenticate using LDAP. To ensure proper synchronization, administrators should configure the PXE and the LDAP server to use the same NTP server.
  • Page 351 Appendix D: LDAP Configuration Illustration d. Repeat Steps a to c to add all permissions beginning with "View." 6. Click OK. The PX_User role is created. 7. Keep the Manage Roles dialog opened to create the PX_Admin role. To create the PX_Admin role with full permissions assigned: 1.
  • Page 352 "The role includes all privileges" to describe the role. 4. Click the Privileges tab to select the Administrator permission. The Administrator permission allows users to configure or change all PXE settings. a. Click Add. The "Add Privileges to new Role" dialog appears.
  • Page 353 Appendix D: LDAP Configuration Illustration 5. Click OK. The PX_Admin role is created. 6. Click Close to quit the dialog.

  • Page 354: Appendix E Integration

    Appendix E Integration The PXE device can work with certain Raritan or non-Raritan products to provide diverse power solutions. In This Chapter Power IQ Configuration .................338 dcTrack ....................340 Power IQ Configuration Raritan'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 355 5. Enter data in Custom Field 1 and Custom Field 2. Optional. The labels may have been changed in Power IQ to identify these fields. 6. If the PDU is a Raritan PX, enter a valid Username and Password for the PDU in the PDU Administrative Credentials section. Re-enter the password in the Password Confirm field.

  • Page 356: Dctrack

    IQ polls PDU. See Configuring Polling Intervals in the Power IQ User Guide. dcTrack dcTrack is a Raritan product that allows you to manage the data center. ® You can use dcTrack to:  Record and manage the data center infrastructure and assets ...

  • Page 357: Dctrack Overview

    Change Control process and work in Request Bypass so requests are processed immediately. dcTrack can be used as a standalone product or integrated with ® Raritan's Power IQ for power ® http://www.raritan.com/products/dcim-software/power-iq and environmental monitoring. Adding the PX to dcTrack Management The PX is categorized as a rack PDU in dcTrack.
  • Page 358 Horizontally mounted/rack mounted rack PDUs do not apply to this step since there is no side to select. 9. If you are adding a Raritan PX2 device for asset sensor management purposes, see Adding a PX2 to dcTrack for information on adding this item as a rack PDU.

  • Page 359: Appendix F Additional Pxe Information

    Reserving IP Addresses in Windows DHCP Servers......349 Sensor Threshold Settings ..............349 MAC Address A label is affixed to the PXE, showing both the serial number and MAC address. If necessary, you can find its IP address through the MAC address by using commonly-used network tools.

  • Page 360: Securelock™ Outlets And Cords

    SecureLock™ Outlets and Cords SecureLock is an innovative mechanism designed by Raritan, which ™ securely holds C14 or C20 plugs that are plugged into Raritan PDUs in place. This method requires the following two components:  Raritan PDU with SecureLock outlets, which have a latch slot inside ™...

  • Page 361: Button-Type Locking Outlets

    Appendix F: Additional PXE Information ™ To remove a SecureLock power cord from the PDU: 1. Press and hold down the two latches on the cord's plug as illustrated in the diagram below. 2. Unplug the cord now. Button-Type Locking Outlets A button-type locking outlet has a button on it.

  • Page 362: Unbalanced Current Calculation

    Appendix F: Additional PXE Information Unbalanced Current Calculation Unbalanced current information is available on 3-phase models only. This section explains how the PXE calculates the unbalanced current percentage. Calculation: 1. Calculate the average current of all 3 lines. Average current = (L1+L2+L3) / 3 2.

  • Page 363: Altitude Correction Factors

    100 * (0.1837) = 18% 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 364: Raritan Training Website

    Truncated Data in the Web Interface Some fields of the PXE web interface can accommodate data entry up to 256 characters. When the data entered is too long, it may be truncated due to some or all of the following factors: ...

  • Page 365: Reserving Ip Addresses In Windows Dhcp Servers

    Appendix F: Additional PXE Information Reserving IP Addresses in Windows DHCP Servers The PXE uses its serial number as the client identifier in the DHCP request. Therefore, to successfully reserve an IP address for the PXE in a Windows DHCP server, use the PXE device's serial number as the ®...

  • Page 366: Thresholds And Sensor States

    Appendix F: Additional PXE Information Thresholds and Sensor States A numeric sensor has four threshold settings: Lower Critical, Lower Warning, Upper Warning and Upper Critical. The threshold settings determine how many sensor states are available for a certain sensor and the range of each sensor state. The diagram below shows how each threshold relates to each state.
  • Page 367 Appendix F: Additional PXE Information  When a sensor only has the Upper Critical threshold enabled, it has two sensor states: normal and above upper critical.  When a sensor has both the Upper Critical and Upper Warning thresholds enabled, it has three sensor states: normal, above upper warning, and above upper critical.
  • Page 368 In the threshold setup dialog, the Assertion Timeout field impacts the "assert" action. It determines how long a sensor must be in the "worse" new state before the PXE turns on the "assert" action. If that sensor changes its state again within the specified wait time, the PXE does NOT assert that state.
  • Page 369 When 'Assertion Timeout' is helpful: If you have created an event rule that instructs the PXE to send notifications for assertion events, setting the "Assertion Timeout" is helpful for eliminating a number of notifications that you may receive in case the sensor's reading fluctuates around a certain threshold.
  • Page 370 Appendix F: Additional PXE Information "To De-assert" and Deassertion Hysteresis After the PXE asserts a state for a sensor, it may de-assert the same state later on. To de-assert a state: To de-assert a state is to announce the end of the previously asserted, bad state.
  • Page 371 Deassertion Hysteresis to 0 (zero). When 'Deassertion Hysteresis' is helpful: If you have created an event rule that instructs the PXE to send notifications for deassertion events, setting the "Deassertion Hysteresis" is helpful for eliminating a number of notifications that you may receive in case a sensor's reading fluctuates around a certain threshold.
  • Page 372 If the temperature falls between 20 and 17 degrees Celsius, the "de-assert" action is NOT turned on.  If the temperature drops to 17 degrees Celsius or lower, the PXE turns on the "de-assert" action to announce the end of the "above upper warning" state.
  • Page 373 Changing Your Own Password • 278 Changing Your Password • 38 Checking Outlet-Specific Data • xiv, 115 Backup and Restore of PXE Device Settings • Checking Server Monitoring States • 156 xv, 173, 176 Checking the Branch Circuit Rating • xiii, 9 Before You Begin •...
  • Page 374 Function • xv, 160, 172, 223 Connecting the PDU to a Power Source • 9 Displaying PDU Information • 54, 115 Connecting the PXE to a Computer • 11, 330 Downloading Diagnostic Information • 178 Connecting the PXE to Your Network • 12 Downloading Key and Certificate Files •...
  • Page 375 Index Enabling or Disabling Data Logging • 221 Example - Turning On a Specific Actuator • Enabling or Disabling EnergyWise • 311 Enabling or Disabling Modbus • 241 Example 1 • 148 Enabling or Disabling Peripheral Device Auto Example 1 - Basic Security Information • 217 Management •...
  • Page 376 Index Full Disaster Recovery • 182 Locking Outlets and Cords • xv, 16, 345 Log an Event Message • 123, 126 Logging in to CLI • 193, 330 Logging in to the Web Interface • 36 Gathering the External Authentication Logging out of CLI •...
  • Page 377 Rack-Mounting the PDU • 2 Naming the PDU • 41, 42, 43, 44, 55, 73, 77, Raritan Training Website • xv, 350 163, 172 Rebooting the PXE Device • 77 Network Configuration • 198 Reliability Data • 216 Network Configuration Commands • 224 Reliability Error Log •...
  • Page 378 Sample Inlet-Level Event Rule • 147 Setting the Inlet's Upper Warning Threshold • Sample PDU-Level Event Rule • 147 Saving the PXE Configuration • 174 Setting the IPv4 Address • 227 Scheduling an Action • xiv, 137 Setting the IPv4 Configuration Mode • 226 SecureLock™...
  • Page 379 Supported Web Browsers • xiii, 35 Warning Icon • 46 Switch Peripheral Actuator • 123, 132 What's New in the PXE User Guide • xiii Switching Off the Actuator(s) • 316 Windows NTP Server Synchronization Switching On the Actuator(s) • 315 Solution •...
  • Page 380 Index Zero U Products • 1...
  • Page 382 For CommandCenter Secure Gateway: Press 6, then Press 2 Phone: +31-10-2844040 Fax: 732-764-8887 Email: tech.europe@raritan.com Email for CommandCenter NOC: tech-ccnoc@raritan.com Email for all other products: tech@raritan.com United Kingdom Monday - Friday 8:30 a.m. to 5 p.m. GMT China Phone +44(0)20-7090-1390...

Table of Contents