1. Manuals
  2. Brands
  3. Raritan Manuals
  4. Power distribution unit
  5. PX3-4000 series
  6. User manual

Raritan PX3-4000 series User Manual

Hide thumbs Also See for PX3-4000 series:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
Table of Contents

Advertisement

Quick Links

PX3-3000/4000/5000 Series
User Guide
Release 3.1
Copyright © 2015 Raritan, Inc.
PX3-0D-v3.1-E
May 2015
255-80-0035-00

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PX3-4000 series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Raritan PX3-4000 series

Summary of Contents for Raritan PX3-4000 series

  • Page 1 PX3-3000/4000/5000 Series User Guide Release 3.1 Copyright © 2015 Raritan, Inc. PX3-0D-v3.1-E May 2015 255-80-0035-00...
  • Page 2 60950-1 or equivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury and death. WARNING! Do not use a Raritan product containing outlet relays to power large inductive loads such as motors or compressors. Attempting to power a large inductive load may result in damage to the relay.

  • Page 3: Safety Instructions

    Safety Instructions 1. Installation of this product should only be performed by a person who has knowledge and experience with electric power. 2. Make sure the line cord is disconnected from power before physically mounting or moving the location of this product. 3.
  • Page 4 Raritan, Inc. © Copyright 2015 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.

  • Page 6: Table Of Contents

    Contents Safety Guidelines Safety Instructions Applicable Models xvii What's New in the PX User Guide Chapter 1 Introduction Product Models ..........................1 Package Contents.......................... 1 Zero U Products........................1 1U Products ......................... 2 2U Products ......................... 2 Chapter 2 Rack-Mounting the PDU Rackmount Safety Guidelines .......................
  • Page 7 Contents Filling Out the Equipment Setup Worksheet ..............12 Installing Cable Retention Clips on the Inlet (Optional) ...............12 Connecting a Locking Line Cord....................14 Disconnecting a Locking Line Cord ...................15 Connecting the PDU to a Power Source ..................16 Configuring the PX........................16 Connecting the PX to a Computer..................18 Installing the USB-to-Serial Driver (Optional)..............19 Connecting the PX to Your Network..................20...
  • Page 8 Contents Beeper ............................91 Replaceable Controller ........................ 91 Chapter 6 Using the Web Interface Supported Web Browsers......................93 Logging in to the Web Interface....................94 Login ..........................94 Changing Your Password....................96 Remembering User Names and Passwords ..............96 Logout ............................97 Introduction to the Web Interface....................
  • Page 9 Contents Setting Up Roles ........................160 Creating a Role........................160 Modifying a Role ......................161 Deleting a Role ........................162 Changing the Role List View ...................163 Access Security Control......................163 Forcing HTTPS Encryption....................163 Configuring the Firewall....................163 Setting Up User Login Controls ..................170 Setting Up Role-Based Access Control Rules ..............174 Setting Up a TLS Certificate ......................178 Certificate Signing Request .....................179 Creating a Self-Signed Certificate ...................181...
  • Page 10 Contents Event Rules and Actions......................222 Components of an Event Rule..................222 Creating an Event Rule ....................222 Sample Event Rules ......................262 A Note about Infinite Loop ....................265 Modifying an Event Rule....................266 Modifying an Action ......................268 Deleting an Event Rule or Action..................268 A Note about Untriggered Rules..................269 Managing Event Logging ......................269 Viewing the Local Event Log ...................269...
  • Page 11 Contents Turning the LHX/SHX On or Off ..................322 Requesting Maximum Cooling for an SHX-30..............323 Firmware Upgrade ........................323 Updating the PX Firmware ....................324 Viewing Firmware Update History ...................326 Full Disaster Recovery ....................327 Updating the Asset Sensor Firmware................327 Accessing the Help ........................327 Retrieving Software Packages Information ..............327 Browsing through the Online Help...................328 Chapter 7 Using SNMP...
  • Page 12 Contents Overcurrent Protector Sensor Threshold Information .............363 Environmental Sensor Threshold Information ..............364 Environmental Sensor Default Thresholds..............365 Security Settings......................366 Existing User Profiles ......................367 Existing Roles ........................368 Load Shedding Settings ....................368 Serial Port Settings......................369 EnergyWise Settings .......................369 USB-Cascading Configuration Information ..............369 Asset Sensor Settings .....................369 Rack Unit Settings of an Asset Sensor ................370 Blade Extension Strip Settings ..................371 Event Log.........................372...
  • Page 13 Flexible Cord Installation Instructions ..................508 Flexible Cord Selection....................508 Plug Selection........................509 Receptacle Selection.......................509 Derating a Raritan Product ....................509 Wiring of 3-Phase In-Line Monitors .................510 In-Line Monitor Unused Channels ...................510 Step by Step Flexible Cord Installation ................510 In-Line Monitor's Web Interface ....................516 Dashboard Page......................517...
  • Page 14 Contents Appendix A Specifications Maximum Ambient Operating Temperature ................519 Serial RS-232 Port Pinouts......................519 Sensor RJ-45 Port Pinouts ......................519 Feature RJ-45 Port Pinouts .......................520 Appendix B Equipment Setup Worksheet Appendix C Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ..................526 TFTP Requirements........................527 DHCP IPv4 Configuration in Windows..................528 DHCP IPv6 Configuration in Windows..................538...
  • Page 15 Contents USB-Cascaded Device's Position ...................569 Appendix G PX Models with Residual Current Monitoring RCM Current Sensor .........................571 RCM State Sensor ........................572 Compliance with IEC 62020 ......................573 RCM Self-Test ...........................574 Web Interface Operations for RCM ...................574 Checking RCM State and Current ...................574 Setting RCM Current Thresholds ..................576 Scheduling RCM Self-Test ....................576 Disabling or Enabling Front Panel RCM Self-Test ............577...
  • Page 16 Button-Type Locking Outlets ...................643 Unbalanced Current Calculation....................644 Altitude Correction Factors ......................645 Data for BTU Calculation ......................646 Raritan Training Website ......................646 Truncated Data in the Web Interface..................647 Reserving IP Addresses in Windows DHCP Servers ..............647 Sensor Threshold Settings ......................648 Thresholds and Sensor States ..................649 "To Assert"...
  • Page 17 In this Online Help, PX3-3nnn is called PX3-3000, PX3-4nnn is called PX3-4000, and PX3-5nnn is called PX3-5000 for convenience. Note: For information on other PX2 or PX3 models, see their respective online help on the Raritan website's Support page (http://www.raritan.com/support/).
  • Page 18 Chapter 1: Applicable Models Comparison between PX2 and PX3 series: Features Front panel Outlet Number SENSOR Replaceable display latching of USB-A port type controller relays ports LED display RJ-12 PX2 series Character LCD RJ-4 5 PX3 phase I display series Dot-matrix LCD RJ-45 PX3 phase II...
  • Page 19 What's New in the PX User Guide Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
  • Page 20 Chapter 1: What's New in the PX User Guide (on page 186) Adding LDAP Server Settings (on page 207) Marking All Outlets (on page 208) Activating or Deactivating the Load Shedding Mode (on page 220) Setting Thresholds for Total Active Energy or Power (on page 223) Creating Actions (on page 226)
  • Page 21 What's New in the PX User Guide (on page 552) Available SCP Commands (on page 577) Front Panel Operations for RCM (on page 577) LCD Message for RCM Critical State (on page 579) Checking RCM States on Phase II Models (on page 580) Displaying the RCM Current (on page 581)

  • Page 22: Chapter 1 Introduction

    The intended use of the Raritan PX is distribution of power to information technology equipment such as computers and communication equipment where such equipment is typically mounted in an equipment rack located in an information technology equipment room.

  • Page 23: 1U Products

    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 ...

  • Page 24: Chapter 2 Rack-Mounting The Pdu

    Mounting Zero U Models Using Claw-Foot Brackets ........7 Mounting Zero U Models Using Two Rear Buttons........8 Mounting 1U or 2U Models................9 Rackmount Safety Guidelines In Raritan products which require rack mounting, follow these precautions: Operation temperature in a closed rack environment may be ...

  • Page 25: Mounting Zero U Models Using L-Brackets

    Chapter 2: Rack-Mounting the PDU Mounting Zero U Models Using L-Brackets If your PDU has circuit breakers implemented, read Circuit Breaker (on page 3) before mounting it. Orientation Limitation To mount Zero U models using L-brackets: 1. Align the baseplates on the rear of the PX device. 2.

  • Page 26: Mounting Zero U Models Using Button Mount

    Chapter 2: Rack-Mounting the PDU 5. Using rack screws, fasten the PX device to the rack through the L-brackets. Mounting Zero U Models Using Button Mount If your PDU has circuit breakers implemented, read Circuit Breaker (on page 3) before mounting it. Orientation Limitation To mount Zero-U models using button mount: 1.
  • Page 27 Chapter 2: Rack-Mounting the PDU 3. Screw each mounting button in the center of each baseplate. The recommended torque for the button is 1.96 N·m (20 kgf·cm). 4. Align the large mounting buttons with the mounting holes in the cabinet, fixing one in place and adjusting the other. 5.

  • Page 28: Mounting Zero U Models Using Claw-Foot Brackets

    Chapter 2: Rack-Mounting the PDU Mounting Zero U Models Using Claw-Foot Brackets If your PDU has circuit breakers implemented, read Circuit Breaker (on page 3) before mounting it. Orientation Limitation To mount Zero U models using claw-foot brackets: 1. Align the baseplates on the rear of the PX device. 2.

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

    Chapter 2: Rack-Mounting the PDU 5. Using rack screws, fasten the PX device to the rack through the claw-foot brackets. 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 (on page 3) before mounting it.

  • Page 30: Mounting 1U Or 2U Models

    Chapter 2: Rack-Mounting the PDU 3. Screw a button in the screw hole near the bottom. The recommended torque for the button is 1.96 N·m (20 kgf·cm). 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).
  • Page 31 Chapter 2: Rack-Mounting the PDU 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners.

  • Page 32: Chapter 3 Installation And Configuration

    3. Inspect the equipment carefully. If any of the equipment is damaged or missing, contact Raritan's Technical Support Department for assistance. 4. Verify that all circuit breakers on the PX device are set to ON. If not, turn them ON.

  • Page 33: Checking The Branch Circuit Rating

    Chapter 3: Installation and Configuration Note: If necessary, contact Raritan Technical Support for the maximum operating temperature for your model. See Maximum Ambient Operating Temperature (on page 519). 2. Allow sufficient space around the PX device for cabling and outlet connections.
  • Page 34 Chapter 3: Installation and Configuration 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...

  • Page 35: Connecting A Locking Line Cord

    Chapter 3: Installation and Configuration Connecting a Locking Line Cord If your PDU is a PX3 Phase II model, it is shipped with either of the following locking line cords.  A line cord with locking clips: A locking inlet on the PDU is required for this cord.

  • Page 36: Disconnecting A Locking Line Cord

    Chapter 3: Installation and Configuration To connect a cord with slide release buttons: Simply plug the cord's connector into the PDU's inlet. Number Item Slide release buttons For information on removing the locking line cord, see Disconnecting a (on page 15). Locking Line Cord Disconnecting a Locking Line Cord The ways to disconnect a locking line cord vary according to the cord...

  • Page 37: Connecting The Pdu To A Power Source

    Chapter 3: Installation and Configuration To disconnect a line cord with slide release buttons: Push both slide release buttons toward the cord while unplugging this cord. Connecting the PDU to a Power Source 1. Verify that all circuit breakers on the PX device are set to ON. If not, turn them ON.
  • Page 38 HyperTerminal or PuTTY. For an RS-232 connection, you need a null-modem cable with DB9 connectors on both ends (Raritan part number: 254-01-0006-00). Tip: An additional way to initially configure multiple PX devices is to use the TFTP server over a DHCP network. This method helps you save a lot of time when there are a large number of PX devices to configure.

  • Page 39: Connecting The Px To A Computer

    Chapter 3: Installation and Configuration Connecting the PX to a Computer To configure the PX using a computer, it must be connected to the computer with an RS-232 serial interface. PX3 Phase II models (zero U): PX3 Phase I models (zero U): If your computer does not have a serial RS-232 port, use a regular USB cable to connect the PX to the computer for initial configuration.

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

    Note: <n> in the filename of "dominion-serial-setup-<n>.exe" represents the file's version number. There are two ways to install this driver: automatic and manual installation. Automatic driver installation is highly recommended. Note: This file is downloaded from the Raritan PX2 Support Files page (https://www.raritan.com/support/product/px2/px2-support-files). ®...

  • Page 41: Connecting The Px To Your Network

    Chapter 3: Installation and Configuration Note: If the PX enters the disaster recovery mode when the USB serial driver is not installed yet, it may be shown as a 'GPS camera' in the Device Manager on the computer connected to it. In Linux: No additional drivers are required, but you must provide the name of the tty device, which can be found in the output of the "dmesg"...
  • Page 42 Chapter 3: Installation and Configuration Below indicates the ETHERNET port on Zero U models: PX3 Phase II models: PX3 Phase I models: Warning: Accidentally plugging an RS-232 RJ-45 connector into the ETHERNET port can cause permanent damages to the Ethernet hardware.

  • Page 43: Initial Network Configuration Via Cli

    A/B/G/N Raritan USB WIFI A/B/G/N Note: To use the Edimax EW-7722UnD or Raritan USB WIFI wireless LAN adapter to connect to an 802.11n wireless network, the handshake timeout setting must be changed to 500 or greater, or the wireless connection will fail.
  • Page 44 4. The PX prompts you to log in. Both user name and password are case sensitive. a. Username: admin b. Password: raritan (or a new password if you have changed it). 5. If prompted to change the default password, follow onscreen instructions to type your new password.
  • Page 45 Chapter 3: Installation and Configuration To set Use this command SSID network wireless SSID <ssid> <ssid> = SSID string If necessary, configure more wireless parameters shown in the following table. To set Use this command BSSID network wireless BSSID <bssid> <bssid>...
  • Page 46 Chapter 3: Installation and Configuration To set Use this command EAP CA network wireless certificate 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 CA certificate does NOT include the first line containing "BEGIN CERTIFICATE"...
  • Page 47 Chapter 3: Installation and Configuration To set Use this command IP address network ip returned by dnsResolverPreference the DNS <resolver> server <resolver> = preferV4 or preferV6 e. After enabling the IPv4 or IPv6 protocol in the earlier step, configure the IPv4 or IPv6 network parameters. To set Use this command IPv4...
  • Page 48 Chapter 3: Installation and Configuration  For static IP configuration, configure these parameters. To set Use this command Static IPv4 or network <version> ipAddress <ip IPv6 address address> <ip address> = static IP address IPv4 subnet network ipv4 subnetMask mask <netmask>...

  • Page 49: Cascading The Px Via Usb

    The IP address configured may take seconds to take effect. Cascading the PX via USB Up to eight (8) Raritan devices are supported as part of a daisy chain. This daisy chain feature permits multiple PX devices to be cascaded using USB cables, sharing the Ethernet connectivity accordingly.
  • Page 50 Chapter 3: Installation and Configuration When the port forwarding mode over wireless LAN is intended, a  Raritan product with two USB-A ports must be the master device, such as PX3 or PX3TS. 3. Connect the master device to the LAN via: A standard network patch cable (CAT5e or higher) if the bridging ...
  • Page 51 Chapter 3: Installation and Configuration 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 113).

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

    Chapter 3: Installation and Configuration Tip: The USB-cascading configuration can be a combination of diverse Raritan products that support the USB-cascading feature, including PX2, PX3, PX3TS, EMX and BCM. For details, see the USB-Cascading Solution Guide, which is available on the PX2 web page (http://www.raritan.com/support/product/px2/).
  • Page 53 Chapter 3: Installation and Configuration 3. Plug the power cord into the outlet, and press the clip toward the power cord until it holds the cord firmly. The clip's central part holding the plug should face downwards toward the ground, like an inverted "U".

  • Page 54: Chapter 4 Connecting External Equipment (Optional)

    Connecting External Equipment Chapter 4 (Optional) More features are available in addition to remotely monitoring and managing the PX if you connect Raritan's or third-party external equipment to your PX. In This Chapter Connecting Environmental Sensor Packages .........33 Before Connecting Equipment to Feature Port (PX3 Phase I Models) ...42 Connecting the Asset Management Sensor..........43...

  • Page 55: Dpx Sensor Packages

    Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of the PX3. To directly connect a differential air pressure sensor: 1. Connect a Raritan-provided phone cable to the IN port of a differential air pressure sensor. 2. Get an RJ-12 to RJ-45 adapter. Connect the adapter's RJ-12 connector to the other end of the phone cable.
  • Page 56 To connect DPX sensor packages via an optional sensor hub: 1. Connect a Raritan sensor hub to the PX device. a. Plug one end of the Raritan-provided phone cable (4-wire, 6-pin, RJ-12) into the IN port (Port 1) of the hub.
  • Page 57 Chapter 4: Connecting External Equipment (Optional) Using a Raritan Y Cable A Raritan Y cable doubles the number of connected environmental sensors per SENSOR port. It supports DPX sensor packages only. Do NOT connect DPX2 or DX sensor packages. To connect DPX sensor packages via a Raritan Y cable: 1.
  • Page 58 Chapter 4: Connecting External Equipment (Optional) Supported Maximum DPX Sensor Distances A maximum connection distance of 98' (30 m) is supported when connecting the following DPX sensor packages to the PX. This maximum includes the 16' (5 m) sensor cable length: ...

  • Page 59: Dpx2 Sensor Packages

    RJ-12 connector and one to three head connectors. You need to manually connect DPX2 sensors to the sensor cable. For more information on DPX2 sensor packages, access the Environmental Sensors Guide or Online Help on Raritan website's Support Files page (https://www.raritan.com/support/product/px2/px2-support-files). Item...
  • Page 60 Chapter 4: Connecting External Equipment (Optional) The following procedure illustrates a DPX2 sensor cable with three head connectors. Your sensor cable may have fewer head connectors. Warning: If there are free head connectors between a DPX2 sensor cable's RJ-12 connector and the final attached DPX2 sensor, the sensors following the free head connector(s) on the same cable do NOT work properly.

  • Page 61: Dx Sensor Packages

    Most DX sensor packages contain terminals for connecting detectors or actuators. For information on connecting actuators or detectors to DX terminals, access the Environmental Sensors Guide or Online Help on Raritan website's PX2 Support Files page (https://www.raritan.com/support/product/px2/px2-support-files). You can cascade up to 12 DX sensor packages.
  • Page 62 Chapter 4: Connecting External Equipment (Optional) a. Plug one end of the cable into the remaining RJ-45 port on the prior DX package. b. Plug the other end into either RJ-45 port on an additional DX package. Repeat the same steps to cascade more DX packages. Exception: You CANNOT cascade DX-PD2C5 sensor packages.

  • Page 63: Before Connecting Equipment To Feature Port (Px3 Phase I Models)

    Chapter 4: Connecting External Equipment (Optional) When connecting a DPX2 sensor package containing two DPX2 sensors: A maximum of ten (10) DX sensor packages can be cascaded because 12-2=10. When connecting a DPX2 sensor package containing one DPX2 sensor: A maximum of eleven (11) DX sensor packages can be cascaded because 12-1=11.

  • Page 64: Connecting The Asset Management Sensor

    ID and positioning information to the PX.  Raritan asset tags: An asset tag is adhered to an IT device. The asset tag uses an electronic ID to identify and locate the device. Warning: The PX3 does NOT support simultaneous connection of both DX-PD2C5 and asset management sensor(s) so do NOT connect both of them to the PX3 device.

  • Page 65: Combining Asset Sensors

    The difference between the master and slave asset sensors is that the master asset sensor has an RJ-45 connector while the slave does not. The following diagram illustrates some asset sensors. Note that Raritan provides more types of asset sensors than the diagram.
  • Page 66 Chapter 4: Connecting External Equipment (Optional) Make sure that the U-shaped sheet metal adjacent to the male  DIN connector is inserted into the rear slot of the master asset sensor. Screw up the U-shaped sheet metal to reinforce the connection.

  • Page 67: Connecting Asset Sensors To The Px

    Chapter 4: Connecting External Equipment (Optional) Connecting Asset Sensors to the PX 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 management sensor at the other.
  • Page 68 Chapter 4: Connecting External Equipment (Optional) The PX device supplies power to the asset sensor assembly through the network cable. All LEDs on the asset sensor assembly may cycle through different colors during the power-on process if the asset sensor's firmware is being upgraded by the PX device.

  • Page 69: Connecting Blade Extension Strips

    For blade servers, which are contained in a single chassis, you can use a blade extension strip to track individual blade servers. Raritan's blade extension strip functions similar to a Raritan asset sensor but requires a tag connector cable for connecting to a tag port on the regular or composite asset sensor.
  • Page 70 Chapter 4: Connecting External Equipment (Optional) Tag ports Cable socket(s) for connecting the tag connector cable Note: Each tag port on the blade extension strip is labeled a number, which is displayed as the slot number in the PX device's web interface. To install a blade extension strip: 1.
  • Page 71 Chapter 4: Connecting External Equipment (Optional) a. Affix the adhesive part of the asset tag to one side of a blade server through the tag's tape. b. Plug the tag connector of the asset tag into the tag port on the blade extension strip.

  • Page 72: Connecting Composite Asset Sensors (Ams-Mx-Z)

    Chapter 4: Connecting External Equipment (Optional) Connecting Composite Asset Sensors (AMS-Mx-Z) A composite asset sensor is named AMS-Mx-Z, where x is a number, such as AMS-M2-Z or AMS-M3-Z. It is a type of asset sensor that functions the same as regular MASTER asset sensors except for the following differences: ...
  • Page 73 The maximum cable length between composite asset sensors is 2 meters.  The maximum number of composite asset sensors that can be daisy chained vary according to the Raritan device. Raritan devices Maximum sensors per chain EMX2-111, Up to 4 composite asset sensors...

  • Page 74: Connecting A Logitech Webcam

    Logitech QuickCam Communicate MP, Model 960-000240  Logitech C200, C210, C270 and C920 Other UVC-compliant webcams may work. However, Raritan has neither tested them nor claimed that they will work properly. More information about the scores of UVC-compliant webcams can be found at http://www.ideasonboard.org/uvc...

  • Page 75: Connecting A Gsm Modem

     NETCOMM IG6000 Industrial Grade SmartModem  US Robotics 56K modem The PX may also support other analog modems which Raritan did not test. Note that the PX does NOT support dial-out or dial-back operations via the modem. To connect an analog modem:...

  • Page 76: Connecting An External Beeper

    Chapter 4: Connecting External Equipment (Optional) 2. Plug the modem's RS-232 cable into the serial port labeled CONSOLE / MODEM on the PX. You need to enable the modem dial-in support to take advantage of this feature, see (on page 141). Configuring the Serial Port Connecting an External Beeper The PX supports the use of an external beeper for audio alarms.

  • Page 77: Chapter 5 Using The Pdu

    Using the PDU Chapter 5 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.

  • Page 78: Inlet

    Chapter 5: Using the PDU Inlet Most of PX3 PDUs are shipped with a locking line cord, which is ready to be plugged into the PDU's inlet and an appropriate receptacle for electricity reception. Such devices cannot be rewired by the user. A locking line cord helps secure the cord connection.

  • Page 79: Outlets

    These models are NOT outlet-switching capable so all outlets are always in the ON state. Outlet LEDs are not available. PX3-4000 Series These PDUs are NOT outlet-switching capable models so all outlets are always in the ON state. A small LED adjacent to each outlet indicates the outlet state. Outlet LEDs always light red, indicating that the outlet power is ON.

  • Page 80: Connection Ports

    Chapter 5: Using the PDU LED state Outlet status What it means circuitry's power supply is broken. LIVE power. The outlet is on and power is ON and LIVE available. The current flowing through the outlet is greater Red flashing ON and LIVE than the upper warning (non-critical) threshold.
  • Page 81 ® This is a "host" port, which is powered, per USB 2.0 specifications. FEATURE Connection to some Raritan access products (such as Dominion KX II) through the use of a power CIM, OR -- Connection to a Schroff LHX-20, SHX-30 or LHX-40 device through an ®...

  • Page 82: Dot-Matrix Lcd Display

    Chapter 5: Using the PDU Port Used for... *SENSOR Connection to Raritan's environmental sensor packages. A sensor hub is required if you want to connect more than one DPX sensor package. ETHERNET Connecting the PX device to your company's network: Connect a standard Cat5e/6 UTP cable to this port and connect the other end to your network.
  • Page 83 Chapter 5: Using the PDU Automatic and Manual Modes After powering on or resetting the PX, the front panel LCD display first shows the Raritan logo and company name, and then enters the automatic mode. Automatic mode: In this mode, the LCD display cycles through the inlet information.
  • Page 84 Chapter 5: Using the PDU Main Menu After pressing to enter the manual mode, the Main Menu appears. Depending on the model you purchased, the Main Menu contains 6 to 9 menu commands. Control buttons that can be used and the system time are shown at the bottom of the LCD display.
  • Page 85 Outlets (on page 71). Outlets Shows the information of connected Raritan environmental sensors or actuators, such as the temperature sensor. You can even turn on or off a connected actuator with this command. Peripherals (on page 75).
  • Page 86 Chapter 5: Using the PDU Control Buttons Use the control buttons to navigate to the menu in the manual mode. Button Function Description Move the selection up, or go to the previous page. Down Move the selection down, or go to the next page. Confirm the selection.
  • Page 87 Chapter 5: Using the PDU 2. If any sensor has entered an alarmed, warning or critical state, a list similar to the following is displayed. Alerted sensors are highlighted in either red or yellow. See The Yellow- or Red-Highlighted (on page 105) for color meanings. Sensors Number Description...
  • Page 88 Chapter 5: Using the PDU Depending on the model you purchased, the "PDU" menu command may contain one or all of the following information.  Internal beeper states - On or Off  Total active power of the PX - available on a multi-inlet model only ...
  • Page 89 Chapter 5: Using the PDU 3. If your PX has more than one inlet, press to show the information of total active power (W) and total active energy (Wh). 4. To return to the Main Menu, press Inlet An inlet's information is separated into two pages. Page numbers are indicated in the top-right corner of the LCD display.
  • Page 90 Chapter 5: Using the PDU 2. The first page shows the inlet's active power (W), apparent power (VA), power factor (PF), and active energy (Wh) from top to down. 3. To go to the next page, press For a single-phase model, the second page shows the inlet's ...
  • Page 91 Chapter 5: Using the PDU OCPs If your model has more overcurrent protectors (OCPs) than the LCD display can show at a time, a page number appears in the top-right corner of the display. Otherwise, no page numbers are available. To show the overcurrent protector information: 1.
  • Page 92 Chapter 5: Using the PDU Outlets With the front panel display, you can do the following for outlets:  Show each outlet's information.  Turn on, off or power cycle an individual outlet if your PX is outlet-switching capable. To do this, you must first enable the front panel outlet control function.
  • Page 93 Chapter 5: Using the PDU 4. The LCD display shows the selected outlet's power state, active power (W), apparent power (VA), power factor (PF) and active energy (Wh) from top to down. Note: In the following diagrams, N represents the selected outlet's number.
  • Page 94 Chapter 5: Using the PDU Power Control This section applies to outlet-switching capable models only. The front panel outlet control must be enabled for performing this power control function. The default is to disable this function. See Enabling (on page 210). Front Panel Outlet Switching Available options for power control vary based on the power state of the selected outlet.
  • Page 95 Chapter 5: Using the PDU 4. The LCD display shows the selected outlet's information. For details, (on page 71). Showing an Outlet's Information Note: In the following diagrams, N represents the selected outlet's number. 5. Press to go to the power control page. A submenu similar to the following diagram appears.
  • Page 96 Main Menu is shown. Peripherals If there are no Raritan environmental sensor packages connected to your PX, the LCD display shows the message "No managed devices" for the "Peripherals" menu command. If any connected sensor is highlighted in red or yellow, that sensor has entered an alarmed, warning or critical state.
  • Page 97 Chapter 5: Using the PDU If the desired sensor or actuator is not visible, press  to scroll up or down. Page numbers are indicated in the top-right corner of the LCD display. Number Description Sensor or actuator names. For a numeric sensor, its reading is displayed right below the sensor name. For a discrete sensor, no reading is displayed.
  • Page 98 Chapter 5: Using the PDU 3. To view an environmental sensor or actuator's detailed information, press to select that sensor, and press . A screen similar to the following is shown. Number Description The ID number assigned to this sensor or actuator. ...
  • Page 99 Chapter 5: Using the PDU Number Description X, Y, and Z coordinates which you specify for this sensor or actuator. See (on page 283). Configuring Environmental Sensors or Actuators 4. Press to return to the sensor list. 5. To return to the Main Menu, press To switch on or off an actuator: 1.
  • Page 100 4. Verify that the actuator status shown on the LCD display has been changed. Assets If there are no Raritan asset management sensors connected, the LCD display shows the message "Asset strip not connected" for the "Assets" menu command. After connecting asset sensors, only the information of the rack units where asset tags have been detected are shown on the LCD display.
  • Page 101 Chapter 5: Using the PDU 2. The LCD display shows a list of rack unit numbers as well as their information similar to the following diagram. Number Description Three pieces of information are displayed from left to right.  A color box: This represents the asset sensor's LED color when an asset tag is detected.
  • Page 102 Chapter 5: Using the PDU Device Info The display shows the PX device's information, network and IPv4 settings through various pages. Page numbers are indicated in the top-right corner of the LCD display. To show the device information: 1. Press to select "Device Info"...
  • Page 103 Chapter 5: Using the PDU 3. To go to the next page which shows the networking mode and USB-cascading status, press Number Description Networking information, including:  Network mode: Wired or Wireless.  MAC address of the PX.  If the networking mode is wireless, the following additional information is available: - SSID - MAC address of the access point being used...
  • Page 104 Chapter 5: Using the PDU 4. To go to the next page which shows IPv4 settings, press Number Description IPv4 network information, including:  Network configuration: DHCP or Static. Static represents Static IP.  IP address.  Netmask.  Gateway. DNS server addresses, including the primary and secondary ones.
  • Page 105 Chapter 5: Using the PDU  Network configuration: Automatic or Static.  IP address(es).  DNS server address(es). If you do not enable IPv6 settings, the following message is displayed instead. 6. To return to the Main Menu, press Showing the Firmware Upgrade Progress When upgrading the PX, the firmware upgrade progress will be displayed as a percentage on the LCD display, similar to the following diagram.

  • Page 106: Reset Button

    Chapter 5: Using the PDU In the end, a message appears, indicating whether the firmware upgrade is successful or fails. Reset Button The reset button is located inside the small hole near the display panel on the PDU. The PX device can be reset to its factory default values using this button when a serial connection is available.

  • Page 107: Circuit Breakers

    Chapter 5: Using the PDU Circuit Breakers PX models rated over 20A (North American) or 16A (international) contain overcurrent protectors for outlets, which are usually branch circuit breakers. These circuit breakers automatically trip (disconnect power) when the current flowing through the circuit breaker exceeds its rating.

  • Page 108: Resetting The Handle-Type Circuit Breaker

    Chapter 5: Using the PDU Resetting the Handle-Type Circuit Breaker Your handle-type circuit breakers may look slightly different from the images shown in this section, but the reset procedure remains the same. To reset the handle-type breakers: 1. Lift the hinged cover over the breaker. 2.

  • Page 109: Fuse

    Chapter 5: Using the PDU Fuse Some PX devices may be implemented with fuses instead of circuit breakers. A fuse blows to protect associated outlets if it detects the overload. If your PDU uses fuses, you must replace it with a new one when it blows or malfunctions.

  • Page 110: Fuse Replacement On 1U Models

    Chapter 5: Using the PDU 3. Push the cover of the fuse holder to expose the fuse. 4. Take the fuse out of the holder. 5. Insert a new fuse into the holder. There is no orientation limit for fuse insertion.
  • Page 111 Chapter 5: Using the PDU To replace a fuse on the 1U PDUs: 1. Disconnect the PDU's power cord from the power source. 2. Remove the desired fuse from the PDU's fuse carrier using a flat screwdriver. a. Rotate the fuse knob counterclockwise until its slot is inclined to 45 degrees.

  • Page 112: Beeper

    PDU. If the controller is broken, you can simply send the controller back to Raritan for repair, or purchase a new controller from Raritan. 1U and 2U models do NOT support this feature.
  • Page 113 Chapter 5: Using the PDU Note: Loosen the screws instead of removing them. 3. Disconnect the PDU's controller cable from the controller. 4. Get a new PX3 controller and install it back into the PDU in the reverse order.

  • Page 114: Chapter 6 Using The Web Interface

    Using the Web Interface Chapter 6 This chapter explains how to use the web interface to administer a PX. In This Chapter Supported Web Browsers................93 Logging in to the Web Interface ..............94 Logout......................97 Introduction to the Web Interface ............98 Viewing the Dashboard .................109 Device Management................111 User Management .................154 Setting Up Roles..................160...

  • Page 115: 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). You are then prompted to change the password for security purposes.
  • Page 116 Chapter 6: Using the Web Interface Note: Both the user name and password are case sensitive. If needed, click Clear to clear either the inputs or any error message that appears. 4. If a security agreement is displayed on the Login page, accept it. To select the agreement checkbox using the keyboard, press the Space bar.

  • Page 117: Changing Your Password

    Chapter 6: Using the Web Interface Changing Your Password Normal users can change their own passwords if they have the Change Own Password permission. See (on page 160). Setting Up Roles If you are the administrator (admin), the PX web interface automatically prompts you to change the password if this is your first time to log in to the PX.

  • Page 118: Logout

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

  • Page 119: Introduction To The Web Interface

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

  • Page 120: Menus

    Chapter 6: Using the Web Interface Menus There is a menu bar across the top of the page. You can click any menu to select the desired menu item from the drop-down list. Four menus are available for managing different tasks or showing information.
  • Page 121 Chapter 6: Using the Web Interface 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 ...
  • Page 122 Chapter 6: Using the Web Interface 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.

  • Page 123: Setup Button

    Chapter 6: Using the Web Interface Collapsing the Tree You can collapse the whole tree structure or a specific component group to hide all or partial tree items. To collapse the whole tree:  Click the black, gradient arrow prior to the root folder icon, or double-click the folder.

  • Page 124: Add Page Icon

    Chapter 6: Using the Web Interface This is the name assigned to the PX device. The default is "my PX." (on page 117). Naming the PDU 2. IP address: The numbers enclosed in parentheses is the IP address assigned to the PX device.

  • Page 125: Logout Button

    Chapter 6: Using the Web Interface 2. Click a tree item whose data page you want to open. The data of the selected tree item is then displayed on the blank page. 3. To open more data pages, repeat the above steps. All tabs representing opened pages are shown across the top of the page.
  • Page 126 Chapter 6: Using the Web Interface Warning Icon If the value you entered in a specific field is invalid, a red warning icon appears to the right and the field in question is surrounded by a red frame as shown in this illustration. When this occurs, position your mouse pointer over the warning icon to view the reason and modify the entered value accordingly.
  • Page 127 Chapter 6: Using the Web Interface 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 lower warning threshold.
  • Page 128 Chapter 6: Using the Web Interface Changing the Column You can hide some columns of a list or table, or adjust a specific column's width. To change displayed columns: 1. Hover your mouse pointer over any column header. A black triangle appears to the far right of this column header.
  • Page 129 Chapter 6: Using the Web Interface Resizing a Dialog Most dialogs cannot be resized except for a few ones (such as the Event Log dialog), which can be resized to display more information at a time. To resize a dialog: 1.

  • Page 130: Viewing The Dashboard

    Chapter 6: Using the Web Interface 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(s), outlets, circuit breakers and alerted sensors.

  • Page 131: Alarms List

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

  • Page 132: Device Management

    Chapter 6: Using the Web Interface 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.

  • Page 133: Displaying Pdu Information

    Chapter 6: Using the Web Interface 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 PDU-specific information: 1. Choose Maintenance > Device Information. The Device Information dialog appears.
  • Page 134 For information on how to cascade devices using USB cables, see (on page 28). Cascading the PX via USB Note: For more information on the USB-cascading configuration, see the USB-Cascading Solution Guide, which is available from Raritan website's PX2 Support Files page (https://www.raritan.com/support/product/px2/px2-support-files).
  • Page 135 Chapter 6: Using the Web Interface 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.
  • Page 136 Chapter 6: Using the Web Interface 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 Device Connected field.
  • Page 137 Chapter 6: Using the Web Interface 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 138: Naming The Pdu

    Chapter 6: Using the Web Interface 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 is my PX.
  • Page 139 Chapter 6: Using the Web Interface 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 (on page 20).
  • Page 140 Chapter 6: Using the Web Interface Wireless Network Settings Wireless SSID, PSK and BSSID parameters were set during the installation and configuration process. You can change them via the web interface. Note for USB-cascading configuration: Port forwarding mode over wireless LAN is supported as of release 3.1.0. You must upgrade all devices in the chain to version 3.1.0 or later if wireless networking is preferred.
  • Page 141 Chapter 6: Using the Web Interface 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 authentication to databases that support MSCHAPv2.
  • Page 142 Chapter 6: Using the Web Interface Modifying Network Settings The PX was configured for network connectivity during the installation and configuration process. See (on page 16). If Configuring the PX necessary, you can modify any network settings using the web interface. Selecting the Internet Protocol The PX device supports two types of Internet protocols -- IPv4 and IPv6.
  • Page 143 Chapter 6: Using the Web Interface Modifying IPv4 Settings You must enable the IPv4 protocol before you can modify the IPv4 network settings. See (on page 121). Selecting the Internet Protocol To modify IPv4 settings: 1. Choose Device Settings > Network. The Network Configuration dialog appears.
  • Page 144 Chapter 6: Using the Web Interface Option Description  Destination: IP address of the other subnet and subnet mask using the format "IP address/subnet mask."  Next Hop: IP address of the next hop router. (on page 125) for illustrations. Static Route Examples 4.
  • Page 145 Chapter 6: Using the Web Interface 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 communicate with the other subnet.
  • Page 146 Chapter 6: Using the Web Interface 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.
  • Page 147 Chapter 6: Using the Web Interface 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 ...

  • Page 148: Modifying Network Service Settings

    In addition, the PX also supports the SNMP and Modbus/TCP protocols. Changing HTTP(S) Settings Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail...
  • Page 149 Chapter 6: Using the Web Interface 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.
  • Page 150 Chapter 6: Using the Web Interface 3. To enable the SSH application, select the Enable SSH Access checkbox. To disable it, deselect the checkbox. 4. To select a different authentication method, select one of the checkboxes. Password authentication only: Enables the password-based login ...
  • Page 151 Chapter 6: Using the Web Interface 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 destination(s) if the built-in "System SNMP Notification Rule"...
  • Page 152 Chapter 6: Using the Web Interface Tip: You can permit or disallow a user to access the PX via the SNMP v3 protocol. See Configuring Users for Encrypted SNMP (on page 331). 4. Enter the MIB-II system group information, if applicable: a.
  • Page 153 Chapter 6: Using the Web Interface Changing Modbus/TCP Settings You can enable or disable the Modbus/TCP access to the PX or the read-only mode, or change the default TCP port for the Modbus service. To change the Modbus service settings: 1.
  • Page 154 Chapter 6: Using the Web Interface 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 (multicast DNS). The advertised services are discovered by clients that have implemented DNS-SD and mDNS. The advertised services include the following: ...

  • Page 155: Setting The Date And Time

    Chapter 6: Using the Web Interface Setting the Date and Time Set the internal clock on the PX device manually, or link to a Network Time Protocol (NTP) server and let it set the date and time for the PX. To set the date and time: 1.
  • Page 156 PX has problems synchronizing with a Windows NTP server, see (on page 137). Windows NTP Server Synchronization Solution Note: If you are using Raritan's Power IQ to manage the PX, you must configure Power IQ and the PX to have the same date/time or NTP settings.
  • Page 157 Chapter 6: Using the Web Interface Press Ctrl+Up arrow or Ctrl+Down arrow to switch between  years. Click , which is adjacent to the year, to show a list of years  and months. Select the desired year from the list to the right and click OK.
  • Page 158 Chapter 6: Using the Web Interface 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 server by the PX.

  • Page 159: Setting The Lcd Display's Default View

    Chapter 6: Using the Web Interface Setting the LCD Display's Default View This setting is only available on PX3 phase II models except for PX3-3000 series, which does NOT provide inlet sensor information. After powering on or resetting a PX, the dot-matrix LCD display enters the automatic mode by default, which cycles through the inlet information and, if available, overcurrent protector information.

  • Page 160: Configuring The Feature Port

     Raritan asset management sensors (asset sensors). See (on page 43). Connecting the Asset Management Sensor  Raritan serial access products, including Dominion KSX II or SX. (on page 630). Dominion KSX II or SX Configuration  External beeper. See...
  • Page 161 Beeper Power CIM Select this type when connecting one of the following Raritan products:  Raritan power CIM, D2CIM-PWR. This CIM is used to connect the PX to the Raritan digital KVM switch, Dominion KX II.  Dominion KSX II ...

  • Page 162: Configuring The Serial Port

    115200 bps. The PX supports the use of one of the following devices via the serial interface:  A computer or a Raritan's KVM product for console management.  An analog modem for remote dial-in and access to the CLI. ...

  • Page 163: Setting The Cascading Mode

    Chapter 6: Using the Web Interface 3. Select 'Use custom SMS center number' if a custom SMS will be used. 4. Enter the SMS center number in the SMS Center field. 5. Click Advanced Information to show information. 6. Enter the number of the recipient's phone in the Recipients Phone field, then click Send SMS Test to send a test SMS message.
  • Page 164 Chapter 6: Using the Web Interface 6. If selecting Port Forwarding, a list of port numbers for diverse networking protocols will be available on the "Protocol to Port Mapping" tab of each cascaded device. Return to the same dialog and click the "Protocol to Port Mapping" tab to view the master device's port numbers.
  • Page 165 Chapter 6: Using the Web Interface Protocols TELNET SNMP MODBUS  XX is a two-digit number representing the device position as shown below: Position Master device Slave 1 Slave 2 Slave 3 Slave 4 Slave 5 Slave 6 Slave 7 For example, to access the Slave 4 device via Modbus/TCP, the port number is 50604.
  • Page 166  Slave device: Assign proper 5NNXX port numbers. Assumption: The Port Forwarding mode is applied to a USB-cascading configuration comprising three Raritan products. The IP address is 192.168.84.77. Master device: Position code for the master device is 00 so each port number is 5NN00 as shown below.
  • Page 167 Chapter 6: Using the Web Interface  To access the master device via SSH, the command is: ssh -p 22 192.168.84.77 Slave 1 device: Position code for Slave 1 is 01 so each port number is 5NN01 as shown below. Protocols Port numbers HTTPS...

  • Page 168: Setting Data Logging

    Chapter 6: Using the Web Interface  To access Slave 2 via HTTP, the IP address is: http://192.168.84.77:50102/  To access Slave 2 via SSH, the command is: ssh -p 50202 192.168.84.77 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.

  • Page 169: Configuring Smtp Settings

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

  • Page 170: Configuring Data Push Settings

    10. Click OK. Configuring Data Push Settings If any Raritan asset sensors have been connected to PX, you can push the asset sensor data to a remote server for data synchronization. The data will be sent in JSON format using HTTP POST requests. You need to set up the destination and authentication for data push on the PX.

  • Page 171: Specifying The Device Altitude

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

  • Page 172: Rebooting The Px Device

    Chapter 6: Using the Web Interface For meters (m), the value ranges between 0 and 3000.  For feet (ft), the value ranges between 0 and 9842.  4. Click OK. 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.

  • Page 173: Monitoring Total Active Energy Or Power

    Chapter 6: Using the Web Interface 2. Click Reset All Active Energy Counters in the Settings section. 3. Click Yes on the confirmation message. Now all 'Active Energy' readings on the PX are reset to 0 (zero) Wh. Tip: You can also reset the active energy readings of an individual inlet. Resetting Inlet Active Energy Readings (on page 213).

  • Page 174: Checking The Internal Beeper State

    Chapter 6: Using the Web Interface 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 91). You can remotely check its state. To check the PX beeper's state: 1.

  • Page 175: User Management

    Chapter 6: Using the Web Interface 5. In the Port field, type a User Datagram Protocol (UDP) port number for communications in the Cisco EnergyWise domain. The port ranges from 1 to 65535. Default is 43440. 6. In the "Polling interval" field, type a polling interval to determine how often the PX is queried in the Cisco EnergyWise domain.
  • Page 176 Chapter 6: Using the Web Interface Field Type this... It is case sensitive.  Spaces are NOT permitted  Full Name The user's first and last names. Password, The password the user enters to log in. Type it first in the Password field and then again in the Confirm Password Confirm Password field.
  • Page 177 Chapter 6: Using the Web Interface Field Description AuthPriv: Authentication and privacy. This  is the default. Use Password as This checkbox is configurable only if AuthNoPriv Authentication or AuthPriv is selected. Pass Phrase When the checkbox is selected, the authentication pass phrase is identical to the user's password.
  • Page 178 Chapter 6: Using the Web Interface 7. Click the SSH tab to enter the public key if the public key authentication for the SSH service is enabled. See Changing SSH (on page 128). Settings a. Open the SSH public key with a text editor. b.

  • Page 179: Modifying A User Profile

    Chapter 6: Using the Web Interface Modifying a User Profile You can change any user profile's information except for the user name. To modify a user profile: 1. Choose User Management > Users. The Manage Users dialog appears. 2. Select the user by clicking it. 3.

  • Page 180: Changing The User List View

    Chapter 6: Using the Web Interface Changing the User List View You may change the number of displayed columns or re-sort the list for better viewing the data. See (on page Changing the View of a List 106). Setting Up Your Preferred Measurement Units The measurement units used in your PX user interfaces can be changed according to your own preferences regardless of the permissions you have.

  • Page 181: Setting Up Roles

    - Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration - Change Own Password - Switch Outlet (all outlets) Note: PX3-3000 and PX3-4000 series are NOT outlet-switching capable so the "Switch Outlet" permission is not available. The Operator role is assigned to a newly created user profile by default.

  • Page 182: Modifying A Role

    Chapter 6: Using the Web Interface 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 list shows all outlets for you to determine which outlets this role can control.

  • Page 183: Deleting A Role

    Chapter 6: Using the Web Interface 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 the Switch Outlet permission is selected, the Arguments list shows all outlets for you to determine which outlets this role can control.

  • Page 184: Changing The Role List View

    Chapter 6: Using the Web Interface Changing the Role List View You may re-sort the list for better viewing the data. See Changing the (on page 106). View of a List Access Security Control The PX provides tools to control access. You can enable the internal firewall, create firewall rules, and create login limitations.
  • Page 185 Chapter 6: Using the Web Interface Enabling the Firewall The firewall rules, if any, take effect only after the firewall is enabled. To enable the PX firewall: 1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears. 2.
  • Page 186 Chapter 6: Using the Web Interface c. Locate the Default Policy field in the Inbound Rules section. d. The default policy is shown in the Default Policy field. To change it, select a different policy from the drop-down list.  Accept: Accepts traffic from all IPv6 addresses. ...
  • Page 187 Chapter 6: Using the Web Interface 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.
  • Page 188 Chapter 6: Using the Web Interface Action Procedure Insert a rule between two Select the rule above which you want to insert a new rule. For  existing rules example, to insert a rule between rules #3 and #4, select #4. Click Insert.
  • Page 189 Chapter 6: Using the Web Interface 6. When finished, the rules appear in the Configure IP Access Control Settings dialog. 7. Click OK. The rules are applied. Editing Firewall Rules When an existing firewall rule requires updates of IP address range and/or policy, modify them accordingly.
  • Page 190 Chapter 6: Using the Web Interface 2. To modify the IPv4 firewall rules, click the IPv4 tab. To modify the IPv6 firewall rules, click the IPv6 tab. 3. Ensure the Enable IPv4 Access Control checkbox is selected on the IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.

  • Page 191: Setting Up User Login Controls

    Chapter 6: Using the Web Interface 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 highlight multiple ones.
  • Page 192 Chapter 6: Using the Web Interface 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 ...
  • Page 193 Chapter 6: Using the Web Interface 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, and special characters, such as @ or &.
  • Page 194 Chapter 6: Using the Web Interface 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.

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

    Chapter 6: Using the Web Interface If the Restricted Service Agreement feature is enabled, the Restricted Service Agreement is displayed when any user logs in to the PX. Do either of the following, or you cannot successfully log in to the PX: ...
  • Page 196 Chapter 6: Using the Web Interface Changing the Default Policy The default policy is to accept all traffic from all IP addresses regardless of the role applied to the user. To change the default policy: 1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
  • Page 197 Chapter 6: Using the Web Interface 3. Ensure the "Enable Role Based Access Control for IPv4" checkbox is selected on the IPv4 tab, or the "Enable Role Based Access Control for IPv6" checkbox is selected on the IPv6 tab. 4. Create specific rules: Action Do this...
  • Page 198 Chapter 6: Using the Web Interface 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 access control rule: 1.

  • Page 199: Setting Up A Tls Certificate

    7. Click OK. Setting Up a TLS Certificate Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail...

  • Page 200: Certificate Signing Request

    Chapter 6: Using the Web Interface 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 the information in the CSR, it provides you with a certificate, which you must install on the PX device.
  • Page 201 Chapter 6: Using the Web Interface 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 Organization, Organizational Unit and Email Address fields.

  • Page 202: Creating A Self-Signed Certificate

    Chapter 6: Using the Web Interface 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 Certificate dialog appears.
  • Page 203 Chapter 6: Using the Web Interface 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 are creating a self-signed certificate.

  • Page 204: Installing Existing Key And Certificate Files

    Chapter 6: Using the Web Interface 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 certificate that is part of a chain of certificates, each part of the chain is signed during the validation process.

  • Page 205: Setting Up External Authentication

    Only users who have the "Change Authentication Settings" permission can set up or modify the authentication settings. Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
  • Page 206 Chapter 6: Using the Web Interface 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, you need to check: The IP address or hostname of the LDAP server ...

  • Page 207: Adding Authentication Servers

    Chapter 6: Using the Web Interface 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 authentication, enable LDAP authentication and enter the information you have gathered for any LDAP/LDAPS server.
  • Page 208 Chapter 6: Using the Web Interface 8. SSL Port - The default is 636. Either use the default port or specify another port. This field is enabled when the "LDAP over SSL" checkbox is selected. 9. Enable verification of LDAP Server Certificate - Select this checkbox if you would like the PX to verify the validity of the selected LDAP server certificate.
  • Page 209 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 server administrator for the appropriate values to enter into these fields.
  • Page 210 Chapter 6: Using the Web Interface 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).

  • Page 211: Sorting The Access Order

    Chapter 6: Using the Web Interface 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 information about the LDAP configuration using Microsoft Active Directory, see...

  • Page 212: Editing Authentication Server Settings

    Chapter 6: Using the Web Interface 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 external authentication configuration: 1.

  • Page 213: Enabling External And Local Authentication Services

    Chapter 6: Using the Web Interface 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 are enabled, the PX follows these rules for authentication: ...
  • Page 214 Chapter 6: Using the Web Interface Outlet Relay Behavior in Latching and Non-Latching Mode Non-Latching Mode:  Relay always opens when power is lost. This insures all relays are open when power is applied to the PDU.  Always select this mode if the combined in-rush current of the devices connected to the PDU trip circuit breakers when power is applied to the PDU.

  • Page 215: Naming Outlets

    Chapter 6: Using the Web Interface Naming Outlets You can give each outlet a unique name up to 32 characters long to identify the equipment connected to it. The customized name is followed by the label in parentheses. Note: In this context, a label is an outlet number, such as 1, 2, 3 and so To name an outlet: 1.
  • Page 216 Chapter 6: Using the Web Interface Outlet name  Outlet status (on/off)  Outlet sensor readings:  - RMS current (A) - Active power (W) - Power factor Non-critical outlet settings (True/False) if the PDU is  outlet-switching capable Outlet receptacle type ...

  • Page 217: Outlet Switching

    Chapter 6: Using the Web Interface Line pair associated with this outlet  Overcurrent protector like a circuit breaker that protects this  outlet, if available on your model Outlet state on device startup  Power off period during power cycle ...
  • Page 218 Chapter 6: Using the Web Interface 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 selected state.
  • Page 219 Chapter 6: Using the Web Interface 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 the outlet's current state.

  • Page 220: Setting The Default Outlet State

    Chapter 6: Using the Web Interface 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 certain outlets' power-on delay timing causes it to take a long time to turn on the next outlets, but you do not intend to wait anymore.
  • Page 221 Chapter 6: Using the Web Interface 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 different state on a particular outlet, see Setting the Outlet-Specific Default State...

  • Page 222: Changing The Cycling Power-Off Period

    Chapter 6: Using the Web Interface Tip: Another way to trigger the same dialog is to use the Outlets page. Select the Outlets folder, highlight the outlet on the Outlets page and then click Setup at the bottom of the page. 4.
  • Page 223 Chapter 6: Using the Web Interface Note: The folder is named "my PX" by default. The name can be customized. 2. Click Setup in the Settings section. The Pdu Setup dialog appears. 3. In the "Power off period during power cycle" field, click the drop-down arrow and select an option from the list.

  • Page 224: Setting The Initialization Delay

    Chapter 6: Using the Web Interface 4. 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) ...

  • Page 225: Setting The Inrush Guard Delay

    Chapter 6: Using the Web Interface You can also type a value if the desired time is not listed. For example, type "15 s" for 15 seconds. 4. Click OK. 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.

  • Page 226: Setting The Outlet Power-On Sequence

    Chapter 6: Using the Web Interface 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 on the PX device.

  • Page 227: Setting The Outlet-Specific Power-On Delay

    Chapter 6: Using the Web Interface 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 sequence is Outlet 1 through Outlet 12, and you want the PX to wait for 5 seconds after turning on Outlet 3 before turning on Outlet 4, assign a delay of 5 seconds on Outlet 3.
  • Page 228 Chapter 6: Using the Web Interface 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"...
  • Page 229 Chapter 6: Using the Web Interface 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 Outlets page. Select the Outlets folder, highlight the outlet on the Outlets page and then click Setup at the bottom of the page.

  • Page 230: Resetting Outlet Active Energy Readings

    Chapter 6: Using the Web Interface 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 prompted to confirm this operation. If you chose to activate the mode in the previous step, click Yes to turn off all non-critical outlets.

  • Page 231: Enabling Front Panel Outlet Switching

    Chapter 6: Using the Web Interface To select all outlets, select the top checkbox in the header row.  3. Click Reset Active Energy at the bottom of the page. 4. Click Yes on the confirmation message. The "Active Energy" readings of all selected outlets are now reset to 0 (zero) Wh.

  • Page 232: Naming The Inlet

    Chapter 6: Using the Web Interface 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, such as I1.

  • Page 233: Monitoring Overcurrent Protectors

    Chapter 6: Using the Web Interface 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: If a sensor row is colored, it means the sensor reading already crosses one of the thresholds or the sensor enters the alarmed state.

  • Page 234: Resetting Inlet Active Energy Readings

    Chapter 6: Using the Web Interface Note: If a sensor row is colored, it means the sensor reading already crosses one of the thresholds, the sensor enters an alarmed state, or the overcurrent protector has tripped or blown. See The Yellow- or Red-Highlighted Sensors (on page 105).

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

    Chapter 6: Using the Web Interface 4. Click Yes on the confirmation message. The 'Active Energy' reading of the selected inlet now shows 0 (zero) Wh. Tip: You can reset all active energy readings at a time. See Resetting All Active Energy Readings (on page 151).

  • Page 236: Setting Power Thresholds

    Chapter 6: Using the Web Interface 6. If disabling an inlet will result in all inlets being disabled, a confirmation dialog appears, indicating that all inlets will be disabled. Then click Yes to confirm this operation or No to abort it. 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...

  • Page 237: Bulk Configuration For Outlet Thresholds

    Chapter 6: Using the Web Interface 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 Outlets page. Select the Outlets folder, highlight the outlet on the Outlets page and then click Setup at the bottom of the page.
  • Page 238 Chapter 6: Using the Web Interface Note: The folder is named "my PX" by default. The name can be customized. 2. Click the Outlets folder. The Outlets page opens. 3. Click Bulk Setup. The Outlet Threshold Bulk Setup dialog appears, with a list of all outlets.

  • Page 239: Setting Inlet Thresholds

    Chapter 6: Using the Web Interface Setting Inlet Thresholds You can set the inlet thresholds so that the alerts are generated when the inlet current and/or voltage crosses the thresholds. To set the inlet thresholds: 1. Click Inlet I1 in the PX Explorer pane, and the Inlet I1 page opens in the right pane.

  • Page 240: Bulk Configuration For Overcurrent Protector Thresholds

    Chapter 6: Using the Web Interface 3. Click Setup. The Overcurrent Protector Setup dialog appears. 4. In the Threshold Configuration table, click the sensor whose thresholds you want to configure. 5. Click Edit or double-click the desired sensor. A threshold setup dialog appears.

  • Page 241: Setting Thresholds For Total Active Energy Or Power

    Chapter 6: Using the Web Interface To select partial overcurrent protectors, click the corresponding  checkboxes of those overcurrent protectors. To deselect any overcurrent protectors, just click their  checkboxes once again. 4. Click Edit Thresholds. The threshold bulk setup dialog appears. 5.
  • Page 242 Chapter 6: Using the Web Interface Note: The folder is named "my PX" by default. The name can be customized. 2. Click Setup in the Settings section. The Pdu Setup dialog appears. 3. In the Threshold Configuration table, click the sensor whose thresholds you want to configure.

  • Page 243: Event Rules And Actions

    Chapter 6: Using the Web Interface Event Rules and Actions A benefit of the product's intelligence is its ability to notify you of 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 deleted. ...
  • Page 244 Chapter 6: Using the Web Interface 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 addresses after the selected event occurs.
  • Page 245 Chapter 6: Using the Web Interface Action Function Push out sensor Sends asset management sensor data to a readings remote server using HTTP POST requests. (on page Push Out Sensor Readings 229). Request LHX/SHX Applies the maximum cooling to the LHX/SHX maximum cooling device.
  • Page 246 Chapter 6: Using the Web Interface Action Function Switch peripheral Switches on or off the mechanism or system actuator connected to the specified actuator. See (on page 241). Switch Peripheral Actuator Note: The "Change load shedding state" and "Switch outlets" options are only available for outlet-switching capable models.
  • Page 247 Chapter 6: Using the Web Interface To remove all actions, click 8. Click OK. 9. To create additional action groups, repeat Steps 3 to 8. Alarm The Alarm is an action that requires users to acknowledge an alert. This helps ensure that the user is aware of the alert. If the Alarm action has been included in a specific event rule and no one acknowledges that alert after it occurs, the PX resends or regenerates an alert notification regularly until the alert is acknowledged or it reaches the...
  • Page 248 Chapter 6: Using the Web Interface  To remove any method from the Alarm Notifications list box, select that method and click 6. In the Notification Options section, configure the notification-resending or -regenerating feature. a. To enable the notification-resending feature, select the "Enable re-scheduling of alarm notifications"...
  • Page 249 Chapter 6: Using the Web Interface 5. From the Beeper Port drop-down list, select the port where the external beeper is connected. This port is the FEATURE port. 6. From the Beeper Action drop-down list, select an action for the external beeper to carry out.
  • Page 250 Chapter 6: Using the Web Interface 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 destination servers and the sensor data type in the Data Push dialog.
  • Page 251 Chapter 6: Using the Web Interface 4. In the "Action name" field, type a new name for the action. The default name is New Action <number>, where <number> is a sequential number starting at 1. 5. In the Action field, click the drop-down arrow and select the desired action: Request LHX/SHX maximum cooling.
  • Page 252 Chapter 6: Using the Web Interface "Time before first Snapshot (s):" - the amount of time (in seconds)  between when the event is triggered and the webcam begins taking snapshots. "Time between Snapshots (s):" - the amount of time between ...
  • Page 253 Chapter 6: Using the Web Interface If the SMTP server settings are not configured yet, click Configure. (on page 148) for the information Configuring SMTP Settings of each field. Default messages are sent based on the event. See (on page 250) for a list of default log Default Log Messages messages and events that trigger them.
  • Page 254 Chapter 6: Using the Web Interface a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received. For example, resend a new inform communication once every 3 seconds.
  • Page 255 Chapter 6: Using the Web Interface Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" Select this if authorization is required but no privacy protocols are required.  Select the authentication protocol - MD5 or ...
  • Page 256 Chapter 6: Using the Web Interface 6. In the "Syslog server" field, specify the IP address to which the syslog is forwarded. 7. In the Transport Protocol field, select one of the syslog protocols: TCP or UDP. The default is UDP. Transport Next steps protocol types...
  • Page 257  Overcurrent protector sensors, including RMS current and tripping state.  Peripheral device sensors, which can be any Raritan environmental sensor packages connected to the PX, such as temperature or humidity sensors. To configure a sensor report action: 1. Choose Device Settings > Event Rules. The Event Rules Settings dialog opens.
  • Page 258 Chapter 6: Using the Web Interface c. To delete any method, select it in the left list box, and click move it back to the right list box. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones. To remove all methods, simply click 7.
  • Page 259 Chapter 6: Using the Web Interface Start Load Shedding: Enters the load shedding mode when the  specified event occurs. Stop Load Shedding: Quits the load shedding mode when the  specified event occurs. 6. Click OK to save the new action. 7.
  • Page 260 Chapter 6: Using the Web Interface Click the Information icon to open the Event Context Information dialog, which contains a list of placeholders and their definitions. See (on page 259) for more Email and SMS Message Placeholders details. Note: Only the 7-bit ASCII charset is supported for SMS messages. 8.
  • Page 261 Chapter 6: Using the Web Interface 5. In the Action field, click the drop-down arrow and select the desired action: Switch LHX/SHX. 6. From the Operation drop-down, select Turn LHX/SHX On or Turn LHX/SHX Off. 7. From the Available LHX/SHXs list box, click on the LHX/SHX to be turned on or off, then click to add to the Switched LHX/SHXs list box.
  • Page 262 Chapter 6: Using the Web Interface 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 DX Sensor Packages...
  • Page 263 Chapter 6: Using the Web Interface 2. Click the Actions tab. 3. Click New. 4. In the "Action name" field, type a new name for the action. The default name is New Action <number>, where <number> is a sequential number starting at 1. 5.
  • Page 264 Chapter 6: Using the Web Interface Creating Rules After required actions are available, you can create event rules to determine what actions are taken to respond to specific events. By default, the PX provides the following built-in event rules:  System Event Log Rule ...
  • Page 265 Chapter 6: Using the Web Interface Event types Radio buttons Numeric sensor Available radio buttons include "Asserted," threshold-crossing "Deasserted" and "Both." events, or the  Asserted: The PX takes the action only when occurrence of the the event occurs. This means the status of selected event -- the described event transits from FALSE to true or false...
  • Page 266 Chapter 6: Using the Web Interface Event types Radio buttons Network interface Available radio buttons include "Link state is link state up," "Link state is down" and "Both."  Link state is up: The PX takes the action only when the network link state changes from down to up.
  • Page 267 Chapter 6: Using the Web Interface Event types Radio buttons Server monitoring Available radio buttons include "Monitoring event started," "Monitoring stopped," and "Both."  Monitoring started: The PX takes the action only when the monitoring of any specified server starts. ...
  • Page 268 Chapter 6: Using the Web Interface Event types Radio buttons PDU load shedding Available radio buttons include "Started," "Stopped" and "Both."  Started: The PX takes the action only when activating the load shedding mode.  Stopped: The PX takes the action only when deactivating the load shedding mode.
  • Page 269 Chapter 6: Using the Web Interface Scheduling an Action An action can be regularly performed at a preset time interval instead of being triggered by a specific event. For example, you can make the PX report the reading or state of a specific environmental sensor regularly by scheduling the "Send Sensor Report"...
  • Page 270 Chapter 6: Using the Web Interface Time options Frequency settings The frequency in minutes ranges from every minute, every 5 minutes, every 10 minutes and so on until every 30 minutes. Minutes The hourly option sets the frequency to either of the Hourly following: ...
  • Page 271 Chapter 6: Using the Web Interface To remove all actions, click  9. Click OK. Default Log Messages Following are default log messages triggered and emailed to specified recipients when PX events occur (are TRUE) or, in some cases, do not occur (are FALSE).
  • Page 272 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Card Reader Management > Card Reader with id Card inserted '[CARDREADERID]' connected. Card Reader Management > Card Reader with id Card Reader attached '[CARDREADERID]' disconnected.
  • Page 273 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Device > Bulk configuration Bulk configuration copied from host copied '[USERIP]'. Device > Network interface link The [IFNAME] network interface link is The [IFNAME] network interface state is up now up.
  • Page 274 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Peripheral Device Slot > * > Peripheral device Peripheral device Numeric Sensor > Above upper '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot critical threshold '[EXTSENSORSLOT]' asserted 'above...
  • Page 275 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* lower critical threshold '[INLET]' asserted 'below lower critical'. '[INLET]' deasserted 'below lower critical'. Inlet > * > Sensor > * > Reset Sensor '[INLETSENSOR]' on inlet '[INLET]' has been reset by user '[USERNAME]' from host '[USERIP]'.
  • Page 276 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Outlet > * > Sensor > * > Above Sensor '[OUTLETSENSOR]' on outlet Sensor '[OUTLETSENSOR]' on upper critical threshold '[OUTLET]' asserted 'above upper outlet '[OUTLET]' deasserted critical'.
  • Page 277 Chapter 6: Using the Web Interface critical threshold 'above upper critical'. deasserted 'above upper critical'. Overcurrent Protector > * > Sensor '[OCPSENSOR]' on Sensor '[OCPSENSOR]' on Sensor > * > Above upper overcurrent protector '[OCP]' asserted overcurrent protector '[OCP]' warning threshold 'above upper warning'.
  • Page 278 Chapter 6: Using the Web Interface modified '[USERIP]'. User Administration > User User '[TARGETUSER]' deleted by user deleted '[USERNAME]' from host '[USERIP]'. User Administration > Password Password of user '[TARGETUSER]' changed changed by user '[USERNAME]' from host '[USERIP]'. User Administration > Password Password settings changed by user settings changed '[USERNAME]' from host '[USERIP]'.
  • Page 279 Chapter 6: Using the Web Interface LHX / SHX > Sensor > Below Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX lower critical threshold [PORTTYPE] port '[PORTID]' asserted at [PORTTYPE] port '[PORTID]' 'below lower critical'. deasserted 'below lower critical'. LHX / SHX >...
  • Page 280 Chapter 6: Using the Web Interface LHX / SHX > Threshold Water The water inlet temperature threshold The water inlet temperature on Inlet on LHX at [PORTTYPE] port LHX at [PORTTYPE] port '[PORTID]' was crossed. '[PORTID]' is within thresholds. LHX / SHX > Threshold Water The water outlet temperature threshold The water outlet temperature on Outlet...
  • Page 281 Chapter 6: Using the Web Interface Placeholder Definition [AMSTAGID] The asset tag ID [CONFIGPARAM] The name of a configuration parameter [CONFIGVALUE] The new value of a parameter [DATETIME] The human readable timestamp of the event occurrence [DEVICEIP] The IP address of the device, the event occurred on [DEVICENAME] The name of the device, the event occurred on [ERRORDESC]...
  • Page 282 Chapter 6: Using the Web Interface Placeholder Definition [PERIPHDEVPOSITION] The position of an attached peripheral device [PORTID] The label of the external port, the event triggering device is connected to [PORTTYPE] The type of the external port (for example, 'feature' or 'auxiliary'), the event triggering device is connected to [RADIUSERRORDESC] A Radius error occurred...

  • Page 283: Sample Event Rules

    Chapter 6: Using the Web Interface Sample Event Rules Sample PDU-Level Event Rule In this example, we want the PX to record the firmware upgrade failure in the internal log when it happens. The sample event rule looks like this: ...
  • Page 284 Chapter 6: Using the Web Interface Any numeric sensor's reading moves past any threshold into the  warning or critical range. Any sensor reading or state returns to normal.  Any sensor becomes unavailable.  The active energy sensor is reset. ...
  • Page 285 Chapter 6: Using the Web Interface For example, when the Inlet I1's voltage enters the upper warning range, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, returning to the normal state, the SNMP notifications are sent again. Sample Environmental-Sensor-Level Event Rule This section applies to outlet-switching capable models only.

  • Page 286: A Note About Infinite Loop

    Chapter 6: Using the Web Interface 5. Select Events > Peripheral Device Slot to indicate we are specifying an event related to the environmental sensor. 6. Select the ID number of the desired contact closure sensor. In this illustration, the ID number of the desired contact closure sensor is 1, so select Slot 1 in the submenu.

  • Page 287: Modifying An Event Rule

    Chapter 6: Using the Web Interface Example 3 This example illustrates a situation where two event rules combined regarding the outlet state changes causes the PX to continuously power cycle outlets 1 and 2. Event selected Action included Outlet > Outlet 1 > Sensor > State > Cycle Outlet 2 On/Off (Switch Outlets -->...
  • Page 288 Chapter 6: Using the Web Interface 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 <Any user>).

  • Page 289: Modifying An Action

    Chapter 6: Using the Web Interface 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 modify an action: 1.

  • Page 290: A Note About Untriggered Rules

    Chapter 6: Using the Web Interface b. Select the desired action from the list. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones. 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.

  • Page 291: Viewing The Wireless Lan Diagnostic Log

    Chapter 6: Using the Web Interface 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 takes the place of the Show Details button. In that case, click select Show Details to view details.

  • Page 292: Viewing Connected Users

    Chapter 6: Using the Web Interface - Click to go to the prior or next page. - 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 ...

  • Page 293: Monitoring Server Accessibility

    Chapter 6: Using the Web Interface 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.

  • Page 294: Adding It Devices For Ping Monitoring

    Chapter 6: Using the Web Interface Adding IT Devices for Ping Monitoring PX can monitor the accessibility of any type of IT equipment, such as database servers, remote authentication servers, power distribution units (PDUs), and so on. PX supports monitoring a maximum of 8 devices. The default ping settings may not be suitable for monitoring devices that require high connection reliability so it is strongly recommended that you should adjust the ping settings to meet your own needs.
  • Page 295 Chapter 6: Using the Web Interface Field Description Wait time (in The wait time before the PX resumes seconds) before pinging after the monitored equipment is resuming pinging declared "Unreachable." Valid range is 1 to after failure 1200 (seconds). Number of The number of times the monitored consecutive failures equipment is declared "Unreachable"...
  • Page 296 Chapter 6: Using the Web Interface a. In the "Number of successful pings to enable feature" field, type b. In the "Wait time (in seconds) after successful ping" field, type 5. 6. To make the PX declare the inaccessibility of the monitored PDU when that PDU becomes inaccessible for around 12 seconds (4 pings * 3 seconds), do the following: a.

  • Page 297: Editing Ping Monitoring Settings

    Chapter 6: Using the Web Interface Editing Ping Monitoring Settings You can edit the ping monitoring settings for any IT device whenever needed. To modify the ping monitoring settings for an IT device: 1. Choose Device Settings > Server Reachability. The Server Reachability dialog appears.

  • Page 298: Environmental Sensors And Actuators

    Environmental Sensors or Actuators include: a. Name the sensor or actuator. b. If the connected sensor is a Raritan contact closure sensor, specify an appropriate sensor type. c. Mark the sensor or actuator's physical location on the rack or in...

  • Page 299: Identifying Environmental Sensors And Actuators

    Identifying Environmental Sensors and Actuators Raritan has developed three types of environmental sensor packages - DPX, DPX2 and DX series. The ways to identify each type of environmental sensor packages in the web interface are different.
  • Page 300 Chapter 6: Using the Web Interface A DPX2 or DX sensor has a serial number tag attached to its rear side. The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the PX. To identify each detected environmental sensor or actuator via serial numbers: 1.
  • Page 301 Chapter 6: Using the Web Interface 2. Locate the Position column, which shows one or two pieces of position information - the sensor port number and, if the sensor package is DPX2 or DX series, the sensor or actuator's location in a chain.

  • Page 302: Managing Environmental Sensors Or Actuators

    Chapter 6: Using the Web Interface Identifying Sensor or Actuator Channels A sensor package may have multiple contact closure (CC) or dry contact (DC) channels, such as DX-D2C6 or DX-PD2C5. When the PX initially detects and automatically manages a sensor package with multiple channels, all channels are assigned with ID numbers in sequence.
  • Page 303 Chapter 6: Using the Web Interface 2. Select the checkbox of the desired sensor or actuator on the Peripheral Devices page. To manage multiple ones, select multiple checkboxes. Note: To identify all detected sensors or actuators, see Identifying Environmental Sensors and Actuators (on page 278).

  • Page 304: Configuring Environmental Sensors Or Actuators

    Unmanaging Environmental Sensors or Actuators (on page 293). Special note for a Raritan humidity sensor: As of release 3.1.0, a Raritan humidity sensor is able to provide two measurements in the user interface - relative and absolute humidity values. A relative humidity value is measured in percentage (%).
  • Page 305 Chapter 6: Using the Web Interface 4. If the selected environmental sensor is a Raritan contact closure sensor connected with a third-party detector/switch, select the appropriate sensor type in the Binary Sensor Subtype field. Contact: The detector/switch is designed to detect the door lock ...
  • Page 306 Chapter 6: Using the Web Interface To set the assertion timeout, type a numeric value in the  Assertion Timeout (samples) field. See "To Assert" and (on page 651). Assertion Timeout To use the default threshold settings, select the Use Default Thresholds radio button.
  • Page 307 Chapter 6: Using the Web Interface Describing the Sensor or Actuator's Location Use the X, Y and Z coordinates to describe each sensor or actuator's physical location. You can use these location values to track records of environmental conditions in fixed locations around your IT equipment. The X, Y and Z values act as additional attributes and are not tied to any specific measurement scheme.
  • Page 308 Chapter 6: Using the Web Interface Changing Default Thresholds The default thresholds are the initial threshold values that automatically apply to numeric environmental sensors. These values are configured on a sensor type basis, which include:  Temperature sensors  Humidity sensors (both relative and absolute humidity) ...
  • Page 309 Chapter 6: Using the Web Interface Setting Thresholds for Multiple Sensors You can configure thresholds for multiple environmental sensors of the same type at a time. For example, if you want all temperature sensors to have identical upper and lower thresholds, follow the procedure below to set up all temperature sensors together.

  • Page 310: Viewing Sensor Or Actuator Data

    Chapter 6: Using the Web Interface Viewing Sensor or Actuator Data Readings and states of the environmental sensors or actuators will display in the web interface after the sensors and actuators are properly connected and managed. The Dashboard page shows the information of managed environmental sensors and actuators only, while the Peripheral Devices page shows the information of both managed and unmanaged ones.
  • Page 311 Chapter 6: Using the Web Interface Position  Serial number  Type  Channel (for a sensor package with contact closure or dry  contact channels) Whether the sensor is an 'Actuator' or not (if yes, this icon  appears in the Actuator column) Reading ...
  • Page 312 If the normal state is set to Normally Open, the normal state means the contact closure switch is open. For a Raritan's DPX floor water sensor, the normal state must be set to Normally Closed, which means no water is detected.
  • Page 313 If the normal state is set to Normally Open, the alarmed state means the contact closure switch is closed. For a Raritan's floor water sensor, the normal state must be set to Normally Closed, which means no water is detected. The alarmed state indicates that the presence of water is detected.

  • Page 314: Unmanaging Environmental Sensors Or Actuators

    Chapter 6: Using the Web Interface "above upper critical" State This state means a numeric sensor's reading is above the upper critical threshold as indicated below: Upper Critical Threshold <= Reading Note: The symbol <= means smaller than (<) or equal to (=). States of Managed Actuators DX sensor packages with dry contact channels allow you to connect actuators.

  • Page 315: Disabling The Automatic Management Function

    Chapter 6: Using the Web Interface Disabling the Automatic Management Function The factory default is to enable the automatic management feature for environmental sensors and actuators. Therefore, when the total number of managed sensors and actuators has not reached 32 yet, the PX automatically brings newly-connected environmental sensors and actuators under management after detecting them.

  • Page 316: Enabling The Front Panel Actuator Control

    Chapter 6: Using the Web Interface 3. Click "Switch on" or "Switch off" to turn on or off the selected actuators. Confirm you want to switch when prompted. Enabling the Front Panel Actuator Control This section applies to PX3 phase II models only. A PX3 phase I model does NOT support this feature.
  • Page 317 Chapter 6: Using the Web Interface 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. Click Setup. The setup dialog for the asset sensor appears. Tip: You can also trigger the same dialog by clicking Asset Management in the left pane, and then clicking Asset Strip Setup or double-clicking the asset sensor in the right pane.

  • Page 318: Setting Asset Sensor Led Colors

    Chapter 6: Using the Web Interface 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. You can configure or change the color settings for all LEDs on the connected asset sensor(s) by following the procedure below.

  • Page 319: Expanding A Blade Extension Strip

    Chapter 6: Using the Web Interface 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. Select the rack unit whose LED settings you want to change. 4.

  • Page 320: Displaying The Asset Sensor Information

    Chapter 6: Using the Web Interface 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 appear below the folder. To collapse a blade extension strip: Double-click the blade extension strip folder, or click the black, ...

  • Page 321: Bulk Configuration

    Chapter 6: Using the Web Interface 5. Click Close to quit the dialog. Bulk Configuration The Bulk Configuration feature lets you save the settings of a configured PX device to your PC. You can use this configuration file to copy that configuration to other PX devices of the same model and firmware version.

  • Page 322: Saving The Px Configuration

    Chapter 6: Using the Web Interface 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 rules, security settings, and so on.

  • Page 323: Copying The Px Configuration

    - Line cord length (meters), which is indicated as An, such as A0 and - Line cord length (centimeters), which is indicated as Ln For example, Raritan's PX2-4724-E2N1K2 and PX2-4724-E2N1K9 share the same specifications, and the only difference is their chassis colors represented by K2 (blue) and K9 (gray).

  • Page 324: Backup And Restore Of Px Device Settings

    Chapter 6: Using the Web Interface 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"...

  • Page 325: Webcam Management

    Chapter 6: Using the Web Interface 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"...

  • Page 326: Adjusting Image Properties

    Chapter 6: Using the Web Interface 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 ...

  • Page 327: Viewing Webcam Snapshots Or Videos

    Chapter 6: Using the Web Interface 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 of five Primary Standalone Live Preview windows.
  • Page 328 Chapter 6: Using the Web Interface 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  (on page 304) or Configuring Webcams Adjusting Image (on page 305).

  • Page 329: Sending Snapshots Or Videos In An Email Or Instant Message

    Chapter 6: Using the Web Interface Sending Snapshots or Videos in an Email or Instant Message Whenever you open a Primary Standalone Live Preview window, a unique URL is generated for this window session, which permits a link to the snapshot or video being captured. You are able to email or instant message up to two (2) recipients a link to webcams attached to the PX.
  • Page 330 Chapter 6: Using the Web Interface  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.

  • Page 331: Snapshot Storage

    Chapter 6: Using the Web Interface 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 File System/Samba.
  • Page 332 Chapter 6: Using the Web Interface Tip: To store snapshots on a remote server rather than the PX, see Configuring Webcam Storage (on page 312). Managing the Snapshots Saved to PX A maximum of 10 saved snapshots can be stored and displayed on the Snapshots page of the PX.
  • Page 333 Chapter 6: Using the Web Interface 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 column header, then click the Delete icon.

  • Page 334: Network Diagnostics

    Chapter 6: Using the Web Interface 8. Enter or use the slide bar to set the number of images that can be saved to the storage location. 9. Click OK. Network Diagnostics The PX provides the following tools in the web interface for diagnosing potential networking issues.

  • Page 335: Listing Tcp Connections

    2. Click Close to quit the dialog. Downloading Diagnostic Information Important: This function is for use by Raritan Field Engineers or when you are directed by Raritan Technical Support. You can download the diagnostic file from the PX device to a client machine.

  • Page 336: Managing The Schroff Lhx/Shx Heat Exchanger

    Chapter 6: Using the Web Interface 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 From the PX, you can do the following remotely: ...

  • Page 337: Enabling And Disabling Schroff Lhx/Shx Heat Exchanger Support

    Chapter 6: Using the Web Interface 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/SHX Heat Exchanger support must be enabled in order for the LHX-MIB to be accessible through SNMP.
  • Page 338 Chapter 6: Using the Web Interface Correctly Displaying the LHX/SHX Device There are two ways to have the PX show the correct LHX/SHX model in the web interface. Auto detection: Set the mode of the Feature Port to Auto to let the ...
  • Page 339 Chapter 6: Using the Web Interface Configuring Temperature and Fan Thresholds An LHX/SHX heat exchanger is implemented with various sensors for detecting the air temperature, water temperature, and fan speed. You can set thresholds for these sensors so that the PX alerts you when any sensor readings are getting close to a critical condition.

  • Page 340: Monitoring The Lhx/Shx Device

    Chapter 6: Using the Web Interface To set the assertion timeout, type a numeric value in the  Assertion Timeout (samples) field. See "To Assert" and (on page 651). Assertion Timeout 6. Click OK. Monitoring the LHX/SHX Device The PX web interface lets you monitor the status of the connected LHX/SHX heat exchanger as well as the status of the LHX/SHX built-in sensor.
  • Page 341 Chapter 6: Using the Web Interface Viewing Details An LHX/SHX heat exchanger page shows detailed information, including:  Device information and settings  The air outlet temperature  The default fan speed  Readings and states of all LHX/SHX built-in sensors ...
  • Page 342 Chapter 6: Using the Web Interface To identify the cause of the critical state, view one of the following.  The LHX/SHX Heat Exchanger section of the Dashboard page. See (on page 319). Viewing the Summary  The Feature Port page. See (on page 319).

  • Page 343: Turning The Lhx/Shx On Or Off

    Chapter 6: Using the Web Interface Below are the time units used for operating hours:  h: hour(s)  d: day(s) For example, "3d 5h" means the total operating time is 3 days and 5 hours. Turning the LHX/SHX On or Off The PX allows you to remotely turn on or off a connected heat exchanger.

  • Page 344: Requesting Maximum Cooling For An Shx-30

    Cooling to cool the device. The maximum cooling process begins. 5. Click Cancel Maximum Cooling to stop the process (if needed). Firmware Upgrade You may upgrade your PX device to benefit from the latest enhancements, improvements and features. Firmware files are available on Raritan website's Support page (http://www.raritan.com/support/).

  • Page 345: Updating The Px Firmware

    Support page read the release notes, then start the upgrade. If you have any questions or concerns about the upgrade, contact Raritan Technical Support BEFORE upgrading. On a multi-inlet PDU (any model with X2 or X3 suffixes), all inlets must be connected to the power source for the PDU to successfully upgrade its firmware.
  • Page 346 Chapter 6: Using the Web Interface 5. To view the certificate of the uploaded firmware, click View Certificate. Optional. 6. To proceed with the update, click Update Firmware. The update may take several minutes. Warning: Do NOT power off the PX during the update. During the firmware update: A progress bar appears in the web interface, indicating the ...

  • Page 347: Viewing Firmware Update History

    PDU's firmware upgrade time. The time indicated in this note is for PX web-interface-based upgrades. Upgrades through other management systems, such as Raritan's Power IQ, may take additional time beyond the control of the PDU itself. This note does not address the upgrades using other management systems.

  • Page 348: Full Disaster Recovery

    Raritan. Contact Raritan Technical Support for the recovery utility, which works in Windows XP/Vista/7 and Linux. In addition, an appropriate PX firmware file is required in the recovery procedure.

  • Page 349: Browsing Through The Online Help

    8. To email any URL link to the currently selected topic to any person, click the "Email this page" icon in the toolbar. 9. To email your comments or suggestions regarding the online help to Raritan, click the "Send feedback" icon...
  • Page 350 Chapter 6: Using the Web Interface 10. To print the currently selected topic, click the "Print this page" icon...

  • Page 351: Chapter 7 Using Snmp

    Using SNMP Chapter 7 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.

  • Page 352: Configuring Users For Encrypted Snmp V3

    Chapter 7: Using SNMP 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 community string in the Write Community ...

  • Page 353: Configuring Snmp Notifications

    Chapter 7: Using SNMP 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 (on page 222). These events can also be Event Rules and Actions used to send SNMP v2c or v3 notifications to a third-party destination.

  • Page 354: Snmpv2C Notifications

    Chapter 7: Using SNMP SNMPv2c Notifications To configure the PX to send SNMP notifications: 1. Choose Device Settings > Network Services > SNMP. The SNMP Settings dialog appears. 2. Enter the MIB-II system group information, if applicable: a. sysContact - the contact person in charge of the system being contacted b.

  • Page 355: Snmpv3 Notifications

    Chapter 7: Using SNMP a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received. For example, resend a new inform communication once every 3 seconds. b.
  • Page 356 Chapter 7: Using SNMP a. sysContact - the contact person in charge of the system being contacted b. sysName - the name assigned to the system c. sysLocation - the location of the system 3. Select the MIB to be downloaded. The SNMP MIB for your PX is used by the SNMP manager.

  • Page 357: Snmp Gets And Sets

    Chapter 7: Using SNMP 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  Enter the authentication passphrase and then confirm the authentication passphrase "authPriv"...

  • Page 358: The Px Mib

    Chapter 7: Using SNMP 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.
  • Page 359 Chapter 7: Using SNMP 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.

  • Page 360: Retrieving Energy Usage

    Chapter 7: Using SNMP SNMP Sets and Thresholds Some objects can be configured from the SNMP manager using SNMP set commands. Objects that can be configured have a MAX-ACCESS level of "read-write" in the MIB. These objects include threshold objects, which causes the PX to generate a warning and send an SNMP notification when certain parameters are exceeded.

  • Page 361: A Note About Enabling Thresholds

    Chapter 7: Using SNMP A Note about Enabling Thresholds When enabling previously disabled thresholds via SNMP, make sure you set a correct value for all thresholds that are supposed to be enabled prior to actually enabling them. Otherwise, you may get an error message.

  • Page 362: Chapter 8 Using The Command Line Interface

    Using the Command Line Interface Chapter 8 This section explains how to use the command line interface (CLI) to administer a PX device. In This Chapter About the Interface ................341 Logging in to CLI ...................342 Help Command..................346 Querying Available Parameters for a Command........347 Showing Information................347 Clearing Information ................378 Configuring the PX Device and Network ..........379...

  • Page 363: Logging In To Cli

    Chapter 8: Using the Command Line Interface Logging in to CLI Logging in via HyperTerminal over a local connection is a little different than logging in using SSH or Telnet. If a security login agreement has been enabled, you must accept the agreement in order to complete the login.

  • Page 364: With Ssh Or Telnet

    Chapter 8: Using the Command Line Interface After properly entering the password, the # or > system prompt appears. See (on page 345) in Different CLI Modes and Prompts the online help for more information. Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile was used to log in to this product's web interface or CLI.

  • Page 365: With An Analog Modem

    Chapter 8: Using the Command Line Interface With an Analog Modem The PX supports remote access to the CLI via a connected analog modem. This feature is especially useful when the LAN access is not available. To connect to the PX via the modem: 1.

  • Page 366: Different Cli Modes And Prompts

    Chapter 8: Using the Command Line Interface Different CLI Modes and Prompts Depending on the login name you use and the mode you enter, the system prompt in the CLI varies.  User Mode: When you log in as a normal user, who may not have full permissions to configure the PX device, the >...

  • Page 367: Help Command

    Chapter 8: Using the Command Line Interface Help Command The help (?) command shows a list of main CLI commands available for the current mode. This is helpful when you are not familiar with CLI commands. Help command under the administrator mode: Help command under the configuration mode: config:# Help command under the diagnostic mode:...

  • Page 368: Querying Available Parameters For A Command

    Chapter 8: Using the Command Line Interface Querying Available Parameters for a Command If you are not sure what commands or parameters are available for a particular type of CLI command or its syntax, you can have the CLI show them by adding a space and the help command (?) to the end of that command.

  • Page 369: Network Configuration

    Chapter 8: Using the Command Line Interface Network Configuration This command shows all network configuration, such as the IP address, networking mode, and MAC address. show network IP Configuration This command shows the IP-related configuration only, such as IPv4 and IPv6 configuration, address(es), gateway, and subnet mask.
  • Page 370 Chapter 8: Using the Command Line Interface 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 of wired.

  • Page 371: Pdu Configuration

    Chapter 8: Using the Command Line Interface Option Description https Only displays the TCP port for the HTTPS service. telnet Only displays the settings of the Telnet service. Only displays the settings of the SSH service. snmp Only displays the SNMP settings. modbus Only displays the settings of the Modbus/TCP service.

  • Page 372: Outlet Information

    Chapter 8: Using the Command Line Interface Outlet Information This command syntax shows the outlet information. show outlets <n> To show detailed information, add the parameter "details" to the end of the command. show outlets <n> details Variables:  <n> is one of the options: all, or a number. Option Description Displays the information for all outlets.

  • Page 373: Inlet Information

    Chapter 8: Using the Command Line Interface Inlet Information This command syntax shows the inlet information. show inlets <n> To show detailed information, add the parameter "details" to the end of the command. show inlets <n> details Variables:  <n> is one of the options: all, or a number. Option Description Displays the information for all inlets.

  • Page 374: Overcurrent Protector Information

    Chapter 8: Using the Command Line Interface Overcurrent Protector Information This command is only available for models with overcurrent protectors for protecting outlets. This command syntax shows the overcurrent protector information, such as a circuit breaker or a fuse. show ocp <n> To show detailed information, add the parameter "details"...

  • Page 375: Date And Time Settings

    Chapter 8: Using the Command Line Interface Date and Time Settings This command shows the current date and time settings on the 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 shows the default measurement units applied to the PX...

  • Page 376: Environmental Sensor Information

    Chapter 8: Using the Command Line Interface Environmental Sensor Information This command syntax shows the environmental sensor's information. show externalsensors <n> To show detailed information, add the parameter "details" to the end of the command. show externalsensors <n> details External sensor 3 ('Temperature 1') Sensor type: Temperature Reading: 31.8 deg C (normal)
  • Page 377 Chapter 8: Using the Command Line Interface * The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripheral Devices page of the PX web interface. Displayed information:  Without the parameter "details," only the sensor ID, sensor type and reading are displayed.

  • Page 378: Environmental Sensor Package Information

    Chapter 8: Using the Command Line Interface 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 environmental sensor packages, each of which may contain more than one sensor or actuator.

  • Page 379: Actuator Information

    Chapter 8: Using the Command Line Interface Actuator Information This command syntax shows an actuator's information. show actuators <n> To show detailed information, add the parameter "details" to the end of the command. show actuators <n> details Variables:  <n> is one of the options: all, or a number. Option Description Displays the information for all actuators.

  • Page 380: Outlet Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Outlet Sensor Threshold Information This command syntax shows the specified outlet sensor's threshold-related information. show sensor outlet <n> <sensor type> To show detailed information, add the parameter "details" to the end of the command. show sensor outlet <n>...

  • Page 381: Outlet Pole Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Outlet Pole Sensor Threshold Information This command is available for an in-line monitor only, including PX2-3000 and PX3-3000 series. This command syntax shows the specified outlet pole sensor's threshold-related information. show sensor outletpole <n> <p> <sensor type> To show detailed information, add the parameter "details"...

  • Page 382: Inlet Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion delay settings of the specified outlet pole sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.

  • Page 383: Inlet Pole Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified inlet sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.

  • Page 384: Overcurrent Protector Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Sensor type Description apparentPower Apparent power sensor powerFactor Power factor sensor activeEnergy Active energy sensor 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.

  • Page 385: Environmental Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Environmental Sensor Threshold Information This command syntax shows the specified environmental sensor's threshold-related information. show sensor externalsensor <n> To show detailed information, add the parameter "details" to the end of the command. show sensor externalsensor <n> details External sensor 3 (Temperature): Reading: 31.8 deg C State:...

  • Page 386: Environmental Sensor Default Thresholds

    Chapter 8: Using the Command Line Interface Variables:  <n> is the environmental sensor number. The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripheral Devices page of the PX web interface. Displayed information: ...

  • Page 387: Security Settings

    Chapter 8: Using the Command Line Interface 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 displayed in addition to default thresholds settings.

  • Page 388: Existing User Profiles

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

  • Page 389: Existing Roles

    Chapter 8: Using the Command Line Interface Existing Roles This command shows the data of one or all existing roles. show roles <role_name> Variables:  <role_name> is the name of the role whose permissions you want to query. The variable can be one of the following options: Option Description This option shows all existing roles.

  • Page 390: Serial Port Settings

    Chapter 8: Using the Command Line Interface Serial Port Settings This command shows the baud rate setting of the serial port labeled CONSOLE / MODEM on the PX device. show serial EnergyWise Settings This command shows the PX device's current configuration for Cisco ®...

  • Page 391: Rack Unit Settings Of An Asset Sensor

    1. Rack Unit Settings of an Asset Sensor For the Raritan asset sensor, a rack unit refers to a tag port. This command shows the settings of a specific rack unit or all rack units on an asset sensor, such as a rack unit's LED color and LED mode.

  • Page 392: Blade Extension Strip Settings

    Chapter 8: Using the Command Line Interface Blade Extension Strip Settings This command shows the information of a blade extension strip, including the total number of tag ports, and if available, the ID (barcode) number of any connected tag. show bladeSlot <n> <rack_unit> <blade_slot> Variables: ...

  • Page 393: Event Log

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

  • Page 394: Wireless Lan Diagnostic Log

    Server-monitoring records, such as a server being declared reachable or unreachable. energywise Cisco EnergyWise-related events, such as enabling the support of the EnergyWise function. assetManagement Raritan asset management events, such as asset tag connections or disconnections. Schroff LHX/SHX heat exchanger events. ® modem Modem-related events.
  • Page 395 Chapter 8: Using the Command Line Interface Server Reachability Information for a Specific Server To show the server reachability information for a certain IT device only, use the following command. show serverReachability server <n> To show detailed information, add the parameter "details" to the end of the command.

  • Page 396: Command History

    Chapter 8: Using the Command Line Interface Command History This command syntax shows the command history for current connection session. show history Displayed information:  A list of commands that were previously entered in the current session is displayed. History Buffer Length This command syntax shows the length of the history buffer for storing history commands.

  • Page 397: Examples

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

  • Page 399: Clearing Information

    Chapter 8: Using the Command Line Interface 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 data from the After typing a "clear"...

  • Page 400: Configuring The Px Device And Network

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

  • Page 401: Pdu Configuration Commands

    Chapter 8: Using the Command Line Interface config:# cancel The # or > prompt appears after pressing Enter, indicating that you have entered the administrator or user mode. See Different CLI Modes and (on page 345). Prompts PDU Configuration Commands A PDU configuration command begins with pdu.
  • Page 402 Chapter 8: Using the Command Line Interface Setting the Outlet Power-On Sequence This section applies to outlet-switching capable models only. This command sets the outlet power-on sequence when the PDU powers config:# pdu outletSequence <option> Variables:  <option> is one of the options: default, or a comma-separated list of outlet numbers.
  • Page 403 Chapter 8: Using the Command Line Interface config:# pdu outletSequenceDelay <outlet1>:<delay1>;<outlet2>:<delay2>; <outlet3>:<delay3>;... Separate outlet numbers and their delay settings with a colon. Outlets followed by delays are separated with a semicolon. Variables:  <outlet1>, <outlet2>, <outlet3> and the like are individual outlet numbers or a range of outlets using a dash.
  • Page 404 Chapter 8: Using the Command Line Interface Note: This feature does NOT take effect and cannot be configured on a PX3 device after the outlet relay is set to the "Latching" mode. See Setting the Outlet Relay Behavior (on page 193). Setting the PDU-Defined Cycling Power-Off Period This section applies to outlet-switching capable models only.
  • Page 405 Chapter 8: Using the Command Line Interface Setting the Outlet Initialization Delay This section applies to outlet-switching capable models only. This command determines the outlet initialization delay timing on device startup. See (on page 203) for Setting the Initialization Delay information on outlet initialization delay.
  • Page 406 Chapter 8: Using the Command Line Interface Enabling or Disabling Data Logging This command enables or disables the data logging feature. config:# pdu dataRetrieval <option> Variables:  <option> is one of the options: enable or disable. Option Description enable Enables the data logging feature. disable Disables the data logging feature.
  • Page 407 This command specifies your PX device's altitude above sea level (in meters). You must specify the PX device's altitude above sea level if a Raritan differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor. See (on page 645).
  • Page 408 Chapter 8: Using the Command Line Interface Enabling or Disabling Peripheral Device Auto Management This command enables or disables the Peripheral Device Auto Management feature. config:# pdu peripheralDeviceAutoManagement <option> Variables:  <option> is one of the options: enable or disable. Option Description enable...

  • Page 409: Network Configuration Commands

    Chapter 8: Using the Command Line Interface Examples This section illustrates several PDU configuration examples. Example 1 - PDU Naming The following command assigns the name "my px12" to the PDU. config:# pdu name "my px12" Example 2 - Outlet Sequence The following command causes a 10-outlet PDU to first power on the 8th to 6th outlets and then the rest of outlets in the ascending order after the PDU powers up.
  • Page 410 Chapter 8: Using the Command Line Interface 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 enables the wired or wireless networking mode. config:# network mode <mode>...
  • Page 411 Chapter 8: Using the Command Line Interface 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 addresses.
  • Page 412 Chapter 8: Using the Command Line Interface Setting the SSID This command specifies the SSID string. config:# network wireless SSID <ssid> Variables:  <ssid> 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 Method...
  • Page 413 Chapter 8: Using the Command Line Interface Setting EAP Parameters When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, password, and CA certificate. Determine the outer authentication protocol: config:# network wireless eapOuterAuthentication <outer_auth>...
  • Page 414 Chapter 8: Using the Command Line Interface config:# network wireless allowConnectionWithIncorrectClock <option3> Variables:  The value of <outer_auth> is PEAP because PX only supports Protected Extensible Authentication Protocol (PEAP) as the outer authentication.  The value of <inner_auth> is MSCHAPv2 because PX only supports Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) as the inner authentication.
  • Page 415 Chapter 8: Using the Command Line Interface 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 mode. See Entering (on page 379).
  • Page 416 Chapter 8: Using the Command Line Interface MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYwNAYDVQ QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA wDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/ A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOH H21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atOb EuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZ ita+z4IBO 6. Paste the contents in the terminal. 7. Press Enter. 8. Verify whether the system shows the following command prompt, indicating the provided CA certificate is valid.
  • Page 417 Chapter 8: Using the Command Line Interface Setting the IPv4 Configuration Mode This command determines the IP configuration mode. config:# network ipv4 ipConfigurationMode <mode> Variables:  <mode> is one of the modes: dhcp or static. Mode Description dhcp The IPv4 configuration mode is set to DHCP. static The IPv4 configuration mode is set to static IP address.
  • Page 418 Chapter 8: Using the Command Line Interface 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 <netmask> Variables:  <netmask> is the subnet mask address. The value ranges from 0.0.0.0 to 255.255.255.255.
  • Page 419 Chapter 8: Using the Command Line Interface 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 command and then override the DHCP-assigned DNS servers.
  • Page 420 Chapter 8: Using the Command Line Interface Setting IPv4 Static Routes If the IPv4 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the PX and devices in the other subnet.
  • Page 421 Chapter 8: Using the Command Line Interface Setting the IPv6 Configuration Mode This command determines the IP configuration mode. config:# network ipv6 ipConfigurationMode <mode> Variables:  <mode> is one of the modes: automatic or static. Mode Description automatic The IPv6 configuration mode is set to automatic. static The IPv6 configuration mode is set to static IP address.
  • Page 422 Chapter 8: Using the Command Line Interface Setting the IPv6 Address After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX device. config:# network ipv6 ipAddress <ip address> Variables: ...
  • Page 423 Chapter 8: Using the Command Line Interface Setting the IPv6 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 automatic configuration mode, you still can manually specify DNS servers with this command and then override the DHCP-assigned DNS servers.
  • Page 424 Chapter 8: Using the Command Line Interface Setting IPv6 Static Routes If the IPv6 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the PX and devices in the other subnet.
  • Page 425 Chapter 8: Using the Command Line Interface Changing the LAN Interface Speed This command determines the LAN interface speed. config:# network interface LANInterfaceSpeed <option> Variables:  <option> is one of the options: auto, 10Mbps, and 100Mbps. Option Description auto System determines the optimum LAN speed through auto-negotiation.
  • Page 426 Chapter 8: Using the Command Line Interface Setting the HTTP Port The commands used to configure the HTTP port settings begin with network services http. Change the HTTP port: config:# network services http port <n> Enable or disable the HTTP port: config:# network services http enabled <option>...
  • Page 427 Chapter 8: Using the Command Line Interface Setting the HTTPS Port The commands used to configure the HTTPS port settings begin with network services https. Change the HTTPS port: config:# network services https port <n> Enable or disable the HTTPS access: config:# network services https enabled <option>...
  • Page 428 Chapter 8: Using the Command Line Interface Option Description false The Telnet service is disabled. Changing the Telnet Port This command changes the Telnet port. config:# network services telnet port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default Telnet port is 23.
  • Page 429 Chapter 8: Using the Command Line Interface Setting the SNMP Configuration You can enable or disable the SNMP v1/v2c or v3 agent, configure the read and write community strings, or set the MIB-II parameters, such as sysContact, using the CLI commands. An SNMP command begins with network services snmp.
  • Page 430 Chapter 8: Using the Command Line Interface Setting the SNMP Read Community This command sets the SNMP read-only community string. config:# network services snmp readCommunity <string> Variables:  <string> is a string comprising 4 to 64 ASCII printable characters.  The string CANNOT include spaces.
  • Page 431 Chapter 8: Using the Command Line Interface Changing the Modbus Configuration You can enable or disable the Modbus agent, configure its read-only capability, or change its TCP port. A Modbus command begins with network services modbus. Enabling or Disabling Modbus This command enables or disables the Modbus protocol.
  • Page 432 Chapter 8: Using the Command Line Interface Changing the Modbus Port This command changes the Modbus port. config:# network services modbus port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default Modbus port is 502. Enabling or Disabling the Service Advertisement This command enables or disables the zero configuration protocol, which enables advertising or auto discovery of network services.

  • Page 433: Time Configuration Commands

    Chapter 8: Using the Command Line Interface Example 3 - Wireless Authentication Method The following command sets the wireless authentication method to PSK. config:# network wireless authMethod PSK Example 4 - Static IPv4 Configuration The following command enables the Static IP configuration mode. config:# network ipv4 ipConfigurationMode static Time Configuration Commands...
  • Page 434 Chapter 8: Using the Command Line Interface Specifying the Primary NTP Server This command specifies the primary time server if synchronization with the NTP server is enabled. config:# time ntp firstServer <first_server> Variables:  The <first_server> is the IP address or host name of the primary NTP server.
  • Page 435 Chapter 8: Using the Command Line Interface Setting the Time Zone In addition to the web interface, the CLI also provides a list of time zones for you to configure the date and time for your PX device. config:# time zone After a list of time zones is displayed, you can either type the index number of the desired time zone or simply press Enter to cancel this setting.

  • Page 436: Security Configuration Commands

    Chapter 8: Using the Command Line Interface 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 command sets the primary time server to 192.168.80.66. config:# time ntp firstServer 192.168.80.66 Security Configuration Commands...
  • Page 437 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 defaultPolicyOut <policy>  IPv6 commands Enable or disable the IPv6 firewall control feature: config:# security ipAccessControl ipv6 enabled <option> Determine the default IPv6 firewall control policy for inbound traffic: config:# security ipAccessControl ipv6 defaultPolicyIn <policy>...
  • Page 438 Chapter 8: Using the Command Line Interface Managing Firewall Rules You can add, delete or modify firewall rules using the CLI commands.  An IPv4 firewall control rule command begins with security ipAccessControl ipv4 rule.  An IPv6 firewall control rule command begins with security ipAccessControl ipv6 rule.
  • Page 439 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv6 rule add <direction> <insert> <rule_number> <ip_mask> <policy> Variables:  <direction> is one of the options: in or out. Direction Description Inbound traffic. Outbound traffic.  <ip_mask> is the combination of the IP address and subnet mask values (or prefix length), which are separated with a slash.
  • Page 440 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule modify <direction> <rule_number> ipMask <ip_mask> Modify an IPv4 rule's policy: config:# security ipAccessControl ipv4 rule modify <direction> <rule_number> policy <policy> Modify all contents of an existing IPv4 rule: config:# security ipAccessControl ipv4 rule modify <direction>...
  • Page 441 Chapter 8: Using the Command Line Interface  <rule_number> is the number of the existing rule that you want to modify.  <ip_mask> 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.
  • Page 442 Chapter 8: Using the Command Line Interface Restricted Service Agreement The CLI command used to set the Restricted Service Agreement feature begins with security restrictedServiceAgreement, Enabling or Disabling the Restricted Service Agreement This command activates or deactivates the Restricted Service Agreement.
  • Page 443 Chapter 8: Using the Command Line Interface b. Type --END-- to indicate the end of the content. c. Press Enter again. 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.
  • Page 444 Chapter 8: Using the Command Line Interface 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 <option> Variables:  <option> is one of the options: enable or disable. Option Description enable...
  • Page 445 Chapter 8: Using the Command Line Interface 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 <value> Variables: ...
  • Page 446 Chapter 8: Using the Command Line Interface 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 strong password commands to modify different parameters at a time.
  • Page 447 Chapter 8: Using the Command Line Interface Lowercase Character Requirement This command determines whether a strong password includes at least a lowercase character. config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option> Variables:  <option> is one of the options: enable or disable. Option Description enable At least one lowercase character is required.
  • Page 448 Chapter 8: Using the Command Line Interface 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 <option> Variables:  <option> is one of the options: enable or disable. Option Description enable...
  • Page 449 Chapter 8: Using the Command Line Interface 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 enabled <option> Determine the IPv4 role-based access control policy: config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>...
  • Page 450 Chapter 8: Using the Command Line Interface Tip: You can combine both commands to modify all role-based access control parameters at a time. See Multi-Command Syntax (on page 491). Managing Role-Based Access Control Rules You can add, delete or modify role-based access control rules. ...
  • Page 451 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role> <policy> <insert> <rule_number> Variables:  <start_ip> is the starting IP address.  <end_ip> is the ending IP address.  <role> is the role for which you want to create an access control rule. ...
  • Page 452 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role <role> Modify an IPv4 rule's policy: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy <policy> Modify all contents of an existing IPv4 rule: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip>...
  • Page 453 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> Variables:  <rule_number> is the number of the existing rule that you want to modify.  <start_ip> is the starting IP address. ...
  • Page 454 Chapter 8: Using the Command Line Interface 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 outlet control feature: config:# security frontPanelPermissions add switchOutlet...
  • Page 455 Chapter 8: Using the Command Line Interface Example 1 - IPv4 Firewall Control Configuration The following command sets up two parameters of the IPv4 access control feature. config:# security ipAccessControl ipv4 enabled true defaultPolicyIn accept defaultPolicyOut accept Results:  The IPv4 access control feature is enabled. ...

  • Page 456: Outlet Configuration Commands

    Chapter 8: Using the Command Line Interface config:# security userBlocking maximumNumberOfFailedLogins 5 blockTime 30 Results: The maximum number of failed logins is set to 5.   The user blocking time is set to 30 minutes. Example 4 - Adding an IPv4 Role-based Access Control Rule The following command creates a newIPv4 role-based access control rule and specifies its location in the list.
  • Page 457 Chapter 8: Using the Command Line Interface Changing an Outlet's Default State This section applies to outlet-switching capable models only. This command determines the initial power condition of an outlet after the PX powers up. config:# outlet <n> stateOnDeviceStartup <option> Variables: ...

  • Page 458: Inlet Configuration Commands

    Chapter 8: Using the Command Line Interface Setting an Outlet's Cycling Power-Off Period This section applies to outlet-switching capable models only. This command determines the power-off period of the power cycling operation for a specific outlet. config:# outlet <n> cyclingPowerOffPeriod <timing> Variables: ...
  • Page 459 Chapter 8: Using the Command Line Interface Changing the Inlet Name This command syntax names an inlet. config:# inlet <n> name "<name>" Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always the number 1. The value is an integer between 1 and 50.

  • Page 460: Overcurrent Protector Configuration Commands

    Chapter 8: Using the Command Line Interface Example - Inlet Naming The following command assigns the name "AC source" to the inlet 1. If your PX device contains multiple inlets, this command names the 1st inlet. config:# inlet 1 name "AC source" Overcurrent Protector Configuration Commands An overcurrent protector configuration command begins with ocp.
  • Page 461 Chapter 8: Using the Command Line Interface Creating a User Profile This command creates a new user profile. config:# user create <name> <option> <roles> After performing the user creation command, the PX prompts you to assign a password to the newly-created user. Then: 1.
  • Page 462 Chapter 8: Using the Command Line Interface 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 <name> password After performing the above command, PX prompts you to enter a new password.
  • Page 463 Chapter 8: Using the Command Line Interface Modifying a User's Personal Data You can change a user's personal data, including the user's full name, telephone number, and email address. Various commands can be combined to modify the parameters of a specific user profile at a time.
  • Page 464 Chapter 8: Using the Command Line Interface Enabling or Disabling a User Profile This command enables or disables a user profile. A user can log in to the PX device only after that user's user profile is enabled. config:# user modify <name> enabled <option> Variables: ...
  • Page 465 Chapter 8: Using the Command Line Interface Modifying SNMPv3 Settings There are different commands to modify the SNMPv3 parameters of a specific user profile. You can combine all of the following commands to modify the SNMPv3 parameters at a time. See Multi-Command Syntax (on page 491).
  • Page 466 Chapter 8: Using the Command Line Interface config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3> Variables: <name> is the name of the user whose settings you want to change.   <option3> is one of the options: true or false. Option Description true Authentication passphrase is identical to the password.
  • Page 467 Chapter 8: Using the Command Line Interface Determine the privacy passphrase: config:# user modify <name> privacyPassPhrase <privacy_passphrase> Variables:  <name> is the name of the user whose settings you want to change.  <privacy_passphrase> is a string used as a privacy passphrase, comprising 8 to 32 ASCII printable characters.
  • Page 468 Chapter 8: Using the Command Line Interface Changing the Role(s) This command changes the role(s) of a specific user. config:# user modify <name> roles <roles> Variables:  <name> is the name of the user whose settings you want to change. ...
  • Page 469 Chapter 8: Using the Command Line Interface Set the preferred length unit: config:# user modify <name> preferredLengthUnit <option2> Variables:  <name> is the name of the user whose settings you want to change.  <option2> is one of the options: meter or feet. Option Description meter...
  • Page 470 Chapter 8: Using the Command Line Interface Example The following procedure illustrates how to change the SSH public key for the user "assistant." 1. Verify that you have entered the configuration mode. See Entering (on page 379). Configuration Mode 2. Type the following command and press Enter. config:# user modify assistant sshPublicKey 3.
  • Page 471 Chapter 8: Using the Command Line Interface Enter new password: 5. Re-type the new password for confirmation and press Enter when the following prompt appears. Re-type new password: Setting Default Measurement Units Default measurement units, including temperature, length, and pressure units, apply to the PX user interfaces across all users except for those whose preferred measurement units are set differently by themselves or the administrator.
  • Page 472 Chapter 8: Using the Command Line Interface config:# user defaultpreferences preferredLengthUnit <option2> Variables:  <option2> is one of the options: meter or feet. Option Description meter This option displays the length or height in meters. feet This option displays the length or height in feet. Set the default pressure unit: config:# user defaultpreferences preferredPressureUnit <option3>...

  • Page 473: Role Configuration Commands

    Chapter 8: Using the Command Line Interface Example 2 - Modifying a User's Roles The following command assigns two roles to the user "May." config:# user modify May roles admin,tester Results:  The user May has the union of all privileges of "admin" and "tester." Example 3 - Default Measurement Units The following command sets all default measurement units at a time.
  • Page 474 Chapter 8: Using the Command Line Interface config:# role create <name> <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon.
  • Page 475 Chapter 8: Using the Command Line Interface Privilege Description changeSnmpSettings Change SNMP Settings changeUserSettings Change Local User Management changeWebcamSettings Change Webcam Configuration clearLog Clear Local Event Log firmwareUpdate Firmware Update performReset Reset (Warm Start) switchOutlet* Switch Outlet switchActuator** Switch Actuator viewEventSetup View Event Settings viewLog...
  • Page 476 Chapter 8: Using the Command Line Interface switchActuator:3  A list of comma-separated ID numbers of different actuators. For example: switchActuator:1,3,6 Note: The ID number of each actuator is shown in the PX web interface. It is an integer between 1 and 32. Modifying a Role You can modify diverse parameters of an existing role, including its privileges.
  • Page 477 Chapter 8: Using the Command Line Interface config:# role modify <name> addPrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon.

  • Page 478: Environmental Sensor Configuration Commands

    Chapter 8: Using the Command Line Interface Deleting a Role This command deletes an existing role. config:# role delete <name> Example - Creating a Role The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup Results: ...
  • Page 479 Specifying the CC Sensor Type Raritan's contact closure sensor (DPX-CC2-TR) supports the connection of diverse third-party or Raritan's detectors/switches. You must specify the type of connected detector/switch for proper operation. Use this command when you need to specify the sensor type.
  • Page 480 Chapter 8: Using the Command Line Interface Type Description vibration The connected detector/switch is for detection of the vibration. Setting the X Coordinate This command specifies the X coordinate of an environmental sensor. config:# externalsensor <n> xlabel "<coordinate>" Variables:  <n>...
  • Page 481 Chapter 8: Using the Command Line Interface Setting the Z Coordinate This command specifies the Z coordinate of an environmental sensor. config:# externalsensor <n> zlabel "<coordinate>" Variables:  <n> is the ID number of the environmental sensor that you want to configure.
  • Page 482 Chapter 8: Using the Command Line Interface Using Default Thresholds This command determines whether default thresholds, including the deassertion hysteresis and assertion timeout, are applied to a specific environmental sensor. config:# externalsensor <n> useDefaultThresholds <option> Variables:  <n> is the ID number of the environmental sensor that you want to configure.

  • Page 483: Configuring Environmental Sensors' Default Thresholds

    Chapter 8: Using the Command Line Interface Example 1 - Environmental Sensor Naming The following command assigns the name "Cabinet humidity" to the environmental sensor with the ID number 4. config:# externalsensor 4 name "Cabinet humidity" Example 2 - Sensor Threshold Selection The following command sets the environmental sensor #1 to use the default thresholds, including the deassertion hysteresis and assertion timeout, as its threshold settings.
  • Page 484 Chapter 8: Using the Command Line Interface config:# defaultThresholds <sensor type> lowerWarning <value> Set the Default Deassertion Hysteresis for a specific sensor type: config:# defaultThresholds <sensor type> hysteresis <hy_value> Set the Default Assertion Timeout for a specific sensor type: config:# defaultThresholds <sensor type>...

  • Page 485: Sensor Threshold Configuration Commands

    Chapter 8: Using the Command Line Interface 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 24 for all temperature sensors.
  • Page 486 Chapter 8: Using the Command Line Interface config:# sensor outlet <n> <sensor type> lowerCritical <option> Set the Lower Warning threshold for an outlet sensor: config:# sensor outlet <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an outlet sensor: config:# sensor outlet <n>...
  • Page 487 Chapter 8: Using the Command Line Interface Option Description A numeric Sets a value for the specified threshold of a value specific outlet sensor and enables this threshold at the same time.  <hy_value> is a numeric value that is assigned to the hysteresis for the specified outlet sensor.
  • Page 488 Chapter 8: Using the Command Line Interface config:# sensor inlet <n> <sensor type> hysteresis <hy_value> Set the assertion timeout for an inlet sensor: config:# sensor inlet <n> <sensor type> assertionTimeout <as_value> Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n>...
  • Page 489 Chapter 8: Using the Command Line Interface  <hy_value> is a numeric value that is assigned to the hysteresis for the specified inlet sensor. See "To De-assert" and Deassertion (on page 653). Hysteresis  <as_value> is a numeric value that is assigned to the assertion timeout for the specified inlet sensor.
  • Page 490 Chapter 8: Using the Command Line Interface config:# sensor inletpole <n> <p> <sensor type> assertionTimeout <as_value> Variables:  <n> is the number of the inlet whose pole sensors you want to configure.  <p> is the label of the inlet pole that you want to configure. Pole Label Current sensor...
  • Page 491 Chapter 8: Using the Command Line Interface  <hy_value> is a numeric value that is assigned to the hysteresis for the specified inlet pole sensor. See "To De-assert" and (on page 653). Deassertion Hysteresis  <as_value> is a number in samples that is assigned to the assertion timeout for the specified inlet pole sensor.
  • Page 492 Chapter 8: Using the Command Line Interface config:# sensor ocp <n> <sensor type> assertionTimeout <as_value> Variables:  <n> is the number of the overcurrent protector that you want to configure.  <sensor type> is one of the following sensor types: Sensor type Description current...
  • Page 493 Chapter 8: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> upperWarning <option> Set the Lower Critical threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> lowerCritical <option> Set the Lower Warning threshold for an environmental sensor: config:# sensor externalsensor <n>...
  • Page 494 Chapter 8: Using the Command Line Interface Option Description A numeric Sets a value for the specified threshold of a value specific environmental sensor and enables this threshold at the same time.  <hy_value> is a numeric value that is assigned to the hysteresis for the specified environmental sensor.
  • Page 495 Chapter 8: Using the Command Line Interface config:# sensor ocp 2 current upperWarning enable upperCritical 16 Results:  The Upper Critical threshold for the 2nd overcurrent protector's RMS current is set to 16A. It also enables the upper critical threshold if this threshold has not been enabled yet.

  • Page 496: Actuator Configuration Commands

    Chapter 8: Using the Command Line Interface 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 (on page 491).

  • Page 497: Server Reachability Configuration Commands

    Chapter 8: Using the Command Line Interface Note: To specify the Z coordinate using the rack units, see Setting the Z Coordinate Format for Environmental Sensors (on page 386).  <description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
  • Page 498 Chapter 8: Using the Command Line Interface  <succ_ping> is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200.  <fail_ping> is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to 100.
  • Page 499 Chapter 8: Using the Command Line Interface config:# serverReachability modify <n> ipAddress <IP_host> Enable or disable the ping monitoring feature for the device: config:# serverReachability modify <n> pingMonitoringEnabled <option> Modify the number of successful pings for declaring "Reachable": config:# serverReachability modify <n> numberOfSuccessfulPingsToEnable <succ_number>...
  • Page 500 Chapter 8: Using the Command Line Interface config:# serverReachability modify <n> numberOfFailuresToDisable <disable_count> Variables:  <n> is a number representing the sequence of the IT device in the server monitoring list.  <IP_host> is the IP address or host name of the IT device whose settings you want to modify.

  • Page 501: Energywise Configuration Commands

    Chapter 8: Using the Command Line Interface 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:# energywise enabled <option> Variables: ...
  • Page 502 Chapter 8: Using the Command Line Interface Specifying the EnergyWise Secret This command syntax specifies the password (secret) to enter the Cisco ® EnergyWise domain. config:# energywise secret <password> Variables:  <password> is a string comprising up to 127 ASCII printable characters.

  • Page 503: Usb-Cascading Configuration Commands

    Chapter 8: Using the Command Line Interface Example - Setting Up EnergyWise The following command sets up two Cisco EnergyWise-related features. ® config:# energywise enabled true port 10288 Results:  The EnergyWise feature implemented on the PX is enabled.  The UDP port is set to 10288.
  • Page 504 PX device. config:# assetStrip <n> numberOfRackUnits <number> Note: For the Raritan asset sensor, a rack unit refers to a tag port. Variables:  <n> is the number of the FEATURE port where the selected asset sensor is physically connected.
  • Page 505 Chapter 8: Using the Command Line Interface 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 <n>...
  • Page 506 Chapter 8: Using the Command Line Interface 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 the PX unable to detect the asset sensors' orientation.
  • Page 507 <color> is the hexadecimal RGB value of a color in HTML format. The <color> variable ranges from #000000 to #FFFFFF. Rack Unit Configuration For the Raritan asset sensor, a rack unit refers to a tag port. A rack unit configuration command begins with rackUnit. Naming a Rack Unit This command syntax assigns or changes the name of the specified rack unit on the specified asset sensor.
  • Page 508 Chapter 8: Using the Command Line Interface 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 <n> <rack_unit> LEDOperationMode <mode> Variables:  <n>...
  • Page 509 Chapter 8: Using the Command Line Interface 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."...

  • Page 510: Serial Port Configuration Commands

    Chapter 8: Using the Command Line Interface 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 the asset sensor #1 to BLACK (that is, 000000) to indicate the absence of a connected asset tag.

  • Page 511: Setting The History Buffer Length

    The following command syntax sets the CONSOLE baud rate (bps) of the serial port labeled CONSOLE / MODEM on the PX device. Change the CONSOLE baud rate before connecting it to any Raritan device, such as Raritan's P2CIM-SER, through the serial port, or there are communications errors.

  • Page 512: Multi-Command Syntax

    Chapter 8: Using the Command Line Interface Multi-Command Syntax To shorten the configuration time, you can combine various configuration commands in one command to perform all of them at a time. All combined commands must belong to the same configuration type, such as commands prefixed with network, user modify, sensor externalsensor and so on.

  • Page 513: Load Shedding Configuration Commands

    Chapter 8: Using the Command Line Interface Example 3 - Combination of SSID and PSK Parameters This multi-command syntax configures both SSID and PSK parameters simultaneously for the wireless feature. config:# network wireless SSID myssid PSK encryp_key Results:  The SSID value is set to myssid. ...

  • Page 514: Enabling Or Disabling Load Shedding

    Chapter 8: Using the Command Line Interface Enabling or Disabling Load Shedding This section applies to outlet-switching capable models only. This command determines whether to enter or exit from the load shedding mode. loadshedding <option> After performing the above command, PX prompts you to confirm the operation.

  • Page 515: Power Control Operations

    Chapter 8: Using the Command Line Interface Power Control Operations This section applies to outlet-switching capable models only. Outlets on the PX device can be turned on or off or power cycled through the CLI. Besides, you can cancel the power-on process while the PX is powering on ALL outlets.

  • Page 516: Turning Off The Outlet(S)

    Chapter 8: Using the Command Line Interface If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then: Type y to confirm the operation, OR  Type n to abort the operation  Turning Off the Outlet(s) This section applies to outlet-switching capable models only.

  • Page 517: Power Cycling The Outlet(S)

    Chapter 8: Using the Command Line Interface Type n to abort the operation  Power Cycling the Outlet(s) This section applies to outlet-switching capable models only. This command power cycles one or multiple outlets. power outlets <numbers> cycle To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation.

  • Page 518: Canceling The Power-On Process

    Chapter 8: Using the Command Line Interface Canceling the Power-On Process This section applies to outlet-switching capable models only. After issuing the command to power on ALL outlets, you can use the following command to stop the power-on process. power cancelSequence To quicken the operation, you can add the parameter "/y"...

  • Page 519: Checking The Accessibility Of Ntp Servers

    Chapter 8: Using the Command Line Interface Checking the Accessibility of NTP Servers This command verifies the accessibility of NTP servers specified manually on your PX and then shows the result. For instructions on specifying NTP servers via CLI, see (on page Setting NTP Parameters 412).

  • Page 520: Switching On An Actuator

    Chapter 8: Using the Command Line Interface Switching On an Actuator This command syntax turns on one actuator. control actuator <n> on To quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation. control actuator <n>...

  • Page 521: Unblocking A User

    Chapter 8: Using the Command Line Interface If you entered the command without "/y", a message appears, prompting you to confirm the operation. Then: Type y to confirm the operation, OR  Type n to abort the operation  Example - Turning On a Specific Actuator The following command turns on the actuator whose ID number is 8.

  • Page 522: Restarting The Pdu

    Chapter 8: Using the Command Line Interface Restarting the PDU This command restarts the PX device. It is not a factory default reset. To restart the PX device: 1. Ensure you have entered administrator mode and the # prompt is displayed.

  • Page 523: Network Troubleshooting

    Chapter 8: Using the Command Line Interface reset activeEnergy outlet <outlet_n> /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 it. Variables: ...

  • Page 524: Quitting Diagnostic Mode

    Chapter 8: Using the Command Line Interface Quitting Diagnostic Mode To quit the diagnostic mode, use this command: diag> exit The # or > prompt appears after pressing Enter, indicating that you have entered the administrator or user mode. See Different CLI Modes and (on page 345).
  • Page 525 Chapter 8: Using the Command Line Interface Testing the Network Connectivity This ping command sends the ICMP ECHO_REQUEST message to a network host for checking its network connectivity. If the output shows the host is responding properly, the network connectivity is good. If not, either the host is shut down or it is not being properly connected to the network.

  • Page 526: Retrieving Previous Commands

    Chapter 8: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your PX device and a network host. diag> traceroute <host> Variables:  <host> is the name or IP address of the host you want to trace. Example - Ping Command The following command checks the network connectivity of the host 192.168.84.222 by sending the ICMP ECHO_REQUEST message to the...

  • Page 527: Logging Out Of Cli

    Chapter 8: Using the Command Line Interface Example 1: Type the first word and the first letter of the second word of the "reset factorydefaults" command, that is, reset f. Then press Tab or Ctrl+i to complete the second word. Example 2: Type the first word and initial letters of the second word of the "security enforceHttpsForWebAccess"...

  • Page 528: Chapter 9 In-Line Monitors

    In-Line Monitors Chapter 9 The model name of a PX in-line monitor follows this format: PX3-3nnn, where n is a number, such as PX3-3411. Unlike most of PX devices, each inlet of an in-line monitor is connected to an outlet only, so an inlet's rating is the same as an outlet's rating. In This Chapter Overview....................507 Safety Instructions .................507...

  • Page 529: Flexible Cord Installation Instructions

    Important: Complete and the most updated instructions on installing a Raritan PX Power Cord flexible cord on Raritan PDUs are included in the Installation Guide , which is available on the Raritan website at this URL: http://www.raritan.com/support/product/px2/px2-support-files. Flexible Cord Selection ...

  • Page 530: Plug Selection

    For example, using a 16A plug would result in a derated ampacity of 16A. 2. The derated ampacity must be marked on the Raritan product so the new reduced rating can be easily identified. 3. For in-line monitors, the receptacles used must have the same...

  • Page 531: Wiring Of 3-Phase In-Line Monitors

    A sealing ring, for small diameter flexible cords, may have been included with the Raritan product, or one can be requested from Raritan, to reduce the inside diameter of the cable gland.
  • Page 532 Chapter 9: In-Line Monitors One-channel in-line monitor Zero U PDU Make sure to locate the ground wire mounting stud(s). There is a separate ground wire mounting stud for each terminal block. Each flexible cord MUST have its green (or green/yellow) ground wire bonded to a ground wire mounting stud.
  • Page 533 Use the following to help determine how much jacket to remove: In the finished assembly, the outer jacket should protrude inside  the Raritan product. The wires will have ring terminals crimped onto them.  In the finished assembly, the wires should have some slack and ...
  • Page 534 A sealing ring for smaller diameter line cords may have been included with the Raritan product, or can be requested from Raritan, to reduce the inside diameter of the cable gland.
  • Page 535 Make sure each ring terminal is firmly fastened and cannot be twisted by hand. Use the following guidelines to help terminal block wiring. In single-phase Raritan products with world-wide ratings, the  terminals are labeled L1 and L2. L1 is the phase wire. L2 is either the neutral (120/230V installations) or another phase wire (208V installations).
  • Page 536 For example, push the L1 line cord wire through the CT labeled L1 and then connect it to the L1 terminal block. For Raritan in-line monitors, where there is a one to one  correspondence between plug and receptacle, maintain the same wire colors for inlet and outlet flexible cords.

  • Page 537: In-Line Monitor's Web Interface

    Chapter 9: In-Line Monitors 9. For in-line monitors, fasten the receptacles to the outlet flexible cords following the manufacturer’s instructions. 10. Complete the wiring of the inlet flexible cord by performing one of these steps: Assemble the plug following the manufacturer’s instructions. ...

  • Page 538: Dashboard

    Chapter 9: In-Line Monitors Dashboard Page After login, the web interface displays the Dashboard page by default. An inline monitor's Dashboard page looks slightly different from a regular PX device's Dashboard page. The power status of the outlet on a three-phase Y-wired inline monitor is displayed on this page, including: ...
  • Page 539 Chapter 9: In-Line Monitors Note: Depending on your model, elements shown on the same page may appear slightly different from this image.

  • Page 540: Appendix A Specifications

    Maximum Ambient Operating Temperature The maximum ambient operating temperature (TMA) for PX varies from 50 to 60 degrees Celsius, depending on the model and certification standard (CE or UL). If necessary, contact Raritan Technical Support for this information for your model. Measure...

  • Page 541: Feature Rj-45 Port Pinouts

    (200mA, fuse protected) Warning: Pin 3 is only intended for use with Raritan devices. Output Transmit Data (Data out) Input Receive Data (Data in) +12V ― Warning: Pin 6 is only intended for use with Raritan devices. Do NOT connect.
  • Page 542 Appendix A: Specifications RJ-45 Pin/signal definition Pin No. Signal Direction Description Signal Ground ― Input Reserved...

  • Page 543: Appendix B Equipment Setup Worksheet

    Appendix B Equipment Setup Worksheet PX Series Model _______ _____ PX Series Serial Number ____________ OUTLET 1 OUTLET 2 OUTLET 3 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER OUTLET 4 OUTLET 5 OUTLET 6 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER...
  • Page 544 Appendix B: Equipment Setup Worksheet OUTLET 7 OUTLET 8 OUTLET 9 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER OUTLET 10 OUTLET 11 OUTLET 12 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER OUTLET 13 OUTLET 14 OUTLET 15 MODEL MODEL MODEL...
  • Page 545 Appendix B: Equipment Setup Worksheet OUTLET 16 OUTLET 17 OUTLET 18 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER OUTLET 19 OUTLET 20 OUTLET 21 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER...
  • Page 546 Appendix B: Equipment Setup Worksheet OUTLET 22 OUTLET 23 OUTLET 24 MODEL MODEL MODEL SERIAL NUMBER SERIAL NUMBER SERIAL NUMBER Types of adapters _________________________________________________________ Types of cables _________________________________________________________ Name of software program _________________________________________________________...

  • Page 547: Bulk Configuration/Upgrade Procedure

    3.1.0 or later. If not, upgrade them first. Steps of using DHCP/TFTP for bulk configuration/upgrade: 1. Create configuration files specific to your PX models and firmware versions. You must contact Raritan Technical Support to properly prepare these files, which include some or all of the following: ...

  • Page 548: Tftp Requirements

    Note: Supported syntax of "fwupdate.cfg" and "config.txt" may vary based on different firmware versions. If you have existing configuration files, it is suggested to double check with Raritan Technical Support for the correctness of these files prior to using this feature.

  • Page 549: Dhcp Ipv4 Configuration In Windows

    Windows Server 2012 system. ® Required Windows IPv4 settings in DHCP: 1. Add a new vendor class for Raritan PX under IPv4. a. Right-click the IPv4 node in DHCP to select Define Vendor Classes. b. Click Add to add a new vendor class.
  • Page 550 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The vendor class is named "Raritan PDU" in this illustration. 2. Define one DHCP standard option - Vendor Class Identifier. a. Right-click the IPv4 node in DHCP to select Set Predefined...
  • Page 551 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select DHCP Standard Options in the "Option class" field, and Vendor Class Identifier in the "Option name" field. Leave the String field blank. 3. Add three options to the new vendor class "Raritan PDU" in the same dialog.
  • Page 552 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Select Raritan PDU in the "Option class" field. b. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the...
  • Page 553 Name field, select String as the data type, and type 3 in the Code field. 4. Create a new policy associated with the "Raritan PDU" vendor class. a. Right-click the Policies node under IPv4 to select New Policy. b. Specify a policy name, and click Next.
  • Page 554 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The policy is named "PDU" in this illustration. c. Click Add to add a new condition.
  • Page 555 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select the vendor class "Raritan PDU" in the Value field, click Add and then Ok. e. Click Next.
  • Page 556 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Select DHCP Standard Options in the "Vendor class" field, select "060 Vendor Class Identifier" from the Available Options list, and type "Raritan PDU 1.0" in the "String value" field.
  • Page 557 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP g. Select the "Raritan PDU" in the "Vendor class" field, select "001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv4 address in the "IP address" field.
  • Page 558 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP h. Select "002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. Select "003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly.

  • Page 559: Dhcp Ipv6 Configuration In Windows

    For those PX devices using IPv6 addresses, follow this procedure to configure your DHCP server. The following illustration is based on Microsoft Windows Server 2012 system. ® Required Windows IPv6 settings in DHCP: 1. Add a new vendor class for Raritan PX under IPv6.
  • Page 560 Click Add to add a new vendor class. c. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)" field, and type the binary codes of "Raritan PDU 1.0" in the New Class dialog.
  • Page 561 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 2. Add three options to the "Raritan PDU 1.0" vendor class. a. Right-click the IPv6 node in DHCP to select Set Predefined Options.
  • Page 562 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select Raritan PDU 1.0 in the "Option class" field. c. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the...
  • Page 563 Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field. 3. Configure server options associated with the "Raritan PDU 1.0" vendor class. a. Right-click the Server Options node under IPv6 to select Configure Options.
  • Page 564 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP c. Select "Raritan PDU 1.0" in the "Vendor class" field, select "00001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv6 address in the "IPv6 address" field.
  • Page 565 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select "00002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. e. Select "00003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly.

  • Page 566: Dhcp Ipv4 Configuration In Linux

    Modify the "dhcpd.conf" file for IPv4 settings when your DHCP server is running Linux. Required Linux IPv4 settings in DHCP: 1. Locate and open the "dhcpd.conf" file of the DHCP server. 2. The PX will provide the following value of the vendor-class-identifier option (option 60). vendor-class-identifier = "Raritan PDU 1.0" ...
  • Page 567 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 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 1 (pdu-tftp-server) = the TFTP server's IPv4 address ...

  • Page 568: Dhcp Ipv6 Configuration In Linux

    13742 (Raritan's IANA number)  Raritan PDU 1.0  15 (the length of the above string "Raritan PDU 1.0")  3. Set the following three sub-options in the "vendor-opts" (option 17). code 1 (pdu-tftp-server) = the TFTP server's IPv6 address...
  • Page 569 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 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. It does NOT matter whether the IPv6 magic cookie is identical to or different from the IPv4 magic cookie.

  • Page 570: Appendix D Resetting To Factory Defaults

    Appendix D Resetting to Factory Defaults 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.

  • Page 571: Using The Cli Command

    Appendix D: Resetting to Factory Defaults PX3 Phase I models: Note: HyperTerminal is available on Windows operating systems prior to Windows Vista. For Windows Vista or later versions, you may use PuTTY, which is a free program you can download from the Internet. See PuTTY's documentation for details on configuration.
  • Page 572 Appendix D: Resetting to Factory Defaults To reset to factory defaults without logging in to the CLI: The PX provides an easier way to reset the product to factory defaults in the CLI prior to login. 1. Connect to the PX and launch a terminal emulation program as described in the above procedure.

  • Page 573: Appendix E Available Scp Commands

    Appendix E Available SCP Commands 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 ..............552 Bulk Configuration via SCP ..............553 Backup and Restore via SCP ..............554 Firmware Update via SCP Same as any PX firmware update, all user management operations are...

  • Page 574: Bulk Configuration Via Scp

    Appendix E: Available SCP Commands 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 <firmware file> <user name>@<device ip>:/fwupdate Bulk Configuration via SCP Like performing bulk configuration via the web interface, there are two steps with the bulk configuration using the SCP commands: a.

  • Page 575: Backup And Restore Via Scp

    Appendix E: Available SCP Commands 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.50:/bulk_config.xml ...
  • Page 576 Appendix E: Available SCP Commands <user name> is the "admin" or any user profile with the  administrator privileges. <device ip> 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.

  • Page 577: Appendix F Px3 Phase I Lcd Display

    Appendix F PX3 Phase I LCD Display The following diagram shows the character LCD display panel on a Zero U PX3 Phase I model. The LCD display can show the reading or status of different components on the PX, or the PX's MAC address and IP address. It consists of: ...

  • Page 578: Control Buttons

    Appendix F: PX3 Phase I LCD Display Section Information shown The following information is displayed:  Readings, data or state of the selected target.  During the firmware upgrade, 'FUP' is displayed. Two types of information may be displayed:  The 'ALARM' status of the selected component.

  • Page 579: Operating The Character Lcd Display

    Appendix F: PX3 Phase I LCD Display (on page 556) for Overview of the Character LCD Display details.  FUNC (Function) button for switching between different data of the selected target, such as the current, voltage or power readings of a particular outlet Operating the Character LCD Display After powering on or resetting this product, the LCD display panel shows...
  • Page 580 Appendix F: PX3 Phase I LCD Display A is displayed for the current reading. A means Amp.  V is displayed for the voltage reading. V means Volt.  W is displayed for the power reading. W means Watt.  If the word "ALARM"...

  • Page 581: Inlet Information

    Appendix F: PX3 Phase I LCD Display Inlet Information The Inlet mode is displayed as "INLET" on the LCD display. Below illustrates the inlet information shown on the LCD display. Section Example information The selected target is INLET 1. This inlet's L1 current reading is 23 amps. The selected inlet line is L1.

  • Page 582: Overcurrent Protector Information

    Appendix F: PX3 Phase I LCD Display To display the unbalanced load and active power of a 3-phase inlet: 1. Switch to the current reading of any inlet line. 2. Press the Up or Down button until "W" or "%" is displayed to the right of the LCD display.

  • Page 583: Ip Address

    Appendix F: PX3 Phase I LCD Display 2. In the Overcurrent Protector mode, press the Up or Down button until the desired overcurrent protector's number is displayed at the top of the LCD display. 3. Check the reading and the text shown below the reading: CLOSE or OPEN.

  • Page 584: Mac Address

    Appendix F: PX3 Phase I LCD Display If you connect your PX to the wireless network, a Wi-Fi icon is displayed at the bottom-right corner. To retrieve the IP address: 1. Press the MODE button until device settings are displayed, indicated by a 'd' in at the top left of the display.

  • Page 585: Outlet Switching

    Appendix F: PX3 Phase I LCD Display Section Example information The LCD display is showing "03," which is part of the MAC address. To display the MAC address: 1. Press the MODE button until device settings are displayed, indicated by a 'd' in at the top left of the display. 2.
  • Page 586 Appendix F: PX3 Phase I LCD Display 2. Press the Up or Down button to select the desired outlet. The selected outlet's number is displayed at the top of the LCD display. 3. Press the FUNC button to to perform the outlet switching operation. The LCD display cycles between two messages as shown in the two diagrams below.

  • Page 587: Environmental Sensor Information

    Appendix F: PX3 Phase I LCD Display 7. You can verify the power state of the selected outlet by checking its LED color. Green indicates the power off state and red indicates the power on state. Environmental Sensor Information The environmental sensor mode is displayed as "SENSOR" on the LCD display.
  • Page 588 Appendix F: PX3 Phase I LCD Display is displayed for a temperature sensor.  m/s is displayed for an air flow sensor.  Pa is displayed for an air pressure sensor.  For a discrete sensor, either of the following states is displayed. nor: The sensor is in the normal state.

  • Page 589: Asset Sensor Information

    Sensor mode to show the asset tag state of each rack unit on the asset sensor. For the Raritan asset sensor, a rack unit refers to a tag port. When there are no asset sensors connected, this mode is not available.

  • Page 590: Usb-Cascaded Device's Position

    Appendix F: PX3 Phase I LCD Display 3. Press the FUNC button. When a blinking double-arrow symbol appears to the left of the LCD display, press the Up or Down button to select the desired rack unit on the asset sensor. The rack unit number appears in the middle of the LCD display.
  • Page 591 Appendix F: PX3 Phase I LCD Display For a master device, a word "MASTER" is displayed on the LCD display instead of the word "SLAVE." To retrieve the device's USB-cascading position information: 1. Press the MODE button until device settings are displayed, indicated by a 'd' in at the top left of the display.

  • Page 592: In This Chapter Rcm Current Sensor

    Appendix G PX Models with Residual Current Monitoring PX models with residual current monitoring (RCM) detect and report residual current - abnormal flow of current into the protective earth conductor. Residual current is a safety issue since electrocution is possible if the rack or any device within it is touched.

  • Page 593: Rcm State Sensor

    Self-test active RCM diagnostics are running. Failure RCM current sensor has malfunctioned. Contact Raritan Technical Support. Note: The factory default is to disable the Warning state. To define and enable this state, see Setting RCM Current Thresholds...

  • Page 594: Compliance With Iec 62020

    Appendix G: PX Models with Residual Current Monitoring Compliance with IEC 62020 IEC 62020 is an international standard for Residual Current Monitors. All PX with RCM are IEC 62020 compliant. IEC 62020 uses the term rated residual operating current (IΔn) to specify residual current, equal to or above which causes an alarm.

  • Page 595: Rcm Self-Test

    Appendix G: PX Models with Residual Current Monitoring IEC 62020 specification PX with RCM characteristics Ability to directly Directionally non-discriminating. discriminate Rated residual operating 0.5A (highest value). current Residual currents with Type A. direct current components RCM Self-Test PX with RCM have a built-in self-test feature that performs these functions: ...
  • Page 596 Appendix G: PX Models with Residual Current Monitoring Residual Operating Current: The magnitude of residual current  detected. Note: To determine the RCM's normal, warning and critical levels, configure the RCM current thresholds. See Setting RCM Current Thresholds (on page 576). RCM Critical State Alarm When a PX device's RCM enters the Critical state, the PX beeps and this alarm is displayed in the Alerted Sensors section of the Dashboard page.

  • Page 597: Setting Rcm Current Thresholds

    Appendix G: PX Models with Residual Current Monitoring Setting RCM Current Thresholds The RCM current thresholds define the critical, warning and normal range of residual current. To configure the RCM current thresholds and run self-test: 1. Click Inlet I1 to open the Inlet page. 2.

  • Page 598: Front Panel Operations For Rcm

    Appendix G: PX Models with Residual Current Monitoring Disabling or Enabling Front Panel RCM Self-Test You can enable or disable the function of performing the RCM self-test by operating the front panel buttons. By default, this function is enabled. To disable or enable the front panel RCM self-test: 1.
  • Page 599 Appendix G: PX Models with Residual Current Monitoring Residual Current: Residual current value in Amps.  If your PX has more than one inlet, only the inlet which has the RCM alarm enters the critical state. 2. If needed, you can press to perform RCM self-test for this inlet.

  • Page 600: Checking Rcm States On Phase Ii Models

    Appendix G: PX Models with Residual Current Monitoring Checking RCM States on Phase II Models Unlike PX3 phase I models, which show RCM information on the LCD display only when there is an RCM critical alarm, PX3 phase II models allow you to retrieve RCM information from the LCD display even though there is no RCM alarm.

  • Page 601: Displaying The Rcm Current

    Appendix G: PX Models with Residual Current Monitoring Displaying the RCM Current Depending on the PX3 model you purchased, the procedures to retrieve RCM readings using the LCD display are different. PX3 phase II models: The RCM reading of each inlet is shown along with the RCM status of each inlet.

  • Page 602: Running Rcm Self-Test

    Appendix G: PX Models with Residual Current Monitoring Running RCM Self-Test You can perform the RCM self-test by operating the front panel buttons. To disable or enable this front panel function, see Disabling or (on page 577). By default, this Enabling Front Panel RCM Self-Test function is enabled.
  • Page 603 Appendix G: PX Models with Residual Current Monitoring 6. After completing the RCM self-test, the LCD display indicates the RCM self-test result: passed or failed. 7. Press to return to the RCM information page. 8. Do one of the following: To perform RCM self-test for additional inlets, press ...

  • Page 604: Rcm Snmp Operations

    Appendix G: PX Models with Residual Current Monitoring Below illustrates the RCM self-test mode. Section Example information The inlet containing RCM sensor is INLET 1. The LCD alternates between "SLF" and "tSt" to indicate that this is self-test mode. ALARM always displays for residual current sensor. LEAK always displays for residual current sensor.

  • Page 605: Cli Operations For Rcm

    Appendix G: PX Models with Residual Current Monitoring Setting RCM Thresholds The inletSensorConfigurationTable contains a row for configuring RCM thresholds. Use index sensorType = 26 to reference the row. Columns inletSensorUpperWarningThreshold, inletSensorUpperCriticalThreshold and inletSensorHysteresis set values for RCM warning, critical and deassertion hysteresis respectively.

  • Page 606: Setting Rcm Current Thresholds

    Appendix G: PX Models with Residual Current Monitoring Setting RCM Current Thresholds Warning Rated Residual Operating Current is the upper warning threshold of the PX RCM sensor, and Critical Rated Residual Operating Current is the upper critical threshold of the RCM sensor. These thresholds are set in the configuration mode.

  • Page 607: Setting Front Panel Rcm Self-Test

    Appendix G: PX Models with Residual Current Monitoring Option Description A numeric Sets a value for the specified RCM current value threshold of the specified inlet and enables this threshold simultaneously. Note that this value is measured in A, not mA. Therefore, to set the value to 6mA, type 0.006.

  • Page 608: Appendix H Ldap Configuration Illustration

    Configure LDAP authentication on the PX device d. Configure roles on the PX device Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.

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

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

  • Page 610: Step C. Configure Ldap Authentication On The Px Device

    Appendix H: LDAP Configuration Illustration 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 (on page 121) and Modifying Network Settings Role of a DNS...
  • Page 611 Appendix H: LDAP Configuration Illustration Base DN for Search - Type dc=techadssl,dc=com as the  starting point where your search begins on the AD server. Login Name Attribute - Ensure the field is set to  sAMAccountName because the LDAP server is Microsoft Active Directory.

  • Page 612: Step D. Configure User Groups On The Px Device

    Appendix H: LDAP Configuration Illustration 5. Click OK. The LDAP server is saved. 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 PX and the LDAP server to use the same NTP server(s).
  • Page 613 Appendix H: LDAP Configuration Illustration d. Repeat Steps a to c to add all permissions beginning with "View." 6. Click OK. The PX_User role is created. 7. Keep the Manage Roles dialog opened to create the PX_Admin role. To create the PX_Admin role with full permissions assigned: 1.
  • Page 614 Appendix H: LDAP Configuration Illustration 2. Type PX_Admin in the Role Name field. 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 allows users to configure or change all PX settings.
  • Page 615 Appendix H: LDAP Configuration Illustration 5. Click OK. The PX_Admin role is created. 6. Click Close to quit the dialog.

  • Page 616: Appendix I Radius Configuration Illustration

    Appendix I RADIUS Configuration Illustration 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.

  • Page 617: Step A: Add Your Px As A Radius Client

    Appendix I: RADIUS Configuration Illustration 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.
  • Page 618 Appendix I: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX. In this example, they are 1812 and 1813. Then close this dialog.
  • Page 619 Appendix I: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PX to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.

  • Page 620: Step B: Configure Connection Request Policies

    Appendix I: RADIUS Configuration Illustration Type the shared secret in the "Shared secret" and "Confirm shared secret" fields. The shared secret must be the same as the one specified on your PX. 5. Click OK. Step B: Configure Connection Request Policies You need to configure the following for connection request policies: a.
  • Page 621 Appendix I: RADIUS Configuration Illustration 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 ...
  • Page 622 Appendix I: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
  • Page 623 Appendix I: RADIUS Configuration Illustration You can leave the "Type of network access server" field to the  default -- Unspecified.
  • Page 624 Appendix I: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
  • Page 625 Appendix I: RADIUS Configuration Illustration 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 example.
  • Page 626 Appendix I: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options: Override network policy authentication settings  CHAP -- the PX uses "CHAP" in this example ...
  • Page 627 Appendix I: RADIUS Configuration Illustration Note: If your PX uses PAP, then select "PAP."...
  • Page 628 Appendix I: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
  • Page 629 Appendix I: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
  • Page 630 Appendix I: RADIUS Configuration Illustration 12. In the Attribute Information dialog, click Add. 13. Select String, type Raritan:G{Admin} in the text box, and then click...
  • Page 631 Appendix I: RADIUS Configuration Illustration 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 632 Appendix I: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
  • Page 633 Appendix I: RADIUS Configuration Illustration 15. Click Next to continue.
  • Page 634 Appendix I: RADIUS Configuration Illustration 16. A summary showing connection request policy settings is displayed. Click Finish to close the dialog.

  • Page 635: Step C: Configure A Vendor-Specific Attribute

    Appendix I: RADIUS Configuration Illustration 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: Admin, User, and SystemTester.
  • Page 636 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 brackets {} -- Admin, User and SystemTester.

  • Page 637: Ad-Related Configuration

    Appendix I: RADIUS Configuration Illustration 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 server is registered in AD only when NPS is configured for the FIRST time and user accounts are created in AD.
  • Page 638 Appendix I: RADIUS Configuration Illustration 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 639 Appendix I: RADIUS Configuration Illustration 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 640: Non-Windows Radius Server

    Non-Windows RADIUS Server For a non-Windows RADIUS server, such as FreeRADIUS, a vendor-specific dictionary file is required. Dictionary File Create a vendor-specific dictionary file for Raritan and add the following information to it. Raritan's vendor code is 13742.

  • Page 641: Format Of The "String

    Raritan-Vendor-Specific string END-VENDOR Raritan Note that "string" in the above contents must be replaced by Raritan:G{roles}, where "roles" are one or multiple roles to which the user belongs. For more details, see (on page Format of the "string" 620). Format of the "string"...
  • Page 642 Appendix I: RADIUS Configuration Illustration Therefore, in Raritan's dictionary file, the attribute line is like the following: ATTRIBUTE Raritan-Vendor-Specific 26 Raritan:G{Admin User SystemTester}...

  • Page 643: Appendix J Integration

    Appendix J Integration The PX device can work with certain Raritan products to provide diverse power solutions. In This Chapter Power IQ Configuration .................622 Dominion KX II Configuration ..............625 Dominion KSX II or SX Configuration............630 dcTrack ....................638 Power IQ Configuration Raritan's Power IQ is a software application that collects and manages the data from different PDUs installed in your server room or data center.

  • Page 644: Adding Pdus To Power Iq Management

    5. Enter data in Custom Field 1 and Custom Field 2. Optional. The labels may have been changed in Power IQ to identify these fields. 6. If the PDU is a Raritan PX, enter a valid Username and Password for the PDU in the PDU Administrative Credentials section. Re-enter the password in the Password Confirm field.
  • Page 645 Appendix J: Integration  noAuthNoPriv - No Authentication Passkey, No Encoding Passkey  authNoPriv - Authentication Passkey, No Encoding Passkey  authPriv - Authentication Passkey, Encoding Passkey a. Depending on the Authorization Level selected, you must enter additional credentials for Authorization and Privacy. b.

  • Page 646: Dominion Kx Ii Configuration

    Appendix J: Integration Dominion KX II Configuration Raritan PX2, PX3 or PX3TS series can be connected to the Raritan's Dominion KX II device (a digital KVM switch) to provide one more alternative of power management. Note that this integration requires the following firmware versions: ...
  • Page 647 Note: PX rack PDUs (power strips) can be named in the PX as well as in KX II and LX. Once a Raritan remote rack PDU is connected to the KX II or LX, it will appear on the Port Configuration page. Click on the power port name on that page to access it.
  • Page 648 Appendix J: Integration 3. Click OK.
  • Page 649 Port Access page. To use this feature, you will need:  Raritan remote rack PDU(s)  Power CIMs (D2CIM-PWR) To make power associations (associate rack PDU outlets to...
  • Page 650 Appendix J: Integration Removing Power Associations When disconnecting target servers and/or rack PDUs from the device, all power associations should first be deleted. When a target has been associated with a rack PDU and the target is removed from the device, the power association remains.

  • Page 651: Dominion Ksx Ii Or Sx Configuration

    Overview The KSX II allows you to control Raritan PX and RPC series rack PDU (power strip) outlets. Once a PX or RPC series is setup and then attached to the KSX II, the rack PDU and its outlets can be controlled from the Powerstrip page in the KSX II interface.
  • Page 652 Appendix J: Integration Model  Temperature  Current Amps  Maximum Amps  Voltage  Power in Watts  Power in Volts Ampere   Outlet Display Information: Name - Named assigned to the outlet when it was configured.  State - On or Off status of the outlet ...
  • Page 653 Appendix J: Integration Configuring KSX II Ports The Port Configuration page displays a list of the KSX II ports. Ports connected to KVM target servers (blades and standard servers) and rack PDUs (power strips) are displayed in blue, and can be edited. If a KSX II port has no CIM connected or is connected to a CIM with no name, a default port name of Dominion_ is assigned to the port.
  • Page 654 Appendix J: Integration  DCIM - Dominion CIM  TierDevice - Tier device  Not Available - No CIM connected  PCIM - Paragon CIM  PowerStrip (rack PDU) - Power strip connected  Dual - VM - Virtual media CIM (D2CIM-VUSB and D2CIM-DVUSB) ...
  • Page 655 Appendix J: Integration Power Control To turn an outlet on: 1. Click the Power menu to access the Powerstrip page. 2. From the Powerstrip drop-down, select the PX rack PDU (power strip) you want to turn on. 3. Click Refresh to view the power controls. 4.

  • Page 656: Dominion Sx

    Appendix J: Integration To cycle the power of an outlet: 1. Click Cycle. The Power Cycle Port dialog opens. 2. Click OK. The outlet will then cycle (note that this may take a few seconds). 3. Once the cycling is complete the dialog will open. Click OK to close the dialog.
  • Page 657 Appendix J: Integration 2. Click Add. The Power Strip Configuration screen appears. 3. Type a name and description in the Name and Description fields. 4. Select the number of outlets from the Number of Outlets drop-down menu. 5. Type the port number in the Port field. 6.
  • Page 658 Appendix J: Integration Power Control 1. Choose Power Control > Power Strip Power Control. The Outlet Control screen appears. 2. Check the box of outlet number you wish to control, and click On/Off buttons to power on/off the selected outlet(s). 3.

  • Page 659: Dctrack

    2. A status box appears, displaying details of the controlled PX, including power state of each outlet on the device. dcTrack dcTrack is a Raritan product that allows you to manage the data center. ® You can use dcTrack to: ...

  • Page 660: Dctrack Overview

    Change Control workflow process and work in Request Bypass so requests are processed immediately. dcTrack can be used as a standalone product or integrated with ® Raritan's Power IQ for power ® http://www.raritan.com/products/dcim-software/power-iq and environmental monitoring. Adding the PX to dcTrack Management The PX is categorized as a power item in dcTrack.
  • Page 661 Appendix J: Integration 2. Launch dcTrack to import the spreadsheet file.

  • Page 662: Appendix K Additional Px Information

    IT equipment to the Raritan PDUs, including:  SecureLock outlets and cords ™  Button-type locking outlets Note that NOT all Raritan PDUs are implemented with any of the above locking outlets.

  • Page 663: Securelock™ Outlets And Cords

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

  • Page 664: Button-Type Locking Outlets

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

  • Page 665: Unbalanced Current Calculation

    Appendix K: Additional PX Information 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 = (L1+L2+L3) / 3 2.

  • Page 666: Altitude Correction Factors

    100 * (0.1837) = 18% Altitude Correction Factors If a Raritan differential air pressure sensor is attached to your device, the altitude you enter for the device can serve as an altitude correction factor. That is, the reading of the differential air pressure sensor will be multiplied by the correction factor to get a correct reading.

  • Page 667: Data For Btu Calculation

    PX2-4000 PX3-4000 PX2-5000 PX3-5000 Raritan Training Website Raritan offers free training materials for various Raritan products on the http://www.raritantraining.com. The Raritan Raritan training website products introduced on this website include the intelligent PDU, dcTrack ® Power IQ, KVM, EMX, BCM and CommandCenter Secure Gateway (CC-SG).

  • Page 668: Truncated Data In The Web Interface

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

  • Page 669: Sensor Threshold Settings

    Appendix K: Additional PX Information Sensor Threshold Settings This section explains the thresholds settings in a threshold setup dialog for a numeric internal or external sensor.

  • Page 670: Thresholds And Sensor States

    Appendix K: Additional PX Information Thresholds and Sensor States A numeric sensor has four threshold settings: Lower Critical, Lower Warning, Upper Warning and Upper Critical. The threshold settings determine how many sensor states are available for a certain sensor and the range of each sensor state. The diagram below shows how each threshold relates to each state.
  • Page 671 Appendix K: Additional PX Information  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.  When a sensor has all thresholds enabled, 5 sensor states are available: normal, above upper warning, above upper critical, below lower warning, and below lower critical.

  • Page 672: To Assert" And Assertion Timeout

    Appendix K: Additional PX Information "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. Assert a state: To assert a state is to announce a "worse" new state. Below are bad state changes that cause the PX to assert.
  • Page 673 Appendix K: Additional PX Information 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 instructs the PX to send notifications for assertion events, setting the "Assertion Timeout"...

  • Page 674: To De-Assert" And Deassertion Hysteresis

    Appendix K: Additional PX Information "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.
  • Page 675 Appendix K: Additional PX Information 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 that sensor's reading hits the pre-determined "deassertion"...

  • Page 676: Ways To Probe Existing User Profiles

    Appendix K: Additional PX Information 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 Celsius, moving from the "above upper warning"...
  • Page 677 Index Applicable Models • xvii Assertion Timeout Example for Temperature Sensors • 652 1U and 2U Port Locations • 60 Asset Management • 295 1U Products • 2 Asset Management Commands • 482 Asset Sensor Information • 568 Asset Sensor Management • 483 Asset Sensor Settings •...

  • Page 678: Index

    Index Changing an Outlet's Default State • 436 Checking the Internal Beeper State • 67, 91, Changing Default Thresholds • xx, 285, 287 Changing HTTP(S) Settings • 128, 163 Circuit Breaker Orientation Limitation • 4, 6, 7, Changing Measurement Units • 447, 450 Changing Modbus/TCP Settings •...
  • Page 679 Deleting Role-Based Access Control Rules • 43, 139, 149, 295 Connecting the PDU to a Power Source • 16 Derating a Raritan Product • 509 Connecting the PX to a Computer • 18, 549, Describing the Sensor or Actuator's Location •...
  • Page 680 Index Displaying PDU Information • 113 Enabling or Disabling Peripheral Device Auto Displaying the Asset Sensor Information • 299 Management • 387 Displaying the RCM Current • xxi, 580 Enabling or Disabling SNMP v1/v2c • 408 Dominion KSX II • 630 Enabling or Disabling SNMP v3 •...
  • Page 681 Index Example - Outlet Naming • 437 Example 4 - Combination of Upper Critical, Example - Ping Command • 505 Upper Warning and Lower Warning Settings Example - Power Cycling Specific Outlets • • 492 Example 4 - In-Depth PDU Information • 378 Example - Server Settings Changed •...
  • Page 682 Index Identifying Environmental Sensors and Logout Button • 104 Actuators • 278, 279, 282 Lowercase Character Requirement • 426 Identifying Sensor or Actuator Channels • 281 Idle Timeout • 424 Initial Network Configuration via CLI • 22, 103, MAC Address • 563, 641 549, 550 Main Menu •...
  • Page 683 Index Monitoring Overcurrent Protectors • 212 Outlet Pole Sensor Threshold Information • Monitoring Server Accessibility • 273 Monitoring the Inlet • 211 Outlet Relay Behavior in Latching and Monitoring the LHX/SHX Device • 315, 319 Non-Latching Mode • 193 Monitoring Total Active Energy or Power • xix, Outlet Sensor Threshold Information •...
  • Page 684 Index PX3-4000 Series • 58 Resetting the Button-Type Circuit Breaker • 86 PX3-5000 Series • 58 Resetting the Handle-Type Circuit Breaker • Resetting the PX • 500 Resetting to Factory Defaults • 85, 502, 549 Querying Available Parameters for a Resizing a Dialog •...
  • Page 685 Index Server Reachability Configuration Commands Setting the HTTPS Port • 406 • 476 Setting the Initialization Delay • 193, 203, 384 Server Reachability Information • 373 Setting the Inrush Guard Delay • 204 Server Reachability Information for a Specific Setting the Inrush Guard Delay Time • 383 Server •...
  • Page 686 Index Setting the Z Coordinate Format • 285 States of Managed Actuators • 76, 293 Setting the Z Coordinate Format for States of Managed Sensors • 66, 76, 290 Environmental Sensors • 386, 460, 476 Static Route Examples • 123, 124, 126 Setting Thresholds for Multiple Sensors •...
  • Page 687 Zero U Products • 1 User Blocking • 424 User Configuration Commands • 439 User Management • 154 Using a Raritan Y Cable • 36 Using an Optional PX Sensor Hub • 35 Using Default Thresholds • 461 Using SNMP • 325, 330 Using the CLI Command •...
  • Page 688 For CommandCenter Secure Gateway: Press 6, then Press 2 Phone: +31-10-2844040 Fax: 732-764-8887 Email: tech.europe@raritan.com Email for CommandCenter NOC: tech-ccnoc@raritan.com Email for all other products: tech@raritan.com United Kingdom Monday - Friday 8:30 a.m. to 5 p.m. GMT China Phone +44(0)20-7090-1390...

This manual is also suitable for:

Px3-5000 seriesPx3-3000 series

Table of Contents