1. Manuals
  2. Brands
  3. Raritan Manuals
  4. Power distribution unit
  5. PX2-1000 SERIES
  6. User manual

Raritan PX2-1000 User Manual

Px2-1000 series; px2-2000 series
Hide thumbs Also See for PX2-1000:
1
2
3
4
5
Table Of Contents
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
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
PX2-1000/2000 Series
User Guide
Release 3.2.10
Copyright © 2016 Raritan, Inc.
DPX2-1000-0M-v3.2.10-E
March 2016
255-80-6105-00

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PX2-1000 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Raritan PX2-1000

Summary of Contents for Raritan PX2-1000

  • Page 1 PX2-1000/2000 Series User Guide Release 3.2.10 Copyright © 2016 Raritan, Inc. DPX2-1000-0M-v3.2.10-E March 2016 255-80-6105-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 2016 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 What's New in the PX User Guide xviii Chapter 1 Introduction Product Models ..........................1 Package Contents.......................... 1 Zero U Products........................1 1U Products ......................... 2 2U Products ......................... 2 APIPA and Link-Local Addressing....................2 Chapter 2 Rack-Mounting the PDU Rackmount Safety Guidelines .......................
  • Page 7 Contents Preparing the Installation Site....................14 Checking the Branch Circuit Rating...................15 Filling Out the Equipment Setup Worksheet ..............15 Installing Cable Retention Clips on the Inlet (Optional) ...............15 Connecting the PDU to a Power Source ..................16 Configuring the PX........................17 Connecting the PX to a Computer..................18 Installing the USB-to-Serial Driver (Optional)..............19 Connecting the PX to Your Network..................20 Initial Network Configuration via CLI .................22...
  • Page 8 Contents Fuse Replacement on 1U Models ..................86 Beeper ............................88 Chapter 6 Using the Web Interface Supported Web Browsers......................89 Logging in to the Web Interface....................90 Login ..........................90 Changing Your Password....................93 Remembering User Names and Passwords ..............93 Logout ............................93 Introduction to the Web Interface....................
  • Page 9 Contents Access Security Control......................159 Forcing HTTPS Encryption....................159 Configuring the Firewall....................159 Setting Up User Login Controls ..................166 Setting Up Role-Based Access Control Rules ..............170 Setting Up a TLS Certificate ......................174 Certificate Signing Request .....................175 Creating a Self-Signed Certificate ...................177 Installing Existing Key and Certificate Files..............179 Downloading Key and Certificate Files................179 Setting Up External Authentication ....................180 Gathering the External Authentication Information............180...
  • Page 10 Contents Managing Event Logging ......................264 Viewing the Local Event Log ...................264 Viewing the Wireless LAN Diagnostic Log ..............265 Viewing Connected Users ......................266 Monitoring Server Accessibility....................267 Adding IT Devices for Ping Monitoring ................267 Editing Ping Monitoring Settings..................270 Deleting Ping Monitoring Settings ...................270 Checking Server Monitoring States .................271 Environmental Sensors and Actuators ..................271 Identifying Environmental Sensors and Actuators............272...
  • Page 11 Contents Chapter 7 Using SNMP Enabling SNMP..........................323 Configuring Users for Encrypted SNMP v3 ................324 Configuring SNMP Notifications ....................325 SNMPv2c Notifications ....................326 SNMPv3 Notifications......................328 SNMP Gets and Sets.........................330 The PX MIB ........................331 A Note about Enabling Thresholds..................334 Chapter 8 Using the Command Line Interface About the Interface........................335 Logging in to CLI........................336 With HyperTerminal......................336...
  • Page 12 Contents Event Log.........................364 Wireless LAN Diagnostic Log ..................365 Server Reachability Information ..................365 Command History......................367 History Buffer Length.......................367 Reliability Data.........................367 Reliability Error Log ......................367 Examples .........................368 Clearing Information........................370 Clearing Event Log ......................370 Clearing WLAN Log......................371 Configuring the PX Device and Network ...................371 Entering Configuration Mode...................371 Quitting Configuration Mode....................372 PDU Configuration Commands ..................372...
  • Page 13 Contents Network Troubleshooting......................492 Entering Diagnostic Mode ....................492 Quitting Diagnostic Mode ....................493 Diagnostic Commands ....................493 Retrieving Previous Commands ....................495 Automatically Completing a Command..................495 Logging out of CLI........................496 Appendix A Specifications Maximum Ambient Operating Temperature ................497 Serial RS-232 Port Pinouts......................497 Sensor RJ-12 Port Pinouts ......................497 Feature RJ-45 Port Pinouts .......................498 Appendix B Equipment Setup Worksheet Appendix C Configuration or Firmware Upgrade with a USB Drive...
  • Page 14 Contents Firmware Upgrade via USB .......................513 Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ..................514 TFTP Requirements........................515 DHCP IPv4 Configuration in Windows..................516 DHCP IPv6 Configuration in Windows..................526 DHCP IPv4 Configuration in Linux.....................533 DHCP IPv6 Configuration in Linux.....................535 Appendix E Resetting to Factory Defaults Using the Reset Button ......................537 Using the CLI Command ......................538...
  • Page 15 Altitude Correction Factors ......................601 Data for BTU Calculation ......................602 Ways to Probe Existing User Profiles ..................603 Truncated Data in the Web Interface..................603 Raritan Training Website ......................604 Appendix K Integration Dominion KX II / III Configuration ....................605 Configuring Rack PDU Targets ..................606 Turning Outlets On/Off and Cycling Power ..............609...
  • Page 16 PX2-1nnn series  PX2-2nnn series In this User Guide, PX2-1nnn is called PX2-1000, and PX2-2nnn is called PX2-2000 for convenience. Note: For information on other PX2 or PX3 models, see their respective Online Help or User Guide on the Raritan website's Support page (http://www.raritan.com/support/).
  • Page 17 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-45 PX3 phase I display series Dot-matrix LCD RJ-45 PX3 phase II display series...
  • Page 18 What's New in the PX User Guide The following sections have changed or information has been added to the PX User Guide based on enhancements and changes to the equipment and/or user documentation. (on page 2) APIPA and Link-Local Addressing (on page 17) Configuring the PX (on page 18)
  • Page 19 What's New in the PX User Guide (on page 371) Clearing WLAN Log (on page Enabling or Disabling Peripheral Device Auto Management 378) (on page 399) Determining the SSH Authentication Method (on page 406) Customizing the Date and Time (on page 446) All Privileges (on page 481) Setting the Baud Rates...

  • Page 20: 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 21: 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 22 Chapter 1: Introduction  The PX previously obtained an IP address from the DHCP server, but the lease of this IP address has expired, and the lease cannot be renewed, or no new IP address can be obtained. Link-local addressing: ...

  • Page 23: Chapter 2 Rack-Mounting The Pdu

    Rack-Mounting the PDU Chapter 2 This chapter describes how to rack mount a PX device. To mount a Zero U PX2-1000 series PDU, you can use either two buttons or L-brackets that Raritan provided. In This Chapter Rackmount Safety Guidelines ..............4 Circuit Breaker Orientation Limitation............5...

  • Page 24: Circuit Breaker Orientation Limitation

    Chapter 2: Rack-Mounting the PDU Circuit Breaker Orientation Limitation Usually a PDU can be mounted in any orientation. However, when mounting a PDU with circuit breakers, you must obey these rules:  Circuit breakers CANNOT face down. For example, do not horizontally mount a Zero U PDU with circuit breakers on the ceiling.
  • Page 25 Chapter 2: Rack-Mounting the PDU 2. Secure the baseplates in place. Use the included L-shaped hex key to loosen the hex socket screws until the baseplate is "slightly" fastened. 3. Align the L-brackets with the baseplates so that the five screw-holes on the baseplates line up through the L-bracket's slots.

  • Page 26: Mounting Zero U Models Using Button Mount

    Chapter 2: Rack-Mounting the PDU Mounting Zero U Models Using Button Mount If your PDU has circuit breakers implemented, read Circuit Breaker (on page 5) before mounting it. Orientation Limitation To mount Zero-U models using button mount: 1. Align the baseplates on the rear of the PX device. Leave at least 24 inches between the baseplates for stability.

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

    Chapter 2: Rack-Mounting the PDU 5. Loosen the hex socket screws until the mounting buttons are secured in their position. 6. Ensure that both buttons can engage their mounting holes simultaneously. 7. Press the PX device forward, pushing the mounting buttons through the mounting holes, then letting the device drop about 5/8".
  • Page 28 Chapter 2: Rack-Mounting the PDU 3. Align the claw-foot brackets with the baseplates so that the five screw-holes on the baseplates line up through the bracket's slots. The rackmount side of brackets should face either the left or right side of the PX device. 4.

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

    Chapter 2: Rack-Mounting the PDU 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 5) before mounting it. Orientation Limitation To mount Zero U models using two buttons: 1.

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

    Chapter 2: Rack-Mounting the PDU 4. Screw a button in the screw hole near the top. The recommended torque for the button is 1.96 N·m (20 kgf·cm). 5. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously.

  • Page 31: Mounting 1U Or 2U Models

    Chapter 2: Rack-Mounting the PDU 2. Screw the L-bracket to the device and ensure the bracket is fastened securely. 3. Repeat Steps 1 to 2 to screw another L-bracket to the bottom of the device. 4. After both L-brackets are installed, you can choose either of the following ways to mount the device in the rack.
  • Page 32 Chapter 2: Rack-Mounting the PDU 2. Insert the cable-support bar into rackmount brackets. 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners.

  • Page 33: Chapter 3 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 34: 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 497). 2. Allow sufficient space around the PX device for cabling and outlet connections.

  • Page 35: Connecting The Pdu To A Power Source

    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 Connecting the PDU to a Power Source 1.

  • Page 36: Configuring The Px

    Chapter 3: Installation and Configuration Configuring the PX You can initially configure the PX by connecting it to a computer, or to a TCP/IP network that supports DHCP. Configuration using a connected computer: 1. Connect the PX to a computer. See Connecting the PX to a (on page 18).

  • Page 37: Connecting The Px To A Computer

    Chapter 3: Installation and Configuration Connecting the PX to a Computer The PX can be connected to a computer for configuration via one of the following ports.  ETHERNET port (female)  USB-B port (male)  RS-232 serial port (male) Zero U models: To use the command line interface (CLI) for configuration, establish an RS-232 or USB connection.

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

    USB-to-serial driver named "Dominion PX2 Serial Console" is required for Microsoft Windows operating systems. ® ® Download the USB serial console driver from the Raritan website's (http://www.raritan.com/support/). The driver contains Support page the dominion-serial.inf, dominion-serial.cat and dominion-serial-setup-<n>.exe files. Note: <n> in the filename of "dominion-serial-setup-<n>.exe" represents the file's version number.

  • Page 39: Connecting The Px To Your Network

    Chapter 3: Installation and Configuration 3. Select the option of driver installation from a specific location, and then specify the location where both dominion-serial.inf and dominion-serial.cat are stored. Note: If any Windows security warning appears, accept it to continue the installation. 4.
  • Page 40 LAN adapters. USB Wireless LAN Adapters The PX supports the following USB Wi-Fi LAN adapters. Wi-Fi LAN adapters Supported 802.11 protocols Proxim Orinoco 8494 A/B/G Zyxel NWD271N Edimax EW-7722UnD A/B/G/N TP-Link TL-WDN3200 v1 A/B/G/N Raritan USB WIFI A/B/G/N...

  • Page 41: Initial Network Configuration Via Cli

    Chapter 3: Installation and Configuration 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 42 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, change or ignore it. ...
  • Page 43 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 44 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 45 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 46 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 47: Bulk Configuration Methods

    Chapter 3: Installation and Configuration Tip: You can type "show network wireless" to display a shortened version of wireless settings. 11. If all are correct, type exit to log out of the PX. If any are incorrect, repeat Steps 7 to 10 to change network settings. The IP address configured may take seconds to take effect.

  • Page 48: Cascading The Px Via Usb

    Chapter 3: Installation and Configuration Cascading the PX via USB You can use USB cables to cascade up to eight Raritan devices. All devices in the USB-cascading chain share the Ethernet connectivity. Different Raritan models can be cascaded as long as they are running an appropriate firmware.
  • Page 49 Chapter 3: Installation and Configuration 4. Connect the USB-A port of the master device to the USB-B port of an additional PX via a USB cable. This additional device is Slave 1. 5. Connect Slave 1's USB-A port to the USB-B port of an additional PX via a USB cable.
  • Page 50 Identifying Cascaded Devices (on page 108). 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. See the USB-Cascading Solution Guide on Raritan website's Support page...

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

    Chapter 3: Installation and Configuration Installing Cable Retention Clips on Outlets (Optional) If your PX device is designed to use a cable retention clip, install the clip before connecting a power cord. A cable retention clip prevents the connected power cord from coming loose or falling off. The use of cable retention clips is highly recommended for regions with high seismic activities, and environments where shocks and vibrations are expected.
  • Page 52 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 53: Chapter 4 Connecting External Equipment (Optional)

    Connecting External Equipment Chapter 4 (Optional) More features are available if you connect Raritan's or third-party external equipment to your PX. In This Chapter Connecting Environmental Sensor Packages .........34 Connecting Asset Management Sensors ..........55 Connecting a Logitech Webcam .............69 Connecting a GSM Modem ..............70 Connecting an Analog Modem ..............70...

  • Page 54: Dpx Sensor Packages

    PX. To connect a DPX differential air pressure sensor: 1. Plug one end of a Raritan-provided phone cable into the IN port of a differential air pressure sensor. 2. Plug the other end of this phone cable into the RJ-12 SENSOR port...
  • Page 55 One DPX sensor package (optional) Using an Optional DPX-ENVHUB4 Sensor Hub Optionally, you can connect a Raritan DPX-ENVHUB4 sensor hub to the PX. This allows you to connect up to four DPX sensor packages to the PX via the hub.
  • Page 56 Chapter 4: Connecting External Equipment (Optional) This diagram illustrates a configuration with a sensor hub connected. The PX device Raritan-provided phone cable DPX-ENVHUB4 sensor hub DPX sensor packages...
  • Page 57 Chapter 4: Connecting External Equipment (Optional) Using an Optional DPX-ENVHUB2 cable A Raritan DPX-ENVHUB2 cable doubles the number of connected environmental sensors per SENSOR port. This cable supports DPX sensor packages only. Do NOT connect DPX2, DPX3 or DX sensor packages to it.
  • Page 58 Chapter 4: Connecting External Equipment (Optional) 2. The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports. 3. Repeat the above steps if there are additional SENSOR ports on your PX.
  • Page 59 Sensor Connection Restrictions:  Connect a DPX sensor package to the PX using the sensor cable pre-installed (or provided) by Raritan. You MUST NOT extend or modify the sensor cable's length by using any tool other than the Raritan's sensor hubs.

  • Page 60: Dpx2 Sensor Packages

    RJ-12 connector and one to three head connectors. You have to connect DPX2 sensor packages to the sensor cable. For more information on DPX2 sensor packages, access the Environmental Sensors Guide or Online Help on Raritan website's (http://www.raritan.com/support/). Support page Item...
  • Page 61 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 package, the sensor packages following the free head connector(s) on the same cable do NOT work properly.

  • Page 62: Dpx3 Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) OR you can directly connect the DPX2 sensor package to a DX sensor chain without using any RJ-12 to RJ-45 adapter. See (on page 47). Connecting a DPX2 Sensor Package to DX Note: If your PX has "two" RJ-12 SENSOR ports, see Guidelines for PX with Two Sensor Ports (on page 54) for sensor connection restrictions.
  • Page 63 Chapter 4: Connecting External Equipment (Optional) Repeat the same steps to cascade more DPX3 sensor packages. 3. Connect the first DPX3 sensor package to the PX.  Plug the adapter cable's RJ-12 connector into the RJ-12 SENSOR port on the PX. Note: If your PX has "two"...
  • Page 64 Chapter 4: Connecting External Equipment (Optional) When connecting a DPX2 sensor package containing two DPX2 sensors: A maximum of ten DPX3 sensor packages can be cascaded because 12-2=10. When connecting a DPX2 sensor package containing one DPX2 sensor: A maximum of eleven DPX3 sensor packages can be cascaded because 12-1=11.

  • Page 65: Dx Sensor Packages

    Most DX sensor packages contain terminals for connecting detectors or actuators. For information on connecting actuators or detectors to DX terminals, refer to the Environmental Sensors Guide or Online Help on Raritan website's (http://www.raritan.com/support/). Support page You can cascade up to 12 DX sensor packages.
  • Page 66 Chapter 4: Connecting External Equipment (Optional) 2. If you want to cascade DX packages, get an additional standard network patch cable (CAT5e or higher) and then: a. Plug one end of the cable into the remaining RJ-45 port on the prior DX package.

  • Page 67: Using An Optional Dpx3-Envhub4 Sensor Hub

    A maximum of eleven DX sensor packages can be cascaded because 12-1=11. Using an Optional DPX3-ENVHUB4 Sensor Hub A Raritan DPX3-ENVHUB4 sensor hub is physically and functionally similar to the DPX-ENVHUB4 sensor hub, which increases the number of sensor ports for the PX, except for the following differences: ...
  • Page 68 Chapter 4: Connecting External Equipment (Optional) 2. Connect the Raritan sensor packages to any of the four OUT ports on the hub.  An RJ-12 to RJ-45 adapter is required for connecting a DPX or DPX2 sensor package to the hub.

  • Page 69: Mixing Diverse Sensor Types

    Chapter 4: Connecting External Equipment (Optional) Mixing Diverse Sensor Types You can mix DPX, DPX2, DPX3 and DX sensor packages on one PX according to the following sensor combinations. In some scenarios, the DPX3-ENVHUB4 sensor hub is required. The PX does NOT support any other sensor-mixing combinations than those described in this section.
  • Page 70 Chapter 4: Connecting External Equipment (Optional)  An RJ-12 to RJ-45 adapter is recommended to connect a DPX or DPX2 sensor package to DPX3-ENVHUB4.  In the following diagrams, the sensor package in "green" can be replaced by a DPX2 sensor package. The sensor package in "blue" can be one DPX2, DPX3 or DX sensor package.
  • Page 71 Chapter 4: Connecting External Equipment (Optional)
  • Page 72 Chapter 4: Connecting External Equipment (Optional) Mix DPX3 and DX in a sensor chain: Any DX sensor package in a chain can be replaced by a DPX3 sensor package. For example, the following diagram shows a sensor chain comprising both DX and DPX3 sensor packages. The total number of sensor packages in this chain cannot exceed 12.

  • Page 73: Guidelines For Px With Two Sensor Ports

    Chapter 4: Connecting External Equipment (Optional) Guidelines for PX with Two Sensor Ports You CANNOT simultaneously connect Raritan environmental sensor packages to both sensor ports of the PX models with "two" sensor ports, unless only DPX sensor packages are connected.

  • Page 74: Connecting Asset Management Sensors

    Raritan asset sensors: An asset sensor transmits the asset management tag's 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 IT device.

  • Page 75: Combining Regular 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 76 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 77: Introduction To Asset Tags

    The FEATURE port of PX2 supports 5 volts of power only, which is insufficient for connecting an asset sensor at a distance between 1 and 10 meters. Therefore, the use of a Raritan X cable is required for PX2 to connect an asset sensor whose cabling distance is over 1 meter.
  • Page 78 5th rack unit. 4. Connect the MASTER asset sensor's RJ-45 connector to the male RJ-45 connector at the longer end of the Raritan X cable. 5. Plug the male RJ-12 phone connector at the shorter end of the X cable into the SENSOR port on the PX2.

  • Page 79: 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 it to a tag port on the regular or composite asset sensor.
  • Page 80 Chapter 4: Connecting External Equipment (Optional) Note: A tag connector cable has a unique barcode, which is displayed in the PX device's web interface for identifying each blade extension strip where it is connected. Blade extension strip with 16 tag ports Mylar section with the adhesive tape Tag ports Cable socket(s) for connecting the tag...
  • Page 81 Chapter 4: Connecting External Equipment (Optional) 2. Move the blade extension strip toward the bottom of the blade chassis until its mylar section is fully under the chassis, and verify that the blade extension strip does not fall off easily. If necessary, you may use the adhesive tape in the back of the mylar section to help fix the strip in place.

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

    Chapter 4: Connecting External Equipment (Optional) 5. Plug the tag connector of the blade extension strip into the closest tag port of the regular or composite asset sensor on the rack. 6. Repeat the above steps to connect additional blade extension strips. Up to 128 asset tags on blade extension strips are supported per FEATURE port.
  • Page 83 Chapter 4: Connecting External Equipment (Optional) Two RJ-45 connectors Tag ports To connect composite asset sensors to the PX device: 1. Connect a composite asset sensor to the PX device via a standard network patch cable (CAT5e or higher). a. Connect one end of the cable to the RJ-45 port labeled "Input" on the composite asset sensor.
  • Page 84 The maximum cable length between composite asset sensors is 2 meters, but the total cable length cannot exceed 10 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 are supported.
  • Page 85 Chapter 4: Connecting External Equipment (Optional) Tip: To increase the maximum number of composite asset sensors attached to a Raritan PX2 PDU or EMX2-111, you can use Raritan's X cable to enhance the power supply to the asset sensor chain. See...
  • Page 86 Chapter 4: Connecting External Equipment (Optional) 2. Plug the male phone connector of the X cable into the RJ-12 SENSOR port of the PX device. This step is required for enhancing the power supply to asset sensors. 3. Plug the male RJ-45 connector at the longer end of the X cable into the RJ-45 port labeled "Input"...
  • Page 87 Chapter 4: Connecting External Equipment (Optional) 4. Connect any Raritan environmental sensor package or sensor hub to the female RJ-12 sensor port of the X cable if environmental sensor packages are needed. Note that a DX or DPX3 sensor requires an RJ-12 to RJ-45 adapter to connect the X cable.

  • Page 88: 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 89: 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: 1.

  • Page 90: Connecting An External Beeper

    Chapter 4: Connecting External Equipment (Optional) You need to enable the modem dial-in support to take advantage of this feature, see (on page 134). Configuring the Serial Port Connecting an External Beeper The PX supports the use of an external beeper for audio alarms. External beepers that are supported include but may not be limited to the following: ...
  • Page 91 Chapter 4: Connecting External Equipment (Optional) (on page 309) Managing the Schroff LHX/SHX Heat Exchanger for enabling the support of the LHX/SHX heat exchanger.

  • Page 92: Chapter 5 Using The Pdu

     Reset button Power Cord Most of Raritan PDUs come with an installed power cord, which is ready to be plugged into an appropriate receptacle for receiving electricity. Such devices cannot be rewired by the user. Connect each PX to an appropriately rated branch circuit. See the label or nameplate affixed to your PX for appropriate input ratings or range of ratings.

  • Page 93: Connection Ports

    Chapter 5: Using the PDU PX2-1000 Series These models are NOT outlet-switching capable so all outlets are always in the ON state. Outlet LEDs are not available. PX2-2000 Series These models are outlet-switching capable. A small LED is adjacent to each outlet to indicate the state of the relay board.
  • Page 94 Cascading the PX devices for sharing a network connection. FEATURE Connection to one of the following devices:  A Raritan access product, such as Dominion KX III KVM switch, with the use of a power CIM.  A Schroff LHX-20, SHX-30 or LHX-40 device, using an RJ-45 to ®...
  • Page 95 (RJ-12)  Raritan's environmental sensor package(s).  Raritan's sensor hub, which expands the number of a sensor port to four ports. ETHERNET Connecting the PX to your company's network. Connect a standard Cat5e/6 UTP cable to this port and connect the other end to your network.

  • Page 96: Led Display

    Chapter 5: Using the PDU LED Display The LED display is located on the side where outlets are available. These diagrams show the LED display on different types of PDUs. Note that the LED display might slightly vary according to the PDU you purchased.
  • Page 97 Chapter 5: Using the PDU The LED display consists of:  A row displaying three digits  A row displaying two digits  Up and Down buttons  Five LEDs for measurement units A Zero U model can detect its own orientation through the built-in tilt sensor and automatically changes the direction of the alphanumeric digits shown on the LED display for readability.
  • Page 98 Chapter 5: Using the PDU LEDs for Measurement Units Five small LED indicators are on the LED display: four measurement units LEDs and one Sensor LED. The measurement units vary according to the readings that appear in the three-digit row. They are: ...
  • Page 99 Chapter 5: Using the PDU  AP: This indicates the selected inlet's active power.  UL: This represents the selected inlet or outlet's Unbalanced Load, which is only available for a three-phase PDU.  ix: This refers to the selected inlet on a multi-inlet PDU, where x is the inlet number.
  • Page 100 Chapter 5: Using the PDU Manual Mode You can press the Up or Down button to enter the Manual Mode so that a particular line or circuit breaker can be selected to show specific readings. In addition, you can select a particular inlet if your PDU has more than one inlet.

  • Page 101: Reset Button

    Chapter 5: Using the PDU  When the active power is displayed, the POWER(kW) LED is lit. Note: The LED display returns to the Automatic Mode after 20 seconds elapse since the last time any button was pressed. Reset Button The reset button is located inside the small hole near the display panel on the PDU.

  • Page 102: Resetting The Button-Type Circuit Breaker

    Chapter 5: Using the PDU Resetting the Button-Type Circuit Breaker Your button-type circuit breakers may look slightly different from the images shown in this section, but the reset procedure remains the same. To reset the button-type breakers: 1. Locate the breaker whose ON button is up, indicating that the breaker has tripped.

  • Page 103: Fuse

    Chapter 5: Using the PDU 3. Examine your PX and the connected equipment to remove or resolve the cause that results in the overload or short circuit. This step is required, or you cannot proceed with the next step. 4. Pull up the operating handle until the colorful rectangle or triangle turns RED.

  • Page 104: Fuse Replacement On Zero U Models

    Chapter 5: Using the PDU Fuse Replacement on Zero U Models This section only applies to a Zero U PDU with "replaceable" fuses. To replace a fuse on the Zero U model: 1. Lift the hinged cover over the fuse. 2.

  • Page 105: Fuse Replacement On 1U Models

    Chapter 5: Using the PDU 4. Take the fuse out of the holder. 5. Insert a new fuse into the holder. There is no orientation limit for fuse insertion. 6. Close the fuse holder and the hinged cover in a reverse order. Fuse Replacement on 1U Models On the 1U model, a fuse is installed in a fuse knob, which fits into the PDU's fuse carrier.
  • Page 106 Chapter 5: Using the PDU 3. Remove the original fuse from this knob, and insert either end of a new one into the knob. Make sure the new fuse's rating is the same as the original one. Number Description Fuse knob Fuse 4.

  • Page 107: Beeper

    Chapter 5: Using the PDU 6. Connect the PDU's power cord to the power source and verify that the corresponding fuse LED is lit, indicating that the fuse works properly. Beeper The PX includes an internal beeper to issue an audible alarm for an overcurrent protector which is open.

  • Page 108: 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................89 Logging in to the Web Interface ..............90 Logout......................93 Introduction to the Web Interface ............94 Viewing the Dashboard .................104 Device Management................106 User Management .................150 Setting Up Roles..................156...

  • Page 109: Logging In To The Web Interface

    The first time you log in to the PX, use the default user name (admin) and password (raritan). For details, see the Quick Setup Guide accompanying the product. After successfully logging in, you can create user profiles for your other users.
  • Page 110 Chapter 6: Using the Web Interface 3. Type your user name in the User Name field, and password in the Password field. Both the user name and password are case sensitive. Note: If needed, click Clear to clear either the inputs or any error message that appears.
  • Page 111 Chapter 6: Using the Web Interface Note: The IP address to access a slave device in the USB-cascading configuration where the port forwarding mode is applied is a combination of the IP address and the port number. See Port Forwarding Examples (on page 140).

  • Page 112: Changing Your Password

    Chapter 6: Using the Web Interface Changing Your Password You must have the Change Own Password permission to change your own password. See (on page 156). Setting Up Roles You must have Administrator Privileges to change other users' passwords. See (on page 154).

  • Page 113: Introduction To The Web Interface

    Chapter 6: Using the Web Interface Close the web browser by clicking the Close button ( ) on the  top-right corner of the browser.  Close the web browser by choosing File > Close, or File > Exit. The command varies according to the version of the browser you use.

  • Page 114: Menus

    Chapter 6: Using the Web Interface Number Web interface element Add Page icon Logout button Data pane * The Setup button is not available on some pages, such as the Dashboard page. For detailed information about these web interface elements, see the sections that follow.
  • Page 115 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 116 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 117: 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 root folder.

  • Page 118: Add Page Icon

    Chapter 6: Using the Web Interface Tip: The presence of the device name and IP address in the status bar indicates the connection to the PX device. If the connection is lost, it shows " " instead. 3. Login name: This is the user name you used to log in to the web interface.

  • Page 119: Data Pane

    Chapter 6: Using the Web Interface The following diagram shows a multi-tab example. 4. With multiple pages opened, you can take these actions:  To switch to one of the opened data pages, click the corresponding tab. If there are too many tabs to be all shown, two arrows ( ) appear at the left and right borders of the pane.
  • Page 120 Chapter 6: Using the Web Interface The Yellow- or Red-Highlighted Sensors When a numeric sensor's reading enters the warning or critical range, the background color of the sensor row turns to yellow or red for alerting you. For a discrete (on/off) sensor, the row changes the background color when the sensor enters the abnormal state.
  • Page 121 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 122 Chapter 6: Using the Web Interface Browser-Defined Shortcut Menu A shortcut menu, which is built in the web browser, may appear when right-clicking anywhere in the PX web interface. The shortcut menu functions are defined by the browser. For example, the Back command on the Internet Explorer (IE) shortcut menu works ®...

  • Page 123: 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 and overcurrent protectors.

  • Page 124: 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 101). 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 125: 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 126: 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 the PDU-specific information: 1. Choose Maintenance > Device Information. 2.
  • Page 127 For information on how to cascade devices using USB cables, see (on page 29). 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 Support page (http://www.raritan.com/support/).
  • Page 128 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 129 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 130 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 131: 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 root folder is my PX.
  • Page 132 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 133 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 later. 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 higher if wireless networking is preferred.
  • Page 134 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 135 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 17). If Configuring the PX necessary, you can modify any network settings later. Selecting the Internet Protocol The PX device supports two types of Internet protocols -- IPv4 and IPv6.
  • Page 136 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 116). Selecting the Internet Protocol To modify IPv4 settings: 1. Choose Device Settings > Network. The Network Configuration dialog appears.
  • Page 137 Chapter 6: Using the Web Interface Option Description mask using the format "IP address/subnet mask."  Next Hop: IP address of the next hop router. (on page 120) for illustrations. Static Route Examples 4. Click OK. Note: The PX supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the PX only uses the primary IPv4 and IPv6 DNS servers.
  • Page 138 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 139 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 140 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 141: 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 142 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 143 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 144 Chapter 6: Using the Web Interface To configure SNMP notification destinations: 1. Click the Notifications tab in the same SNMP dialog. 2. Select the Enabled checkbox. 3. Select an SNMP notification type - SNMP v2c Trap, SNMP v2c Inform, SNMP v3 Trap, and SNMP v3 Inform. 4.
  • Page 145 Chapter 6: Using the Web Interface Changing Telnet Settings You can enable or disable the Telnet access to the command line interface, or change the default TCP port for the Telnet service. To change Telnet service settings: 1. Choose Device Settings > Network Services > Telnet. The Telnet Settings dialog appears.
  • Page 146 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 (multicastDNS). The advertised services are discovered by clients that have implemented DNS-SD and mDNS. The advertised services include the following: ...

  • Page 147: Setting The Date And Time

    Chapter 6: Using the Web Interface 2. Click Yes on the confirmation message to switch off the zero configuration advertising. The feature is disabled and the Service Advertisement checkbox is deselected in the submenu. Setting the Date and Time Set the internal clock on the PX device manually, or link to a Network Time Protocol (NTP) server.
  • Page 148 Chapter 6: Using the Web Interface The PX follows the NTP server sanity check per the IETF RFC. If your PX has problems synchronizing with a Windows NTP server, see (on page 131). Windows NTP Server Synchronization Solution Note: If you are using Sunbird'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 149 Chapter 6: Using the Web Interface  Click , which is adjacent to the year, to show a list of years and months. Select the desired year from the list to the right and click OK. If the list does not show the desired year, click to show additional years.
  • Page 150 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 151: Setting Default Measurement Units

    Chapter 6: Using the Web Interface Setting Default Measurement Units Default measurement units are applied to the PX web and CLI interfaces across all users, including users accessing the device via external authentication servers. Default units apply before users set their own preferred measurement units or the administrator changes preferred units for any user.

  • Page 152: Configuring The Feature Port

    Raritan Computer Interface Module (CIM) for KVM access. See (on page 605). Dominion KX II / III Configuration  Raritan serial access products, including Dominion KSX II, SX or SX II. See (on page 610). Dominion KSX II, SX or SX II Configuration ...

  • Page 153: Configuring The Serial Port

    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  Dominion SX or SX II 4.
  • Page 154 Chapter 6: Using the Web Interface 2. In the "Connected device" field, select an appropriate option to force the serial port to enter the correct state. Options Description Automatic detection The PX automatically detects the device type on the serial port. Select this option unless your PX cannot correctly detect the connected device.

  • Page 155: Setting The Cascading Mode

    Chapter 6: Using the Web Interface Setting the Cascading Mode A maximum of eight PX devices can be cascaded using USB cables and therefore share only one Ethernet connection. See Cascading the PX (on page 29). via USB The Ethernet sharing mode applied to the USB-cascading configuration is either network bridging or port forwarding.
  • Page 156 Chapter 6: Using the Web Interface Return to the same dialog and click the "Protocol to Port Mapping" tab to view the master device's port numbers. For information on accessing each cascaded device in the Port Forwarding mode, see (on page 140). Port Forwarding Examples Overview of the Cascading Modes You must apply a cascading mode to the USB-cascading configuration.
  • Page 157 Chapter 6: Using the Web Interface  "Bridging" mode: As illustrated in the following diagram, the DHCP server communicates with every cascaded device respectively and assigns four different IP addresses accordingly. Each device has one IP address. The way to remotely access each cascaded device is completely the same as accessing a standalone device in the network.
  • Page 158 Chapter 6: Using the Web Interface Port Number Syntax In the Port Forwarding mode, all devices in the USB-cascading configuration share the same IP address. To access any cascaded device, you must assign an appropriate port number to it.  Master device: The port number is either 5NNXX or the standard TCP/UDP port.
  • Page 159  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 160 Chapter 6: Using the Web Interface Protocols Port numbers 50200 TELNET 50300 SNMP 50500 MODBUS 50600 Examples using "5NN00" ports:  To access the master device via HTTPS, the IP address is: https://192.168.84.77:50000/  To access the master device via HTTP, the IP address is: http://192.168.84.77:50100/ ...
  • Page 161 Chapter 6: Using the Web Interface  To access Slave 1 via HTTP, the IP address is: http://192.168.84.77:50101/  To access Slave 1 via SSH, the command is: ssh -p 50201 192.168.84.77 Slave 2 device: Position code for Slave 2 is 02 so each port number is 5NN02 as shown below.

  • Page 162: Setting Data Logging

    60 seconds along with the minimum and maximum measurement values are written to the log. Note that the outlet-level measurement data is NOT available for Raritan models described in this User Guide. Note: The PX device's SNMP agent must be enabled for this feature to work.

  • Page 163: Configuring Smtp Settings

    Chapter 6: Using the Web Interface Configuring SMTP Settings The PX can be configured to send alerts or event messages to a specific administrator by email. To do this, you have to configure the SMTP settings and enter an IP address for your SMTP server and a sender's email address.

  • Page 164: 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 165: 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's DPX differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor. See (on page 601).

  • Page 166: Rebooting The Px Device

    Chapter 6: Using the Web Interface Rebooting the PX Device You can remotely reboot the PX device via the web interface. Resetting the PX does not interrupt the operation of connected servers because there is no loss of power to outlets. Outlets that have been powered on prior to the reset remain powered on and outlets that have been powered off remain powered off during and after the reset.

  • Page 167: Monitoring Total Active Energy Or Power

    Chapter 6: Using the Web Interface Tip: You can also reset the active energy readings of an individual inlet. Resetting Inlet Active Energy Readings (on page 206). Monitoring Total Active Energy or Power This section applies only to multi-inlet models, including PX in-line monitors.

  • Page 168: 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 88). If intended, you can set an event rule to turn on the internal beeper when a specific event occurs.

  • Page 169: User Management

    Chapter 6: Using the Web Interface 3. In the "Domain name" field, type the name of a Cisco EnergyWise domain where the PX belongs. The domain name comprises up to 127 printable ASCII characters. Spaces and asterisks are NOT acceptable. ...
  • Page 170 Chapter 6: Using the Web Interface Field Type this... User Name The name the user enters to log in to the PX.  4 to 32 characters  Case sensitive  Spaces are NOT permitted. Full Name The user's first and last names. Password, ...
  • Page 171 Chapter 6: Using the Web Interface Field Description privacy.  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 172 Chapter 6: Using the Web Interface Field Description Privacy Protocol Click the drop-down arrow and select the desired privacy protocol from the list. Two protocols are available:  DES (default)  AES-128 7. Click the SSH tab to enter the public key if the public key authentication for the SSH service is enabled.

  • Page 173: Modifying A User Profile

    Chapter 6: Using the Web Interface Note: The measurement unit change only applies to the web interface and command line interface. Users can change the measurement units at any time by setting up their own user preferences. See Setting Up Your Preferred Measurement Units (on page 155).

  • Page 174: Setting Up Your Preferred Measurement Units

    Chapter 6: Using the Web Interface 2. Select the user you want to delete by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones. 3. Click Delete. 4. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.

  • Page 175: Setting Up Roles

    - Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration - Change Own Password - Switch Outlet (all outlets) Note: PX2-1000 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 176: 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 177: 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 178: Access Security Control

    Chapter 6: Using the Web Interface Access Security Control The PX provides tools to control access. You can enable the internal firewall, create firewall rules, and create login limitations. Tip: You can also create and install the certificate or set up external authentication servers to control any access.
  • Page 179 Chapter 6: Using the Web Interface 2. To enable the IPv4 firewall, click the IPv4 tab, and select the Enable IPv4 Access Control checkbox. 3. To enable the IPv6 firewall, click the IPv6 tab, and select the Enable IPv6 Access Control checkbox. 4.
  • Page 180 Chapter 6: Using the Web Interface  Accept: Accepts traffic from all IPv6 addresses.  Drop: Discards traffic from all IPv6 addresses, without sending any failure notification to the source host.  Reject: Discards traffic from all IPv6 addresses, and an ICMP message is sent to the source host for failure notification.
  • Page 181 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 182 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. ...
  • Page 183 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 184 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 185: 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 186 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 a number.
  • Page 187 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 188 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 189: 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 190 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 191 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 192 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 193: 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 194: 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 195 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 196: 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 197 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 198: 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 199: 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 200 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: ...

  • Page 201: 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 202 Chapter 6: Using the Web Interface  None 7. Port (None/StartTLS) - The default Port is 389. Either use the standard LDAP TCP port or specify another port. 8. Port (TLS) - The default is 636. Either use the default port or specify another port.
  • Page 203 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 204 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 205: 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 206: 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 207: 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 208: Checking Outlet-Specific Data

    Chapter 6: Using the Web Interface 3. Click Setup in the right pane. The setup dialog for the selected outlet appears. 4. Type a name in the Outlet Name field. 5. Click OK. Checking Outlet-Specific Data To find out each outlet's name, label, and receptacle type, you can check the Outlets page or each individual outlet's page.
  • Page 209 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 210 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 211: 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 212 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 213: Changing The Cycling Power-Off Period

    Chapter 6: Using the Web Interface 4. In the "State on device startup" field, click the drop-down arrow and select an option from the list.  on: Turns on this outlet when the PX powers up.  off: Turns off this outlet when the PX powers up. ...
  • Page 214 Chapter 6: Using the Web Interface 3. In the "Power off period during power cycle" field, click the drop-down arrow and select an option from the list. Valid range is zero second to one hour. Time units in the list are explained below: s: second(s) ...

  • Page 215: Setting The Initialization Delay

    Chapter 6: Using the Web Interface  min: minute(s)  h: hour(s)  To make the outlet's power-off period identical to the PDU-defined setting, select the "PDU defined" option. See Changing the PDU-Defined Cycling Power-Off Period page 194). Tip: The information in parentheses following the option "PDU defined"...

  • Page 216: Setting The Inrush Guard Delay

    Chapter 6: Using the Web Interface Tip: When there are a large number of outlets, set the value to a lower number so that you can avoid a long wait before all the outlets are available again. Setting the Inrush Guard Delay This section applies to outlet-switching capable models only.

  • Page 217: 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 218: 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 219 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 220 Chapter 6: Using the Web Interface 2. In the PX Explorer pane, click the outlet you want. The page specific to that outlet opens in the right pane. 3. Click Setup in the right pane. The setup dialog for the selected outlet appears.

  • Page 221: No Support For Front Panel Outlet Switching

    Outlets page, and you CANNOT turn on any of them. No Support for Front Panel Outlet Switching PX2-1000 models do NOT support the outlet-switching function. PX2-2000 models support the outlet-switching function, but do NOT support the feature of using front panel buttons to switch on or off an outlet.

  • Page 222: 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 223: Monitoring Overcurrent Protectors

    Unbalanced Current factors in PX2-1000 and PX2-2000 3-phase models: When a PX2-1000 or PX2-2000 3-phase PDU has no load attached to it, its Unbalanced Current might have a non-zero percent reading. This is because the PDU factors the Inlet current that is needed to operate the PDU into the calculation for Unbalanced Current.
  • Page 224 Chapter 6: Using the Web Interface  Lines associated with this overcurrent protector  Outlets protected by this overcurrent protector  Sensor readings: - Current drawn (A) - Current remaining (A) Note: If a sensor row is colored, it means the sensor reading already crosses one of the thresholds, the sensor enters an alarmed state, or the overcurrent protector has tripped or blown.

  • Page 225: Resetting Inlet Active Energy Readings

    Chapter 6: Using the Web Interface Resetting Inlet Active Energy Readings You can manually reset the active energy readings of an individual inlet instead of resetting all active energy readings of the PDU. This is especially useful when your PX has more than one inlet. Only users with the "Admin"...

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

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

  • Page 227: Setting Power Thresholds

    Chapter 6: Using the Web Interface Setting Power Thresholds Setting and enabling the thresholds causes the PX to generate alert notifications when it detects that any component's power state crosses the thresholds. See (on page The Yellow- or Red-Highlighted Sensors 101).

  • Page 228: Setting An Overcurrent Protector's Thresholds

    Chapter 6: Using the Web Interface 7. To set the assertion timeout, type a numeric value in the Assertion Timeout (samples) field. See "To Assert" and Assertion Timeout (on page 595). 8. Click OK in the threshold setup dialog to retain the changes. 9.

  • Page 229: Bulk Configuration For Overcurrent Protector Thresholds

    Chapter 6: Using the Web Interface Bulk Configuration for Overcurrent Protector Thresholds The PX allows you to set power thresholds for multiple overcurrent protectors at a time to save your time. Note: To set the power thresholds for an individual overcurrent protector, you can either follow the instructions below or those described in the section Setting an Overcurrent Protector's Thresholds...

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

    Chapter 6: Using the Web Interface Setting Thresholds for Total Active Energy or Power This section applies only to multi-inlet models, including PX in-line monitors. Thresholds for total active energy and total active power are disabled by default. You can enable and set them so that you are alerted when the total active energy or total active power hits a certain level.
  • Page 231 Chapter 6: Using the Web Interface 8. Click OK.

  • Page 232: 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 233 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 234 Chapter 6: Using the Web Interface Action Function Log event message Records the selected events in the internal log. (on page 219). Log an Event Message Push out sensor Sends asset management sensor data to a readings remote server using HTTP POST requests. (on page Push Out Sensor Readings 220).
  • Page 235 Chapter 6: Using the Web Interface Action Function Switch outlets Switches on, off or cycles the power to the specified outlet(s). See Switch Outlets page 232). Switch peripheral Switches on or off the mechanism or system actuator connected to the specified actuator. See (on page 233).
  • Page 236 Chapter 6: Using the Web Interface 7. To remove an action from the action group, select it from the Used Actions list box, and click to move it to the Available Actions list box. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
  • Page 237 Chapter 6: Using the Web Interface b. Click to add the selected method to the Alarm Notifications list box. c. Repeat the above steps to add more methods if needed.  To remove any method from the Alarm Notifications list box, select that method and click 6.
  • Page 238 Chapter 6: Using the Web Interface 3. 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. 4. In the Action field, click the drop-down arrow and select the desired action: External beeper.
  • Page 239 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 240 Chapter 6: Using the Web Interface Request LHX/SHX Maximum Cooling If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will be available. See Enabling and Disabling Schroff LHX/SHX Heat (on page 310). Exchanger Support The "Request LHX/SHX Maximum Cooling" action applies the maximum cooling to the SHX-30 device only.
  • Page 241 Chapter 6: Using the Web Interface To use a different SMTP server, select the Use Custom SMTP Settings checkbox. If the SMTP server settings are not configured yet, click Configure. (on page 144) for the information Configuring SMTP Settings of each field. 8.
  • Page 242 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: Send email.
  • Page 243 Chapter 6: Using the Web Interface 5. In the Action field, click the drop-down arrow and select the desired action: Send SNMP notification. 6. Select the type of SNMP notification. See either procedure below according to your selection. To send SNMP v2c notifications: 1.
  • Page 244 Chapter 6: Using the Web Interface b. In the Number of Retries field, enter the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails.
  • Page 245 Chapter 6: Using the Web Interface Syslog Message Use this action to automatically forward event messages to the specified syslog server. Determine the syslog transmission mechanism you prefer when setting it up - UDP, TCP or TLS over TCP. The PX may or may not detect the syslog message transmission failure. If yes, it will log this syslog failure as well as the failure reason in the event log.
  • Page 246  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 247 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: Send sensor report.
  • Page 248 Chapter 6: Using the Web Interface 10. To save this action, click OK. Note: When intending to send a sensor report using custom messages, use the placeholder [SENSORREPORT] to report sensor readings. See Email and SMS Message Placeholders (on page 254). Change Load Shedding State The "Change load shedding state"...
  • Page 249 Chapter 6: Using the Web Interface Send SMS Message You can configure emails to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and PX placeholders. The placeholders represent information which is pulled from the PX and inserted into the message.
  • Page 250 Chapter 6: Using the Web Interface Internal Beeper You can have the built-in beeper of the PX turned on or off when a certain event occurs. To switch the internal beeper: 1. Click the Actions tab. 2. Click New. 3. In the "Action name" field, type a new name for the action. The default name is New Action <number>, where <number>...
  • Page 251 Chapter 6: Using the Web Interface 8. Click OK. Switch Outlets The "Switch outlets" action is available only when your PX is outlet-switching capable. This action turns on, off or power cycles a specific outlet. To switch on, off or power cycle any outlet(s): 1.
  • Page 252 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 253 Chapter 6: Using the Web Interface 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. In the Action field, click the drop-down arrow and select the desired action: Record snapshots to webcam storage.
  • Page 254 Chapter 6: Using the Web Interface 2. On the Rules tab, click New. 3. In the "Rule name" field, type a new name for identifying the rule. The default name is New Rule <number>, where <number> is a sequential number. 4.
  • Page 255 Chapter 6: Using the Web Interface Event types Radio buttons Sensor availability Available radio buttons include "Unavailable," "Available" and "Both."  Unavailable: The PX takes the action only when the chosen sensor is NOT detected and becomes unavailable.  Available: The PX takes the action only when the chosen sensor is detected and becomes available.
  • Page 256 Chapter 6: Using the Web Interface Event types Radio buttons Restricted service Available radio buttons include "Accepted," agreement "Declined," and "Both."  Accepted: The PX takes the action only when the specified user accepts the restricted service agreement.  Declined: The PX takes the action only when the specified user rejects the restricted service agreement.
  • Page 257 Chapter 6: Using the Web Interface Event types Radio buttons Device connection Available radio buttons include "Connected," or disconnection, "Disconnected" and "Both." such as a  Connected: The PX takes the action only USB-cascaded when the selected device is physically slave device connected to it.
  • Page 258 Chapter 6: Using the Web Interface 8. To remove any action, select it from the "Selected actions" list box, and click to move it back to the "Available actions" list box. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
  • Page 259 Chapter 6: Using the Web Interface Time options Frequency settings The frequency in minutes ranges from every minute, every 5 Minutes minutes, every 10 minutes and so on until every 30 minutes. The hourly option sets the timing to either of the following: Hourly ...
  • Page 260 Chapter 6: Using the Web Interface  To remove all actions, click 9. Click OK. Send Sensor Report Example Below is an example of a scheduled action set to send a temperature sensor report via email hourly. In this example, a.
  • Page 261 Chapter 6: Using the Web Interface  You must create the destination action as illustrated below prior to creating the 'Send Hourly Temperature Sensor Readings' action. For details, see (on page 222). Send EMail 2. Create the 'Send sensor report' action -- Send Hourly Temperature Sensor Readings.
  • Page 262 Chapter 6: Using the Web Interface  Type the action's name -- Send Hourly Temperature Sensor Readings.  Select the 'Send sensor report' action.  Select the destination action 'Send Sensor Temp Report Email'.  Add the desired temperature sensor(s) from the Available Sensors list to the Report Sensors box.
  • Page 263 Chapter 6: Using the Web Interface  Type the timer name -- Hourly Sensor Temperature Readings.  Select the Enabled checkbox.  Select Hourly, and set the Minute to 30.  Select the 'Send Hourly Temperature Sensor Readings' action. c. Click OK. For details, see (on page 239).
  • Page 264 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Asset Management > Rack Unit Asset tag with ID '[TAGID]' connected Asset tag with ID '[TAGID]' > * > Tag Connected at rack unit [RACKUNIT], slot disconnected at rack unit [RACKSLOT] of asset strip [STRIPID]...
  • Page 265 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Device > Firmware validation Firmware validation failed by user failed '[USERNAME]' from host '[USERIP]'. Device > Firmware update Firmware upgrade started from version started '[OLDVERSION]' to version...
  • Page 266 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Device > Sending SNMP inform Sending SNMP inform to manager failed or no response [SNMPMANAGER]:[SNMPMANAGER PORT] failed or no response. [ERRORDESC].
  • Page 267 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Peripheral Device Slot > * > Peripheral device Peripheral device Numeric Sensor > Below lower '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot warning '[EXTSENSORSLOT]' asserted 'below...
  • Page 268 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* > Above upper critical '[INLETPOLE]' of inlet '[INLET]' '[INLETPOLE]' of inlet '[INLET]' asserted 'above upper critical'. deasserted 'above upper critical'. Inlet >...
  • Page 269 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* lower critical '[OUTLET]' asserted 'below lower outlet '[OUTLET]' deasserted critical'. 'below lower critical'. Outlet > * > Sensor > * > Reset Sensor '[OUTLETSENSOR]' on outlet '[OUTLET]' has been reset by user '[USERNAME]' from host '[USERIP]'.
  • Page 270 Chapter 6: Using the Web Interface Sensor > * > Below lower overcurrent protector '[OCP]' asserted overcurrent protector '[OCP]' critical 'below lower critical'. deasserted 'below lower critical'. Overcurrent Protector > * > Sensor '[OCPSENSOR]' on Sensor '[OCPSENSOR]' on Sensor > * > Open/Closed overcurrent protector '[OCP]' is open.
  • Page 271 Chapter 6: Using the Web Interface added '[USERNAME]' from host '[USERIP]'. User Administration > Role Role '[TARGETROLE]' modified by modified user '[USERNAME]' from host '[USERIP]'. User Administration > Role Role '[TARGETROLE]' deleted by user deleted '[USERNAME]' from host '[USERIP]'. Webcam Management > Webcam '[WEBCAMNAME]' Webcam attached ('[WEBCAMUVCID]') added to port...
  • Page 272 Chapter 6: Using the Web Interface LHX / SHX > Emergency Emergency cooling on LHX at Emergency cooling on LHX at Cooling [PORTTYPE] port '[PORTID]' was [PORTTYPE] port '[PORTID]' was activated. deactivated. LHX / SHX > Maximum cooling Maximum cooling was requested for Maximum cooling is not any more request LHX at [PORTTYPE] port '[PORTID]'.
  • Page 273 Chapter 6: Using the Web Interface LHX / SHX > Threshold The humidity threshold on LHX at The humidity on LHX at Humidity [PORTTYPE] port '[PORTID]' was [PORTTYPE] port '[PORTID]' is crossed. within thresholds. LHX / SHX > External Water An external water cooling failure Cooling Failure occurred on LHX at [PORTTYPE] port...
  • Page 274 Chapter 6: Using the Web Interface Placeholder Definition [AMSRACKUNITPOSITION] The (vertical) rack unit position, an action applies to [AMSSTATE] The human readable state of an asset strip [AMSTAGID] The asset tag ID [CIRCUITCTRATING] The circuit CT rating [CIRCUITCURRENTRATING] The circuit current rating [CIRCUITNAME] The circuit name [CIRCUITPOLE]...
  • Page 275 Chapter 6: Using the Web Interface Placeholder Definition [OCP] The overcurrent protector label [OLDVERSION] The firmware version the device is being upgraded from [OUTLETPOLE] The outlet power line identifier [OUTLETSENSOR] The outlet sensor name [OUTLET] The outlet label [PDUPOLESENSOR] The sensor name for a certain power line [PDUSENSOR] The PDU sensor name [PERIPHDEVPOSITION]...

  • Page 276: Sample Event Rules

    Chapter 6: Using the Web Interface Placeholder Definition [TRANSFERSWITCH] The transfer switch label [UMTARGETROLE] The name of a user management role, an action was applied on [UMTARGETUSER] The user, an action was triggered for [USERIP] The IP address, a user connected from [USERNAME] The user who triggered an action [VERSION]...
  • Page 277 Chapter 6: Using the Web Interface Sample Inlet-Level Event Rule In this example, we want the PX to send SNMP notifications to the SNMP manager for any sensor change event of the Inlet I1. Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps or informs, depending on the settings for the System SNMP Notification Action.
  • Page 278 Chapter 6: Using the Web Interface Sample Environmental-Sensor-Level Event Rule This section applies to outlet-switching capable models only. In this example, we want PX to enable the load shedding function when a contact closure sensor enters the alarmed state. This sample event rule requires creating a new action before creating the rule.

  • Page 279: A Note About Infinite Loop

    Chapter 6: Using the Web Interface 7. Select State Sensor because the contact closure sensor is a discrete sensor, which indicates the environmental changes through the status changes. 8. Select "Alarmed/Open/On" in the submenu since we want the action "Activate Loading Shedding" to be taken when the selected contact closure sensor changes its state related to the "alarmed"...

  • Page 280: 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 281 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 282: 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 283: A Note About Untriggered Rules

    Chapter 6: Using the Web Interface 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 284: Viewing The Wireless Lan Diagnostic Log

    Chapter 6: Using the Web Interface 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.  Click to view the latest events. ...

  • Page 285: Viewing Connected Users

    Chapter 6: Using the Web Interface - Type a number in the Page text box and press Enter to go to a specific page.  Select a log entry from the list and click Show Details, or simply double-click the log entry to view detailed information. Note: Sometimes when the dialog is too narrow, the icon takes the place of the Show Details button.

  • Page 286: 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 287 Chapter 6: Using the Web Interface 2. Click New. The Add New Server dialog appears. 3. By default, the "Enable ping monitoring for this server" checkbox is selected. If not, select it to enable this feature. 4. Provide the information required. Field Description IP address/hostname IP address or host name of the IT...
  • Page 288 Chapter 6: Using the Web Interface Example: Ping Monitoring and SNMP Notifications In this illustration, it is assumed that a significant PDU (IP address: 192.168.84.95) shall be monitored by your PX to make sure that PDU is properly operating all the time, and the PX must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or network failure.

  • Page 289: Editing Ping Monitoring Settings

    Chapter 6: Using the Web Interface 3. In the "Rule name" field, type "Send SNMP notifications for PDU (192.168.84.95) inaccessibility." 4. Select the Enabled checkbox to enable this new rule. 5. In the Event field, choose Server Monitoring > 192.168.84.95 > Unreachable.

  • Page 290: Checking Server Monitoring States

    Chapter 6: Using the Web Interface 4. Click Yes on the confirmation message. 5. Click Close to quit the dialog. Checking Server Monitoring States Server monitoring results are available in the Server Reachability dialog after specifying IT devices for the PX device to monitor their network accessibility.

  • Page 291: Identifying 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 the room.
  • Page 292 Chapter 6: Using the Web Interface Matching the Serial Number A DPX environmental sensor package includes a serial number tag on the sensor cable. A DPX2, DPX3 or DX sensor has a serial number tag attached to its rear side. The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the PX.
  • Page 293 Chapter 6: Using the Web Interface Matching the Position DPX2, DPX3 and DX sensor packages can be daisy chained. The PX can indicate each sensor or actuator's position by showing the sensor port where the environmental sensor package is connected as well as its sequence in a sensor daisy chain.
  • Page 294 Chapter 6: Using the Web Interface For example, if a DPX sensor package is connected to the SENSOR port numbered 1, its Position column only shows "Port 1" no matter a DPX3-ENVHUB4 sensor hub is used or not. Note: For the PX devices with only one SENSOR port, it always shows "Port 1."...

  • Page 295: Managing Environmental Sensors Or Actuators

    Chapter 6: Using the Web Interface Managing Environmental Sensors or Actuators The PX starts to retrieve an environmental sensor's reading and/or state and records the state transitions after the environmental sensor is managed. To control an actuator, you also need to have it managed. The PX device can manage a maximum of 32 environmental sensors or actuators.
  • Page 296 Unmanaging Environmental Sensors or Actuators (on page 287). 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. ...

  • Page 297: Configuring Environmental Sensors Or Actuators

    Chapter 6: Using the Web Interface Configuring Environmental Sensors or Actuators You can change the default name to easily identify the managed sensor or actuator, and describe its location with X, Y and Z coordinates. To configure environmental sensors or actuators: 1.
  • Page 298 Chapter 6: Using the Web Interface 5. If the selected sensor is a numeric sensor, its threshold settings are displayed in the dialog. See (on page Sensor Threshold Settings 592) for detailed information. There are two types of thresholds: sensor-specific thresholds and default thresholds.
  • Page 299 Chapter 6: Using the Web Interface 2. Click Setup in the Settings section. The Pdu Setup dialog appears. 3. In the Peripheral Device Z Coordinate Format field, click the drop-down arrow and select an option from the list.  Rack Units: The height of the Z coordinate is measured in standard rack units.
  • Page 300 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 301 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 302: 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 303 Chapter 6: Using the Web Interface  Position  Serial number  Type  Channel (for a sensor package with contact closure or dry contact channels)  Whether the sensor is an 'Actuator' or not (if yes, this icon appears in the Actuator column) ...
  • Page 304 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 Open, which means no water is detected.
  • Page 305 If the normal state is set to Normally Open, the alarmed state means the contact closure switch is closed. For 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 306: 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 307: Disabling The Automatic Management Function

    Chapter 6: Using the Web Interface Note: If the desired action cannot be performed on any of the selected sensors or actuators, that action becomes unavailable. Deselect the inapplicable ones to perform the action. 3. Click Release. After a sensor or actuator is removed from management: ...

  • Page 308: Controlling Actuators

    Chapter 6: Using the Web Interface Controlling Actuators If you have any DX sensor packages with actuators connected, which can move or control a mechanism or system, you can remotely turn on or off the actuators to control the connected mechanism or system. To turn on or off an individual actuator: 1.
  • Page 309 Chapter 6: Using the Web Interface Note: The asset sensor is named "Asset Strip 1" by default. The name changes after being customized. Tip: The same asset sensor's page can be also opened by clicking Feature Port in the left pane, and then double-clicking the asset sensor in the right pane.

  • Page 310: Setting Asset Sensor Led Colors

    Chapter 6: Using the Web Interface 11. Click OK. Setting Asset Sensor LED Colors Each LED on the asset sensor indicates the presence and absence of a connected asset tag by changing its color. By default the LED color of the tag ports with tags connected is green, and the color of the tag ports without tags connected is red.

  • Page 311: Expanding A Blade Extension Strip

    Chapter 6: Using the Web Interface Note: The asset sensor is named "Asset Strip 1" by default. The name changes after being customized. Tip: The same asset sensor's page can be also opened by clicking Feature Port in the left pane, and then double-clicking the asset sensor in the right pane.

  • Page 312: Displaying The Asset Sensor Information

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

  • Page 313: Bulk Configuration

    Chapter 6: Using the Web Interface 2. Click the desired asset sensor in the left pane. The page specific to that asset sensor opens in the right pane, showing the asset sensor settings and information of all rack units (tag ports). Note: You can also access this dialog by double-clicking the asset sensor shown on the Dashboard page.

  • Page 314: 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 315: 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 316: 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 317: 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 318: 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 USB hub, set the resolution to 352x288 or lower for optimal performance.

  • Page 319: 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 320 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 298) or Configuring Webcams Adjusting Image (on page 299).

  • Page 321: 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 322 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 323: 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 324 Chapter 6: Using the Web Interface Tip: To store snapshots on a remote server rather than the PX, see Configuring Webcam Storage (on page 306). Managing the Snapshots Saved to PX A maximum of 10 saved snapshots can be stored and displayed on the Snapshots page of the PX.
  • Page 325 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 326: Network Diagnostics

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

  • Page 327: 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 328: 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 329: 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 330 Chapter 6: Using the Web Interface Setting Up an LHX/SHX Once a Schroff LHX/SHX heat exchanger is connected, you can set up the device by giving it a name, and configure its setpoint air outlet and default fan speed. To set up the LHX/SHX: 1.

  • Page 331: Monitoring The Lhx/Shx

    Chapter 6: Using the Web Interface 3. Select the desired sensor in the Sensors table and click Setup Thresholds, or double-click that sensor. The setup dialog for the selected sensor appears. 4. Adjust the threshold and deassertion hysteresis settings. The Upper Critical and Lower Critical values are points at which the PX considers the operating environment critical and outside the range of the acceptable threshold.
  • Page 332 Chapter 6: Using the Web Interface Viewing the Summary Both the Dashboard and Feature Port pages display the summary of the connected LHX/SHX heat exchanger, including the heat exchanger's name and status. If an LHX/SHX is highlighted in red in the summary, it indicates that there is LHX/SHX sensor failure on that heat exchanger.
  • Page 333 Chapter 6: Using the Web Interface Device States and Icon Variations The PX web interface changes icons to represent different statuses of the connected LHX/SHX heat exchanger. Icons Device status The heat exchanger is turned ON and operating normally. The heat exchanger is turned OFF. The heat exchanger is turned ON but enters the critical state because of any LHX/SHX sensor failure.

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

    Chapter 6: Using the Web Interface Operating Hours Operating hours are the accumulative time since the LHX/SHX heat exchanger is first connected to the PX device and turned ON. The PX web interface displays the operating hours both for the heat exchanger and its fans.

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

    Cooling to cool the device. The maximum cooling process begins. 4. 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 336: Updating The Px Firmware

    Raritan website's (http://www.raritan.com/support/). If Support page 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 337 Chapter 6: Using the Web Interface  The front panel display on the PX shows three digits: 'FuP' or 'FUP.' Exception: A PX3 Phase II model shows the upgrade progress in percent instead of FUP on its LCD display.  The outlet LEDs flash when the relay boards are being updated.
  • Page 338 The information in this section only applies to the PDU running a firmware version earlier than 2.1.6. When you are upgrading (or downgrading) the PX2-1000 or PX2-2000 series from any firmware version prior to version 2.1.6 to another version, there is possibility that a bootloader update failure message similar to the following appears at the end of the firmware update process.

  • Page 339: Viewing Firmware Update History

    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 340: Updating The Asset Sensor Firmware

    Chapter 6: Using the Web Interface Updating the Asset Sensor Firmware After connecting the asset sensor to the PX device, it automatically checks its own firmware version against the version of the asset sensor firmware stored in the PX firmware. If two versions are different, the asset sensor automatically starts downloading the new firmware from the PX device to upgrade its own firmware.
  • Page 341 "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 10. To print the currently selected topic, click the "Print this page" icon...

  • Page 342: 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 343: 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." ...

  • Page 344: 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 213). These events can also be Event Rules and Actions used to send SNMP v2c or v3 notifications to a third-party destination.

  • Page 345: 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. On the Notifications tab, select the Enabled checkbox to enable the SNMP notification feature.
  • Page 346 Chapter 7: Using SNMP 3. From the Notification Type drop-down, select the type of SNMP notification. 4. For SNMP INFORM communications, leave the resend settings at their default or: a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received.

  • Page 347: Snmpv3 Notifications

    Chapter 7: Using SNMP SNMPv3 Notifications To configure the PX to send SNMPv3 notifications: 1. Choose Device Settings > Network Services > SNMP. The SNMP Settings dialog appears. 2. On the Notifications tab, select the Enabled checkbox to enable the SNMP notification feature.
  • Page 348 Chapter 7: Using SNMP 3. From the Notification Type drop-down, select the type of SNMP notification. 4. For SNMP TRAPs, the engine ID is prepopulated. 5. For SNMP INFORM communications, leave the resend settings at their default or: a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received.

  • Page 349: 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 350: 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 351 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 352 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 353: 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 354: 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 ................335 Logging in to CLI ...................336 Help Command..................340 Querying Available Parameters for a Command........341 Showing Information................341 Clearing Information ................370 Configuring the PX Device and Network ..........371...

  • Page 355: 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 356: With Ssh Or Telnet

    Chapter 8: Using the Command Line Interface 5. Type a password and press Enter. The password is case sensitive. After properly entering the password, the # or > system prompt appears. See (on page 339) in Different CLI Modes and Prompts the User Guide for more information.

  • Page 357: With An Analog Modem

    Chapter 8: Using the Command Line Interface Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile was used to log in to this product's web interface or CLI. 6. You are now logged in to the command line interface and can begin administering the PX.

  • Page 358: 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 359: 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 360: 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 361: 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 362 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 363: 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 364: 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 365: 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 366: 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 367: 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 368: 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 369 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 370: 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 371: 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 372: Inlet Sensor Threshold Information

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

  • Page 373: Inlet Pole Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Inlet Pole Sensor Threshold Information This command is only available for a three-phase PDU except for an in-line monitor (PX2-3000 series). This command syntax shows the specified inlet pole sensor's threshold-related information. show sensor inletpole <n> <p> <sensor type> To show detailed information, add the parameter "details"...

  • Page 374: Overcurrent Protector 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 pole sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.

  • Page 375: 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 376: 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 377: 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 378: 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 379: 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 380: 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 381: 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 382: 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 383: 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 384: Wireless Lan Diagnostic Log

    Internal or external sensor events, such as state changes of any sensors. serverMonitor Server-monitoring records, such as a server being declared reachable or unreachable. assetManagement Raritan asset management events, such as asset tag connections or disconnections. Schroff LHX/SHX heat exchanger events. ® modem Modem-related events.
  • Page 385 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 386: 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 387: 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 388 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 389: 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 390: Clearing Wlan Log

    Chapter 8: Using the Command Line Interface Clearing WLAN Log This command removes all data from the diagnostic log for the wireless LAN (WLAN) connection. clear wlanlog -- OR -- clear wlanlog /y If you entered the command without "/y," a message appears, prompting you to confirm the operation.

  • Page 391: Quitting Configuration Mode

    Chapter 8: Using the Command Line Interface "apply" command before closing the terminal emulation program. Closing Quitting the program does not save any configuration changes. See Configuration Mode (on page 372). Quitting Configuration Mode Both of "apply" and "cancel" commands let you quit the configuration mode.
  • Page 392 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 393 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 394 Chapter 8: Using the Command Line Interface Setting the PDU-Defined Cycling Power-Off Period This section applies to outlet-switching capable models only. This command sets the power-off period of the power cycling operation for all outlets. config:# pdu cyclingPowerOffPeriod <timing> Variables: ...
  • Page 395 Chapter 8: Using the Command Line Interface Specifying Non-Critical Outlets This section applies to outlet-switching capable models only. This command determines critical and non-critical outlets. It is associated with the load shedding mode. See Setting Non-Critical Outlets and (on page 199). Load Shedding Mode config:# pdu nonCriticalOutlets <outlets1>:false;<outlets2>:true...
  • Page 396 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's DPX differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor.
  • Page 397 Chapter 8: Using the Command Line Interface Setting the Z Coordinate Format for Environmental Sensors This command enables or disables the use of rack units for specifying the height (Z coordinate) of environmental sensors. config:# pdu externalSensorsZCoordinateFormat <option> Variables:  <option>...

  • Page 398: 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 399 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 400 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 401 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 402 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 403 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 404 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 371).
  • Page 405 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 406 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 407 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 408 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 409 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 410 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 411 Chapter 8: Using the Command Line Interface Setting the IPv6 Gateway After selecting the static IP configuration mode, you can use this command to specify the gateway. config:# network ipv6 gateway <ip address> Variables:  <ip address> is the IP address of the gateway. This value uses the IPv6 address format.
  • Page 412 Chapter 8: Using the Command Line Interface Overriding the IPv6 DHCP-Assigned DNS Server After specifying the primary/secondary DNS server, you can use this command to override the DHCP-assigned DNS server with the one you specified. config:# network ipv6 overrideDNS <option> Variables: ...
  • Page 413 Chapter 8: Using the Command Line Interface config:# network ipv6 staticRoutes modify <route_ID> <dest-2> <hop> Variables:  <dest-1> is the IP address and prefix length of the subnet where the PX belongs. The format is IP address/prefix length.  <hop> is the IP address of the next hop router. ...
  • Page 414 Chapter 8: Using the Command Line Interface Changing the LAN Duplex Mode This command determines the LAN interface duplex mode. config:# network interface LANInterfaceDuplexMode <mode> Variables:  <mode> is one of the modes: auto, half or full. Option Description auto The PX selects the optimum transmission mode through auto-negotiation.
  • Page 415 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 416 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 417 Chapter 8: Using the Command Line Interface 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. Changing the SSH Configuration You can enable or disable the SSH service, or change its TCP port using the CLI commands.
  • Page 418 Chapter 8: Using the Command Line Interface Determining the SSH Authentication Method This command syntax determines the SSH authentication method. config:# network services ssh authentication <auth_method> Variables:  <option> is one of the options: passwordOnly, publicKeyOnly or passwordOrPublicKey. Option Description passwordOnly Enables the password-based login only.
  • Page 419 Chapter 8: Using the Command Line Interface Enabling or Disabling SNMP v3 This command enables or disables the SNMP v3 protocol. config:# network services snmp v3 <option> Variables:  <option> is one of the options: enable or disable. Option Description enable The SNMP v3 protocol is enabled.
  • Page 420 Chapter 8: Using the Command Line Interface Setting the sysName Value This command sets the SNMP MIB-II sysName value. config:# network services snmp sysName <value> Variables:  <value> is a string comprising 0 to 255 alphanumeric characters. Setting the sysLocation Value This command sets the SNMP MIB-II sysLocation value.
  • Page 421 Chapter 8: Using the Command Line Interface Enabling or Disabling the Read-Only Mode This command enables or disables the read-only mode for the Modbus agent. config:# network services modbus readonly <option> Variables:  <option> is one of the options: true or false. Option Description true...

  • Page 422: Time Configuration Commands

    Chapter 8: Using the Command Line Interface Examples This section illustrates several network configuration examples. Example 1 - Networking Mode The following command enables the wired networking mode. config:# network mode wired Example 2 - Enabling Both IP Protocols The following command determines that both IPv4 and IPv6 protocols are enabled.
  • Page 423 Chapter 8: Using the Command Line Interface Mode Description The date and time settings synchronize with a specified NTP server. Setting NTP Parameters A time configuration command that is used to set the NTP parameters begins with time ntp. Specifying the Primary NTP Server This command specifies the primary time server if synchronization with the NTP server is enabled.
  • Page 424 Chapter 8: Using the Command Line Interface Overriding DHCP-Assigned NTP Servers This command determines whether the customized NTP server settings override the DHCP-specified NTP servers. config:# time ntp overrideDHCPProvidedServer <option> Variables:  <option> is one of these options: true or false. Mode Description true...
  • Page 425 Chapter 8: Using the Command Line Interface Customizing the Date and Time If intending to manually configure the date and time, use the following CLI commands to specify them. Note: You shall set the time configuration method to "manual" prior to customizing the date and time.

  • Page 426: Checking The Accessibility Of Ntp Servers

    Chapter 8: Using the Command Line Interface Examples This section illustrates several time configuration examples. Example 1 - Time Setup Method The following command sets the date and time settings by using the NTP servers. config:# time method ntp Example 2 - Primary NTP Server The following command sets the primary time server to 192.168.80.66.

  • Page 427: Security Configuration Commands

    Chapter 8: Using the Command Line Interface Security Configuration Commands A security configuration command begins with security. Firewall Control You can manage firewall control features through the CLI. The firewall control lets you set up rules that permit or disallow access to the PX device from a specific or a range of IP addresses.
  • Page 428 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv6 defaultPolicyIn <policy> Determine the default IPv6 firewall control policy for outbound traffic: config:# security ipAccessControl ipv6 defaultPolicyOut <policy> Variables:  <option> is one of the options: true or false. Option Description true...
  • Page 429 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add <direction> <ip_mask> <policy> Add a new IPv4 rule by inserting it above or below a specific rule: config:# security ipAccessControl ipv4 rule add <direction> <ip_mask> <policy> <insert> <rule_number>...
  • Page 430 Chapter 8: Using the Command Line Interface  <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.  <policy> is one of the options: accept, drop or reject. Policy Description accept...
  • Page 431 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule modify <direction> <rule_number> ipMask <ip_mask> policy <policy>  IPv6 commands Modify an IPv6 rule's IP address and/or prefix length: config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> ipMask <ip_mask>...
  • Page 432 Chapter 8: Using the Command Line Interface Option Description reject Discards traffic from/to the specified IP address(es), and an ICMP message is sent to the source or destination host for failure notification. Deleting a Firewall Rule The following commands remove a specific IPv4 or IPv6 rule from the list.
  • Page 433 Chapter 8: Using the Command Line Interface Enabling or Disabling the Restricted Service Agreement This command activates or deactivates the Restricted Service Agreement. config:# security restrictedServiceAgreement enabled <option> Variables:  <option> is one of the options: true or false. Option Description true Enables the Restricted Service Agreement...
  • Page 434 Chapter 8: Using the Command Line Interface If the content is successfully entered, the CLI displays this message "Successfully entered Restricted Service Agreement" followed by the total number of entered characters in parentheses. Note: The new content of Restricted Service Agreement is saved only after typing the apply command.
  • Page 435 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 436 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 437 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 438 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 439 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 440 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 441 Chapter 8: Using the Command Line Interface Managing Role-Based Access Control Rules You can add, delete or modify role-based access control rules.  An IPv4 role-based access control command for managing rules begins with security roleBasedAccessControl ipv4 rule.  An IPv6 role-based access control command for managing rules begins with security roleBasedAccessControl ipv6 rule.
  • Page 442 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 443 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 444 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 445 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 446 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add 192.168.84.123/24 accept insertAbove 5 Results:  A new IPv4 firewall control rule is added to accept all packets sent from the IPv4 address 192.168.84.123.  The newly-added rule is inserted above the 5th rule. That is, the new rule becomes the 5th rule, and the original 5th rule becomes the 6th rule.

  • Page 447: Outlet Configuration Commands

    Chapter 8: Using the Command Line Interface Outlet Configuration Commands An outlet configuration command begins with outlet. Such a command allows you to configure an individual outlet. Changing the Outlet Name This command names an outlet. config:# outlet <n> name "<name>" Variables: ...

  • Page 448: Inlet Configuration Commands

    Chapter 8: Using the Command Line Interface Note: Setting the outlet's default state to an option other than pduDefined overrides the PDU-defined default state on that outlet. See Setting the PDU-Defined Default Outlet State (on page 374). Setting an Outlet's Cycling Power-Off Period This section applies to outlet-switching capable models only.
  • Page 449 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 450: 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 451 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 452 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 453 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 454 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 455 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 482).
  • Page 456 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 457 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 458 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 459 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 460 Chapter 8: Using the Command Line Interface c. Paste the contents into the terminal. d. Press Enter. To remove an existing SSH public key: 1. Type the same command as shown above. 2. When the system prompts you to input the contents, press Enter without typing or pasting anything.
  • Page 461 Chapter 8: Using the Command Line Interface 2. Type the following command and press Enter. config:# password 3. Type the existing password and press Enter when the following prompt appears. Current password: 4. Type the new password and press Enter when the following prompt appears.
  • Page 462 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 463 Chapter 8: Using the Command Line Interface Example 1 - Creating a User Profile The following command creates a new user profile and sets two parameters for the new user. config:# user create May enable admin Results:  A new user profile "May" is created. ...

  • Page 464: Role Configuration Commands

    Chapter 8: Using the Command Line Interface config:# user defaultpreferences preferredTemperatureUnit F preferredLengthUnit feet preferredPressureUnit psi Results:  The default temperature unit is set to Fahrenheit.  The default length unit is set to feet.  The default pressure unit is set to psi. Role Configuration Commands A role configuration command begins with role.
  • Page 465 Chapter 8: Using the Command Line Interface All Privileges This table lists all privileges. Note that available privileges vary according to the model you purchased. For example, a PDU without the outlet switching function does not have the privilege "switchOutlet." Privilege Description acknowledgeAlarms...
  • Page 466 Chapter 8: Using the Command Line Interface Privilege Description viewLog View Local Event Log viewSecuritySettings View Security Settings viewSnmpSettings View SNMP Settings viewUserSettings View Local User Management viewWebcamSettings View Webcam Snapshots and Configuration * The "switchOutlet" privilege requires an argument that is separated with a colon.
  • Page 467 Chapter 8: Using the Command Line Interface Modifying a Role You can modify diverse parameters of an existing role, including its privileges. Modify a role's description: config:# role modify <name> description "<description>" Variables:  <name> is a string comprising up to 32 ASCII printable characters. ...
  • Page 468 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 469: 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 470 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 471 Chapter 8: Using the Command Line Interface Setting the X Coordinate This command specifies the X coordinate of an environmental sensor. config:# externalsensor <n> xlabel "<coordinate>" Variables:  <n> is the ID number of the environmental sensor that you want to configure.
  • Page 472 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 473 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 474: 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 475 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 476: 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 477 Chapter 8: Using the Command Line Interface config:# sensor inlet <n> <sensor type> lowerCritical <option> Set the Lower Warning threshold for an inlet sensor: config:# sensor inlet <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an inlet sensor: config:# sensor inlet <n>...
  • Page 478 Chapter 8: Using the Command Line Interface  <option> is one of the options: enable, disable or a numeric value. Option Description enable Enables the specified threshold for a specific inlet sensor. disable Disables the specified threshold for a specific inlet sensor.
  • Page 479 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 480 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 597). Deassertion Hysteresis  <as_value> is a number in samples that is assigned to the assertion timeout for the specified inlet pole sensor.
  • Page 481 Chapter 8: Using the Command Line Interface 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 482 Chapter 8: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> upperCritical <option> Set the Upper Warning threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> upperWarning <option> Set the Lower Critical threshold for an environmental sensor: config:# sensor externalsensor <n>...
  • Page 483 Chapter 8: Using the Command Line Interface  <option> is one of the options: enable, disable or a numeric value. Option Description enable Enables the specified threshold for a specific environmental sensor. disable Disables the specified threshold for a specific environmental sensor.
  • Page 484 Chapter 8: Using the Command Line Interface Example 3 - Upper Thresholds for Overcurrent Protector Sensors The following command sets both the Upper Critical and Upper Warning thresholds for the 2nd overcurrent protector. config:# sensor ocp 2 current upperWarning enable upperCritical 16 Results: ...

  • Page 485: 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 482).

  • Page 486: 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 378).  <description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
  • Page 487 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 488 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 489 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 490: 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 491 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 492: 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 493 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 494 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 495 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 496 <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 497 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 498 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 499: 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 500 The following commands set the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the PX device. Change the baud rate before connecting it to the desired device, such as a computer, a Raritan's P2CIM-SER, or a modem, through the serial port, or there are communications errors.

  • Page 501: Setting The History Buffer Length

    Chapter 8: Using the Command Line Interface Option Description forceGsmModem The port enters the GSM modem state. Example The following command sets the CONSOLE baud rate of the PX device's serial port to 9600 bps. config:# serial consoleBaudRate 9600 Setting the History Buffer Length This command syntax sets the history buffer length, which determines the amount of history commands that can be retained in the buffer.
  • Page 502 Chapter 8: Using the Command Line Interface config:# network ipv4 ipAddress 192.168.84.225 subnetMask 255.255.255.0 gateway 192.168.84.0 Results:  The IP address is set to 192.168.84.225.  The subnet mask is set to 255.255.255.0.  The gateway is set to 192.168.84.0. Example 2 - Combination of Upper Critical and Upper Warning Settings The following multi-command syntax simultaneously configures Upper Critical and Upper Warning thresholds for the RMS current of the 2nd...

  • Page 503: Load Shedding Configuration Commands

    Chapter 8: Using the Command Line Interface Load Shedding Configuration Commands This section applies to outlet-switching capable models only. A load shedding configuration command begins with loadshedding. Unlike other CLI configuration commands, the load shedding configuration command is performed in the administrator mode rather than the configuration mode.

  • Page 504: Power Control Operations

    Chapter 8: Using the Command Line Interface Example The following command has the PX enter the load shedding mode. config:# loadshedding start Power Control Operations This section applies to outlet-switching capable models only. Outlets on the PX device can be turned on or off or power cycled through the CLI.

  • Page 505: Turning Off The Outlet(S)

    Chapter 8: Using the Command Line Interface Option Description A comma- Switches ON multiple, inconsecutive or separated list of consecutive outlets. outlets For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and 15, type outlets 2,4,9,11-13,15. A range of Switches ON multiple, consecutive outlets.

  • Page 506: Power Cycling The Outlet(S)

    Chapter 8: Using the Command Line Interface Option Description A comma- Switches OFF multiple, inconsecutive or separated list of consecutive outlets. outlets For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and 15, type outlets 2,4,9,11-13,15. A range of Switches OFF multiple, consecutive outlets.

  • Page 507: Canceling The Power-On Process

    Chapter 8: Using the Command Line Interface Option Description A comma- Power cycles multiple, inconsecutive or separated list of consecutive outlets. outlets For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and 15, type outlets 2,4,9,11-13,15. A range of Power cycles multiple, consecutive outlets.

  • Page 508: Actuator Control Operations

    Chapter 8: Using the Command Line Interface Actuator Control Operations An actuator, which is connected to a dry contact signal channel of a DX sensor, can control a mechanism or system. You can switch on or off that mechanism or system through the actuator control command in the CLI.

  • Page 509: Switching Off An Actuator

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

  • Page 510: Resetting The Px

    Chapter 8: Using the Command Line Interface 3. When the "Username to unblock" prompt appears, type the name of the blocked user and press Enter. 4. A message appears, indicating that the specified user was unblocked successfully. Resetting the PX You can reset the PX device to factory defaults or simply restart it using the CLI commands.

  • Page 511: Resetting To Factory Defaults

    Chapter 8: Using the Command Line Interface To reset one inlet's active energy readings: reset activeEnergy inlet <n> -- OR -- reset activeEnergy inlet <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 512: Quitting Diagnostic Mode

    Chapter 8: Using the Command Line Interface 2. Type diag and press Enter. The diag# or diag> prompt appears, indicating that you have entered the diagnostic mode. 3. Now you can type any diagnostic commands for troubleshooting. Quitting Diagnostic Mode To quit the diagnostic mode, use this command: diag>...
  • Page 513 Chapter 8: Using the Command Line Interface Option Description connections Shows network connections. Testing the Network Connectivity This ping command sends the ICMP ECHO_REQUEST message to a network host for checking its network connectivity. If the output shows the host is responding 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 514: 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 515: 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 516: 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 517: Feature Rj-45 Port Pinouts

    Output Reserved ― Signal Ground ― Power for CIM (200mA, fuse protected) Warning: Pin 3 is only intended for use with Raritan devices. Output Transmit Data (Data out) Input Receive Data (Data in) No Connection ― Signal Ground Input Reserved...

  • Page 518: 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 519 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 520 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 521 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 522: Appendix C Configuration Or Firmware Upgrade With A Usb Drive

    Appendix C Configuration or Firmware Upgrade with a USB Drive You can accomplish part or all of the following tasks simultaneously by plugging a USB flash drive which contains one or several special configuration files into the PX.  Configuration changes ...

  • Page 523: System And Usb Requirements

    PX system requirements:  There is at least one USB-A port available on your Raritan device.  Your PX must be version 2.2.13 or later. Note that the PX interpreted the USB drive contents using the firmware which was running when plugging the USB drive into the PX, not the new firmware after firmware upgrade.
  • Page 524 Appendix C: Configuration or Firmware Upgrade with a USB Drive Raritan provides a Mass Deployment Utility, which helps you to quickly generate all configuration files for your PX. See Creating Configuration (on page 512). Files via Mass Deployment Utility...

  • Page 525: Fwupdate.cfg

    Specify the name of a firmware binary file used to upgrade your PX.  The specified firmware file must be compatible with your PX and have an official Raritan signature.  If the specified firmware file is the same as the current firmware version of your PX, no firmware upgrade is performed unless you have set the option "force_update"...
  • Page 526 Appendix C: Configuration or Firmware Upgrade with a USB Drive  If this option is set to true, the firmware upgrade is always performed even though your PX is running the same firmware version as the specified firmware file.  This option CANNOT break other constraints like the minimum downgrade version.
  • Page 527 Appendix C: Configuration or Firmware Upgrade with a USB Drive  The PX utters a short beep when writing the diagnostic data to the USB drive. factory_reset  Supported as of release 3.0.0.  If this option is set to true, the PX will be reset to factory defaults. ...

  • Page 528: Config.txt

    PX model. You can use Raritan's Mass Deployment Utility to create this file by yourself, or contact Raritan to get a device configuration file specific to your PX model and firmware version.
  • Page 529 Appendix C: Configuration or Firmware Upgrade with a USB Drive Special configuration keys: There are 3 special configuration keys that are prefixed with magic:.  A special key that sets a user account's password without knowing the firmware's internal encryption/hashing algorithms is implemented as of release 2.2.13.

  • Page 530: Devices.csv

    Appendix C: Configuration or Firmware Upgrade with a USB Drive devices.csv If there are device-specific settings to configure, you must create a device list configuration file - devices.csv, to store unique data of each This file must be:  An excel file in the CSV format. ...

  • Page 531: Creating Configuration Files Via Mass Deployment Utility

    After entering required information, you can generate all configuration files with only one click, including fwupdate.cfg, config.txt and devices.csv. To use the Mass Deployment Utility: 1. Download the Mass Deployment Utility from the Raritan website.  The utility is named mass_deployment-xxx (where xxx is the version number).

  • Page 532: Firmware Upgrade Via Usb

    6. When the firmware upgrade finishes, the front panel display indicates the firmware upgrade result.  =-] (happy smiley): Successful.  =-[ (sad smiley): Failed. Check the log file in the USB drive or contact Raritan Technical Support to look into the failure cause.

  • Page 533: Appendix D Bulk Configuration Or Firmware Upgrade Via Dhcp/Tftp

    Steps of using DHCP/TFTP for bulk configuration/upgrade: 1. Create configuration files specific to your PX models and firmware versions. See (on page 504) or contact Raritan Configuration Files Technical Support to properly prepare some or all of the following files: ...

  • Page 534: 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 535: 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 536 Appendix D: 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 537 Appendix D: 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 538 Appendix D: 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 539 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 540 Appendix D: 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 541 Appendix D: 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 542 Appendix D: 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 543 Appendix D: 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 544 Appendix D: 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 545: 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 546 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 547 Appendix D: 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 548 Appendix D: 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 549 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 550 Appendix D: 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 551 Appendix D: 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 552: 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 553 Appendix D: 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). ...

  • Page 554: 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 555 Appendix D: 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 556: Appendix E Resetting To Factory Defaults

    Appendix E 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 557: Using The Cli Command

    Appendix E: Resetting to Factory Defaults This diagram shows the location of the reset button on Zero U models. This diagram shows the location of the reset button on 1U models. This diagram shows the location of the reset button on 2U models. Note: HyperTerminal is available on Windows operating systems prior to Windows Vista.
  • Page 558 Appendix E: Resetting to Factory Defaults 4. After the # system prompt appears, type either of the following commands and press Enter. reset factorydefaults -- OR -- reset factorydefaults /y 5. If you entered the command without "/y" in Step 4, a message appears prompting you to confirm the operation.

  • Page 559: Appendix F Available Scp Commands

    Appendix F 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 ..............540 Bulk Configuration via SCP ..............541 Backup and Restore via SCP ..............542 Firmware Update via SCP Same as any PX firmware update, all user management operations are...

  • Page 560: Bulk Configuration Via Scp

    Appendix F: 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 561: Backup And Restore Via Scp

    Appendix F: 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 562 Appendix F: 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 563: Appendix G 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 564: Step B. Configure User Groups On The Ad Server

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

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

    Appendix G: 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 116) and Modifying Network Settings Role of a DNS...
  • Page 566 Appendix G: 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 567: Step D. Configure Roles On The Px Device

    Appendix G: LDAP Configuration Illustration 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 568 Appendix G: LDAP Configuration Illustration c. Click Add. 6. Click OK. The PX_User role is created. 7. Keep the Manage Roles dialog opened to create the PX_Admin role. To create the PX_Admin role with full permissions assigned: 1. Click New. The Create New Role dialog appears. 2.
  • Page 569 Appendix G: LDAP Configuration Illustration 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 570 Appendix G: LDAP Configuration Illustration 5. Click OK. The PX_Admin role is created. 6. Click Close to quit the dialog.

  • Page 571: Appendix H Updating The Ldap Schema

    Appendix H Updating the LDAP Schema In This Chapter Returning User Group Information ............552 Setting the Registry to Permit Write Operations to the Schema ...553 Creating a New Attribute ...............553 Adding Attributes to the Class ...............554 Updating the Schema Cache..............556 Editing rciusergroup Attributes for User Members ........556 Returning User Group Information Use the information in this section to return User Group information (and...

  • Page 572: Setting The Registry To Permit Write Operations To The Schema

    Appendix H: Updating the LDAP Schema Setting the Registry to Permit Write Operations to the Schema To allow a domain controller to write to the schema, you must set a registry entry that permits schema updates. To permit write operations to the schema: 1.

  • Page 573: Adding Attributes To The Class

    Appendix H: Updating the LDAP Schema 3. Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears. 4. Type rciusergroup in the Common Name field. 5. Type rciusergroup in the LDAP Display Name field. 6.
  • Page 574 Appendix H: Updating the LDAP Schema 2. Scroll to the user class in the right pane and right-click it. 3. Choose Properties from the menu. The user Properties dialog appears. 4. Click the Attributes tab to open it. 5. Click Add.

  • Page 575: Updating The Schema Cache

    Appendix H: Updating the LDAP Schema 6. Choose rciusergroup from the Select Schema Object list. 7. Click OK in the Select Schema Object dialog. 8. Click OK in the User Properties dialog. Updating the Schema Cache To update the schema cache: 1.
  • Page 576 Appendix H: Updating the LDAP Schema 3. Go to the directory where the support tools were installed. Run adsiedit.msc. The ADSI Edit window opens. 4. Open the Domain. 5. In the left pane of the window, select the CN=Users folder.
  • Page 577 Appendix H: Updating the LDAP Schema 6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties. 7. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list.

  • Page 578: 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 579: 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 580 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 581 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 582: 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 583 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 584 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 585 Appendix I: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
  • Page 586 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 587 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 588 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 589 Appendix I: RADIUS Configuration Illustration Note: If your PX uses PAP, then select "PAP."...
  • Page 590 Appendix I: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
  • Page 591 Appendix I: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
  • Page 592 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 593 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 594 Appendix I: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
  • Page 595 Appendix I: RADIUS Configuration Illustration 15. Click Next to continue.
  • Page 596 Appendix I: RADIUS Configuration Illustration 16. A summary showing connection request policy settings is displayed. Click Finish to close the dialog.

  • Page 597: 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 598 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 599: 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 600 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 601 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 602: 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 603: 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" 584). Format of the "string"...
  • Page 604 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 605: Appendix J 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 606: 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 607: Button-Type Locking Outlets

    Appendix J: 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 608: Unbalanced Current Calculation

    Appendix J: 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 609: Reserving Ip Addresses In Windows Dhcp Servers

    Appendix J: Additional PX Information  Average current: (5.5+5.2+4.0) / 3 = 4.9 amps  L1 current unbalance: (5.5 - 4.9) / 4.9 = 0.1224  L2 current unbalance: (5.2 - 4.9) / 4.9 = 0.0612  L3 current unbalance: (4.0 - 4.9) / 4.9 = -0.1837 ...
  • Page 610 Appendix J: Additional PX Information Field Description IP address Enter the IP address you want to reserve. MAC address Enter the ASCII codes of the PX serial number. Do NOT contain spaces in the ASCII codes.  In this example, enter 50454731413030303033 Other fields Configure them according to your needs.

  • Page 611: Sensor Threshold Settings

    Appendix J: 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 612: Thresholds And Sensor States

    Appendix J: 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 613 Appendix J: 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. States of "above upper warning" and "below lower warning" are warning states to call for your attention.

  • Page 614: To Assert" And Assertion Timeout

    Appendix J: 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. To 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 615 Appendix J: 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 616: To De-Assert" And Deassertion Hysteresis

    Appendix J: 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 617 Appendix J: 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 618: Pdview App For Viewing The Px

    PDView App for Viewing the PX Raritan has developed an app that can turn your iOS or Android mobile device into a local display for the PX. This app is called PDView and it can be downloaded for free.
  • Page 619 Appendix J: Additional PX Information 2. After installing the PDView, launch it. Below illustrates the PDView for Android devices. 3. Connect your mobile device to the USB port of the PX. Your mobile device type determines which USB port on the PX shall be used to connect the mobile device.

  • Page 620: Altitude Correction Factors

    PX. 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 621: Data For Btu Calculation

    The heat generated by the PX device differs according to the model you purchased. To calculate the heat (BTU/hr), use the following power data according to your model type in the BTU calculation formula. Model name Maximum power (Watt) PX2-1000 PX3-1000 PX2-2000 PX3-2000 PX2-3000...

  • Page 622: Ways To Probe Existing User Profiles

    Appendix J: Additional PX Information Ways to Probe Existing User Profiles This section indicates available ways to query existing user accounts on the PX.  With SNMP v3 activated, you get the "user unknown" error when the user name used to authenticate does not exist. ...

  • Page 623: Raritan Training Website

    Appendix J: Additional PX Information 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 624: Appendix K Integration

    Appendix K Integration The PX device can work with certain Raritan's or Sunbird's products to provide diverse power solutions. In This Chapter Dominion KX II / III Configuration ............605 Dominion KSX II, SX or SX II Configuration..........610 Power IQ Configuration .................614 dcTrack ....................615...

  • Page 625: Configuring Rack Pdu Targets

    KX III allows you to connect rack PDUs (power strips) to KX III ports. KX III rack PDU configuration is done from the KX III Port Configuration page. Note: Raritan recommends no more than eight (8) rack PDUs (power strips) be connected to a KX III at once since performance may be affected.
  • Page 626 Note: PX rack PDUs (power strips) can be named in the PX as well as in the KX III. Once a Raritan remote rack PDU is connected to the KX III, it will appear on the Port Configuration page. Click on the power port name on that page to access it.
  • Page 627 Appendix K: Integration 3. Click OK.

  • Page 628: Turning Outlets On/Off And Cycling Power

    Port Access page. To use this feature, you will need:  Raritan remote rack PDU(s)  Power CIMs (D2CIM-PWR) Make a Power Association...

  • Page 629: Dominion Ksx Ii, Sx Or Sx Ii Configuration

    KSX II, SX or SX II Online Help on the Product Online Help page (http://www.raritan.com/support/online-help/) Dominion KSX II After connecting a Dominion KSX II to the Raritan PDU, you can monitor the PDU and even control its outlets if the PDU is an outlet-switching capable model.
  • Page 630 Appendix K: Integration Connecting a Rack PDU To connect the Raritan PX to the KSX II: 1. Connect one end of a Cat5 cable to the following ports of different Raritan PX.  PX1 series: RJ-45 "SERIAL" port  PX2 or PX3 series: RJ-45 "FEATURE" port 2.

  • Page 631: Dominion Sx And Sx Ii

    PX device to specific SX or SX II ports. Dominion SX II The way to use Dominion SX II to connect, configure and control a Raritan PX is the same as the way to use Dominion KX III. For detailed information, refer to: ...
  • Page 632 Appendix K: Integration 4. Select the number of outlets from the Number of Outlets drop-down menu. 5. Type the port number in the Port field. 6. Click OK. Power Control 1. Choose Power Control > Power Strip Power Control. The Outlet Control screen appears.

  • Page 633: Power Iq Configuration

    Appendix K: Integration Checking Power Strip Status 1. Choose Power Control > Power Strip Status. 2. A status box appears, displaying details of the controlled PX, including power state of each outlet on the device. Power IQ Configuration Sunbird's Power IQ is a software application that collects and manages the data from different PDUs installed in your server room or data center.

  • Page 634: Dctrack

    Appendix K: Integration dcTrack Sunbird's dcTrack is a product that allows you to manage the data ® center. The PX is categorized as a power item in dcTrack. dcTrack offers an import wizard for conveniently adding the PX as well as other IT equipment to dcTrack for management.

  • Page 635: Dctrack Overview

    Appendix K: Integration dcTrack Overview dcTrack is a powerful and intelligent data center management and ® automation application. It has been designed by data center and IT professionals to provide broad and deep visibility into the data center. It empowers data center managers to plan for growth and change by optimizing their current operations, assets, and infrastructure.

  • Page 636: Asset Management Sensors And Dctrack

    To poll and display asset management events in dcTrack  The PX that the asset sensor is connected to must exist in dcTrack. EMX devices are identified as probes in dcTrack; Raritan PDUs are identified as sensors.  Each IT item connected to the asset sensor via an asset tag must exist in dcTrack.
  • Page 637 Index Assertion Timeout Example for Temperature Sensors • 596 Asset Management • 289 1U and 2U Port Locations • 75 Asset Management Commands • 473 1U Products • 2 Asset Management Sensors and dcTrack • Asset Sensor Management • 474 Asset Sensor Settings •...

  • Page 638: Index

    Index Changing Telnet Settings • 126 config.txt • 504, 507, 509 Changing the Cycling Power-Off Period • 194 Configuration Files • 503, 504, 514 Changing the Default Policy • 159, 160, 170, Configuration or Firmware Upgrade with a USB Drive • xix, 29, 294, 503, 513, 514 Changing the Inlet Name •...
  • Page 639 Index Connecting Composite Asset Sensors Deleting an Event Rule or Action • 263 (AMS-Mx-Z) • 64, 68 Deleting Authentication Server Settings • 187 Connecting Environmental Sensor Packages • Deleting Firewall Rules • 165 xviii, 35, 69, 271 Deleting Ping Monitoring Settings • 270 Connecting External Equipment (Optional) •...
  • Page 640 Index Editing Firewall Rules • 164 Entering Diagnostic Mode • 339, 492 Editing Ping Monitoring Settings • 270 Environmental Sensor Configuration Editing rciusergroup Attributes for User Commands • 450 Members • 556 Environmental Sensor Default Thresholds • Editing Role-Based Access Control Rules • Environmental Sensor Information •...
  • Page 641 Index Example 2 - Combination of Upper Critical and From Microsoft Active Directory • 552 Upper Warning Settings • 483 Full Disaster Recovery • 320 Example 2 - Enabling Both IP Protocols • 403 Fuse • 84 Example 2 - In-Depth Security Information • Fuse Replacement on 1U Models •...
  • Page 642 Index IP Configuration • 342 Modifying a Role • 153, 154, 157, 448 Modifying a Role-Based Access Control Rule • Modifying a User Profile • 93, 154, 157, 432 LAN Interface Settings • 342 Modifying a User's Personal Data • 434 Layout •...
  • Page 643 Push Out Sensor Readings • 145, 215, 220 Network Configuration Commands • 379 PX Explorer Pane • 95 Network Diagnostics • 307 PX2-1000 Series • 74 Network Service Settings • 343 PX2-2000 Series • 74 Network Troubleshooting • 307, 492 Networking Mode •...
  • Page 644 Index Returning User Group Information • 552 Setting Asset Sensor LED Colors • 290, 291 Role Configuration Commands • 445 Setting Data Logging • 143, 377 Role of a DNS Server • 122, 546 Setting Data Logging Measurements Per Entry Role-Based Access Control •...
  • Page 645 Index Setting the IPv6 Secondary DNS Server • 392 Showing Network Connections • 493 Setting the LED Operation Mode • 478 Single Login Limitation • 416 Setting the Networking Mode • 380 Snapshot Storage • 304 Setting the Outlet Initialization Delay • 375 SNMP Gets and Sets •...
  • Page 646 Index Supported Maximum DPX Sensor Distances • USB-Cascading Configuration Information • 36, 41 Supported Web Browsers • xviii, 89 User Blocking • 417 Supported Wireless LAN Configuration • 23 User Configuration Commands • 431 Switch LHX/SHX • 215, 231 User Management • 150 Switch Outlets •...
  • Page 647 Index Zero U Connection Ports • 74 Zero U Products • 2...
  • Page 648 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:

Px2-3000Px3-3000Px3-1000Px3-4000Px2-4000Px2-5000 ... Show all

Table of Contents