Raritan EMX2-888 User Manual
  1. Manuals
  2. Brands
  3. Raritan Manuals
  4. Switch
  5. EMX2-888
  6. User manual

Raritan EMX2-888 User Manual

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

Advertisement

Quick Links

Raritan EMX
User Guide
Release 3.2.10
Copyright © 2016 Raritan, Inc.
EMX-0J-v3.2.10-E
March 2016
255-80-6107-00

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EMX2-888 and is the answer not in the manual?

Questions and answers

Related Manuals for Raritan EMX2-888

Summary of Contents for Raritan EMX2-888

  • Page 1 Raritan EMX User Guide Release 3.2.10 Copyright © 2016 Raritan, Inc. EMX-0J-v3.2.10-E March 2016 255-80-6107-00...
  • Page 2 Raritan, Inc. © Copyright 2016 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.

  • Page 3: Table Of Contents

    What's New in the EMX User Guide Chapter 1 Introduction Overview ............................1 Product Models ..........................2 EMX2-111..........................2 EMX2-888..........................3 Package Contents.......................... 3 APIPA and Link-Local Addressing....................4 Chapter 2 Rack Mounting an EMX Mounting a Zero U EMX ........................ 6 Mounting a 1U EMX........................
  • Page 4 Overview of the LCD Display.....................67 Control Buttons ........................68 Operating the LCD Display....................68 EMX2-888 Contact Closure Sensor Termination ................76 Connecting Contact Closure Sensors to EMX2-888 ............77 EMX2-888 Contact Closure Sensor LEDs ................81 Reset Button ..........................82 Beeper ............................82 Chapter 6 Using the Web Interface Supported Web Browsers......................
  • Page 5 Contents Naming the EMX ......................110 Modifying the Network Configuration................110 Modifying Network Service Settings ................120 Setting the Date and Time....................127 Setting Default Measurement Units.................131 Configuring the Feature Port ...................132 Configuring the Auxiliary Port ..................133 Configuring the Serial Port ....................135 Setting the Cascading Mode ...................136 Specifying the Device Altitude ..................143 Setting Data Logging .......................144 Configuring SMTP Settings .....................145...
  • Page 6 Contents Managing Event Logging ......................232 Viewing the Local Event Log ...................232 Viewing the Wireless LAN Diagnostic Log ..............233 Clearing Event Entries.....................234 Viewing Connected Users ......................234 Monitoring Server Accessibility....................235 Adding IT Devices for Ping Monitoring ................235 Editing Ping Monitoring Settings..................238 Deleting Ping Monitoring Settings ...................238 Checking Server Monitoring States .................239 Environmental Sensors and Actuators ..................239 Identifying Environmental Sensors and Actuators............240...
  • Page 7 Contents Network Diagnostics ........................293 Pinging a Host .........................293 Tracing the Network Route....................294 Listing TCP Connections ....................294 Downloading Diagnostic Information ..................294 Rebooting the EMX........................295 Accessing the Help ........................296 Retrieving Software Packages Information ..............296 Browsing through the Online Help...................296 Chapter 7 Using SNMP Enabling SNMP..........................298 Configuring Users for Encrypted SNMP v3 ................299 Configuring SNMP Notifications ....................300...
  • Page 8 Contents Blade Extension Strip Settings ..................330 Event Log.........................331 Wireless LAN Diagnostic Log ..................332 Server Reachability Information ..................332 Command History......................334 History Buffer Length.......................334 Reliability Data.........................334 Reliability Error Log ......................334 Examples .........................335 Clearing Information........................336 Clearing Event Log ......................337 Clearing WLAN Log......................337 Configuring the EMX Device and Network ................337 Entering Configuration Mode...................338 Quitting Configuration Mode....................338 Device Configuration Commands..................339...
  • Page 9 Logging out of CLI........................439 Appendix A Specifications Maximum Ambient Operating Temperature ................440 EMX2-111 Feature RJ-45 Port Pinouts ..................440 EMX2-888 Feature RJ-45 Port Pinouts ..................441 Sensor RJ-12 Port Pinouts ......................441 Serial RS-232 Port Pinouts......................441 RS-485 Port Pinouts ........................442 Appendix B Configuration or Firmware Upgrade with a USB Drive System and USB Requirements ....................444...
  • Page 10 Contents Firmware Upgrade via USB .......................453 Appendix C Bulk Configuration or Firmware Upgrade via DHCP/TFTP Bulk Configuration/Upgrade Procedure ..................454 TFTP Requirements........................455 DHCP IPv4 Configuration in Windows..................456 DHCP IPv6 Configuration in Windows..................466 DHCP IPv4 Configuration in Linux.....................473 DHCP IPv6 Configuration in Linux.....................475 Appendix D Resetting to Factory Defaults Using the Reset Button ......................477 Using the CLI Command ......................478...
  • Page 11 Ways to Probe Existing User Profiles ..................539 Truncated Data in the Web Interface..................540 Raritan Training Website ......................540 Connecting Contact Closure Sensors to OLD EMX2-888 ............541 Appendix J Integrating Asset Management Sensors with Other Products Asset Management Sensors and Raritan PDUs ...............543 Asset Management Sensors and dcTrack.................543...
  • Page 12 What's New in the EMX User Guide Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
  • Page 13 MAC Address (on page 74) USB-Cascaded Device's Position (on page 76) EMX2-888 Contact Closure Sensor Termination (on page 77) Connecting Contact Closure Sensors to EMX2-888 (on page 81) EMX2-888 Contact Closure Sensor LEDs (on page 82) Beeper (on page 83)
  • Page 14 Sensor Threshold Settings (on page 536) PDView App for Viewing the EMX (on page Connecting Contact Closure Sensors to OLD EMX2-888 541) Please see the Release Notes for a more detailed explanation of the changes applied to this version of EMX.

  • Page 15: Chapter 1 Introduction

    IT devices to administer. The following items are required for setting up the asset management system:  Raritan asset tags: You tag an IT device by sticking an electronic asset tag on it.  Raritan asset management sensors (asset sensors): Each asset sensor transmits the tag and position information to the EMX.

  • Page 16: Product Models

    EMX2-111  EMX2-888 All models are functionally identical, but vary in the dimension and total number of ports. Note: For a list of available asset sensor kits and tags, visit the Raritan website's Product Selector page (http://www.findmypdu.com/). EMX2-111 EMX2-111 has the following ports and components: ...

  • Page 17: Emx2-888

    Contact closure sensor termination For details on each port, see (on page 64). Connection Ports Note: If your EMX is EMX2-888, which contains built-in contact closure sensor terminals, see Connecting Contact Closure Sensors to OLD EMX2-888 (on page 541) and...

  • Page 18: Apipa And Link-Local Addressing

    Chapter 1: Introduction APIPA and Link-Local Addressing The EMX supports Automatic Private Internet Protocol Addressing (APIPA) as of release 3.2.0. With APIPA, your EMX automatically configures a link-local IP address and a link-local host name when it cannot obtain a valid IP address from any DHCP server in the TCP/IP network.
  • Page 19 Chapter 1: Introduction Retrieval of the link-local IPv4 address:  (on page 72). IPv4 Address...

  • Page 20: Chapter 2 Rack Mounting An Emx

    Rack Mounting an EMX Chapter 2 Depending on the model you purchased, the way to mount an EMX device varies. In This Chapter Mounting a Zero U EMX ................6 Mounting a 1U EMX ..................7 Mounting a Zero U EMX This section describes how to mount a Zero U EMX device using L-brackets and two buttons.

  • Page 21: Mounting A 1U Emx

    Chapter 2: Rack Mounting an EMX 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. Mount the device by screwing a mounting button in the back ...
  • Page 22 Chapter 2: Rack Mounting an EMX 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners.

  • Page 23: Chapter 3 Installation And Configuration

    1. Install the cable retention clip by inserting both ends into the tiny holes on two hexagon screws adjacent to the power socket. 2. Plug one end of the Raritan-provided power cord into the power socket, and press the cable retention clip toward the power cord until...

  • Page 24: Configuring The Emx

    Chapter 3: Installation and Configuration 3. Connect the other end of the power cord to an appropriate power source. Configuring the EMX You can initially configure the EMX by connecting it to a computer, or to a TCP/IP network that supports DHCP. Configuration over a DHCP-enabled network: 1.

  • Page 25: Connecting The Emx To A Computer

    USB-B port (male)  RS-232 serial port (male) EMX2-111: EMX2-888: To use the command line interface (CLI) for configuration, establish an RS-232 or USB connection. To use a web browser for configuration, make a network connection to the computer. The EMX is automatically configured with the following link-local addressing in any network without DHCP available: ...

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

    A USB-to-serial driver named "Dominion EMX Serial Console" is required for Microsoft Windows operating systems. ® ® Download the USB serial console driver from the Raritan website's (http://www.raritan.com/support/). The driver contains Support page the dominion-serial.inf, dominion-serial.cat and dominion-serial-setup-<n>.exe files. Note: <n> in the filename of "dominion-serial-setup-<n>.exe" represents the file's version number.
  • Page 27 Chapter 3: Installation and Configuration 3. Connect the EMX to the computer via a USB cable. The driver is automatically installed. ® Manual driver installation in Windows 1. Make sure the EMX has been connected to the computer via a USB cable.

  • Page 28: Connecting The Emx To Your Network

    Chapter 3: Installation and Configuration Connecting the EMX to Your Network To remotely administer the EMX, you must connect the EMX to your local area network (LAN). The EMX can be connected to a wired or wireless network. Note: If your EMX will be used as a master device in the USB-cascading configuration where the bridging mode applies, make a wired connection.

  • Page 29: Initial Network Configuration Via Cli

    A/B/G/N Raritan USB WIFI A/B/G/N Note: To use the Edimax EW-7722UnD or Raritan USB WIFI wireless LAN adapter to connect to an 802.11n wireless network, the handshake timeout setting must be changed to 500 or greater, or the wireless connection will fail.
  • Page 30 4. The EMX prompts you to log in. Both user name and password are case sensitive. a. Username: admin b. Password: raritan (or a new password if you have changed it). 5. If prompted to change the default password, change or ignore it. ...
  • Page 31 Chapter 3: Installation and Configuration Tip: You can combine multiple commands to configure multiple parameters at a time. For example, network interface LANInterfaceSpeed <option> LANInterfaceDuplexMode <mode> c. For the wireless network mode, you must configure the Service Set Identifier (SSID) parameter. To set Use this command SSID...
  • Page 32 Chapter 3: Installation and Configuration To set Use this command EAP passord network wireless eapPassword When prompted to enter the password for EAP authentication, type the password. EAP CA network wireless certificate eapCACertificate When prompted to enter the CA certificate, open the certificate with a text editor, copy and paste the content into the communications program.
  • Page 33 Chapter 3: Installation and Configuration To set Use this command IP protocol network ip proto <protocol> <protocol> = v4Only, v6Only or both IP address network ip returned by dnsResolverPreference the DNS <resolver> server <resolver> = preferV4 or preferV6 e. After enabling the IPv4 or IPv6 protocol in the earlier step, configure the IPv4 or IPv6 network parameters.
  • Page 34 Chapter 3: Installation and Configuration  For static IP configuration, configure these parameters. To set Use this command Static IPv4 or network <version> ipAddress <ip IPv6 address address> <ip address> = static IP address IPv4 subnet network ipv4 subnetMask mask <netmask>...

  • Page 35: Bulk Configuration Methods

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

  • Page 36: Cascading The Emx Via Usb

    Chapter 3: Installation and Configuration Cascading the EMX via USB You can use USB cables to cascade up to eight Raritan devices. All devices in the USB-cascading chain share the Ethernet connectivity. Different Raritan models can be cascaded as long as they are running an appropriate firmware.
  • Page 37 Chapter 3: Installation and Configuration 4. Connect the USB-A port of the master device to the USB-B port of an additional EMX via a USB cable. This additional device is Slave 1. 5. Connect Slave 1's USB-A port to the USB-B port of an additional EMX via a USB cable.
  • Page 38 Identifying Cascaded Devices (on page 107). Tip: The USB-cascading configuration can be a combination of diverse Raritan products that support the USB-cascading feature, including PX2, PX3, PX3TS, EMX and BCM. See the USB-Cascading Solution Guide on Raritan website's Support page...

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

    Raritan asset sensors: An asset sensor transmits the asset management tag's ID and positioning information to the EMX.  Raritan asset tags: An asset tag is adhered to an IT device. The asset tag uses an electronic ID to identify and locate the IT device.

  • Page 40: Combining Regular Asset Sensors

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

  • Page 42: Introduction To Asset Tags

    Chapter 4: Connecting External Equipment (Optional) Introduction to Asset Tags You need both asset sensors and asset tags for tracking IT devices. Asset tags provide an ID number for each IT device. The asset tags are adhered to an IT device at one end and plugged in to an asset sensor at the other.

  • Page 43: Emx2-111 Connection

    The FEATURE port of EMX2-111 supports 5 volts of power only, which is insufficient for connecting an asset sensor at a distance between 1 and 10 meters. Therefore, the use of a Raritan X cable is required for EMX2-111 to connect an asset sensor whose cabling distance is over 1 meter.
  • Page 44 FEATURE port on the EMX2-111. MASTER asset sensor Asset tags IT devices Raritan X cable Note: To connect Raritan's environmental sensor packages to EMX2-111, connect them to the female RJ-12 connector of the X cable. For details, Using an X Cable (on page 37).

  • Page 45: Emx2-888 Connection

    Chapter 4: Connecting External Equipment (Optional) EMX2-888 Connection Unlike EMX2-111, EMX2-888 does NOT need to use a Raritan X cable because its FEATURE port supports 12 volts of power. To connect a regular asset sensor assembly to EMX2-888: 1. Assemble regular asset sensors according to your needs. See (on page 26).

  • Page 46: Connecting Blade Extension Strips

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

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

    Chapter 4: Connecting External Equipment (Optional) Connecting Composite Asset Sensors (AMS-Mx-Z) A composite asset sensor is named AMS-Mx-Z, where x is a number, such as AMS-M2-Z or AMS-M3-Z. It is a type of asset sensor that functions the same as regular MASTER asset sensors except for the following differences: ...

  • Page 50: Daisy-Chain Limitations Of Composite Asset Sensors

    The maximum cable length between composite asset sensors is 2 meters, but the total cable length cannot exceed 10 meters.  The maximum number of composite asset sensors that can be daisy chained vary according to the Raritan device. Raritan devices Maximum sensors per chain EMX2-111,...
  • Page 51 PMC (BCM2 series) Tip: To increase the maximum number of composite asset sensors attached to a Raritan PX2 PDU or EMX2-111, you can use Raritan's X cable to enhance the power supply to the asset sensor chain. See Using an X Cable (on page 37).
  • Page 52 Chapter 4: Connecting External Equipment (Optional) 2. Plug the male phone connector of the X cable into the RJ-12 SENSOR port of the EMX device. This step is required for enhancing the power supply to asset sensors. 3. Plug the male RJ-45 connector at the longer end of the X cable into the RJ-45 port labeled "Input"...

  • Page 53: Connecting Environmental Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) 4. Connect any Raritan environmental sensor package or sensor hub to the female RJ-12 sensor port of the X cable if environmental sensor packages are needed. Note that a DX or DPX3 sensor requires an RJ-12 to RJ-45 adapter to connect the X cable.

  • Page 54: Dpx Sensor Packages

    EMX2-111 This model has only one SENSOR port so it can manage up to 32 sensors and/or actuators. EMX2-888 This model has 8 SENSOR ports, which can manage up to 128 sensors and/or actuators in total. In addition, it has two built-in contact closure terminals to connect two contact closure sensors.
  • Page 55 EMX. 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 EMX.

  • Page 56: Dpx Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) Using an Optional DPX-ENVHUB4 Sensor Hub Optionally, you can connect a Raritan DPX-ENVHUB4 sensor hub to the EMX. This allows you to connect up to four DPX sensor packages to the EMX via the hub.

  • Page 57: Dpx Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) Using an Optional DPX-ENVHUB2 cable A Raritan DPX-ENVHUB2 cable doubles the number of connected environmental sensors per SENSOR port. This cable supports DPX sensor packages only. Do NOT connect DPX2, DPX3 or DX sensor packages to it.

  • Page 58: Dpx Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) 2. The cable has two RJ-12 sensor ports. Connect DPX sensor packages to the cable's sensor ports. 3. Repeat the above steps if there are additional SENSOR ports on your EMX.

  • Page 59: Dpx Sensor Packages

    Sensor Connection Restrictions:  Connect a DPX sensor package to the EMX using the sensor cable pre-installed (or provided) by Raritan. You MUST NOT extend or modify the sensor cable's length by using any tool other than the Raritan's sensor hubs.

  • Page 60: Dpx2 Sensor Packages

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

  • Page 62: Dpx3 Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) 3. Plug the RJ-12 connector of the DPX2 sensor cable into the RJ-12 SENSOR port on the EMX. OR you can directly connect the DPX2 sensor package to a DX sensor chain without using any RJ-12 to RJ-45 adapter. See (on page 52).

  • Page 63: Dpx3 Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) To connect DPX3 sensor packages to the EMX: 1. Connect an RJ-12 to RJ-45 adapter cable to the DPX3 sensor package.  Connect the adapter's RJ-45 connector to either RJ-45 port of the DPX3 sensor package. 2.

  • Page 64: Dpx3 Sensor Packages

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

  • Page 65: Dx Sensor Packages

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

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

    Plug the RJ-45 connector of this cable into the IN port (Port 1) of the hub. b. Plug the RJ-12 connector of this cable into the RJ-12 SENSOR port of the EMX. 2. Connect the Raritan sensor packages to any of the four OUT ports on the hub.
  • Page 68 An RJ-12 to RJ-45 adapter is required for connecting a DPX or DPX2 sensor package to the hub. This diagram illustrates a configuration with a sensor hub connected. The EMX RJ-12 to RJ-45 adapter cable DPX3-ENVHUB4 sensor hub Any Raritan sensor packages...

  • Page 69: Mixing Diverse Sensor Types

    Chapter 4: Connecting External Equipment (Optional) Mixing Diverse Sensor Types You can mix DPX, DPX2, DPX3 and DX sensor packages on any sensor port of the EMX2-888 or EMX2-111 according to the following sensor combinations. In some scenarios, the DPX3-ENVHUB4 sensor hub is required.
  • Page 70 Chapter 4: Connecting External Equipment (Optional)  An RJ-12 to RJ-45 adapter is recommended to connect a DPX or DPX2 sensor package to DPX3-ENVHUB4.  In the following diagrams, the sensor package in "green" can be replaced by a DPX2 sensor package. The sensor package in "blue" can be one DPX2, DPX3 or DX sensor package.
  • Page 71 Chapter 4: Connecting External Equipment (Optional)

  • Page 72: Dpx3 Sensor Packages

    Chapter 4: Connecting External Equipment (Optional) Mix DPX3 and DX in a sensor chain: Any DX sensor package in a chain can be replaced by a DPX3 sensor package. For example, the following diagram shows a sensor chain comprising both DX and DPX3 sensor packages. The total number of sensor packages in this chain cannot exceed 12.

  • Page 73: Connecting A Logitech Webcam

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

  • Page 74: Connecting A Gsm Modem

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

  • Page 75: Connecting An External Beeper

    Chapter 4: Connecting External Equipment (Optional) You need to enable the modem dial-in support to take advantage of this feature, see (on page 135). Configuring the Serial Port Connecting an External Beeper The EMX supports the use of an external beeper for audio alarms. External beepers that are supported include but may not be limited to the following: ...
  • Page 76 Chapter 4: Connecting External Equipment (Optional) To connect an SHX-30 heat exchanger: 1. Plug one end of the Schroff adapter cable into the RS-485 port on the Schroff SHX heat exchanger. 2. Plug the other end of the adapter cable into one of available RS-485 ports on your EMX.

  • Page 77: Connecting The Schneider Electric Powerlogic Pm710

    Note: EMX2-888 does not support the PowerLogic PM710. This device is only supported when plugged into the RS485 port using a PM710 supported cable (not provided by Raritan with the EMX). Refer to your Schneider Electric PowerLogic PM710 documentation for information on the pinouts for the meter.

  • Page 78: Chapter 5 Using The Emx

    Chapter 5 In This Chapter Power Switch...................64 Connection Ports ..................64 LCD Display Panel ..................66 EMX2-888 Contact Closure Sensor Termination ........76 Reset Button....................82 Beeper .....................82 Power Switch A power switch turns on or off the EMX. EMX2-111 front panel power switch:...
  • Page 79 Used for... SENSOR (RJ-12) Connection to one of the following devices:  Raritan's environmental sensor package(s). Raritan's sensor hub, which expands the number of a sensor  port to four ports. RS-485 Connection to an electrical device with the RS-485 interface.

  • Page 80: Lcd Display Panel

     Establishing a USB connection between a computer and the EMX for using the command line interface or performing the disaster recovery. For disaster recovery instructions, contact Raritan Technical Support. LCD Display Panel The LCD display panel shows the sensor reading or status, asset management states and the device's IP or MAC address.

  • Page 81: Overview Of The Lcd Display

     A discrete (on/off) sensor enters the alarmed state.  NO asset tag is detected on the selected rack unit. Note: For the Raritan asset sensor, a rack unit refers to a tag port. The measurement unit of the displayed data, such as % This section indicates: ...

  • Page 82: Control Buttons

    Chapter 5: Using the EMX Control Buttons There are four control buttons.  Up and Down buttons for selecting a specific target, which can be an environmental sensor's ID number or an asset sensor's port number  MODE button for switching between various modes, including: - Sensor mode - Asset Sensor mode, indicated by the word ASSET, for showing the asset sensor information...
  • Page 83 Chapter 5: Using the EMX Number Example information The selected environmental sensor's reading is 22 The word "MASTER" indicates the EMX is the master device in a USB-cascading configuration. See Cascading (on page 22). the EMX via USB Note: For a standalone EMX, this word is NOT displayed. For a slave device, it shows "SLAVE"...
  • Page 84 Chapter 5: Using the EMX States Description The actuator is turned on. The actuator is turned off. Note: Numeric sensors show both numeric readings and sensor states to indicate environmental or internal conditions while discrete (on/off) sensors show sensor states only to indicate state changes. 4.
  • Page 85 Asset Sensor Information The LCD display can show the asset sensor state on each FEATURE port as well as the asset tag state of each rack unit. For the Raritan asset sensor, a rack unit refers to a tag port.
  • Page 86 Chapter 5: Using the EMX If no asset sensor is physically connected to the selected FEATURE port, the term "nA" appears. 3. Press the FUNC button. When a blinking double-arrow symbol appears to the left of the LCD display, press the Up or Down button to select the desired rack unit on the asset sensor.
  • Page 87 Chapter 5: Using the EMX If you connect your EMX to the wireless network, a Wi-Fi icon is displayed at the bottom-right corner. To display the IPv4 address: 1. Press the MODE button to enter the Device mode, indicated by an alphabet "d"...

  • Page 88: Usb-Cascaded Device's Position

    Chapter 5: Using the EMX Section Example information The word "MASTER" indicates the EMX is the master device in a USB-cascading configuration. See (on page 22). Cascading the EMX via USB Note: For a standalone EMX, this word is NOT displayed. For a slave device, it shows "SLAVE"...
  • Page 89 Chapter 5: Using the EMX Section Example information "d" means the LCD display has entered the Device mode. "CA" indicates that the USB-cascading information is being displayed. "SLAVE" indicates that this EMX is a slave device. Note: For a master device, it shows the word "MASTER" instead.

  • Page 90: Emx2-888 Contact Closure Sensor Termination

    Connect third-party detectors/switches to the CC sensor termination on your EMX2-888. Exception: Older EMX2-888 models have the "spring-loaded" CC sensor termination built into EMX2-888 so they do not use a detachable terminal module. See Connecting Contact Closure Sensors to OLD EMX2-888 (on page 541).

  • Page 91: Connecting Contact Closure Sensors To Emx2-888

     To set to Normally Open (N.O), press the button to turn it up. Tip: Alternatively, third-party CC switches can be connected to Raritan's DPX-CC2-TR or DX sensor package, which is then connected to a SENSOR port on the EMX. For sensor information, refer to the...
  • Page 92 Chapter 5: Using the EMX The two termination points to the right are associated with channel 1 (CC1 as indicated in the panel), and the two to the left are associated with channel 2 (CC2). With this design, there are two ways to plug discrete detectors/switches: ...
  • Page 93 Chapter 5: Using the EMX 3. Use a screwdriver with a 2.5 mm wide shaft to tighten the screws above each termination point to secure the wires, using a torque of 0.196 N·m (2 kgf·cm). To make connections when the terminal module is separated from the EMX: 1.
  • Page 94 Chapter 5: Using the EMX 3. Strip the insulation and insert each wire of both detectors/switches into each termination point. 4. Use a screwdriver with a 2.5 mm wide shaft to tighten the screws above each termination point to secure the wires, using a torque of 0.196 N·m (2 kgf·cm).

  • Page 95: Emx2-888 Contact Closure Sensor Leds

    6. Tighten the two screws on two sides of the module to secure it. EMX2-888 Contact Closure Sensor LEDs Two LEDs that show the states of corresponding CC sensor channels are located on the leftmost of the EMX2-888 panel.  The upper LED is for CC2.

  • Page 96: Reset Button

    Chapter 5: Using the EMX For Raritan's DPX water sensors, the Normal state must be set to Normally Open (N.O). The following is the correct LED behavior based on proper dip switch settings. Sensor state No water detected Water detected Reset Button The reset button is located inside a small hole which is labeled RESET.

  • Page 97: Chapter 6 Using The Web Interface

    Chrome 32 and later ® ®  Android 4.2 and later  IOS 7.0  Windows Edge ® Note: Tablets such as iPad are supported but not recommended for use with EMX2-888. Smartphones are not supported for use with EMX2-888.

  • Page 98: Logging In To The Web Interface

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

  • Page 101: Changing Your Password

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

  • Page 102: Introduction To The Web Interface

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

  • Page 103: Menus

    Chapter 6: Using the Web Interface Data pane Dashboard * The Setup button is not available on some pages, such as the Dashboard page. For detailed information about these web interface elements, see the sections that follow. Menus  User Management contains user profiles, permissions, and password settings.
  • Page 104 Chapter 6: Using the Web Interface First level Second level Third level Auxiliary Ports (RS-485) If one of the following is connected:  LHX-20  SHX-30  LHX-40  PowerLogic PM710  Snapshots **Webcam Snapashots  Webcam...
  • Page 105 Chapter 6: Using the Web Interface *The EMX folder is named "EMX" by default. The name can be customized. See (on page 110). Naming the EMX ** A Webcam icon appears only when a supported Logitech webcam is ® connected to the EMX. See (on page Connecting a Logitech Webcam 59).
  • Page 106 Chapter 6: Using the Web Interface Expanding the Tree The icons representing all components implemented on or connected to the EMX device are expanded by default. If they are hidden, you may expand the tree manually to show all component icons. To expand the tree: 1.
  • Page 107 Chapter 6: Using the Web Interface 3. Repeat Step 2 for other component groups you want to expand. The expanded tree looks similar to this image.
  • Page 108 Chapter 6: Using the Web Interface Collapsing the Tree You can collapse the whole tree structure or a specific component group to hide all or partial tree items. To collapse the whole tree:  Click the black, gradient arrow prior to the EMX folder icon, or double-click the folder.
  • Page 109 Chapter 6: Using the Web Interface 2. Select the number of the port that you want to configure, and click Setup. Or you can simply double-click that port number. The Feature Port Setup dialog for the selected port appears. 3. In the Detection Mode field, select the way to display connected asset sensors.

  • Page 110: Setup Button

    Chapter 6: Using the Web Interface 3. In the Detection Mode field, select the way to display connected LHX/SHX heat exchangers.  Disabled: When applied, disables to port and nothing connected to the port is detected.  Auto: An icon is displayed for this port only when the EMX device detects the physical connection of the LHX/SHX heat exchanger on this port.

  • Page 111: Add Page Icon

    Chapter 6: Using the Web Interface  Login name: This is the user name you used to log in to the web interface.  Last login time: This shows the date and time this login name was used to log in to this EMX device last time.

  • Page 112: Data Pane

    Chapter 6: Using the Web Interface 2. Click a tree item whose data page you want to open. The data of the selected tree item is then displayed on the blank page. 3. To open more data pages, repeat the above steps. All tabs representing opened pages are shown across the top of the page.

  • Page 113: More Information

    Chapter 6: Using the Web Interface 2. When the mouse pointer turns into a two-way arrow, drag the border horizontally to widen or shrink the pane. More Information This section explains additional web interface elements or operations that are useful. Warning Icon If the value you entered in a specific field is invalid, a red warning icon appears to the right and the field in question is surrounded by a red...
  • Page 114 Chapter 6: Using the Web Interface The Yellow- or Red-Highlighted Sensors When a numeric sensor's reading enters the warning or critical range, the background color of the sensor row turns to yellow or red for alerting you. For a discrete (on/off) sensor, the row changes the background color when the sensor enters the abnormal state.
  • Page 115 Chapter 6: Using the Web Interface To find the exact meaning of the alert, read the information shown in the State (or Status) column:  below lower critical: The numeric sensor's reading drops below the lower critical threshold.  below lower warning: The numeric sensor's reading drops below the lower warning threshold.
  • Page 116 Chapter 6: Using the Web Interface Browser-Defined Shortcut Menu A shortcut menu, which is built in the web browser, may appear when right-clicking anywhere in the EMX web interface. The shortcut menu functions are defined by the browser. For example, the Back command on the Internet Explorer (IE) shortcut menu works ®...

  • Page 117: Dashboard

    Chapter 6: Using the Web Interface Dashboard When you log in to the web interface, the Dashboard page is displayed by default. This page provides an overview of the EMX device's status.
  • Page 118 Chapter 6: Using the Web Interface The page is divided into several sections according to connected equipment, such as asset sensors and environmental sensors. Double-clicking any item on the Dashboard page opens the data page specific to the selected item. Note: If a sensor reading row is colored, it means the sensor reading already crosses one of the thresholds, or at least one LHX built-in sensor fails on the heat exchanger.

  • Page 119: Alarms List

    Chapter 6: Using the Web Interface Alarms List You can create event rules that request users to acknowledge certain alerts, and resend alert notifications if the acknowledgment action is not taken yet. See (on page 188). Creating Actions If any of these alerts has not been acknowledged since its occurrence, the Alarms section on the dashboard shows this alert until it is acknowledged.

  • Page 120: Alerted Sensors

    Chapter 6: Using the Web Interface Column Description Details Click "Details" to trigger a dialog showing both the alarm details and the acknowledgment button. Only users who have the Acknowledge Alarms permission can manually acknowledge an alarm. To acknowledge an alarm: 1.
  • Page 121 For information on how to cascade devices using USB cables, see (on page 22). Cascading the EMX via USB Note: For more information on the USB-cascading configuration, see the USB-Cascading Solution Guide, which is available from Raritan website's Support page (http://www.raritan.com/support/).
  • Page 122 Chapter 6: Using the Web Interface Fields Description Cascade Position Indicates the position of the EMX in the USB-cascading configuration.  0 (zero) represents the master device.  A non-zero number represents a slave device. 1 is Slave 1, 2 is Slave 2, 3 is Slave 3 and so on. This field is NOT available on a standalone EMX.
  • Page 123 Chapter 6: Using the Web Interface The following diagram shows 1, indicating it is the first slave - Slave 1.  The final slave device shows a non-zero number which indicates its position in the Cascade Position field and no in the Cascaded Device Connected field.

  • Page 124: Naming The Emx

    Chapter 6: Using the Web Interface The following diagram shows 2, indicating it is the second slave - Slave 2. The Cascaded Device Connected field shows no, indicating that it is the final one in the chain. Naming the EMX To change the device name: 1.
  • Page 125 Chapter 6: Using the Web Interface Modifying Network Interface Settings The EMX supports two types of network interfaces: wired and wireless. You should configure the network interface settings according to the networking mode that applies. See Connecting the EMX to Your (on page 14).
  • Page 126 Chapter 6: Using the Web Interface Wireless Network Settings Wireless SSID, PSK and BSSID parameters were set during the installation and configuration process. You can change them later. Note for USB-cascading configuration: Port forwarding mode over wireless LAN is supported as of release 3.1.0. You must upgrade all devices in the chain to version 3.1.0 or higher if wireless networking is preferred.
  • Page 127 Chapter 6: Using the Web Interface Options Description EAP - PEAP PEAP stands for Protected Extensible Authentication Protocol. Enter the following authentication data:  Inner Authentication: Only Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) is supported, allowing authentication to databases that support MSCHAPv2.
  • Page 128 Chapter 6: Using the Web Interface Modifying Network Settings The EMX was configured for network connectivity during the installation and configuration process. See (on page 10). If Configuring the EMX necessary, you can modify any network settings later. Selecting the Internet Protocol The EMX device supports two types of Internet protocols -- IPv4 and IPv6.
  • Page 129 Chapter 6: Using the Web Interface Modifying IPv4 Settings You must enable the IPv4 protocol before you can modify the IPv4 network settings. See (on page 114). Selecting the Internet Protocol To modify IPv4 settings: 1. Choose Device Settings > Network. The Network Configuration dialog appears.
  • Page 130 Chapter 6: Using the Web Interface Option Description mask using the format "IP address/subnet mask."  Next Hop: IP address of the next hop router. (on page 118) for illustrations. Static Route Examples 4. Click OK. Note: The EMX supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the EMX only uses the primary IPv4 and IPv6 DNS servers.
  • Page 131 Chapter 6: Using the Web Interface Option Description  IP address  Default gateway  Primary DNS server  Secondary DNS server (optional)  DNS Suffix (optional) If your local network contains two subnets and IP forwarding has been enabled, you can click Append to add static routes so that your EMX can communicate with the other subnet.
  • Page 132 Chapter 6: Using the Web Interface Static Route Examples This section has two static route examples: IPv4 and IPv6. Both examples assume that two network interface controllers (NIC) have been installed in one network server, leading to two available subnets, and IP forwarding has been enabled.
  • Page 133 Chapter 6: Using the Web Interface In this example, NIC-2 (192.168.100.88) is the next hop router for your EMX to communicate with any device in the other subnet 192.168.200.0. In the IPv4 "Append new Route" dialog, you should specify:  Destination: 192.168.200.0/24 ...

  • Page 134: Modifying Network Service Settings

    In addition, the EMX also supports the SNMP and Modbus/TCP protocols. Changing HTTP(S) Settings Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail...
  • Page 135 Chapter 6: Using the Web Interface HTTPS uses Transport Layer Security (TLS) technology to encrypt all traffic to and from the EMX device so it is a more secure protocol than HTTP. By default, any access to the EMX device via HTTP is automatically redirected to HTTPS.
  • Page 136 Chapter 6: Using the Web Interface Configuring SNMP Settings You can enable or disable SNMP communication between an SNMP manager and the EMX device. Enabling SNMP communication allows the manager to retrieve information or configure the EMX. Besides, you may need to configure the SNMP destination(s) if the built-in "System SNMP Notification Rule"...
  • Page 137 Chapter 6: Using the Web Interface To configure SNMP notification destinations: 1. Click the Notifications tab in the same SNMP dialog. 2. Select the Enabled checkbox. 3. Select an SNMP notification type - SNMP v2c Trap, SNMP v2c Inform, SNMP v3 Trap, and SNMP v3 Inform. 4.
  • Page 138 Chapter 6: Using the Web Interface Changing Telnet Settings You can enable or disable the Telnet access to the command line interface, or change the default TCP port for the Telnet service. To change Telnet service settings: 1. Choose Device Settings > Network Services > Telnet. The Telnet Settings dialog appears.
  • Page 139 Chapter 6: Using the Web Interface c. Connect the RS232-to-USB adapter to the USB-A port on the EMX. Note: DO NOT connect the Modbus RTU device or Modbus bus to the RS485 ports on the EMX, which is NOT supported. 2.
  • Page 140 Chapter 6: Using the Web Interface TCP Port - Required Use the default port 503, or assign a different port. Valid range is 1 to 65535. Port 502 is the default Modbus/TCP port for EMX, so you cannot use that port for the Modbus Gateway. Parity and Line Speed - Required Use the default settings, or update if the Modbus RTU devices are using different communication parameters.

  • Page 141: Setting The Date And Time

    Chapter 6: Using the Web Interface Enabling Service Advertisement The EMX advertises all enabled services that are reachable using the IP network. This feature uses DNS-SD (Domain Name System-Service Discovery) and mDNS (multicastDNS). The advertised services are discovered by clients that have implemented DNS-SD and mDNS. The advertised services include the following: ...
  • Page 142 Chapter 6: Using the Web Interface If the daylight saving time rules are not available for the selected time zone, the checkbox is not configurable. 4. Choose one of the methods to set the date and time:  To customize the date and time, select the User Specified Time radio button, and then enter the date and time in appropriate fields.
  • Page 143 Chapter 6: Using the Web Interface How to Use the Calendar The calendar icon next to the Date field is a convenient tool to quickly change the year, month and date. To select a date using the calendar: 1. To change the year shown in the calendar, do either of the following: ...
  • Page 144 Chapter 6: Using the Web Interface  Click on the top of the calendar to switch between months.  Click , which is adjacent to the year, to show a list of years and months. Select the desired month from the list to the left and click OK.

  • Page 145: Setting Default Measurement Units

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

  • Page 146: Configuring The Feature Port

    Chapter 6: Using the Web Interface Configuring the Feature Port The EMX device supports connecting one of the following devices to its FEATURE port:  Raritan asset management sensors (asset sensors). See (on page 25). Connecting Asset Management Sensors  External beeper. See...

  • Page 147: Configuring The Auxiliary Port

    Chapter 6: Using the Web Interface Device type Description LHX 20 Schroff LHX-20 heat exchanger. ® All Schroff SHX/LHX device types are available only ® after the LHX/SHX support is enabled. See Enabling and Disabling Schroff LHX/SHX Heat Exchanger (on page 273). Support SHX 30 Schroff...
  • Page 148 Chapter 6: Using the Web Interface  LHX-20  SHX-30  LHX-40  PowerLogic PM710...

  • Page 149: Configuring The Serial Port

    Note: The serial port bit-rate change is needed when the EMX works in conjunction with Raritan's Dominion LX KVM switch. The Dominion LX only supports 19200 bps for communications over the serial interface. You can set diverse bit-rate settings for console and modem operations.

  • Page 150: Setting The Cascading Mode

    Chapter 6: Using the Web Interface To configure the analog modem settings: 1. Click the Analog Modem tab. 2. Select the "Answer incoming calls" checkbox to enable the remote access via a modem. Otherwise, deselect this checkbox. 3. Specify the number of rings the EMX must wait before answering the call.
  • Page 151 Chapter 6: Using the Web Interface 3. Verify that the "Position in cascaded chain" field shows 0 (Master), indicating that this EMX is the master device. 4. Select the preferred cascading mode in the "Cascading mode" field.  Bridging: Each device in the USB-cascading configuration is accessed with a different IP address.
  • Page 152 Chapter 6: Using the Web Interface Overview of the Cascading Modes You must apply a cascading mode to the USB-cascading configuration. (on page 136). Setting the Cascading Mode Overview:  The Bridging mode supports the wired network only while the Port Forwarding mode supports both wired and wireless networks.
  • Page 153 Chapter 6: Using the Web Interface  "Port Forwarding" mode: The DHCP server communicates with the master device only and assigns one IP address. All slave devices use the same IP address as the master device. You must specify a 5XXXX port number (where X is a number) when remotely accessing any slave device through the network.
  • Page 154 Chapter 6: Using the Web Interface Position Slave 2 Slave 3 Slave 4 Slave 5 Slave 6 Slave 7 For example, to access the Slave 4 device via Modbus/TCP, the port number is 50604. See (on page 141) for Port Forwarding Examples further illustrations.
  • Page 155  Slave device: Assign proper 5NNXX port numbers. Assumption: The Port Forwarding mode is applied to a USB-cascading configuration comprising three Raritan products. The IP address is 192.168.84.77. Master device: Position code for the master device is 00 so each port number is 5NN00 as shown below.
  • Page 156 Chapter 6: Using the Web Interface Slave 1 device: Position code for Slave 1 is 01 so each port number is 5NN01 as shown below. Protocols Port numbers HTTPS 50001 HTTP 50101 50201 TELNET 50301 SNMP 50501 MODBUS 50601 Examples: ...

  • Page 157: Specifying The Device Altitude

    -p 50202 192.168.84.77 Specifying the Device Altitude You must specify the EMX device's altitude above sea level if a Raritan's DPX differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor. See (on page 539).

  • Page 158: Setting Data Logging

    Chapter 6: Using the Web Interface Setting Data Logging The EMX can store 120 measurements for each sensor in a memory buffer. This memory buffer is known as the data log. Sensor readings in the data log can be retrieved using SNMP. You can configure how often measurements are written into the data log using the Measurements Per Log Entry field.

  • Page 159: Configuring Smtp Settings

     High priority type: Sensor readings or states are updated in a shorter interval, which is less than or equal to 3 seconds. Raritan contact closure sensors belong to this type. Configuring SMTP Settings The EMX can be configured to send alerts or event messages to a specific administrator by email.
  • Page 160 Chapter 6: Using the Web Interface 7. If your SMTP server requires password authentication, do this: a. Select the Server Requires Authentication checkbox. b. Type a user name in the User Name field. c. Type a password in the Password field. 8.

  • Page 161: Configuring Data Push Settings

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

  • Page 162: Checking The Internal Beeper State

    Chapter 6: Using the Web Interface  To remove the asset sensor, select it in the Selected list box and click (Remove) or (Remove All). 7. Click OK. Checking the Internal Beeper State The internal beeper of the EMX always turns OFF if there are no event rules that involve this beeper.

  • Page 163: User And Role Management

    Chapter 6: Using the Web Interface User and Role Management The EMX is shipped with one built-in user profile: admin, which is used for initial login and configuration. This profile has full system permissions, and should be reserved for the system administrator.
  • Page 164 Chapter 6: Using the Web Interface Field Type this...  Case sensitive 4. Select the Enabled checkbox. Enabled users can log in to the EMX device. 5. Select the "Force password change on next login" checkbox if you prefer a password change by the user when the user logs in for the first time after this checkbox is enabled.
  • Page 165 Chapter 6: Using the Web Interface Field Description printable characters. Confirm Re-type the same authentication pass phrase for Authentication confirmation. Pass Phrase Use Authentication This checkbox is configurable only if AuthPriv is Pass Phrase as selected. Privacy Pass When the checkbox is selected, the privacy pass Phrase phrase is identical to the authentication pass phrase.

  • Page 166: Modifying A User Profile

    Chapter 6: Using the Web Interface  If no roles meet your needs, you can:  Modify the permissions of an existing role: To modify the permissions of any role, double-click the role or highlight it and then click Edit Role. See (on page Modifying a Role 155).

  • Page 167: Deleting A User Profile

    Chapter 6: Using the Web Interface 5. To change the SNMPv3 access permissions, click the SNMPv3 tab and make necessary changes. For details, see Step 6 of Creating a (on page 149). User Profile 6. To change the permissions, click the Roles tab and do one of these: Select or deselect any role's checkbox.

  • Page 168: Setting Up Roles

    Chapter 6: Using the Web Interface Note: The measurement unit change only applies to the web interface and command line interface. Setting your preferences does not change the default measurement units, which apply to all users before any individual user or the administrator sets preferred measurement units on a per-user basis.

  • Page 169: Creating A Role

    Chapter 6: Using the Web Interface Creating a Role Create a new role when you need a new combination of permissions. To create a role: 1. Choose User Management > Roles. The Manage Roles dialog appears. Tip: You can also access the Manage Roles dialog by clicking the Manage Roles button in the Edit User 'XXX' dialog.

  • Page 170: Deleting A Role

    Chapter 6: Using the Web Interface 4. Modify the text shown in the Description field if necessary. 5. To change the permissions, click the Privileges tab. Note: You cannot change the Admin role's permissions. 6. To delete any permissions, do this: a.

  • Page 171: Access Security Control

    Chapter 6: Using the Web Interface 2. Select the role you want to delete by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones. 3. Click Delete. 4. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion.
  • Page 172 Chapter 6: Using the Web Interface Enabling the Firewall The firewall rules, if any, take effect only after the firewall is enabled. To enable the EMX firewall: 1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears. 2.
  • Page 173 Chapter 6: Using the Web Interface b. Ensure the Enable IPv6 Access Control checkbox is selected. c. Locate the Default Policy field in the Inbound Rules section. d. The default policy is shown in the Default Policy field. To change it, select a different policy from the drop-down list.
  • Page 174 Chapter 6: Using the Web Interface Note: Valid IPv4 addresses range from 0.0.0.0 through 255.255.255.255. Make sure the IPv4 addresses entered are within the scope. To create firewall rules: 1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears.
  • Page 175 Chapter 6: Using the Web Interface Action Procedure Insert a rule between two  Select the rule above which you want to insert a new rule. For existing rules example, to insert a rule between rules #3 and #4, select #4. ...
  • Page 176 Chapter 6: Using the Web Interface 6. When finished, the rules appear in the Configure IP Access Control Settings dialog. 7. Click OK. The rules are applied. Editing Firewall Rules When an existing firewall rule requires updates of IP address range and/or policy, modify them accordingly.
  • Page 177 Chapter 6: Using the Web Interface 2. To modify the IPv4 firewall rules, click the IPv4 tab. To modify the IPv6 firewall rules, click the IPv6 tab. 3. Ensure the Enable IPv4 Access Control checkbox is selected on the IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab.

  • Page 178: Setting Up User Login Controls

    Chapter 6: Using the Web Interface 3. Ensure the Enable IPv4 Access Control checkbox is selected on the IPv4 tab, or the Enable IPv6 Access Control checkbox is selected on the IPv6 tab. 4. Select the rule that you want to delete. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
  • Page 179 Chapter 6: Using the Web Interface  X min: This type of option sets the time limit to X minutes, where X is a number.  X h: This type of option sets the time limit to X hours, where X is a number.
  • Page 180 Chapter 6: Using the Web Interface Enabling Strong Passwords Use of strong passwords makes it more difficult for intruders to crack user passwords and access the EMX device. By default, strong passwords should be at least eight characters long and contain upper- and lower-case letters, numbers, and special characters, such as @ or &.
  • Page 181 Chapter 6: Using the Web Interface Tip: If the desired time option is not listed, you can manually type the desired time in this field. For example, you can type "9 d" to set the password aging time to 9 days. 4.

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

    Chapter 6: Using the Web Interface If the Restricted Service Agreement feature is enabled, the Restricted Service Agreement is displayed when any user logs in to the EMX. Do either of the following, or you cannot successfully log in to the EMX: ...
  • Page 183 Chapter 6: Using the Web Interface Changing the Default Policy The default policy is to accept all traffic from all IP addresses regardless of the role applied to the user. To change the default policy: 1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears.
  • Page 184 Chapter 6: Using the Web Interface 3. Ensure the "Enable Role Based Access Control for IPv4" checkbox is selected on the IPv4 tab, or the "Enable Role Based Access Control for IPv6" checkbox is selected on the IPv6 tab. 4. Create specific rules: Action Do this...
  • Page 185 Chapter 6: Using the Web Interface Action Do this... role  Click OK. The system inserts the rule and automatically renumbers the following rules. 5. Click OK. Editing Role-Based Access Control Rules You can modify existing rules when these rules do not meet your needs. To modify a role-based access control rule: 1.

  • Page 186: Setting Up A Tls Certificate

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

  • Page 187: Certificate Signing Request

    Chapter 6: Using the Web Interface Having an X.509 digital certificate ensures that both parties in an TLS connection are who they say they are. To obtain a certificate for the EMX, create a Certificate Signing Request (CSR) and submit it to a certificate authority (CA). After the CA processes the information in the CSR, it provides you with a certificate, which you must install on the EMX device.
  • Page 188 Chapter 6: Using the Web Interface Field Type this information Common Name The fully qualified domain name (FQDN) of your EMX device. Email Address An email address where you or another administrative user can be reached. Note: All fields in the Subject section are mandatory, except for the Organization, Organizational Unit and Email Address fields.

  • Page 189: Creating A Self-Signed Certificate

    Chapter 6: Using the Web Interface Installing a CA-Signed Certificate After the CA provides a signed certificate according to the CSR you submitted, you must install it on the EMX device. To install the certificate: 1. Choose Device Settings > Security > SSL Certificate. The Manage SSL Certificate dialog appears.
  • Page 190 Chapter 6: Using the Web Interface Field Type this information Key Length Select the key length (bits) from the drop-down list in this field. A larger key length enhances the security, but slows down the EMX device's response. Self Sign Ensure this checkbox is selected, which indicates that you are creating a self-signed certificate.

  • Page 191: Installing Existing Key And Certificate Files

    Chapter 6: Using the Web Interface Installing Existing Key and Certificate Files If the TLS certificate and private key files are already available, you can install them directly without going through the process of creating a CSR or a self-signed certificate. Note: If you are using a TLS certificate that is part of a chain of certificates, each part of the chain is signed during the validation process.

  • Page 192: Setting Up External Authentication

    Only users who have the "Change Authentication Settings" permission can set up or modify the authentication settings. Important: Raritan disables SSL 3.0 and uses TLS for releases 3.0.4, 3.0.20 and later releases due to published security vulnerabilities in SSL 3.0. Make sure your network infrastructure, such as LDAP and mail services, uses TLS rather than SSL 3.0.
  • Page 193 Chapter 6: Using the Web Interface Gathering the LDAP Information It requires knowledge of your LDAP server and directory settings to configure the EMX for LDAP authentication. If you are not familiar with the settings, consult your LDAP administrator for help. To configure LDAP authentication, you need to check: ...

  • Page 194: Adding Authentication Servers

    Chapter 6: Using the Web Interface Adding Authentication Servers Add all external AA servers that you want to use to the EMX. Later you can use the sequence of the server list to control the AA servers' access priority. Adding LDAP Server Settings To activate and use external LDAP/LDAPS server authentication, enable LDAP authentication and enter the information you have gathered for any LDAP/LDAPS server.
  • Page 195 Chapter 6: Using the Web Interface  None 7. Port (None/StartTLS) - The default Port is 389. Either use the standard LDAP TCP port or specify another port. 8. Port (TLS) - The default is 636. Either use the default port or specify another port.
  • Page 196 LDAP/LDAPS (up to 31 characters), and where in the database to begin searching for the specified Base DN. An example Base Search value might be: cn=Users,dc=raritan,dc=com. Consult your AA server administrator for the appropriate values to enter into these fields.
  • Page 197 Chapter 6: Using the Web Interface Note: If the EMX 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 EMX and the LDAP server to use the same NTP server(s).

  • Page 198: Sorting The Access Order

    Chapter 6: Using the Web Interface 10. To verify if the authentication configuration is set correctly, you may click Test Connection to check whether the EMX can connect to the remote authentication server successfully. Tip: You can also do this by using the Test Connection button in the Authentication Settings dialog.

  • Page 199: Editing Authentication Server Settings

    Chapter 6: Using the Web Interface Editing Authentication Server Settings If the configuration of any external authentication server has been changed, such as the port number, you must modify the authentication settings on the EMX device accordingly, or the authentication fails. To modify the external authentication configuration: 1.

  • Page 200: Enabling External And Local Authentication Services

    Chapter 6: Using the Web Interface Enabling External and Local Authentication Services To make authentication function properly all the time - even when external authentication is not available, you can enable both the local and remote authentication services. When both authentication services are enabled, the EMX follows these rules for authentication: ...

  • Page 201: Event Rules And Actions

    Chapter 6: Using the Web Interface Event Rules and Actions A benefit of the product's intelligence is its ability to notify you of and react to a change in conditions. This event notification or reaction is an "event rule." The EMX is shipped with four built-in event rules, which cannot be deleted.

  • Page 202: Creating An Event Rule

    Chapter 6: Using the Web Interface Creating an Event Rule The best way to create a new set of event rules in sequence is to:  Create actions for responding to one or multiple events  Create rules to determine what actions are taken when these events occur Creating Actions The EMX comes with three built-in actions:...
  • Page 203 Chapter 6: Using the Web Interface Action Function Execute an action Creates a group of actions comprising existing group actions. See (on page 190). Action Group Alarm Requires the user to acknowledge the alert when it is generated. If needed, you can have the alert notifications regularly generated until a person takes the acknowledgment action.
  • Page 204 Chapter 6: Using the Web Interface Action Function Switch LHX/SHX Switches on or off the LHX/SHX device. See (on page 205). Switch LHX/SHX This option is available only when the Schroff LHX/SHX support has been enabled. Record snapshots to Makes a connected webcam start or stop webcam storage taking snapshots.
  • Page 205 Chapter 6: Using the Web Interface 7. To remove an action from the action group, select it from the Used Actions list box, and click to move it to the Available Actions list box. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones.
  • Page 206 Chapter 6: Using the Web Interface b. Click to add the selected method to the Alarm Notifications list box. c. Repeat the above steps to add more methods if needed.  To remove any method from the Alarm Notifications list box, select that method and click 6.
  • Page 207 Chapter 6: Using the Web Interface 3. In the "Action name" field, type a new name for the action. The default name is New Action <number>, where <number> is a sequential number starting at 1. 4. In the Action field, click the drop-down arrow and select the desired action: External beeper.
  • Page 208 Chapter 6: Using the Web Interface Push Out Sensor Readings If you have connected Raritan's asset sensors to the EMX, you can configure the EMX to push asset sensor data to a remote server after a certain event occurs. Before creating this action, make sure that you have properly defined the destination servers and the sensor data type in the Data Push dialog.
  • Page 209 Chapter 6: Using the Web Interface Request LHX/SHX Maximum Cooling If Schroff LHX/SHX Support is enabled, the LHX/SHX-related actions will be available. See Enabling and Disabling Schroff LHX/SHX Heat (on page 273). Exchanger Support The "Request LHX/SHX Maximum Cooling" action applies the maximum cooling to the SHX-30 device only.
  • Page 210 Chapter 6: Using the Web Interface To use a different SMTP server, select the Use Custom SMTP Settings checkbox. If the SMTP server settings are not configured yet, click Configure. (on page 145) for the information Configuring SMTP Settings of each field. 8.
  • Page 211 Chapter 6: Using the Web Interface 4. In the "Action name" field, type a new name for the action. The default name is New Action <number>, where <number> is a sequential number starting at 1. 5. In the Action field, click the drop-down arrow and select the desired action: Send email.
  • Page 212 Chapter 6: Using the Web Interface 5. In the Action field, click the drop-down arrow and select the desired action: Send SNMP notification. 6. Select the type of SNMP notification. See either procedure below according to your selection. To send SNMP v2c notifications: 1.
  • Page 213 Chapter 6: Using the Web Interface b. In the Number of Retries field, enter the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails.
  • Page 214 Chapter 6: Using the Web Interface Syslog Message Use this action to automatically forward event messages to the specified syslog server. Determine the syslog transmission mechanism you prefer when setting it up - UDP, TCP or TLS over TCP. The EMX may or may not detect the syslog message transmission failure. If yes, it will log this syslog failure as well as the failure reason in the event log.
  • Page 215  Overcurrent protector sensors, including RMS current and tripping state.  Peripheral device sensors, which can be any Raritan environmental sensor packages connected to the EMX, such as temperature or humidity sensors. To configure a sensor report action: 1. Choose Device Settings > Event Rules. The Event Rules Settings dialog opens.
  • Page 216 Chapter 6: Using the Web Interface 4. In the "Action name" field, type a new name for the action. The default name is New Action <number>, where <number> is a sequential number starting at 1. 5. In the Action field, click the drop-down arrow and select the desired action: Send sensor report.
  • Page 217 Chapter 6: Using the Web Interface 10. To save this action, click OK. Note: When intending to send a sensor report using custom messages, use the placeholder [SENSORREPORT] to report sensor readings. See Email and SMS Message Placeholders (on page 224). Send SMS Message You can configure emails to be sent when an event occurs and can customize the message.
  • Page 218 Chapter 6: Using the Web Interface Note: Only the 7-bit ASCII charset is supported for SMS messages. 8. Click OK. Internal Beeper You can have the built-in beeper of the EMX turned on or off when a certain event occurs. To switch the internal beeper: 1.
  • Page 219 Chapter 6: Using the Web Interface  Turn On: Turns on the selected actuator.  Turn Off: Turns off the selected actuator. 6. To select the actuator where this action will be applied, select it from the Available Actuators list and click to add it to the Switched Actuators list box.
  • Page 220 Chapter 6: Using the Web Interface Record Snapshots to Webcam Storage This option allows you to define an action that starts or stops a specific webcam from taking snapshots. To configure a record snapshot to webcam storage action: 1. Choose Device Settings > Event Rules. The Event Rules Settings dialog opens.
  • Page 221 Chapter 6: Using the Web Interface Creating Rules After required actions are available, you can create event rules to determine what actions are taken to respond to specific events. By default, the EMX provides the following built-in event rules:  System Event Log Rule ...
  • Page 222 Chapter 6: Using the Web Interface Event types Radio buttons Numeric sensor Available radio buttons include "Asserted," threshold-crossing "Deasserted" and "Both." events, or the  Asserted: The EMX takes the action only occurrence of the when the event occurs. This means the selected event -- status of the described event transits from true or false...
  • Page 223 Chapter 6: Using the Web Interface Event types Radio buttons Network interface Available radio buttons include "Link state is link state up," "Link state is down" and "Both."  Link state is up: The EMX takes the action only when the network link state changes from down to up.
  • Page 224 Chapter 6: Using the Web Interface Event types Radio buttons Server monitoring Available radio buttons include "Monitoring event started," "Monitoring stopped," and "Both."  Monitoring started: The EMX takes the action only when the monitoring of any specified server starts. ...
  • Page 225 Chapter 6: Using the Web Interface 11. Click Close to quit the dialog. Note: Asset management sensor event rules must be recreated after an EMX firmware upgrade. Scheduling an Action An action can be regularly performed at a preset time interval instead of being triggered by a specific event.
  • Page 226 Chapter 6: Using the Web Interface Time options Frequency settings The frequency in minutes ranges from every minute, every 5 Minutes minutes, every 10 minutes and so on until every 30 minutes. The hourly option sets the timing to either of the following: Hourly ...
  • Page 227 Chapter 6: Using the Web Interface  To remove all actions, click 9. Click OK. Send Sensor Report Example Below is an example of a scheduled action set to send a temperature sensor report via email hourly. In this example, a.
  • Page 228 Chapter 6: Using the Web Interface  You must create the destination action as illustrated below prior to creating the 'Send Hourly Temperature Sensor Readings' action. For details, see (on page 196). Send EMail 2. Create the 'Send sensor report' action -- Send Hourly Temperature Sensor Readings.
  • Page 229 Chapter 6: Using the Web Interface  Type the action's name -- Send Hourly Temperature Sensor Readings.  Select the 'Send sensor report' action.  Select the destination action 'Send Sensor Temp Report Email'.  Add the desired temperature sensor(s) from the Available Sensors list to the Report Sensors box.
  • Page 230 Chapter 6: Using the Web Interface  Type the timer name -- Hourly Sensor Temperature Readings.  Select the Enabled checkbox.  Select Hourly, and set the Minute to 30.  Select the 'Send Hourly Temperature Sensor Readings' action. c. Click OK. For details, see (on page 211).
  • Page 231 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Asset Management > Rack Unit Asset tag with ID '[TAGID]' connected Asset tag with ID '[TAGID]' > * > Tag Connected at rack unit [RACKUNIT], slot disconnected at rack unit [RACKSLOT] of asset strip [STRIPID]...
  • Page 232 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Device > Firmware validation Firmware validation failed by user failed '[USERNAME]' from host '[USERIP]'. Device > Firmware update Firmware upgrade started from version started '[OLDVERSION]' to version...
  • Page 233 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Device > Sending SNMP inform Sending SNMP inform to manager failed or no response [SNMPMANAGER]:[SNMPMANAGER PORT] failed or no response. [ERRORDESC].
  • Page 234 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Peripheral Device Slot > * > Peripheral device Peripheral device Numeric Sensor > Below lower '[EXTSENSORNAME]' in slot '[EXTSENSORNAME]' in slot warning '[EXTSENSORSLOT]' asserted 'below...
  • Page 235 Chapter 6: Using the Web Interface Event/Context Default Assertion Message when Default Assertion Message the Event = TRUE when the Event = FALSE* Power Logic Device > * > Sensor '[PLSENSORNAME]' on Power Sensor '[PLSENSORNAME]' on Sensor > * > Above upper Logic Device at [PORTTYPE] port Power Logic Device at warning...
  • Page 236 Chapter 6: Using the Web Interface User Administration > User User '[TARGETUSER]' modified by modified user '[USERNAME]' from host '[USERIP]'. User Administration > User User '[TARGETUSER]' deleted by user deleted '[USERNAME]' from host '[USERIP]'. User Administration > Password Password of user '[TARGETUSER]' changed changed by user '[USERNAME]' from host '[USERIP]'.
  • Page 237 Chapter 6: Using the Web Interface LHX / SHX > * > Sensor > Sensor '[LHXSENSORID]' on LHX at Sensor '[LHXSENSORID]' on LHX Below lower warning threshold [PORTTYPE] port '[PORTID]' asserted at [PORTTYPE] port '[PORTID]' 'below lower warning'. deasserted 'below lower warning'. LHX / SHX >...
  • Page 238 Chapter 6: Using the Web Interface LHX / SHX > * > Threshold Air The air outlet temperature threshold on The air outlet temperature on LHX Outlet LHX at [PORTTYPE] port '[PORTID]' at [PORTTYPE] port '[PORTID]' is was crossed. within thresholds. LHX / SHX >...
  • Page 239 Chapter 6: Using the Web Interface Placeholder Description [AMSRACKUNITPOSITION] The (vertical) rack unit position, an action applies to [AMSSTATE] The human readable state of an asset strip [AMSTAGID] The asset tag ID [CONFIGPARAM] The name of a configuration parameter [CONFIGVALUE] The new value of a parameter [DATETIME] The human readable timestamp of the event...

  • Page 240: Sample Event Rules

    Chapter 6: Using the Web Interface Placeholder Description [SENSORREADINGUNIT] The unit of a sensor reading [SENSORREADING] The value of a sensor reading [SENSORREPORT] The formatted sensor report contents [SENSORSTATENAME] The human readable state of a sensor [SMTPRECIPIENTS] The list of recipients, an SMTP message was sent to [SMTPSERVER] The name or IP address of an SMTP server [SYSCONTACT]...
  • Page 241 Chapter 6: Using the Web Interface 3. From the Event drop-down, select Device > "Network interface link state is up". These selections indicate we are specifying an event regarding asset sensor management, and we want the EMX to respond to the event related to physical connections and/or disconnections.

  • Page 242: A Note About Infinite Loop

    Chapter 6: Using the Web Interface 3. Select "Numeric Sensor" to indicate the sensor is a numeric sensor. Note: A numeric sensor uses numeric values to indicate the environmental condition while a discrete (on/off) sensor uses alphabetical characters to indicate the sensor state. 4.

  • Page 243: Modifying An Event Rule

    Chapter 6: Using the Web Interface Example 1 This example illustrates an event rule which continuously causes the EMX to send out email messages. Event selected Action included Device > Sending SMTP message Send email failed Example 2 This example illustrates an event rule which continuously causes the EMX to send out SMTP messages when one of the selected events listed on the Device menu occurs.
  • Page 244 Chapter 6: Using the Web Interface For example, in a user activity event rule for the "admin" user, you can click the "admin" tab to display a pull-down submenu showing all user names, and then select a different user name or all users (shown as <Any user>).

  • Page 245: Modifying An Action

    Chapter 6: Using the Web Interface Modifying an Action An existing action can be changed so that all event rules where this action is involved change their behavior accordingly. Exception: The built-in actions "System Event Log Action" and "System Tamper Alarm" are not user-configurable. To modify an action: 1.

  • Page 246: A Note About Untriggered Rules

    Chapter 6: Using the Web Interface c. Click Delete. d. Click Yes on the confirmation message. 4. Click Close to quit the dialog. A Note about Untriggered Rules In some cases, a measurement exceeds a threshold causing the EMX to generate an alert.

  • Page 247: Viewing The Wireless Lan Diagnostic Log

    Chapter 6: Using the Web Interface Note: Sometimes when the dialog is too narrow, the icon takes the place of the Show Details button. In that case, click select Show Details to view details.  Click to view the latest events. ...

  • Page 248: Clearing Event Entries

    Chapter 6: Using the Web Interface 2. Click Yes on the confirmation message. Clearing Event Entries If it is not necessary to keep existing event history, you can remove all of it from the local log. To delete all event entries: 1.

  • Page 249: Monitoring Server Accessibility

    Chapter 6: Using the Web Interface Column Description Idle Time The length of time for which a user remains idle. The unit "min" represents minutes. 2. To disconnect any user, click the corresponding Disconnect button. a. A dialog appears, prompting you to confirm the operation. b.
  • Page 250 Chapter 6: Using the Web Interface 2. Click New. The Add New Server dialog appears. 3. By default, the "Enable ping monitoring for this server" checkbox is selected. If not, select it to enable this feature. 4. Provide the information required. Field Description IP address/hostname IP address or host name of the IT...
  • Page 251 Chapter 6: Using the Web Interface Example: Ping Monitoring and SNMP Notifications In this illustration, it is assumed that a significant PDU (IP address: 192.168.84.95) shall be monitored by your EMX to make sure that PDU is properly operating all the time, and the EMX must send out SNMP notifications (trap or inform) if that PDU is declared unreachable due to power or network failure.

  • Page 252: Editing Ping Monitoring Settings

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

  • Page 253: Checking Server Monitoring States

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

  • Page 254: Identifying Environmental Sensors And Actuators

    Environmental Sensors or Actuators include: a. Name the sensor or actuator. b. If the connected sensor is a Raritan contact closure sensor, specify an appropriate sensor type. c. Mark the sensor or actuator's physical location on the rack or in the room.
  • Page 255 Chapter 6: Using the Web Interface Matching the Serial Number A DPX environmental sensor package includes a serial number tag on the sensor cable. A DPX2, DPX3 or DX sensor has a serial number tag attached to its rear side. The serial number for each sensor or actuator appears listed in the web interface after each sensor or actuator is detected by the EMX.
  • Page 256 Chapter 6: Using the Web Interface Matching the Position DPX2, DPX3 and DX sensor packages can be daisy chained. The EMX can indicate each sensor or actuator's position by showing the sensor port where the environmental sensor package is connected as well as its sequence in a sensor daisy chain.
  • Page 257 Chapter 6: Using the Web Interface For example, if a DPX sensor package is connected to the SENSOR port numbered 1, its Position column only shows "Port 1" no matter a DPX3-ENVHUB4 sensor hub is used or not. Note: For the EMX devices with only one SENSOR port, it always shows "Port 1."...

  • Page 258: Managing Environmental Sensors Or Actuators

    Chapter 6: Using the Web Interface Managing Environmental Sensors or Actuators The EMX starts to retrieve an environmental sensor's reading and/or state and records the state transitions after the environmental sensor is managed. To control an actuator, you also need to have it managed. The EMX device can manage a maximum of 32 environmental sensors or actuators.
  • Page 259 Unmanaging Environmental Sensors or Actuators (on page 256). Special note for a Raritan humidity sensor: As of release 3.1.0, a Raritan humidity sensor is able to provide two measurements in the user interface - relative and absolute humidity values. ...

  • Page 260: Configuring Environmental Sensors Or Actuators

    Chapter 6: Using the Web Interface Configuring Environmental Sensors or Actuators You can change the default name to easily identify the managed sensor or actuator, and describe its location with X, Y and Z coordinates. To configure environmental sensors or actuators: 1.
  • Page 261 Chapter 6: Using the Web Interface 5. If the selected sensor is a numeric sensor, its threshold settings are displayed in the dialog. See (on page Sensor Threshold Settings 529) for detailed information. There are two types of thresholds: sensor-specific thresholds and default thresholds.
  • Page 262 Chapter 6: Using the Web Interface 2. Click Setup on the Settings page. The Setup dialog appears. 3. In the Peripheral Device Z Coordinate Format field, click the drop-down arrow and select an option from the list.  Rack Units: The height of the Z coordinate is measured in standard rack units.
  • Page 263 Chapter 6: Using the Web Interface Changing Default Thresholds The default thresholds are the initial threshold values that automatically apply to numeric environmental sensors. These values are configured on a sensor type basis, which include:  Temperature sensors  Humidity sensors (both relative and absolute humidity) ...
  • Page 264 Chapter 6: Using the Web Interface 6. Click OK. Setting Thresholds for Multiple Sensors You can configure thresholds for multiple environmental sensors of the same type at a time. For example, if you want all temperature sensors to have identical upper and lower thresholds, follow the procedure below to set up all temperature sensors together.

  • Page 265: Viewing Sensor And Actuator Data

    Chapter 6: Using the Web Interface  To select all of those listed on the Peripheral Devices page, simply select the checkbox in the header row. 3. Click Setup. Note that the Setup button is disabled if any of the selected sensors belongs to a different type.
  • Page 266 Chapter 6: Using the Web Interface  Information of each managed sensor and actuator, including: - Name - Position - Reading (for numeric sensors) - State To view both managed and unmanaged ones: Click Peripheral Devices in the left pane. Detailed information for each connected sensor or actuator is displayed, including: ...
  • Page 267 Chapter 6: Using the Web Interface Sensor state Applicable to below lower warning Numeric sensors above upper warning Numeric sensors above upper critical Numeric sensors "unavailable" State The unavailable state means the connectivity or communications with the sensor is lost. The EMX pings all managed sensors at regular intervals in seconds.
  • Page 268 If the normal state is set to Normally Open, the normal state means the contact closure switch is open. For a Raritan's DPX floor water sensor, the normal state must be set to Normally Closed, which means no water is detected.
  • Page 269 Chapter 6: Using the Web Interface "below lower critical" State This state means a numeric sensor's reading is below the lower critical threshold as indicated below: Reading < Lower Critical Threshold "below lower warning" State This state means a numeric sensor's reading is below the lower warning threshold as indicated below: Lower Critical Threshold <= Reading <...

  • Page 270: Unmanaging Environmental Sensors Or Actuators

    Chapter 6: Using the Web Interface Unmanaging Environmental Sensors or Actuators When it is unnecessary to monitor a particular environmental factor, you can unmanage or release the corresponding environmental sensor so that the EMX device stops retrieving the sensor's reading and/or state. This procedure also applies if you want to unmanage an actuator.

  • Page 271: Disabling The Automatic Management Function

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

  • Page 272: Asset Management

    Chapter 6: Using the Web Interface Asset Management Configure the asset management settings only when an asset sensor is physically connected to the EMX device. Note: To set up an asset management system, see Connecting Asset Management Sensors (on page 25). Configuring the Asset Sensor The EMX cannot detect how many rack units (tag ports) a connected asset management sensor supports, so you must provide this...
  • Page 273 Chapter 6: Using the Web Interface  Bottom-Up: The rack units are numbered in the descending order from the highest to the lowest rack unit. 9. In the Numbering Offset field, select the starting number. For example, if you select 3, the first rack unit is numbered 3, the second is numbered 4, the third is numbered 5, and so on until the final number.

  • Page 274: Setting Asset Sensor Led Colors

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

  • Page 275: Configuring A Specific Rack Unit

    Chapter 6: Using the Web Interface Note: You can also access this dialog by double-clicking the asset sensor shown on the Dashboard page. 3. Click Setup on the asset sensor page. The setup dialog for that asset sensor appears. 4. To change the LED color denoting the presence of a tag, either click a color in the color palette or type the hexadecimal RGB value of the color in the "Color with connected Tag"...

  • Page 276: Expanding A Blade Extension Strip

    Chapter 6: Using the Web Interface  LED Mode: Select On to have the LED stay lit, Off to have it stay off, "Slow blinking" to have it blink slowly, or "Fast blinking" to have it blink quickly.  LED Color: If you select On, "Slow blinking" or "Fast blinking" in the LED Mode field, select an LED color by either clicking a color in the color palette or typing the hexadecimal RGB value of a color in the accompanying text box.

  • Page 277: Displaying The Asset Sensor Information

    Chapter 6: Using the Web Interface 3. Double-click that rack unit or click the white arrow prior to the folder icon. The arrow then turns into a black, gradient arrow , and all tag ports of the blade extension strip appear below the folder. To collapse a blade extension strip: ...

  • Page 278: Webcam Management Page Opens

    Chapter 6: Using the Web Interface Webcam Management With a Logitech webcam connected to the EMX device, you can visually ® monitor the environment around the EMX via snapshots or videos captured by the webcam.  To view snapshots and videos, you need the permission of either "Change Webcam Configuration"...

  • Page 279: Configuring Webcam Storage

    Chapter 6: Using the Web Interface a. Video - the webcam is in video mode. Set the Framerate (frames per second) rate. b. Snapshot - the webcam displays images from the webcam. Set the "Time between Snapshots" rate as measured in seconds. 7.

  • Page 280: Adjusting Image Properties

    Chapter 6: Using the Web Interface 3. By default, Local, meaning the EMX, is the designated default storage. 4. Select CIFS/Samba as the storage location. 5. Enter the server where to store the images. 6. If needed, enter the share drive/folder to store the images in. 7.

  • Page 281: Viewing Webcam Snapshots Or Videos

    Chapter 6: Using the Web Interface Viewing Webcam Snapshots or Videos You can switch between snapshots or live videos being captured by a webcam. The snapshot or video is displayed either in the EMX web interface or in a Primary Standalone Live Preview window that you open. You can open a maximum of five Primary Standalone Live Preview windows.

  • Page 282: Saving Snapshots

    Chapter 6: Using the Web Interface  To change any image settings, click Setup . See (on page 264) or Configuring Webcams Adjusting Image (on page 266). Properties  To save the snapshot being displayed, click the "Store Snapshot to Webcam Storage" icon .

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

    Chapter 6: Using the Web Interface 3. Click on the Snapshots icon in the navigation tree to verify that those snapshots are successfully saved and listed on the Snapshots page. Tip: To store snapshots on a remote server rather than the EMX, see Configuring Webcam Storage (on page 265).

  • Page 284: Managing The Snapshots Saved To Emx

    Chapter 6: Using the Web Interface  Neither the Primary Standalone Live Preview window nor any remote session based on the same URL remains open, but the idle timeout period has not expired yet since the last Live Preview window session was closed.
  • Page 285 Chapter 6: Using the Web Interface  Snapshot: displays the image of the snapshot being selected.  Details: shows the information which had been entered when the snapshot was saved, including resolution and location settings. Tip: To save more than 10 snapshots, save snapshots onto a remote server.

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

    Chapter 6: Using the Web Interface Managing the Schroff LHX/SHX Heat Exchanger The EMX supports monitoring and administering the Schroff LHX-20, ® LHX-40 and SHX-30 heat exchanger if this device is connected to the EMX. From the EMX, you can do the following remotely: ...

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

    Chapter 6: Using the Web Interface Enabling and Disabling Schroff LHX/SHX Heat Exchanger Support By default, Schroff LHX/SHX Heat Exchanger support is disabled. As such, support needs to be enabled before the device appears in the navigation tree or on the dashboard. Additionally, Schroff LHX/SHX Heat Exchanger support must be enabled in order for the LHX-MIB to be accessible through SNMP.

  • Page 288: Configuring The Lhx/Shx

    Chapter 6: Using the Web Interface Configuring the LHX/SHX After enabling the LHX/SHX support on the EMX, the EMX should automatically detect the connected LHX/SHX device and display it under the Auxiliary Ports or the Feature Ports folder, depending on the port it is connected to.
  • Page 289 Chapter 6: Using the Web Interface Setting Up an LHX/SHX Once a Schroff LHX/SHX heat exchanger is connected, you can set up the device by giving it a name, and configure its setpoint air outlet and default fan speed. To set up the LHX/SHX: 1.
  • Page 290 Chapter 6: Using the Web Interface 7. Click OK. Configuring Temperature and Fan Thresholds An LHX/SHX heat exchanger is implemented with various sensors for detecting the air temperature, water temperature, and fan speed. You can set thresholds for these sensors so that the EMX alerts you when any sensor readings are getting close to a critical condition.

  • Page 291: Monitoring The Lhx/Shx

    Chapter 6: Using the Web Interface 4. Adjust the threshold and deassertion hysteresis settings. The Upper Critical and Lower Critical values are points at which the EMX considers the operating environment critical and outside the range of the acceptable threshold. ...
  • Page 292 Chapter 6: Using the Web Interface 2. Locate the LHX/SHX Heat Exchanger section where the LHX/SHX summary is shown. LHX/SHX summary on the Ports page:  Click the Auxiliary Ports folder in the EMX Explorer pane. - OR -  Click the Feature Ports folder.
  • Page 293 Chapter 6: Using the Web Interface Viewing Details An LHX/SHX heat exchanger page shows detailed information, including:  Device information and settings, such as the LHX/SHX device name  The air outlet temperature  The default fan speed  Readings and states of all LHX/SHX built-in sensors ...
  • Page 294 Chapter 6: Using the Web Interface 2. Click the desired LHX/SHX device. Its page opens in the right pane. Device States and Icon Variations The EMX web interface changes icons to represent different statuses of the connected LHX/SHX heat exchanger. Icons Device status The heat exchanger is turned ON and operating...
  • Page 295 Chapter 6: Using the Web Interface To identify the cause of a critical state, refer to:  (on page 277) Viewing the Summary  (on page 281) Alert States and LHX Event Log Alert States and LHX Event Log Remote Alert Acknowledgment is supported by the LHX-20 and LHX-40. The SHX-30 does not support Remote Alert Acknowledgment.

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

    Chapter 6: Using the Web Interface Operating Hours Operating hours are the accumulative time since the LHX/SHX heat exchanger is first connected to the EMX device and turned ON. The EMX web interface displays the operating hours both for the heat exchanger and its fans.
  • Page 297 Chapter 6: Using the Web Interface In the Information section, click either Switch Off or Switch On. 3. If you clicked Switch Off, a dialog appears, prompting you to confirm the operation. Click Yes to turn it off or No to abort the operation. The heat exchanger's icon changes after being turned on or off.

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

    Chapter 6: Using the Web Interface Requesting Maximum Cooling for an SHX-30 The EMX allows you to remotely activate the Schroff SHX-30's maximum cooling feature. The LHX-20 and LHX-40 do not support remote activation of maximum cooling. When you click Request Maximum Cooling on the EMX web interface, the SHX-30 enters into emergency cooling mode and runs at its maximum cooling level of 100% in order to cool the device.

  • Page 299: Managing Schneider Electric Powerlogic Pm710

    Note: EMX2-888 does not support the PowerLogic PM710. To configure the PM710: 1. Connect the PM710 sensor to EMX2-111 if it is not already connected.

  • Page 300: Resetting The Pm710 Minimum And Maximum Values

    Chapter 6: Using the Web Interface Resetting the PM710 Minimum and Maximum Values The PM710 saves readings when they reach their highest and lowest value. The highest value and lowest value are the minimum and maximum values, which can be reset as needed. Review your PM710 documentation for additional information.

  • Page 301: Bulk Configuration

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

  • Page 302: Saving The Emx Configuration

    Chapter 6: Using the Web Interface Saving the EMX Configuration A source device is an already configured EMX device that is used to create a configuration file containing the settings that can be shared between EMX devices. These settings include user and role configurations, event rules, security settings, and so on.

  • Page 303: Copying The Emx Configuration

    Chapter 6: Using the Web Interface Copying the EMX Configuration A target device is the EMX device that loads another EMX device's configuration file. Copying a source EMX device's configuration to a target device adjusts the target EMX device's settings to match those of the source EMX device.

  • Page 304: Backup And Restore Of Emx Device Settings

    Chapter 6: Using the Web Interface Backup and Restore of EMX Device Settings Different from the Bulk Configuration file, the backup file contains device-specific data like network settings. To back up or restore EMX device settings, you should perform the Backup/Restore feature. All EMX information is captured in the XML backup file except for the device logs and TLS certificate.

  • Page 305: Firmware Upgrade

    Before starting the upgrade, read the release notes downloaded from the Raritan website's (http://www.raritan.com/support/). If Support page you have any questions or concerns about the upgrade, contact Raritan Technical Support BEFORE upgrading. Warning: Do NOT perform the firmware upgrade over a wireless network connection.

  • Page 306: Viewing Firmware Update History

    Chapter 6: Using the Web Interface 7. When the update is complete, a message appears, indicating the update is successful. 8. The EMX resets, and the Login page re-appears. You can now log in and resume your operation. Note 1: The other logged-in users are also logged out when the firmware update is complete.

  • Page 307: Full Disaster Recovery

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

  • Page 308: Tracing The Network Route

    1. Choose Maintenance > Network Diagnostics > List TCP Connections. The TCP Connections window appears. 2. Click Close to quit the dialog. Downloading Diagnostic Information Important: This function is for use by Raritan Field Engineers or when you are directed by Raritan Technical Support.

  • Page 309: Rebooting The Emx

    1. Choose Maintenance > Download Diagnostic Information. You are then prompted to save or open the file. 2. Click Save to save the file. 3. E-mail this file as instructed by Raritan Technical Support. Rebooting the EMX You can remotely reboot the EMX device via the web interface.

  • Page 310: Accessing The Help

    Chapter 6: Using the Web Interface Accessing the Help The Help menu provides:  Current firmware and software packages information  A link to the EMX help Retrieving Software Packages Information You can check the current firmware version and the information of all open source packages embedded in the EMX device through the web interface.
  • Page 311 "Email this page" icon in the toolbar. 9. To email your comments or suggestions regarding the online help to Raritan, click the "Send feedback" icon 10. To print the currently selected topic, click the "Print this page" icon...

  • Page 312: Chapter 7 Using Snmp

    Using SNMP Chapter 7 This SNMP section helps you set up the EMX for use with an SNMP manager. The EMX 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 313: Configuring Users For Encrypted Snmp V3

    Chapter 7: Using SNMP 2. Select the "enable" checkbox in the "SNMP v1 / v2c" field to enable communication with an SNMP manager using SNMP v1 or v2c protocol.  Type the SNMP read-only community string in the Read Community String field. Usually the string is "public." ...

  • Page 314: Configuring Snmp Notifications

    Chapter 7: Using SNMP 5. Click OK. The user is now set up for encrypted SNMP v3 communication. Configuring SNMP Notifications The EMX automatically keeps an internal log of events that occur. See (on page 187). These events can also be Event Rules and Actions used to send SNMP v2c or v3 notifications to a third-party destination.

  • Page 315: Snmpv2C Notifications

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

  • Page 317: Snmpv3 Notifications

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

  • Page 319: Snmp Gets And Sets

    Chapter 7: Using SNMP Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" Select this if authorization is required but no privacy protocols are required.  Select the authentication protocol - MD5 or  Enter the authentication passphrase and then confirm the authentication passphrase "authPriv"...

  • Page 320: The Emx Mib

    Chapter 7: Using SNMP The EMX MIB The SNMP MIB file is required for using your EMX device with an SNMP manager. An SNMP MIB file describes the SNMP functions. Downloading SNMP MIB The SNMP MIB file for the EMX can be easily downloaded from the web interface.
  • Page 321 Chapter 7: Using SNMP Layout Opening the MIB reveals the custom objects that describe the EMX system. As standard, these objects are first presented at the beginning of the file, listed under their parent group. The objects then appear again individually, defined and described in detail.

  • Page 322: 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 323: Chapter 8 Using The Command Line Interface

    Using the Command Line Interface Chapter 8 This section explains how to use the command line interface (CLI) to administer a EMX device. In This Chapter About the Interface ................309 Logging in to CLI ...................310 Help Command..................314 Querying Available Parameters for a Command........315 Showing Information................315 Clearing Information ................336 Configuring the EMX Device and Network ..........337...

  • Page 324: Logging In To Cli

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

  • Page 325: With Ssh Or Telnet

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

  • Page 326: With An Analog Modem

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

  • Page 327: Different Cli Modes And Prompts

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

  • Page 328: Help Command

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

  • Page 329: Querying Available Parameters For A Command

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

  • Page 330: Network Configuration

    Chapter 8: Using the Command Line Interface Network Configuration This command shows all network configuration, such as the IP address, networking mode, and MAC address. show network IP Configuration This command shows the IP-related configuration only, such as IPv4 and IPv6 configuration, address(es), gateway, and subnet mask.
  • Page 331 Chapter 8: Using the Command Line Interface Networking Mode This command shows whether the current networking mode is wired or wireless. show network mode Note: If the EMX is a slave device connected to the LAN via the master EMX device, the show network mode command displays wired(USB) instead of wired.

  • Page 332: Device Configuration

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

  • Page 333: Default Measurement Units

    Chapter 8: Using the Command Line Interface Default Measurement Units This command shows the default measurement units applied to the EMX web and CLI interfaces across all users, especially those users authenticated through remote authentication servers. show user defaultPreferences 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 EMX.

  • Page 334: Environmental Sensor Information

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

  • Page 336: Environmental Sensor Package Information

    Chapter 8: Using the Command Line Interface Environmental Sensor Package Information Different from the "show externalsensors" commands, which show the reading, status and configuration of an individual environmental sensor, the following command shows the information of all connected environmental sensor packages, each of which may contain more than one sensor or actuator.

  • Page 337: Actuator Information

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

  • Page 338: Environmental Sensor Threshold Information

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

  • Page 339: Environmental Sensor Default Thresholds

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

  • Page 340: Security Settings

    Chapter 8: Using the Command Line Interface Displayed information:  Without the parameter "details," only the default upper and lower thresholds, deassertion hysteresis and assertion timeout settings of the specified sensor type are displayed.  With the parameter "details," the threshold range is displayed in addition to default thresholds settings.

  • Page 341: Existing User Profiles

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

  • Page 342: Existing Roles

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

  • Page 343: Asset Sensor Settings

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

  • Page 344: Blade Extension Strip Settings

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

  • Page 345: Event Log

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

  • Page 346: Wireless Lan Diagnostic Log

    Chapter 8: Using the Command Line Interface Event type Description assetManagement Raritan asset management events, such as asset tag connections or disconnections. Schroff LHX/SHX heat exchanger events. ® modem Modem-related events. timerEvent Scheduled action events. webcam Events for webcam management, if available.
  • Page 347 Chapter 8: Using the Command Line Interface Server Reachability Information for a Specific Server To show the server reachability information for a certain IT device only, use the following command. show serverReachability server <n> To show detailed information, add the parameter "details" to the end of the command.

  • Page 348: Command History

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

  • Page 349: Examples

    Chapter 8: Using the Command Line Interface Option Description A specific Displays the specified number of last entries in the integer number reliability error log. Examples This section provides examples of the show command. Example 1 - Basic Security Information The diagram shows the output of the show security command.

  • Page 350: Clearing Information

    Chapter 8: Using the Command Line Interface Example 2 - In-Depth Security Information More information is displayed when typing the show security details command. Clearing Information You can use the clear commands to remove unnecessary data from the EMX. After typing a "clear" command, press Enter to execute it. Note: Depending on your login name, the # prompt may be replaced by the >...

  • Page 351: Clearing Event Log

    Chapter 8: Using the Command Line Interface Clearing Event Log This command removes all data from the event log. clear eventlog -- OR -- clear eventlog /y If you entered the command without "/y," a message appears, prompting you to confirm the operation. Type y to clear the event log or n to abort the operation.

  • Page 352: Entering Configuration Mode

    Chapter 8: Using the Command Line Interface Entering Configuration Mode Configuration commands function in configuration mode only. To enter configuration mode: 1. Ensure you have entered administrator mode and the # prompt is displayed. Note: If you enter configuration mode from user mode, you may have limited permissions to make configuration changes.

  • Page 353: Device Configuration Commands

    Chapter 8: Using the Command Line Interface Device Configuration Commands A device configuration command begins with emd. You can use the device configuration commands to change the settings that apply to the whole EMX device. Configuration commands are case sensitive so ensure you capitalize them correctly.
  • Page 354 This command specifies your EMX device's altitude above sea level (in meters). You must specify the EMX device's altitude above sea level if a Raritan's DPX differential air pressure sensor is attached. This is because the device's altitude is associated with the altitude correction factor.

  • Page 355: Network Configuration Commands

    Chapter 8: Using the Command Line Interface Option Description freeForm Any alphanumeric string can be used for specifying the Z coordinate. Note: After determining the format for the Z coordinate, you can set a value for it. See Setting the Z Coordinate (on page 410).
  • Page 356 Chapter 8: Using the Command Line Interface Setting the Networking Mode If your EMX device is implemented with both wired and wireless networking mechanisms, you must determine which mechanism is enabled for network connectivity before further configuring networking parameters. This command enables the wired or wireless networking mode. config:# network mode <mode>...
  • Page 357 Chapter 8: Using the Command Line Interface Mode Description v6Only Enables IPv6 only on all interfaces. both Enables both IPv4 and IPv6 on all interfaces. Selecting IPv4 or IPv6 Addresses This command determines which IP address is used when the DNS server returns both of IPv4 and IPv6 addresses.
  • Page 358 Chapter 8: Using the Command Line Interface Setting the SSID This command specifies the SSID string. config:# network wireless SSID <ssid> Variables:  <ssid> is the name of the wireless access point, which consists of: - Up to 32 ASCII characters - No spaces - ASCII codes 0x20 ~ 0x7E Setting the Authentication Method...
  • Page 359 Chapter 8: Using the Command Line Interface Setting EAP Parameters When the wireless authentication method is set to EAP, you must configure EAP authentication parameters, including outer authentication, inner authentication, EAP identity, password, and CA certificate. Determine the outer authentication protocol: config:# network wireless eapOuterAuthentication <outer_auth>...
  • Page 360 Chapter 8: Using the Command Line Interface config:# network wireless allowConnectionWithIncorrectClock <option3> Variables:  The value of <outer_auth> is PEAP because EMX only supports Protected Extensible Authentication Protocol (PEAP) as the outer authentication.  The value of <inner_auth> is MSCHAPv2 because EMX only supports Microsoft's Challenge Authentication Protocol Version 2 (MSCHAPv2) as the inner authentication.
  • Page 361 Chapter 8: Using the Command Line Interface EAP CA Certificate Example This section provides a CA certificate example only. Your CA certificate contents should be different from the contents displayed in this example. To provide a CA certificate: 1. Make sure you have entered the configuration mode. See Entering (on page 338).
  • Page 362 Chapter 8: Using the Command Line Interface MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswgag wZAYDVR0ZAQH/BFowWDBWMFQxCzAJBgNVBAYTAlVTMTYwNAYDVQ QKEy1OYXRpb25hbCBBZXJvbmF1dGljcyBhbmQgU3BhY2UgQWRta W5pc3RyYXRpb24xDTALBgNVBAMTBENSTDEwFwYDVR0BAQH/BA0w C4AJODMyOTcwODEwMBgGA1UdAgQRMA8ECTgzMjk3MDgyM4ACBSA wDQYDVR0KBAYwBAMCBkAwCwYJKoZIhvcNAQEEA4GBAH2y1VCEw/ A4zaXzSYZJTTUi3uawbbFiS2yxHvgf28+8Js0OHXk1H1w2d6qOH H21X82tZXd/0JtG0g1T9usFFBDvYK8O0ebgz/P5ELJnBL2+atOb EuJy1ZZ0pBDWINR3WkDNLCGiTkCKp0F5EWIrVDwh54NNevkCQRZ ita+z4IBO 6. Paste the contents in the terminal. 7. Press Enter. 8. Verify whether the system shows the following command prompt, indicating the provided CA certificate is valid.
  • Page 363 Chapter 8: Using the Command Line Interface Setting the IPv4 Configuration Mode This command determines the IP configuration mode. config:# network ipv4 ipConfigurationMode <mode> Variables:  <mode> is one of the modes: dhcp or static. Mode Description dhcp The IPv4 configuration mode is set to DHCP. static The IPv4 configuration mode is set to static IP address.
  • Page 364 Chapter 8: Using the Command Line Interface Setting the IPv4 Subnet Mask After selecting the static IP configuration mode, you can use this command to define the subnet mask. config:# network ipv4 subnetMask <netmask> Variables:  <netmask> is the subnet mask address. The value ranges from 0.0.0.0 to 255.255.255.255.
  • Page 365 Chapter 8: Using the Command Line Interface Setting the IPv4 Secondary DNS Server After selecting the static IP configuration mode, you can use this command to specify the secondary DNS server. If you have selected the DHCP configuration mode, you still can manually specify DNS servers with this command and then override the DHCP-assigned DNS servers.
  • Page 366 Chapter 8: Using the Command Line Interface Setting IPv4 Static Routes If the IPv4 network mode is set to static IP and your local network contains two subnets, you can configure static routes to enable or disable communications between the EMX and devices in the other subnet.
  • Page 367 Chapter 8: Using the Command Line Interface Setting the IPv6 Configuration Mode This command determines the IP configuration mode. config:# network ipv6 ipConfigurationMode <mode> Variables:  <mode> is one of the modes: automatic or static. Mode Description automatic The IPv6 configuration mode is set to automatic. static The IPv6 configuration mode is set to static IP address.
  • Page 368 Chapter 8: Using the Command Line Interface Setting the IPv6 Gateway After selecting the static IP configuration mode, you can use this command to specify the gateway. config:# network ipv6 gateway <ip address> Variables:  <ip address> is the IP address of the gateway. This value uses the IPv6 address format.
  • Page 369 Chapter 8: Using the Command Line Interface Overriding the IPv6 DHCP-Assigned DNS Server After specifying the primary/secondary DNS server, you can use this command to override the DHCP-assigned DNS server with the one you specified. config:# network ipv6 overrideDNS <option> Variables: ...
  • Page 370 Chapter 8: Using the Command Line Interface config:# network ipv6 staticRoutes modify <route_ID> <dest-2> <hop> Variables:  <dest-1> is the IP address and prefix length of the subnet where the EMX belongs. The format is IP address/prefix length.  <hop> is the IP address of the next hop router. ...
  • Page 371 Chapter 8: Using the Command Line Interface Changing the LAN Duplex Mode This command determines the LAN interface duplex mode. config:# network interface LANInterfaceDuplexMode <mode> Variables:  <mode> is one of the modes: auto, half or full. Option Description auto The EMX selects the optimum transmission mode through auto-negotiation.
  • Page 372 Chapter 8: Using the Command Line Interface Setting the HTTP Port The commands used to configure the HTTP port settings begin with network services http. Change the HTTP port: config:# network services http port <n> Enable or disable the HTTP port: config:# network services http enabled <option>...
  • Page 373 Chapter 8: Using the Command Line Interface Setting the HTTPS Port The commands used to configure the HTTPS port settings begin with network services https. Change the HTTPS port: config:# network services https port <n> Enable or disable the HTTPS access: config:# network services https enabled <option>...
  • Page 374 Chapter 8: Using the Command Line Interface Changing the Telnet Port This command changes the Telnet port. config:# network services telnet port <n> Variables:  <n> is a TCP port number between 1 and 65535. The default Telnet port is 23. Changing the SSH Configuration You can enable or disable the SSH service, or change its TCP port using the CLI commands.
  • Page 375 Chapter 8: Using the Command Line Interface Determining the SSH Authentication Method This command syntax determines the SSH authentication method. config:# network services ssh authentication <auth_method> Variables:  <option> is one of the options: passwordOnly, publicKeyOnly or passwordOrPublicKey. Option Description passwordOnly Enables the password-based login only.
  • Page 376 Chapter 8: Using the Command Line Interface Enabling or Disabling SNMP v3 This command enables or disables the SNMP v3 protocol. config:# network services snmp v3 <option> Variables:  <option> is one of the options: enable or disable. Option Description enable The SNMP v3 protocol is enabled.
  • Page 377 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 378 Chapter 8: Using the Command Line Interface Enabling or Disabling the Read-Only Mode This command enables or disables the read-only mode for the Modbus agent. config:# network services modbus readonly <option> Variables:  <option> is one of the options: true or false. Option Description true...

  • Page 379: 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 380 Chapter 8: Using the Command Line Interface Mode Description The date and time settings synchronize with a specified NTP server. Setting NTP Parameters A time configuration command that is used to set the NTP parameters begins with time ntp. Specifying the Primary NTP Server This command specifies the primary time server if synchronization with the NTP server is enabled.
  • Page 381 Chapter 8: Using the Command Line Interface Overriding DHCP-Assigned NTP Servers This command determines whether the customized NTP server settings override the DHCP-specified NTP servers. config:# time ntp overrideDHCPProvidedServer <option> Variables:  <option> is one of these options: true or false. Mode Description true...
  • Page 382 Chapter 8: Using the Command Line Interface Customizing the Date and Time If intending to manually configure the date and time, use the following CLI commands to specify them. Note: You shall set the time configuration method to "manual" prior to customizing the date and time.

  • Page 383: Checking The Accessibility Of Ntp Servers

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

  • Page 384: Security Configuration Commands

    Chapter 8: Using the Command Line Interface Security Configuration Commands A security configuration command begins with security. Firewall Control You can manage firewall control features through the CLI. The firewall control lets you set up rules that permit or disallow access to the EMX device from a specific or a range of IP addresses.
  • Page 385 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv6 defaultPolicyIn <policy> Determine the default IPv6 firewall control policy for outbound traffic: config:# security ipAccessControl ipv6 defaultPolicyOut <policy> Variables:  <option> is one of the options: true or false. Option Description true...
  • Page 386 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add <direction> <ip_mask> <policy> Add a new IPv4 rule by inserting it above or below a specific rule: config:# security ipAccessControl ipv4 rule add <direction> <ip_mask> <policy> <insert> <rule_number>...
  • Page 387 Chapter 8: Using the Command Line Interface  <ip_mask> is the combination of the IP address and subnet mask values (or prefix length), which are separated with a slash. For example, an IPv4 combination looks like this: 192.168.94.222/24.  <policy> is one of the options: accept, drop or reject. Policy Description accept...
  • Page 388 Chapter 8: Using the Command Line Interface config:# security ipAccessControl ipv4 rule modify <direction> <rule_number> ipMask <ip_mask> policy <policy>  IPv6 commands Modify an IPv6 rule's IP address and/or prefix length: config:# security ipAccessControl ipv6 rule modify <direction> <rule_number> ipMask <ip_mask>...
  • Page 389 Chapter 8: Using the Command Line Interface Option Description reject Discards traffic from/to the specified IP address(es), and an ICMP message is sent to the source or destination host for failure notification. Deleting a Firewall Rule The following commands remove a specific IPv4 or IPv6 rule from the list.
  • Page 390 Chapter 8: Using the Command Line Interface Enabling or Disabling the Restricted Service Agreement This command activates or deactivates the Restricted Service Agreement. config:# security restrictedServiceAgreement enabled <option> Variables:  <option> is one of the options: true or false. Option Description true Enables the Restricted Service Agreement...
  • Page 391 Chapter 8: Using the Command Line Interface If the content is successfully entered, the CLI displays this message "Successfully entered Restricted Service Agreement" followed by the total number of entered characters in parentheses. Note: The new content of Restricted Service Agreement is saved only after typing the apply command.
  • Page 392 Chapter 8: Using the Command Line Interface Password Aging This command enables or disables the password aging feature, which controls whether the password should be changed at a regular interval: config:# security loginLimits passwordAging <option> Variables:  <option> is one of the options: enable or disable. Option Description enable...
  • Page 393 Chapter 8: Using the Command Line Interface User Blocking There are different commands for changing different user blocking parameters. These commands begin with security userBlocking. You can combine multiple commands to modify the user blocking parameters at a time. See (on page 431).
  • Page 394 Chapter 8: Using the Command Line Interface Enabling or Disabling Strong Passwords This command enables or disables the strong password feature. config:# security strongPasswords enabled <option> Variables:  <option> is one of the options: true or false. Option Description true Enables the strong password feature.
  • Page 395 Chapter 8: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneLowerCaseCharacter <option> Variables:  <option> is one of the options: enable or disable. Option Description enable At least one lowercase character is required. disable No lowercase character is required. Uppercase Character Requirement This command determines whether a strong password includes at least a uppercase character.
  • Page 396 Chapter 8: Using the Command Line Interface Special Character Requirement This command determines whether a strong password includes at least a special character. config:# security strongPasswords enforceAtLeastOneSpecialCharacter <option> Variables:  <option> is one of the options: enable or disable. Option Description enable At least one special character is required.
  • Page 397 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 enabled <option> Determine the IPv4 role-based access control policy: config:# security roleBasedAccessControl ipv4 defaultPolicy <policy>  IPv6 commands Enable or disable the IPv6 role-based access control feature: config:# security roleBasedAccessControl ipv6 enabled <option> Determine the IPv6 role-based access control policy: config:# security roleBasedAccessControl ipv6 defaultPolicy <policy>...
  • Page 398 Chapter 8: Using the Command Line Interface Managing Role-Based Access Control Rules You can add, delete or modify role-based access control rules.  An IPv4 role-based access control command for managing rules begins with security roleBasedAccessControl ipv4 rule.  An IPv6 role-based access control command for managing rules begins with security roleBasedAccessControl ipv6 rule.
  • Page 399 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 400 Chapter 8: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify <rule_number> role <role> Modify an IPv4 rule's policy: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> policy <policy> Modify all contents of an existing IPv4 rule: config:# security roleBasedAccessControl ipv4 rule modify <rule_number> startIpAddress <start_ip>...
  • Page 401 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 402 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 403: User Configuration Commands

    Chapter 8: Using the Command Line Interface Example 4 - Adding an IPv4 Role-based Access Control Rule The following command creates a newIPv4 role-based access control rule and specifies its location in the list. config:# security roleBasedAccessControl ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertAbove 3 Results: ...
  • Page 404 Chapter 8: Using the Command Line Interface  <roles> is a role or a list of comma-separated roles assigned to the specified user profile. Modifying a User Profile A user profile contains various parameters that you can modify. Tip: You can combine all commands to modify the parameters of a specific user profile at a time.
  • Page 405 Chapter 8: Using the Command Line Interface Modifying a User's Personal Data You can change a user's personal data, including the user's full name, telephone number, and email address. Various commands can be combined to modify the parameters of a specific user profile at a time.
  • Page 406 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 EMX device only after that user's user profile is enabled. config:# user modify <name> enabled <option> Variables: ...
  • Page 407 Chapter 8: Using the Command Line Interface Modifying SNMPv3 Settings There are different commands to modify the SNMPv3 parameters of a specific user profile. You can combine all of the following commands to modify the SNMPv3 parameters at a time. See Multi-Command Syntax (on page 431).
  • Page 408 Chapter 8: Using the Command Line Interface config:# user modify <name> userPasswordAsAuthenticationPassphrase <option3> Variables:  <name> is the name of the user whose settings you want to change.  <option3> is one of the options: true or false. Option Description true Authentication passphrase is identical to the password.
  • Page 409 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 410 Chapter 8: Using the Command Line Interface Changing the Role(s) This command changes the role(s) of a specific user. config:# user modify <name> roles <roles> Variables:  <name> is the name of the user whose settings you want to change. ...
  • Page 411 Chapter 8: Using the Command Line Interface Set the preferred length unit: config:# user modify <name> preferredLengthUnit <option2> Variables:  <name> is the name of the user whose settings you want to change.  <option2> is one of the options: meter or feet. Option Description meter...
  • Page 412 Chapter 8: Using the Command Line Interface d. Press Enter. To remove an existing SSH public key: 1. Type the same command as shown above. 2. When the system prompts you to input the contents, press Enter without typing or pasting anything. Example The following procedure illustrates how to change the SSH public key for the user "assistant."...
  • Page 413 Chapter 8: Using the Command Line Interface 2. Type the following command and press Enter. config:# password 3. Type the existing password and press Enter when the following prompt appears. Current password: 4. Type the new password and press Enter when the following prompt appears.
  • Page 414 Chapter 8: Using the Command Line Interface config:# user defaultpreferences preferredLengthUnit <option2> Variables:  <option2> is one of the options: meter or feet. Option Description meter This option displays the length or height in meters. feet This option displays the length or height in feet. Set the default pressure unit: config:# user defaultpreferences preferredPressureUnit <option3>...
  • Page 415 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 416: Role Configuration Commands

    Chapter 8: Using the Command Line Interface config:# user defaultpreferences preferredTemperatureUnit F preferredLengthUnit feet preferredPressureUnit psi Results:  The default temperature unit is set to Fahrenheit.  The default length unit is set to feet.  The default pressure unit is set to psi. Role Configuration Commands A role configuration command begins with role.
  • Page 417 Chapter 8: Using the Command Line Interface config:# role create <name> <privilege1>:<argument1>,<argument2>...; <privilege2>:<argument1>,<argument2>...; <privilege3>:<argument1>,<argument2>...; Variables:  <name> is a string comprising up to 32 ASCII printable characters.  <privilege1>, <privilege2>, <privilege3> and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon.
  • Page 418 Chapter 8: Using the Command Line Interface Privilege Description changeUserSettings Change Local User Management changeWebcamSettings Change Webcam Configuration clearLog Clear Local Event Log firmwareUpdate Firmware Update performReset Reset (Warm Start) switchActuator** Switch Actuator viewEventSetup View Event Settings viewEverything Unrestricted View Privileges viewLog View Local Event Log viewSecuritySettings...
  • Page 419 Chapter 8: Using the Command Line Interface Modifying a Role You can modify diverse parameters of an existing role, including its privileges. Modify a role's description: config:# role modify <name> description "<description>" Variables:  <name> is a string comprising up to 32 ASCII printable characters. ...
  • Page 420 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 421: Environmental Sensor Configuration Commands

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

  • Page 426: Configuring Environmental Sensors' Default Thresholds

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

  • Page 428: Environmental 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 429 Chapter 8: Using the Command Line Interface config:# sensor externalsensor <n> <sensor type> lowerWarning <option> Set the deassertion hysteresis for an environmental sensor: config:# sensor externalsensor <n> <sensor type> hysteresis <hy_value> Set the assertion timeout for an environmental sensor: config:# sensor externalsensor <n>...
  • Page 430 Chapter 8: Using the Command Line Interface Example The following command sets the Upper Critical threshold of the environmental "temperature" sensor with the ID number 2 to 40 degrees Celsius. It also enables the upper critical threshold if this threshold has not been enabled yet.

  • Page 431: Actuator Configuration Commands

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

  • Page 432: 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 340).  <description> is a sentence or paragraph comprising up to 64 ASCII printable characters, and it must be enclosed in quotes.
  • Page 433 Chapter 8: Using the Command Line Interface  <succ_ping> is the number of successful pings for declaring the monitored device "Reachable." Valid range is 0 to 200.  <fail_ping> is the number of consecutive unsuccessful pings for declaring the monitored device "Unreachable." Valid range is 1 to 100.
  • Page 434 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 435 Chapter 8: Using the Command Line Interface config:# serverReachability modify <n> numberOfFailuresToDisable <disable_count> Variables:  <n> is a number representing the sequence of the IT device in the server monitoring list.  <IP_host> is the IP address or host name of the IT device whose settings you want to modify.

  • Page 436: Usb-Cascading Configuration Commands

    Chapter 8: Using the Command Line Interface USB-Cascading Configuration Commands A USB-cascading configuration command begins with cascading. You can set the cascading mode on the master device. Note: You CANNOT change the cascading mode on slave devices. Configuring the Cascading Mode This command determines the cascading mode.
  • Page 437 EMX device. config:# assetStrip <n> numberOfRackUnits <number> Note: For the Raritan asset sensor, a rack unit refers to a tag port. Variables:  <n> is the number of the FEATURE port where the selected asset sensor is physically connected.
  • Page 438 Chapter 8: Using the Command Line Interface Specifying the Rack Unit Numbering Mode This command syntax specifies the numbering mode of rack units on the asset sensors connected to the EMX device. The numbering mode changes the rack unit numbers. config:# assetStrip <n>...
  • Page 439 Chapter 8: Using the Command Line Interface Specifying the Asset Sensor Orientation This command syntax specifies the orientation of the asset sensors connected to the EMX device. Usually you do not need to perform this command unless your asset sensors do NOT come with the tilt sensor, causing the EMX unable to detect the asset sensors' orientation.
  • Page 440 <color> is the hexadecimal RGB value of a color in HTML format. The <color> variable ranges from #000000 to #FFFFFF. Rack Unit Configuration For the Raritan asset sensor, a rack unit refers to a tag port. A rack unit configuration command begins with rackUnit. Naming a Rack Unit This command syntax assigns or changes the name of the specified rack unit on the specified asset sensor.
  • Page 441 Chapter 8: Using the Command Line Interface Setting the LED Operation Mode This command syntax determines whether a specific rack unit on the specified asset sensor follows the global LED color settings. config:# rackUnit <n> <rack_unit> LEDOperationMode <mode> Variables:  <n>...
  • Page 442 Chapter 8: Using the Command Line Interface Setting an LED Color for a Rack Unit This command syntax sets the LED color for a specific rack unit on the specified asset sensor. You need to set a rack unit's LED color only when the LED operation mode of this rack unit has been set to "manual."...

  • Page 443: Serial Port Configuration Commands

    Chapter 8: Using the Command Line Interface Mode Description blinkFast This mode has the LED blink quickly. Examples This section illustrates several asset management examples. Example 1 - Asset Sensor LED Colors for Disconnected Tags This command syntax sets the LED color for all rack units on the asset sensor #1 to BLACK (that is, 000000) to indicate the absence of a connected asset tag.
  • Page 444 The following commands set the baud rate (bps) of the serial port labeled CONSOLE / MODEM on the EMX device. Change the baud rate before connecting it to the desired device, such as a computer, a Raritan's P2CIM-SER, or a modem, through the serial port, or there are communications errors.

  • Page 445: Setting The History Buffer Length

    Chapter 8: Using the Command Line Interface Option Description forceGsmModem The port enters the GSM modem state. Example The following command sets the CONSOLE baud rate of the EMX device's serial port to 9600 bps. config:# serial consoleBaudRate 9600 Setting the History Buffer Length This command syntax sets the history buffer length, which determines the amount of history commands that can be retained in the buffer.

  • Page 446: Actuator Control Operations

    Chapter 8: Using the Command Line Interface config:# network ipv4 ipAddress 192.168.84.225 subnetMask 255.255.255.0 gateway 192.168.84.0 Results:  The IP address is set to 192.168.84.225.  The subnet mask is set to 255.255.255.0.  The gateway is set to 192.168.84.0. Example 2 - Combination of SSID and PSK Parameters This multi-command syntax configures both SSID and PSK parameters simultaneously for the wireless feature.

  • Page 447: Switching On An Actuator

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

  • Page 448: Example - Turning On A Specific Actuator

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

  • Page 449: Restarting The Device

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

  • Page 450: Entering Diagnostic Mode

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

  • Page 452: Retrieving Previous Commands

    Chapter 8: Using the Command Line Interface Options Description timeout <number3> Determines the waiting period before timeout. <number3> is an integer number in seconds ranging from 1 to 600. The command looks like the following when it includes all options: diag>...

  • Page 453: Automatically Completing A Command

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

  • Page 454: Appendix A Specifications

    Appendix A Specifications In This Chapter Maximum Ambient Operating Temperature ..........440 EMX2-111 Feature RJ-45 Port Pinouts..........440 EMX2-888 Feature RJ-45 Port Pinouts..........441 Sensor RJ-12 Port Pinouts ..............441 Serial RS-232 Port Pinouts..............441 RS-485 Port Pinouts................442 Maximum Ambient Operating Temperature The maximum ambient operating temperature (TMA) for the EMX is the same for all models regardless of the certification standard (CE or UL).

  • Page 455: Emx2-888 Feature Rj-45 Port Pinouts

    Appendix A: Specifications EMX2-888 Feature RJ-45 Port Pinouts RJ-45 Pin/signal definition Pin No. Signal Direction Description Output Reserved ― Signal Ground ― Fuse protected Warning: Pin 3 is only intended for use with Raritan devices. Output Transmit Data (Data out)

  • Page 456: Rs-485 Port Pinouts

    Appendix A: Specifications RS-232 Pin/signal definition Pin No. Signal Direction Description Input Data Input Receive data (data in) Output Transmit data Output Data terminal ready ― Signal ground Input Data set ready Output Request to send Input Clear to send Input Ring indicator RS-485 Port Pinouts...

  • Page 457: Appendix B Configuration Or Firmware Upgrade With A Usb Drive

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

  • Page 458: System And Usb Requirements

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

  • Page 460: Fwupdate.cfg

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

  • Page 463: Config.txt

    EMX 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 EMX model and firmware version.
  • Page 464 Appendix B: Configuration or Firmware Upgrade with a USB Drive Special configuration keys: There are 3 special configuration keys that are prefixed with magic:.  A special key that sets a user account's password without knowing the firmware's internal encryption/hashing algorithms is implemented as of release 2.2.13.

  • Page 465: Devices.csv

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

  • Page 466: Creating Configuration Files Via Mass Deployment Utility

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

  • Page 467: Firmware Upgrade Via Usb

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

  • Page 468: Appendix C Bulk Configuration Or Firmware Upgrade Via Dhcp/Tftp

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

  • Page 469: Tftp Requirements

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

  • Page 470: Dhcp Ipv4 Configuration In Windows

    Windows Server 2012 system. ® Required Windows IPv4 settings in DHCP: 1. Add a new vendor class for Raritan EMX under IPv4. a. Right-click the IPv4 node in DHCP to select Define Vendor Classes. b. Click Add to add a new vendor class.
  • Page 471 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 472 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 473 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 474 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 475 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 476 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 477 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 478 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 479 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP h. Select "002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. Select "003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly.

  • Page 480: Dhcp Ipv6 Configuration In Windows

    For those EMX devices using IPv6 addresses, follow this procedure to configure your DHCP server. The following illustration is based on Microsoft Windows Server 2012 system. ® Required Windows IPv6 settings in DHCP: 1. Add a new vendor class for Raritan EMX under IPv6.
  • Page 481 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 482 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 483 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 484 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 485 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 486 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP d. Select "00002 pdu-update-control-file" from the Available Options list, and type the filename "fwupdate.cfg" in the "String value" field. e. Select "00003 pdu-update-magic" from the Available Options list, and type any string in the "String value" field. This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly.

  • Page 487: Dhcp Ipv4 Configuration In Linux

    Modify the "dhcpd.conf" file for IPv4 settings when your DHCP server is running Linux. Required Linux IPv4 settings in DHCP: 1. Locate and open the "dhcpd.conf" file of the DHCP server. 2. The EMX will provide the following value of the vendor-class-identifier option (option 60).  vendor-class-identifier = "Raritan PDU 1.0"...
  • Page 488 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP Configure the same option in DHCP accordingly. The EMX accepts the configuration or firmware upgrade only when this value in DHCP matches. 3. Set the following three sub-options in the "vendor-encapsulated-options" (option 43). ...

  • Page 489: Dhcp Ipv6 Configuration In Linux

    13742 (Raritan's IANA number)  Raritan PDU 1.0  15 (the length of the above string "Raritan PDU 1.0") 3. Set the following three sub-options in the "vendor-opts" (option 17).  code 1 (pdu-tftp-server) = the TFTP server's IPv6 address...
  • Page 490 Appendix C: Bulk Configuration or Firmware Upgrade via DHCP/TFTP  code 2 (pdu-update-control-file) = the name of the control file "fwupdate.cfg"  code 3 (pdu-update-magic) = any string This third option/code is the magic cookie to prevent the fwupdate.cfg commands from being executed repeatedly. It does NOT matter whether the IPv6 magic cookie is identical to or different from the IPv4 magic cookie.

  • Page 491: Appendix D Resetting To Factory Defaults

    Using the Reset Button An RS-232 serial connection to a computer is required for using the reset button. The following diagrams show the reset button on EMX2-111 and EMX2-888. EMX2-111: EMX2-888: To reset to factory defaults using the reset button: 1.

  • Page 492: Using The Cli Command

    Appendix D: Resetting to Factory Defaults 3. Press (and release) the Reset button of the EMX device while pressing the Esc key of the keyboard several times in rapid succession. A prompt (=>) should appear after about one second. 4. Type defaults to reset the EMX to its factory defaults. 5.
  • Page 493 Appendix D: Resetting to Factory Defaults To reset to factory defaults without logging in to the CLI: The EMX provides an easier way to reset the product to factory defaults in the CLI prior to login. 1. Connect to the EMX and launch a terminal emulation program as described in the above procedure.

  • Page 494: Appendix E Available Scp Commands

    Appendix E Available SCP Commands You can perform a Secure Copy (SCP) command to update the EMX firmware, do bulk configuration, or back up and restore the configuration. In This Chapter Firmware Update via SCP ..............480 Bulk Configuration via SCP ..............481 Backup and Restore via SCP ..............482 Firmware Update via SCP Same as any EMX firmware update, all user management operations are...

  • Page 495: Bulk Configuration Via Scp

    Appendix E: Available SCP Commands SCP command example: scp emx-ecx-030200-42396.bin admin@192.168.87.50:/fwupdate Tip: The PSCP works in a similar way to the SCP so the PSCP syntax is similar. pscp <firmware file> <user name>@<device ip>:/fwupdate Bulk Configuration via SCP Like performing bulk configuration via the web interface, there are two steps with the bulk configuration using the SCP commands: a.

  • Page 496: Backup And Restore Via Scp

    Appendix E: Available SCP Commands 3. The system copies the configuration included in the file "bulk_config.xml" to another EMX, and displays the following message. Starting restore operation. The connection will be closed now. SCP command examples:  Save operation's example: scp admin@192.168.87.50:/bulk_config.xml ...
  • Page 497 Appendix E: Available SCP Commands scp backup_settings.xml <user name>@<device ip>:/settings_restore  <user name> is the "admin" or any user profile with the administrator privileges. <device ip> is the IP address of the EMX that you want to  update. 2. Type the password when the system prompts you to type it. 3.

  • Page 498: Appendix F Ldap Configuration Illustration

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

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

    Appendix F: LDAP Configuration Illustration Step B. Configure User Groups on the AD Server You must create the groups (roles) for the EMX on the AD server, and then make appropriate users members of these groups. In this illustration, we assume: ...
  • Page 500 Appendix F: LDAP Configuration Illustration 3. Add the emxuser and userb accounts to the EMX_Admin group. 4. Verify whether each group comprises correct users.

  • Page 501: Step C. Configure Ldap Authentication On The Emx Device

    Appendix F: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the EMX Device You must enable and set up LDAP authentication properly on the EMX device to use external authentication. In the illustration, we assume:  The DNS server settings have been configured properly. See (on page 114) and Modifying Network Settings Role of a DNS...
  • Page 502 Appendix F: LDAP Configuration Illustration  Base DN for Search - Type dc=techadssl,dc=com as the starting point where your search begins on the AD server.  Login Name Attribute - Ensure the field is set to sAMAccountName because the LDAP server is Microsoft Active Directory.

  • Page 503: Step D. Configure Roles On The Emx Device

    Appendix F: LDAP Configuration Illustration 5. Click OK. The LDAP server is saved. 6. Click OK. The LDAP authentication is activated. Note: If the EMX 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 EMX and the LDAP server to use the same NTP server(s).
  • Page 504 Appendix F: LDAP Configuration Illustration c. Click Add. 6. Click OK. The EMX_User role is created. 7. Keep the Manage Roles dialog opened to create the EMX_Admin role. To create the EMX_Admin role with full permissions assigned: 1. Click New. The Create New Role dialog appears. 2.
  • Page 505 Appendix F: LDAP Configuration Illustration 3. Type a description for the EMX_Admin role in the Description field. In this example, we type "The role includes all privileges" to describe the role. 4. Click the Privileges tab to select the Administrator permission. The Administrator permission allows users to configure or change all EMX settings.
  • Page 506 Appendix F: LDAP Configuration Illustration 5. Click OK. The EMX_Admin role is created. 6. Click Close to quit the dialog.

  • Page 507: Appendix G Updating The Ldap Schema

    Appendix G Updating the LDAP Schema In This Chapter Returning User Group Information ............493 Setting the Registry to Permit Write Operations to the Schema ...494 Creating a New Attribute ...............494 Adding Attributes to the Class ...............495 Updating the Schema Cache..............497 Editing rciusergroup Attributes for User Members ........497 Returning User Group Information Use the information in this section to return User Group information (and...

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

    Appendix G: 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 509: Adding Attributes To The Class

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

    Appendix G: 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 512 Appendix G: 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.
  • Page 513 Appendix G: Updating the LDAP Schema 5. In the left pane of the window, select the CN=Users folder. 6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties.
  • Page 514 Appendix G: Updating the LDAP Schema 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 EMX) in the Edit Attribute field. Click OK.

  • Page 515: Appendix H Radius Configuration Illustration

    Appendix H RADIUS Configuration Illustration This section provides illustrations for configuring RADIUS authentication. One illustration is based on the Microsoft Network Policy Server (NPS), ® and the other is based on a non-Windows RADIUS server, such as FreeRADIUS. The following steps are required for any RADIUS authentication: 1.

  • Page 516: Step A: Add Your Emx As A Radius Client

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

  • Page 519: Step B: Configure Connection Request Policies

    Appendix H: 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 EMX. 5. Click OK. Step B: Configure Connection Request Policies You need to configure the following for connection request policies: a.
  • Page 520 Appendix H: RADIUS Configuration Illustration b. Connection request forwarding method c. Authentication method(s) d. Standard RADIUS attributes In the following illustration, we assume:  Local NPS server is used  IP address of your EMX: 192.168.56.29  RADIUS protocol selected on your EMX: CHAP ...
  • Page 521 Appendix H: 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 522 Appendix H: RADIUS Configuration Illustration  You can leave the "Type of network access server" field to the default -- Unspecified.
  • Page 523 Appendix H: RADIUS Configuration Illustration 4. Click Next to show the "Specify Conditions" screen. Click Add. 5. The "Select condition" dialog appears. Click Add.
  • Page 524 Appendix H: RADIUS Configuration Illustration 6. The NAS IPv4 Address dialog appears. Type the EMX IP address -- 192.168.56.29, and click OK. 7. Click Next in the New Connection Request Policy dialog. 8. Select "Authenticate requests on this server" because a local NPS server is used in this example.
  • Page 525 Appendix H: RADIUS Configuration Illustration Note: Connection Request Forwarding options must match your environment. 9. When the system prompts you to select the authentication method, select the following two options:  Override network policy authentication settings  CHAP -- the EMX uses "CHAP" in this example...
  • Page 526 Appendix H: RADIUS Configuration Illustration Note: If your EMX uses PAP, then select "PAP."...
  • Page 527 Appendix H: RADIUS Configuration Illustration 10. Select Standard to the left of the dialog and then click Add.
  • Page 528 Appendix H: RADIUS Configuration Illustration 11. Select Filter-Id from the list of attributes and click Add.
  • Page 529 Appendix H: 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 530 Appendix H: RADIUS Configuration Illustration Admin inside the curved brackets {} is the existing role on the EMX. It is recommended to use the Admin role to test this configuration. The role name is case sensitive.
  • Page 531 Appendix H: RADIUS Configuration Illustration 14. The new attribute is added. Click OK.
  • Page 532 Appendix H: RADIUS Configuration Illustration 15. Click Next to continue.
  • Page 533 Appendix H: RADIUS Configuration Illustration 16. A summary showing connection request policy settings is displayed. Click Finish to close the dialog.

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

    Appendix H: RADIUS Configuration Illustration Step C: Configure a Vendor-Specific Attribute You must specify a vendor-specific attribute (VSA) for Raritan on Windows 2008 NPS. Raritan's vendor code is 13742. In the following illustration, we assume:  There are three roles available on your EMX: Admin, User, and SystemTester.
  • Page 535 Type 26 in the "Vendor-assigned attribute number" field. b. Select String in the "Attribute format" field. c. Type Raritan:G{Admin User SystemTester} in the "Attribute value" field. In this example, three roles are specified inside the curved brackets {} -- Admin, User and SystemTester.

  • Page 536: Ad-Related Configuration

    Appendix H: RADIUS Configuration Illustration AD-Related Configuration When RADIUS authentication is intended, make sure you also configure the following settings related to Microsoft Active Directory (AD):  Register the NPS server in AD  Configure remote access permission for users in AD The NPS server is registered in AD only when NPS is configured for the FIRST time and user accounts are created in AD.
  • Page 537 Appendix H: RADIUS Configuration Illustration 3. Click OK, and then OK again. To grant EMX users remote access permission: 1. Open Active Directory Users and Computers. 2. Open the properties dialog of the user whom you want to grant the access permission.
  • Page 538 Appendix H: RADIUS Configuration Illustration 3. Click the Dial-in tab and select the "Allow access" checkbox. To enable reversible encryption for CHAP authentication: 1. Open Active Directory Users and Computers. 2. Open the properties dialog of the user that you want to configure.

  • Page 539: Non-Windows Radius Server

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

  • Page 540: Format Of The "String

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

  • Page 542: Appendix I Additional Emx Information

    Ways to Probe Existing User Profiles............539 Truncated Data in the Web Interface ............540 Raritan Training Website ...............540 Connecting Contact Closure Sensors to OLD EMX2-888.....541 Reserving IP Addresses in Windows DHCP Servers The EMX uses its serial number as the client identifier in the DHCP request.

  • Page 543: Sensor Threshold Settings

    Appendix I: Additional EMX Information Field Description MAC address Enter the ASCII codes of the EMX serial number. Do NOT contain spaces in the ASCII codes.  In this example, enter 50454731413030303033 Other fields Configure them according to your needs. Sensor Threshold Settings This section explains the thresholds settings in a threshold setup dialog for a numeric internal or external sensor.

  • Page 544: Thresholds And Sensor States

    Appendix I: Additional EMX Information Thresholds and Sensor States A numeric sensor has four threshold settings: Lower Critical, Lower Warning, Upper Warning and Upper Critical. The threshold settings determine how many sensor states are available for a certain sensor and the range of each sensor state. The diagram below shows how each threshold relates to each state.
  • Page 545 Appendix I: Additional EMX Information  When a sensor only has the Upper Critical threshold enabled, it has two sensor states: normal and above upper critical.  When a sensor has both the Upper Critical and Upper Warning thresholds enabled, it has three sensor states: normal, above upper warning, and above upper critical.

  • Page 546: To Assert" And Assertion Timeout

    Appendix I: Additional EMX Information "To Assert" and Assertion Timeout If multiple sensor states are available for a specific sensor, the EMX asserts a state for it whenever a bad state change occurs. To assert a state: To assert a state is to announce a "worse" new state. Below are bad state changes that cause the EMX to assert.
  • Page 547 Appendix I: Additional EMX Information Note: For most sensors, the measurement unit in the "Assertion Timeout" field is sample. Because the EMX measures each sensor every second, timing of a sample is equal to a second. How "Assertion Timeout" is helpful: If you have created an event rule that instructs the EMX to send notifications for assertion events, setting the "Assertion Timeout"...

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

    Appendix I: Additional EMX Information "To De-assert" and Deassertion Hysteresis After the EMX asserts a worse state for a sensor, it may de-assert the same state later on. To de-assert a state: To de-assert a state is to announce the end of the previously asserted worse state.
  • Page 549 Appendix I: Additional EMX Information This function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system when the temperature exceeds a pre-determined level. "Deassertion Hysteresis" instructs the EMX to de-assert the worse state for a sensor only when that sensor's reading hits the pre-determined "deassertion"...

  • Page 550: Pdview App For Viewing The Emx

    PDView App for Viewing the EMX Raritan has developed an app that can turn your iOS or Android mobile device into a local display for the EMX. This app is called PDView and it can be downloaded for free.
  • Page 551 Appendix I: Additional EMX Information 2. After installing the PDView, launch it. Below illustrates the PDView for Android devices. 3. Connect your mobile device to the USB port of the EMX. Your mobile device type determines which USB port on the EMX shall be used to connect the mobile device.
  • Page 552 Appendix I: Additional EMX Information The PDView shows a "Connected" message when it detects the physical connection to the EMX. 4. Log in to the PDView app at the login prompt. Now you can view limited EMX information or even change some settings. Tip: To skip the final login step, you can click the upper right icon of PDView to save one or multiple user credentials.

  • Page 553: Altitude Correction Factors

    Appendix I: Additional EMX Information 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 554: Truncated Data In The Web Interface

    Use of other interfaces, such as the CLI or SNMP, to view the data in these fields Raritan Training Website Raritan offers free training materials for various Raritan products on the http://www.raritantraining.com. The Raritan Raritan training website products introduced on this website include the intelligent PDU, dcTrack ®...

  • Page 555: Connecting Contact Closure Sensors To Old Emx2-888

    Follow the steps below to connect Raritan's or third-party contact closure detectors/switches to the termination points labeled CONTACT SENSOR if your EMX is the old EMX2-888 with a built-in spring-loaded terminal module. It is not guaranteed that all third-party detectors/switches are compatible with the EMX.
  • Page 556 Appendix I: Additional EMX Information 4. Release the tiny rectangular buttons after inserting the wires properly. 5. Verify that these wires are firmly fastened. 6. By default, the open status of the detector/switch is considered normal. To set the "normal" setting to "closed" , press down the corresponding button adjacent to the termination points.

  • Page 557: Appendix J Integrating Asset Management Sensors With Other Products

     PX3 PDUs  PX3TS transfer switches For information on setting up asset sensors to work with each product, refer to its User Guide or Online Help on the Raritan website's Support (http://www.raritan.com/support/). page Asset Management Sensors and dcTrack If any asset sensors are connected to the EMX, the EMX can transmit their information to Sunbird's dcTrack.
  • Page 558 Appendix J: Integrating Asset Management Sensors with Other Products  Each IT item connected to the asset sensor via an asset tag must exist in dcTrack. You do not need to manually enter the asset tag IDs for IT items that already exist in dcTrack as long as these items are in the Installed status.

  • Page 559: Index

    Changing the Sensor Description • 410 Asset Management Sensors and dcTrack • Changing the Sensor Name • 408 Changing the SSH Configuration • 360 Asset Management Sensors and Raritan Changing the SSH Port • 360 PDUs • 544 Changing the Telnet Configuration • 359 Asset Sensor Information •...
  • Page 560 Configuration or Firmware Upgrade with a Connecting Contact Closure Sensors to OLD USB Drive • xiv, 21, 287, 443, 453, 454 EMX2-888 • xiv, 3, 76, 77, 542 Configuring a Specific Rack Unit • 261 Connecting Environmental Sensor Packages •...
  • Page 561 Determining How to Display Tree Items • 94, EMX2-888 • 3 EMX2-888 Connection • xii, 31 Determining the SSH Authentication Method • EMX2-888 Contact Closure Sensor LEDs • xiii, xiv, 361 Determining the Time Setup Method • 365, EMX2-888 Contact Closure Sensor Termination •...
  • Page 562 Index Enabling or Disabling SSH • 360 Example 1 - Combination of IP, Subnet Mask Enabling or Disabling Strong Passwords • 380 and Gateway Parameters • 431 Enabling or Disabling Telnet • 359 Example 1 - Creating a User Profile • 401 Enabling or Disabling the Read-Only Mode •...
  • Page 563 Index Logging out of CLI • 439 Login • xiii, 10, 12, 84, 150 Login Limitation • 377 Gathering the External Authentication Logout • 87 Information • 178 Lowercase Character Requirement • 380 Gathering the LDAP Information • 179 Gathering the RADIUS Information • 179 MAC Address •...
  • Page 564 Naming the EMX • 91, 92, 94, 96, 110, 143, RADIUS Configuration Illustration • xiv, 183, 148, 247, 257 Network Configuration • 316 Raritan Training Website • 541 Network Configuration Commands • 341 Rebooting the EMX • 295 Network Diagnostics • 293 Record Snapshots to Webcam Storage •...
  • Page 565 Index Sample Event Rules • 226 Setting the Automatic Daylight Savings Time • Sample Sensor-Level Event Rule • 227 Sample User-Activity-Level Event Rule • 228 Setting the Baud Rates • xiv, 430 Saving Snapshots • 264, 268, 270 Setting the BSSID • 348 Saving the EMX Configuration •...

  • Page 566: Usb-Cascaded Device's Position

    Index Setting Up Your Preferred Measurement Units Supported Maximum DPX Sensor Distances • • 131, 152, 153 41, 45 Setting Wireless Parameters • 343 Supported Web Browsers • xiii, 83 Setup Button • 96 Supported Wireless LAN Configuration • 15 Showing Information •...
  • Page 567 Index Using an Optional DPX-ENVHUB4 Sensor Hub • 42 Using an X Cable • 30, 37 Using Default Thresholds • 411 Using SNMP • 292, 298 Using the CLI Command • 435, 478 Using the Command Line Interface • 120, 248, 309, 478 Using the EMX •...

  • Page 568: United Kingdom

    For CommandCenter Secure Gateway: Press 6, then Press 2 Phone: +31-10-2844040 Fax: 732-764-8887 Email: tech.europe@raritan.com Email for CommandCenter NOC: tech-ccnoc@raritan.com Email for all other products: tech@raritan.com United Kingdom Monday - Friday 8:30 a.m. to 5 p.m. GMT China Phone +44(0)20-7090-1390...

Table of Contents