1. Manuals
  2. Brands
  3. Raritan Manuals
  4. Power distribution unit
  5. PXE
  6. User manual

Raritan PXE User Manual

Hide thumbs Also See for PXE:
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
Table of Contents

Advertisement

Quick Links

Download this manual
Raritan PXE
User Guide
Xerus
Firmware v3.4.0
™
Copyright © 2018 Raritan, Inc.
PXE-1B-v3.4.0-E
January 2018
255-80-0008-00

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PXE and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Raritan PXE

Summary of Contents for Raritan PXE

  • Page 1 Raritan PXE User Guide Xerus Firmware v3.4.0 ™ Copyright © 2018 Raritan, Inc. PXE-1B-v3.4.0-E January 2018 255-80-0008-00...
  • Page 2 60950-1 or equivalent rating. Attempting to power non-rated devices may result in electric shock, fire, personal injury and death. WARNING! Do not use a Raritan product containing outlet relays to power large inductive loads such as motors or compressors. Attempting to power a large inductive load may result in damage to the relay.
  • Page 3 Tip 1: The outlet (socket) shall be installed near the equipment and shall be easily accessible. Tip 2: For detailed information on any Raritan PDU's overcurrent protectors' design, refer to that model's product specification on Raritan website's PDU Product Selector page https://www.raritan.com/product-selector...
  • Page 4 Raritan, Inc. © Copyright 2018 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

    Connecting the PDU to a Power Source ..................11   Connecting the PXE to Your Network..................... 11   Configuring the PXE ........................12   Installing the USB-to-Serial Driver (Optional) ..............13   Connecting the PXE to a Computer ..................14   Initial Network Configuration via CLI .................. 15...
  • Page 7 Contents   Bulk Configuration Methods ......................18   Installing Cable Retention Clips on Outlets (Optional) ..............18 Chapter 4 Connecting Environmental Sensor Packages     Identifying the Sensor Port......................21   DPX Sensor Packages ........................21   Using an Optional DPX-ENVHUB4 Sensor Hub ..............23  ...
  • Page 8 Miscellaneous ........................214   Maintenance ..........................216   Device Information......................218   Viewing Connected Users ....................220   Viewing or Clearing the Local Event Log................221   Updating the PXE Firmware ....................222   Viewing Firmware Update History ..................224 viii...
  • Page 9 Backup and Restore of Device Settings................232   Network Diagnostics......................233   Downloading Diagnostic Information ................234   Rebooting the PXE Device....................235   Resetting All Settings to Factory Defaults ................ 235   Retrieving Software Packages Information............... 236 Chapter 7 Using SNMP  ...
  • Page 10 Reliability Error Log......................278   Examples..........................278   Clearing Information ........................280   Clearing Event Log......................280   Configuring the PXE Device and Network..................281   Entering Configuration Mode..................... 281   Quitting Configuration Mode....................281   PDU Configuration Commands..................282  ...
  • Page 11 Contents   Retrieving Previous Commands....................388   Automatically Completing a Command ..................388 Chapter 9 Using SCP Commands     Firmware Update via SCP ......................390   Bulk Configuration via SCP ......................391   Backup and Restore via SCP ......................392  ...
  • Page 12   Step B. Configure User Groups on the AD Server ............... 438   Step C. Configure LDAP Authentication on the PXE Device ............439   Step D. Configure Roles on the PXE Device................. 440 Appendix F Updating the LDAP Schema  ...
  • Page 13 "To Assert" and Assertion Timeout ................... 495   "To De-assert" and Deassertion Hysteresis ..............497   Default Voltage and Current Thresholds ..................500   PDView App for Viewing the PXE....................502   Saving User Credentials for PDView's Automatic Login........... 505   Altitude Correction Factors......................507  ...
  • Page 14 What's New in the PXE User Guide The following sections have changed or information has been added to the PXE User Guide based on enhancements and changes to the equipment and/or user documentation. Configuring the PXE (on page 12) Identifying the Sensor Port...
  • Page 15 What's New in the PXE User Guide Default Log Messages (on page 164) Available Actions (on page 172) Placeholders for Custom Messages (on page 191) Writing or Loading a Lua Script (on page 209) Manually Starting or Stopping a Script...
  • Page 16 Chapter 1: What's New in the PXE User Guide Changing the LAN Duplex Mode (on page 296) Setting NTP Parameters (on page 305) Role Configuration Commands (on page 344) All Privileges (on page 344) Authentication Commands (on page 348) Determining the Authentication Method...

  • Page 17: Chapter 1 Introduction

    APIPA and Link-Local Addressing ..............2 Before You Begin..................3 Product Models The PXE comes in several models that are built to stock and can be obtained almost immediately. Raritan also offers custom models that are built to order and can only be obtained on request.

  • Page 18: Apipa And Link-Local Addressing

    DHCP-assigned address. Scenarios where APIPA applies:  DHCP is enabled on the PXE, but no IP address is assigned to the PXE. This may be caused by the absence or malfunction of DHCP servers in the network.

  • Page 19: Before You Begin

    Raritan's Technical Support Department for assistance. 4. Verify that all circuit breakers on the PXE device 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.

  • Page 20: Filling Out The Equipment Setup Worksheet

    Chapter 1: Introduction Filling Out the Equipment Setup Worksheet An Equipment Setup Worksheet is provided in this User Guide. See Equipment Setup Worksheet (on page 398). Use this worksheet to record the model, serial number, and use of each IT device connected to the PDU.

  • Page 21: Chapter 2 Rack-Mounting The Pdu

    Chapter 2 Rack-Mounting the PDU This chapter describes how to rack mount a PXE device. In This Chapter Rackmount Safety Guidelines ..............5 Circuit Breaker Orientation Limitation ............5 Mounting 1U Models Using L-Brackets and Buttons .........6 Mounting Zero U Models Using Two Rear Buttons........7 Mounting Zero U Models Using L-Brackets and Buttons......9...

  • Page 22: Mounting 1U Models Using L-Brackets And Buttons

    Chapter 2: Rack-Mounting the PDU Mounting 1U Models Using L-Brackets and Buttons This section describes how to mount a 1U PXE device using L-brackets and two buttons. To mount 1U models using L-brackets and two buttons: 1. Align the two edge slots of the L-bracket with the two screw holes on the top of the PXE device.

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

    Chapter 2: Rack-Mounting the PDU  Mount the device by screwing a mounting button in the back center of each L-bracket and then having both buttons engage the mounting holes in the rack. The recommended torque for the button is 1.96 N·m (20 kgf·cm). Mounting Zero U Models Using Two Rear Buttons The following describes how to mount a PDU using two buttons only.
  • Page 24 5. Ensure that the two buttons can engage their mounting holes in the rack or cabinet simultaneously. 6. Press the PXE device forward, pushing the mounting buttons through the mounting holes, then letting the device drop slightly. This secures the PXE device in place and completes the installation.

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

    To mount Zero U models using L-brackets and two buttons: 1. Align the two central holes of the L-bracket with the two screw holes on the top of the PXE device. 2. Screw the L-bracket to the device and ensure the bracket is fastened securely.
  • Page 26 Chapter 2: Rack-Mounting the PDU 4. After both L-brackets are installed, you can choose either of the following ways to mount the device in the rack.  Using rack screws, fasten the device to the rack through two identical holes near the edge of each L-bracket. ...

  • Page 27: Chapter 3 Initial Installation And Configuration

    Installing Cable Retention Clips on Outlets (Optional) ......18 Connecting the PDU to a Power Source 1. Verify that all circuit breakers on the PXE device 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.

  • Page 28: Configuring The Pxe

    Chapter 3: Initial Installation and Configuration See this diagram for the ETHERNET port location. Configuring the PXE You can initially configure the PXE by connecting it to a computer, or to a TCP/IP network that supports DHCP. Configuration via a connected computer: Connecting the PXE to a 1.

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

    Automatic driver installation is highly recommended. Automatic driver installation in Windows ® 1. Make sure the PXE is NOT connected to the computer via a USB cable. 2. Run dominion-serial-setup-<n>.exe on the computer and follow online instructions to install the driver.

  • Page 30: Connecting The Pxe To A Computer

    For example, if you are using the kermit terminal program, and the tty device is "/dev/ttyACM0," perform the following commands: > set line /dev/ttyACM0 > connect Connecting the PXE to a Computer The PXE can be connected to a computer for configuration via one of the following ports.  ETHERNET port ...

  • Page 31: Initial Network Configuration Via Cli

    Login (on page 49). Initial Network Configuration via CLI After the PXE is connected to your network, you must provide it with an IP address and some additional networking information. This section describes the initial network configuration via the USB connection.
  • Page 32 Chapter 3: Initial Installation and Configuration 6. The # prompt appears. 7. Type config and press Enter. 8. To configure network settings, type appropriate commands and press Enter. Refer to the following commands list. CLI commands are case sensitive. 9. After finishing the network settings, type apply to save changes. To abort, type cancel.
  • Page 33 Chapter 3: Initial Installation and Configuration  Static IP configuration: To set Use this command network <ipvX> interface <ETH> Static IPv4 or address <ip address> IPv6 address <ip address> = static IP address, with a syntax similar to the example below. ...

  • Page 34: Bulk Configuration Methods

    Chapter 3: Initial Installation and Configuration Bulk Configuration Methods If you have to set up multiple PXE devices, you can use one of the following configuration methods to save your time. Use a bulk configuration file:  Requirement: All PXE devices to configure are of the same model and firmware.
  • Page 35 Chapter 3: Initial Installation and Configuration Note: Some NEMA sockets on PSE-certified PDUs for Japan have integral locking capability and do not need cable retention clips. See (on page 486). Locking Outlets and Cords To install and use a cable retention clip on the outlet: 1.

  • Page 36: Chapter 4 Connecting Environmental Sensor Packages

    An environmental sensor package may comprise sensors only or a combination of sensors and actuators. The PXE can manage a maximum of 32 sensors and/or actuators. The supported maximum cabling distance is 98 feet (30 m), except for DPX sensor packages.

  • Page 37: Identifying The Sensor Port

    Chapter 4: Connecting Environmental Sensor Packages Identifying the Sensor Port Warning: If you purchase Raritan's environmental sensor packages, make sure you connect them to the correct port on the PXE, or damages may be caused to the PXE and/or connected sensor packages.
  • Page 38 PXE. To connect a DPX differential air pressure sensor: 1. Plug one end of a Raritan-provided phone cable into the IN port of a differential air pressure sensor. 2. Plug the other end of this phone cable into the RJ-12 SENSOR port on the PXE.

  • Page 39: Using An Optional Dpx-Envhub4 Sensor Hub

    Optionally, you can connect a Raritan DPX-ENVHUB4 sensor hub to the PXE. This allows you to connect up to four DPX sensor packages to the PXE via the hub. This sensor hub supports DPX sensor packages only. Do NOT connect DPX2, DPX3 or DX sensor packages to it.

  • Page 40: Using An Optional Dpx-Envhub2 Cable

    This cable supports DPX sensor packages only. Do NOT connect DPX2, DPX3 or DX sensor packages to it. To connect DPX sensor packages via the DPX-ENVHUB2 cable: 1. Plug the connector of this cable directly into the PXE device's RJ-12 SENSOR port.
  • Page 41 Chapter 4: Connecting Environmental Sensor Packages 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 PXE.

  • Page 42: Supported Maximum Dpx Sensor Distances

    PXE and the sensor hub is up to 33' (10 m). Maximum distance illustration: The following illustrates the maximum distance when connecting DPX sensor packages with a maximum 16' (5 m) sensor cable to a PXE via a sensor hub. ...

  • Page 43: Dpx2 Sensor Packages

    RJ-12 connector and one to three head connectors. You have to connect DPX2 sensor packages to the sensor cable. For more information on DPX2 sensor packages, access the Environmental Sensors and Actuators Guide (or Online Help) on Raritan website's Support page http://www.raritan.com/support/...
  • Page 44 NOT work properly. Therefore, always occupy all head connectors prior to the final sensor package with a DPX2 sensor package. To connect DPX2 sensor packages to the PXE: 1. Connect a DPX2 sensor package to the first head connector of the DPX2 sensor cable.

  • Page 45: Dpx3 Sensor Packages

    RJ-45 ports, each of which is located on either end of a DPX3 sensor package. LED for indicating the sensor status. To connect DPX3 sensor packages to the PXE: 1. Connect an RJ-12 to RJ-45 adapter cable to the DPX3 sensor package.

  • Page 46: Connecting A Dpx2 Sensor Package To Dpx3

    Chapter 4: Connecting Environmental Sensor Packages Repeat the same steps to cascade more DPX3 sensor packages. 3. Connect the first DPX3 sensor package to the PXE.  Plug the adapter cable's RJ-12 connector into the RJ-12 SENSOR port on the PXE.

  • Page 47: Dx Or Dx2 Sensor Packages

    32 sensors and/or actuators. If there are more than 32 sensors and/or actuators connected, every sensor and/or actuator after the 32nd one is NOT managed by the PXE. For example, if you cascade 12 DX packages, and each package contains...
  • Page 48 Plug the other end into either RJ-45 port on an additional DX package. Repeat the same steps to cascade more DX packages. 3. Connect the first DX sensor package to the PXE.  Plug the adapter cable's RJ-12 connector into the RJ-12 SENSOR port of the PXE.

  • Page 49: Connecting A Dpx2 Sensor Package To Dx

    Chapter 4: Connecting Environmental Sensor Packages Connecting a DPX2 Sensor Package to DX You can connect only one DPX2 sensor package to the "end" of a DX sensor chain. It is strongly recommended to use an RJ-12 to RJ-45 adapter for connecting the DPX2 to the final DX in the chain. The maximum number of DX sensor packages in the chain must be less than 12 when a DPX2 sensor package is involved.

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

    Plug the RJ-12 connector of this cable into the RJ-12 SENSOR port of the PXE. 2. Connect the Raritan sensor packages to any of the four OUT ports on the hub.  An RJ-12 to RJ-45 adapter is required for connecting a DPX or...
  • Page 51 Chapter 4: Connecting Environmental Sensor Packages This diagram illustrates a configuration with a sensor hub connected. The PXE RJ-12 to RJ-45 adapter cable DPX3-ENVHUB4 sensor hub Any Raritan sensor packages...

  • Page 52: Mixing Diverse Sensor Types

    Chapter 4: Connecting Environmental Sensor Packages Mixing Diverse Sensor Types You can mix DPX, DPX2, DPX3 and DX sensor packages on one PXE according to the following sensor combinations. In some scenarios, the DPX3-ENVHUB4 sensor hub is required. The PXE does NOT support any other sensor-mixing combinations than those described in this section.
  • Page 53 DPX2, DPX3 or DX sensor package.  An RJ-12 to RJ-45 adapter cable MUST be used for connecting the DPX3-ENVHUB4 to the PXE. This section only illustrations the following three combinations, but actually there are tens of different combinations by using the...
  • Page 54 Chapter 4: Connecting Environmental Sensor Packages...
  • Page 55 Chapter 4: Connecting Environmental Sensor Packages Mix DPX3 and DX in a sensor chain: Any DX 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 56: Chapter 5 Using The Pdu

    How the overcurrent protector (a circuit breaker) works In This Chapter Panel Components ..................40 Circuit Breakers ..................45 Panel Components The PXE comes in Zero U, 1U, and 2U sizes. All types of models come with the following components on the outer panels.  Power cord ...

  • Page 57: Connection Ports

    The table below explains the function of each port. Port Used for... USB-B Establishing a USB connection between a computer and the PXE for using the command line interface or performing the disaster recovery. For disaster recovery instructions, contact Raritan Technical Support. RS-485 Reserved for a future release.

  • Page 58: Led Display

    Up and Down buttons  Five LEDs for measurement units Note: When a PXE device powers up, it proceeds with the power-on self test and software loading for a few moments. When the software has completed loading, the LED display illuminates.
  • Page 59 One of the measurement unit LEDs will be lit to indicate the unit for the value currently shown in the three-digit row. The Sensor LED is lit only when PXE detects the physical connection of any environmental sensor. The five LEDs look similar to this diagram but may slightly vary according to the model you purchased.
  • Page 60 Chapter 5: Using the PDU Manual Mode You can press the Up or Down button to enter the Manual Mode so that a particular line or the inlet's active power is selected to show specific readings. To operate the LED display: 1.

  • Page 61: Reset Button

    The reset button is located inside the small hole near the display panel on the PDU. Pressing this reset button restarts the PXE device's software without any loss of power to outlets. This operation also power cycles the LED display, causing the LED display to go blank and then return to normal.

  • Page 62: Resetting The Handle-Type Circuit Breaker

    Chapter 5: Using the PDU 2. Examine your PXE and the connected equipment to remove or resolve the cause that results in the overload or short circuit. This step is required, or you cannot proceed with the next step. 3. Press the ON button until it is completely down.
  • Page 63 Chapter 5: Using the PDU 4. Pull up the operating handle until the colorful rectangle or triangle turns RED.

  • Page 64: Chapter 6 Using The Web Interface

    Clicking these adjusts numeric values by 1. Login, Logout and Password Change The first time you log in to the PXE, use the factory default "admin" user credentials. For details, see the Quick Setup Guide accompanying the product.

  • Page 65: Login

    Tab to go to the checkbox and then Enter. Note: To configure the security agreement, see Enabling the Restricted Service Agreement (on page 153). 5. Click Login or press Enter. The PXE web interface opens. The PXE web interface similar to the following image opens.

  • Page 66: Changing Your Password

    Chapter 6: Using the Web Interface Changing Your Password You must have the Change Own Password permission to change your own password. See Creating Roles (on page 105). You must have Administrator Privileges to change other users' Editing or Deleting Users passwords.

  • Page 67: Remembering User Names And Passwords

    To log out without closing the web browser:  Click "Logout" on the top-right corner. -- OR --  Close the PXE tab while there are other tabs available in the browser. To log out by closing the web browser:  Click on the top-right corner of the window.

  • Page 68: 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 69  Date and time of your user account's last login. - Click Last Login to view your login history.  PXE system time, which is converted to the time zone of your computer or mobile device. - Click Device Time to open the Date/Time setup page.

  • Page 70: Menu

    Menu Information shown Dashboard Summary of the PXE status, including a list of alerted sensors and alarms, if any. Dashboard (on page 57). Device data and settings, such as the device name and MAC address.
  • Page 71 Chapter 6: Using the Web Interface Menu Information shown Peripherals Status and settings of Raritan environmental sensor packages, if connected. Peripherals (on page 78). User Management Data and settings of user accounts and groups, such as password change. User Management (on page 98).

  • Page 72: Quick Access To A Specific Page

    Chapter 6: Using the Web Interface Quick Access to a Specific Page If you often visit a specific page in the PXE web interface, you can note down its URL or bookmark it with your web browser. Next time, you can simply enter its URL in the address bar of the browser prior to login.

  • Page 73: Dashboard

    Chapter 6: Using the Web Interface 3. The arrow turns to , indicating the list is sorted in the "ascending" order. 4. To resort the list based on a different column, click a different column header. In this example, the 'Event Class' column is clicked. 5.
  • Page 74 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 59).

  • Page 75: Dashboard - Inlet I1

    Chapter 6: Using the Web Interface Dashboard - Inlet I1 The number of phases shown in the Inlet section varies, depending on the model. Link to the Inlet page: To view more information or configure the inlet(s), click this section's title 'Inlet I1' to go to the Inlet page.
  • Page 76 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 77: Dashboard - Alerted Sensors

    Dashboard - Alerted Sensors When any internal sensors or environmental sensor packages connected to the PXE enter an abnormal state, the Alerted Sensors section in the Dashboard show them for alerting users. To view detailed information or configure each alerted sensor, you can Individual click each sensor's name to go to individual sensor pages.
  • Page 78 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 For numeric sensors:  above upper warning  below lower warning For numeric sensors: ...

  • Page 79: Dashboard - Inlet History

    Chapter 6: Using the Web Interface Dashboard - Inlet History The power chart for the inlet 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.

  • Page 80: Dashboard - Alarms

    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. Dashboard - Alarms If configuring any event rules which require users to take the acknowledgment action, the Alarms section will list any event which no one acknowledges yet since event occurrence.
  • Page 81 Tip: The date and time shown on the PXE web interface are automatically converted to your computer's time zone. To avoid any time confusion, you can apply the same time zone settings as those of PXE to your computer.

  • Page 82: Pdu

    Chapter 6: Using the Web Interface The PXE device's generic information and PDU-level global settings are available on the PDU page. Menu To open the PDU page, click 'PDU' in the (on page 54). Device information shown:  Firmware version ...
  • Page 83 The default is to enable it.  The device's altitude is associated Altitude Specifies the PXE device's altitude with the altitude correction factor. above sea level when a Raritan's DPX Altitude Correction Factors differential air pressure sensor is (on page 507). attached.

  • Page 84: Internal Beeper State

    To reset ALL active energy counters: An active energy reading is a value of total accumulated energy, which is never reset, even if the power fails or the PXE is rebooted. However, you can manually reset this reading to restart the energy accumulation process.

  • Page 85: How The Automatic Management Function Works

    'Inlet' in the (on page 54). Inlet thresholds, when enabled, help you identify whether the inlet enters the warning or critical level. In addition, you can have the PXE automatically generate alert notifications for any warning or critical Event Rules and Actions status.
  • Page 86 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 PXE has more than one inlet. 1. Click 2. Click Reset on the confirmation message.
  • Page 87 Chapter 6: Using the Web Interface 2. Click the desired sensor (required), and then click Edit Thresholds. 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...

  • Page 88: Outlets

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

  • Page 89: Available Data Of The Outlets Overview Page

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

  • Page 91: Ocps

    PXE has overcurrent protectors. Overcurrent protector associated with this outlet OCPs The OCPs page is available only when your PXE has overcurrent protectors, such as circuit breakers. The OCPs page lists all overcurrent protectors as well as their data. Menu To open the OCPs page, click 'OCPs' in the (on page 54).

  • Page 92: Individual Ocp Pages

    Chapter 6: Using the Web Interface Individual OCP Pages An OCP's data/setup page is opened after clicking any OCP's name on the OCPs page. See OCPs (on page 75). General OCP information: Field Description Label This OCP's physical number Type This OCP's type Rating This OCP's rated current...
  • Page 93 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 94: Peripherals

    Chapter 6: Using the Web Interface Peripherals If there are Raritan environmental sensor packages connected to the Connecting PXE, they are listed on the Peripherals page. See Environmental Sensor Packages (on page 20). An environmental sensor package comprises one or some of the following sensors/actuators: ...
  • Page 95 (on page 83). An actuator is never highlighted. Column Description Name By default the PXE assigns a name comprising the following two elements to a newly-managed sensor/actuator.  Sensor/actuator type, such as "Temperature" or "Dry Contact."  Sequential number of the same sensor/actuator type, like 1, 2, 3 and so on.
  • Page 96 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 87). Position The data indicates where this sensor or actuator is located in the sensor chain.
  • Page 97 Chapter 6: Using the Web Interface  To select ALL sensors/actuators, select the topmost checkbox in the header row. Figure 1: Select all checkboxes 3. To release selected ones, click > Release. To manage them, click > Manage.  The management action triggers a "Manage peripheral device" dialog.
  • Page 98 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 applying to newly-added sensors but also the threshold values of the already-managed sensors Individual where default thresholds are being used.

  • Page 99: Yellow- Or Red-Highlighted Sensors

    3. Confirm the operation when prompted. Yellow- or Red-Highlighted Sensors The PXE 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.
  • Page 100 Chapter 6: Using the Web Interface In the following table, "R" represents any numeric sensor's reading. The symbol <= means "smaller than" or "equal to." Sensor status Color States shown in Description the interface Unknown unavailable Sensor state or readings cannot be detected. Managed vs unmanaged Sensors are not being managed.

  • Page 101: Managed Vs Unmanaged Sensors/Actuators

    The PXE neither communicates with unmanaged sensors/actuators nor retrieves their data.  Unmanaged sensors/actuators are listed only when they are physically connected to the PXE. They disappear when they are no longer connected.  They do have an ID number.

  • Page 102: Sensor/Actuator States

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

  • Page 103: Finding The Sensor's Serial Number

    Sensors or actuators are physically connected to the PXE but not managed yet. Note: Unmanaged sensors or actuators will disappear from the web interface after they are no longer physically connected to the PXE. To manage a sensor/actuator, go to (on page 78).

  • Page 104: Identifying The Sensor Position And Channel

    The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the PXE. Match the serial number from the tag to those listed in the sensor table.
  • Page 105 Chapter 6: Using the Web Interface  If a Raritan DPX3-ENVHUB4 sensor hub is involved, the hub port information is also indicated for DPX2, DPX3 and DX series, but NOT indicated for DPX series. Hub Port 3 For example, ...

  • Page 106: Managing One Sensor Or Actuator

    1. From the list of "unmanaged" sensors/actuators, click the one you want to manage. 2. The "Manage peripheral device" dialog appears.  To let the PXE randomly assign an ID number to it, select "Automatically assign a sensor number." This method does not release any managed sensor or actuator. ...
  • Page 107 Chapter 6: Using the Web Interface Special note for a Raritan humidity sensor: A Raritan humidity sensor is able to provide two measurements - relative and absolute humidity values.  A relative humidity value is measured in percentage (%). ...

  • Page 108: Individual Sensor/Actuator Pages

    To configure a numeric sensor's threshold settings: 1. Click Edit Thresholds. Tip: The date and time shown on the PXE web interface are automatically converted to your computer's time zone. To avoid any time confusion, you can apply the same time zone settings as those...
  • Page 109 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 78).
  • Page 110 This field is available for the DX-PIR presence detector only. Normal Delay It determines the wait time before the PXE announces that the presence detector is back to normal after it actually returns to normal. Adjust the value in seconds.
  • Page 111 Chapter 6: Using the Web Interface To view a numeric sensor's chart This sensor's data within the past tens of minutes is shown in the chart. Note that only a numeric sensor has this diagram. State sensors and actuators do not have such data. ...
  • Page 112 Chapter 6: Using the Web Interface To turn on or off an actuator: 1. Click the desired control button. : Turn ON. : Turn OFF. 2. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on. Note: If you try to turn on more than one "powered dry contact"...

  • Page 113: Sensor/Actuator Location Example

    Chapter 6: Using the Web Interface Sensor/Actuator Location Example Use the X, Y and Z coordinates to describe each sensor's or actuator's physical location in the data center. See Individual Sensor/Actuator Pages (on page 92). The X, Y and Z values act as additional attributes and are not tied to any specific measurement scheme.

  • Page 114: User Management

    'admin' or change its permissions, but you can and should change its password. A "role" determines the tasks/actions a user is permitted to perform on the PXE so you must assign one or multiple roles to each user. Menu Click 'User Management' in the (on page 54), and the following submenu displays.

  • Page 115: Creating Users

    Note that you must enter information in the fields showing the message 'required.' User information: Field/setting Description User Name The name the user enters to log in to the PXE.  4 to 32 characters  Case sensitive  Spaces are NOT permitted.
  • Page 116 Chapter 6: Using the Web Interface Field/setting Description Force password When selected, a password change request change on next automatically appears when next time the user login logs in. Changing Your Password For details, see page 50). SSH: You need to enter the SSH public key only if the public key authentication Changing SSH Settings for SSH is enabled.
  • Page 117 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 118 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 119: 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 120 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 121: 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. Creating Users The PXE provides two built-in roles. See (on page 99). Built-in role Description Admin Provide full permissions.

  • Page 122: Editing Or Deleting Roles

    Chapter 6: Using the Web Interface a. Click on that privilege's row to display a list of available arguments for this privilege. b. Select the desired arguments.  To select all arguments, simply select that privilege's checkbox. For example, you can specify the actuators that users can switch on/off as shown below.

  • Page 123: Setting Your Preferred Measurement Units

    4. Click Delete on the confirmation message. Setting Your Preferred Measurement Units You can change the measurement units shown in the PXE user interface according to your own preferences regardless of the permissions you have. Tip: Preferences can also be changed by administrators for specific users on the Edit User page.

  • Page 124: Setting Default Measurement Units

     Psi = pounds per square inch 3. Click Save. Setting Default Measurement Units Default measurement units are applied to all PXE user interfaces across all users, including users accessing the PXE via external authentication servers. For a list of affected user interfaces, see...

  • Page 125: Device Settings

    Chapter 6: Using the Web Interface User Interfaces Showing Default Units Default measurement units will apply to the following user interfaces or information:  Web interface for "newly-created" local users when they have not Creating configured their own preferred measurement units. See Users (on page 99).
  • Page 126 Chapter 6: Using the Web Interface Menu command Submenu command Refer to... Configuring Network Settings Network (on page 111) Changing HTTP(S) Settings Network Services HTTP (on page 121) Configuring SNMP Settings SNMP (on page 122) Configuring SMTP Settings SMTP Server (on page 124) Changing SSH Settings (on page 126)

  • Page 127: Configuring Network Settings

     For the cascading mode, leave it to the default option 'None' because the PXE does NOT have the USB-A port to cascade another PXE. For information on the cascading feature other Raritan PDUs support, refer to the Cascading Guide on Raritan...
  • Page 128 If the device's cascading mode is set to 'Bridging', the BRIDGE section appears. Then you must click the BRIDGE section for IPv4/IPv6 settings. However, it is recommended that you do not change the cascading mode since PXE does NOT have the USB-A port to support the cascading feature. Enable Interface: Make sure the Ethernet interface is enabled, or all networking through this interface fails.
  • Page 129 Field Description Cascading Mode Leave it to the default "None" unless you are establishing a cascading chain. For more information, refer to:  Cascading Multiple PXE Devices for Sharing Ethernet Connectivity  Setting the Cascading Mode...
  • Page 130 You need to configure these settings only when your local network contains two subnets, and you want PXE to communicate with the other subnet. If so, make sure IP forwarding has been enabled in your network, and then you can click 'Add Route' to add static routes.
  • Page 131 PXE device) at a time. Show the LAN's current status, including the Current State current speed and duplex mode. Note: Auto-negotiation is disabled after setting both the speed and duplex settings of the PXE to NON-Auto values, which may result in a duplex mismatch.
  • Page 132 (NIC) have been installed in one network server, leading to two available subnets, and IP forwarding has been enabled. All of the NICs and PXE devices in the examples use static IP addresses.
  • Page 133 Chapter 6: Using the Web Interface In this example, NIC-2 (192.168.100.88) is the next hop router for your PXE 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 134 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 PXE: fd07:2fa:6cff:2405::30  fd07:2fa:6cff:1111::50 fd07:2fa:6cff:2405::80 Two NICs: ...
  • Page 135 Chapter 6: Using the Web Interface In this example, NIC-2 (fd07:2fa:6cff:2405::80) is the next hop router for your PXE 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 136: Configuring Network Services

    Chapter 6: Using the Web Interface Configuring Network Services The PXE 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 248).
  • Page 137 Changing HTTP(S) Settings HTTPS uses Transport Layer Security (TLS) technology to encrypt all traffic to and from the PXE so it is a more secure protocol than HTTP. The PXE supports TLS By default, any access to the PXE via HTTP is automatically redirected to HTTPS.
  • Page 138 Configuring SNMP Settings You can enable or disable SNMP communication between an SNMP manager and the PXE device. 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 139 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.
  • Page 140 See (on page 180). Send an SNMP Notification 5. You must download the SNMP MIB for your PXE to use with your SNMP manager. a. Click the Download MIBs title bar to show the download links. Downloading SNMP b.
  • Page 141 Chapter 6: Using the Web Interface Field Description Server Name Type the name or IP address of the mail server. 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.
  • Page 142 PXE and the client's cipher availability/settings. Tip: If intending to force the PXE to use a specific AES cipher, refer to your client's user documentation for information on configuring AES settings.
  • Page 143 3. To use a different port, type a new port number. 4. Click Save. Changing Modbus Settings You can enable or disable the Modbus/TCP access to the PXE, set it to the read-only mode, or change the TCP port. To change the Modbus/TCP settings: 1.
  • Page 144 .local host name, that is, <preferred_host_name>.local , where <preferred_host_name> is the preferred host name you have specified for PXE. The IPv4 host name is the first priority. If an IPv4 host name is not available, then use the IPv6 host name.

  • Page 145: Configuring Security Settings

    This product supports SHA-2 TLS certificates. Tip: To force all HTTP accesses to the PXE to be redirected to HTTPS, see (on page 121). Changing HTTP(S) Settings...
  • Page 146 Creating IP Access Control Rules IP access control rules (firewall rules) determine whether to accept or discard traffic to/from the PXE, based on the IP address of the host sending or receiving the traffic. When creating rules, keep these principles in mind: ...
  • Page 147 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 148 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. To configure IPv6 access control rules: 1. On the same page, select the Enable IPv6 Access Control checkbox to enable IPv6 access control rules.
  • Page 149 Chapter 6: Using the Web Interface Editing or Deleting IP Access Control Rules When an existing IP access control rule requires updates of IP address range and/or policy, modify them accordingly. Or you can delete any unnecessary rules. To modify or delete a rule: 1.
  • Page 150 Chapter 6: Using the Web Interface  Deny: Rejects any user's login attempt when no matching rules are present. 4. Create rules. Refer to the tables below for different operations. ADD a rule to the end of the list  Click Append. ...
  • Page 151 Chapter 6: Using the Web Interface  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. On the same page, select the "Enable Role Based Access Control for IPv6"...
  • Page 152 As of release 3.4.0, you can create or apply for a multi-domain certificate with subject alternative names. To obtain a CA-signed certificate: Creating 1. Create a Certificate Signing Request (CSR) on the PXE. See a CSR (on page 137). 2. Submit it to a certificate authority (CA). After the CA processes the information in the CSR, it provides you with a certificate.
  • Page 153 Chapter 6: Using the Web Interface Creating a CSR Follow this procedure to create the CSR for your PXE device. Note that you must enter information in the fields showing the message 'required.' To create a CSR: 1. Choose Device Settings > Security > SSL Certificate.
  • Page 154 To get a certificate from a certificate authority (CA), first create a CSR and send it to the CA. See Creating a CSR (on page 137). After receiving the CA-signed certificate, install it onto the PXE. To install the CA-signed certificate: 1. Choose Device Settings > Security > SSL Certificate.
  • Page 155 Active SSL Certificate section. Creating a Self-Signed Certificate When appropriate certificate and key files for the PXE device are unavailable, the alternative, other than submitting a CSR to the CA, is to generate a self-signed certificate.
  • Page 156 Installing or Downloading Existing Certificate and Key You can download the already-installed certificate and private key from any PXE for backup or file transfer. For example, you can install the files onto a replacement PXE device, add the certificate to your browser and so on.
  • Page 157 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 the PXE: 1. Choose Device Settings > Security > SSL Certificate. 2. Select the "Upload Key and Certificate" checkbox at the bottom of the page.
  • Page 158 When configured for external authentication, all PXE users must have an account on the external AA server. Local-authentication-only users will have no access to the PXE except for the admin, who always can access the PXE. If the external authentication fails, an "Authentication failed" message is displayed.
  • Page 159 PXE and the client (such as a web browser), which is impacted by the cipher priority of the PXE and the client's cipher availability/settings. Tip: If intending to force the PXE to use a specific AES cipher, refer to your client's user documentation for information on configuring AES settings.
  • Page 160 Copy settings from This checkbox appears only when there are existing AA server existing LDAP server settings on the PXE. To duplicate any existing AA server's settings, refer to the duplicating procedure below.
  • Page 161 LDAP/LDAPS directory services by Microsoft for use in Windows environments. Security Determine whether you would like to use Transport Layer Security (TLS) encryption, which allows the PXE to communicate securely with the LDAPS server. Three options are available:  StartTLS ...
  • Page 162  Example: testradius.com 4. To verify if the authentication configuration is set correctly, click Test Connection to check whether the PXE can connect to the new server successfully. Tip: You can also test the connection on the Authentication page after finishing adding servers.
  • Page 163 4. Modify the IP Address/Hostname field. 5. Click Add Server. Note: If the PXE 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 PXE and the LDAP server to use the same NTP server(s).
  • Page 164 Confirm Shared Secret 4. To verify if the authentication configuration is set correctly, click Test Connection to check whether the PXE can connect to the new server successfully. Tip: You can also test the connection on the Authentication page after finishing adding servers.
  • Page 165 Save Order to save the new sequence. Note: Whenever the PXE is successfully connected to one external authentication server, it STOPS trying to access the remaining servers in the authentication list regardless of the user authentication result.
  • Page 166 Chapter 6: Using the Web Interface 2. Select the following checkbox. Then the PXE always tries external authentication first. Whenever the external authentication fails, the PXE switches to local authentication. 3. Click Save. To disable external authentication: 1. In the Authentication Type, select Local.
  • Page 167 Keep the idle timeout to 20 minutes or less if possible. This reduces the number of idle sessions connected, and the number of simultaneous commands sent to the PXE. 2. Select the "Prevent concurrent login with same username" checkbox if intending to prevent multiple persons from using the same login name simultaneously.
  • Page 168 At least one numeric character = Required At least one special character = Required Number of forbidden previous passwords Note: The maximum password length accepted by the PXE is 64 characters. 2. Make changes to the default settings as needed. 3. Click Save.
  • Page 169 Enabling the Restricted Service Agreement The restricted service agreement feature, if enabled, forces users to read a security agreement when they log in to the PXE. Users must accept the agreement, or they cannot log in. An event notifying you if a user has accepted or declined the agreement Default Log Messages can be generated.

  • Page 170: Setting The Date And Time

    Restricted Service Agreement" is displayed. Setting the Date and Time Set the internal clock on the PXE device manually, or link to a Network Time Protocol (NTP) server. Note: If you are using Sunbird's Power IQ to manage the PXE, you must configure Power IQ and the PXE to have the same date/time or NTP settings.
  • Page 171 Click Check NTP Servers to verify the validity and accessibility of the manually-specified NTP servers. Click Save. The PXE follows the NTP server sanity check per the IETF RFC. If your PXE has problems synchronizing with a Windows NTP server, see Windows NTP Server Synchronization Solution...
  • Page 172 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 173 Chapter 6: Using the Web Interface Windows NTP Server Synchronization Solution The NTP client on the PXE follows the NTP RFC so the PXE 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 PXE.

  • Page 174: Event Rules And Actions

    Action: This is the response to the event. For example, the PXE notifies the system administrator of the event via email. If you want the PXE to perform one action at a regular interval instead of waiting until an event occurs, you can schedule that action. For example, you can make the PXE email the temperature report every hour.
  • Page 175 Assign a name to this scheduled action. b. Make sure the Enabled checkbox is selected, or the PXE does not perform this scheduled action. c. Set the interval time, which ranges from every minute to yearly.
  • Page 176  <Any sub-event> means all events shown on the list.  <Any Numeric Sensor> means all numeric sensors of the PXE, including internal and environmental sensors. <Any Numeric Sensor> is especially useful if you want to receive the notifications when any numeric sensor's readings pass through a specific threshold.
  • Page 177 6. In this example, 'Above upper critical threshold' is selected because we want the PXE to react only when the selected temperature sensor's reading enters the upper critical range. A "Trigger condition" field appears, requiring you to define the "exact" condition related to the "upper critical"...
  • Page 178 That is, the status of the selected event transits from TRUE to FALSE.  Both: The PXE takes the action both when the event occurs (asserts) and when the event stops/disappears (deasserts). State sensor state...
  • Page 179  Both: The PXE takes the action both when the chosen sensor becomes unavailable or available.  Link state is up: The PXE takes the action Network interface only when the network link state changes link state from down to up.
  • Page 180 Default Log Messages Following are default log messages recorded internally and emailed to specified recipients when PXE events occur (are TRUE) or, in some cases, Send Email stop or become unavailable (are FALSE). See...
  • Page 181 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Card Reader Management > Card Reader with id Card inserted '[CARDREADERID]' connected. Card Reader Management > Card Reader with id Card Reader attached '[CARDREADERID]' disconnected.
  • Page 182 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Device > Event log cleared Event log cleared by user '[USERNAME]' from host '[USERIP]'. Device > Bulk configuration Bulk configuration saved by user saved '[USERNAME]' from host '[USERIP]'.
  • Page 183 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE authentication with incorrrect system clock. Device > Features > Schroff LHX Schroff LHX / SHX support enabled. Schroff LHX / SHX support disabled. / SHX Support Energywise >...
  • Page 184 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 State Sensor/Actuator > '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot Alarmed/Open/On [EXTSENSORSLOT] is [EXTSENSORSLOT] is...
  • Page 185 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 Above upper warning threshold '[INLETPOLE]' of inlet '[INLET]' pole '[INLETPOLE]' of inlet '[INLET]' asserted 'above upper warning' at...
  • Page 186 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Modem > Modem detached A [MODEMTYPE] modem was removed. Overcurrent Protector > * > Sensor '[OCPSENSOR]' on overcurrent Sensor '[OCPSENSOR]' on Sensor >...
  • Page 187 Chapter 6: Using the Web Interface Event/context Default message when the event = Default message when the event TRUE = FALSE Unreachable unreachable. reachable. Server Monitoring > * > Connection to server Unrecoverable '[MONITOREDHOST]' could not be restored. User Activity > * > User logon User '[USERNAME]' from host User '[USERNAME]' from host state...
  • Page 188  System Tamper Alarm: This action causes the PXE to show the alarm for the DX tamper sensor, if any, on the Dashboard page until a person acknowledges it. By default, this action has been assigned to the built-in tamper detection event rules.
  • Page 189 Creates a group of actions comprising existing Action Group group actions. See (on page 176). External beeper PXE does NOT support this feature so you can ignore this action. Internal beeper PXE does NOT support this feature so you can ignore this action. Log event message Records the selected events in the internal log.
  • Page 190 If the Alarm action has been included in a specific event rule and no one acknowledges that alert after it occurs, the PXE resends or regenerates an alert notification regularly until the alert is acknowledged or the maximum number of alert notifications is sent.
  • Page 191  Send email  Send SMS message  Internal beeper Note: PXE does NOT support external and internal beepers so you can ignore related actions. If no appropriate actions are available, create them first. a. To select any methods, select them one by one in the Available field.
  • Page 192 (on page 164). Push Out Sensor Readings You can configure the PXE 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 PXE, you can also configure the PXE to push the data to a server.
  • Page 193 You can configure emails to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and PXE placeholders. The placeholders represent information which is pulled from the PXE and inserted into the message.
  • Page 194 Send Sensor Report You may set the PXE 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 as listed below.
  • Page 195 Chapter 6: Using the Web Interface 2. Select "Send sensor report" from the Action list. 3. In the Destination Actions section, select the method(s) to report sensor readings or states. The number of available methods varies, depending on how many messaging actions have been created. The messaging action types include: ...
  • Page 196 Chapter 6: Using the Web Interface  To remove any sensor from the Report Sensors list box, select it and click . To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones. 6. To immediately send out the sensor report, click Send Report Now. Tip: When intending to send a sensor report using custom messages, use the placeholder [SENSORREPORT] to report sensor readings.
  • Page 197 5. In the Community fields, enter the SNMP community string to access the device(s). The community is the group representing the PXE and all SNMP management stations. Tip: An SNMP v2c notification action permits only a maximum of three SNMP destinations.
  • Page 198 Start or Stop a Lua Script If you have created or loaded a Lua script file into the PXE, you can have that script automatically run or stop in response to a specific event. For instructions on creating or loading a Lua script into this product, see Lua Scripts (on page 209).
  • Page 199  To remove any existing argument, click adjacent to Switch Peripheral Actuator If you have any actuator connected to the PXE, you can set up the PXE so it automatically turns on or off the system controlled by the actuator when a specific event occurs.
  • Page 200 Chapter 6: Using the Web Interface 3. In the Syslog Server field, specify the IP address to which the syslog is forwarded. 4. In the Transport Protocol field, select one of the syslog protocols: TCP, UDP or TCP+TLS. The default is UDP. Transport Next steps protocols...
  • Page 201 Scheduling an Action An action can be regularly performed at a preset time interval instead of being triggered by a specific event. For example, you can make the PXE report the reading or state of a specific sensor regularly by scheduling the "Send Sensor Report"...
  • Page 202 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 203 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 204 Chapter 6: Using the Web Interface  If intended, you can customize the email messages in this action. 2. Click to create a 'Send sensor report' action that includes the 'Email a Sensor Report' action as its destination Send Sensor Report action.
  • Page 205 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 185).
  • Page 206 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 PXE will send out an email containing the specified temperature sensor readings hourly every day.
  • Page 207 Chapter 6: Using the Web Interface Placeholders for Custom Messages The action "Send email" allows you to customize event messages. See Send Email (on page 177). When clicking anywhere inside the text box, the Event Context Information displays, showing a list of placeholders and their definitions. Simply drag the scroll bar and then click the desired placeholder to insert it into the custom message.
  • Page 208 Chapter 6: Using the Web Interface Placeholder Definition [AMSNUMBER] The numeric ID of an asset strip [AMSRACKUNITPOSITION] The (vertical) rack unit position, an action applies to [AMSSTATE] The human readable state of an asset strip [AMSTAGID] The asset tag ID [CARDREADERID] The id of a card reader [CIRCUITCTRATING]...
  • Page 209 Chapter 6: Using the Web Interface Placeholder Definition [ISASSERTED] Boolean flag whether an event condition became true (1) or false (0) [LDAPERRORDESC] An LDAP error occurred [LHXFANID] The ID of a fan connected to an LHX/SHX [LHXPOWERSUPPLYID] The ID of an LHX/SHX power supply [LHXSENSORID] The ID of an LHX/SHX sensor probe [LOGMESSAGE]...
  • Page 210 Chapter 6: Using the Web Interface Placeholder Definition [POWERMETER] The PMC power meter ID [RADIUSERRORDESC] A Radius error occurred [ROMCODE] The rom code of an attached peripheral device [SENSORREADINGUNIT] The unit of a sensor reading [SENSORREADING] The value of a sensor reading [SENSORREPORT] The formatted sensor report contents [SENSORSTATENAME]...
  • Page 211 Then click Delete on the confirmation message. Sample Event Rules Sample PDU-Level Event Rule In this example, we want the PXE to record the firmware upgrade failure in the internal log when it happens. The event rule involves: ...
  • Page 212 Chapter 6: Using the Web Interface 3. To make the PXE record the firmware update failure event in the internal log, select "System Event Log Action" in the Available Actions field. Sample Inlet-Level Event Rule In this example, we want the PXE to send SNMP notifications to the SNMP manager for any sensor change event of the Inlet I1.
  • Page 213 SNMP notifications are sent again. Sample Sensor-Level Event Rule In this example, we want the PXE to send a notification email when a contact closure sensor enters the alarmed state. This event rule requires creating a new action before creating the rule.
  • Page 214 Chapter 6: Using the Web Interface 4. In the Recipient Email Addresses field, type one or multiple recipients' email addresses. 5. (Optional) Specify the SMTP settings and custom log message if needed. 6. Click Create to finish the creation.
  • Page 215 Peripherals 5. Select "State Sensor/Actuator" because the contact closure sensor is a state sensor. 6. Select "Alarmed" since we want the PXE to respond when the selected contact closure sensor changes its state related to the "alarmed" state. 7. In the "Trigger condition" field, select the Alarmed/Open/On radio button so that the action is taken only when the contact closure sensor enters the alarmed state.
  • Page 216 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 PXE 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 217 Example 2 This example illustrates an event rule which continuously causes the PXE 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 218: Setting Data Logging

    60 seconds along with the minimum and maximum measurement values are written to the log. Note: The PXE device's SNMP agent must be enabled for this feature to work. See (on page 238). In addition,...

  • Page 219: Configuring Data Push Settings

    5. Click Save. This button is located at the bottom of the page. Important: Although it is possible to selectively enable/disable logging for individual sensors on the PXE, it is NOT recommended to do so. Configuring Data Push Settings You can push the sensor log to a remote server for data synchronization.
  • Page 220 Setting Data Logging selected on the Data Logging page. See (on page 202). Note: PXE does NOT support asset management strips so you can ignore asset management-related data. 7. Click Create. 8. Repeat the same steps for additional destinations.

  • Page 221: Monitoring Server Accessibility

    Chapter 6: Using the Web Interface Monitoring Server Accessibility You can monitor whether specific IT devices are alive by having the PXE device 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 222 In the beginning, the status of the added IT equipment shows "Waiting for reliable connection," which means the requested number of consecutive successful or unsuccessful pings has not reached before the PXE can declare that the monitored device is reachable or unreachable.
  • Page 223 Example: Ping Monitoring and SNMP Notifications In this illustration, it is assumed that a significant PDU (IP address: 192.168.84.95) shall be monitored by your PXE to make sure that PDU is properly operating all the time, and the PXE must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or network failure.
  • Page 224 Number of consecutive unsuccessful pings for failure  To make the PXE stop pinging the target PDU for 60 seconds (1 minute) after the PDU inaccessibility is declared. After 60 seconds, the PXE will re-ping the target PDU, enter the following data.

  • Page 225: Lua Scripts

    Raritan also provides some Lua scripts examples, which you can load as needed. Note: Not all Raritan Lua script examples can apply to your PXE model. You should read each example's introduction before applying them. You must have the Administrator Privileges to manage Lua scripts.
  • Page 226 Source Code section. Therefore, do not load a new script if the current script meets your needs. 6. If you chose to load a script or Raritan's example in the previous step, its codes are then displayed in the Source Code section. Double check the codes.
  • Page 227 When starting a script, you can choose to start it either with its default arguments or with new arguments. Tip: To have the PXE automatically start or stop a script in response to an event, create an event rule. See...
  • Page 228 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 229 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 54). 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 230: Miscellaneous

    EnergyWise energy management architecture is implemented ® in your place, you can enable the Cisco EnergyWise endpoint implemented on the PXE so that this PXE becomes part of the Cisco EnergyWise domain. To set the Cisco EnergyWise configuration: 1. Choose Device Settings > Miscellaneous.
  • Page 231  Range from 1 to 65535.  Default is 43440. Polling interval Type a polling interval to determine how often the PXE is queried in the Cisco EnergyWise domain.  Range from 30 to 600 ms.  Default is 180 ms.

  • Page 232: Maintenance

    (on page 218) Viewing Connected Users Connected Users (on page 220) Event Log Viewing or Clearing the Local Event Log (on page 221) Updating the PXE Firmware Update Firmware (on page 222) Viewing Firmware Update History Firmware History (on page 224)
  • Page 233 Network Diagnostics Network Diagnostic (on page 233) Downloading Diagnostic Information Download Diagnostic (on page 234)  Rebooting the PXE Device (on page 235) Unit Reset  Resetting All Settings to Factory Defaults (on page 235) About iPDU Retrieving Software Packages Information...

  • Page 234: Device Information

    Device Information Using the web interface, you can retrieve hardware and software information of components or peripheral devices connected to your PXE. Tip: If the information shown on this page does not match the latest status, press F5 to reload it.
  • Page 235 Chapter 6: Using the Web Interface 2. Click the desired section's title bar to show that section's information. For example, click the Network section. The number of available sections is model dependent. 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.

  • Page 236: Viewing Connected Users

    Chapter 6: Using the Web Interface Viewing Connected Users You can check which users have logged in to the PXE device and their status. If you have administrator privileges, you can terminate any user's connection to the PXE. To view and manage connected users: 1.

  • Page 237: Viewing Or Clearing The Local Event Log

    By default, the PXE captures certain system events and saves them in a local (internal) event log. You can view over 2000 historical events that occurred on the PXE in the local event log. When the log size exceeds 256KB, each new entry overwrites the oldest one.

  • Page 238: Updating The Pxe Firmware

    Raritan website's Support page http://www.raritan.com/support/ If you have any questions or concerns about the upgrade, contact Raritan Technical Support BEFORE upgrading. On a multi-inlet PDU (any model with X2 or X3 suffixes), all inlets must be connected to power for the PDU to successfully upgrade its firmware.
  • Page 239 No users can successfully log in to the PXE.  Other users' operation, if any, is forced to suspend. 7. When the update is complete, the PXE resets, and the Login page re-appears.  Other logged-in users are logged out when the firmware update is complete.

  • Page 240: Viewing Firmware Update History

    Chapter 6: Using the Web Interface Full Disaster Recovery If the firmware upgrade fails, causing the PXE device to stop working, you can recover it by using a special utility rather than returning the device to Raritan. Contact Raritan Technical Support for the recovery utility, which works in Windows XP/Vista/7/10 and Linux.

  • Page 241: Bulk Configuration

    The Bulk Configuration feature lets you save generic settings of a configured PXE device to your computer. You can use this configuration file to copy common settings to other PXE devices of the same model and firmware version. See Bulk Configuration Restrictions (on page 226).
  • Page 242 "Bulk configuration copied" event rule. The last configuration-copying record: If you once copied any bulk configuration or device backup file to the PXE, the last record similar to the following is displayed at the bottom of both the Bulk Configuration and Backup/Restore pages.
  • Page 243 "mechanical designs" which are indicated in the table below, the bulk configuration remains feasible. These mechanical designs are represented by suffixes added to the model name of a PXE device. In the table, represents a number. For example, A can be A1, A2, A3, and so on.
  • Page 244 To create new bulk profile(s): 1. Log in to the source PXE device, whose settings you want to download. 2. Choose Maintenance > Bulk Configuration.
  • Page 245 Step 1: Select the desired bulk configuration profile (optional) 1. Log in to the source PXE, whose settings you want to copy. 2. Choose Maintenance > Bulk Configuration. 3. Click on the row of the wanted profile to open the Edit Bulk Profile page.
  • Page 246 Step 3: Perform bulk configuration You must have the Administrator Privileges to upload the configuration. 1. Log in to the target PXE, which is of the same model and runs the same firmware. 2. Choose Maintenance > Bulk Configuration. 3. Click to select the configuration file.
  • Page 247 Chapter 6: Using the Web Interface Alternatives: To use a different method to perform bulk configuration, refer to:  Bulk Configuration via SCP (on page 391)  Bulk Configuration or Firmware Upgrade via DHCP/TFTP page 402)  Configuration or Firmware Upgrade with a USB Drive Modifying or Removing Bulk Profiles You can modify or remove any bulk profile except for the built-in one.

  • Page 248: 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 a PXE device's settings, you should perform the Backup/Restore feature. All PXE information is captured in the plain-TEXT-formatted backup file except for the device logs and TLS certificate.

  • Page 249: Network Diagnostics

    "Bulk configuration copied" event rule. The last configuration-copying record: If you once copied any bulk configuration or device backup file to the PXE, the last record similar to the following is displayed at the bottom of both the Bulk Configuration and Backup/Restore pages.

  • Page 250: Downloading Diagnostic Information

    Important: This function is for use by Raritan Field Engineers or when you are directed by Raritan Technical Support. You can download the diagnostic file from the PXE to a client machine. The file is compressed into a .tgz file and should be sent to Raritan Technical Support for interpretation.

  • Page 251: Rebooting The Pxe Device

    Chapter 6: Using the Web Interface Rebooting the PXE Device You can remotely reboot the PXE device via the web interface. Resetting the PXE does not interrupt the operation of connected servers because there is no loss of power to outlets.

  • Page 252: Retrieving Software Packages Information

    To reset the device to factory defaults: 1. Choose Maintenance > Unit Reset > 2. Click Factory Reset to reset the PXE to factory defaults. 3. A message appears, with a countdown timer showing the remaining time of the operation. It takes about two minutes to complete.
  • Page 253 Chapter 6: Using the Web Interface 2. You can click any link to access related information or download any software package.

  • Page 254: Chapter 7 Using Snmp

    Chapter 7 Using SNMP This SNMP section helps you set up the PXE for use with an SNMP manager. The PXE 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 255: 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 239) ...

  • Page 256: Snmpv3 Notifications

    The port number used to access the device(s). Community The SNMP community string to access the device(s). The community is the group representing the PXE and all SNMP management stations. 6. Click Save. SNMPv3 Notifications 1. Choose Device Settings > Network Services > SNMP.
  • Page 257 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.
  • Page 258 Chapter 7: Using SNMP Field Description Host The IP address of the device(s) you want to access. 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.

  • Page 259: Downloading Snmp Mib

     ASSETMANAGEMENT-MIB: The SNMP MIB file for asset management. Note: PXE does NOT support the asset management feature so you can ignore the asset management MIB. 4. Click Save to save the file onto your computer. MIB download via the Device Information page: 1.

  • Page 260: Snmp Gets And Sets

    Valid objects for these requests are limited to those found in the SNMP MIB-II System Group and the custom PXE MIB. The PXE MIB The SNMP MIB file is required for using your PXE device with an SNMP manager. An SNMP MIB file describes the SNMP functions.
  • Page 261 For example, the measurementsGroup group contains objects for sensor readings of PXE as a whole. One object listed under this group, measurementsUnitSensorValue, is described later in the MIB as "The sensor value". pduRatedCurrent, part of the configGroup group,...
  • Page 262 Some objects can be configured from the SNMP manager using SNMP set commands. Objects that can be configured have a MAX-ACCESS level of "read-write" in the MIB. These objects include threshold objects, which causes the PXE to generate a warning and send an SNMP notification when certain Sensor Threshold Settings parameters are exceeded.

  • Page 263: A Note About Enabling Thresholds

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

  • Page 264: Chapter 8 Using The Command Line Interface

    Retrieving Previous Commands.............. 388 Automatically Completing a Command ..........388 About the Interface The PXE provides a command line interface that enables data center administrators to perform some basic management tasks. Using this interface, you can do the following: ...

  • Page 265: Logging In To Cli

    Windows Vista. To log in using HyperTerminal: 1. Connect your computer to the PXE via a local (USB) connection. 2. Launch HyperTerminal on your computer and open a console window. When the window first opens, it is blank.

  • Page 266: With Ssh Or Telnet

    CLI. 6. You are now logged in to the command line interface and can begin administering the PXE. With SSH or Telnet You can remotely log in to the command line interface (CLI) using an SSH or Telnet client, such as PuTTY.

  • Page 267: Different Cli Modes And Prompts

    PXE device, the > prompt appears.  Administrator Mode: When you log in as an administrator, who has full permissions to configure the PXE device, the # prompt appears.  Configuration Mode: You can enter the configuration mode from the administrator or user mode.

  • Page 268: The ? Command For Showing Available Commands

    Chapter 8: Using the Command Line Interface The ? Command for Showing Available Commands When you are not familiar with CLI commands, you can press the ? key at anytime for one of the following purposes.  Show a list of main CLI commands available in the current mode. ...

  • Page 269: Showing Information

    Showing Information You can use the show commands to view current settings or the status of the PXE device or part of it, such as the IP address, networking mode, firmware version, states or readings of internal or external sensors, user profiles, and so on.

  • Page 270: Network Configuration

    <ETH> is one of the network interfaces: . Note that you must choose/configure the bridge interface if your PXE is set to the bridging mode. Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET interface do NOT function.
  • Page 271 Tip: You can also type the command without adding this option "all" to get the same data. That show network ip interface Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI.
  • Page 272 <ETH> is one of the network interfaces: . Note that you must choose/configure the bridge interface if your PXE is set to the bridging mode. Note: In the bridging mode, only the IP parameters of the BRIDGE interface function. The IP parameters of the ETHERNET interface do NOT function.
  • Page 273 Tip: You can also type the command without adding this option "all" to get the same data. That show network ipv4 interface Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI. Network Interface Settings This command shows the specified network interface's information which is NOT related to IP configuration.
  • Page 274 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 275: Pdu Configuration

    Chapter 8: Using the Command Line Interface PDU Configuration This command shows the PDU configuration, such as the device name, firmware version and model type. show pdu To show detailed information, add the parameter "details" to the end of the command. show pdu details Outlet Information This command syntax shows the outlet information.

  • Page 276: 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 277: 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 278: Date And Time Settings

    Note: If a user has set his/her own preferred measurement units or the administrator has changed any user's preferred units, the web and CLI interfaces show the preferred measurement units for that user instead of the default ones after that user logs in to the PXE. See Existing User Profiles (on page 273) for the preferred measurement units for a specific user.

  • Page 279: 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 280: Actuator 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 PXE web interface. Displayed information:  Without the parameter "details," only the sensor ID, sensor type and reading are displayed.

  • Page 281: Environmental Sensor Package Information

    Chapter 8: Using the Command Line Interface * The actuator number is the ID number assigned to the actuator. The ID number can be found using the PXE web interface or CLI. It is an integer starting at 1. Displayed information: ...

  • Page 282: Inlet Sensor Threshold Information

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

  • Page 283: 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. This command syntax shows the specified inlet pole sensor's threshold-related information. show sensor inletpole <n> <p> <sensor type> To show detailed information, add the parameter "details" to the end of the command.
  • Page 284 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 285: Environmental Sensor Threshold Information

    1.0 deg C Assertion timeout: 0 samples 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 PXE web interface.

  • Page 286: Environmental Sensor Default Thresholds

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

  • Page 287: Security Settings

    With the parameter "details," the threshold range is displayed in addition to default thresholds settings. Security Settings This command shows the security settings of the PXE. show security To show detailed information, add the parameter "details" to the end of the command.

  • Page 288: Authentication Settings

    Chapter 8: Using the Command Line Interface Authentication Settings General authentication settings: This command displays the authentication settings of the PXE, 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 289: 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 290: Existing Roles

    This option shows the data of the specified role only. Displayed information:  Role settings are displayed, including the role description and privileges. EnergyWise Settings This command shows the PXE device's current configuration for Cisco ® EnergyWise. show energywise...

  • Page 291: 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 292: Server Reachability Information

    Cisco EnergyWise-related events, such as enabling the support of the EnergyWise function. Note: You can ignore the following event types in the CLI because the PXE does not support them: assetManagement, cardReader, lhx, modem, transferSwitch and webcam. Server Reachability Information This command shows all server reachability information with a list of monitored servers and status.

  • Page 293: Command History

    Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the specified device's IP address, monitoring enabled/disabled state and current status are displayed.  With the parameter "details," more settings for the specified device are displayed, such as number of pings and wait time prior to the next ping.

  • Page 294: Reliability Error Log

    Chapter 8: Using the Command Line Interface Reliability Error Log This command shows the reliability error log. show reliability errorlog <n> Variables:  <n> is one of the options: (zero) or any other integer number. Option Description Displays all entries in the reliability error log. Tip: You can also type the command without adding this option "0"...
  • Page 295 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 296: Clearing Information

    Clearing Information You can use the clear commands to remove unnecessary data from the PXE. After typing a "clear" command, press Enter to execute it. Note: Depending on your login name, the # prompt may be replaced by the > prompt. See (on page 251).

  • Page 297: Configuring The Pxe Device And Network

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

  • Page 298: Pdu Configuration Commands

    A PDU configuration command begins with . You can use the PDU configuration commands to change the settings that apply to the whole PXE device. Changing the PDU Name This command changes the PXE device's name. config:# pdu name "<name>" Variables: ...
  • Page 299 Specifying the Device Altitude This command specifies your PXE device's altitude above sea level (in meters). You must specify the PXE device's altitude above sea level if a Raritan's DPX differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction Altitude Correction Factors factor.
  • Page 300 Chapter 8: Using the Command Line Interface Setting the Z Coordinate Format for Environmental Sensors This command enables or disables the use of rack units for specifying the height (Z coordinate) of environmental sensors. config:# pdu externalSensorsZCoordinateFormat <option> Variables:  <option>...

  • Page 301: Network Configuration Commands

    Chapter 8: Using the Command Line Interface Setting the Maximum Number of Active Powered Dry Contact Actuators This command determines the upper limit of "active" powered dry contact actuators on one PXE device. config:# pdu activePoweredDryContactLimit <number> Variables:  <number> is the number representing the maximum number of active powered dry contact actuators.
  • Page 302 The IPv4 configuration mode is set to DHCP. static The IPv4 configuration mode is set to static IP address. Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI.
  • Page 303 Cannot begin or end with a hyphen  Cannot contain more than 63 characters  Cannot contain punctuation marks, spaces, and other symbols Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI.
  • Page 304 Determine the IPv4 address of the BRIDGE interface (that is, the bridging mode).  <ip address> is the IP address being assigned to your PXE device. Its 192.168.84.99/24 format is "IP address/prefix". For example, Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI.
  • Page 305 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 PXE and devices in the other subnet. network ipv4 staticRoutes...
  • Page 306 Its format is . You can modify either the IP address or the subnet mask or both. Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI. Configuring IPv6 Parameters...
  • Page 307 The IPv6 configuration mode is set to static IP address. Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI. Setting the IPv6 Preferred Host Name After selecting DHCP as the IPv6 configuration mode, you can specify the preferred host name, which is optional.
  • Page 308 /64, to the end of this IPv6 address. Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI. Setting the IPv6 Gateway After selecting the static IP configuration mode, you can use this command to specify the gateway.
  • Page 309 Setting IPv6 Static Routes If the IPv6 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the PXE and devices in the other subnet. network ipv6 staticRoutes...
  • Page 310 Its format is . You can modify either the IP address or the prefix length or both. Note: PXE does NOT support the cascading feature so you can ignore the BRIDGE option and bridge-related information in the CLI. Configuring DNS Parameters Use the following commands to configure static DNS-related settings.
  • Page 311 <ip address> is the IP address of the DNS server.  <suffix1>, <suffix2>, and the like are the DNS suffixes that automatically apply when searching for any device via PXE. For raritan.com example, <suffix1> can be , and <suffix2> can be legrand.com...
  • Page 312 <mode> is one of the modes: Option Description auto The PXE selects the optimum transmission mode through auto-negotiation. half Half duplex: Data is transmitted in one direction (to or from the PXE device) at a time. full...
  • Page 313 Chapter 8: Using the Command Line Interface Setting Network Service Parameters network services A network service command begins with Setting the HTTP Port The commands used to configure the HTTP port settings begin with network services http Change the HTTP port: config:# network services http port <n>...
  • Page 314 <option> is one of the options: Option Description true Forces any access to the PXE via HTTP to be redirected to HTTPS. false No HTTP access is redirected to HTTPS. Changing the Telnet Configuration You can enable or disable the Telnet service, or change its TCP port using the CLI commands.
  • Page 315 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 316 Chapter 8: Using the Command Line Interface Determining the SSH Authentication Method This command syntax determines the SSH authentication method. config:# network services ssh authentication <auth_method> Variables:  <option> is one of the options: passwordOnly publicKeyOnly passwordOrPublicKey Option Description passwordOnly Enables the password-based login only.
  • Page 317 Chapter 8: Using the Command Line Interface Enabling or Disabling SNMP v3 This command enables or disables the SNMP v3 protocol. config:# network services snmp v3 <option> Variables:  <option> is one of the options: enable disable Option Description enable The SNMP v3 protocol is enabled.
  • Page 318 Chapter 8: Using the Command Line Interface Setting the sysName Value This command sets the SNMP MIB-II sysName value. config:# network services snmp sysName <value> Variables:  <value> is a string comprising 0 to 255 alphanumeric characters. Setting the sysLocation Value This command sets the SNMP MIB-II sysLocation value.
  • Page 319 Chapter 8: Using the Command Line Interface Enabling or Disabling the Read-Only Mode This command enables or disables the read-only mode for the Modbus agent. config:# network services modbus readonly <option> Variables:  <option> is one of the options: true false Option Description...

  • Page 320: Time Configuration Commands

    Chapter 8: Using the Command Line Interface Examples This section illustrates several network configuration examples. Example 1 - Networking Mode The following command enables the wired networking mode. config:# network mode wired Example 2 - Enabling Both IP Protocols The following command determines that both IPv4 and IPv6 protocols are enabled.
  • Page 321 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 322 1:50:20 pm. Setting the Time Zone The CLI has a list of time zones to configure the date and time for the PXE. config:# time zone After a list of time zones is displayed, type the index number of the time zone or press Enter to cancel.
  • Page 323 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 savings time is applied to the time settings.

  • Page 324: Checking The Accessibility Of Ntp Servers

    A security configuration command begins with Firewall Control You can manage firewall control features through the CLI. The firewall control lets you set up rules that permit or disallow access to the PXE device from a specific or a range of IP addresses. ...
  • Page 325 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 326 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 327 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 328 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 329 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 330 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 331 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 332 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 333 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 334 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 PXE web interface or CLI. config:# security loginLimits idleTimeout <value>...
  • Page 335 Chapter 8: Using the Command Line Interface Strong Passwords The strong password commands determine whether a strong password is required for login, and what a strong password should contain at least. A strong password command begins with security strongPasswords. You can combine multiple strong password commands to modify different parameters at a time.
  • Page 336 Chapter 8: Using the Command Line Interface Lowercase Character Requirement This command determines whether a strong password includes at least a lowercase character. config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option> Variables:  enable disable <option> is one of the options: Option Description enable At least one lowercase character is required.
  • Page 337 Chapter 8: Using the Command Line Interface Option Description disable No numeric character is required. Special Character Requirement This command determines whether a strong password includes at least a special character. config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option> Variables:  enable disable <option>...
  • Page 338 Chapter 8: Using the Command Line Interface Modifying Role-Based Access Control Parameters There are different commands for modifying role-based access control parameters.  IPv4 commands Enable or disable the IPv4 role-based access control feature: config:# security roleBasedAccessControl ipv4 enabled <option> Determine the IPv4 role-based access control policy: config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>...
  • Page 339 Chapter 8: Using the Command Line Interface Tip: You can combine both commands to modify all role-based access control parameters at a time. See (on page Multi-Command Syntax 381). Managing Role-Based Access Control Rules You can add, delete or modify role-based access control rules. ...
  • Page 340 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule add <start_ip> <end_ip> <role> <policy> <insert> <rule_number> Variables:  <start_ip> is the starting IP address.  <end_ip> is the ending IP address.  <role> is the role for which you want to create an access control rule.
  • Page 341 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> Modify an IPv4 rule's role: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role <role> Modify an IPv4 rule's policy: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy <policy>...
  • Page 342 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify <rule_number> startIpAddress <start_ip> endIpAddress <end_ip> role <role> policy <policy> Variables:  <rule_number> is the number of the existing rule that you want to modify.  <start_ip> is the starting IP address. ...
  • Page 343 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 enabled true defaultPolicyIn accept defaultPolicyOut accept Results:  The IPv4 access control feature is enabled.  The default policy for inbound traffic is set to "accept."  The default policy for outbound traffic is set to "accept." Example 2 - Adding an IPv4 Firewall Rule The following command adds a new IPv4 access control rule and specifies its location in the list.

  • Page 344: Outlet Configuration Commands

    Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertAbove 3 Results:  A new IPv4 role-based access control rule is added, dropping all packets from any IPv4 address between 192.168.78.50 and 192.168.90.100 when the user is a member of the role "admin."...
  • Page 345 Chapter 8: Using the Command Line Interface Changing the Inlet Name This command syntax names an inlet. config:# inlet <n> name "<name>" Variables:  <n> is the number of the inlet that you want to configure. For a single-inlet PDU, <n> is always the number 1. The value is an integer between 1 and 50.

  • Page 346: 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 PXE device contains multiple inlets, this command names the 1st inlet. config:# inlet 1 name "AC source"...
  • Page 347 This command creates a new user profile. config:# user create <name> <option> <roles> After performing the user creation command, the PXE prompts you to assign a password to the newly-created user. Then: 1. Type the password and press Enter. 2. Re-type the same password for confirmation and press Enter.
  • Page 348 Administrator Privileges. config:# user modify <name> password After performing the above command, PXE prompts you to enter a new password. Then: 1. Type a new password and press Enter. 2. Re-type the new password for confirmation and press Enter.
  • Page 349 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 350 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 PXE device only after that user's user profile is enabled. config:# user modify <name> enabled <option>...
  • Page 351 You can combine all of the following commands to modify the SNMPv3 parameters at a time. See Multi-Command Syntax (on page 381). Enable or disable the SNMP v3 access to PXE for the specified user: config:# user modify <name> snmpV3Access <option1>...
  • Page 352 Chapter 8: Using the Command Line Interface config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3> Variables:  <name> is the name of the user whose settings you want to change.  <option3> is one of the options: true false Option Description true Authentication passphrase is identical to the password.
  • Page 353 Chapter 8: Using the Command Line Interface Determine the privacy passphrase: config:# user modify <name> privacyPassPhrase <privacy_passphrase> Variables:  <name> is the name of the user whose settings you want to change.  <privacy_passphrase> is a string used as a privacy passphrase, comprising 8 to 32 ASCII printable characters.
  • Page 354 (on page 381). Note: The measurement unit change only applies to the web interface and command line interface. Tip: To set the default measurement units applied to the PXE user interfaces for all users via CLI, see Setting Default Measurement Units (on page 341).
  • Page 355 Chapter 8: Using the Command Line Interface Set the preferred length unit: config:# user modify <name> preferredLengthUnit <option2> Variables:  <name> is the name of the user whose settings you want to change.  <option2> is one of the options: meter feet Option...
  • Page 356 After performing this command, the PXE prompts you to enter both current and new passwords respectively. Important: After the password is changed successfully, the new password is effective immediately no matter you type the command "apply"...
  • Page 357 Setting Default Measurement Units Default measurement units, including temperature, length, and pressure units, apply to the PXE user interfaces across all users except for those whose preferred measurement units are set differently by themselves or the administrator. Diverse measurement unit commands can be combined so that you can set all default measurement units at a time.
  • Page 358 Chapter 8: Using the Command Line Interface config:# user defaultpreferences preferredLengthUnit <option2> Variables:  meter feet <option2> is one of the options: Option Description meter This option displays the length or height in meters. feet This option displays the length or height in feet. Set the default pressure unit: config:# user defaultpreferences preferredPressureUnit <option3>...
  • Page 359 Chapter 8: Using the Command Line Interface Example 1 - Creating a User Profile The following command creates a new user profile and sets two parameters for the new user. config:# user create May enable admin Results:  A new user profile "May" is created. ...

  • Page 360: Role Configuration Commands

    All Privileges This table lists all privileges. Note that available privileges vary according to the model you purchased. All PXE models do NOT support features and privileges associated with the LHX/SHX, modem, web cam and transfer switch.
  • Page 361 Chapter 8: Using the Command Line Interface Privilege Description changeAssetStripConfiguration Change Asset Strip Configuration changeAuthSettings Change Authentication Settings changeDataTimeSettings Change Date/Time Settings changeExternalSensorsConfiguration Change Peripheral Device Configuration changeLhxConfiguration Change LHX/SHX Configuration changeModemConfiguration Change Modem Configuration changeNetworkSettings Change Network Settings changePassword Change Own Password changePduConfiguration Change Pdu, Inlet, Outlet &...
  • Page 362 A list of comma-separated ID numbers of different actuators. For example: switchActuator:1,3,6 Note: The ID number of each actuator is shown in the PXE web interface. It is an integer between 1 and 32. Modifying a Role You can modify diverse parameters of an existing role, including its privileges.
  • Page 363 Chapter 8: Using the Command Line Interface config:# role modify <name> addPrivileges <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon.

  • Page 364: Authentication Commands

    Chapter 8: Using the Command Line Interface Deleting a Role This command deletes an existing role. config:# role delete <name> Example - Creating a Role The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup Results: ...
  • Page 365 Chapter 8: Using the Command Line Interface config:# authentication type <option1> useLocalIfRemoteUnavailable <option2> Note: You cannot enable or disable the option of switching to local authentication without determining the authentication type in the CLI. Therefore, always type "authentication type <option1>" when setting up "useLocalIfRemoteUnavailable".
  • Page 366 Chapter 8: Using the Command Line Interface Adding an LDAP Server Adding an LDAP server requires the entry of quite a lot of parameters, such as the server's IP address, TCP port number, Base DN and so on. You can repeat the following CLI command to add more than one LDAP server.
  • Page 367 Chapter 8: Using the Command Line Interface Type Description activeDirectory Microsoft Active Directory  <security> is one of the security options: none startTls Type Description none No security startTls StartTLS  anonymouseBind <bind_type> is one of the bind options: , or authenticatedBind Type Description...
  • Page 368 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> bindDN <bind_DN> "Optional Parameters" table: Parameters To configure userSearchSubfilter <filter> User search subfilter bindDN <bind_DN> bind DN  The system will prompt you to enter and re-confirm the bind password after adding this parameter to the command.
  • Page 369 The "verifyServerCertificate" parameter is added to the command and set to "true." config:# authentication ldap add ldap.raritan.com 389 openldap startTls ... inetOrgPerson verifyServerCertificate true b. The system now prompts you to enter the certificate's content. c. Type or copy the certificate's content in the CLI and press Enter.
  • Page 370 <host> is the IP address or host name of the LDAP server.  <server_num> is the sequential number of the specified server shown on the server list of the PXE. See Authentication Settings page 272). Modifying an Existing LDAP Server You can modify one or multiple parameters of an existing LDAP server, such as its IP address, TCP port number, Base DN and so on.
  • Page 371 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 372 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 373 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 374 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 375 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 376: Environmental Sensor Configuration Commands

     <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
  • Page 377  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
  • Page 378  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
  • Page 379  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
  • Page 380  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.

  • Page 381: 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 382 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 383: 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 384 Chapter 8: Using the Command Line Interface config:# sensor inlet <n> <sensor type> lowerCritical <option> Set the Lower Warning threshold for an inlet sensor: config:# sensor inlet <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an inlet sensor: config:# sensor inlet <n>...
  • Page 385 Chapter 8: Using the Command Line Interface  enable disable <option> is one of the options: or a numeric value. Option Description enable Enables the specified threshold for a specific inlet sensor. disable Disables the specified threshold for a specific inlet sensor.
  • Page 386 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 387 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 388  <n> is the ID number of the environmental sensor that you want to configure. The ID number is available in the PXE web interface or using the command "show externalsensors <n>" in the CLI. It is an integer between 1 and 32.
  • Page 389 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 390: Actuator Configuration Commands

     <n> is the ID number assigned to the actuator. The ID number can be found using the PXE web interface or CLI. It is an integer starting at  <name> is a string comprising up to 64 ASCII printable characters.

  • Page 391: 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 284).  <description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
  • Page 392 <fail_wait> is the wait time to send the next ping after a unsuccessful ping. Valid range is 3 to 600 (seconds).  <resume> is the wait time before the PXE resumes pinging after declaring the monitored device "Unreachable." Valid range is 5 to 120 (seconds).
  • Page 393 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 394 <fail_wait> is the wait time to send the next ping after a unsuccessful ping. Valid range is 3 to 600 (seconds).  <resume> is the wait time before the PXE resumes pinging after declaring the monitored device "Unreachable." Valid range is 5 to 120 (seconds).

  • Page 395: 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 PXE device is enabled. config:# energywise enabled <option> Variables:  <option> is one of the options:...
  • Page 396  <port> is the UDP port number ranging between 1 and 65535. Setting the Polling Interval This command syntax determines the polling interval at which the Cisco ® EnergyWise domain queries the PXE device. config:# energywise polling <timing> Variables: ...

  • Page 397: Multi-Command Syntax

    ® config:# energywise enabled true port 10288 Results:  The EnergyWise feature implemented on the PXE is enabled.  The UDP port is set to 10288. 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...

  • Page 398: Actuator Control Operations

     <n> is an actuator's ID number. The ID number is available in the PXE web interface or using the show command in the CLI. It is an integer between 1 and 32. If you entered the command without "/y", a message appears, prompting you to confirm the operation.

  • Page 399: Switching Off An Actuator

    The following command turns on the actuator whose ID number is 8. control actuator 8 on Unblocking a User If any user is blocked from accessing the PXE, you can unblock them at the local console. To unblock a user: 1.

  • Page 400: Resetting The Pxe

    4. A message appears, indicating that the specified user was unblocked successfully. Resetting the PXE You can reset the PXE device to factory defaults or simply restart it using the CLI commands. Restarting the PDU This command restarts the PXE device. It is not a factory default reset.

  • Page 401: Resetting To Factory Defaults

    Type y to confirm the reset or n to abort it. Variables:  <n> is the inlet number. Resetting to Factory Defaults The following commands restore all settings of the PXE device to factory defaults. To reset PXE settings after login, use either command: reset factorydefaults -- OR --...

  • Page 402: Quitting Diagnostic Mode

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

  • Page 404: Retrieving Previous Commands

    Chapter 8: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your PXE device and a network host. diag> traceroute <host> Variables:  <host> is the name or IP address of the host you want to trace.
  • Page 405 Chapter 8: Using the Command Line Interface Examples:  Example 1 (only one possible command): a. Type the first word and the first letter of the second word of the "reset factorydefaults" command -- that is, reset f. b. Then press Tab or Ctrl+i to complete the second word. ...

  • Page 406: Chapter 9 Using Scp Commands

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

  • Page 407: Bulk Configuration Via Scp

    IP address of the PXE whose configuration you want to save. 2. Type the user password when prompted. 3. The system saves the configuration from the PXE to a file named "bulk_config.txt." To copy the configuration via SCP: 1.

  • Page 408: Backup And Restore Via Scp

    IP address of the PXE whose settings you want to back up. 2. Type the user password when prompted. 3. The system saves the settings from the PXE to a file named "backup_settings.txt." To restore the settings via SCP:...

  • Page 409: Downloading Diagnostic Data Via Scp

    Scenario 1: Use the default SCP port and default filename  SSH/SCP port is the default (22), and the accessed PXE is a standalone device.  The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot (.) in the end of the SCP command as shown below.
  • Page 410 Chapter 9: Using SCP Commands Scenario 2: Specify a different SCP port but use the default filename  SSH/SCP port is NOT the default (22), or the accessed PXE is a Port-Forwarding slave device.  The diagnostic file's default filename "diag-data.zip" is wanted. Then add a dot in the end of the SCP command as shown below.
  • Page 411 Chapter 9: Using SCP Commands Windows PSCP command: PSCP in Windows works in a similar way to the SCP.  pscp -P <port> <user name>@<device ip>:/diag-data.zip <filename>...

  • Page 412: Appendix A Specifications

    In This Chapter Maximum Ambient Operating Temperature........... 396 Sensor RJ-12 Port Pinouts..............396 RS-485 Port Pinouts................396 Maximum Ambient Operating Temperature The maximum ambient operating temperature (TMA) for the PXE is the same for all models. Measure Specification Max Ambient Temperature...
  • Page 413 Appendix A: Specifications RS-485 Pin/signal definition ― ― ― ― ― ― bi-direction Data + ― ― ― ― ― ― bi-direction Data - ― ― ― ― ― ―...

  • Page 414: Appendix B Equipment Setup Worksheet

    Appendix B Equipment Setup Worksheet PXE Series Model ____________ PXE 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...
  • Page 415 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 416 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 417 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 418: Appendix C Bulk Configuration Or Firmware Upgrade Via Dhcp/Tftp

    Bulk Configuration/Upgrade Procedure The DHCP/TFTP feature is supported as of release 3.1.0 so make sure that all PXE devices which you want to configure or upgrade are running firmware version 3.1.0 or later. Steps of using DHCP/TFTP for bulk configuration/upgrade: 1.

  • Page 419: Configuration Files

    DHCP IPv4 Configuration in Linux (on page 431)  DHCP IPv6 Configuration in Linux (on page 433) 5. Make sure all of the desired PXE devices use DHCP as the IP directly configuration method and have been connected to the network.
  • Page 420 This file is required only when there are device-specific settings to devices.csv configure for multiple PXE devices. See (on page 410). Raritan provides a Mass Deployment Utility, which helps you to quickly Creating generate all configuration files for your PXE. See Configuration Files via Mass Deployment Utility...

  • Page 421: Fwupdate.cfg

    For a PXE with factory default configuration, set this option to raritan. logfile  Specify the name of a text file where the PXE will append the log messages when interpreting the TFTP server contents.  If the specified file does not exist in the TFTP server, it will be automatically created.
  • Page 422 . See (on page 410). match  Specify a match condition for identifying a line or a PXE device in the device configuration file "devices.csv." The option's value comprises one word and one number as explained below:  The word prior to the colon is an identification property, which is either serial for serial number or mac for MAC address.
  • Page 423 TFTP server. factory_reset  If this option is set to true, the PXE will be reset to factory defaults.  If the device configuration will be updated at the same time, the factory reset will be executed before updating the device configuration.

  • Page 424: Config.txt

    PXE model. You can use Raritan's Mass Deployment Utility to create this file by yourself, or contact Raritan to get a device configuration file specific to your PXE model and firmware version.
  • Page 425 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP value line 2 Note: The line break before the closing EOF is not part of the value. If a line break is required in the value, insert an additional empty line before the closing EOF.

  • Page 426: Devices.csv

    MAC address to one of the columns in the file. Determine the column to identify PXE devices:  By default, a PXE searches for its serial number in the 1st column.  match To override the default, set the option in the "fwupdate.cfg"...

  • Page 427: Creating Configuration Files Via Mass Deployment Utility

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

  • Page 428: Data Encryption In 'Config.txt

    If an appropriate "config.txt" is not created yet, see Configuration Files via Mass Deployment Utility (on page 411). 2. Launch a terminal to log in to the CLI of any PXE running version Logging in to CLI (on page 249).

  • Page 429: Tftp Requirements

    See (on page 402). If you are going to upload any PXE diagnostic file or create a log file in the TFTP server, the first of the following requirements is also required.  The TFTP server supports the write operation, including file creation and upload.

  • Page 430: Dhcp Ipv4 Configuration In Windows

    Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP DHCP IPv4 Configuration in Windows For those PXE devices using IPv4 addresses, follow this procedure to configure your DHCP server. The following illustration is based on Microsoft Windows Server 2012 system.
  • Page 431 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The vendor class is named "Raritan PDU" in this illustration. 2. Define one DHCP standard option - Vendor Class Identifier. a. Right-click the IPv4 node in DHCP to select Set Predefined...
  • Page 432 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select DHCP Standard Options in the "Option class" field, and Vendor Class Identifier in the "Option name" field. Leave the String field blank. 3. Add three options to the new vendor class "Raritan PDU" in the same dialog.
  • Page 433 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP a. Select Raritan PDU in the "Option class" field. b. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the...
  • Page 434 Name field, select String as the data type, and type 3 in the Code field. 4. Create a new policy associated with the "Raritan PDU" vendor class. a. Right-click the Policies node under IPv4 to select New Policy. b. Specify a policy name, and click Next.
  • Page 435 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP The policy is named "PDU" in this illustration. c. Click Add to add a new condition.
  • Page 436 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select the vendor class "Raritan PDU" in the Value field, click Add and then Ok. e. Click Next.
  • Page 437 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Select DHCP Standard Options in the "Vendor class" field, select "060 Vendor Class Identifier" from the Available Options list, and type "Raritan PDU 1.0" in the "String value" field.
  • Page 438 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP g. Select the "Raritan PDU" in the "Vendor class" field, select "001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv4 address in the "IP address" field.
  • Page 439 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP h. Select "002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. Select "003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third fwupdate.cfg option/code is the magic cookie to prevent the commands from being executed repeatedly.

  • Page 440: Dhcp Ipv6 Configuration In Windows

    Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Important: The magic cookie is transmitted to and stored in PXE 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 PXE.
  • Page 441 Click Add to add a new vendor class. c. Specify a unique name for the vendor class, type "13742" in the "Vendor ID (IANA)" field, and type the binary codes of "Raritan PDU 1.0" in the New Class dialog.
  • Page 442 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP 2. Add three options to the "Raritan PDU 1.0" vendor class. a. Right-click the IPv6 node in DHCP to select Set Predefined Options.
  • Page 443 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP b. Select Raritan PDU 1.0 in the "Option class" field. c. Click Add to add the first option. Type "pdu-tftp-server" in the Name field, select IP Address as the data type, and type 1 in the...
  • Page 444 Click Add to add the third one. Type "pdu-update-magic" in the Name field, select String as the data type, and type 3 in the Code field. 3. Configure server options associated with the "Raritan PDU 1.0" vendor class. a. Right-click the Server Options node under IPv6 to select Configure Options.
  • Page 445 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP c. Select "Raritan PDU 1.0" in the "Vendor class" field, select "00001 pdu-tftp-server" from the Available Options list, and type your TFTP server's IPv6 address in the "IPv6 address" field.
  • Page 446 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select "00002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. e. Select "00003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third fwupdate.cfg option/code is the magic cookie to prevent the commands from being executed repeatedly.

  • Page 447: Dhcp Ipv4 Configuration In Linux

    Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Important: The magic cookie is transmitted to and stored in PXE 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 PXE.
  • Page 448 In the following illustration diagram, it is a combination of a date and a serial number. Important: The magic cookie is transmitted to and stored in PXE 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 PXE.

  • Page 449: Dhcp Ipv6 Configuration In Linux

    Linux. Required Linux IPv6 settings in DHCP: 1. Locate and open the "dhcpd6.conf" file of the DHCP server. 2. The PXE will provide the following values to the "vendor-class" option (option 16). Configure related settings in DHCP accordingly. ...
  • Page 450 In the following illustration diagram, it is a combination of a date and a serial number. Important: The magic cookie is transmitted to and stored in PXE 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 PXE.

  • Page 451: Appendix D Resetting To Factory Defaults

    Appendix D Resetting to Factory Defaults For security reasons, the PXE device can be reset to factory defaults only at the local console. Important: Exercise caution before resetting the PXE to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on.
  • Page 452 Appendix D: Resetting to Factory Defaults To reset to factory defaults without logging in to the CLI: The PXE provides an easier way to reset the product to factory defaults in the CLI prior to login. 1. Connect to the PXE and launch a terminal emulation program as described in the above procedure.

  • Page 453: Appendix E Ldap Configuration Illustration

    Step A. Determine User Accounts and Roles Determine the user accounts and roles (groups) that are authenticated for accessing the PXE. In this example, we will create two user roles with different permissions. Each role (group) will consist of two user accounts available on the AD server.

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

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

  • Page 455: Step C. Configure Ldap Authentication On The Pxe Device

    Appendix E: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the PXE Device You must enable and set up LDAP authentication properly on the PXE device to use external authentication. In the illustration, we assume:  Wired The DNS server settings have been configured properly. See Network Settings (on page 112) and Role of a DNS Server.

  • Page 456: Step D. Configure Roles On The Pxe Device

    5. In the Authentication Type field, select LDAP. 6. Click Save. The LDAP authentication is activated. Note: If the PXE 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 PXE and the LDAP server to use the same NTP server(s).
  • Page 457 Appendix E: 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 458 Appendix E: LDAP Configuration Illustration c. In the Privileges list, select Administrator Privileges. The Administrator Privileges allows users to configure or change all PXE settings. d. Click Save. The PX_Admin role is created.

  • Page 459: Appendix F Updating The Ldap Schema

    From LDAP/LDAPS When an LDAP/LDAPS authentication is successful, the PXE determines the permissions for a given user based on the permissions of the user's role. Your remote LDAP server can provide these user role names by...

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

    Appendix F: 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 461: Adding Attributes To The Class

    Appendix F: Updating the LDAP Schema 3. Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears. 4. Type rciusergroup in the Common Name field. rciusergroup 5. Type in the LDAP Display Name field. 6.
  • Page 462 Appendix F: 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 463: Updating The Schema Cache

    Appendix F: 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 464 Appendix F: 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 465 7. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list. 8. Click Edit. The String Attribute Editor dialog appears. 9. Type the user role (created in the PXE) in the Edit Attribute field. Click OK.

  • Page 466: Appendix G Radius Configuration Illustration

    Servers (on page 147). 2. Configure roles on the PXE. See Creating Roles (on page 105). 3. Configure PXE user credentials and roles on your RADIUS server.  To configure using standard attributes, see Standard Attributes (on page 450). ...
  • Page 467 (on page 482). Step A: Add Your PXE as a RADIUS Client The RADIUS implementation on a PXE 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 468 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 PXE. In this example, they are 1812 and 1813. Then close this dialog.
  • Page 469 New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PXE to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b. Type a name for identifying your PXE in the "Friendly name" field. 192.168.56.29 c.
  • Page 470 Appendix G: 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 PXE. 5. Click OK.
  • Page 471 Appendix G: 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 PXE  Connection request forwarding method  Authentication method(s) ...
  • Page 472 Appendix G: 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 473 Appendix G: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
  • Page 474 Appendix G: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
  • Page 475 Appendix G: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the PXE 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...
  • Page 476 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 PXE uses "CHAP" in this example...
  • Page 477 Appendix G: RADIUS Configuration Illustration Note: If your PXE uses PAP, then select "PAP."...
  • Page 478 Appendix G: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
  • Page 479 Appendix G: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
  • Page 480 Appendix G: 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 481 Appendix G: RADIUS Configuration Illustration Admin inside the curved brackets {} is the existing role on the PXE. It is recommended to use the Admin role to test this configuration. The role name is case sensitive.
  • Page 482 Appendix G: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
  • Page 483 Appendix G: RADIUS Configuration Illustration 15. Click Next to continue.

  • Page 484: Freeradius Standard Attribute Illustration

    Appendix G: 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 485: Vendor-Specific Attributes

    To configure Windows 2008 NPS with the vendor-specific attribute , you must: Step A: Add Your PXE as a RADIUS a. Add your PXE to NPS. See Client (on page 451). b. On the NPS, configure connection request policies and the vendor-specific attribute.
  • Page 486 Appendix G: RADIUS Configuration Illustration Step A: Add Your PXE as a RADIUS Client The RADIUS implementation on a PXE 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 487 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 PXE. In this example, they are 1812 and 1813. Then close this dialog.
  • Page 488 New RADIUS Client. The New RADIUS Client dialog appears. 4. Do the following to add your PXE to NPS: a. Verify the "Enable this RADIUS client" checkbox is selected. b. Type a name for identifying your PXE in the "Friendly name" field. 192.168.56.29 c.
  • Page 489 Appendix G: 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 PXE. 5. Click OK.
  • Page 490 IP address of your PXE = 192.168.56.29  Local NPS server is used  RADIUS protocol selected on your PXE = CHAP  Existing roles of your PXE = Admin, User and SystemTester Illustration: 1. Open the NPS console, and expand the Policies folder.
  • Page 491 Appendix G: 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 492 Appendix G: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
  • Page 493 Appendix G: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
  • Page 494 Appendix G: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the PXE 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...
  • Page 495 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 PXE uses "CHAP" in this example...
  • Page 496 Appendix G: RADIUS Configuration Illustration Note: If your PXE 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 497: 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. Add all user data, including user names, passwords, and roles Presumptions in the illustration: ...

  • Page 498: Ad-Related Configuration

    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 ("). steve Cleartext-Password := "test123" Raritan-PDU-User-Roles = "Raritan:G{Admin User SystemTester}" AD-Related Configuration When RADIUS authentication is intended, make sure you also configure the following settings related to Microsoft Active Directory (AD): ...
  • Page 499 Appendix G: RADIUS Configuration Illustration 2. Right-click NPS (Local) and select "Register server in Active Directory." 3. Click OK, and then OK again. To grant PXE users remote access permission: 1. Open Active Directory Users and Computers.
  • Page 500 Appendix G: 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 501 Appendix G: RADIUS Configuration Illustration 3. Click the Account tab and select the "Store password using reversible encryption" checkbox.

  • Page 502: Appendix H Additional Pxe Information

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

  • Page 503: Securelock™ Outlets And Cords

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

  • Page 504: Button-Type Locking Outlets

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

  • Page 505: Mac Address

    Appendix H: Additional PXE Information MAC Address A label is affixed to the PXE, showing both the serial number and MAC address. If necessary, you can find its IP address through the MAC address by using commonly-used network tools. Contact your LAN administrator for assistance.
  • Page 506 Appendix H: Additional PXE Information Interface Client identifier conversion ETHERNET PEG1A00003 = 50 45 47 31 41 30 30 30 30 33 BRIDGE PEG1A00003 = 50 45 47 31 41 30 30 30 30 33 2. In your DHCP server, bring up the New Reservation dialog, and separate the converted ASCII codes with spaces.

  • Page 507: Reserving Ip In Linux

    For each interface's client identifier, see DHCP Servers (on page 489). In the following illustrations, it is assumed that the PXE serial number is PEG1A00003, and the IP address you want to reserve is 192.168.20.1. Illustration with ASCII code conversion: 1.

  • Page 508: Sensor Threshold Settings

    Appendix H: Additional PXE Information host mypx { option dhcp-client-identifier = "\000PEG1A00003"; fixed-address 192.168.20.1; 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.
  • Page 509 Appendix H: Additional PXE 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 510 Appendix H: Additional PXE 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 511: To Assert" And Assertion Timeout

    Appendix H: Additional PXE Information "To Assert" and Assertion Timeout If multiple sensor states are available for a specific sensor, the PXE 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.
  • Page 512 3 seconds. How "Assertion Timeout" is helpful: If you have created an event rule that instructs the PXE to send notifications for assertion events, setting the "Assertion Timeout" is helpful for eliminating a number of notifications that you may receive in case the sensor's readings fluctuate around a certain threshold.

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

    Appendix H: Additional PXE Information "To De-assert" and Deassertion Hysteresis After the PXE 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 514 Appendix H: Additional PXE Information...
  • Page 515 Deassertion Hysteresis to 0 (zero). How "Deassertion Hysteresis" is helpful: If you have created an event rule that instructs the PXE to send notifications for deassertion events, setting the "Deassertion Hysteresis" is helpful for eliminating a number of notifications that you may receive in case a sensor's readings fluctuate around a certain threshold.

  • Page 516: Default Voltage And Current Thresholds

    20 degrees Celsius, moving from the "above upper warning" range to the "normal" range, either of the following may occur:  If the temperature falls between 20 and 17 degrees Celsius, the PXE does NOT perform the "deassertion" action. ...
  • Page 517 Appendix H: Additional PXE 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...

  • Page 518: Pdview App For Viewing The Pxe

    Raritan has developed an app that can turn your Android mobile device into a local display for the PXE. PDView is especially helpful when your PXE is not connected to the network but you need to check the PXE status, retrieve its information, or change its settings. Requirements for using PDView: ...
  • Page 519 Appendix H: Additional PXE Information 2. Launch the PDView app from your mobile device. Below illustrates the PDView. a. The "Disconnected" message displays first when PDView has not detected the PXE yet. A diagram in PDView indicates the appropriate USB port your mobile device should connect according to your mobile operating system.
  • Page 520 Appendix H: Additional PXE Information 3. Connect your mobile device to the USB-B port of the PXE. The PDView shows the "Connected" message when it detects the connected PXE. 4. If the factory-default user credentials "admin/raritan" remain unchanged, PDView automatically logs in to the PXE web interface.

  • Page 521: Saving User Credentials For Pdview's Automatic Login

    The following procedure illustrates iPad only, but the procedure applies to any iOS or Android mobile devices. To save user credentials in PDView: 1. Make sure your mobile device is NOT connected to the PXE so that PDView does NOT perform the automatic login feature after it is launched.
  • Page 522 Appendix H: Additional PXE Information 3. Tap the top-right icon...

  • Page 523: Altitude Correction Factors

    5. Type the desired user credentials, and tap Save. Altitude Correction Factors If a Raritan differential air pressure sensor is attached to your device, the altitude you enter for the device can serve as an altitude correction factor. That is, the reading of the differential air pressure sensor will be multiplied by the correction factor to get a correct reading.

  • Page 524: Unbalanced Current Calculation

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

  • Page 525: Ways To Probe Existing User Profiles

    Any authenticated users can query currently-existing connection sessions, which show a list of associated user names. Raritan Training Website Raritan offers free training materials for various Raritan products on the Raritan training website http://www.raritantraining.com . The Raritan products introduced on this website include intelligent PDU, KVM, EMX, BCM, and CommandCenter Secure Gateway (CC-SG).

  • Page 526: Device-Specific Settings

    For information on how the uploaded certificate (chain) is related to a TLS server's certificate, see What is a Certificate Chain (on page 511).  For an example of creating and uploading a TLS certificate to PXE, Illustration - GMAIL SMTP Certificate Chain (on page 514).

  • Page 527: What Is A Certificate Chain

    A certificate or a chain of certificates is used for trusting a TLS server that you want to connect. The receiver, such as PXE, can trust a TLS server only after an appropriate certificate (chain) which is "related to" that TLS server's certificate is uploaded to the receiver.
  • Page 528 Appendix H: Additional PXE 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 529 When uploading a (partial) chain onto the PXE, it means you trust each certificate in the chain to certify the authenticity of certificates a server sends to PXE. Therefore, at least the root certificate must be authentic, issued by a CA you trust, and downloaded from that CA over a secure channel.

  • Page 530: Illustration - Gmail Smtp Certificate Chain

    Illustration - GMAIL SMTP Certificate Chain If you will apply your company's SMTP service to PXE, ignore this GMAIL illustration topic. Simply contact your IT department to retrieve the appropriate certificate (chain) file and upload it to the PXE.
  • Page 531 Appendix H: Additional PXE 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 532 'Equifax Secure Certificate Authority', which indicates it is the root CA, there are no more missing certificates to search for. Step 3 -- Upload the missing certificate(s) to PXE: 1. Paste the root certificate's content into a plain text file that will be...

  • Page 533: Browsing Through The Online Help

    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 PXE for using the GMAIL SMTP service. Note: If your SMTP server requires the upload of a certificate file comprising multiple certificates, make sure the order of these certificates is correct in the file.
  • Page 534 Appendix H: Additional PXE 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.

  • Page 535: Appendix I Integration

    ® center. The PXE is categorized as a power item in dcTrack. dcTrack offers an import wizard for conveniently adding the PXE as well as other IT equipment to dcTrack for management. You can use dcTrack to: ...

  • Page 536: Dctrack Overview

    Appendix I: 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 537 Calendar • xiv, 154, 156 Adding Radius Servers • xiv, 142, 147, 149, 450 Changing a User's Password • 332 Additional PXE Information • 486 Changing HTTP(S) Settings • 110, 120, 121, AD-Related Configuration • 451, 469, 482 Alarm • 173, 174 Changing Measurement Units •...
  • Page 538 Index Changing the Telnet Configuration • 298 Connecting the PXE to a Computer • 2, 12, 14, Changing the Telnet Port • 299 Changing the UDP Port • 380 Connecting the PXE to Your Network • 11, 12, Changing Your Own Password • 340 Changing Your Password •...
  • Page 539 Index Deleting a Role-Based Access Control Rule • Enabling and Configuring SNMP • 197, 202, Deleting a User Profile • 340 Enabling or Disabling a User Profile • 334 Detailed Information on Outlet Pages • 73, 74 Enabling or Disabling an Inlet (for Multi-Inlet Determining the Authentication Method •...
  • Page 540 Index Example • 306, 316, 332, 340 Example 3 - User Blocking • 327 Ping Monitoring and SNMP Notifications • Example 4 - Adding an IPv4 Role-based 205, 207 Access Control Rule • 327 Example - Actuator Naming • 375 Example 4 - In-Depth PDU Information •...
  • Page 541 Index Initial Network Configuration via CLI • 2, 12, Managing External Authentication Settings • 15, 435 142, 146, 148, 149 Inlet • 54, 59, 60, 68, 69 Managing Firewall Rules • 310 Inlet Configuration Commands • 328 Managing One Sensor or Actuator • 80, 81, 90 Inlet Information •...
  • Page 542 PDU Configuration • 259 PDU Configuration Commands • 282 Resetting the PXE • 384 PDView App for Viewing the PXE • xvi, 502 Resetting to Factory Defaults • 236, 385, 435 Performing Bulk Configuration • xv, 225, 229 Restarting the PDU • 384 Peripherals •...
  • Page 543 Index Sample Inlet-Level Event Rule • 196 Setting the IPv4 Preferred Host Name • xv, Sample PDU-Level Event Rule • 195 Sample Sensor-Level Event Rule • 197 Setting the IPv6 Address • xv, 292 Saving User Credentials for PDView's Setting the IPv6 Configuration Mode • xv, 290 Automatic Login •...
  • Page 544 Unpacking the Product and Components • 3 Step A Updating the LDAP Schema • 443 Add Your PXE as a RADIUS Client • 450, Updating the PXE Firmware • 216, 222, 390 451, 469, 470 Updating the Schema Cache • 447 Step A.
  • Page 545 Index Writing or Loading a Lua Script • xv, 209, 213 Y  Yellow- or Red-Highlighted Sensors • 69, 79, 83, 86, 92, 494 Z  Z Coordinate Format • xiv, 67, 68 Zero U Products • 1...

Table of Contents