LEGRAND Raritan PX3-1000 Series User Manual
  1. Manuals
  2. Brands
  3. LEGRAND Manuals
  4. Power distribution unit
  5. Raritan PX3-1000 Series
  6. User manual
LEGRAND Raritan PX3-1000 Series User Manual

LEGRAND Raritan PX3-1000 Series User Manual

Hide thumbs
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
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
Table of Contents

Advertisement

Quick Links

Download this manual
PX3-1000 Series
User Guide
Xerus
Firmware v3.6.0
™
Copyright © 2019 Raritan, Inc.
PX3-1000-1H-v3.6.0-E
March 2020
255-80-0034-00

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for LEGRAND Raritan PX3-1000 Series

Summary of Contents for LEGRAND Raritan PX3-1000 Series

  • Page 1 PX3-1000 Series User Guide Xerus Firmware v3.6.0 ™ Copyright © 2019 Raritan, Inc. PX3-1000-1H-v3.6.0-E March 2020 255-80-0034-00...
  • Page 2 Safety Guidelines WARNING! Read and understand all sections in this guide before installing or operating this product. WARNING! Connect this product to an AC power source whose voltage is within the range specified on the product's nameplate. Operating this product outside the nameplate voltage range may result in electric shock, fire, personal injury and death.
  • Page 3 Safety Instructions 1. Installation of this product should only be performed by a person who has knowledge and experience with electric power. 2. Make sure the line cord is disconnected from power before physically mounting or moving the location of this product.
  • Page 4 This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated into another language without express prior written consent of Raritan, Inc. © Copyright 2019 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.

  • Page 6: Table Of Contents

    Contents Safety Guidelines Safety Instructions Applicable Models xvii What's New in the PX3 User Guide 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 Before You Begin ............................
  • Page 7 Contents Button-Type Locking Outlets ......................20 Chapter 3 Initial Installation and Configuration Connecting the PDU to a Power Source ..................... 21 Connecting the PX3 to Your Network ......................22 USB Wireless LAN Adapters ......................23 Supported Wireless LAN Configuration ..................23 Dual Ethernet Connection .......................
  • Page 8 Contents Connecting a Logitech Webcam ......................... 78 Connecting a GSM Modem ........................79 Connecting an Analog Modem ........................79 Connecting an External Beeper ........................80 Connecting a Schroff LHX/SHX Heat Exchanger ..................80 Connecting a Modbus RTU Device or Bus ....................81 Chapter 5 PDU Linking FAQs ................................
  • Page 9 Contents Beeper ..............................156 Replaceable Controller ..........................157 Threaded Grounding Point ........................158 Chapter 7 Using the Web Interface Supported Web Browsers ........................159 Login, Logout and Password Change ......................159 Login .............................. 159 Changing Your Password ....................... 162 Remembering User Names and Passwords .................. 163 Logout ............................
  • Page 10 Contents Schroff LHX/SHX ..........................234 Power CIM ............................. 239 User Management ............................ 240 Creating Users ..........................241 Editing or Deleting Users ....................... 244 Creating Roles ..........................246 Editing or Deleting Roles ....................... 248 Setting Your Preferred Measurement Units ................. 249 Setting Default Measurement Units .....................
  • Page 11 Contents Chapter 8 Using SNMP Enabling and Configuring SNMP ....................... 447 SNMPv2c Notifications ........................448 SNMPv3 Notifications ........................449 Downloading SNMP MIB .......................... 452 SNMP Gets and Sets ..........................453 The PX3 MIB ..........................453 A Note about Enabling Thresholds ....................455 Chapter 9 Using the Command Line Interface About the Interface ..........................
  • Page 12 Contents Network Connections Diagnostic Log ................... 487 Server Reachability Information ....................487 Command History ......................... 488 Reliability Data ..........................489 Reliability Error Log ........................489 Reliability Hardware Failures ......................489 Examples ............................489 Clearing Information ..........................492 Clearing Event Log ......................... 492 Clearing Diagnostic Log for Network Connections ................
  • Page 13 Contents Retrieving Previous Commands ....................... 622 Automatically Completing a Command ....................622 Logging out of CLI ............................. 623 Chapter 10 Using SCP Commands Firmware Update via SCP ......................... 624 Bulk Configuration via SCP ........................625 Backup and Restore via SCP ........................626 Downloading Diagnostic Data via SCP ......................
  • Page 14 Contents Firmware Upgrade via USB ........................653 Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ....................656 TFTP Requirements ..........................657 DHCP IPv4 Configuration in Windows ...................... 657 DHCP IPv6 Configuration in Windows ...................... 667 DHCP IPv4 Configuration in Linux ......................674 DHCP IPv6 Configuration in Linux ......................
  • Page 15 Contents CLI Operations for RCM ..........................700 Showing Residual Current Monitoring Information ..............701 Setting RCM Current Thresholds ....................701 Setting Front Panel RCM Self-Test ....................703 Running RCM Self-Test ........................703 Degaussing RCM Type B Sensors ....................703 Appendix H Old Generations of PX3 Models PX3 'Phase II' Front Panel Display......................
  • Page 16 Contents AD-Related Configuration ........................768 Appendix L Additional PX3 Information RJ45-to-DB9 Cable Requirements for Modem Connections ..............772 Reserving IP Addresses in DHCP Servers ....................773 Reserving IP in Windows ....................... 774 Reserving IP in Linux ........................775 Sensor Threshold Settings ........................777 Thresholds and Sensor States .......................
  • Page 17 Applicable Models This User Guide is applicable to all the following PDU Generations. • PX3 with iX7 PDU Generation (1000 series) ™ Any PX Generations can be associated with existing metering families called “Series”, from 1000 series to 5000 series. For example, PX2-4000 and PX3-4000 series are all inlet metered and outlet metered PDUs, but have different controller generations.
  • Page 18 Chapter 1: Applicable Models Product models PXC / PXO Dot-matrix LCD Dot-matrix LCD LED display Front panel display display display Outlet latching relays Number of LAN ports 100 Mbps ** 1,000 Mbps 100 Mbps Maximum LAN rate Replaceable controller Number of USB-A ports 12 Mbps 480 Mbps 480 Mbps...
  • Page 19 What's New in the PX3 User Guide Important: If your PX3 is running any firmware version older than 3.3.0, you must upgrade it to 3.3.x or 3.4.x before upgrading it to 3.5.0 or later. See Updating the PX3 Firmware (on page 406). New Features and Updates: •...

  • Page 21: Chapter 1 Introduction

    Chapter 1 Introduction In this User Guide, PX3 refers to PX3 with "iX7 " controller (that is, PX3-iX7) ™ unless otherwise specified. Raritan's PX3 is an intelligent power distribution unit (PDU) that allows you to reboot remote servers and other network devices and/or to monitor power in the data center.

  • Page 22: 1U Products

    Chapter 1: Introduction 1U Products • One PX3 • 1U bracket pack and screws • Cable retention clips for the inlet (for some models only) 2U Products • One PX3 • 2U bracket pack and screws • Cable retention clips for the inlet (for some models only) APIPA and Link-Local Addressing PX3 supports Automatic Private Internet Protocol Addressing (APIPA).

  • Page 23: Before You Begin

    Chapter 1: Introduction • IPv6 address: A link-local IPv6 address is available only after IPv6 is enabled on the PX3. Configuring Network Settings (on page 253). • Host name - pdu.local: You can type https://pdu.local to access the PX3 instead of typing the link-local IP address.

  • Page 24: Checking The Branch Circuit Rating

    Chapter 1: Introduction Checking the Branch Circuit Rating The rating of the branch circuit supplying power to the PDU shall be in accordance with national and local electrical codes. Filling Out the Equipment Setup Worksheet An Equipment Setup Worksheet is provided in this User Guide. See Equipment Setup Worksheet (on page 637).

  • Page 25: Chapter 2 Rackmount, Inlet And Outlet Connections

    Chapter 2 Rackmount, Inlet and Outlet Connections In This Chapter Circuit Breaker Orientation Limitation ..............5 Rack-Mounting the PDU ..................5 Connecting a PX3 Locking Line Cord ..............14 Installing Cable Retention Clips on the Inlet (Optional) ........16 Installing Cable Retention Clips on Outlets (Optional) ........17 Locking Outlets and Cords ..................

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

    Chapter 2: Rackmount, Inlet and Outlet Connections Mounting Zero U Models Using L-Brackets If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it. To mount Zero U models using L-brackets: Align the baseplates on the rear of the PX3 device. Secure the baseplates in place.

  • Page 27: Mounting Zero U Models Using Button Mount

    Chapter 2: Rackmount, Inlet and Outlet Connections Using rack screws, fasten the PX3 device to the rack through the L-brackets. Mounting Zero U Models Using Button Mount If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it. To mount Zero-U models using button mount: Align the baseplates on the rear of the PX3 device.

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

    Chapter 2: Rackmount, Inlet and Outlet Connections Align the large mounting buttons with the mounting holes in the cabinet, fixing one in place and adjusting the other. Loosen the hex socket screws until the mounting buttons are secured in their position. Ensure that both buttons can engage their mounting holes simultaneously.
  • Page 29 Chapter 2: Rackmount, Inlet and Outlet Connections Secure the baseplates in place. Use the included L-shaped hex key to loosen the hex socket screws until the baseplate is "slightly" fastened. Align the claw-foot brackets with the baseplates so that the five screw-holes on the baseplates line up through the bracket's slots.

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

    Chapter 2: Rackmount, Inlet and Outlet Connections Mounting Zero U Models Using Two Rear Buttons The following describes how to mount a PX3 using two buttons only. If your PDU has circuit breakers implemented, read Circuit Breaker Orientation Limitation (on page 5) before mounting it. To mount Zero U models using two buttons: Turn to the rear of the PX3.

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

    Chapter 2: Rackmount, Inlet and Outlet Connections Screw a button in the screw hole near the top. The recommended torque for the button is 1.96 N·m (20 kgf·cm). Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously.

  • Page 32: Mounting 1U Or 2U Models

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

  • Page 34: Connecting A Px3 Locking Line Cord

    Chapter 2: Rackmount, Inlet and Outlet Connections Connecting a PX3 Locking Line Cord The PX3 is shipped with either of the following locking line cords. • A line cord with locking clips: A locking inlet on the PDU is required for this cord.

  • Page 35: Disconnecting A Px3 Locking Line Cord

    Chapter 2: Rackmount, Inlet and Outlet Connections Number Item Slide release buttons For information on removing the locking line cord, see Disconnecting a PX3 Locking Line Cord (on page 15). Disconnecting a PX3 Locking Line Cord The ways to disconnect a locking line cord vary according to the cord type. To disconnect a line cord with locking clips: Press both locking clips of the line cord while unplugging the cord.

  • Page 36: Installing Cable Retention Clips On The Inlet (Optional)

    Chapter 2: Rackmount, Inlet and Outlet Connections Installing Cable Retention Clips on the Inlet (Optional) If your PX3 device is designed to use a cable retention clip, install the clip before connecting a power cord. A cable retention clip prevents the connected power cord from coming loose or falling off.

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

    Chapter 2: Rackmount, Inlet and Outlet Connections Installing Cable Retention Clips on Outlets (Optional) If your PX3 device is designed to use a cable retention clip, install the clip before connecting a power cord. A cable retention clip prevents the connected power cord from coming loose or falling off.

  • Page 38: Locking Outlets And Cords

    Chapter 2: Rackmount, Inlet and Outlet Connections Plug the power cord into the outlet, and press the clip toward the power cord until it holds the cord firmly. The clip's central part holding the plug should face downwards toward the ground, like an inverted "U". This allows gravity to keep the clip in place.
  • Page 39 Chapter 2: Rackmount, Inlet and Outlet Connections Item Description Latches on the SecureLock cord's plug ™ Only specific PDUs are implemented with the SecureLock mechanism. If your ™ PDU does not have this design, do NOT use the SecureLock cords with it. ™...

  • Page 40: Button-Type Locking Outlets

    Chapter 2: Rackmount, Inlet and Outlet Connections Button-Type Locking Outlets Such outlets do not require any special power cords to achieve the locking purpose. All you need to do is simply plug a regular power cord into the locking outlet and the outlet automatically locks the cord. To remove a power cord from the locking outlet: Press and hold down the tiny button adjacent to the outlet.

  • Page 41: Chapter 3 Initial Installation And Configuration

    Chapter 3 Initial Installation and Configuration This chapter explains how to install your PX3 and configure it for network connectivity. In This Chapter Connecting the PDU to a Power Source ............. 21 Connecting the PX3 to Your Network ..............22 Configuring the PX3 ....................

  • Page 42: Connecting The Px3 To Your Network

    Chapter 3: Initial Installation and Configuration Connecting the PX3 to Your Network To remotely administer the PX3, you must connect the PX3 to your local area network (LAN). PX3 can be connected to a wired or wireless network. Note: If your PX3 will work as a master device in the bridging mode, you must make a wired connection.

  • Page 43: Usb Wireless Lan Adapters

    Chapter 3: Initial Installation and Configuration ▪ Connect a USB hub to the USB-A port on the PX3. Then plug the supported USB wireless LAN adapter into the appropriate USB port on the hub. USB Wireless LAN Adapters (on page 23) for a list of supported wireless LAN adapters.

  • Page 44: Dual Ethernet Connection

    Chapter 3: Initial Installation and Configuration Dual Ethernet Connection One PX3 device has two Ethernet (LAN) ports: • ETH 10/100/1000 (marked in green) supports up to 1000 Mbps. This is "ETH1". • ETH 10/100 (marked in white) supports up to 100 Mbps. This is "ETH2". For more information on the two ports, see Connection Ports (on page 117,...

  • Page 45: Connecting A Mobile Device To Px3

    Chapter 3: Initial Installation and Configuration Retrieve the DHCP-assigned IPv4 address. Use the front panel LCD display to retrieve it. See Device Info (on page 141). Launch a web browser to configure the PX3. See Login (on page 159). Configuration via a connected mobile device: Download the PDView app to your mobile device.
  • Page 46 Chapter 3: Initial Installation and Configuration ▪ https://itunes.apple.com/app/raritan-pdview/id780382738 ▪ https://play.google.com/store/apps/details?id=com.raritan.android.pd view Install PDView. Step B: Connect the mobile device to PX3 Get an appropriate USB cable for your mobile device. ▪ iOS: Use the regular USB cable shipped with your iOS mobile device. ▪...
  • Page 47 Chapter 3: Initial Installation and Configuration The "Disconnected" message displays first when PDView has not detected the PX3 yet. A diagram in PDView indicates the appropriate USB port your mobile device should connect according to your mobile operating system. Note: PDView also shows the 'Disconnected' status during the firmware upgrade.
  • Page 48 Chapter 3: Initial Installation and Configuration b. The PDView shows the "Connected" message when it detects the connected PX3. If the factory-default user credentials "admin/raritan" remain unchanged, PDView automatically logs in to the web interface of PX3. If they have been changed, the login screen displays instead and you must enter appropriate user credentials for login.
  • Page 49 Chapter 3: Initial Installation and Configuration Saving User Credentials for PDView's Automatic Login When PDView detects PX3 for the "first" time, it automatically attempts to log in with the factory-default user credentials -- admin (user name) and raritan (password). If you have modified the factory-default user credentials, PDView's automatic login fails and the login screen displays for you to manually enter user credentials.
  • Page 50 ▪ Per default, three administrator user credentials are pre-configured for three companies' products: ▪ Raritan ▪ Legrand ▪ ServerTech (Server Technology) Modify existing user credentials or type new ones, and tap Save. ▪ The pre-configured admin credentials can be removed or overwritten...

  • Page 51: Connecting The Px3 To A Computer

    Chapter 3: Initial Installation and Configuration Connecting the PX3 to a Computer The PX3 can be connected to a computer for configuration via one of the following ports. • Ethernet port • USB-B port • RS-232 serial port (RJ-45) Note that the port locations on your models may differ. •...
  • Page 52 Chapter 3: Initial Installation and Configuration USB connection: A USB-to-serial driver is required in Windows . Install this driver before ® connecting the USB cable. See Installing the USB-to-Serial Driver (Optional) (on page 795). Connect a USB cable between a computer's USB-A port and the USB-B port of PX3.

  • Page 53: Bulk Configuration Methods

    Chapter 3: Initial Installation and Configuration DB9 pin signal DB9 pin No. RJ-45 pin No. RJ-45 pin signal 1 (Not connected) 9 (Not connected) Note: The blue Cisco RJ-45 to DB9 adapter cable CANNOT be used for connecting a modem. See RJ45-to-DB9 Cable Requirements for Modem Connections (on page 772).

  • Page 54: Cascading Multiple Px3 Devices For Sharing Ethernet Connectivity

    Chapter 3: Initial Installation and Configuration A USB flash drive: • Requirement: A FAT32- or supperfloppy-formatted USB flash drive containing two special configuration files and one devices list file is required. • Procedure: Plug this USB drive into the PX3. When a happy smiley is shown on the front panel display, press and hold one of the control buttons on the front panel until the display turns blank.

  • Page 55: Cascading All Devices Via Usb

    Chapter 3: Initial Installation and Configuration • Do NOT connect cascaded devices other than master to the LAN or WLAN. • (WIFI only) You must use Raritan's USB WIFI wireless LAN adapter instead of other WIFI adapters for wireless network connection. Troubleshooting: When a networking issue occurs, check the cascading connection and/or software settings of all devices in the chain.
  • Page 56 Chapter 3: Initial Installation and Configuration Number Device role Master device Slave 1 Slave 2 Slave 3 To cascade PX3 devices via USB: Make sure all Raritan devices are running firmware version 3.3.10 or later. Choose the appropriate one as the master device. ▪...
  • Page 57 Chapter 3: Initial Installation and Configuration A tip for USB cascading: The "USB-cascading" chain can be a combination of diverse Raritan products that support the USB-cascading feature, including PX3, PXC, Smart Rack Controller, transfer switch, PX2, BCM and EMX.

  • Page 58: Extended Cascading With Px3 Devices

    Chapter 3: Initial Installation and Configuration Extended Cascading with PX3 Devices PX3 supports cascading via either Ethernet or USB ports. This is because they have "two" Ethernet ports. You can use either Ethernet port on the PX3 PDU for cascading. You must set the cascading mode before establishing the chain.
  • Page 59 Chapter 3: Initial Installation and Configuration Number Device role Master device Slave 1 Slave 2 Slave 3...
  • Page 60 Chapter 3: Initial Installation and Configuration For instructions on USB cascading, see Cascading All Devices via USB (on page 35). Suggestions for extended cascading: • Ethernet cascading is recommended because of the longer distance, lower latency and more reliable connection it supports. •...

  • Page 61: Restrictions Of Port-Forwarding Connections

    Chapter 3: Initial Installation and Configuration Recommendations for cascade loops: You can connect both the first and the last PDU to your network (cascade loop) under the following conditions: The remaining network MUST use R/STP to avoid network loops. Both the first and the last PDUs MUST either attach to the same switch or, if they are attached to two separate switches, you must configure both ports of these switches so that the STP costs are high.
  • Page 62 Chapter 3: Initial Installation and Configuration • One cascaded device has two upstream devices via Ethernet and USB cables. • One cascaded device has two downstream devices.

  • Page 63: Power-Sharing Restrictions And Connection

    Chapter 3: Initial Installation and Configuration • One device is connected to another device via two cascading cables - USB and Ethernet cables. Power-Sharing Restrictions and Connection Two PX3 devices can share power supply to their controllers via EXPANSION ports, so that when either PX3 controller fails to receive DC 12V power from its inlet(s), it continues to receive backup power from another PX3 device which functions properly and therefore remains to be accessible to users.

  • Page 64: Making A Power-Sharing Connection

    Chapter 3: Initial Installation and Configuration • All internal sensors become "unavailable", including sensors of inlets, outlets, and OCPs. Exception: Only active energy data remains available. • Communications with relay/meter boards are lost. Therefore, firmware upgrade may fail due to this reason. Available data or operations on the PDU that enters the power-sharing mode: •...

  • Page 65: Power-Sharing Configurations And Restrictions

    Chapter 3: Initial Installation and Configuration Power-Sharing Configurations and Restrictions When either PX3 PDU enters the power-sharing mode, BOTH PDUs involved in the power-sharing connection support "less" external equipment than usual. It is strongly recommended to remove specific equipment from both PX3 PDUs when making a power-sharing connection.

  • Page 66: Supported Sensor Configurations For Power Sharing

    Chapter 3: Initial Installation and Configuration Supported Sensor Configurations for Power Sharing All information and restrictions described in this section apply to BOTH PDUs involved in the power-sharing configuration, unless otherwise specified. • There are no limitations for connecting Raritan's DPX or DPX2 environmental sensor packages to an iX7 PDU in the power-sharing mode.
  • Page 67 Chapter 3: Initial Installation and Configuration Other sensor restrictions when door handles are present: First make sure the connection of door handles complies with the above restrictions. The following restrictions apply only to the PDU that has all the door handles connected.

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

    Chapter 4 Connecting External Equipment (Optional) More features are available if you connect Raritan's or third-party external equipment to your PX3. In This Chapter Connecting Raritan Environmental Sensor Packages ......... 48 Connecting Asset Management Strips ..............68 Connecting a Logitech Webcam ................. 78 Connecting a GSM Modem .................

  • Page 69: Identifying The Sensor Port

    Chapter 4: Connecting External Equipment (Optional) Identifying the Sensor Port Warning: If you purchase Raritan's environmental sensor packages, make sure you connect them to the correct port on the PX3, or damages may be caused to PX3 and/or connected sensor packages. How to identify the SENSOR port: •...
  • Page 70 Chapter 4: Connecting External Equipment (Optional) Connect DX2 to the PX3: Connect a standard network patch cable (CAT5e or higher) to either RJ-45 port on a DX2 sensor package. If you want to cascade DX2 packages, get an additional standard network patch cable (CAT5e or higher) and then: Plug one end of the cable into the remaining RJ-45 port on the prior DX2 package.

  • Page 71: Dx Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) 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 and Actuators Guide (or Online Help) on Raritan website's Support page (http://www.raritan.com/support/).

  • Page 72: Dpx3 Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) Exception: You CANNOT cascade DX-PD2C5 sensor packages. One PX3 supports only one DX-PD2C5. Connect the first DX sensor package to the PX3 by plugging its cable's connector into the RJ-45 SENSOR port of the PX3. If needed, connect a DPX2 sensor package to the end of the DX chain.
  • Page 73 Chapter 4: Connecting External Equipment (Optional) Plug one end of the cable into the remaining RJ-45 port on the prior DPX3. b. Plug the other end into either RJ-45 port on an additional DPX3. Repeat the same steps to cascade more DPX3 sensor packages. Connect the first DPX3 sensor package to the PX3 by plugging its cable's connector into the RJ-45 SENSOR port of the PX3.

  • Page 74: Dpx2 Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) DPX2 Sensor Packages A DPX2 sensor cable is shipped with a DPX2 sensor package. This cable is made up of one RJ-12 connector and one to three head connectors. You have to connect DPX2 sensor packages to the sensor cable. For more information on DPX2 sensor packages, access the Environmental Sensors and Actuators Guide (or Online Help) on Raritan website's Support...
  • Page 75 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 76 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 Connecting a DPX2 Sensor Package to DX2, DX or DPX3 (on page 56). Connecting a DPX2 Sensor Package to DX2, DX or DPX3 You can connect one DPX2 sensor package to the "end"...

  • Page 77: Dpx Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) DPX Sensor Packages Most DPX sensor packages come with a factory-installed sensor cable, whose sensor connector is RJ-12. For the cabling length restrictions, see Supported Maximum DPX Sensor Distances (on page 61). Warning: For proper operation, wait for 15-30 seconds between each connection operation or each disconnection operation of environmental sensor packages.
  • Page 78 Chapter 4: Connecting External Equipment (Optional) If intended, connect one DPX sensor package to the OUT port of the differential air pressure sensor. It can be any DPX sensor package, such as a DPX-T3H1. The PX3 Raritan differential air pressure sensors One DPX sensor package (optional) RJ-12 to RJ-45 adapter Using an Optional DPX-ENVHUB4 Sensor Hub...
  • Page 79 Chapter 4: Connecting External Equipment (Optional) This diagram illustrates a configuration with a sensor hub connected. RJ-12 to RJ-45 adapter Raritan-provided phone cable DPX-ENVHUB4 sensor hub DPX sensor packages Using an Optional DPX-ENVHUB2 cable A Raritan DPX-ENVHUB2 cable doubles the number of connected environmental sensors per SENSOR port.
  • Page 80 Chapter 4: Connecting External Equipment (Optional) The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports. Repeat the above steps if there are additional SENSOR ports on your PX3.
  • Page 81 Chapter 4: Connecting External Equipment (Optional) Supported Maximum DPX Sensor Distances When connecting the following DPX sensor packages to the PX3, you must follow two restrictions. • DPX-CC2-TR • DPX-T1 • DPX-T3H1 • DPX-AF1 • DPX-T1DP1 Sensor connection restrictions: • Connect a DPX sensor package to the PX3 using the sensor cable pre-installed (or provided) by Raritan.

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

    Chapter 4: Connecting External Equipment (Optional) 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 PX3, except for the following differences: •...

  • Page 83: Mixing Diverse Sensor Types

    Chapter 4: Connecting External Equipment (Optional) A standard network cable DPX3-ENVHUB4 sensor hub Any Raritan sensor packages Mixing Diverse Sensor Types You can mix diverse sensor packages on one PX3 according to the following sensor combination principles. In some scenarios, the DPX3-ENVHUB4 sensor hub is required.
  • Page 84 Chapter 4: Connecting External Equipment (Optional) 1 DX + 1 DPX: • It is strongly recommended to use an RJ-12 to RJ-45 adapter to connect the DPX sensor package to the DX sensor package. Diverse combinations via the DPX3-ENVHUB4 sensor hub: •...
  • Page 85 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, DX or DX2 sensor package.
  • Page 86 Chapter 4: Connecting External Equipment (Optional)
  • Page 87 Chapter 4: Connecting External Equipment (Optional) Mix DX2, DX and DPX3 in a sensor chain: Any DX or DX2 sensor package in a chain can be replaced by a DPX3 sensor package, or vice versa. The total number of sensor packages in this chain cannot exceed 12.

  • Page 88: Connecting Asset Management Strips

    Chapter 4: Connecting External Equipment (Optional) You can add a DPX2 sensor package to the end of such a sensor-mixing chain if needed. See Connecting a DPX2 Sensor Package to DX2, DX or DPX3 (on page 56). Connecting Asset Management Strips You can remotely track the locations of up to 64 IT devices in the rack by connecting asset management strips (asset strips) to the PX3 after IT devices are tagged electronically.

  • Page 89: Combining Regular Asset Strips

    Chapter 4: Connecting External Equipment (Optional) Combining Regular Asset Strips Each tag port on the regular asset strips corresponds to a rack unit and can be used to locate IT devices in a specific rack (or cabinet). For each rack, you can attach asset strips up to 64U long, consisting of one MASTER and multiple SLAVE asset strips.
  • Page 90 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 strip. Screw up the U-shaped sheet metal to reinforce the connection. Connect another 8U slave strip to the one being attached to the master strip in the same manner as Step 1.

  • Page 91: Introduction To Asset Tags

    Chapter 4: Connecting External Equipment (Optional) Introduction to Asset Tags You need both asset strips and asset tags for tracking IT devices. Asset tags provide an ID number for each IT device. The asset tags are adhered to an IT device at one end and plugged in to an asset strip at the other. The asset strip is connected to the PX3, and the asset tag transmits the ID and positioning information to the asset strip.
  • Page 92 Chapter 4: Connecting External Equipment (Optional) The PX3 device supplies power to the connected asset strip assembly. All LEDs on the asset strip assembly may cycle through different colors during the power-on process if the asset strip's firmware is being upgraded by the PX3.

  • Page 93: Connecting Blade Extension Strips

    Chapter 4: Connecting External Equipment (Optional) 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 strip but requires a tag connector cable for connecting it to a tag port on the regular or composite asset strip.
  • Page 94 Chapter 4: Connecting External Equipment (Optional) Mylar section with the adhesive tape Tag ports Cable socket(s) for connecting the tag connector cable Note: Each tag port on the blade extension strip is labeled a number, which is displayed as the slot number in the PX3 device's web interface. To install a blade extension strip: Connect the tag connector cable to the blade extension strip.

  • Page 95: Connecting Composite Asset Strips (Ams-Mx-Z)

    Chapter 4: Connecting External Equipment (Optional) b. Plug the tag connector of the asset tag into a tag port on the blade extension strip. Repeat the above step until all blade servers in the chassis are connected to the blade extension strip via asset tags. Plug the tag connector of the blade extension strip into the closest tag port of the regular or composite asset strip on the rack.
  • Page 96 Chapter 4: Connecting External Equipment (Optional) The composite asset strip is especially useful for tracking large devices such as SAN boxes in the cabinet. The following diagram illustrates AMS-M3-Z. Two RJ-45 connectors Tag ports Important: DO NOT hot swap or hot plug any AMS-Mx-Z in a composite asset strip chain after connecting the chain to the PX3 device.
  • Page 97 Chapter 4: Connecting External Equipment (Optional) Affix an asset tag to the IT device. Then connect this asset tag to the composite asset strip by plugging the tag connector into the tag port on the composite asset strip. For details, see Connecting Regular Asset Strips to PX3 (on page 71).

  • Page 98: Connecting A Logitech Webcam

    Chapter 4: Connecting External Equipment (Optional) Raritan devices Maximum strips per chain PX3TS transfer switches PMC (BCM2 series) Note: In case you hot swap or hot plug any AMS-Mx-Z in a chain, causing the FEATURE port of the PX3 to malfunction, you can power cycle or reset the PX3 to restore the FEATURE port.

  • Page 99: Connecting A Gsm Modem

    Chapter 4: Connecting External Equipment (Optional) Connecting a GSM Modem The following Cinterion GSM modems can be connected to the PX3 in order to ® send SMS messages containing event information. • MC52iT • MC55iT • EHS6T Available Actions (on page 334) for more information on SMS messages. Note: PX3 cannot receive SMS messages.

  • Page 100: Connecting An External Beeper

    Chapter 4: Connecting External Equipment (Optional) ▪ A third party RJ-45 to "DB9 male" adapter/cable is required for this connection. See RJ45-to-DB9 Cable Requirements for Modem Connections (on page 772). You need to enable the modem dial-in support to take advantage of this feature, see Configuring the Serial Port (on page 387).

  • Page 101: Connecting A Modbus Rtu Device Or Bus

    Chapter 4: Connecting External Equipment (Optional) Connecting a Modbus RTU Device or Bus If connecting the Modbus RTU devices to PX3 and enabling the Modbus Gateway feature, the Modbus TCP clients on your network will be able to communicate with those Modbus RTU devices attached to PX3. To use the Modbus Gateway feature: Connect a Modbus RTU device, or a Modbus bus with multiple RTU devices, to the PX3 via two adapters described below.

  • Page 102: Chapter 5 Pdu Linking

    Chapter 5 PDU Linking The PDU Linking feature allows the linking configuration of a single master PDU unit to multiple link units for faster and more efficient power management. Only one master unit is connected to the network in PDU Linking, which allows a cost-efficient PDU operation and networking infrastructure.

  • Page 103: Faqs

    Chapter 5: PDU Linking FAQs What’s the difference between a "master unit" and a "link unit"? Master and link units are the same model PDUs that are equal to each other, and each has its own IP address. You designate a PDU as the master unit by logging into the unit and then adding a link unit.
  • Page 104 Chapter 5: PDU Linking Note: Re-linking uses the same Link Unit ID and hostname, but you will need to reauthenticate with your login credentials. What user privileges are required for managing the PDU Linking configuration? Administrative privileges are required for both the master unit and link unit. To add a link, your administrative login account is required, but after that you only log in to the master to manage the chain, as all link units in the chain are visible in the user interface from the master unit view.

  • Page 105: Pdu Linking In The Web Gui

    Chapter 5: PDU Linking How are firmware updates handled? Uploaded firmware images in the GUI are automatically distributed to all link units at the same time. Starting a firmware update requires the same image to be uploaded to all units. Does PDU Linking support mass deployment of PDUs? Yes, mass deployment has been extended to support a setup for the PDU Linking feature (multi-IP or single-IP) via the Raritan Mass Deployment Utility,...

  • Page 106: Designating The Master Unit

    Chapter 5: PDU Linking Designating the Master Unit Log in to the PDU you want to designate as the master unit. When you add the first link unit, a chain is established between the master and the new link, and the master becomes ID "1".

  • Page 107: Adding A Link Unit

    Chapter 5: PDU Linking Adding a Link Unit A link unit (up to seven units) can be added to a single master unit. On the PDU page, the master unit is displayed as highlighted in the following screen example in red. Note the following section "Link PDUs", designed for the PDU Linking feature, where multiple PDUs added to the chain are displayed as the link units.
  • Page 108 Chapter 5: PDU Linking To add a link unit: Log in to the master PDU as shown displayed above in the PDU page. Click Add Link PDU. The following add box displays: The Link ID is populated as the next available ID number (2-8), assigned sequentially as each link unit is added to the chain to identify the link unit in the user interfaces.
  • Page 109 Chapter 5: PDU Linking The new link unit is added on the PDU page with the master unit, in a list in the Link PDUs section. All link units added to the chain in this way are now managed by the single master unit. The PDU page displays the following information about the link unit: •...

  • Page 110: Master Units Manage Link Units

    Chapter 5: PDU Linking About the Link ID The PDU ID "1" is automated and reserved internally for the master unit. The master unit’s PDU ID "1" cannot be edited. The Link ID "2-8" is available for you to select as the ID for each of the link units you add to chain.

  • Page 111: Releasing A Link Unit

    Chapter 5: PDU Linking Releasing a Link Unit Releasing a link unit means the unit is separated from the chain and the unit then becomes standalone. The master unit no longer has access to the released link unit. Note: If a release action is attempted on a link unit when the unit is an unreachable state, a warning message displays, and the master will not recognize the link unit.

  • Page 112: Switching To A Different Pdu

    Chapter 5: PDU Linking To release a link unit: From the PDU page, in the Link PDUs section, click a link unit to select it. Click Release Link PDU. A confirmation prompts to cancel or release: If released, the link unit is removed from the PDU page. Switching to a Different PDU Switching PDUs is a control function noted by the Switch control in the in the upper left corner of the PDU, Outlet, Outlet Groups, OCPs, and Feature Ports...

  • Page 113: Re-Linking A Link Unit

    Chapter 5: PDU Linking To return to the PDU page for the master, select the master PDU. Master number "1" appears in parentheses. Note: The Switch control is only available when there is at least one link unit in the chain; otherwise, the page defaults to displaying only the data of the master PDU.
  • Page 114 Chapter 5: PDU Linking Although re-linking uses the same Link Unit ID and hostname of the unreachable unit, you will need to reauthenticate with your login credentials shown below. Click the Re-link button. The status of the link unit changes to "OK".

  • Page 115: Viewing Link Unit Information

    Chapter 5: PDU Linking Viewing Link Unit Information When a link unit is added to the chain, the master unit view (through the GUI) allows full access to the operational data of the link unit. For example, using the navigation tabs of the GUI, link unit data is displayed in several pages: the Dashboard, PDUs, Inlets, Outlets, Outlet Groups, Peripherals, and Feature Ports.
  • Page 116 Chapter 5: PDU Linking...
  • Page 117 Chapter 5: PDU Linking PDU Page The PDU page displays the details and settings for the selected unit (master or link). The Link PDUs section is only shown when the master unit is selected.
  • Page 118 Chapter 5: PDU Linking Inlets Page On the Inlets page, the master unit and link units are displayed together on the same page. In this example, data for the single inlet of the master "My PDU (1)" Inlet I1, and the inlet of the link unit "My PDU (2)" Inlet I1, are shown together on the Inlets page.
  • Page 119 Chapter 5: PDU Linking Outlets Page The Outlets page defaults to display only the outlets of the master unit, in this example 30 outlets.
  • Page 120 Chapter 5: PDU Linking Viewing Outlets for Link Units On the Outlets page, you can switch from the master to the link. From the Outlets page drop-down, select the link unit "My PDU (2)". Note: To view outlets for a specific link unit, the link unit must be selected by name.
  • Page 121 Chapter 5: PDU Linking You can switch back to the master unit by selecting "My PDU (1)". Note: The Switch control is only available when there is at least one link unit in the chain; otherwise, the page defaults to displaying only the outlets of the master.
  • Page 122 Chapter 5: PDU Linking From the Outlets page (either master or link), select an outlet in the list to view operational details for the specific outlet and to configure outlet settings.

  • Page 123: Outlet Groups

    Chapter 5: PDU Linking Outlet Groups An outlet group is a named collection of selected outlets. When user-defined, an outlet group can contain outlets from different PDUs, including both master and link units. Outlet groups support fast and efficient outlet control actions (On, Off, Power Cycle) across multiple PDUs, and with PDU Linking, member outlets for the master and its link units can be collected in the same outlet group.
  • Page 124 Chapter 5: PDU Linking...
  • Page 125 Chapter 5: PDU Linking Viewing Outlet Group Details Click an outlet group name in the list to display operations details for the outlet group. From this page, you can issue the outlet control actions On, Off, and Cycle (power cycling to restore the outlet) for all member outlets in the outlet group.
  • Page 126 Chapter 5: PDU Linking To add an outlet group: On the Outlet Groups page, click . The New Outlet Group page displays, defaulting to the outlets in the master unit. Type a name for the new outlet group. Select individual member outlets for the master as shown in the default page, or to select all outlets for the master, select My PDU (1).
  • Page 127 Chapter 5: PDU Linking Controlling Outlets in Groups From the Outlet Groups page, select an outlet group by name. Click the desired control: On, Off, or Cycle. This example shows three outlets in status On. When Off is clicked, a prompt appears to confirm applying the action to all outlets in the group.

  • Page 128: Pairwise Outlet Groups

    Chapter 5: PDU Linking Pairwise Outlet Groups The PDU Linking feature offers the "pairwise" functionality for outlet grouping. Pairwise lets you create auto-named pairs of outlet groups than span multiple PDUs (master and link units) using the same outlet label. Pairwise simplifies outlet switching up or down a server by automatically creating multiple outlet groups, each containing one pair of outlets between PDUs that can be controlled as a pair-related outlet group.
  • Page 129 Chapter 5: PDU Linking Confirm the pairwise creation. Pairwise outlet groups are created and named automatically for all outlets on the master and link unit, such as "Outlet pair 1", "Outlet pair 2", "Outlet pair 3", etc.

  • Page 130: Ocps Page

    Chapter 5: PDU Linking OCPs Page Overcurrent protectors from both master and link PDUs are displayed together on the same OCPs page. If sensors are present on the units, sensor data for both master and link units will also appear on the page. Peripherals Page The Peripherals Page shows peripheral devices connected to the master or link unit.

  • Page 131: Feature Ports Page

    Chapter 5: PDU Linking Feature Ports Page The Feature Ports Page can display device Asset Strip information and the Switch PDU control is available for the data from both the master and link units. Displays for Master and Link Units Each unit in a PDU Linking chain displays its own PDU data (inlets, outlets, sensors, alerts, etc.) Master unit:...
  • Page 132 Chapter 5: PDU Linking PDU information shows a list of link units with host name/IP address, model, device name, serial number, firmware version, and communication status. Link units: No display of alarms (no event engine on link units) PDU information shows the master IP address...

  • Page 133: Pdu Linking In The Cli

    Chapter 5: PDU Linking PDU Linking in the CLI For each PDU in a chain, you can list the PDUs, switch a PDU, add a new link PDU, and release a link PDU. You can then use all regular PDU-related commands as usual to access and control individual units, as with any standalone PDU.

  • Page 134: Pdu Linking Cli Commands

    Chapter 5: PDU Linking PDU Linking CLI Commands PDU List Displays the following information for each unit: • Link ID • Communication status (for link unit only) • Device name • Model name • Serial number • Firmware version # pdu list Switch PDU Switch between the master and link units.

  • Page 135: Chapter 6 Introduction To Pdu Components

    Chapter 6 Introduction to PDU Components This chapter explains how to use the PX3 device, including: • Introduction to the LEDs and ports on the PDU • Operation of the front panel display • The overcurrent protector's behavior • The internal beeper's behavior •...

  • Page 136: Inlet

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

  • Page 137: Outlets

    Chapter 6: Introduction to PDU Components Outlets The total number of outlets varies from model to model. PX3-1000 Series These models are NOT outlet-switching capable so all outlets are always in the ON state. Outlet LEDs are not available. Connection Ports Depending on the model you purchased, the total number of ports available varies.
  • Page 138 Chapter 6: Introduction to PDU Components Connection Port Functions The table below explains the function of each port. Port Used for... • Cascading PX3 devices for sharing a network connection. See Cascading USB-B All Devices via USB (on page 35). •...

  • Page 139: Dot-Matrix Lcd Display

    Chapter 6: Introduction to PDU Components Port Used for... SENSOR Connection to one of the following devices: ▪ (RJ-45) Raritan's environmental sensor package(s). ▪ Raritan's sensor hub, which expands the number of a sensor port to four ports. ETH 10/100/1000, PX3 has two Ethernet ports.
  • Page 140 Chapter 6: Introduction to PDU Components You can use the LCD display to view the PDU information and even switch an outlet. It consists of: • A dot-matrix LCD display • Four control buttons Zero U models automatically adjust the orientation of the content shown on the dot-matrix LCD display after detecting the direction in which the PDU is installed.
  • Page 141 Chapter 6: Introduction to PDU Components Automatic and Manual Modes After powering on or resetting the PX3, the front panel LCD display first shows some dots, then Raritan logo and finally enters the automatic mode. Automatic mode without alerts available: In this mode, the LCD display cycles through the inlet information as long as there are no alerts.
  • Page 142 Chapter 6: Introduction to PDU Components Control Buttons Use the control buttons to navigate to the menu in the manual mode. Button Function Down Back -- OR -- Switch between automatic and manual modes...
  • Page 143 Chapter 6: Introduction to PDU Components Operating the Dot-Matrix LCD Display Enter manual mode when you want to operate the dot-matrix LCD display. You can use the dot-matrix LCD display to: • Show information of the PX3, built-in components, or connected peripheral devices •...
  • Page 144 Chapter 6: Introduction to PDU Components Main Menu The Main Menu contains 6 to 8 menu commands, depending on the model. Control buttons that can be used and the system time are shown at the bottom of the LCD display. The currently-selected item's number and total of menu items are indicated in the top-right corner of the display.
  • Page 145 Chapter 6: Introduction to PDU Components Menu command Function Indicates all alerted sensors, if any. See Alerts (on page 125). Alerts Shows the internal beeper's state, and, if it is on, the reason for turning on. If your PDU has multiple inlets, this menu item also shows the total active power and total active energy.
  • Page 146 Chapter 6: Introduction to PDU Components Alerted sensors, if any, are highlighted in either red or yellow. For color definitions, see Yellow- or Red-Highlighted Sensors (on page 208). ▪ The top and bottom bars on the LCD display may be yellow or red, depending on the type(s) of available alerts.
  • Page 147 Chapter 6: Introduction to PDU Components Number Description The 'Details' command appears for alarms only. ▪ If your Alert List comprises alerted sensors only, then 'Details' is not shown. Press to view additional pages. When there are multiple pages, page numbers appear in the top-right corner of the display. (Optional) If there are alarms in the Alert List, you can perform the following operations.
  • Page 148 Chapter 6: Introduction to PDU Components Depending on the model you purchased, the "PDU" menu command may show one or all of the following data. • Internal beeper states -- Active or Off • Total active power of the PX3 -- available on multi-inlet models and in-line monitors only •...
  • Page 149 Chapter 6: Introduction to PDU Components Press to show the status of the 12V power supply to the controller. For details on this sensor, see +12V Power Supply Sensor (on page 186). If your PX3 has more than one inlet, press to show the information of total active power (W) and total active energy (Wh).
  • Page 150 Chapter 6: Introduction to PDU Components Muting the Internal Beeper After enabling the internal beeper's mute control function, you can choose to mute the beeper via the front panel whenever the beeper sounds for an alarm. By default, the beeper's mute control feature via front panel is enabled. Tip: To disable this feature, see Front Panel Settings (on page 386).
  • Page 151 Chapter 6: Introduction to PDU Components The beeper stops beeping, and the Beeper State shows "Active (Muted)". Note that the alarmed state remains unchanged yet for the moment. Inlet An inlet's information is divided into two pages. Page numbers are indicated in the top-right corner of the LCD display.
  • Page 152 Chapter 6: Introduction to PDU Components To go to other page(s), press ▪ For a single-phase model, the second page shows the inlet's voltage (V), frequency (Hz) and current (A). ▪ For a three-phase model, the next several pages respectively show unbalanced current's percentage, line frequency, and the current and voltage values of each line.
  • Page 153 Chapter 6: Introduction to PDU Components The LCD display shows a list of overcurrent protectors similar to the following diagram. Number Description Overcurrent protector names. Associated lines and rated current are displayed below each overcurrent protector's name. Current reading of the corresponding overcurrent protector. If the desired overcurrent protector is not visible, press scroll up or down.
  • Page 154 Chapter 6: Introduction to PDU Components The display shows a list of environmental sensors/actuators. ▪ If the desired sensor or actuator is not visible, press scroll up or down. ▪ When the list exceeds one page, the currently-selected sensor/actuator's ID number and total of managed sensors/actuators are indicated in the top-right corner of the display.
  • Page 155 Chapter 6: Introduction to PDU Components Number Description Sensor or actuator states as listed below. For further information, see Sensor/Actuator States (on page 211). ▪ n/a = unavailable ▪ Normal ▪ Alarmed ▪ Lower Critical = below lower critical ▪ Lower Warning = below lower warning ▪...
  • Page 156 Chapter 6: Introduction to PDU Components Number Description The following information is listed. ▪ Serial number ▪ Chain position, which involves the following information: ▪ Port <N>: <N> is the number of the sensor port where this sensor or actuator is connected. This number is always 1 for PX3. ▪...
  • Page 157 Chapter 6: Introduction to PDU Components Press to turn on or off the actuator. A confirmation message similar to the following is shown. Press to select Yes or No, and then press Verify that the actuator status shown on the LCD display has been changed.
  • Page 158 Chapter 6: Introduction to PDU Components ▪ The number of tags includes both the tags attached to the asset strip and those attached to the blade extension strip, if any. Press to show this asset strip's details, including: ▪ State - strip status. ▪...
  • Page 159 Chapter 6: Introduction to PDU Components ▪ Orientation - the strip's orientation. Press again to show a list of available tags and their information. ▪ When the list exceeds one page, the currently-selected main tag and total of available main tags are indicated in the top-right corner of the display.
  • Page 160 Chapter 6: Introduction to PDU Components Number Description Two numbers are displayed for each tag. ▪ Rack unit number: The number assigned to this tag based on the selected numbering mode. See Asset Strip (on page 225). ▪ The index number in parentheses: The physical port number printed on the asset strip.
  • Page 161 Chapter 6: Introduction to PDU Components Number Description The slot number of each asset tag The connected asset tag's ID number (barcode). Device Info The display shows the device's information, network and IPv4/IPv6 settings through various pages. Page numbers are indicated in the top-right corner of the LCD display.
  • Page 162 Chapter 6: Introduction to PDU Components Press to show the Network Common page. Number Description DNS servers. Default gateways. Press to show the Network Cascading page.
  • Page 163 Chapter 6: Introduction to PDU Components Number Description Cascading status, which can be one of the following: ▪ No Cascading: This device's cascading mode is set to None. See Setting the Cascading Mode (on page 270). ▪ Network Bridge Enabled: This device's cascading mode is set to Bridging. Its IP address is also displayed on this page.
  • Page 164 Chapter 6: Introduction to PDU Components A PX3 has two Ethernet pages -- ETH1 and ETH2. Number Description Ethernet interface information, including: ▪ MAC address. ▪ Speed. ▪ Full or half duplex.
  • Page 165 Chapter 6: Introduction to PDU Components Number Description IPv4/IPv6 network information, including: ▪ Network configuration: DHCP (or Automatic), or Static. Static represents Static ▪ IP address. ▪ Prefix length, such as "/24". Note: If you disable any Ethernet interface, a message 'Interface Disabled' is shown.
  • Page 166 Chapter 6: Introduction to PDU Components -- OR -- Number Description If NO supported WLAN adapter is plugged or detected, the message "No Adapter Detected" is shown. If a supported WLAN adapter is detected and configured properly, wireless network information is shown instead, including: ▪...
  • Page 167 Chapter 6: Introduction to PDU Components Alerts Notice in a Yellow or Red Screen In the automatic mode, if an alert occurs, the LCD display automatically shows a yellow or red screen which indicates the total number of alerted sensors and information of the latest transitions.
  • Page 168 Chapter 6: Introduction to PDU Components When there is any alarm present: The LCD display looks similar to the above diagram except that it shows the alarm(s) and the available command in the bottom-right corner is 'Actions' instead of 'Alert list'.
  • Page 169 Chapter 6: Introduction to PDU Components Available operations: • For the notice listing alerted sensors only, press to view a list of all alerted sensors. See Alerts (on page 125). • For the notice where at least an alarm is present, press .
  • Page 170 Chapter 6: Introduction to PDU Components ▪ Show alert list: This option lists all of alerted sensors and alarms. You still can choose to acknowledge alarms after viewing the list. Alerts (on page 125). ▪ Acknowledge all alarms: This option immediately acknowledges all existing alarms, without showing the list of alarms.

  • Page 171: Reset Button

    Chapter 6: Introduction to PDU Components In the end, a message appears, indicating whether the firmware upgrade succeeds or fails. Reset Button The reset button is located inside the small hole labeled RESET near the display panel. Pressing this reset button restarts the PX3 software without any loss of power to outlets.

  • Page 172: Resetting The Button-Type Circuit Breaker

    Chapter 6: Introduction to PDU Components 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: Locate the breaker whose ON button is up, indicating that the breaker has tripped.

  • Page 173: Fuse

    Chapter 6: Introduction to PDU Components Examine your PX3 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. Pull up the operating handle until the colorful rectangle or triangle turns RED.
  • Page 174 Chapter 6: Introduction to PDU Components Verify the new fuse's rating against the rating specified in the fuse holder's cover. Push the cover of the fuse holder to expose the fuse. Take the fuse out of the holder. Insert a new fuse into the holder. There is no orientation limit for fuse insertion.

  • Page 175: Fuse Replacement On 1U Models

    Chapter 6: Introduction to PDU Components 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. Number Description Fuse carrier Fuse knob where a fuse is installed To replace a fuse on 1U PDUs: Disconnect the PDU's power cord from the power source.

  • Page 176: Beeper

    Chapter 6: Introduction to PDU Components Number Description Fuse Install this knob along with the new fuse into the fuse carrier using a flat screwdriver. Have this knob's slot inclined 45 degrees when inserting the knob into the fuse carrier. b.

  • Page 177: Replaceable Controller

    Chapter 6: Introduction to PDU Components Replaceable Controller A PX3 Zero U model provides flexibility for replacement of its controller. The controller, which contains the dot-matrix LCD display and connection ports, is usually located in the middle of the PDU. If the controller is broken, you can simply send the controller back to Raritan for repair, or purchase a new controller from Raritan.

  • Page 178: Threaded Grounding Point

    Chapter 6: Introduction to PDU Components Disconnect the PDU's controller cable from the controller. Get a new PX3 controller and install it back into the PDU in the reverse order. Threaded Grounding Point If the PX3 model you purchased is designed to have a threaded grounding point, you can identify it via the grounding symbol as shown below: Wire this point to an electrical system in order to protectively ground the PX3.

  • Page 179: Chapter 7 Using The Web Interface

    Chapter 7 Using the Web Interface This chapter explains how to use the web interface to administer the PX3. In This Chapter Supported Web Browsers ................. 159 Login, Logout and Password Change ..............159 Web Interface Overview ................... 164 Dashboard ......................171 PDU ........................
  • Page 180 Chapter 7: Using the Web Interface ▪ If the link-local addressing has been enabled, you can type pdu.local instead of an IP address. See APIPA and Link-Local Addressing page 2). Tip: You can also enter the desired page's URL so that you can immediately go to that page after login.
  • Page 181 Chapter 7: Using the Web Interface Depending on your hardware configuration, your web interface shown onscreen may look slightly different from the image below. Note: The address to access a slave device in the Port Forwarding mode via non-standard ports is a combination of a protocol (http:// or https://), an IP address and a port number.

  • Page 182: Changing Your Password

    Chapter 7: Using the Web Interface Changing Your Password You need appropriate permissions to change your password. Refer to the following for details. To change other users' passwords, Administrator Privileges are required instead. See Editing or Deleting Users (on page 244). Password change request on first login: On first login, if you have both the Change Local User Management and Change Security Settings permissions, you can choose to either change your password...

  • Page 183: Remembering User Names And Passwords

    Chapter 7: Using the Web Interface ▪ A password comprises 4 to 64 characters. Remembering User Names and Passwords PX3 supports the password manager of common web browsers, including: • Microsoft Internet Explorer ® • Mozilla Firefox ® • Google Chrome ®...

  • Page 184: Web Interface Overview

    Chapter 7: Using the Web Interface Web Interface Overview The web interface consists of four areas as shown below. Operation: Click any menu or submenu item in the area of That item's data/setup page is then opened in the area of Now you can view or configure settings on the opened page.
  • Page 185 Chapter 7: Using the Web Interface To return to the main menu and the Dashboard page, click on the top-left corner. Number Web interface element Menu (on page 167) Data/setup page of the selected menu item. ▪ Left side: - PX3 device name.
  • Page 186 Chapter 7: Using the Web Interface Number Web interface element Note: To customize the device name, see (on page 182). ▪ Right side: - Displayed language, which is English (EN) by default. You can change it. - Your login name, which you can click to view your user account settings. - Logout button.

  • Page 187: Menu

    Chapter 7: Using the Web Interface Menu Depending on your model and hardware configuration, your PX3 may show all or some menu items shown below. Menu Information shown Dashboard Summary of the PX3 status, including a list of alerted sensors and alarms, if any. Dashboard (on page 171).
  • Page 188 Chapter 7: Using the Web Interface Menu Information shown Feature Port Status and settings of the device connected to the Feature port(s), which can be one of the following. The name 'Feature ▪ Asset Strip Port(s)' will be ▪ External Beeper replaced with one ▪...

  • Page 189: Quick Access To A Specific Page

    Chapter 7: Using the Web Interface If a menu item contains the submenu, the submenu is shown after clicking that item. To return to the previous menu list, do any below: • Click the topmost link with the symbol <. For example, click •...

  • Page 190: Sorting A List

    Chapter 7: Using the Web Interface Sorting a List If any list displays an arrow ( ) in one of its column headers, you are allowed to resort the list by clicking any column header. The list will be resorted in the ascending or descending order based on the selected column. Illustration -- Event Log: By default, the Event Log is sorted in the descending order based on the ID column.

  • Page 191: Dashboard

    Chapter 7: Using the Web Interface Dashboard The Dashboard page contains four to five sections, depending on your model.
  • Page 192 Chapter 7: Using the Web Interface Number Section Information shown ▪ Overview of inlet power data Inlet I1 ▪ A current bar per phase, which changes colors to indicate the RMS current state - green: normal - yellow: warning - red: critical Dashboard - Inlet I1 (on page 173).

  • Page 193: Dashboard - Inlet I1

    Chapter 7: Using the Web Interface This section does NOT display as long as there are no hardware failures present. Hardware Issue Detection (on page 421). Dashboard - Inlet I1 The number of phases shown in the Inlet section is model dependent. Link to the Inlet page: To view more information or configure the inlet(s), click this section's title 'Inlet I1' to go to the Inlet page.
  • Page 194 Chapter 7: Using the Web Interface The left side lists all or some of the following data. Available data is model dependent. • Active power (kW or W) • Apparent power (kVA or VA) • Active energy (kWh or Wh) •...

  • Page 195: Dashboard - Ocp

    Chapter 7: Using the Web Interface Dashboard - OCP Availability and total number of OCPs depend on the models. Each OCP's link: To view more information or configure individual OCPs, click the desired OCP's index number, which is C1, C2 and the like, to go to its setup page. Each OCP's power data: OCP data from top to bottom includes: •...

  • Page 196: Dashboard - Alerted Sensors

    Chapter 7: Using the Web Interface • A bar showing OCP current levels • OCP status -- open or closed • Associated line pair The RMS current bars automatically change colors to indicate the current status if OCP thresholds have been enabled. To configure thresholds, see OCPs (on page 195).
  • Page 197 Chapter 7: Using the Web Interface Summary in the section title: Information in parentheses adjacent to the title is the total number of alerted sensors. For example: • 1 Critical: 1 sensor enters the critical or alarmed state. - Numeric sensors enter the critical state. - State sensors enter the alarmed state.

  • Page 198: Dashboard - Inlet History

    Chapter 7: Using the Web Interface Dashboard - Inlet History • The Inlet History graph displays the history of the sensor values. Select a different data type by clicking the selector below the diagram. •...
  • Page 199 Chapter 7: Using the Web Interface ▪ To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. Inlet selection on multi-inlet models: If your PDU is a multi-inlet model, you can have one or multiple inlets show their power charts by selecting the checkbox(es) of the desired inlet(s).

  • Page 200: Dashboard - Alarms

    Chapter 7: Using the Web Interface ▪ When both inlets are shown in the chart, simply hover your mouse over either inlet's data line. Both inlets' values display simultaneously, marked with corresponding colors. Dashboard - Alarms If configuring any event rules which require users to take the acknowledgment action, the Alarms section will list any event which no one acknowledges yet since event occurrence.
  • Page 201 Chapter 7: Using the Web Interface This table explains each column of the alarms list. Field Description Name Custom name of the Alarm action. Reason The first event that triggers the alert. First Appearance Date and time when the event indicated in the Reason column occurred for the first time.

  • Page 202: Pdu

    Chapter 7: Using the Web Interface The PX3 device's generic information and PDU settings are available on the PDU page. To open the PDU page, click 'PDU' in the Menu (on page 167). Device information shown: • Firmware version • Serial number •...

  • Page 203: Internal Beeper State

    Chapter 7: Using the Web Interface To configure the thresholds of total active energy and power: For a multi-inlet model or an in-line monitor, a "Thresholds" section is available on the PDU page. See Setting Thresholds for Total Active Energy or Power page 184).

  • Page 204: Time Units

    Chapter 7: Using the Web Interface Tip: To check the internal beeper state via CLI, see PDU Configuration (on page 466). Time Units If you choose to type a new value in the time-related fields, such as the "Idle timeout period" field, you must add a time unit after the numeric value. For example, you can type '15 s' for 15 seconds.
  • Page 205 Chapter 7: Using the Web Interface Click the Thresholds title bar at the bottom of the page to display thresholds. Click the desired sensor (required), and then click Edit Thresholds. Make changes as needed. ▪ To enable any threshold, select the corresponding checkbox. ▪...

  • Page 206: +12V Power Supply Sensor

    Chapter 7: Using the Web Interface +12V Power Supply Sensor The PX3's controller receives DC 12V power from its inlet. A sensor monitors the power supply status and indicates it on the PDU page. State Description The PX3 controller is receiving power from its own inlet. fault The PX3 controller cannot receive power from its own inlet because of a power failure on the inlet or a broken...

  • Page 207: Inlet

    Chapter 7: Using the Web Interface Inlet You can view all inlet information, configure inlet-related settings, or reset the inlet active energy on the Inlet page. To open this page, click 'Inlet' in the Menu (on page 167). Inlet thresholds, once enabled, help you identify whether the inlet enters the warning or critical level.
  • Page 208 Chapter 7: Using the Web Interface To reset the inlet's active energy counter: Only users with the "Admin" role assigned can reset active energy readings. The energy reset feature per inlet is especially useful when your PX3 has more than one inlet. Click Click Reset on the confirmation message.
  • Page 209 Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 777). Click Save. To configure residual current thresholds: If your model supports residual current monitoring, a section titled "Residual Current Monitor"...

  • Page 210: Configuring A Multi-Inlet Model

    Chapter 7: Using the Web Interface Configuring a Multi-Inlet Model If the PX3 has more than one inlet, the Inlets page lists all inlets. To view or configure each inlet: Click 'Show Details' of the desired inlet. Now you can configure the selected inlet, such as enabling thresholds or resetting its energy.
  • Page 211 Chapter 7: Using the Web Interface Click Save. The inlet status now shows "Disabled." To disable additional inlets, repeat the above steps. ▪ If disabling an inlet will result in all inlets being disabled, a confirmation dialog appears, indicating that all inlets will be disabled. Then click Yes to confirm this operation or No to abort it.

  • Page 212: Outlets

    Chapter 7: Using the Web Interface Outlets The Outlets page shows a list of all outlets and their data, such as each outlet's associated lines. To open this page, click 'Outlets' in the Menu (on page 167). • Go to an individual outlet's data/setup page by clicking an outlet's name. Individual Outlet Pages (on page 193).

  • Page 213: Available Data Of The Outlets Overview Page

    Chapter 7: Using the Web Interface Available Data of the Outlets Overview Page All of the following outlet data is displayed on the outlets overview page based on your selection. To show or hide specific data, click . See Outlets page 192).
  • Page 214 Chapter 7: Using the Web Interface ▪ The outlet's custom name, if available, is displayed in the outlets list, following by its label in parentheses. Other operations: • You can go to another outlet's data/setup page by clicking the outlet selector on the top-left corner.

  • Page 215: Ocps

    Chapter 7: Using the Web Interface Field Description Overcurrent protector This information is available only when your PX3 has overcurrent protectors. Overcurrent protector associated with this outlet OCPs The OCPs page is available only when your PX3 has overcurrent protectors, such as circuit breakers.
  • Page 216 Chapter 7: Using the Web Interface ▪ The RMS current bars change colors to indicate the status if the OCP thresholds have been configured and enabled. Status Bar colors normal above upper warning above upper critical Note: The "below lower warning" and "below lower critical" states also show yellow and red colors respectively.

  • Page 217: Individual Ocp

    Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 777). Click Save. Individual OCP Pages An OCP's data/setup page is opened after clicking any OCP's name on the OCPs or Dashboard page.
  • Page 218 Chapter 7: Using the Web Interface Field Description RMS current This OCP's current state and readings, including current drawn and current remaining. To customize this OCP's name: Click Edit Settings. Type a name. Click Save. To view this OCP's RMS current chart: This OCP's data chart is shown in the Overcurrent Protector History section.
  • Page 219 Chapter 7: Using the Web Interface ▪ To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. To configure this OCP's threshold settings: By default, upper thresholds of an OCP's RMS current have been configured.
  • Page 220 Chapter 7: Using the Web Interface ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 777). Click Save.
  • Page 221 Chapter 7: Using the Web Interface Other operations: • You can go to another OCP's data/setup page by clicking the OCP selector on the top-left corner. • You can go to the associated Inlet's data page by clicking the Inlet link in the Details section.

  • Page 222: Peripherals

    Chapter 7: Using the Web Interface Peripherals If there are Raritan environmental sensor packages connected to the PX3, they are listed on the Peripherals page. See Connecting Raritan Environmental Sensor Packages (on page 48). An environmental sensor package comprises one or some of the following sensors/actuators: •...
  • Page 223 Chapter 7: Using the Web Interface • Go to an individual sensor's or actuator's data/setup page by clicking its name. If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 170). Sensor/actuator overview on this page: If any sensor enters an alarmed state, it is highlighted in yellow or red.
  • Page 224 Chapter 7: Using the Web Interface Column Description Position The data indicates where this sensor or actuator is located in the sensor chain. Identifying the Sensor Position and Channel page 213). Actuator Indicates whether this sensor package is an actuator or not.
  • Page 225 Chapter 7: Using the Web Interface ▪ The management action triggers a "Manage Peripheral Device" dialog. Simply click Manage if you are managing multiple sensors/actuators. ▪ If you are managing only one sensor/actuator, you can choose to assign an ID number by selecting "Manually select a sensor number." Managing One Sensor or Actuator (on page 215).
  • Page 226 Chapter 7: Using the Web Interface Field Function Note ▪ The device's altitude is associated Altitude Specifies the altitude of PX3 above sea with the altitude correction factor. level when a Raritan's differential air Altitude Correction Factors pressure sensor is attached. page 787).
  • Page 227 Chapter 7: Using the Web Interface Click the desired sensor type (required), and then click Edit Thresholds. Make changes as needed. ▪ To enable any threshold, select the corresponding checkbox. ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 777).

  • Page 228: Yellow- Or Red-Highlighted Sensors

    Chapter 7: Using the Web Interface : Turn ON. : Turn OFF. Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered dry contact" actuator can be turned on at the same time.
  • Page 229 Chapter 7: Using the Web Interface Sensor status Color States shown in Description the interface unmanaged Sensors are not being managed. See Managed vs Unmanaged Sensors/Actuators (on page 210). ▪ Numeric or state sensors are within the normal range. Normal normal -- OR -- ▪...

  • Page 230: Managed Vs Unmanaged Sensors/Actuators

    Chapter 7: Using the Web Interface Managed vs Unmanaged Sensors/Actuators To manually manage or unmanage/release a sensor or actuator, see Peripherals (on page 202). Managed sensors/actuators: • PX3 communicates with managed sensors/actuators and retrieves their data. • Managed sensors/actuators are always listed on the Peripheral Devices page no matter they are physically connected or not.

  • Page 231: Sensor/Actuator States

    Chapter 7: Using the Web Interface Sensor/Actuator States An environmental sensor or actuator shows its real-time state after being managed. Available sensor states depend on the sensor type -- numeric or state sensors. For example, a contact closure sensor is a state sensor so it switches between three states only -- unavailable, alarmed and normal.

  • Page 232: Finding The Sensor's Serial Number

    Chapter 7: Using the Web Interface Note that for a contact closure sensor, the normal state depends on the normal setting you have configured. Refer to the Environmental Sensors and Actuators Guide (or Online Help) for detailed information, which is available on Raritan's Support page (http://www.raritan.com/support/).

  • Page 233: Identifying The Sensor Position And Channel

    Chapter 7: Using the Web Interface A DX2 DX, DPX2 or DPX3 sensor package 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 PX3. Match the serial number from the tag to those listed in the sensor table.
  • Page 234 Chapter 7: Using the Web Interface • If a Raritan DPX3-ENVHUB4 sensor hub is involved, the hub port information is also indicated for DX2, DX, DPX2 and DPX3 series, but NOT indicated for DPX series. For example, Hub Port 3. •...

  • Page 235: How The Automatic Management Function Works

    Chapter 7: Using the Web Interface How the Automatic Management Function Works This setting is configured on Peripherals (on page 202). After enabling the automatic management function: When the total number of managed sensors and actuators has not reached the upper limit yet, PX3 automatically brings newly-connected environmental sensors and actuators under management after detecting them.
  • Page 236 Chapter 7: Using the Web Interface The Manage Peripheral Device dialog appears. ▪ To let PX3 randomly assign an ID number to it, select "Automatically assign a sensor number." This method does not release any managed sensor or actuator. ▪ To assign a desired ID number, select "Manually select a sensor number."...

  • Page 237: Individual Sensor/Actuator Pages

    Chapter 7: Using the Web Interface However, only relative humidity sensors are "automatically" managed if the automatic management function is enabled. You must "manually" manage absolute humidity sensors as needed. Note that relative and absolute values of the same humidity sensor do NOT share the same ID number though they share the same serial number and position.
  • Page 238 Chapter 7: Using the Web Interface Select or deselect 'Use default thresholds' according to your needs. ▪ To have this sensor follow the default threshold settings configured for its own sensor type, select the 'Use default thresholds' checkbox. The default threshold settings are configured on the page of Peripherals (on page 202).
  • Page 239 Chapter 7: Using the Web Interface To set up a sensor's or actuator's physical location and additional settings: Click Edit Settings. Make changes to available fields, and then click Save. Fields Description Name A name for the sensor or actuator. Description Any descriptive text you want.
  • Page 240 Chapter 7: Using the Web Interface Fields Description Sensor Polarity This field is available for DX2-CC2 contact closure sensors only. Determine the normal state of your DX2-CC2. ▪ Normal Open: The open status of the connected detector/switch is considered normal. An alarm is triggered when the detector/switch turns closed. ▪...
  • Page 241 Chapter 7: Using the Web Interface ▪ To retrieve the exact data at a particular time, hover your mouse over the data line in the chart. Both the time and data are displayed as illustrated below. To turn on or off an actuator: Click the desired control button.

  • Page 242: Z Coordinate Format

    Chapter 7: Using the Web Interface Note: Per default you can turn on as many dry contact actuators as you want, but only one "powered dry contact" actuator can be turned on at the same time. To change this limitation of "powered dry contact" actuators, modify the active powered dry contact setting.

  • Page 243: Feature Port

    Chapter 7: Using the Web Interface Format Description Free-form Any alphanumeric string can be used for specifying the Z coordinate. The value comprises 0 to 24 characters. Configure Z coordinates on the Individual Sensor/Actuator Pages (on page 217). Sensor/Actuator Location Example Use the X, Y and Z coordinates to describe each sensor's or actuator's physical location in the data center.
  • Page 244 Chapter 7: Using the Web Interface Device Description Power CIM This type represents one of the following Raritan products: ▪ Raritan power CIM, D2CIM-PWR. This CIM is used to connect the PX3 to the Raritan digital KVM switch -- Dominion KX II / III. ▪...

  • Page 245: Asset Strip

    Chapter 7: Using the Web Interface Mode Description Asset Strip, Force the PX3 to show the selected device's data/setup page regardless of the physical Raritan asset strips, connection status. LHX 20, SHX 30, LHX 40, Power CIM Note: 'LHX 20', 'SHX 30', and 'LHX 40' are not available when the support of LHX/SHX heat exchangers is disabled.
  • Page 246 Chapter 7: Using the Web Interface Field Description Name Name for this asset strip assembly. Number of rack Total of available tag ports on this asset strip units assembly, ranging between 8 and 64. ▪ For the current generation of asset strips, which show the suffix "G3"...
  • Page 247 Chapter 7: Using the Web Interface ▪ Type the hexadecimal RGB value of the color, such as #00FF00. Click Ok. The rack unit numbering and LED color settings are immediately updated on the Rack Units list illustrated below. ▪ The 'Index' number is the physical tag port number printed on the asset strip, which is not configurable.
  • Page 248 Chapter 7: Using the Web Interface To customize a single rack unit's settings: You can make a specific rack unit's LED behave differently from the others on the asset strip, including the LED light and color. Click the desired rack unit on the Rack Units list. The setup dialog for the selected one appears.
  • Page 249 Chapter 7: Using the Web Interface Field Description LED Mode This field is configurable only after the Operation Mode is set to Manual Override. Determine how the LED light behaves for this particular rack unit. ▪ On: The LED stays lit. ▪...
  • Page 250 Chapter 7: Using the Web Interface All tag ports of the blade extension strip are listed below it. Their port numbers are displayed in the Slot column. ▪ To hide the blade extension slots list, click...
  • Page 251 Chapter 7: Using the Web Interface To customize asset IDs on programmable asset tags: You can customize asset IDs only when the asset tags are "programmable" ones. Non-programmable tags do not support this feature. In addition, you can also customize the ID of a blade extension strip. If a barcode reader is intended, connect it to the computer you use to access the PX3.
  • Page 252 Chapter 7: Using the Web Interface ▪ An asset ID contains up to 12 characters that comprise only numbers and/or UPPER CASE alphabets. Lower case alphabets are NOT accepted. Verify the correctness of customized asset IDs and modify as needed. Click Apply at the bottom of the page to save changes.

  • Page 253: External Beeper

    Chapter 7: Using the Web Interface Asset Strip Automatic Firmware Upgrade After connecting the asset strip to the PX3, it automatically checks its own firmware version against the version of the asset strip firmware stored in the PX3 firmware. If two versions are different, the asset strip automatically starts downloading the new firmware from the PX3 to upgrade its own firmware.

  • Page 254: Schroff Lhx/Shx

    Chapter 7: Using the Web Interface Schroff LHX/SHX You must enable the LHX/SHX support for the PX3 to detect the presence of a supported Schroff LHX/SHX heat exchanger. See Miscellaneous (on page 394). ® After enabling the LHX/SHX support and connecting a supported Schroff ®...
  • Page 255 Chapter 7: Using the Web Interface For the functionality of this icon on the top-right corner, see Feature Port (on page 223). To view the LHX/SHX device state: The Operation State field indicates whether the device is operating fine, and the Switch State field indicates its power status.
  • Page 256 Chapter 7: Using the Web Interface To configure LHX/SHX settings: Click Edit Settings. Configure the settings as needed. ▪ Provide a customized name. ▪ Specify the desired air outlet setpoint temperature. ▪ Specify the default fan speed. Click Save. To view all sensor data and configure thresholds: Locate the Sensors section, which lists all air outlet/inlet temperatures and fan speeds, and indicates the door closed/open status of the LHX/SHX device.
  • Page 257 Chapter 7: Using the Web Interface b. Click Edit Thresholds. Enable and set the desired thresholds and deassertion hysteresis. Note that assertion timeout is NOT available on LHX/SHX. d. Click Save. After thresholds are enabled, sensors may be highlighted in yellow or red if they enter the warning or critical range.
  • Page 258 Chapter 7: Using the Web Interface If any LHX sensors fail, they are indicated. Click Acknowledge to acknowledge the sensor failure. To view the history of LHX events, click Show Event Log to go to the Event Log page. Operation time statistics: This section indicates the accumulative operation hours of the LHX/SHX device and its fans since the device is connected to the PX3 and turned on.

  • Page 259: Power Cim

    Chapter 7: Using the Web Interface SHX Request Maximum Cooling The PX3 allows you to remotely activate the Schroff SHX 30's maximum cooling feature. Both LHX 20 and LHX 40 do not support remote activation of maximum cooling. The Request Maximum Cooling feature is available only after the PX3 detects SHX 30.

  • Page 260: User Management

    Chapter 7: Using the Web Interface User Management User Management menu deals with user accounts, permissions, and preferred measurement units on a per-user basis. PX3 is shipped with one built-in administrator account: admin, which is ideal for initial login and system administration. You cannot delete 'admin' or change its permissions, but you can and should change its password.

  • Page 261: Creating Users

    Chapter 7: Using the Web Interface Creating Users All users must have a user account, containing the login name and password. Multiple users can log in simultaneously using the same login name. To add users, choose User Management > Users > User information: Field/setting Description...
  • Page 262 Chapter 7: Using the Web Interface Copy and paste all content in the text editor into the SSH Public Key field. SNMPv3: The SNMPv3 access permission is disabled by default. Field/setting Description Enable SNMPv3 Select this checkbox when intending to permit the SNMPv3 access by this user.
  • Page 263 Chapter 7: Using the Web Interface Field/setting Description Password, Type the privacy password if the 'Same as Authentication Password' checkbox is deselected. Confirm password The password must consist of 8 to 32 ASCII printable characters. • Protocol: This section is configurable only when 'Authentication' or 'Authentication &...

  • Page 264: Editing Or Deleting Users

    Chapter 7: Using the Web Interface Note: Users can change the measurement units at any time by setting their own preferences. See Setting Your Preferred Measurement Units (on page 249). Roles: Select one or multiple roles to determine the user's permissions. To select all roles, select the topmost checkbox in the header row.
  • Page 265 Chapter 7: Using the Web Interface In the Enabled column: • : The user is enabled. • : The user is disabled. If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 170). To edit or delete a user account: On the Users page, click the desired user.

  • Page 266: Creating Roles

    Chapter 7: Using the Web Interface Click Click Delete on the confirmation message. Creating Roles A role is a combination of permissions. Each user must have at least one role. The PX3 provides two built-in roles. Built-in role Description Admin Provide full permissions.
  • Page 267 Chapter 7: Using the Web Interface Assign a role name. ▪ 1 to 32 characters long ▪ Case sensitive ▪ Spaces are permitted Type a description for the role in the Description field. Select the desired privilege(s). ▪ The 'Administrator Privileges' includes all privileges. ▪...

  • Page 268: Editing Or Deleting Roles

    Chapter 7: Using the Web Interface Editing or Deleting Roles Choose User Management > Roles to open the Roles page, which lists all roles. If wanted, you can resort the list by clicking the desired column header. See Sorting a List (on page 170).

  • Page 269: Setting Your Preferred Measurement Units

    Chapter 7: Using the Web Interface ▪ To select all roles, except for the Admin role, select the topmost checkbox in the header row. Click on the top-right corner. Click Delete on the confirmation message. Setting Your Preferred Measurement Units You can change the measurement units shown in the PX3 user interface according to your own preferences regardless of the permissions you have.

  • Page 270: Setting Default Measurement Units

    Chapter 7: Using the Web Interface Setting Default Measurement Units Default measurement units are applied to all PX3 user interfaces across all users, including users accessing the PX3 via external authentication servers. For a list of affected user interfaces, see User Interfaces Showing Default Units (on page 250).

  • Page 271: Device Settings

    Chapter 7: Using the Web Interface Device Settings Click 'Device Settings' in the Menu (on page 167), and the following submenu displays. Menu command Submenu command Refer to... Network Configuring Network Settings (on page 253) Network Services HTTP Changing HTTP(S) Settings (on page 279) SNMP Configuring SNMP Settings...
  • Page 272 Chapter 7: Using the Web Interface Menu command Submenu command Refer to... SMTP Server Configuring SMTP Settings (on page 283) Changing SSH Settings (on page 284) Telnet Changing Telnet Settings (on page 285) Modbus Changing Modbus Settings (on page 285) Server Advertising Enabling Service Advertising (on page 288)

  • Page 273: Configuring Network Settings

    Chapter 7: Using the Web Interface Configuring Network Settings Configure wired, wireless, and Internet protocol-related settings on the Network page after Connecting the PX3 to Your Network (on page 22). You can enable both the wired and wireless networking on PX3 so that it has multiple IP addresses -- wired and wireless IP.
  • Page 274 Chapter 7: Using the Web Interface After enabling either or both Internet protocols: After enabling IPv4 and/or IPv6, all but not limited to the following protocols will be compliant with the selected Internet protocol(s): • LDAP • • SMTP • •...
  • Page 275 Chapter 7: Using the Web Interface • DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements: ▪ Consists of alphanumeric characters and/or hyphens ▪ Cannot begin or end with a hyphen ▪ Cannot contain more than 63 characters ▪...
  • Page 276 Chapter 7: Using the Web Interface (Optional) To view the diagnostic log for EAP authentication: • Click Show EAP Authentication Log. See Diagnostic Log for Network Connections (on page 265). Common Network Settings Common Network Settings are OPTIONAL, not required. Therefore, leave them unchanged if there are no specific local networking requirements.
  • Page 277 Chapter 7: Using the Web Interface Field Description First/Second/Third Manually specify static DNS server(s). DNS server ▪ If any static DNS server is specified in these fields, it will override the DHCP-assigned DNS server. ▪ If DHCP (or Automatic) is selected for IPv4/IPv6 settings, and there are NO static DNS servers specified, the PX3 will use DHCP-assigned DNS servers.
  • Page 278 Chapter 7: Using the Web Interface Field Description simultaneously. • Half: Data is transmitted in one direction (to or from the PX3) at a time. Show the LAN's current status, including the current Current state speed and duplex mode. Authentication Select an authentication method.
  • Page 279 Chapter 7: Using the Web Interface Field Description Client certificate, This field appears when 'EAP', 'PEAP' and 'TLS' are Client private key, all selected. Client private key password PEM encoded X.509 certificate and PEM encoded private key are required for certification-based authentication methods.
  • Page 280 Chapter 7: Using the Web Interface Field/setting Description Click this button to import a certificate file. Then you can: ▪ Click Show to view the certificate's content. ▪ Click Remove to delete the installed certificate if it is inappropriate. ▪ Select this checkbox to make the authentication Allow expired and succeed regardless of the certificate's validity not yet valid...
  • Page 281 Chapter 7: Using the Web Interface Field/setting Description USB LAN adapter is firmly connected or whether it is supported. SSID Type the name of the wireless access point (AP). Force AP BSSID If the BSSID is available, select this checkbox. BSSID Type the MAC address of an access point.
  • Page 282 Chapter 7: Using the Web Interface Field/setting Description Identity This field appears when 'EAP' is selected. Type your user name. Password This field appears only when 'EAP', 'PEAP' and 'MS-CHAPv2' are all selected. Type your password. Client certificate, This field appears when 'EAP', 'PEAP' and 'TLS' are Client private key, all selected.
  • Page 283 Chapter 7: Using the Web Interface • Available settings for the CA Certificate: If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see TLS Certificate Chain page 804). Field/setting Description Enable verification of...
  • Page 284 Chapter 7: Using the Web Interface • DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements: ▪ Consists of alphanumeric characters and/or hyphens ▪ Cannot begin or end with a hyphen ▪ Cannot contain more than 63 characters ▪...
  • Page 285 Chapter 7: Using the Web Interface Diagnostic Log for Network Connections PX3 provides a diagnostic log for inspecting connection errors that occurred during the EAP authentication or the wireless network connection. The information is useful for technical support. Note that the diagnostic log shows data only after connection errors are detected.
  • Page 286 Chapter 7: Using the Web Interface Static Route Examples This section describes two static route examples: IPv4 and IPv6. Both examples assume that two network interface controllers (NIC) have been installed in one network server, leading to two available subnets, and IP forwarding has been enabled.
  • Page 287 Chapter 7: Using the Web Interface In this example, NIC-2 (192.168.100.88) is the next hop router for your PX3 to communicate with any device in the other subnet 192.168.200.0. In the IPv4 "Static Routes" section, you should enter the data as shown below. Note that the address in the first field must be of the Classless Inter-Domain Routing (CIDR) notation.
  • Page 288 Chapter 7: Using the Web Interface Tip: If you have configured multiple static routes, you can click on any route and then make changes, use to re-sort the priority, or click to delete it. IPv6 example: • Your PX3: fd07:2fa:6cff:2405::30 •...
  • Page 289 Chapter 7: Using the Web Interface In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your PX3 to communicate with any device in the other subnet fd07:2fa:6cff:1111::0. In the IPv6 "Static Routes" section, you should enter the data as shown below. Note that the address in the first field must be of the Classless Inter-Domain Routing (CIDR) notation.
  • Page 290 Chapter 7: Using the Web Interface Setting the Cascading Mode A maximum of 16 PX3 devices can be cascaded to share one Ethernet connection. See Cascading Multiple PX3 Devices for Sharing Ethernet Connectivity (on page 34). The cascading mode configured on the master device determines the Ethernet sharing method, which is either network bridging or port forwarding.
  • Page 291 Chapter 7: Using the Web Interface Field Description Master or Slave. Port forwarding role This is to determine which device is the (available on all cascaded master and which ones are slave devices. devices) USB or ETH1/ETH2. Downstream interface This is to determine which port on the (available on the maser master device is connected to Slave 1.
  • Page 292 Chapter 7: Using the Web Interface Online cascading information: For more information on cascading configurations and restrictions, refer to the Cascading Guide on the Raritan Support page (http://www.raritan.com/support/). Overview of the Cascading Modes You must apply a cascading mode to the cascading chain. See Setting the Cascading Mode (on page 270).
  • Page 293 Chapter 7: Using the Web Interface You must specify a 5XXXX port number (where X is a number) when remotely accessing any slave device with the shared IP address. See Port Number Syntax (on page 273). Comparison between cascading modes: •...
  • Page 294 Chapter 7: Using the Web Interface • XX is a two-digit number representing the device position as shown below. Position Position Master device Slave 8 Slave 1 Slave 9 Slave 2 Slave 10 Slave 3 Slave 11 Slave 4 Slave 12 Slave 5 Slave 13 Slave 6...
  • Page 295 Chapter 7: Using the Web Interface Port Forwarding Examples To access a cascaded device in the Port Forwarding mode, assign a port number to the IP address. • Master device: Assign proper 5NNXX port numbers or standard TCP/UDP ports. See Port Number Syntax (on page 273) for details.
  • Page 296 Chapter 7: Using the Web Interface Slave 1 device: Position code for Slave 1 is '01' so each port number is 5NN01 as shown below. Protocols Port numbers HTTPS 50001 HTTP 50101 50201 TELNET 50301 SNMP 50501 MODBUS 50601 Examples: •...
  • Page 297 Chapter 7: Using the Web Interface Adding, Removing or Swapping Cascaded Devices Change a device's cascading mode first before adding that device to a cascading chain, or before disconnecting that device from the chain. If you only want to change the cascading mode of an existing chain, or swap the master and slave device, always start from the slave device.

  • Page 298: Configuring Network Services

    Chapter 7: Using the Web Interface ▪ You must disconnect the LAN cable and ALL cascading cables connected to the two devices first before swapping them, and then reconnecting all cables. To change the cascading mode applied to a chain: Access the last slave device, and change its cascading mode.
  • Page 299 Chapter 7: Using the Web Interface HTTPS and HTTP enable the access to the web interface. Telnet and SSH enable the access to the command line interface. See Using the Command Line Interface (on page 456). By default, SSH is enabled, Telnet is disabled, and all TCP ports for supported services are set to standard ports.
  • Page 300 Chapter 7: Using the Web Interface Special note for AES ciphers: The PX3 device's TLS-based protocols support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between PX3 and the client (such as a web browser), which is impacted by the cipher priority of PX3 and the client's cipher availability/settings.
  • Page 301 Chapter 7: Using the Web Interface Configuring SNMP Settings You can enable or disable SNMP communication between an SNMP manager and the PX3. Enabling SNMP communication allows the manager to retrieve and even 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 302 Chapter 7: Using the Web Interface Enable or disable "SNMP v1 / v2c" and/or "SNMP v3" by clicking the corresponding checkbox. ▪ The SNMP v1/v2c read-only access is enabled by default. The default 'Read community string' is "public." ▪ To enable read-write access, type the 'Write community string.' Usually the string is "private."...
  • Page 303 Chapter 7: Using the Web Interface Configuring SMTP Settings The PX3 can be configured to send alerts or event messages to a specific administrator by email. See Event Rules and Actions (on page 316). To send emails, you have to configure the SMTP settings and enter an IP address for your SMTP server and a sender's email address.
  • Page 304 Chapter 7: Using the Web Interface Field/setting Description Click this button to import a certificate file. Then you can: ▪ Click Show to view the certificate's content. ▪ Click Remove to delete the installed certificate if it is inappropriate. ▪ Select this checkbox to make the authentication Allow expired and succeed regardless of the certificate's validity not yet valid...
  • Page 305 Chapter 7: Using the Web Interface ▪ Public key authentication only: Enables the public key-based login only. ▪ Password and public key authentication: Enables both the password- and public key-based login. This is the default. Click Save. If the public key authentication is selected, you must enter a valid SSH public key for each user profile to log in over the SSH connection.
  • Page 306 Chapter 7: Using the Web Interface Modbus Gateway: If connecting the Modbus RTU devices to PX3 and enabling the Modbus Gateway feature, the Modbus TCP clients on your network will be able to communicate with those Modbus RTU devices attached to PX3. See Connecting a Modbus RTU Device or Bus (on page 81).
  • Page 307 Chapter 7: Using the Web Interface Field Description Use the default port 503, or assign a different port. Valid range is TCP port 1 to 65535. Note: Port 502 is the default Modbus/TCP port for PX3, so you cannot use that port for the Modbus Gateway. Use the default values, or update if the Modbus RTU devices are Parity, using different communication parameters.
  • Page 308 Chapter 7: Using the Web Interface Enabling Service Advertising The PX3 advertises all enabled services that are reachable using the IP network. This feature uses DNS-SD (Domain Name System-Service Discovery) and MDNS (Multicast DNS). The advertised services are discovered by clients that have implemented DNS-SD and MDNS.

  • Page 309: Configuring Security Settings

    Chapter 7: Using the Web Interface Configuring Security Settings The PX3 provides tools to control access. You can enable the internal firewall, create firewall rules, and set login limitations. In addition, you can create and install the certificate or set up external authentication servers for access control.
  • Page 310 Chapter 7: Using the Web Interface Creating IP Access Control Rules IP access control rules (firewall rules) determine whether to accept or discard traffic to/from the PX3, based on the IP address of the host sending or receiving the traffic. When creating rules, keep these principles in mind: •...
  • Page 311 Chapter 7: Using the Web Interface ADD a rule to the end of the list ▪ Click Append. ▪ Type an IP address and subnet mask in the IP/Mask field. ▪ Select an option in the Policy field. ▪ Accept: Accepts traffic from/to the specified IP address(es). ▪...
  • Page 312 Chapter 7: Using the Web Interface ▪ You can select any existing rule and then click change its priority. Click Save. The rules are applied.
  • Page 313 Chapter 7: Using the Web Interface To configure IPv6 access control rules: On the same page, select the 'Enable IPv6 access control' checkbox to enable IPv6 access control rules. Follow the same procedure as the above IPv4 rule setup to create IPv6 rules.
  • Page 314 Chapter 7: Using the Web Interface Creating Role Based Access Control Rules Role-based access control rules are similar to IP access control rules, except that they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their IP addresses. Same as IP access control rules, the order of role-based access control rules is important, since the rules are executed in numerical order.
  • Page 315 Chapter 7: Using the Web Interface ▪ You can select any existing rule and then click change its priority. Click Save. The rules are applied. To configure IPv6 access control rules: On the same page, select the 'Enable role based access control for IPv6' checkbox to enable IPv6 access control rules.
  • Page 316 Chapter 7: Using the Web Interface ▪ Make changes to the selected rule, and then click Save. For information on each field, see Creating Role Based Access Control Rules (on page 294). ▪ Click to remove it. ▪ To resort its order, click Click Save.
  • Page 317 Chapter 7: Using the Web Interface Creating a CSR Follow this procedure to create the CSR for your PX3. Note that you must enter information in the fields showing the message 'required.' To create a CSR: Choose Device Settings > Security > TLS Certificate. Provide the information requested.
  • Page 318 Chapter 7: Using the Web Interface Field Do this Key length Select an available key length (bits). A larger key length enhances the security, but slows down the response of PX3. ▪ Only 2048 is available now. Self-sign For requesting a certificate signed by the CA, ensure this checkbox is NOT selected.
  • Page 319 Chapter 7: Using the Web Interface To verify whether the certificate has been installed successfully, check the data shown in the Active TLS Certificate section. Creating a Self-Signed Certificate When appropriate certificate and key files for PX3 are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate.
  • Page 320 Chapter 7: Using the Web Interface Double check the data shown in the New TLS Certificate section. b. If correct, click "Install Key and Certificate" to install the self-signed certificate and private key. Tip: To verify whether the certificate has been installed successfully, check the data shown in the Active TLS Certificate section.
  • Page 321 Chapter 7: Using the Web Interface Click Upload. The selected files are installed. To verify whether the certificate has been installed successfully, check the data shown in the Active TLS Certificate section. Setting Up External Authentication Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0.
  • Page 322 Chapter 7: Using the Web Interface Special note about the AES cipher: The PX3 device's TLS-based protocols support AES 128- and 256-bit ciphers. The exact cipher to use is negotiated between PX3 and the client (such as a web browser), which is impacted by the cipher priority of PX3 and the client's cipher availability/settings.
  • Page 323 Chapter 7: Using the Web Interface Adding LDAP/LDAPS Servers To use LDAP authentication, enable it and enter the information you have gathered. Note that you must enter information in the fields showing the message 'required.' To add LDAP/LDAPS servers: Choose Device Settings > Security > Authentication. Click New in the LDAP Servers section.
  • Page 324 Chapter 7: Using the Web Interface Field/setting Description Enable verification of Select this checkbox if it is required to validate the LDAP server's certificate LDAP server certificate by the PX3 prior to the connection. If the certificate validation fails, the connection is refused. CA certificate Consult your AA server administrator to get the CA certificate file for the LDAPS server.
  • Page 325 Chapter 7: Using the Web Interface Field/setting Description User entry object class The object class for user entries. ▪ Usually it is inetOrgPerson. User search subfilter Search criteria for finding LDAP user objects within the directory tree. Active Directory The name of the Active Directory Domain. domain ▪...
  • Page 326 Chapter 7: Using the Web Interface Note: If the PX3 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 PX3 and the LDAP server to use the same NTP server(s).
  • Page 327 Chapter 7: Using the Web Interface To verify if the authentication configuration is set correctly, click Test Connection to check whether the PX3 can connect to the new server successfully. Tip: You can also test the connection on the Authentication page after finishing adding servers.
  • Page 328 Chapter 7: Using the Web Interface Note: Whenever PX3 is successfully connected to one external authentication server, it STOPS trying access to remaining servers in the authentication list regardless of the user authentication result. To enable both external and local authentication: In the 'Authentication type' field, select the external authentication you want -- LDAP or RADIUS.
  • Page 329 Chapter 7: Using the Web Interface Tip: If any user blocking event occurs, you can unblock that user manually by using the "unblock" CLI command over a local connection. See Unblocking a User (on page 618). To set limitations for login timeout and use of identical login names: In the "Idle timeout period"...
  • Page 330 Chapter 7: Using the Web Interface Minimum length = 8 characters Maximum length = 32 characters At least one lowercase character = Required At least one uppercase character = Required At least one numeric character = Required At least one special character = Required Number of forbidden previous passwords Note: The maximum password length accepted by PX3 is 64 characters.
  • Page 331 Chapter 7: Using the Web Interface Login manner after enabling the service agreement: After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen. Do either of the following, or the login fails: • In the web interface, select the checkbox labeled "I understand and accept the restricted service agreement."...

  • Page 332: Setting The Date And Time

    Chapter 7: Using the Web Interface Setting the Date and Time Set the internal clock on the PX3 manually, or link to a Network Time Protocol (NTP) server. Note: If you are using Sunbird's Power IQ to manage the PX3, you must configure Power IQ and the PX3 to have the same date/time or NTP settings.
  • Page 333 Chapter 7: Using the Web Interface Use the NTP server ▪ Select "Synchronize with NTP server." ▪ There are two ways to assign the NTP servers: ▪ To use the DHCP-assigned NTP servers, DO NOT enter any NTP servers for the First and Second time server.
  • Page 334 Chapter 7: Using the Web Interface Calendar The calendar icon in the Date field is a convenient tool to select a custom date. Click it and a calendar similar to the following appears. Number Item Description arrows Switch between months. dates All dates of the selected month.
  • Page 335 Chapter 7: Using the Web Interface Windows NTP Server Synchronization Solution The NTP client on the PX3 follows the NTP RFC so the PX3 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 PX3.

  • Page 336: Event Rules And Actions

    Chapter 7: Using the Web Interface Event Rules and Actions A benefit of the product's intelligence is its ability to notify you of or react to a change in conditions. This event notification or reaction is an "event rule." An event rule consists of two parts: •...
  • Page 337 Chapter 7: Using the Web Interface Assign a name to this scheduled action. b. Make sure the Enabled checkbox is selected, or the PX3 does not perform this scheduled action. Set the interval time, which ranges from every minute to yearly. d.
  • Page 338 Chapter 7: Using the Web Interface ▪ <Any Numeric Sensor> means all numeric sensors of the PX3, including internal and environmental sensors. <Any Numeric Sensor> is especially useful if you want to receive the notifications when any numeric sensor's readings pass through a specific threshold. In this example, the Peripheral Device Slot is selected, which is related to the environmental sensor packages.
  • Page 339 Chapter 7: Using the Web Interface In this example, Numeric Sensor is selected because we want to select numeric-sensor-related event(s). Then a field for numeric-sensor-related events appears. Click this field to select one of the numeric-sensor-related events from the list. In this example, 'Above upper critical threshold' is selected because we want the PX3 to react only when the selected temperature sensor's reading enters the upper critical range.
  • Page 340 Chapter 7: Using the Web Interface To remove any action(s) from the 'Selected actions' field, click that action's ▪ To remove all actions, click Deselect All. Radio buttons for different events: According to the event you select, the "Trigger condition" field containing three radio buttons may or may not appear.
  • Page 341 Chapter 7: Using the Web Interface Event types Radio buttons ▪ Link state is up: PX3 takes the action only when Network interface link the network link state changes from down to up. state ▪ Link state is down: PX3 takes the action only when the network link state changes from up to down.
  • Page 342 Chapter 7: Using the Web Interface Event types Radio buttons ▪ Connected: PX3 takes the action only when the Device connection or selected device is physically connected to it. disconnection, such as ▪ Disconnected: PX3 takes the action only when a USB-cascaded slave device the selected device is physically disconnected...
  • Page 343 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Asset Management > Firmware Firmware update for asset strip Update [AMSNUMBER] ('[AMSNAME]'): status changed to '[AMSSTATE]'. Asset Management > Device Config parameter '[CONFIGPARAM]' of Config Changed asset strip [AMSNUMBER] ('[AMSNAME]')
  • Page 344 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Device > Firmware update Firmware upgraded successfully from completed version '[OLDVERSION]' to version '[VERSION]' by user '[USERNAME]' from host '[USERIP]'. Device >...
  • Page 345 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Device > Sending Syslog message Sending Syslog message to server failed [SYSLOGSERVER]:[SYSLOGPORT] ([SYSLOGTRANSPORTPROTO]) failed. [ERRORDESC]. Device > Sending SMS message Sending SMS message to failed '[PHONENUMBER]' failed.
  • Page 346 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Peripheral Device Slot > * > Peripheral device '[EXTSENSORNAME]' in Peripheral device '[EXTSENSORNAME]' Numeric Sensor > Below lower slot [EXTSENSORSLOT] asserted 'below in slot [EXTSENSORSLOT] deasserted warning threshold lower warning' at [SENSORREADING]...
  • Page 347 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE [SENSORREADINGUNIT]. [SENSORREADINGUNIT]. Sensor '[INLETSENSOR]' on inlet '[INLET]' Inlet > * > Sensor > * > Reset has been reset by user '[USERNAME]' from host '[USERIP]'.
  • Page 348 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Inlet > Pole > * > Sensor > Below Sensor '[PDUPOLESENSOR]' on pole Sensor '[PDUPOLESENSOR]' on pole lower critical threshold '[INLETPOLE]' of inlet '[INLET]' asserted '[INLETPOLE]' of inlet '[INLET]' 'below lower critical' at [SENSORREADING]...
  • Page 349 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Outlet > * > Sensor > * > Below Sensor '[OUTLETSENSOR]' on outlet Sensor '[OUTLETSENSOR]' on outlet lower warning threshold '[OUTLET]' asserted 'below lower warning' '[OUTLET]' deasserted 'below lower at [SENSORREADING]...
  • Page 350 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Overcurrent Protector > * > Sensor '[OCPSENSOR]' on overcurrent Sensor '[OCPSENSOR]' on overcurrent Sensor > * > Above upper critical protector '[OCP]' asserted 'above upper protector '[OCP]' deasserted 'above threshold...
  • Page 351 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE Server Monitoring > Power control operation for [MONITOREDHOST] > Power '[MONITOREDHOST]' finished with result: control completed [SERVERPOWERRESULT] Server Monitoring > User '[USERNAME]' initiated a power [MONITOREDHOST] >...
  • Page 352 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE modified '[USERNAME]' from host '[USERIP]'. User Administration > Role Role '[UMTARGETROLE]' deleted by user deleted '[USERNAME]' from host '[USERIP]'. Webcam Management >...
  • Page 353 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE LHX/SHX > Sensor > Below lower Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX at critical threshold [PORTTYPE] port '[PORTID]' asserted [PORTTYPE] port '[PORTID]' deasserted 'below lower critical' at [SENSORREADING] 'below lower critical' at...
  • Page 354 Chapter 7: Using the Web Interface Event/context Default message when the event = TRUE Default message when the event = FALSE LHX/SHX > Threshold Air Inlet The air inlet temperature threshold on The air inlet temperature on LHX at LHX at [PORTTYPE] port '[PORTID]' was [PORTTYPE] port '[PORTID]' is within crossed.
  • Page 355 Chapter 7: Using the Web Interface 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 356 Chapter 7: Using the Web Interface Action Function Internal beeper Turns on or off the internal beeper. See Internal Beeper (on page 339). Log event message Records the selected events in the internal log. See Log an Event Message (on page 340). Power control server PX3-1000 does NOT support this feature.
  • Page 357 Chapter 7: Using the Web Interface Action Function Switch LHX/SHX Switches on or off the LHX/SHX device. See Switch LHX/SHX (on page 352). This option is available only when the Schroff LHX/SHX support has been enabled. Switch outlet group PX3-1000 does NOT support this feature. Switch peripheral Switches on or off the mechanism or system actuator...
  • Page 358 Chapter 7: Using the Web Interface To add all available methods, simply click Select All. b. To delete any methods, click a method's in the Selected field. To remove all methods, simply click Deselect All. To enable the notification-resending feature, select the 'Enable re-scheduling of alarm notifications' checkbox.
  • Page 359 Chapter 7: Using the Web Interface External Beeper This section applies to PX3 only. If an external beeper is connected to the PX3, the PX3 can change the beeper's behavior or status to respond to a certain event. To control the connected external beeper: Choose Device Settings >...
  • Page 360 Chapter 7: Using the Web Interface Log an Event Message The option 'Log event message' records the selected events in the internal log. The default log message generated for each type of event is available in the section titled Default Log Messages (on page 322).
  • Page 361 Chapter 7: Using the Web Interface If 'Start recording' is selected, adjust the values of the following: ▪ Number of snapshots - the number of snapshots to be taken when the event occurs. The maximum amount of snapshots that can be stored on the PX3 is 10. If you set it for a number greater than 10 and the storage location is on the PX3, after the 10th snapshot is taken and stored, the oldest snapshots are overwritten.
  • Page 362 Chapter 7: Using the Web Interface Folder name options Definition Serial number / Webcam name / Three folders will be created. Formatted timestamp ▪ Definitions of the parent folder and first subfolder are the same as the first row. ▪ The final subfolder's name is the time when the recording event occurs, which is a format comprising year, month, date, hour, minute, second and timezone.
  • Page 363 Chapter 7: Using the Web Interface In the Available LHX/SHX field, select the desired SHX-30 device one by one, or click Select All. To remove any SHX-30 device from the Selected LHX/SHX field, click that device's or click Deselect All. Send Email You can configure emails to be sent when an event occurs and can customize the message.
  • Page 364 Chapter 7: Using the Web Interface When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 363).
  • Page 365 Chapter 7: Using the Web Interface Send Sensor Report You may set the PX3 so that it automatically reports the latest readings or states of one or multiple sensors by sending a message or email or simply recording the report in a log. These sensors can be either internal or environmental sensors listed below.
  • Page 366 Chapter 7: Using the Web Interface b. Click the second to select the specific sensor for the target from the list. Click to add the selected sensor to the Report Sensors list box. For example, to monitor the current reading of the Inlet 1, select Inlet 1 from the left field, and then select RMS Current from the right field.
  • Page 367 Chapter 7: Using the Web Interface Send SMS Message You can configure SMS messages to be sent when an event occurs and can customize the message. Only the 7-bit ASCII charset is supported for SMS messages. Messages consist of a combination of free text and PX3 placeholders. The placeholders represent information which is pulled from the PX3 and inserted into the message.
  • Page 368 Chapter 7: Using the Web Interface ▪ When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Just scroll down to select the desired placeholder. For details, see Placeholders for Custom Messages (on page 363).
  • Page 369 Chapter 7: Using the Web Interface Select the webcam that is capturing the images you want sent in the email. Adjust the values of the following: ▪ Number of snapshots - the number of snapshots to be taken when the event occurs.
  • Page 370 Chapter 7: Using the Web Interface Send an SNMP Notification This option sends an SNMP notification to one or multiple SNMP destinations. Operation: Choose Device Settings > Event Rules > Select 'Send SNMP notification' from the Action list. Select the type of SNMP notification. See either procedure below according to your selection.
  • Page 371 Chapter 7: Using the Web Interface b. In the 'Number of retries' field, specify the number of times you want to re-send the inform communication if it fails. For example, inform communications are re-sent up to 5 times when the initial communication fails.
  • Page 372 Chapter 7: Using the Web Interface In the Script field, select the script that you want it to be started or stopped when an event occurs. ▪ No script is available if you have not created or loaded it into the PX3. To apply different arguments than the default, do the following.
  • Page 373 Chapter 7: Using the Web Interface In the Operation field, select an operation for the selected actuator(s). ▪ Turn on: Turns on the selected actuator(s). ▪ Turn off: Turns off the selected actuator(s). To select the actuator(s) where this action will be applied, select them one by one from the 'Available actuators' list.
  • Page 374 Chapter 7: Using the Web Interface Transport Next steps protocols A TLS certificate is required. Do the following: Type an appropriate port number in the 'TCP port' field. Default is 6514. b. In the 'CA certificate' field, click to select a TLS certificate. After importing the certificate, you may: ▪...
  • Page 375 Chapter 7: Using the Web Interface To remove any action(s) from the 'Selected actions' field, click that action's ▪ To remove all actions, click Deselect All. Select the desired frequency in the 'Execution time' field, and then specify the time interval or a specific date and time in the field(s) that appear.
  • Page 376 Chapter 7: Using the Web Interface Execution time Frequency settings Click the Frequency field to select an option. Minutes The frequency ranges from every minute, every 5 minutes, every 10 minutes and so on until every 30 minutes. Type a value in the Minute field, which is set to either of the Hourly following: ▪...
  • Page 377 Chapter 7: Using the Web Interface Send Sensor Report Example To create a scheduled action for emailing a temperature sensor report hourly, it requires: • A 'Send email' action • A 'Send sensor report' action • A timer - that is, the scheduled action Steps: Click to create a 'Send email' action that sends an...
  • Page 378 Chapter 7: Using the Web Interface ▪ If wanted, you can customize the subject and content of this email in this action.
  • Page 379 Chapter 7: Using the Web Interface...
  • Page 380 Chapter 7: Using the Web Interface Click to create a 'Send sensor report' action that includes the 'Email a Sensor Report' action as its destination action. For details, see Send Sensor Report (on page 345). ▪ In this example, this action is named Send Temperature Sensor Readings.
  • Page 381 Chapter 7: Using the Web Interface ▪ You can specify more than one temperature sensor as needed in this action. Click to create a timer for performing the 'Send Temperature Sensor Readings' action hourly. For details, see Scheduling an Action (on page 354).
  • Page 382 Chapter 7: Using the Web Interface ▪ In this example, the timer is named Hourly Temperature Sensor Reports. ▪ To perform the specified action at 12:30 pm, 01:30 pm, 02:30 pm, and so on, select Hourly, and set the Minute to 30. Then the PX3 will send out an email containing the specified temperature sensor readings hourly every day.
  • Page 383 Chapter 7: Using the Web Interface Placeholders for Custom Messages Actions of "Send email" and "Send SMS message" allow you to customize event messages. See Send Email (on page 343) or Send SMS Message (on page 347). In addition, you can add custom text message to the "Send snapshots via email"...
  • Page 384 Chapter 7: Using the Web Interface Placeholder Definition [AMSNAME] The name of an asset strip [AMSNUMBER] The numeric ID of an asset strip [AMSRACKUNITPOSITION] The (vertical) rack unit position [AMSSTATE] The human-readable state of an asset strip [AMSTAGID] The asset tag ID [CARDREADERCHANNEL] The channel number of a card reader [CARDREADERID]...
  • Page 385 Chapter 7: Using the Web Interface Placeholder Definition [LDAPERRORDESC] The LDAP error occurred [LHXFANID] The ID of a fan connected to an LHX/SHX [LHXPOWERSUPPLYID] The ID of an LHX/SHX power supply [LHXSENSORID] The ID of an LHX/SHX sensor probe [LOGMESSAGE] The original log message [MONITOREDHOST] The name or IP address of a monitored host...
  • Page 386 Chapter 7: Using the Web Interface Placeholder Definition [PORTTYPE] The type of the external port (e.g. 'feature' or 'auxiliary') the event-triggering device is connected to [RADIUSERRORDESC] The Radius error message [ROMCODE] The romcode of an attached peripheral device [SENSORREADING] The value of a sensor reading [SENSORREADINGUNIT] The unit of a sensor reading [SENSORREPORT]...
  • Page 387 Chapter 7: Using the Web Interface Editing or Deleting a Rule/Action You can change the settings of an event rule, action or scheduled action, or delete them. Exception: Some settings of the built-in event rules or actions are not user-configurable. You cannot delete built-in rules and actions. See Built-in Rules and Rule Configuration (on page 317) or...
  • Page 388 Chapter 7: Using the Web Interface To make PX3 record the firmware update failure event in the internal log, select "System Event Log Action" in the 'Available actions' field. Sample Outlet-Level Event Rule In this example, we want the PX3 to send SNMP notifications to the SNMP manager for any sensor change event of outlet 3.
  • Page 389 Chapter 7: Using the Web Interface Note: The SNMP notifications may be SNMP v2c or SNMP v3 traps/informs, depending on the settings for the System SNMP Notification Action. See Enabling and Configuring SNMP (on page 447). Then the SNMP notifications are sent when: ▪...
  • Page 390 Chapter 7: Using the Web Interface Sample Inlet-Level Event Rule In this example, we want the PX3 to send SNMP notifications to the SNMP manager for any sensor change event of the Inlet I1. The event rule involves: • Event: Inlet > Sensor > Any sub-event •...
  • Page 391 Chapter 7: Using the Web Interface ▪ The active energy sensor is reset. For example, when the Inlet I1's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again. A Note about Infinite Loop You should avoid building an infinite loop when creating event rules.

  • Page 392: Setting Data Logging

    Chapter 7: Using the Web Interface A Note about Untriggered Rules In some cases, a measurement exceeds a threshold causing the PX3 to generate an alert. The measurement then returns to a value within the threshold, but the PX3 does not generate an alert message for the Deassertion event.

  • Page 393: Configuring Data Push Settings

    Chapter 7: Using the Web Interface ▪ If any section's number of sensors exceeds 35, the remaining sensors are listed on next page(s). If so, a pagination bar similar to the following diagram displays in this section, which you can click any button to switch between pages.
  • Page 394 Chapter 7: Using the Web Interface If the destination server requires authentication, select the 'Use authentication' checkbox, and enter the following data. ▪ User name comprising up to 64 characters ▪ Password comprising up to 128 characters In the 'Entry type' field, determine the data that will be transmitted. ▪...
  • Page 395 Chapter 7: Using the Web Interface Data Push Format Each push message contains exactly one JSON object. The data format is formally defined in IDL files, sharing several definitions from the JSON-RPC data model. IDL files are available by launching JSON-RPC online help (https://help.raritan.com/json-rpc/pdu/v3.6.0/namespacedatapush.html).
  • Page 396 Chapter 7: Using the Web Interface Sensor Descriptors for Inlet Active Power The following illustrates a descriptor for an inlet active power sensor. The metadata field is relevant only to numeric sensors so the readingtype field is displayed twice in the illustration. Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.
  • Page 397 Chapter 7: Using the Web Interface Log Rows The following illustrates log rows with only one sensor record shown. The actual length and order of log rows will be the same as those of sensors descriptors. Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.
  • Page 398 Chapter 7: Using the Web Interface Asset Management Tag List The root object of the asset management tag list message is an AssetStripsMessage structure. It contains current data about all connected asset management strips and tags, which is similar to the illustration below.
  • Page 399 Chapter 7: Using the Web Interface...
  • Page 400 Chapter 7: Using the Web Interface (Continued)
  • Page 401 Chapter 7: Using the Web Interface Asset Management Tag Log The root object of the asset management log message is an AssetLogPushMessage structure. It contains a list of tag or strip events since the last successful push. Note that a Raritan-provided explanation, which is the comment beginning with // in each line, is added to the following illustration for you to understand it better.

  • Page 402: Monitoring Server Accessibility

    Chapter 7: Using the Web Interface Monitoring Server Accessibility You can monitor whether specific IT devices are alive by having the PX3 continuously ping them. An IT device's successful response to the ping commands indicates that the IT device is still alive and can be remotely accessed.
  • Page 403 Chapter 7: Using the Web Interface Field Description Number of consecutive The number of consecutive pings without any unsuccessful pings for response before the monitored equipment is failure declared "Unreachable." Valid range is 1 to 100. Wait time before The wait time before the PX3 resumes pinging resuming pinging after after the monitored equipment is declared failure...
  • Page 404 Chapter 7: Using the Web Interface Status Description Reachable The monitored equipment is accessible. Unreachable The monitored equipment is inaccessible. Waiting for reliable The connection between the PX3 device and the connection monitored equipment is not reliably established yet. Editing or Deleting Ping Monitoring Settings You can edit the ping monitoring settings of any IT device or simply delete it if no longer needed.
  • Page 405 Chapter 7: Using the Web Interface ▪ To make the PX3 declare the accessibility of the monitored PDU every 15 seconds (3 pings * 5 seconds) when that PDU is accessible, enter the following data. Field Data entered Number of successful pings to enable feature Wait time after successful ping ▪...

  • Page 406: Front Panel Settings

    Chapter 7: Using the Web Interface This will make the PX3 react only when the target PDU becomes inaccessible. Select the System SNMP Notification Action. Note: If you have not configured the System SNMP Notification Action to specify the SNMP destination(s), see Editing or Deleting a Rule/Action (on page 367).

  • Page 407: Configuring The Serial Port

    Chapter 7: Using the Web Interface ▪ By default the front panel RCM self-test function, if available, is enabled. See Disabling or Enabling Front Panel RCM Self-Test page 694). Click Save. If the 'Mute beeper' feature is enabled, you can operate the front panel to mute it whenever it beeps.
  • Page 408 Chapter 7: Using the Web Interface Options Description Force console The PX3 attempts to recognize that the connected device is set for the console mode. Force analog modem The PX3 attempts to recognize that the connected device is an analog modem. Force GSM modem The PX3 attempts to recognize that the connected device is a GSM modem.

  • Page 409: Lua Scripts

    Chapter 7: Using the Web Interface Lua Scripts If you can write or obtain any Lua scripts, you can create or load them into the PX3 to control its behaviors. Raritan also provides some Lua scripts examples, which you can load as needed.
  • Page 410 Chapter 7: Using the Web Interface ▪ To remove any existing argument, click adjacent to it. Note: The above default arguments will be overridden by new arguments specified with the "Start with Arguments" command or with any Lua-script-related event rule. See Manually Starting or Stopping a Script (on page 391) or Start or Stop a Lua Script...
  • Page 411 Chapter 7: Using the Web Interface Manually Starting or Stopping a Script You can manually start or stop an existing Lua script at any time. When starting a script, you can choose to start it either with its default arguments or with new arguments. Tip: To have the PX3 automatically start or stop a script in response to an event, create an event rule.
  • Page 412 Chapter 7: Using the Web Interface Click Start. The script output will be shown in the Script Output section. ▪ If needed, click to delete the existing output data. To manually stop a script: Choose Device Settings > Lua Scripts. Click the desired script whose state is either 'Running' or 'Restarting.' For details, see Checking Lua Scripts States...
  • Page 413 Chapter 7: Using the Web Interface Checking Lua Scripts States Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state and settings of each script. State: Four script states are available. State Description The script is never executed since the device boot. Running The script is currently being executed.

  • Page 414: Miscellaneous

    Chapter 7: Using the Web Interface Make changes to the information shown, except for the script's name, which cannot be revised. ▪ To replace the current script, click Load Local File or Load Example to select a new script. To delete a script: Choose Device Settings >...
  • Page 415 Chapter 7: Using the Web Interface To set the Cisco EnergyWise configuration: Select the Enable EnergyWise checkbox. Configure the following: Field Description Domain name Type the name of a Cisco EnergyWise domain where the PX3 belongs ▪ Up to 127 printable ASCII characters are permitted. ▪...

  • Page 416: Maintenance

    Chapter 7: Using the Web Interface Maintenance Click 'Maintenance' in the Menu (on page 167), and the following submenu displays. Submenu command Refer to... Device Information Device Information (on page 398) Connected Users Viewing Connected Users (on page 403) Event Log Viewing or Clearing the Local Event Log (on page 405) Update Firmware...
  • Page 417 Chapter 7: Using the Web Interface Submenu command Refer to... Bulk Configuration Bulk Configuration (on page 411) Backup/Restore Backup and Restore of Device Settings (on page 418) Network Diagnostic Network Diagnostics (on page 420) Download Diagnostic Downloading Diagnostic Information (on page 421) Hardware Failures Hardware Issue Detection (on page 421)

  • Page 418: Device Information

    Chapter 7: Using the Web Interface Device Information Using the web interface, you can retrieve hardware and software information of components or peripheral devices connected to your PX3. Tip: If the information shown on this page does not match the latest status, press F5 to reload it.
  • Page 419 Chapter 7: Using the Web Interface Section title Information shown name, serial number, firmware version, hardware revision, MIB download link(s) and so Note that the download link of LHX-MIB is available only after enabling the Schroff LHX/SHX support. See Miscellaneous (on page 394).
  • Page 420 Chapter 7: Using the Web Interface Identifying Cascaded Devices For information on how to cascade PX3 devices, see Cascading Multiple PX3 Devices for Sharing Ethernet Connectivity (on page 34). This section explains how to identify a cascaded device on the Device Information page.
  • Page 421 Chapter 7: Using the Web Interface Cascading information in the Port Forwarding mode: • The Common section contains three read-only fields for indicating the cascading status. Fields Description Port forwarding Indicates the Port Forwarding is enabled. See Setting the Cascading Mode (on page 270).
  • Page 422 Chapter 7: 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 423: Viewing Connected Users

    Chapter 7: Using the Web Interface The following diagram shows 2, indicating it is the second slave device - Slave 2. The 'Cascaded device connected' field shows no, indicating that it is the final one in the chain. • For a list of port numbers required for accessing each cascaded device in the Port Forwarding mode, click the Port Forwarding title bar on the same page.
  • Page 424 Chapter 7: Using the Web Interface Column Description User Name The login name of each connected user. IP Address The IP address of each user's host. For the login via a local connection (serial RS-232 or USB), <local> is displayed instead of an IP address. Client Type The interface through which the user is being connected to the PX3.

  • Page 425: Viewing Or Clearing The Local Event Log

    Chapter 7: Using the Web Interface Viewing or Clearing the Local Event Log By default, the PX3 captures certain system events and saves them in a local (internal) event log. You can view over 2000 historical events that occurred on the PX3 in the local event log.

  • Page 426: Updating The Px3 Firmware

    Chapter 7: Using the Web Interface Updating the PX3 Firmware Firmware files are available on Raritan website's Support page (http://www.raritan.com/support/). When performing the firmware upgrade, the PX3 keeps each outlet's power status unchanged so no server operation is interrupted. During and after the firmware upgrade, outlets that have been powered on prior to the firmware upgrade remain powered ON and outlets that have been powered off remain powered OFF.
  • Page 427 Chapter 7: Using the Web Interface Once complete, information of both installed and uploaded firmware versions as well as compatibility and signature-checking results are displayed. ▪ If anything is incorrect, click Discard Upload. To proceed with the update, click Update Firmware. Warning: Do NOT power off the PX3 during the update.
  • Page 428 Chapter 7: Using the Web Interface Upgrade Guidelines for Existing Cascading Chains You must obey the following guidelines when upgrading a chain. Otherwise, a networking issue occurs. • Firmware version 3.3.10 or later is NOT compatible with pre-3.3.10 firmware versions in terms of the cascading feature so all Raritan devices in the cascading chain must run version 3.3.10 or later.
  • Page 429 3.5.0, 3.4.0, and so on. Therefore, it is suggested to AVOID downgrading your cascading chain unless instructed by Raritan or Legrand Technical Support. For minimum firmware versions, see Cascading Restrictions in the Cascading Guide on the Support page (http://www.raritan.com/support/).

  • Page 430: Viewing Firmware Update History

    Chapter 7: Using the Web Interface A Note about Firmware Upgrade Time The PDU firmware upgrade time varies from unit to unit, depending on various external and internal factors. External factors include, but are not limited to: network throughput, firmware file size, and speed at which the firmware is retrieved from the storage location.

  • Page 431: Bulk Configuration

    Chapter 7: Using the Web Interface If wanted, you can resort the list by clicking the desired column header. Sorting a List (on page 170). Bulk Configuration The Bulk Configuration feature lets you save generic settings of a configured PX3 device to your computer. You can use this configuration file to copy common settings to other PX3 devices of the same model and firmware version.
  • Page 432 Chapter 7: Using the Web Interface Note: On startup, PX3 performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset. For example, the "Bulk configuration copied"...
  • Page 433 Chapter 7: Using the Web Interface Mechanical designs ignored by bulk configuration: When the source and target devices share the same technical specifications but are only different with any "mechanical designs" which are indicated in the table below, the bulk configuration remains feasible. These mechanical designs are represented by suffixes added to the model name of a PX3 device.
  • Page 434 Chapter 7: Using the Web Interface Customizing Bulk Configuration Profiles A bulk profile defines which settings are downloaded/saved from the source device and which are not. The default is to apply the built-in bulk profile, which downloads all settings from the source device except for device-specific data. If the built-in profile does not meet your needs, you can create your own profile(s), and then apply the wanted profile before downloading/saving any settings from the source device.
  • Page 435 Chapter 7: Using the Web Interface Option Description Built-in The setting will follow the same setting of Raritan's built-in profile. ▪ If 'Excluded' is selected in the built-in profile, this setting will be also excluded. ▪ If 'Included' is selected in the built-in profile, this setting will be also included.
  • Page 436 Chapter 7: Using the Web Interface Step 2: Save a bulk configuration file You must have the Administrator Privileges or "Unrestricted View Privileges" to download the configuration. Log in to the source PX3 if you have not yet. Choose Maintenance > Bulk Configuration. Check the 'Bulk format' field.
  • Page 437 Chapter 7: Using the Web Interface Alternatives: To use a different bulk configuration method, refer to: • Bulk Configuration via SCP (on page 625) • Bulk Configuration or Firmware Upgrade via DHCP/TFTP (on page 655) • Configuration or Firmware Upgrade with a USB Drive (on page 641) •...

  • Page 438: Backup And Restore Of Device Settings

    Chapter 7: Using the Web Interface ▪ To select ALL profiles, select the topmost checkbox in the header row. Click on the top-right corner. Click Delete on the confirmation message. Backup and Restore of Device Settings Unlike the bulk configuration file, the backup file contains ALL device settings, including device-specific data like device names and all network settings.
  • Page 439 Chapter 7: Using the Web Interface To restore the PX3 using a backup file: You must have the Administrator Privileges to restore the device settings. Choose Maintenance > Backup/Restore. Click to select the backup file. Click 'Upload & Restore Device Settings' to upload the file. ▪...

  • Page 440: Network Diagnostics

    Chapter 7: Using the Web Interface Network Diagnostics PX3 provides the following tools in the web interface for diagnosing potential networking issues. • Ping: The tool is useful for checking whether a host is accessible through the network or Internet. •...

  • Page 441: Downloading Diagnostic Information

    Chapter 7: Using the Web Interface 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 PX3 to a client machine. The file is compressed into a .tgz file and should be sent to Raritan Technical Support for interpretation.
  • Page 442 Chapter 7: Using the Web Interface Hardware Failure alerts on the Dashboard page: Note that current hardware failure events, if any, will also display on the Dashboard (on page 171). Hardware failure types: Hardware issues Description A specific networking interface of PX3 is NOT detected. Network device not detected A specific I2C bus is stuck, which affects the communication with I2C Bus stuck...

  • Page 443: Rebooting The Px3

    Chapter 7: Using the Web Interface Rebooting the PX3 You can remotely reboot the PX3 via the web interface. Resetting the PX3 does not interrupt the operation of connected servers because there is no loss of power to outlets. During and after the reboot, outlets that have been powered on prior to the reboot remain powered on, and outlets that have been powered off remain powered off.

  • Page 444: Retrieving Software Packages Information

    Chapter 7: Using the Web Interface To reset the device to factory defaults: Choose Maintenance > Unit Reset > Type your password and then click Factory Reset to reset the PX3 to factory defaults. A message appears, with a countdown timer showing the remaining time of the operation.

  • Page 445: Webcam Management

    Chapter 7: Using the Web Interface Webcam Management The 'Webcams' menu item appears when there is any webcam(s) connected to the PX3, or when there are snapshots saved onto the PX3 already. See Connecting a Logitech Webcam (on page 78).
  • Page 446 Chapter 7: Using the Web Interface With a Logitech webcam connected to the PX3, you can visually monitor the ® environment around the PX3 via snapshots or videos captured by the webcam. Permissions required: To do... Permission(s) required Either permission below: View snapshots and videos ▪...

  • Page 447: Configuring Webcams And Viewing Live Images

    Chapter 7: Using the Web Interface Configuring Webcams and Viewing Live Images To configure a webcam or view live snapshot/video sessions, choose Webcams in the Menu (on page 167). Then click the desired webcam to open that webcam's page. Note that default webcam names are determined by the detection order. The one that is detected first is named Webcam, and the other that is detected later is named Webcam 2.
  • Page 448 Chapter 7: Using the Web Interface Tip: The date and time shown on the PX3 web interface are automatically converted to your computer's time zone. To avoid time confusion, it is suggested to apply the same time zone settings as those of PX3 to your computer or mobile device.
  • Page 449 Chapter 7: Using the Web Interface Click Edit Settings. Enter a name for the webcam. Up to 64 ASCII printable characters are supported. ▪ If configured to store snapshots on a remote server, the webcam's name determines the name of the folder where snapshots are stored. Changing Storage Settings (on page 434) and Identifying...

  • Page 450: Sending Links To Snapshots Or Videos

    Chapter 7: Using the Web Interface Sending Links to Snapshots or Videos When opening a Primary Standalone Live Preview window, a unique URL is generated for this window session. You can email or instant message this URL to as many people as possible as long as your system resources permit. Recipients can then click on the provided link and view live snapshots or videos simultaneously in the Secondary Standalone Live Preview window(s).
  • Page 451 Chapter 7: Using the Web Interface Select the URL shown on the top of the image. b. Right click to copy the URL, or press CTRL+ C. Send the URL link through an email or instant message application to one or multiple persons.

  • Page 452: Viewing And Managing Locally-Saved Snapshots

    Chapter 7: Using the Web Interface How Long a Link Remains Accessible For documentation purposes, the one who opens and sends the URL of the Primary Standalone Live Preview window is called User A and the two recipients of the same URL link are called User B and C. User C is able to access the snapshot or video image via the link when the URL link remains valid, which can be one of these scenarios: •...
  • Page 453 Chapter 7: Using the Web Interface To view saved snapshots: Choose Webcams > . The Snapshots page opens. Click the snapshot you want to view from the list. Tip: The date and time shown on the PX3 web interface are automatically converted to your computer's time zone.

  • Page 454: Changing Storage Settings

    Chapter 7: Using the Web Interface On the top of the list, click Click Delete on the confirmation message. To download any image onto the computer: • To download an image onto your computer, move your mouse to that image, right click on it, and choose Save Image As. Changing Storage Settings Important: The PX3 web interface only lists the snapshots stored locally on the PX3 device, but does NOT list those saved onto remote servers.
  • Page 455 Chapter 7: Using the Web Interface Storage location Description 'Local' means the PX3. This is the default. Local ▪ It can store a maximum of 10 snapshots only. ▪ The web interface can list and display all snapshots stored on the PX3. See Viewing and Managing Locally-Saved Snapshots (on page 432).
  • Page 456 Chapter 7: Using the Web Interface Tip for notifications showing the snapshots path on FTP: If you are using SNMP to retrieve PX3 data, you can make PX3 automatically send a notification containing the full path or URL to the snapshots saved onto FTP with this SNMP code: webcamStorageUploadStarted.
  • Page 457 Chapter 7: Using the Web Interface Number Folder name description The name of the webcam that your PX3 detects first. This is the folder where the snapshots captured by the first webcam are stored. ▪ The first webcam's default name is "Webcam". ▪...

  • Page 458: Smartlock And Card Reader

    Chapter 7: Using the Web Interface SmartLock and Card Reader Raritan's SmartLock kits provide several cabinet access control solutions. If you have purchased a SmartLock kit with the door handle controller "DX2-DH2C2", both menu items "SmartLock" and "Card Readers" will appear in the menu after connecting and configuring properly DX2-DH2C2 and the door handles included in the kit.
  • Page 459 Chapter 7: Using the Web Interface Note that "SmartLock" appears only when your door handles are connected to PX3 via DX2-DH2C2, but "Card Readers" appears as long as PX3 detects the presence of any card reader -- either a standalone USB card reader or a card reader integrated with the door handles.

  • Page 460: Smartlock

    Chapter 7: Using the Web Interface SmartLock To open the SmartLock page, choose SmartLock in the Menu (on page 167). The page shows information of all DX2-DH2C2 modules attached to PX3, including its serial number, position and its door handle configuration. On this page you can: •...
  • Page 461 Chapter 7: Using the Web Interface • Configure the door handles connected to DX2-DH2C2. You must set this because PX3 cannot detect the types of connected door handles. • Control the door handles connected to DX2-DH2C2. To configure the door handles: There are two door handle sections per DX2-DH2C2 because a DX2-DH2C2 has two door handle ports.
  • Page 462 Chapter 7: Using the Web Interface Section Description ▪ Specify how long the door handle lock can remain Timeout open after someone opens the door handle via a smart card or via remote control using the software. When the timeout expires, the door handle lock will be automatically closed.
  • Page 463 Chapter 7: Using the Web Interface Door Handle Status and Control After configuring the door handle type properly, two more sections are shown for the configured door handle -- Door State and Card Reader.
  • Page 464 Chapter 7: Using the Web Interface To view the status of the door and card reader: Section Description Shows all sensor states detected by DX2-DH2C2, including: Door State ▪ Door: States of contact closure sensors connected to DX2-DH2C2. Contact closure sensors detect whether the door is physically opened or closed.

  • Page 465: Card Readers

    Chapter 7: Using the Web Interface Go to the proper door handle section, and click Open or Close to open or close the door handle lock. Confirm the operation when prompted. Now you can physically open the cabinet door with the opened door handle.
  • Page 466 Chapter 7: Using the Web Interface When a user scans his/her smart card with the card reader, PX3 will retrieve the card's type and ID and show them in the corresponding Card Type and Card ID column. If no data is shown in the two columns, it means the scanned card may not be supported by the card reader.

  • Page 467: Chapter 8 Using Snmp

    Chapter 8 Using SNMP This SNMP section helps you set up the PX3 for use with an SNMP manager. The PX3 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 468: Snmpv2C Notifications

    Chapter 8: Using SNMP In the SNMP Notifications section, enable the SNMP notification feature, and configure related fields. For details, refer to: ▪ SNMPv2c Notifications (on page 448) ▪ SNMPv3 Notifications (on page 449) Note: Any changes made to the 'SNMP Notifications' section on the SNMP page will update the settings of the System SNMP Notification Action, and vice versa.

  • Page 469: Snmpv3 Notifications

    Chapter 8: Using SNMP Field Description once every 3 seconds. Number of retries 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. Host The IP address of the device(s) you want to access.
  • Page 470 Chapter 8: Using SNMP In the SNMP Notifications section, make sure the 'Enable SNMP notifications' checkbox is selected. Select 'SNMPv3 trap' or 'SNMPv3 inform' as the notification type. For SNMP TRAPs, the engine ID is prepopulated. Type values in the following fields. Field Description Host...
  • Page 471 Chapter 8: Using SNMP Field Description This is the address to which notifications are sent by the SNMP agent. Port The port number used to access the device(s). User ID User name for accessing the device. ▪ Make sure the user has the SNMP v3 access permission.

  • Page 472: Downloading Snmp Mib

    Chapter 8: Using SNMP Downloading SNMP MIB You must download an appropriate SNMP MIB file for successful SNMP communications. Always use the latest SNMP MIB downloaded from the current firmware of your PX3. You can download the MIBs from two different pages of the web interface. MIB download via the SNMP page: Choose Device Settings >...

  • Page 473: Snmp Gets And Sets

    Chapter 8: Using SNMP SNMP Gets and Sets In addition to sending notifications, the PX3 is able to receive SNMP get and set requests from third-party SNMP managers. • Get requests are used to retrieve information about the PX3, such as the system location, and the current on a specific outlet.
  • Page 474 Chapter 8: Using SNMP Layout Opening the MIB reveals the custom objects that describe the PX3 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 475: A Note About Enabling Thresholds

    Chapter 8: Using SNMP Configuring NTP Server Settings Using SNMP, you can change the following NTP server-related settings in the unitConfigurationTable: • Enable or disable synchronization of the device's date and time with NTP servers (synchronizeWithNTPServer) • Enable or disable the use of DHCP-assigned NTP servers if synchronization with NTP servers is enabled (useDHCPProvidedNTPServer) •...

  • Page 476: Chapter 9 Using The Command Line Interface

    Chapter 9 Using the Command Line Interface This section explains how to use the command line interface (CLI) to administer the PX3. Note that available CLI commands are model dependent. CLI commands are case sensitive. In This Chapter About the Interface ..................456 Logging in to CLI ....................

  • Page 477: Logging In To Cli

    Chapter 9: 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 478: With Ssh Or Telnet

    Chapter 9: Using the Command Line Interface After properly entering the password, the PDU name appears at the prompt. See Different CLI Modes and Prompts (on page 459) in the User Guide for more information. Tip: The 'Last login' information, including the date and time, is also displayed if the same user account was used to log in to this product's web interface or CLI.

  • Page 479: With An Analog Modem

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

  • Page 480: Closing A Local Connection

    Chapter 9: Using the Command Line Interface Closing a Local Connection Close the window or terminal emulation program when you finish accessing the PX3 over the local connection. When accessing or upgrading multiple PX3 devices, do not transfer the local connection cable from one device to another without closing the local connection window first.

  • Page 481: Querying Available Parameters For A Command

    Chapter 9: 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 (?) or list command (ls) to the end of that command.

  • Page 482: Showing Information

    Chapter 9: Using the Command Line Interface Showing Information You can use the show commands to view current settings or the status of the PX3 device or part of it, such as the IP address, networking mode, firmware version, states or readings of internal or external sensors, user profiles, and so Some "show"...
  • Page 483 Chapter 9: Using the Command Line Interface IP Configuration This command shows the IP settings shared by all network interfaces, such as DNS and routes. Information shown will include both IPv4 and IPv6 configuration. Tip: To show IPv4-only and IPv6-only configuration data, see IPv4-Only or IPv6-Only Configuration (on page 464).
  • Page 484 Chapter 9: Using the Command Line Interface IPv4-Only or IPv6-Only Configuration To show IPv4-only or IPv6-only configuration, use any of the following commands. Tip: To show both IPv4 and IPv6 configuration data, see IP Configuration page 463). To show IPv4 settings shared by all network interfaces, such as DNS and routes: show network ipv4 common To show IPv6 settings shared by all network interfaces, such as DNS and...
  • Page 485 Chapter 9: Using the Command Line Interface Interface Description bridge Show the IPv4 or IPv6 configuration of the BRIDGE interface. Show the IPv4 or IPv6 configuration of all interfaces. Tip: You can also type the command without adding this option "all" to get the same data. That is, show network ipv4 interface.

  • Page 486: Pdu Configuration

    Chapter 9: Using the Command Line Interface Network Service Settings This command shows the network service settings only, including the Telnet setting, TCP ports for HTTP, HTTPS, SSH and Modbus/TCP services, and SNMP settings. show network services <option> Variables: • <option>...

  • Page 487: Outlet Information

    Chapter 9: 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 488: Inlet Information

    Chapter 9: 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 489: Overcurrent Protector Information

    Chapter 9: 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 490: Date And Time Settings

    Chapter 9: Using the Command Line Interface Date and Time Settings This command shows the current date and time settings on the PX3. 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 PX3 web and CLI interfaces across all users, especially those users authenticated through...

  • Page 491: Environmental Sensor Information

    Chapter 9: 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 Variables: •...

  • Page 492: Environmental Sensor Package Information

    Chapter 9: Using the Command Line Interface * The environmental sensor number is the ID number assigned to the sensor, which can be found on the Peripherals page of the PX3 web interface. Displayed information: • Without the parameter "details," only the sensor ID, sensor type and reading are displayed.

  • Page 493: Actuator Information

    Chapter 9: 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 494: Inlet Sensor Threshold Information

    Chapter 9: 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.
  • Page 495 CLI is A, not mA. Sensor type Description peakCurrent Peak current sensor Supported on PXC and Legrand PDU only ▪ three-phase models als support pole-level peak current ▪ models with metered breakers also support...

  • Page 496: Inlet Pole Sensor Threshold Information

    Chapter 9: Using the Command Line Interface Inlet Pole Sensor Threshold Information This command syntax shows the specified inlet pole sensor's threshold-related information. show sensor inletpole <n> <p> <sensor type> To show detailed information, add the parameter "details" to the end of the command.
  • Page 497 CLI is A, not mA. Sensor type Description peakCurrent Peak current sensor Supported on PXC and Legrand PDU only ▪ three-phase models als support pole-level peak current ▪ models with metered breakers also support...

  • Page 498: Overcurrent Protector Sensor Threshold Information

    Chapter 9: Using the Command Line Interface Overcurrent Protector Sensor Threshold Information This command is only available for models with overcurrent protectors for protecting outlets. This command syntax shows the specified overcurrent protector sensor's threshold-related information. show sensor ocp <n> <sensor type> To show detailed information, add the parameter "details"...

  • Page 499: Environmental Sensor Threshold Information

    Chapter 9: 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...

  • Page 500: Environmental Sensor Default Thresholds

    Chapter 9: 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 Peripherals page of the PX3 web interface. Displayed information: •...

  • Page 501: Security Settings

    Chapter 9: Using the Command Line Interface Sensor types Description All of the above numeric sensors Tip: You can also type the command without adding this option "all" to get the same data. 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.

  • Page 502: Authentication Settings

    Chapter 9: Using the Command Line Interface Authentication Settings General authentication settings: This command displays the authentication settings of the PX3, including both LDAP and Radius settings. show authentication One LDAP server's settings: To show the configuration of a specific LDAP server, assign the desired LDAP server with its sequential number in the command.

  • Page 503: Existing User Profiles

    Chapter 9: 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 504: Existing Roles

    Chapter 9: 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 505: Asset Strip Settings

    Chapter 9: Using the Command Line Interface Asset Strip Settings This command shows the asset strip settings, such as the total number of rack units (tag ports), asset strip state, numbering mode, orientation, available tags and LED color settings. show assetStrip <n> Variables: •...

  • Page 506: Event Log

    Chapter 9: Using the Command Line Interface Option Description A specific Displays the settings of the specified rack unit on the number specified asset strip. Use the index number to specify the rack unit. The index number is available on the asset strip or the Asset Strip page of the web interface.

  • Page 507: Network Connections Diagnostic Log

    Chapter 9: Using the Command Line Interface Event type Description userAdministration User management events, such as a new user profile or a new role. userActivity User activities, such as login or logout. Displays PDU-related events. sensor Internal or external sensor events, such as state changes of any sensors.

  • Page 508: Command History

    Chapter 9: 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 509: Reliability Data

    Chapter 9: Using the Command Line Interface Reliability Data This command shows the reliability data. show reliability data Reliability Error Log This command shows the reliability error log. show reliability errorlog <n> Variables: • <n> is one of the options: 0 (zero) or any other integer number. Option Description Displays all entries in the reliability error log.
  • Page 510 Chapter 9: Using the Command Line Interface Example 1 - Basic Security Information The diagram shows the output of the show security command.
  • Page 511 Chapter 9: 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 512: Clearing Information

    Chapter 9: 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 PX3. After typing a "clear"...

  • Page 513: Clearing Diagnostic Log For Network Connections

    Chapter 9: Using the Command Line Interface Clearing Diagnostic Log for Network Connections This command removes all data from the diagnostic log for both the EAP authentication and WLAN connection. clear networkDiagLog -- OR -- clear networkDiagLog /y If you entered the command without "/y," a message appears, prompting you to confirm the operation.

  • Page 514: Quitting Configuration Mode

    Chapter 9: Using the Command Line Interface Quitting Configuration Mode Both of "apply" and "cancel" commands let you quit the configuration mode. The difference is that "apply" saves all changes you made in the configuration mode while "cancel" aborts all changes. To quit the configuration mode, use either command: config:# apply...
  • Page 515 Chapter 9: Using the Command Line Interface Enabling or Disabling Data Logging This command enables or disables the data logging feature. config:# pdu dataRetrieval <option> Variables: • <option> is one of the options: enable or disable. Option Description enable Enables the data logging feature. disable Disables the data logging feature.
  • Page 516 Chapter 9: Using the Command Line Interface Specifying the Device Altitude This command specifies the altitude of your PX3 above sea level (in meters). You must specify the altitude of PX3 above sea level if a Raritan's differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor.
  • Page 517 Chapter 9: Using the Command Line Interface Enabling or Disabling Peripheral Device Auto Management This command enables or disables the Peripheral Device Auto Management feature. config:# pdu peripheralDeviceAutoManagement <option> Variables: • <option> is one of the options: enable or disable. Option Description enable...

  • Page 518: Network Configuration Commands

    Chapter 9: Using the Command Line Interface Example 2 - Data Logging Enabled The following command enables the data logging feature. config:# pdu dataRetrieval enable Network Configuration Commands A network configuration command begins with network. A number of network settings can be changed through the CLI, such as the IP address, transmission speed, duplex mode, and so on.
  • Page 519 Chapter 9: Using the Command Line Interface • <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. Setting the IPv4 Preferred Host Name After selecting DHCP as the IPv4 configuration mode, you can specify the preferred host name, which is optional.
  • Page 520 Chapter 9: Using the Command Line Interface Setting the IPv4 Address After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX3. config:# network ipv4 interface <ETH> address <ip address> Variables: •...
  • Page 521 Chapter 9: 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 PX3 and devices in the other subnet. These commands are prefixed with network ipv4 staticRoutes.
  • Page 522 Chapter 9: Using the Command Line Interface config:# network ipv4 staticRoutes modify <route_ID> dest <dest-2> interface <ETH> Variables: • <dest-1> is a combination of the IP address and subnet mask of the other subnet. The format is IP address/subnet mask. •...
  • Page 523 Chapter 9: Using the Command Line Interface Interface Description bridge Determine the IPv6 configuration mode of the BRIDGE interface (that is, bridging mode). • <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 524 Chapter 9: Using the Command Line Interface • Cannot contain punctuation marks, spaces, and other symbols Setting the IPv6 Address After selecting the static IP configuration mode, you can use this command to assign a permanent IP address to the PX3. config:# network ipv6 interface <ETH>...
  • Page 525 Chapter 9: 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 526 Chapter 9: Using the Command Line Interface config:# network ipv6 staticRoutes modify <route_ID> dest <dest-2> interface <ETH> Variables: • <dest-1> is the IP address and prefix length of the subnet where the PX3 belongs. The format is IP address/prefix length. •...
  • Page 527 <suffix1>, <suffix2>, and the like are the DNS suffixes that automatically apply when searching for any device via PX3. For example, <suffix1> can be raritan.com, and <suffix2> can be legrand.com. You can specify up to 6 suffixes by separating them with commas.
  • Page 528 Chapter 9: Using the Command Line Interface • <option> is one of the options: true or false. Option Description true The specified network interface is enabled. false The specified network interface is disabled. Changing the LAN Interface Speed This command determines the LAN interface speed. config:# network ethernet <ETH>...
  • Page 529 Chapter 9: Using the Command Line Interface Changing the LAN Duplex Mode This command determines the LAN interface duplex mode. config:# network ethernet <ETH> duplexMode <mode> Variables: • <ETH> is one of the options -- eth1 or eth2. Option Description eth1 ETH1 port eth2...
  • Page 530 Chapter 9: Using the Command Line Interface • <method> is one of the authentication methods: NONE or EAP. Method Description NONE The authentication method is set to NONE. The authentication method is set to EAP. Setting Ethernet EAP Parameters When the selected Ethernet interface's authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, client certificate, client private key, password, CA certificate, and RADIUS authentication server.
  • Page 531 Chapter 9: Using the Command Line Interface config:# network ethernet <ETH> eapInnerAuthentication <inner_auth> Set the EAP identity: config:# network ethernet <ETH> eapIdentity <identity> Set the EAP password: config:# network ethernet <ETH> eapPassword After performing the above command, the PX3 prompts you to enter the password.
  • Page 532 Chapter 9: Using the Command Line Interface config:# network ethernet <ETH> allowConnectionWithIncorrectClock <option3> Set the RADIUS authentication server for EAP: config:# network ethernet <ETH> eapAuthServerName <FQDN> Variables: • <ETH> is one of the options -- eth1 or eth2. Option Description eth1 ETH1 port eth2...
  • Page 533 Chapter 9: Using the Command Line Interface • <option2> is one of the options: true or false. Option Description true Always make the network connection successful even though the TLS certificate chain contains any certificate which is outdated or not valid yet. false The network connection is NOT successfully established when the TLS certificate chain contains any certificate...
  • Page 534 Chapter 9: Using the Command Line Interface Open a CA certificate using a text editor. You should see certificate contents similar to the following. Select and copy the contents as illustrated below, including the starting line containing "BEGIN CERTIFICATE" and the ending line containing "END CERTIFICATE."...
  • Page 535 Chapter 9: Using the Command Line Interface ▪ CA certificate: config:# network ethernet eth1 eapCACertificate The system prompts you to enter the contents of the chosen certificate or private key. Press Enter without typing any data. Verify whether the system shows the following command prompt, indicating the existing certificate or private key has been removed.
  • Page 536 Chapter 9: Using the Command Line Interface Enabling or Disabling 802.11n High Throughput This command enables or disables the 802.11n high throughput protocol. config:# network wireless enableHT <option> Variables: • <option> is one of the options: true or false. Option Description true 802.11n is enabled.
  • Page 537 Chapter 9: Using the Command Line Interface Setting Wireless EAP Parameters When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, client certificate, client private key, password, CA certificate, and RADIUS authentication server.
  • Page 538 Chapter 9: Using the Command Line Interface Allow expired and not yet valid TLS certificates: config:# network wireless allowOffTimeRangeCerts <option2> Allow wireless network connection with incorrect system time: config:# network wireless allowConnectionWithIncorrectClock <option3> Set the RADIUS authentication server for EAP: config:# network wireless eapAuthServerName <FQDN>...
  • Page 539 Chapter 9: Using the Command Line Interface Option Description false The network connection is NOT successfully established when the TLS certificate chain contains any certificate which is outdated or not valid yet. • <option3> is one of the options: true or false. Option Description true...
  • Page 540 Chapter 9: Using the Command Line Interface Mode Description portForwarding The Port Forwarding mode, where every cascaded device in the chain shares the same IP address, with diverse port numbers assigned. Important: When enabling either cascading mode, you must make sure the other cascading mode is disabled, or the preferred cascading mode may not be enabled successfully.
  • Page 541 Chapter 9: Using the Command Line Interface Setting Network Service Parameters A network service command begins with network services. 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>...
  • Page 542 Chapter 9: 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 543 Chapter 9: Using the Command Line Interface Option Description false The Telnet service is disabled. Changing the Telnet Port This command changes the Telnet port. config:# network services telnet port <n> Variables: • <n> is a TCP port number between 1 and 65535. The default Telnet port is Changing the SSH Configuration You can enable or disable the SSH service, or change its TCP port using the CLI commands.
  • Page 544 Chapter 9: 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 545 Chapter 9: 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 546 Chapter 9: 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 547 Chapter 9: 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 548: Time Configuration Commands

    Chapter 9: Using the Command Line Interface • <option> is one of the options: enable or disable. Option Description enable Service advertisement via the selected method (MDNS or LLMNR) is enabled. disable Service advertisement via the selected method (MDNS or LLMNR) is disabled. Examples This section illustrates several network configuration examples.
  • Page 549 Chapter 9: Using the Command Line Interface Determining the Time Setup Method This command determines the method to configure the system date and time. config:# time method <method> Variables: • <method> is one of the time setup options: manual or ntp. Mode Description manual...
  • Page 550 Chapter 9: Using the Command Line Interface Setting NTP Parameters A time configuration command for NTP-related parameters begins with time ntp. Specify the primary time server: config:# time ntp firstServer <first_server> Specify the secondary time server: config:# time ntp secondServer <second_server> To delete the primary time server: config:# time ntp firstServer ""...
  • Page 551 Chapter 9: Using the Command Line Interface Customizing the Date and Time To manually configure the date and time, use the following CLI commands to specify them. Note: You shall set the time configuration method to "manual" prior to customizing the date and time. See Determining the Time Setup Method page 529).
  • Page 552 Chapter 9: Using the Command Line Interface Type apply for the selected time zone to take effect. Setting the Automatic Daylight Savings Time This command determines whether the daylight saving time is applied to the time settings. config:# time autoDST <option> Variables: •...

  • Page 553: Checking The Accessibility Of Ntp Servers

    Chapter 9: Using the Command Line Interface Checking the Accessibility of NTP Servers This command verifies the accessibility of NTP servers specified manually on your PX3 and then shows the result. For instructions on specifying NTP servers via CLI, see Setting NTP Parameters (on page 530).
  • Page 554 Chapter 9: Using the Command Line Interface config:# security ipAccessControl ipv4 defaultPolicyIn <policy> Determine the default IPv4 firewall control policy for outbound traffic: config:# security ipAccessControl ipv4 defaultPolicyOut <policy> • IPv6 commands Enable or disable the IPv6 firewall control feature: config:# security ipAccessControl ipv6 enabled <option>...
  • Page 555 Chapter 9: Using the Command Line Interface Tip: You can combine both commands to modify all firewall control parameters at a time. See Multi-Command Syntax (on page 615). Managing Firewall Rules You can add, delete or modify firewall rules using the CLI commands. •...
  • Page 556 Chapter 9: Using the Command Line Interface config:# security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy> <insert> <rule_number> -- OR -- config:# security ipAccessControl ipv6 rule add <direction> <insert> <rule_number> <ip_mask> <policy> Variables: • <direction> is one of the options: in or out. Direction Description Inbound traffic.
  • Page 557 Chapter 9: Using the Command Line Interface Modifying a Firewall Rule Depending on what to modify in an existing rule, the command varies. • IPv4 commands Modify an IPv4 rule's IP address and/or subnet mask: config:# security ipAccessControl ipv4 rule modify <direction> <rule_number> ipMask <ip_mask>...
  • Page 558 Chapter 9: Using the Command Line Interface Direction Description Outbound traffic. • <rule_number> is the number of the existing rule that you want to modify. • <ip_mask> is the combination of the IP address and subnet mask values (or prefix length), which are separated with a slash. For example, an IPv4 combination looks like this: 192.168.94.222/24.
  • Page 559 Chapter 9: Using the Command Line Interface Restricted Service Agreement The CLI command used to set the Restricted Service Agreement feature begins with security restrictedServiceAgreement, Enabling or Disabling the Restricted Service Agreement This command activates or deactivates the Restricted Service Agreement. config:# security restrictedServiceAgreement enabled <option>...
  • Page 560 Chapter 9: Using the Command Line Interface After the Restricted Service Agreement feature is enabled, the agreement's content is displayed on the login screen. Do either of the following, or the login fails: • In the web interface, select the checkbox labeled "I understand and accept the restricted service agreement."...
  • Page 561 Chapter 9: Using the Command Line Interface Specifying the Agreement Contents This command allows you to create or modify contents of the Restricted Service Agreement. config:# security restrictedServiceAgreement bannerContent After performing the above command, do the following: Type the text comprising up to 10,000 ASCII characters when the CLI prompts you to enter the content.
  • Page 562 Chapter 9: Using the Command Line Interface Login Limitation The login limitation feature controls login-related limitations, such as password aging, simultaneous logins using the same user name, and the idle time permitted before forcing a user to log out. A login limitation command begins with security loginLimits. You can combine multiple commands to modify various login limitation parameters at a time.
  • Page 563 Chapter 9: Using the Command Line Interface Password Aging Interval This command determines how often the password should be changed. config:# security loginLimits passwordAgingInterval <value> Variables: • <value> is a numeric value in days set for the password aging interval. The interval ranges from 7 to 365 days.
  • Page 564 Chapter 9: 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 565 Chapter 9: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option> Variables: • <option> is one of the options: enable or disable. Option Description enable At least one lowercase character is required. disable No lowercase character is required. Uppercase Character Requirement This command determines whether a strong password includes at least a uppercase character.
  • Page 566 Chapter 9: Using the Command Line Interface 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 At least one special character is required.
  • Page 567 Chapter 9: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 enabled <option> Determine the IPv4 role-based access control policy: config:# security roleBasedAccessControl ipv4 defaultPolicy <policy> • IPv6 commands Enable or disable the IPv6 role-based access control feature: config:# security roleBasedAccessControl ipv6 enabled <option> Determine the IPv6 role-based access control policy: config:# security roleBasedAccessControl ipv6 defaultPolicy <policy>...
  • Page 568 Chapter 9: 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 569 Chapter 9: 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 570 Chapter 9: 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 571 Chapter 9: 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 572 Chapter 9: Using the Command Line Interface Enabling or Disabling Front Panel Actuator Control The following CLI commands control whether you can turn on or off connected actuator(s) by operating the front panel LCD display. To enable the front panel actuator control feature: config:# security frontPanelPermissions add switchActuator To disable the front panel actuator control feature:...
  • Page 573 Chapter 9: Using the Command Line Interface Example 1 - IPv4 Firewall Control Configuration The following command sets up two parameters of the IPv4 access control feature. config:# security ipAccessControl ipv4 enabled true defaultPolicyIn accept defaultPolicyOut accept Results: • The IPv4 access control feature is enabled. •...

  • Page 574: Outlet Configuration Commands

    Chapter 9: Using the Command Line Interface Example 4 - Adding an IPv4 Role-based Access Control Rule The following command creates a newIPv4 role-based access control rule and specifies its location in the list. config:# security roleBasedAccessControl ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertAbove 3 Results: •...
  • Page 575 Chapter 9: 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 1. The value is an integer between 1 and 50. •...

  • Page 576: Overcurrent Protector Configuration Commands

    Chapter 9: Using the Command Line Interface Overcurrent Protector Configuration Commands An overcurrent protector configuration command begins with ocp. The command configures an individual circuit breaker or fuse which protects outlets. Changing the Overcurrent Protector Name This command names a circuit breaker or a fuse which protects outlets on your PX3.
  • Page 577 Chapter 9: Using the Command Line Interface Variables: • <name> is a string comprising up to 32 ASCII printable characters. The <name> variable CANNOT contain spaces. • <option> is one of the options: enable or disable. Option Description enable Enables the newly-created user profile. disable Disables the newly-created user profile.
  • Page 578 Chapter 9: Using the Command Line Interface Type the following command to change the password for the user profile "May." config:# user modify May password Type a new password when prompted, and press Enter. Type the same new password and press Enter. If the password change is completed successfully, the config:# prompt appears.
  • Page 579 Chapter 9: 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 PX3 only after that user's user profile is enabled. config:# user modify <name> enabled <option> Variables: •...
  • Page 580 Chapter 9: Using the Command Line Interface config:# user modify <name> snmpV3Access <option1> Determine the security level: config:# user modify <name> securityLevel <option2> Determine whether the authentication passphrase is identical to the password: config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3> Determine the authentication passphrase: config:# user modify <name>...
  • Page 581 Chapter 9: Using the Command Line Interface config:# user modify <name> privacyProtocol <option6> Variables: • <name> is the name of the user whose settings you want to change. • <option1> is one of the options: enable or disable. Option Description enable Enables the SNMP v3 access permission for the specified user.
  • Page 582 Chapter 9: Using the Command Line Interface Option Description SHA-1 SHA-1 authentication protocol is applied. • <option6> is one of the options: DES or AES-128. Option Description DES privacy protocol is applied. AES-128 AES-128 privacy protocol is applied. • An authentication or privacy passphrase is a string comprising 8 to 32 ASCII printable characters.
  • Page 583 Chapter 9: Using the Command Line Interface Tip: To set the default measurement units applied to the PX3 user interfaces for all users via CLI, see Setting Default Measurement Units (on page 565). Set the preferred temperature unit: config:# user modify <name> preferredTemperatureUnit <option1> Set the preferred length unit: config:# user modify <name>...
  • Page 584 Chapter 9: Using the Command Line Interface Specifying the SSH Public Key If the SSH key-based authentication is enabled, specify the SSH public key for each user profile using the following procedure. To specify or change the SSH public key for a specific user: Type the SSH public key command as shown below and press Enter.
  • Page 585 Chapter 9: Using the Command Line Interface Changing Your Own Password Every user can change their own password via this command if they have the Change Own Password privilege. Note that this command does not begin with user. config:# password After performing this command, the PX3 prompts you to enter both current and new passwords respectively.
  • Page 586 Chapter 9: Using the Command Line Interface Tip: To change the preferred measurement units displayed in the PX3 user interfaces for a specific user via CLI, see Changing Measurement Units (on page 562). Set the default temperature unit: config:# user defaultpreferences preferredTemperatureUnit <option1> Set the default length unit: config:# user defaultpreferences preferredLengthUnit <option2>...
  • Page 587 Chapter 9: 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 Mary enable admin Results: • A new user profile "Mary" is created. •...

  • Page 588: Role Configuration Commands

    Chapter 9: Using the Command Line Interface Role Configuration Commands A role configuration command begins with role. Creating a Role This command creates a new role, with a list of semicolon-separated privileges assigned to the role. config:# role create <name> <privilege1>;<privilege2>;<privilege3>... If a specific privilege contains any arguments, that privilege should be followed by a colon and the argument(s).
  • Page 589 Chapter 9: Using the Command Line Interface Privilege Description changeExternalSensorsConfiguration Change Peripheral Device Configuration changeLhxConfiguration Change LHX/SHX Configuration changeModemConfiguration Change Modem Configuration changeNetworkSettings Change Network Settings changePassword Change Own Password changePduConfiguration Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration changeSecuritySettings Change Security Settings changeSnmpSettings Change SNMP Settings...
  • Page 590 Chapter 9: Using the Command Line Interface switchActuator:2 switchActuator:3 • A list of comma-separated ID numbers of different actuators. For example: switchActuator:1,3,6 Note: The ID number of each actuator is shown in the PX3 web interface. It is an integer. Modifying a Role You can modify diverse parameters of an existing role, including its privileges.

  • Page 591: Authentication Commands

    Chapter 9: Using the Command Line Interface config:# role modify <name> removePrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Note: When removing privileges from a role, make sure the specified privileges and arguments (if any) exactly match those assigned to the role. Otherwise, the command fails to remove specified privileges that are not available.
  • Page 592 Chapter 9: Using the Command Line Interface Determining the Authentication Method You can choose to set the authentication type only, or both set the authentication type and determine whether to switch to local authentication in case the remote authentication is not available. Determine the authentication type only: config:# authentication type <option1>...
  • Page 593 Chapter 9: Using the Command Line Interface LDAP Settings All LDAP-related commands begin with authentication ldap. If you enable LDAP authentication, you must add at least one LDAP server. Later you can modify or delete any existing LDAP server as needed. Adding an LDAP Server Adding an LDAP server requires the entry of quite a lot of parameters, such as the server's IP address, TCP port number, Base DN and so on.
  • Page 594 Chapter 9: Using the Command Line Interface Tip: To verify all settings of a newly-added server, see Authentication Settings (on page 482). Variables: • <host> is the IP address or host name of the LDAP server. • <port> is the port number assigned for communication with the LDAP server.
  • Page 595 Chapter 9: Using the Command Line Interface config:# authentication ldap add <host> <port> <ldap_type> <security> <bind_type> <base_DN> <login_name_att> <user_entry_class> adDomain <AD_domain> ▪ Example 2 -- Set up the bind DN: config:# authentication ldap add <host> <port> <ldap_type> <security> <bind_type> <base_DN> <login_name_att> <user_entry_class> bindDN <bind_DN>...
  • Page 596 Chapter 9: Using the Command Line Interface • <allow_exp_cert> is one of the options: true or false. Option Description true Certificates that are either expired or not valid yet are all accepted. false Only valid certificates are accepted. Illustrations of Adding LDAP Servers This section shows several LDAP command examples.
  • Page 597 Chapter 9: Using the Command Line Interface b. The system prompts you to specify the bind DN password. Type the password and press Enter. d. Re-type the same password. Copying an Existing Server's Settings If the server that you will add completely shares the same settings with any server that has been configured, use the following command.
  • Page 598 Chapter 9: Using the Command Line Interface Parameters Description Change the IP address or host name. host <host> ▪ <host> is the new IP address or host name. Change the TCP port number. port <port> ▪ <port> is the new TCP port number. Change the server type.
  • Page 599 Chapter 9: Using the Command Line Interface Parameters Description Re-upload a different certificate. certificate First add the "certificate" parameter to the command, and press Enter. b. The system prompts you for the input of the certificate. Type or copy the content of the certificate in the CLI and press Enter.
  • Page 600 Chapter 9: Using the Command Line Interface Removing an Existing LDAP Server This command removes an existing LDAP server from the server list. config:# authentication ldap delete <server_num> Variables: • <server_num> is the sequential number of the specified server in the LDAP server list.
  • Page 601 Chapter 9: Using the Command Line Interface Example: config:# authentication radius add 192.168.7.99 chap 1812 1813 10 3 Modifying an Existing Radius Server You can modify one or multiple parameters of an existing Radius server, or change the priority or sequence of existing servers in the server list. Change the IP address or host name: config:# authentication radius modify <server_num>...
  • Page 602 Chapter 9: Using the Command Line Interface config:# authentication radius modify <server_num> sortPositon <position> Tip: You can add more than one parameters to the command. For example, "authentication radius modify <server_num> host <host> authType <rds_type> authPort <auth_port> accountPort <acct_port> ...". Variables: •...

  • Page 603: Environmental Sensor Configuration Commands

    Chapter 9: Using the Command Line Interface Environmental Sensor Configuration Commands An environmental sensor configuration command begins with externalsensor. You can configure the name and location parameters of an individual environmental sensor. Note: To configure an actuator, see Actuator Configuration Commands page 600).
  • Page 604 Chapter 9: Using the Command Line Interface Type Description smokeDetection The connected detector/switch is for detection of the smoke presence. waterDetection The connected detector/switch is for detection of the water presence. vibration The connected detector/switch is for detection of the vibration.
  • Page 605 Chapter 9: 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 606 Chapter 9: 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 607: Configuring Environmental Sensors' Default Thresholds

    Chapter 9: 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 608 Chapter 9: Using the Command Line Interface config:# defaultThresholds <sensor type> hysteresis <hy_value> Set the Default Assertion Timeout for a specific sensor type: config:# defaultThresholds <sensor type> assertionTimeout <as_value> Variables: • <sensor type> is one of the following numeric sensor types: Sensor types Description absoluteHumidity...

  • Page 609: Sensor Threshold Configuration Commands

    Chapter 9: 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 610 Chapter 9: Using the Command Line Interface config:# sensor inlet <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an inlet sensor: config:# sensor inlet <n> <sensor type> hysteresis <hy_value> Set the assertion timeout for an inlet sensor: config:# sensor inlet <n>...
  • Page 611 CLI is A, not mA. Sensor type Description peakCurrent Peak current sensor Supported on PXC and Legrand PDU only ▪ three-phase models als support pole-level peak current ▪ models with metered breakers also support...
  • Page 612 Chapter 9: Using the Command Line Interface Commands for Inlet Pole Sensors A sensor configuration command for inlet poles begins with sensor inletpole. This type of command is available on a three-phase PDU only. You can configure various inlet pole sensor threshold settings at a time by combining multiple commands.
  • Page 613 Chapter 9: Using the Command Line Interface • <sensor type> is one of the following sensor types: Sensor type Description current Current sensor voltage Voltage sensor activePower Active power sensor apparentPower Apparent power sensor powerFactor Power factor sensor activeEnergy Active energy sensor unbalancedCurrent Unbalanced load sensor Note: If the requested sensor type is not supported, the "Sensor is not...
  • Page 614 CLI is A, not mA. Sensor type Description peakCurrent Peak current sensor Supported on PXC and Legrand PDU only ▪ three-phase models als support pole-level peak current ▪ models with metered breakers also support...
  • Page 615 Chapter 9: Using the Command Line Interface Commands for Overcurrent Protector Sensors A sensor configuration command for overcurrent protectors begins with sensor ocp. You can configure various overcurrent protector threshold settings at a time by combining multiple commands. See Multi-Command Syntax (on page 615).
  • Page 616 Chapter 9: 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 the overcurrent protector sensor. Disables the specified threshold for the overcurrent disable protector sensor.
  • Page 617 Chapter 9: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> hysteresis <hy_value> Set the assertion timeout for an environmental sensor: config:# sensor externalsensor <n> <sensor type> assertionTimeout <as_value> Variables: • <n> is the ID number of the environmental sensor that you want to configure.
  • Page 618 Chapter 9: Using the Command Line Interface • <hy_value> is a numeric value that is assigned to the hysteresis for the specified environmental sensor. See "To De-assert" and Deassertion Hysteresis (on page 782). • <as_value> is a number in samples that is assigned to the assertion timeout for the specified environmental sensor.
  • Page 619 Chapter 9: Using the Command Line Interface config:# sensor ocp 2 current upperWarning enable upperCritical 16 Results: • The Upper Critical threshold for the 2nd overcurrent protector's RMS current is set to 16A. It also enables the upper critical threshold if this threshold has not been enabled yet.

  • Page 620: Actuator Configuration Commands

    Chapter 9: 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 Multi-Command Syntax (on page 615).

  • Page 621: Server Reachability Configuration Commands

    Chapter 9: Using the Command Line Interface • <description> is a string comprising up to 64 ASCII printable characters, and it must be enclosed in quotes when it contains spaces. Example - Actuator Naming The following command assigns the name "Door lock of cabinet 3" to the actuator whose ID number is 9.
  • Page 622 Chapter 9: 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 623 Chapter 9: Using the Command Line Interface config:# serverReachability modify <n> pingMonitoringEnabled <option> Modify the number of successful pings for declaring "Reachable": config:# serverReachability modify <n> numberOfSuccessfulPingsToEnable <succ_number> Modify the number of unsuccessful pings for declaring "Unreachable": config:# serverReachability modify <n> numberOfUnsuccessfulPingsForFailure <fail_number>...

  • Page 624: Energywise Configuration Commands

    Chapter 9: Using the Command Line Interface • <succ_number> is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200. • <fail_number> is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to 100. •...
  • Page 625 Chapter 9: Using the Command Line Interface Specifying the EnergyWise Domain This command syntax specifies to which Cisco EnergyWise domain the PX3 ® belongs. config:# energywise domain <name> Variables: • <name> is a string comprising up to 127 ASCII printable characters. Spaces and asterisks are NOT acceptable.

  • Page 626: Asset Management Commands

    Chapter 9: Using the Command Line Interface Setting the Polling Interval This command syntax determines the polling interval at which the Cisco ® EnergyWise domain queries the PX3. config:# energywise polling <timing> Variables: • <timing> is an integer number in seconds. It ranges between 30 and 600 seconds.
  • Page 627 Chapter 9: Using the Command Line Interface Naming an Asset Strip This command syntax names or changes the name of an asset strip connected to the PX3 device. config:# assetStrip <n> name "<name>" Variables: • <n> is the number of the FEATURE port where the selected asset strip is physically connected.
  • Page 628 Chapter 9: Using the Command Line Interface Specifying the Rack Unit Numbering Mode This command syntax specifies the numbering mode of rack units on the asset strips connected to the PX3 device. The numbering mode changes the rack unit numbers. config:# assetStrip <n>...
  • Page 629 Chapter 9: Using the Command Line Interface Specifying the Asset Strip Orientation This command syntax specifies the orientation of the asset strips connected to the PX3 device. Usually you do not need to perform this command unless your asset strips do NOT come with the tilt sensor, causing the PX3 unable to detect the asset strips' orientation.
  • Page 630 Chapter 9: Using the Command Line Interface Setting LED Colors for Disconnected Tags This command syntax sets the LED color for all rack units on the connected asset strip(s) to indicate the absence of a connected asset tag. config:# assetStrip <n> LEDColorForDisconnectedTags <color> Variables: •...
  • Page 631 Chapter 9: Using the Command Line Interface Setting the LED Operation Mode This command syntax determines whether a specific rack unit on the specified asset strip follows the global LED color settings. config:# rackUnit <n> <rack_unit> LEDOperationMode <mode> Variables: • <n>...
  • Page 632 Chapter 9: 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 strip. 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 633: Serial Port Configuration Commands

    Chapter 9: Using the Command Line Interface Mode Description blinkSlow This mode has the LED blink slowly. blinkFast This mode has the LED blink quickly. Examples This section illustrates several asset management examples. Example 1 - Asset Strip 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 634 Chapter 9: Using the Command Line Interface Setting the Baud Rates The following commands set the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the PX3 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 635: Multi-Command Syntax

    Chapter 9: Using the Command Line Interface Option Description forceAnalogModem The PX3 attempts to recognize that the connected device is an analog modem. forceGsmModem The PX3 attempts to recognize that the connected device is a GSM modem. Example The following command sets the CONSOLE baud rate of the PX3 device's serial port to 9600 bps.

  • Page 636: Actuator Control Operations

    Chapter 9: Using the Command Line Interface config:# sensor ocp 2 current upperCritical disable upperWarning 15 Results: • The Upper Critical threshold of the 2nd overcurrent protector's RMS current is disabled. • The Upper Warning threshold of the 2nd overcurrent protector's RMS current is set to 15A and enabled at the same time.

  • Page 637: Switching On An Actuator

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

  • Page 638: Example - Turning On A Specific Actuator

    Chapter 9: Using the Command Line Interface ▪ Type n to abort the operation Example - Turning On a Specific Actuator The following command turns on the actuator whose ID number is 8. control actuator 8 on Unblocking a User If any user is blocked from accessing the PX3, you can unblock them at the local console.

  • Page 639: Resetting To Factory Defaults

    Chapter 9: Using the Command Line Interface If you entered the command without "/y" in Step 2, a message appears prompting you to confirm the operation. Type y to confirm the reset. Wait until the reset is complete. Note: Device reset will cause CLI communications over an "USB" connection to be lost.

  • Page 640: Quitting Diagnostic Mode

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

  • Page 642: Retrieving Previous Commands

    Chapter 9: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your PX3 and a network host. diag> traceroute <host> <useICMP> Variables: • <host> is the name or IP address of the host you want to trace. •...

  • Page 643: Logging Out Of Cli

    Chapter 9: Using the Command Line Interface Examples: • Example 1 (only one possible command): Type the first word and the first letter of the second word of the "reset factorydefaults" command -- that is, reset f. b. Then press Tab or Ctrl+i to complete the second word. •...

  • Page 644: Chapter 10 Using Scp Commands

    Chapter 10 Using SCP Commands You can perform a Secure Copy (SCP) command to update the PX3 firmware, do bulk configuration, or back up and restore the configuration. In This Chapter Firmware Update via SCP ................. 624 Bulk Configuration via SCP ................625 Backup and Restore via SCP ................

  • Page 645: Bulk Configuration Via Scp

    Chapter 10: Using SCP Commands SCP example: scp pdu-px2-030410-44599.bin admin@192.168.87.50:/fwupdate Windows PSCP command: PSCP in Windows works in a similar way to the SCP. ▪ 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: Save a configuration from a source PX3.

  • Page 646: Backup And Restore Via Scp

    Chapter 10: Using SCP Commands The system copies the configuration included in the file "bulk_config.txt" to another PX3, and displays the following message. Starting restore operation. The connection will be closed now. SCP examples: • Save operation: scp admin@192.168.87.50:/bulk_config.txt today_config.txt •...

  • Page 647: Downloading Diagnostic Data Via Scp

    Chapter 10: Using SCP Commands ▪ <device ip> is the IP address or hostname of the PX3 whose settings you want to back up. Type the user password when prompted. The system saves the settings from the PX3 to a file named "backup_settings.txt."...
  • Page 648 Chapter 10: Using SCP Commands Scenario 1: Use the default SCP port and default filename ▪ SSH/SCP port is the default (22), and the accessed PX3 is a standalone device. ▪ The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot (.) in the end of the SCP command as shown below.

  • Page 649: Uploading Or Downloading Raw Configuration Data

    Chapter 10: Using SCP Commands SCP example: scp admin@192.168.87.50:/diag-data.zip . Windows PSCP command: PSCP in Windows works in a similar way to the SCP. ▪ pscp -P <port> <user name>@<device ip>:/diag-data.zip <filename> Uploading or Downloading Raw Configuration Data You can download the raw configuration data of a specific PX3 for review, backup or modification.
  • Page 650 Chapter 10: Using SCP Commands Scenario 3: Specify a new filename but use the default SCP port ▪ SSH/SCP port is the default (22), and the accessed PX3 is a standalone device. ▪ Renaming the raw configuration file is wanted. scp <user name>@<device ip>:/raw_config.txt <filename>...
  • Page 651 Chapter 10: Using SCP Commands Scenario 2: Only one PX3 to configure, with a non-default SCP port ▪ SSH/SCP port is NOT the default (22), or the accessed PX3 is a Port-Forwarding slave device. ▪ There is only one device to configure so a CSV file for device-specific settings is NOT needed. scp -P <port>...

  • Page 652: Keys That Cannot Be Uploaded

    Chapter 10: Using SCP Commands ▪ If the second column contains each device's serial number, the parameter is then serial:2. ▪ If the seventh column contains each device's MAC address, the parameter is then mac:7. SCP examples: • Raw configuration download example -- scp admin@192.168.87.50:/raw_config.txt config.txt •...
  • Page 653 Chapter 10: Using SCP Commands Note that these configuration keys cannot be part of the configuration that you will upload to any PX3. That is, they should be either not available or they remain to be commented out in the configuration file you will upload.

  • Page 654: Maximum Ambient Operating Temperature

    Appendix A Specifications In This Chapter Maximum Ambient Operating Temperature ............ 634 Serial RS-232 "RJ-45" Port Pinouts ..............634 Sensor RJ-45 Port Pinouts ................. 634 Feature RJ-45 Port Pinouts ................635 Expansion RJ-45 Port Pinouts ................636 Maximum Ambient Operating Temperature The maximum ambient operating temperature (TMA) for PX3 is 60 degrees Celsius.

  • Page 655: Appendix A Specifications

    Appendix A: Specifications RJ-45 Pin/signal definition +12V ― Power (fuse protected) +12V ― Power (fuse protected) ― Signal Ground RS485_DP bi-directional Data Positive of the RS-485 RS485_DN bi-directional Data Negative of the RS-485 ― Signal Ground 1-wire ― 1-wire signal for Raritan environmental sensor packages ―...

  • Page 656: Expansion Rj-45 Port Pinouts

    Appendix A: Specifications RJ-45 Pin/signal definition Pin No. Signal Direction Description Raritan devices. Do NOT connect. ― Signal Ground Input Reserved Expansion RJ-45 Port Pinouts RJ-45 Pin/signal definition Pin No. Signal Direction Description +12V ― Power (fuse protected) +12V ― Power (fuse protected) ―...

  • Page 657: Appendix B Equipment Setup Worksheet

    Appendix B Equipment Setup Worksheet PX3 Series Model ____________ PX3 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 658 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 659 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 660 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 661: 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 PX3. • Configuration changes •...

  • Page 662: System And Usb Requirements

    Appendix C: Configuration or Firmware Upgrade with a USB Drive ▪ If no firmware upgrade task will be performed, a happy smiley is displayed after around 30 seconds. The happy smiley looks like one of the following, depending on your Raritan product.

  • Page 663: Configuration Files

    Appendix C: Configuration or Firmware Upgrade with a USB Drive Configuration Files There are three types of configuration files. • fwupdate.cfg: This file MUST be always present for performing configuration or firmware upgrade tasks. See fwupdate.cfg (on page 644). • config.txt: This file is used for configuring device settings.

  • Page 664: Fwupdate.cfg

    Appendix C: Configuration or Firmware Upgrade with a USB Drive fwupdate.cfg The configuration file, fwupdate.cfg, is an ASCII text file containing key-value pairs, one per line. Each value in the file must be separated by an equal sign (=), without any surrounding spaces.
  • Page 665 Appendix C: Configuration or Firmware Upgrade with a USB Drive logfile • Specify the name of a text file where the PX3 will append the log messages when interpreting the USB drive contents. • If the specified file does not exist in the USB drive, it will be automatically created.
  • Page 666 Appendix C: Configuration or Firmware Upgrade with a USB Drive • The default value is serial:1, making the PX3 search for its serial number in the first column. • This option is used only if the "device_list" option has been set. factory_reset •...
  • Page 667 Appendix C: Configuration or Firmware Upgrade with a USB Drive • The PX3 device beeps after it finishes writing the diagnostic data to the USB drive. tls_cert_file • Specify the filename of the wanted TLS server certificate. The filename can contain a single placeholder ${SERIAL} that is replaced with the serial number of the PX3.

  • Page 668: Config.txt

    Appendix C: Configuration or Firmware Upgrade with a USB Drive config.txt To perform device configuration using a USB drive, you must: • Copy the device configuration file "config.txt" to the root directory of the USB drive. • Reference the "config.txt" file in the config option of the "fwupdate.cfg" file.
  • Page 669 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. Example: magic:users[1].cleartext_password=joshua ▪...

  • Page 670: Devices.csv

    Appendix C: Configuration or Firmware Upgrade with a USB Drive Tip: You can also download "config.txt" from a specific PX3 or upload it to a specific PX3 from anywhere in the world via Internet. See Raw Configuration Upload and Download (on page 678).

  • Page 671: Creating Configuration Files Via Mass Deployment Utility

    Appendix C: Configuration or Firmware Upgrade with a USB Drive Creating Configuration Files via Mass Deployment Utility The Mass Deployment Utility is an Excel file that lets you fill in basic information required for the three configuration files, such as the admin account and password.

  • Page 672: Data Encryption In 'Config.txt

    Appendix C: Configuration or Firmware Upgrade with a USB Drive Data Encryption in 'config.txt' When intending to prevent people from identifying the values of any settings, you can encrypt them. Encrypted data still can be properly interpreted and performed by any PX3 running firmware version 3.2.20 or later. Data encryption procedure: Open the "config.txt"...

  • Page 673: Firmware Upgrade Via Usb

    Appendix C: Configuration or Firmware Upgrade with a USB Drive The CLI generates and shows the encrypted form of "private." In the "config.txt" file, make the following changes to the SNMP write community setting. Replace the word "private" with the encrypted value that CLI shows. b.
  • Page 674 Appendix C: Configuration or Firmware Upgrade with a USB Drive ▪ Sad smiley: Failed. Check the log file in the USB drive or contact Raritan Technical Support to look into the failure cause. The sad smiley looks like one of the following. For the first diagram, its background color will turn red.

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

    Appendix D Bulk Configuration or Firmware Upgrade via DHCP/TFTP If a TFTP server is available, you can use it and appropriate configuration files to perform any or all of the following tasks for a large number of PX3 devices in the same network.

  • Page 676: Bulk Configuration/Upgrade Procedure

    Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure Any firmware downgrade using "fwupdate.cfg" is NOT supported by default. Only firmware upgrade is permitted with "fwupdate.cfg". A special parameter is required to permit firmware downgrade via "fwupdate.cfg". fwupdate.cfg (on page 644).

  • Page 677: Tftp Requirements

    Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP TFTP Requirements To perform bulk configuration or firmware upgrade successfully, your TFTP server must meet the following requirements: • The server is able to work with both IPv4 and IPv6. In Linux, remove any IPv4 or IPv6 flags from /etc/xinetd.d/tftp. Note: DHCP will execute the "fwupdate.cfg"...
  • Page 678 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Click Add to add a new vendor class. Specify a unique name for this vendor class and type the binary codes of "Raritan PDU 1.0" in the New Class dialog. The vendor class is named "Raritan PDU"...
  • Page 679 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Right-click the IPv4 node in DHCP to select Set Predefined Options. b. Select DHCP Standard Options in the "Option class" field, and Vendor Class Identifier in the "Option name" field. Leave the String field blank. Add three options to the new vendor class "Raritan PDU"...
  • Page 680 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Select Raritan PDU in the "Option class" field. b. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.
  • Page 681 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Click Add to add the second option. Type "pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field. d. Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field.
  • Page 682 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The policy is named "PDU" in this illustration. Click Add to add a new condition.
  • Page 683 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. Click Next.
  • Page 684 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 685 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 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 686 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 687: Dhcp Ipv6 Configuration In Windows

    Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Important: The magic cookie is transmitted to and stored in PX3 at the time of executing the "fwupdate.cfg" commands. The DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX3.
  • Page 688 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Right-click the IPv6 node in DHCP to select Define Vendor Classes. b. Click Add to add a new vendor class. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)"...
  • Page 689 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Add three options to the "Raritan PDU 1.0" vendor class. Right-click the IPv6 node in DHCP to select Set Predefined Options.
  • Page 690 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select Raritan PDU 1.0 in the "Option class" field. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.
  • Page 691 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Click Add to add the second option. Type "pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field. 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.
  • Page 692 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 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 693 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. 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 694: Dhcp Ipv4 Configuration In Linux

    Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Important: The magic cookie is transmitted to and stored in PX3 at the time of executing the "fwupdate.cfg" commands. The DHCP/TFTP operation is triggered only when there is a mismatch between the magic cookie in DHCP and the one stored in PX3.
  • Page 695 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Configure the same option in DHCP accordingly. The PX3 accepts the configuration or firmware upgrade only when this value in DHCP matches. Set the following three sub-options in the "vendor-encapsulated-options" (option 43). ▪...

  • Page 696: Dhcp Ipv6 Configuration In Linux

    Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP IPv4 illustration example in dhcpd.conf: DHCP IPv6 Configuration in Linux Modify the "dhcpd6.conf" file for IPv6 settings when your DHCP server is running Linux. Required Linux IPv6 settings in DHCP: Locate and open the "dhcpd6.conf" file of the DHCP server. The PX3 will provide the following values to the "vendor-class"...
  • Page 697 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP ▪ 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 698: Appendix E Raw Configuration Upload And Download

    Appendix E Raw Configuration Upload and Download You can modify any existing "config.txt", and then upload it to a specific PX3 for modifying part or all of its settings. There are two ways to get one "config.txt": • You create this file by yourself, either using or not using the Mass Deployment Utility.

  • Page 699: Download Via Curl

    Appendix E: Raw Configuration Upload and Download Parameter Description <user> Any user name that has the Administrator Privileges. <password> The password of the specified user name. <device IP> Hostname or IP address of the PX3 whose raw configuration you want to download. ▪...

  • Page 700: Uploading Raw Configuration

    Appendix E: Raw Configuration Upload and Download Parameter Description <password> The password of the specified user name. <device IP> Hostname or IP address of the PX3 whose raw configuration you want to download. When the download is complete, a line indicates 100 in the first % column. Go to the directory where you perform the curl command to find the "config.txt"...

  • Page 701: Upload Via Curl

    Appendix E: Raw Configuration Upload and Download Upload via Curl If curl is available on your computer, you can upload the raw configuration to PX3 with the curl command. There are two scenarios with the curl upload methods. • When there are NO device-specific settings involved, you upload the configuration file only, regardless of the number of PX3 devices to update.

  • Page 702: Curl Upload Return Codes

    Appendix E: Raw Configuration Upload and Download Parameter Description <user>, Refer to the above table for explanation. ▪ For device-specific settings in the <config <password>, file>, refer each device-specific configuration <device IP>, key to a specific column in the <dev_list <config file>.
  • Page 703 Appendix E: Raw Configuration Upload and Download Code Description An internal error occurred. A parameter error occurred. A raw configuration update operation is already running. The file is too large. Invalid raw configuration file provided. Invalid device list file or match provided. Device list file required but missing.

  • Page 704: Appendix F Resetting To Factory Defaults

    Appendix F Resetting to Factory Defaults You can use either the reset button or the command line interface (CLI) to reset the PX3. Important: Exercise caution before resetting the PX3 to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on.

  • Page 705: Using The Cli Command

    Appendix F: Resetting to Factory Defaults Note: PuTTY is a free program you can download from the Internet. See PuTTY's documentation for details on configuration. Using the CLI Command The Command Line Interface (CLI) provides a reset command for restoring the PX3 to factory defaults.

  • Page 706: Appendix G Px3 Models With Residual Current Monitoring

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

  • Page 707: Rcm State Sensor

    Appendix G: PX3 Models with Residual Current Monitoring RCM sensor type Description PDU models Detects AC leakage and is sensitive down to 6mA Models ending in Type A leakage. Detects AC and DC leakage and is sensitive down to Models ending in: Type B 14mA.

  • Page 708: Compliance With Iec 62020

    Appendix G: PX3 Models with Residual Current Monitoring Important: When your PX3 enters the power-sharing mode, the RCM sensor enters the 'unavailable' state and will not work until the power-sharing mode ends. For information on power sharing, see Power-Sharing Restrictions and Connection (on page 43).

  • Page 709: Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring IEC 62020 specification PX3 with RCM characteristics Connection of load Monitored line is directly connected. conductors Fault indicating means Visual, with other output signals. Ability to directly discriminate Directionally non-discriminating. Rated residual operating 0.5A (highest value).

  • Page 710: Web Interface Operations For Rcm

    Appendix G: PX3 Models with Residual Current Monitoring Web Interface Operations for RCM The RCM on PX3 is either an inlet sensor or an inlet pole sensor. To view, configure or run self-test, click Inlet in the Menu (on page 167). Checking RCM State and Current A section titled 'Residual Current Monitor' is available on the Inlet page, showing both the present RCM state and residual current.
  • Page 711 Appendix G: PX3 Models with Residual Current Monitoring Locate the Residual Current Monitor section on the Inlet page. ▪ RCM State: There are five states - normal, warning, critical, self-test active and failure. For more information, see RCM State Sensor page 687).

  • Page 712: Setting Rcm Current Thresholds

    Appendix G: PX3 Models with Residual Current Monitoring RCM Critical State Alarm When a PX3 device's RCM sensor enters the Critical state, the PX3 beeps and this alarm is displayed in the Alerted Sensors section of the Dashboard page. Note that only the RCM sensor will cause the PDU to beep while RCM "DC" sensor does not cause the PDU to beep regardless of its sensor state.

  • Page 713: Scheduling Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring In the Residual Current Monitor section, click Setup. Set up RCM thresholds. Enable or disable the Residual Operating Current, which is the critical threshold. Residual current greater than this value triggers Critical RCM state.

  • Page 714: Disabling Or Enabling Front Panel Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring Disabling or Enabling Front Panel RCM Self-Test You can enable or disable the function of performing the RCM self-test by operating the front panel buttons. By default, this function is enabled. To disable or enable the front panel RCM self-test: Choose Device Settings >...
  • Page 715 Appendix G: PX3 Models with Residual Current Monitoring Click the desired sensor (required), and then click Edit Thresholds. For example, select "L1 Residual DC Current". Make changes as needed. ▪ To enable any threshold, select the corresponding checkbox. ▪ Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, Sensor Threshold Settings (on page 777).

  • Page 716: Front Panel Operations For Rcm

    Appendix G: PX3 Models with Residual Current Monitoring Front Panel Operations for RCM The front panel LCD display shows an alarm message when the RCM enters the critical state. Besides, you can operate the LCD display to check the RCM status. This section introduces the RCM information shown on the dot-matrix LCD display.

  • Page 717: Checking Rcm States And Current

    Appendix G: PX3 Models with Residual Current Monitoring If needed, you can press to perform RCM self-test for this inlet. For details, see steps 4 to 5 in the topic titled Running RCM Self-Test (on page 698). Checking RCM States and Current You can retrieve RCM information from the LCD display.

  • Page 718: Running Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring Running RCM Self-Test You can perform the RCM self-test by operating the front panel buttons. For Type B "M18" models, the self-test feature will perform tests on all poles of the selected inlet simultaneously. To disable or enable this front panel function, see Disabling or Enabling Front Panel RCM Self-Test...

  • Page 719: Rcm Snmp Operations

    Appendix G: PX3 Models with Residual Current Monitoring After completing the RCM self-test, the LCD display indicates the RCM self-test result: passed or failed. Press to return to the RCM information page. Do one of the following: ▪ To return to the Main Menu, press ▪...

  • Page 720: Rcm Residual Current And State Objects

    Appendix G: PX3 Models with Residual Current Monitoring RCM Residual Current and State Objects The inletSensorMeasurementsTable contains entries for RCM residual current and states. Use index sensorType = 26 to retrieve the row for residual current. Column measurementsInletSensorValue contains the residual current. Use index sensorType = 27 to retrieve the row for RCM state.

  • Page 721: Showing Residual Current Monitoring Information

    Appendix G: PX3 Models with Residual Current Monitoring Showing Residual Current Monitoring Information This command syntax shows the residual current monitoring (RCM) information, which is only available on the models with RCM. The information displayed include the RCM current, state and thresholds. For Type B "M18"...
  • Page 722 Appendix G: PX3 Models with Residual Current Monitoring config:# residualCurrentMonitor <n> criticalRatedResidualOperatingCurrent <value> Note: The PX3 triggers events when residual current values are above (but not equal to) thresholds. For example, you would set the critical threshold to 29mA to specify the IEC 62020 IΔn of 30mA. See Compliance with IEC 62020 (on page 688).

  • Page 723: Setting Front Panel Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring Setting Front Panel RCM Self-Test You can enable or disable the front panel RCM self-test function via CLI in addition to the web interface. To enable the front panel RCM self-test: security frontPanelPermissions add rcmSelfTest To disable the front panel RCM self-test: security frontPanelPermissions remove rcmSelfTest Running RCM Self-Test...

  • Page 724: Appendix H Old Generations Of Px3 Models

    Appendix H Old Generations of PX3 Models There are two types of old PX3 PDUs. • PX3 phase I models • PX3 phase II models Old PX3 PDUs are different from PX3 with iX7 controller in terms of the ™ following designs: •...

  • Page 725: Px3 'Phase I' Front Panel Display

    Appendix H: Old Generations of PX3 Models PX3 'Phase I' Front Panel Display The following diagram is the Zero U model of PX3 'phase II' PDUs. Its LCD display on the panel can show the reading or status of different components on the PX3, or its MAC address and IP address.

  • Page 726: Control Buttons

    Appendix H: Old Generations of PX3 Models Section Information shown The following information is displayed: • Readings, data or state of the selected target. • During the firmware upgrade, "FUP" is displayed. Two types of information may be displayed: • The "ALARM"...

  • Page 727: Operating The Lcd Display

    Appendix H: Old Generations of PX3 Models • FUNC (Function) button for switching between different data of the selected target, such as the current, voltage or power readings of a particular outlet Operating the LCD Display After powering on or resetting this product, the LCD display panel shows the current reading of OUTLET 1 by default before you select a different target.
  • Page 728 Appendix H: Old Generations of PX3 Models ▪ W is displayed for the power reading. W means Watt. If the word "ALARM" appears below the reading, it means the currently displayed reading already reaches or crosses the upper or lower thresholds.
  • Page 729 Appendix H: Old Generations of PX3 Models Section Example information This inlet's L1 current reading is 23 amps. The selected inlet line is L1. "MASTER" indicates the PX3 is the master device in a cascading chain. For a slave device, it shows "SLAVE" instead. Note: "MASTER/SLAVE"...
  • Page 730 Appendix H: Old Generations of PX3 Models Overcurrent Protector Information The Overcurrent Protector mode is displayed as either "CB" or "FUSE" on the LCD display, which varies according to the type of overcurrent protector implemented on your PX3. CB refers to the circuit breaker and FUSE refers to the fuse.
  • Page 731 Appendix H: Old Generations of PX3 Models IPv4 Address The IP address is available in the Device mode, which is indicated by the alphabet 'd' shown at the top of the LCD display. Note that this type of LCD display only shows the IPv4 address (if available). Below illustrates the IP address information.
  • Page 732 Appendix H: Old Generations of PX3 Models To retrieve the "IPv4" address on PX3: Press the MODE button to enter the Device mode, indicated by an alphabet "d" at the top left of the display. The LCD display cycles between the four octets of the IPv4 address, indicated by "i4"...
  • Page 733 Appendix H: Old Generations of PX3 Models For example, if the MAC address is 00:0d:5d:03:5E:1A, the LCD display shows the following information one after another: M 00 --> M:0d --> M:5d --> M:03 --> M:5E --> M:1A Note that 'M' is NOT followed by the colon symbol when showing the first two digits of the MAC address.
  • Page 734 Appendix H: Old Generations of PX3 Models ▪ When showing a numeric sensor's reading, the appropriate measurement unit is displayed to the right of the reading. Measurement Sensor types units A relative humidity sensor A temperature sensor An air flow sensor An air pressure sensor NO measurement For an "absolute"...
  • Page 735 Appendix H: Old Generations of PX3 Models Press the FUNC button to display the X, Y and Z coordinates of the sensor respectively. ▪ X coordinate is shown as "x:NN," where NN are the first two numeric digits entered for the X coordinate in the web interface. ▪...
  • Page 736 Appendix H: Old Generations of PX3 Models Section Example information "30" indicates that the selected target is the 30th rack unit. "MASTER" indicates the PX3 is the master device in a cascading chain. For a slave device, it shows "SLAVE" instead. Note: "MASTER/SLAVE"...
  • Page 737 Appendix H: Old Generations of PX3 Models USB-Cascaded Device's Position Note: As of release 3.3.10, the following cascading information is no longer available in the Bridging mode, but remains available in the Port Forwarding mode. A cascaded device's position is available by operating the LCD display. Below illustrates a slave device's position.
  • Page 738 Appendix H: Old Generations of PX3 Models Number Device position Number Device position Master device Slave 8 Slave 1 Slave 9 Slave 2 Slave 10 Slave 3 Slave 11 Slave 4 Slave 12 Slave 5 Slave 13 Slave 6 Slave 14 Slave 7 Slave 15 RCM Information...
  • Page 739 Appendix H: Old Generations of PX3 Models To display the RCM current: Press the MODE button until the term "INLET" is displayed. Verify the LCD is showing the inlet's current, which is indicated by the presence of the letter "A." If not, switch to current by pressing the FUNC button.

  • Page 740: Serial Rs-232 "Db9" Port Pinouts

    Appendix H: Old Generations of PX3 Models Below illustrates the RCM self-test mode. Section Example information The inlet containing RCM sensor is INLET 1. The LCD alternates between "SLF" and "tSt" to indicate that this is self-test mode. ALARM always displays for residual current sensor. LEAK always displays for residual current sensor.

  • Page 741: Appendix Ildap Configuration Illustration

    Appendix I LDAP Configuration Illustration This section provides an LDAP example for illustrating the configuration procedure using Microsoft Active Directory (AD). To configure LDAP ® authentication, four main steps are required: Determine user accounts and roles (groups) intended for the PX3 b.

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

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

  • Page 743: Step C. Configure Ldap Authentication On The Px3

    Appendix I: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the PX3 You must enable and set up LDAP authentication properly on the PX3 to use external authentication. In the illustration, we assume: • The DNS server settings have been configured properly. See Wired Network Settings (on page 254) and...
  • Page 744 Appendix I: LDAP Configuration Illustration Field/setting Do this... Ensure the field is set to sAMAccountName because the LDAP server is Login Name Attribute Microsoft Active Directory. Ensure the field is set to user because the LDAP server is Microsoft Active User entry object class Directory.
  • Page 745 Appendix I: LDAP Configuration Illustration Click Add Server.The LDAP server is saved. In the Authentication Type field, select LDAP. Click Save. The LDAP authentication is activated.

  • Page 746: Step D. Configure Roles On The Px3

    Appendix I: LDAP Configuration Illustration Note: If the PX3 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 PX3 and the LDAP server to use the same NTP server(s).
  • Page 747 Appendix I: LDAP Configuration Illustration In the Privileges list, select Unrestricted View Privileges, which includes all View permissions. The Unrestricted View Privileges permission lets users view all settings without the capability to configure or change them. d. Click Save. The PX_User role is created. Keep the Roles page open to create the PX_Admin role.
  • Page 748 Appendix I: LDAP Configuration Illustration In the Privileges list, select Administrator Privileges. The Administrator Privileges allows users to configure or change all PX3 settings. d. Click Save. The PX_Admin role is created.

  • Page 749: Appendix J Updating The Ldap Schema

    Appendix J Updating the LDAP Schema In This Chapter Returning User Group Information ..............729 Setting the Registry to Permit Write Operations to the Schema ..... 730 Creating a New Attribute .................. 730 Adding Attributes to the Class ................731 Updating the Schema Cache ................

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

    Appendix J: 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: Right-click the Active Directory Schema root node in the left pane of the ®...

  • Page 751: Adding Attributes To The Class

    Appendix J: Updating the LDAP Schema Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears. Type rciusergroup in the Common Name field. Type rciusergroup in the LDAP Display Name field. Type 1.3.6.1.4.1.13742.50 in the Unique x5000 Object ID field.
  • Page 752 Appendix J: Updating the LDAP Schema Scroll to the user class in the right pane and right-click it. Choose Properties from the menu. The user Properties dialog appears. Click the Attributes tab to open it. Click Add. Choose rciusergroup from the Select Schema Object list.

  • Page 753: Updating The Schema Cache

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

  • Page 756: Appendix K Radius Configuration Illustration

    Appendix K 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 FreeRADIUS server. The following steps are required for any RADIUS authentication: Configure RADIUS authentication on the PX3.
  • Page 757 Appendix K: RADIUS Configuration Illustration b. On the NPS, configure Connection Request Policies and the standard attribute. See Step B: Configure Connection Policies and Standard Attributes (on page 741). Some configuration associated with Microsoft Active Directory (AD) is also required for RADIUS authentication. See AD-Related Configuration (on page 768).
  • Page 758 Appendix K: RADIUS Configuration Illustration 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 PX3. In this example, they are 1812 and 1813. Then close this dialog.
  • Page 759 Appendix K: RADIUS Configuration Illustration Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. Do the following to add your PX3 to NPS: Verify the "Enable this RADIUS client" checkbox is selected. b.
  • Page 760 Appendix K: 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 PX3. Click OK.
  • Page 761 Appendix K: RADIUS Configuration Illustration Step B: Configure Connection Policies and Standard Attributes You need to configure the following for connection request policies: • IP address or host name of the PX3 • Connection request forwarding method • Authentication method(s) •...
  • Page 762 Appendix K: RADIUS Configuration Illustration Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. Type a descriptive name for identifying this policy in the "Policy name" field.
  • Page 763 Appendix K: RADIUS Configuration Illustration ▪ You can leave the "Type of network access server" field to the default -- Unspecified.
  • Page 764 Appendix K: RADIUS Configuration Illustration Click Next to show the "Specify Conditions" screen. Click Add. The "Select condition" dialog appears. Click Add.
  • Page 765 Appendix K: RADIUS Configuration Illustration The NAS IPv4 Address dialog appears. Type the PX3 IP address -- 192.168.56.29, and click OK. Click Next in the New Connection Request Policy dialog. Select "Authenticate requests on this server" because a local NPS server is used in this example.
  • Page 766 Appendix K: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. When the system prompts you to select the authentication method, select the following two options: ▪ Override network policy authentication settings ▪ CHAP -- the PX3 uses "CHAP" in this example...
  • Page 767 Appendix K: RADIUS Configuration Illustration Note: If your PX3 uses PAP, then select "PAP."...
  • Page 768 Appendix K: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
  • Page 769 Appendix K: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
  • Page 770 Appendix K: 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 OK.
  • Page 771 Appendix K: RADIUS Configuration Illustration Admin inside the curved brackets {} is the existing role on the PX3. It is recommended to use the Admin role to test this configuration. The role name is case sensitive.
  • Page 772 Appendix K: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
  • Page 773 Appendix K: RADIUS Configuration Illustration 15. Click Next to continue.

  • Page 774: Freeradius Standard Attribute Illustration

    Appendix K: RADIUS Configuration Illustration 16. A summary showing connection request policy settings is displayed. Click Finish to close the dialog. FreeRADIUS Standard Attribute Illustration With standard attributes, NO dictionary files are required. You simply add all user data, including user names, passwords, and roles, in the following FreeRADIUS path.

  • Page 775: Vendor-Specific Attributes

    Appendix K: RADIUS Configuration Illustration steve Cleartext-Password := "test123" Filter-ID = "Raritan:G{Admin}", Filter-ID = "Raritan:G{SystemTester}" Vendor-Specific Attributes You must specify the following properties when using a RADIUS vendor-specific attribute (VSA). • Vendor code = 13742 • Vendor-assigned attribute number = 26 •...
  • Page 776 Appendix K: RADIUS Configuration Illustration Step A: Add Your PX3 as a RADIUS Client The RADIUS implementation on the PX3 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. Presumptions in the illustration: •...
  • Page 777 Appendix K: RADIUS Configuration Illustration 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 PX3. In this example, they are 1812 and 1813. Then close this dialog.
  • Page 778 Appendix K: RADIUS Configuration Illustration Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. Do the following to add your PX3 to NPS: Verify the "Enable this RADIUS client" checkbox is selected. b.
  • Page 779 Appendix K: 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 PX3. Click OK.
  • Page 780 Appendix K: RADIUS Configuration Illustration Step B: Configure Connection Policies and Vendor-Specific Attributes You need to configure the following for connection request policies: • IP address or host name of the PX3 • Connection request forwarding method • Authentication method(s) •...
  • Page 781 Appendix K: RADIUS Configuration Illustration Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. Type a descriptive name for identifying this policy in the "Policy name" field.
  • Page 782 Appendix K: RADIUS Configuration Illustration ▪ You can leave the "Type of network access server" field to the default -- Unspecified.
  • Page 783 Appendix K: RADIUS Configuration Illustration Click Next to show the "Specify Conditions" screen. Click Add. The "Select condition" dialog appears. Click Add.
  • Page 784 Appendix K: RADIUS Configuration Illustration The NAS IPv4 Address dialog appears. Type the PX3 IP address -- 192.168.56.29, and click OK. Click Next in the New Connection Request Policy dialog. Select "Authenticate requests on this server" because a local NPS server is used in this example.
  • Page 785 Appendix K: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. When the system prompts you to select the authentication method, select the following two options: ▪ Override network policy authentication settings ▪ CHAP -- the PX3 uses "CHAP" in this example...
  • Page 786 Appendix K: RADIUS Configuration Illustration Note: If your PX3 uses PAP, then select "PAP." 10. Select Vendor Specific to the left of the dialog, and click Add. The Add Vendor Specific Attribute dialog appears. 11. Select Custom in the Vendor field, and click Add. The Attribute Information dialog appears.

  • Page 787: Freeradius Vsa Illustration

    Appendix K: RADIUS Configuration Illustration Note that multiple roles are separated with a space. 16. Click OK. FreeRADIUS VSA Illustration A vendor-specific dictionary file is required for the vendor-specific-attribute configuration on FreeRADIUS. Therefore, there are two major configuration steps. Use a dictionary to define the Raritan vendor-specific attribute b.

  • Page 788: Ad-Related Configuration

    Appendix K: RADIUS Configuration Illustration VENDOR Raritan 13742 BEGIN-VENDOR Raritan ATTRIBUTE Raritan-User-Roles 26 string END-VENDOR Raritan Step B -- create a user profile for "steve" in FreeRADIUS: Go to this location: /etc/raddb/users. Add the data of the user "steve" by typing the following. Note that the values after the equal sign (=) must be enclosed in double quotes (").
  • Page 789 Appendix K: RADIUS Configuration Illustration Right-click NPS (Local) and select "Register server in Active Directory." Click OK, and then OK again. To grant PX3 users remote access permission: Open Active Directory Users and Computers. Open the properties dialog of the user whom you want to grant the access permission.
  • Page 790 Appendix K: RADIUS Configuration Illustration Click the Dial-in tab and select the "Allow access" checkbox. To enable reversible encryption for CHAP authentication: Open Active Directory Users and Computers. Open the properties dialog of the user that you want to configure.
  • Page 791 Appendix K: RADIUS Configuration Illustration Click the Account tab and select the "Store password using reversible encryption" checkbox.

  • Page 792: Appendix L Additional Px3 Information

    Appendix L Additional PX3 Information In This Chapter RJ45-to-DB9 Cable Requirements for Modem Connections......772 Reserving IP Addresses in DHCP Servers ............773 Sensor Threshold Settings ................777 Default Voltage and Current Thresholds ............785 Altitude Correction Factors ................787 Unbalanced Current Calculation ...............

  • Page 793: Reserving Ip Addresses In Dhcp Servers

    Appendix L: Additional PX3 Information Pin signal DB9 pin No. RJ-45 pin No. Note: The RJ45-to-DB9 adapter/cable used for connecting modems CANNOT be used to connect the PX3 to a computer. See RJ45-to-DB9 Cable Requirements for Computer Connections (on page 32). Reserving IP Addresses in DHCP Servers PX3 uses its serial number as the client identifier in the DHCP request.

  • Page 794: Reserving Ip In Windows

    Appendix L: Additional PX3 Information Reserving IP in Windows To reserve the IP address of any network interface in the Windows DHCP server, you must convert that interface's client identifier into hexadecimal ASCII codes. For each interface's client identifier, see Reserving IP Addresses in DHCP Servers (on page 773).

  • Page 795: Reserving Ip In Linux

    Appendix L: Additional PX3 Information Reserving IP in Linux There are two methods to reserve the IP address of any network interface in the standard Linux DHCP server (ISC DHCP server): • Convert an interface's client identifier into hexadecimal ASCII codes. •...
  • Page 796 Appendix L: Additional PX3 Information Interface Client identifier conversion WIRELESS PEG1A00003-WIRELESS = 50 45 47 31 41 30 30 30 30 33 2D 57 49 52 45 4C 45 53 53 ▪ The suffix comprising the dash symbol and the word "WIRELESS"...

  • Page 797: Sensor Threshold Settings

    Appendix L: Additional PX3 Information Sensor Threshold Settings This section explains the thresholds settings for a numeric sensor. Thresholds and Sensor States A numeric sensor has four thresholds: 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.
  • Page 798 Appendix L: Additional PX3 Information above upper critical Upper Critical above upper warning Upper Warning normal Lower Warning below lower warning Lower Critical below lower critical Available sensor states:...
  • Page 799 Appendix L: Additional PX3 Information The more thresholds are enabled for a sensor, the more sensor states are available for it. The "normal' state is always available regardless of whether any threshold is enabled. For example: • When a sensor only has the Upper Critical threshold enabled, it has two sensor states: normal and above upper critical.

  • Page 800: To Assert" And Assertion Timeout

    Appendix L: Additional PX3 Information "To Assert" and Assertion Timeout If multiple sensor states are available for a specific sensor, the PX3 asserts a state for it whenever a bad state change occurs. To assert a state: To assert a state is to announce a new, "worse" state. Below are bad state changes that cause the PX3 to assert.
  • Page 801 Appendix L: Additional PX3 Information In the threshold settings, the Assertion Timeout field postpones the "assertion" action. It determines how long a sensor must remain in the "worse" new state before the PX3 triggers the "assertion" action. If that sensor changes its state again within the specified wait time, the PX3 does NOT assert the worse state.

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

    Appendix L: Additional PX3 Information "To De-assert" and Deassertion Hysteresis After the PX3 asserts a worse state for a sensor, it may de-assert that state later on if the readings improve. To de-assert a state: To de-assert a state is to announce the end of the previously-asserted worse state.
  • Page 803 Appendix L: Additional PX3 Information...
  • Page 804 Appendix L: Additional PX3 Information In the threshold settings, the Deassertion Hysteresis field determines a new level to trigger the "deassertion" action. This function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system when the temperature exceeds a pre-determined level.

  • Page 805: Default Voltage And Current Thresholds

    Appendix L: Additional PX3 Information Assumption: Upper Warning threshold is enabled. Upper Warning = 20 (degrees Celsius) Deassertion Hysteresis = 3 (degrees Celsius) "Deassertion" level = 20-3 = 17 (degrees Celsius) When the PX3 detects that a temperature sensor's reading drops below 20 degrees Celsius, moving from the "above upper warning"...
  • Page 806 Appendix L: Additional PX3 Information Multi-phase inlets or outlets: • Line-Line RMS voltage: Threshold Default value Lower critical -6% of minimum rating Lower warning -3% of minimum rating Upper warning +3% of maximum rating Upper critical +6% of maximum rating Hysteresis •...

  • Page 807: Altitude Correction Factors

    Appendix L: Additional PX3 Information Total residual current: Threshold Default value Upper critical 30mA Hysteresis 15mA 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 808: Data For Btu Calculation

    Appendix L: Additional PX3 Information L1 current unbalance = (L1 - average current) / average current L2 current unbalance = (L2 - average current) / average current L3 current unbalance = (L3 - average current) / average current Determine the maximum absolute value among three lines' current unbalance values.

  • Page 809: Ways To Probe Existing User Profiles

    Appendix L: Additional PX3 Information Model name Maximum power (Watt) 2000 series 3000 series 4000 series 5000 series Ways to Probe Existing User Profiles This section indicates available ways to query existing user accounts on the PX3. • With SNMP v3 activated, you get the "user unknown" error when the user name used to authenticate does not exist.

  • Page 810: Role Of A Dns Server

    Appendix L: Additional PX3 Information Role of a DNS Server As Internet communications are carried out on the basis of IP addresses, appropriate DNS server settings are required for mapping domain names (host names) to corresponding IP addresses, or the PX3 may fail to connect to the given host.
  • Page 811 Appendix L: Additional PX3 Information Symptom Probable cause • Anything below is lost or loose on the master device: Failure to access the master device ▪ Network connection ▪ Power supply • Anything below is disabled on the master device: ▪...
  • Page 812 Appendix L: Additional PX3 Information Symptom Probable cause • One of the following issues occurs on the master device: Failure to access a slave device ▪ Network connection is lost. ▪ Power is lost. ▪ The Ethernet or wireless interface is disabled. •...

  • Page 813: Slave Device Events In The Log

    Appendix L: Additional PX3 Information Tip: To determine which PX3 may be the failure point of network, you may ping each PX3 in the cascading chain, or check the slave-related events in the event log of each PX3. See The Ping Tool (on page 794) and Slave Device Events in the Log...

  • Page 814: The Ping Tool

    Appendix L: Additional PX3 Information Messages for the USB-cascading chain: In the Bridging mode, events regarding connection/disconnection of a downstream slave device via USB is NOT logged. However, in the Port Forwarding mode, whenever the connection or disconnection of a downstream slave device via USB is detected, the PX3 at the USB-A end of the USB cable logs it in the internal log.

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

    Appendix L: Additional PX3 Information Installing the USB-to-Serial Driver (Optional) The PX3 can emulate a USB-to-serial converter over a USB connection. A USB-to-serial driver named "Dominion PX2 Serial Console" is required for Microsoft Windows operating systems. ® ® Download the Windows driver for USB serial console from the Raritan website's Support page (http://www.raritan.com/support/).

  • Page 816: Initial Network Configuration Via Cli

    Appendix L: Additional PX3 Information Note: If the PX3 enters the disaster recovery mode when the USB serial driver is not installed yet, it may be shown as a 'GPS camera' in the Device Manager on the computer connected to it. In Linux: No additional drivers are required, but you must provide the name of the tty device, which can be found in the output of the "dmesg"...
  • Page 817 Appendix L: Additional PX3 Information ▪ To change it, follow onscreen instructions to type your new password. ▪ To ignore it, simply press Enter. The # prompt appears. Type config and press Enter. To configure network settings, type appropriate commands and press Enter.
  • Page 818 Appendix L: Additional PX3 Information • Static IP configuration: To set Use this command network <ipvX> interface <ETH> Static IPv4 or address <ip address> IPv6 address <ip address> = static IP address, with a syntax similar to the example below. ▪...
  • Page 819 Appendix L: Additional PX3 Information To set or Use this command enable network ethernet <ETH> EAP identity eapIdentity <identity> <identity> = your user name for EAP authentication network ethernet <ETH> EAP TLS client eapClientCertificate certificate When prompted to enter the client certificate, open the certificate with a text editor, copy and paste the content into the communications program.
  • Page 820 Appendix L: Additional PX3 Information The content to be copied from the CA certificate does NOT include the first line containing "BEGIN CERTIFICATE" and the final line containing "END CERTIFICATE." If a certificate is installed, configure the following: Whether to Use this command network ethernet <ETH>...
  • Page 821 Appendix L: Additional PX3 Information To set or Use this command enable network wireless authMethod Wireless <method> authentication method <method> = psk or eap network wireless PSK <psk> <psk> = PSK string network wireless Wireless EAP eapOuterAuthentication outer <outer_auth> authentication <outer_auth>...
  • Page 822 Appendix L: Additional PX3 Information To set or Use this command enable network wireless Wireless EAP eapCACertificate CA certificate When prompted to enter the CA certificate, open the certificate with a text editor, copy and paste the content into the communications program. network wireless Radius eapAuthServerName <FQDN>...

  • Page 823: Device-Specific Settings

    Appendix L: Additional PX3 Information • Wireless IPv4 / IPv6 settings: Commands for wireless IP settings are identical to those for wired networking. Just replace the variable <ETH> with the word 'wireless'. The following illustrates a few examples. To set or Use this command enable network ipv4 interface WIRELESS...

  • Page 824: Tls Certificate Chain

    Appendix L: Additional PX3 Information TLS Certificate Chain A TLS server sends out a certificate to any client attempting to connect to it. The receiver determines whether a TLS server can be trusted by verifying that server's certificate, using the certificate (chain) stored on the receiver. Therefore, to successfully connect to a TLS server, you must upload a valid certificate or (partial) certificate chain to the receiver.
  • Page 825 Appendix L: Additional PX3 Information • Certificate A. The self-signed certificate issued by Issuer A. Issuer A is a root CA. The above three certificates form a certificate path, which is called the "certificate chain". Each certificate in the chain is the issuer certificate of the certificate that follows it.
  • Page 826 Appendix L: Additional PX3 Information Warning: The certificate (chain) uploaded to the receiver must always contain the ROOT certificate even though the TLS server provides the root certificate. When uploading a (partial) chain onto the PX3, it means you trust each certificate in the chain to certify the authenticity of certificates a server sends to PX3.

  • Page 827: Illustration - Gmail Smtp Certificate Chain

    Appendix L: Additional PX3 Information It is NOT recommended to upload the server certificate to the receiver except when it is a self-signed certificate. Using self-signed server certificates is also not recommended and may not even work in all cases. Order of the chain in the certificate file: The order of a certificate chain's content in the certificate file uploaded to the receiver must look like the following.
  • Page 828 Appendix L: Additional PX3 Information Information that shows the certificates the SMTP server has is displayed. Certificate chain 0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com i:/C=US/O=Google Inc/CN=Google Internet Authority G2 -----BEGIN CERTIFICATE----- MIIEdjCCA16gAwIBAgIIbzO9vIL2OXcwDQYJKoZIhvcNAQELBQAwSTELMAkGA1UE YHKKJH96sSNC+6dLpOOoRritL5z+jn2WFLcQkL2mRoWQi6pYTzPyXB4D -----END CERTIFICATE----- 1 s:/C=US/O=Google Inc/CN=Google Internet Authority G2 i:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA -----BEGIN CERTIFICATE----- MIIEKDCCAxCgAwIBAgIQAQAhJYiw+lmnd+8Fe2Yn3zANBgkqhkiG9w0BAQsFADBC MqO5tzHpCvX2HzLc...
  • Page 829 Appendix L: Additional PX3 Information ▪ Google Internet Authority G2 ▪ GeoTrust Global CA ▪ Equifax Secure Certificate Authority ▪ Each certificate's content is located between the line of "BEGIN CERTIFICATE" and the line of "END CERTIFICATE". ▪ The topmost certificate is the server certificate. The section titled "Server certificate"...

  • Page 830: Browsing Through The Online Help

    Appendix L: Additional PX3 Information Note: If your SMTP server requires the upload of a certificate file comprising multiple certificates, make sure the order of these certificates is correct in the file. See What is a Certificate Chain (on page 804). IMPORTANT NOTE: If your SMTP server provides a full certificate chain, you should be suspicious whether any attacker fakes the certificate chain and doubt whether the root...
  • Page 831 Appendix L: Additional PX3 Information To have the left pane show the list of topics, click the Contents tab at the bottom. To show the Index page, click the Index tab. To email any URL link to the currently selected topic to any person, click the "Email this page"...

  • Page 832: Appendix M Integration

    Appendix M Integration The PX3 can work with certain Raritan or third-party products to provide diverse power solutions. In This Chapter Dominion KX II / III Configuration ..............812 Dominion KSX II, SX or SX II Configuration ............817 Power IQ Configuration ..................822 dcTrack......................
  • Page 833 Appendix M: Integration Connecting a PX PDU Raritan PX series rack PDUs (power strips) are connected to the Dominion device using the D2CIM-PWR CIM. To connect the rack PDU: Connect the male RJ-45 of the D2CIM-PWR to the following female RJ-45 connector of the rack PDU.
  • Page 834 Appendix M: Integration D2CIM-PWR to rack PDU connection D2CIM-PWR to KX III target device port via Cat5 cable Naming the Rack PDU (Port Page for Power Strips) Note: PX rack PDUs (power strips) can be named in the PX as well as in the KX III.
  • Page 835 Appendix M: Integration Click OK.

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

    Appendix M: Integration Associating Outlets with Target Devices The Port page opens when you click on a port on the Port Configuration page. If an outlet is connected to the same server that the port is connected to, a power association can be made with the target device. A server can have up to four power plugs and you can associate a different rack PDU (power strip) with each.

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

    Appendix M: Integration Click OK on the Power Off confirmation dialog. The outlet will be turned off and its state will be displayed as 'off'. To cycle the power of an outlet: Click Cycle next to the outlet you want to cycle. The Power Cycle Port dialog opens.

  • Page 838: Dominion Sx And Sx Ii

    Appendix M: Integration Attach an AC power cord to the target server and an available rack PDU outlet. Connect the rack PDU to an AC power source. Power on the KSX II device. Important: When using CC-SG, the power ports should be inactive before attaching rack PDUs that were swapped between the power ports.
  • Page 839 Appendix M: Integration Dominion SX II The way to use Dominion SX II to configure and control a Raritan PDU is similar to using Dominion KX III, but the connection method is different from KX III. Note: If using a CSCSPCS-1 cable for the connection, it must be "Rev.0C". If using a CSCSPCS-10 cable, it must be "Rev.0D".
  • Page 840 Appendix M: Integration Dominion SX Configuring a PX3 on Dominion SX Choose Setup > Power Strip Configuration. Click Add. The Power Strip Configuration screen appears. Type a name and description in the Name and Description fields. Select the number of outlets from the Number of Outlets drop-down menu.
  • Page 841 Appendix M: Integration Power Control Choose Power Control > Power Strip Power Control. The Outlet Control screen appears. Check the box of outlet number you wish to control, and click On/Off buttons to power on/off the selected outlet(s). A confirmation message appears, indicating successful operation.

  • Page 842: Power Iq Configuration

    Appendix M: Integration Checking Power Strip Status Choose Power Control > Power Strip Status. A status box appears, displaying details of the controlled PX3, 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 843: Dctrack

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

  • Page 844: Asset Management Strips And Dctrack

    Appendix M: Integration Asset Management Strips and dcTrack If any asset strips are connected to the PX3, the PX3 can transmit their information to Sunbird's dcTrack. All you have to do is to add the PX3 to dcTrack, and also add each IT item where an asset tag is attached to dcTrack. Note: For instructions on connecting asset strips, see Connecting Asset Management Strips...

  • Page 845: Index

    Index Assertion Timeout Example for Temperature Sensors • 781 Asset Management Commands • 606 +12V Power Supply Sensor • 44, 129, 182, 186 Asset Management Strips and dcTrack • 824 Asset Management Tag List • 375, 378 Asset Management Tag Log • 375, 381 1U and 2U Port Locations •...
  • Page 846 Index Cascading All Devices via USB • 35, 40, 118 Commands for Environmental Sensors • 596 Cascading Multiple PX3 Devices for Sharing Commands for Inlet Pole Sensors • 592, 702 Ethernet Connectivity • 22, 24, 34, 256, 270, Commands for Inlet Sensors • 589, 702 Commands for Overcurrent Protector Sensors •...
  • Page 847 Index Connecting a Schroff LHX/SHX Heat Exchanger • Dashboard - Inlet I1 • 172, 173, 187 80, 234 Dashboard - OCP • 172, 175 Connecting an Analog Modem • 79, 459 Data Encryption in 'config.txt' • 648, 649, 652 Connecting an External Beeper • 80, 233 Data for BTU Calculation •...
  • Page 848 Index Dominion KX II / III Configuration • 239, 812 Enabling or Disabling SNMP v3 • 525 Dominion SX • 820 Enabling or Disabling SSH • 523 Dominion SX and SX II • 818 Enabling or Disabling Strong Passwords • 544 Dominion SX II •...
  • Page 849 Index Example 1 - Combination of ETH1's Activation, Configuration Method and IP • 615 Example 1 - Creating a User Profile • 567 FAQs • 83 Example 1 - Environmental Sensor Naming • 587 Feature Port • 168, 223, 225, 233, 235, 239 Example 1 - IPv4 Firewall Control Configuration •...
  • Page 850 Index Individual OCP Pages • 197 Logout • 163 Individual Outlet Pages • 192, 193 Lowercase Character Requirement • 544 Individual Sensor/Actuator Pages • 136, 176, 203, Lua Scripts • 252, 351, 389 205, 206, 207, 217, 223 Initial Installation and Configuration • 21 Initial Network Configuration via CLI •...
  • Page 851 Index Mounting Zero U Models Using Button Mount • 7 Mounting Zero U Models Using Claw-Foot Brackets • 8 Package Contents • 1, 3 Mounting Zero U Models Using L-Brackets • 6 Pairwise Outlet Groups • 108 Mounting Zero U Models Using L-Brackets and Panel Components •...
  • Page 852 Index Restrictions of Port-Forwarding Connections • 38, 41, 793 Retrieving Previous Commands • 460, 461, 622 Rack Unit Configuration • 610 Retrieving Software Packages Information • 397, Rack Unit Settings of an Asset Strip • 485 Rackmount Safety Guidelines • 5 Returning User Group Information •...
  • Page 853 Index Serial Port Configuration Commands • 613 Setting the IPv4 Preferred Host Name • 499 Serial Port Settings • 484 Setting the IPv6 Address • 504 Serial RS-232 • 634, 720 Setting the IPv6 Configuration Mode • 502 Server Reachability Configuration Commands • Setting the IPv6 Gateway •...
  • Page 854 Index SNMPv2c Notifications • 282, 448 SNMPv3 Notifications • 282, 448, 449 Sorting a List • 170, 176, 192, 195, 203, 227, 245, Testing the Network Connectivity • 621, 794 248, 265, 363, 403, 411 TFTP Requirements • 656, 657 Special Character Requirement •...
  • Page 855 Index Using the Command Line Interface • 186, 279, 456, 685, 700 Using the Reset Button • 684 Using the Web Interface • 159 Vendor-Specific Attributes • 736, 755 Viewing and Managing Locally-Saved Snapshots • 340, 423, 432, 435 Viewing Connected Users • 396, 403, 430 Viewing Firmware Update History •...

Table of Contents