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

    Copyright © 2016 raritan, inc. Dpx2-1000-0m-v3.2.10-e march 2016 255-80-6105-00 px2-1000/2000 series user guide release 3.2.10

  • Page 2: Safety Guidelines

    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: Safety Instructions

    1. Installation of this product should only be performed by a person who has knowledge and experience with electric power. 2. Make sure the line cord is disconnected from power before physically mounting or moving the location of this product. 3. 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 2016 raritan, inc. All third-party softw...

  • Page 6

    Vi contents safety guidelines ii safety instructions iii applicable models xvi what's new in the px user guide xviii chapter 1 introduction 1 product models ..............................................................................................................................1 package content...

  • Page 7

    Contents vii preparing the installation site............................................................................................14 checking the branch circuit rating...................................................................................15 filling out the equipment setup worksheet...

  • Page 8

    Contents viii fuse replacement on 1u models .....................................................................................86 beeper .........................................................................................................................................88 chapter 6 using the w...

  • Page 9

    Contents ix access security control.............................................................................................................159 forcing https encryption..............................................................................................159 configuring the firewall.........

  • Page 10

    Contents x managing event logging ...........................................................................................................264 viewing the local event log ...........................................................................................264 viewing the wireless lan diagnos...

  • Page 11

    Contents xi chapter 7 using snmp 323 enabling snmp..........................................................................................................................323 configuring users for encrypted snmp v3 ...............................................................................324 c...

  • Page 12

    Contents xii event log.........................................................................................................................364 wireless lan diagnostic log ..........................................................................................365 server reachability information...

  • Page 13

    Contents xiii network troubleshooting...........................................................................................................492 entering diagnostic mode ...............................................................................................492 quitting diagnostic mode ......

  • Page 14

    Contents xiv firmware upgrade via usb .......................................................................................................513 appendix d bulk configuration or firmware upgrade via dhcp/tftp 514 bulk configuration/upgrade procedure......................................................

  • Page 15

    Contents xv step b: configure connection request policies .............................................................563 step c: configure a vendor-specific attribute ................................................................578 ad-related configuration..........................................

  • Page 16: Applicable Models

    Xvi this user guide is applicable to the following pdus (n indicated below represents a number). Px2-1nnn series px2-2nnn series in this user guide, px2-1nnn is called px2-1000, and px2-2nnn is called px2-2000 for convenience. Note: for information on other px2 or px3 models, see their respective on...

  • Page 17

    Applicable models xvii comparison between px2 and px3 series: features front panel display outlet latching relays number of usb-a ports sensor port type replaceable controller px2 series led display 1 rj-12 px3 phase i series character lcd display * 2 rj-45 *** px3 phase ii series dot-matrix lcd dis...

  • Page 18

    Xviii the following sections have changed or information has been added to the px user guide based on enhancements and changes to the equipment and/or user documentation. Apipa and link-local addressing (on page 2) configuring the px (on page 17) connecting the px to a computer (on page 18) installi...

  • Page 19

    What's new in the px user guide xix clearing wlan log (on page 371) enabling or disabling peripheral device auto management (on page 378) determining the ssh authentication method (on page 399) customizing the date and time (on page 406) all privileges (on page 446) setting the baud rates (on page 4...

  • Page 20: Chapter 1

    1 raritan px 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 px is distribution of power to information technology equipment such as computers and communicat...

  • Page 21

    Chapter 1: introduction 2 1u products the px device 1u bracket pack and screws a null-modem cable with db9 connectors on both ends (raritan number: 254-01-0006-00) (optional) cable retention clips for the inlet (for some models only) 2u products the px device 2u bracket pack and screws a null-modem ...

  • Page 22

    Chapter 1: introduction 3 the px previously obtained an ip address from the dhcp server, but the lease of this ip address has expired, and the lease cannot be renewed, or no new ip address can be obtained. Link-local addressing: ipv4 address: factory default is to enable ipv4 only. The link-local ip...

  • Page 23: Chapter 2

    4 this chapter describes how to rack mount a px device. To mount a zero u px2-1000 series pdu, you can use either two buttons or l-brackets that raritan provided. In this chapter rackmount safety guidelines ...................................................................4 circuit breaker orientat...

  • Page 24

    Chapter 2: rack-mounting the pdu 5 circuit breaker orientation limitation usually a pdu can be mounted in any orientation. However, when mounting a pdu with circuit breakers, you must obey these rules: circuit breakers cannot face down. For example, do not horizontally mount a zero u pdu with circui...

  • Page 25

    Chapter 2: rack-mounting the pdu 6 2. Secure the baseplates in place. Use the included l-shaped hex key to loosen the hex socket screws until the baseplate is "slightly" fastened. 3. Align the l-brackets with the baseplates so that the five screw-holes on the baseplates line up through the l-bracket...

  • Page 26

    Chapter 2: rack-mounting the pdu 7 mounting zero u models using button mount if your pdu has circuit breakers implemented, read circuit breaker orientation limitation (on page 5) before mounting it. To mount zero-u models using button mount: 1. Align the baseplates on the rear of the px device. Leav...

  • Page 27

    Chapter 2: rack-mounting the pdu 8 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 px device forward, pushing the mounting buttons through the mounting holes, then letti...

  • Page 28

    Chapter 2: rack-mounting the pdu 9 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 px device. 4. Fasten the brackets in place with a...

  • Page 29

    Chapter 2: rack-mounting the pdu 10 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 5) before mounting it. To mount zero u models using ...

  • Page 30

    Chapter 2: rack-mounting the pdu 11 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 px device forward, pushing the mount...

  • Page 31

    Chapter 2: rack-mounting the pdu 12 2. Screw the l-bracket to the device and ensure the bracket is fastened securely. 3. Repeat steps 1 to 2 to screw another l-bracket to the bottom of the device. 4. After both l-brackets are installed, you can choose either of the following ways to mount the device...

  • Page 32

    Chapter 2: rack-mounting the pdu 13 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..

  • Page 33: Chapter 3

    14 this chapter explains how to install a px device and configure it for network connectivity. In this chapter before you begin ....................................................................................14 installing cable retention clips on the inlet (optional)...........................15...

  • Page 34

    Chapter 3: installation and configuration 15 note: if necessary, contact raritan technical support for the maximum operating temperature for your model. See maximum ambient operating temperature (on page 497). 2. Allow sufficient space around the px device for cabling and outlet connections. 3. Revi...

  • Page 35

    Chapter 3: installation and configuration 16 zero u models 1u/2u models 3. Connect the power cord to the inlet, and press the clip toward the power cord until it holds the cord firmly. Zero u models 1u/2u models connecting the pdu to a power source 1. Verify that all circuit breakers on the px devic...

  • Page 36

    Chapter 3: installation and configuration 17 configuring the px you can initially configure the px by connecting it to a computer, or to a tcp/ip network that supports dhcp. Configuration using a connected computer: 1. Connect the px to a computer. See connecting the px to a computer (on page 18). 2...

  • Page 37

    Chapter 3: installation and configuration 18 connecting the px to a computer the px can be connected to a computer for configuration via one of the following ports. Ethernet port (female) usb-b port (male) rs-232 serial port (male) zero u models: to use the command line interface (cli) for configura...

  • Page 38

    Chapter 3: installation and configuration 19 note: not all serial-to-usb converters work properly with the px so raritan does not introduce the use of such converters. Direct network connection: 1. Connect one end of a standard network patch cable to the ethernet port of the px. 2. Connect the other...

  • Page 39

    Chapter 3: installation and configuration 20 3. Select the option of driver installation from a specific location, and then specify the location where both dominion-serial.Inf and dominion-serial.Cat are stored. Note: if any windows security warning appears, accept it to continue the installation. 4...

  • Page 40

    Chapter 3: installation and configuration 21 below indicates the ethernet port on px2 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: accidentally plugging an rs-232 rj-45 connector into the ...

  • Page 41

    Chapter 3: installation and configuration 22 note: to use the edimax ew-7722und or raritan usb wifi wireless lan adapter to connect to an 802.11n wireless network, the handshake timeout setting must be changed to 500 or greater, or the wireless connection will fail. Supported wireless lan configurat...

  • Page 42

    Chapter 3: installation and configuration 23 tip: for a usb connection, you can determine the com port by choosing control panel > system > hardware > device manager, and locating the "dominion px2 serial console" under the ports group. 3. In the communications program, press enter to send a carriag...

  • Page 43

    Chapter 3: installation and configuration 24 to set use this command ssid network wireless ssid = ssid string if necessary, configure more wireless parameters shown in the following table. To set use this command bssid network wireless bssid = ap mac address or none authentication method network wir...

  • Page 44

    Chapter 3: installation and configuration 25 to set use this command eap ca certificate network wireless eapcacertificate when prompted to enter the ca certificate, open the certificate with a text editor, copy and paste the content into the communications program. The content to be copied from the ...

  • Page 45

    Chapter 3: installation and configuration 26 to set use this command ip address returned by the dns server network ip dnsresolverpreference = preferv4 or preferv6 e. After enabling the ipv4 or ipv6 protocol in the earlier step, configure the ipv4 or ipv6 network parameters. To set use this command i...

  • Page 46

    Chapter 3: installation and configuration 27 for static ip configuration, configure these parameters. To set use this command static ipv4 or ipv6 address network ipaddress address> = static ip address ipv4 subnet mask network ipv4 subnetmask = subnet mask ipv4 or ipv6 gateway network gateway address...

  • Page 47

    Chapter 3: installation and configuration 28 tip: you can type "show network wireless" to display a shortened version of wireless settings. 11. If all are correct, type exit to log out of the px. If any are incorrect, repeat steps 7 to 10 to change network settings. The ip address configured may tak...

  • Page 48

    Chapter 3: installation and configuration 29 cascading the px via usb you can use usb cables to cascade up to eight raritan devices. All devices in the usb-cascading chain share the ethernet connectivity. Different raritan models can be cascaded as long as they are running an appropriate firmware. T...

  • Page 49

    Chapter 3: installation and configuration 30 4. Connect the usb-a port of the master device to the usb-b port of an additional px via a usb cable. This additional device is slave 1. 5. Connect slave 1's usb-a port to the usb-b port of an additional px via a usb cable. The second additional device is...

  • Page 50

    Chapter 3: installation and configuration 31 number device role master device slave 1 slave 2 slave 3 note: to remotely identify the master and slave devices and their positions in the usb-cascading configuration, see identifying cascaded devices (on page 108). Tip: the usb-cascading configuration c...

  • Page 51

    Chapter 3: installation and configuration 32 installing cable retention clips on outlets (optional) if your px device is designed to use a cable retention clip, install the clip before connecting a power cord. A cable retention clip prevents the connected power cord from coming loose or falling off....

  • Page 52

    Chapter 3: installation and configuration 33 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 the clip i...

  • Page 53: Chapter 4

    34 more features are available if you connect raritan's or third-party external equipment to your px. In this chapter connecting environmental sensor packages .........................................34 connecting asset management sensors ................................................55 connecting...

  • Page 54

    Chapter 4: connecting external equipment (optional) 35 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 40). Warning: for proper operation...

  • Page 55

    Chapter 4: connecting external equipment (optional) 36 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 px device raritan differential air pressure sensors one dpx sensor package (optiona...

  • Page 56

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

  • Page 57

    Chapter 4: connecting external equipment (optional) 38 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 58

    Chapter 4: connecting external equipment (optional) 39 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 px..

  • Page 59

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

  • Page 60

    Chapter 4: connecting external equipment (optional) 41 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 61

    Chapter 4: connecting external equipment (optional) 42 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 62

    Chapter 4: connecting external equipment (optional) 43 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 47). Note: if your px has "two" rj-12 sensor ports, see guidelines for px with...

  • Page 63

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

  • Page 64

    Chapter 4: connecting external equipment (optional) 45 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 65

    Chapter 4: connecting external equipment (optional) 46 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 66

    Chapter 4: connecting external equipment (optional) 47 2. If you want to cascade dx packages, get an additional standard network patch cable (cat5e or higher) and then: 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...

  • Page 67

    Chapter 4: connecting external equipment (optional) 48 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 68

    Chapter 4: connecting external equipment (optional) 49 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 69

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

  • Page 70

    Chapter 4: connecting external equipment (optional) 51 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, dp...

  • Page 71

    Chapter 4: connecting external equipment (optional) 52.

  • Page 72

    Chapter 4: connecting external equipment (optional) 53 mix dpx3 and dx in a sensor chain: any dx sensor package in a chain can be replaced by a dpx3 sensor package. For example, the following diagram shows a sensor chain comprising both dx and dpx3 sensor packages. The total number of sensor package...

  • Page 73

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

  • Page 74

    Chapter 4: connecting external equipment (optional) 55 a dpx3 or dx sensor chain sensor-mixing connections: the px with "two" sensor ports supports the sensor-mixing combinations listed in the section titled mixing diverse sensor types (on page 50). You can connect the sensor-mixing combination to e...

  • Page 75

    Chapter 4: connecting external equipment (optional) 56 combining regular asset sensors each tag port on the regular asset sensor 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 sensors up to 64u long, consisting of ...

  • Page 76

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

  • Page 77

    Chapter 4: connecting external equipment (optional) 58 introduction to asset tags you need both asset sensors 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 sensor at the oth...

  • Page 78

    Chapter 4: connecting external equipment (optional) 59 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 device occupies the 5th and 6th rack units, plug the asset tag into the tag port matches the 5t...

  • Page 79

    Chapter 4: connecting external equipment (optional) 60 (c) it devices (d) raritan x cable note: 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 66). Connecting blade extension strips for ...

  • Page 80

    Chapter 4: connecting external equipment (optional) 61 note: a tag connector cable has a unique barcode, which is displayed in the px device's web interface for identifying each blade extension strip where it is connected. Blade extension strip with 16 tag ports mylar section with the adhesive tape ...

  • Page 81

    Chapter 4: connecting external equipment (optional) 62 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 82

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

  • Page 83

    Chapter 4: connecting external equipment (optional) 64 two rj-45 connectors tag ports to connect composite asset sensors to the px device: 1. Connect a composite asset sensor to the px device via a standard network patch cable (cat5e or higher). A. Connect one end of the cable to the rj-45 port labe...

  • Page 84

    Chapter 4: connecting external equipment (optional) 65 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 sensors in the chain. Important: do not mix ams-m2-z and ams-m3-z in a chain. ...

  • Page 85

    Chapter 4: connecting external equipment (optional) 66 tip: to increase the maximum number of composite asset sensors attached to a raritan px2 pdu or emx2-111, you can use raritan's x cable to enhance the power supply to the asset sensor chain. See using an x cable (on page 66). Important: do not m...

  • Page 86

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

  • Page 87

    Chapter 4: connecting external equipment (optional) 68 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 88

    Chapter 4: connecting external equipment (optional) 69 connecting a logitech webcam connect webcams to px in order to view videos or snapshots of the webcam's surrounding area. The following uvc-compliant webcams are supported: logitech ® webcam ® pro 9000, model 960-000048 logitech quickcam deluxe ...

  • Page 89

    Chapter 4: connecting external equipment (optional) 70 connecting a gsm modem a cinterion ® mc52it or mc55it gsm modem can be connected to the px in order to send sms messages containing event information. See creating actions (on page 214) for more information on sms messages. Note: px cannot recei...

  • Page 90

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

  • Page 91

    Chapter 4: connecting external equipment (optional) 72 see managing the schroff lhx/shx heat exchanger (on page 309) for enabling the support of the lhx/shx heat exchanger..

  • Page 92: Chapter 5

    73 this chapter explains how to use the px device. It describes the leds and ports on the pdu, and explains how to use the front panel display. It also explains how the overcurrent protector works and when the beeper sounds. In this chapter panel components .............................................

  • Page 93

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

  • Page 94

    Chapter 5: using the pdu 75 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, many px2 series 1u...

  • Page 95

    Chapter 5: using the pdu 76 port used for... Console/ modem establishing a serial connection between the px 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 px to the computer. Sensor (rj-12) connection to...

  • Page 96

    Chapter 5: using the pdu 77 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 models:.

  • Page 97

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

  • Page 98

    Chapter 5: using the pdu 79 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) for voltage kilowat...

  • Page 99

    Chapter 5: using the pdu 80 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 number. For example, i...

  • Page 100

    Chapter 5: using the pdu 81 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 is indicated as ...

  • Page 101

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

  • Page 102

    Chapter 5: using the pdu 83 resetting the button-type circuit breaker your button-type circuit breakers may look slightly different from the images shown in this section, but the reset procedure remains the same. To reset the button-type breakers: 1. Locate the breaker whose on button is up, indicat...

  • Page 103

    Chapter 5: using the pdu 84 3. Examine your px 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 triangle turns red...

  • Page 104

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

  • Page 105

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

  • Page 106

    Chapter 5: using the pdu 87 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 carrier using a flat...

  • Page 107

    Chapter 5: using the pdu 88 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 px includes an internal beeper to issue an audible alarm for an overcurrent protector which is open. The beeper sound...

  • Page 108: Chapter 6

    89 this chapter explains how to use the web interface to administer a px. In this chapter supported web browsers........................................................................89 logging in to the web interface ..............................................................90 logout.............

  • Page 109

    Chapter 6: using the web interface 90 logging in to the web interface to log in to the web interface, you must enter a user name and password. The first time you log in to the px, use the default user name (admin) and password (raritan). For details, see the quick setup guide accompanying the produc...

  • Page 110

    Chapter 6: using the web interface 91 3. Type your user name in the user name field, and password in the password field. Both the user name and password are case sensitive. Note: if needed, click clear to clear either the inputs or any error message that appears. 4. If a security agreement is displa...

  • Page 111

    Chapter 6: using the web interface 92 note: the ip address to access a slave device in the usb-cascading configuration where the port forwarding mode is applied is a combination of the ip address and the port number. See port forwarding examples (on page 140). Password change request for first login...

  • Page 112

    Chapter 6: using the web interface 93 changing your password you must have the change own password permission to change your own password. See setting up roles (on page 156). You must have administrator privileges to change other users' passwords. See modifying a user profile (on page 154). To chang...

  • Page 113

    Chapter 6: using the web interface 94 close the web browser by clicking the close button ( ) on the top-right corner of the browser. Close the web browser by choosing file > close, or file > exit. The command varies according to the version of the browser you use. Choose the refresh command or click...

  • Page 114

    Chapter 6: using the web interface 95 number web interface element add page icon logout button data pane * the setup button is not available on some pages, such as the dashboard page. For detailed information about these web interface elements, see the sections that follow. Menus user management con...

  • Page 115

    Chapter 6: using the web interface 96 first level second level third level feature port folder one of the following is displayed, depending on your configuration: none asset strip power cim external beeper lhx-20 shx-30 lhx-40 webcam management snapshots webcam * the folder is named "my px" by defau...

  • Page 116

    Chapter 6: using the web interface 97 if it is not expanded, click the white arrow prior to the folder icon, or double-click the folder. The arrow then turns into a black, gradient arrow , and icons of components or component groups appear below the pdu folder. 2. To expand any component group at th...

  • Page 117

    Chapter 6: using the web interface 98 collapsing the tree you can collapse the whole tree structure or a specific component group to hide all or partial tree items. To collapse the whole tree: click the black, gradient arrow prior to the root folder icon, or double-click the root folder. Note: this ...

  • Page 118

    Chapter 6: using the web interface 99 tip: the presence of the device name and ip address in the status bar indicates the connection to the px device. If the connection is lost, it shows " " instead. 3. Login name: this is the user name you used to log in to the web interface. 4. Last login time: th...

  • Page 119

    Chapter 6: using the web interface 100 the following diagram shows a multi-tab example. 4. With multiple pages opened, you can take these actions: to switch to one of the opened data pages, click the corresponding tab. If there are too many tabs to be all shown, two arrows ( and ) appear at the left...

  • Page 120

    Chapter 6: using the web interface 101 the yellow- or red-highlighted sensors when a numeric sensor's reading enters the warning or critical range, the background color of the sensor row turns to yellow or red for alerting you. For a discrete (on/off) sensor, the row changes the background color whe...

  • Page 121

    Chapter 6: using the web interface 102 to find the exact meaning of the alert, read the information shown in the state (or status) column: below lower critical: the numeric sensor's reading drops below the lower critical threshold. Below lower warning: the numeric sensor's reading drops below the lo...

  • Page 122

    Chapter 6: using the web interface 103 browser-defined shortcut menu a shortcut menu, which is built in the web browser, may appear when right-clicking anywhere in the px web interface. The shortcut menu functions are defined by the browser. For example, the back command on the internet explorer ® (...

  • Page 123

    Chapter 6: using the web interface 104 viewing the dashboard when you log in to the web interface, the dashboard page is displayed by default. This page provides an overview of the px device's status. The page is divided into various sections according to the component type, such as inlet and overcu...

  • Page 124

    Chapter 6: using the web interface 105 any tripped circuit breakers or blown fuses for the background color meanings in this section, see the yellow- or red-highlighted sensors (on page 101). Alarms list you can create event rules that request users to acknowledge certain alerts, and resend alert no...

  • Page 125

    Chapter 6: using the web interface 106 column description details click "details" to trigger a dialog showing both the alarm details and the acknowledgment button. Only users who have the acknowledge alarms permission can manually acknowledge an alarm. To acknowledge an alarm: 1. Double-click the al...

  • Page 126

    Chapter 6: using the web interface 107 displaying pdu information to display information specific to the px device that you are using, such as inlet or outlet types, trigger the device information dialog. To display the pdu-specific information: 1. Choose maintenance > device information. 2. Click a...

  • Page 127

    Chapter 6: using the web interface 108 tab data controllers each outlet controller's serial number, board id, firmware version and hardware version. Inlets each inlet's plug type, rated voltage and current. Overcurrent protectors each overcurrent protector's type, rated current and the outlets that ...

  • Page 128

    Chapter 6: using the web interface 109 fields description networking mode indicates how the px is connected to the lan. Wired: the device is connected to the lan through a standard network cable. Wireless: the device is connected to the lan through a supported usb wireless lan adapter. See usb wirel...

  • Page 129

    Chapter 6: using the web interface 110 a master device shows 0 (zero) in the cascade position field and yes in the cascaded device connected field. A slave device in the middle position shows a non-zero number which indicates its exact position in the cascade position field and yes in the cascaded d...

  • Page 130

    Chapter 6: using the web interface 111 the following diagram shows 1, indicating it is the first slave - slave 1. 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..

  • Page 131

    Chapter 6: using the web interface 112 the following diagram shows 2, indicating it is the second slave - slave 2. The cascaded device connected field shows no, indicating that it is the final one in the chain. Naming the pdu the default name for px root folder is my px. You may give it a unique dev...

  • Page 132

    Chapter 6: using the web interface 113 modifying network interface settings the px supports two types of network interfaces: wired and wireless. You should configure the network interface settings according to the networking mode that applies. See connecting the px to your network (on page 20). Wire...

  • Page 133

    Chapter 6: using the web interface 114 wireless network settings wireless ssid, psk and bssid parameters were set during the installation and configuration process. You can change them later. Note for usb-cascading configuration: port forwarding mode over wireless lan is supported as of release 3.1....

  • Page 134

    Chapter 6: using the web interface 115 options description eap - peap peap stands for protected extensible authentication protocol. Enter the following authentication data: inner authentication: only microsoft's challenge authentication protocol version 2 (mschapv2) is supported, allowing authentica...

  • Page 135

    Chapter 6: using the web interface 116 modifying network settings the px was configured for network connectivity during the installation and configuration process. See configuring the px (on page 17). If necessary, you can modify any network settings later. Selecting the internet protocol the px dev...

  • Page 136

    Chapter 6: using the web interface 117 modifying ipv4 settings you must enable the ipv4 protocol before you can modify the ipv4 network settings. See selecting the internet protocol (on page 116). To modify ipv4 settings: 1. Choose device settings > network. The network configuration dialog appears....

  • Page 137

    Chapter 6: using the web interface 118 option description mask using the format "ip address/subnet mask." next hop: ip address of the next hop router. See static route examples (on page 120) for illustrations. 4. Click ok. Note: the px supports a maximum of 3 dns servers. If two ipv4 dns servers and...

  • Page 138

    Chapter 6: using the web interface 119 option description ip address default gateway primary dns server secondary dns server (optional) dns suffix (optional) if your local network contains two subnets and ip forwarding has been enabled, you can click append to add static routes so that your px can c...

  • Page 139

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

  • Page 140

    Chapter 6: using the web interface 121 in this example, nic-2 (192.168.100.88) is the next hop router for your px to communicate with any device in the other subnet 192.168.200.0. In the ipv4 "append new route" dialog, you should specify: destination: 192.168.200.0/24 next hop: 192.168.100.88 ipv6 e...

  • Page 141

    Chapter 6: using the web interface 122 in this example, nic-2 (fd07:2fa:6cff:2405::80) is the next hop router for your px to communicate with any device in the other subnet fd07:2fa:6cff:1111::0. In the ipv6 'append new route' dialog, you should specify: destination: fd07:2fa:6cff:2405::0/64 next ho...

  • Page 142

    Chapter 6: using the web interface 123 https uses transport layer security (tls) technology to encrypt all traffic to and from the px device so it is a more secure protocol than http. By default, any access to the px device via http is automatically redirected to https. You can disable this redirect...

  • Page 143

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

  • Page 144

    Chapter 6: using the web interface 125 to configure snmp notification destinations: 1. Click the notifications tab in the same snmp dialog. 2. Select the enabled checkbox. 3. Select an snmp notification type - snmp v2c trap, snmp v2c inform, snmp v3 trap, and snmp v3 inform. 4. Specify the snmp noti...

  • Page 145

    Chapter 6: using the web interface 126 changing telnet settings you can enable or disable the telnet access to the command line interface, or change the default tcp port for the telnet service. To change telnet service settings: 1. Choose device settings > network services > telnet. The telnet setti...

  • Page 146

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

  • Page 147

    Chapter 6: using the web interface 128 2. Click yes on the confirmation message to switch off the zero configuration advertising. The feature is disabled and the service advertisement checkbox is deselected in the submenu. Setting the date and time set the internal clock on the px device manually, o...

  • Page 148

    Chapter 6: using the web interface 129 the px follows the ntp server sanity check per the ietf rfc. If your px has problems synchronizing with a windows ntp server, see windows ntp server synchronization solution (on page 131). Note: if you are using sunbird's power iq to manage the px, you must con...

  • Page 149

    Chapter 6: using the web interface 130 click , which is adjacent to the year, to show a list of years and months. Select the desired year from the list to the right and click ok. If the list does not show the desired year, click or to show additional years. 2. To change the month shown in the calend...

  • Page 150

    Chapter 6: using the web interface 131 windows ntp server synchronization solution the ntp client on the px follows the ntp rfc so the px rejects any ntp servers whose root dispersion is more than one second. An ntp server with a dispersion of more than one second is considered an inaccurate ntp ser...

  • Page 151

    Chapter 6: using the web interface 132 setting default measurement units default measurement units are applied to the px web and cli interfaces across all users, including users accessing the device via external authentication servers. Default units apply before users set their own preferred measure...

  • Page 152

    Chapter 6: using the web interface 133 configuring the feature port the px device supports connecting one of the following devices to its feature port: raritan computer interface module (cim) for kvm access. See dominion kx ii / iii configuration (on page 605). Raritan serial access products, includ...

  • Page 153

    Chapter 6: using the web interface 134 device type description lhx 20 schroff ® lhx-20 heat exchanger. All schroff ® shx/lhx device types are available only after the lhx/shx support is enabled. See enabling and disabling schroff lhx/shx heat exchanger support (on page 310). Shx 30 schroff ® shx-30 ...

  • Page 154

    Chapter 6: using the web interface 135 2. In the "connected device" field, select an appropriate option to force the serial port to enter the correct state. Options description automatic detection the px automatically detects the device type on the serial port. Select this option unless your px cann...

  • Page 155

    Chapter 6: using the web interface 136 setting the cascading mode a maximum of eight px devices can be cascaded using usb cables and therefore share only one ethernet connection. See cascading the px via usb (on page 29). The ethernet sharing mode applied to the usb-cascading configuration is either...

  • Page 156

    Chapter 6: using the web interface 137 return to the same dialog and click the "protocol to port mapping" tab to view the master device's port numbers. For information on accessing each cascaded device in the port forwarding mode, see port forwarding examples (on page 140). Overview of the cascading...

  • Page 157

    Chapter 6: using the web interface 138 "bridging" mode: as illustrated in the following diagram, the dhcp server communicates with every cascaded device respectively and assigns four different ip addresses accordingly. Each device has one ip address. The way to remotely access each cascaded device i...

  • Page 158

    Chapter 6: using the web interface 139 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 stan...

  • Page 159

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

  • Page 160

    Chapter 6: using the web interface 141 protocols port numbers 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: http://192.168.84...

  • Page 161

    Chapter 6: using the web interface 142 to access slave 1 via http, the ip address is: http://192.168.84.77:50101/ to access slave 1 via ssh, the command is: ssh -p 50201 192.168.84.77 slave 2 device: position code for slave 2 is 02 so each port number is 5nn02 as shown below. Protocols port numbers ...

  • Page 162

    Chapter 6: using the web interface 143 setting data logging the px 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 da...

  • Page 163

    Chapter 6: using the web interface 144 configuring smtp settings the px can be configured to send alerts or event messages to a specific administrator by email. To do this, you have to configure the smtp settings and enter an ip address for your smtp server and a sender's email address. If any email...

  • Page 164

    Chapter 6: using the web interface 145 to always send the email messages even though the installed certificate chain contains a certificate that is outdated or not valid yet, select this checkbox. To prevent the email messages from being sent when any certificate in the installed certificate chain i...

  • Page 165

    Chapter 6: using the web interface 146 5. In the "entry type" field, determine the data that will be transmitted. Asset management information: transmit the information of the specified asset sensor(s), including the general status of the specified sensor(s) and a list of asset tags on blade extensi...

  • Page 166

    Chapter 6: using the web interface 147 rebooting the px device you can remotely reboot the px device via the web interface. Resetting the px does not interrupt the operation of connected servers because there is no loss of power to outlets. Outlets that have been powered on prior to the reset remain...

  • Page 167

    Chapter 6: using the web interface 148 tip: you can also reset the active energy readings of an individual inlet. See resetting inlet active energy readings (on page 206). Monitoring total active energy or power this section applies only to multi-inlet models, including px in-line monitors. A px dev...

  • Page 168

    Chapter 6: using the web interface 149 checking the internal beeper state the internal beeper can alert you if any overcurrent protector, including fuses and circuit breakers, has tripped or blown on the px. See beeper (on page 88). If intended, you can set an event rule to turn on the internal beep...

  • Page 169

    Chapter 6: using the web interface 150 3. In the "domain name" field, type the name of a cisco energywise domain where the px belongs. The domain name comprises up to 127 printable ascii characters. Spaces and asterisks are not acceptable. 4. In the "domain password" field, type the authentication p...

  • Page 170

    Chapter 6: using the web interface 151 field type this... User name the name the user enters to log in to the px. 4 to 32 characters case sensitive spaces are not permitted. Full name the user's first and last names. Password, confirm password 4 to 64 characters case sensitive spaces are permitted. ...

  • Page 171

    Chapter 6: using the web interface 152 field description privacy. Authpriv: authentication and privacy. This is the default. Use password as authentication pass phrase this checkbox is configurable only if authnopriv or authpriv is selected. When the checkbox is selected, the authentication pass phr...

  • Page 172

    Chapter 6: using the web interface 153 field description privacy protocol click the drop-down arrow and select the desired privacy protocol from the list. Two protocols are available: des (default) aes-128 7. Click the ssh tab to enter the public key if the public key authentication for the ssh serv...

  • Page 173

    Chapter 6: using the web interface 154 note: the measurement unit change only applies to the web interface and command line interface. Users can change the measurement units at any time by setting up their own user preferences. See setting up your preferred measurement units (on page 155). Modifying...

  • Page 174

    Chapter 6: using the web interface 155 2. Select the user you want to delete by clicking it. To make multiple selections, press ctrl+click or shift+click to highlight multiple ones. 3. Click delete. 4. A message appears, prompting you to confirm the operation. Click yes to confirm the deletion. Sett...

  • Page 175

    Chapter 6: using the web interface 156 setting up roles a role defines the operations and functions a user is permitted to perform or access. Every user must be assigned at least a role. The px is shipped with two built-in roles: admin and operator. The admin role provides full permissions. You can ...

  • Page 176

    Chapter 6: using the web interface 157 c. If the permission you selected contains any argument setting, the arguments list is shown to the right, such as the switch actuator permission. Then select one or multiple arguments. For example, if the switch outlet permission is selected, the arguments lis...

  • Page 177

    Chapter 6: using the web interface 158 b. Select the permission you want from the privileges list. C. If the permission you selected contains any argument setting, the arguments list is shown to the right, such as the switch actuator permission. Then select one or multiple arguments. For example, if...

  • Page 178

    Chapter 6: using the web interface 159 access security control the px provides tools to control access. You can enable the internal firewall, create firewall rules, and create login limitations. Tip: you can also create and install the certificate or set up external authentication servers to control...

  • Page 179

    Chapter 6: using the web interface 160 2. To enable the ipv4 firewall, click the ipv4 tab, and select the enable ipv4 access control checkbox. 3. To enable the ipv6 firewall, click the ipv6 tab, and select the enable ipv6 access control checkbox. 4. Click ok. Changing the default policy after enabli...

  • Page 180

    Chapter 6: using the web interface 161 accept: accepts traffic from all ipv6 addresses. Drop: discards traffic from all ipv6 addresses, without sending any failure notification to the source host. Reject: discards traffic from all ipv6 addresses, and an icmp message is sent to the source host for fa...

  • Page 181

    Chapter 6: using the web interface 162 to create firewall rules: 1. Choose device settings > security > ip access control. The configure ip access control settings dialog appears. 2. Click the ipv4 tab for creating ipv4 firewall rules, or click the ipv6 tab for creating ipv6 firewall rules. 3. Ensur...

  • Page 182

    Chapter 6: using the web interface 163 action procedure insert a rule between two existing 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. The "insert new rule" dialog appears. Type an ip address and sub...

  • Page 183

    Chapter 6: using the web interface 164 6. When finished, the rules appear in the configure ip access control settings dialog. 7. Click ok. The rules are applied. Editing firewall rules when an existing firewall rule requires updates of ip address range and/or policy, modify them accordingly. To modi...

  • Page 184

    Chapter 6: using the web interface 165 2. To modify the ipv4 firewall rules, click the ipv4 tab. To modify the ipv6 firewall rules, click the ipv6 tab. 3. Ensure the enable ipv4 access control checkbox is selected on the ipv4 tab, or the enable ipv6 access control checkbox is selected on the ipv6 ta...

  • Page 185

    Chapter 6: using the web interface 166 3. Ensure the enable ipv4 access control checkbox is selected on the ipv4 tab, or the enable ipv6 access control checkbox is selected on the ipv6 tab. 4. Select the rule that you want to delete. To make multiple selections, press ctrl+click or shift+click to hi...

  • Page 186

    Chapter 6: using the web interface 167 x min: this type of option sets the time limit to x minutes, where x is a number. X h: this type of option sets the time limit to x hours, where x is a number. 1 d: this option sets the time limit to 1 day. Tip: if the desired time option is not listed, you can...

  • Page 187

    Chapter 6: using the web interface 168 enabling strong passwords use of strong passwords makes it more difficult for intruders to crack user passwords and access the px device. By default, strong passwords should be at least eight characters long and contain upper- and lower-case letters, numbers, a...

  • Page 188

    Chapter 6: using the web interface 169 tip: if the desired time option is not listed, you can manually type the desired time in this field. For example, you can type "9 d" to set the password aging time to 9 days. 4. Click ok. Enabling and editing the security banner use the px restricted service ag...

  • Page 189

    Chapter 6: using the web interface 170 if the restricted service agreement feature is enabled, the restricted service agreement is displayed when any user logs in to the px. Do either of the following, or you cannot successfully log in to the px: in the web interface, select the checkbox labeled "i ...

  • Page 190

    Chapter 6: using the web interface 171 changing the default policy the default policy is to accept all traffic from all ip addresses regardless of the role applied to the user. To change the default policy: 1. Choose device settings > security > role based access control. The configure role based ac...

  • Page 191

    Chapter 6: using the web interface 172 3. Ensure the "enable role based access control for ipv4" checkbox is selected on the ipv4 tab, or the "enable role based access control for ipv6" checkbox is selected on the ipv6 tab. 4. Create specific rules: action do this... Add a rule to the end of the rul...

  • Page 192

    Chapter 6: using the web interface 173 action do this... Role click ok. The system inserts the rule and automatically renumbers the following rules. 5. Click ok. Editing role-based access control rules you can modify existing rules when these rules do not meet your needs. To modify a role-based acce...

  • Page 193

    Chapter 6: using the web interface 174 6. Click ok. Deleting role-based access control rules when any access control rule becomes unnecessary or obsolete, remove it. To delete a role-based access control rule: 1. Choose device settings > security > role based access control. The configure role based...

  • Page 194

    Chapter 6: using the web interface 175 having an x.509 digital certificate ensures that both parties in an tls connection are who they say they are. To obtain a certificate for the px, create a certificate signing request (csr) and submit it to a certificate authority (ca). After the ca processes th...

  • Page 195

    Chapter 6: using the web interface 176 field type this information common name the fully qualified domain name (fqdn) of your px device. Email address an email address where you or another administrative user can be reached. Note: all fields in the subject section are mandatory, except for the organ...

  • Page 196

    Chapter 6: using the web interface 177 installing a ca-signed certificate after the ca provides a signed certificate according to the csr you submitted, you must install it on the px device. To install the certificate: 1. Choose device settings > security > ssl certificate. The manage ssl certificat...

  • Page 197

    Chapter 6: using the web interface 178 field type this information key length select the key length (bits) from the drop-down list in this field. A larger key length enhances the security, but slows down the px device's response. Self sign ensure this checkbox is selected, which indicates that you a...

  • Page 198

    Chapter 6: using the web interface 179 installing existing key and certificate files if the tls certificate and private key files are already available, you can install them directly without going through the process of creating a csr or a self-signed certificate. Note: if you are using a tls certif...

  • Page 199

    Chapter 6: using the web interface 180 setting up external authentication for security purposes, users attempting to log in to the px must be authenticated. The px supports the access using one of the following authentication mechanisms: local database of user profiles on the px device lightweight d...

  • Page 200

    Chapter 6: using the web interface 181 gathering the ldap information it requires knowledge of your ldap server and directory settings to configure the px for ldap authentication. If you are not familiar with the settings, consult your ldap administrator for help. To configure ldap authentication, y...

  • Page 201

    Chapter 6: using the web interface 182 adding authentication servers add all external aa servers that you want to use to the px. Later you can use the sequence of the server list to control the aa servers' access priority. Adding ldap server settings to activate and use external ldap/ldaps server au...

  • Page 202

    Chapter 6: using the web interface 183 none 7. Port (none/starttls) - the default port is 389. Either use the standard ldap tcp port or specify another port. 8. Port (tls) - the default is 636. Either use the default port or specify another port. This field is enabled only when "tls" is selected in ...

  • Page 203

    Chapter 6: using the web interface 184 16. Base dn for search - enter the name you want to bind against the ldap/ldaps (up to 31 characters), and where in the database to begin searching for the specified base dn. An example base search value might be: cn=users,dc=raritan,dc=com. Consult your aa ser...

  • Page 204

    Chapter 6: using the web interface 185 note: if the px clock and the ldap server clock are out of sync, the installed tls certificates, if any, may be considered expired. To ensure proper synchronization, administrators should configure the px and the ldap server to use the same ntp server(s). Addin...

  • Page 205

    Chapter 6: using the web interface 186 11. Click ok. The new radius server is listed in the authentication settings dialog. 12. To add additional radius servers, repeat steps 3 to 11. 13. Click ok. Radius authentication is now in place. More information about ad or radius configuration for more info...

  • Page 206

    Chapter 6: using the web interface 187 editing authentication server settings if the configuration of any external authentication server has been changed, such as the port number, you must modify the authentication settings on the px device accordingly, or the authentication fails. To modify the ext...

  • Page 207

    Chapter 6: using the web interface 188 enabling external and local authentication services to make authentication function properly all the time - even when external authentication is not available, you can enable both the local and remote authentication services. When both authentication services a...

  • Page 208

    Chapter 6: using the web interface 189 3. Click setup in the right pane. The setup dialog for the selected outlet appears. 4. Type a name in the outlet name field. 5. Click ok. Checking outlet-specific data to find out each outlet's name, label, and receptacle type, you can check the outlets page or...

  • Page 209

    Chapter 6: using the web interface 190 switching multiple or all outlets this section applies to outlet-switching capable models only. The power state can be changed regardless of each outlet's current state. That is, you can turn on or off or power cycle the outlets even if they are already in the ...

  • Page 210

    Chapter 6: using the web interface 191 5. A dialog for confirming the operation appears. Click yes and all outlets switch on, off, or cycle their power. Switching an outlet this section applies to outlet-switching capable models only. You can turn on or off or power cycle any outlet regardless of th...

  • Page 211

    Chapter 6: using the web interface 192 stopping the power-on sequence this section applies to outlet-switching capable models only. The px allows you to stop the outlet power-on sequence while all outlets are being turned on. This function is useful when you have set a certain power-on sequence and ...

  • Page 212

    Chapter 6: using the web interface 193 setting the pdu-defined default state this section applies to outlet-switching capable models only. This procedure sets the pdu-defined outlet state, which determines the initial power state of all outlets after powering up the px device. Tip: to set a differen...

  • Page 213

    Chapter 6: using the web interface 194 4. In the "state on device startup" field, click the drop-down arrow and select an option from the list. On: turns on this outlet when the px powers up. Off: turns off this outlet when the px powers up. Last known: restores this outlet to the previous power sta...

  • Page 214

    Chapter 6: using the web interface 195 3. In the "power off period during power cycle" field, click the drop-down arrow and select an option from the list. Valid range is zero second to one hour. Time units in the list are explained below: s: second(s) min: minute(s) h: hour(s) you can also type a v...

  • Page 215

    Chapter 6: using the web interface 196 min: minute(s) h: hour(s) to make the outlet's power-off period identical to the pdu-defined setting, select the "pdu defined" option. See changing the pdu-defined cycling power-off period (on page 194). Tip: the information in parentheses following the option ...

  • Page 216

    Chapter 6: using the web interface 197 tip: when there are a large number of outlets, set the value to a lower number so that you can avoid a long wait before all the outlets are available again. Setting the inrush guard delay this section applies to outlet-switching capable models only. When electr...

  • Page 217

    Chapter 6: using the web interface 198 setting the outlet power-on sequence this section applies to outlet-switching capable models only. By default, the outlets are sequentially powered on in ascending order from outlet 1 to the highest-numbered outlet when turning on or power cycling all outlets o...

  • Page 218

    Chapter 6: using the web interface 199 setting the outlet-specific power-on delay this section applies to outlet-switching capable models only. You can make a power-on delay occur between two outlets that are turned on consecutively when the px turns on all outlets. For example, if the power-up sequ...

  • Page 219

    Chapter 6: using the web interface 200 marking all outlets this section applies to outlet-switching capable models only. You can configure all critical and non-critical outlets at a time. To mark all outlets at a time: 1. Click the pdu folder. Note: the folder is named "my px" by default. The name c...

  • Page 220

    Chapter 6: using the web interface 201 2. In the px explorer pane, click the outlet you want. The page specific to that outlet opens in the right pane. 3. Click setup in the right pane. The setup dialog for the selected outlet appears. Tip: another way to trigger the same dialog is to use the outlet...

  • Page 221

    Chapter 6: using the web interface 202 2. Click the outlets folder, and the outlets page opens in the right pane. 3. To enter the load shedding mode, click start near the load shedding section at the lower left corner of the page. To exit from the load shedding mode, click stop. 4. You are then prom...

  • Page 222

    Chapter 6: using the web interface 203 naming the inlet you can customize the inlet's name for your own purpose. For example, you can name an inlet to identify its power source. The customized name is followed by the label in parentheses. Note: in this context, the label refers to the inlet number, ...

  • Page 223

    Chapter 6: using the web interface 204 inlet sensor readings: - rms current per line (a) - rms voltage per line pair (v) - active power (w) - apparent power (va) - power factor - active energy (wh) - unbalanced load percentage (for 3-phase models) - line frequency (hz), if available on your pdu note...

  • Page 224

    Chapter 6: using the web interface 205 lines associated with this overcurrent protector outlets protected by this overcurrent protector sensor readings: - current drawn (a) - current remaining (a) note: if a sensor row is colored, it means the sensor reading already crosses one of the thresholds, th...

  • Page 225

    Chapter 6: using the web interface 206 resetting inlet active energy readings you can manually reset the active energy readings of an individual inlet instead of resetting all active energy readings of the pdu. This is especially useful when your px has more than one inlet. Only users with the "admi...

  • Page 226

    Chapter 6: using the web interface 207 disabling an inlet (for multi-inlet pdus) the px, if it has more than one inlet, enables all inlets by default so that the px detects and displays all sensors' readings and states, and reports or shows warnings, events or alarm notifications associated with all...

  • Page 227

    Chapter 6: using the web interface 208 setting power thresholds setting and enabling the thresholds causes the px to generate alert notifications when it detects that any component's power state crosses the thresholds. See the yellow- or red-highlighted sensors (on page 101). There are four threshol...

  • Page 228

    Chapter 6: using the web interface 209 7. To set the assertion timeout, type a numeric value in the assertion timeout (samples) field. See "to assert" and assertion timeout (on page 595). 8. Click ok in the threshold setup dialog to retain the changes. 9. To set the thresholds for other sensors, rep...

  • Page 229

    Chapter 6: using the web interface 210 bulk configuration for overcurrent protector thresholds the px allows you to set power thresholds for multiple overcurrent protectors at a time to save your time. Note: to set the power thresholds for an individual overcurrent protector, you can either follow t...

  • Page 230

    Chapter 6: using the web interface 211 setting thresholds for total active energy or power this section applies only to multi-inlet models, including px 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 al...

  • Page 231

    Chapter 6: using the web interface 212 8. Click ok..

  • Page 232

    Chapter 6: using the web interface 213 event rules and actions a benefit of the product's intelligence is its ability to notify you of and react to a change in conditions. This event notification or reaction is an "event rule." the px is shipped with four built-in event rules, which cannot be delete...

  • Page 233

    Chapter 6: using the web interface 214 creating actions the px comes with three built-in actions: system event log action: this action records the selected event in the internal log when the event occurs. System snmp notification action: this action sends snmp notifications to one or multiple ip add...

  • Page 234

    Chapter 6: using the web interface 215 action function log event message records the selected events in the internal log. See log an event message (on page 219). Push out sensor readings sends asset management sensor data to a remote server using http post requests. See push out sensor readings (on ...

  • Page 235

    Chapter 6: using the web interface 216 action function switch outlets switches on, off or cycles the power to the specified outlet(s). See switch outlets (on page 232). Switch peripheral actuator switches on or off the mechanism or system connected to the specified actuator. See switch peripheral ac...

  • Page 236

    Chapter 6: using the web interface 217 7. To remove an action from the action group, select it from the used actions list box, and click to move it to the available actions list box. To make multiple selections, press ctrl+click or shift+click to highlight multiple ones. To remove all actions, click...

  • Page 237

    Chapter 6: using the web interface 218 b. Click to add the selected method to the alarm notifications list box. C. Repeat the above steps to add more methods if needed. To remove any method from the alarm notifications list box, select that method and click . 6. In the notification options section, ...

  • Page 238

    Chapter 6: using the web interface 219 3. In the "action name" field, type a new name for the action. The default name is new action , where is a sequential number starting at 1. 4. In the action field, click the drop-down arrow and select the desired action: external beeper. 5. From the beeper port...

  • Page 239

    Chapter 6: using the web interface 220 push out sensor readings if you have connected raritan's asset sensors to the px, you can configure the px to push asset sensor data to a remote server after a certain event occurs. Before creating this action, make sure that you have properly defined the desti...

  • Page 240

    Chapter 6: using the web interface 221 request lhx/shx maximum cooling if schroff lhx/shx support is enabled, the lhx/shx-related actions will be available. See enabling and disabling schroff lhx/shx heat exchanger support (on page 310). The "request lhx/shx maximum cooling" action applies the maxim...

  • Page 241

    Chapter 6: using the web interface 222 to use a different smtp server, select the use custom smtp settings checkbox. If the smtp server settings are not configured yet, click configure. See configuring smtp settings (on page 144) for the information of each field. 8. Select the webcam that is captur...

  • Page 242

    Chapter 6: using the web interface 223 4. In the "action name" field, type a new name for the action. The default name is new action , where is a sequential number starting at 1. 5. In the action field, click the drop-down arrow and select the desired action: send email. 6. In the "recipients email ...

  • Page 243

    Chapter 6: using the web interface 224 5. In the action field, click the drop-down arrow and select the desired action: send snmp notification. 6. Select the type of snmp notification. See either procedure below according to your selection. To send snmp v2c notifications: 1. From the notification ty...

  • Page 244

    Chapter 6: using the web interface 225 b. In the number of retries field, enter the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails. 4. For both snmp traps and informs, enter the...

  • Page 245

    Chapter 6: using the web interface 226 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 px may or may not detect the syslog message transmis...

  • Page 246

    Chapter 6: using the web interface 227 transport protocol types next steps if a tls certificate is required, select the "enable secure syslog over tls" checkbox, and then do the following: a. Specify an appropriate port number in the "tcp port (tls)" field. Default is 6514. B. In the ca certificate ...

  • Page 247

    Chapter 6: using the web interface 228 4. In the "action name" field, type a new name for the action. The default name is new action , where is a sequential number starting at 1. 5. In the action field, click the drop-down arrow and select the desired action: send sensor report. 6. In the destinatio...

  • Page 248

    Chapter 6: using the web interface 229 10. To save this action, click ok. Note: when intending to send a sensor report using custom messages, use the placeholder [sensorreport] to report sensor readings. See email and sms message placeholders (on page 254). Change load shedding state the "change loa...

  • Page 249

    Chapter 6: using the web interface 230 send sms message 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 px placeholders. The placeholders represent information which is pulled from the px and inserted into the...

  • Page 250

    Chapter 6: using the web interface 231 internal beeper you can have the built-in beeper of the px turned on or off when a certain event occurs. To switch the internal beeper: 1. Click the actions tab. 2. Click new. 3. In the "action name" field, type a new name for the action. The default name is ne...

  • Page 251

    Chapter 6: using the web interface 232 8. Click ok. Switch outlets the "switch outlets" action is available only when your px is outlet-switching capable. This action turns on, off or power cycles a specific outlet. To switch on, off or power cycle any outlet(s): 1. Click the actions tab. 2. Click n...

  • Page 252

    Chapter 6: using the web interface 233 switch peripheral actuator if you have any actuator connected to the px, you can set up the px so it automatically turns on or off the system controlled by this actuator when a specific event occurs. Note: for information on connecting actuators to the px, see ...

  • Page 253

    Chapter 6: using the web interface 234 3. Click new. 4. In the "action name" field, type a new name for the action. The default name is new action , where is a sequential number starting at 1. 5. In the action field, click the drop-down arrow and select the desired action: record snapshots to webcam...

  • Page 254

    Chapter 6: using the web interface 235 2. On the rules tab, click new. 3. In the "rule name" field, type a new name for identifying the rule. The default name is new rule , where is a sequential number. 4. Select the enabled checkbox to activate this event rule. 5. Click event to select an event for...

  • Page 255

    Chapter 6: using the web interface 236 event types radio buttons sensor availability available radio buttons include "unavailable," "available" and "both." unavailable: the px takes the action only when the chosen sensor is not detected and becomes unavailable. Available: the px takes the action onl...

  • Page 256

    Chapter 6: using the web interface 237 event types radio buttons restricted service agreement available radio buttons include "accepted," "declined," and "both." accepted: the px takes the action only when the specified user accepts the restricted service agreement. Declined: the px takes the action...

  • Page 257

    Chapter 6: using the web interface 238 event types radio buttons device connection or disconnection, such as a usb-cascaded slave device available radio buttons include "connected," "disconnected" and "both." connected: the px takes the action only when the selected device is physically connected to...

  • Page 258

    Chapter 6: using the web interface 239 8. To remove any action, select it from the "selected actions" list box, and click to move it back to the "available actions" list box. To make multiple selections, press ctrl+click or shift+click to highlight multiple ones. To remove all actions, click . 9. Cl...

  • Page 259

    Chapter 6: using the web interface 240 time options frequency settings minutes the frequency in minutes ranges from every minute, every 5 minutes, every 10 minutes and so on until every 30 minutes. Hourly the hourly option sets the timing to either of the following: the minute field is set to 0 (zer...

  • Page 260

    Chapter 6: using the web interface 241 to remove all actions, click . 9. Click ok. Send sensor report example below is an example of a scheduled action set to send a temperature sensor report via email hourly. In this example, a. Define a 'send email' destination action that is name send sensor temp...

  • Page 261

    Chapter 6: using the web interface 242 you must create the destination action as illustrated below prior to creating the 'send hourly temperature sensor readings' action. For details, see send email (on page 222). 2. Create the 'send sensor report' action -- send hourly temperature sensor readings ....

  • Page 262

    Chapter 6: using the web interface 243 type the action's name -- send hourly temperature sensor readings . Select the 'send sensor report' action. Select the destination action 'send sensor temp report email'. Add the desired temperature sensor(s) from the available sensors list to the report sensor...

  • Page 263

    Chapter 6: using the web interface 244 type the timer name -- hourly sensor temperature readings. Select the enabled checkbox. Select hourly, and set the minute to 30. Select the 'send hourly temperature sensor readings' action. C. Click ok. For details, see scheduling an action (on page 239). Then ...

  • Page 264

    Chapter 6: using the web interface 245 event/context default assertion message when the event = true default assertion message when the event = false* asset management > rack unit > * > tag connected asset tag with id '[tagid]' connected at rack unit [rackunit], slot [rackslot] of asset strip [strip...

  • Page 265

    Chapter 6: using the web interface 246 event/context default assertion message when the event = true default assertion message when the event = false* device > firmware validation failed firmware validation failed by user '[username]' from host '[userip]'. Device > firmware update started firmware u...

  • Page 266

    Chapter 6: using the web interface 247 event/context default assertion message when the event = true default assertion message when the event = false* device > sending snmp inform failed or no response sending snmp inform to manager [snmpmanager]:[snmpmanager port] failed or no response. [errordesc]...

  • Page 267

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

  • Page 268

    Chapter 6: using the web interface 249 event/context default assertion message when the event = true default assertion message when the event = false* > above upper critical '[inletpole]' of inlet '[inlet]' asserted 'above upper critical'. '[inletpole]' of inlet '[inlet]' deasserted 'above upper cri...

  • Page 269

    Chapter 6: using the web interface 250 event/context default assertion message when the event = true default assertion message when the event = false* lower critical '[outlet]' asserted 'below lower critical'. Outlet '[outlet]' deasserted 'below lower critical'. Outlet > * > sensor > * > reset senso...

  • Page 270

    Chapter 6: using the web interface 251 sensor > * > below lower critical overcurrent protector '[ocp]' asserted 'below lower critical'. Overcurrent protector '[ocp]' deasserted 'below lower critical'. Overcurrent protector > * > sensor > * > open/closed sensor '[ocpsensor]' on overcurrent protector ...

  • Page 271

    Chapter 6: using the web interface 252 added '[username]' from host '[userip]'. User administration > role modified role '[targetrole]' modified by user '[username]' from host '[userip]'. User administration > role deleted role '[targetrole]' deleted by user '[username]' from host '[userip]'. Webcam...

  • Page 272

    Chapter 6: using the web interface 253 lhx / shx > emergency cooling emergency cooling on lhx at [porttype] port '[portid]' was activated. Emergency cooling on lhx at [porttype] port '[portid]' was deactivated. Lhx / shx > maximum cooling request maximum cooling was requested for lhx at [porttype] p...

  • Page 273

    Chapter 6: using the web interface 254 lhx / shx > threshold humidity the humidity threshold on lhx at [porttype] port '[portid]' was crossed. The humidity on lhx at [porttype] port '[portid]' is within thresholds. Lhx / shx > external water cooling failure an external water cooling failure occurred...

  • Page 274

    Chapter 6: using the web interface 255 placeholder definition [amsrackunitposition] the (vertical) rack unit position, an action applies to [amsstate] the human readable state of an asset strip [amstagid] the asset tag id [circuitctrating] the circuit ct rating [circuitcurrentrating] the circuit cur...

  • Page 275

    Chapter 6: using the web interface 256 placeholder definition [ocp] the overcurrent protector label [oldversion] the firmware version the device is being upgraded from [outletpole] the outlet power line identifier [outletsensor] the outlet sensor name [outlet] the outlet label [pdupolesensor] the se...

  • Page 276

    Chapter 6: using the web interface 257 placeholder definition [transferswitch] the transfer switch label [umtargetrole] the name of a user management role, an action was applied on [umtargetuser] the user, an action was triggered for [userip] the ip address, a user connected from [username] the user...

  • Page 277

    Chapter 6: using the web interface 258 sample inlet-level event rule in this example, we want the px to send snmp notifications to the snmp manager for any sensor change event of the inlet i1. Note: the snmp notifications may be snmp v2c or snmp v3 traps or informs, depending on the settings for the...

  • Page 278

    Chapter 6: using the web interface 259 sample environmental-sensor-level event rule this section applies to outlet-switching capable models only. In this example, we want px to enable the load shedding function when a contact closure sensor enters the alarmed state. This sample event rule requires c...

  • Page 279

    Chapter 6: using the web interface 260 7. Select state sensor because the contact closure sensor is a discrete sensor, which indicates the environmental changes through the status changes. 8. Select "alarmed/open/on" in the submenu since we want the action "activate loading shedding" to be taken whe...

  • Page 280

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

  • Page 281

    Chapter 6: using the web interface 262 for example, in a user activity event rule for the "admin" user, you can click the "admin" tab to display a pull-down submenu showing all user names, and then select a different user name or all users (shown as ). 5. If the "trigger condition" field is availabl...

  • Page 282

    Chapter 6: using the web interface 263 modifying an action an existing action can be changed so that all event rules where this action is involved change their behavior accordingly. Exception: the built-in actions "system event log action" and "system tamper alarm" are not user-configurable. To modi...

  • Page 283

    Chapter 6: using the web interface 264 c. Click delete. D. Click yes on the confirmation message. 4. Click close to quit the dialog. A note about untriggered rules in some cases, a measurement exceeds a threshold causing the px to generate an alert. The measurement then returns to a value within the...

  • Page 284

    Chapter 6: using the web interface 265 note: sometimes when the dialog is too narrow, the icon takes the place of the show details button. In that case, click and select show details to view details. Click to view the latest events. View a specific type of events only by selecting an event type in t...

  • Page 285

    Chapter 6: using the web interface 266 - type a number in the page text box and press enter to go to a specific page. Select a log entry from the list and click show details, or simply double-click the log entry to view detailed information. Note: sometimes when the dialog is too narrow, the icon ta...

  • Page 286

    Chapter 6: using the web interface 267 column description idle time the length of time for which a user remains idle. The unit "min" represents minutes. 2. To disconnect any user, click the corresponding disconnect button. A. A dialog appears, prompting you to confirm the operation. B. Click yes to ...

  • Page 287

    Chapter 6: using the web interface 268 2. Click new. The add new server dialog appears. 3. By default, the "enable ping monitoring for this server" checkbox is selected. If not, select it to enable this feature. 4. Provide the information required. Field description ip address/hostname ip address or...

  • Page 288

    Chapter 6: using the web interface 269 example: ping monitoring and snmp notifications in this illustration, it is assumed that a significant pdu (ip address: 192.168.84.95) shall be monitored by your px to make sure that pdu is properly operating all the time, and the px must send out snmp notifica...

  • Page 289

    Chapter 6: using the web interface 270 3. In the "rule name" field, type "send snmp notifications for pdu (192.168.84.95) inaccessibility." 4. Select the enabled checkbox to enable this new rule. 5. In the event field, choose server monitoring > 192.168.84.95 > unreachable. 6. In the "trigger condit...

  • Page 290

    Chapter 6: using the web interface 271 4. Click yes on the confirmation message. 5. Click close to quit the dialog. Checking server monitoring states server monitoring results are available in the server reachability dialog after specifying it devices for the px device to monitor their network acces...

  • Page 291

    Chapter 6: using the web interface 272 4. The px should automatically manage the detected sensors and actuators. Verify whether detected sensors and actuators are managed. If not, have them managed. See managing environmental sensors or actuators (on page 276). 5. Configure the sensors and actuators...

  • Page 292

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

  • Page 293

    Chapter 6: using the web interface 274 matching the position dpx2, dpx3 and dx sensor packages can be daisy chained. The px can indicate each sensor or actuator's position by showing the sensor port where the environmental sensor package is connected as well as its sequence in a sensor daisy chain. ...

  • Page 294

    Chapter 6: using the web interface 275 for example, if a dpx sensor package is connected to the sensor port numbered 1, its position column only shows "port 1" no matter a dpx3-envhub4 sensor hub is used or not. Note: for the px devices with only one sensor port, it always shows "port 1." dpx2, dpx3...

  • Page 295

    Chapter 6: using the web interface 276 managing environmental sensors or actuators the px starts to retrieve an environmental sensor's reading and/or state and records the state transitions after the environmental sensor is managed. To control an actuator, you also need to have it managed. The px de...

  • Page 296

    Chapter 6: using the web interface 277 tip: the information in parentheses following each id number indicates whether the number has been assigned to any sensor or actuator. If it has been assigned to a sensor or actuator, it shows its serial number. Otherwise, it shows the word "unused." the manual...

  • Page 297

    Chapter 6: using the web interface 278 configuring environmental sensors or actuators you can change the default name to easily identify the managed sensor or actuator, and describe its location with x, y and z coordinates. To configure environmental sensors or actuators: 1. Click peripheral devices...

  • Page 298

    Chapter 6: using the web interface 279 5. If the selected sensor is a numeric sensor, its threshold settings are displayed in the dialog. See sensor threshold settings (on page 592) for detailed information. There are two types of thresholds: sensor-specific thresholds and default thresholds. To use...

  • Page 299

    Chapter 6: using the web interface 280 2. Click setup in the settings section. The pdu setup dialog appears. 3. In the peripheral device z coordinate format field, click the drop-down arrow and select an option from the list. Rack units: the height of the z coordinate is measured in standard rack un...

  • Page 300

    Chapter 6: using the web interface 281 changing default thresholds the default thresholds are the initial threshold values that automatically apply to numeric environmental sensors. These values are configured on a sensor type basis, which include: temperature sensors humidity sensors (both relative...

  • Page 301

    Chapter 6: using the web interface 282 setting thresholds for multiple sensors you can configure thresholds for multiple environmental sensors of the same type at a time. For example, if you want all temperature sensors to have identical upper and lower thresholds, follow the procedure below to set ...

  • Page 302

    Chapter 6: using the web interface 283 viewing sensor or actuator data readings and states of the environmental sensors or actuators will display in the web interface after the sensors and actuators are properly connected and managed. The dashboard page shows the information of managed environmental...

  • Page 303

    Chapter 6: using the web interface 284 position serial number type channel (for a sensor package with contact closure or dry contact channels) whether the sensor is an 'actuator' or not (if yes, this icon appears in the actuator column) reading state states of managed sensors an environmental sensor...

  • Page 304

    Chapter 6: using the web interface 285 "unavailable" state the unavailable state means the connectivity or communications with the sensor is lost. The px pings all managed sensors at regular intervals in seconds. If it does not detect a particular sensor for three consecutive scans, the unavailable ...

  • Page 305

    Chapter 6: using the web interface 286 "alarmed" state this state means a discrete (on/off) sensor is in the "abnormal" state. Usually for a contact closure sensor, the meaning of this state varies based on the sensor's normal state setting. If the normal state is set to normally closed, the alarmed...

  • Page 306

    Chapter 6: using the web interface 287 "above upper critical" state this state means a numeric sensor's reading is above the upper critical threshold as indicated below: upper critical threshold note: the symbol states of managed actuators dx sensor packages with dry contact channels allow you to co...

  • Page 307

    Chapter 6: using the web interface 288 note: if the desired action cannot be performed on any of the selected sensors or actuators, that action becomes unavailable. Deselect the inapplicable ones to perform the action. 3. Click release. After a sensor or actuator is removed from management: the id n...

  • Page 308

    Chapter 6: using the web interface 289 controlling actuators if you have any dx sensor packages with actuators connected, which can move or control a mechanism or system, you can remotely turn on or off the actuators to control the connected mechanism or system. To turn on or off an individual actua...

  • Page 309

    Chapter 6: using the web interface 290 note: the asset sensor is named "asset strip 1" by default. The name changes after being customized. Tip: the same asset sensor's page can be also opened by clicking feature port in the left pane, and then double-clicking the asset sensor in the right pane. 3. ...

  • Page 310

    Chapter 6: using the web interface 291 11. Click ok. Setting asset sensor led colors each led on the asset sensor indicates the presence and absence of a connected asset tag by changing its color. By default the led color of the tag ports with tags connected is green, and the color of the tag ports ...

  • Page 311

    Chapter 6: using the web interface 292 note: the asset sensor is named "asset strip 1" by default. The name changes after being customized. Tip: the same asset sensor's page can be also opened by clicking feature port in the left pane, and then double-clicking the asset sensor in the right pane. 3. ...

  • Page 312

    Chapter 6: using the web interface 293 2. Locate the rack unit (tag port) where the blade extension strip is connected. 3. Double-click that rack unit or click the white arrow prior to the folder icon. The arrow then turns into a black, gradient arrow , and all tag ports of the blade extension strip...

  • Page 313

    Chapter 6: using the web interface 294 2. Click the desired asset sensor in the left pane. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports). Note: you can also access this dialog by double-clicking the ass...

  • Page 314

    Chapter 6: using the web interface 295 saving the px configuration a source device is an already configured px device that is used to create a configuration file containing the settings that can be shared between px devices. These settings include user and role configurations, thresholds, event rule...

  • Page 315

    Chapter 6: using the web interface 296 copying the px configuration a target device is the px device that loads another px device's configuration file. Copying a source px device's configuration to a target device adjusts the target px device's settings to match those of the source px device. In ord...

  • Page 316

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

  • Page 317

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

  • Page 318

    Chapter 6: using the web interface 299 4. Type the location information in each location field if needed. Up to 63 characters are supported. 5. Select a resolution for the webcam. If you connect two webcams to one usb-a port using a powered usb hub, set the resolution to 352x288 or lower for optimal...

  • Page 319

    Chapter 6: using the web interface 300 viewing webcam snapshots or videos you can switch between snapshots or live videos being captured by a webcam. The snapshot or video is displayed either in the px web interface or in a primary standalone live preview window that you open. You can open a maximum...

  • Page 320

    Chapter 6: using the web interface 301 the webcam's location information, if available, is displayed in the location pane of the px web interface. To change any image settings, click setup . See configuring webcams (on page 298) or adjusting image properties (on page 299). To save the snapshot being...

  • Page 321

    Chapter 6: using the web interface 302 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, which permits a link to the snapshot or video being captured. You are able to email or inst...

  • Page 322

    Chapter 6: using the web interface 303 neither the primary standalone live preview window nor any remote session based on the same url remains open, but the idle timeout period has not expired yet since the last live preview window session was closed. For information on idle timeout, see enabling lo...

  • Page 323

    Chapter 6: using the web interface 304 snapshot storage once a snapshot is taken using the store snapshot to webcam storage feature, it is stored locally on the px by default. Up to ten (10) images can be stored on the px at once. To save more than 10 snapshots, save the images on a common internet ...

  • Page 324

    Chapter 6: using the web interface 305 tip: to store snapshots on a remote server rather than the px, see configuring webcam storage (on page 306). Managing the snapshots saved to px a maximum of 10 saved snapshots can be stored and displayed on the snapshots page of the px. See saving snapshots (on...

  • Page 325

    Chapter 6: using the web interface 306 to delete any snapshot from the storage: delete snapshots by selecting the checkbox next to the snapshot you want to delete, then clicking the delete icon at the top of the section. To select and delete all snapshots at once, click the checkbox in the checkbox ...

  • Page 326

    Chapter 6: using the web interface 307 network diagnostics the px provides the following tools in the web interface for diagnosing potential networking issues. Ping trace route list tcp connections tip: these network diagnostic tools are also available through cli. See network troubleshooting (on pa...

  • Page 327

    Chapter 6: using the web interface 308 5. Click run. A dialog appears, displaying the trace route results. Listing tcp connections you can use the "list tcp connections" to display a list of tcp connections. To list tcp connections: 1. Choose maintenance > network diagnostics > list tcp connections....

  • Page 328

    Chapter 6: using the web interface 309 managing the schroff lhx/shx heat exchanger the px supports monitoring and administering the schroff ® lhx-20, lhx-40 and shx-30 heat exchanger if this device is connected to the px. From the px, you can do the following remotely: name a connected lhx heat exch...

  • Page 329

    Chapter 6: using the web interface 310 enabling and disabling schroff lhx/shx heat exchanger support by default, schroff lhx/shx heat exchanger support is disabled. As such, support needs to be enabled before the device appears in the navigation tree or on the dashboard. Additionally, schroff lhx/sh...

  • Page 330

    Chapter 6: using the web interface 311 setting up an lhx/shx once a schroff lhx/shx heat exchanger is connected, you can set up the device by giving it a name, and configure its setpoint air outlet and default fan speed. To set up the lhx/shx: 1. Expand the feature port folder as needed. 2. Click th...

  • Page 331

    Chapter 6: using the web interface 312 3. Select the desired sensor in the sensors table and click setup thresholds, or double-click that sensor. The setup dialog for the selected sensor appears. 4. Adjust the threshold and deassertion hysteresis settings. The upper critical and lower critical value...

  • Page 332

    Chapter 6: using the web interface 313 viewing the summary both the dashboard and feature port pages display the summary of the connected lhx/shx heat exchanger, including the heat exchanger's name and status. If an lhx/shx is highlighted in red in the summary, it indicates that there is lhx/shx sen...

  • Page 333

    Chapter 6: using the web interface 314 device states and icon variations the px web interface changes icons to represent different statuses of the connected lhx/shx heat exchanger. Icons device status the heat exchanger is turned on and operating normally. The heat exchanger is turned off. The heat ...

  • Page 334

    Chapter 6: using the web interface 315 operating hours operating hours are the accumulative time since the lhx/shx heat exchanger is first connected to the px device and turned on. The px web interface displays the operating hours both for the heat exchanger and its fans. Operating hour information ...

  • Page 335

    Chapter 6: using the web interface 316 requesting maximum cooling for an shx-30 the px allows you to remotely activate the schroff shx-30's maximum cooling feature. The lhx-20 and lhx-40 do not support remote activation of maximum cooling. When you click request maximum cooling on the px web interfa...

  • Page 336

    Chapter 6: using the web interface 317 updating the px firmware when performing the firmware upgrade, the px keeps each outlet's power status unchanged so no server operation is interrupted. Outlets that have been powered on prior to the firmware upgrade remain powered on and outlets that have been ...

  • Page 337

    Chapter 6: using the web interface 318 the front panel display on the px shows three digits: 'fup' or 'fup.' exception: a px3 phase ii model shows the upgrade progress in percent instead of fup on its lcd display. The outlet leds flash when the relay boards are being updated. Exception: if the firmw...

  • Page 338

    Chapter 6: using the web interface 319 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 339

    Chapter 6: using the web interface 320 viewing firmware update history the firmware upgrade history, if available, is permanently stored on the px device. This history indicates when a firmware upgrade event occurred, the prior and new versions associated with the firmware upgrade event, and the upg...

  • Page 340

    Chapter 6: using the web interface 321 updating the asset sensor firmware after connecting the asset sensor to the px device, it automatically checks its own firmware version against the version of the asset sensor firmware stored in the px firmware. If two versions are different, the asset sensor a...

  • Page 341

    Chapter 6: using the web interface 322 to view the next topic, click the next icon in the toolbar. To view the previous topic, click the previous icon . To view the first topic, click the home icon . 4. To expand or collapse a topic that contains sub-topics, do the following: to expand any topic, cl...

  • Page 342: Chapter 7

    323 this snmp section helps you set up the px for use with an snmp manager. The px 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 snmp ........................

  • Page 343

    Chapter 7: using snmp 324 2. Select the "enable" checkbox in the "snmp v1 / v2c" field to enable communication with an snmp manager using snmp v1 or v2c protocol. Type the snmp read-only community string in the read community string field. Usually the string is "public." type the read/write communit...

  • Page 344

    Chapter 7: using snmp 325 5. Click ok. The user is now set up for encrypted snmp v3 communication. Configuring snmp notifications the px automatically keeps an internal log of events that occur. See event rules and actions (on page 213). These events can also be used to send snmp v2c or v3 notificat...

  • Page 345

    Chapter 7: using snmp 326 snmpv2c notifications to configure the px to send snmp notifications: 1. Choose device settings > network services > snmp. The snmp settings dialog appears. 2. On the notifications tab, select the enabled checkbox to enable the snmp notification feature..

  • Page 346

    Chapter 7: using snmp 327 3. From the notification type drop-down, select the type of snmp notification. 4. For snmp inform communications, leave the resend settings at their default or: a. In the timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is ...

  • Page 347

    Chapter 7: using snmp 328 snmpv3 notifications to configure the px to send snmpv3 notifications: 1. Choose device settings > network services > snmp. The snmp settings dialog appears. 2. On the notifications tab, select the enabled checkbox to enable the snmp notification feature..

  • Page 348

    Chapter 7: using snmp 329 3. From the notification type drop-down, select the type of snmp notification. 4. For snmp traps, the engine id is prepopulated. 5. For snmp inform communications, leave the resend settings at their default or: a. In the timeout (sec) field, enter the interval of time, in s...

  • Page 349

    Chapter 7: using snmp 330 security level description "noauthnopriv" select this if no authorization or privacy protocols are needed. "authnopriv" select this if authorization is required but no privacy protocols are required. Select the authentication protocol - md5 or sha enter the authentication p...

  • Page 350

    Chapter 7: using snmp 331 the px mib the snmp mib file is required for using your px device with an snmp manager. An snmp mib file describes the snmp functions. Downloading snmp mib the snmp mib file for the px can be easily downloaded from the web interface. There are two ways to download the snmp ...

  • Page 351

    Chapter 7: using snmp 332 layout opening the mib reveals the custom objects that describe the px 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 a...

  • Page 352

    Chapter 7: using snmp 333 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 px to generate a warning and s...

  • Page 353

    Chapter 7: using snmp 334 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 354: Chapter 8

    335 this section explains how to use the command line interface (cli) to administer a px device. In this chapter about the interface ................................................................................335 logging in to cli ....................................................................

  • Page 355

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

    Chapter 8: using the command line interface 337 5. Type a password and press enter. The password is case sensitive. After properly entering the password, the # or > system prompt appears. See different cli modes and prompts (on page 339) in the user guide for more information. Tip: the "last login" ...

  • Page 357

    Chapter 8: using the command line interface 338 tip: the "last login" information, including the date and time, is also displayed if the same user profile was used to log in to this product's web interface or cli. 6. You are now logged in to the command line interface and can begin administering the...

  • Page 358

    Chapter 8: using the command line interface 339 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 px device, the > prompt app...

  • Page 359

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

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

    Chapter 8: using the command line interface 342 network configuration this command shows all network configuration, such as the ip address, networking mode, and mac address. # show network ip configuration this command shows the ip-related configuration only, such as ipv4 and ipv6 configuration, add...

  • Page 362

    Chapter 8: using the command line interface 343 networking mode this command shows whether the current networking mode is wired or wireless. # show network mode note: if the px is a slave device connected to the lan via the master px device, the show network mode command displays wired(usb) instead ...

  • Page 363

    Chapter 8: using the command line interface 344 option description https only displays the tcp port for the https service. Telnet only displays the settings of the telnet service. Ssh only displays the settings of the ssh service. Snmp only displays the snmp settings. Modbus only displays the settin...

  • Page 364

    Chapter 8: using the command line interface 345 outlet information this command syntax shows the outlet information. # show outlets to show detailed information, add the parameter "details" to the end of the command. # show outlets details variables: is one of the options: all, or a number. Option d...

  • Page 365

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

  • Page 366

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

    Chapter 8: using the command line interface 348 date and time settings this command shows the current date and time settings on the px 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 s...

  • Page 368

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

    Chapter 8: using the command line interface 350 * the environmental sensor number is the id number assigned to the sensor, which can be found on the peripheral devices page of the px web interface. Displayed information: without the parameter "details," only the sensor id, sensor type and reading ar...

  • Page 370

    Chapter 8: using the command line interface 351 environmental sensor package information different from the "show externalsensors" commands, which show the reading, status and configuration of an individual environmental sensor, the following command shows the information of all connected environmen...

  • Page 371

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

  • Page 372

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

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

  • Page 374

    Chapter 8: using the command line interface 355 displayed information: without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified inlet pole sensor are displayed. With the parameter "details," more sensor information is...

  • Page 375

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

    Chapter 8: using the command line interface 357 variables: is the environmental sensor number. The environmental sensor number is the id number assigned to the sensor, which can be found on the peripheral devices page of the px web interface. Displayed information: without the parameter "details," o...

  • Page 377

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

  • Page 378

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

  • Page 379

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

  • Page 380

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

  • Page 381

    Chapter 8: using the command line interface 362 option description a specific asset sensor number displays the settings of the asset sensor connected to the specified feature port number. For the px device with only one feature port, the valid number is always 1. Rack unit settings of an asset senso...

  • Page 382

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

  • Page 383

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

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

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

    Chapter 8: using the command line interface 367 command history this command syntax shows the command history for current connection session. # show history displayed information: a list of commands that were previously entered in the current session is displayed. History buffer length this command ...

  • Page 387

    Chapter 8: using the command line interface 368 examples this section provides examples of the show command. Example 1 - basic security information the diagram shows the output of the show security command..

  • Page 388

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

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

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

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

  • Page 392

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

  • Page 393

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

  • Page 394

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

  • Page 395

    Chapter 8: using the command line interface 376 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 setting non-critical outlets and load shedding mo...

  • Page 396

    Chapter 8: using the command line interface 377 for more information, see setting data logging (on page 143). 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...

  • Page 397

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

  • Page 398

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

    Chapter 8: using the command line interface 380 setting the networking mode if your px device is implemented with both wired and wireless networking mechanisms, you must determine which mechanism is enabled for network connectivity before further configuring networking parameters. This command enabl...

  • Page 400

    Chapter 8: using the command line interface 381 mode description v6only enables ipv6 only on all interfaces. Both enables both ipv4 and ipv6 on all interfaces. Selecting ipv4 or ipv6 addresses this command determines which ip address is used when the dns server returns both of ipv4 and ipv6 addresse...

  • Page 401

    Chapter 8: using the command line interface 382 setting the ssid this command specifies the ssid string. Config:# network wireless ssid variables: is the name of the wireless access point, which consists of: - up to 32 ascii characters - no spaces - ascii codes 0x20 ~ 0x7e setting the authentication...

  • Page 402

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

    Chapter 8: using the command line interface 384 config:# network wireless allowconnectionwithincorrectclock variables: the value of is peap because px only supports protected extensible authentication protocol (peap) as the outer authentication. The value of is mschapv2 because px only supports micr...

  • Page 404

    Chapter 8: using the command line interface 385 eap ca certificate example this section provides a ca certificate example only. Your ca certificate contents should be different from the contents displayed in this example. To provide a ca certificate: 1. Make sure you have entered the configuration m...

  • Page 405

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

  • Page 406

    Chapter 8: using the command line interface 387 setting the ipv4 configuration mode this command determines the ip configuration mode. Config:# network ipv4 ipconfigurationmode variables: is one of the modes: dhcp or static. Mode description dhcp the ipv4 configuration mode is set to dhcp. Static th...

  • Page 407

    Chapter 8: using the command line interface 388 setting the ipv4 subnet mask after selecting the static ip configuration mode, you can use this command to define the subnet mask. Config:# network ipv4 subnetmask variables: is the subnet mask address. The value ranges from 0.0.0.0 to 255.255.255.255....

  • Page 408

    Chapter 8: using the command line interface 389 setting the ipv4 secondary dns server after selecting the static ip configuration mode, you can use this command to specify the secondary dns server. If you have selected the dhcp configuration mode, you still can manually specify dns servers with this...

  • Page 409

    Chapter 8: using the command line interface 390 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 px and devices in the other subnet. These commands are ...

  • Page 410

    Chapter 8: using the command line interface 391 setting the ipv6 configuration mode this command determines the ip configuration mode. Config:# network ipv6 ipconfigurationmode variables: is one of the modes: automatic or static. Mode description automatic the ipv6 configuration mode is set to autom...

  • Page 411

    Chapter 8: using the command line interface 392 setting the ipv6 gateway after selecting the static ip configuration mode, you can use this command to specify the gateway. Config:# network ipv6 gateway variables: is the ip address of the gateway. This value uses the ipv6 address format. Setting the ...

  • Page 412

    Chapter 8: using the command line interface 393 overriding the ipv6 dhcp-assigned dns server after specifying the primary/secondary dns server, you can use this command to override the dhcp-assigned dns server with the one you specified. Config:# network ipv6 overridedns variables: is one of the opt...

  • Page 413

    Chapter 8: using the command line interface 394 config:# network ipv6 staticroutes modify variables: is the ip address and prefix length of the subnet where the px belongs. The format is ip address/prefix length. Is the ip address of the next hop router. Is the id number of the route setting which y...

  • Page 414

    Chapter 8: using the command line interface 395 changing the lan duplex mode this command determines the lan interface duplex mode. Config:# network interface laninterfaceduplexmode variables: is one of the modes: auto, half or full. Option description auto the px selects the optimum transmission mo...

  • Page 415

    Chapter 8: using the command line interface 396 setting the http port the commands used to configure the http port settings begin with network services http . Change the http port: config:# network services http port enable or disable the http port: config:# network services http enabled variables: ...

  • Page 416

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

    Chapter 8: using the command line interface 398 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 the ssh configuration you can enable or disable the ssh se...

  • Page 418

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

  • Page 419

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

  • Page 420

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

  • Page 421

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

  • Page 422

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

    Chapter 8: using the command line interface 404 mode description ntp the date and time settings synchronize with a specified ntp server. Setting ntp parameters a time configuration command that is used to set the ntp parameters begins with time ntp. Specifying the primary ntp server this command spe...

  • Page 424

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

  • Page 425

    Chapter 8: using the command line interface 406 customizing the date and time if intending to manually configure the date and time, use the following cli commands to specify them. Note: you shall set the time configuration method to "manual" prior to customizing the date and time. See determining th...

  • Page 426

    Chapter 8: using the command line interface 407 examples this section illustrates several time configuration examples. Example 1 - time setup method the following command sets the date and time settings by using the ntp servers. Config:# time method ntp example 2 - primary ntp server the following c...

  • Page 427

    Chapter 8: using the command line interface 408 security configuration commands a security configuration command begins with security. Firewall control you can manage firewall control features through the cli. The firewall control lets you set up rules that permit or disallow access to the px device...

  • Page 428

    Chapter 8: using the command line interface 409 config:# security ipaccesscontrol ipv6 defaultpolicyin determine the default ipv6 firewall control policy for outbound traffic: config:# security ipaccesscontrol ipv6 defaultpolicyout variables: is one of the options: true or false. Option description ...

  • Page 429

    Chapter 8: using the command line interface 410 config:# security ipaccesscontrol ipv4 rule add add a new ipv4 rule by inserting it above or below a specific rule: config:# security ipaccesscontrol ipv4 rule add -- or -- config:# security ipaccesscontrol ipv4 rule add ipv6 commands add a new rule to...

  • Page 430

    Chapter 8: using the command line interface 411 is the combination of the ip address and subnet mask values (or prefix length), which are separated with a slash. For example, an ipv4 combination looks like this: 192.168.94.222/24. Is one of the options: accept, drop or reject. Policy description acc...

  • Page 431

    Chapter 8: using the command line interface 412 config:# security ipaccesscontrol ipv4 rule modify ipmask policy ipv6 commands modify an ipv6 rule's ip address and/or prefix length: config:# security ipaccesscontrol ipv6 rule modify ipmask modify an ipv6 rule's policy: config:# security ipaccesscont...

  • Page 432

    Chapter 8: using the command line interface 413 option description reject discards traffic from/to the specified ip address(es), and an icmp message is sent to the source or destination host for failure notification. Deleting a firewall rule the following commands remove a specific ipv4 or ipv6 rule...

  • Page 433

    Chapter 8: using the command line interface 414 enabling or disabling the restricted service agreement this command activates or deactivates the restricted service agreement. Config:# security restrictedserviceagreement enabled variables: is one of the options: true or false. Option description true...

  • Page 434

    Chapter 8: using the command line interface 415 if the content is successfully entered, the cli displays this message "successfully entered restricted service agreement" followed by the total number of entered characters in parentheses. Note: the new content of restricted service agreement is saved ...

  • Page 435

    Chapter 8: using the command line interface 416 single login limitation this command enables or disables the single login feature, which controls whether multiple logins using the same login name simultaneously is permitted. Config:# security loginlimits singlelogin variables: is one of the options:...

  • Page 436

    Chapter 8: using the command line interface 417 idle timeout this command determines how long a user can remain idle before that user is forced to log out of the px web interface or cli. Config:# security loginlimits idletimeout variables: is a numeric value in minutes set for the idle timeout. The ...

  • Page 437

    Chapter 8: using the command line interface 418 strong passwords the strong password commands determine whether a strong password is required for login, and what a strong password should contain at least. A strong password command begins with security strongpasswords . You can combine multiple stron...

  • Page 438

    Chapter 8: using the command line interface 419 lowercase character requirement this command determines whether a strong password includes at least a lowercase character. Config:# security strongpasswords enforceatleastonelowercasecharacter variables: is one of the options: enable or disable. Option...

  • Page 439

    Chapter 8: using the command line interface 420 option description disable no numeric character is required. Special character requirement this command determines whether a strong password includes at least a special character. Config:# security strongpasswords enforceatleastonespecialcharacter vari...

  • Page 440

    Chapter 8: using the command line interface 421 modifying role-based access control parameters there are different commands for modifying role-based access control parameters. Ipv4 commands enable or disable the ipv4 role-based access control feature: config:# security rolebasedaccesscontrol ipv4 en...

  • Page 441

    Chapter 8: using the command line interface 422 managing role-based access control rules you can add, delete or modify role-based access control rules. An ipv4 role-based access control command for managing rules begins with security rolebasedaccesscontrol ipv4 rule. An ipv6 role-based access contro...

  • Page 442

    Chapter 8: using the command line interface 423 config:# security rolebasedaccesscontrol ipv6 rule add variables: is the starting ip address. Is the ending ip address. Is the role for which you want to create an access control rule. Is one of the options: allow or deny. Policy description allow acce...

  • Page 443

    Chapter 8: using the command line interface 424 config:# security rolebasedaccesscontrol ipv4 rule modify role modify an ipv4 rule's policy: config:# security rolebasedaccesscontrol ipv4 rule modify policy modify all contents of an existing ipv4 rule: config:# security rolebasedaccesscontrol ipv4 ru...

  • Page 444

    Chapter 8: using the command line interface 425 config:# security rolebasedaccesscontrol ipv6 rule modify startipaddress endipaddress role policy variables: is the number of the existing rule that you want to modify. Is the starting ip address. Is the ending ip address. Is one of the existing roles....

  • Page 445

    Chapter 8: using the command line interface 426 enabling or disabling front panel outlet switching this section applies to outlet-switching capable models only. The following cli commands control whether you can turn on or off an outlet by operating the front panel display. To enable the front panel...

  • Page 446

    Chapter 8: using the command line interface 427 config:# security ipaccesscontrol ipv4 rule add 192.168.84.123/24 accept insertabove 5 results: a new ipv4 firewall control rule is added to accept all packets sent from the ipv4 address 192.168.84.123. The newly-added rule is inserted above the 5th ru...

  • Page 447

    Chapter 8: using the command line interface 428 outlet configuration commands an outlet configuration command begins with outlet. Such a command allows you to configure an individual outlet. Changing the outlet name this command names an outlet. Config:# outlet name "" variables: is the number of th...

  • Page 448

    Chapter 8: using the command line interface 429 note: setting the outlet's default state to an option other than pdudefined overrides the pdu-defined default state on that outlet. See setting the pdu-defined default outlet state (on page 374). Setting an outlet's cycling power-off period this sectio...

  • Page 449

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

  • Page 450

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

  • Page 451

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

  • Page 452

    Chapter 8: using the command line interface 433 changing a user's password this command allows you to change an existing user's password if you have the administrator privileges. Config:# user modify password after performing the above command, px prompts you to enter a new password. Then: 1. Type a...

  • Page 453

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

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

  • Page 455

    Chapter 8: using the command line interface 436 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 482). Enable o...

  • Page 456

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

  • Page 457

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

  • Page 458

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

  • Page 459

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

  • Page 460

    Chapter 8: using the command line interface 441 c. Paste the contents into the terminal. 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 fo...

  • Page 461

    Chapter 8: using the command line interface 442 2. Type the following command and press enter. 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 pa...

  • Page 462

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

  • Page 463

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

  • Page 464

    Chapter 8: using the command line interface 445 config:# user defaultpreferences preferredtemperatureunit f preferredlengthunit feet preferredpressureunit psi results: the default temperature unit is set to fahrenheit. The default length unit is set to feet. The default pressure unit is set to psi. ...

  • Page 465

    Chapter 8: using the command line interface 446 all privileges this table lists all privileges. Note that available privileges vary according to the model you purchased. For example, a pdu without the outlet switching function does not have the privilege "switchoutlet." privilege description acknowl...

  • Page 466

    Chapter 8: using the command line interface 447 privilege description viewlog view local event log viewsecuritysettings view security settings viewsnmpsettings view snmp settings viewusersettings view local user management viewwebcamsettings view webcam snapshots and configuration * the "switchoutle...

  • Page 467

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

  • Page 468

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

  • Page 469

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

  • Page 470

    Chapter 8: using the command line interface 451 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 px web interface or using the com...

  • Page 471

    Chapter 8: using the command line interface 452 setting the x coordinate this command specifies the x coordinate of an environmental sensor. Config:# externalsensor xlabel "" variables: is the id number of the environmental sensor that you want to configure. The id number is available in the px web ...

  • Page 472

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

  • Page 473

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

  • Page 474

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

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

    Chapter 8: using the command line interface 457 example - default upper thresholds for temperature it is assumed that your preferred measurement unit for temperature is set to degrees celsius. Then the following command sets the default upper warning threshold to 20 and upper critical threshold to 2...

  • Page 477

    Chapter 8: using the command line interface 458 config:# sensor inlet lowercritical set the lower warning threshold for an inlet sensor: config:# sensor inlet lowerwarning set the deassertion hysteresis for an inlet sensor: config:# sensor inlet hysteresis set the assertion timeout for an inlet sens...

  • Page 478

    Chapter 8: using the command line interface 459 is one of the options: enable, disable or a numeric value. Option description enable enables the specified threshold for a specific inlet sensor. Disable disables the specified threshold for a specific inlet sensor. A numeric value sets a value for the...

  • Page 479

    Chapter 8: using the command line interface 460 config:# sensor inletpole assertiontimeout variables: is the number of the inlet whose pole sensors you want to configure. Is the label of the inlet pole that you want to configure. Pole label current sensor voltage sensor 1 l1 l1 l1 - l2 2 l2 l2 l2 - ...

  • Page 480

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

  • Page 481

    Chapter 8: using the command line interface 462 config:# sensor ocp assertiontimeout variables: is the number of the overcurrent protector that you want to configure. Is one of the following sensor types: sensor type description current current sensor note: if the requested sensor type is not suppor...

  • Page 482

    Chapter 8: using the command line interface 463 config:# sensor externalsensor uppercritical set the upper warning threshold for an environmental sensor: config:# sensor externalsensor upperwarning set the lower critical threshold for an environmental sensor: config:# sensor externalsensor lowercrit...

  • Page 483

    Chapter 8: using the command line interface 464 is one of the options: enable, disable or a numeric value. Option description enable enables the specified threshold for a specific environmental sensor. Disable disables the specified threshold for a specific environmental sensor. A numeric value sets...

  • Page 484

    Chapter 8: using the command line interface 465 example 3 - upper thresholds for overcurrent protector sensors the following command sets both the upper critical and upper warning thresholds for the 2nd overcurrent protector. Config:# sensor ocp 2 current upperwarning enable uppercritical 16 results...

  • Page 485

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

  • Page 486

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

  • Page 487

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

  • Page 488

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

    Chapter 8: using the command line interface 470 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 one of t...

  • Page 490

    Chapter 8: using the command line interface 471 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 px device is enabled. Config:# ener...

  • Page 491

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

  • Page 492

    Chapter 8: using the command line interface 473 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 px is enabled. The udp port is set to 10288. Usb-casca...

  • Page 493

    Chapter 8: using the command line interface 474 asset sensor management an asset sensor management configuration command begins with assetstrip . Naming an asset sensor this command syntax names or changes the name of an asset sensor connected to the px device. Config:# assetstrip name "" variables:...

  • Page 494

    Chapter 8: using the command line interface 475 specifying the rack unit numbering mode this command syntax specifies the numbering mode of rack units on the asset sensors connected to the px device. The numbering mode changes the rack unit numbers. Config:# assetstrip rackunitnumberingmode variable...

  • Page 495

    Chapter 8: using the command line interface 476 specifying the asset sensor orientation this command syntax specifies the orientation of the asset sensors connected to the px device. Usually you do not need to perform this command unless your asset sensors do not come with the tilt sensor, causing t...

  • Page 496

    Chapter 8: using the command line interface 477 setting led colors for disconnected tags this command syntax sets the led color for all rack units on the connected asset sensor(s) to indicate the absence of a connected asset tag. Config:# assetstrip ledcolorfordisconnectedtags variables: is the hexa...

  • Page 497

    Chapter 8: using the command line interface 478 setting the led operation mode this command syntax determines whether a specific rack unit on the specified asset sensor follows the global led color settings. Config:# rackunit ledoperationmode variables: is the number of the feature port where the se...

  • Page 498

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

  • Page 499

    Chapter 8: using the command line interface 480 mode description blinkfast this mode has the led blink quickly. Examples this section illustrates several asset management examples. Example 1 - asset sensor led colors for disconnected tags this command syntax sets the led color for all rack units on ...

  • Page 500

    Chapter 8: using the command line interface 481 setting the baud rates the following commands set the baud rate (bps) of the serial port labeled console / modem on the px device. Change the baud rate before connecting it to the desired device, such as a computer, a raritan's p2cim-ser, or a modem, t...

  • Page 501

    Chapter 8: using the command line interface 482 option description forcegsmmodem the port enters the gsm modem state. Example the following command sets the console baud rate of the px device's serial port to 9600 bps. Config:# serial consolebaudrate 9600 setting the history buffer length this comma...

  • Page 502

    Chapter 8: using the command line interface 483 config:# network ipv4 ipaddress 192.168.84.225 subnetmask 255.255.255.0 gateway 192.168.84.0 results: the ip address is set to 192.168.84.225. The subnet mask is set to 255.255.255.0. The gateway is set to 192.168.84.0. Example 2 - combination of upper...

  • Page 503

    Chapter 8: using the command line interface 484 load shedding configuration commands this section applies to outlet-switching capable models only. A load shedding configuration command begins with loadshedding. Unlike other cli configuration commands, the load shedding configuration command is perfo...

  • Page 504

    Chapter 8: using the command line interface 485 example the following command has the px enter the load shedding mode. Config:# loadshedding start power control operations this section applies to outlet-switching capable models only. Outlets on the px device can be turned on or off or power cycled t...

  • Page 505

    Chapter 8: using the command line interface 486 option description a comma- separated list of outlets switches on multiple, inconsecutive or consecutive outlets. For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and 15, type outlets 2,4,9,11-13,15. A range of outlets with an en dash in betwee...

  • Page 506

    Chapter 8: using the command line interface 487 option description a comma- separated list of outlets switches off multiple, inconsecutive or consecutive outlets. For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and 15, type outlets 2,4,9,11-13,15. A range of outlets with an en dash in betwe...

  • Page 507

    Chapter 8: using the command line interface 488 option description a comma- separated list of outlets power cycles multiple, inconsecutive or consecutive outlets. For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and 15, type outlets 2,4,9,11-13,15. A range of outlets with an en dash in betwe...

  • Page 508

    Chapter 8: using the command line interface 489 actuator control operations an actuator, which is connected to a dry contact signal channel of a dx sensor, can control a mechanism or system. You can switch on or off that mechanism or system through the actuator control command in the cli. Perform th...

  • Page 509

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

  • Page 510

    Chapter 8: using the command line interface 491 3. When the "username to unblock" prompt appears, type the name of the blocked user and press enter. 4. A message appears, indicating that the specified user was unblocked successfully. Resetting the px you can reset the px device to factory defaults o...

  • Page 511

    Chapter 8: using the command line interface 492 to reset one inlet's active energy readings: # reset activeenergy inlet -- or -- # reset activeenergy inlet /y if you entered the command without "/y", a message appears prompting you to confirm the operation. Type y to confirm the reset or n to abort ...

  • Page 512

    Chapter 8: using the command line interface 493 2. Type diag and press enter. The diag# or diag> prompt appears, indicating that you have entered the diagnostic mode. 3. Now you can type any diagnostic commands for troubleshooting. Quitting diagnostic mode to quit the diagnostic mode, use this comma...

  • Page 513

    Chapter 8: using the command line interface 494 option description connections shows network connections. 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 properl...

  • Page 514

    Chapter 8: using the command line interface 495 tracing the route this command syntax traces the network route between your px 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 netwo...

  • Page 515

    Chapter 8: using the command line interface 496 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 516: Appendix A  Specifications

    497 in this chapter maximum ambient operating temperature ..........................................497 serial rs-232 port pinouts....................................................................497 sensor rj-12 port pinouts....................................................................497 f...

  • Page 517

    Appendix a: specifications 498 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 518

    499 px series model ____________ px 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 works...

  • Page 519

    Appendix b: equipment setup worksheet 500 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 520

    Appendix b: equipment setup worksheet 501 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 521

    Appendix b: equipment setup worksheet 502 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 522: With A Usb Drive

    503 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 px. Configuration changes firmware upgrade downloading diagnostic data tip: you can also accomplish the same tasks via the tftp se...

  • Page 523

    Appendix c: configuration or firmware upgrade with a usb drive 504 tip: you can remove the usb drive and plug it into another px for performing the same task(s) once the happy smiley or the firmware upgrade message displays. If nothing is shown on the display and no task is performed after plugging ...

  • Page 524

    Appendix c: configuration or firmware upgrade with a usb drive 505 raritan provides a mass deployment utility, which helps you to quickly generate all configuration files for your px. See creating configuration files via mass deployment utility (on page 512)..

  • Page 525

    Appendix c: configuration or firmware upgrade with a usb drive 506 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 a single = character, without any surrounding spaces. Keys are not case se...

  • Page 526

    Appendix c: configuration or firmware upgrade with a usb drive 507 if this option is set to true, the firmware upgrade is always performed even though your px is running the same firmware version as the specified firmware file. This option cannot break other constraints like the minimum downgrade ve...

  • Page 527

    Appendix c: configuration or firmware upgrade with a usb drive 508 the px utters a short beep when writing the diagnostic data to the usb drive. Factory_reset supported as of release 3.0.0. If this option is set to true, the px will be reset to factory defaults. If the device configuration will be u...

  • Page 528

    Appendix c: configuration or firmware upgrade with a usb drive 509 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.Cfg...

  • Page 529

    Appendix c: configuration or firmware upgrade with a usb drive 510 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 530

    Appendix c: configuration or firmware upgrade with a usb drive 511 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 px. This file must be: an excel file in the csv format. Copied to the root d...

  • Page 531

    Appendix c: configuration or firmware upgrade with a usb drive 512 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 532

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

  • Page 533: Upgrade Via Dhcp/tftp

    514 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 px devices in the same network. Initial deployment configuration changes firmware upgrade downloading diagnostic data this feature is drastically u...

  • Page 534

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 515 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 535

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

  • Page 536

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 517 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 537

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 518 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 538

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 519 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 539

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 520 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 540

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

  • Page 541

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

  • Page 542

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 523 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 543

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 524 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 544

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 525 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 545

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 526 important: the magic cookie is transmitted to and stored in px 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 st...

  • Page 546

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 527 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 547

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 528 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 548

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 529 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 549

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 530 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 550

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 531 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 551

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 532 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 552

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 533 important: the magic cookie is transmitted to and stored in px 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 st...

  • Page 553

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

  • Page 554

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 535 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 555

    Appendix d: bulk configuration or firmware upgrade via dhcp/tftp 536 code 2 (pdu-update-control-file) = the name of the control file "fwupdate.Cfg" 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. I...

  • Page 556

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

  • Page 557

    Appendix e: resetting to factory defaults 538 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 558

    Appendix e: resetting to factory defaults 539 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 without "/y" in step 4, a message appears prompting you to confirm the ...

  • Page 559

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

  • Page 560

    Appendix f: available scp commands 541 scp command example: scp pdu-px2-030000-41270.Bin admin@192.168.87.50:/fwupdate tip: the pscp works in a similar way to the scp so the pscp syntax is similar. Pscp @:/fwupdate bulk configuration via scp like performing bulk configuration via the web interface, ...

  • Page 561

    Appendix f: available scp commands 542 3. The system copies the configuration included in the file "bulk_config.Xml" to another px, and displays the following message. Starting restore operation. The connection will be closed now. Scp command examples: save operation's example: scp admin@192.168.87....

  • Page 562

    Appendix f: available scp commands 543 is the "admin" or any user profile with the administrator privileges. Is the ip address of the px that you want to update. 2. Type the password when the system prompts you to type it. 3. The system copies the configuration included in the file "backup_settings....

  • Page 563

    544 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 px b. Create user groups for the px on the ad...

  • Page 564

    Appendix g: ldap configuration illustration 545 step b. Configure user groups on the ad server you must create the groups (roles) for the px on the ad server, and then make appropriate users members of these groups. In this illustration, we assume: the groups (roles) for the px are named px_admin an...

  • Page 565

    Appendix g: ldap configuration illustration 546 step c. Configure ldap authentication on the px device you must enable and set up ldap authentication properly on the px device to use external authentication. In the illustration, we assume: the dns server settings have been configured properly. See m...

  • Page 566

    Appendix g: ldap configuration illustration 547 base dn for search - type dc=techadssl,dc=com as the starting point where your search begins on the ad server. Login name attribute - ensure the field is set to samaccountname because the ldap server is microsoft active directory. User entry object cla...

  • Page 567

    Appendix g: ldap configuration illustration 548 6. Click ok. The ldap authentication is activated. Note: if the px clock and the ldap server clock are out of sync, the installed tls certificates, if any, may be considered expired. To ensure proper synchronization, administrators should configure the...

  • Page 568

    Appendix g: ldap configuration illustration 549 c. Click add. 6. Click ok. The px_user role is created. 7. Keep the manage roles dialog opened to create the px_admin role. To create the px_admin role with full permissions assigned: 1. Click new. The create new role dialog appears. 2. Type px_admin i...

  • Page 569

    Appendix g: ldap configuration illustration 550 3. Type a description for the px_admin role in the description field. In this example, we type "the role includes all privileges" to describe the role. 4. Click the privileges tab to select the administrator permission. The administrator permission all...

  • Page 570

    Appendix g: ldap configuration illustration 551 5. Click ok. The px_admin role is created. 6. Click close to quit the dialog..

  • Page 571

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

  • Page 572

    Appendix h: updating the ldap schema 553 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 573

    Appendix h: updating the ldap schema 554 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 574

    Appendix h: updating the ldap schema 555 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 575

    Appendix h: updating the ldap schema 556 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 576

    Appendix h: updating the ldap schema 557 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 577

    Appendix h: updating the ldap schema 558 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 578

    559 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 non-windows radius server, such as freeradius. The following steps are required for any radius authentication: 1. Confi...

  • Page 579

    Appendix i: radius configuration illustration 560 step a: add your px as a radius client the radius implementation on a px 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. In this...

  • Page 580

    Appendix i: radius configuration illustration 561 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 px. In this example, they are 1812 and 1813. Then close this dialog..

  • Page 581

    Appendix i: radius configuration illustration 562 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 px to nps: a. Verify the "enable this radius client" checkbox is selected. B. Type a ...

  • Page 582

    Appendix i: radius configuration illustration 563 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 px. 5. Click ok. Step b: configure connection request policies you need to configure the following fo...

  • Page 583

    Appendix i: radius configuration illustration 564 b. Connection request forwarding method c. Authentication method(s) d. Standard radius attributes in the following illustration, we assume: local nps server is used ip address of your px: 192.168.56.29 radius protocol selected on your px: chap existi...

  • Page 584

    Appendix i: radius configuration illustration 565 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 585

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

  • Page 586

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

  • Page 587

    Appendix i: radius configuration illustration 568 6. The nas ipv4 address dialog appears. Type the px 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 exa...

  • Page 588

    Appendix i: radius configuration illustration 569 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 px uses "chap" ...

  • Page 589

    Appendix i: radius configuration illustration 570 note: if your px uses pap, then select "pap.".

  • Page 590

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

  • Page 591

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

  • Page 592

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

  • Page 593

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

  • Page 594

    Appendix i: radius configuration illustration 575 14. The new attribute is added. Click ok..

  • Page 595

    Appendix i: radius configuration illustration 576 15. Click next to continue..

  • Page 596

    Appendix i: radius configuration illustration 577 16. A summary showing connection request policy settings is displayed. Click finish to close the dialog..

  • Page 597

    Appendix i: radius configuration illustration 578 step c: configure a vendor-specific attribute you must specify a vendor-specific attribute (vsa) for raritan on windows 2008 nps. Raritan's vendor code is 13742. In the following illustration, we assume: there are three roles available on your px: ad...

  • Page 598

    Appendix i: radius configuration illustration 579 a. Type 26 in the "vendor-assigned attribute number" field. B. Select string in the "attribute format" field. C. Type raritan:g{admin user systemtester} in the "attribute value" field. In this example, three roles are specified inside the curved brac...

  • Page 599

    Appendix i: radius configuration illustration 580 ad-related configuration when radius authentication is intended, make sure you also configure the following settings related to microsoft active directory (ad): register the nps server in ad configure remote access permission for users in ad the nps ...

  • Page 600

    Appendix i: radius configuration illustration 581 3. Click ok, and then ok again. To grant px users remote access permission: 1. Open active directory users and computers. 2. Open the properties dialog of the user whom you want to grant the access permission..

  • Page 601

    Appendix i: radius configuration illustration 582 3. Click the dial-in tab and select the "allow access" checkbox. To enable reversible encryption for chap authentication: 1. Open active directory users and computers. 2. Open the properties dialog of the user that you want to configure..

  • Page 602

    Appendix i: radius configuration illustration 583 3. Click the account tab and select the "store password using reversible encryption" checkbox. Non-windows radius server for a non-windows radius server, such as freeradius, a vendor-specific dictionary file is required. Dictionary file create a vend...

  • Page 603

    Appendix i: radius configuration illustration 584 # -*- text -*- # # dictionary.Raritan # # # version: $id$ # vendor raritan 13742 # # standard attribute # begin-vendor raritan attribute raritan-vendor-specific 26 string end-vendor raritan note that "string" in the above contents must be replaced by...

  • Page 604

    Appendix i: radius configuration illustration 585 therefore, in raritan's dictionary file, the attribute line is like the following: attribute raritan-vendor-specific 26 raritan:g{admin user systemtester}.

  • Page 605

    586 in this chapter mac address ........................................................................................586 locking outlets and cords ....................................................................586 unbalanced current calculation ..................................................

  • Page 606

    Appendix j: additional px information 587 securelock™ outlets and cords securelock ™ is an innovative mechanism designed by raritan, which securely holds c14 or c20 plugs that are plugged into raritan pdus in place. This method requires the following two components: raritan pdu with securelock ™ out...

  • Page 607

    Appendix j: additional px information 588 to remove a securelock ™ power cord from the pdu: 1. Press and hold down the two latches on the cord's plug as illustrated in the diagram below. 2. Unplug the cord now. Button-type locking outlets a button-type locking outlet has a button on it. Such outlets...

  • Page 608

    Appendix j: additional px information 589 unbalanced current calculation unbalanced current information is available on 3-phase models only. This section explains how the px calculates the unbalanced current percentage. Calculation: 1. Calculate the average current of all 3 lines. Average current = ...

  • Page 610

    Appendix j: additional px information 591 field description ip address enter the ip address you want to reserve. Mac address enter the ascii codes of the px serial number. Do not contain spaces in the ascii codes. In this example, enter 50454731413030303033 other fields configure them according to y...

  • Page 611

    Appendix j: additional px information 592 sensor threshold settings this section explains the thresholds settings in a threshold setup dialog for a numeric internal or external sensor..

  • Page 612

    Appendix j: additional px information 593 thresholds and sensor states a numeric sensor has four threshold settings: lower critical, lower warning, upper warning and upper critical. The threshold settings determine how many sensor states are available for a certain sensor and the range of each senso...

  • Page 613

    Appendix j: additional px information 594 when a sensor has both the upper critical and upper warning thresholds enabled, it has three sensor states: normal, above upper warning, and above upper critical. States of "above upper warning" and "below lower warning" are warning states to call for your a...

  • Page 614

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

  • Page 615

    Appendix j: additional px information 596 note: for most sensors, the measurement unit in the "assertion timeout" field is sample. Because the px measures each sensor every second, timing of a sample is equal to a second. How "assertion timeout" is helpful: if you have created an event rule that ins...

  • Page 616

    Appendix j: additional px information 597 "to de-assert" and deassertion hysteresis after the px asserts a worse state for a sensor, it may de-assert the same state later on. To de-assert a state: to de-assert a state is to announce the end of the previously asserted worse state. Below are good stat...

  • Page 617

    Appendix j: additional px information 598 this function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system when the temperature exceeds a pre-determined level. "deassertion hysteresis" instructs the px to de-assert the worse state for a sensor only when tha...

  • Page 618

    Appendix j: additional px information 599 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 px detects that a temperature sensor's reading drops below 20 degrees...

  • Page 619

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

  • Page 620

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

  • Page 621

    Appendix j: additional px information 602 altitude (meters) altitude (feet) correction factor 250 820 0.98 425 1394 1.00 500 1640 1.01 740 2428 1.04 1500 4921 1.15 2250 7382 1.26 3000 9842 1.38 data for btu calculation the heat generated by the px device differs according to the model you purchased....

  • Page 622

    Appendix j: additional px information 603 ways to probe existing user profiles this section indicates available ways to query existing user accounts on the px. With snmp v3 activated, you get the "user unknown" error when the user name used to authenticate does not exist. Any user with the permissio...

  • Page 623

    Appendix j: additional px information 604 raritan training website raritan offers free training materials for various raritan products on the raritan training website http://www.Raritantraining.Com . The raritan products introduced on this website include the intelligent pdu, dctrack ® , power iq, k...

  • Page 624: Appendix K  Integration

    605 the px device can work with certain raritan's or sunbird's products to provide diverse power solutions. In this chapter dominion kx ii / iii configuration ..........................................................605 dominion ksx ii, sx or sx ii configuration........................................

  • Page 625

    Appendix k: integration 606 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 626

    Appendix k: integration 607 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 627

    Appendix k: integration 608 3. Click ok..

  • Page 628

    Appendix k: integration 609 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 629

    Appendix k: integration 610 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 630

    Appendix k: integration 611 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 631

    Appendix k: integration 612 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 609). Dominion sx and sx ii by connecting to a dominion sx or sx ii device, you can associate one or more outle...

  • Page 632

    Appendix k: integration 613 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 outlet control screen appears. 2. Check the box of outlet number you w...

  • Page 633

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

  • Page 634

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

  • Page 635

    Appendix k: integration 616 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 636

    Appendix k: integration 617 asset management sensors and dctrack if any asset sensors are connected to the px, the px can transmit their information to sunbird's dctrack. All you have to do is to add the px to dctrack, and also add each it item where an asset tag is attached to dctrack. Note: for in...

  • Page 637: Index

    619 1 1u and 2u port locations • 75 1u products • 2 2 2u products • 2 a a note about enabling thresholds • 334 a note about firmware upgrade time • 319 a note about infinite loop • 260 a note about untriggered rules • 264 about the interface • 335 access security control • 159 accessing the help • 3...

  • Page 638

    Index 620 changing telnet settings • 126 changing the cycling power-off period • 194 changing the default policy • 159, 160, 170, 171 changing the inlet name • 430 changing the lan duplex mode • 395 changing the lan interface speed • 394 changing the modbus configuration • 401 changing the modbus po...

  • Page 639

    Index 621 connecting composite asset sensors (ams-mx-z) • 64, 68 connecting environmental sensor packages • xviii, 35, 69, 271 connecting external equipment (optional) • 35, 75 connecting regular asset sensors to the px • xviii, 59, 65 connecting the pdu to a power source • 17 connecting the px to a...

  • Page 640

    Index 622 editing firewall rules • 164 editing ping monitoring settings • 270 editing rciusergroup attributes for user members • 556 editing role-based access control rules • 173 email and sms message placeholders • xviii, 222, 223, 229, 230, 254 enabling and disabling schroff lhx/shx heat exchanger...

  • Page 641

    Index 623 example 2 - combination of upper critical and upper warning settings • 483 example 2 - enabling both ip protocols • 403 example 2 - in-depth security information • 369 example 2 - modifying a user's roles • 444 example 2 - outlet sequence • 379 example 2 - primary ntp server • 407 example ...

  • Page 642

    Index 624 ip configuration • 342 l lan interface settings • 342 layout • 333 ldap configuration illustration • 186, 544 led display • 77 leds for measurement units • 79, 81 listing tcp connections • 308 load shedding configuration commands • 484 load shedding settings • 360 locking outlets and cords...

  • Page 643

    Index 625 naming the rack pdu (port page for power strips) • 607, 612 network configuration • 342 network configuration commands • 379 network diagnostics • 307 network service settings • 343 network troubleshooting • 307, 492 networking mode • 343 no support for front panel outlet switching • 202 n...

  • Page 644

    Index 626 returning user group information • 552 role configuration commands • 445 role of a dns server • 122, 546 role-based access control • 420 s safety guidelines • ii safety instructions • iii, 16 sample environmental-sensor-level event rule • 259 sample event rules • 257 sample inlet-level eve...

  • Page 645

    Index 627 setting the ipv6 secondary dns server • 392 setting the led operation mode • 478 setting the networking mode • 380 setting the outlet initialization delay • 375 setting the outlet power-on sequence • 198, 373 setting the outlet power-on sequence delay • 373 setting the outlet-specific defa...

  • Page 646

    Index 628 supported maximum dpx sensor distances • 36, 41 supported web browsers • xviii, 89 supported wireless lan configuration • 23 switch lhx/shx • 215, 231 switch outlets • 216, 232 switch peripheral actuator • 216, 233 switching an outlet • 191 switching multiple or all outlets • 190, 191, 192...

  • Page 647

    Index 629 z zero u connection ports • 74 zero u products • 2.

  • Page 648

    U.S./canada/latin america monday - friday 8 a.M. - 6 p.M. Et phone: 800-724-8090 or 732-764-8886 for commandcenter noc: press 6, then press 1 for commandcenter secure gateway: press 6, then press 2 fax: 732-764-8887 email for commandcenter noc: tech-ccnoc@raritan.Com email for all other products: te...