1. DL manuals
  2. Raritan
  3. Controller
  4. EMX2-111
  5. User Manual

Raritan EMX2-111 User Manual

Manual is about: rack controller

Summary of EMX2-111

  • Page 1

    Raritan emx user guide copyright © 2017 raritan, inc. Emx-1a-v3.3.10-e march 2017 255-80-6107-00 xerus ™ firmware v3.3.10

  • Page 2

    This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated into another language without express prior written consent of raritan, inc. © copyright 2017 raritan, inc. All third-party softw...

  • Page 3

    Iii contents what's new in the emx user guide xi chapter 1 introduction 1 overview............................................................................................................................................ 1 product models................................................................

  • Page 4

    Contents iv connecting composite asset strips (ams-mx-z)................................................................ 35 connecting environmental sensor packages................................................................................ 39 dpx sensor packages....................................

  • Page 5

    Contents v emx ................................................................................................................................................. 98 internal beeper state .......................................................................................................... 99 z co...

  • Page 6

    Contents vi network diagnostics.......................................................................................................... 275 downloading diagnostic information ................................................................................ 276 rebooting the emx device ................

  • Page 7

    Contents vii rack unit settings of an asset strip.................................................................................. 310 blade extension strip settings .......................................................................................... 311 event log................................

  • Page 8

    Contents viii retrieving previous commands................................................................................................... 419 automatically completing a command ....................................................................................... 420 logging out of cli............

  • Page 9

    Contents ix firmware upgrade via usb.......................................................................................................... 440 appendix c bulk configuration or firmware upgrade via dhcp/tftp 442 bulk configuration/upgrade procedure ...................................................

  • Page 10

    Contents x ad-related configuration ............................................................................................................ 515 appendix h additional emx information 519 reserving ip addresses in dhcp servers .........................................................................

  • Page 11

    Xi the following sections have changed or information has been added to the emx user guide based on enhancements and changes to the equipment and/or user documentation. Usb wireless lan adapters (on page 11) initial network configuration via cli (on page 15) cascading multiple emx devices for sharin...

  • Page 12

    Chapter 1: what's new in the emx user guide xii enabling or disabling the lan interface (on page 333) changing the lan interface speed (on page 333) changing the lan duplex mode (on page 334) configuring the cascading mode (on page 339) deleting an ntp server (on page 350) downloading diagnostic dat...

  • Page 13

    1 in this chapter overview ......................................................................................................1 product models ........................................................................................... 2 package contents...............................................

  • Page 14

    Chapter 1: introduction 2 event notifications: event rules and actions that are triggered when an event occurs are supported by the emx. Email messages, log events, syslog messages, webcam snapshots, snmp traps and sms messages can be triggered when the events you define occur. In addition, images c...

  • Page 15

    Chapter 1: introduction 3 emx2-888 emx2-888 has the following ports and components: 8 sensor ports 8 feature ports 8 rs-485 ports 3 usb ports (2 usb-a and 1 usb-b) 1 rs-232 port 1 ethernet port 1 lcd display control buttons contact closure sensor termination for details on each port, see connection ...

  • Page 16

    Chapter 1: introduction 4 apipa and link-local addressing the emx supports automatic private internet protocol addressing (apipa). 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...

  • Page 17

    Chapter 1: introduction 5 retrieval of the link-local ipv4 address: see ipv4 address (on page 75). Before you begin prepare the installation site. Make sure the installation area is clean and not exposed to extreme temperatures or humidity. Allow sufficient space around the emx for cabling and asset...

  • Page 18

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

  • Page 19

    Chapter 2: rack mounting an emx 7 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 moun...

  • Page 20

    Chapter 2: rack mounting an emx 8 3. Secure with the provided end cap screws. 4. Fasten the rackmount brackets' ears to the rack using your own fasteners..

  • Page 21

    9 this chapter explains how to install a emx device and configure it for network connectivity. In this chapter connecting the emx to a power source ..................................................... 9 connecting the emx to your network....................................................... 10 con...

  • Page 22

    Chapter 3: initial installation and configuration 10 3. Connect the other end of the power cord to an appropriate power source. Connecting the emx to your network to remotely administer the emx, you must connect the emx to your local area network (lan). Emx can be connected to a wired or wireless ne...

  • Page 23

    Chapter 3: initial installation and configuration 11 usb wireless lan adapters the emx supports the following usb wi-fi lan adapters. Wi-fi lan adapters supported 802.11 protocols sparklan wubr-508n a/b/g/n proxim orinoco 8494 a/b/g zyxel nwd271n b/g edimax ew-7722und a/b/g/n tp-link tl-wdn3200 v1 a...

  • Page 24

    Chapter 3: initial installation and configuration 12 2. Retrieve the dhcp-assigned ipv4 address. Use the front panel lcd display to retrieve it. See ipv4 address (on page 75). 3. Launch a web browser to configure the emx. See login (on page 87). Configuration using a connected computer: 1. Connect t...

  • Page 25

    Chapter 3: initial installation and configuration 13 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 l...

  • Page 26

    Chapter 3: initial installation and configuration 14 installing the usb-to-serial driver (optional) the emx can emulate a usb-to-serial converter over a usb connection. A usb-to-serial driver named "dominion emx serial console" is required for microsoft ® windows ® operating systems. Download the wi...

  • Page 27

    Chapter 3: initial installation and configuration 15 note: if the emx enters the disaster recovery mode when the usb serial driver is not installed yet, it may be shown as a 'gps camera' in the device manager on the computer connected to it. In linux: no additional drivers are required, but you must...

  • Page 28

    Chapter 3: initial installation and configuration 16 5. If prompted to change the default password, change or ignore it.  to change it, follow onscreen instructions to type your new password.  to ignore it, simply press enter. 6. The # prompt appears. 7. Type config and press enter. 8. To configur...

  • Page 29

    Chapter 3: initial installation and configuration 17 static ip configuration: to set use this command static ipv4 or ipv6 address network interface address = static ip address, with a syntax similar to the example below.  example: 192.168.7.9/24 static ipv4 or ipv6 gateway network gateway address> ...

  • Page 30

    Chapter 3: initial installation and configuration 18 to set or enable use this command 802.11n protocol network wireless enableht = true , or false authentication method network wireless authmethod = psk or eap psk network wireless psk = psk string eap outer authentication network wireless eapoutera...

  • Page 31

    Chapter 3: initial installation and configuration 19 the content to be copied from the ca certificate does not include the first line containing "begin certificate" and the final line containing "end certificate." if a certificate is installed, configure the following: whether to use this command ve...

  • Page 32

    Chapter 3: initial installation and configuration 20 to verify network settings: after exiting the above configuration mode and the # prompt re-appears, type this command to verify all network settings. Show network the ip address configured may take seconds to take effect. Bulk configuration method...

  • Page 33

    Chapter 3: initial installation and configuration 21 cascading multiple emx devices for sharing ethernet connectivity you can have multiple emx devices share one ethernet connection by cascading them via usb. Warning: to upgrade an existing usb-cascading chain from a version older than 3.3.10, you m...

  • Page 34

    Chapter 3: initial installation and configuration 22 do not connect slave devices to the lan via a standard network patch cable or a usb wireless lan adapter. An ethernet-cascaded device must have its ethernet interface enabled for the networking to work properly. By default the ethernet interface i...

  • Page 35

    Chapter 3: initial installation and configuration 23 3. Log in to all devices one by one and select the same cascading mode. See setting the cascading mode (on page 162).  bridging mode: set the cascading mode of all devices to bridging.  port forwarding mode: set the cascading mode of all devices...

  • Page 36

    Chapter 3: initial installation and configuration 24 number device role 1 master device 2 slave 1 3 slave 2 8. Configure or change the network settings of the master and/or slave devices as needed.  bridging: each cascaded device has its own network settings. For example, some devices can have dhcp...

  • Page 37

    25 more features are available if you connect raritan's or third-party external equipment to your emx. In this chapter connecting asset management strips...................................................... 25 connecting environmental sensor packages .......................................... 39 co...

  • Page 38

    Chapter 4: connecting external equipment (optional) 26 combining regular asset strips each tag port on the regular asset strips corresponds to a rack unit and can be used to locate it devices in a specific rack (or cabinet). For each rack, you can attach asset strips up to 64u long, consisting of on...

  • Page 39

    Chapter 4: connecting external equipment (optional) 27  make sure that the u-shaped sheet metal adjacent to the male din connector is inserted into the rear slot of the master strip. Screw up the u-shaped sheet metal to reinforce the connection. 2. Connect another 8u slave strip to the one being at...

  • Page 40

    Chapter 4: connecting external equipment (optional) 28 introduction to asset tags you need both asset strips and asset tags for tracking it devices. Asset tags provide an id number for each it device. The asset tags are adhered to an it device at one end and plugged in to an asset strip at the other...

  • Page 41

    Chapter 4: connecting external equipment (optional) 29 emx2-111 connection the feature port of emx2-111 supports 5 volts of power only, which is insufficient for connecting the latest generation (g3) of asset strips. Therefore, the use of a raritan x cable is required for emx2-111 to connect current...

  • Page 42

    Chapter 4: connecting external equipment (optional) 30 6. Plug the male rj-45 connector at the shorter end of the x cable into the feature port on the emx2-111 device. (a) master asset strip (b) asset tags (c) it devices (d) raritan x cable tip: to connect raritan's environmental sensor packages to ...

  • Page 43

    Chapter 4: connecting external equipment (optional) 31 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 strip assembly to emx2-888: 1. Assemble regular asset strips according to your n...

  • Page 44

    Chapter 4: connecting external equipment (optional) 32 connecting blade extension strips for blade servers, which are contained in a single chassis, you can use a blade extension strip to track individual blade servers. Raritan's blade extension strip functions similar to a raritan asset strip but r...

  • Page 45

    Chapter 4: connecting external equipment (optional) 33 d mylar section with the adhesive tape e tag ports f 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 inter...

  • Page 46

    Chapter 4: connecting external equipment (optional) 34 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. 4. Repeat the above step until all blade servers in the ch...

  • Page 47

    Chapter 4: connecting external equipment (optional) 35 connecting composite asset strips (ams-mx-z) a composite asset strip is named ams-mx-z, where x is a number, such as ams-m2-z or ams-m3-z. It is a type of asset strip that functions the same as regular master asset strips except for the followin...

  • Page 48

    Chapter 4: connecting external equipment (optional) 36 b. Connect one end of the network cable to the rj-45 connector labeled "output" on the previous composite asset strip. C. Connect the other end of the cable to the rj-45 connector labeled "input" on the subsequent composite asset strip. D. Repea...

  • Page 49

    Chapter 4: connecting external equipment (optional) 37 raritan devices maximum strips per chain emx2-888, px3 pdus, px3ts transfer switches pmc (bcm2 series) up to 6 composite asset strips are supported. Tip: to increase the maximum number of composite asset strips attached to a raritan px2 pdu, emx...

  • Page 50

    Chapter 4: connecting external equipment (optional) 38 2. Plug the male rj-12 phone connector at the shorter end of the x cable into the rj-12 sensor port on the emx2-111 device. This step is required for enhancing the power supply to asset strips. 3. Plug the male rj-45 connector at the longer end ...

  • Page 51

    Chapter 4: connecting external equipment (optional) 39 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 52

    Chapter 4: connecting external equipment (optional) 40 model supported maximum number of sensors/actuators 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 t...

  • Page 53

    Chapter 4: connecting external equipment (optional) 41 for the cabling length restrictions, see supported maximum dpx sensor distances (on page 45). Warning: for proper operation, wait for 15-30 seconds between each connection operation or each disconnection operation of environmental sensor package...

  • Page 54

    Chapter 4: connecting external equipment (optional) 42 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. This sensor hub supports dpx sensor packages only...

  • Page 55

    Chapter 4: connecting external equipment (optional) 43 dpx sensor packages 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 packa...

  • Page 56

    Chapter 4: connecting external equipment (optional) 44 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 57

    Chapter 4: connecting external equipment (optional) 45 supported maximum dpx sensor distances when connecting the following dpx sensor packages to the emx, you must follow two restrictions. Dpx-cc2-tr dpx-t1 dpx-t3h1 dpx-af1 dpx-t1dp1 sensor connection restrictions: connect a dpx sensor package to t...

  • Page 58

    Chapter 4: connecting external equipment (optional) 46 emx2-111 33' (10 m) cable up to 1 hub 16' (5 m) cable up to 4 dpx-t3h1 sensor packages dpx2 sensor packages a dpx2 sensor cable is shipped with a dpx2 sensor package. This cable is made up of one rj-12 connector and one to three head connectors....

  • Page 59

    Chapter 4: connecting external equipment (optional) 47 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...

  • Page 60

    Chapter 4: connecting external equipment (optional) 48 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 connecting a dpx2 sensor package t...

  • Page 61

    Chapter 4: connecting external equipment (optional) 49 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. If you want to cascade dpx3 sensor pac...

  • Page 62

    Chapter 4: connecting external equipment (optional) 50 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 ma...

  • Page 63

    Chapter 4: connecting external equipment (optional) 51 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'...

  • Page 64

    Chapter 4: connecting external equipment (optional) 52 a. Plug one end of the cable into the remaining rj-45 port on the prior dx package. B. Plug the other end into either rj-45 port on an additional dx package. Repeat the same steps to cascade more dx packages. 3. Connect the first dx sensor packa...

  • Page 65

    Chapter 4: connecting external equipment (optional) 53 when connecting a dpx2 sensor package containing two dpx2 sensors: a maximum of ten dx sensor packages can be cascaded because 12-2=10. When connecting a dpx2 sensor package containing one dpx2 sensor: a maximum of eleven dx sensor packages can ...

  • Page 66

    Chapter 4: connecting external equipment (optional) 54 2. Connect the raritan sensor packages to any of the four out ports on the hub.  an rj-12 to rj-45 adapter is required for connecting a dpx or dpx2 sensor package to the hub. This diagram illustrates a configuration with a sensor hub connected....

  • Page 67

    Chapter 4: connecting external equipment (optional) 55 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. When mixing...

  • Page 68

    Chapter 4: connecting external equipment (optional) 56 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, dp...

  • Page 69

    Chapter 4: connecting external equipment (optional) 57.

  • Page 70

    Chapter 4: connecting external equipment (optional) 58 mix dpx3 and dx in a sensor chain: any dx sensor package in a chain can be replaced by a dpx3 sensor package, or vice versa. The total number of sensor packages in this chain cannot exceed 12. For example, the following diagram shows a sensor ch...

  • Page 71

    Chapter 4: connecting external equipment (optional) 59 connecting a logitech webcam connect webcams to emx in order to view videos or snapshots of the webcam's surrounding area. The following usb video class (uvc) compliant webcam is supported: logitech ® webcam ® pro 9000, model 960-000048 other uv...

  • Page 72

    Chapter 4: connecting external equipment (optional) 60 connecting a gsm modem the following cinterion ® gsm modems can be connected to the emx in order to send sms messages containing event information. Mc52it mc55it ehs6 see available actions (on page 219) for more information on sms messages. Note...

  • Page 73

    Chapter 4: connecting external equipment (optional) 61 you need to enable the modem dial-in support to take advantage of this feature, see configuring the serial port (on page 253). Connecting an external beeper the emx supports the use of an external beeper for audio alarms. External beepers that a...

  • Page 74

    Chapter 4: connecting external equipment (optional) 62 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. To connect an lh...

  • Page 75

    Chapter 4: connecting external equipment (optional) 63 connecting the schneider electric powerlogic pm710 the schneider electric powerlogic ® pm710 power meter is connected to the emx rs485 port. Once it is connected and the emx detects it, the pm710 is viewed in the emx web interface. This device i...

  • Page 76

    Chapter 4: connecting external equipment (optional) 64 b. Connect an rs232-to-usb adapter (using ftdi's ft232 chip) to the rs485-to-rs232 adapter. 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,...

  • Page 77

    65 in this chapter power switch ............................................................................................. 65 connection ports ....................................................................................... 65 lcd display panel ................................................

  • Page 78

    Chapter 5: using the emx 66 emx2-888.

  • Page 79

    Chapter 5: using the emx 67 no. Port used for... 1 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. 2 rs-485 connection to an electrical device with the rs-485 inte...

  • Page 80

    Chapter 5: using the emx 68 no. Port used for... 6 ethernet connecting the emx to your company's network via a standard network patch cable (cat5e/6). This connection is necessary to administer or access the emx remotely. There are two small leds adjacent to the port:  green indicates a physical li...

  • Page 81

    Chapter 5: using the emx 69 overview of the lcd display different types of information are shown in different sections of the lcd display. The diagram indicates the sections. Section information shown the selected mode and target, such as sensor 8, sensor 36, 1 sensor 28, ca (cascading mode), or the...

  • Page 82

    Chapter 5: using the emx 70 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 ...

  • Page 83

    Chapter 5: using the emx 71 number example information the selected target is the environmental sensor whose id number is 9 (sensor 9). The selected environmental sensor's reading is 22 . The word "master" indicates the emx is the master device in a cascading configuration. For a slave device, it sh...

  • Page 84

    Chapter 5: using the emx 72 states description nor normal state. Ala alarmed state.  this state is accompanied with the word "alarm" below it.  available states for a dry contact signal actuator (dx sensor series): states description on the actuator is turned on. Off the actuator is turned off. No...

  • Page 85

    Chapter 5: using the emx 73 if one or both of the first two digits for a specific coordinate are alphabetical characters, these alphabetical characters are replaced with dashes (-). 6. Press the func button to display the serial number of the sensor, which is shown as "s:xx," where xx are two digits...

  • Page 86

    Chapter 5: using the emx 74 section example information the word "master" indicates the emx is the master device in a cascading configuration. For a slave device, it shows "slave" instead. Note: as of release 3.3.10, the "master/slave" information is no longer available in the bridging mode, but rem...

  • Page 87

    Chapter 5: using the emx 75 ipv4 address the ip address is available in the device mode, which is indicated by the alphabet 'd' shown at the top of the lcd display. Note that the lcd display only shows the ipv4 address (if available). Below illustrates the ip address information. Section example inf...

  • Page 88

    Chapter 5: using the emx 76 to display the ipv4 address: 1. Press the mode button to enter the device mode, indicated by an alphabet "d" at the top left of the display. 2. The lcd display cycles between the four octets of the ipv4 address, indicated by "i4" at the upper right corner of the display. ...

  • Page 89

    Chapter 5: using the emx 77 3. The mac address is displayed as "m:xx", where xx are two digits of the mac address. The lcd will cycle through the mac address from the first two digits to the final two. For example, if the mac address is 00:0d:5d:03:5e:1a, the lcd display shows the following informat...

  • Page 90

    Chapter 5: using the emx 78 2. Press the func button until "ca" is displayed at the top right of the display. 3. The device's position is represented by any number defined below: number device position 0 master device 1 slave 1 2 slave 2 3 slave 3 4 slave 4 5 slave 5 6 slave 6 7 slave 7 as of releas...

  • Page 91

    Chapter 5: using the emx 79 emx2-888 contact closure sensor termination an emx2-888 model contains two built-in contact closure (cc) sensor channels, each of which comprises two termination points. Emx2-888 is designed to use a detachable terminal module for cc sensor termination, which makes instal...

  • Page 92

    Chapter 5: using the emx 80 numbers components 3 two buttons to configure the normal settings of the built-in cc sensor channels.  the upper button is for cc2.  the lower button is for cc1. To adjust the normal settings:  to set to normally closed (n.C), press the button to turn it down.  to set...

  • Page 93

    Chapter 5: using the emx 81 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: connect the discrete detectors/swi...

  • Page 94

    Chapter 5: using the emx 82 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. Loosen the two screws on each side of t...

  • Page 95

    Chapter 5: using the emx 83 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). 5. Plug the t...

  • Page 96

    Chapter 5: using the emx 84 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. The lower led is for cc1....

  • Page 97

    Chapter 5: using the emx 85 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. Led sensor state off no water detected lit water detected reset button the reset button is located inside a...

  • Page 98

    86 this chapter explains how to use the web interface to administer a emx. In this chapter supported web browsers ......................................................................... 86 login, logout and password change ....................................................... 86 web interface ov...

  • Page 99

    Chapter 6: using the web interface 87 login you must enable javascript in the web browser for proper operation. To log in to the web interface: 1. Open a browser and type the ip address of the emx.  if the link-local addressing has been enabled, you can type pdu.Local instead of an ip address. See ...

  • Page 100

    Chapter 6: using the web interface 88 note: the address to access a slave device in the port forwarding mode via non-standard ports is a combination of a protocol (http:// or https://), an ip address and a port number. See port forwarding examples (on page 166). Changing your password you must have ...

  • Page 101

    Chapter 6: using the web interface 89 remembering user names and passwords the emx supports the password manager of common web browsers, including: microsoft internet explorer ® mozilla firefox ® google chrome ® you can save the login name and password when these browsers ask whether to remember the...

  • Page 102

    Chapter 6: using the web interface 90 4. To return to the main menu and the dashboard page, click on the top-left corner. Number web interface element menu (on page 91) data/setup page of the selected menu item  left side: - emx device name note: to customize the device name, see emx (on page 98). ...

  • Page 103

    Chapter 6: using the web interface 91 number web interface element from top to bottom --  your emx model  current firmware version  online documentation: link to the emx online help. - see browsing through the online help (on page 540).  raritan support: link to the raritan technical support web...

  • Page 104

    Chapter 6: using the web interface 92 menu information shown dashboard summary of the emx status, which shows a list of alerted sensors and alarms, if any. See dashboard (on page 94). Emx device data and settings, such as the device name and mac address. See emx (on page 98). Peripherals status and ...

  • Page 105

    Chapter 6: using the web interface 93 menu information shown maintenance device information and maintenance commands, such as firmware upgrade, device backup and reset. See maintenance (on page 260). If a menu item contains the submenu, the submenu is shown after clicking that item. To return to the...

  • Page 106

    Chapter 6: using the web interface 94 sorting a list if any list displays this arrow in one of its column headers, you are allowed to resort the list by clicking any column header. The list will be resorted in the ascending or descending order based on the selected column. Example: 1. By default, th...

  • Page 107

    Chapter 6: using the web interface 95 number section information shown alerted sensors  when no sensors enter the alarmed state, this section shows the message "no alerted sensors."  when any sensor enters the alarmed state, this section lists all of them. See dashboard - alerted sensors (on page ...

  • Page 108

    Chapter 6: using the web interface 96 - state sensors enter the alarmed state. 1 warned: 1 'numeric' sensor enters the warning state. List of alerted sensors: two icons are used to indicate various sensor states. Icons sensor states for numeric sensors:  above upper warning  below lower warning fo...

  • Page 109

    Chapter 6: using the web interface 97 dashboard - alarms if configuring any event rules which require users to take the acknowledgment action, the alarms section will list any event which no one acknowledges yet since event occurrence. Note: for information on event rules, see event rules and action...

  • Page 110

    Chapter 6: using the web interface 98 field description more alerts this field appears only when there are more than one type of events triggering this alert. If there are other types of events (that is, other reasons) triggering the same alert, the total number of additional reasons is displayed. Y...

  • Page 111

    Chapter 6: using the web interface 99 field function note peripheral device z coordinate format determines how to describe the vertical locations (z coordinates) of raritan environmental sensor packages. Options: rack-units and free-form see z coordinate format (on page 100). To specify the location...

  • Page 112

    Chapter 6: using the web interface 100 states description the beeper is turned on. Active "activation reason" is displayed, indicating why the beeper sounds an alarm. For example, if the beeper is turned on because of a specific event rule "xxx," the activation reason looks like: event action trigge...

  • Page 113

    Chapter 6: using the web interface 101 after disabling the automatic management function: the emx no longer automatically manages any newly-added environmental sensors and actuators, and therefore neither id numbers are assigned nor sensor readings or states are available for newly-added ones. You m...

  • Page 114

    Chapter 6: using the web interface 102 note: to disable the automatic management function, go to emx (on page 98). You need to manually manage a sensor/actuator only when it is not under management. When any sensor/actuator is no longer needed, you can unmanage/release it. Open the peripherals page ...

  • Page 115

    Chapter 6: using the web interface 103 if wanted, you can resort the list by clicking the desired column header. See sorting a list (on page 94). Sensor/actuator overview on this page: if any sensor enters the alarmed state, it is highlighted in yellow or red. See yellow- or red-highlighted sensors ...

  • Page 116

    Chapter 6: using the web interface 104 to release or manage sensors/actuators: when the total of managed sensors/actuators reaches the maximum (32), you cannot manage additional ones. The only way to manage any sensor/actuator is to release or replace any managed ones. To replace a managed sensor/ac...

  • Page 117

    Chapter 6: using the web interface 105 managed ones show one of the managed states. To configure default threshold settings: note that any changes made to default threshold settings not only re-determine the initial threshold values applying to newly-added sensors but also the threshold values of th...

  • Page 118

    Chapter 6: using the web interface 106 : turn on. : turn off. 3. Confirm the operation when prompted. Yellow- or red-highlighted sensors the emx highlights those sensors that enter the abnormal state with a yellow or red color. Note that numeric sensors can change colors only after you have enabled ...

  • Page 119

    Chapter 6: using the web interface 107 sensor status color states shown in the interface description above upper critical upper critical threshold critical below lower critical "r" alarmed alarmed state sensors enter the abnormal state. If you have connected a schroff ® lhx/shx heat exchanger, when ...

  • Page 120

    Chapter 6: using the web interface 108 they show one of the managed states. See sensor/actuator states (on page 108). For managed 'numeric' sensors, their readings are retrieved and displayed. If any numeric sensor is disconnected or its reading cannot be retrieved, it shows "unavailable" for its re...

  • Page 121

    Chapter 6: using the web interface 109 state description alarmed the state sensor enters the abnormal state. Unavailable  the communication with the managed sensor is lost. -- or --  dpx2, dpx3 or dx sensor packages are upgrading their sensor firmware. Note that for a contact closure sensor, the n...

  • Page 122

    Chapter 6: using the web interface 110 finding the sensor's serial number a dpx environmental sensor package includes a serial number tag on the sensor cable. A dpx2, dpx3 or dx sensor package has a serial number tag attached to its rear side. The serial number for each sensor or actuator appears li...

  • Page 123

    Chapter 6: using the web interface 111 identifying the sensor position and channel raritan has developed four types of environmental sensor packages - dpx, dpx2, dpx3 and dx series. Only dpx2, dpx3 and dx sensor packages can be daisy chained. The emx can indicate where each sensor or actuator is con...

  • Page 124

    Chapter 6: using the web interface 112 example physical position port 1 connected to the sensor port #1. Port 1, channel 2  connected to the sensor port #1.  the sensor/actuator is the 2nd channel of the sensor package. Port 1, chain position 4  connected to the sensor port #1.  the sensor/actua...

  • Page 125

    Chapter 6: using the web interface 113 2. The "manage peripheral device" dialog appears.  to let the emx randomly assign an id number to it, select "automatically assign a sensor number." this method does not release any managed sensor or actuator.  to assign the desired id number to it, select "m...

  • Page 126

    Chapter 6: using the web interface 114 however, only relative humidity sensors are "automatically" managed if the automatic management function is enabled. You must "manually" manage absolute humidity sensors as needed. Note that relative and absolute values of the same humidity sensor do not share ...

  • Page 127

    Chapter 6: using the web interface 115 2. Select or deselect use default thresholds according to your needs.  to have this sensor follow the default threshold settings configured for its sensor type, select the use default thresholds checkbox. The default threshold settings are configured on the pa...

  • Page 128

    Chapter 6: using the web interface 116 to set up a sensor's or actuator's physical location and additional settings: 1. Click edit settings. 2. Make changes to available fields, and then click save. Fields description binary sensor subtype this field is available for a contact closure sensor only. D...

  • Page 129

    Chapter 6: using the web interface 117 to view a numeric sensor's readings waveform: this sensor's data within the past tens of minutes is shown in the waveform diagram. Note that only a numeric sensor has this diagram. State sensors and actuators do not show such data. To turn on or off an actuator...

  • Page 130

    Chapter 6: using the web interface 118 2. Confirm the operation on the confirmation message. An actuator's state is marked in red when it is turned on. Other operations: you can go to another sensor's or actuators's data/setup page by clicking the selector on the top-left corner. Sensor/actuator loc...

  • Page 131

    Chapter 6: using the web interface 119 feature port(s) one feature port supports connection to the following devices. Device description asset strip raritan asset strips external beeper an external beeper with the rj-45 socket. Lhx 20 schroff ® lhx-20 heat exchanger. Shx 30 schroff ® shx-30 heat exc...

  • Page 132

    Chapter 6: using the web interface 120 2. Click the detection mode field, and select one mode. 3. Mode description auto enable the port to automatically detect the device connection. Disabled disable the port's detection capability. Asset strip, raritan asset strips, lhx 20, shx 30, lhx 40 force the...

  • Page 133

    Chapter 6: using the web interface 121 note: the mode column shows 'pinned' if you select a specific device in the detection mode field. Asset strip after connecting and detecting raritan asset management strips (asset strips), the emx shows the name 'asset strip.'  emx2-888 shows 'asset strip' for...

  • Page 134

    Chapter 6: using the web interface 122 field description number of rack units total of available tag ports on this asset strip assembly, ranging between 8 and 64.  for the current generation of asset strips, which show the suffix "g3" on its hardware label, the emx automatically detects the number ...

  • Page 135

    Chapter 6: using the web interface 123  click a color in the color palette.  type the hexadecimal rgb value of the color, such as #00ff00. 3. Click ok. The rack unit numbering and led color settings are immediately updated on the rack units list illustrated below.  the 'index' number is the physi...

  • Page 136

    Chapter 6: using the web interface 124 to customize a single rack unit's settings: you can make a specific rack unit's led behave differently from the others on the asset strip, including the led light and color. 1. Click the desired rack unit on the rack units list. The setup dialog for the selecte...

  • Page 137

    Chapter 6: using the web interface 125 field description led mode this field is configurable only after the operation mode is set to manual override. Determine how the led light behaves for this particular rack unit. On : the led stays lit. Off : the led stays off. Slow blinking : the led blinks slo...

  • Page 138

    Chapter 6: using the web interface 126 2. All tag ports of the blade extension strip are listed below it. Their port numbers are displayed in the slot column.  to hide the blade extension slots list, click ..

  • Page 139

    Chapter 6: using the web interface 127 to customize asset ids on programmable asset tags: you can customize asset ids only when the asset tags are "programmable" ones. Non-programmable tags do not support this feature. In addition, you can also customize the id of a blade extension strip. If a barco...

  • Page 140

    Chapter 6: using the web interface 128  an asset id contains up to 12 characters that comprise only numbers and/or upper case alphabets. Lower case alphabets are not accepted. 3. Verify the correctness of customized asset ids and modify as needed. 4. Click apply at the bottom of the page or rack un...

  • Page 141

    Chapter 6: using the web interface 129 asset strip automatic firmware upgrade after connecting the asset strip to the emx, it automatically checks its own firmware version against the version of the asset strip firmware stored in the emx firmware. If two versions are different, the asset strip autom...

  • Page 142

    Chapter 6: using the web interface 130 schroff lhx/shx you must enable the lhx/shx support for the emx to detect the presence of a supported schroff ® lhx/shx heat exchanger. See miscellaneous (on page 260). After enabling the lhx/shx support and connecting the supported schroff ® lhx/shx heat excha...

  • Page 143

    Chapter 6: using the web interface 131 for the feature port's mode configuration, see feature port(s) (on page 119). To view the lhx/shx device state: the operation state field indicates whether the device is operating fine, and the switch state field indicates its power status. If the device does n...

  • Page 144

    Chapter 6: using the web interface 132 tip: you can also create event rules to notify you of the warning or critical levels. See event rules and actions (on page 204). To view sensor alerts and lhx event log: remote alert acknowledgment is supported by the lhx-20 and lhx-40. The shx-30 does not supp...

  • Page 145

    Chapter 6: using the web interface 133 auxiliary port(s) one auxiliary port supports connection to the following devices. Device description lhx 20 schroff ® lhx-20 heat exchanger. Shx 30 schroff ® shx-30 heat exchanger. Lhx 40 schroff ® lhx-40 heat exchanger. Powerlogic pm710 schneider electric pow...

  • Page 146

    Chapter 6: using the web interface 134 mode description auto enable the port to automatically detect the device connection. Disabled disable the port's detection capability. Lhx 20, shx 30, lhx 40, powerlogic pm710 force the emx to show the selected device's data/setup page regardless of the physica...

  • Page 147

    Chapter 6: using the web interface 135 schneider electric powerlogic pm710 all settings are configured on a per port basis. If you disconnect a pm710 from one emx port and connect it to another emx port, you must reconfigure the settings. However, if you disconnect a pm710 from an emx port and then ...

  • Page 148

    Chapter 6: using the web interface 136 to configure threshold settings for pm710: 1. Click the thresholds title bar at the bottom of the page to display a list of sensor thresholds. 2. Click the desired sensor (required), and then click edit thresholds. 3. Make changes as needed.  to enable any thr...

  • Page 149

    Chapter 6: using the web interface 137  type a new value in the accompanying text box. For concepts of thresholds, deassertion hysteresis and assertion timeout, see sensor threshold settings (on page 523). 4. Click save. To reset the pm710 minimum and maximum values: 1. At the bottom of the sensors...

  • Page 150

    Chapter 6: using the web interface 138 user management user management menu deals with user accounts, permissions, and preferred measurement units on a per-user basis. The emx is shipped with one built-in administrator account: admin, which is ideal for initial login and system administrator. You ca...

  • Page 151

    Chapter 6: using the web interface 139 user information: field/setting description user name the name the user enters to log in to the emx.  4 to 32 characters  case sensitive  spaces are not permitted. Full name the user's first and last names. Password, confirm password  4 to 64 characters  c...

  • Page 152

    Chapter 6: using the web interface 140 field/setting description (on page 172). Security level click the field to select a preferred security level from the list:  none: no authentication and no privacy. This is the default.  authentication: authentication and no privacy.  authentication & privac...

  • Page 153

    Chapter 6: using the web interface 141 protocol: this section is configurable only when 'authentication' or 'authentication & privacy' is selected. Field/setting description authentication click this field to select the desired authentication protocol. Two protocols are available:  md5  sha-1 (def...

  • Page 154

    Chapter 6: using the web interface 142 note: users can change the measurement units at any time by setting their own preferences. See setting your preferred measurement units (on page 146). Roles: select one or multiple roles to determine the user's permissions. To select all roles, select the top-m...

  • Page 155

    Chapter 6: using the web interface 143  to change the password, type a new password in the password and confirm password fields. If the password field is left blank, the password remains unchanged.  to delete this user, click , and confirm the operation. 3. Click save. To delete multiple user acco...

  • Page 156

    Chapter 6: using the web interface 144 if the two do not satisfy your needs, add new roles. To create a role: 1. Choose user management > roles > . 2. Assign a role name.  1 to 32 characters long  case sensitive  spaces are permitted as of release 3.3.0 3. Type a description for the role in the d...

  • Page 157

    Chapter 6: using the web interface 145 editing or deleting roles choose user management > roles to open the roles page, which lists all roles. If wanted, you can resort the list by clicking the desired column header. See sorting a list (on page 94). The admin role is not user-configurable so the loc...

  • Page 158

    Chapter 6: using the web interface 146 setting your preferred measurement units you can change the measurement units shown in the emx user interface according to your own preferences regardless of the permissions you have. Tip: preferences can also be changed by administrators for specific users on ...

  • Page 159

    Chapter 6: using the web interface 147 setting default measurement units default measurement units are applied to all emx user interfaces across all users, including users accessing the emx via external authentication servers. For a list of affected user interfaces, see user interfaces showing defau...

  • Page 160

    Chapter 6: using the web interface 148 device settings click 'device settings' in the menu (on page 91), and the following submenu displays. Menu command submenu command refer to... Network configuring network settings (on page 149) http changing http(s) settings (on page 171) snmp configuring snmp ...

  • Page 161

    Chapter 6: using the web interface 149 configuring network settings configure wired, wireless, and internet protocol-related settings on the network page after connecting the emx to your network (on page 10). You can enable both the wired and wireless networking on the emx so that it has multiple ip...

  • Page 162

    Chapter 6: using the web interface 150 5. To configure the ethernet interface settings, see ethernet interface settings (on page 152). 6. Click save. After enabling either or both internet protocols: after enabling ipv4 and/or ipv6, all but not limited to the following protocols will be compliant wi...

  • Page 163

    Chapter 6: using the web interface 151 field/setting description  static: manually configure the ipv4 settings. Dhcp settings: optionally specify the preferred hostname, which must meet the following requirements:  consists of alphanumeric characters and/or hyphens  cannot begin or end with a hyp...

  • Page 164

    Chapter 6: using the web interface 152 field description dns resolver reference determine which ip address is used when the dns resolver returns both ipv4 and ipv6 addresses.  ipv4 address: use the ipv4 addresses.  ipv6 address: use the ipv6 addresses. Dns suffixes (optional) specify a dns suffix ...

  • Page 165

    Chapter 6: using the web interface 153 field description auto: system determines the optimum lan speed through auto-negotiation. 10 mbit/s: speed is always 10 mbps. 100 mbit/s: speed is always 100 mbps. Duplex select a duplex mode. Auto: the emx selects the optimum transmission mode through auto-neg...

  • Page 166

    Chapter 6: using the web interface 154 field/setting description bssid type the mac address of an access point enable high throughput (802.11n) enable or disable 802.11n protocol. Authentication select an authentication method.  no authentication: no authentication data is required.  psk: a pre-sh...

  • Page 167

    Chapter 6: using the web interface 155 field/setting description click this button to install a certificate file. Then you can:  click show to view the certificate's content.  click remove to delete the installed certificate if it is inappropriate. Allow expired and not yet valid certificates  se...

  • Page 168

    Chapter 6: using the web interface 156 static settings: assign a static ipv4 address, which follows this syntax "ip address/prefix length". Example: 192.168.84.99/24 ipv6 settings: field/setting description enable ipv6 enable or disable the ipv6 protocol. Ip auto configuration select the method to c...

  • Page 169

    Chapter 6: using the web interface 157  if there are more than 5 pages and the page numbers displayed in the bar does not show the desired one, click to have it show the next or previous five page numbers, if available. 3. To refresh the diagnostic, click on the top-right corner. 4. If wanted, you ...

  • Page 170

    Chapter 6: using the web interface 158 static route examples this section describes two static route examples: ipv4 and ipv6. Both examples assume that two network interface controllers (nic) have been installed in one network server, leading to two available subnets, and ip forwarding has been enab...

  • Page 171

    Chapter 6: using the web interface 159 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 "static routes" section, you should specify:.

  • Page 172

    Chapter 6: using the web interface 160 tip: if you have configured multiple static routes, you can click on any route and then make changes, use or to re-sort the priority, or click to delete it. Ipv6 example: your emx: fd07:2fa:6cff:2405::30 two nics: fd07:2fa:6cff:1111::50 and fd07:2fa:6cff:2405::...

  • Page 173

    Chapter 6: using the web interface 161 in this example, nic-2 (fd07:2fa:6cff:2405::80) is the next hop router for your emx to communicate with any device in the other subnet fd07:2fa:6cff:1111::0. In the ipv6 "static routes" section, you should specify: tip: if you have configured multiple static ro...

  • Page 174

    Chapter 6: using the web interface 162 setting the cascading mode a maximum of 16 emx devices can be cascaded to share one ethernet connection. See cascading multiple emx devices for sharing ethernet connectivity (on page 21). The cascading mode configured on the master device determines the etherne...

  • Page 175

    Chapter 6: using the web interface 163 6. Now you can configure the network settings.  bridging mode: click the bridge section on the same page.  port forwarding mode: click the ethernet or wireless section on the same page, depending on the networking method you prefer. 7. Click save. For informa...

  • Page 176

    Chapter 6: using the web interface 164 "bridging" mode: in this mode, the dhcp server communicates with every cascaded device respectively and assigns four different ip addresses. Each device has its own ip address. The way to remotely access each cascaded device is completely the same as accessing ...

  • Page 177

    Chapter 6: using the web interface 165 port number syntax in the port forwarding mode, all devices in the usb-cascading configuration share the same ip address. To access any cascaded device, you must assign an appropriate port number to it. Master device: the port number is either 5nnxx or the stan...

  • Page 178

    Chapter 6: using the web interface 166 for example, to access the slave 4 device via modbus/tcp, the port number is 50604. See port forwarding examples (on page 166) for further illustrations. Tip: the full list of each cascaded device's port numbers can be retrieved from the web interface. Choose m...

  • Page 179

    Chapter 6: using the web interface 167 protocols port numbers http 50100 ssh 50200 telnet 50300 snmp 50500 modbus 50600 examples using "5nn00" ports: to access the master device via https, the ip address is: https://192.168.84.77:50000/ to access the master device via http, the ip address is: http:/...

  • Page 180

    Chapter 6: using the web interface 168 examples: to access slave 1 via https, the ip address is: https://192.168.84.77:50001/ to access slave 1 via http, the ip address is: http://192.168.84.77:50101/ to access slave 1 via ssh, the command is: ssh -p 50201 192.168.84.77 slave 2 device: position code...

  • Page 181

    Chapter 6: using the web interface 169 adding, removing or swapping cascaded devices change the cascading mode first before adding any device to a cascading chain, or before disconnecting a cascaded device from the chain. If you only want to change the cascading mode of an existing chain, or swap th...

  • Page 182

    Chapter 6: using the web interface 170 to change the cascading mode applied to a chain: 1. Access the last slave device, and change its cascading mode.  if the new cascading mode is 'port forwarding', you must also set its role to 'slave'. 2. Access the second to last, third to last and so on until...

  • Page 183

    Chapter 6: using the web interface 171 changing http(s) settings https uses transport layer security (tls) technology to encrypt all traffic to and from the emx so it is a more secure protocol than http. The emx supports tls 1.0 , 1.1 and 1.2 . By default, any access to the emx via http is automatic...

  • Page 184

    Chapter 6: using the web interface 172 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 and even control the power status of each outlet. Besides, you may need to configure th...

  • Page 185

    Chapter 6: using the web interface 173 a. Click the download mibs title bar to show the download links. B. Click the emd-mib download link. See downloading snmp mib (on page 287). 6. Click save. Configuring smtp settings the emx can be configured to send alerts or event messages to a specific admini...

  • Page 186

    Chapter 6: using the web interface 174 field description user name, password type a user name and password for authentication after selecting the above checkbox.  the length of user name and password ranges between 4 and 64. Case sensitive.  spaces are not allowed for the user name, but allowed fo...

  • Page 187

    Chapter 6: using the web interface 175 special note for aes ciphers: the emx device's ssl/tls-based protocols, including smtp over starttls, support aes 128- and 256-bit ciphers. The exact cipher to use is negotiated between the emx and the client (such as a web browser), which is impacted by the ci...

  • Page 188

    Chapter 6: using the web interface 176 3. To use a different port, type a new port number. 4. Click save. Changing modbus settings the emx supports both the modbus/tcp and modbus gateway features. Enable either or both modbus features according to your needs. Modbus/tcp access: you can enable or dis...

  • Page 189

    Chapter 6: using the web interface 177 field description tcp port use the default port 503, or assign a different port. Valid range is 1 to 65535. Note: port 502 is the default modbus/tcp port for emx, so you cannot use that port for the modbus gateway. Parity, line speed use the default values, or ...

  • Page 190

    Chapter 6: using the web interface 178 enabling service advertising 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 (multicast dns). The advertised services are discovered by clients that have i...

  • Page 191

    Chapter 6: using the web interface 179 configuring security settings the emx provides tools to control access. You can enable the internal firewall, create firewall rules, and set login limitations. In addition, you can create and install the certificate or set up external authentication servers for...

  • Page 192

    Chapter 6: using the web interface 180 note: valid ipv4 addresses range from 0.0.0.0 through 255.255.255.255. To configure ipv4 access control rules: 1. Choose device settings > security > ip access control. 2. Select the enable ipv4 access control checkbox to enable ipv4 access control rules. 3. De...

  • Page 193

    Chapter 6: using the web interface 181  you can select any existing rule and then click or to change its priority. 7. Click save. The rules are applied. To configure ipv6 access control rules: 1. On the same page, select the enable ipv6 access control checkbox to enable ipv6 access control rules. 2...

  • Page 194

    Chapter 6: using the web interface 182 creating role access control rules role-based access control rules are similar to ip access control rules, except they are applied to members of a specific role. This enables you to grant system permissions to a specific role, based on their ip addresses. Same ...

  • Page 195

    Chapter 6: using the web interface 183 insert a rule between two rules  select the rule above which you want to insert a new rule. For example, to insert a rule between rules #3 and #4, select #4.  click insert above.  type a starting ip address in the start ip field.  type an ending ip address ...

  • Page 196

    Chapter 6: using the web interface 184  click to remove it.  to resort its order, click or . 5. Click save.  ipv4 rules: make sure you click the save button in the ipv4 section, or the changes made to ipv4 rules are not saved.  ipv6 rules: make sure you click the save button in the ipv6 section,...

  • Page 197

    Chapter 6: using the web interface 185 creating a csr follow this procedure to create the csr for your emx device. Note that you must enter information in the fields showing the message 'required.' to create a csr: 1. Choose device settings > security > ssl certificate. 2. Provide the information re...

  • Page 198

    Chapter 6: using the web interface 186 field do this challenge, confirm challenge type a password. The password is used to protect the certificate or csr. This information is optional. The value should be 4 to 64 characters long. Case sensitive. 3. Click create new ssl key to create both the csr and...

  • Page 199

    Chapter 6: using the web interface 187 creating a self-signed certificate when appropriate certificate and key files for the emx device are unavailable, the alternative, other than submitting a csr to the ca, is to generate a self-signed certificate. Note that you must enter information in the field...

  • Page 200

    Chapter 6: using the web interface 188 4. Once complete, do the following: a. Double check the data shown in the new ssl certificate section. B. If correct, click "install key and certificate" to install the self-signed certificate and private key. Tip: to verify whether the certificate has been ins...

  • Page 201

    Chapter 6: using the web interface 189 to install available key and certificate files onto the emx: 1. Choose device settings > security > ssl certificate. 2. Select the "upload key and certificate" checkbox at the bottom of the page. 3. The key file and certificate file fields appear. Click to sele...

  • Page 202

    Chapter 6: using the web interface 190 for security purposes, users attempting to log in to the emx must be authenticated. The emx supports the following authentication mechanisms: local user database on the emx lightweight directory access protocol (ldap) remote access dial-in user service (radius)...

  • Page 203

    Chapter 6: using the web interface 191 special note about the aes cipher: the emx device's ssl/tls-based protocols, including ldaps, support aes 128- and 256-bit ciphers. The exact cipher to use is negotiated between the emx and the client (such as a web browser), which is impacted by the cipher pri...

  • Page 204

    Chapter 6: using the web interface 192  if using a microsoft active directory server, consult your ad administrator for the name of the active directory domain. Bind distinguished name (dn) and password (if anonymous bind is not used) the base dn of the server (used for searching for users) the log...

  • Page 205

    Chapter 6: using the web interface 193 field/setting description type of ldap server choose one of the following options:  openldap  microsoft active directory. Active directory is an implementation of ldap/ldaps directory services by microsoft for use in windows environments. Security determine w...

  • Page 206

    Chapter 6: using the web interface 194 field/setting description bind dn required after deselecting the anonymous bind checkbox. Distinguished name (dn) of the user who is permitted to search the ldap directory in the defined search base. Bind password, confirm bind password required after deselecti...

  • Page 207

    Chapter 6: using the web interface 195 to duplicate ldap/ldaps server settings: if you have added any ldap/ldaps server to the emx, and the server you will add shares identical settings with an existing one, the most convenient way is to duplicate that ldap/ldaps server's data and then revise the ip...

  • Page 208

    Chapter 6: using the web interface 196 field/setting description authentication port, accounting port the default are standard ports -- 1812 and 1813. To use non-standard ports, type a new port number. Timeout this sets the maximum amount of time to establish contact with the radius server before ti...

  • Page 209

    Chapter 6: using the web interface 197 managing external authentication settings choose device settings > security > authentication to open the authentication page, where you can: enable both the external and local authentication edit or delete a server resort the access order of servers test the co...

  • Page 210

    Chapter 6: using the web interface 198 2. Select the following checkbox. Then the emx always tries external authentication first. Whenever the external authentication fails, the emx switches to local authentication. 3. Click save. To disable external authentication: 1. In the authentication type, se...

  • Page 211

    Chapter 6: using the web interface 199 tip: if any user blocking event occurs, you can unblock that user manually by using the "unblock" cli command over a local connection. See unblocking a user (on page 415). To set limitations for login timeout and use of identical login names: 1. In the "idle ti...

  • Page 212

    Chapter 6: using the web interface 200 configuring password policy choose device settings > security > password policy to open the password policy page, where you can: force users to use strong passwords. Force users to change passwords at a regular interval -- that is, password aging. Use of strong...

  • Page 213

    Chapter 6: using the web interface 201 enabling the restricted service agreement the restricted service agreement feature, if enabled, forces users to read a security agreement when they log in to the emx. Users must accept the agreement, or they cannot log in. An event notifying you if a user has a...

  • Page 214

    Chapter 6: using the web interface 202  if the daylight saving time rules are not available for the selected time zone, the checkbox is not configurable. 4. Select the method for setting the date and time. Customize the date and time  select user specified time.  type values in the date field usi...

  • Page 215

    Chapter 6: using the web interface 203 calendar the calendar icon in the date field is a convenient tool to select a custom date. Click it and a calendar appears. Button function arrows switch between months. Dates (01-31) click a date. Today select today. Clear clear the entry, if any, in the date ...

  • Page 216

    Chapter 6: using the web interface 204 note: do not use 0x08 (automatic reliable time server) because its dispersion starts at a high value and then gradually decreases to one second or lower. 3. Localclockdispersion must be set to 0. Event rules and actions a benefit of the product's intelligence i...

  • Page 217

    Chapter 6: using the web interface 205 to create a scheduled action: 1. If the needed action is not available yet, create it by clicking . See above. Note: when creating scheduled actions, available actions are less than usual because it is meaningless to schedule certain actions like "alarm," "log ...

  • Page 218

    Chapter 6: using the web interface 206 system tamper detection unavailable: this causes the emx to send alarm notifications if a dx tamper sensor was once connected or remains connected but then the emx does not detect the presence of the tamper sensor. It is enabled by default. Event rule configura...

  • Page 219

    Chapter 6: using the web interface 207 6. In this example, 'above upper critical threshold' is selected because we want the emx to react only when the selected temperature sensor's reading enters the upper critical range. A "trigger condition" field appears, requiring you to define the "exact" condi...

  • Page 220

    Chapter 6: using the web interface 208 radio buttons for different events: according to the event you select, the "trigger condition" field containing three radio buttons may or may not appear. Event types radio buttons numeric sensor threshold-crossing events, or the occurrence of the selected even...

  • Page 221

    Chapter 6: using the web interface 209 event types radio buttons network interface link state  link state is up: the emx takes the action only when the network link state changes from down to up.  link state is down: the emx takes the action only when the network link state changes from up to down...

  • Page 222

    Chapter 6: using the web interface 210 event types radio buttons server reachability  unreachable: the emx takes the action only when any specified server becomes inaccessible.  reachable: the emx takes the action only when any specified server becomes accessible.  both: the emx takes the action ...

  • Page 223

    Chapter 6: using the web interface 211 event/context default message when the event = true default message when the event = false asset management > firmware update firmware update for asset strip [stripid] ('[stripname]'): status changed to '[state]'. Asset management > device config changed config...

  • Page 224

    Chapter 6: using the web interface 212 event/context default message when the event = true default message when the event = false device > firmware update started firmware upgrade started from version '[oldversion]' to version '[version]' by user '[username]' from host '[userip]'. Device > firmware ...

  • Page 225

    Chapter 6: using the web interface 213 event/context default message when the event = true default message when the event = false device > sending snmp inform failed or no response sending snmp inform to manager [snmpmanager]:[snmpmanagerp ort] failed or no response. [errordesc]. Device > sending sy...

  • Page 226

    Chapter 6: using the web interface 214 event/context default message when the event = true default message when the event = false peripheral device slot > * > numeric sensor > below lower warning threshold peripheral device '[extsensorname]' in slot '[extsensorslot]' asserted 'below lower warning' a...

  • Page 227

    Chapter 6: using the web interface 215 event/context default message when the event = true default message when the event = false [sensorreadingunit]. [sensorreading] [sensorreadingunit]. Power logic device > * > sensor > * > above upper warning sensor '[plsensorname]' on power logic device at [port...

  • Page 228

    Chapter 6: using the web interface 216 event/context default message when the event = true default message when the event = false '[userip]' was blocked. User activity > * > session timeout session of user '[username]' from host '[userip]' timed out. User administration > user added user '[targetuse...

  • Page 229

    Chapter 6: using the web interface 217 event/context default message when the event = true default message when the event = false lhx/shx > * > sensor > unavailable sensor '[lhxsensorid]' on lhx at [porttype] port '[portid]' unavailable. Sensor '[lhxsensorid]' on lhx at [porttype] port '[portid]' av...

  • Page 230

    Chapter 6: using the web interface 218 event/context default message when the event = true default message when the event = false lhx/shx > * > sensor failure a sensor failure (broken or short circuit) occurred on lhx at [porttype] port '[portid]' at sensor '[lhxsensorid]'. Lhx/shx > * > fan failure...

  • Page 231

    Chapter 6: using the web interface 219 available actions the emx comes with three built-in actions, which cannot be deleted. You can create additional actions for responding to different events. Built-in actions: system event log action: this action records the selected event in the internal log whe...

  • Page 232

    Chapter 6: using the web interface 220 action function external beeper enables or disables the connected external beeper, or causes it to enter an alarm cycle. See external beeper (on page 223). Internal beeper turns on or off the internal beeper. See internal beeper (on page 223). Log event message...

  • Page 233

    Chapter 6: using the web interface 221 action function start/stop lua script if you are a developer who can create a lua script, you can upload it to the emx, and have the emx automatically perform or stop the script in response to an event. See start or stop a lua script (on page 232). Switch lhx/s...

  • Page 234

    Chapter 6: using the web interface 222  external beeper  syslog message  send email  send sms message  internal beeper if no appropriate actions are available, create them first. A. To select any methods, select them one by one in the available field. To add all available methods, simply click ...

  • Page 235

    Chapter 6: using the web interface 223 3. To select any action(s), select them one by one from the available actions list.  to select all available actions, click select all. 4. To remove any action(s) from the selected actions field, click that action's .  to remove all actions, click deselect al...

  • Page 236

    Chapter 6: using the web interface 224 log an event message the option "log event message" records the selected events in the internal log. The default log message generated for each type of event is available in the section titled default log messages (on page 210). Push out sensor readings you can...

  • Page 237

    Chapter 6: using the web interface 225 if "start recording" is selected, adjust the values of the following:  number of snapshots - the number of snapshots to be taken when the event occurs. The maximum amount of snapshots that can be stored on the emx is 10. If you set it for a number greater than...

  • Page 238

    Chapter 6: using the web interface 226 send email you can configure emails to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and emx placeholders. The placeholders represent information is pulled from the emx and inserted into the message. ...

  • Page 239

    Chapter 6: using the web interface 227 send sensor report you may set the emx so that it automatically reports the latest readings or states of one or multiple sensors by sending a message or email or simply recording the report in a log. These sensors can be either internal or environmental sensors...

  • Page 240

    Chapter 6: using the web interface 228 b. Click the second to select the specific sensor for the target from the list. C. Click to add the selected sensor to the report sensors list box. For example, to monitor the current reading of the inlet 1, select inlet 1 from the left field, and then select r...

  • Page 241

    Chapter 6: using the web interface 229 send sms message you can configure sms messages to be sent when an event occurs and can customize the message. Messages consist of a combination of free text and emx placeholders. The placeholders represent information which is pulled from the emx and inserted ...

  • Page 242

    Chapter 6: using the web interface 230 send snapshots via email this option notifies one or multiple persons for the selected events by emailing snapshots or videos captured by a connected logitech ® webcam. Operation: 1. Choose device settings > event rules > . 2. Select "send snapshots via email" ...

  • Page 243

    Chapter 6: using the web interface 231 to send snmp v2c notifications: 1. In the notification type field, select snmpv2c trap or snmpv2c inform. 2. For snmp inform communications, leave the resend settings at their default or do the following: a. In the timeout field, specify the interval of time, i...

  • Page 244

    Chapter 6: using the web interface 232 4. For both snmp traps and informs, enter the following as needed and then click ok to apply the settings: a. Host name b. Port number c. User id for accessing the host -- make sure the user id has the snmpv3 permission. D. Select the host security level securi...

  • Page 245

    Chapter 6: using the web interface 233  no script is available if you have not created or loaded it into the emx. 5. To apply different arguments than the default, do the following. Note that the newly-added arguments will override this script's default arguments. A. Click . B. Type the key and val...

  • Page 246

    Chapter 6: using the web interface 234 3. In the operation field, select an operation for the selected actuator(s).  turn on: turns on the selected actuator(s).  turn off: turns off the selected actuator(s). 4. To select the actuator(s) where this action will be applied, select them one by one fro...

  • Page 247

    Chapter 6: using the web interface 235 transport protocols next steps tcp+tls a tls certificate is required. Do the following: a. Type an appropriate port number in the "tcp port" field. Default is 6514. B. In the ca certificate field, click to select a tls certificate. After installing the certific...

  • Page 248

    Chapter 6: using the web interface 236  to remove all actions, click deselect all. 4. Select the desired frequency in the execution time field, and then specify the time interval or a specific date and time in the field(s) that appear..

  • Page 249

    Chapter 6: using the web interface 237 execution time frequency settings minutes click the frequency field to select an option. The frequency ranges from every minute, every 5 minutes, every 10 minutes and so on until every 30 minutes. Hourly type a value in the minute field, which is set to either ...

  • Page 250

    Chapter 6: using the web interface 238 execution time frequency settings yearly this option requires three settings:  month - january through december.  day of month - 1 to 31.  time - the value is measured in 12-hour format so you must correctly specify am or pm by clicking the am/pm button. An ...

  • Page 251

    Chapter 6: using the web interface 239 then the emx will send out an email containing the specified temperature sensor readings hourly every day. Whenever you want the emx to stop sending the temperature report, simply deselect the enabled checkbox in the timer. Email and sms message placeholders ac...

  • Page 252

    Chapter 6: using the web interface 240 placeholder definition [devicename] the name of the device, the event occurred on [errordesc] the error message [eventrulename] the name of the matching event rule [extsensorname] the name of a peripheral device [extsensorslot] the id of a peripheral device slo...

  • Page 253

    Chapter 6: using the web interface 241 placeholder definition [smtpserver] the name or ip address of an smtp server [syscontact] syscontact as configured for snmp [syslocation] syslocation as configured for snmp [sysname] sysname as configured for snmp [timereventid] the id of a timer event [timesta...

  • Page 254

    Chapter 6: using the web interface 242 sample event rules sample asset-management-level event rule in this example, we want the emx to record in the internal log when the network link is up to down. The sample event rule looks like this: event: device > network interface link state is up trigger con...

  • Page 255

    Chapter 6: using the web interface 243 5. Select "tag connected" as the events we want to record are related to physical tag connections or disconnections. 6. Select the both radio button since we want both connection and disconnection actions to be recorded when either event occurs. 7. Select "syst...

  • Page 256

    Chapter 6: using the web interface 244 5. Select "state sensor/actuator" because the contact closure sensor is a state sensor. 6. Select "alarmed" since we want the emx to respond when the selected contact closure sensor changes its state related to the "alarmed" state. 7. In the "trigger condition"...

  • Page 257

    Chapter 6: using the web interface 245 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 d...

  • Page 258

    Chapter 6: using the web interface 246  if any section's number of sensors exceeds 35, the remaining sensors are listed on next page(s). If so, a pagination bar similar to the following diagram displays in this section, which you can click any button to switch between pages. 5. Click save. This but...

  • Page 259

    Chapter 6: using the web interface 247 configuring data push settings you can push the sensor or asset strip 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 260

    Chapter 6: using the web interface 248  asset management log: transmit the log of all asset strips, which is generated when there are changes made to asset tags and asset strips, including asset tag connection or disconnection events.  sensor log: transmit the record of all logged sensors, includi...

  • Page 261

    Chapter 6: using the web interface 249 monitoring server accessibility you can monitor whether specific it devices are alive by having the emx device continuously ping them. An it device's successful response to the ping commands indicates that the it device is still alive and can be remotely access...

  • Page 262

    Chapter 6: using the web interface 250 field description number of consecutive unsuccessful pings for failure the number of consecutive pings without any response before the monitored equipment is declared "unreachable." valid range is 1 to 100. Wait time before resuming pinging after failure the wa...

  • Page 263

    Chapter 6: using the web interface 251 editing or deleting ping monitoring settings you can edit the ping monitoring settings of any it device or simply delete it if no longer needed. To modify or delete any monitored it device: 1. Choose device settings > server reachability. 2. Click the desired o...

  • Page 264

    Chapter 6: using the web interface 252 field data entered wait time after successful ping 5  to make the emx declare the inaccessibility of the monitored pdu when that pdu becomes inaccessible for around 12 seconds (4 seconds * 3 pings), enter the following data. Field data entered wait time after ...

  • Page 265

    Chapter 6: using the web interface 253 5. Select the system snmp notification action. Note: if you have not configured the system snmp notification action to specify the snmp destination(s), see editing or deleting a rule/action (on page 241). Configuring the serial port you can change the bit rate ...

  • Page 266

    Chapter 6: using the web interface 254 options description force console the emx attempts to recognize that the connected device is set for the console mode. Force analog modem the emx attempts to recognize that the connected device is an analog modem. Force gsm modem the emx attempts to recognize t...

  • Page 267

    Chapter 6: using the web interface 255 lua scripts if you can write or obtain any lua scripts, you can create or load them into the emx to control its behaviors. Raritan also provides some lua scripts examples, which you can load as needed. Note: not all raritan lua script examples can apply to your...

  • Page 268

    Chapter 6: using the web interface 256 b. Type the key and value. C. Repeat the same steps to enter more arguments as needed.  to remove any existing argument, click adjacent to it. Note: default arguments are overridden by the new arguments specified with the "start with arguments" command or with...

  • Page 269

    Chapter 6: using the web interface 257 next steps: to execute the newly-added script now, click , or click > start with arguments. See manually starting or stopping a script (on page 257). To add more scripts, return to the scripts list by clicking "lua scripts" again in the menu (on page 91), and t...

  • Page 270

    Chapter 6: using the web interface 258  click if needing additional arguments. 5. Click start. 6. The script output will be shown in the script output section.  if needed, click to delete the existing output data. To manually stop a script: 1. Choose device settings > lua scripts. 2. Click the des...

  • Page 271

    Chapter 6: using the web interface 259 checking lua scripts states choose device settings > lua scripts to show the scripts list, which indicates the current state and settings of each script. State: four script states are available. New : the script is never executed since the device boot. Running ...

  • Page 272

    Chapter 6: using the web interface 260 3. Click > edit script. 4. Make changes to the information shown, except for the script's name, which cannot be revised.  to replace the current script, click load local file or load example to select a new script. To delete a script: 1. Choose device settings...

  • Page 273

    Chapter 6: using the web interface 261 submenu command refer to... Backup/restore backup and restore of device settings (on page 274) network diagnostic network diagnostics (on page 275) download diagnostic downloading diagnostic information (on page 276) unit reset rebooting the emx device (on page...

  • Page 274

    Chapter 6: using the web interface 262 device information using the web interface, you can retrieve hardware and software information of components or peripheral devices connected to your emx. Tip: if the information shown on this page does not match the latest status, press f5 to reload it. To disp...

  • Page 275

    Chapter 6: using the web interface 263 the number of available sections is model dependent. Section title information shown information general device information, such as model name, serial number, firmware version, hardware revision, mib download link(s) and so on. Note that the download link of l...

  • Page 276

    Chapter 6: using the web interface 264  if the information shown on this page does not match the latest status, press f5 to reload it. Cascading information in the bridging mode: the common section contains two read-only fields for indicating the cascading status. Note that the cascading position i...

  • Page 277

    Chapter 6: using the web interface 265 fields description cascade position indicates the position of the emx in the 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. Cascaded device con...

  • Page 278

    Chapter 6: using the web interface 266 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. The following diagram shows 2, ...

  • Page 279

    Chapter 6: using the web interface 267 viewing connected users you can check which users have logged in to the emx device and their status. If you have administrator privileges, you can terminate any user's connection to the emx. To view and manage connected users: 1. Choose maintenance > connected ...

  • Page 280

    Chapter 6: using the web interface 268 if there are live webcam sessions: all live preview sessions sharing the same url, including one primary standalone live preview window of the sender and two sessions of the remote recipients, are identified as one single "" user in the connected users list. Yo...

  • Page 281

    Chapter 6: using the web interface 269 to clear the local log: 1. Click on the top-right corner. 2. Click clear log on the confirmation message. Updating the emx firmware firmware files are available on raritan website's support page ( http://www.Raritan.Com/support/ ). You must be the administrator...

  • Page 282

    Chapter 6: using the web interface 270  the front panel display shows the firmware upgrade message. Three digits are displayed: fup. See overview of the lcd display (on page 69).  no users can successfully log in to the emx.  other users' operation, if any, is forced to suspend. 7. When the updat...

  • Page 283

    Chapter 6: using the web interface 271 full disaster recovery if the firmware upgrade fails, causing the emx device to stop working, you can recover it by using a special utility rather than returning the device to raritan. Contact raritan technical support for the recovery utility, which works in w...

  • Page 284

    Chapter 6: using the web interface 272 bulk configuration the bulk configuration feature lets you save generic settings of a configured emx device to your computer. You can use this configuration file to copy common settings to other emx devices of the same model and firmware version. Note that no d...

  • Page 285

    Chapter 6: using the web interface 273 enter the admin password, and click restore. 6. Wait until the emx device resets and the login page re-appears. Note: on startup, the emx performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of th...

  • Page 286

    Chapter 6: using the web interface 274 backup and restore of device settings unlike the bulk configuration file, the backup file contains all device settings, including device-specific data like device names and network settings. To back up or restore a emx device's settings, you should perform the ...

  • Page 287

    Chapter 6: using the web interface 275 note: on startup, the emx performs all of its functions, including event rules and logs, based on the new configuration you have copied instead of the previous configuration prior to the device reset. For example, the "bulk configuration copied" event is logged...

  • Page 288

    Chapter 6: using the web interface 276 2. Click run ping to ping the host. The ping results are then displayed. Trace route: 1. Type values in the following fields. Field/setting description host name the ip address or name of the host whose route you want to check. Timeout(s) a timeout value in sec...

  • Page 289

    Chapter 6: using the web interface 277 rebooting the emx device you can remotely reboot the emx device via the web interface. Warning: rebooting the emx deletes all webcam snapshots that are saved on the emx locally. See viewing saved snapshots and managing storage (on page 282). To reboot the devic...

  • Page 290

    Chapter 6: using the web interface 278 to reset the device to factory defaults: 1. Choose maintenance > unit reset > . 2. Click factory reset to reset the emx to factory defaults. 3. A message appears, with a countdown timer showing the remaining time of the operation. It takes about two minutes to ...

  • Page 291

    Chapter 6: using the web interface 279 2. You can click any link to access related information or download any software package. Webcam management the webcam-related menu items appear only when there are webcam(s) connected to the emx. See connecting a logitech webcam (on page 59). With a logitech ®...

  • Page 292

    Chapter 6: using the web interface 280 4. To have the live session also displayed in a primary standalone live preview window, click new live preview window.  you can send out this window's url to share the live image with other users. See sending snapshots or videos in an email or instant message ...

  • Page 293

    Chapter 6: using the web interface 281 sending snapshots or videos in an email or instant message whenever you open a primary standalone live preview window, a unique url is generated for this window session. A url supports a maximum of three sessions. Therefore, you can email or instant message up ...

  • Page 294

    Chapter 6: using the web interface 282 2. Click live preview > new live preview window. The live snapshot or video in a standalone live preview window opens. See configuring webcams and viewing live images (on page 279). 3. Copy the url from the live preview window, and send it through an email or i...

  • Page 295

    Chapter 6: using the web interface 283 3. If the latest saved snapshot is not listed yet, click > refresh on the top of the list. 4. To manually delete any images: a. Select the checkboxes of the images you want to remove.  to select all images, select the top-most checkbox in the header row. B. On...

  • Page 296

    284 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. In this chapter enabling and configuring snmp.......

  • Page 297

    Chapter 7: using snmp 285 to enable snmp notifications: 1. Choose device settings > network services > snmp. 2. In the snmp notifications section, enable the snmp notification feature, and configure related fields. For details, refer to: snmpv2c notifications (on page 285) snmpv3 notifications (on p...

  • Page 298

    Chapter 7: using snmp 286 6. Click save. Snmpv3 notifications 1. Choose device settings > network services > snmp. 2. In the snmp agent, make sure the enable snmp v1/v2c checkbox is selected. 3. In the snmp notifications section, make sure the enable snmp notifications checkbox is selected. 4. Selec...

  • Page 299

    Chapter 7: using snmp 287 field description authentication protocol, authentication passphrase, confirm authentication passphrase the three fields are available when the security level is set to authnopriv or authpriv.  select the authentication protocol - md5 or sha  enter the authentication pass...

  • Page 300

    Chapter 7: using snmp 288 mib download via the device information page: 1. Choose maintenance > device information. 2. In the information section, click the desired download link:  emd-mib  assetmanagement-mib  lhx mib 3. Click save to save the file onto your computer. Note: lhx-mib is available ...

  • Page 301

    Chapter 7: using snmp 289 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. For exa...

  • Page 302

    Chapter 7: using snmp 290 configuring ntp server settings using snmp, you can change the following ntp server-related settings in the unitconfigurationtable: enable or disable synchronization of the device's date and time with ntp servers (synchronizewithntpserver) enable or disable the use of dhcp-...

  • Page 303

    291 this section explains how to use the command line interface (cli) to administer a emx device. Cli commands are case sensitive. In this chapter about the interface.................................................................................. 291 logging in to cli.................................

  • Page 304

    Chapter 8: using the command line interface 292 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. Users are au...

  • Page 305

    Chapter 8: using the command line interface 293 after properly entering the password, the # or > system prompt appears. See different cli modes and prompts (on page 294) in the user guide for more information. Tip: the "last login" information, including the date and time, is also displayed if the s...

  • Page 306

    Chapter 8: using the command line interface 294 with an analog modem the emx supports remote access to the cli via a connected analog modem. This feature is especially useful when the lan access is not available. To connect to the emx via the modem: 1. Make sure the emx has an analog modem connected...

  • Page 307

    Chapter 8: using the command line interface 295 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 > prompt ap...

  • Page 308

    Chapter 8: using the command line interface 296 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: c...

  • Page 309

    Chapter 8: using the command line interface 297 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 c...

  • Page 310

    Chapter 8: using the command line interface 298 network configuration this command shows all network configuration and all network interfaces' information, such as the ip address, mac address, the ethernet interface's duplex mode, and the wireless interface's status/settings. # show network ip confi...

  • Page 311

    Chapter 8: using the command line interface 299 option description all show the ip-related configuration of all interfaces. You can type the cli command without the word 'all.' for example, show network ip interface . Ipv4-only or ipv6-only configuration to show ipv4-only configuration or ipv6-only ...

  • Page 312

    Chapter 8: using the command line interface 300 option description ethernet show the ipv4 or ipv6 configuration of the ethernet interface. Wireless show the ipv4 or ipv6 configuration of the wireless interface. Bridge show the ipv4 or ipv6 configuration of the bridge interface. All show the ipv4 or ...

  • Page 313

    Chapter 8: using the command line interface 301 network service settings this command shows the network service settings only, including the telnet setting, tcp ports for http, https, ssh and modbus/tcp services, and snmp settings. # show network services variables: is one of the options: all , http...

  • Page 314

    Chapter 8: using the command line interface 302 device configuration this command shows the emx configuration, such as the device name, firmware version and model type. # show emd to show detailed information, add the parameter "details" to the end of the command. # show emd details date and time se...

  • Page 315

    Chapter 8: using the command line interface 303 environmental sensor information this command syntax shows the environmental sensor's information. # show externalsensors to show detailed information, add the parameter "details" to the end of the command. # show externalsensors details external senso...

  • Page 316

    Chapter 8: using the command line interface 304 * the environmental sensor number is the id number assigned to the sensor, which can be found on the peripherals page of the emx web interface. Displayed information: without the parameter "details," only the sensor id, sensor type and reading are disp...

  • Page 317

    Chapter 8: using the command line interface 305 actuator information this command syntax shows an actuator's information. # show actuators to show detailed information, add the parameter "details" to the end of the command. # show actuators details variables: is one of the options: all , or a number...

  • Page 318

    Chapter 8: using the command line interface 306 environmental sensor threshold information this command syntax shows the specified environmental sensor's threshold-related information. # show sensor externalsensor to show detailed information, add the parameter "details" to the end of the command. #...

  • Page 319

    Chapter 8: using the command line interface 307 displayed information: without the parameter "details," only the reading, threshold, deassertion hysteresis and assertion timeout settings of the specified environmental sensor are displayed. With the parameter "details," more sensor information is dis...

  • Page 320

    Chapter 8: using the command line interface 308 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 t...

  • Page 321

    Chapter 8: using the command line interface 309 existing user profiles this command shows the data of one or all existing user profiles. # show user to show detailed information, add the parameter "details" to the end of the command. # show user details variables: is the name of the user whose profi...

  • Page 322

    Chapter 8: using the command line interface 310 existing roles this command shows the data of one or all existing roles. # show roles variables: is the name of the role whose permissions you want to query. The variable can be one of the following options: option description all this option shows all...

  • Page 323

    Chapter 8: using the command line interface 311 asset strip settings this command shows the asset strip settings, such as the total number of rack units (tag ports), asset strip state, numbering mode, orientation, available tags and led color settings. # show assetstrip variables: is one of the opti...

  • Page 324

    Chapter 8: using the command line interface 312 option description a specific number displays the settings of the specified rack unit on the specified asset strip. Use the index number to specify the rack unit. The index number is available on the asset strip or the asset strip page of the web inter...

  • Page 325

    Chapter 8: using the command line interface 313 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 ...

  • Page 326

    Chapter 8: using the command line interface 314 event type description servermonitor server-monitoring records, such as a server being declared reachable or unreachable. Assetmanagement raritan asset management events, such as asset tag connections or disconnections. Lhx schroff ® lhx/shx heat excha...

  • Page 327

    Chapter 8: using the command line interface 315 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 to show detailed information, add the parameter "details" to the...

  • Page 328

    Chapter 8: using the command line interface 316 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 ...

  • Page 329

    Chapter 8: using the command line interface 317 option description a specific integer number displays the specified number of last entries in the reliability error log. Examples this section provides examples of the show command. Example 1 - basic security information the diagram shows the output of...

  • Page 330

    Chapter 8: using the command line interface 318 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 en...

  • Page 331

    Chapter 8: using the command line interface 319 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...

  • Page 332

    Chapter 8: using the command line interface 320 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 ...

  • Page 333

    Chapter 8: using the command line interface 321 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 t...

  • Page 334

    Chapter 8: using the command line interface 322 setting data logging measurements per entry this command defines the number of measurements accumulated per log entry. Config:# emd measurementsperlogentry variables: is an integer between 1 and 600. The default is 60 samples per log entry. For more in...

  • Page 335

    Chapter 8: using the command line interface 323 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 392). Enabling or disabling peri...

  • Page 336

    Chapter 8: using the command line interface 324 setting the ipv4 configuration mode this command determines the ip configuration mode. Config:# network ipv4 interface configmethod variables: is one of the network interfaces: ethernet , wireless , bridge or all . Note that you must choose/configure t...

  • Page 337

    Chapter 8: using the command line interface 325 setting the ipv4 preferred host name after selecting dhcp as the ipv4 configuration mode, you can specify the preferred host name, which is optional. The following is the command: config:# network ipv4 interface preferredhostname variables: is one of t...

  • Page 338

    Chapter 8: using the command line interface 326 setting the ipv4 address after selecting the static ip configuration mode, you can use this command to assign a permanent ip address to the emx device. Config:# network ipv4 interface address variables: is one of the network interfaces: ethernet , wire...

  • Page 339

    Chapter 8: using the command line interface 327 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. These commands are...

  • Page 340

    Chapter 8: using the command line interface 328 config:# network ipv4 staticroutes modify interface variables: is a combination of the ip address and subnet mask of the other subnet. The format is ip address/subnet mask . Is the ip address of the next hop router. Is one of the interfaces: ethernet ,...

  • Page 341

    Chapter 8: using the command line interface 329 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. Setting the ipv6 preferred host name after selecting dhcp as the ipv6...

  • Page 342

    Chapter 8: using the command line interface 330 setting the ipv6 address after selecting the static ip configuration mode, you can use this command to assign a permanent ip address to the emx device. Config:# network ipv6 interface address address> variables: is one of the network interfaces: ethern...

  • Page 343

    Chapter 8: using the command line interface 331 setting ipv6 static routes if the ipv6 network mode is set to static ip and your local network contains two subnets, you can configure static routes to enable or disable communications between the emx and devices in the other subnet. These commands are...

  • Page 344

    Chapter 8: using the command line interface 332 config:# network ipv6 staticroutes modify interface variables: is the ip address and prefix length of the subnet where the emx belongs. The format is ip address/prefix length . Is the ip address of the next hop router. Is one of the interfaces: etherne...

  • Page 345

    Chapter 8: using the command line interface 333 configuring dns parameters use the following commands to configure dns-related settings. Specify the primary dns server: config:# network dns firstserver specify the secondary dns server: config:# network dns secondserver specify the third dns server: ...

  • Page 346

    Chapter 8: using the command line interface 334 enabling or disabling the lan interface this command enables or disables the lan interface. Config:# network ethernet ethernet enabled variables: is one of the options: true or false . Option description true the specified network interface is enabled....

  • Page 347

    Chapter 8: using the command line interface 335 changing the lan duplex mode this command determines the lan interface duplex mode. Config:# network ethernet ethernet duplexmode variables: is one of the modes: auto , half or full . Option description auto the emx selects the optimum transmission mod...

  • Page 348

    Chapter 8: using the command line interface 336 - ascii codes 0x20 ~ 0x7e setting the authentication method this command sets the wireless authentication method to either psk or extensible authentication protocol (eap). Config:# network wireless authmethod variables: is one of the authentication met...

  • Page 349

    Chapter 8: using the command line interface 337 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 authen...

  • Page 350

    Chapter 8: using the command line interface 338 config:# network wireless allowconnectionwithincorrectclock variables: the value of is peap because emx only supports protected extensible authentication protocol (peap) as the outer authentication. The value of is mschapv2 because emx only supports mi...

  • Page 351

    Chapter 8: using the command line interface 339 option description false the wireless network connection is not successfully established when the emx finds that the tls certificate is not valid due to incorrect system time. Eap ca certificate example this section provides a ca certificate example on...

  • Page 352

    Chapter 8: using the command line interface 340 miicjtccafigawibagiemaygrzalbgkqhkig9w0baqqwrtelmak ga1uebhmcvvmxnja0bgnvbaotlu5hdglvbmfsieflcm9uyxv0aw nzigfuzcbtcgfjzsbbzg1pbmlzdhjhdglvbjamfxe5nja1mjgxm zq5mdurmdgwmbcrotgwnti4mtm0ota1kza4mdawzzelmakga1ue bhmcvvmxnja0bgnvbaotlu5hdglvbmfsieflcm9uyxv0...

  • Page 353

    Chapter 8: using the command line interface 341 cascading mode may not be enabled successfully. Mode description bridge the network bridging mode, where each cascaded device is assigned a unique ip address. Portforwarding the port forwarding mode, where every cascaded device in the chain shares the ...

  • Page 354

    Chapter 8: using the command line interface 342 is one of the following options: option description ethernet ethernet port is the port where the 1st slave device is connected. Usb usb port is the port where the 1st slave device is connected. Setting network service parameters a network service comma...

  • Page 355

    Chapter 8: using the command line interface 343 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 enable or disable the https access: config:# network services https enabled va...

  • Page 356

    Chapter 8: using the command line interface 344 option description false the telnet service is disabled. Changing the telnet port this command changes the telnet port. Config:# network services telnet port variables: is a tcp port number between 1 and 65535. The default telnet port is 23. Changing t...

  • Page 357

    Chapter 8: using the command line interface 345 determining the ssh authentication method this command syntax determines the ssh authentication method. Config:# network services ssh authentication variables: is one of the options: passwordonly , publickeyonly or passwordorpublickey . Option descript...

  • Page 358

    Chapter 8: using the command line interface 346 enabling or disabling snmp v3 this command enables or disables the snmp v3 protocol. Config:# network services snmp v3 variables: is one of the options: enable or disable . Option description enable the snmp v3 protocol is enabled. Disable the snmp v3 ...

  • Page 359

    Chapter 8: using the command line interface 347 setting the sysname value this command sets the snmp mib-ii sysname value. Config:# network services snmp sysname variables: is a string comprising 0 to 255 alphanumeric characters. Setting the syslocation value this command sets the snmp mib-ii sysloc...

  • Page 360

    Chapter 8: using the command line interface 348 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 variables: is one of the options: true or false . Option description true the read-only mode is...

  • Page 361

    Chapter 8: using the command line interface 349 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 dete...

  • Page 362

    Chapter 8: using the command line interface 350 determining the time setup method this command determines the method to configure the system date and time. Config:# time method variables: is one of the time setup options: manual or ntp . Mode description manual the date and time settings are customi...

  • Page 363

    Chapter 8: using the command line interface 351 overriding dhcp-assigned ntp servers this command determines whether the customized ntp server settings override the dhcp-specified ntp servers. Config:# time ntp overridedhcpprovidedserver variables: is one of these options: true or false . Mode descr...

  • Page 364

    Chapter 8: using the command line interface 352 example to set the time zone: 1. Type the time zone command as shown below and press enter. Config:# time zone 2. The system shows a list of time zones. Type the index number of the desired time zone and press enter. 3. Type apply for the selected time...

  • Page 365

    Chapter 8: using the command line interface 353 setting the automatic daylight savings time this command determines whether the daylight savings time is applied to the time settings. Config:# time autodst variables: is one of the options: enable or disable . Mode description enable daylight savings ...

  • Page 366

    Chapter 8: using the command line interface 354 checking the accessibility of ntp servers this command verifies the accessibility of ntp servers specified manually on your emx and then shows the result. For instructions on specifying ntp servers via cli, see setting ntp parameters (on page 349). To ...

  • Page 367

    Chapter 8: using the command line interface 355 modifying firewall control parameters there are different commands for modifying firewall control parameters. Ipv4 commands enable or disable the ipv4 firewall control feature: config:# security ipaccesscontrol ipv4 enabled determine the default ipv4 f...

  • Page 368

    Chapter 8: using the command line interface 356 option description false disables the ip access control feature. Is one of the options: accept, drop or reject . Option description accept accepts traffic from all ip addresses. Drop discards traffic from all ip addresses, without sending any failure n...

  • Page 369

    Chapter 8: using the command line interface 357 config:# security ipaccesscontrol ipv4 rule add ipv6 commands add a new rule to the bottom of the ipv6 rules list: config:# security ipaccesscontrol ipv6 rule add add a new ipv6 rule by inserting it above or below a specific rule: config:# security ipa...

  • Page 370

    Chapter 8: using the command line interface 358 is one of the options: insertabove or insertbelow . Option description insertabove inserts the new rule above the specified rule number. Then: new rule's number = the specified rule number insertbelow inserts the new rule below the specified rule numbe...

  • Page 371

    Chapter 8: using the command line interface 359 config:# security ipaccesscontrol ipv6 rule modify policy modify all contents of an ipv6 existing rule: config:# security ipaccesscontrol ipv6 rule modify ipmask policy variables: is one of the options: in or out . Direction description in inbound traf...

  • Page 372

    Chapter 8: using the command line interface 360 config:# security ipaccesscontrol ipv4 rule delete ipv6 commands config:# security ipaccesscontrol ipv6 rule delete variables: is one of the options: in or out . Direction description in inbound traffic. Out outbound traffic. Is the number of the exist...

  • Page 373

    Chapter 8: using the command line interface 361 after the restricted service agreement feature is enabled, the agreement's content is displayed in the login screen. Do either of the following, or the login fails: in the web interface, select the checkbox labeled "i understand and accept the restrict...

  • Page 374

    Chapter 8: using the command line interface 362 single login limitation this command enables or disables the single login feature, which controls whether multiple logins using the same login name simultaneously is permitted. Config:# security loginlimits singlelogin variables: is one of the options:...

  • Page 375

    Chapter 8: using the command line interface 363 idle timeout this command determines how long a user can remain idle before that user is forced to log out of the emx web interface or cli. Config:# security loginlimits idletimeout variables: is a numeric value in minutes set for the idle timeout. The...

  • Page 376

    Chapter 8: using the command line interface 364 strong passwords the strong password commands determine whether a strong password is required for login, and what a strong password should contain at least. A strong password command begins with security strongpasswords . You can combine multiple stron...

  • Page 377

    Chapter 8: using the command line interface 365 lowercase character requirement this command determines whether a strong password includes at least a lowercase character. Config:# security strongpasswords enforceatleastonelowercasecharacter variables: is one of the options: enable or disable . Optio...

  • Page 378

    Chapter 8: using the command line interface 366 option description disable no numeric character is required. Special character requirement this command determines whether a strong password includes at least a special character. Config:# security strongpasswords enforceatleastonespecialcharacter vari...

  • Page 379

    Chapter 8: using the command line interface 367 modifying role-based access control parameters there are different commands for modifying role-based access control parameters. Ipv4 commands enable or disable the ipv4 role-based access control feature: config:# security rolebasedaccesscontrol ipv4 en...

  • Page 380

    Chapter 8: using the command line interface 368 tip: you can combine both commands to modify all role-based access control parameters at a time. See multi-command syntax (on page 412). Managing role-based access control rules you can add, delete or modify role-based access control rules. An ipv4 rol...

  • Page 381

    Chapter 8: using the command line interface 369 config:# security rolebasedaccesscontrol ipv6 rule add variables: is the starting ip address. Is the ending ip address. Is the role for which you want to create an access control rule. Is one of the options: allow or deny . Policy description allow acc...

  • Page 382

    Chapter 8: using the command line interface 370 config:# security rolebasedaccesscontrol ipv4 rule modify startipaddress endipaddress modify an ipv4 rule's role: config:# security rolebasedaccesscontrol ipv4 rule modify role modify an ipv4 rule's policy: config:# security rolebasedaccesscontrol ipv4...

  • Page 383

    Chapter 8: using the command line interface 371 config:# security rolebasedaccesscontrol ipv6 rule modify startipaddress endipaddress role policy variables: is the number of the existing rule that you want to modify. Is the starting ip address. Is the ending ip address. Is one of the existing roles....

  • Page 384

    Chapter 8: using the command line interface 372 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 i...

  • Page 385

    Chapter 8: using the command line interface 373 config:# security rolebasedaccesscontrol ipv4 rule add 192.168.78.50 192.168.90.100 admin deny insertabove 3 results: a new ipv4 role-based access control rule is added, dropping all packets from any ipv4 address between 192.168.78.50 and 192.168.90.10...

  • Page 386

    Chapter 8: using the command line interface 374 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. See multi-command syntax (on page 412). Changing a user's password...

  • Page 387

    Chapter 8: using the command line interface 375 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. See multi-comma...

  • Page 388

    Chapter 8: using the command line interface 376 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 enabled variables: is the name of the user whose settings you...

  • Page 389

    Chapter 8: using the command line interface 377 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 412). Enable o...

  • Page 390

    Chapter 8: using the command line interface 378 config:# user modify userpasswordasauthenticationpassphrase variables: is the name of the user whose settings you want to change. Is one of the options: true or false . Option description true authentication passphrase is identical to the password. Fal...

  • Page 391

    Chapter 8: using the command line interface 379 determine the privacy passphrase: config:# user modify privacypassphrase variables: is the name of the user whose settings you want to change. Is a string used as a privacy passphrase, comprising 8 to 32 ascii printable characters. Determine the authen...

  • Page 392

    Chapter 8: using the command line interface 380 changing the role(s) this command changes the role(s) of a specific user. Config:# user modify roles variables: is the name of the user whose settings you want to change. Is a role or a list of comma-separated roles assigned to the specified user profi...

  • Page 393

    Chapter 8: using the command line interface 381 set the preferred length unit: config:# user modify preferredlengthunit variables: is the name of the user whose settings you want to change. Is one of the options: meter or feet . Option description meter this option displays the length or height in m...

  • Page 394

    Chapter 8: using the command line interface 382 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 chan...

  • Page 395

    Chapter 8: using the command line interface 383 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. Enter new password: 5. Re-type the new password for confirm...

  • Page 396

    Chapter 8: using the command line interface 384 config:# user defaultpreferences preferredlengthunit variables: 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...

  • Page 397

    Chapter 8: using the command line interface 385 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. The new user profile is enabled. The admi...

  • Page 398

    Chapter 8: using the command line interface 386 role configuration commands a role configuration command begins with role . Creating a role this command creates a new role, with a list of semicolon-separated privileges assigned to the role. Config:# role create ;;... If a specific privilege contains...

  • Page 399

    Chapter 8: using the command line interface 387 changeemdconfiguration change emd configuration changeexternalsensorsconfiguration change peripheral device configuration changelhxconfiguration change lhx/shx configuration changemodemconfiguration change modem configuration changenetworksettings chan...

  • Page 400

    Chapter 8: using the command line interface 388 **the "switchactuator" privilege requires an argument that is separated with a colon. The argument could be: all actuators, that is, switchactuator:all an actuator's id number. For example: switchactuator:1 switchactuator:2 switchactuator:3 a list of c...

  • Page 401

    Chapter 8: using the command line interface 389 config:# role modify addprivileges :,...; :,...; :,...; ... Variables: is a string comprising up to 32 ascii printable characters. , , and the like are names of the privileges assigned to the role. Separate each privilege with a semi-colon. See all pri...

  • Page 402

    Chapter 8: using the command line interface 390 deleting a role this command deletes an existing role. Config:# role delete example - creating a role the following command creates a new role and assigns privileges to the role. Config:# role create tester firmwareupdate;vieweventsetup results: a new ...

  • Page 403

    Chapter 8: using the command line interface 391 changing the sensor name this command names an environmental sensor. Config:# externalsensor name "" variables: is the id number of the environmental sensor that you want to configure. The id number is available in the emx web interface or using the co...

  • Page 404

    Chapter 8: using the command line interface 392 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 xlabel "" variables: is the id number of th...

  • Page 405

    Chapter 8: using the command line interface 393 setting the z coordinate this command specifies the z coordinate of an environmental sensor. Config:# externalsensor zlabel "" variables: is the id number of the environmental sensor that you want to configure. The id number is available in the emx web...

  • Page 406

    Chapter 8: using the command line interface 394 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 usedefaultthresholds variables: is the id n...

  • Page 407

    Chapter 8: using the command line interface 395 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 c...

  • Page 408

    Chapter 8: using the command line interface 396 config:# defaultthresholds lowerwarning set the default deassertion hysteresis for a specific sensor type: config:# defaultthresholds hysteresis set the default assertion timeout for a specific sensor type: config:# defaultthresholds assertiontimeout v...

  • Page 409

    Chapter 8: using the command line interface 397 sensor types measurement units vibration g is the deassertion hysteresis value applied to the specified sensor type. Is the assertion timeout value applied to the specified sensor type. It ranges from 0 to 100 (samples). Example - default upper thresho...

  • Page 410

    Chapter 8: using the command line interface 398 config:# sensor externalsensor upperwarning set the lower critical threshold for an environmental sensor: config:# sensor externalsensor lowercritical set the lower warning threshold for an environmental sensor: config:# sensor externalsensor lowerwarn...

  • Page 411

    Chapter 8: using the command line interface 399 option description a numeric value sets a value for the specified threshold of a specific environmental sensor and enables this threshold at the same time. Is a numeric value that is assigned to the hysteresis for the specified environmental sensor. Se...

  • Page 412

    Chapter 8: using the command line interface 400 actuator configuration commands an actuator configuration command begins with actuator . You can configure the name and location parameters of an individual actuator. You can configure various parameters for one actuator at a time. See multi-command sy...

  • Page 413

    Chapter 8: using the command line interface 401 note: to specify the z coordinate using the rack units, see setting the z coordinate format for environmental sensors (on page 321). Is a sentence or paragraph comprising up to 64 ascii printable characters, and it must be enclosed in quotes. Example -...

  • Page 414

    Chapter 8: using the command line interface 402 is the number of successful pings for declaring the monitored device "reachable." valid range is 0 to 200. Is the number of consecutive unsuccessful pings for declaring the monitored device "unreachable." valid range is 1 to 100. Is the wait time to se...

  • Page 415

    Chapter 8: using the command line interface 403 config:# serverreachability modify ipaddress enable or disable the ping monitoring feature for the device: config:# serverreachability modify pingmonitoringenabled modify the number of successful pings for declaring "reachable": config:# serverreachabi...

  • Page 416

    Chapter 8: using the command line interface 404 config:# serverreachability modify numberoffailurestodisable variables: is a number representing the sequence of the it device in the server monitoring list. Is the ip address or host name of the it device whose settings you want to modify. Is one of t...

  • Page 417

    Chapter 8: using the command line interface 405 asset management commands you can use the cli commands to change the settings of the connected asset strip (if any) or the settings of leds on the asset strip. Asset strip management an asset strip management configuration command begins with assetstri...

  • Page 418

    Chapter 8: using the command line interface 406 specifying the rack unit numbering mode this command syntax specifies the numbering mode of rack units on the asset strips connected to the emx device. The numbering mode changes the rack unit numbers. Config:# assetstrip rackunitnumberingmode variable...

  • Page 419

    Chapter 8: using the command line interface 407 specifying the asset strip orientation this command syntax specifies the orientation of the asset strips connected to the emx device. Usually you do not need to perform this command unless your asset strips do not come with the tilt sensor, causing the...

  • Page 420

    Chapter 8: using the command line interface 408 setting led colors for disconnected tags this command syntax sets the led color for all rack units on the connected asset strip(s) to indicate the absence of a connected asset tag. Config:# assetstrip ledcolorfordisconnectedtags variables: is the hexad...

  • Page 421

    Chapter 8: using the command line interface 409 setting the led operation mode this command syntax determines whether a specific rack unit on the specified asset strip follows the global led color settings. Config:# rackunit ledoperationmode variables: is the number of the feature port where the sel...

  • Page 422

    Chapter 8: using the command line interface 410 setting an led color for a rack unit this command syntax sets the led color for a specific rack unit on the specified asset strip. You need to set a rack unit's led color only when the led operation mode of this rack unit has been set to "manual." conf...

  • Page 423

    Chapter 8: using the command line interface 411 mode description blinkslow this mode has the led blink slowly. Blinkfast this mode has the led blink quickly. Examples this section illustrates several asset management examples. Example 1 - asset strip led colors for disconnected tags this command syn...

  • Page 424

    Chapter 8: using the command line interface 412 setting the baud rates 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, ...

  • Page 425

    Chapter 8: using the command line interface 413 option description forceconsole the emx attempts to recognize that the connected device is set for the console mode. Forceanalogmodem the emx attempts to recognize that the connected device is an analog modem. Forcegsmmodem the emx attempts to recogniz...

  • Page 426

    Chapter 8: using the command line interface 414 example 1 - combination of ip, subnet mask and gateway parameters the following multi-command syntax configures ipv4 address, subnet mask and gateway for the network connectivity simultaneously. Config:# network ipv4 ipaddress 192.168.84.225 subnetmask...

  • Page 427

    Chapter 8: using the command line interface 415 switching on an actuator this command syntax turns on one actuator. # control actuator on to quicken the operation, you can add the parameter "/y" to the end of the command, which confirms the operation. # control actuator on /y variables: is an actuat...

  • Page 428

    Chapter 8: using the command line interface 416 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 ...

  • Page 429

    Chapter 8: using the command line interface 417 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. 2. Type either of the following commands to restart t...

  • Page 430

    Chapter 8: using the command line interface 418 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. Type di...

  • Page 431

    Chapter 8: using the command line interface 419 showing network connections this command syntax displays network connections and/or status of ports. Diag> netstat variables: is one of the options: ports or connections . Option description ports shows tcp/udp ports. Connections shows network connecti...

  • Page 432

    Chapter 8: using the command line interface 420 options description timeout determines the waiting period before timeout. Is an integer number in seconds ranging from 1 to 600. The command looks like the following when it includes all options: diag> ping count size timeout tracing the route this com...

  • Page 433

    Chapter 8: using the command line interface 421 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 c...

  • Page 434

    422 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 ....................................................................... 421 bulk configuration via scp ...................

  • Page 435

    Chapter 9: using scp commands 423 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 command -- pscp @:/fwupdate bulk configuration via scp like performing bulk configuration via the web interface, there are two steps with ...

  • Page 436

    Chapter 9: using scp commands 424 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 examples: save operation: scp admin@192.168.87.50:/bulk_config.Xml co...

  • Page 437

    Chapter 9: using scp commands 425 scp backup_settings.Xml @ ip>:/settings_restore is the "admin" or any user profile with the administrator privileges. Is the ip address of the emx whose settings you want to restore. 2. Type the user password when prompted. 3. The system copies the configuration inc...

  • Page 438

    Chapter 9: using scp commands 426 3. The system saves the diagnostic data from the emx to a file named "diag-data.Tgz." scp example: scp admin@192.168.87.50:/diag-data.Tgz windows pscp command: pscp in windows works in a similar way to the scp.  pscp @:/diag-data.Tgz.

  • Page 439

    427 in this chapter maximum ambient operating temperature........................................... 426 emx2-111 feature rj-45 port pinouts................................................... 426 emx2-888 feature rj-45 port pinouts................................................... 427 sensor rj-12 ...

  • Page 440

    Appendix a: specifications 428 rj-45 pin/signal definition pin no. Signal direction description 8 dcd input reserved emx2-888 feature rj-45 port pinouts rj-45 pin/signal definition pin no. Signal direction description 1 dtr output reserved 2 gnd ― signal ground 3 +5v ― fuse protected warning: pin 3 ...

  • Page 441

    Appendix a: specifications 429 rj-12 pin/signal definition 4 ― ― ― 5 gnd ― signal ground 6 1-wire 1-wire signal for external environmental sensor packages serial rs-232 "db9" port pinouts rs-232 pin/signal definition pin no. Signal direction description 1 dcd input data 2 rxd input receive data (dat...

  • Page 442

    Appendix a: specifications 430 rs-485 pin/signal definition 6 d- bi-direction al data - 7 ― ― ― 8 ― ― ―.

  • Page 443

    431 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 firmware upgrade downloading diagnostic data tip: you can also accomplish the same tasks via the tftp s...

  • Page 444

    Appendix b: configuration or firmware upgrade with a usb drive 432 configuration files there are three types of configuration files. Fwupdate.Cfg: this file must be always present for performing configuration or firmware upgrade tasks. See fwupdate.Cfg (on page 432). Config.Txt: this file is used fo...

  • Page 445

    Appendix b: configuration or firmware upgrade with a usb drive 433 fwupdate.Cfg the configuration file, fwupdate.Cfg , is an ascii text file containing key-value pairs, one per line. Each value in the file must be separated by an equal sign (=), without any surrounding spaces. Keys are not case sens...

  • Page 446

    Appendix b: configuration or firmware upgrade with a usb drive 434 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 ...

  • Page 447

    Appendix b: configuration or firmware upgrade with a usb drive 435 the default value is serial:1, making the emx search for its serial number in the first column. This option is used only if the "device_list" option has been set. Collect_diag if this option is set to true, the diagnostic data of the...

  • Page 448

    Appendix b: configuration or firmware upgrade with a usb drive 436 additional configuration keys set via the config.Txt file will be applied after performing the configuration restore operation. This option cannot be used with the option "bulk_config_restore." if a firmware upgrade will be performed...

  • Page 449

    Appendix b: configuration or firmware upgrade with a usb drive 437 config.Txt to perform device configuration using a usb drive, you must: copy the device configuration file "config.Txt" to the root directory of the usb drive. Reference the "config.Txt" file in the config option of the "fwupdate.Cfg...

  • Page 450

    Appendix b: configuration or firmware upgrade with a usb drive 438 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 implemente...

  • Page 451

    Appendix b: configuration or firmware upgrade with a usb drive 439 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. Copied to the root...

  • Page 452

    Appendix b: configuration or firmware upgrade with a usb drive 440 data encryption in 'config.Txt' encryption for any settings in the file "config.Txt" is supported as of release 3.2.20. When intending to prevent people from identifying the values of any settings, you can encrypt them. Encrypted dat...

  • Page 453

    Appendix b: configuration or firmware upgrade with a usb drive 441 1. In the cli, type the following command to encrypt "private." 2. The cli generates and shows the encrypted form of "private." 3. In the "config.Txt" file, make the following changes to the snmp write community setting. A. Replace t...

  • Page 454

    Appendix b: configuration or firmware upgrade with a usb drive 442 6. When the firmware upgrade finishes, the front panel display indicates the firmware upgrade result.  happy smiley: successful. Depending on your product, the happy smiley looks like one of the following.  sad smiley: failed. Chec...

  • Page 455

    443 if a tftp server is available, you can use it and appropriate configuration files to perform any or all of the following tasks for a large number of emx devices in the same network. Initial deployment configuration changes firmware upgrade downloading diagnostic data this feature is drastically ...

  • Page 456

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 444 config.Txt devices.Csv 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 suppor...

  • Page 457

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 445 all required configuration files are available in the tftp root directory. See bulk configuration/upgrade procedure (on page 442). If you are going to upload any emx diagnostic file or create a log file in the tftp server, the firs...

  • Page 458

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 446 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 options..

  • Page 459

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 447 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 460

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 448 a. Select raritan pdu in the "option class" field. B. Click add to add the first option. Type "pdu-tftp-server" in the name field, select ip address as the data type, and type 1 in the code field..

  • Page 461

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 449 c. Click add to add the second option. Type "pdu-update-control-file" in the name field, select string as the data type, and type 2 in the code field. D. Click add to add the third one. Type "pdu-update-magic" in the name field, se...

  • Page 462

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 450 the policy is named "pdu" in this illustration. C. Click add to add a new condition..

  • Page 463

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 451 d. Select the vendor class "raritan pdu" in the value field, click add and then ok. E. Click next..

  • Page 464

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 452 f. 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 465

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 453 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 466

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 454 h. Select "002 pdu-update-control-file" from the available options list, and type the filename "fwupdate.Cfg" in the "string value" field. I. Select "003 pdu-update-magic" from the available options list, and type any string in the...

  • Page 467

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 455 important: the magic cookie is transmitted to and stored in emx at the time of executing the "fwupdate.Cfg" commands. The dhcp/tftp operation is triggered only when there is a mismatch between the magic cookie in dhcp and the one s...

  • Page 468

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 456 a. Right-click the ipv6 node in dhcp to select define vendor classes. B. Click add to add a new vendor class. C. Specify a unique name for the vendor class, type "13742" in the "vendor id (iana)" field, and type the binary codes of...

  • Page 469

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 457 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 470

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 458 b. Select raritan pdu 1.0 in the "option class" field. C. Click add to add the first option. Type "pdu-tftp-server" in the name field, select ip address as the data type, and type 1 in the code field..

  • Page 471

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 459 d. Click add to add the second option. Type "pdu-update-control-file" in the name field, select string as the data type, and type 2 in the code field. E. Click add to add the third one. Type "pdu-update-magic" in the name field, se...

  • Page 472

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 460 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 473

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 461 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...

  • Page 474

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 462 important: the magic cookie is transmitted to and stored in emx at the time of executing the "fwupdate.Cfg" commands. The dhcp/tftp operation is triggered only when there is a mismatch between the magic cookie in dhcp and the one s...

  • Page 475

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 463 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).  c...

  • Page 476

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 464 ipv4 illustration example in dhcpd.Conf: dhcp ipv6 configuration in linux modify the "dhcpd6.Conf" file for ipv6 settings when your dhcp server is running linux. Required linux ipv6 settings in dhcp: 1. Locate and open the "dhcpd6....

  • Page 477

    Appendix c: bulk configuration or firmware upgrade via dhcp/tftp 465  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 ...

  • Page 478

    466 you can use either the reset button or the command line interface (cli) to reset the emx. Important: exercise caution before resetting the emx to its factory defaults. This erases existing information and customized settings, such as user profiles, threshold values, and so on. Only firmware upgr...

  • Page 479

    Appendix d: resetting to factory defaults 467 2. Launch a terminal emulation program such as hyperterminal, kermit, or putty, and open a window on the emx. For information on the serial port configuration, see step 2 of initial network configuration via cli (on page 15). 3. Press (and release) the r...

  • Page 480

    Appendix d: resetting to factory defaults 468 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 procedu...

  • Page 481

    469 this section provides an ldap example for illustrating the configuration procedure using microsoft active directory ® (ad). To configure ldap authentication, four main steps are required: a. Determine user accounts and roles (groups) intended for the emx b. Create user groups for the emx on the ...

  • Page 482

    Appendix e: ldap configuration illustration 470 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: the groups (roles) for the emx are named emx_admin...

  • Page 483

    Appendix e: ldap configuration illustration 471 3. Add the emxuser and userb accounts to the emx_admin group. 4. Verify whether each group comprises correct users..

  • Page 484

    Appendix e: ldap configuration illustration 472 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...

  • Page 485

    Appendix e: ldap configuration illustration 473 field/setting do this... Bind dn, bind password, confirm bind password skip the three fields because of anonymous bind. Base dn for search type dc=techadssl,dc=com as the starting point where your search begins on the ad server. Login name attribute en...

  • Page 486

    Appendix e: ldap configuration illustration 474 2. Click to add a new role. A. Type emx_user in the role name field. B. Type a description for the emx_user role in the description field. In this example, we type "view emx settings" to describe the role. C. In the privileges list, select unrestricted...

  • Page 487

    Appendix e: ldap configuration illustration 475 4. Keep the roles page open to create the emx_admin role. To create the emx_admin role with full permissions assigned: 1. Click to add another role. A. Type emx_admin in the role name field. B. Type a description for the emx_admin role in the descripti...

  • Page 488

    Appendix e: ldap configuration illustration 476 2. The emx_admin role is created..

  • Page 489

    477 in this chapter returning user group information ......................................................... 476 setting the registry to permit write operations to the schema ........... 477 creating a new attribute......................................................................... 477 addin...

  • Page 490

    Appendix f: updating the ldap schema 478 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. Right-click the active directory ® schem...

  • Page 491

    Appendix f: updating the ldap schema 479 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. Type 1.3.6.1.4.1.13742...

  • Page 492

    Appendix f: updating the ldap schema 480 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 493

    Appendix f: updating the ldap schema 481 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. Right-click active directory ® schema in the left pa...

  • Page 494

    Appendix f: updating the ldap schema 482 3. Go to the directory where the support tools were installed. Run adsiedit.Msc. The adsi edit window opens. 4. Open the domain. 5. In the left pane of the window, select the cn=users folder..

  • Page 495

    Appendix f: updating the ldap schema 483 6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select properties. 7. Click the attribute editor tab if it is not already open. Choose rciusergroup from the attributes list. 8. Click edit. The strin...

  • Page 496

    484 this section provides illustrations for configuring radius authentication. One illustration is based on the microsoft ® network policy server (nps), and the other is based on a freeradius server. The following steps are required for any radius authentication: 1. Configure radius authentication o...

  • Page 497

    Appendix g: radius configuration illustration 485 b. On the nps, configure connection request policies and the standard attribute. See step b: configure connection policies and standard attributes (on page 488). Some configuration associated with microsoft active directory (ad) is also required for ...

  • Page 498

    Appendix g: radius configuration illustration 486 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 499

    Appendix g: radius configuration illustration 487 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. Type a...

  • Page 500

    Appendix g: radius configuration illustration 488 f. 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..

  • Page 501

    Appendix g: radius configuration illustration 489 step b: configure connection policies and standard attributes you need to configure the following for connection request policies: ip address or host name of the emx connection request forwarding method authentication method(s) standard radius attrib...

  • Page 502

    Appendix g: radius configuration illustration 490 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 503

    Appendix g: radius configuration illustration 491  you can leave the "type of network access server" field to the default -- unspecified..

  • Page 504

    Appendix g: radius configuration illustration 492 4. Click next to show the "specify conditions" screen. Click add. 5. The "select condition" dialog appears. Click add..

  • Page 505

    Appendix g: radius configuration illustration 493 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 ex...

  • Page 506

    Appendix g: radius configuration illustration 494 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 "c...

  • Page 507

    Appendix g: radius configuration illustration 495 note: if your emx uses pap, then select "pap.".

  • Page 508

    Appendix g: radius configuration illustration 496 10. Select standard to the left of the dialog and then click add..

  • Page 509

    Appendix g: radius configuration illustration 497 11. Select filter-id from the list of attributes and click add..

  • Page 510

    Appendix g: radius configuration illustration 498 12. In the attribute information dialog, click add. 13. Select string, type raritan:g{admin} in the text box, and then click ok..

  • Page 511

    Appendix g: radius configuration illustration 499 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 512

    Appendix g: radius configuration illustration 500 14. The new attribute is added. Click ok..

  • Page 513

    Appendix g: radius configuration illustration 501 15. Click next to continue..

  • Page 514

    Appendix g: radius configuration illustration 502 16. A summary showing connection request policy settings is displayed. Click finish to close the dialog. Freeradius standard attribute illustration with standard attributes, no dictionary files are required. You simply add all user data, including us...

  • Page 515

    Appendix g: radius configuration illustration 503 steve cleartext-password := "test123" filter-id = "raritan:g{admin}", filter-id = "raritan:g{systemtester}" vendor-specific attributes you must specify the following properties when using a radius vendor-specific attribute (vsa). Vendor code = 13742 ...

  • Page 516

    Appendix g: radius configuration illustration 504 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. Presu...

  • Page 517

    Appendix g: radius configuration illustration 505 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 g: radius configuration illustration 506 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. Type a...

  • Page 519

    Appendix g: radius configuration illustration 507 f. 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..

  • Page 520

    Appendix g: radius configuration illustration 508 step b: configure connection policies and vendor-specific attributes you need to configure the following for connection request policies: ip address or host name of the emx connection request forwarding method authentication method(s) standard radius...

  • Page 521

    Appendix g: radius configuration illustration 509 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 g: radius configuration illustration 510  you can leave the "type of network access server" field to the default -- unspecified..

  • Page 523

    Appendix g: radius configuration illustration 511 4. Click next to show the "specify conditions" screen. Click add. 5. The "select condition" dialog appears. Click add..

  • Page 524

    Appendix g: radius configuration illustration 512 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 ex...

  • Page 525

    Appendix g: radius configuration illustration 513 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 "c...

  • Page 526

    Appendix g: radius configuration illustration 514 note: if your emx uses pap, then select "pap." 10. Select vendor specific to the left of the dialog, and click add. The add vendor specific attribute dialog appears. 11. Select custom in the vendor field, and click add. The attribute information dial...

  • Page 527

    Appendix g: radius configuration illustration 515 note that multiple roles are separated with a space. 16. Click ok. Freeradius vsa illustration a vendor-specific dictionary file is required for the vendor-specific-attribute configuration on freeradius. Therefore, there are two major configuration s...

  • Page 528

    Appendix g: radius configuration illustration 516 vendor raritan 13742 begin-vendor raritan attribute raritan-user-roles 26 string end-vendor raritan step b -- create a user profile for "steve" in freeradius: 1. Go to this location: /etc/raddb/users. 2. Add the data of the user "steve" by typing the...

  • Page 529

    Appendix g: radius configuration illustration 517 2. Right-click nps (local) and select "register server in active directory." 3. Click ok, and then ok again. To grant emx users remote access permission: 1. Open active directory users and computers..

  • Page 530

    Appendix g: radius configuration illustration 518 2. Open the properties dialog of the user whom you want to grant the access permission. 3. Click the dial-in tab and select the "allow access" checkbox. To enable reversible encryption for chap authentication: 1. Open active directory users and compu...

  • Page 531

    Appendix g: radius configuration illustration 519 3. Click the account tab and select the "store password using reversible encryption" checkbox..

  • Page 532

    520 in this chapter reserving ip addresses in dhcp servers .............................................. 519 sensor threshold settings...................................................................... 523 pdview app for viewing the emx ..............................................................

  • Page 533

    Appendix h: additional emx information 521 reserving ip in windows to reserve the ip address of any network interface in the windows dhcp server, you must convert that interface's client identifier into hexadecimal ascii codes. For each interface's client identifier, see reserving ip addresses in dh...

  • Page 534

    Appendix h: additional emx information 522 reserving ip in linux there are two methods to reserve the ip address of any network interface in the standard linux dhcp server (isc dhcp server): convert an interface's client identifier into hexadecimal ascii codes. Use an interface's original client ide...

  • Page 535

    Appendix h: additional emx information 523 interface client identifier conversion bridge peg1a00003 = 50 45 47 31 41 30 30 30 30 33 2. Separate the converted ascii codes with a colon, and a prefix "00:" must be added to the beginning of the converted codes. For example, the converted client identifi...

  • Page 536

    Appendix h: additional emx information 524 sensor threshold settings this section explains the thresholds settings for a numeric sensor. Thresholds and sensor states a numeric sensor has four thresholds: lower critical, lower warning, upper warning and upper critical. The threshold settings determin...

  • Page 537

    Appendix h: additional emx information 525 above upper critical upper critical above upper warning upper warning normal lower warning below lower warning lower critical below lower critical available sensor states:.

  • Page 538

    Appendix h: additional emx information 526 the more thresholds are enabled for a sensor, the more sensor states are available for it. The "normal' state is always available regardless of whether any threshold is enabled. For example: when a sensor only has the upper critical threshold enabled, it ha...

  • Page 539

    Appendix h: additional emx information 527 "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 new, "worse" state. Below are bad state...

  • Page 540

    Appendix h: additional emx information 528 in the threshold settings, the assertion timeout field postpones or even cancels the "assertion" action. It determines how long a sensor must be in the "worse" new state before the emx triggers the "assertion" action. If that sensor changes its state again ...

  • Page 541

    Appendix h: additional emx information 529 "to de-assert" and deassertion hysteresis after the emx asserts a worse state for a sensor, it may de-assert that state later on if the readings improve. To de-assert a state: to de-assert a state is to announce the end of the previously-asserted worse stat...

  • Page 542

    Appendix h: additional emx information 530 in the threshold settings, the deassertion hysteresis field determines a new level to trigger the "deassertion" action. This function is similar to a thermostat, which instructs the air conditioner to turn on the cooling system when the temperature exceeds ...

  • Page 543

    Appendix h: additional emx information 531 assumption: upper warning threshold is enabled. Upper warning = 20 (degrees celsius) deassertion hysteresis = 3 (degrees celsius) "deassertion" level = 20-3 = 17 (degrees celsius) when the emx detects that a temperature sensor's reading drops below 20 degre...

  • Page 544

    Appendix h: additional emx information 532 2. After installing the pdview, launch it. Below illustrates the pdview screen 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 de...

  • Page 545

    Appendix h: additional emx information 533 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 cli...

  • Page 546

    Appendix h: additional emx information 534 altitude (meters) altitude (feet) correction factor 425 1394 1.00 500 1640 1.01 740 2428 1.04 1500 4921 1.15 2250 7382 1.26 3000 9842 1.38 ways to probe existing user profiles this section indicates available ways to query existing user accounts on the emx....

  • Page 547

    Appendix h: additional emx information 535 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 t...

  • Page 548

    Appendix h: additional emx information 536 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 ...

  • Page 549

    Appendix h: additional emx information 537 possible root causes the following lists the network accessibility issues and possible root causes. You can always troubleshoot the software settings by connecting the emx to a computer if network access to that emx fails. See connecting the emx to a comput...

  • Page 550

    Appendix h: additional emx information 538 symptom probable cause failure to access a slave device network connection to the master device is lost. The cascading cable connected to the slave device in question or any upstream device (if available) is loose or lost. No power is supplied to the slave ...

  • Page 551

    Appendix h: additional emx information 539 slave connection and disconnection events in the bridging mode, events regarding connection/disconnection of a downstream slave device via usb is not logged. However, in the port forwarding mode, whenever the connection or disconnection of a downstream slav...

  • Page 552

    Appendix h: additional emx information 540 ping via the cli you can access the cli interface by connecting a computer to the emx or using ssh/telnet. See ssh/telnet access (see " with ssh or telnet " on page 293) for details. You must perform the ping command in the diagnostic mode. To enter the dia...

  • Page 553

    Appendix h: additional emx information 541 diag> ping count size timeout browsing through the online help the emx online help is accessible over the internet. To use online help, active content must be enabled in your browser. If you are using internet explorer 7, you must enable scriplets. Consult ...

  • Page 554

    Appendix h: additional emx information 542 9. To email any url link to the currently selected topic to any person, click the "email this page" icon in the toolbar. 10. To email your comments or suggestions regarding the online help to raritan, click the "send feedback" icon . 11. To print the curren...

  • Page 555

    543 in this chapter asset management strips and raritan pdus......................................... 542 asset management strips and dctrack .................................................. 542 asset management strips and raritan pdus asset strips also work with the following raritan power distri...

  • Page 556

    Appendix i: integrating asset management strips with other products 544 each it item connected to the asset strip 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 557

    545 a a note about enabling thresholds • 290 a note about infinite loop • 244 a note about untriggered rules • 244 about the interface • 291 action group • 219, 222 actuator configuration commands • 390, 391, 400 actuator control operations • 414 actuator information • 305 adding a firewall rule • 3...

  • Page 558

    Index 546 changing the ssh configuration • 344 changing the ssh port • 344 changing the telnet configuration • 343 changing the telnet port • 344 changing your own password • 382 changing your password • 88, 138, 139 checking lua scripts states • 257, 258, 259 checking the accessibility of ntp serve...

  • Page 559

    Index 547 creating users • 86, 88, 138, 142, 143, 144, 147, 175, 190, 284 customizing the date and time • 352 d daisy-chain limitations of composite asset strips • 36, 37 dashboard • 92, 94, 221 dashboard - alarms • 95, 97, 219 dashboard - alerted sensors • 95 data encryption in 'config.Txt' • 437, ...

  • Page 560

    Index 548 enabling or disabling telnet • 343 enabling or disabling the lan interface • xii, 334 enabling or disabling the read-only mode • 348 enabling or disabling the restricted service agreement • 360 enabling service advertising • 148, 170, 178, 348 enabling the restricted service agreement • 87...

  • Page 561

    Index 549 full disaster recovery • 271 fwupdate.Cfg • 431, 432, 433, 437, 439, 441 g gathering ldap/radius information • 190, 191 h help command • 296 history buffer length • 316 how the automatic management function works • 99, 100, 323 i identifying cascaded devices • 263 identifying the sensor po...

  • Page 562

    Index 550 mounting a zero u emx • 6 multi-command syntax • 356, 361, 363, 364, 368, 374, 375, 377, 380, 383, 395, 397, 400, 402, 413 n naming a rack unit • 408 naming an asset strip • 405 network configuration • xi, 298 network configuration commands • 323 network diagnostics • 261, 275 network inte...

  • Page 563

    Index 551 sample sensor-level event rule • 243 scheduling an action • 205, 224, 235, 238 schneider electric powerlogic pm710 • 133, 135 schroff lhx/shx • 62, 119, 130, 133 security configuration commands • 354 security settings • 308 send an snmp notification • 172, 220, 230 send email • 210, 220, 2...

  • Page 564

    Index 552 setting wireless parameters • 335 setting your preferred measurement units • 99, 138, 142, 146, 147 showing information • 297 showing network connections • 419 shx request maximum cooling • 132 single login limitation • 362 slave connection and disconnection events • xii, 538, 539 snmp get...

  • Page 565

    Index 553 using an optional dpx3-envhub4 sensor hub • 42, 53 using an optional dpx-envhub2 cable • 43 using an optional dpx-envhub4 sensor hub • 42 using an x cable • 30, 37 using default thresholds • 394 using scp commands • 422 using snmp • 270, 284 using the cli command • 417, 467 using the comma...