1. DL manuals
  2. Raritan
  3. Power distribution unit
  4. PX2-1000 SERIES
  5. User Manual

Raritan PX2-1000 SERIES User Manual

Other manuals for PX2-1000 SERIES: User manual

Summary of PX2-1000 SERIES

  • Page 1

    Px2-1000/2000 series user guide xerus ™ firmware v3.3.10 copyright © 2017 raritan, inc. Dpx2-1000-1a-v3.3.10-e march 2017 255-80-6105-00

  • Page 2

    Warning! Read and understand all sections in this guide before installing or operating this product. Warning! Connect this product to an ac power source whose voltage is within the range specified on the product's nameplate. Operating this product outside the nameplate voltage range may result in el...

  • Page 3

    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. This product is designed to be used within an electro...

  • Page 4

    This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated into another language without express prior written consent of raritan, inc. © copyright 2017 raritan, inc. All third-party softw...

  • Page 6

    Vi contents safety guidelines ii safety instructions iii applicable models xv what's new in the px2 user guide xvii chapter 1 introduction 1 product models .................................................................................................................................... 1 package c...

  • Page 7

    Contents vii chapter 3 initial installation and configuration 21 connecting the pdu to a power source ........................................................................................... 21 connecting the px2 to your network .......................................................................

  • Page 8

    Contents viii led display .............................................................................................................................. 80 reset button ............................................................................................................................ 85 cir...

  • Page 9

    Contents ix ocps ................................................................................................................................................. 133 individual ocp pages ............................................................................................................ 135...

  • Page 10

    Contents x rebooting the px2 device ..................................................................................................... 315 resetting all settings to factory defaults ........................................................................... 315 retrieving software packages inform...

  • Page 11

    Contents xi existing user profiles ........................................................................................................... 354 existing roles ........................................................................................................................ 355 load shedding...

  • Page 12

    Contents xii turning off the outlet(s) ....................................................................................................... 484 power cycling the outlet(s) .................................................................................................. 485 canceling the power-on...

  • Page 13

    Contents xiii creating configuration files via mass deployment utility ................................................. 515 data encryption in 'config.Txt' ............................................................................................... 516 firmware upgrade via usb .....................

  • Page 14

    Contents xiv freeradius vsa illustration ................................................................................................ 589 ad-related configuration ............................................................................................................... 590 appendix i additi...

  • Page 15

    Xv this user guide is applicable to the following pdu generation. • px2 pdu generation (1000/2000 series) any px generations can be associated with existing metering families called “series”, from 1000 series to 5000 series. For example, px2-4000, px3-4000 series and px3-ix7-4000 series are all inle...

  • Page 16

    Chapter 1: applicable models xvi comparison between px2, px3 and px3-ix7: * only px3 models with outlet switching have outlet latching relays. ** only px3 "zero u" (phase ii and ix7 ™ ) have the replaceable controller. *** px3 phase i models do not support a replaceable controller and are not availa...

  • Page 17

    Xvii the following sections have changed or information has been added to the px2 user guide based on enhancements and changes to the equipment and/or user documentation. Applicable models (on page xv) usb wireless lan adapters (on page 22) connecting the px2 to a computer (on page 24) initial netwo...

  • Page 18

    Chapter 1: what's new in the px2 user guide xviii changing the lan duplex mode (on page 386) configuring the cascading mode (on page 391) deleting an ntp server (on page 402) downloading diagnostic data via scp (on page 498) step c. Configure ldap authentication on the px2 device (on page 547) reser...

  • Page 19

    1 raritan px2 is an intelligent power distribution unit (pdu) that allows you to reboot remote servers and other network devices and/or to monitor power in the data center. The intended use of the raritan px2 is distribution of power to information technology equipment such as computers and communic...

  • Page 20

    Chapter 1: introduction 2 zero u products • the px2 device • screws, brackets and/or buttons for zero u • an "optional" null-modem cable with db9 connectors on both ends (raritan number: 254-01-0006-00) • cable retention clips for the inlet (for some models only) • cable retention clips for outlets ...

  • Page 21

    Chapter 1: introduction 3 apipa and link-local addressing the px2 supports automatic private internet protocol addressing (apipa). With apipa, your px2 automatically configures a link-local ip address and a link-local host name when it cannot obtain a valid ip address from any dhcp server in the tcp...

  • Page 22

    Chapter 1: introduction 4 retrieval of the link-local address: • perform the first three steps in the initial network configuration via cli (on page 27). Before you begin before beginning the installation, perform the following activities: • unpack the product and components • prepare the installati...

  • Page 23

    Chapter 1: introduction 5 checking the branch circuit rating the rating of the branch circuit supplying power to the pdu shall be in accordance with national and local electrical codes. Filling out the equipment setup worksheet an equipment setup worksheet is provided in this user guide. See equipme...

  • Page 24

    6 in this chapter circuit breaker orientation limitation ........................................................ 6 rack-mounting the pdu ............................................................................... 6 installing cable retention clips on the inlet (optional) ..........................

  • Page 25

    Chapter 2: rackmount, inlet and outlet connections 7 connect equipment to the supply circuit carefully to avoid overloading circuits. Ground all equipment properly, especially supply connections, to the branch circuit. Mounting zero u models using l-brackets if your pdu has circuit breakers implemen...

  • Page 26

    Chapter 2: rackmount, inlet and outlet connections 8 3. Align the l-brackets with the baseplates so that the five screw-holes on the baseplates line up through the l-bracket's slots. The rackmount side of brackets should face either the left or right side of the px2 device. 4. Fasten the brackets in...

  • Page 27

    Chapter 2: rackmount, inlet and outlet connections 9 mounting zero u models using button mount if your pdu has circuit breakers implemented, read circuit breaker orientation limitation (on page 6) before mounting it. To mount zero-u models using button mount: 1. Align the baseplates on the rear of t...

  • Page 28

    Chapter 2: rackmount, inlet and outlet connections 10 5. Loosen the hex socket screws until the mounting buttons are secured in their position. 6. Ensure that both buttons can engage their mounting holes simultaneously. 7. Press the px2 device forward, pushing the mounting buttons through the mounti...

  • Page 29

    Chapter 2: rackmount, inlet and outlet connections 11 3. Align the claw-foot brackets with the baseplates so that the five screw-holes on the baseplates line up through the bracket's slots. The rackmount side of brackets should face either the left or right side of the px2 device. 4. Fasten the brac...

  • Page 30

    Chapter 2: rackmount, inlet and outlet connections 12 mounting zero u models using two rear buttons the following describes how to mount a pdu using two buttons only. If your pdu has circuit breakers implemented, read circuit breaker orientation limitation (on page 6) before mounting it. To mount ze...

  • Page 31

    Chapter 2: rackmount, inlet and outlet connections 13 4. Screw a button in the screw hole near the top. The recommended torque for the button is 1.96 n·m (20 kgf·cm). 5. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously. 6. Press the px2 device forward...

  • Page 32

    Chapter 2: rackmount, inlet and outlet connections 14 2. Screw the l-bracket to the device and ensure the bracket is fastened securely. 3. Repeat steps 1 to 2 to screw another l-bracket to the bottom of the device. 4. After both l-brackets are installed, you can choose either of the following ways t...

  • Page 33

    Chapter 2: rackmount, inlet and outlet connections 15 2. Insert the cable-support bar into rackmount brackets. 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners. Installing cable retention clips on the inlet (optional) if your px2...

  • Page 34

    Chapter 2: rackmount, inlet and outlet connections 16 to install and use a cable retention clip on the inlet: 1. Locate two tiny holes adjacent to the inlet. 2. Install the cable retention clip by inserting two ends of the clip into the tiny holes. Zero u models 1u/2u models 3. Connect the power cor...

  • Page 35

    Chapter 2: rackmount, inlet and outlet connections 17 installing cable retention clips on outlets (optional) if your px2 device is designed to use a cable retention clip, install the clip before connecting a power cord. A cable retention clip prevents the connected power cord from coming loose or fa...

  • Page 36

    Chapter 2: rackmount, inlet and outlet connections 18 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". This allows gravity to keep t...

  • Page 37

    Chapter 2: rackmount, inlet and outlet connections 19 item description a latches on the securelock ™ cord's plug only specific pdus are implemented with the securelock ™ mechanism. If your pdu does not have this design, do not use the securelock ™ cords with it. Tip: the securelock ™ outlets can acc...

  • Page 38

    Chapter 2: rackmount, inlet and outlet connections 20 button-type locking outlets a button-type locking outlet has a button on it. Such outlets do not require any special power cords to achieve the locking purpose. All you need to do is simply plug a regular power cord into the locking outlet and th...

  • Page 39

    21 this chapter explains how to install a px2 device and configure it for network connectivity. In this chapter connecting the pdu to a power source .................................................... 21 connecting the px2 to your network ......................................................... 21...

  • Page 40

    Chapter 3: initial installation and configuration 22 2. Connect the other end of the cable to your lan. Below indicates the ethernet port on px zero u models: for 1u/2u models, the ethernet port is usually located on the back except for a few models. This diagram shows the port on the back. Warning:...

  • Page 41

    Chapter 3: initial installation and configuration 23 wi-fi lan adapters supported 802.11 protocols tp-link tl-wdn3200 v1 a/b/g/n raritan usb wifi a/b/g/n note: to use the edimax ew-7722und or raritan usb wifi wireless lan adapter to connect to an 802.11n wireless network, the handshake timeout setti...

  • Page 42

    Chapter 3: initial installation and configuration 24 note: for details on the link-local addressing, see apipa and link-local addressing (on page 3). Configuration over a dhcp-enabled network: 1. Connect the px2 to a dhcp ipv4 network. See connecting the px2 to your network (on page 21). 2. Retrieve...

  • Page 43

    Chapter 3: initial installation and configuration 25 to use the command line interface (cli) for configuration, establish an rs-232 or usb connection. To use a web browser for configuration, make a network connection to the computer. The px2 is automatically configured with the following link-local ...

  • Page 44

    Chapter 3: initial installation and configuration 26 installing the usb-to-serial driver (optional) the px2 can emulate a usb-to-serial converter over a usb connection. A usb-to-serial driver named "dominion px2 serial console" is required for microsoft ® windows ® operating systems. Download the wi...

  • Page 45

    Chapter 3: initial installation and configuration 27 note: if the px2 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. In linux: no additional drivers are required, but you must...

  • Page 46

    Chapter 3: initial installation and configuration 28 5. If prompted to change the default password, change or ignore it. To change it, follow onscreen instructions to type your new password. To ignore it, simply press enter. 6. The # prompt appears. 7. Type config and press enter. 8. To configure ne...

  • Page 47

    Chapter 3: initial installation and configuration 29 • static ip configuration: to set use this command static ipv4 or ipv6 address network interface address = static ip address, with a syntax similar to the example below. Example: 192.168.7.9/24 static ipv4 or ipv6 gateway network gateway address> ...

  • Page 48

    Chapter 3: initial installation and configuration 30 to set or enable use this command 802.11n protocol network wireless enableht = true , or false authentication method network wireless authmethod = psk or eap psk network wireless psk = psk string eap outer authentication network wireless eapoutera...

  • Page 49

    Chapter 3: initial installation and configuration 31 the content to be copied from the ca certificate does not include the first line containing "begin certificate" and the final line containing "end certificate." if a certificate is installed, configure the following: whether to use this command ve...

  • Page 50

    Chapter 3: initial installation and configuration 32 to verify network settings: after exiting the above configuration mode and the # prompt re-appears, type this command to verify all network settings. • show network the ip address configured may take seconds to take effect. Bulk configuration meth...

  • Page 51

    Chapter 3: initial installation and configuration 33 cascading multiple px2 devices for sharing ethernet connectivity you can have multiple px2 devices share one ethernet connection by cascading them via usb. Warning: to upgrade an existing usb-cascading chain from a version older than 3.3.10, you m...

  • Page 52

    Chapter 3: initial installation and configuration 34 cascading guidelines for port forwarding the following guidelines must be obeyed for establishing a cascading chain in the port forwarding mode. • each cascaded device, except for the master device, must have only one upstream device. • each casca...

  • Page 53

    Chapter 3: initial installation and configuration 35 cascading the px2 via usb any certified usb 2.0 cable up to 16 feet (5 meters) long can be used. Decide the cascading mode first before establishing the chain. All cascading modes support a maximum of 16 devices in a chain. For more information on...

  • Page 54

    Chapter 3: initial installation and configuration 36 number device role slave 2 slave 3 to cascade px2 devices via usb: 1. Make sure all raritan devices to be cascaded are running firmware version 3.3.10 or later. 2. Select one as the master device. When the port forwarding mode over wireless lan is...

  • Page 55

    37 more features are available if you connect raritan's or third-party external equipment to your px2. In this chapter connecting environmental sensor packages ........................................... 37 connecting asset management strips ...................................................... 58 ...

  • Page 56

    Chapter 4: connecting external equipment (optional) 38 dpx sensor packages most dpx sensor packages come with a factory-installed sensor cable, whose sensor connector is rj-12. For the cabling length restrictions, see supported maximum dpx sensor distances (on page 43). Warning: for proper operation...

  • Page 57

    Chapter 4: connecting external equipment (optional) 39 3. If intended, connect one dpx sensor package to the out port of the differential air pressure sensor. It can be any dpx sensor package, such as a dpx-t3h1. The px2 device raritan differential air pressure sensors one dpx sensor package (option...

  • Page 58

    Chapter 4: connecting external equipment (optional) 40 this diagram illustrates a configuration with a sensor hub connected. The px2 device raritan-provided phone cable dpx-envhub4 sensor hub dpx sensor packages.

  • Page 59

    Chapter 4: connecting external equipment (optional) 41 using an optional dpx-envhub2 cable a raritan dpx-envhub2 cable doubles the number of connected environmental sensors per sensor port. This cable supports dpx sensor packages only. Do not connect dpx2, dpx3 or dx sensor packages to it. To connec...

  • Page 60

    Chapter 4: connecting external equipment (optional) 42 2. The cable has two rj-12 sensor ports. Connect dpx sensor packages to the cable's sensor ports. 3. Repeat the above steps if there are additional sensor ports on your px2..

  • Page 61

    Chapter 4: connecting external equipment (optional) 43 supported maximum dpx sensor distances when connecting the following dpx sensor packages to the px2, you must follow two restrictions. • dpx-cc2-tr • dpx-t1 • dpx-t3h1 • dpx-af1 • dpx-t1dp1 sensor connection restrictions: • connect a dpx sensor ...

  • Page 62

    Chapter 4: connecting external equipment (optional) 44 dpx2 sensor packages a dpx2 sensor cable is shipped with a dpx2 sensor package. This cable is made up of one rj-12 connector and one to three head connectors. You have to connect dpx2 sensor packages to the sensor cable. For more information on ...

  • Page 63

    Chapter 4: connecting external equipment (optional) 45 the following procedure illustrates a dpx2 sensor cable with three head connectors. Your sensor cable may have fewer head connectors. Warning: if there are free head connectors between a dpx2 sensor cable's rj-12 connector and the final attached...

  • Page 64

    Chapter 4: connecting external equipment (optional) 46 or you can directly connect the dpx2 sensor package to a dx sensor chain without using any rj-12 to rj-45 adapter. See connecting a dpx2 sensor package to dx (on page 50). Note: if your px2 has "two" rj-12 sensor ports, see guidelines for px2 wi...

  • Page 65

    Chapter 4: connecting external equipment (optional) 47 repeat the same steps to cascade more dpx3 sensor packages. 3. Connect the first dpx3 sensor package to the px2. Plug the adapter cable's rj-12 connector into the rj-12 sensor port on the px2. Note: if your px2 has "two" rj-12 sensor ports, see ...

  • Page 66

    Chapter 4: connecting external equipment (optional) 48 when connecting a dpx2 sensor package containing two dpx2 sensors: a maximum of ten dpx3 sensor packages can be cascaded because 12-2=10. When connecting a dpx2 sensor package containing one dpx2 sensor: a maximum of eleven dpx3 sensor packages ...

  • Page 67

    Chapter 4: connecting external equipment (optional) 49 dx sensor packages most dx sensor packages contain terminals for connecting detectors or actuators. For information on connecting actuators or detectors to dx terminals, refer to the environmental sensors guide or online help on raritan website'...

  • Page 68

    Chapter 4: connecting external equipment (optional) 50 a. Plug one end of the cable into the remaining rj-45 port on the prior dx package. B. Plug the other end into either rj-45 port on an additional dx package. Repeat the same steps to cascade more dx packages. 3. Connect the first dx sensor packa...

  • Page 69

    Chapter 4: connecting external equipment (optional) 51 when connecting a dpx2 sensor package containing two dpx2 sensors: a maximum of ten dx sensor packages can be cascaded because 12-2=10. When connecting a dpx2 sensor package containing one dpx2 sensor: a maximum of eleven dx sensor packages can ...

  • Page 70

    Chapter 4: connecting external equipment (optional) 52 2. Connect the raritan sensor packages to any of the four out ports on the hub. An rj-12 to rj-45 adapter is required for connecting a dpx or dpx2 sensor package to the hub. This diagram illustrates a configuration with a sensor hub connected. T...

  • Page 71

    Chapter 4: connecting external equipment (optional) 53 mixing diverse sensor types you can mix dpx, dpx2, dpx3 and dx sensor packages on one px2 according to the following sensor combinations. In some scenarios, the dpx3-envhub4 sensor hub is required. The px2 does not support any other sensor-mixin...

  • Page 72

    Chapter 4: connecting external equipment (optional) 54 • an rj-12 to rj-45 adapter is recommended to connect a dpx or dpx2 sensor package to dpx3-envhub4. • in the following diagrams, the sensor package in "green" can be replaced by a dpx2 sensor package. The sensor package in "blue" can be one dpx2...

  • Page 73

    Chapter 4: connecting external equipment (optional) 55.

  • Page 74

    Chapter 4: connecting external equipment (optional) 56 mix dpx3 and dx in a sensor chain: any dx sensor package in a chain can be replaced by a dpx3 sensor package, or vice versa. The total number of sensor packages in this chain cannot exceed 12. For example, the following diagram shows a sensor ch...

  • Page 75

    Chapter 4: connecting external equipment (optional) 57 guidelines for px2 with two sensor ports you cannot simultaneously connect raritan environmental sensor packages to both sensor ports of the px2 models with "two" sensor ports, unless only dpx sensor packages are connected. Dpx sensor packages: ...

  • Page 76

    Chapter 4: connecting external equipment (optional) 58 a dpx3 or dx sensor chain sensor-mixing connections: • the px2 with "two" sensor ports supports the sensor-mixing combinations listed in the section titled mixing diverse sensor types (on page 53). • you can connect the sensor-mixing combination...

  • Page 77

    Chapter 4: connecting external equipment (optional) 59 combining regular asset strips each tag port on the regular asset strips corresponds to a rack unit and can be used to locate it devices in a specific rack (or cabinet). For each rack, you can attach asset strips up to 64u long, consisting of on...

  • Page 78

    Chapter 4: connecting external equipment (optional) 60 make sure that the u-shaped sheet metal adjacent to the male din connector is inserted into the rear slot of the master strip. Screw up the u-shaped sheet metal to reinforce the connection. 2. Connect another 8u slave strip to the one being atta...

  • Page 79

    Chapter 4: connecting external equipment (optional) 61 introduction to asset tags you need both asset strips and asset tags for tracking it devices. Asset tags provide an id number for each it device. The asset tags are adhered to an it device at one end and plugged in to an asset strip at the other...

  • Page 80

    Chapter 4: connecting external equipment (optional) 62 2. Plug the connector of each asset tag into the corresponding tag port on the asset strip. Note: if an it device occupies more than one rack unit in the rack, it is suggested to plug the asset tag into the lowest tag port. For example, if a dev...

  • Page 81

    Chapter 4: connecting external equipment (optional) 63 (a) master asset strip (b) asset tags (c) it devices (d) raritan x cable.

  • Page 82

    Chapter 4: connecting external equipment (optional) 64 tip: to connect raritan's environmental sensor packages to px2, connect them to the female rj-12 connector of the x cable. For details, see using an x cable (on page 70). The px2 device supplies power to the connected asset strip assembly. All l...

  • Page 83

    Chapter 4: connecting external equipment (optional) 65 a barcode (id number) for the tag connector cable b tag connector c cable connector for connecting the blade extension strip note: a tag connector cable has a unique barcode, which is displayed in the px2 device's web interface for identifying e...

  • Page 84

    Chapter 4: connecting external equipment (optional) 66 2. Move the blade extension strip toward the bottom of the blade chassis until its mylar section is fully under the chassis, and verify that the blade extension strip does not fall off easily. If necessary, you may use the adhesive tape in the b...

  • Page 85

    Chapter 4: connecting external equipment (optional) 67 5. Plug the tag connector of the blade extension strip into the closest tag port of the regular or composite asset strip on the rack. 6. Repeat the above steps to connect additional blade extension strips. Up to 128 asset tags on blade extension...

  • Page 86

    Chapter 4: connecting external equipment (optional) 68 a two rj-45 connectors b tag ports to connect composite asset strips to the px2 device: 1. Connect a composite asset strip to the px2 device via a standard network patch cable (cat5e or higher). A. Connect one end of the cable to the rj-45 port ...

  • Page 87

    Chapter 4: connecting external equipment (optional) 69 e. It is highly recommended using the cable ties to help hold the weight of all connecting cables. 4. Repeat step 2 to connect it devices to the other composite asset strips in the chain. Important: different types of composite asset strips can ...

  • Page 88

    Chapter 4: connecting external equipment (optional) 70 tip: to increase the maximum number of composite asset strips attached to a raritan px2 pdu, emx2-111 or bcm1, use raritan's x cable to enhance the power supply to the asset strip chain. See using an x cable (on page 70). Important: different ty...

  • Page 89

    Chapter 4: connecting external equipment (optional) 71 2. Plug the male rj-12 phone connector at the shorter end of the x cable into the rj-12 sensor port on the px2 device. This step is required for enhancing the power supply to asset strips. 3. Plug the male rj-45 connector at the longer end of th...

  • Page 90

    Chapter 4: connecting external equipment (optional) 72 4. Connect any raritan environmental sensor package or sensor hub to the female rj-12 sensor port of the x cable if environmental sensor packages are needed. Note that a dx or dpx3 sensor requires an rj-12 to rj-45 adapter to connect the x cable...

  • Page 91

    Chapter 4: connecting external equipment (optional) 73 connecting a logitech webcam connect webcams to px2 in order to view videos or snapshots of the webcam's surrounding area. The following usb video class (uvc) compliant webcam is supported: • logitech ® webcam ® pro 9000, model 960-000048 other ...

  • Page 92

    Chapter 4: connecting external equipment (optional) 74 connecting a gsm modem the following cinterion ® gsm modems can be connected to the px2 in order to send sms messages containing event information. • mc52it • mc55it • ehs6 see available actions (on page 252) for more information on sms messages...

  • Page 93

    Chapter 4: connecting external equipment (optional) 75 you need to enable the modem dial-in support to take advantage of this feature, see configuring the serial port (on page 289). Connecting an external beeper the px2 supports the use of an external beeper for audio alarms. External beepers that a...

  • Page 94

    76 this chapter explains how to use the px2 device, including: • introduction to the leds and ports on the pdu • operation of the front panel display • the overcurrent protector's behavior • the internal beeper's behavior • the reset button in this chapter panel components .............................

  • Page 95

    Chapter 5: introduction to pdu components 77 px2-1000 series these models are not outlet-switching capable so all outlets are always in the on state. Outlet leds are not available. Px2-2000 series these models are outlet-switching capable. A small led is adjacent to each outlet to indicate the state...

  • Page 96

    Chapter 5: introduction to pdu components 78 1u and 2u port locations the difference between zero u, 1u and 2u models is that zero u models have all the connection ports located on the front panel while 1u and 2u models have the ports located respectively on the front and back panels. In addition, m...

  • Page 97

    Chapter 5: introduction to pdu components 79 port used for... Console/ modem (db9) establishing a serial connection between the px2 and a computer or modem. This is a standard dte rs-232 port. You can use a null-modem cable with two db9 connectors on both ends to connect the px2 to the computer. Sen...

  • Page 98

    Chapter 5: introduction to pdu components 80 led display the led display is located on the side where outlets are available. These diagrams show the led display on different types of pdus. Note that the led display might slightly vary according to the pdu you purchased. Zero u models: 1u models: 2u ...

  • Page 99

    Chapter 5: introduction to pdu components 81 the led display consists of: • a row displaying three digits • a row displaying two digits • up and down buttons • five leds for measurement units a zero u model can detect its own orientation through the built-in tilt sensor and automatically changes the...

  • Page 100

    Chapter 5: introduction to pdu components 82 leds for measurement units five small led indicators are on the led display: four measurement units leds and one sensor led. The measurement units vary according to the readings that appear in the three-digit row. They are: • amp (a) for current • volt (v...

  • Page 101

    Chapter 5: introduction to pdu components 83 • ap: this indicates the selected inlet's active power. • ul: this represents the selected inlet or outlet's unbalanced load, which is only available for a three-phase pdu. • ix: this refers to the selected inlet on a multi-inlet pdu, where x is the inlet...

  • Page 102

    Chapter 5: introduction to pdu components 84 manual mode you can press the up or down button to enter the manual mode so that a particular line or circuit breaker can be selected to show specific readings. In addition, you can select a particular inlet if your pdu has more than one inlet. Each inlet...

  • Page 103

    Chapter 5: introduction to pdu components 85 when the active power is displayed, the power(kw) led is lit. Note: the led display returns to the automatic mode after 20 seconds elapse since the last time any button was pressed. Reset button the reset button is located inside the small hole near the d...

  • Page 104

    Chapter 5: introduction to pdu components 86 resetting the button-type circuit breaker your button-type circuit breakers may look slightly different from the images shown in this section, but the reset procedure remains the same. To reset the button-type breakers: 1. Locate the breaker whose on butt...

  • Page 105

    Chapter 5: introduction to pdu components 87 3. Examine your px2 and the connected equipment to remove or resolve the cause that results in the overload or short circuit. This step is required, or you cannot proceed with the next step. 4. Pull up the operating handle until the colorful rectangle or ...

  • Page 106

    Chapter 5: introduction to pdu components 88 fuse replacement on zero u models this section only applies to a zero u pdu with "replaceable" fuses. To replace a fuse on zero u models: 1. Lift the hinged cover over the fuse. 2. Verify the new fuse's rating against the rating specified in the fuse hold...

  • Page 107

    Chapter 5: introduction to pdu components 89 4. Take the fuse out of the holder. 5. Insert a new fuse into the holder. There is no orientation limit for fuse insertion. 6. Close the fuse holder and the hinged cover in a reverse order. Fuse replacement on 1u models on the 1u model, a fuse is installe...

  • Page 108

    Chapter 5: introduction to pdu components 90 3. Remove the original fuse from this knob, and insert either end of a new one into the knob. Make sure the new fuse's rating is the same as the original one. Number description fuse knob fuse 4. Install this knob along with the new fuse into the fuse car...

  • Page 109

    Chapter 5: introduction to pdu components 91 6. Connect the pdu's power cord to the power source and verify that the corresponding fuse led is lit, indicating that the fuse works properly. Beeper the px2 includes an internal beeper to issue an audible alarm for an overcurrent protector which is open...

  • Page 110

    92 this chapter explains how to use the web interface to administer a px2. In this chapter supported web browsers ........................................................................... 92 login, logout and password change ........................................................ 92 web interface...

  • Page 111

    Chapter 6: using the web interface 93 login you must enable javascript in the web browser for proper operation. To log in to the web interface: 1. Open a browser and type the ip address of the px2. If the link-local addressing has been enabled, you can type pdu.Local instead of an ip address. See ap...

  • Page 112

    Chapter 6: using the web interface 94 note: the address to access a slave device in the port forwarding mode via non-standard ports is a combination of a protocol (http:// or https://), an ip address and a port number. See port forwarding examples (on page 199). Changing your password you must have ...

  • Page 113

    Chapter 6: using the web interface 95 remembering user names and passwords the px2 supports the password manager of common web browsers, including: • microsoft internet explorer ® • mozilla firefox ® • google chrome ® you can save the login name and password when these browsers ask whether to rememb...

  • Page 114

    Chapter 6: using the web interface 96 4. To return to the main menu and the dashboard page, click on the top-left corner. Number web interface element menu (on page 98) data/setup page of the selected menu item left side: - px2 device name.

  • Page 115

    Chapter 6: using the web interface 97 number web interface element note: to customize the device name, see pdu (on page 111). Right side: - your login name, which you can click to view your user account settings - logout button from top to bottom -- your px2 model current firmware version online doc...

  • Page 116

    Chapter 6: using the web interface 98 menu depending on your model and hardware configuration, your px2 may show all or some menu items shown below. Menu information shown dashboard summary of the px2 status, including a list of alerted sensors and alarms, if any. See dashboard (on page 101). Pdu de...

  • Page 117

    Chapter 6: using the web interface 99 menu information shown ocps the ocps menu item appears only when there are overcurrent protectors implemented on your model. Ocp status and settings, such as ocp thresholds. See ocps (on page 133). Peripherals status and settings of raritan environmental sensor ...

  • Page 118

    Chapter 6: using the web interface 100 if a menu item contains the submenu, the submenu is shown after clicking that item. To return to the previous menu list, do any below: • click the topmost link with the symbol >. For example, click . • press backspace on the keyboard. • or click on the top-left...

  • Page 119

    Chapter 6: using the web interface 101 2. To have it resorted in the descending order based on the same column, click the timestamp header. 3. The arrow turns to , indicating the list is sorted in the "descending" order. 4. To resort the list based on a different column, click a different column hea...

  • Page 120

    Chapter 6: using the web interface 102 number section information shown inlet i1 overview of inlet power data a current bar per phase, which changes colors to indicate the rms current state - green: normal - yellow: warning - red: critical see dashboard - inlet i1 (on page 103). Overcurrent protecto...

  • Page 121

    Chapter 6: using the web interface 103 dashboard - inlet i1 the number of phases shown in the inlet section varies, depending on the model. Link to the inlet page: to view more information or configure the inlet(s), click this section's title 'inlet i1' to go to the inlet page. See inlet (on page 11...

  • Page 122

    Chapter 6: using the web interface 104 left side - generic inlet power data: the left side lists all or some of the following data. Available data is model dependent. • active power (kw or w) • apparent power (kva or va) • active energy (kwh or wh) • power factor • line frequency (hz) - model depend...

  • Page 123

    Chapter 6: using the web interface 105 dashboard - ocp availability and total number of ocps depend on the models. Each ocp's link: to view more information or configure individual ocps, click the desired ocp's index number, which is c1, c2 and the like, to go to its setup page. Each ocp's power dat...

  • Page 124

    Chapter 6: using the web interface 106 dashboard - alerted sensors when any internal sensors or environmental sensor packages connected to the px2 enter an abnormal state, the alerted sensors section in the dashboard show them for alerting users. This section also lists tripped circuit breakers or b...

  • Page 125

    Chapter 6: using the web interface 107 • 1 warned: 1 'numeric' sensor enters the warning state. List of alerted sensors: two icons are used to indicate various sensor states. Icons sensor states for numeric sensors: above upper warning below lower warning for numeric sensors: above upper critical be...

  • Page 126

    Chapter 6: using the web interface 108 dashboard - inlet history the power waveform for the inlet helps you observe whether there were abnormal events within the past tens of minutes. The default is to show the inlet's active power data. You can have it show the waveform of other inlet power data. S...

  • Page 127

    Chapter 6: using the web interface 109 inlet selection on multi-inlet models: if your pdu is a multi-inlet model, you can have one or multiple inlets show their power waveforms by selecting the checkbox(es) of the desired inlet(s). When multiple inlets are displayed, their waveform colors differ. Yo...

  • Page 128

    Chapter 6: using the web interface 110 this table explains each column of the alarms list. Field description name the customized name of the alarm action. Reason the first event that triggers the alert. First appearance the date and time when the event indicated in the reason column occurred for the...

  • Page 129

    Chapter 6: using the web interface 111 pdu the px2 device's generic information and pdu-level global settings are available on the pdu page. To open the pdu page, click 'pdu' in the menu (on page 98). Device information shown: • firmware version • serial number • mac address • rating • internal beep...

  • Page 130

    Chapter 6: using the web interface 112 field function note name customizes the device name. *outlet state on device startup determines the initial power state of all outlets after the px2 device powers up. Options: on, off, and last known see options for outlet state on startup (on page 115). After ...

  • Page 131

    Chapter 6: using the web interface 113 field function note peripheral device auto management enables or disables the automatic management feature for raritan environmental sensor packages. The default is to enable it. See how the automatic management function works (on page 117). Altitude specifies ...

  • Page 132

    Chapter 6: using the web interface 114 tip: you can choose to reset the active energy reading of an individual inlet only. See inlet (on page 119). To view total active energy and power on multi-inlet models: if your px2 is a multi-inlet model, a "power" section for showing the data of total active ...

  • Page 133

    Chapter 6: using the web interface 115 states description "activation reason" is displayed, indicating why the beeper sounds an alarm. For example, if the beeper is turned on because of a specific event rule "xxx," the activation reason looks like: event action triggered by rule: xxx scenarios when ...

  • Page 134

    Chapter 6: using the web interface 116 initialization delay use cases apply the initialization delay in either of the following scenarios. • when power may not initially be stable after being restored • when ups batteries may be charging tip: when there are a large number of outlets, set the value t...

  • Page 135

    Chapter 6: using the web interface 117 how the automatic management function works this setting is configured on pdu (on page 111). After enabling the automatic management function: when the total number of managed sensors and actuators has not reached the upper limit yet, the px2 automatically brin...

  • Page 136

    Chapter 6: using the web interface 118 setting thresholds for total active energy or power this section applies only to multi-inlet models, including in-line monitors. Thresholds for total active energy and total active power are disabled by default. You can enable and set them so that you are alert...

  • Page 137

    Chapter 6: using the web interface 119 inlet you can view all inlet information, configure inlet-related settings, or reset the inlet active energy on the inlet page. To open this page, click 'inlet' in the menu (on page 98). Inlet thresholds, when enabled, help you identify whether the inlet enters...

  • Page 138

    Chapter 6: using the web interface 120 3. Click save. 4. The inlet's custom name is displayed on the inlet or dashboard page, followed by its label in parentheses. To reset the inlet's active energy counter: only users with the "admin" role assigned can reset active energy readings. The energy reset...

  • Page 139

    Chapter 6: using the web interface 121 4. Click save. Configuring a multi-inlet model if the px2 has more than one inlet, the inlets page lists all inlets. To view or configure each inlet: 1. Click 'show details' of the desired inlet. 2. Now you can configure the selected inlet, such as enabling thr...

  • Page 140

    Chapter 6: using the web interface 122 outlets the outlets page shows a list of all outlets and the overview of outlet status and readings. To open this page, click 'outlets' in the menu (on page 98). On this page, you can: • view all outlets' status. If any outlet sensor enters the alarmed state, i...

  • Page 141

    Chapter 6: using the web interface 123 • go to an individual outlet's data/setup page by clicking an outlet's name. See individual outlet pages (on page 128). If wanted, you can resort the list by clicking the desired column header. See sorting a list (on page 100). To show or hide specific columns ...

  • Page 142

    Chapter 6: using the web interface 124 to power control multiple outlets: you can switch any outlet regardless of its current power state. That is, you can turn on any outlet that is already turned on, or turn off any outlet that is already turned off. 1. Click to make checkboxes appear in front of ...

  • Page 143

    Chapter 6: using the web interface 125 if needed, click to stop the outlet-switching operation. Available data of the outlets overview page all of the following outlet data is displayed on the outlets overview page based on your selection. To show or hide specific data, click . See outlets (on page ...

  • Page 144

    Chapter 6: using the web interface 126 button function top up down bottom restores to the default sequence next time when power cycling the px2, it will turn on all outlets based on the new outlet order. The new order also applies when performing the power-on or power-cycling operation on partial ou...

  • Page 145

    Chapter 6: using the web interface 127 tip: you can also set up non-critical outlet setting by configuring outlets one by one. See individual outlet pages (on page 128). Load shedding mode when a ups supplying power to the px2 switches into battery backup operation, it may be desirable to switch off...

  • Page 146

    Chapter 6: using the web interface 128 the message "load shedding active" appears next to the 'outlets' title. Tip: to make the non critical column appear on the outlets page. See outlets (on page 122) or available data of the outlets overview page (on page 125). To exit from the load shedding mode:...

  • Page 147

    Chapter 6: using the web interface 129 the individual outlet's page shows this outlet's detailed information. See detailed information on outlet pages (on page 131). In addition, you can perform the following operations on this outlet page. Note that only outlet-switching capable models show the pow...

  • Page 148

    Chapter 6: using the web interface 130 to configure this outlet: 1. Click edit settings. 2. Configure available fields. Note that the fields marked with * are only available on outlet-switching capable models. Field descriptions name type an outlet name up to 32 characters long. *state on device sta...

  • Page 149

    Chapter 6: using the web interface 131 other operations: • you can go to another outlet's data/setup page by clicking the outlet selector on the top-left corner. • you can go to the associated inlet's or overcurrent protector's data pages by clicking the inlet or overcurrent protector links in the d...

  • Page 150

    Chapter 6: using the web interface 132 field description inlet this information is useful when there are multiple inlets on your pdu. Inlet associated with this outlet overcurrent protector this information is available only when your px2 has overcurrent protectors. Overcurrent protector associated ...

  • Page 151

    Chapter 6: using the web interface 133 ocps this page is available only when your px2 has overcurrent protectors, such as circuit breakers. The ocps page lists all overcurrent protectors as well as their status. If any ocp trips or its current level enters the alarmed state, it is highlighted in red...

  • Page 152

    Chapter 6: using the web interface 134 status bar colors normal above upper warning above upper critical note: the "below lower warning" and "below lower critical" states also show yellow and red colors respectively. However, it is not meaningful to enable these two thresholds for current levels. • ...

  • Page 153

    Chapter 6: using the web interface 135 individual ocp pages an ocp's data/setup page is opened after clicking any ocp's name on the ocps or dashboard page. See ocps (on page 133) or dashboard (on page 101). General ocp information: field description label this ocp's physical number status open or cl...

  • Page 154

    Chapter 6: using the web interface 136 to view this ocp's power waveform: this ocp's rms current data in waveform is shown in the overcurrent protector history section. To configure this ocp's threshold settings: 1. Click the thresholds title bar at the bottom of the page to display the threshold da...

  • Page 155

    Chapter 6: using the web interface 137 tip: to configure thresholds for multiple ocps at a time, see ocps (on page 133). Other operations: • you can go to another ocp's data/setup page by clicking the ocp selector on the top-left corner. • you can go to the associated inlet's data page by clicking t...

  • Page 156

    Chapter 6: using the web interface 138 peripherals if there are raritan environmental sensor packages connected to the px2, they are listed on the peripherals page. See connecting environmental sensor packages (on page 37). An environmental sensor package comprises one or some of the following senso...

  • Page 157

    Chapter 6: using the web interface 139 • go to an individual sensor's or actuator's data/setup page by clicking its name. If wanted, you can resort the list by clicking the desired column header. See sorting a list (on page 100). Sensor/actuator overview on this page: if any sensor enters the alarme...

  • Page 158

    Chapter 6: using the web interface 140 column description serial number this is the serial number printed on the sensor package's label. It helps to identify your raritan sensors/actuators. See finding the sensor's serial number (on page 147). Position the data indicates where this sensor or actuato...

  • Page 159

    Chapter 6: using the web interface 141 the management action triggers a "manage peripheral device" dialog. Simply click manage if you are managing multiple sensors/actuators. If you are managing only one sensor/actuator, you can choose to assign an id number by selecting "manually select a sensor nu...

  • Page 160

    Chapter 6: using the web interface 142 2. Click the desired sensor type (required), and then click edit thresholds. 3. Make changes as needed. To enable any threshold, select the corresponding checkbox. Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis...

  • Page 161

    Chapter 6: using the web interface 143 yellow- or red-highlighted sensors the px2 highlights those sensors that enter the abnormal state with a yellow or red color. Note that numeric sensors can change colors only after you have enabled their thresholds. Tip: when an actuator is turned on, it is als...

  • Page 162

    Chapter 6: using the web interface 144 sensor status color states shown in the interface description alarmed alarmed state sensors enter the abnormal state. Ocp alarm open circuit breaker trips. -- or -- fuse blown. If you have connected a schroff ® lhx/shx heat exchanger, when any sensor implemente...

  • Page 163

    Chapter 6: using the web interface 145 • they show one of the managed states. See sensor/actuator states (on page 145). • for managed 'numeric' sensors, their readings are retrieved and displayed. If any numeric sensor is disconnected or its reading cannot be retrieved, it shows "unavailable" for it...

  • Page 164

    Chapter 6: using the web interface 146 state description alarmed the state sensor enters the abnormal state. Unavailable the communication with the managed sensor is lost. -- or -- dpx2, dpx3 or dx sensor packages are upgrading their sensor firmware. Note that for a contact closure sensor, the norma...

  • Page 165

    Chapter 6: using the web interface 147 finding the sensor's serial number a dpx environmental sensor package includes a serial number tag on the sensor cable. A dpx2, dpx3 or dx sensor package has a serial number tag attached to its rear side. The serial number for each sensor or actuator appears li...

  • Page 166

    Chapter 6: using the web interface 148 identifying the sensor position and channel raritan has developed four types of environmental sensor packages - dpx, dpx2, dpx3 and dx series. Only dpx2, dpx3 and dx sensor packages can be daisy chained. The px2 can indicate where each sensor or actuator is con...

  • Page 167

    Chapter 6: using the web interface 149 example physical position port 1 connected to the sensor port #1. Port 1, channel 2 connected to the sensor port #1. The sensor/actuator is the 2nd channel of the sensor package. Port 1, chain position 4 connected to the sensor port #1. The sensor/actuator is l...

  • Page 168

    Chapter 6: using the web interface 150 2. The "manage peripheral device" dialog appears. To let the px2 randomly assign an id number to it, select "automatically assign a sensor number." this method does not release any managed sensor or actuator. To assign the desired id number to it, select "manua...

  • Page 169

    Chapter 6: using the web interface 151 however, only relative humidity sensors are "automatically" managed if the automatic management function is enabled. You must "manually" manage absolute humidity sensors as needed. Note that relative and absolute values of the same humidity sensor do not share ...

  • Page 170

    Chapter 6: using the web interface 152 2. Select or deselect use default thresholds according to your needs. To have this sensor follow the default threshold settings configured for its sensor type, select the use default thresholds checkbox. The default threshold settings are configured on the page...

  • Page 171

    Chapter 6: using the web interface 153 to set up a sensor's or actuator's physical location and additional settings: 1. Click edit settings. 2. Make changes to available fields, and then click save. Fields description binary sensor subtype this field is available for a contact closure sensor only. D...

  • Page 172

    Chapter 6: using the web interface 154 to view a numeric sensor's readings waveform: this sensor's data within the past tens of minutes is shown in the waveform diagram. Note that only a numeric sensor has this diagram. State sensors and actuators do not show such data. To turn on or off an actuator...

  • Page 173

    Chapter 6: using the web interface 155 2. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on. Other operations: you can go to another sensor's or actuators's data/setup page by clicking the selector on the top-left corner. Sensor/actuator loc...

  • Page 174

    Chapter 6: using the web interface 156 feature port the feature port supports connection to the following devices. Device description asset strip raritan asset strips external beeper an external beeper with the rj-45 socket. Lhx 20 schroff ® lhx-20 heat exchanger. Shx 30 schroff ® shx-30 heat exchan...

  • Page 175

    Chapter 6: using the web interface 157 when the px2 detects the connection of any listed device, it replaces 'feature port' in the menu with that device's name and shows that device's data/settings instead. See asset strip (on page 158), external beeper (on page 166), schroff lhx/shx (on page 167) a...

  • Page 176

    Chapter 6: using the web interface 158 mode description asset strip, raritan asset strips, lhx 20, shx 30, lhx 40, power cim force the px2 to show the selected device's data/setup page regardless of the physical connection status. Note: 'lhx 20', 'shx 30', and 'lhx 40' are not available when the sup...

  • Page 177

    Chapter 6: using the web interface 159 field description name name for this asset strip assembly. Number of rack units total of available tag ports on this asset strip assembly, ranging between 8 and 64. For the current generation of asset strips, which show the suffix "g3" on its hardware label, th...

  • Page 178

    Chapter 6: using the web interface 160 for color settings, there are two ways to set the color. Click a color in the color palette. Type the hexadecimal rgb value of the color, such as #00ff00. 3. Click ok. The rack unit numbering and led color settings are immediately updated on the rack units list...

  • Page 179

    Chapter 6: using the web interface 161 to customize a single rack unit's settings: you can make a specific rack unit's led behave differently from the others on the asset strip, including the led light and color. 1. Click the desired rack unit on the rack units list. The setup dialog for the selecte...

  • Page 180

    Chapter 6: using the web interface 162 field description led mode this field is configurable only after the operation mode is set to manual override. Determine how the led light behaves for this particular rack unit. On : the led stays lit. Off : the led stays off. Slow blinking : the led blinks slo...

  • Page 181

    Chapter 6: using the web interface 163 2. All tag ports of the blade extension strip are listed below it. Their port numbers are displayed in the slot column. To hide the blade extension slots list, click ..

  • Page 182

    Chapter 6: using the web interface 164 to customize asset ids on programmable asset tags: you can customize asset ids only when the asset tags are "programmable" ones. Non-programmable tags do not support this feature. In addition, you can also customize the id of a blade extension strip. If a barco...

  • Page 183

    Chapter 6: using the web interface 165 an asset id contains up to 12 characters that comprise only numbers and/or upper case alphabets. Lower case alphabets are not accepted. 3. Verify the correctness of customized asset ids and modify as needed. 4. Click apply at the bottom of the page or rack unit...

  • Page 184

    Chapter 6: using the web interface 166 asset strip automatic firmware upgrade after connecting the asset strip to the px2, it automatically checks its own firmware version against the version of the asset strip firmware stored in the px2 firmware. If two versions are different, the asset strip autom...

  • Page 185

    Chapter 6: using the web interface 167 schroff lhx/shx you must enable the lhx/shx support for the px2 to detect the presence of a supported schroff ® lhx/shx heat exchanger. See miscellaneous (on page 296). After enabling the lhx/shx support and connecting a supported schroff ® lhx/shx heat exchang...

  • Page 186

    Chapter 6: using the web interface 168 for the functionality of this icon on the top-right corner, see feature port (on page 156). To view the lhx/shx device state: the operation state field indicates whether the device is operating fine, and the switch state field indicates its power status. If the...

  • Page 187

    Chapter 6: using the web interface 169 tip: you can also create event rules to notify you of the warning or critical levels. See event rules and actions (on page 236). To view sensor alerts and lhx event log: remote alert acknowledgment is supported by the lhx-20 and lhx-40. The shx-30 does not supp...

  • Page 188

    Chapter 6: using the web interface 170 power cim after connecting and detecting a raritan power cim, the px2 shows 'power cim' in place of 'feature port' in the menu. See dominion kx ii / iii configuration (on page 618) or dominion ksx ii, sx or sx ii configuration (on page 623). Open the power cim ...

  • Page 189

    Chapter 6: using the web interface 171 creating users all users must have a user account, containing the login name and password. Multiple users can log in simultaneously using the same login name. To add users, choose user management > users > . Note that you must enter information in the fields sh...

  • Page 190

    Chapter 6: using the web interface 172 field/setting description force password change on next login when selected, a password change request automatically appears when next time the user logs in. For details, see changing your password (on page 94). Ssh: you need to enter the ssh public key only if...

  • Page 191

    Chapter 6: using the web interface 173 field/setting description password, confirm password type the authentication password if the 'same as user password' checkbox is deselected. The password must consist of 8 to 32 ascii printable characters. • privacy password: this section is configurable only w...

  • Page 192

    Chapter 6: using the web interface 174 field description length unit preferred units for length or height -- meter or feet. Pressure unit preferred units for pressure -- pascal or psi. Pascal = one newton per square meter psi = pounds per square inch note: users can change the measurement units at a...

  • Page 193

    Chapter 6: using the web interface 175 editing or deleting users to edit or delete users, choose user management > users to open the users page, which lists all users. In the enabled column: • : the user is enabled. • : the user is disabled. If wanted, you can resort the list by clicking the desired...

  • Page 194

    Chapter 6: using the web interface 176 creating roles a role is a combination of permissions. Each user must have at least one role. The px2 provides two built-in roles. The operator role is assigned to a newly-created user account per default. See creating users (on page 171). Built-in role descrip...

  • Page 195

    Chapter 6: using the web interface 177 5. To select any privilege requiring the argument setting, click to select the desired arguments. For example, on an outlet-switching capable model, you can specify the outlets that are allowed to be switched on/off for the 'switch outlet' privilege as shown be...

  • Page 196

    Chapter 6: using the web interface 178 tip: to delete only one role, you can simply click that user without making the checkboxes appear. See the above procedure. 2. Select one or multiple roles. To select all roles, except for the admin role, select the top-most checkbox in the header row. 3. Click...

  • Page 197

    Chapter 6: using the web interface 179 setting default measurement units default measurement units are applied to all px2 user interfaces across all users, including users accessing the px2 via external authentication servers. For a list of affected user interfaces, see user interfaces showing defau...

  • Page 198

    Chapter 6: using the web interface 180 device settings click 'device settings' in the menu (on page 98), and the following submenu displays. Menu command submenu command refer to... Network configuring network settings (on page 181) network services http changing http(s) settings (on page 204) snmp ...

  • Page 199

    Chapter 6: using the web interface 181 menu command submenu command refer to... Miscellaneous miscellaneous (on page 296) * the availability of "front panel" depends on the model. Configuring network settings configure wired, wireless, and internet protocol-related settings on the network page after...

  • Page 200

    Chapter 6: using the web interface 182 you must connect a usb wireless lan adapter to the px2 for wireless networking. Note: if the device's cascading mode is set to 'bridging' or its role is set to 'slave' in the port forwarding mode, the wireless settings will be disabled. 5. To configure the ethe...

  • Page 201

    Chapter 6: using the web interface 183 ipv4 settings: field/setting description enable ipv4 enable or disable the ipv4 protocol. Ip auto configuration select the method to configure ipv4 settings. Dhcp: auto-configure ipv4 settings via dhcp servers. Static: manually configure the ipv4 settings. • dh...

  • Page 202

    Chapter 6: using the web interface 184 common network settings common network settings are optional, not required. Therefore, leave them unchanged if there are no specific local networking requirements. Field description cascading mode leave it to the default "none" unless you are establishing a cas...

  • Page 203

    Chapter 6: using the web interface 185 ethernet interface settings by default the ethernet interface is enabled. Enable interface: make sure the ethernet interface is enabled, or all networking through this interface fails. This setting is available in the ethernet section, but not available in the ...

  • Page 204

    Chapter 6: using the web interface 186 wireless network settings if the device's cascading mode is set to 'bridging' or its role is set to 'slave' in the port forwarding mode, the wireless settings will be disabled. See setting the cascading mode (on page 195). By default the wireless interface is d...

  • Page 205

    Chapter 6: using the web interface 187 field/setting description identity this field appears only when 'eap - peap' is selected. Type your user name. Password this field appears only when 'eap - peap' is selected. Type your password. Ca certificate this field appears only when 'eap - peap' is select...

  • Page 206

    Chapter 6: using the web interface 188 field/setting description allow wireless connection if system clock is incorrect when this checkbox is deselected, and if the system time is incorrect, the installed tls certificate is considered not valid yet and will cause the wireless network connection to f...

  • Page 207

    Chapter 6: using the web interface 189 • automatic settings: optionally specify the preferred hostname, which must meet the above requirements. • static settings: assign a static ipv6 address, which follows this syntax "ip address/prefix length". Example: fd07:2fa:6cff:1111::0/128 (optional) to view...

  • Page 208

    Chapter 6: using the web interface 190 2. Click clear log on the confirmation message..

  • Page 209

    Chapter 6: using the web interface 191 static route examples this section describes two static route examples: ipv4 and ipv6. Both examples assume that two network interface controllers (nic) have been installed in one network server, leading to two available subnets, and ip forwarding has been enab...

  • Page 210

    Chapter 6: using the web interface 192 in this example, nic-2 (192.168.100.88) is the next hop router for your px2 to communicate with any device in the other subnet 192.168.200.0. In the ipv4 "static routes" section, you should specify:.

  • Page 211

    Chapter 6: using the web interface 193 tip: if you have configured multiple static routes, you can click on any route and then make changes, use or to re-sort the priority, or click to delete it. Ipv6 example: • your px2: fd07:2fa:6cff:2405::30 • two nics: fd07:2fa:6cff:1111::50 and fd07:2fa:6cff:24...

  • Page 212

    Chapter 6: using the web interface 194 in this example, nic-2 (fd07:2fa:6cff:2405::80) is the next hop router for your px2 to communicate with any device in the other subnet fd07:2fa:6cff:1111::0. In the ipv6 "static routes" section, you should specify: tip: if you have configured multiple static ro...

  • Page 213

    Chapter 6: using the web interface 195 setting the cascading mode a maximum of 16 px2 devices can be cascaded to share one ethernet connection. See cascading multiple px2 devices for sharing ethernet connectivity (on page 33). The cascading mode configured on the master device determines the etherne...

  • Page 214

    Chapter 6: using the web interface 196 downstream interface: usb or ethernet. This is to determine which port of the master device is connected to slave 1. Always select usb. 6. Now you can configure the network settings. Bridging mode: click the bridge section on the same page. Port forwarding mode...

  • Page 215

    Chapter 6: using the web interface 197 • "bridging" mode: in this mode, the dhcp server communicates with every cascaded device respectively and assigns four different ip addresses. Each device has its own ip address. The way to remotely access each cascaded device is completely the same as accessin...

  • Page 216

    Chapter 6: using the web interface 198 port number syntax in the port forwarding mode, all devices in the usb-cascading configuration share the same ip address. To access any cascaded device, you must assign an appropriate port number to it. • master device: the port number is either 5nnxx or the st...

  • Page 217

    Chapter 6: using the web interface 199 for example, to access the slave 4 device via modbus/tcp, the port number is 50604. See port forwarding examples (on page 199) for further illustrations. Tip: the full list of each cascaded device's port numbers can be retrieved from the web interface. Choose m...

  • Page 218

    Chapter 6: using the web interface 200 protocols port numbers http 50100 ssh 50200 telnet 50300 snmp 50500 modbus 50600 examples using "5nn00" ports: • to access the master device via https, the ip address is: https://192.168.84.77:50000/ • to access the master device via http, the ip address is: ht...

  • Page 219

    Chapter 6: using the web interface 201 examples: • to access slave 1 via https, the ip address is: https://192.168.84.77:50001/ • to access slave 1 via http, the ip address is: http://192.168.84.77:50101/ • to access slave 1 via ssh, the command is: ssh -p 50201 192.168.84.77 slave 2 device: positio...

  • Page 220

    Chapter 6: using the web interface 202 adding, removing or swapping cascaded devices change the cascading mode first before adding any device to a cascading chain, or before disconnecting a cascaded device from the chain. If you only want to change the cascading mode of an existing chain, or swap th...

  • Page 221

    Chapter 6: using the web interface 203 to change the cascading mode applied to a chain: 1. Access the last slave device, and change its cascading mode. If the new cascading mode is 'port forwarding', you must also set its role to 'slave'. 2. Access the second to last, third to last and so on until t...

  • Page 222

    Chapter 6: using the web interface 204 changing http(s) settings https uses transport layer security (tls) technology to encrypt all traffic to and from the px2 so it is a more secure protocol than http. The px2 supports tls 1.0 , 1.1 and 1.2 . By default, any access to the px2 via http is automatic...

  • Page 223

    Chapter 6: using the web interface 205 configuring snmp settings you can enable or disable snmp communication between an snmp manager and the px2 device. Enabling snmp communication allows the manager to retrieve and even control the power status of each outlet. Besides, you may need to configure th...

  • Page 224

    Chapter 6: using the web interface 206 a. Click the download mibs title bar to show the download links. B. Click the pdu2-mib download link. See downloading snmp mib (on page 325). 6. Click save. Configuring smtp settings the px2 can be configured to send alerts or event messages to a specific admin...

  • Page 225

    Chapter 6: using the web interface 207 field description user name, password type a user name and password for authentication after selecting the above checkbox. The length of user name and password ranges between 4 and 64. Case sensitive. Spaces are not allowed for the user name, but allowed for th...

  • Page 226

    Chapter 6: using the web interface 208 special note for aes ciphers: the px2 device's ssl/tls-based protocols, including smtp over starttls, support aes 128- and 256-bit ciphers. The exact cipher to use is negotiated between the px2 and the client (such as a web browser), which is impacted by the ci...

  • Page 227

    Chapter 6: using the web interface 209 3. To use a different port, type a new port number. 4. Click save. Changing modbus settings you can enable or disable the modbus/tcp access to the px2, set it to the read-only mode, or change the tcp port. To change the modbus/tcp settings: 1. Choose device set...

  • Page 228

    Chapter 6: using the web interface 210 enabling service advertising the px2 advertises all enabled services that are reachable using the ip network. This feature uses dns-sd (domain name system-service discovery) and mdns (multicast dns). The advertised services are discovered by clients that have i...

  • Page 229

    Chapter 6: using the web interface 211 configuring security settings the px2 provides tools to control access. You can enable the internal firewall, create firewall rules, and set login limitations. In addition, you can create and install the certificate or set up external authentication servers for...

  • Page 230

    Chapter 6: using the web interface 212 note: valid ipv4 addresses range from 0.0.0.0 through 255.255.255.255. To configure ipv4 access control rules: 1. Choose device settings > security > ip access control. 2. Select the enable ipv4 access control checkbox to enable ipv4 access control rules. 3. De...

  • Page 231

    Chapter 6: using the web interface 213 you can select any existing rule and then click or to change its priority. 7. Click save. The rules are applied. To configure ipv6 access control rules: 1. On the same page, select the enable ipv6 access control checkbox to enable ipv6 access control rules. 2. ...

  • Page 232

    Chapter 6: using the web interface 214 creating role access control rules role-based access control rules are similar to ip access control rules, except they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their ip addresses. Same ...

  • Page 233

    Chapter 6: using the web interface 215 insert a rule between two rules select the rule above which you want to insert a new rule. For example, to insert a rule between rules #3 and #4, select #4. Click insert above. Type a starting ip address in the start ip field. Type an ending ip address in the e...

  • Page 234

    Chapter 6: using the web interface 216 click to remove it. To resort its order, click or . 5. Click save. Ipv4 rules: make sure you click the save button in the ipv4 section, or the changes made to ipv4 rules are not saved. Ipv6 rules: make sure you click the save button in the ipv6 section, or the ...

  • Page 235

    Chapter 6: using the web interface 217 creating a csr follow this procedure to create the csr for your px2 device. Note that you must enter information in the fields showing the message 'required.' to create a csr: 1. Choose device settings > security > ssl certificate. 2. Provide the information re...

  • Page 236

    Chapter 6: using the web interface 218 field do this challenge, confirm challenge type a password. The password is used to protect the certificate or csr. This information is optional. The value should be 4 to 64 characters long. Case sensitive. 3. Click create new ssl key to create both the csr and...

  • Page 237

    Chapter 6: using the web interface 219 creating a self-signed certificate when appropriate certificate and key files for the px2 device are unavailable, the alternative, other than submitting a csr to the ca, is to generate a self-signed certificate. Note that you must enter information in the field...

  • Page 238

    Chapter 6: using the web interface 220 4. Once complete, do the following: a. Double check the data shown in the new ssl certificate section. B. If correct, click "install key and certificate" to install the self-signed certificate and private key. Tip: to verify whether the certificate has been ins...

  • Page 239

    Chapter 6: using the web interface 221 to install available key and certificate files onto the px2: 1. Choose device settings > security > ssl certificate. 2. Select the "upload key and certificate" checkbox at the bottom of the page. 3. The key file and certificate file fields appear. Click to sele...

  • Page 240

    Chapter 6: using the web interface 222 for security purposes, users attempting to log in to the px2 must be authenticated. The px2 supports the following authentication mechanisms: • local user database on the px2 • lightweight directory access protocol (ldap) • remote access dial-in user service (r...

  • Page 241

    Chapter 6: using the web interface 223 special note about the aes cipher: the px2 device's ssl/tls-based protocols, including ldaps, support aes 128- and 256-bit ciphers. The exact cipher to use is negotiated between the px2 and the client (such as a web browser), which is impacted by the cipher pri...

  • Page 242

    Chapter 6: using the web interface 224 if using a microsoft active directory server, consult your ad administrator for the name of the active directory domain. • bind distinguished name (dn) and password (if anonymous bind is not used) • the base dn of the server (used for searching for users) • the...

  • Page 243

    Chapter 6: using the web interface 225 field/setting description type of ldap server choose one of the following options: openldap microsoft active directory. Active directory is an implementation of ldap/ldaps directory services by microsoft for use in windows environments. Security determine wheth...

  • Page 244

    Chapter 6: using the web interface 226 field/setting description bind dn required after deselecting the anonymous bind checkbox. Distinguished name (dn) of the user who is permitted to search the ldap directory in the defined search base. Bind password, confirm bind password required after deselecti...

  • Page 245

    Chapter 6: using the web interface 227 to duplicate ldap/ldaps server settings: if you have added any ldap/ldaps server to the px2, and the server you will add shares identical settings with an existing one, the most convenient way is to duplicate that ldap/ldaps server's data and then revise the ip...

  • Page 246

    Chapter 6: using the web interface 228 field/setting description authentication port, accounting port the default are standard ports -- 1812 and 1813. To use non-standard ports, type a new port number. Timeout this sets the maximum amount of time to establish contact with the radius server before ti...

  • Page 247

    Chapter 6: using the web interface 229 managing external authentication settings choose device settings > security > authentication to open the authentication page, where you can: • enable both the external and local authentication • edit or delete a server • resort the access order of servers • tes...

  • Page 248

    Chapter 6: using the web interface 230 2. Select the following checkbox. Then the px2 always tries external authentication first. Whenever the external authentication fails, the px2 switches to local authentication. 3. Click save. To disable external authentication: 1. In the authentication type, se...

  • Page 249

    Chapter 6: using the web interface 231 tip: if any user blocking event occurs, you can unblock that user manually by using the "unblock" cli command over a local connection. See unblocking a user (on page 488). To set limitations for login timeout and use of identical login names: 1. In the "idle ti...

  • Page 250

    Chapter 6: using the web interface 232 to force users to create strong passwords: 1. Select the 'enabled' checkbox of strong passwords to activate the strong password feature. The following are the default settings: minimum length = 8 characters maximum length = 32 characters at least one lowercase ...

  • Page 251

    Chapter 6: using the web interface 233 login manner after enabling the service agreement: after the restricted service agreement feature is enabled, the agreement's content is displayed in the login screen. Do either of the following, or the login fails: • in the web interface, select the checkbox l...

  • Page 252

    Chapter 6: using the web interface 234 customize the date and time select user specified time. Type values in the date field using the yyyy-mm-dd format, or click to select a date. For details, see calendar (on page 234). Type values in the time field using the hh:mm:ss format, or click to adjust va...

  • Page 253

    Chapter 6: using the web interface 235 button function dates (01-31) click a date. Today select today. Clear clear the entry, if any, in the date field. Close close the calendar. Windows ntp server synchronization solution the ntp client on the px2 follows the ntp rfc so the px2 rejects any ntp serv...

  • Page 254

    Chapter 6: using the web interface 236 event rules and actions a benefit of the product's intelligence is its ability to notify you of or react to a change in conditions. This event notification or reaction is an "event rule." an event rule consists of two parts: • event: this is the situation where...

  • Page 255

    Chapter 6: using the web interface 237 note: when creating scheduled actions, available actions are less than usual because it is meaningless to schedule certain actions like "alarm," "log event message," "send email," "syslog message" and the like. 2. Click to schedule the desired action. A. Assign...

  • Page 256

    Chapter 6: using the web interface 238 event rule configuration illustration: 1. Choose device settings > event rules > . 2. Click the event field to select an event type. Means all events shown on the list. Means all numeric sensors of the px2, including internal and environmental sensors. Sensor> ...

  • Page 257

    Chapter 6: using the web interface 239 6. In this example, 'above upper critical threshold' is selected because we want the px2 to react only when the selected temperature sensor's reading enters the upper critical range. A "trigger condition" field appears, requiring you to define the "exact" condi...

  • Page 258

    Chapter 6: using the web interface 240 radio buttons for different events: according to the event you select, the "trigger condition" field containing three radio buttons may or may not appear. Event types radio buttons numeric sensor threshold-crossing events, or the occurrence of the selected even...

  • Page 259

    Chapter 6: using the web interface 241 event types radio buttons network interface link state link state is up: the px2 takes the action only when the network link state changes from down to up. Link state is down: the px2 takes the action only when the network link state changes from up to down. Bo...

  • Page 260

    Chapter 6: using the web interface 242 event types radio buttons server reachability unreachable: the px2 takes the action only when any specified server becomes inaccessible. Reachable: the px2 takes the action only when any specified server becomes accessible. Both: the px2 takes the action when a...

  • Page 261

    Chapter 6: using the web interface 243 event/context default message when the event = true default message when the event = false asset management > firmware update firmware update for asset strip [stripid] ('[stripname]'): status changed to '[state]'. Asset management > device config changed config...

  • Page 262

    Chapter 6: using the web interface 244 event/context default message when the event = true default message when the event = false device > firmware update started firmware upgrade started from version '[oldversion]' to version '[version]' by user '[username]' from host '[userip]'. Device > firmware ...

  • Page 263

    Chapter 6: using the web interface 245 event/context default message when the event = true default message when the event = false device > sending snmp inform failed or no response sending snmp inform to manager [snmpmanager]:[snmpmanagerp ort] failed or no response. [errordesc]. Device > sending sy...

  • Page 264

    Chapter 6: using the web interface 246 event/context default message when the event = true default message when the event = false peripheral device slot > * > numeric sensor > below lower warning threshold peripheral device '[extsensorname]' in slot '[extsensorslot]' asserted 'below lower warning' a...

  • Page 265

    Chapter 6: using the web interface 247 event/context default message when the event = true default message when the event = false modem > dial-in link established an incoming call from caller '[callerid]' was received. The incoming call from caller '[callerid]' was disconnected: [callendreason]. Mod...

  • Page 266

    Chapter 6: using the web interface 248 event/context default message when the event = true default message when the event = false outlet > * > pole > * > sensor > unavailable sensor '[polesensor]' on pole '[outletpole]' of outlet '[outlet]' unavailable. Sensor '[polesensor]' on pole '[outletpole]' o...

  • Page 267

    Chapter 6: using the web interface 249 event/context default message when the event = true default message when the event = false pdu > load shedding > started px placed in load shedding mode by user '[username]' from host '[userip]'. Px removed from load shedding mode by user '[username]' from host...

  • Page 268

    Chapter 6: using the web interface 250 event/context default message when the event = true default message when the event = false user administration > role added role '[targetrole]' added by user '[username]' from host '[userip]'. User administration > role modified role '[targetrole]' modified by ...

  • Page 269

    Chapter 6: using the web interface 251 event/context default message when the event = true default message when the event = false lhx/shx > condenser pump failure the condenser pump on lhx at [porttype] port '[portid]' failed. The condenser pump on lhx at [porttype] port '[portid]' is back to normal...

  • Page 270

    Chapter 6: using the web interface 252 event/context default message when the event = true default message when the event = false lhx/shx > threshold water inlet the water inlet temperature threshold on lhx at [porttype] port '[portid]' was crossed. The water inlet temperature on lhx at [porttype] p...

  • Page 271

    Chapter 6: using the web interface 253 • system tamper alarm: this action causes the px2 to show the alarm for the dx tamper sensor, if any, on the dashboard page until a person acknowledges it. By default, this action has been assigned to the built-in tamper detection event rules. For information o...

  • Page 272

    Chapter 6: using the web interface 254 action function request lhx/shx maximum cooling applies the maximum cooling to the lhx/shx device. See request lhx/shx maximum cooling (on page 259). This option is available only when the schroff lhx/shx support has been enabled. Send email emails a textual me...

  • Page 273

    Chapter 6: using the web interface 255 4. Enter the information as needed and click create. 5. Then you can assign the newly-created action to an event rule or schedule it. See event rules and actions (on page 236). Alarm the alarm is an action that requires users to acknowledge an alert. This helps...

  • Page 274

    Chapter 6: using the web interface 256 7. (optional) you can instruct the px2 to send the acknowledgment notification after the alarm is acknowledged in the acknowledgment notifications field. Available methods are identical to those for generating alarm notifications. A. In the available field, sel...

  • Page 275

    Chapter 6: using the web interface 257 stop load shedding: quits the load shedding mode when the specified event occurs. External beeper if an external beeper is connected to the px2, the px2 can change the beeper's behavior or status to respond to a certain event. To control the connected external ...

  • Page 276

    Chapter 6: using the web interface 258 log an event message the option "log event message" records the selected events in the internal log. The default log message generated for each type of event is available in the section titled default log messages (on page 242). Push out sensor readings you can...

  • Page 277

    Chapter 6: using the web interface 259 if "start recording" is selected, adjust the values of the following: number of snapshots - the number of snapshots to be taken when the event occurs. The maximum amount of snapshots that can be stored on the px2 is 10. If you set it for a number greater than 1...

  • Page 278

    Chapter 6: using the web interface 260 send email you can configure emails to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and px2 placeholders. The placeholders represent information is pulled from the px2 and inserted into the message. ...

  • Page 279

    Chapter 6: using the web interface 261 send sensor report you may set the px2 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...

  • Page 280

    Chapter 6: using the web interface 262 a. Click the first to select a target component from the list. B. Click the second to select the specific sensor for the target from the list. C. Click to add the selected sensor to the report sensors list box. For example, to monitor the current reading of the...

  • Page 281

    Chapter 6: using the web interface 263 send sms message you can configure sms messages to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and px2 placeholders. The placeholders represent information which is pulled from the px2 and inserted ...

  • Page 282

    Chapter 6: using the web interface 264 send snapshots via email this option notifies one or multiple persons for the selected events by emailing snapshots or videos captured by a connected logitech ® webcam. Operation: 1. Choose device settings > event rules > . 2. Select "send snapshots via email" ...

  • Page 283

    Chapter 6: using the web interface 265 to send snmp v2c notifications: 1. In the notification type field, select snmpv2c trap or snmpv2c inform. 2. For snmp inform communications, leave the resend settings at their default or do the following: a. In the timeout field, specify the interval of time, i...

  • Page 284

    Chapter 6: using the web interface 266 4. For both snmp traps and informs, enter the following as needed and then click ok to apply the settings: a. Host name b. Port number c. User id for accessing the host -- make sure the user id has the snmpv3 permission. D. Select the host security level securi...

  • Page 285

    Chapter 6: using the web interface 267 no script is available if you have not created or loaded it into the px2. 5. To apply different arguments than the default, do the following. Note that the newly-added arguments will override this script's default arguments. A. Click . B. Type the key and value...

  • Page 286

    Chapter 6: using the web interface 268 cycle outlet: cycles power to the selected outlet(s). 4. To specify the outlet(s) where this action will be applied, select them one by one from the available outlets list. To add all outlets, click select all. 5. To remove any outlets from the selected outlets...

  • Page 287

    Chapter 6: using the web interface 269 syslog message use this action to automatically forward event messages to the specified syslog server. Determine the syslog transmission mechanism you prefer when setting it up - udp, tcp or tls over tcp. The px2 may or may not detect the syslog message transmi...

  • Page 288

    Chapter 6: using the web interface 270 scheduling an action an action can be regularly performed at a preset time interval instead of being triggered by a specific event. For example, you can make the px2 report the reading or state of a specific sensor regularly by scheduling the "send sensor repor...

  • Page 289

    Chapter 6: using the web interface 271 execution time frequency settings minutes click the frequency field to select an option. The frequency ranges from every minute, every 5 minutes, every 10 minutes and so on until every 30 minutes. Hourly type a value in the minute field, which is set to either ...

  • Page 290

    Chapter 6: using the web interface 272 execution time frequency settings yearly this option requires three settings: month - january through december. Day of month - 1 to 31. Time - the value is measured in 12-hour format so you must correctly specify am or pm by clicking the am/pm button. An exampl...

  • Page 291

    Chapter 6: using the web interface 273 then the px2 will send out an email containing the specified temperature sensor readings hourly every day. Whenever you want the px2 to stop sending the temperature report, simply deselect the enabled checkbox in the timer. Email and sms message placeholders ac...

  • Page 292

    Chapter 6: using the web interface 274 placeholder definition [circuitsensor] the circuit sensor name [circuit] the circuit identifier [configparam] the name of a configuration parameter [configvalue] the new value of a parameter [datetime] the human readable timestamp of the event occurrence [devic...

  • Page 293

    Chapter 6: using the web interface 275 placeholder definition [outletname] the outlet name note: if any outlet does not have a name, neither an outlet name nor an outlet number will be shown in the custom message for it. Therefore, it is recommended to check the availability of all outlet names if i...

  • Page 294

    Chapter 6: using the web interface 276 placeholder definition [sysname] sysname as configured for snmp [timereventid] the id of a timer event [timestamp] the timestamp of the event occurrence [transferswitchreason] the transfer reason [transferswitchsensor] the transfer switch sensor name [transfers...

  • Page 295

    Chapter 6: using the web interface 277 sample event rules sample pdu-level event rule in this example, we want the px2 to record the firmware upgrade failure in the internal log when it happens. The event rule involves: • event: device > firmware update failed • action: system event log action to cr...

  • Page 296

    Chapter 6: using the web interface 278 any sensor becomes unavailable. The active energy sensor is reset. For example, when the inlet i1's voltage exceeds the upper warning threshold, the snmp notifications are sent, and when the voltage drops below the upper warning threshold, the snmp notification...

  • Page 297

    Chapter 6: using the web interface 279 note: id numbers of all sensors/actuators are available on the peripherals page. See peripherals (on page 138). 5. Select "state sensor/actuator" because the contact closure sensor is a state sensor. 6. Select "alarmed" since we want the px2 to respond when the...

  • Page 298

    Chapter 6: using the web interface 280 example 3 this example illustrates a situation where two event rules combined regarding the outlet state changes causes the px2 to continuously power cycle outlets 1 and 2 in turn. Event selected action included outlet > outlet 1 > sensor > outlet state > on/of...

  • Page 299

    Chapter 6: using the web interface 281 setting data logging the px2 can store 120 measurements for each sensor in a memory buffer. This memory buffer is known as the data log. Sensor readings in the data log can be retrieved using snmp. You can configure how often measurements are written into the d...

  • Page 300

    Chapter 6: using the web interface 282 if any section's number of sensors exceeds 35, the remaining sensors are listed on next page(s). If so, a pagination bar similar to the following diagram displays in this section, which you can click any button to switch between pages. 5. Click save. This butto...

  • Page 301

    Chapter 6: using the web interface 283 5. If the destination server requires authentication, select the use authentication checkbox, and enter the following data. User name password 6. In the entry type field, determine the data that will be transmitted. Asset management tag list: transmit the infor...

  • Page 302

    Chapter 6: using the web interface 284 monitoring server accessibility you can monitor whether specific it devices are alive by having the px2 device continuously ping them. An it device's successful response to the ping commands indicates that the it device is still alive and can be remotely access...

  • Page 303

    Chapter 6: using the web interface 285 field description number of consecutive unsuccessful pings for failure the number of consecutive pings without any response before the monitored equipment is declared "unreachable." valid range is 1 to 100. Wait time before resuming pinging after failure the wa...

  • Page 304

    Chapter 6: using the web interface 286 editing or deleting ping monitoring settings you can edit the ping monitoring settings of any it device or simply delete it if no longer needed. To modify or delete any monitored it device: 1. Choose device settings > server reachability. 2. Click the desired o...

  • Page 305

    Chapter 6: using the web interface 287 field data entered wait time after successful ping 5 to make the px2 declare the inaccessibility of the monitored pdu when that pdu becomes inaccessible for around 12 seconds (4 seconds * 3 pings), enter the following data. Field data entered wait time after un...

  • Page 306

    Chapter 6: using the web interface 288 5. Select the system snmp notification action. Note: if you have not configured the system snmp notification action to specify the snmp destination(s), see editing or deleting a rule/action (on page 276). No support for front panel outlet switching px2-1000 mod...

  • Page 307

    Chapter 6: using the web interface 289 configuring the serial port you can change the bit rate of the serial port labeled console / modem on the px2. The default bit rate for both console and modem operation is 115200 bps. The px2 supports using the following devices via the serial interface: • a co...

  • Page 308

    Chapter 6: using the web interface 290 2. Click the console baud rate field to select the baud rate intended for console management. Note: for a serial rs-232 or usb connection between a computer and the px2, leave it at the default (115200 bps). 3. Click the modem baud rate field to select the baud...

  • Page 309

    Chapter 6: using the web interface 291 writing or loading a lua script you can enter or load up to 4 scripts to the px2. Tip: if you can no longer enter or load a new script after reaching the upper limit, you can either delete any existing script or simply modify/replace an existing script's codes....

  • Page 310

    Chapter 6: using the web interface 292 5. In the source code section, do one of the following. It is recommended to leave the enable syntax highlighting checkbox selected unless you do not need different text colors to identify diverse code syntaxes. To write a lua script, type the codes in the sour...

  • Page 311

    Chapter 6: using the web interface 293 manually starting or stopping a script you can manually start or stop an existing lua script at any time. When starting a script, you can choose to start it either with its default arguments or with new arguments. Tip: to have the px2 automatically start or sto...

  • Page 312

    Chapter 6: using the web interface 294 click if needing additional arguments. 5. Click start. 6. The script output will be shown in the script output section. If needed, click to delete the existing output data. To manually stop a script: 1. Choose device settings > lua scripts. 2. Click the desired...

  • Page 313

    Chapter 6: using the web interface 295 checking lua scripts states choose device settings > lua scripts to show the scripts list, which indicates the current state and settings of each script. State: four script states are available. • new : the script is never executed since the device boot. • runn...

  • Page 314

    Chapter 6: using the web interface 296 3. Click > edit script. 4. Make changes to the information shown, except for the script's name, which cannot be revised. To replace the current script, click load local file or load example to select a new script. To delete a script: 1. Choose device settings >...

  • Page 315

    Chapter 6: using the web interface 297 field description domain password type the authentication password (secret) for entering the cisco energywise domain up to 127 printable ascii characters are permitted. Spaces and asterisks are not acceptable. Port type a user datagram protocol (udp) port numbe...

  • Page 316

    Chapter 6: using the web interface 298 device information using the web interface, you can retrieve hardware and software information of components or peripheral devices connected to your px2. Tip: if the information shown on this page does not match the latest status, press f5 to reload it. To disp...

  • Page 317

    Chapter 6: using the web interface 299 section title information shown controllers each inlet or outlet controller's serial number, board id, firmware version and hardware version. Inlets each inlet's plug type, rated voltage and current. Peripheral devices serial numbers, model names, position and ...

  • Page 318

    Chapter 6: using the web interface 300 cascading information in the bridging mode: • the common section contains two read-only fields for indicating the cascading status. Note that the cascading position is not available in the bridging mode. Fields description port forwarding indicates the port for...

  • Page 319

    Chapter 6: using the web interface 301 fields description cascaded device connected indicates whether a slave device is detected on the usb-a or ethernet port. Yes: connection to a slave device is detected. No: no connection to a slave device is detected. A master device shows 0 (zero) in the cascad...

  • Page 320

    Chapter 6: using the web interface 302 the final slave device shows a non-zero number which indicates its position in the cascade position field and no in the cascaded device connected field. The following diagram shows 2, indicating it is the second slave - slave 2. The cascaded device connected fi...

  • Page 321

    Chapter 6: using the web interface 303 column description client type the interface through which the user is being connected to the px2. Web gui: refers to the web interface. Cli: refers to the command line interface (cli). The information in parentheses following "cli" indicates how this user is c...

  • Page 322

    Chapter 6: using the web interface 304 viewing or clearing the local event log by default, the px2 captures certain system events and saves them in a local (internal) event log. You can view over 2000 historical events that occurred on the px2 in the local event log. When the log size exceeds 256kb,...

  • Page 323

    Chapter 6: using the web interface 305 updating the px2 firmware firmware files are available on raritan website's support page ( http://www.Raritan.Com/support/ ). When performing the firmware upgrade, the px2 keeps each outlet's power status unchanged so no server operation is interrupted. During ...

  • Page 324

    Chapter 6: using the web interface 306 a progress bar appears on the web interface, indicating the update status. The front panel display shows the firmware upgrade message. See three-digit row (on page 81). The outlet leds flash if the relay boards are being updated. If the firmware update does not...

  • Page 325

    Chapter 6: using the web interface 307 a note about firmware upgrade time the pdu firmware upgrade time varies from unit to unit, depending on various external and internal factors. External factors include, but are not limited to: network throughput, firmware file size, and speed at which the firmw...

  • Page 326

    Chapter 6: using the web interface 308 stm32 bootloader update failure the information in this section only applies to the pdu running a firmware version earlier than 2.1.6. When you are upgrading (or downgrading) the px2-1000 or px2-2000 series from any firmware version prior to version 2.1.6 to an...

  • Page 327

    Chapter 6: using the web interface 309 bulk configuration the bulk configuration feature lets you save generic settings of a configured px2 device to your computer. You can use this configuration file to copy common settings to other px2 devices of the same model and firmware version. See bulk confi...

  • Page 328

    Chapter 6: using the web interface 310 enter the admin password, and click restore. 6. Wait until the px2 device resets and the login page re-appears. Note: on startup, the px2 performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of th...

  • Page 329

    Chapter 6: using the web interface 311 device-specific settings not included the settings saved in the bulk configuration file include user and role configurations, thresholds, event rules, security settings, date/time and so on. Note: because the date and time settings are saved in the configuratio...

  • Page 330

    Chapter 6: using the web interface 312 example: you can perform bulk configuration between raritan's px2-4724-e2n1k2 and px2-4724-e2n1k9. • reason: the two models share the same technical specifications, and the only difference is their chassis colors represented by k2 (blue) and k9 (gray). Backup a...

  • Page 331

    Chapter 6: using the web interface 313 note: on startup, the px2 performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset. For example, the "bulk configuration copied" event is logged...

  • Page 332

    Chapter 6: using the web interface 314 2. Click run ping to ping the host. The ping results are then displayed. Trace route: 1. Type values in the following fields. Field/setting description host name the ip address or name of the host whose route you want to check. Timeout(s) a timeout value in sec...

  • Page 333

    Chapter 6: using the web interface 315 rebooting the px2 device you can remotely reboot the px2 device via the web interface. Resetting the px2 does not interrupt the operation of connected servers because there is no loss of power to outlets. During and after the reboot, outlets that have been powe...

  • Page 334

    Chapter 6: using the web interface 316 to reset the device to factory defaults: 1. Choose maintenance > unit reset > . 2. Click factory reset to reset the px2 to factory defaults. 3. A message appears, with a countdown timer showing the remaining time of the operation. It takes about two minutes to ...

  • Page 335

    Chapter 6: using the web interface 317 webcam management the webcam-related menu items appear only when there are webcam(s) connected to the px2. See connecting a logitech webcam (on page 73). With a logitech ® webcam connected to the px2, you can visually monitor the environment around the px2 via ...

  • Page 336

    Chapter 6: using the web interface 318 you can send out this window's url to share the live image with other users. See sending snapshots or videos in an email or instant message (on page 319). 5. To switch between snapshot and video modes, see the settings section below. In the video mode, the numb...

  • Page 337

    Chapter 6: using the web interface 319 sending snapshots or videos in an email or instant message whenever you open a primary standalone live preview window, a unique url is generated for this window session. A url supports a maximum of three sessions. Therefore, you can email or instant message up ...

  • Page 338

    Chapter 6: using the web interface 320 2. Click live preview > new live preview window. The live snapshot or video in a standalone live preview window opens. See configuring webcams and viewing live images (on page 317). 3. Copy the url from the live preview window, and send it through an email or i...

  • Page 339

    Chapter 6: using the web interface 321 3. If the latest saved snapshot is not listed yet, click > refresh on the top of the list. 4. To manually delete any images: a. Select the checkboxes of the images you want to remove. To select all images, select the top-most checkbox in the header row. B. On t...

  • Page 340

    322 this snmp section helps you set up the px2 for use with an snmp manager. The px2 can be configured to send traps or informs to an snmp manager, as well as receive get and set commands in order to retrieve status and configure some basic settings. In this chapter enabling and configuring snmp ......

  • Page 341

    Chapter 7: using snmp 323 to enable snmp notifications: 1. Choose device settings > network services > snmp. 2. In the snmp notifications section, enable the snmp notification feature, and configure related fields. For details, refer to: snmpv2c notifications (on page 323) snmpv3 notifications (on p...

  • Page 342

    Chapter 7: using snmp 324 6. Click save. Snmpv3 notifications 1. Choose device settings > network services > snmp. 2. In the snmp agent, make sure the enable snmp v1/v2c checkbox is selected. 3. In the snmp notifications section, make sure the enable snmp notifications checkbox is selected. 4. Selec...

  • Page 343

    Chapter 7: using snmp 325 field description authentication protocol, authentication passphrase, confirm authentication passphrase the three fields are available when the security level is set to authnopriv or authpriv. Select the authentication protocol - md5 or sha enter the authentication passphra...

  • Page 344

    Chapter 7: using snmp 326 mib download via the device information page: 1. Choose maintenance > device information. 2. In the information section, click the desired download link: pdu2-mib assetmanagement-mib lhx mib 3. Click save to save the file onto your computer. Note: lhx-mib is available only ...

  • Page 345

    Chapter 7: using snmp 327 layout opening the mib reveals the custom objects that describe the px2 system at the unit level as well as at the individual-outlet level. As standard, these objects are first presented at the beginning of the file, listed under their parent group. The objects then appear ...

  • Page 346

    Chapter 7: using snmp 328 snmp sets and thresholds some objects can be configured from the snmp manager using snmp set commands. Objects that can be configured have a max-access level of "read-write" in the mib. These objects include threshold objects, which causes the px2 to generate a warning and ...

  • Page 347

    Chapter 7: using snmp 329 a note about enabling thresholds when enabling previously disabled thresholds via snmp, make sure you set a correct value for all thresholds that are supposed to be enabled prior to actually enabling them. Otherwise, you may get an error message..

  • Page 348

    330 this section explains how to use the command line interface (cli) to administer a px2 device. Cli commands are case sensitive. In this chapter about the interface ................................................................................... 330 logging in to cli ..............................

  • Page 349

    Chapter 8: using the command line interface 331 logging in to cli logging in via hyperterminal over a local connection is a little different than logging in using ssh or telnet. If a security login agreement has been enabled, you must accept the agreement in order to complete the login. Users are au...

  • Page 350

    Chapter 8: using the command line interface 332 after properly entering the password, the # or > system prompt appears. See different cli modes and prompts (on page 334) in the user guide for more information. Tip: the "last login" information, including the date and time, is also displayed if the s...

  • Page 351

    Chapter 8: using the command line interface 333 with an analog modem the px2 supports remote access to the cli via a connected analog modem. This feature is especially useful when the lan access is not available. To connect to the px2 via the modem: 1. Make sure the px2 has an analog modem connected...

  • Page 352

    Chapter 8: using the command line interface 334 different cli modes and prompts depending on the login name you use and the mode you enter, the system prompt in the cli varies. • user mode: when you log in as a normal user, who may not have full permissions to configure the px2 device, the > prompt ...

  • Page 353

    Chapter 8: using the command line interface 335 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: c...

  • Page 354

    Chapter 8: using the command line interface 336 querying available parameters for a command if you are not sure what commands or parameters are available for a particular type of cli command or its syntax, you can have the cli show them by adding a space and the help command (?) to the end of that c...

  • Page 355

    Chapter 8: using the command line interface 337 network configuration this command shows all network configuration and all network interfaces' information, such as the ip address, mac address, the ethernet interface's duplex mode, and the wireless interface's status/settings. # show network ip confi...

  • Page 356

    Chapter 8: using the command line interface 338 option description all show the ip-related configuration of all interfaces. You can type the cli command without the word 'all.' for example, show network ip interface . Ipv4-only or ipv6-only configuration to show ipv4-only configuration or ipv6-only ...

  • Page 357

    Chapter 8: using the command line interface 339 option description ethernet show the ipv4 or ipv6 configuration of the ethernet interface. Wireless show the ipv4 or ipv6 configuration of the wireless interface. Bridge show the ipv4 or ipv6 configuration of the bridge interface. All show the ipv4 or ...

  • Page 358

    Chapter 8: using the command line interface 340 network service settings this command shows the network service settings only, including the telnet setting, tcp ports for http, https, ssh and modbus/tcp services, and snmp settings. # show network services variables: • is one of the options: all , ht...

  • Page 359

    Chapter 8: using the command line interface 341 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 ...

  • Page 360

    Chapter 8: using the command line interface 342 inlet information this command syntax shows the inlet information. # show inlets to show detailed information, add the parameter "details" to the end of the command. # show inlets details variables: • is one of the options: all , or a number. Option de...

  • Page 361

    Chapter 8: using the command line interface 343 overcurrent protector information this command is only available for models with overcurrent protectors for protecting outlets. This command syntax shows the overcurrent protector information, such as a circuit breaker or a fuse. # show ocp to show det...

  • Page 362

    Chapter 8: using the command line interface 344 date and time settings this command shows the current date and time settings on the px2 device. # show time to show detailed information, add the parameter "details" to the end of the command. # show time details default measurement units this command ...

  • Page 363

    Chapter 8: using the command line interface 345 environmental sensor information this command syntax shows the environmental sensor's information. # show externalsensors to show detailed information, add the parameter "details" to the end of the command. # show externalsensors details external senso...

  • Page 364

    Chapter 8: using the command line interface 346 * the environmental sensor number is the id number assigned to the sensor, which can be found on the peripherals page of the px2 web interface. Displayed information: • without the parameter "details," only the sensor id, sensor type and reading are di...

  • Page 365

    Chapter 8: using the command line interface 347 actuator information this command syntax shows an actuator's information. # show actuators to show detailed information, add the parameter "details" to the end of the command. # show actuators details variables: • is one of the options: all , or a numb...

  • Page 366

    Chapter 8: using the command line interface 348 inlet sensor threshold information this command syntax shows the specified inlet sensor's threshold-related information. # show sensor inlet to show detailed information, add the parameter "details" to the end of the command. # show sensor inlet detail...

  • Page 367

    Chapter 8: using the command line interface 349 inlet pole sensor threshold information this command is only available for a three-phase pdu except for an in-line monitor (px-3000 series). This command syntax shows the specified inlet pole sensor's threshold-related information. # show sensor inletp...

  • Page 368

    Chapter 8: using the command line interface 350 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 informatio...

  • Page 369

    Chapter 8: using the command line interface 351 environmental sensor threshold information this command syntax shows the specified environmental sensor's threshold-related information. # show sensor externalsensor to show detailed information, add the parameter "details" to the end of the command. #...

  • Page 370

    Chapter 8: using the command line interface 352 displayed information: • without the parameter "details," only the reading, threshold, deassertion hysteresis and assertion timeout settings of the specified environmental sensor are displayed. • with the parameter "details," more sensor information is...

  • Page 371

    Chapter 8: using the command line interface 353 • without the parameter "details," only the default upper and lower thresholds, deassertion hysteresis and assertion timeout settings of the specified sensor type are displayed. • with the parameter "details," the threshold range is displayed in additi...

  • Page 372

    Chapter 8: using the command line interface 354 existing user profiles this command shows the data of one or all existing user profiles. # show user to show detailed information, add the parameter "details" to the end of the command. # show user details variables: • is the name of the user whose pro...

  • Page 373

    Chapter 8: using the command line interface 355 existing roles this command shows the data of one or all existing roles. # show roles variables: • is the name of the role whose permissions you want to query. The variable can be one of the following options: option description all this option shows a...

  • Page 374

    Chapter 8: using the command line interface 356 serial port settings this command shows the baud rate setting of the serial port labeled console / modem on the px2 device. # show serial energywise settings this command shows the px2 device's current configuration for cisco ® energywise. # show energ...

  • Page 375

    Chapter 8: using the command line interface 357 rack unit settings of an asset strip a rack unit refers to a tag port on the asset strips. This command shows the settings of a specific rack unit or all rack units on an asset strip, such as a rack unit's led color and led mode. # show rackunit variab...

  • Page 376

    Chapter 8: using the command line interface 358 blade extension strip settings this command shows the information of a blade extension strip, including the total number of tag ports, and if available, the id (barcode) number of any connected tag. # show bladeslot variables: • is the number of the fe...

  • Page 377

    Chapter 8: using the command line interface 359 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 ...

  • Page 378

    Chapter 8: using the command line interface 360 event type description sensor internal or external sensor events, such as state changes of any sensors. Servermonitor server-monitoring records, such as a server being declared reachable or unreachable. Assetmanagement raritan asset management events, ...

  • Page 379

    Chapter 8: using the command line interface 361 server reachability information for a specific server to show the server reachability information for a certain it device only, use the following command. # show serverreachability server to show detailed information, add the parameter "details" to the...

  • Page 380

    Chapter 8: using the command line interface 362 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 comman...

  • Page 381

    Chapter 8: using the command line interface 363 option description a specific integer number displays the specified number of last entries in the reliability error log. Examples this section provides examples of the show command. Example 1 - basic security information the diagram shows the output of...

  • Page 382

    Chapter 8: using the command line interface 364 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 383

    Chapter 8: using the command line interface 365 example 4 - in-depth pdu information more information is displayed when typing the show pdu details command. Displayed information varies depending on the model you purchased. Clearing information you can use the clear commands to remove unnecessary da...

  • Page 384

    Chapter 8: using the command line interface 366 clearing wlan log this command removes all data from the diagnostic log for the wireless lan (wlan) connection. # clear wlanlog -- or -- # clear wlanlog /y if you entered the command without "/y," a message appears, prompting you to confirm the operati...

  • Page 385

    Chapter 8: using the command line interface 367 "apply" command before closing the terminal emulation program. Closing the program does not save any configuration changes. See quitting configuration mode (on page 367). Quitting configuration mode both of "apply" and "cancel" commands let you quit th...

  • Page 386

    Chapter 8: using the command line interface 368 setting the outlet power-on sequence this section applies to outlet-switching capable models only. This command sets the outlet power-on sequence when the pdu powers up. Config:# pdu outletsequence variables: • is one of the options: default , or a com...

  • Page 387

    Chapter 8: using the command line interface 369 config:# pdu outletsequencedelay :;:; :;... Separate outlet numbers and their delay settings with a colon. Outlets followed by delays are separated with a semicolon. Variables: • , , and the like are individual outlet numbers or a range of outlets usin...

  • Page 388

    Chapter 8: using the command line interface 370 setting the pdu-defined cycling power-off period this section applies to outlet-switching capable models only. This command sets the power-off period of the power cycling operation for all outlets. Config:# pdu cyclingpoweroffperiod variables: • is the...

  • Page 389

    Chapter 8: using the command line interface 371 specifying non-critical outlets this section applies to outlet-switching capable models only. This command determines critical and non-critical outlets. It is associated with the load shedding mode. See load shedding mode (on page 127). Config:# pdu no...

  • Page 390

    Chapter 8: using the command line interface 372 setting data logging measurements per entry this command defines the number of measurements accumulated per log entry. Config:# pdu measurementsperlogentry variables: • is an integer between 1 and 600. The default is 60 samples per log entry. For more ...

  • Page 391

    Chapter 8: using the command line interface 373 setting the z coordinate format for environmental sensors this command enables or disables the use of rack units for specifying the height (z coordinate) of environmental sensors. Config:# pdu externalsensorszcoordinateformat variables: • is one of the...

  • Page 392

    Chapter 8: using the command line interface 374 examples this section illustrates several pdu configuration examples. Example 1 - pdu naming the following command assigns the name "my px12" to the pdu. Config:# pdu name "my px12" example 2 - outlet sequence the following command causes a 10-outlet p...

  • Page 393

    Chapter 8: using the command line interface 375 setting the ipv4 configuration mode this command determines the ip configuration mode. Config:# network ipv4 interface configmethod variables: • is one of the network interfaces: ethernet , wireless , bridge or all . Note that you must choose/configure...

  • Page 394

    Chapter 8: using the command line interface 376 setting the ipv4 preferred host name after selecting dhcp as the ipv4 configuration mode, you can specify the preferred host name, which is optional. The following is the command: config:# network ipv4 interface preferredhostname variables: • is one of...

  • Page 395

    Chapter 8: using the command line interface 377 setting the ipv4 address after selecting the static ip configuration mode, you can use this command to assign a permanent ip address to the px2 device. Config:# network ipv4 interface address variables: • is one of the network interfaces: ethernet , wi...

  • Page 396

    Chapter 8: using the command line interface 378 setting ipv4 static routes if the ipv4 network mode is set to static ip and your local network contains two subnets, you can configure static routes to enable or disable communications between the px2 and devices in the other subnet. These commands are...

  • Page 397

    Chapter 8: using the command line interface 379 config:# network ipv4 staticroutes modify interface variables: • is a combination of the ip address and subnet mask of the other subnet. The format is ip address/subnet mask . • is the ip address of the next hop router. • is one of the interfaces: ethe...

  • Page 398

    Chapter 8: using the command line interface 380 • 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. Setting the ipv6 preferred host name after selecting dhcp as the ip...

  • Page 399

    Chapter 8: using the command line interface 381 setting the ipv6 address after selecting the static ip configuration mode, you can use this command to assign a permanent ip address to the px2 device. Config:# network ipv6 interface address address> variables: • is one of the network interfaces: ethe...

  • Page 400

    Chapter 8: using the command line interface 382 setting ipv6 static routes if the ipv6 network mode is set to static ip and your local network contains two subnets, you can configure static routes to enable or disable communications between the px2 and devices in the other subnet. These commands are...

  • Page 401

    Chapter 8: using the command line interface 383 config:# network ipv6 staticroutes modify interface variables: • is the ip address and prefix length of the subnet where the px2 belongs. The format is ip address/prefix length . • is the ip address of the next hop router. • is one of the interfaces: e...

  • Page 402

    Chapter 8: using the command line interface 384 configuring dns parameters use the following commands to configure dns-related settings. Specify the primary dns server: config:# network dns firstserver specify the secondary dns server: config:# network dns secondserver specify the third dns server: ...

  • Page 403

    Chapter 8: using the command line interface 385 enabling or disabling the lan interface this command enables or disables the lan interface. Config:# network ethernet ethernet enabled variables: • is one of the options: true or false . Option description true the specified network interface is enable...

  • Page 404

    Chapter 8: using the command line interface 386 changing the lan duplex mode this command determines the lan interface duplex mode. Config:# network ethernet ethernet duplexmode variables: • is one of the modes: auto , half or full . Option description auto the px2 selects the optimum transmission m...

  • Page 405

    Chapter 8: using the command line interface 387 - ascii codes 0x20 ~ 0x7e setting the authentication method this command sets the wireless authentication method to either psk or extensible authentication protocol (eap). Config:# network wireless authmethod variables: • is one of the authentication m...

  • Page 406

    Chapter 8: using the command line interface 388 setting eap parameters when the wireless authentication method is set to eap, you must configure eap authentication parameters, including outer authentication, inner authentication, eap identity, password, and ca certificate. Determine the outer authen...

  • Page 407

    Chapter 8: using the command line interface 389 config:# network wireless allowconnectionwithincorrectclock variables: • the value of is peap because px2 only supports protected extensible authentication protocol (peap) as the outer authentication. • the value of is mschapv2 because px2 only support...

  • Page 408

    Chapter 8: using the command line interface 390 option description false the wireless network connection is not successfully established when the px2 finds that the tls certificate is not valid due to incorrect system time. Eap ca certificate example this section provides a ca certificate example on...

  • Page 409

    Chapter 8: using the command line interface 391 miicjtccafigawibagiemaygrzalbgkqhkig9w0baqqwrtelmak ga1uebhmcvvmxnja0bgnvbaotlu5hdglvbmfsieflcm9uyxv0aw nzigfuzcbtcgfjzsbbzg1pbmlzdhjhdglvbjamfxe5nja1mjgxm zq5mdurmdgwmbcrotgwnti4mtm0ota1kza4mdawzzelmakga1ue bhmcvvmxnja0bgnvbaotlu5hdglvbmfsieflcm9uyxv0...

  • Page 410

    Chapter 8: using the command line interface 392 cascading mode may not be enabled successfully. Mode description bridge the network bridging mode, where each cascaded device is assigned a unique ip address. Portforwarding the port forwarding mode, where every cascaded device in the chain shares the ...

  • Page 411

    Chapter 8: using the command line interface 393 • is one of the following options: option description ethernet ethernet port is the port where the 1st slave device is connected. Usb usb port is the port where the 1st slave device is connected. Setting network service parameters a network service com...

  • Page 412

    Chapter 8: using the command line interface 394 setting the https port the commands used to configure the https port settings begin with network services https . Change the https port: config:# network services https port enable or disable the https access: config:# network services https enabled va...

  • Page 413

    Chapter 8: using the command line interface 395 option description false the telnet service is disabled. Changing the telnet port this command changes the telnet port. Config:# network services telnet port variables: • is a tcp port number between 1 and 65535. The default telnet port is 23. Changing...

  • Page 414

    Chapter 8: using the command line interface 396 determining the ssh authentication method this command syntax determines the ssh authentication method. Config:# network services ssh authentication variables: • is one of the options: passwordonly , publickeyonly or passwordorpublickey . Option descri...

  • Page 415

    Chapter 8: using the command line interface 397 enabling or disabling snmp v3 this command enables or disables the snmp v3 protocol. Config:# network services snmp v3 variables: • is one of the options: enable or disable . Option description enable the snmp v3 protocol is enabled. Disable the snmp v...

  • Page 416

    Chapter 8: using the command line interface 398 setting the sysname value this command sets the snmp mib-ii sysname value. Config:# network services snmp sysname variables: • is a string comprising 0 to 255 alphanumeric characters. Setting the syslocation value this command sets the snmp mib-ii sysl...

  • Page 417

    Chapter 8: using the command line interface 399 enabling or disabling the read-only mode this command enables or disables the read-only mode for the modbus agent. Config:# network services modbus readonly variables: • is one of the options: true or false . Option description true the read-only mode ...

  • Page 418

    Chapter 8: using the command line interface 400 examples this section illustrates several network configuration examples. Example 1 - networking mode the following command enables the wired networking mode. Config:# network mode wired example 2 - enabling both ip protocols the following command dete...

  • Page 419

    Chapter 8: using the command line interface 401 determining the time setup method this command determines the method to configure the system date and time. Config:# time method variables: • is one of the time setup options: manual or ntp . Mode description manual the date and time settings are custo...

  • Page 420

    Chapter 8: using the command line interface 402 overriding dhcp-assigned ntp servers this command determines whether the customized ntp server settings override the dhcp-specified ntp servers. Config:# time ntp overridedhcpprovidedserver variables: • is one of these options: true or false . Mode des...

  • Page 421

    Chapter 8: using the command line interface 403 example to set the time zone: 1. Type the time zone command as shown below and press enter. Config:# time zone 2. The system shows a list of time zones. Type the index number of the desired time zone and press enter. 3. Type apply for the selected time...

  • Page 422

    Chapter 8: using the command line interface 404 setting the automatic daylight savings time this command determines whether the daylight savings time is applied to the time settings. Config:# time autodst variables: • is one of the options: enable or disable . Mode description enable daylight saving...

  • Page 423

    Chapter 8: using the command line interface 405 checking the accessibility of ntp servers this command verifies the accessibility of ntp servers specified manually on your px2 and then shows the result. For instructions on specifying ntp servers via cli, see setting ntp parameters (on page 401). To ...

  • Page 424

    Chapter 8: using the command line interface 406 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 determine the default ipv4...

  • Page 425

    Chapter 8: using the command line interface 407 option description false disables the ip access control feature. • 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...

  • Page 426

    Chapter 8: using the command line interface 408 config:# security ipaccesscontrol ipv4 rule add • ipv6 commands add a new rule to the bottom of the ipv6 rules list: config:# security ipaccesscontrol ipv6 rule add add a new ipv6 rule by inserting it above or below a specific rule: config:# security i...

  • Page 427

    Chapter 8: using the command line interface 409 • 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 num...

  • Page 428

    Chapter 8: using the command line interface 410 config:# security ipaccesscontrol ipv6 rule modify policy modify all contents of an ipv6 existing rule: config:# security ipaccesscontrol ipv6 rule modify ipmask policy variables: • is one of the options: in or out . Direction description in inbound tr...

  • Page 429

    Chapter 8: using the command line interface 411 config:# security ipaccesscontrol ipv4 rule delete ipv6 commands config:# security ipaccesscontrol ipv6 rule delete variables: • is one of the options: in or out . Direction description in inbound traffic. Out outbound traffic. • is the number of the e...

  • Page 430

    Chapter 8: using the command line interface 412 after the restricted service agreement feature is enabled, the agreement's content is displayed in the login screen. Do either of the following, or the login fails: • in the web interface, select the checkbox labeled "i understand and accept the restri...

  • Page 431

    Chapter 8: using the command line interface 413 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. Press enter again. 6. Verify ...

  • Page 432

    Chapter 8: using the command line interface 414 password aging this command enables or disables the password aging feature, which controls whether the password should be changed at a regular interval: config:# security loginlimits passwordaging variables: • is one of the options: enable or disable ....

  • Page 433

    Chapter 8: using the command line interface 415 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 multi-command syntax (o...

  • Page 434

    Chapter 8: using the command line interface 416 enabling or disabling strong passwords this command enables or disables the strong password feature. Config:# security strongpasswords enabled variables: • is one of the options: true or false . Option description true enables the strong password featu...

  • Page 435

    Chapter 8: using the command line interface 417 option description disable no lowercase character is required. Uppercase character requirement this command determines whether a strong password includes at least a uppercase character. Config:# security strongpasswords enforceatleastoneuppercasecharac...

  • Page 436

    Chapter 8: using the command line interface 418 config:# security strongpasswords enforceatleastonespecialcharacter variables: • is one of the options: enable or disable . Option description enable at least one special character is required. Disable no special character is required. Maximum password...

  • Page 437

    Chapter 8: using the command line interface 419 config:# security rolebasedaccesscontrol ipv4 defaultpolicy • ipv6 commands enable or disable the ipv6 role-based access control feature: config:# security rolebasedaccesscontrol ipv6 enabled determine the ipv6 role-based access control policy: config:...

  • Page 438

    Chapter 8: using the command line interface 420 adding a role-based access control rule depending on where you want to add a new rule in the list, the command syntax for adding a rule varies. • ipv4 commands add a new rule to the bottom of the ipv4 rules list: config:# security rolebasedaccesscontro...

  • Page 439

    Chapter 8: using the command line interface 421 • 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 num...

  • Page 440

    Chapter 8: using the command line interface 422 config:# security rolebasedaccesscontrol ipv4 rule modify startipaddress endipaddress role policy • ipv6 commands modify a rule's ipv6 address range: config:# security rolebasedaccesscontrol ipv6 rule modify startipaddress endipaddress modify an ipv6 r...

  • Page 441

    Chapter 8: using the command line interface 423 policy description deny drops traffic from the specified ip address range when the user is a member of the specified role deleting a role-based access control rule these commands remove a specific rule from the list. Ipv4 commands config:# security rol...

  • Page 442

    Chapter 8: using the command line interface 424 example 1 - ipv4 firewall control configuration the following command sets up two parameters of the ipv4 access control feature. Config:# security ipaccesscontrol ipv4 enabled true defaultpolicyin accept defaultpolicyout accept results: • the ipv4 acce...

  • Page 443

    Chapter 8: using the command line interface 425 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...

  • Page 444

    Chapter 8: using the command line interface 426 changing an outlet's default state this section applies to outlet-switching capable models only. This command determines the initial power condition of an outlet after the px2 powers up. Config:# outlet stateondevicestartup variables: • is the number o...

  • Page 445

    Chapter 8: using the command line interface 427 setting an outlet's cycling power-off period this section applies to outlet-switching capable models only. This command determines the power-off period of the power cycling operation for a specific outlet. Config:# outlet cyclingpoweroffperiod variable...

  • Page 446

    Chapter 8: using the command line interface 428 changing the inlet name this command syntax names an inlet. Config:# inlet name "" variables: • is the number of the inlet that you want to configure. For a single-inlet pdu, is always the number 1. The value is an integer between 1 and 50. • is a stri...

  • Page 447

    Chapter 8: using the command line interface 429 example - inlet naming the following command assigns the name "ac source" to the inlet 1. If your px2 device contains multiple inlets, this command names the 1st inlet. Config:# inlet 1 name "ac source" overcurrent protector configuration commands an o...

  • Page 448

    Chapter 8: using the command line interface 430 creating a user profile this command creates a new user profile. Config:# user create after performing the user creation command, the px2 prompts you to assign a password to the newly-created user. Then: 1. Type the password and press enter. 2. Re-type...

  • Page 449

    Chapter 8: using the command line interface 431 2. Re-type the new password for confirmation and press enter. Variables: • 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." 1. Verify that you have ente...

  • Page 450

    Chapter 8: using the command line interface 432 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. See multi-comma...

  • Page 451

    Chapter 8: using the command line interface 433 enabling or disabling a user profile this command enables or disables a user profile. A user can log in to the px2 device only after that user's user profile is enabled. Config:# user modify enabled variables: • is the name of the user whose settings y...

  • Page 452

    Chapter 8: using the command line interface 434 modifying snmpv3 settings there are different commands to modify the snmpv3 parameters of a specific user profile. You can combine all of the following commands to modify the snmpv3 parameters at a time. See multi-command syntax (on page 480). Enable o...

  • Page 453

    Chapter 8: using the command line interface 435 config:# user modify userpasswordasauthenticationpassphrase variables: • is the name of the user whose settings you want to change. • is one of the options: true or false . Option description true authentication passphrase is identical to the password....

  • Page 454

    Chapter 8: using the command line interface 436 determine the privacy passphrase: config:# user modify privacypassphrase variables: • is the name of the user whose settings you want to change. • is a string used as a privacy passphrase, comprising 8 to 32 ascii printable characters. Determine the au...

  • Page 455

    Chapter 8: using the command line interface 437 changing the role(s) this command changes the role(s) of a specific user. Config:# user modify roles variables: • is the name of the user whose settings you want to change. • is a role or a list of comma-separated roles assigned to the specified user p...

  • Page 456

    Chapter 8: using the command line interface 438 set the preferred length unit: config:# user modify preferredlengthunit variables: • is the name of the user whose settings you want to change. • is one of the options: meter or feet . Option description meter this option displays the length or height ...

  • Page 457

    Chapter 8: using the command line interface 439 d. Press enter. To remove an existing ssh public key: 1. Type the same command as shown above. 2. When the system prompts you to input the contents, press enter without typing or pasting anything. Example the following procedure illustrates how to chan...

  • Page 458

    Chapter 8: using the command line interface 440 config:# password 3. Type the existing password and press enter when the following prompt appears. Current password: 4. Type the new password and press enter when the following prompt appears. Enter new password: 5. Re-type the new password for confirm...

  • Page 459

    Chapter 8: using the command line interface 441 config:# user defaultpreferences preferredlengthunit variables: • 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 defau...

  • Page 460

    Chapter 8: using the command line interface 442 example 1 - creating a user profile the following command creates a new user profile and sets two parameters for the new user. Config:# user create may enable admin results: • a new user profile "may" is created. • the new user profile is enabled. • th...

  • Page 461

    Chapter 8: using the command line interface 443 role configuration commands a role configuration command begins with role . Creating a role this command creates a new role, with a list of semicolon-separated privileges assigned to the role. Config:# role create ;;... If a specific privilege contains...

  • Page 462

    Chapter 8: using the command line interface 444 privilege description changeauthsettings change authentication settings changedatatimesettings change date/time settings changeexternalsensorsconfiguration change peripheral device configuration changelhxconfiguration change lhx/shx configuration chang...

  • Page 463

    Chapter 8: using the command line interface 445 * the "switchoutlet" privilege requires an argument that is separated with a colon. The argument could be: • all outlets, that is, switchoutlet:all • an outlet number. For example: switchoutlet:1 switchoutlet:2 switchoutlet:3 • a list of comma-separate...

  • Page 464

    Chapter 8: using the command line interface 446 modifying a role you can modify diverse parameters of an existing role, including its privileges. Modify a role's description: config:# role modify description "" variables: • is a string comprising up to 32 ascii printable characters. • is a descripti...

  • Page 465

    Chapter 8: using the command line interface 447 config:# role modify addprivileges :,...; :,...; :,...; ... Variables: • is a string comprising up to 32 ascii printable characters. • , , and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See all...

  • Page 466

    Chapter 8: using the command line interface 448 deleting a role this command deletes an existing role. Config:# role delete example - creating a role the following command creates a new role and assigns privileges to the role. Config:# role create tester firmwareupdate;vieweventsetup results: • a ne...

  • Page 467

    Chapter 8: using the command line interface 449 changing the sensor name this command names an environmental sensor. Config:# externalsensor name "" variables: • is the id number of the environmental sensor that you want to configure. The id number is available in the px2 web interface or using the ...

  • Page 468

    Chapter 8: using the command line interface 450 type description vibration the connected detector/switch is for detection of the vibration. Setting the x coordinate this command specifies the x coordinate of an environmental sensor. Config:# externalsensor xlabel "" variables: • is the id number of ...

  • Page 469

    Chapter 8: using the command line interface 451 setting the z coordinate this command specifies the z coordinate of an environmental sensor. Config:# externalsensor zlabel "" variables: • is the id number of the environmental sensor that you want to configure. The id number is available in the px2 w...

  • Page 470

    Chapter 8: using the command line interface 452 using default thresholds this command determines whether default thresholds, including the deassertion hysteresis and assertion timeout, are applied to a specific environmental sensor. Config:# externalsensor usedefaultthresholds variables: • is the id...

  • Page 471

    Chapter 8: using the command line interface 453 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 c...

  • Page 472

    Chapter 8: using the command line interface 454 config:# defaultthresholds lowerwarning set the default deassertion hysteresis for a specific sensor type: config:# defaultthresholds hysteresis set the default assertion timeout for a specific sensor type: config:# defaultthresholds assertiontimeout v...

  • Page 473

    Chapter 8: using the command line interface 455 sensor types measurement units vibration g • is the deassertion hysteresis value applied to the specified sensor type. • is the assertion timeout value applied to the specified sensor type. It ranges from 0 to 100 (samples). Example - default upper thr...

  • Page 474

    Chapter 8: using the command line interface 456 config:# sensor inlet uppercritical set the upper warning threshold for an inlet sensor: config:# sensor inlet upperwarning set the lower critical threshold for an inlet sensor: config:# sensor inlet lowercritical set the lower warning threshold for an...

  • Page 475

    Chapter 8: using the command line interface 457 sensor type description unbalancedcurrent unbalanced load sensor linefrequency line frequency sensor residualcurrent residual current sensor phaseangle inlet phase angle sensor note: if the requested sensor type is not supported, the "sensor is not ava...

  • Page 476

    Chapter 8: using the command line interface 458 config:# sensor inletpole upperwarning set the lower critical threshold for an inlet pole: config:# sensor inletpole lowercritical set the lower warning threshold for an inlet pole: config:# sensor inletpole lowerwarning set the inlet pole's deassertio...

  • Page 477

    Chapter 8: using the command line interface 459 note: if the requested sensor type is not supported, the "sensor is not available" message is displayed. • is one of the options: enable , disable or a numeric value. Option description enable enables the specified threshold for the specified inlet pol...

  • Page 478

    Chapter 8: using the command line interface 460 config:# sensor ocp lowercritical set the lower warning threshold for an overcurrent protector: config:# sensor ocp lowerwarning set the deassertion hysteresis for an overcurrent protector: config:# sensor ocp hysteresis set the assertion timeout for a...

  • Page 479

    Chapter 8: using the command line interface 461 • is a numeric value that is assigned to the hysteresis for the specified overcurrent protector sensor. See "to de-assert" and deassertion hysteresis (on page 603). • is a number in samples that is assigned to the assertion timeout for the specified ov...

  • Page 480

    Chapter 8: using the command line interface 462 config:# sensor externalsensor assertiontimeout variables: • is the id number of the environmental sensor that you want to configure. The id number is available in the px2 web interface or using the command "show externalsensors " in the cli. It is an ...

  • Page 481

    Chapter 8: using the command line interface 463 example 1 - upper critical threshold for a temperature sensor the following command sets the upper critical threshold of the environmental "temperature" sensor with the id number 2 to 40 degrees celsius. It also enables the upper critical threshold if ...

  • Page 482

    Chapter 8: using the command line interface 464 actuator configuration commands an actuator configuration command begins with actuator . You can configure the name and location parameters of an individual actuator. You can configure various parameters for one actuator at a time. See multi-command sy...

  • Page 483

    Chapter 8: using the command line interface 465 note: to specify the z coordinate using the rack units, see setting the z coordinate format for environmental sensors (on page 373). • is a sentence or paragraph comprising up to 64 ascii printable characters, and it must be enclosed in quotes. Example...

  • Page 484

    Chapter 8: using the command line interface 466 • is the number of successful pings for declaring the monitored device "reachable." valid range is 0 to 200. • is the number of consecutive unsuccessful pings for declaring the monitored device "unreachable." valid range is 1 to 100. • is the wait time...

  • Page 485

    Chapter 8: using the command line interface 467 config:# serverreachability modify ipaddress enable or disable the ping monitoring feature for the device: config:# serverreachability modify pingmonitoringenabled modify the number of successful pings for declaring "reachable": config:# serverreachabi...

  • Page 486

    Chapter 8: using the command line interface 468 config:# serverreachability modify numberoffailurestodisable variables: • is a number representing the sequence of the it device in the server monitoring list. • is the ip address or host name of the it device whose settings you want to modify. • is on...

  • Page 487

    Chapter 8: using the command line interface 469 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 px2 device is enabled. Config:# en...

  • Page 488

    Chapter 8: using the command line interface 470 specifying the energywise secret this command syntax specifies the password (secret) to enter the cisco ® energywise domain. Config:# energywise secret variables: • is a string comprising up to 127 ascii printable characters. Spaces and asterisks are n...

  • Page 489

    Chapter 8: using the command line interface 471 example - setting up energywise the following command sets up two cisco ® energywise-related features. Config:# energywise enabled true port 10288 results: • the energywise feature implemented on the px2 is enabled. • the udp port is set to 10288. Asse...

  • Page 490

    Chapter 8: using the command line interface 472 specifying the number of rack units this command syntax specifies the total number of rack units on an asset strip connected to the px2 device. Config:# assetstrip numberofrackunits note: a rack unit refers to a tag port on the asset strips. Variables:...

  • Page 491

    Chapter 8: using the command line interface 473 specifying the rack unit numbering offset this command syntax specifies the starting number of rack units on the asset strips connected to the px2 device. Config:# assetstrip rackunitnumberingoffset variables: • is the number of the feature port where ...

  • Page 492

    Chapter 8: using the command line interface 474 setting led colors for connected tags this command syntax sets the led color for all rack units on the asset strip #1 to indicate the presence of a connected asset tag. Config:# assetstrip ledcolorforconnectedtags variables: • is the hexadecimal rgb va...

  • Page 493

    Chapter 8: using the command line interface 475 naming a rack unit this command syntax assigns or changes the name of the specified rack unit on the specified asset strip. Config:# rackunit name "" variables: • is the number of the feature port where the selected asset strip is physically connected....

  • Page 494

    Chapter 8: using the command line interface 476 mode description manual this option enables selection of a different led color and led mode for the specified rack unit. When this option is selected, see setting an led color for a rack unit (on page 476) and setting an led mode for a rack unit (on pa...

  • Page 495

    Chapter 8: using the command line interface 477 setting an led mode for a rack unit this command syntax sets the led mode for a specific rack unit on the specified asset strip. You need to set a rack unit's led mode only when the led operation mode of this rack unit has been set to "manual." config:...

  • Page 496

    Chapter 8: using the command line interface 478 example 2 - rack unit naming the following command assigns the name "linux server" to the rack unit whose index number is 25 on the asset sensor#1. Config:# rackunit 1 25 name "linux server" serial port configuration commands a serial port configuratio...

  • Page 497

    Chapter 8: using the command line interface 479 forcing the device detection mode this command forces the serial port on the px2 to enter a specific device detection mode. Config:# serial devicedetectiontype variables: • is one of the detection modes: automatic , forceconsole , forceanalogmodem, or ...

  • Page 498

    Chapter 8: using the command line interface 480 multi-command syntax to shorten the configuration time, you can combine various configuration commands in one command to perform all of them at a time. All combined commands must belong to the same configuration type, such as commands prefixed with net...

  • Page 499

    Chapter 8: using the command line interface 481 example 3 - combination of ssid and psk parameters this multi-command syntax configures both ssid and psk parameters simultaneously for the wireless feature. Config:# network wireless ssid myssid psk encryp_key results: • the ssid value is set to myssi...

  • Page 500

    Chapter 8: using the command line interface 482 enabling or disabling load shedding this section applies to outlet-switching capable models only. This command determines whether to enter or exit from the load shedding mode. # loadshedding after performing the above command, px2 prompts you to confir...

  • Page 501

    Chapter 8: using the command line interface 483 power control operations this section applies to outlet-switching capable models only. Outlets on the px2 device can be turned on or off or power cycled through the cli. Besides, you can cancel the power-on process while the px2 is powering on all outl...

  • Page 502

    Chapter 8: using the command line interface 484 if you entered the command without "/y", a message appears, prompting you to confirm the operation. Then: type y to confirm the operation, or type n to abort the operation turning off the outlet(s) this section applies to outlet-switching capable model...

  • Page 503

    Chapter 8: using the command line interface 485 if you entered the command without "/y", a message appears, prompting you to confirm the operation. Then: type y to confirm the operation, or type n to abort the operation power cycling the outlet(s) this section applies to outlet-switching capable mod...

  • Page 504

    Chapter 8: using the command line interface 486 if you entered the command without "/y", a message appears, prompting you to confirm the operation. Then: type y to confirm the operation, or type n to abort the operation canceling the power-on process this section applies to outlet-switching capable ...

  • Page 505

    Chapter 8: using the command line interface 487 switching on an actuator this command syntax turns on one actuator. # control actuator on to quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation. # control actuator on /y variables: • is an actu...

  • Page 506

    Chapter 8: using the command line interface 488 if you entered the command without "/y", a message appears, prompting you to confirm the operation. Then: type y to confirm the operation, or type n to abort the operation example - turning on a specific actuator the following command turns on the actu...

  • Page 507

    Chapter 8: using the command line interface 489 restarting the pdu this command restarts the px2 device. It is not a factory default reset. To restart the px2 device: 1. Ensure you have entered administrator mode and the # prompt is displayed. 2. Type either of the following commands to restart the ...

  • Page 508

    Chapter 8: using the command line interface 490 if you entered the command without "/y", a message appears prompting you to confirm the operation. Type y to confirm the reset or n to abort it. Variables: • is the inlet number. Resetting to factory defaults the following commands restore all settings...

  • Page 509

    Chapter 8: using the command line interface 491 quitting diagnostic mode to quit the diagnostic mode, use this command: diag> exit the # or > prompt appears after pressing enter, indicating that you have entered the administrator or user mode. See different cli modes and prompts (on page 334). Diagn...

  • Page 510

    Chapter 8: using the command line interface 492 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 ho...

  • Page 511

    Chapter 8: using the command line interface 493 tracing the route this command syntax traces the network route between your px2 device and a network host. Diag> traceroute variables: • is the name or ip address of the host you want to trace. Example - ping command the following command checks the ne...

  • Page 512

    Chapter 8: using the command line interface 494 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 wor...

  • Page 513

    495 you can perform a secure copy (scp) command to update the px2 firmware, do bulk configuration, or back up and restore the configuration. In this chapter firmware update via scp ......................................................................... 495 bulk configuration via scp .................

  • Page 514

    Chapter 9: using scp commands 496 scp example: scp pdu-px2-030000-41270.Bin admin@192.168.87.50:/fwupdate windows pscp command: pscp in windows works in a similar way to the scp.  pscp @ ip>:/fwupdate bulk configuration via scp like performing bulk configuration via the web interface, there are two...

  • Page 515

    Chapter 9: using scp commands 497 3. The system copies the configuration included in the file "bulk_config.Xml" to another px2, and displays the following message. Starting restore operation. The connection will be closed now. Scp examples: • save operation: scp admin@192.168.87.50:/bulk_config.Xml ...

  • Page 516

    Chapter 9: using scp commands 498 scp backup_settings.Xml @ ip>:/settings_restore is the "admin" or any user profile with the administrator privileges. Is the ip address of the px2 whose settings you want to restore. 2. Type the user password when prompted. 3. The system copies the configuration inc...

  • Page 517

    Chapter 9: using scp commands 499 3. The system saves the diagnostic data from the px2 to a file named "diag-data.Tgz." scp example: scp admin@192.168.87.50:/diag-data.Tgz windows pscp command: pscp in windows works in a similar way to the scp.  pscp @:/diag-data.Tgz.

  • Page 518

    500 in this chapter maximum ambient operating temperature ........................................... 500 serial rs-232 "db9" port pinouts ........................................................... 500 sensor rj-12 port pinouts ..........................................................................

  • Page 519

    Appendix a: specifications 501 rj-12 pin/signal definition pin no. Signal direction description 1 +12v ― power (500ma, fuse protected) 2 gnd ― signal ground 3 ― ― ― 4 ― ― ― 5 gnd ― signal ground 6 1-wire 1-wire signal for external environmental sensor packages feature rj-45 port pinouts rj-45 pin/si...

  • Page 520

    502 px2 series model ____________ px2 series serial number ____________ outlet 1 outlet 2 outlet 3 model model model serial number serial number serial number use use use outlet 4 outlet 5 outlet 6 model model model serial number serial number serial number use use use appendix b equipment setup wor...

  • Page 521

    Appendix b: equipment setup worksheet 503 outlet 7 outlet 8 outlet 9 model model model serial number serial number serial number use use use outlet 10 outlet 11 outlet 12 model model model serial number serial number serial number use use use outlet 13 outlet 14 outlet 15 model model model serial nu...

  • Page 522

    Appendix b: equipment setup worksheet 504 outlet 16 outlet 17 outlet 18 model model model serial number serial number serial number use use use outlet 19 outlet 20 outlet 21 model model model serial number serial number serial number use use use.

  • Page 523

    Appendix b: equipment setup worksheet 505 outlet 22 outlet 23 outlet 24 model model model serial number serial number serial number use use use types of adapters _________________________________________________________ types of cables _________________________________________________________ name o...

  • Page 524

    506 you can accomplish part or all of the following tasks simultaneously by plugging a usb flash drive which contains one or several special configuration files into the px2. • configuration changes • firmware upgrade • downloading diagnostic data tip: you can also accomplish the same tasks via the ...

  • Page 525

    Appendix c: configuration or firmware upgrade with a usb drive 507 configuration files there are three types of configuration files. • fwupdate.Cfg: this file must be always present for performing configuration or firmware upgrade tasks. See fwupdate.Cfg (on page 508). • config.Txt: this file is use...

  • Page 526

    Appendix c: configuration or firmware upgrade with a usb drive 508 fwupdate.Cfg the configuration file, fwupdate.Cfg , is an ascii text file containing key-value pairs, one per line. Each value in the file must be separated by an equal sign (=), without any surrounding spaces. Keys are not case sens...

  • Page 527

    Appendix c: configuration or firmware upgrade with a usb drive 509 • if the specified firmware file is the same as the current firmware version of your px2, no firmware upgrade is performed unless you have set the option "force_update" to true. Force_update • if this option is set to true, the firmw...

  • Page 528

    Appendix c: configuration or firmware upgrade with a usb drive 510 • the default value is serial:1, making the px2 search for its serial number in the first column. • this option is used only if the "device_list" option has been set. Collect_diag • if this option is set to true, the diagnostic data ...

  • Page 529

    Appendix c: configuration or firmware upgrade with a usb drive 511 • additional configuration keys set via the config.Txt file will be applied after performing the configuration restore operation. • this option cannot be used with the option "bulk_config_restore." • if a firmware upgrade will be per...

  • Page 530

    Appendix c: configuration or firmware upgrade with a usb drive 512 config.Txt to perform device configuration using a usb drive, you must: • copy the device configuration file "config.Txt" to the root directory of the usb drive. • reference the "config.Txt" file in the config option of the "fwupdate...

  • Page 531

    Appendix c: configuration or firmware upgrade with a usb drive 513 special configuration keys: there are 3 special configuration keys that are prefixed with magic:. A special key that sets a user account's password without knowing the firmware's internal encryption/hashing algorithms is implemented ...

  • Page 532

    Appendix c: configuration or firmware upgrade with a usb drive 514 devices.Csv if there are device-specific settings to configure, you must create a device list configuration file - devices.Csv , to store unique data of each px2. This file must be: • an excel file in the csv format. • copied to the ...

  • Page 533

    Appendix c: configuration or firmware upgrade with a usb drive 515 creating configuration files via mass deployment utility the mass deployment utility is an excel file that lets you fill in basic information required for the three configuration files, such as the admin account and password. After e...

  • Page 534

    Appendix c: configuration or firmware upgrade with a usb drive 516 6. Verify that at least 3 configuration files are created - fwupdate.Cfg , config.Txt and devices.Csv . You are ready to configure or upgrade any px2 with these files. See configuration or firmware upgrade with a usb drive (on page 5...

  • Page 535

    Appendix c: configuration or firmware upgrade with a usb drive 517 illustration: in this example, we will encrypt the word "private", which is the value of the snmp write community in the "config.Txt" file. 1. In the cli, type the following command to encrypt "private." 2. The cli generates and show...

  • Page 536

    Appendix c: configuration or firmware upgrade with a usb drive 518 4. The px2 performs the firmware upgrade. The upgrade message "fup" is shown on the front panel display. Tip: you can remove the usb drive and plug it into another px2 for firmware upgrade when the firmware upgrade message displays. ...

  • Page 537

    519 if a tftp server is available, you can use it and appropriate configuration files to perform any or all of the following tasks for a large number of px2 devices in the same network. • initial deployment • configuration changes • firmware upgrade • downloading diagnostic data this feature is dras...

  • Page 538

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 520 config.Txt devices.Csv note: supported syntax of "fwupdate.Cfg" and "config.Txt" may vary based on different firmware versions. If you have existing configuration files, it is suggested to double check with raritan technical suppor...

  • Page 539

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 521 • all required configuration files are available in the tftp root directory. See bulk configuration/upgrade procedure (on page 519). If you are going to upload any px2 diagnostic file or create a log file in the tftp server, the fi...

  • Page 540

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 522 the vendor class is named "raritan pdu" in this illustration. 2. Define one dhcp standard option - vendor class identifier. A. Right-click the ipv4 node in dhcp to select set predefined options..

  • Page 541

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 523 b. Select dhcp standard options in the "option class" field, and vendor class identifier in the "option name" field. Leave the string field blank. 3. Add three options to the new vendor class "raritan pdu" in the same dialog..

  • Page 542

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 524 a. Select raritan pdu in the "option class" field. B. Click add to add the first option. Type "pdu-tftp-server" in the name field, select ip address as the data type, and type 1 in the code field..

  • Page 543

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 525 c. Click add to add the second option. Type "pdu-update-control-file" in the name field, select string as the data type, and type 2 in the code field. D. Click add to add the third one. Type "pdu-update-magic" in the name field, se...

  • Page 544

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 526 the policy is named "pdu" in this illustration. C. Click add to add a new condition..

  • Page 545

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 527 d. Select the vendor class "raritan pdu" in the value field, click add and then ok. E. Click next..

  • Page 546

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 528 f. Select dhcp standard options in the "vendor class" field, select "060 vendor class identifier" from the available options list, and type "raritan pdu 1.0" in the "string value" field..

  • Page 547

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 529 g. Select the "raritan pdu" in the "vendor class" field, select "001 pdu-tftp-server" from the available options list, and type your tftp server's ipv4 address in the "ip address" field..

  • Page 548

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 530 h. Select "002 pdu-update-control-file" from the available options list, and type the filename "fwupdate.Cfg" in the "string value" field. I. Select "003 pdu-update-magic" from the available options list, and type any string in the...

  • Page 549

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 531 important: the magic cookie is transmitted to and stored in px2 at the time of executing the "fwupdate.Cfg" commands. The dhcp/tftp operation is triggered only when there is a mismatch between the magic cookie in dhcp and the one s...

  • Page 550

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 532 a. Right-click the ipv6 node in dhcp to select define vendor classes. B. Click add to add a new vendor class. C. Specify a unique name for the vendor class, type "13742" in the "vendor id (iana)" field, and type the binary codes of...

  • Page 551

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 533 2. Add three options to the "raritan pdu 1.0" vendor class. A. Right-click the ipv6 node in dhcp to select set predefined options..

  • Page 552

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 534 b. Select raritan pdu 1.0 in the "option class" field. C. Click add to add the first option. Type "pdu-tftp-server" in the name field, select ip address as the data type, and type 1 in the code field..

  • Page 553

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 535 d. Click add to add the second option. Type "pdu-update-control-file" in the name field, select string as the data type, and type 2 in the code field. E. Click add to add the third one. Type "pdu-update-magic" in the name field, se...

  • Page 554

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 536 c. Select "raritan pdu 1.0" in the "vendor class" field, select "00001 pdu-tftp-server" from the available options list, and type your tftp server's ipv6 address in the "ipv6 address" field..

  • Page 555

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 537 d. Select "00002 pdu-update-control-file" from the available options list, and type the filename "fwupdate.Cfg" in the "string value" field. E. Select "00003 pdu-update-magic" from the available options list, and type any string in...

  • Page 556

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 538 important: the magic cookie is transmitted to and stored in px2 at the time of executing the "fwupdate.Cfg" commands. The dhcp/tftp operation is triggered only when there is a mismatch between the magic cookie in dhcp and the one s...

  • Page 557

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 539 configure the same option in dhcp accordingly. The px2 accepts the configuration or firmware upgrade only when this value in dhcp matches. 3. Set the following three sub-options in the "vendor-encapsulated-options" (option 43). Cod...

  • Page 558

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 540 ipv4 illustration example in dhcpd.Conf: dhcp ipv6 configuration in linux modify the "dhcpd6.Conf" file for ipv6 settings when your dhcp server is running linux. Required linux ipv6 settings in dhcp: 1. Locate and open the "dhcpd6....

  • Page 559

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 541 code 3 (pdu-update-magic) = any string this third option/code is the magic cookie to prevent the fwupdate.Cfg commands from being executed repeatedly. It does not matter whether the ipv6 magic cookie is identical to or different fr...

  • Page 560

    542 you can use either the reset button or the command line interface (cli) to reset the px2. Important: exercise caution before resetting the px2 to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on. Only active energy...

  • Page 561

    Appendix e: resetting to factory defaults 543 this diagram shows the location of the reset button on zero u models. This diagram shows the location of the reset button on 1u models. This diagram shows the location of the reset button on 2u models. Note: hyperterminal is available on windows operatin...

  • Page 562

    Appendix e: resetting to factory defaults 544 3. Log in to the cli by typing the user name "admin" and its password. 4. After the # system prompt appears, type either of the following commands and press enter. # reset factorydefaults -- or -- # reset factorydefaults /y 5. If you entered the command ...

  • Page 563

    545 this section provides an ldap example for illustrating the configuration procedure using microsoft active directory ® (ad). To configure ldap authentication, four main steps are required: a. Determine user accounts and roles (groups) intended for the px2 b. Create user groups for the px2 on the ...

  • Page 564

    Appendix f: ldap configuration illustration 546 step b. Configure user groups on the ad server you must create the groups (roles) for the px2 on the ad server, and then make appropriate users members of these groups. In this illustration, we assume: • the groups (roles) for the px2 are named px_admi...

  • Page 565

    Appendix f: ldap configuration illustration 547 step c. Configure ldap authentication on the px2 device you must enable and set up ldap authentication properly on the px2 device to use external authentication. In the illustration, we assume: • the dns server settings have been configured properly. S...

  • Page 566

    Appendix f: ldap configuration illustration 548 field/setting do this... Bind dn, bind password, confirm bind password skip the three fields because of anonymous bind. Base dn for search type dc=techadssl,dc=com as the starting point where your search begins on the ad server. Login name attribute en...

  • Page 567

    Appendix f: ldap configuration illustration 549 2. Click to add a new role. A. Type px_user in the role name field. B. Type a description for the px_user role in the description field. In this example, we type "view px settings" to describe the role. C. In the privileges list, select unrestricted vi...

  • Page 568

    Appendix f: ldap configuration illustration 550 to create the px_admin role with full permissions assigned: 1. Click to add another role. A. Type px_admin in the role name field. B. Type a description for the px_admin role in the description field. In this example, we type "includes all px privilege...

  • Page 569

    551 in this chapter returning user group information .......................................................... 551 setting the registry to permit write operations to the schema ........... 552 creating a new attribute .......................................................................... 552 ad...

  • Page 570

    Appendix g: updating the ldap schema 552 setting the registry to permit write operations to the schema to allow a domain controller to write to the schema, you must set a registry entry that permits schema updates. To permit write operations to the schema: 1. Right-click the active directory ® schem...

  • Page 571

    Appendix g: updating the ldap schema 553 3. Click new and then choose attribute. When the warning message appears, click continue and the create new attribute dialog appears. 4. Type rciusergroup in the common name field. 5. Type rciusergroup in the ldap display name field. 6. Type 1.3.6.1.4.1.13742...

  • Page 572

    Appendix g: updating the ldap schema 554 2. Scroll to the user class in the right pane and right-click it. 3. Choose properties from the menu. The user properties dialog appears. 4. Click the attributes tab to open it. 5. Click add..

  • Page 573

    Appendix g: updating the ldap schema 555 6. Choose rciusergroup from the select schema object list. 7. Click ok in the select schema object dialog. 8. Click ok in the user properties dialog. Updating the schema cache to update the schema cache: 1. Right-click active directory ® schema in the left pa...

  • Page 574

    Appendix g: updating the ldap schema 556 3. Go to the directory where the support tools were installed. Run adsiedit.Msc. The adsi edit window opens. 4. Open the domain. 5. In the left pane of the window, select the cn=users folder..

  • Page 575

    Appendix g: updating the ldap schema 557 6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select properties. 7. Click the attribute editor tab if it is not already open. Choose rciusergroup from the attributes list. 8. Click edit. The strin...

  • Page 576

    558 this section provides illustrations for configuring radius authentication. One illustration is based on the microsoft ® network policy server (nps), and the other is based on a freeradius server. The following steps are required for any radius authentication: 1. Configure radius authentication o...

  • Page 577

    Appendix h: radius configuration illustration 559 b. On the nps, configure connection request policies and the standard attribute. See step b: configure connection policies and standard attributes (on page 563). Some configuration associated with microsoft active directory (ad) is also required for ...

  • Page 578

    Appendix h: radius configuration illustration 560 2. Right-click nps (local), and select properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your px2. In this example, they are 1812 and 1813. Then close this dialog..

  • Page 579

    Appendix h: radius configuration illustration 561 3. Under "radius clients and servers," right-click radius client and select new radius client. The new radius client dialog appears. 4. Do the following to add your px2 to nps: a. Verify the "enable this radius client" checkbox is selected. B. Type a...

  • Page 580

    Appendix h: radius configuration illustration 562 f. Type the shared secret in the "shared secret" and "confirm shared secret" fields. The shared secret must be the same as the one specified on your px2. 5. Click ok..

  • Page 581

    Appendix h: radius configuration illustration 563 step b: configure connection policies and standard attributes you need to configure the following for connection request policies: • ip address or host name of the px2 • connection request forwarding method • authentication method(s) • standard radiu...

  • Page 582

    Appendix h: radius configuration illustration 564 2. Right-click connection request policies and select new. The new connection request policy dialog appears. 3. Type a descriptive name for identifying this policy in the "policy name" field..

  • Page 583

    Appendix h: radius configuration illustration 565 you can leave the "type of network access server" field to the default -- unspecified..

  • Page 584

    Appendix h: radius configuration illustration 566 4. Click next to show the "specify conditions" screen. Click add. 5. The "select condition" dialog appears. Click add..

  • Page 585

    Appendix h: radius configuration illustration 567 6. The nas ipv4 address dialog appears. Type the px2 ip address -- 192.168.56.29 , and click ok. 7. Click next in the new connection request policy dialog. 8. Select "authenticate requests on this server" because a local nps server is used in this ex...

  • Page 586

    Appendix h: radius configuration illustration 568 note: connection request forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options: override network policy authentication settings chap -- the px2 uses "chap"...

  • Page 587

    Appendix h: radius configuration illustration 569 note: if your px2 uses pap, then select "pap.".

  • Page 588

    Appendix h: radius configuration illustration 570 10. Select standard to the left of the dialog and then click add..

  • Page 589

    Appendix h: radius configuration illustration 571 11. Select filter-id from the list of attributes and click add..

  • Page 590

    Appendix h: radius configuration illustration 572 12. In the attribute information dialog, click add. 13. Select string, type raritan:g{admin} in the text box, and then click ok..

  • Page 591

    Appendix h: radius configuration illustration 573 admin inside the curved brackets {} is the existing role on the px2. It is recommended to use the admin role to test this configuration. The role name is case sensitive..

  • Page 592

    Appendix h: radius configuration illustration 574 14. The new attribute is added. Click ok..

  • Page 593

    Appendix h: radius configuration illustration 575 15. Click next to continue..

  • Page 594

    Appendix h: radius configuration illustration 576 16. A summary showing connection request policy settings is displayed. Click finish to close the dialog. Freeradius standard attribute illustration with standard attributes, no dictionary files are required. You simply add all user data, including us...

  • Page 595

    Appendix h: radius configuration illustration 577 steve cleartext-password := "test123" filter-id = "raritan:g{admin}", filter-id = "raritan:g{systemtester}" vendor-specific attributes you must specify the following properties when using a radius vendor-specific attribute (vsa). • vendor code = 1374...

  • Page 596

    Appendix h: radius configuration illustration 578 step a: add your px2 as a radius client the radius implementation on a px2 follows the standard radius internet engineering task force (ietf) specification so you must select "radius standard" as its vendor name when configuring the nps server. Presu...

  • Page 597

    Appendix h: radius configuration illustration 579 2. Right-click nps (local), and select properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your px2. In this example, they are 1812 and 1813. Then close this dialog..

  • Page 598

    Appendix h: radius configuration illustration 580 3. Under "radius clients and servers," right-click radius client and select new radius client. The new radius client dialog appears. 4. Do the following to add your px2 to nps: a. Verify the "enable this radius client" checkbox is selected. B. Type a...

  • Page 599

    Appendix h: radius configuration illustration 581 f. Type the shared secret in the "shared secret" and "confirm shared secret" fields. The shared secret must be the same as the one specified on your px2. 5. Click ok..

  • Page 600

    Appendix h: radius configuration illustration 582 step b: configure connection policies and vendor-specific attributes you need to configure the following for connection request policies: • ip address or host name of the px2 • connection request forwarding method • authentication method(s) • standar...

  • Page 601

    Appendix h: radius configuration illustration 583 2. Right-click connection request policies and select new. The new connection request policy dialog appears. 3. Type a descriptive name for identifying this policy in the "policy name" field..

  • Page 602

    Appendix h: radius configuration illustration 584 you can leave the "type of network access server" field to the default -- unspecified..

  • Page 603

    Appendix h: radius configuration illustration 585 4. Click next to show the "specify conditions" screen. Click add. 5. The "select condition" dialog appears. Click add..

  • Page 604

    Appendix h: radius configuration illustration 586 6. The nas ipv4 address dialog appears. Type the px2 ip address -- 192.168.56.29 , and click ok. 7. Click next in the new connection request policy dialog. 8. Select "authenticate requests on this server" because a local nps server is used in this ex...

  • Page 605

    Appendix h: radius configuration illustration 587 note: connection request forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options: override network policy authentication settings chap -- the px2 uses "chap"...

  • Page 606

    Appendix h: radius configuration illustration 588 note: if your px2 uses pap, then select "pap." 10. Select vendor specific to the left of the dialog, and click add. The add vendor specific attribute dialog appears. 11. Select custom in the vendor field, and click add. The attribute information dial...

  • Page 607

    Appendix h: radius configuration illustration 589 note that multiple roles are separated with a space. 16. Click ok. Freeradius vsa illustration a vendor-specific dictionary file is required for the vendor-specific-attribute configuration on freeradius. Therefore, there are two major configuration s...

  • Page 608

    Appendix h: radius configuration illustration 590 vendor raritan 13742 begin-vendor raritan attribute raritan-user-roles 26 string end-vendor raritan step b -- create a user profile for "steve" in freeradius: 1. Go to this location: /etc/raddb/users. 2. Add the data of the user "steve" by typing the...

  • Page 609

    Appendix h: radius configuration illustration 591 2. Right-click nps (local) and select "register server in active directory." 3. Click ok, and then ok again. To grant px2 users remote access permission: 1. Open active directory users and computers..

  • Page 610

    Appendix h: radius configuration illustration 592 2. Open the properties dialog of the user whom you want to grant the access permission. 3. Click the dial-in tab and select the "allow access" checkbox. To enable reversible encryption for chap authentication: 1. Open active directory users and compu...

  • Page 611

    Appendix h: radius configuration illustration 593 3. Click the account tab and select the "store password using reversible encryption" checkbox..

  • Page 612

    594 in this chapter mac address ............................................................................................. 594 reserving ip addresses in dhcp servers ............................................... 595 sensor threshold settings ........................................................

  • Page 613

    Appendix i: additional px2 information 595 reserving ip addresses in dhcp servers the px2 uses its serial number as the client identifier in the dhcp request. Therefore, to successfully reserve an ip address for the px2 in a dhcp server, use the px2 device's serial number as the unique id instead of...

  • Page 614

    Appendix i: additional px2 information 596 interface client identifier conversion wireless peg1a00003-wireless = 50 45 47 31 41 30 30 30 30 33 2d 57 49 52 45 4c 45 53 53 the suffix comprising the dash symbol and the word "wireless" is also converted. Bridge peg1a00003 = 50 45 47 31 41 30 30 30 30 33...

  • Page 615

    Appendix i: additional px2 information 597 reserving ip in linux there are two methods to reserve the ip address of any network interface in the standard linux dhcp server (isc dhcp server): • convert an interface's client identifier into hexadecimal ascii codes. • use an interface's original client...

  • Page 616

    Appendix i: additional px2 information 598 for example, the client identifier of the ethernet interface looks like the following: \000 peg1a00003 3. Now enter the original client identifier with the following syntax. The client identifier is enclosed in quotation marks. Host mypx { option dhcp-clien...

  • Page 617

    Appendix i: additional px2 information 599 above upper critical upper critical above upper warning upper warning normal lower warning below lower warning lower critical below lower critical available sensor states:.

  • Page 618

    Appendix i: additional px2 information 600 the more thresholds are enabled for a sensor, the more sensor states are available for it. The "normal' state is always available regardless of whether any threshold is enabled. For example: • when a sensor only has the upper critical threshold enabled, it ...

  • Page 619

    Appendix i: additional px2 information 601 "to assert" and assertion timeout if multiple sensor states are available for a specific sensor, the px2 asserts a state for it whenever a bad state change occurs. To assert a state: to assert a state is to announce a new, "worse" state. Below are bad state...

  • Page 620

    Appendix i: additional px2 information 602 in the threshold settings, the assertion timeout field postpones or even cancels the "assertion" action. It determines how long a sensor must be in the "worse" new state before the px2 triggers the "assertion" action. If that sensor changes its state again ...

  • Page 621

    Appendix i: additional px2 information 603 "to de-assert" and deassertion hysteresis after the px2 asserts a worse state for a sensor, it may de-assert that state later on if the readings improve. To de-assert a state: to de-assert a state is to announce the end of the previously-asserted worse stat...

  • Page 622

    Appendix i: additional px2 information 604 in the threshold settings, the deassertion hysteresis field determines a new level to trigger the "deassertion" action. This function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system when the temperature exceeds ...

  • Page 623

    Appendix i: additional px2 information 605 assumption: upper warning threshold is enabled. Upper warning = 20 (degrees celsius) deassertion hysteresis = 3 (degrees celsius) "deassertion" level = 20-3 = 17 (degrees celsius) when the px2 detects that a temperature sensor's reading drops below 20 degre...

  • Page 624

    Appendix i: additional px2 information 606 2. After installing the pdview, launch it. Below illustrates the pdview screen for android devices. 3. Connect your mobile device to the usb port of the px2. Your mobile device type determines which usb port on the px2 shall be used to connect the mobile de...

  • Page 625

    Appendix i: additional px2 information 607 the pdview shows a "connected" message when it detects the physical connection to the px2. 4. Log in to the pdview app at the login prompt. Now you can view limited px2 information or even change some settings. Tip: to skip the final login step, you can cli...

  • Page 626

    Appendix i: additional px2 information 608 altitude (meters) altitude (feet) correction factor 425 1394 1.00 500 1640 1.01 740 2428 1.04 1500 4921 1.15 2250 7382 1.26 3000 9842 1.38 unbalanced current calculation unbalanced current information is available on 3-phase models only. This section explai...

  • Page 627

    Appendix i: additional px2 information 609 example: • each line's current: l1 = 5.5 amps l2 = 5.2 amps l3 = 4.0 amps • average current: (5.5+5.2+4.0) / 3 = 4.9 amps • l1 current unbalance: (5.5 - 4.9) / 4.9 = 0.1224 • l2 current unbalance: (5.2 - 4.9) / 4.9 = 0.0612 • l3 current unbalance: (4.0 - 4....

  • Page 628

    Appendix i: additional px2 information 610 ways to probe existing user profiles this section indicates available ways to query existing user accounts on the px2. • with snmp v3 activated, you get the "user unknown" error when the user name used to authenticate does not exist. • any user with the per...

  • Page 629

    Appendix i: additional px2 information 611 role of a dns server as internet communications are carried out on the basis of ip addresses, appropriate dns server settings are required for mapping domain names (host names) to corresponding ip addresses, or the px2 may fail to connect to the given host....

  • Page 630

    Appendix i: additional px2 information 612 symptom probable cause failure to access the master device • network connection to the master device is lost. • no power is supplied to the master device. • the ethernet or wireless interface on the master device is disabled. • ipv4 (or ipv6) settings are d...

  • Page 631

    Appendix i: additional px2 information 613 symptom probable cause failure to access a slave device • network connection to the master device is lost. • the cascading cable connected to the slave device in question or any upstream device (if available) is loose or lost. • no power is supplied to the ...

  • Page 632

    Appendix i: additional px2 information 614 slave connection and disconnection events in the bridging mode, events regarding connection/disconnection of a downstream slave device via usb is not logged. However, in the port forwarding mode, whenever the connection or disconnection of a downstream slav...

  • Page 633

    Appendix i: additional px2 information 615 ping via the cli you can access the cli interface by connecting a computer to the px2 or using ssh/telnet. See ssh/telnet access (see " with ssh or telnet " on page 332) for details. You must perform the ping command in the diagnostic mode. To enter the dia...

  • Page 634

    Appendix i: additional px2 information 616 diag> ping count size timeout browsing through the online help the px2 online help is accessible over the internet. To use online help, active content must be enabled in your browser. If you are using internet explorer 7, you must enable scriplets. Consult ...

  • Page 635

    Appendix i: additional px2 information 617 9. To email any url link to the currently selected topic to any person, click the "email this page" icon in the toolbar. 10. To email your comments or suggestions regarding the online help to raritan, click the "send feedback" icon . 11. To print the curren...

  • Page 636

    618 the px2 device can work with certain raritan products to provide diverse power solutions. In this chapter dominion kx ii / iii configuration ............................................................. 618 dominion ksx ii, sx or sx ii configuration .................................................

  • Page 637

    Appendix j: integration 619 configuring rack pdu targets kx iii allows you to connect rack pdus (power strips) to kx iii ports. Kx iii rack pdu configuration is done from the kx iii port configuration page. Note: raritan recommends no more than eight (8) rack pdus (power strips) be connected to a kx...

  • Page 638

    Appendix j: integration 620 diagram key px rack pdu d2cim-pwr kx iii d2cim-pwr to rack pdu connection d2cim-pwr to kx iii target device port via cat5 cable naming the rack pdu (port page for power strips) note: px rack pdus (power strips) can be named in the px as well as in the kx iii. Once a rarit...

  • Page 639

    Appendix j: integration 621 3. Click ok..

  • Page 640

    Appendix j: integration 622 associating outlets with target devices the port page opens when you click on a port on the port configuration page. If an outlet is connected to the same server that the port is connected to, a power association can be made with the target device. A server can have up to...

  • Page 641

    Appendix j: integration 623 to turn an outlet off: 1. Click off next to the outlet you want to power off. 2. Click ok on the power off dialog. 3. Click ok on the power off confirmation dialog. The outlet will be turned off and its state will be displayed as 'off'. To cycle the power of an outlet: 1....

  • Page 642

    Appendix j: integration 624 connecting a rack pdu to connect the raritan px to the ksx ii: 1. Connect one end of a cat5 cable to the following ports of different raritan px. Px1 series: rj-45 "serial" port px2 or px3 series: rj-45 "feature" port 2. Connect the other end of the cat5 cable to either t...

  • Page 643

    Appendix j: integration 625 power control the ksx ii operation to turn on/off or power cycle a px is the same as the kx iii operation. See turning outlets on/off and cycling power (on page 622). Dominion sx and sx ii by connecting to a dominion sx or sx ii device, you can associate one or more outle...

  • Page 644

    Appendix j: integration 626 4. You can now add the px as a managed power strip to the sx ii. See configure power strips from the remote console or configure power strips using cli in the sx ii user guide or online help. Px appliance sx ii dominion sx configuring a px2 on dominion sx 1. Choose setup ...

  • Page 645

    Appendix j: integration 627 3. Type a name and description in the name and description fields. 4. Select the number of outlets from the number of outlets drop-down menu. 5. Type the port number in the port field. 6. Click ok. Power control 1. Choose power control > power strip power control. The out...

  • Page 646

    Appendix j: integration 628 checking power strip status 1. Choose power control > power strip status. 2. A status box appears, displaying details of the controlled px2, including power state of each outlet on the device. Power iq configuration sunbird's power iq is a software application that collec...

  • Page 647

    Appendix j: integration 629 dctrack sunbird's dctrack ® is a product that allows you to manage the data center. The px2 is categorized as a power item in dctrack. Dctrack offers an import wizard for conveniently adding the px2 as well as other it equipment to dctrack for management. You can use dctr...

  • Page 648

    Appendix j: integration 630 dctrack overview dctrack ® is a powerful and intelligent data center management and automation application. It has been designed by data center and it professionals to provide broad and deep visibility into the data center. It empowers data center managers to plan for gro...

  • Page 649

    Appendix j: integration 631 asset management strips and dctrack if any asset strips are connected to the px2, the px2 can transmit their information to sunbird's dctrack. All you have to do is to add the px2 to dctrack, and also add each it item where an asset tag is attached to dctrack. Note: for i...

  • Page 651

    633 1 1u and 2u port locations • 78 1u products • 2 2 2u products • 2 a a note about enabling thresholds • 329 a note about firmware upgrade time • 307 a note about infinite loop • 279 a note about untriggered rules • 280 about the interface • 330 action group • 253, 256 actuator configuration comma...

  • Page 652

    Index 634 changing an outlet's default state • 426 changing http(s) settings • 180, 203, 204, 211 changing measurement units • 437, 440 changing modbus settings • 180, 203, 209 changing ssh settings • 172, 180, 203, 208 changing telnet settings • 180, 203, 208, 330 changing the inlet name • 428 chan...

  • Page 653

    Index 635 connecting composite asset strips • 67, 71 connecting environmental sensor packages • 37, 72, 138 connecting external equipment (optional) • 37, 78 connecting regular asset strips to px2 • xvii, 61, 68 connecting the pdu to a power source • 21 connecting the px2 to a computer • xvii, 3, 23...

  • Page 654

    Index 636 e eap ca certificate example • 388, 390 editing or deleting a rule/action • 252, 276, 288 editing or deleting ip access control rules • 213 editing or deleting ping monitoring settings • 286 editing or deleting role access control rules • 215 editing or deleting roles • 177 editing or dele...

  • Page 655

    Index 637 example 1 - environmental sensor naming • 453 example 1 - ipv4 firewall control configuration • 423 example 1 - networking mode • 400 example 1 - pdu naming • 374 example 1 - time setup method • 404 example 1 - upper critical threshold for a temperature sensor • 463 example 2 • 279 example...

  • Page 656

    Index 638 initial network configuration via cli • xvii, 4, 23, 24, 25, 27, 195, 542, 543 initialization delay use cases • 112, 116 inlet • 98, 103, 104, 114, 119, 121 inlet configuration commands • 427 inlet information • 342 inlet pole sensor threshold information • 349 inlet sensor threshold infor...

  • Page 657

    Index 639 mounting zero u models using button mount • 9 mounting zero u models using claw-foot brackets • 10 mounting zero u models using l-brackets • 7 mounting zero u models using l-brackets and buttons • 13 mounting zero u models using two rear buttons • 12 multi-command syntax • 407, 413, 415, 4...

  • Page 658

    Index 640 rack-mounting the pdu • 6 radius configuration illustration • 222, 558 raritan training website • 610 rebooting the px2 device • 297, 315 record snapshots to webcam storage • 253, 258 reliability data • 362 reliability error log • 362 remembering user names and passwords • 95 request lhx/s...

  • Page 659

    Index 641 setting network service parameters • 393 setting non-critical outlets • 123, 126, 127 setting ntp parameters • 401, 405 setting outlet power-on sequence and delay • 123, 125 setting the alarmed to normal delay for dx-pir • 452 setting the authentication method • 387 setting the automatic d...

  • Page 660

    Index 642 specifying the ssh public key • 396, 438 standard attributes • 558 start or stop a lua script • 254, 266, 291, 293 static route examples • 181, 184, 191, 378, 382 step a add your px2 as a radius client • 558, 559, 577, 578 step a. Determine user accounts and roles • 545 step b configure co...

  • Page 661

    Index 643 w ways to probe existing user profiles • 610 web interface overview • 95, 616 webcam management • 99, 303, 317 what's new in the px2 user guide • xvii windows ntp server synchronization solution • 234, 235 wired network settings • 181, 182, 196, 210, 547 wireless lan diagnostic log • 189, ...