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

LEGRAND Raritan PX3-4000 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
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
Table of Contents

Advertisement

Quick Links

Download this manual
PX3-3000/4000/5000 Series
User Guide
Xerus
Firmware v3.5.10
™
Copyright © 2019 Raritan, Inc.
PX3-1G-v3.5.10-E
May 2019
255-80-0035-00

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for LEGRAND Raritan PX3-4000 Series

Summary of Contents for LEGRAND Raritan PX3-4000 Series

  • Page 1 PX3-3000/4000/5000 Series User Guide Xerus Firmware v3.5.10 ™ Copyright © 2019 Raritan, Inc. PX3-1G-v3.5.10-E May 2019 255-80-0035-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. 3.
  • 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 xviii   What's New in the PX3 User Guide   Chapter 1 Introduction     Product Models..........................1   Package Contents..........................1   Zero U Products ........................2   1U Products..........................2  ...
  • 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  ...
  • Page 8 Contents   Connecting a Logitech Webcam..................... 82   Connecting a GSM Modem ......................83   Connecting an Analog Modem ....................... 84   Connecting an External Beeper ..................... 84   Connecting a Schroff LHX/SHX Heat Exchanger ................85   Connecting a Modbus RTU Device or Bus..................85 Chapter 5 Introduction to PDU Components  ...
  • Page 9 Contents   Options for Outlet State on Startup ................... 178   Initialization Delay Use Cases.................... 179   Inrush Current and Inrush Guard Delay................179   Time Units .......................... 180   Setting Thresholds for Total Active Energy or Power ............180  ...
  • Page 10 Contents   Setting Default Measurement Units .................. 283   Device Settings ..........................284   Configuring Network Settings ................... 286   Configuring Network Services................... 314   Configuring Security Settings .................... 325   Setting the Date and Time ....................349   Event Rules and Actions ....................353  ...
  • Page 11 Contents   A Note about Enabling Thresholds ..................510 Chapter 8 Using the Command Line Interface     About the Interface ........................512   Logging in to CLI........................... 512   With HyperTerminal......................512   With SSH or Telnet......................513   With an Analog Modem ......................
  • Page 12 Contents   Command History ......................549   Reliability Data ........................549   Reliability Error Log......................549   Reliability Hardware Failures .................... 549   Examples..........................550   Clearing Information ........................552   Clearing Event Log......................552   Clearing Diagnostic Log for Network Connections............553  ...
  • Page 13 Contents   Unblocking a User ........................705   Resetting the PX3 ......................... 705   Restarting the PDU ......................706   Resetting Active Energy Readings..................706   Resetting to Factory Defaults .................... 707   Network Troubleshooting......................707   Entering Diagnostic Mode....................708  ...
  • Page 14 Contents Appendix A Specifications     Maximum Ambient Operating Temperature................741   Serial RS-232 "RJ-45" Port Pinouts..................... 741   Sensor RJ-45 Port Pinouts......................741   Feature RJ-45 Port Pinouts ......................742   Expansion RJ-45 Port Pinouts ..................... 743 Appendix B Equipment Setup Worksheet  ...
  • Page 15 Contents Appendix F Resetting to Factory Defaults     Using the Reset Button ........................ 793   Using the CLI Command ......................794 Appendix G PX3 Models with Residual Current Monitoring     RCM Current Sensor ........................797   RCM State Sensor......................... 798  ...
  • Page 16 Contents   Serial RS-232 "DB9" Port Pinouts ....................836 Appendix I LDAP Configuration Illustration     Step A. Determine User Accounts and Roles ................837   Step B. Configure User Groups on the AD Server ............... 838   Step C. Configure LDAP Authentication on the PX3 ..............839  ...
  • Page 17 Contents   Default Voltage and Current Thresholds ..................901   Altitude Correction Factors......................903   Unbalanced Current Calculation....................904   Data for BTU Calculation......................905   Ways to Probe Existing User Profiles ..................906   Raritan Training Website......................906   Role of a DNS Server........................
  • Page 18 Applicable Models This User Guide is applicable to the following PDU Generation.  PDU Generation (3000/4000/5000 series) PX3 with iX7 ™ 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 19: Product Models

    Applicable Models Comparison between PX2, PX3, PXC and PXO series: 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...
  • Page 20 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 459). The following sections have changed or information has been added to the PX3 User Guide based on enhancements and changes to the equipment and/or user documentation.
  • Page 21 What's New in the PX3 User Guide Changing Storage Settings (on page 488) SmartLock (on page 494) Card Readers (on page 499) Network Connections Diagnostic Log (on page 547) Clearing Diagnostic Log for Network Connections (on page 553) Setting IPv4 Static Routes (on page 566) Setting IPv6 Static Routes (on page 570)

  • Page 22: Package Contents

    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 23: Zero U Products

    Chapter 1: Introduction Zero U Products  One PX3  Screws, brackets and/or buttons for Zero U  Cable retention clips for the inlet (for some models only)  Cable retention clips for outlets (for some models only) 1U Products ...

  • Page 24: Before You Begin

    Chapter 1: Introduction Note: Configuration by connecting the PX3 to a computer using a network cable is an application of this scenario. See Connecting the (on page 31). PX3 to a Computer  The PX3 previously obtained an IP address from the DHCP server, but the lease of this IP address has expired, and the lease cannot be renewed, or no new IP address is available.

  • Page 25: Preparing The Installation Site

    Chapter 1: Introduction 4. Verify that all circuit breakers on the PX3 are set to ON. If not, turn them ON. Or make sure that all fuses are inserted and seated properly. If there are any fuse covers, ensure that they are closed. Note: Not all models have overcurrent protectors.

  • Page 26: 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 27: Mounting Zero U Models Using L-Brackets

    Chapter 2: Rackmount, Inlet and Outlet Connections  Connect equipment to the supply circuit carefully to avoid overloading circuits.  Ground all equipment properly, especially supply connections, to the branch circuit. Mounting Zero U Models Using L-Brackets Circuit Breaker If your PDU has circuit breakers implemented, read Orientation Limitation (on page 5) before mounting it.
  • Page 28 Chapter 2: Rackmount, Inlet and Outlet Connections 3. Align the L-brackets with the baseplates so that the five screw-holes on the baseplates line up through the L-bracket's slots. The rackmount side of brackets should face either the left or right side of the PX3 device.

  • Page 29: Mounting Zero U Models Using Button Mount

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

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

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

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

  • Page 33: Mounting 1U Or 2U Models

    Chapter 2: Rackmount, Inlet and Outlet Connections 4. Screw a button in the screw hole near the top. The recommended torque for the button is 1.96 N·m (20 kgf·cm). 5. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously.
  • Page 34 Chapter 2: Rackmount, Inlet and Outlet Connections 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners.

  • Page 35: 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 36: Disconnecting A Px3 Locking Line Cord

    Chapter 2: Rackmount, Inlet and Outlet Connections To connect a cord with slide release buttons: Simply plug the cord's connector into the PDU's inlet. Number Item Slide release buttons Disconnecting a For information on removing the locking line cord, see PX3 Locking Line Cord (on page 15).

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

    Chapter 2: Rackmount, Inlet and Outlet Connections To disconnect a line cord with slide release buttons: Push both slide release buttons toward the cord while unplugging this cord. 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.

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

    Chapter 2: Rackmount, Inlet and Outlet Connections Zero U models 1U/2U models 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 39: Locking Outlets And Cords

    Chapter 2: Rackmount, Inlet and Outlet Connections 2. Install the cable retention clip by inserting two ends of the clip into the tiny holes. 3. Plug the power cord into the outlet, and press the clip toward the power cord until it holds the cord firmly. The clip's central part holding the plug should face downwards toward the ground, like an inverted "U".

  • Page 40: Securelock™ Outlets And Cords

    Chapter 2: Rackmount, Inlet and Outlet Connections SecureLock™ Outlets and Cords SecureLock is an innovative mechanism designed by Raritan, which ™ securely holds C14 or C20 plugs that are plugged into Raritan PDUs in place. This method requires the following two components: ...

  • Page 41: Button-Type Locking Outlets

    Chapter 2: Rackmount, Inlet and Outlet Connections To remove a SecureLock power cord from the PDU: ™ 1. Press and hold down the two latches on the cord's plug as illustrated in the diagram below. 2. Unplug the cord now. Button-Type Locking Outlets Such outlets do not require any special power cords to achieve the locking purpose.

  • Page 42: 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................... 25 Bulk Configuration Methods ..............33 Cascading Multiple PX3 Devices for Sharing Ethernet Connectivity..

  • Page 43: 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 44: Usb Wireless Lan Adapters

    Chapter 3: Initial Installation and Configuration  Plug a supported USB wireless LAN adapter into the USB-A port on your PX3.  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.

  • Page 45: Dual Ethernet Connection

    Chapter 3: Initial Installation and Configuration Dual Ethernet Connection One PX3 device has two Ethernet (LAN) ports:  green ETH 10/100/1000 (marked in ) supports up to 1000 Mbps. This is "ETH1".  ETH 10/100 (marked in white ) supports up to 100 Mbps. This is "ETH2".

  • Page 46: Configuring The Px3

    Chapter 3: Initial Installation and Configuration Configuring the PX3 You can initially configure the PX3 via one of the following:  A TCP/IP network that supports DHCP  A mobile device with PDView installed  A computer physically connected to the PX3 Configuration via a DHCP-enabled network: Connecting the PX3 1.

  • Page 47: Connecting A Mobile Device To Px3

    Chapter 3: Initial Installation and Configuration Connecting a Mobile Device to PX3 Raritan's PDView is a free app that turns your iOS or Android mobile device into a local display for PX3. PDView is especially helpful when your PX3 is not connected to the network but you need to check the PX3 status, retrieve its information, or change its settings.
  • Page 48 Chapter 3: Initial Installation and Configuration  Android : USB-B port Step C: Launch PDView to access the PX3 1. Launch the PDView app from your mobile device. Below illustrate iPad's PDView screens. a. The "Disconnected" message displays first when PDView has not detected the PX3 yet.
  • Page 49 Chapter 3: Initial Installation and Configuration Note: PDView also shows the 'Disconnected' status during the firmware upgrade. If so, wait until the firmware upgrade finishes. b. The PDView shows the "Connected" message when it detects the connected PX3. 2. If the factory-default user credentials "admin/raritan" remain unchanged, PDView automatically logs in to the web interface of PX3.
  • Page 50 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) 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 51 Per default, three administrator user credentials are pre-configured for three companies' products:  Raritan  Legrand  ServerTech (Server Technology) 5. Modify existing user credentials or type new ones, and tap Save.  The pre-configured admin credentials can be removed or...

  • Page 52: 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 ports  USB-B port  RS-232 serial port (RJ-45) Note that the port locations on your models may differ. ...
  • Page 53 Chapter 3: Initial Installation and Configuration USB connection: 1. A USB-to-serial driver is required in Windows . Install this driver ® Installing the USB-to-Serial before connecting the USB cable. See Driver (Optional) (on page 911). 2. Connect a USB cable between a computer's USB-A port and the USB-B port of PX3.

  • Page 54: 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 (on page 888).

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

    Chapter 3: Initial Installation and Configuration SCP or PSCP command:  Requirement : Two files are required -- one is a configuration file in TXT and the other is a devices list file in CSV.  Procedure : Upload both files to all of PX3 devices one by one, using the appropriate SCP or PSCP command.
  • Page 56 Chapter 3: Initial Installation and Configuration You can have multiple PX3 devices share one Ethernet connection by cascading them via one of the interfaces below:  USB interface  Ethernet interface The first one in the cascading chain is the master device and all the other are slave devices.
  • Page 57 Chapter 3: Initial Installation and Configuration  Do NOT connect slave devices 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 Cascading software settings of all devices in the chain.

  • Page 58: Cascading All Devices Via Usb

    Chapter 3: Initial Installation and Configuration Cascading All Devices via USB You must set the cascading mode before establishing the chain. See Setting the Cascading Mode (on page 304). Any certified USB 2.0 cable up to 5 meters (16 feet) long can be used. Both cascading modes support a maximum of 16 devices in a chain.
  • Page 59 Chapter 3: Initial Installation and Configuration Number Device role Slave 3 To cascade PX3 devices via USB: 1. Make sure all Raritan devices are running firmware version 3.3.10 or later. 2. Choose the appropriate one as the master device.  When the Port Forwarding mode over "wireless LAN"...
  • Page 60 Chapter 3: Initial Installation and Configuration  Port Forwarding mode: Only the master device's network settings should be configured. 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 61: 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 62 Chapter 3: Initial Installation and Configuration Number Device role Master device Slave 1 Slave 2 Slave 3...
  • Page 63 Chapter 3: Initial Installation and Configuration Cascading All Devices via USB For instructions on USB cascading, see (on page 37). Suggestions for extended cascading:  Ethernet cascading is recommended because of the longer distance, lower latency and more reliable connection it supports. ...

  • Page 64: Restrictions Of Port-Forwarding Connections

    Chapter 3: Initial Installation and Configuration  Bridging mode: Each cascaded device has its own network settings. For example, you can have some devices use DHCP-assigned IP addresses and the others use static IP addresses.  Port Forwarding mode: Only the master device's network settings should be configured.
  • Page 65 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 66: 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 67: 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 68: Power-Sharing Configurations And Restrictions

    Chapter 3: Initial Installation and Configuration 2. Connect one end to a PX3 device's EXPANSION port, and the other end to another one's EXPANSION port.  Note that the EXPANSION port location on your PX3 may differ from the following images. Power-Sharing Configurations and Restrictions When either PX3 PDU enters the power-sharing mode, BOTH PDUs involved in the power-sharing connection support "less"...

  • Page 69: 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 limitations for connecting Raritan's DPX or DPX2 environmental sensor packages to an iX7 PDU in the power-sharing ™...
  • Page 70 Chapter 3: Initial Installation and Configuration  A maximum of 2 door handles connected to a maximum of one DX2-DH2C2 or one DX-PD2C5 package are supported.  All of the 2 door handles must be controlled by the same PDU so that you can have "only one"...

  • Page 71: 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 ......50 Connecting Asset Management Strips............71 Connecting a Logitech Webcam..............82 Connecting a GSM Modem ................

  • Page 72: 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 73 Chapter 4: Connecting External Equipment (Optional) Connect DX2 to the PX3: 1. Connect a standard network patch cable (CAT5e or higher) to either RJ-45 port on a DX2 sensor package. 2. If you want to cascade DX2 packages, get an additional standard network patch cable (CAT5e or higher) and then: a.

  • Page 74: 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 Support page Online Help) on Raritan website's http://www.raritan.com/support/ You can cascade up to 12 DX sensor packages.

  • Page 75: Dpx3 Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) a. Plug one end of the cable into the remaining RJ-45 port on the prior DX package. b. Plug the other end into either RJ-45 port on an additional DX package. Repeat the same steps to cascade more DX packages. Exception: You CANNOT cascade DX-PD2C5 sensor packages.

  • Page 76: Dpx3 Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) Numbers Components LED for indicating the sensor status. To connect DPX3 to the PX3: 1. Connect a standard network patch cable (CAT5e or higher) to either RJ-45 port on the DPX3 sensor package. 2. If you want to cascade DPX3 sensor packages, get an additional standard network patch cable (CAT5e or higher) and then: a.

  • Page 77: 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 Support page...
  • Page 78 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 79 Chapter 4: Connecting External Equipment (Optional) b. Connect the adapter's RJ-45 connector to the RJ-45 SENSOR port of the PX3. OR you can directly connect the DPX2 sensor package to a DX sensor Connecting a chain without using any RJ-12 to RJ-45 adapter. See DPX2 Sensor Package to DX2, DX or DPX3 (on page 58).

  • Page 80: Dpx Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) When connecting a DPX2 sensor package containing "one" DPX2 sensor: A maximum of eleven DX sensor packages can be cascaded because 12-1=11. DPX Sensor Packages Most DPX sensor packages come with a factory-installed sensor cable, whose sensor connector is RJ-12.
  • Page 81 Chapter 4: Connecting External Equipment (Optional) 2. Get an RJ-12 to RJ-45 adapter. Connect the adapter's RJ-12 connector to the other end of the phone cable. 3. Connect this adapter's RJ-45 connector to the RJ-45 SENSOR port on the PX3. 4.
  • Page 82 Chapter 4: Connecting External Equipment (Optional) b. Get an RJ-12 to RJ-45 adapter. Connect this adapter's RJ-12 connector to the other end of the phone cable. c. Connect this adapter's RJ-45 connector to the PDU's RJ-45 SENSOR port. 2. Connect DPX sensor packages to any of the four OUT ports on the hub.
  • Page 83 Chapter 4: Connecting External Equipment (Optional) 2. The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports. 3. Repeat the above steps if there are additional SENSOR ports on your PX3.
  • Page 84 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 85: 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 86 Chapter 4: Connecting External Equipment (Optional) This diagram illustrates a configuration with a sensor hub connected. A standard network cable DPX3-ENVHUB4 sensor hub Any Raritan sensor packages...

  • Page 87: Mixing Diverse Sensor Types

    Chapter 4: Connecting External Equipment (Optional) 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. When mixing different sensor types, remember that the PX3 only supports a maximum of 32 sensors/actuators.
  • Page 88 Chapter 4: Connecting External Equipment (Optional) Diverse combinations via the DPX3-ENVHUB4 sensor hub:  You must use the DPX3-ENVHUB4 sensor hub instead of the old DPX-ENVHUB4 sensor hub. Each port on the hub supports any of the following:  One individual DX2 sensor package ...
  • Page 89 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 90 Chapter 4: Connecting External Equipment (Optional)
  • Page 91 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 92: 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 Connecting a DPX2 Sensor Package to DX2, DX or chain if needed. See DPX3 (on page 58). 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 93: 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 94 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. 2.

  • Page 95: 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.
  • Page 96 Chapter 4: Connecting External Equipment (Optional)  Connect one end of the cable to the RJ-45 connector on the MASTER asset strip.  Connect the other end of the cable to the FEATURE port on the PX3 device. 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 97: 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 98 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: 1.
  • Page 99 Chapter 4: Connecting External Equipment (Optional) a. Affix the adhesive part of the asset tag to one side of a blade server through the tag's tape. b. Plug the tag connector of the asset tag into a tag port on the blade extension strip.

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

    Chapter 4: Connecting External Equipment (Optional) Connecting Composite Asset Strips (AMS-Mx-Z) A composite asset strip is named AMS-Mx-Z, where x is a number, such as AMS-M2-Z or AMS-M3-Z. It is a type of asset strip that functions the same as regular MASTER asset strips except for the following differences: ...
  • Page 101 Chapter 4: Connecting External Equipment (Optional) c. Connect the other end of the cable to the RJ-45 connector labeled "Input" on the secondary composite asset strip. d. Repeat the same steps to connect more composite asset strips. Daisy-Chain Limitations of Composite Asset Strips page 81) for the maximum number of composite asset strips supported per chain.
  • Page 102 Chapter 4: Connecting External Equipment (Optional) Daisy-Chain Limitations of Composite Asset Strips There are some limitations when daisy chaining composite asset strips "AMS-Mx-Z," where x is a number.  The maximum cable length between composite asset strips is 2 meters, but the total cable length cannot exceed 10 meters. ...

  • Page 103: Connecting A Logitech Webcam

    Chapter 4: Connecting External Equipment (Optional) Connecting a Logitech Webcam Connect webcams to PX3 in order to view videos or snapshots of the webcam's surrounding area. The following USB Video Class (UVC) compliant webcam is supported:  Logitech HD pro C920 ®...

  • Page 104: 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  EHS6 Available Actions (on page 375) for more information on SMS messages.

  • Page 105: Connecting An Analog Modem

    Chapter 4: Connecting External Equipment (Optional) Connecting an Analog Modem The PX3 supports remote dial-in communications to access the CLI through an analog modem. This dial-in feature provides an additional alternative to access the PX3 when the LAN access is not available. To dial in to the PX3, the remote computer must have a modem connected and dial the correct phone number.

  • Page 106: Connecting A Schroff Lhx/Shx Heat Exchanger

    Chapter 4: Connecting External Equipment (Optional) The beeper can be located at a distance up to 330 feet (100 m) away from the PX3. Connecting a Schroff LHX/SHX Heat Exchanger To remotely monitor and administer the Schroff LHX-20, LHX-40 and ®...
  • Page 107 Chapter 4: Connecting External Equipment (Optional)  The Modbus RTU devices on the bus are identified with their Modbus RTU addresses using the Modbus unit identifier addresses in the Modbus TCP protocol. If the Modbus TCP client does not support unit identifier addressing, Changing Modbus Settings refer to (on page 321).

  • Page 108: Chapter 5 Introduction To Pdu Components

    Chapter 5 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 109: Inlet

    Chapter 5: 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 110: Outlets

    Chapter 5: Introduction to PDU Components Inlet on the side Inlet on the top Outlets The total number of outlets varies from model to model. PX3-3000 Series These models are NOT outlet-switching capable so all outlets are always in the ON state. Outlet LEDs are not available.

  • Page 111: Connection Ports

    Chapter 5: Introduction to PDU Components LED state Outlet status What it means The outlet is turned off and no power is available. Not lit Powered OFF OR the control circuitry's power supply is broken. ON and LIVE LIVE power. The outlet is on and power is available. The current flowing through the outlet is greater Red flashing ON and LIVE...
  • Page 112 Chapter 5: Introduction to PDU Components  CONSOLE/MODEM port x 1 (blue)  Sensor port x 1 (yellow)  USB-A port x 2  USB-B port x 1  Feature port x 1 (red)  Ethernet port x 2 (green and white) Note: ETH 10/100/1000 (marked in ) supports up to 1000 Mbps.
  • Page 113 Chapter 5: Introduction to PDU Components Port Used for... FEATURE Connection to one of the following devices:  A Raritan access product, such as Dominion KX III KVM switch, with the use of a power CIM.  A Schroff LHX-20, SHX-30 or LHX-40 device, using an RJ-45 to ®...

  • Page 114: Dot-Matrix Lcd Display

    Chapter 5: Introduction to PDU Components Port Used for... ETH 10/100/1000, PX3 has two Ethernet ports.  green ETH 10/100 ETH 10/100/1000 (marked in ) supports up to 1000 Mbps. This is "ETH1".  white ETH 10/100 (marked in ) supports up to 100 Mbps. This is "ETH2".
  • Page 115 Chapter 5: 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 116 Chapter 5: 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 117 Chapter 5: 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 118 Chapter 5: 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 119 Chapter 5: Introduction to PDU Components Main Menu The Main Menu contains 8 to 10 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 120 Chapter 5: Introduction to PDU Components Menu command Function Indicates all alerted sensors, if any. See Alerts (on page 100). Alerts Shows the internal beeper's state, and, if it is on, the reason for turning If your PDU has multiple inlets, this menu item also shows the total active power and total active energy.
  • Page 121 Chapter 5: Introduction to PDU Components Alerts The "Alerts" menu command shows a list of the following alerted sensors, including both internal and external sensors.  Any numeric sensor that enters the warning or critical range if the thresholds have been enabled ...
  • Page 122 Chapter 5: Introduction to PDU Components Number Description The time the alarm occurred. If the alarm occurred at least two times, then more information is shown.  Number of alarms  The first occurrence time  The last occurrence time Alerted sensor names.
  • Page 123 Chapter 5: Introduction to PDU Components a. Press to view detailed information of the alarm. b. (Optional) If the alarm occurred more than one time, the numbers of current page and total pages are shown in the top-right corner, similar to the above diagram. Press to view the information of other occurrences.
  • Page 124 Chapter 5: 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 125 Chapter 5: Introduction to PDU Components By default the energy pulsing is turned off. DO NOT enable this feature unless you have to use it. Note: This feature, once enabled, blink all outlet LEDs proportional to the energy consumption. It can be used as a simple interface in certification labs where they use an optical sensor to count the number of pulses and compare it to the energy reading of a reference meter.
  • Page 126 Chapter 5: Introduction to PDU Components 4. Press to show the status of the 12V power supply to the +12V Power Supply controller. For details on this sensor, see Sensor (on page 182). 5. If your PX3 has more than one inlet, press to show the information of total active power (W) and total active energy (Wh).
  • Page 127 Chapter 5: 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 (on page 437).
  • Page 128 Chapter 5: Introduction to PDU Components 3. Press to select Yes and then press 4. 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 129 Chapter 5: Introduction to PDU Components 2. The first page shows the inlet's active power (W), apparent power (VA), power factor (PF), and active energy (Wh). 3. 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).
  • Page 130 Chapter 5: Introduction to PDU Components OCPs If your model has more overcurrent protectors (OCPs) than the LCD display can show at a time, a page number appears in the top-right corner of the display. Otherwise, no page numbers are available. To show the overcurrent protector information: 1.
  • Page 131 Chapter 5: Introduction to PDU Components Outlets With the front panel display, you can do the following for outlets:  Show each outlet's information.  Turn on, off or power cycle an individual outlet if your PX3 is outlet-switching capable. To do this, you must first enable the front panel outlet control function.
  • Page 132 Chapter 5: Introduction to PDU Components 3. Press to select an outlet, and press  If the desired outlet is not visible, press to scroll up or down. 4. The LCD display shows the selected outlet's power state, active power (W), apparent power (VA), power factor (PF) and active energy (Wh).
  • Page 133 Chapter 5: Introduction to PDU Components 6. To return to the Main Menu, press several times until the Main Menu is shown. Power Control This section applies to outlet-switching capable models only. The front panel outlet control must be enabled for performing this power Front Panel control function.
  • Page 134 Chapter 5: Introduction to PDU Components If so, the word "Off" replaces the current value. 3. Press to select an outlet, and press If the desired outlet is not visible, press to scroll up or down. 4. The LCD display shows the selected outlet's information. For details, Showing an Outlet's Information (on page 110).
  • Page 135 Chapter 5: Introduction to PDU Components Note: The submenu is not available when the front panel outlet control is disabled. If so, a message "Front-panel outlet control is disabled" is displayed.  When the selected outlet has been turned off, 'Switch On' replaces the option of 'Switch Off'.
  • Page 136 Chapter 5: Introduction to PDU Components Outlet Groups You can do the following on the front panel display:  Show each outlet group's information, including each member outlet of a group.  Turn on, off or power cycle an individual outlet group if your PX3 is outlet-switching capable.
  • Page 137 Chapter 5: Introduction to PDU Components  Each group's active power value The currently-selected outlet group's number and total of outlet groups are indicated in the top-right corner of the display, such as "1/4" in the above diagram.  A red circle indicates that all outlets of the group are powered ...
  • Page 138 Chapter 5: Introduction to PDU Components Note: In the following diagrams, N represents the selected outlet group's index number. The rightmost number in the title bar represents this group's total pages. 5. To check the status of each member outlet of the group, press 6.
  • Page 139 Chapter 5: Introduction to PDU Components Group's Power Control This section applies to outlet-switching capable models only. The front panel outlet control must be enabled for performing this power Front Panel control function. The default is to disable this function. See Settings (on page 437).
  • Page 140 Chapter 5: Introduction to PDU Components Note: In the following diagrams, N represents the selected outlet group's index number. The rightmost number in the title bar represents this group's total pages. 3. Press to go to the power control page. A submenu similar to the following diagram appears.
  • Page 141 Chapter 5: Introduction to PDU Components  Cycle: Power cycle the outlet group. 5. A confirmation message appears. Press to select Yes or No, and then press  Yes: Confirm the operation.  No: Abort the operation. 6. Verify that the selected outlet group is switched on or off, depending on the option you selected in the above step.
  • Page 142 Chapter 5: Introduction to PDU Components Operating The top and bottom bars also turn yellow or red. See the Dot-Matrix LCD Display (on page 97). Number Description Sensor or actuator names. Sensor or actuator states as listed below. For further information, see Sensor/Actuator States (on page 240).
  • Page 143 Chapter 5: Introduction to PDU Components 3. To view an environmental sensor or actuator's detailed information, press to select that sensor or actuator, and press A screen similar to the following is shown. Number Description The ID number assigned to this sensor or actuator. ...
  • Page 144 Chapter 5: Introduction to PDU Components Number Description Depending on the sensor type, any of the following information is displayed:  State of a state sensor: Normal Alarmed Open Closed  State of an actuator:  Reading of a numeric sensor. X, Y, and Z coordinates which you specify for this sensor or actuator.
  • Page 145 Chapter 5: Introduction to PDU Components 2. Press to turn on or off the actuator. A confirmation message similar to the following is shown. 3. Press to select Yes or No, and then press 4. Verify that the actuator status shown on the LCD display has been changed.
  • Page 146 Chapter 5: 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. 3. Press to show this asset strip's details, including:  State - strip status.
  • Page 147 Chapter 5: Introduction to PDU Components  Orientation - the strip's orientation. 4. 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 148 Chapter 5: 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 Asset Strip selected numbering mode. See (on page 256).  The index number in parentheses: The physical port number printed on the asset strip.
  • Page 149 Chapter 5: Introduction to PDU Components Number Description The information of the selected blade extension strip, including:  Rack unit number  Index number in parentheses  Current LED color of the tag port where it is connected  Extension strip's ID number (barcode) The slot number of each asset tag The connected asset tag's ID number (barcode).
  • Page 150 Chapter 5: Introduction to PDU Components Number Description Device ratings, including rated voltage, frequency, current and power. 3. Press to show the Network Common page. Number Description DNS servers. Default gateways. 4. Press to show the Network Cascading page.
  • Page 151 Chapter 5: 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 304).  Network Bridge Enabled: This device's cascading mode is set to Bridging. Its IP address is also displayed on this page.
  • Page 152 Chapter 5: 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 153 Chapter 5: Introduction to PDU Components Number Description IPv4/IPv6 network information, including:  Network configuration: DHCP (or Automatic), or Static. Static represents Static IP.  IP address.  Prefix length, such as "/24". Note: If you disable any Ethernet interface, a message 'Interface Disabled' is shown.
  • Page 154 Chapter 5: 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 155 Chapter 5: Introduction to PDU Components  If you want to return to the factory default, also repeat step 1 until the LCD shows "Automatic Orientation". 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 156 Chapter 5: 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 157 Chapter 5: Introduction to PDU Components Available operations:  For the notice listing alerted sensors only, press to view a list Alerts of all alerted sensors. See (on page 100).  For the notice where at least an alarm is present, press .
  • Page 158 Chapter 5: Introduction to PDU Components  Show alert list : This option lists all of alerted sensors and alarms. You still can choose to acknowledge alarms after Alerts viewing the list. See (on page 100).  Acknowledge all alarms : This option immediately acknowledges all existing alarms, without showing the list of alarms.

  • Page 159: Reset Button

    Chapter 5: Introduction to PDU Components Showing the Firmware Upgrade Progress When upgrading the PX3, the firmware upgrade progress will be displayed as a percentage on the LCD display, similar to the following diagram. In the end, a message appears, indicating whether the firmware upgrade succeeds or fails.

  • Page 160: Circuit Breakers

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

  • Page 161: Resetting The Handle-Type Circuit Breaker

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

  • Page 162: Fuse

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

  • Page 163: Fuse Replacement On 1U Models

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

  • Page 165: Beeper

    Chapter 5: Introduction to PDU Components 5. Verify whether this knob's head is aligned with the fuse carrier. If its head is higher or lower than the fuse carrier, re-install it. Number Description INAPPROPRIATE installations Appropriate installation 6. Connect the PDU's power cord to the power source and verify that the corresponding fuse LED is lit, indicating that the fuse works properly.

  • Page 166: Replaceable Controller

    Chapter 5: Introduction to PDU Components Replaceable Controller Zero U A PX3 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 167: Threaded Grounding Point

    Chapter 5: Introduction to PDU Components 3. Disconnect the PDU's controller cable from the controller. 4. Get a new PX3 controller and install it back into the PDU in the reverse order. 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...

  • Page 168: Chapter 6 Using The Web Interface

    Chapter 6 Using the Web Interface This chapter explains how to use the web interface to administer the PX3. In This Chapter Supported Web Browsers ............... 147 Login, Logout and Password Change ............. 147 Web Interface Overview................152 Dashboard ....................160 PDU......................

  • Page 169: Login

    Chapter 6: Using the Web Interface Login You must enable JavaScript in the web browser for proper operation. To log in to the web interface: 1. Open a browser and type the IP address of your PX3.  If the link-local addressing has been enabled, you can type pdu.local APIPA and Link-Local instead of an IP address.
  • Page 170 Chapter 6: 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 171: Changing Your Password

    Chapter 6: 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 Editing or Deleting Users instead. See (on page 277). Password change request on first login: first login , if you have both the Change Local User Management and...

  • Page 172: Remembering User Names And Passwords

    Chapter 6: 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 173: Web Interface Overview

    Chapter 6: Using the Web Interface Web Interface Overview The web interface consists of four areas as shown below. Operation: 1. Click any menu or submenu item in the area of 2. That item's data/setup page is then opened in the area of 3.

  • Page 174: Menu

    Chapter 6: Using the Web Interface 4. To return to the main menu and the Dashboard page, click on the top-left corner. Number Web interface element Menu (on page 155) Data/setup page of the selected menu item.  Left side:...
  • Page 175 Chapter 6: Using the Web Interface Number Web interface element - PX3 device name. Note: To customize the device name, see (on page 173).  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.

  • Page 176: Dashboard

    Chapter 6: 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.
  • Page 177 Chapter 6: Using the Web Interface Menu Information shown Outlet Groups Only PDUs with outlet-switching and/or outlet-metering feature show this menu item. You can create one or multiple groups comprising one or multiple outlets of the same PX3. Functions which you can perform on an outlet group vary depending on the model you purchased.
  • Page 178 Chapter 6: Using the Web Interface Menu Information shown SmartLock Either or both menu items appear only when you connect Raritan's -- and/or -- SmartLock kit to this product. For details, refer to the user Card Readers documentation accompanying the SmartLock kit or download it from Support page http://www.raritan.com/support/ Raritan's...

  • Page 179: Quick Access To A Specific Page

    Chapter 6: 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 180: Sorting A List

    Chapter 6: Using the Web Interface Page Peripherals https://192.168.84.118/#/peripherals Event Log https://192.168.84.118/#/maintenance/eventLog/0 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.

  • Page 181: Dashboard

    Chapter 6: Using the Web Interface 5. The arrow now appears adjacent to the selected column 'Event Class,' indicating the list is sorted in the ascending order based on that column. Dashboard The Dashboard page contains four to five sections, depending on your model.
  • Page 182 Chapter 6: 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 162).

  • Page 183: Dashboard - Inlet I1

    Chapter 6: Using the Web Interface If PX3 detects any internal hardware issues, a section labeled "Hardware Failures" will appear on the Dashboard page, listing all of current hardware issues. This section does NOT display as long as there are no hardware failures Hardware Issue Detection present.
  • Page 184 Chapter 6: 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 185: Dashboard - Ocp

    Chapter 6: Using the Web Interface  A bar showing the RMS current level  RMS voltage (V) The RMS current bars automatically change colors to indicate the current status if the thresholds have been enabled. To configure thresholds, see Inlet (on page 183).
  • Page 186 Chapter 6: Using the Web Interface Each OCP's power data: OCP data from top to bottom includes:  RMS current (A), and rated current  Smaller gray text adjacent to RMS current is each OCP's rated current, such as "16A" shown in the above diagram. ...

  • Page 187: Dashboard - Alerted Sensors

    Chapter 6: Using the Web Interface Dashboard - Alerted Sensors When any internal sensors or environmental sensor packages connected to the PX3 enter an abnormal state, the Alerted Sensors section in the Dashboard show them for alerting users. This section also lists tripped circuit breakers or blown fuses, if available.
  • Page 188 Chapter 6: Using the Web Interface  1 Warned: 1 'numeric' sensor enters the warning state. List of alerted sensors: Two icons are used to indicate various sensor states. Icons Sensor states Numeric sensors:  above upper warning  below lower warning Numeric sensors: ...

  • Page 189: Dashboard - Inlet History

    Chapter 6: Using the Web Interface Dashboard - Inlet History The inlet's power chart helps you observe whether there were abnormal events within the past tens of minutes. The default is to show the inlet's active power data. You can have it show the chart of other inlet power data. Simply select a different data type by clicking the selector below the diagram.
  • Page 190 Chapter 6: 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 191 Chapter 6: Using the Web Interface  When multiple inlets are displayed in the chart, their colors differ. You can identify each inlet's data according to the colors of the selected inlet checkboxes.  When both inlets are shown in the chart, simply hover your mouse over either inlet's data line.

  • Page 192: Dashboard - Alarms

    Chapter 6: Using the Web Interface 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. Note: For information on event rules, see Event Rules and Actions page 353).
  • Page 193 Chapter 6: Using the Web Interface Field Description More Alerts This field appears only when there are more than one types of events triggering this alert. If there are other types of events (that is, other reasons) triggering the same alert, the total number of additional reasons is displayed.

  • Page 194: Pdu

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

  • Page 195: Px3 Latching Relay Behavior

    Chapter 6: Using the Web Interface Field Function Note PX3 Latching Relay Behavior *Relay behavior Selects an operating mode to on power loss determine the latching relay behavior page 178). when PDU power is lost.  Options: Non-latching and Latching ...
  • Page 196 Chapter 6: Using the Web Interface Field Function Note  Power cycling the outlet(s) turns *Power off period Determines the power-off period after the outlet(s) off and then back on. during power the outlet is switched OFF during a  You can override this global power cycle power cycle.
  • Page 197 Chapter 6: Using the Web Interface Tip: You can choose to reset the active energy reading of an individual inlet or outlet. See (on page 183) or Inlet Individual Outlet Pages page 200). To view total active energy and power on multi-inlet models: If your PX3 is a multi-inlet model or an in-line monitor, a "Power"...
  • Page 198 Chapter 6: Using the Web Interface States Description Active The beeper is turned on. "Activation Reason" is displayed, indicating why the beeper sounds an alarm. For example, if the beeper is turned on because of a specific event rule "XXX," the activation reason looks like: Event Action triggered by rule: XXX Scenarios when the beeper sounds an alarm:...
  • Page 199 Chapter 6: Using the Web Interface PX3 Latching Relay Behavior PX3 incorporates latching relays in models with outlet switching. Unlike non-latching relays, latching relays do NOT require power to keep their contacts closed. PX3 outlet switching can be configured to operate as a true latching relay or to simulate a non-latching relay.

  • Page 200: Initialization Delay Use Cases

    Chapter 6: Using the Web Interface If you are configuring an individual outlet on Individual Outlet Pages page 200), there is one more outlet state option. Additional Function option PDU defined Follows the global outlet state setting, which is set (xxx) (on page 173).

  • Page 201: Time Units

    Chapter 6: Using the Web Interface Time Units If you choose to type a new value in the time-related fields, such as the Inrush Guard Delay field, you must add a time unit after the numeric value. For example, you can type '15 s' for 15 seconds. Note that different fields have different range of valid values.
  • Page 202 Chapter 6: Using the Web Interface 2. Click the Thresholds title bar at the bottom of the page to display thresholds. 3. Click the desired sensor (required), and then click Edit Thresholds. 4. Make changes as needed.  To enable any threshold, select the corresponding checkbox. ...

  • Page 203: +12V Power Supply Sensor

    Chapter 6: Using the Web Interface +12V Power Supply Sensor A PX3 PDU'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.

  • Page 204: Inlet

    Chapter 6: 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 Menu 'Inlet' in the (on page 155). Inlet thresholds, once enabled, help you identify whether the inlet enters the warning or critical level.
  • Page 205 Chapter 6: 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. 1.
  • Page 206 Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 893). 4. Click Save. To configure residual current thresholds: If your model supports residual current monitoring, a section titled "Residual Current Monitor"...

  • Page 207: Configuring A Multi-Inlet Model

    Chapter 6: 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: 1. Click 'Show Details' of the desired inlet. 2. Now you can configure the selected inlet, such as enabling Inlet thresholds or resetting its energy.
  • Page 208 Chapter 6: Using the Web Interface 3. Click Save. 4. The inlet status now shows "Disabled." 5. 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.

  • Page 209: Outlets

    Chapter 6: Using the Web Interface Outlets The Outlets page shows a list of all outlets and the overview of outlet Menu status and data. To open this page, click 'Outlets' in the (on page 155). On this page, you can: ...

  • Page 210: Available Data Of The Outlets Overview Page

    Chapter 6: Using the Web Interface  Go to an individual outlet's data/setup page by clicking an Individual Outlet Pages outlet's name. See (on page 200). If wanted, you can resort the list by clicking the desired column header. Sorting a List (on page 159).
  • Page 211 Chapter 6: Using the Web Interface Command Refer to Load Shedding Mode *Activate Load Shedding (on page 197) -- OR-- Deactivate Load Shedding To power control or reset the active energy readings of multiple outlets: You can switch any outlet regardless of its current power state. That is, you can turn on any outlet that is already turned on, or turn off any outlet that is already turned off.
  • Page 212 Chapter 6: Using the Web Interface Button/command Action Power ON. Power OFF. Power cycle.  Power cycling the outlet(s) turns the outlet(s) off and then back on. Resets active energy readings > Reset Energy Counter of selected outlets.  Only users with the "Admin" role assigned can reset active energy readings.
  • Page 213 Chapter 6: Using the Web Interface Available Data of the Outlets Overview Page All or some of the following outlet data is displayed on the outlets overview page based on your model and selection. To show or hide Outlets specific data, click .
  • Page 214 Chapter 6: Using the Web Interface Bulk Configuration for Outlet Thresholds Outlet thresholds, if enabled, help you identify whether any outlet enters the warning or critical level. See Yellow- or Red-Highlighted Sensors (on page 238). In addition, you can have PX3 automatically generate alert Event Rules and notifications for any warning or critical status.
  • Page 215 Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 893). 6. Click Save. Setting Outlet Power-On Sequence and Delay By default, outlets are sequentially powered on in the ascending order from outlet 1 to the final when turning ON or power cycling all outlets on the PX3.
  • Page 216 Chapter 6: Using the Web Interface Button Function Down Bottom Restores to the default sequence Next time when power cycling the PX3, it will turn on all outlets based on the new outlet order. The new order also applies when performing the power-on or power-cycling operation on partial outlets.
  • Page 217 Chapter 6: Using the Web Interface  To select ALL outlets, select the topmost checkbox in the header row. 3. To turn non-critical outlets into critical ones, deselect their checkboxes.  To deselect ALL outlets, deselect the topmost checkbox in the header row.

  • Page 218: Load Shedding Mode

    Chapter 6: Using the Web Interface Load Shedding Mode When a UPS supplying power to PX3 switches into battery backup operation, it may be desirable to switch off non-critical outlets to conserve UPS battery life. This feature is known as load shedding. Outlets that are turned off when load shedding is activated are called non-critical outlets.
  • Page 219 Chapter 6: Using the Web Interface  The off icon appears for outlets, critical or non-critical, that WILL NOT be automatically powered on when deactivating the load shedding mode. Tip: The above two icons are switched if you manually perform any power operations on non-critical outlets during the load shedding mode.
  • Page 220 Chapter 6: Using the Web Interface Off and Lock Icons for Outlets This section further explains the following two icons for outlets, which display in the load shedding mode.  Lock icon : It means the outlet WILL be automatically powered on after deactivating the load shedding mode.

  • Page 221: Individual Outlet Pages

    Chapter 6: Using the Web Interface Individual Outlet Pages An outlet's data/setup page is opened after clicking the outlet's name on the Outlets overview page. See Outlets (on page 188). The individual outlet's page shows this outlet's detailed information. See Detailed Information on Outlet Pages (on page 206).
  • Page 222 Chapter 6: Using the Web Interface Button/command Action Power ON. Power OFF. Power cycle.  Power cycling the outlet(s) turns the outlet(s) off and then back on. 2. Confirm it on the confirmation message. Tip: To switch an outlet using the front panel display, see Power Control (on page 112).
  • Page 223 Chapter 6: Using the Web Interface Field Description *Power off period Select an option to determine how long this during power cycle outlet is turned off before turning back on.  Options: PDU defined or customized time. Power-Off Period Options for Individual Outlets (on page 207).
  • Page 224 Chapter 6: Using the Web Interface Tip: To reset ALL active energy counters on the PX3, see (on page 173). To view this outlet's power chart: By default this outlet's active power data within the past tens of minutes is shown in the power chart. You can click the selector below the chart to show a different data type for this outlet, including:...
  • Page 225 Chapter 6: 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 outlet's threshold settings: Per default, there are pre-defined RMS voltage and current threshold Default Voltage and Current Thresholds values in related fields.
  • Page 226 Chapter 6: Using the Web Interface 3. Make changes as needed.  To enable any threshold, select the corresponding checkbox.  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 893).
  • Page 227 Chapter 6: Using the Web Interface Other operations:  You can go to another outlet's data/setup page by clicking the outlet selector on the top-left corner.  You can go to the associated Inlet's or overcurrent protector's data pages by clicking the Inlet or Overcurrent Protector links in the Details section.
  • Page 228 Chapter 6: Using the Web Interface Field Description Inlet This information is useful when there are multiple inlets on your PDU. Inlet associated with this outlet Overcurrent protector This information is available only when your PX3 has overcurrent protectors. Overcurrent protector associated with this outlet Sensors section: ...

  • Page 229: Outlet Groups

    Chapter 6: Using the Web Interface Outlet Groups Only PDUs with outlet-switching and/or outlet-metering feature show this menu item. Menu Choose Outlet Groups in the (on page 155). The following Outlet Groups page opens. Required permissions: You must have one of the permissions below to be able to operate all or some of the outlet group features.

  • Page 230: Creating An Outlet Group

    Chapter 6: Using the Web Interface Then you can perform one of the following actions on one or multiple outlet groups:  Power on, off or cycle the selected group(s). See Outlet Group Power Control (on page 210).  Observe the power status of each outlet group and/or power status of each member outlet.

  • Page 231: Outlet Group Power Control

    Chapter 6: Using the Web Interface 2. Type the group name. 3. Select the outlets you want in the Available field.  To select all outlets of the PDU, click Select All. 4. To delete any selected outlet(s), click an outlet's in the Selected field.
  • Page 232 Chapter 6: Using the Web Interface Tip: To perform the desired action on only one outlet group, you can simply click that group without making the checkboxes appear. 2. Select multiple outlet groups.  To select ALL outlet groups, select the topmost checkbox in the header row.
  • Page 233 Chapter 6: Using the Web Interface  For detailed information about which outlets are turned on and which are turned off, you can open that outlet group's page by clicking on its name. To switch one group on a specific outlet group's page: This method allows you to switch ONLY one outlet group at a time.
  • Page 234 Chapter 6: Using the Web Interface  Confirm the operation when prompted. If Switchable Outlet Groups are Limited For the Switch Outlet Group permission, if you assign a role to any user, which permits the user to switch only "specific" outlet groups instead of all outlet groups, the following switching issue may appear.

  • Page 235: Resetting A Group's Active Energy

    Chapter 6: Using the Web Interface Resetting a Group's Active Energy An outlet group's active energy is the sum of increments of all member outlets' active energy values. For detailed information, see Outlet Groups (on page 208). Note: A group's active energy is NOT the sum of all member outlets' active energy values.
  • Page 236 Chapter 6: Using the Web Interface 3. Click > Reset Energy Counter.  Confirm the operation when prompted. To reset one group's active energy on a specific outlet group's page: This method allows you to reset the active energy of ONLY one outlet group at a time.

  • Page 237: Modifying An Outlet Group

    Chapter 6: Using the Web Interface Modifying an Outlet Group To modify an outlet group, you must have either permission below.  Administrator Privileges  Change Pdu, Inlet, Outlet & Overcurrent Protector Configuration You can do the following on an individual outlet group's page: ...
  • Page 238 Chapter 6: Using the Web Interface To modify the member outlets: 1. Click Edit Members. 2. Add or remove outlets of this group.  To select any outlet(s), select them one by one from the Available list.  To select all available outlets, click Select All. ...

  • Page 239: Deleting An Outlet Group

    Chapter 6: Using the Web Interface 3. Click Save. Tip: PX3 allows you to assign the same name to diverse outlet groups. If this really occurs, you still can identify different groups through their unique index numbers. To configure the thresholds of group sensors: 1.
  • Page 240 Chapter 6: Using the Web Interface Tip: To perform the desired action on only one outlet group, you can simply click that group without making the checkboxes appear. 2. Select multiple outlet groups. 3. To select ALL outlet groups, select the topmost checkbox in the header row.

  • Page 241: Viewing More Information

    Chapter 6: Using the Web Interface Viewing More Information On the individual outlet group page, you can view more information by doing the following. To observe an outlet group's active power chart:  The chart of an outlet group's active power history will be shown for you to have an overview of its overall changes in the past tens of minutes.
  • Page 242 Chapter 6: Using the Web Interface To visit a member outlet's page from the current page:  On an outlet group's individual page, you can go to a member outlet's page easily. Just click the outlet links in the Outlets section. To visit a different outlet group's page from the current page: ...

  • Page 243: Ocps

    Chapter 6: Using the Web Interface OCPs The OCPs page is available only when your PX3 has overcurrent protectors, such as circuit breakers. The OCPs page lists all overcurrent protectors as well as their status. If any OCP trips or its current level enters the alarmed state, it is Yellow- or Red-Highlighted Sensors highlighted in red or yellow.
  • Page 244 Chapter 6: Using the Web Interface Status Bar colors normal above upper warning above upper critical Note: The "below lower warning" and "below lower critical" states also show yellow and red colors respectively. However, it is not meaningful to enable the two thresholds for current levels. ...

  • Page 245: Individual Ocp Pages

    Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 893). 5. 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 246 Chapter 6: Using the Web Interface Field Description Rating This OCP's rated current. Lines Lines associated with this OCP. Protected outlets Outlets associated with this OCP. Inlet Inlet associated with this OCP. This information is useful only when your PDU has multiple inlets. RMS current This OCP's current state and readings, including current drawn and current...
  • Page 247 Chapter 6: 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 Default Voltage and Current Thresholds configured.
  • Page 248 Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, see Sensor Threshold Settings (on page 893). 4. Click Save.
  • Page 249 Chapter 6: 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 250: Possible Ocp-Tripped Root Cause

    Chapter 6: Using the Web Interface Possible OCP-Tripped Root Cause This feature applies to PX3-5000 and PX3-4000 models only. Outlet-metered models that support "outlet peak current" sensors can detect which outlet is LIKELY to cause the associated OCP to trip, and indicate it on several user interfaces, including the web interface, front panel display, and command line interface (CLI).
  • Page 251 Chapter 6: Using the Web Interface Front panel display: The 'Likely trip cause' message will be displayed for an "open" OCP, OCPs indicating which outlet may cause the OCP-tripped event. See page 109). CLI:  Perform the show ocp command in the CLI. If any OCP has tripped, then the outlet that may cause this event is shown in parentheses in Overcurrent Protector the State field of the tripped OCP.

  • Page 252: Peripherals

    Chapter 6: Using the Web Interface Peripherals If there are Raritan environmental sensor packages connected to the Connecting Raritan PX3, they are listed on the Peripherals page. See Environmental Sensor Packages (on page 50). An environmental sensor package comprises one or some of the following sensors/actuators: ...
  • Page 253 Chapter 6: 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. Sorting a List (on page 159). Sensor/actuator overview on this page: If any sensor enters an alarmed state, it is highlighted in yellow or red.
  • Page 254 Chapter 6: Using the Web Interface Column Description Serial Number This is the serial number printed on the sensor package's label. It helps to identify your Raritan Finding the Sensor's Serial sensors/actuators. See Number (on page 242). Position The data indicates where this sensor or actuator is located in the sensor chain.
  • Page 255 Chapter 6: Using the Web Interface 3. To release selected ones, click > Release. To manage them, click > Manage.  The management action triggers a "Manage Peripheral Device" multiple dialog. Simply click Manage if you are managing sensors/actuators.  If you are managing only sensor/actuator, you can choose to assign an ID number by selecting "Manually select a sensor...
  • Page 256 Chapter 6: Using the Web Interface Field Function Note How the Automatic Peripheral device Enables or disables the automatic Management Function Works auto management management feature for Raritan environmental sensor packages. page 245).  The default is to enable it. ...
  • Page 257 Chapter 6: Using the Web Interface To configure default threshold settings: Note that any changes made to default threshold settings not only re-determine the initial threshold values that will apply to newly-added sensors but also the threshold values of the already-managed sensors Individual where default thresholds are being applied.
  • Page 258 Chapter 6: Using the Web Interface  Type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion Sensor Threshold Settings timeout, see (on page 893). 4. Click Save. Tip: To customize the threshold settings on a per-sensor basis, go to (on page 247).

  • Page 259: Yellow- Or Red-Highlighted Sensors

    Chapter 6: Using the Web Interface Yellow- or Red-Highlighted Sensors The PX3 highlights those sensors that enter the abnormal state with a yellow or red color. Note that numeric sensors can change colors only after you have enabled their thresholds. Tip: When an actuator is turned ON, it is also highlighted in red for drawing attention.

  • Page 260: Managed Vs Unmanaged Sensors/Actuators

    Chapter 6: Using the Web Interface Sensor status Color States shown in Description the interface alarmed State sensors enter the abnormal state. Alarmed  Circuit breaker trips. OCP alarm Open -- OR --  Fuse blown. If you have connected a Schroff LHX/SHX heat exchanger, when any ®...

  • Page 261: Sensor/Actuator States

    Chapter 6: Using the Web Interface  Sensor/Actuator States They show one of the managed states. See (on page 240).  For managed 'numeric' sensors, their readings are retrieved and displayed. If any numeric sensor is disconnected or its reading cannot be retrieved, it shows "unavailable"...
  • Page 262 Chapter 6: Using the Web Interface State Description alarmed The state sensor enters the abnormal state.  Communication with the managed sensor unavailable is lost. -- OR --  DX2, DX, DPX2 or DPX3 sensor packages are upgrading their sensor firmware. Note that for a contact closure sensor, the normal state depends on the normal setting you have configured.

  • Page 263: Finding The Sensor's Serial Number

    Chapter 6: Using the Web Interface Finding the Sensor's Serial Number A DPX environmental sensor package includes a serial number tag on the sensor cable. 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.

  • Page 264: Identifying The Sensor Position And Channel

    Chapter 6: Using the Web Interface Identifying the Sensor Position and Channel Raritan has developed five types of environmental sensor packages - DPX, DPX2, DPX3, DX and DX2 series. Only DPX2, DPX3, DX and DX2 sensor packages can be daisy chained. PX3 can indicate where each sensor or actuator is connected on the Peripheral Devices page.
  • Page 265 Chapter 6: Using the Web Interface Example Physical position Connected to the sensor port #1. Port 1  Connected to the sensor port #1. Port 1,  The sensor/actuator is the 2nd channel of the sensor package. Channel 2  Connected to the sensor port #1. Port 1, ...

  • Page 266: How The Automatic Management Function Works

    Chapter 6: Using the Web Interface How the Automatic Management Function Works This setting is configured on Peripherals (on page 231). 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 267 Chapter 6: Using the Web Interface 2. 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. ...

  • Page 268: Individual Sensor/Actuator Pages

    Chapter 6: 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 269 Chapter 6: Using the Web Interface 2. 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 231).
  • Page 270 Chapter 6: Using the Web Interface To set up a sensor's or actuator's physical location and additional settings: 1. Click Edit Settings. 2. Make changes to available fields, and then click Save. Fields Description Name A name for the sensor or actuator. Description Any descriptive text you want.
  • Page 271 Chapter 6: 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 272 Chapter 6: 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: 1.

  • Page 273: Z Coordinate Format

    Chapter 6: 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 274: Feature Port

    Chapter 6: Using the Web Interface Format Description of any environmental sensors or actuators. Free-form Any alphanumeric string can be used for specifying the Z coordinate. The value comprises 0 to 24 characters. Individual Sensor/Actuator Pages 2. Configure Z coordinates on the (on page 247).
  • Page 275 Chapter 6: Using the Web Interface Device Description LHX 40 Schroff LHX-40 heat exchanger. ® 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 276: Asset Strip

    Chapter 6: Using the Web Interface Mode Description Auto Enable the port to automatically detect the device connection. Disabled Disable the port's detection capability. Asset Strip, Force the PX3 to show the selected device's data/setup page regardless of the physical Raritan asset connection status.
  • Page 277 Chapter 6: Using the Web Interface Asset Strip After connecting and detecting Raritan asset management strips (asset strips), the PX3 shows 'Asset Strip' in place of 'Feature Port' in the menu. Note: For connection instructions, see Connecting Asset Management (on page 71). Strips Menu To open the Asset Strip page, click it in the...
  • Page 278 Chapter 6: Using the Web Interface Field Description 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" on its hardware label, the PX3 automatically detects the number of its tag ports (rack units), and you cannot...
  • Page 279 Chapter 6: Using the Web Interface  Click a color in the color palette.  Type the hexadecimal RGB value of the color, such as #00FF00. 3. Click Ok. The rack unit numbering and LED color settings are immediately updated on the Rack Units list illustrated below. ...
  • Page 280 Chapter 6: 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. 1. Click the desired rack unit on the Rack Units list. The setup dialog for the selected one appears.
  • Page 281 Chapter 6: 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.  : The LED stays lit. ...
  • Page 282 Chapter 6: Using the Web Interface 2. All tag ports of the blade extension strip are listed below it. Their port numbers are displayed in the Slot column.  To hide the blade extension slots list, click...
  • Page 283 Chapter 6: 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.
  • Page 284 Chapter 6: 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. 3. Verify the correctness of customized asset IDs and modify as needed.
  • Page 285 Chapter 6: Using the Web Interface Tip: Another way to abort changes is to click Rack Units. Refer to the diagram below. 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.

  • Page 286: External Beeper

    Chapter 6: Using the Web Interface External Beeper After connecting and detecting a supported external beeper, the PX3 shows 'External Beeper' in place of 'Feature Port' in the menu. Note: For connection instructions, see Connecting an External Beeper (on page 84). Menu To open the External Beeper page, click it in the (on page 155).

  • Page 287: Schroff Lhx/Shx

    Chapter 6: 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 447). After enabling the LHX/SHX support and connecting a supported Schroff ®...
  • Page 288 Chapter 6: Using the Web Interface Feature For the functionality of this icon on the top-right corner, see Port (on page 253). To view the LHX/SHX device state: The Operation State field indicates whether the device is operating fine, and the Switch State field indicates its power status. If the device does not operate properly, such as some sensor failure, it shows "critical"...
  • Page 289 Chapter 6: Using the Web Interface To configure LHX/SHX settings: 1. Click Edit Settings. 2. Configure the settings as needed.  Provide a customized name.  Specify the desired air outlet setpoint temperature.  Specify the default fan speed. 3. Click Save. To view all sensor data and configure thresholds: 1.
  • Page 290 Chapter 6: Using the Web Interface b. Click Edit Thresholds. c. Enable and set the desired thresholds and deassertion hysteresis. Note that assertion timeout is NOT available on LHX/SHX. d. Click Save. 3. After thresholds are enabled, sensors may be highlighted in yellow or red if they enter the warning or critical range.
  • Page 291 Chapter 6: Using the Web Interface 2. If any LHX sensors fail, they are indicated. Click Acknowledge to acknowledge the sensor failure. 3. 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...

  • Page 292: Power Cim

    Chapter 6: 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 293: User Management

    Chapter 6: 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 294 Chapter 6: 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 > Note that you must enter information in the fields showing the message 'required.' User information:...
  • Page 295 Chapter 6: Using the Web Interface Field/setting Description Force password When selected, a password change request change on next automatically appears the next time the user logs login Changing Your Password For details, see page 150). SSH: You need to enter the SSH public key only if the public key authentication Changing SSH Settings for SSH is enabled.
  • Page 296 Chapter 6: Using the Web Interface Field/setting Description Password, Type the authentication password if the 'Same as User Password' checkbox is deselected. Confirm password The password must consist of 8 to 32 ASCII printable characters.  Privacy Password: This section is configurable only when 'Authentication &...
  • Page 297 Chapter 6: Using the Web Interface Field Description Length unit Preferred units for length or height -- Meter or Feet. Pressure unit Preferred units for pressure -- Pascal or Psi.  Pascal = one newton per square meter  Psi = pounds per square inch Note: Users can change the measurement units at any time by setting their own preferences.

  • Page 298: Editing Or Deleting Users

    Chapter 6: Using the Web Interface Editing or Deleting Users To edit or delete users, choose User Management > Users to open the Users page, which lists all users. In the Enabled column:  : The user is enabled.  : The user is disabled.
  • Page 299 Chapter 6: Using the Web Interface  To delete this user, click , and confirm the operation. 3. Click Save. To delete multiple user accounts: 1. On the Users page, click to make checkboxes appear in front of user names. Tip: To delete only one user, you can simply click that user without making the checkboxes appear.

  • Page 300: Creating Roles

    Chapter 6: Using the Web Interface 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. Operator Provide frequently-used permissions, including: ...
  • Page 301 Chapter 6: Using the Web Interface 5. If any privilege requires the argument setting, the symbol displays in the rightmost edge of that privilege's row. To select such a privilege: a. Click on that privilege's row to display a list of available arguments for that privilege.

  • Page 302: Editing Or Deleting Roles

    Chapter 6: 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. Sorting a List (on page 159).

  • Page 303: Setting Your Preferred Measurement Units

    Chapter 6: Using the Web Interface Tip: To delete only one role, you can simply click that role without making the checkboxes appear. Refer to the above procedure. 2. Select one or multiple roles.  To select all roles, except for the Admin role, select the topmost checkbox in the header row.
  • Page 304 Chapter 6: 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. User Interfaces Showing For a list of affected user interfaces, see Default Units (on page 283).

  • Page 305: Device Settings

    Chapter 6: Using the Web Interface Device Settings Menu Click 'Device Settings' in the (on page 155), and the following submenu displays. Menu command Submenu command Refer to... Network Configuring Network Settings (on page 286) Changing HTTP(S) Settings Network Services HTTP (on page 315) Configuring SNMP Settings...
  • Page 306 Chapter 6: Using the Web Interface Menu command Submenu command Refer to... Configuring SMTP Settings SMTP Server (on page 318) Changing SSH Settings (on page 320) Changing Telnet Settings Telnet (on page 321) Changing Modbus Settings Modbus (on page 321) Enabling Service Advertising Server Advertising (on page 324)
  • Page 307 Chapter 6: 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 308 Chapter 6: Using the Web Interface Ethernet 5. To configure the ETH1/ETH2 interface settings, see Interface Settings (on page 290). 6. Click Save. 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): ...
  • Page 309 Chapter 6: Using the Web Interface Field/setting Description  Static : Manually configure the IPv4 settings. Preferred Enter the hostname you prefer for IPv4 hostname connectivity  DHCP settings: Optionally specify the preferred hostname, which must meet the following requirements: ...
  • Page 310 Chapter 6: Using the Web Interface (Optional) To view the diagnostic log for EAP authentication:  Diagnostic Log for Click Show EAP Authentication Log. See Network Connections (on page 299). Common Network Settings Common Network Settings are OPTIONAL, not required. Therefore, leave them unchanged if there are no specific local networking requirements.
  • Page 311 Chapter 6: 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 312 Chapter 6: Using the Web Interface Field Description transmission mode through auto-negotiation.  Full: Data is transmitted in both directions 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 state current speed and duplex mode.
  • Page 313 Chapter 6: Using the Web Interface Field Description Client certificate, This field appears when 'EAP', 'PEAP' and 'TLS' Client private key, are all selected. Client private key password PEM encoded X.509 certificate and PEM encoded private key are required for certification-based authentication methods.
  • Page 314 Chapter 6: Using the Web Interface Field/setting Description chain validity of the TLS certificate that will be installed.  For example, the PX3 will check the certificate's validity period against the system time. Click this button to import a certificate file. Then you can: ...
  • Page 315 Chapter 6: Using the Web Interface Wireless Network Settings If the device's cascading mode is set to 'Bridging' or its role is set to 'Slave' in the port forwarding mode, the wireless settings will be Setting the Cascading Mode disabled. See (on page 304).
  • Page 316 Chapter 6: Using the Web Interface Field/setting Description Outer This field appears when 'EAP' is selected. authentication There are two authentication methods for EAP.  PEAP: A TLS tunnel is established, and an inner authentication method can be specified for this tunnel. ...
  • Page 317 Chapter 6: Using the Web Interface Field/setting Description Client certificate, This field appears when 'EAP', 'PEAP' and 'TLS' Client private key, are all selected. Client private key password PEM encoded X.509 certificate and PEM encoded private key are required for certification-based authentication methods.
  • Page 318 Chapter 6: 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 Allow expired and authentication succeed regardless of the not yet valid...
  • Page 319 Chapter 6: Using the Web Interface  Cannot contain more than 63 characters  Cannot contain punctuation marks, spaces, and other symbols  Static settings: Assign a static IPv4 address, which follows this syntax "IP address/prefix length". 192.168.84.99/24 Example: IPv6 settings: Field/setting Description Enable IPv6...
  • Page 320 Chapter 6: 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 321 Chapter 6: 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 322 Chapter 6: 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.
  • Page 323 Chapter 6: 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 324 Chapter 6: 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.
  • Page 325 Chapter 6: Using the Web Interface Interface list: Interface name Description When another wired network is connected to the BRIDGE Ethernet port of your PX3, and your PX3 has been set to the bridging mode, select this interface name instead of the Ethernet interface. When another wired network is connected to the ETH1 ETH1 port of your PX3, select this interface name.
  • Page 326 Chapter 6: Using the Web Interface Mode Description No cascading mode is enabled. This is the None default. Each device in the cascading chain is Bridging accessed with a different IP address. Each device in the cascading chain is Port Forwarding accessed with the same IP address(es) but with a different port number assigned.
  • Page 327 Chapter 6: Using the Web Interface  In the Port Forwarding mode, all cascaded devices share the master device's network settings. You only need to configure the master device's network settings in the ETH1/ETH2 and/or WIRELESS section. Wired Network Settings Wireless Network (on page 287) or Settings...
  • Page 328 Chapter 6: Using the Web Interface Overview of the Cascading Modes You must apply a cascading mode to the cascading chain. See Setting the Cascading Mode (on page 304). There are two cascading modes: Bridging and Port Forwarding. In the following illustration, it is assumed that users enable the DHCP networking for the cascading chain comprising four devices.
  • Page 329 Chapter 6: Using the Web Interface Comparison between cascading modes:  The Bridging mode supports the wired network only, while the Port Forwarding mode supports both wired and wireless networks.  Both cascading modes support a maximum of 16 devices in a chain. ...
  • Page 330 Chapter 6: 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 331 Chapter 6: Using the Web Interface In the Port Forwarding mode, the cascaded device does NOT allow you to modify the standard TCP/UDP port configuration, including HTTP, HTTPS, SSH, Telnet and Modbus/TCP. Port Forwarding Examples To access a cascaded device in the Port Forwarding mode, assign a port number to the IP address.
  • Page 332 Chapter 6: Using the Web Interface  To access the master device via SSH, the command is: ssh -p 22 192.168.84.77 Slave 1 device: Position code for Slave 1 is '01' so each port number is 5NN01 as shown below. Protocols Port numbers HTTPS...
  • Page 333 Chapter 6: Using the Web Interface Examples:  To access Slave 2 via HTTPS, the IP address is: https://192.168.84.77:50002/  To access Slave 2 via HTTP, the IP address is: http://192.168.84.77:50102/  To access Slave 2 via SSH, the command is: ssh -p 50202 192.168.84.77 Adding, Removing or Swapping Cascaded Devices Change a device's cascading mode first before adding that device to a...
  • Page 334 Chapter 6: Using the Web Interface To swap the master and slave device:  In the Bridging mode, you can swap the master and slave devices by simply disconnecting ALL cascading cables from them, and then reconnecting cascading cables. No changes to software settings are required.

  • Page 335: Configuring Network Services

    Chapter 6: Using the Web Interface Configuring Network Services PX3 supports the following network communication services. HTTPS and HTTP enable the access to the web interface. Telnet and SSH Using the enable the access to the command line interface. See Command Line Interface (on page 511).
  • Page 336 Chapter 6: Using the Web Interface Submenu command Refer to Enabling Service Advertising Server Advertising (on page 324) Important: Raritan uses TLS instead of SSL 3.0 due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
  • Page 337 Chapter 6: 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 338 Chapter 6: Using the Web Interface 2. 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 339 Chapter 6: Using the Web Interface 4. To configure SNMP notifications: a. Select the 'Enable SNMP notifications' checkbox. b. Select a notification type -- SNMPv2c trap, SNMPv2c inform, SNMPv3 trap, and SNMPv3 inform. c. Specify the SNMP notification destinations and enter necessary information.
  • Page 340 Chapter 6: Using the Web Interface Field Description Port Type the port number.  Default is 25 Sender email Type an email address for the sender. address Number of sending Type the number of email retries. retries  Default is 2 retries Time between Type the interval between email retries in sending retries...
  • Page 341 Chapter 6: Using the Web Interface 3. Now that you have set the SMTP settings, you can test it to ensure it works properly. a. Type the recipient's email address in the 'Recipient email addresses' field. Use a comma to separate multiple email addresses.
  • Page 342 Chapter 6: Using the Web Interface Changing Telnet Settings You can enable or disable the Telnet access to the command line interface, or change the TCP port. To change Telnet settings: 1. Choose Device Settings > Network Services > Telnet. 2.
  • Page 343 Chapter 6: 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 85).
  • Page 344 Chapter 6: Using the Web Interface Field Description Use the default port 503, or assign a different port. Valid TCP port range is 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 Parity, are using different communication parameters.
  • Page 345 Chapter 6: 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. The advertised services include the following: ...

  • Page 346: Configuring Security Settings

    Chapter 6: 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 347 Chapter 6: 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 348 Chapter 6: 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 349 Chapter 6: Using the Web Interface  You can select any existing rule and then click to change its priority. 7. Click Save. The rules are applied.
  • Page 350 Chapter 6: Using the Web Interface To configure IPv6 access control rules: 1. On the same page, select the 'Enable IPv6 access control' checkbox to enable IPv6 access control rules. 2. Follow the same procedure as the above IPv4 rule setup to create IPv6 rules.
  • Page 351 Chapter 6: 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.
  • Page 352 Chapter 6: Using the Web Interface 5. When finished, the rules are listed on this page.  You can select any existing rule and then click to change its priority. 6. Click Save. The rules are applied. To configure IPv6 access control rules: 1.
  • Page 353 Chapter 6: Using the Web Interface 4. Perform the desired action.  Make changes to the selected rule, and then click Save. For Creating Role Based Access information on each field, see Control Rules (on page 330).  Click to remove it. ...
  • Page 354 Chapter 6: 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: 1. Choose Device Settings > Security > TLS Certificate. 2.
  • Page 355 Chapter 6: 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 356 Chapter 6: Using the Web Interface 3. Click Upload to install it. 4. 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 357 Chapter 6: Using the Web Interface A password is not required for a self-signed certificate so the Challenge and Confirm Challenge fields disappear. 3. Click Create New TLS Key to create both the self-signed certificate and private key. This may take several minutes to complete. 4.
  • Page 358 Chapter 6: Using the Web Interface 3. You are prompted to open or save the file. Click Save to save it onto your computer. To install available key and certificate files onto PX3: 1. Choose Device Settings > Security > TLS Certificate. 2.
  • Page 359 Chapter 6: Using the Web Interface For security purposes, users attempting to log in to PX3 must be authenticated. PX3 supports the following authentication mechanisms:  Local user database on the PX3  Lightweight Directory Access Protocol (LDAP)  Remote Access Dial-In User Service (Radius) protocol By default, PX3 is configured for local authentication.
  • Page 360 Chapter 6: 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 361 Chapter 6: 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: 1. Choose Device Settings > Security > Authentication. 2.
  • Page 362 Chapter 6: Using the Web Interface Field/setting Description Enable verification Select this checkbox if it is required to validate the LDAP server's of LDAP server certificate by the PX3 prior to the connection. certificate 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 363 Chapter 6: Using the Web Interface Field/setting Description User entry object The object class for user entries. class  Usually it is inetOrgPerson. User search Search criteria for finding LDAP user objects within the directory subfilter tree. Active Directory The name of the Active Directory Domain. domain ...
  • Page 364 Chapter 6: 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 365 Chapter 6: Using the Web Interface Field/setting Description Shared secret, The shared secret is necessary to protect communication with the Radius server. Confirm shared secret 4. To verify if the authentication configuration is set correctly, click Test Connection to check whether the PX3 can connect to the new server successfully.
  • Page 366 Chapter 6: Using the Web Interface  Click Delete to delete the server, and then confirm the operation.  Click Test Connection to verify the connection to the selected server. User credentials may be required.  Click to change the server order, which determines the access priority, and click Save Order to save the new sequence.
  • Page 367 Chapter 6: Using the Web Interface  If you type a value, the value must be followed by a time unit, Time Units such as '4 min.' See (on page 180). 3. In the 'Maximum number of failed logins' field, type a number. This is the maximum number of login failure the user is permitted before the user is blocked from accessing the PX3.
  • Page 368 Chapter 6: Using the Web Interface  If you type a value, the value must be followed by a time unit, Time Units such as '10 d.' See (on page 180). 3. Click Save. To force users to create strong passwords: 1.
  • Page 369 Chapter 6: 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 370: Setting The Date And Time

    Chapter 6: 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 371 Chapter 6: 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 372 Chapter 6: 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 373 Chapter 6: 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 374: Event Rules And Actions

    Chapter 6: Using the Web Interface Event Rules and Actions A benefit of the product's intelligence is its ability to notify you of or react to a change in conditions. This event notification or reaction is an "event rule." An event rule consists of two parts: ...
  • Page 375 Chapter 6: Using the Web Interface Note: When creating scheduled actions, available actions are less than usual because it is meaningless to schedule certain actions like "Alarm," "Log event message," "Send email," "Syslog message" and the like. 2. Click to schedule the desired action.
  • Page 376 Chapter 6: Using the Web Interface Event rule configuration illustration: 1. Choose Device Settings > Event Rules > 2. Click the Event field to select an event type.  <Any sub-event> means all events shown on the list.  <Any Numeric Sensor> means all numeric sensors of the PX3, including internal and environmental sensors.
  • Page 377 Chapter 6: Using the Web Interface 5. 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. 6.
  • Page 378 Chapter 6: Using the Web Interface  To select all available actions, click Select All. 9. 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"...
  • Page 379 Chapter 6: Using the Web Interface Event types Radio buttons Sensor availability Available radio buttons include "Unavailable," "Available" and "Both."  Unavailable: PX3 takes the action only when the chosen sensor is NOT detected and becomes unavailable.  Available: PX3 takes the action only when the chosen sensor is detected and becomes available.
  • Page 380 Chapter 6: Using the Web Interface Event types Radio buttons  Monitoring started: PX3 takes the action only Server monitoring when the monitoring of any specified server event starts.  Monitoring stopped: PX3 takes the action only when the monitoring of any specified server stops.
  • Page 381 Chapter 6: Using the Web Interface Default Log Messages These default log messages are recorded internally and emailed to specified recipients when PX3 events occur (are TRUE) or, in some cases, Send Email stop or become unavailable (are FALSE). See (on page 385) to configure email messages.
  • Page 382 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Asset Management > Composition changed on composite Composite Asset Strip asset strip [AMSNUMBER] Composition Changed ('[AMSNAME]'). Card Reader Management > Card of type '[SMARTCARDTYPE]' with Card Reader >...
  • Page 383 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Device > Device identification Config parameter '[CONFIGPARAM]' changed changed to '[CONFIGVALUE]' by user '[USERNAME]' from host '[USERIP]'. Device > Device settings saved Device settings saved by user '[USERNAME]' from host '[USERIP]'.
  • Page 384 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Device > A Radius error A Radius error occurred: occurred [ERRORDESC]. Device > Raw configuration Raw configuration downloaded by user downloaded '[USERNAME]' from host '[USERIP]'.
  • Page 385 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Peripheral Device Slot > * > Peripheral device Peripheral device Numeric Sensor > Below lower '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot warning threshold [EXTSENSORSLOT] asserted 'below [EXTSENSORSLOT] deasserted...
  • Page 386 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Inlet > * > Sensor > * > Below Sensor '[INLETSENSOR]' on inlet Sensor '[INLETSENSOR]' on inlet lower warning threshold '[INLET]' asserted 'below lower '[INLET]' deasserted 'below lower warning' at [SENSORREADING]...
  • Page 387 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Inlet > Pole > * > Sensor > Sensor '[PDUPOLESENSOR]' on pole Sensor '[PDUPOLESENSOR]' on Below lower warning threshold '[INLETPOLE]' of inlet '[INLET]' pole '[INLETPOLE]' of inlet '[INLET]' asserted 'below lower warning' at...
  • Page 388 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Outlet > * > Power control > Outlet '[OUTLET]' has been powered Powered off off by user '[USERNAME]' from host '[USERIP]'.
  • Page 389 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Above upper critical threshold '[OUTLETPOLE]' of outlet '[OUTLET]' pole '[OUTLETPOLE]' of outlet asserted 'above upper critical' at '[OUTLET]' asserted 'above upper [SENSORREADING] critical' at [SENSORREADING] [SENSORREADINGUNIT].
  • Page 390 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Outlet Grouping > Outlet Group Sensor '[OUTLETGROUPSENSOR]' on Sensor '[OUTLETGROUPSENSOR]' > * > Sensor > Above upper outlet group '[OUTLETGROUPID]' on outlet group '[OUTLETGROUPID]' warning threshold asserted 'above upper warning' at...
  • Page 391 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE [SENSORREADINGUNIT]. Overcurrent Protector > * > Sensor '[OCPSENSOR]' on overcurrent Sensor '[OCPSENSOR]' on Sensor > * > Below lower protector '[OCP]' asserted 'below overcurrent protector '[OCP]' warning threshold...
  • Page 392 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Server Monitoring > * > Server '[MONITOREDHOST]' is now Server '[MONITOREDHOST]' is no Monitored being monitored. longer being monitored. Server Monitoring >...

  • Page 393: Webcam Management

    Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE host '[USERIP]'. User Administration > Password settings changed by user Password settings changed '[USERNAME]' from host '[USERIP]'. User Administration > Role Role '[UMTARGETROLE]' added by added user '[USERNAME]' from host...
  • Page 394 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > Sensor > Above Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX at upper warning threshold [PORTTYPE] port '[PORTID]' asserted [PORTTYPE] port '[PORTID]' 'above upper warning' at deasserted 'above upper warning'...
  • Page 395 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE LHX/SHX > Door Contact The door of LHX at [PORTTYPE] port The door of LHX at [PORTTYPE] port '[PORTID]' was opened. '[PORTID]' was closed.
  • Page 396 Chapter 6: Using the Web Interface The asterisk symbol (*) represents anything you select for the 'trigger' events. Available Actions The PX3 comes with three built-in actions, which cannot be deleted. You can create additional actions for responding to different events. Built-in actions: ...
  • Page 397 Chapter 6: Using the Web Interface Action Function Alarm Requires the user to acknowledge the alert after it is generated. If needed, you can have the alert notifications regularly generated until a person takes the acknowledgment action. Alarm (on page 378). Change load Enters or quits the load shedding mode.
  • Page 398 Chapter 6: Using the Web Interface Action Function Send Email Send email Emails a textual message. See page 385). Send sensor report Reports the readings or status of the selected sensors, including internal or external sensors. See Send Sensor Report (on page 387).
  • Page 399 Chapter 6: Using the Web Interface 5. Then you can assign the newly-created action to an event rule or Event Rules and Actions schedule it. See (on page 353). Alarm The Alarm is an action that requires users to acknowledge an alert. This helps ensure that the user is aware of the alert.
  • Page 400 Chapter 6: Using the Web Interface 7. (Optional) You can instruct the PX3 to send the acknowledgment notification after the alarm is acknowledged in the 'Acknowledgment notifications' field. Available methods are identical to those for generating alarm notifications. a. In the Available field, select desired methods one by one, or click Select All.
  • Page 401 Chapter 6: Using the Web Interface  Stop load shedding: Quits the load shedding mode when the specified event occurs. External Beeper 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: 1.
  • Page 402 Chapter 6: 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 Default Log Messages the section titled (on page 360).

  • Page 403: Configuring Data Push Settings

    Chapter 6: Using the Web Interface Push Out Sensor Readings You can configure the PX3 to push sensor log to a remote server after a certain event occurs, including logs of internal sensors, environmental sensors and actuators. If you have connected Raritan's asset strips to the PX3, you can also configure the PX3 to push the data to a server.
  • Page 404 Chapter 6: Using the Web Interface 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 405 Chapter 6: 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 406 Chapter 6: Using the Web Interface 3. In the Available LHX/SHX field, select the desired SHX-30 device one by one, or click Select All. 4. 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 407 Chapter 6: 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 407).
  • Page 408 Chapter 6: 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 409 Chapter 6: Using the Web Interface a. Click the first to select a target component from the list. b. Click the second to select the specific sensor for the target from the list. c. Click to add the selected sensor to the Report Sensors list box.
  • Page 410 Chapter 6: 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 411 Chapter 6: 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 407).
  • Page 412 Chapter 6: Using the Web Interface To use a different SMTP server, select the 'Use custom SMTP server' checkbox. The fields for customized SMTP settings appear. For Configuring SMTP Settings information on each field, see (on page 318). 5. Select the webcam that is capturing the images you want sent in the email.
  • Page 413 Chapter 6: Using the Web Interface Note: In case you need to type any square brackets "[" and "]" in the custom message for non-placeholder words, always add a backslash in front of the square bracket. That is, \[ or \]. Otherwise, the message sent will not display the square brackets.
  • Page 414 Chapter 6: Using the Web Interface Tip: An SNMP v2c notification action permits only a maximum of three SNMP destinations. To assign more than three SNMP destinations to a specific rule, first create several SNMP v2c notification actions, each of which contains completely different SNMP destinations, and then add all of these SNMP v2c notification actions to the same rule.
  • Page 415 Chapter 6: Using the Web Interface Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" Select this if authorization is required but no privacy protocols are required.  Select the authentication protocol - MD5 or ...
  • Page 416 Chapter 6: Using the Web Interface b. Type the key and value. c. Repeat the same steps to enter more arguments as needed.  To remove any existing argument, click adjacent to Switch LHX/SHX If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will Miscellaneous be available.
  • Page 417 Chapter 6: Using the Web Interface Switch Outlets The "Switch outlets" action is available only when your PX3 is outlet-switching capable. This action turns on, off or power cycles a specific outlet. Operation: 1. Choose Device Settings > Event Rules > 2.
  • Page 418 Chapter 6: Using the Web Interface 4. To select the actuator(s) where this action will be applied, select them one by one from the 'Available actuators' list.  To add all actuators, click Select All. 5. To remove any selected actuator from the 'Selected actuators' field, click that actuator's ...
  • Page 419 Chapter 6: Using the Web Interface Transport Next steps protocols A TLS certificate is required. Do the following: a. 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 420 Chapter 6: Using the Web Interface  To select all available actions, click Select All. 3. To remove any action(s) from the 'Selected actions' field, click that action's  To remove all actions, click Deselect All. 4. 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 421 Chapter 6: Using the Web Interface Execution Frequency settings time 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 422 Chapter 6: Using the Web Interface Execution Frequency settings time This option requires three settings: Yearly  Month - January through December.  Day of month - 1 to 31.  Time - the value is measured in 12-hour format so you must correctly specify AM or PM by clicking the AM/PM button.
  • Page 423 Chapter 6: Using the Web Interface  If wanted, you can customize the subject and content of this email in this action.
  • Page 424 Chapter 6: Using the Web Interface...
  • Page 425 Chapter 6: Using the Web Interface 2. Click to create a 'Send sensor report' action that includes the 'Email a Sensor Report' action as its destination Send Sensor Report action. For details, see (on page 387).  Send Temperature Sensor In this example, this action is named Readings...
  • Page 426 Chapter 6: Using the Web Interface  You can specify more than one temperature sensor as needed in this action. 3. Click to create a timer for performing the 'Send Temperature Sensor Readings' action hourly. Scheduling an Action For details, see (on page 398).
  • Page 427 Chapter 6: Using the Web Interface  Hourly Temperature Sensor In this example, the timer is named 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 428 Chapter 6: 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 385) or Send SMS Message (on page 389). In addition, you can add custom text message to Send Snapshots via Email the "Send snapshots via email"...
  • Page 429 Chapter 6: Using the Web Interface Placeholder Definition [AMSLEDOPMODE] The LED operating mode [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]...
  • Page 430 Chapter 6: Using the Web Interface Placeholder Definition [INLET] The inlet label [INLETPOLE] The inlet power line identifier [INLETSENSOR] The inlet sensor name [ISASSERTED] Boolean flag whether an event condition became true (1) or false (0) [LDAPERRORDESC] The LDAP error occurred [LHXFANID] The ID of a fan connected to an LHX/SHX [LHXPOWERSUPPLYID]...
  • Page 431 Chapter 6: Using the Web Interface Placeholder Definition [PDUSENSOR] The PDU sensor name [PERIPHDEVPOSITION] The position of an attached peripheral device [PHONENUMBER] The destination phone number of an outgoing SMS message [PORTID] The label of the external port the event-triggering device is connected to [PORTTYPE] The type of the external port (e.g.
  • Page 432 Chapter 6: Using the Web Interface Placeholder Definition [USERIP] The IP address a user connected from [USERNAME] The user who performed an operation [VERSION] The firmware version the device is upgrading to Note: In case you need to type any square brackets "[" and "]" in the custom message for non-placeholder words, always add a backslash in front of the square bracket.
  • Page 433 Chapter 6: Using the Web Interface 2. Select "Firmware update failed" so that the PX3 responds to the event related to firmware upgrade failure. 3. 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 434 Chapter 6: 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 (on page Enabling and Configuring SNMP 501). Then the SNMP notifications are sent when: ...
  • Page 435 Chapter 6: 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 436 Chapter 6: Using the Web Interface  Any sensor reading or state returns to normal.  Any sensor becomes unavailable.  The active energy sensor is reset. For example, when the Inlet I1's voltage exceeds the upper warning threshold, the SNMP notifications are sent, and when the voltage drops below the upper warning threshold, the SNMP notifications are sent again.
  • Page 437 Chapter 6: Using the Web Interface After the new action is created, follow the procedure below to create an event rule that triggers the load shedding mode when the contact closure sensor enters the alarmed state. This event rule involves the following: ...
  • Page 438 Chapter 6: Using the Web Interface 8. Select "Activate Load Shedding" from the 'Available actions' list. A Note about Infinite Loop You should avoid building an infinite loop when creating event rules. The infinite loop refers to a condition where the PX3 keeps busy because the action or one of the actions taken for a certain event triggers an identical or similar event which will result in an action triggering one more event.
  • Page 439 Chapter 6: Using the Web Interface Example 2 This example illustrates an event rule which continuously causes the PX3 to send out SMTP messages when one of the selected events listed on the Device menu occurs. Note that <Any sub-event> under the Device menu includes the event "Sending SMTP message failed."...
  • Page 440 Chapter 6: Using the Web Interface Setting Data Logging The PX3 can store 120 measurements for each sensor in a memory buffer. This memory buffer is known as the data log. Sensor readings in the data log can be retrieved using SNMP. You can configure how often measurements are written into the data log using the Measurements Per Log Entry field.
  • Page 441 Chapter 6: 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 442 Chapter 6: Using the Web Interface Note: If the required certificate file is a chain of certificates, and you are not sure about the requirements of a certificate chain, see (on page 920). Certificate Chain 5. If the destination server requires authentication, select the 'Use authentication' checkbox, and enter the following data.
  • Page 443 Chapter 6: Using the Web Interface  To modify settings, make necessary changes and then click Save.  To delete it, click , and then confirm it on the confirmation message. 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.
  • Page 444 Chapter 6: 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 445 Chapter 6: 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 446 Chapter 6: 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 447 Chapter 6: Using the Web Interface...
  • Page 448 Chapter 6: Using the Web Interface (Continued)
  • Page 449 Chapter 6: 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 450: Monitoring Server Accessibility

    Chapter 6: 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 451 Chapter 6: Using the Web Interface Field Description IP address/hostname IP address or host name of the IT equipment which you want to monitor. Number of The number of successful pings required to successful pings to declare that the monitored equipment is enable feature "Reachable."...
  • Page 452 Chapter 6: Using the Web Interface To configure the shutdown and power control settings: Restriction: To make the power control feature work properly, the power cord(s) of the monitored IT device must be connected to the "same" PDU which is monitoring the IT device. Field Description Shutdown command...
  • Page 453 Chapter 6: Using the Web Interface Field Description Method of checking This field determines when PX3 will power successful shutdown off the outlet(s) that supplies power to the monitored device, after PX3 issues the shutdown command to that device.  Timer ...
  • Page 454 Chapter 6: Using the Web Interface Field Description Timeout for shutdown This field appears for the 'Active power check drop' method. Valid values range between 5 and 10,000 seconds. The power-off operation is performed only when the active power value of the selected outlet or outlet group drops below the 'Active power threshold' within the period of time specified in this field.
  • Page 455 Chapter 6: Using the Web Interface 2. The column labeled "Status" indicates the accessibility of monitored equipment. 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.
  • Page 456 Chapter 6: Using the Web Interface 4. Observe the Power Control status of the monitored device to make sure the shutdown operation succeeds. To power on a monitored device: 1. Select the IT device that you want to turn on. 2.
  • Page 457 Chapter 6: Using the Web Interface Field Data entered IP address/hostname 192.168.84.95  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 3...

  • Page 458: Front Panel Settings

    Chapter 6: Using the Web Interface Field/setting Data specified Rule name Send SNMP notifications for PDU (192.168.84.95) inaccessibility Event Choose Server Monitoring > 192.168.84.95 > Unreachable Trigger condition Select the Unreachable radio button This will make the PX3 react only when the target PDU becomes inaccessible.
  • Page 459 Chapter 6: Using the Web Interface Mode Data entered Automatic mode The LCD display cycles through both the inlet and overcurrent protector information. This is the default. Overcurrent protector information is available only when your PX3 has overcurrent protectors. Inlet overview The LCD display cycles through the inlet information only.

  • Page 460: Configuring The Serial Port

    Chapter 6: Using the Web Interface Configuring the Serial Port You can change the bit rate of the serial port labeled CONSOLE / MODEM on the PX3. The default bit rate for console and modem operation is 115200 bps. The PX3 supports using the following devices via the serial interface: ...

  • Page 461: Lua Scripts

    Chapter 6: Using the Web Interface 2. Click the 'Console baud rate' field to select the baud rate intended for console management. Note: For a serial RS-232 or USB connection between a computer and the PX3, leave it at the default (115200 bps). 3.
  • Page 462 Chapter 6: Using the Web Interface Writing or Loading a Lua Script You can enter or load up to 4 scripts to the PX3. Tip: If you can no longer enter or load a new script after reaching the upper limit, you can either delete any existing script or simply modify/replace an existing script's codes.
  • Page 463 Chapter 6: Using the Web Interface 5. In the Source Code section, do one of the following. It is recommended to leave the Enable Syntax Highlighting checkbox selected unless you do not need different text colors to identify diverse code syntaxes. ...
  • Page 464 Chapter 6: 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 465 Chapter 6: Using the Web Interface  Click if needing additional arguments. 5. Click Start. 6. The script output will be shown in the Script Output section.  If needed, click to delete the existing output data. To manually stop a script: 1.
  • Page 466 Chapter 6: Using the Web Interface To return to the scripts list:  Click "Lua Scripts" on the top of the page.  Menu Or click "Lua Scripts" in the (on page 155). Checking Lua Scripts States Choose Device Settings > Lua Scripts to show the scripts list, which indicates the current state and settings of each script.
  • Page 467 Chapter 6: Using the Web Interface Modifying or Deleting a Script You can edit an existing script's codes or even replace it with a new script. Or you can simply remove a unnecessary script from the PX3. To modify or replace a script: 1.

  • Page 468: Miscellaneous

    Chapter 6: Using the Web Interface Miscellaneous By default, the Schroff LHX/SHX heat exchanger support and Cisco EnergyWise feature implemented on the PX3 are disabled. Support needs to be enabled for the LHX/SHX information to appear in the PX3 web interface. Besides, Schroff LHX/SHX support must be enabled in order for the LHX-MIB to be accessible through SNMP.
  • Page 469 Chapter 6: Using the Web Interface Field Description Port Type a User Datagram Protocol (UDP) port number for communications in the Cisco EnergyWise domain.  Range from 1 to 65535.  Default is 43440. Polling interval Type a polling interval to determine how often the PX3 is queried in the Cisco EnergyWise domain.

  • Page 470: Maintenance

    Chapter 6: Using the Web Interface Maintenance Menu Click 'Maintenance' in the (on page 155), and the following submenu displays. Submenu command Refer to... Device Information Device Information (on page 451) Viewing Connected Users Connected Users (on page 456) Event Log Viewing or Clearing the Local Event Log (on page 458) Updating the PX3 Firmware...

  • Page 471: Bulk Configuration

    Chapter 6: Using the Web Interface Submenu command Refer to... Bulk Configuration Bulk Configuration (on page 464) Backup and Restore of Device Settings Backup/Restore (on page 471) Network Diagnostics Network Diagnostic (on page 473) Downloading Diagnostic Information Download Diagnostic (on page 474) Hardware Issue Detection Hardware Failures (on page 474)
  • Page 472 Chapter 6: 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 473 Chapter 6: Using the Web Interface Section title Information shown Information General device information, such as model name, serial number, firmware version, hardware revision, MIB download link(s) and so on. Note that the download link of LHX-MIB is available only after enabling the Schroff Miscellaneous LHX/SHX support.
  • Page 474 Chapter 6: Using the Web Interface Identifying Cascaded Devices Cascading Multiple For information on how to cascade PX3 devices, see PX3 Devices for Sharing Ethernet Connectivity (on page 34). This section explains how to identify a cascaded device on the Device Information page.
  • Page 475 Chapter 6: 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 304).
  • Page 476 Chapter 6: Using the Web Interface  A master device shows (zero) in the 'Cascade position' field and 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 in the 'Cascaded device connected' field.
  • Page 477 Chapter 6: Using the Web Interface The following diagram shows 2, indicating it is the second slave device - Slave 2. The 'Cascaded device connected' field shows 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 478 Chapter 6: Using the Web Interface If wanted, you can resort the list by clicking the desired column Sorting a List header. See (on page 159). 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>...
  • Page 479 Chapter 6: Using the Web Interface The IP address refers to the IP address of the host where the Primary Standalone Live Preview window exists, NOT the IP address of the other two associated sessions. Webcam Management For more webcam information, see (on page 478).
  • Page 480 Chapter 6: 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 481 Chapter 6: Using the Web Interface 3. Click Upload. A progress bar appears to indicate the upload process. 4. 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. 5.
  • Page 482 Chapter 6: 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 483 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...
  • Page 484 Chapter 6: 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 485 Chapter 6: Using the Web Interface  Update date and time  Previous firmware version  Update firmware version  Update result 2. If wanted, you can resort the list by clicking the desired column Sorting a List header. See (on page 159).
  • Page 486 Chapter 6: Using the Web Interface b. Save a bulk configuration file from the source device. c. Perform bulk configuration on one or multiple target devices. 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.
  • Page 487 Chapter 6: Using the Web Interface Bulk Configuration Restrictions Before performing bulk configuration, make sure your source and target devices are compatible devices for sharing general settings. Restrictions for bulk configuration:  The target device must be running the same firmware version as the source device.
  • Page 488 Chapter 6: Using the Web Interface Suffix Mechanical design Example Locking Outlet types or options E2 = Locking Controller options G0 = no controller Chassis colors K6 = yellow The line cord's length in centimeters Chassis dimensions or other mechanical changes OCP brand options Special requests for device painting or printing...
  • Page 489 Chapter 6: Using the Web Interface 6. Now decide which settings are wanted and which are not. a. Click of the setting which you want to configure. b. When the pop-up menu appears, select one of the options. Note that the two options 'Inherited' and 'Built-in' are mutually exclusive.
  • Page 490 Chapter 6: Using the Web Interface Performing Bulk Configuration On the source device, make sure the wanted profile has been set as the default one. If not, start from step 1 below. If yes, go to step 2 directly. Step 1: Select the desired bulk configuration profile (optional) 1.
  • Page 491 Chapter 6: Using the Web Interface 5. When prompted to open or save the configuration file, click Save. Step 3: Perform bulk configuration You must have the Administrator Privileges to upload the configuration. 1. Log in to the target PX3, which is of the same model and runs the same firmware as the source PX3.
  • Page 492 Chapter 6: Using the Web Interface 3. Click Save. To remove a single profile: 1. Click on the row of the wanted profile. 2. Click on the top-right corner. 3. Click Delete on the confirmation message. To remove one or multiple profiles: 1.
  • Page 493 Chapter 6: Using the Web Interface 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. To back up or restore the settings of PX3, you should perform the Backup/Restore feature.
  • Page 494 Chapter 6: Using the Web Interface 5. Wait until the PX3 resets and the Login page re-appears, indicating that the restore is complete. 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.
  • Page 495 Chapter 6: Using the Web Interface Field Description Number of A number up to 20. requests This determines how many packets are sent for pinging the host. 2. Click Run Ping to ping the host. The Ping results are then displayed. Trace Route: 1.
  • Page 496 Chapter 6: Using the Web Interface Hardware Issue Detection This page lists any internal hardware issues PX3 has detected, including current events and historical records. Choose Maintenance > Hardware Failures, and the page similar to either of the following diagrams opens. NO hardware failures detected: Hardware failure(s) detected: Hardware Failure alerts on the Dashboard page:...
  • Page 497 Chapter 6: Using the Web Interface 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 sensors. Communication with a specific slave controller fails. Slave controller not reachable A specific slave controller does not work properly.
  • Page 498 Chapter 6: Using the Web Interface 3. A message appears, with a countdown timer showing the remaining time of the operation. It takes about one minute to complete. 4. When the restart is complete, the login page opens. Tip: If you are not redirected to the login page after the restart is complete, click the text "this link"...
  • Page 499 Chapter 6: Using the Web Interface Tip: If you are not redirected to the login page after the reset is complete, click the text "this link" in the countdown message. Alternative: There are two more methods to reset the device to factory defaults. ...

  • Page 500: Webcam Management

    Chapter 6: 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 Connecting a Logitech Webcam already. See (on page 82).
  • Page 501 Chapter 6: 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 502: Configuring Webcams And Viewing Live Images

    Chapter 6: Using the Web Interface Configuring Webcams and Viewing Live Images To configure a webcam or view live snapshot/video sessions, choose Menu Webcams in the (on page 155). Then click the desired webcam to open that webcam's page. Note that default webcam names are determined by the detection order. Webcam The one that is detected first is named , and the other that is...
  • Page 503 Chapter 6: 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 504 Chapter 6: Using the Web Interface Settings: 1. By default the Settings section is open. If not, click the Settings title bar. 2. Click Edit Settings. 3. Enter a name for the webcam. Up to 64 ASCII printable characters are supported. ...

  • Page 505: Sending Links To Snapshots Or Videos

    Chapter 6: Using the Web Interface To return to the Webcam Management page:  Click Webcam Management on the top of the page.  Menu Or click Webcams again in the (on page 155). Sending Links to Snapshots or Videos When opening a Primary Standalone Live Preview window, a unique URL is generated for this window session.
  • Page 506 Chapter 6: Using the Web Interface  Note that default webcam names are determined by the Webcam detection order. The one that is detected first is named Webcam 2 and the other that is detected later is named 3. Click in the Live Preview section.

  • Page 507: Viewing And Managing Locally-Saved Snapshots

    Chapter 6: 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 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 508 Chapter 6: Using the Web Interface saved onto the PX3 locally. If needed, download important snapshots before rebooting the device. To view saved snapshots: 1. Choose Webcams > . The Snapshots page opens. 2. 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 509 Chapter 6: Using the Web Interface  To select all images, select the topmost checkbox in the header row. 3. On the top of the list, click 4. Click Delete on the confirmation message. To download any image onto the computer: ...

  • Page 510: Changing Storage Settings

    Chapter 6: Using the Web Interface 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. You must launch appropriate third-party applications, such as an FTP client, to access and manage the snapshots stored on remote servers.
  • Page 511 Chapter 6: 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 Viewing and snapshots stored on the PX3. See Managing Locally-Saved Snapshots (on page 485).
  • Page 512 Chapter 6: 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 513 Chapter 6: 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 514: Smartlock And Card Reader

    Chapter 6: 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 515: Smartlock

    Chapter 6: 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 516 Chapter 6: Using the Web Interface SmartLock To open the SmartLock page, choose SmartLock in the Menu (on page 155). 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 517 Chapter 6: 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 518 Chapter 6: 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 519 Chapter 6: 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 520 Chapter 6: Using the Web Interface To view the status of the door and card reader: Section Description Shows all sensor states detected by DX2-DH2C2, Door State including:  Door : States of contact closure sensors connected to DX2-DH2C2. Contact closure sensors detect whether the door is physically opened or closed.

  • Page 521: Card Readers

    Chapter 6: Using the Web Interface 2. Go to the proper door handle section, and click Open or Close to open or close the door handle lock. 3. Confirm the operation when prompted. 4. Now you can physically open the cabinet door with the opened door handle.
  • Page 522 Chapter 6: 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 523: Chapter 7 Using Snmp

    Chapter 7 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 524: Snmpv2C Notifications

    Chapter 7: Using SNMP To enable SNMP notifications: 1. Choose Device Settings > Network Services > SNMP. 2. In the SNMP Notifications section, enable the SNMP notification feature, and configure related fields. For details, refer to:  SNMPv2c Notifications (on page 502) ...
  • Page 525 Chapter 7: Using SNMP Field Description Timeout The interval of time, in seconds, after which a new inform communication is resent if the first is not received.  For example, resend a new inform communication once every 3 seconds. Number of retries The number of times you want to resend the inform communication if it fails.
  • Page 526 Chapter 7: Using SNMP 3. In the SNMP Notifications section, make sure the 'Enable SNMP notifications' checkbox is selected. 4. Select 'SNMPv3 trap' or 'SNMPv3 inform' as the notification type. 5. For SNMP TRAPs, the engine ID is prepopulated. 6. Type values in the following fields. Field Description Host...
  • Page 527 Chapter 7: 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 528: Downloading Snmp Mib

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

  • Page 529: Snmp Gets And Sets

    Chapter 7: 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 530 Chapter 7: 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 531 Chapter 7: Using SNMP SNMP Sets and Thresholds Some objects can be configured from the SNMP manager using SNMP set commands. Objects that can be configured have a MAX-ACCESS level of "read-write" in the MIB. These objects include threshold objects, which cause the PX3 to generate a warning and send an SNMP notification when certain Sensor Threshold Settings parameters are exceeded.

  • Page 532: Retrieving Energy Usage

    Chapter 7: Using SNMP Retrieving Energy Usage You can discover how much energy an IT device consumes by retrieving the Active Energy for the outlet this IT device is plugged into. The Active Energy values are included in the outletSensorMeasurementsTable, along with other outlet sensor readings.

  • Page 533: Chapter 8 Using The Command Line Interface

    Chapter 8 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.................. 512 Logging in to CLI..................

  • Page 534: About The Interface

    Chapter 8: Using the Command Line Interface About the Interface The PX3 provides a command line interface that enables data center administrators to perform some basic management tasks. Using this interface, you can do the following:  Reset the PX3 ...

  • Page 535: With Ssh Or Telnet

    Chapter 8: Using the Command Line Interface  Parity = None  Flow control = None Tip: For a USB connection, you can determine the COM port by choosing Control Panel > System > Hardware > Device Manager, and locating the "Dominion PX2 Serial Console" under the Ports group. 3.

  • Page 536: With An Analog Modem

    Chapter 8: Using the Command Line Interface Note: If using the SSH client, the name must NOT exceed 25 characters. Otherwise, the login fails. Then you are prompted to enter a password. 4. Type a password and press Enter. The password is case sensitive. 5.

  • Page 537: Different Cli Modes And Prompts

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

  • Page 538: Querying Available Parameters For A Command

    Chapter 8: Using the Command Line Interface config:# In the diagnostic mode: diag:# Press Enter after pressing the ? command, and a list of main commands for the current mode is displayed. Tip: To automatically complete a command after typing part of the full command, see (on page 711).

  • Page 539: Showing Information

    Chapter 8: Using the Command Line Interface config:# role create ? Tip: To automatically complete a command after typing part of the full command, see (on page 711). Automatically Completing a Command To re-execute one of the previous commands, see Retrieving Previous (on page 710).
  • Page 540 Chapter 8: 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 (on page 519).
  • Page 541 Chapter 8: 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 (on page 518). 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...
  • Page 542 Chapter 8: 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 show network ipv4 interface Network Interface Settings This command shows the specified network interface's information...
  • Page 543 Chapter 8: 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 544: Pdu Configuration

    Chapter 8: Using the Command Line Interface PDU Configuration This command shows the PDU configuration, such as the device name, firmware version, model type and upper limit of active powered dry contact actuators. show pdu To show detailed information, add the parameter "details" to the end of the command.

  • Page 545: Outlet Group Information

    Chapter 8: Using the Command Line Interface Outlet Group Information This command syntax shows the outlet group information. show outletgroups <n> To show detailed information, add the parameter "details" to the end of the command. show outletgroups <n> details Variables: ...

  • Page 546: Inlet Information

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

  • Page 547: Overcurrent Protector Information

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

  • Page 548: Date And Time Settings

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

  • Page 549: Environmental Sensor Information

    Chapter 8: Using the Command Line Interface Environmental Sensor Information This command syntax shows the environmental sensor's information. show externalsensors <n> To show detailed information, add the parameter "details" to the end of the command. show externalsensors <n> details Variables: ...

  • Page 550: Environmental Sensor Package Information

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

  • Page 551: Actuator Information

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

  • Page 552: Outlet Sensor Threshold Information

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

  • Page 553: Outlet Pole Sensor Threshold Information

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

  • Page 554: Outlet Group Threshold Information

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

  • Page 555: Inlet Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Inlet Sensor Threshold Information This command is NOT available for an in-line monitor (PX3-3000 series). 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 556 Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified inlet sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.

  • Page 557: Inlet Pole Sensor Threshold Information

    Chapter 8: Using the Command Line Interface Inlet Pole Sensor Threshold Information This command is only available for a three-phase PDU except for an in-line monitor (PX3-3000 series). This command syntax shows the specified inlet pole sensor's threshold-related information. show sensor inletpole <n> <p> <sensor type> To show detailed information, add the parameter "details"...
  • Page 558 Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the reading, state, threshold, deassertion hysteresis and assertion timeout settings of the specified inlet pole sensor are displayed.  With the parameter "details," more sensor information is displayed, including resolution and range.

  • Page 559: Overcurrent Protector Sensor Threshold Information

    Chapter 8: 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 560: Environmental Sensor Threshold Information

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

  • Page 561: Environmental Sensor Default Thresholds

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

  • Page 562: Security Settings

    Chapter 8: Using the Command Line Interface Sensor types Description vibration Vibration sensors 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 563: Authentication Settings

    Chapter 8: 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 564: Existing User Profiles

    Chapter 8: Using the Command Line Interface  With the parameter "details" added, detailed information of the specified server is displayed, such as an LDAP server's bind DN and the login name attribute, or a Radius server's timeout and retries values.

  • Page 565: Existing Roles

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

  • Page 566: Serial Port Settings

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

  • Page 567: Rack Unit Settings Of An Asset Strip

    Chapter 8: Using the Command Line Interface Rack Unit Settings of an Asset Strip A rack unit refers to a tag port on the asset strips. This command shows the settings of a specific rack unit or all rack units on an asset strip, such as a rack unit's LED color and LED mode.

  • Page 568: Event Log

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

  • Page 569: Network Connections Diagnostic Log

    Chapter 8: Using the Command Line Interface Event type Description sensor Internal or external sensor events, such as state changes of any sensors. serverMonitor Server-monitoring records, such as a server being declared reachable or unreachable. assetManagement Raritan asset management events, such as asset tag connections or disconnections.
  • Page 570 Chapter 8: Using the Command Line Interface Server Reachability Information for a Specific Server To show the server reachability information for a certain IT device only, use the following command. show serverReachability server <n> To show detailed information, add the parameter "details" to the end of the command.

  • Page 571: Reliability Data

    Chapter 8: Using the Command Line Interface Command History This command shows the command history for current connection session. show history Displayed information:  A list of commands that were previously entered in the current session is displayed. Reliability Data This command shows the reliability data.

  • Page 572: Examples

    Chapter 8: Using the Command Line Interface Examples This section provides examples of the show command. Example 1 - Basic Security Information show security The diagram shows the output of the command.
  • Page 573 Chapter 8: Using the Command Line Interface Example 2 - In-Depth Security Information More information is displayed when typing the show security details command. Example 3 - Basic PDU Information show pdu The diagram shows the output of the command.

  • Page 574: Clearing Information

    Chapter 8: Using the Command Line Interface Example 4 - In-Depth PDU Information More information is displayed when typing the show pdu details command. Displayed information varies depending on the model you purchased. Clearing Information You can use the clear commands to remove unnecessary data from the PX3.

  • Page 575: Clearing Diagnostic Log For Network Connections

    Chapter 8: 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 576: Quitting Configuration Mode

    Chapter 8: Using the Command Line Interface Quitting Configuration Mode (on page 554). 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"...
  • Page 577 Chapter 8: Using the Command Line Interface Setting the Outlet Relay Behavior This section applies to outlet-switching capable models only. This command syntax determines the relay behavior of all outlets on a PX3 model. config:# pdu relayBehaviorOnPowerLoss <option> Variables:  <option>...
  • Page 578 Chapter 8: Using the Command Line Interface Setting the Outlet Power-On Sequence Delay This section applies to outlet-switching capable models only. This command sets the delays (in seconds) for outlets when turning on all outlets in sequence. config:# pdu outletSequenceDelay <outlet1>:<delay1>;<outlet2>:<delay2>; <outlet3>:<delay3>;...
  • Page 579 Chapter 8: Using the Command Line Interface Option Description lastKnownState Restores all outlets to the previous status before powering down the PX3 when the PDU powers up again. Note: This feature does NOT take effect and cannot be configured on a PX3 device after the outlet relay is set to the "Latching"...
  • Page 580 Chapter 8: Using the Command Line Interface Setting the Outlet Initialization Delay This section applies to outlet-switching capable models only. This command determines the outlet initialization delay timing on device startup. See (on page 173) for information on outlet initialization delay.
  • Page 581 Chapter 8: Using the Command Line Interface Enabling or Disabling Data Logging This command enables or disables the data logging feature. config:# pdu dataRetrieval <option> Variables:  enable disable <option> is one of the options: Option Description enable Enables the data logging feature. disable Disables the data logging feature.
  • Page 582 Chapter 8: 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 583 Chapter 8: Using the Command Line Interface Enabling or Disabling Peripheral Device Auto Management This command enables or disables the Peripheral Device Auto Management feature. config:# pdu peripheralDeviceAutoManagement <option> Variables:  <option> is one of the options: enable disable Option Description enable Enables the automatic management feature for...

  • Page 584: Network Configuration Commands

    Chapter 8: Using the Command Line Interface Example 1 - PDU Naming The following command assigns the name "my px12" to the PDU. config:# pdu name "my px12" Example 2 - Outlet Sequence The following command causes a 10-outlet PDU to first power on the 8th to 6th outlets and then the rest of outlets in the ascending order after the PDU powers up.
  • Page 585 Chapter 8: Using the Command Line Interface Setting the IPv4 Configuration Mode This command determines the IP configuration mode. config:# network ipv4 interface <ETH> configMethod <mode> Variables:  <ETH> is one of the network interfaces: ETH1/ETH2 WIRELESS , or BRIDGE .
  • Page 586 Chapter 8: Using the Command Line Interface Setting the IPv4 Preferred Host Name After selecting DHCP as the IPv4 configuration mode, you can specify the preferred host name, which is optional. The following is the command: config:# network ipv4 interface <ETH> preferredHostName <name> Variables: ...
  • Page 587 Chapter 8: 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 588 Chapter 8: Using the Command Line Interface Setting IPv4 Static Routes If the IPv4 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the PX3 and devices in the other subnet.
  • Page 589 Chapter 8: 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 590 Chapter 8: Using the Command Line Interface Interface Description wireless Determine the IPv6 configuration mode of the WIRELESS interface (that is, wireless networking). bridge Determine the IPv6 configuration mode of the BRIDGE interface (that is, bridging mode).  automatic static <mode>...
  • Page 591 Chapter 8: Using the Command Line Interface Interface Description bridge Determine the IPv6 preferred host name of the BRIDGE interface (that is, bridging mode).  <name> is a host name which:  Consists of alphanumeric characters and/or hyphens  Cannot begin or end with a hyphen ...
  • Page 592 Chapter 8: Using the Command Line Interface  <ip address> is the IP address being assigned to your PX3. This value uses the IPv6 address format. Note that you must add , which indicates a prefix length of bits such as /64, to the end of this IPv6 address.
  • Page 593 Chapter 8: Using the Command Line Interface config:# network ipv6 staticRoutes delete <route_ID> Modify an existing static route: config:# network ipv6 staticRoutes modify <route_ID> dest <dest-2> nextHop <hop> -- OR -- config:# network ipv6 staticRoutes modify <route_ID> dest <dest-2> interface <ETH>...
  • Page 594 <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.  preferV4 preferV6.
  • Page 595 Chapter 8: Using the Command Line Interface Option Description preferV6 Use the IPv6 addresses returned by the DNS server. Setting LAN Interface Parameters network ethernet A LAN interface configuration command begins with Enabling or Disabling the LAN Interface This command enables or disables the LAN interface. config:# network ethernet <ETH>...
  • Page 596 Chapter 8: Using the Command Line Interface Option Description eth2 ETH2 port  auto 10Mbps 100Mbps or 1000Mbps <option> is one of the options: Option Description auto System determines the optimum LAN speed through auto-negotiation. 10Mbps The LAN speed is always 10 Mbps. 100Mbps The LAN speed is always 100 Mbps.
  • Page 597 Chapter 8: Using the Command Line Interface Option Description full Full duplex: Data is transmitted in both directions simultaneously. Setting the Ethernet Authentication Method This command sets the authentication method for the selected Ethernet interface to either none or Extensible Authentication Protocol (EAP). config:# network ethernet <ETH>...
  • Page 598 Chapter 8: 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 599 Chapter 8: 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:  eth1 or eth2 <ETH> is one of the options -- Option Description eth1 ETH1 port eth2...
  • Page 600 Chapter 8: Using the Command Line Interface  true false <option2> is one of the options: 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...
  • Page 601 Chapter 8: Using the Command Line Interface 5. Select and copy the contents as illustrated below, excluding the starting line containing "BEGIN CERTIFICATE" and the ending line containing "END CERTIFICATE." MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYwNAYDVQ QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA...
  • Page 602 Chapter 8: Using the Command Line Interface config:# Removing the Uploaded Certificate or Private Key The procedures of removing an existing client certificate, client private key or CA certificate in CLI are similar. This section illustrates such a procedure for the Ethernet interface "ETH1."...
  • Page 603 Chapter 8: Using the Command Line Interface Setting Wireless Parameters You must configure wireless parameters, including Service Set Identifier (SSID), authentication method, Pre-Shared Key (PSK), and Basic Service Set Identifier (BSSID) after the wireless networking mode is enabled. network wireless A wireless configuration command begins with Note: If wireless networking mode is not enabled, the SSID, PSK and BSSID values are not applied until the wireless networking mode is...
  • Page 604 Chapter 8: Using the Command Line Interface Setting the Wireless Authentication Method This command sets the wireless authentication method to either PSK or Extensible Authentication Protocol (EAP). config:# network wireless authMethod <method> Variables:  <method> is one of the authentication methods: Method Description The authentication method is set to PSK.
  • Page 605 Chapter 8: 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. For more information, see Wireless Network Settings (on page 294).
  • Page 606 Chapter 8: 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 607 Chapter 8: Using the Command Line Interface  true false <option2> is one of the options: 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...
  • Page 608 Chapter 8: Using the Command Line Interface Configuring the Cascading Mode This command determines the cascading mode. config:# network <mode> enabled <option1> Variables:  <mode> is one of the following cascading modes. Mode Description bridge The Bridging mode, where each cascaded device is assigned a unique IP address.
  • Page 609 Chapter 8: Using the Command Line Interface If Port Forwarding mode is enabled, you must configure two more settings to finish the configuration: On ALL cascaded devices, you must configure the 'role' setting one by one. config:# network portForwarding role <option2> On the master device, you must configure the 'downstream interface' setting.
  • Page 610 Chapter 8: Using the Command Line Interface Setting the HTTP Port The commands used to configure the HTTP port settings begin with network services http Change the HTTP port: config:# network services http port <n> Enable or disable the HTTP port: config:# network services http enabled <option>...
  • Page 611 Chapter 8: Using the Command Line Interface Setting the HTTPS Port The commands used to configure the HTTPS port settings begin with network services https Change the HTTPS port: config:# network services https port <n> Enable or disable the HTTPS access: config:# network services https enabled <option>...
  • Page 612 Chapter 8: Using the Command Line Interface Option Description false The Telnet service is disabled. Changing the Telnet Port This command changes the Telnet port. config:# network services telnet port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default Telnet port is 23.
  • Page 613 Chapter 8: Using the Command Line Interface Changing the SSH Port This command changes the SSH port. config:# network services ssh port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default SSH port is 22. Determining the SSH Authentication Method This command syntax determines the SSH authentication method.
  • Page 614 Chapter 8: Using the Command Line Interface Enabling or Disabling SNMP v1/v2c This command enables or disables the SNMP v1/v2c protocol. config:# network services snmp v1/v2c <option> Variables:  <option> is one of the options: enable disable Option Description enable The SNMP v1/v2c protocol is enabled.
  • Page 615 Chapter 8: Using the Command Line Interface Setting the SNMP Write Community This command sets the SNMP read/write community string. config:# network services snmp writeCommunity <string> Variables:  <string> is a string comprising 4 to 64 ASCII printable characters.  The string CANNOT include spaces.
  • Page 616 Chapter 8: Using the Command Line Interface Enabling or Disabling Modbus This command enables or disables the Modbus protocol. config:# network services modbus enabled <option> Variables:  <option> is one of the options: true false Option Description true The Modbus agent is enabled. false The Modbus agent is disabled.
  • Page 617 Chapter 8: Using the Command Line Interface Enabling or Disabling Service Advertising This command enables or disables the zero configuration protocol, which enables advertising or auto discovery of network services. See Enabling Service Advertising (on page 324) for details. config:# network services zeroconfig <method>...

  • Page 618: Time Configuration Commands

    Chapter 8: Using the Command Line Interface Example 3 - Wireless Authentication Method The following command sets the wireless authentication method to PSK. config:# network wireless authMethod PSK Example 4 - Static IPv4 Configuration The following command enables the Static IPv4 configuration mode on the ETH1 interface.
  • Page 619 Chapter 8: 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 620 Chapter 8: 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 (on page 596).
  • Page 621 Chapter 8: Using the Command Line Interface 2. The system shows a list of time zones. Type the index number of the desired time zone and press Enter. 3. Type apply for the selected time zone to take effect. Setting the Automatic Daylight Savings Time This command determines whether the daylight saving time is applied to the time settings.

  • Page 622: Checking The Accessibility Of Ntp Servers

    Chapter 8: Using the Command Line Interface Checking the Accessibility of NTP Servers This command verifies the accessibility of NTP servers specified manually on your PX3 and then shows the result. For instructions on specifying NTP servers via CLI, see Setting NTP Parameters (on page 597).
  • Page 623 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 enabled <option> Determine the default IPv4 firewall control policy for inbound traffic: config:# security ipAccessControl ipv4 defaultPolicyIn <policy> Determine the default IPv4 firewall control policy for outbound traffic: config:# security ipAccessControl ipv4 defaultPolicyOut <policy>...
  • Page 624 Chapter 8: Using the Command Line Interface  <policy> is one of the options: accept, drop reject Option Description accept Accepts traffic from all IP addresses. drop Discards traffic from all IP addresses, without sending any failure notification to the source host. reject Discards traffic from all IP addresses, and an ICMP message is sent to the source host for...
  • Page 625 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add <direction> <insert> <rule_number> <ip_mask> <policy>  IPv6 commands Add a new rule to the bottom of the IPv6 rules list: config:# security ipAccessControl ipv6 rule add <direction> <ip_mask> <policy> Add a new IPv6 rule by inserting it above or below a specific rule: config:# security ipAccessControl ipv6 rule add <direction>...
  • Page 626 Chapter 8: Using the Command Line Interface  <insert> is one of the options: insertAbove insertBelow Option Description insertAbove Inserts the new rule above the specified rule number. Then: new rule's number = the specified rule number insertBelow Inserts the new rule below the specified rule number.
  • Page 627 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> policy <policy> Modify all contents of an IPv6 existing rule: config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> ipMask <ip_mask> policy <policy> Variables:  <direction> is one of the options: Direction Description Inbound traffic.
  • Page 628 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule delete <direction> <rule_number> IPv6 commands config:# security ipAccessControl ipv6 rule delete <direction> <rule_number> Variables:  <direction> is one of the options: Direction Description Inbound traffic. Outbound traffic.  <rule_number>...
  • Page 629 Chapter 8: 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 630 Chapter 8: 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: 1. Type the text comprising up to 10,000 ASCII characters when the CLI prompts you to enter the content.
  • Page 631 Chapter 8: 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. security loginLimits A login limitation command begins with You can combine multiple commands to modify various login limitation Multi-Command Syntax...
  • Page 632 Chapter 8: 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. Idle Timeout This command determines how long a user can remain idle before that user is forced to log out of the PX3 web interface or CLI.
  • Page 633 Chapter 8: Using the Command Line Interface config:# security userBlocking maximumNumberOfFailedLogins <value1> Determine how long a user is blocked: config:# security userBlocking blockTime <value2> Variables:  <value1> is an integer between 3 and 10, or unlimited , which sets no limit on the maximum number of failed logins and thus disables the user blocking function.
  • Page 634 Chapter 8: Using the Command Line Interface Minimum Password Length This command determines the minimum length of the password. config:# security strongPasswords minimumLength <value> Variables:  <value> is an integer between 8 and 32. Maximum Password Length This command determines the maximum length of the password. config:# security strongPasswords maximumLength <value>...
  • Page 635 Chapter 8: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter <option> Variables:  enable disable <option> is one of the options: Option Description enable At least one uppercase character is required. disable No uppercase character is required. Numeric Character Requirement This command determines whether a strong password includes at least a numeric character.
  • Page 636 Chapter 8: Using the Command Line Interface Option Description disable No special character is required. Maximum Password History This command determines the number of previous passwords that CANNOT be repeated when changing the password. config:# security strongPasswords passwordHistoryDepth <value> Variables: ...
  • Page 637 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 enabled <option> Determine the IPv6 role-based access control policy: config:# security roleBasedAccessControl ipv6 defaultPolicy <policy> Variables:  true false <option> is one of the options: Option Description true Enables the role-based access control feature. false Disables the role-based access control feature.
  • Page 638 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip> <role> <policy> Add a new IPv4 rule by inserting it above or below a specific rule: config:# security roleBasedAccessControl ipv4 rule add <start_ip> <end_ip> <role> <policy>...
  • Page 639 Chapter 8: Using the Command Line Interface Option Description insertBelow Inserts the new rule below the specified rule number. Then: new rule's number = the specified rule number +  <rule_number> is the number of the existing rule which you want to insert the new rule above or below.
  • Page 640 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> role <role> Modify an IPv6 rule's policy: config:# security roleBasedAccessControl ipv6 rule modify <rule_number> policy <policy> Modify all contents of an existing IPv6 rule: config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip>...
  • Page 641 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule delete <rule_number> Variables:  <rule_number> is the number of the existing rule that you want to remove. Enabling or Disabling Front Panel Outlet Switching This section applies to outlet-switching capable models only. The following CLI commands control whether you can turn on or off an outlet by operating the front panel display.
  • Page 642 Chapter 8: 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 643 Chapter 8: Using the Command Line Interface Examples This section illustrates several security configuration examples. 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: ...

  • Page 644: Outlet Configuration Commands

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

  • Page 646: Outlet Group Configuration Commands

    Chapter 8: Using the Command Line Interface Setting an Outlet's Cycling Power-Off Period This section applies to outlet-switching capable models only. This command determines the power-off period of the power cycling operation for a specific outlet. config:# outlet <n> cyclingPowerOffPeriod <timing> Variables: ...
  • Page 647 Chapter 8: Using the Command Line Interface Creating an Outlet Group This command creates a new outlet group. config:# outletgroup add "<name>" <members> Variables:  <name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be enclosed in quotes when it contains spaces.
  • Page 648 Chapter 8: Using the Command Line Interface config:# outletgroup delete <ID> Variables:  <ID> is an outlet group's index number.  <name> is a string comprising up to 64 ASCII printable characters. The <name> variable must be enclosed in quotes when it contains spaces.

  • Page 649: Inlet Configuration Commands

    Chapter 8: Using the Command Line Interface Powering On/Off/Cycle Outlet Groups This section applies to outlet-switching capable models only. administrator mode You must perform this operation in the . See Different CLI Modes and Prompts (on page 515). Power on one outlet group: power outletgroup <ID>...
  • Page 650 Chapter 8: Using the Command Line Interface Changing the Inlet Name This command syntax names an inlet. config:# inlet <n> name "<name>" Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always 1. The value is an integer between 1 and 50.

  • Page 651: Overcurrent Protector Configuration Commands

    Chapter 8: Using the Command Line Interface Example - Inlet Naming The following command assigns the name "AC source" to the inlet 1. If your PX3 contains multiple inlets, this command names the 1st inlet. config:# inlet 1 name "AC source" Overcurrent Protector Configuration Commands ocp.
  • Page 652 Chapter 8: Using the Command Line Interface Creating a User Profile This command creates a new user profile. config:# user create <name> <option> <roles> After performing the user creation command, the PX3 prompts you to assign a password to the newly-created user. Then: 1.
  • Page 653 Chapter 8: Using the Command Line Interface Changing a User's Password This command allows you to change an existing user's password if you have the Administrator Privileges. config:# user modify <name> password After performing the above command, PX3 prompts you to enter a new password.
  • Page 654 Chapter 8: Using the Command Line Interface Modifying a User's Personal Data You can change a user's personal data, including the user's full name, telephone number, and email address. Various commands can be combined to modify the parameters of a Multi-Command Syntax specific user profile at a time.
  • Page 655 Chapter 8: Using the Command Line Interface Enabling or Disabling a User Profile This command enables or disables a user profile. A user can log in to the PX3 only after that user's user profile is enabled. config:# user modify <name> enabled <option> Variables: ...
  • Page 656 Chapter 8: Using the Command Line Interface Modifying SNMPv3 Settings There are different commands to modify the SNMPv3 parameters of a specific user profile. You can combine all of the following commands to modify the SNMPv3 parameters at a time. See Multi-Command Syntax (on page 696).
  • Page 657 Chapter 8: Using the Command Line Interface config:# user modify <name> privacyPassPhrase After performing the above command, PX3 prompts you to enter the privacy passphrase. Determine the authentication protocol: config:# user modify <name> authenticationProtocol <option5> Determine the privacy protocol: config:# user modify <name>...
  • Page 658 Chapter 8: Using the Command Line Interface Option Description false Authentication passphrase is different from the password.  true false <option4> is one of the options: Option Description true Privacy passphrase is identical to the authentication passphrase. false Privacy passphrase is different from the authentication passphrase.
  • Page 659 Chapter 8: Using the Command Line Interface Changing Measurement Units You can change the measurement units displayed for temperatures, length, and pressure for a specific user profile. Different measurement unit commands can be combined so that you can set all measurement Multi-Command Syntax units at a time.
  • Page 660 Chapter 8: Using the Command Line Interface  pascal <option3> is one of the options: Option Description pascal This option displays the pressure value in Pascals (Pa). This option displays the pressure value in psi. 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.
  • Page 661 Chapter 8: Using the Command Line Interface Deleting a User Profile This command deletes an existing user profile. config:# user delete <name> 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 user begin with config:#...
  • Page 662 Chapter 8: Using the Command Line Interface Setting Default Measurement Units Default measurement units, including temperature, length, and pressure units, apply to the PX3 user interfaces across all users except for those whose preferred measurement units are set differently by themselves or the administrator.
  • Page 663 Chapter 8: Using the Command Line Interface Option Description feet This option displays the length or height in feet.  pascal <option3> is one of the options: Option Description pascal This option displays the pressure value in Pascals (Pa). This option displays the pressure value in psi. Examples This section illustrates several user configuration examples.

  • Page 664: Role Configuration Commands

    Chapter 8: Using the Command Line Interface Example 3 - Default Measurement Units The following command sets all default measurement units at a time. config:# user defaultpreferences preferredTemperatureUnit F preferredLengthUnit feet preferredPressureUnit psi Results:  The default temperature unit is set to Fahrenheit. ...
  • Page 665 Chapter 8: Using the Command Line Interface config:# role create <name> <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a All Privileges semi-colon.
  • Page 666 Chapter 8: Using the Command Line Interface Privilege Description changeSecuritySettings Change Security Settings changeSnmpSettings Change SNMP Settings changeUserSettings Change Local User Management changeWebcamSettings Change Webcam Configuration clearLog Clear Local Event Log firmwareUpdate Firmware Update performReset Reset (Warm Start) switchActuator* Switch Actuator switchOutlet** Switch Outlet switchOutletGroup***...
  • Page 667 Chapter 8: Using the Command Line Interface Note: The ID number of each actuator is shown in the PX3 web interface. It is an integer. ** The "switchOutlet" privilege requires an argument that is separated with a colon. The argument could be: ...
  • Page 668 Chapter 8: Using the Command Line Interface config:# role modify <name> addPrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Remove specific privileges from a role: config:# role modify <name> removePrivileges <privilege1>;<privilege2>;<privilege3>... If a specific privilege contains any arguments, add a colon and the argument(s) after that privilege. config:# role modify <name>...

  • Page 669: Authentication Commands

    Chapter 8: Using the Command Line Interface Example - Creating a Role The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup Results:  A new role "tester" is created.  Two privileges are assigned to the role: firmwareUpdate (Firmware Update) and viewEventSetup (View Event Settings).
  • Page 670 Chapter 8: Using the Command Line Interface Option Description ldap Enable LDAP authentication. radius Enable Radius authentication.  true false <option2> is one of the options: Option Description true Remote authentication is the first priority. The device will switch to local authentication when the remote authentication is not available.
  • Page 671 Chapter 8: Using the Command Line Interface config:# authentication ldap add <host> <port> <ldap_type> <security> <bind_type> <base_DN> <login_name_att> <user_entry_class> "Optional Parameters" Note: "Optional Parameters" refer to one or multiple parameters listed in the section (on page 650). They are required Optional Parameters only when your server settings need to specify these parameters.
  • Page 672 Chapter 8: Using the Command Line Interface  anonymouseBind <bind_type> is one of the bind options: , or authenticatedBind Type Description anonymousBind Enable the anonymous Bind. Bind DN and password are NOT required. authenticatedBind Enable the Bind with authentication. Bind DN and password are required. ...
  • Page 673 Chapter 8: Using the Command Line Interface Parameters To configure adDomain <AD_domain> Active Directory Domain name verifyServerCertificate <verify_cert> Certificate verification setting  After setting to true, the system will prompt you to upload a certificate. For Illustrations of Adding LDAP details, see Servers (on page 651).
  • Page 674 Chapter 8: Using the Command Line Interface config:# authentication ldap add ac-ldap.raritan.com 389 activeDirectory none anonymousBind dc=raritan,dc=com sAMAccountName user adDomain raritan.com An LDAP server with a TLS certificate uploaded: a. Enter the CLI command with the following two TLS-related options set and/or added: ...
  • Page 675 Chapter 8: Using the Command Line Interface 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. Add an LDAP server by copying an existing server's settings: config:# authentication ldap addClone <server_num>...
  • Page 676 Chapter 8: 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 677 Chapter 8: Using the Command Line Interface Parameters Description Re-upload a different certificate. certificate a. First add the "certificate" parameter to the command, and press Enter. b. The system prompts you for the input of the certificate. c. Type or copy the content of the certificate in the CLI and press Enter.
  • Page 678 Chapter 8: Using the Command Line Interface config:# authentication ldap modify 1 host 192.168.3.3 port 633 serverType activeDirectory Removing an Existing LDAP Server This command removes an existing LDAP server from the server list. config:# authentication ldap delete <server_num> Variables: ...
  • Page 679 Chapter 8: Using the Command Line Interface  <auth_port> is the authentication port number.  <acct_port> is the accounting port number.  <timeout> is the timeout value in seconds. It ranges between 1 to 10 seconds.  <retries> is the number of retries. It ranges between 0 to 5. To enter the shared secret: 1.
  • Page 680 Chapter 8: Using the Command Line Interface config:# authentication radius modify <server_num> retries <retries> Change the shared secret: config:# authentication radius modify <server_num> secret Change the priority of the specified server: config:# authentication radius modify <server_num> sortPositon <position> Tip: You can add more than one parameters to the command. For example, "...

  • Page 681: Environmental Sensor Configuration Commands

    Chapter 8: Using the Command Line Interface Removing an Existing Radius Server This command removes an existing Radius server from the server list. config:# authentication radius delete <server_num> Variables:  <server_num> is the sequential number of the specified server in the Radius server list.
  • Page 682 Chapter 8: Using the Command Line Interface Specifying the CC Sensor Type Raritan's contact closure sensor supports the connection of diverse third-party. You must specify the type of connected detector/switch for proper operation. Use this command when you need to specify the sensor type.
  • Page 683 Chapter 8: Using the Command Line Interface Setting the Y Coordinate This command specifies the Y coordinate of an environmental sensor. config:# externalsensor <n> ylabel "<coordinate>" Variables:  <n> is the ID number of the environmental sensor that you want to configure.
  • Page 684 Chapter 8: Using the Command Line Interface Changing the Sensor Description This command provides a description for a specific environmental sensor. config:# externalsensor <n> description "<description>" Variables:  <n> is the ID number of the environmental sensor that you want to configure.
  • Page 685 Chapter 8: Using the Command Line Interface Setting the Alarmed to Normal Delay for DX-PIR This command determines the value of the Alarmed to Normal Delay setting for a Raritan presence detector. config:# externalsensor <n> alarmedToNormalDelay <time> Variables:  <n> is the ID number of the environmental sensor that you want to configure.

  • Page 686: Configuring Environmental Sensors' Default Thresholds

    Chapter 8: Using the Command Line Interface Configuring Environmental Sensors' Default Thresholds You can set the default values of upper and lower thresholds, deassertion hysteresis and assertion timeout on a sensor type basis, including temperature, humidity, air pressure and air flow sensors. The default thresholds automatically apply to all environmental sensors that are newly detected or added.
  • Page 687 Chapter 8: Using the Command Line Interface config:# defaultThresholds <sensor type> assertionTimeout <as_value> Variables:  <sensor type> is one of the following numeric sensor types: Sensor types Description absoluteHumidity Absolute humidity sensors relativeHumidity Relative humidity sensors temperature Temperature sensors airPressure Air pressure sensors airFlow Air flow sensors...

  • Page 688: Sensor Threshold Configuration Commands

    Chapter 8: Using the Command Line Interface Example - Default Upper Thresholds for Temperature It is assumed that your preferred measurement unit for temperature is set to degrees Celsius. Then the following command sets the default Upper Warning threshold to 20 and Upper Critical threshold to 24 for all temperature sensors.
  • Page 689 Chapter 8: Using the Command Line Interface config:# sensor outlet <n> <sensor type> lowerCritical <option> Set the Lower Warning threshold for an outlet sensor: config:# sensor outlet <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an outlet sensor: config:# sensor outlet <n>...
  • Page 690 Chapter 8: Using the Command Line Interface Option Description A numeric Sets a value for the specified threshold of a value specific outlet sensor and enables this threshold at the same time.  <hy_value> is a numeric value that is assigned to the hysteresis for "To De-assert"...
  • Page 691 Chapter 8: Using the Command Line Interface config:# sensor outletgroup <ID> <sensor type> hysteresis <hy_value> Set the assertion timeout for an outlet group sensor: config:# sensor outletgroup <ID> <sensor type> assertionTimeout <as_value> Variables:  <ID> is an outlet group's index number. ...
  • Page 692 Chapter 8: Using the Command Line Interface Commands for Inlet Sensors sensor inlet A sensor configuration command for inlets begins with You can configure various inlet sensor threshold settings at a time by Multi-Command Syntax combining multiple commands. See (on page 696).
  • Page 693 Chapter 8: Using the Command Line Interface Sensor type Description voltage Voltage sensor activePower Active power sensor apparentPower Apparent power sensor powerFactor Power factor sensor activeEnergy Active energy sensor unbalancedCurrent Unbalanced load sensor lineFrequency Line frequency sensor phaseAngle Inlet phase angle sensor Note: If the requested sensor type is not supported, the "Sensor is not available"...
  • Page 694 Chapter 8: Using the Command Line Interface Sensor type Description reactivePower Reactive power sensor displacementPowerFa Displacement power factor sensor ctor residualCurrent RCM current sensor  For Type A, it is the sensor that detects residual AC current.  For Type B, it is the sensor that detects both residual AC and DC current.
  • Page 695 Chapter 8: Using the Command Line Interface config:# sensor inletpole <n> <p> <sensor type> hysteresis <hy_value> Set the Inlet Pole's Assertion Timeout: config:# sensor inletpole <n> <p> <sensor type> assertionTimeout <as_value> Variables:  <n> is the number of the inlet whose pole sensors you want to configure.
  • Page 696 Chapter 8: Using the Command Line Interface Option Description A numeric Sets a value for the specified threshold of the value specified inlet pole sensor and enables this threshold at the same time.  <hy_value> is a numeric value that is assigned to the hysteresis for "To De-assert"...
  • Page 697 Chapter 8: 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 Multi-Command Syntax time by combining multiple commands. See page 696).
  • Page 698 Chapter 8: Using the Command Line Interface config:# sensor ocp <n> <sensor type> assertionTimeout <as_value> Variables:  <n> is the number of the overcurrent protector that you want to configure.  <sensor type> is one of the following sensor types: Sensor type Description current...
  • Page 699 Chapter 8: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> upperCritical <option> Set the Upper Warning threshold for an environmental sensor: config:# sensor externalsensor <n> <sensor type> upperWarning <option> Set the Lower Critical threshold for an environmental sensor: config:# sensor externalsensor <n>...
  • Page 700 Chapter 8: Using the Command Line Interface Sensor types Description airFlow Air flow sensors vibration Vibration sensors Note: If the specified sensor type does not match the type of the specified environmental sensor, this error message appears: "Specified sensor type 'XXX' does not match the sensor's type (<sensortype>),"...
  • Page 701 Chapter 8: Using the Command Line Interface Example 2 - Warning Thresholds for Inlet Sensors The following command sets both the Upper Warning and Lower Warning thresholds for the inlet 1 RMS current. config:# sensor inlet 1 current upperWarning 20 lowerWarning 12 Results: ...

  • Page 702: Actuator Configuration Commands

    Chapter 8: Using the Command Line Interface Actuator Configuration Commands An actuator configuration command begins with actuator . You can configure the name and location parameters of an individual actuator. You can configure various parameters for one actuator at a time. See Multi-Command Syntax (on page 696).

  • Page 703: Server Reachability Configuration Commands

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

  • Page 707: Energywise Configuration Commands

    Chapter 8: Using the Command Line Interface EnergyWise Configuration Commands An EnergyWise configuration command begins with energywise Enabling or Disabling EnergyWise This command syntax determines whether the Cisco EnergyWise ® endpoint implemented on the PX3 is enabled. config:# energywise enabled <option> Variables: ...
  • Page 708 Chapter 8: Using the Command Line Interface Specifying the EnergyWise Secret This command syntax specifies the password (secret) to enter the Cisco ® EnergyWise domain. config:# energywise secret <password> Variables:  <password> is a string comprising up to 127 ASCII printable characters.

  • Page 709: Asset Management Commands

    Chapter 8: Using the Command Line Interface Example - Setting Up EnergyWise The following command sets up two Cisco EnergyWise-related features. ® config:# energywise enabled true port 10288 Results:  The EnergyWise feature implemented on the PX3 is enabled.  The UDP port is set to 10288.
  • Page 710 Chapter 8: Using the Command Line Interface Specifying the Number of Rack Units This command syntax specifies the total number of rack units on an asset strip connected to the PX3 device. config:# assetStrip <n> numberOfRackUnits <number> Note: A rack unit refers to a tag port on the asset strips. Variables: ...
  • Page 711 Chapter 8: Using the Command Line Interface Specifying the Rack Unit Numbering Offset This command syntax specifies the starting number of rack units on the asset strips connected to the PX3 device. config:# assetStrip <n> rackUnitNumberingOffset <number> Variables:  <n> is the number of the FEATURE port where the selected asset strip is physically connected.
  • Page 712 Chapter 8: Using the Command Line Interface Setting LED Colors for Connected Tags This command syntax sets the LED color for all rack units on the asset strip #1 to indicate the presence of a connected asset tag. config:# assetStrip <n> LEDColorForConnectedTags <color> Variables: ...
  • Page 713 Chapter 8: Using the Command Line Interface Naming a Rack Unit This command syntax assigns or changes the name of the specified rack unit on the specified asset strip. config:# rackUnit <n> <rack_unit> name "<name>" Variables:  <n> is the number of the FEATURE port where the selected asset strip is physically connected.
  • Page 714 Chapter 8: Using the Command Line Interface Mode Description manual This option enables selection of a different LED color and LED mode for the specified rack unit. Setting an LED When this option is selected, see Color for a Rack Unit Setting (on page 692) and an LED Mode for a Rack Unit...
  • Page 715 Chapter 8: Using the Command Line Interface Setting an LED Mode for a Rack Unit This command syntax sets the LED mode for a specific rack unit on the specified asset strip. You need to set a rack unit's LED mode only when the LED operation mode of this rack unit has been set to "manual."...

  • Page 716: Serial Port Configuration Commands

    Chapter 8: Using the Command Line Interface Example 2 - Rack Unit Naming The following command assigns the name "Linux server" to the rack unit whose index number is 25 on the asset sensor#1. config:# rackUnit 1 25 name "Linux server" Serial Port Configuration Commands serial A serial port configuration command begins with...
  • Page 717 Chapter 8: Using the Command Line Interface Forcing the Device Detection Mode This command forces the serial port on the PX3 to enter a specific device detection mode. config:# serial deviceDetectionType <mode> Variables:  <mode> is one of the detection modes: automatic forceConsole forceAnalogModem,...

  • Page 718: Multi-Command Syntax

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

  • Page 719: Load Shedding Configuration Commands

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

  • Page 720: Enabling Or Disabling Load Shedding

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

  • Page 721: Power Control Operations

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

  • Page 722: Turning Off The Outlet(S)

    Chapter 8: Using the Command Line Interface Option Description A range of Switches ON multiple, consecutive outlets. outlets with a For example, to specify 6 consecutive outlets -- 3, hyphen in 4, 5, 6, 7, 8, type: between outlets 3-8. If you entered the command without "/y", a message appears, prompting you to confirm the operation.

  • Page 723: Power Cycling The Outlet(S)

    Chapter 8: Using the Command Line Interface Option Description A specific outlet Switches OFF the specified outlet. number A comma- Switches OFF multiple, inconsecutive or separated list consecutive outlets. of outlets For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and 15, type: outlets 2,4,9,11-13,15.
  • Page 724 Chapter 8: Using the Command Line Interface Option Description A specific outlet Power cycles the specified outlet. number A comma- Power cycles multiple, inconsecutive or separated list consecutive outlets. of outlets For example, to specify 7 outlets -- 2, 4, 9, 11, 12, 13 and 15, type: outlets 2,4,9,11-13,15.

  • Page 725: Canceling The Power-On Process

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

  • Page 726: Switching On An Actuator

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

  • Page 727: Example - Turning On A Specific Actuator

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

  • Page 728: Restarting The Pdu

    Chapter 8: Using the Command Line Interface Restarting the PDU This command restarts the PX3. It is not a factory default reset. To restart the PX3: 1. Ensure you have entered administrator mode and the # prompt is displayed. 2. Type either of the following commands to restart the PX3. reset unit -- OR -- reset unit /y...

  • Page 729: Resetting To Factory Defaults

    Chapter 8: Using the Command Line Interface reset activeEnergy outlet <outlet_n> /y To reset one outlet group's active energy readings: reset activeEnergy outletgroup <ID> -- OR -- reset activeEnergy outletgroup <ID> /y If you entered the command without "/y", a message appears prompting you to confirm the operation.

  • Page 730: Entering Diagnostic Mode

    Chapter 8: Using the Command Line Interface Entering Diagnostic Mode Diagnostic commands function in the diagnostic mode only. To enter the diagnostic mode: 1. Enter either of the following modes:  Administrator mode: The # prompt is displayed.  User mode: The > prompt is displayed. 2.
  • Page 731 Chapter 8: Using the Command Line Interface Showing Network Connections This command syntax displays network connections and/or status of ports. diag> netstat <option> Variables:  <option> is one of the options: ports connections Option Description ports Shows TCP/UDP ports. connections Shows network connections.

  • Page 732: Retrieving Previous Commands

    Chapter 8: Using the Command Line Interface Options Description size <number2> Determines the packet size. <number2> is an integer number in bytes between 1 and 65468. timeout <number3> Determines the waiting period before timeout. <number3> is an integer number in seconds ranging from 1 to 600.

  • Page 733: Automatically Completing A Command

    Chapter 8: Using the Command Line Interface Automatically Completing a Command A CLI command always consists of several words. You can easily enter a command by typing first word(s) or letter(s) and then pressing Tab or Ctrl+i instead of typing the whole command word by word. To have a command completed automatically: 1.

  • Page 734: Logging Out Of Cli

    Chapter 8: Using the Command Line Interface Logging out of CLI After completing your tasks using the CLI, always log out of the CLI to prevent others from accessing the CLI. To log out of the CLI: 1. Ensure you have entered administrator mode and the # prompt is displayed.

  • Page 735: Chapter 9 Using Scp Commands

    Chapter 9 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 ............... 713 Bulk Configuration via SCP ..............714 Backup and Restore via SCP..............

  • Page 736: Bulk Configuration Via Scp

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

  • Page 737: Backup And Restore Via Scp

    Chapter 9: Using SCP Commands 2. Type the user password when prompted. 3. 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: ...
  • Page 738 Chapter 9: Using SCP Commands  <user name> is the "admin" or any user profile with Administrator Privileges  <device ip> is the IP address or hostname of the PX3 whose settings you want to back up. 2. Type the user password when prompted. 3.

  • Page 739: Downloading Diagnostic Data Via Scp

    Chapter 9: Using SCP Commands Downloading Diagnostic Data via SCP You can download the diagnostic data via SCP. To download the diagnostic data via SCP: 1. Type one of the following SCP commands and press Enter. Scenario 1: Use the default SCP port and default filename ...

  • Page 740: Uploading Or Downloading Raw Configuration Data

    Chapter 9: Using SCP Commands  <port> is the current SSH/SCP port number, or the port number of a specific slave device in the Port-Forwarding chain.  <filename> is the new filename of the downloaded file. 2. Type the password when prompted. 3.
  • Page 741 Chapter 9: 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 raw configuration file's default filename "raw_config.txt" is wanted. Then add a dot (.) in the end of the SCP command as shown below.
  • Page 742 Chapter 9: Using SCP Commands  If you do NOT specify a new filename in the command, such as Scenarios 1 or 2, the downloaded file's default name is "raw_config.txt."  If you specify a new filename in the command, such as Scenarios 3 or 4, the downloaded file is renamed accordingly.
  • Page 743 Chapter 9: Using SCP Commands  <user name> is the "admin" or any user profile with Administrator Privileges.  <device ip> is the IP address or hostname of the PX3 where you want to upload the specified file.  <port> is the current SSH/SCP port number, or the port number of a specific slave device in the Port-Forwarding chain.

  • Page 744: Keys That Cannot Be Uploaded

    Chapter 9: Using SCP Commands Windows PSCP commands: PSCP in Windows works in a similar way to the SCP.  pscp -P <port> <user name>@<device ip>:/raw_config.txt <filename>  pscp -P <port> <CSV file> <config file> <user name>@<device ip>:/raw_config_update /match=<col> Alternative of bulk configuration via SCP: Both methods of uploading 'bulk configuration' file or 'raw configuration' file via SCP can serve the purpose of bulk configuration.

  • Page 745: Chapter 10 In-Line Monitors

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

  • Page 746: Flexible Cord Installation Instructions

    Chapter 10: In-Line Monitors 5. Examine the branch circuit receptacle that will supply electric power to this product. Make sure the receptacle’s power lines, neutral and protective earth ground pins are wired correctly and are the correct voltage and phase. Make sure the branch circuit receptacle is protected by a suitably rated fuse or circuit breaker.

  • Page 747: Flexible Cord Selection

    Chapter 10: In-Line Monitors Flexible Cord Selection  The preferred flexible cable is type SOOW, 600V, 90°C or 105°C. Consult Raritan before using a different flexible cable type.  The rated ampacity of the flexible cord must be greater than or equal to the Raritan product’s rated ampacity marked on its nameplate.

  • Page 748: Derating A Raritan Product

    Chapter 10: In-Line Monitors Derating a Raritan Product Lower rated plugs, receptacles and flexible cords may be connected to a Raritan product. This results in a derated (reduced) ampacity rating for the product. Derating guidelines: 1. Choose the plug and use its rated ampacity to determine the derated ampacity.

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

    Chapter 10: In-Line Monitors Wiring of 3-Phase In-Line Monitors 3-phase in-line monitors contain 4-pole wiring terminal blocks (L1, L2, L3, N) to monitor 5-wire (4P+PE) 3-phase wye connections. Delta wired 4-wire (3P+PE) 3-phase connections are also permitted (no wire connected to the terminal block neutral “N”). No additional hardware or firmware configuration is required to specify whether the connection is 5-wire wye or 4-wire delta.
  • Page 750 Chapter 10: In-Line Monitors One-channel in-line monitor Zero U PDU Make sure to locate the ground wire mounting stud(s). There is a separate ground wire mounting stud for each terminal block. Each flexible cord MUST have its green (or green/yellow) ground wire bonded to a ground wire mounting stud.
  • Page 751 Chapter 10: In-Line Monitors For in-line monitors, make sure to identify the inlet terminal blocks (rear of monitor) and outlet terminal blocks (front of monitor). Each inlet terminal block has a corresponding outlet terminal block. Number Description Inlets (labeled LINE) Outlets (labeled LOAD) 2.
  • Page 752 Chapter 10: In-Line Monitors Temporarily hand tighten the gland nut and verify the cord cannot be twisted or pushed or pulled in the gland. Do not proceed if hand tightening results in a loose cord. In some models, especially in-line monitors, the flexible cord’s diameter may be too small for the cable gland.
  • Page 753 Chapter 10: In-Line Monitors 6. Fasten the ring terminals of all remaining wires to the terminal block and tighten each using a torque screwdriver. The appropriate torque settings vary according to the screw size. Screw size Torque setting (N·m) Tolerance 0.49 1.27 1.96...
  • Page 754 Chapter 10: In-Line Monitors  If your PDU is inlet metered, such as PDU models PX2-1nnn and PX2-2nnn (where n is a number), you must pass each line cord wire through the correct CT in the correct direction. Each CT is labeled and contains a direction arrow.

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

    Chapter 10: In-Line Monitors 8. Re-install the PDU wiring access panel or in-line monitor cover plate. This completes internal wiring of the Raritan product. 9. For in-line monitors, fasten the receptacles to the outlet flexible cords following the manufacturer’s instructions. 10.

  • Page 756: Dashboard Page

    Chapter 10: In-Line Monitors Dashboard Page An in-line monitor's Dashboard page looks slightly different from a regular PX3 device's Dashboard page. Note: Depending on your model, elements shown on your page may appear slightly different from this image.
  • Page 757 Chapter 10: In-Line Monitors Number Section Content  Overview of each outlet's power data -- in the above diagram, Outlet(s) there are 4 outlets.  A current bar per outlet, which changes colors to indicate the RMS current state -- normal (green), warning (yellow) or critical (red).
  • Page 758 Chapter 10: In-Line Monitors 2. Click its title, such as Inlet/Outlet 1, Inlet/Outlet 2, and the like. The selected outlet's page opens. To view the inlet power chart: 1. To view the power chart of one or multiple outlets, select one or multiple outlet checkboxes below the diagram.
  • Page 759 Chapter 10: In-Line Monitors  Available data types include RMS current, RMS voltage, active power and apparent power.  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.
  • Page 760 Chapter 10: In-Line Monitors  When the data of multiple outlets is shown in the chart, simply hover your mouse over any outlet's data line. Values of outlets display simultaneously, marked with corresponding colors.

  • Page 761: Inlets/Outlets Page

    Chapter 10: In-Line Monitors Inlets/Outlets Page On the Inlets/Outlets page, you can:  View each outlet's power data (which is also each inlet's power data)  Configure each inlet/outlet as needed, such as customizing outlet names, setting thresholds or resetting energy. Outlet thresholds, when enabled, help you identify whether the outlet enters the warning or critical level.
  • Page 762 Chapter 10: In-Line Monitors 2. A list of inlets/outlets is displayed. Click "Show Details" of the desired inlet/outlet. 3. The individual inlet/outlet page opens. On this page, you can:  View details, such as its receptacle type  View all of its sensors data ...

  • Page 763: Maximum Ambient Operating Temperature

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

  • Page 764: Feature Rj-45 Port Pinouts

    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 bus RS485_DN bi-directional Data Negative of the RS-485 bus ― Signal Ground 1-wire ― 1-wire signal for Raritan environmental sensor packages...

  • Page 765: Expansion Rj-45 Port Pinouts

    Appendix A: Specifications RJ-45 Pin/signal definition Pin No. Signal Direction Description intended for use with 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 ―...

  • Page 766: 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 767 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 768 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 769 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 770: 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 771: System And Usb Requirements

    Appendix C: Configuration or Firmware Upgrade with a USB Drive 4. Plug the USB drive into the USB-A port of the PX3. 5. The initial message shown on the front panel display depends on the first task performed by the PX3. ...

  • Page 772: Configuration Files

    Appendix C: Configuration or Firmware Upgrade with a USB Drive USB drive requirements:  The drive contains either a single partition formatted as a Windows FAT32 filesystem, or NO partition tables (that is, a superfloppy-formatted drive).  fwupdate.cfg The drive contains a configuration file called in its root fwupdate.cfg directory.
  • Page 773 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 774 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 775 Appendix C: Configuration or Firmware Upgrade with a USB Drive For example, mac:7 instructs the PX3 to search for the MAC address in the 7th column of the "devices.csv" file.  The default value is serial:1, making the PX3 search for its serial number in the first column.
  • Page 776 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. switch_outlets  This feature works on outlet-switching capable models only.  Switch on or off specific outlets. ...
  • Page 777 Appendix C: Configuration or Firmware Upgrade with a USB Drive  Script output will be recorded to a log file -- <BASENAME_OF_SCRIPT>.<SERIAL_NUMBER>.log. Note this log file's size is limited on DHCP/TFTP.  A DHCP/TFTP-located script has a timeout of 60 seconds. After that duration the script will be removed.

  • Page 778: 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"...
  • Page 779 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.
  • Page 780 Appendix C: Configuration or Firmware Upgrade with a USB Drive To encrypt any settings: Data You can encrypt the value of any setting in the config.txt. See Encryption in 'config.txt' (on page 761). To restore a specific setting to factory default: Add "delete:"...

  • Page 781: Devices.csv

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

  • Page 782: 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 783: Data Encryption In 'Config.txt

    Appendix C: Configuration or Firmware Upgrade with a USB Drive fwupdate.cfg 6. Verify that at least 3 configuration files are created - config.txt devices.csv . You are ready to configure or upgrade any Configuration or Firmware Upgrade with PX3 with these files. See a USB Drive (on page 748).

  • Page 784: Firmware Upgrade Via Usb

    Appendix C: Configuration or Firmware Upgrade with a USB Drive Illustration: In this example, we will encrypt the word "private", which is the value of the SNMP write community in the "config.txt" file. 1. In the CLI, type the following command to encrypt "private." 2.
  • Page 785 Appendix C: Configuration or Firmware Upgrade with a USB Drive 4. The PX3 performs the firmware upgrade.  The front panel display shows the firmware upgrade progress. Tip: You can remove the USB drive and plug it into another PX3 for firmware upgrade when the firmware upgrade message displays.
  • Page 786 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 787: Appendix D Bulk Configuration Or Firmware Upgrade Via Dhcp/Tftp

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

  • Page 788: Tftp Requirements

    Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 6. Re-boot these PX3 devices. The DHCP server will execute the commands in the "fwupdate.cfg" file on the TFTP server to configure or upgrade those PX3 devices supporting DHCP in the same network. DHCP will execute the "fwupdate.cfg"...
  • Page 789 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Click Add to add a new vendor class. c. 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 790 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. 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.
  • Page 791 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Select Raritan PDU in the "Option class" field. b. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.
  • Page 792 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP c. Click Add to add the second option. Type "pdu-update-control-file" in the Name field, select String as the data type, and type 2 in the Code field. d. Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field.
  • Page 793 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The policy is named "PDU" in this illustration. c. Click Add to add a new condition.
  • Page 794 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select the vendor class "Raritan PDU" in the Value field, click Add and then Ok. e. Click Next.
  • Page 795 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 796 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP g. Select the "Raritan PDU" in the "Vendor class" field, select "001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv4 address in the "IP address" field.
  • Page 797 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 798: 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. Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg"...
  • Page 799 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Right-click the IPv6 node in DHCP to select Define Vendor Classes. b. Click Add to add a new vendor class. c. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)"...
  • Page 800 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 2. Add three options to the "Raritan PDU 1.0" vendor class. a. Right-click the IPv6 node in DHCP to select Set Predefined Options.
  • Page 801 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select Raritan PDU 1.0 in the "Option class" field. c. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the Code field.
  • Page 802 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. e. 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 803 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP c. Select "Raritan PDU 1.0" in the "Vendor class" field, select "00001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv6 address in the "IPv6 address" field.
  • Page 804 Appendix D: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select "00002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. e. Select "00003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third fwupdate.cfg option/code is the magic cookie to prevent the commands from being executed repeatedly.

  • Page 805: 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. Therefore, you must modify the magic cookie's value in DHCP when intending to execute the "fwupdate.cfg"...
  • Page 806 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. 3. Set the following three sub-options in the "vendor-encapsulated-options" (option 43). ...

  • Page 807: 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: 1. Locate and open the "dhcpd6.conf" file of the DHCP server. 2.
  • Page 808 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 809: 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 810: Download Via Curl

    Appendix E: Raw Configuration Upload and Download http(s)://<user>:<password>@<device IP>/cgi-bin/raw_config_download.cgi 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 811: Uploading Raw Configuration

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

  • Page 812: 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 813 Appendix E: Raw Configuration Upload and Download Parameter Description Refer to the above table for explanation. <user>,  For device-specific settings in the <config <password>, file>, refer each device-specific <device IP>, configuration key to a specific column in the <config config.txt <dev_list file>.

  • Page 814: Curl Upload Return Codes

    Appendix E: Raw Configuration Upload and Download Curl Upload Return Codes After performing raw configuration Upload via Curl (on page 790), curl will return a code to indicate the result of the file upload. Code Description Operation was successful. An internal error occurred. A parameter error occurred.

  • Page 815: 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 816: Using The Cli Command

    Appendix F: Resetting to Factory Defaults  PX3 Zero U: 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 Using restoring the PX3 to factory defaults.
  • Page 817 Appendix F: Resetting to Factory Defaults 2. At the Username prompt in the CLI, type "factorydefaults" and press Enter. Username: factorydefaults 3. Type y on a confirmation message to perform the reset.
  • Page 818 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 819: Appendix G Px3 Models With Residual Current Monitoring

    Appendix G: PX3 Models with Residual Current Monitoring RCM Current Sensor The RCM current sensor detects current imbalance which indicates current is flowing to ground. The sensor cannot determine the exact location. It just reports the sum of all residual current in the PDU and devices plugged into it, which is either per inlet or per inlet pole, depending on the model.

  • Page 820: Rcm State Sensor

    Appendix G: PX3 Models with Residual Current Monitoring RCM State Sensor The RCM state sensor reports events based on residual current thresholds or RCM self-test failure. The RCM state is always determined by the magnitude of "total" residual current values per inlet or per inlet pole as explained below. ...

  • Page 821: Compliance With Iec 62020

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

  • Page 822: Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring IEC 62020 specification PX3 with RCM characteristics Ability to directly Directionally non-discriminating. discriminate Rated residual operating 0.5A (highest value). current Residual currents with Model dependent. direct current components  Models ending in M5 are Type A. ...

  • Page 823: 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, Menu configure or run self-test, click Inlet in the (on page 155). 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 824 Appendix G: PX3 Models with Residual Current Monitoring To check RCM state and current on the Inlet page: 1. Click Inlet. See Web Interface Operations for RCM (on page 801). 2. Locate the Residual Current Monitor section on the Inlet page. ...
  • Page 825 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"...

  • Page 826: Setting Rcm Current Thresholds

    Appendix G: PX3 Models with Residual Current Monitoring Setting RCM Current Thresholds The RCM current thresholds define the critical, warning and normal range of residual current.  For Type A, RCM current thresholds are the thresholds of residual AC current. ...

  • Page 827: Scheduling Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring For a model that detects residual current per inlet pole, the above fields are available for each pole. Configure them one by one. d. Click Save. 4. Click 'Start Self Test' to run RCM self-test. Scheduling RCM Self-Test You can have the PX3 run RCM self-test automatically at a regular time interval or on a specific date and time.

  • Page 828: Setting Rcm Dc Current Thresholds

    Appendix G: PX3 Models with Residual Current Monitoring  To disable this function, deselect the "Perform RCM self-test" checkbox.  To enable this function, select the "Perform RCM self-test" checkbox. 3. Click Save. Setting RCM DC Current Thresholds RCM DC current sensors are available on Type B models only. See RCM Current Sensor (on page 797).

  • Page 829: Front Panel Operations For Rcm

    Appendix G: PX3 Models with Residual Current Monitoring  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 Sensor Threshold Settings timeout, see (on page 893).

  • Page 830: Checking Rcm States And Current

    Appendix G: PX3 Models with Residual Current Monitoring  RCM State: Critical.  Residual Current: Residual current value in Amps.  For Type A, it is the sum of residual AC current.  For Type B, it is the sum of residual AC and DC current. ...

  • Page 831: Running Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring  Residual Current: Residual current value in Amps.  For Type A, it is the sum of residual AC current.  For Type B, it is the sum of residual AC and DC current. ...
  • Page 832 Appendix G: PX3 Models with Residual Current Monitoring  If your PDU shows multiple inlets or inlet poles, press to select the desired inlet or inlet pole and press 4. Press to perform RCM self-test on the selected inlet. 5. A confirmation message displays. By default, Yes is selected. ...

  • Page 833: Rcm Snmp Operations

    Appendix G: PX3 Models with Residual Current Monitoring 6. After completing the RCM self-test, the LCD display indicates the RCM self-test result: passed or failed. 7. Press to return to the RCM information page. 8. Do one of the following: ...

  • Page 834: Rcm Residual Current And State Objects

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

  • Page 835: 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 836: Setting Rcm Current Thresholds

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

  • Page 837: Setting Front Panel Rcm Self-Test

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

  • Page 838: Running Rcm Self-Test

    Appendix G: PX3 Models with Residual Current Monitoring Running RCM Self-Test You can perform RCM self-test for a specific inlet via CLI. After the self-test finishes, the test result is shown: pass or fail. For Type B "M18" models, the self-test feature will perform tests on all poles of the selected inlet simultaneously.

  • Page 839: 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 840: 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 841 Appendix H: Old Generations of PX3 Models Section Information shown The selected mode and target, such as INLET 1, OUTLET 1, SENSOR 1, SENSOR 2, and so on. The following information is displayed:  Readings, data or state of the selected target. ...

  • Page 842: Operating The Lcd Display

    Appendix H: Old Generations of PX3 Models - Asset Strip mode, indicated by the word ASSET, for showing the asset strip information Overview of the LCD Display (on page 818) for details.  FUNC (Function) button for switching between different data of the selected target, such as the current, voltage or power readings of a particular outlet Operating the LCD Display...
  • Page 843 Appendix H: Old Generations of PX3 Models 3. Press the FUNC button to switch between voltage, active power and current readings of the selected target.  A is displayed for the current reading. A means Amp.  V is displayed for the voltage reading. V means Volt. ...
  • Page 844 Appendix H: Old Generations of PX3 Models Inlet Information The Inlet mode is displayed as "INLET" on the LCD display. Below illustrates the inlet information shown on the LCD display. Section Example information The selected target is INLET 1. This inlet's L1 current reading is 23 amps. The selected inlet line is L1.
  • Page 845 Appendix H: Old Generations of PX3 Models To display the unbalanced load and active power of a 3-phase inlet: 1. Switch to the current reading of any inlet line. 2. Press the Up or Down button until "W" or "%" is displayed to the right of the LCD display.
  • Page 846 Appendix H: Old Generations of PX3 Models To display the overcurrent protector information: 1. Press the MODE button until the word "CB" or "FUSE" is displayed. 2. In the Overcurrent Protector mode, press the Up or Down button until the desired overcurrent protector's number is displayed at the top of the LCD display.
  • Page 847 Appendix H: Old Generations of PX3 Models Section Example information "MASTER" indicates the PX3 is the master device in a cascading chain. For a slave device, it shows "SLAVE" instead. Note: "MASTER/SLAVE" information is only available in Port Forwarding mode. If you connect your PX3 to the wireless network, a Wi-Fi icon is displayed at the bottom-right corner.
  • Page 848 Appendix H: Old Generations of PX3 Models Section Example information "M" indicates that the displayed information is the MAC address. "MASTER" indicates the PX3 is the master device in a cascading chain. For a slave device, it shows "SLAVE" instead. Note: "MASTER/SLAVE"...
  • Page 849 Appendix H: Old Generations of PX3 Models  When outlet 1 has been powered on, the word 'on' is displayed as shown below.  When outlet 1 has been powered off, the word "oFF" is displayed instead. 2. Press the Up or Down button to select the desired outlet. The selected outlet's number is displayed at the top of the LCD display.
  • Page 850 Appendix H: Old Generations of PX3 Models Note: If you press a different button in this step, for example, pressed the Down button in step 4 but the Up button in step 5, the outlet switching operation is not confirmed and the LCD display will return to the messages in step 3.
  • Page 851 Appendix H: Old Generations of PX3 Models Number Example information The measurement unit is (degrees in Celsius). To display the environmental sensor information: 1. Press the MODE button until this product enters the Sensor mode, as indicated by "SENSOR" at the top of the LCD display. 2.
  • Page 852 Appendix H: Old Generations of PX3 Models States Description The actuator is turned off. Note: Numeric sensors show both numeric readings and sensor states to indicate environmental or internal conditions while state sensors show sensor states only to indicate state changes. 5.
  • Page 853 Appendix H: Old Generations of PX3 Models Note: Some alphabets cannot be properly displayed due to the LCD display restriction. For example, Q looks like 9, Z looks like 2, and M looks like . Check the sensor's label or the web interface when you have doubts.
  • Page 854 Appendix H: Old Generations of PX3 Models 2. By default the PX3 selects the asset strip connected to the first FEATURE port so it shows "1" at the top. Because the PX3 has only one FEATURE port, "1" is the only option. 3.
  • Page 855 Appendix H: Old Generations of PX3 Models To retrieve the device's cascading position information: 1. Press the MODE button to enter the Device mode, indicated by a 'd' in at the top left of the display. 2. Press the FUNC button until "CA" is displayed at the top right of the display.
  • Page 856 Appendix H: Old Generations of PX3 Models RCM Information If your "old" PX3 model supports residual current monitoring (RCM), this information is available in the front panel LCD display. For more information on RCM, see PX3 Models with Residual Current Monitoring (on page 796).
  • Page 857 Appendix H: Old Generations of PX3 Models Below illustrates the residual current information shown on the LCD display. Section Example information The inlet containing RCM sensor is INLET 1. This residual current is 0 mA. ALARM always displays for residual current sensor. LEAK always displays for residual current sensor.

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

    Appendix H: Old Generations of PX3 Models Section Example information 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. Note: To disable or enable this front panel function, see Disabling or (on page 805).

  • Page 859: 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: a. Determine user accounts and roles (groups) intended for the PX3 b.

  • Page 860: 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 861: 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:  Wired The DNS server settings have been configured properly. See Network Settings Role of a DNS Server (on page 287) and...
  • Page 862 Appendix I: LDAP Configuration Illustration Field/setting Do this... Bind DN, Skip the three fields because of anonymous bind. Bind password, Confirm bind password Base DN for search Type dc=techadssl,dc=com as the starting point where your search begins on the AD server. Login Name Attribute Ensure the field is set to sAMAccountName because the LDAP server is Microsoft Active Directory.
  • Page 863 Appendix I: LDAP Configuration Illustration 4. Click Add Server.The LDAP server is saved. 5. In the Authentication Type field, select LDAP. 6. Click Save. The LDAP authentication is activated.

  • Page 864: 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 865 Appendix I: LDAP Configuration Illustration c. 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. 3.
  • Page 866 Appendix I: LDAP Configuration Illustration c. 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 867: Appendix J Updating The Ldap Schema

    Appendix J Updating the LDAP Schema In This Chapter Returning User Group Information ............845 Setting the Registry to Permit Write Operations to the Schema ... 846 Creating a New Attribute................. 846 Adding Attributes to the Class ..............847 Updating the Schema Cache ..............849 Editing rciusergroup Attributes for User Members .......

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

  • Page 869: Adding Attributes To The Class

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

  • Page 871: Updating The Schema Cache

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

  • Page 874: 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: Adding Radius 1.
  • Page 875 Appendix K: RADIUS Configuration Illustration b. On the NPS, configure Connection Request Policies and the standard Step B: Configure Connection Policies and Standard attribute. See Attributes (on page 857). Some configuration associated with Microsoft Active Directory (AD) is AD-Related Configuration also required for RADIUS authentication.
  • Page 876 Appendix K: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX3. In this example, they are 1812 and 1813. Then close this dialog.
  • Page 877 Appendix K: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PX3 to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
  • Page 878 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. 5. Click OK.
  • Page 879 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 880 Appendix K: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
  • Page 881 Appendix K: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
  • Page 882 Appendix K: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
  • Page 883 Appendix K: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the PX3 IP address -- 192.168.56.29 , and click OK. 7. Click Next in the New Connection Request Policy dialog. 8. Select "Authenticate requests on this server" because a local NPS server is used in this example.
  • Page 884 Appendix K: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options:  Override network policy authentication settings  CHAP -- the PX3 uses "CHAP" in this example...
  • Page 885 Appendix K: RADIUS Configuration Illustration Note: If your PX3 uses PAP, then select "PAP."...
  • Page 886 Appendix K: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
  • Page 887 Appendix K: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
  • Page 888 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...
  • Page 889 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 890 Appendix K: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
  • Page 891 Appendix K: RADIUS Configuration Illustration 15. Click Next to continue.

  • Page 892: 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 893: 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 894 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.
  • Page 895 Appendix K: RADIUS Configuration Illustration 2. Right-click NPS (Local), and select Properties. Verify the authentication and accounting port numbers shown in the properties dialog are the same as those specified on your PX3. In this example, they are 1812 and 1813. Then close this dialog.
  • Page 896 Appendix K: RADIUS Configuration Illustration 3. Under "RADIUS Clients and Servers," right-click RADIUS Client and select New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PX3 to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b.
  • Page 897 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. 5. Click OK.
  • Page 898 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 899 Appendix K: RADIUS Configuration Illustration 2. Right-click Connection Request Policies and select New. The New Connection Request Policy dialog appears. 3. Type a descriptive name for identifying this policy in the "Policy name" field.
  • Page 900 Appendix K: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
  • Page 901 Appendix K: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
  • Page 902 Appendix K: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the PX3 IP address -- 192.168.56.29 , and click OK. 7. Click Next in the New Connection Request Policy dialog. 8. Select "Authenticate requests on this server" because a local NPS server is used in this example.
  • Page 903 Appendix K: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options:  Override network policy authentication settings  CHAP -- the PX3 uses "CHAP" in this example...
  • Page 904 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 905: 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. a. Use a dictionary to define the Raritan vendor-specific attribute b.

  • Page 906: 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: 1. Go to this location: /etc/raddb/users. 2. 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 907 Appendix K: RADIUS Configuration Illustration 2. Right-click NPS (Local) and select "Register server in Active Directory." 3. Click OK, and then OK again. To grant PX3 users remote access permission: 1. Open Active Directory Users and Computers.
  • Page 908 Appendix K: RADIUS Configuration Illustration 2. Open the properties dialog of the user whom you want to grant the access permission. 3. Click the Dial-in tab and select the "Allow access" checkbox. To enable reversible encryption for CHAP authentication: 1. Open Active Directory Users and Computers. 2.
  • Page 909 Appendix K: RADIUS Configuration Illustration 3. Click the Account tab and select the "Store password using reversible encryption" checkbox.
  • Page 910 Appendix L Additional PX3 Information In This Chapter RJ45-to-DB9 Cable Requirements for Modem Connections ....888 Reserving IP Addresses in DHCP Servers ..........889 Sensor Threshold Settings..............893 Default Voltage and Current Thresholds ..........901 Altitude Correction Factors..............903 Unbalanced Current Calculation ............904 Data for BTU Calculation.................

  • Page 911: Appendix L Additional Px3 Information

    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 912: 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. Reserving IP Addresses in For each interface's client identifier, see DHCP Servers (on page 889).

  • Page 913: 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):  hexadecimal Convert an interface's client identifier into ASCII codes. ...
  • Page 914 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 915: 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 916 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 917 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 918: 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 919 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 920: 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 921 Appendix L: Additional PX3 Information...
  • Page 922 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 923: 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 924 Appendix L: Additional PX3 Information Threshold Default value Hysteresis 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 925: Altitude Correction Factors

    Appendix L: Additional PX3 Information Threshold Default value Upper warning 65% of OCP rating Hysteresis 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.

  • Page 926: Unbalanced Current Calculation

    Appendix L: Additional PX3 Information Unbalanced Current Calculation Unbalanced current information is available on 3-phase models only. This section explains how PX3 calculates the unbalanced current percentage. Calculation: 1. Calculate the average current of all 3 lines. Average current = (L1+L2+L3) / 3 2.

  • Page 927: Data For Btu Calculation

    Appendix L: Additional PX3 Information  Average current: (5.5+5.2+4.0) / 3 = 4.9 amps  L1 current unbalance: (5.5 - 4.9) / 4.9 = 0.1224  L2 current unbalance: (5.2 - 4.9) / 4.9 = 0.0612  L3 current unbalance: (4.0 - 4.9) / 4.9 = -0.1837 ...

  • Page 928: Ways To Probe Existing User Profiles

    Appendix L: Additional PX3 Information 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 929: Cascading Troubleshooting

    Appendix L: Additional PX3 Information Cascading Troubleshooting Any accessibility problem occurred on one of the devices in the cascading chain may result in failure to access all downstream slave devices that are connected to it. Possible Root Causes The following lists the network accessibility issues and possible root causes.
  • Page 930 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 931: 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 910) and Slave Device Events in the Log (on page 909).
  • Page 932 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 933: 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 934: 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 935 Appendix L: Additional PX3 Information b. Default password: raritan (or a new password if you have changed it). 5. If prompted to change the default password, change or ignore it.  To change it, follow onscreen instructions to type your new password.
  • Page 936 Appendix L: Additional PX3 Information To set or Use this command enable network dns resolverPreference IP address <resolver> returned by the DNS <resolver> = preferV4 preferV6 server  Static IP configuration: To set Use this command network <ipvX> interface <ETH> Static IPv4 or address <ip address>...
  • Page 937 Appendix L: Additional PX3 Information To set or Use this command enable network ethernet <ETH> EAP outer eapOuterAuthentication authentication <outer_auth> PEAP <outer_auth> = network ethernet <ETH> EAP inner eapInnerAuthentication authentication <inner_auth> MSCHAPv2 <inner_auth> = network ethernet <ETH> EAP identity eapIdentity <identity> <identity>...
  • Page 938 Appendix L: Additional PX3 Information To set or Use this command enable network ethernet <ETH> EAP CA eapCACertificate 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 ethernet <ETH>...
  • Page 939 Appendix L: Additional PX3 Information Commands for wireless networking:  General wireless settings: To set or Use this command enable network wireless enabled Wireless <option> interface true false <option> = , or network wireless SSID <ssid> SSID <ssid> = SSID string network wireless BSSID <bssid>...
  • Page 940 Appendix L: Additional PX3 Information To set or Use this command enable network wireless Wireless EAP eapClientCertificate TLS client certificate When prompted to enter the client certificate, open the certificate with a text editor, copy and paste the content into the communications program. network wireless Wireless EAP eapClientPrivateKey...
  • Page 941 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 wireless Verify the enableCertVerification...

  • Page 942: Device-Specific Settings

    Appendix L: Additional PX3 Information To verify network settings: After exiting the above configuration mode and the # prompt re-appears, type this command to verify all network settings.  show network The IP address configured may take seconds to take effect. Device-Specific Settings A bulk configuration file will NOT contain any device-specific information like the following list.

  • Page 943: What Is A Certificate Chain

    Appendix L: Additional PX3 Information What is a Certificate Chain If you are familiar with a certificate chain, you can ignore this topic Illustration - GMAIL SMTP Certificate Chain and refer to (on page 924). A certificate or a chain of certificates is used for trusting a TLS server that you want to connect.
  • Page 944 Appendix L: Additional PX3 Information Each certificate in the chain is the issuer certificate of the certificate that follows it. That is, A is the issuer certificate of B, and B is the issuer certificate of C. Note: In fact many certificate chains may comprise only the root certificate and a TLS server's certificate and do not have any intermediate certificate(s) like 'Certificate B' involved.
  • Page 945 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 946: 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 947 Appendix L: Additional PX3 Information openssl s_client -showcerts -connect smtp.gmail.com:465 Alternative: To view the certificate chain instead of all certificates, you can remove the "-showcerts" option from the above command. 2. Information that shows the certificates the SMTP server has is displayed.
  • Page 948 Appendix L: Additional PX3 Information 3. Onscreen information under the title 'Certificate chain' indicates that there are three issuers and three certificates on this server.  Each line beginning with the letter "i" indicates an issuer. They are:  Google Internet Authority G2 ...

  • Page 949: Browsing Through The Online Help

    Appendix L: Additional PX3 Information  Content copying must include the lines of "BEGIN CERTIFICATE" and "END CERTIFICATE". .pem .crt .cer 2. Save that file as a file. In this example, it is named as "my-root.pem." 3. Upload the file "my-root.pem" to PX3 for using the GMAIL SMTP service.
  • Page 950 Appendix L: Additional PX3 Information  To collapse any expanded topic, click the black, gradient arrow prior to the topic, or double-click the expanded topic. The arrow then turns into a white arrow , and all sub-topics below that topic disappear. 6.

  • Page 951: 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............929 Dominion KSX II, SX or SX II Configuration ..........934 Power IQ Configuration ................939 dcTrack ....................

  • Page 952: Configuring Rack Pdu Targets

    Appendix M: Integration Configuring Rack PDU Targets KX III allows you to connect rack PDUs (power strips) to KX III ports. KX III rack PDU configuration is done from the KX III Port Configuration page. Note: Raritan recommends no more than eight (8) rack PDUs (power strips) be connected to a KX III at once since performance may be affected.
  • Page 953 Appendix M: Integration Diagram key PX rack PDU D2CIM-PWR KX III D2CIM-PWR to rack PDU connection D2CIM-PWR to KX III target device port via Cat5 cable Naming the Rack PDU (Port Page for Power Strips) Note: PX rack PDUs (power strips) can be named in the PX as well as in the KX III.
  • Page 954 Appendix M: Integration 3. Click OK.

  • Page 955: 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 956: Dominion Ksx Ii, Sx Or Sx Ii Configuration

    Appendix M: Integration To turn an outlet off: 1. Click Off next to the outlet you want to power off. 2. Click OK on the Power Off dialog. 3. Click OK on the Power Off confirmation dialog. The outlet will be turned off and its state will be displayed as 'off'.
  • Page 957 Appendix M: Integration Connecting a Rack PDU To connect the Raritan PX to the KSX II: 1. Connect one end of a Cat5 cable to the following ports of different Raritan PX.  PX1 series: RJ-45 "SERIAL" port  PX2, PX3 or PX3TS series: RJ-45 "FEATURE" port 2.

  • Page 958: Dominion Sx And Sx Ii

    Appendix M: Integration Power Control The KSX II operation to turn on/off or power cycle a PX is the same as the KX III operation. See Turning Outlets On/Off and Cycling Power page 933). Dominion SX and SX II By connecting to a Dominion SX or SX II device, you can associate one or more outlets on a PX3 device to specific SX or SX II ports.
  • Page 959 Appendix M: Integration 4. You can now add the PX as a managed power strip to the SX II. See Configure Power Strips from the Remote Console or Configure Power Strips Using CLI. in the SX II User Guide or Online Help. PX appliance SX II Dominion SX...
  • Page 960 Appendix M: Integration 3. Type a name and description in the Name and Description fields. 4. Select the number of outlets from the Number of Outlets drop-down menu. 5. Type the port number in the Port field. 6. Click OK. Power Control 1.

  • Page 961: Power Iq Configuration

    Appendix M: Integration Checking Power Strip Status 1. Choose Power Control > Power Strip Status. 2. 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 962: 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 963: Dctrack Overview

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

  • Page 964: 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.

  • Page 965: Index

    Index Assertion Timeout Example for Temperature +  Sensors • 898 Asset Management Commands • 688 +12V Power Supply Sensor • 46, 105, 173, 182 Asset Management Strips and dcTrack • 943 1  Asset Management Tag List • 422, 425 Asset Management Tag Log • 422, 428 1U and 2U Port Locations •...
  • Page 966 Index Bulk Configuration/Upgrade Procedure • 766, Checking RCM State and Current • 802, 804 Checking RCM States and Current • 809 Button-Type Locking Outlets • 20 Checking the Accessibility of NTP Servers • C  Checking the Branch Circuit Rating • 4 Circuit Breaker Orientation Limitation •...
  • Page 967 Index Configuring Security Settings • xxi, 325 Copying an Existing Server's Settings • 649, Configuring SMTP Settings • 285, 314, 318, 385, 391 Creating a CSR • 332, 333, 334 Configuring SNMP Settings • 274, 285, 314, Creating a New Attribute • 847 316, 375, 502 Creating a Role •...
  • Page 968 Index Degaussing RCM Type B Sensors • 817 Dot-Matrix LCD Display • 93 Deleting a Firewall Rule • 606 Download via Curl • 788, 789 Deleting a Monitored Device • 683 Download via Web Browsers • 788 Deleting a Role • 647 Downloading Diagnostic Data via SCP •...
  • Page 969 Index Enabling or Disabling Modbus • 595 Example - Default Upper Thresholds for Enabling or Disabling Peripheral Device Auto Temperature • 667 Management • 562 Example - Inlet Naming • 630 Enabling or Disabling Service Advertising • Example - OCP Naming • 630 xxii, 596 Example - Outlet Naming •...
  • Page 970 Index Example 3 - Combination of SSID and PSK Full Disaster Recovery • 463 Parameters • 698 Fuse • 141 Example 3 - Default Measurement Units • 643 Fuse Replacement on 1U Models • 142 Example 3 - Outlet Sequence Delay • 563 Fuse Replacement on Zero U Models •...
  • Page 971 Index Inlet Sensor Threshold Information • 534, 814 Logging out of CLI • 713 Inlets/Outlets Page • 740 Login • 25, 31, 148, 304, 911 In-Line Monitor Unused Channels • 728 Login Limitation • 610 In-Line Monitors • 724 Login, Logout and Password Change • 147 In-Line Monitor's Web Interface •...
  • Page 972 Index Modifying an Existing LDAP Server • 654 Operating the Dot-Matrix LCD Display • 95, 97, Modifying an Existing Radius Server • 658 98, 100, 121, 139, 818 Modifying an Outlet Group • 209, 216 Operating the LCD Display • 821 Modifying Firewall Control Parameters •...
  • Page 973 Index Port Forwarding Examples • 149, 306, 309, RADIUS Configuration Illustration • 338, 853 Radius Settings • 657 Port Number Syntax • 305, 307, 308, 310, 909 Raritan Training Website • 907 Possible OCP-Tripped Root Cause • 224, 229, Raw Configuration Upload and Download • 465, 470, 759, 765, 788 Possible Root Causes •...
  • Page 974 Index Restarting the PDU • 707 Sensor Log • 422 Restricted Service Agreement • 607 Sensor RJ-45 Port Pinouts • 742 Restrictions of Port-Forwarding Connections • Sensor Threshold Configuration Commands • 40, 43, 910 Retrieving Energy Usage • 511 Sensor Threshold Settings • 181, 185, 194, 205, Retrieving Previous Commands •...
  • Page 975 Index Setting RCM DC Current Thresholds • 803, 805, Setting the SSID • 582 Setting the sysContact Value • 594 Setting RCM Thresholds • 813 Setting the sysLocation Value • 594 Setting the Alarmed to Normal Delay for Setting the sysName Value • 594 DX-PIR •...
  • Page 976 Index Specifying the Agreement Contents • 609 Syslog Message • 377, 397 Specifying the Asset Strip Orientation • 690 System and USB Requirements • 749, 750 Specifying the CC Sensor Type • 661 T  Specifying the Device Altitude • 561 Specifying the EnergyWise Domain •...
  • Page 977 Index Using an Optional DPX3-ENVHUB4 Sensor Y  Hub • 60, 64 Using an Optional DPX-ENVHUB2 cable • 61 Yellow- or Red-Highlighted Sensors • 97, 100, Using an Optional DPX-ENVHUB4 Sensor Hub 120, 134, 183, 188, 193, 207, 222, 232, 238, •...

This manual is also suitable for:

Raritan px3-3000 seriesRaritan px3-5000 series

Table of Contents