Raritan EMX User Guide Release 2.2.0 Copyright © 2012 Raritan, Inc. EMX-0D-v2.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 2012 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.
Contents Chapter 1 Introduction 1 Overview ........................................................................................................................................ 2 What's New in EMX Help ...............................................................................................................iii Product Models ............................................................................................................................. iv EMX2-111 .....................................
Contents Reset Button ................................................................................................................................ 50 Contact Closure Sensor Termination ........................................................................................... 51 Power Switch ............................................................................................................................... 51 Logging In ........................................................................
Contents Changing the Telnet Settings ............................................................................................ 91 Enabling Service Advertisement........................................................................................ 92 Configuring the SMTP Settings ................................................................................................... 92 Setting Up an EMX Using Bulk Configuration .............................................................................
Contents Modifying an Action ......................................................................................................... 157 Deleting an Event Rule or Action..................................................................................... 158 A Note about Untriggered Rules ...................................................................................... 158 Event Logging ..................................................................................................................
Contents Chapter 9 Using SNMP 201 Overview .................................................................................................................................... 201 Enabling SNMP .......................................................................................................................... 202 Configuring SNMP Notifications ................................................................................................ 204 SNMPv2c Notifications ..................................
Contents Asset Sensor Management ............................................................................................. 313 Rack Unit Configuration ................................................................................................... 316 Setting the History Buffer Length..................................................................................... 320 Multi-Command Syntax ...................................................................................................
Contents Appendix C Raritan PX Asset Management 349 Overview .................................................................................................................................... 349 Appendix D Specifications 351 Altitude Correction Factors (EMX) ............................................................................................. 351 Maximum Ambient Operating Temperature (EMX) ................................................................... 351 Serial RS-232 Port Pinouts ...
Chapter 1 Introduction In This Chapter Overview ....................................................................................................2 What's New in EMX Help ......................................................................... iii Product Models ......................................................................................... iv Product Features ....................................................................................... v Package Contents ...........................
Chapter 1: Introduction Overview The EMX device provides a rack management solution that combines both asset management and environmental monitoring capabilities. With asset management capability, you can remotely track the location of IT equipment after tagging the IT devices electronically. This feature is especially useful when there are hundreds of IT devices to administer.
What's New in EMX Help The following sections have changed or information has been added to the EMX Help based on enhancements and changes to the equipment and/or user documentation.
Chapter 1: Introduction Product Models The EMX devices include two models: EMX2-111 and EMX2-888. Different models are functionally identical, but vary in the size and total number of ports.
Introduction Product Features In general, the EMX features include: The ability to remotely track the location of each IT equipment that is electronically tagged using Raritan asset tags LED color change on the asset sensor to distinguish between detected and undetected asset tags Support for a maximum of 10-meter cabling on the EMX-888 and 1meter cabling for the EMX-111 for each connected asset sensor The ability to monitor environmental factors such as external temperature and humidity
Chapter 1: Introduction The ability to monitor a connected Schroff® LHX-20 or LHX-40 heat exchanger The ability to diagnose the network, such as pinging a host or listing TCP connections The ability to monitor sever accessibility Full disaster recovery option in case of a catastrophic failure during a firmware upgrade Package Contents The following describes the equipment shipped with an EMX device.
Chapter 2 Installing and Configuring the EMX Device In This Chapter Before You Begin ......................................................................................7 Mounting the EMX Device .........................................................................7 Connecting the EMX to a Power Source .................................................11 Configuring the EMX ...............................................................................11 Combining Asset Sensors .......................
Chapter 2: Installing and Configuring the EMX Device Mounting a Zero U EMX Device This section describes how to mount a Zero U EMX device using Lbrackets and two buttons. To mount Zero U models using L-brackets and two buttons: 1. Align the two edge slots of the L-bracket with the two screw holes on the top of the EMX device. 2. Screw the L-bracket to the device and ensure the bracket is fastened securely. 3. Repeat Steps 1 to 2 to screw another L-bracket to the bottom of the device. 4.
Chapter 2: Installing and Configuring the EMX Device Mount the device by screwing a mounting button in the back center of each L-bracket and then having both buttons engage the mounting holes in the rack. The recommended torque for the button is 1.96 N·m (20 kgf·cm). Mounting a 1U EMX Device Using the appropriate brackets and tools, fasten the 1U EMX device to the rack or cabinet. To mount the 1U EMX device: 1. Attach one rackmount bracket to one side of the EMX device. a.
Chapter 2: Installing and Configuring the EMX Device 3. Insert one end of the cable-support bar into the L-shaped hole of the rackmount bracket, and align the hole on the end of the bar with the threaded hole adjacent to the L-shaped hole. 4. Secure the cable-support bar with one of the Raritan-provided cap screws. 5. Repeat Steps 3 to 4 to secure the other end of the cable-support bar to the other rackmount bracket. 6.
Chapter 2: Installing and Configuring the EMX Device Connecting the EMX to a Power Source If your EMX device is designed to use a cable retention clip, install the clip before connecting a power cord. A cable retention clip prevents the connected power cord from coming loose or falling off. The use of cable retention clips is highly recommended for regions with high seismic activities, and environments where shocks and vibrations are expected. To connect the EMX device to a power source: 1.
Chapter 2: Installing and Configuring the EMX Device 2. Connect the EMX device to the network via a wired or wireless connection. 3. Configure the EMX device using the command line interface. Connecting the EMX to a Computer To configure the EMX using a computer, it must be connected to the computer with an RS-232 serial interface. The computer must have a communications program such as HyperTerminal or PuTTY.
Chapter 2: Installing and Configuring the EMX Device 2. Run dominion-serial-setup.exe. A Dominion Serial Console Driver Setup Wizard appears. 3. Click Install to install the driver. 4. Click Finish when the installation is complete. 5. Connect the EMX's USB cable to the computer. The driver is automatically installed. To install the driver in Windows® XP: 1. Disconnect the EMX's USB cable from the computer. 2. Check if the file "usbser.sys" is available in C:\Windows\ServicePackFiles\i386.
Chapter 2: Installing and Configuring the EMX Device Connecting the EMX to Your Network To use the web interface to administer the EMX, you must connect the EMX to your local area network (LAN). The EMX can be connected to a wired or wireless network. To make a wired connection: 1. Connect a standard Category 5e/6 UTP cable to the ETHERNET port on the EMX. 2. Connect the other end of the cable to your LAN. To make a wireless connection: Do one of the following: Plug a 802.
Chapter 2: Installing and Configuring the EMX Device Initial Network Configuration After the EMX device is connected to your network, you must provide it with an IP address and some additional networking information. This section describes the initial configuration via a serial or USB connection. To configure the EMX via the LAN, see Modifying the Network Configuration (BCM, EMX, PX2, PXE) (see "Modifying the Network Configuration" on page 78). To configure the EMX device: 1.
Chapter 2: Installing and Configuring the EMX Device b. For the wired network mode, you may configure the LAN interface settings. In most scenarios, the default setting (auto) works well and should not be changed unless required. To set LAN interface speed Use this command network interface LANInterfaceSpeed
Chapter 2: Installing and Configuring the EMX Device To set Use this command Authentication network wireless authMethod method where is psk for Pre-Shared Key or eap for Extensible Authentication Protocol. PSK network wireless PSK where is the PSK string. network wireless EAP outer authentication eapOuterAuthentication where is PEAP. network wireless EAP inner authentication eapInnerAuthentication where is MSCHAPv2.
Chapter 2: Installing and Configuring the EMX Device To set IP protocol Use this command network ip proto where is v4Only for enabling IPv4, v6Only for enabling IPv6 or both for enabling both IPv4 and IPv6 protocols. IP address returned by the DNS server network ip dnsResolverPreference where is preferV4 for IPv4 addresses or preferV6 for IPv6 addresses. e. If you enabled the IPv4 protocol in the previous step, configure the IPv4 network parameters.
Chapter 2: Installing and Configuring the EMX Device For the static IPv4 configuration, configure these parameters. To set Static IPv4 address Use this command network ipv4 ipAddress where is the IP address you want to assign. Subnet mask network ipv4 subnetMask where is the subnet mask. Gateway network ipv4 gateway where is the IP address of the gateway.
Chapter 2: Installing and Configuring the EMX Device where
Chapter 2: Installing and Configuring the EMX Device 10. To verify whether all settings are correct, type the following commands one by one. Current network settings are displayed. Command show network Description show network ip all Show all IP configuration parameters. show network wireless details Show all wireless parameters. (Perform this command only when you enable the wireless mode.) Show network parameters.
Chapter 2: Installing and Configuring the EMX Device Combining Asset Sensors Each tag port on the asset sensors corresponds to a rack unit and can be used to locate the IT devices on a specific rack (or cabinet). For each rack, you can attach asset sensors up to 64U long, consisting of one MASTER and multiple SLAVE asset sensors. The difference between the master and slave asset sensors is that the master asset sensor has an RJ-45 connector while the slave one does not.
Chapter 2: Installing and Configuring the EMX Device Make sure that the U-shaped sheet metal adjacent to the male DIN connector is inserted into the rear slot of the master asset sensor. Screw up the U-shaped sheet metal to reinforce the connection. 2. Connect another 8U slave asset sensor to the one being attached to the master asset sensor in the same manner as Step 1. 3. Repeat the above step to connect more slave asset sensors. The length of the asset sensor assembly can be up to 64U.
Chapter 2: Installing and Configuring the EMX Device Connecting Asset Sensors to the EMX You need both asset sensors and asset tags for tracking devices. Asset tags, which are affixed to devices, provide an ID number for each device, while the asset sensors transmit ID numbers and positioning information to the connected EMX device. The following diagram illustrates an asset tag.
Chapter 2: Installing and Configuring the EMX Device Connecting an Asset Sensor to the EMX-111 The EMX-111 does not natively support the 12 volts of power needed to connect to asset management sensors via a Category 5e/6 cable. Distances greater than 1 to 10 meters require the use of a 12V Feature Port X-Cable along with a Category 5e/6 cable to connect to asset management strips.
Chapter 2: Installing and Configuring the EMX Device Diagram key EMX-111 Category 5e/6 cable (Cat5e/6 cable) 12V Feature Port X-Cable (X-cable) To connect asset sensors to the EMX-111 device: 1. Affix the adhesive end of an asset tag to each IT device through the tag's tape. 2. Plug the connector on the other end of each asset tag into the corresponding tag port on the asset sensor. 3. Connect one end of a Cat5e/6 cable to the RJ-45 connector on the MASTER asset sensor.
Chapter 2: Installing and Configuring the EMX Device Connecting an Asset Sensor to the EMX-888 The EMX-888 can connect to an asset management strip via a Category 5e/6 cable up to a distance of 10 meters. Note: The EMX-888 does not require the use of a 12V Feature Port XCable like the EMX-111.
Chapter 2: Installing and Configuring the EMX Device To connect asset sensors to the EMX-888 device: 1. Affix the adhesive end of an asset tag to each IT device through the tag's tape. 2. Plug the connector on the other end of each asset tag into the corresponding tag port on the asset sensor. 3. Connect one end of a Cat5e/6 cable to the RJ-45 connector on the MASTER asset sensor, and then connect the other end of the cable into a FEATURE port on the EMX-888. 4.
Chapter 2: Installing and Configuring the EMX Device b. Connect the other end of the cable to the FEATURE port on the EMX. 2. Affix an asset tag to the IT device and connect this asset tag to the AMS-M2-Z by plugging the tag connector into the tag port on the AMS-M2-Z. See Connecting Asset Sensors to the EMX (on page 24) for details. 3. If necessary, daisy chain multiple AMS-M2-Z to track more than two IT devices via this EMX. a. Verify that the Category 5e/6 cable length is within the limitation.
Chapter 2: Installing and Configuring the EMX Device Connecting Blade Extension Strips For blade servers, which are contained in a single chassis, you can use a blade extension strip to track individual blade servers. Raritan's blade extension strip functions similar to a Raritan asset sensor but requires a tag connector cable for connecting to a tag port on the regular asset sensor or AMS-M2-Z. The blade extension strip contains 4 to 16 tag ports, depending on which model you purchased.
Chapter 2: Installing and Configuring the EMX Device Note: Each tag port on the blade extension strip is labeled a number, which is displayed as the slot number in the EMX's web interface. To install a blade extension strip: 1. Connect the tag connector cable to the blade extension strip. Plug the cable's connector into the socket at either end of the blade extension strip. 2.
Chapter 2: Installing and Configuring the EMX Device b. Plug the tag connector of the asset tag into the tag port on the blade extension strip. 4. Repeat the above step until all blade servers in the chassis are connected to the blade extension strip via asset tags. 5. Plug the tag connector of the blade extension strip into the closest tag port of the asset sensor assembly or the AMS-M2-Z asset sensor on the rack.
Chapter 2: Installing and Configuring the EMX Device Connecting Environmental Sensors (Optional) To enable the detection of environmental factors around the EMX, connect one or more Raritan environmental sensors to the EMX device. The maximum distance for all sensor cabling plugged into the product's sensor port should not exceed 30 meters/100 feet. Contact Raritan Technical Support if you have questions. If a Raritan sensor hub is used, you can connect up to 16 environmental sensors per SENSOR port.
Chapter 2: Installing and Configuring the EMX Device Note: If you are using a 12V Feature Port X-Cable to connect an asset management sensor (AMS) to the EMX-111, the SENSOR port on the device is already being used. Plug the other end of the Raritan provided phone cable into the Sensor connector on the 12V Feature Port X-Cable instead of the SENSOR port on the EMX-111. 2. Connect Raritan environmental sensors to any of the four OUT ports on the hub.
Chapter 2: Installing and Configuring the EMX Device About Contact Closure Sensors Raritan's contact closure sensor (DPX-CC2-TR) can detect the openand-closed status of the connected detectors/switches. This feature requires the integration of at least a discrete (on/off) detector/switch to work properly.
Chapter 2: Installing and Configuring the EMX Device Connecting Detectors/Switches to DPX-CC2-TR A DPX-CC2-TR unit provides two channels for connecting two discrete (on/off) detectors/switches. There are four spring-loaded termination points on the body of DPX-CC2-TR: the two to the right are associated with one channel (as indicated by the LED number), and the two to the left are associated with the other. You must plug discrete detectors/switches into these termination points.
Chapter 2: Installing and Configuring the EMX Device Configuring a Contact Closure Sensor Before using DPX-CC2-TR to detect the contact closure status, water, smoke or vibration, you must determine the normal state by adjusting its dip switch, which controls the LED state on the body of DPX-CC2-TR. A dip switch is associated with a channel. To adjust the dip switch setting: 1. Place the detectors/switches connected to DPX-CC2-TR to the position where you want to detect a specific environmental situation.
Chapter 2: Installing and Configuring the EMX Device Note: The dip switch setting must be properly configured, or the sensor LED may be incorrectly lit in the Normal state. Connecting Third-Party Detectors/Switches to the EMX A specific EMX model (EMX2-888) provides two channels of contact closure sensor termination points, allowing for direct connection of thirdparty contact closure detectors/switches. It is not guaranteed that all third-party detectors/switches are compatible with the EMX device.
Chapter 2: Installing and Configuring the EMX Device Plug both wires of the other detector/switch into the two termination points to the right. 4. Release the tiny rectangular buttons after inserting the wires properly. 5. Verify that these wires are firmly fastened. 6. By default the open status of the detector/switch is considered normal. To set the "normal" setting to "closed" , press down the corresponding button adjacent to the termination points.
Chapter 2: Installing and Configuring the EMX Device Connecting Differential Air Pressure Sensors You can have a Raritan differential air pressure sensor connected to the EMX device if the differential air pressure data is desired. With this sensor, the temperature around the sensor can be also detected through a temperature sensor implemented inside it. Multiple differential air pressure sensors can be cascaded. To connect differential air pressure sensors: 1.
Chapter 2: Installing and Configuring the EMX Device Connecting a Logitech Webcam (Optional) The EMX supports webcams connected to it, allowing you to view video or snapshots of the area surrounding the webcam.
Chapter 2: Installing and Configuring the EMX Device To connect an LHX heat exchanger to the serial FEATURE port using a serial cable (provided by Schroff): 1. Plug DB9 end of cable into the RS232 port on the Schroff LHX heat exchanger. 2. Plug the other end of the cable into one of available serial FEATURE ports on your EMX device. See Schroff LHX Heat Exchangers (on page 192) for how to monitor and administer the heat exchanger using the EMX.
Chapter 3 Getting Started In This Chapter Supported Web Browsers........................................................................43 Connection Ports .....................................................................................43 LCD Display Panel ..................................................................................45 Reset Button ............................................................................................50 Contact Closure Sensor Termination ....................
Chapter 3: Getting Started Port Used for... FEATURE Connection to asset sensors via a Category 5e/6 cable. Note: The EMX device supplies power to the connected asset sensors after the connection is established. CONSOLE/ MODEM Establishing a serial connection between a computer and the EMX device: SENSOR Connection to Raritan's environmental sensors. This is a standard DTE RS-232 port. You can use a null-modem cable with two DB9 connectors on both ends to connect the EMX device to the computer.
Chapter 3: Getting Started LCD Display Panel The LCD display panel shows the sensor reading or status, asset management states and the device's MAC address. It consists of: An LCD display Control buttons LCD Display Different types of information are shown in different sections of the LCD display. The diagram indicates the sections.
Chapter 3: Getting Started Section Information shown Depending on your selection, the information displayed includes: The selected environmental sensor, including the sensor's ID number. The EMX shows the selected environmental sensor in two ways: For a sensor whose ID number is below 100, it is displayed as "SENSOR X" or "SENSOR XX," where X and XX are numeric digits.
Chapter 3: Getting Started Section Information shown The measurement unit for the selected environmental sensor appears. The measurement unit varies according to the sensor type: % is displayed for a humidity sensor. is displayed for a temperature sensor. When the term "ASSET" appears, the displayed information is associated with asset sensors and asset tags. Control Buttons There are four control buttons.
Chapter 3: Getting Started 2. The LCD display shows the reading or state of the selected sensor in the middle of the LCD display. For a numeric sensor's reading, the appropriate measurement unit is displayed to the right of the reading. % is displayed for a humidity sensor. is displayed for a temperature sensor. For a discrete sensor, either of the following sensor states is displayed. on: The sensor is in the abnormal state. oFF: The sensor is in the normal state.
Chapter 3: Getting Started Asset Management Information The LCD display can display the asset sensor state on each FEATURE port as well as the asset tag state of each rack unit. For the Raritan asset sensor, a rack unit refers to a tag port. To display the asset management information: 1. Press the MODE button until the term "ASSET" is displayed in the top-right corner of the LCD display. 2. Press the Up or Down button until the desired FEATURE port number is displayed in the top of the LCD display.
Chapter 3: Getting Started MAC Address The EMX's MAC address is available by operating the LCD display, and in Device mode. Contact your LAN administrator for assistance. To display the MAC address: 1. Press the MODE button until the device settings are displayed, indicated by a 'd' in at the top left of the display. 2. Press the Function button below the Mode button one time to change from the IP address to MAC address mode. The character "M" appears in the left side of the LCD display. 3.
Chapter 3: Getting Started Contact Closure Sensor Termination Two channels for connecting two third-party contact closure sensors are provided on the EMX2-888 model. For more information, see: Connecting Third-Party Detectors/Switches to the EMX (on page 38) Contact Closure Sensor LEDs (on page 39) Power Switch The power switch turns on or off the EMX device.
Chapter 3: Getting Started http(s):// where is the IP address of the EMX device. 2. If a security alert message appears, click OK or Yes to accept. The Login page then opens. 3. Type your user name in the User Name field, and password in the Password field. Note: Both the user name and password are case sensitive, so make sure you capitalize them correctly. Click Clear to clear either the inputs or any error message that appears. 4.
Chapter 3: Getting Started Choose the Refresh command or click the Refresh button on the web browser. 2. Either the login page opens or the browser is closed, depending on your choice in the previous step. Changing Your Password Normal users can change their own passwords if they have the Change Own Password permission. See Setting Up Roles (on page 69).
Chapter 3: Getting Started Introduction to the Web Interface The web interface provides two panes, a menu bar, a status bar, an Add Page icon, and a logout button throughout every page. Number Web interface element Menus EMX Explorer pane Setup button* Status bar Add Page icon Logout button Data pane * The Setup button is not available on some pages, such as the Dashboard page. For detailed information about these web interface elements, see the sections that follow.
Chapter 3: Getting Started Menus Four menus are available for managing different tasks or showing information. User Management contains menu items for managing user profiles, permissions (roles), and password. Device Settings deals with device-related settings, such as the device name, network settings, security settings, and system time. Maintenance provides tools that are helpful for maintaining the EMX, such as the event log, hardware information, firmware upgrade and so on.
Chapter 3: Getting Started Last login time: This shows the date and time this login name was used to log in to this EMX device last time. When the mouse pointer hovers over the last login time, detailed information about the last login is displayed, including the access client and IP address. For the login via a serial connection, is displayed instead of an IP address. There are different types of access clients: Web GUI: Refers to the EMX web interface.
Chapter 3: Getting Started The following diagram shows a multi-tab example. 4. With multiple pages opened, you can take these actions: To switch to one of the opened data pages, click the corresponding tab. If there are too many tabs to be all shown, two arrows ( and ) appear at the left and right borders of the pane. Click either arrow to navigate through all tabs. To close any data page, click the Close button ( corresponding tab.
Chapter 3: Getting Started Readings Highlighted in Yellow or Red When a numeric sensor's reading crosses any upper or lower threshold, the background color of the whole row turns to yellow or red for alerting users. For a discrete (on/off) sensor, the row changes the background color when the sensor enters the abnormal state.
Chapter 3: Getting Started To find the exact meaning of the alert, read the information shown in the State (or Status) column: below lower critical: The numeric sensor's reading drops below the lower critical threshold. below lower warning: The numeric sensor's reading drops below the lower warning threshold. above upper critical: The numeric sensor's reading reaches or exceeds the upper critical threshold.
Chapter 3: Getting Started Browser-Defined Shortcut Menu A shortcut menu, which is built in the web browser, may appear when right-clicking anywhere in the EMX web interface. The shortcut menu functions are defined by the browser. For example, the Back command on the Internet Explorer® (IE) shortcut menu works the same as the Back button in the IE browser. Both of these functions take you to the previous page.
Chapter 3: Getting Started Viewing the Dashboard When you log in to the web interface, the Dashboard page is displayed by default. This page provides an overview of the EMX device's status. The page is divided into several sections according to connected equipment, such as asset sensors and environmental sensors. Doubleclicking any item on the Dashboard page opens the data page specific to the selected item.
Chapter 4 User and Role Management In This Chapter Overview ..................................................................................................62 Managing Users ......................................................................................62 Managing Roles .......................................................................................69 Overview The EMX is shipped with one built-in user profile: admin, which is used for initial login and configuration.
Chapter 4: User and Role Management Field Type this... Spaces are NOT permitted Full Name The user's first and last names. Password, The password the user enters to log in. Type it first in the Password field and then again in the Confirm Password field. Confirm Password The password can be 4 to 32 characters long. It is case sensitive. Spaces are permitted. Telephone Number A phone number where the user can be reached. eMail Address An email address where the user can be reached.
Chapter 4: User and Role Management Field Description is the default. Use Password as Authentication Pass Phrase This checkbox is configurable only if AuthNoPriv or AuthPriv is selected. Authentication Pass Phrase Type the authentication pass phrase in this field if the "Use Password as Authentication Pass Phrase" checkbox is disabled. When the checkbox is selected, the authentication pass phrase is identical to the user's password.
Chapter 4: User and Role Management 7. Click the SSH tab to enter the public key if the public key authentication for the SSH service is enabled. See Changing the SSH Settings (on page 90). a. Open the SSH public key with a text editor. b. Copy and paste all contents in the text editor into the Public Key field on the SSH tab. 8. Click the Roles tab to determine the permissions of the user. 9. Select one or multiple roles by selecting corresponding checkboxes. The Admin role provides full permissions.
Chapter 4: User and Role Management Modifying a User Profile You can change any user profile's information except for the user name. To modify a user profile: 1. Choose User Management > Users. The Manage Users dialog appears. 2. Select the user by clicking it. 3. Click Edit or double-click the user. The Edit User 'XXX' dialog appears, where XXX is the user name. 4. Make all necessary changes to the information shown. To change the password, type a new password in the Password and Confirm Password fields.
Chapter 4: User and Role Management 4. A message appears, prompting you to confirm the operation. Click Yes to confirm the deletion. Setting Up User Preferences (Units of Measure) The units of measure used in your EMX GUI can be changed as needed. Note: Changing your preferences does not change the EMX device display. See Setting Up Default User Preferences (Units of Measure) (on page 67) for information on changing the device display. To change your EMX GUI units of measure: 1.
Chapter 4: User and Role Management In the Temperature Unit field, select (Celsius) or (Fahrenheit) as the measurement unit for temperatures. In the Length Unit field, select "Meter" or "Feet" as the measurement unit for length or height. In the Pressure Unit field, select "Pascal" or "psi" as the measurement unit for pressure. 3. Click OK. Changing the User List View You may change the number of displayed columns or re-sort the list for better viewing the data.
Chapter 4: User and Role Management b. Click Yes to disconnect the user or No to abort the operation. If clicking Yes, the connected user is forced to log out. You may change the sorting order of the list if necessary. 3. Click Close to quit the dialog. Managing Roles Setting Up Roles To manage any settings, you must log in to the user account with appropriate permissions. A role defines the operations and functions a user is permitted to perform or access. Every user must be assigned at least a role.
Chapter 4: User and Role Management a. Click Add. The "Add Privileges to new Role" dialog appears. b. Select the permission you want from the Privileges list. c. If the permission you selected contains any argument setting, the Arguments list is shown to the right. Then select one or multiple arguments. d. Click Add to add the selected permission (and arguments if any). e. Repeat Steps a to d until you add all necessary permissions. 6. Click OK to save the changes.
Chapter 4: User and Role Management c. If the permission you selected contains any argument setting, the Arguments list is shown to the right. Then select one or multiple arguments. d. Click Add to add the selected permission (and arguments if any). e. Repeat Steps a to d until you add all necessary permissions. 8. To change a specific permission's arguments, do this: a. Select the permission by clicking it. b. Click Edit.
Chapter 5 EMX Device Management In This Chapter Overview ..................................................................................................72 Naming the EMX Device .........................................................................72 Displaying the Device Information ...........................................................73 Setting the Date and Time .......................................................................73 Specifying the Device Altitude ...........................
Chapter 5: EMX Device Management 4. Click OK to save the changes. Displaying the Device Information The Device Information dialog displays information specific to the EMX device that you are accessing, such as IDs and protocol versions of asset sensors. To display the device information: 1. Choose Maintenance > Device Information. The Device Information dialog appears. 2. Click the tab containing the information you want to view.
Chapter 5: EMX Device Management To customize the date and time, select the User Specified Time radio button, and then enter the date and time in appropriate fields. Use the yyyy-mm-dd format for the date and the hh:mm:ss format for the time. To set the date, delete existing numbers in the Date field and type new ones, or click the calendar icon to select a date. The time is measured in 24-hour format so enter 13 for 1:00pm, 14 for 2:00pm, and so on.
Chapter 5: EMX Device Management Note: The EMX folder is named "EMX" by default. The name changes after customizing the device name. See Naming the EMX Device (on page 72). 2. Click Setup on the Settings page. The EMX Setup dialog appears. 3. Type an integer number in the Altitude field. Depending on the measurement unit displayed, the range of valid numbers differs. For meters (m), the value ranges between 0 and 3000. For feet (ft), the value ranges between 0 and 9842. 4.
Chapter 5: EMX Device Management 5. To change the temperature unit, select the desired option in the Temperature Unit field. : This option displays the temperature in Celsius. : This option displays the temperature in Fahrenheit. 6. To change the length or height unit, select the desired option in the Length Unit field. Meter: This option displays the length or height in meters. Feet: This option displays the length or height in feet. 7.
Chapter 5: EMX Device Management Disabled: When applied, disables to port and nothing connected to the port is detected. Auto: An icon is displayed for this port only when the EMX device detects the physical connection of the asset sensor on this port. Otherwise, nothing is displayed. This is the default approach. Pinned: An icon is displayed for this port all the time, but the icon image varies according to the connection status.
Chapter 5: EMX Device Management Auto: An icon is displayed for this port only when the EMX device detects the physical connection of the LHX heat exchanger on this port. Otherwise, nothing is displayed. This is the default approach. Pinned: An icon is displayed for this port all the time, but the icon image varies according to the connection status. See Device States and Icon Variations (on page 196).
Chapter 5: EMX Device Management 4. To change the LAN speed, click the drop-down arrow in the Speed field and select an option from the list. Auto: System determines the optimum LAN speed through autonegotiation. 10 Mbit/s: The LAN speed is always 10 Mbps. 100 Mbit/s: The LAN speed is always 100 Mbps. 5. To change the duplex mode, click the drop-down arrow in the Duplex field and select an option from the list. Auto: The EMX selects the optimum transmission mode through auto-negotiation.
Chapter 5: EMX Device Management 7. In the Authentication field, click the drop-down arrow, and select an appropriate option from the list. Option Description No Authentication Select this option when no authentication data is required. PSK A Pre-Shared Key is required for this option. In the Pre-Shared Key field, type the PSK string. EAP - PEAP PEAP stands for Protected Extensible Authentication Protocol.
Chapter 5: EMX Device Management Selecting the Internet Protocol The EMX device supports two types of Internet protocols -- IPv4 and IPv6. You can enable either or both Internet protocols. After enabling the desired Internet protocol(s), all but not limited to the following protocols will be compliant with the enabled Internet protocol(s): LDAP NTP SMTP SSH Telnet FTP SSL SNMP SysLog To select the appropriate Internet Protocol: 1. Choose Device Settings > Network.
Chapter 5: EMX Device Management Modifying the IPv4 Settings You must enable the IPv4 protocol before you can modify the IPv4 network settings. See Selecting the Internet Protocol (on page 81). To modify the IPv4 settings: 1. Choose Device Settings > Network. The Network Configuration dialog appears. 2. Click the IPv4 Settings tab. 3. In the IP Auto Configuration field, click the drop-down arrow, and select the desired option from the list.
Chapter 5: EMX Device Management Note: The EMX supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the EMX only uses the primary IPv4 and IPv6 DNS servers. Modifying the IPv6 Settings You must enable the IPv6 protocol before you can modify the IPv6 network settings. See Selecting the Internet Protocol (on page 81). To modify the IPv6 settings: 1. Choose Device Settings > Network. The Network Configuration dialog appears. 2. Click the IPv6 Settings tab. 3.
Chapter 5: EMX Device Management Note: The EMX supports a maximum of 3 DNS servers. If two IPv4 DNS servers and two IPv6 DNS servers are available, the EMX only uses the primary IPv4 and IPv6 DNS servers. Role of a DNS Server As Internet communications are carried out on the basis of IP addresses, appropriate DNS server settings are required for mapping domain names (host names) to corresponding IP addresses, or the EMX may fail to connect to the given host.
Chapter 5: EMX Device Management 2. To use a different port for HTTP or HTTPS, type a new port number in the corresponding field. Valid range is 1 to 65535. Warning: Different network services cannot share the same TCP port. 3. Click OK to save the changes. Configuring the SNMP Settings, Traps and Informs SNMP communications allow you to retrieve the status of the EMX device.
Chapter 5: EMX Device Management 3. Select the "enable" checkbox in the "SNMP v1 / v2c" field to enable communication with an SNMP manager using SNMP v1 or v2c protocol. Type the SNMP read-only community string in the Read Community String field. Usually the string is "public." Type the read/write community string in the Write Community String field. Usually the string is "private." 4.
Chapter 5: EMX Device Management 7. Click OK, or continue to the Notifications tab create SNMP TRAP or INFORM communications.
Chapter 5: EMX Device Management 8. To create an SNMP TRAP or INFORM communication, open the Notifications tab on the SNMP Settings dialog. 9. Select the Enabled checkbox to enable the feature. For SNMPv2/c TRAP and INFORM notifications: 1. From the Notification Type drop-down, select the type of SNMP notification. 2. For SNMP INFORM communications, leave the resend settings at their default or: a.
Chapter 5: EMX Device Management 5. In the Community fields, enter the SNMP community string to access the device(s). The community is the group representing the EMX and all SNMP management stations. 6. Click OK. For SNMPv3 TRAP and INFORM notifications: 1. On the Notifications tab, select the Enable checkbox to enable the SNMP notification feature. 2. From the Notification Type drop-down, select the type of SNMP notification. 3. For SNMP TRAPs, the engine ID is prepopulated. 4.
Chapter 5: EMX Device Management Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" "authPriv" Click OK Select this if authorization is required but no privacy protocols are required. Select the authentication protocol - MD5 or SHA Enter the authentication passphrase and then confirm the authentication passphrase Click OK Select this if authentication and privacy protocols are required.
Chapter 5: EMX Device Management Allow password authentication only: Enables the passwordbased login only. Allow public key authentication only: Enables the public keybased login only. Allow password and public key authentication: Enables both the password- and public key-based login. This is the default. 5. Click OK to save the changes. If the public key authentication is selected, you must type a valid SSH public key for each user profile to log in over the SSH connection.
Chapter 5: EMX Device Management Enabling Service Advertisement The EMX advertises all enabled services that are reachable using the IP network. This feature uses DNS-SD (Domain Name System-Service Discovery) and mDNS (multicast DNS). The advertised services are discovered by clients that have implemented DNS-SD and mDNS. The advertised services include the following: HTTP HTTPS Telnet SSH Modbus json-rpc SNMP This feature is enabled by default.
Chapter 5: EMX Device Management 2. Type the name or IP address of the mail server in the Server Name field. 3. Type the port number for the SMTP server in the Port field. The default is 25. 4. Type an email address for the sender in the Sender Email Address field. 5. Type the number of email retries in the Number of Sending Retries field. The default is 2 retries. 6. Type the time interval between email retries in the "Time Interval Between Sending Retries (in minutes)" field.
Chapter 5: EMX Device Management Setting Up an EMX Using Bulk Configuration Use this feature if you have already set up an EMX and are now setting up another. The Bulk Configuration feature lets you save the settings of a configured EMX device to your PC. You can use this configuration file to: Copy that configuration to other EMX devices of the same model and firmware version. Restore the settings of the same EMX device to previous configuration.
Chapter 5: EMX Device Management Saving an EMX Configuration A source device is an already configured EMX device that is used to create a configuration file containing the settings that can be shared between EMX devices. These settings include user and role configurations, event rules, security settings, and so on.
Chapter 5: EMX Device Management Copying a EMX Configuration A target device is an EMX device that loads another EMX device's configuration file. Copying an EMX configuration to a target device adjusts that EMX device's settings to match those of the source EMX device. In order to successfully copy an EMX configuration: The user must be the Admin user. Or the Admin role is assigned to the user. The target EMX device must be of the same model type as the source EMX device.
Chapter 5: EMX Device Management The file is saved in the XML format, and its content is encrypted using the AES-128 encryption algorithm. To restore the EMX using a backup XML file: 1. Choose Maintenance > Backup/Restore. The Backup/Restore of Device Settings dialog opens. 2. In the Copy Device Settings section, click Browse to locate the file. 3. Click Upload & Restore Device Settings to upload the file. A message appears, prompting you to confirm the operation and enter the admin password. 4.
Chapter 5: EMX Device Management 5. To view the certificate of the uploaded firmware, click View Certificate. Optional. 6. To proceed with the update, click Update Firmware. The update may take several minutes. Warning: Do NOT power off the EMX device during the update. During the firmware update: A progress bar appears in the web interface, indicating the update status. No users can successfully log in to the EMX.
Chapter 5: EMX Device Management Firmware upgrade result 2. You may change the number of displayed columns or re-sort the list for better viewing the data. 3. To view the details of any firmware upgrade event, select it and click Details, or simply double-click the event. The Firmware Update Details dialog appears, showing detailed information of the selected event. 4. Click Close to quit the dialog.
Chapter 5: EMX Device Management Pinging a Host The Ping tool is useful for checking whether a host is accessible through the network or Internet. To ping a host: 1. Choose Maintenance > Network Diagnostics > Ping. The Ping Network Host dialog appears. 2. In the Host Name field, type the name or IP address of the host that you want to check. 3. In the Number of Requests field, type a number up to 10 or adjust the value by clicking either arrow.
Chapter 5: EMX Device Management when you are directed by Raritan Technical Support. You can download the diagnostic file from the EMX device to a client machine. The file is compressed into a .tgz file and should be sent to Raritan Technical Support for interpretation. This feature is accessible only by users with Administrative Privileges. To retrieve a diagnostic file: 1. Choose Maintenance > Download Diagnostic Information. The File Download dialog appears. 2. Click Save. The Save As dialog appears.
Chapter 5: EMX Device Management Rebooting the EMX You can remotely reboot the EMX device via the web interface. Rebooting the EMX does not reset the configuration of the device as is done during a factory reset. Note: Rebooting the EMX deletes the snapshots taken via webcam. To reboot the device: 1. Choose Maintenance > Unit Reset. The Reset Device dialog appears. 2. Click Yes to reset the EMX. 3. A message appears with a countdown timer showing the remaining time of the operation.
Chapter 5: EMX Device Management 2. Launch a terminal emulation program such as HyperTerminal, Kermit, or PuTTY, and open a window on the EMX. 3. Press (and release) the Reset button of the EMX device while pressing the Esc key of the keyboard several times in rapid succession. A prompt (=>) should appear after about one second. 4. Type defaults to reset the EMX to its factory defaults. 5. Wait until the Username prompt appears, indicating the reset is complete.
Chapter 6 Security In This Chapter Access Security Control ........................................................................104 Setting Up an SSL Certificate ................................................................118 Setting Up LDAP Authentication ...........................................................123 Enabling and Editing the Security Banner (Restrictive Service Agreement Banner) ..................................................................................................
Chapter 6: Security Configuring the Firewall The EMX has a firewall that you can configure to prevent specific IP addresses and ranges of IP addresses from accessing the EMX device. By default the firewall is disabled. To configure the firewall: 1. Enable the firewall. See Enabling the Firewall (on page 105). 2. Set the default policy. See Changing the Default Policy (on page 105). 3. Create firewall rules specifying which addresses to accept and which ones to discard.
Chapter 6: Security a. Click the IPv4 tab if necessary. b. Ensure the Enable IPv4 Access Control checkbox is selected. c. The default policy is shown in the Default Policy field. To change it, select a different policy from the drop-down list. Accept: Accepts traffic from all IPv4 addresses. Drop: Discards traffic from all IPv4 addresses, without sending any failure notification to the source host.
Chapter 6: Security To specify an entire subnet or range of addresses, change the subnet mask accordingly. Note: Valid IP addresses range from 0.0.0.0 through 255.255.255.255. Make sure the IP addresses entered are within the scope. To create firewall rules: 1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears. 2. Click the IPv4 tab for creating firewall rules, or click the IPv6 tab for creating IPv6 firewall rules. 3.
Chapter 6: Security Action Procedure Insert a rule between two existing 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. The "Insert new Rule" dialog appears. Type an IP address and subnet mask in the IP/Mask field. Select Accept, Drop or Reject from the drop-down list in the Policy field. Accept: Accepts traffic from the specified IP address(es).
Chapter 6: Security Editing Firewall Rules When an existing firewall rule requires updates of IP address range and/or policy, modify them accordingly. To modify a firewall rule: 1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears. 2. To modify the IPv4 firewall rules, click the IPv4 tab. To modify the IPv6 firewall rules, click the IPv6 tab. 3.
Chapter 6: Security Deleting Firewall Rules When any firewall rules become obsolete or unnecessary, remove them from the rules list. To delete a firewall rule: 1. Choose Device Settings > Security > IP Access Control. The Configure IP Access Control Settings dialog appears. 2. To delete the IPv4 firewall rules, click the IPv4 tab. To delete the IPv6 firewall rules, click the IPv6 tab. 3.
Chapter 6: Security 3. To enable the user blocking feature, select the "Block user on login failure" checkbox. 4. Type a number in the "Maximum number of failed logins" field. This is the maximum number of failed logins the user is permitted before the user's login is blocked from accessing the EMX device. 5. To determine how long the login is blocked, select the desired length of time from the drop-down list in the "Block timeout" field. The following describes available options.
Chapter 6: Security Tip: If the desired time option is not listed, you can manually type the desired time in this field. For example, you can type "4 min" to set the time to 4 minutes. 5. Click OK to save the changes. Tip: Keep the idle timeout to 20 minutes or less if possible. This reduces the number of idle sessions connected, and the number of simultaneous commands sent to the EMX.
Chapter 6: Security Enabling Password Aging Password Aging determines whether users are required to change passwords at regular intervals. The default interval is 60 days. To force users to change passwords regularly: 1. Choose Device Settings > Security > Password Policy. The Password Policy dialog appears. 2. Select the Password Aging checkbox to enable the password aging feature. 3.
Chapter 6: Security 2. To enable the IPv4 firewall, click the IPv4 tab, and select the Enable Role Based Access Control for IPv4 checkbox. 3. To enable the IPv6 firewall, click the IPv6 tab, and select the Enable Role Based Access Control for IPv6 checkbox. 4. Click OK to save the changes. Changing the Default Policy The default policy is to accept all traffic from all IP addresses regardless of the role applied to the user. To change the default policy: 1.
Chapter 6: Security Creating Role-Based Access Control Rules Role-based access control rules accept or drop traffic, based on the user's role and IP address. Like firewall rules, the order of rules is important, since the rules are executed in numerical order. To create role-based access control rules: 1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears. 2.
Chapter 6: Security Action Do this... Type an ending IP address in the Ending IP Address field. Select a role from the drop-down list in the Role field. This rule applies to members of this role only. Select Allow or Deny from the drop-down list in the Policy field.
Chapter 6: Security Sorting Role-Based Access Control Rules Similar to firewall rules, the order of role-based access control rules determines which one of the rules matching the same IP address is performed. To sort role-based access control rules: 1. Choose Device Settings > Security > Role Based Access Control. The Configure Role Based Access Control Settings dialog appears. 2. To sort the IPv4 firewall rules, click the IPv4 tab. To sort the IPv6 firewall rules, click the IPv6 tab. 3.
Chapter 6: Security Setting Up an SSL Certificate Having an X.509 digital certificate ensures that both parties in an SSL connection are who they say they are. To obtain a certificate for the EMX, create a Certificate Signing Request (CSR) and submit it to a certificate authority (CA). After the CA processes the information in the CSR, it provides you with an SSL certificate, which you must install on the EMX device.
Chapter 6: Security Field Type this information Organization The registered name of your company. Organizational Unit The name of your department. Common Name The fully qualified domain name (FQDN) of your EMX device. Email Address An email address where you or another administrative user can be reached. Note: All fields in the Subject section are mandatory, except for the Organization, Organizational Unit and Email Address fields.
Chapter 6: Security Installing a CA-Signed Certificate After the CA provides a signed certificate according to the CSR you submitted, you must install it on the EMX device. To install the certificate: 1. Choose Device Settings > Security > SSL Certificate. The Manage SSL Certificate dialog appears. 2. Click the New SSL Certificate tab. 3. In the Certificate File field, click Browse to select the certificate file provided by the CA. 4. Click Upload. The certificate is installed on the EMX device.
Chapter 6: Security Field Type this information Key Length Select the key length (bits) from the drop-down list in this field. A larger key length enhances the security, but slows down the EMX device's response. Self Sign Ensure this checkbox is selected, which indicates that you are creating a self-signed certificate. Validity in days This field appears after the Self Sign checkbox is selected. Type the number of days for which the self-signed certificate is valid in this field.
Chapter 6: Security Installing Existing Key and Certificate Files If the SSL certificate and private key files are already available, you can install them directly without going through the process of creating a CSR or a self-signed certificate. Note: If you are using a SSL certificate that is part of a chain of certificates, each part of the chain is signed during the validation process.
Chapter 6: Security Setting Up LDAP Authentication For security purposes, users attempting to log in to the EMX must be authenticated. The EMX supports the access using one of the following authentication mechanisms: Local database of user profiles on the EMX device Lightweight Directory Access Protocol (LDAP) By default, the EMX is configured for local authentication. If you stay with this method, you do not need to do anything other than create user profiles for each authorized user.
Chapter 6: Security If using a Microsoft Active Directory server, consult your AD administrator for the name of the Active Directory Domain.
Chapter 6: Security 8. SSL Port - The default is 636. Either use the default port or specify another port. This field is enabled when the "LDAP over SSL" checkbox is selected. 9. Use only trusted LDAP Server Certificates - Select this checkbox if you would like to use a trusted LDAP server certificate file, that is, a certificate file signed by the CA. When NOT selected, you can use all LDAP/LDAPS server certificates, including a self-signed certificate file.
Chapter 6: Security Login name attribute (also called AuthorizationString) User entry object class User search subfilter (also called BaseSearch) Note: The EMX will preoccupy the login name attribute and user entry object class with default values, which should not be changed unless required. 17. Active Directory Domain - Type the name of the Active Directory Domain. For example, testradius.com. Consult with your Active Directory Administrator for a specific domain name. 18.
Chapter 6: Security Sorting the LDAP Access Order The order of the LDAP list determines the access priority of remote LDAP/LDAPS servers. The EMX first tries to access the top LDAP/LDAPS server in the list for authentication, then the next one if the access to the first one fails, and so on until the EMX device successfully connects to one of the listed LDAP/LDAPS servers.
Chapter 6: Security 5. Click OK to save the changes. Deleting the LDAP Server Settings You can delete the authentication settings of a specific LDAP/LDAPS server when the server is not available or used for remote authentication. To remove one or multiple LDAP/LDAPS servers: 1. Choose Device Settings > Security > Authentication. The Authentication Settings dialog appears. 2. Select the LDAP/LDAPS server that you want to remove.
Chapter 6: Security Enabling LDAP and Local Authentication Services To make authentication function properly all the time -- even when external authentication is not available, you can enable both the local and remote authentication services. When both authentication services are enabled, the EMX follows these rules for authentication: When any of the LDAP/LDAPS servers in the access list is accessible, the EMX authenticates against the connected LDAP/LDAPS server only.
Chapter 6: Security 4. Click OK.
Chapter 7 Event Rules, Event Actions and Application Logs In This Chapter Event Rules and Actions .......................................................................131 Event Logging ........................................................................................158 Viewing the Communication Log ...........................................................160 Event Rules and Actions A benefit of the product's intelligence is its ability to notify you of and react to a change in conditions.
Chapter 7: Event Rules, Event Actions and Application Logs Creating an Event Rule The best way to create a new set of event rule, in sequence, is: Create actions for responding to one or multiple events Create rules to determine what actions are taken when these events occur Creating Rules After required actions are available, you can create event rules to determine what actions are taken to respond to specific events.
Chapter 7: Event Rules, Event Actions and Application Logs Event types Radio buttons Numeric sensor threshold-crossing events, or the occurrence of the selected event -true or false Available radio buttons include "Asserted," "Deasserted" and "Both." Asserted: The EMX takes the action only when the event occurs. This means the status of the described event transits from FALSE to TRUE. Deasserted: The EMX takes the action only when the event condition disappears.
Chapter 7: Event Rules, Event Actions and Application Logs Event types Radio buttons Network interface link state Available radio buttons include "Link state is up," "Link state is down" and "Both." Link state is up: The EMX takes the action only when the network link state changes from down to up. Link state is down: The EMX takes the action only when the network link state changes from up to down. Both: The EMX takes the action whenever the network link state changes.
Chapter 7: Event Rules, Event Actions and Application Logs Event types Radio buttons Server reachability Available radio buttons include "Unreachable," "Reachable," and "Both." 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 when any specified server becomes either inaccessible or accessible. 1.
Chapter 7: Event Rules, Event Actions and Application Logs Creating Actions The EMX comes with two built-in actions: System Event Log Action: This action records the selected event in the internal log when the event occurs. System SNMP Notification Action: This action sends SNMP notifications to one or multiple IP addresses after the selected event occurs.
Chapter 7: Event Rules, Event Actions and Application Logs Log an Event Message This option records the selected events in the internal log. To create a log event message: 1. Choose Device Settings > Event Rules. The Event Rules Settings dialog opens. 2. Click the Actions tab. 3. Click New. 4. In the "Action name" field, type a new name for the action. The default name is New Action , where is a sequential number based on how many actions are already created. 5.
Chapter 7: Event Rules, Event Actions and Application Logs 10. Use the slide bars to increase or decrease the following: Number of Snapshots - the number of snapshots to be included in the sequence of images that are taken when the event occurs. For example, you can specify 10 images be taken once the event triggers the action. Snapshots/Mail field - the number of snapshots from the sequence to be sent at one time in the email.
Chapter 7: Event Rules, Event Actions and Application Logs 6. In the "Recipients email addresses" field, specify the email address(es) of the recipient(s). Use a comma to separate multiple email addresses. 7. To use the SMTP server specified in the SMTP Server Settings dialog, select the Use Default SMTP Server checkbox. To use a different SMTP server, select the Use Custom SMTP Settings checkbox. If the SMTP server settings are not configured yet, click Configure.
Chapter 7: Event Rules, Event Actions and Application Logs a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received. For example, resend a new inform communication once every 3 seconds. b. In the Number of Retries field, enter the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails. 3.
Chapter 7: Event Rules, Event Actions and Application Logs Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" "authPriv" Click OK Select this if authorization is required but no privacy protocols are required. Select the authentication protocol - MD5 or SHA Enter the authentication passphrase and then confirm the authentication passphrase Click OK Select this if authentication and privacy protocols are required.
Chapter 7: Event Rules, Event Actions and Application Logs 7. In the Port field, specify an appropriate port number. 8. Click OK to save the new action. 9. Click Close to quit the dialog. Send SMS Message 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.
Chapter 7: Event Rules, Event Actions and Application Logs Click the Information icon to open the Event Context Information dialog, which contains a list of placeholders and their definitions. See Email and SMS Message Placeholders (on page 145) for more details. Note: Only English is supported for SMS messages. For Turkish characters, use 7-bit ASCII instead. 8. Click OK to save the new action. 9. Click Close to quit the dialog. Switch LHX If Schroff LHX Support is enabled, this option is available.
Chapter 7: Event Rules, Event Actions and Application Logs 3. Click New. 4. In the "Action name" field, type a new name for the action. The default name is New Action , where is a sequential number based on how many actions are already created. 5. In the Action field, click the drop-down arrow and select the desired action from the list. 6. Select a webcam from the Webcam drop-down. 7. Selecting the action to perform - Start Recording or Stop Recording. 8.
Chapter 7: Event Rules, Event Actions and Application Logs Email and SMS Message Placeholders Following are placeholders that can be used in custom event email messages. Note: Click the Information icon to open the Event Context Information dialog, which contains a list of placeholders and their definitions. Note: The LHX placeholders are only available when the Schroff LHX Support feature is enabled.
Chapter 7: Event Rules, Event Actions and Application Logs 146 Placeholder Description [CONFIGVALUE] The new value of a parameter [DATETIME] The human readable timestamp of the event occurrence [DEVICEIP] The IP address of the device, the event occurred on. [DEVICENAME] The name of the device, the event occurred on [EXTSENSORCHANNEL] The channel of an external sensor (e.g.
Chapter 7: Event Rules, Event Actions and Application Logs Placeholder Description [LHXSUPPORTENABLED] The Schroff LHX Support state [MONITOREDHOST] The name or IP address of a monitored host [OLDSENSORSTATE] The numeric ID of the previous sensor state [OLDVERSION] The firmware version the device is being upgraded from [OUTLETPOLE] The outlet power line identifier [OUTLETSENSOR] The outlet sensor name [PDUPOLESENSOR] The sensor name for a certain power line [PLSENSOR] The Power Logic Devic
Chapter 7: Event Rules, Event Actions and Application Logs Placeholder Description [UMTARGETUSER] The user, an action was triggered for [USERIP] The IP address, a user connected from [USERNAME] The user who triggered an action [VERSION] The firmware version the device is upgrading to [WIRESENSOR] The wire sensor name Default Log Messages Following are default log messages triggered and emailed to specified recipients when EMX events occur (are TRUE) or, in some cases, do not occur (are FALSE).
Chapter 7: Event Rules, Event Actions and Application Logs Event/Context Default Assertion Message when the Event = TRUE Default Assertion Message when the Event = FALSE* Device > Event log cleared Event log cleared by user '[USERNAME]' from host '[USERIP]'. Device > Bulk configuration saved Bulk configuration saved from host '[USERIP]'. Device > Bulk configuration copied Bulk configuration copied from host '[USERIP]'.
Chapter 7: Event Rules, Event Actions and Application Logs Event/Context in Default Assertion Message when the Event = TRUE '[USERIP]' logged in. User Activity > * > Authentication failure Authentication failed for user '[USERNAME]' from host '[USERIP]'. Default Assertion Message when the Event = FALSE* '[USERIP]' logged out. User Activity > * > User blocked User '[USERNAME]' from host '[USERIP]' was blocked.
Chapter 7: Event Rules, Event Actions and Application Logs Event/Context Default Assertion Message when the Event = TRUE alarmed. Default Assertion Message when the Event = FALSE* '[EXTSENSORSLOT]' is no longer alarmed. Server Monitoring > * > Monitored Server '[SERVER]' is now being monitored. Server '[SERVER]' is no longer being monitored. Server Monitoring > * > Unreachable Server '[SERVER]' is unreachable. Server '[SERVER]' is reachable.
Chapter 7: Event Rules, Event Actions and Application Logs Event/Context Default Assertion Message when the Event = TRUE Default Assertion Message when the Event = FALSE* LHX > Sensor > Unavailable Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' unavailable. Sensor '[LHXSENSORID]' on LHX at [PORTTYPE] port '[PORTID]' available.
Chapter 7: Event Rules, Event Actions and Application Logs Event/Context Default Assertion Message when the Event = TRUE LHX at [PORTTYPE] port '[PORTID]' at power supply '[LHXPOWERSUPPLYID]'. Default Assertion Message when the Event = FALSE* LHX > Threshold Humidity Auxiliary Port 2 The humidity threshold on LHX at [PORTTYPE] port '[PORTID]' was crossed. The humidity on LHX at [PORTTYPE] port '[PORTID]' is within thresholds.
Chapter 7: Event Rules, Event Actions and Application Logs Event/Context Default Assertion Message when the Event = TRUE Default Assertion Message when the Event = FALSE* Power Logic Device > * > Sensor > * > Below lower critical threshold Sensor '[PLSENSORNAME]' on Power Logic Device at [PORTTYPE] port '[PORTID]' asserted 'below lower critical' at [SENSORREADING] [SENSORREADINGUNIT].
Chapter 7: Event Rules, Event Actions and Application Logs 5. Select "System Event Log Action" as we intend to record this event in the internal log when the specified events occur. Sample Sensor-Level Event Rule In this example, we want the EMX device to send SNMP traps to the SNMP manager when the reading of the temperature sensor connected to the sensor port #1 crosses any threshold or when the sensor is unavailable.
Chapter 7: Event Rules, Event Actions and Application Logs 4. Select "" because we want to specify all events related to the sensor connected to sensor port #1, including the sensor's unavailable state and threshold-crossing events -- "Above upper critical, "Above upper warning," "Below lower warning," and "Below lower critical." 5. Select "System SNMP Notification Action" as we want to send SNMP traps to respond to the specified events when these events occur.
Chapter 7: Event Rules, Event Actions and Application Logs 4. To change the event, click the desired tab in the Event field and select a different item from the pull-down menu or submenu. For example, in a user activity event rule for the "admin" user, you can click the "admin" tab to display a pull-down submenu showing all user names, and then select a different user name or all user names (referred to as ). 5.
Chapter 7: Event Rules, Event Actions and Application Logs Note: If you do not click Save before quitting the current settings page, a message appears. Then click Yes to save the changes, Discard to abort the changes or Cancel to return to the current settings page. 6. Click Close to quit the dialog. Deleting an Event Rule or Action If any event rule or action is obsolete, simply remove it. Note: You cannot delete the built-in event rules and actions. To delete an event rule or action: 1.
Chapter 7: Event Rules, Event Actions and Application Logs Viewing the Local Event Log You can view up to 2,000 historical events that occurred to the EMX device in the local event log. When the log already contains 2,000 entries, each new entry overwrites the oldest entry. To display the local log: 1. Choose Maintenance > View Event Log. The Event Log dialog appears.
Chapter 7: Event Rules, Event Actions and Application Logs 2. Click Clear Event Log. 3. Click Close to quit the dialog. Viewing the Communication Log The EMX allows you to inspect all communications occurred between the EMX device and its graphical user interface (GUI). The information is usually useful for a technical support engineer only and you may not need to view it. This feature is accessible only by users with Administrative Privileges. To view the communication log: 1.
Chapter 8 Managing External Devices In This Chapter Overview ................................................................................................161 EMX and PX2 PDU Cascading Connections ........................................162 Server Accessibility ...............................................................................164 Configuring the Serial Port ....................................................................169 Environmental Sensors .........................................
Chapter 8: Managing External Devices EMX and PX2 PDU Cascading Connections Up to four (4) devices are supported as part of a daisy chain. Specifically, a EMX can have up to three (3) additional EMXs connected to it, or up to three (3) PX2 devices connected to it. Note: For help on setting up and configuring PX2 devices, see the PX2 Help for additional information.
Chapter 8: Managing External Devices Cascading EMX Devices Note: When cascading devices, use a wired network connection. Wireless connections are not supported when cascading devices. To connect EMX devices to an EMX device: 1. If needed, upgrade the EMX firmware of each device that will be part of the chain. 2. Plug a USB cable into the USB-B port on the slave EMX, and connect it to the USB-A port on the master EMX. 3.
Chapter 8: Managing External Devices 3. If you are adding an additional PX2 to the chain, plug a USB cable into USB-B port on the additional PX, then plug the other end into USB-A on the PX2 that is already connected to the master EMX. Up to three (3) PX2s can be connected to the master EMX. Server Accessibility You can monitor whether specific IT devices are alive by having the EMX device continuously ping them.
Chapter 8: Managing External Devices Adding IT Devices for Ping Monitoring You can have the EMX monitor the accessibility of any IT equipment, such as DB servers, remote authentication servers or any power distribution unit (PDU). The EMX supports monitoring a maximum of 8 devices. The default ping settings may not be suitable for monitoring devices that require high connection reliability so it is strongly recommended that you should adjust the ping settings to meet your own needs.
Chapter 8: Managing External Devices Field Description Wait Time (in seconds) before Resuming Pinging The wait time before the EMX resumes pinging after the monitored equipment is declared unreachable. Valid range is 1 to 1200 (seconds). 5. Click OK to save the changes. 6. To add more IT devices, repeat Steps 2 to 5. 7. Click Close to quit the dialog.
Chapter 8: Managing External Devices 5. In the Wait Time (in seconds) before Resuming Pinging field, type 60 to make the EMX stops pinging the target PDU for 60 seconds (1 minute) after the PDU inaccessibility is declared. After 60 seconds, the EMX will re-ping the target PDU. Step 2: Create an event rule to send SNMP notifications for this PDU 1. Choose Device Settings > Event Rules. The Event Rule Settings dialog appears. 2. Click New. 3.
Chapter 8: Managing External Devices Deleting Ping Monitoring Settings When it is not necessary to monitor the accessibility of any IT device, just remove it. To delete ping monitoring settings for an IT device: 1. Choose Device Settings > Server Reachability. The Server Reachability dialog appears. 2. Select the IT device whose ping monitoring settings you want to remove by clicking it. To make multiple selections, press Ctrl+click or Shift+click to highlight multiple ones. 3. Click Delete. 4.
Chapter 8: Managing External Devices Configuring the Serial Port You can change the bit-rate of the serial port labeled CONSOLE / MODEM on the EMX device. The default bit-rate is 115200 bps. Bit-rate adjustment may be necessary only when you integrate the EMX with another Raritan product via the serial interface. Change the bit-rate before connecting it to a Raritan product through the serial port, or there are communication problems.
Chapter 8: Managing External Devices 2. Log in to the EMX web interface. The EMX should have detected the connected sensors, and display them in the web interface. 3. Identify each sensor through the sensor's serial number. See Identifying Environmental Sensors (on page 170). 4. The EMX should automatically manage the detected sensors. Verify whether detected sensors are managed. If not, have them managed. See Managing Environmental Sensors (on page 171). 5. Configure the sensors.
Chapter 8: Managing External Devices Match the serial number from the tag to those listed in the sensor table. Note that the information in the "#" and "Port" columns is different. Column Information # The ID number assigned to each environmental sensor. Port The number of the SENSOR port where each environmental sensor is physically connected. "CC1" and "CC2" refer to the onboard contact closure sensor termination.
Chapter 8: Managing External Devices Note: To identify all detected sensors, see Identifying Environmental Sensors (on page 170). 4. Click Manage. The "Manage sensor ()" dialog appears, where is the sensor's serial number and is the sensor's type. Note: For a contact closure sensor, a channel number is added to the end of the . 5.
Chapter 8: Managing External Devices 3. Select the sensor that you want to configure. 4. Click Setup. The "Setup of external sensor ()" dialog appears, where is the serial number of this sensor and is the sensor's type. Tip: You can also trigger the same setup dialog by selecting the desired environmental sensor icon in the tree and then clicking Setup on that sensor's page opened in the right pane. 5.
Chapter 8: Managing External Devices Setting the Z Coordinate Format You can use either the number of rack units or a descriptive text to describe the vertical locations (Z coordinates) of environmental sensors. To determine the Z coordinate format: 1. In left navigation panel, click the EMX folder. The Settings page opens. Note: The EMX folder is named "EMX" by default. The name changes after customizing the device name. See Naming the EMX Device (on page 72). 2. Click Setup on the Settings page.
Chapter 8: Managing External Devices Describing the Sensor Location Use the X, Y and Z coordinates to describe each sensor's physical location. You can use these location values to track records of environmental conditions in fixed locations around your IT equipment. The X, Y and Z values act as additional attributes and are not tied to any specific measurement scheme. If you choose to, you can use nonmeasurement values.
Chapter 8: Managing External Devices Setting Data Logging The EMX can store 120 measurements for each sensor in a memory buffer. This memory buffer is known as the data log. Sensor readings in the data log can be retrieved using SNMP. You can configure how often measurements are written into the data log using the Measurements Per Log Entry field.
Chapter 8: Managing External Devices To select partial sensors, select the corresponding checkboxes of the desired sensors in the Logging Enabled column. To select all sensors, click Enable All or Enable All in Page. To deselect all sensors, click Disable All or Disable All in Page. 5. Click OK to save the changes. Information about Update Interval Raritan environmental sensors can be divided into two categories according to the update interval of the sensor's reading or state.
Chapter 8: Managing External Devices To view both of managed and unmanaged environmental sensors: 1. If the EMX folder is not expanded, expand it to show all components. Note: The EMX folder is named "EMX" by default. The name changes after customizing the device name. See Naming the EMX Device (on page 72). 2. Click the External Sensors folder in the EMX Explorer pane, and the External Sensors page opens in the right pane.
Chapter 8: Managing External Devices States of Managed Sensors An environmental sensor shows the state after being managed. Available sensor states vary depending on the sensor type -- numeric or discrete sensors. For example, a contact closure sensor is a discrete (on/off) sensor so it switches between three states only -- unavailable, alarmed and normal.
Chapter 8: Managing External Devices "normal" State This state indicates the sensor is in the normal state. For a contact closure sensor, usually this state is the normal state you have set. If the normal state is set to Normally Closed, the normal state means the contact closure switch is closed. If the normal state is set to Normally Open, the normal state means the contact closure switch is open.
Chapter 8: Managing External Devices "below lower critical" State This state means a numeric sensor's reading is below the lower critical threshold as indicated below: Reading < Lower Critical Threshold "below lower warning" State This state means a numeric sensor's reading is below the lower warning threshold as indicated below: Lower Critical Threshold <= Reading < Lower Warning Threshold Note: The symbol <= means smaller than (<) or equal to (=).
Chapter 8: Managing External Devices After a sensor is removed from management, the ID number assigned to that sensor is released and can be automatically assigned to any newlydetected sensor. Threshold Information Setting and enabling the thresholds causes the EMX to generate alert notifications when it detects that any sensor's state crosses the thresholds. There are four thresholds for each sensor: Lower Critical, Lower Warning, Upper Warning and Upper Critical.
Chapter 8: Managing External Devices Lower Warning Reset Hysteresis Lower Warning Threshold Lower Critical Reset Hysteresis Lower Critical Threshold The hysteresis values define a reset threshold. For upper thresholds, the measurement must fall past this reset threshold before a deassertion event is generated. For lower thresholds, the measurement must rise above this reset threshold before a deassertion event is generated.
Chapter 8: Managing External Devices Webcams The EMX supports webcams connected to it, allowing you to view video or snapshots of the area surrounding the webcam. The following webcams are supported: Logitech® Webcam® Pro 9000, Model 960-000048 Logitech QuickCam Deluxe for Notebooks, Model 960-000043 Logitech QuickCam Communicate MP, Model 960-000240 Logitech C200 The EMX 888 device supports up to two (2) webcams, and the EMX 111 supports one (1) webcam.
Chapter 8: Managing External Devices Configuring Webcams Before you can configure a webcam, it must be connected to the EMX. See Connecting a Logitech Webcam (Optional) (on page 41). To configure a webcam: 1. In the navigation tree, click on the Webcam Management folder. The Webcam Management page opens. 2. Click on the webcam you want to configure and then click Setup at the bottom right of page. The Webcam Setup dialog opens. 3. Enter a name for the webcam. Up to 64 characters are supported. 4.
Chapter 8: Managing External Devices Configuring Webcam Storage By default, when a snapshot is taken using the Store Snapshot to Webcam Storage feature, it is stored locally on the EMX. Up to ten (10) images can be stored on the EMX at once. To save more than 10 snapshots, save the images on a Common Internet File System/Samba. Note: NFS and FTP are not supported for this release and are disabled on the dialog. To configure another storage location for images: 1.
Chapter 8: Managing External Devices Viewing Webcam Snapshots and Videos By default, once a webcam is attached, it is set to take snapshots every five (5) seconds. Change the webcam settings and/or switch between snapshots and live video from the Webcam Setup dialog by clicking on a webcam in the navigation tree and then clicking the Setup button in the Live Preview pane. See Configuring Webcams (on page 185).
Chapter 8: Managing External Devices In the snapshot mode, a snapshot mode icon appears on the top-left corner of the image along with the number of images the webcam is set to take per second. In the video mode, a video mode icon appears on the top-left corner of the image. Switch between snapshot mode and video mode, click Setup and select either the Image or Video radio buttons. A date and time stamp is displayed on each snapshot, as well.
Chapter 8: Managing External Devices To take a snapshot from webcam: 1. In the navigation tree, click on the webcam you want to take a snapshot with. The webcam image is displayed in the right pane. The webcam must be in snapshot mode in order to take snapshots. If the webcam is in video mode, click Setup in the right pane above the video image to open the Webcam Setup dialog, then select the Snapshot radio button. 2.
Chapter 8: Managing External Devices 3. Use the navigation icons to move through each snapshot, or enter a specific page number to jump to that snapshot snapshot page. 4. Click the Refresh icon to refresh the page. New snapshots are displayed if they are available. To delete snapshots manually: Delete snapshots by selecting the checkbox next to the snapshot you want to delete, then clicking the Delete icon at the top of the section.
Chapter 8: Managing External Devices The video remains open in a secondary Live Preview window in the User A's EMX interface. So long as the secondary Live Preview window is open in User A's interface, even after User A logs out of the EMX interface or the session times out, the link is available.
Chapter 8: Managing External Devices Schroff LHX Heat Exchangers After connecting the Schroff® LHX heat exchanger to the EMX device via the Feature port or the RS-485 port, the EMX detects LHX. The LHX is viewed under the Feature folder or the Auxiliary Port folder in the navigation tree, depending on the port it is connected to. Note: If connecting the LHX to the Feature port, use the serial cable provided with the LHX.
Chapter 8: Managing External Devices Naming a Heat Exchanger To help identify an LHX heat exchanger in the EMX web interface, assign a name to it. The customized LHX heat exchanger's name is followed by the device type and RS-485 port number in parentheses. The web interface provides two types of setup dialogs for naming a specific LHX heat exchanger. To name a heat exchanger using the Auxiliary Port Setup dialog: 1. Connect the LHX heat exchanger to EMX if it is not already connected. 2.
Chapter 8: Managing External Devices Configuring LHX Temperature and Fan Thresholds An LHX heat exchanger is implemented with various sensors for detecting the air temperature, water temperature, and fan speed. You can set thresholds for these sensors so that the EMX alerts you when any sensor readings are getting close to a critical condition. These settings are stored on the EMX port where the heat exchanger is connected, and are lost if that heat exchanger is moved to a different port.
Chapter 8: Managing External Devices Viewing the Summary Both the Dashboard and Auxiliary Port pages display the summary of all connected LHX heat exchangers, including the RS-485 port number where each heat exchanger is connected, and each heat exchanger's status. If any LHX heat exchanger is highlighted in red in the summary, it indicates that there is LHX sensor failure on that heat exchanger. View the State or Status column to identify failed sensors. To view the LHX summary on the Dashboard page: 1.
Chapter 8: Managing External Devices If any LHX sensor reading reaches or crosses the critical or warning threshold, that sensor reading row is highlighted in red or yellow. See Readings Highlighted in Yellow or Red (on page 58). Device States and Icon Variations The EMX web interface changes icons to represent different statuses of each connected LHX heat exchanger. Icons Device status The heat exchanger is turned ON and operating normally. The heat exchanger is turned OFF.
Chapter 8: Managing External Devices Operating Hours Operating hours are the accumulative time since the LHX heat exchanger is first connected to the EMX device and turned ON. The EMX web interface displays the operating hours both for the heat exchanger and its fans. Operating hour information is located in the Statistics section of each heat exchanger page.
Chapter 8: Managing External Devices 3. If you clicked Switch Off in the previous step, a dialog appears, prompting you to confirm the operation. Click Yes to turn it off or No to abort the operation. The heat exchanger's icon shown in the web interface changes after being turned on or off. See Device States and Icon Variations (on page 196). PowerLogic PM710 The Schneider Electric PowerLogic® PM710 power meter is connected to the EMX-111 RS485 port.
Chapter 8: Managing External Devices Configuring the PM710 and Configuring Threshold Settings Note: All settings are configured on a per port basis. If you disconnect a PM710 from one EMX port and connect it to another, you must reconfigure the settings. However, if you disconnect a PM710 from a port and then plug it back in to the same port, the already configured settings still apply. To configure the PM710: 1. Connect the PM710 sensor to EMX if it is not already connected. 2.
Chapter 8: Managing External Devices 3. Click on Reset All Min / Max Values at the bottom left of the Sensors section of the page. 4. Click OK to confirm. All values are reset. Clearing the PM710 Energy Accumulators The PM710 saves energy accumulator values, which can be reset as needed. Review your PM710 documentation for additional information. To clear the PM710 energy accumulator values: 1. If the Auxiliary Ports folder is not expanded, expand it to show all devices connected to the RS-485 ports. 2.
Chapter 9 Using SNMP In This Chapter Overview ................................................................................................201 Enabling SNMP .....................................................................................202 Configuring SNMP Notifications ............................................................204 Configuring Users for Encrypted SNMP v3 ...........................................208 SNMP Gets and Sets ............................................................
Chapter 9: Using SNMP Enabling SNMP By default, SNMP v1/v2c is enabled on the EMX so the EMX can communicate with an SNMP manager. If you have disabled the SNMP, it must be enabled to communicate with an SNMP manager. Note that read-only access is enabled and the community string is public. To enable SNMP: 1. Choose Device Settings > Network Services > SNMP. The SNMP Settings dialog appears. 2.
Chapter 9: Using SNMP a. sysContact - the contact person in charge of the system being contacted b. sysName - the name assigned to the system c. sysLocation - the location of the system 5. Select the MIB to be downloaded. The SNMP MIB for your EMX is used by the SNMP manager. Important: You must download the SNMP MIB for your EMX to use with your SNMP manager. Click Download MIB in this dialog to download the desired MIB file. For more details, see Downloading SNMP MIB (on page 209). 6.
Chapter 9: Using SNMP Configuring SNMP Notifications The EMX automatically keeps an internal log of events that occur. See Event Rules and Actions (on page 131). These events can also be used to send SNMP v2c or v3 notifications to a third-party destination. The EMX provides you with the ability to create SNMPv2c and SNMPv3 TRAP communications, or SNMPv2c and SNMPv3 INFORM communications.
Chapter 9: Using SNMP SNMPv2c Notifications To configure the EMX to send SNMP notifications: 1. Choose Device Settings > Network Services > SNMP. The SNMP Settings dialog appears. 2. Enter the MIB-II system group information, if applicable: a. sysContact - the contact person in charge of the system being contacted b. sysName - the name assigned to the system c. sysLocation - the location of the system 3. Select the MIB to be downloaded. The SNMP MIB for your EMX is used by the SNMP manager.
Chapter 9: Using SNMP a. In the Timeout (sec) field, enter the interval of time, in seconds, after which a new inform communication is resent if the first is not received. For example, resend a new inform communication once every 3 seconds. b. In the Number of Retries field, enter the number of times you want to resend the inform communication if it fails. For example, inform communications are resent up to 5 times when the initial communication fails. 8.
Chapter 9: Using SNMP a. sysContact - the contact person in charge of the system being contacted b. sysName - the name assigned to the system c. sysLocation - the location of the system 3. Select the MIB to be downloaded. The SNMP MIB for your EMX is used by the SNMP manager. Important: You must download the SNMP MIB for your EMX to use with your SNMP manager. Click Download MIB in this dialog to download the desired MIB file. For more details, see Downloading SNMP MIB (on page 209). 4.
Chapter 9: Using SNMP Security level Description "noAuthNoPriv" Select this if no authorization or privacy protocols are needed. "authNoPriv" "authPriv" Click OK Select this if authorization is required but no privacy protocols are required. Select the authentication protocol - MD5 or SHA Enter the authentication passphrase and then confirm the authentication passphrase Click OK Select this if authentication and privacy protocols are required.
Chapter 9: Using SNMP 5. Click OK to save the changes. The user is now set up for encrypted SNMP v3 communication. SNMP Gets and Sets In addition to sending traps, the EMX is able to receive SNMP get and set requests from third-party SNMP managers. Get requests are used to retrieve information about the EMX, such as the system location. Set requests are used to configure a subset of the information, such as the SNMP system name. Note: The SNMP system name is the EMX device name.
Chapter 9: Using SNMP 4. Click Save to save the file onto your computer. To download the file from the Device Information dialog: 1. Choose Maintenance > Device Information. The Device Information dialog appears. 2. Click the "download" link in the EMD-MIB, ASSETMANAGEMENTMIB or LHX-MIB field to download the desired SNMP MIB. 3. Click Save to save the file onto your computer. Layout Opening the MIB reveals the custom objects that describe the EMX system.
Chapter 9: Using SNMP SNMP Sets and Thresholds Some objects can be configured from the SNMP manager using SNMP set commands. Objects that can be configured have a MAX-ACCESS level of "read-write" in the MIB. These objects include threshold objects, which causes the EMX to generate a warning and send an SNMP trap when certain parameters are exceeded. See Threshold Information (on page 182) for a description of how thresholds work.
Chapter 10 Using the Command Line Interface In This Chapter About the Interface ................................................................................212 Logging in to CLI ...................................................................................213 Restricted Service Agreement ...............................................................216 Help Command ......................................................................................218 Showing Information .......................
Chapter 10: Using the Command Line Interface Logging in to CLI Logging in via HyperTerminal over a local connection is a little different than logging in using SSH or Telnet. If a security login agreement has been enabled, you must accept the agreement in order to complete the login. Users are authenticated first and the security banner is checked afterwards. With HyperTerminal You can use any terminal emulation programs for local access to the command line interface.
Chapter 10: Using the Command Line Interface 5. Type a password and press Enter. The password is case sensitive, so make sure you capitalize the correct letters. After properly entering the password, the # or > system prompt appears. See Different CLI Modes and Prompts (on page 215) in the EMX User Guide for details. Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile was once used to log in to the EMX web interface or CLI. 6.
Chapter 10: Using the Command Line Interface 5. After properly entering the password, the # or > system prompt appears. See Different CLI Modes and Prompts (on page 215) in the EMX User Guide for details. Tip: The "Last Login" information, including the date and time, is also displayed if the same user profile was once used to log in to the EMX web interface or CLI. 6. You are now logged in to the command line interface and can begin administering the EMX device.
Chapter 10: Using the Command Line Interface Restricted Service Agreement Welcome to EMX CLI! Last login: 2012-08-06 04:58:42 EDT [CLI (Telnet) from ] # show security details [...] Restricted Service Agreement: disabled Restricted Service Agreement Banner Content: Unauthorized access prohibited; all access and activities not explicitly authorized by management are unauthorized. All activities are monitored and logged. There is no privacy on this system.
Chapter 10: Using the Command Line Interface # show security details [...] Restricted Service Agreement: enforced Restricted Service Agreement Banner Content: This is my new restricted service agreement. # -> on login (with newly configured banner) Login for EMX CLI Username: admin Password: RESTRICTED SERVICE AGREEMENT ============================== This is my new restricted service agreement.
Chapter 10: Using the Command Line Interface Help Command The help or ? command shows a list of main CLI commands available for the current mode. This is helpful when you are not familiar with the CLI commands. The help command syntax under the administrator mode is: # help OR # ? The help command syntax under the configuration mode is: config:# help OR config:# ? Press Enter after typing the command, and a list of main commands for the current mode is displayed.
Chapter 10: Using the Command Line Interface Network Configuration This command shows all network configuration, such as the IP address, networking mode, and MAC address. # show network IP Configuration This command shows the IP-related configuration only, such as IPv4 and IPv6 configuration, address(es), gateway, and subnet mask. # show network ip
Chapter 10: Using the Command Line Interface Wireless Configuration This command only shows the wireless configuration of the EMX device, such as the SSID parameter. # show network wireless To show detailed information, add the parameter "details" to the end of the command. # show network wireless details Network Service Settings This command shows the network service settings only, including the Telnet setting, TCP ports for HTTP, HTTPS and SSH services, and SNMP settings.
Chapter 10: Using the Command Line Interface Asset Sensor Settings This command shows the asset sensor settings, such as the total number of rack units (tag ports), asset sensor state, numbering mode, orientation, available tags and LED color settings. # show assetStrip Variables: is one of the options: all, or a number. Option Description all Displays all asset sensor information. Tip: You can also type the command without adding this option "all" to get the same data.
Chapter 10: Using the Command Line Interface Environmental Sensor Information This command syntax shows the environmental sensor's information. # show externalsensors External sensor 3 ('Temperature 1') Sensor type: Temperature Reading: 31.8 deg C (normal) Serial number: AEI0950133 Description: Not configured Location: X Not configured Y Not configured Z Not configured To show detailed information, add the parameter "details" to the end of the command.
Chapter 10: Using the Command Line Interface Deassertion hysteresis: 1.0 deg C Assertion timeout: 0 samples Variables: is one of the options: all, or a number. Option Description all Displays the information for all environmental sensors. Tip: You can also type the command without adding this option "all" to get the same data. A specific Displays the information for the specified environmental environmental sensor only.
Chapter 10: Using the Command Line Interface 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. # show sensor externalsensor details Variables: is the environmental sensor number.
Chapter 10: Using the Command Line Interface Serial #config Entering configuration mode Apply - save and activate changed settings and leave config mode Cancel - leave config mode without applying the changed settings config:# serial {baudRate [1200|2400|4800|9600|19200|38400|57600|115200]} Note: If this command is executed during a session in which the user connected to the serial port of the device, then the changes will take effect after the user logs out and logs back in.
Chapter 10: Using the Command Line Interface 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 profile you want to query. The variable can be one of the options: all or a user's name. Option Description all This option shows all existing user profiles.
Chapter 10: Using the Command Line Interface 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 existing roles. Tip: You can also type the command without adding this option "all" to get the same data.
Chapter 10: Using the Command Line Interface Rack Unit Settings of an Asset Sensor For the Raritan asset sensor, a rack unit refers to a tag port. This command shows the settings of a specific rack unit or all rack units on an asset sensor, such as a rack unit's LED color and LED mode. # show rackUnit Variables: is the number of the FEATURE port where the selected asset sensor is physically connected. For the EMX device with only one FEATURE port, the number is always 1.
Chapter 10: Using the Command Line Interface Blade Extension Strip Settings This command shows the information of a blade extension strip, including the total number of tag ports, and if available, the ID (barcode) number of any connected tag. # show bladeSlot Variables: is the number of the FEATURE port where the selected asset sensor is physically connected. For the EMX device with only one FEATURE port, the number is always 1.
Chapter 10: Using the Command Line Interface History Buffer Length This command syntax shows the length of the history buffer for storing the history commands. # show history bufferlength Displayed information: The current history buffer length is displayed. Examples This section provides examples of the show command. Example 1 - Basic Security Information The diagram shows the output of the show security command.
Chapter 10: Using the Command Line Interface Example 2 - In-Depth Security Information More information is displayed when typing the show security details command. Configuring the EMX Device and Network To configure the EMX device or network settings through the CLI, you must log in as the administrator. Entering the Configuration Mode You must enter the configuration mode since configuration commands function in the configuration mode only. To enter the configuration mode: 1.
Chapter 10: Using the Command Line Interface Quitting the Configuration Mode (on page 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. The commands are case sensitive so ensure you capitalize them correctly. Changing the Device Name This command syntax changes the EMX device's name.
Chapter 10: Using the Command Line Interface Setting the Z Coordinate Format for Environmental Sensors This command syntax enables or disables the use of rack units for specifying the height (Z coordinate) of environmental sensors. config:# emd externalSensorsZCoordinateFormat
Chapter 10: Using the Command Line Interface For more information, see Setting Data Logging (on page 176). Example The following command enables the data logging feature. config:# emd dataRetrieval enable Setting the Data Logging Measurements Per Entry This command syntax 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.
Chapter 10: Using the Command Line Interface Setting the Networking Mode If your EMX device is implemented with both of the wired and wireless networking mechanisms, you must determine which mechanism is enabled for network connectivity before further configuring networking parameters. This command syntax enables the wired or wireless networking mode. config:# network mode Variables: is one of the modes: wired or wireless. Mode Description wired Enables the wired networking mode.
Chapter 10: Using the Command Line Interface Enabling IPv4 or IPv6 This command syntax determines which IP protocol is enabled on the EMX. config:# network ip proto Variables: is one of the options: v4Only, v6Only or both. Mode Description v4Only Enables IPv4 only on all interfaces. This is the default. v6Only Enables IPv6 only on all interfaces. both Enables both IPv4 and IPv6 on all interfaces.
Chapter 10: Using the Command Line Interface Example The following command determines that only IPv4 addresses returned by the DNS server are used. config:# network ip dnsResolverPreference preferV4 Setting the Wireless Parameters You must configure wireless parameters, including Service Set Identifier (SSID), authentication method, Pre-Shared Key (PSK), and Basic Service Set Identifier (BSSID) after the wireless networking mode is enabled. A wireless configuration command begins with network wireless.
Chapter 10: Using the Command Line Interface Setting the Authentication Method This command syntax sets the wireless authentication method to either PSK or Extensible Authentication Protocol (EAP). config:# network wireless authMethod Variables: is one of the authentication methods: PSK or EAP. Method Description PSK The wireless authentication method is set to PSK. EAP The wireless authentication method is set to EAP.
Chapter 10: Using the Command Line Interface Setting the 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. Setting the Outer Authentication This command syntax determines the outer authentication protocol for the EAP.
Chapter 10: Using the Command Line Interface Setting the EAP Identity This command syntax determines the EAP identity. config:# network wireless eapIdentity Variables: is your user name for the EAP authentication. Example The following command sets the EAP identity to "eap_user01." config:# network wireless eapIdentity eap_user01 Setting the EAP Password This command syntax determines the EAP password.
Chapter 10: Using the Command Line Interface d. Press Enter. Tip: To remove an existing CA certificate, simply press Enter without typing or pasting anything when the system prompts you to input the certificate contents. 3. If the certificate is valid, the system shows the command prompt "config:#" again. If not, it shows a message indicating that the certificate is not valid. Example This section provides a CA certificate example only.
Chapter 10: Using the Command Line Interface MIICjTCCAfigAwIBAgIEMaYgRzALBgkqhkiG9w0BAQQwRTELMAk GA1UEBhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aW NzIGFuZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjAmFxE5NjA1MjgxM zQ5MDUrMDgwMBcROTgwNTI4MTM0OTA1KzA4MDAwZzELMAkGA1UE BhMCVVMxNjA0BgNVBAoTLU5hdGlvbmFsIEFlcm9uYXV0aWNzIGF uZCBTcGFjZSBBZG1pbmlzdHJhdGlvbjEgMAkGA1UEBRMCMTYwEw YDVQQDEwxTdGV2ZSBTY2hvY2gwWDALBgkqhkiG9w0BAQEDSQAwR gJBALrAwyYdgxmzNP/ts0Uyf6BpmiJYktU/w4NG67ULaN4B5CnE z7k57s9o3YY3LecETgQ5iQHmkwlYDTL2fTgVfw0CAQOjgaswga
Chapter 10: Using the Command Line Interface Configuring the IPv4 Parameters An IPv4 configuration command begins with network ipv4. The commands are case sensitive so ensure you capitalize them correctly. Setting the IPv4 Configuration Mode This command syntax determines the IP configuration mode. config:# network ipv4 ipConfigurationMode Variables: is one of the modes: dhcp or static. Mode Description dhcp The IPv4 configuration mode is set to DHCP.
Chapter 10: Using the Command Line Interface Example The following command sets the IPv4 preferred host name to "myv4host." config:# network ipv4 preferredHostName my-v4host Setting the IPv4 Address After selecting the static IP configuration mode, you can use this command syntax to assign a permanent IP address to the EMX device. config:# network ipv4 ipAddress Variables: is the IP address being assigned to your EMX device. The value ranges from 0.0.0.0 to 255.255.255.
Chapter 10: Using the Command Line Interface Setting the IPv4 Gateway After selecting the static IP configuration mode, you can use this command syntax to specify the gateway. config:# network ipv4 gateway Variables: is the IP address of the gateway. The value ranges from 0.0.0.0 to 255.255.255.255. Example The following command sets the IPv4 gateway to 255.255.255.0. config:# network ipv4 gateway 255.255.255.
Chapter 10: Using the Command Line Interface Setting the IPv4 Secondary DNS Server After selecting the static IP configuration mode, you can use this command syntax to specify the secondary DNS server. config:# network ipv4 secondaryDNSServer Variables: is the IP address of the secondary DNS server. The value ranges from 0.0.0.0 to 255.255.255.255. Note: The EMX supports a maximum of 3 DNS servers.
Chapter 10: Using the Command Line Interface Example The following command overrides the DHCP-assigned DNS server with the one you specified. config:# network ipv4 overrideDNS enable Configuring the IPv6 Parameters An IPv6 configuration command begins with network ipv6. The commands are case sensitive so ensure you capitalize them correctly. Setting the IPv6 Configuration Mode This command syntax determines the IP configuration mode.
Chapter 10: Using the Command Line Interface Setting the IPv6 Address After selecting the static IP configuration mode, you can use this command syntax to assign a permanent IP address to the EMX device. config:# network ipv6 ipAddress Variables: is the IP address being assigned to your EMX device. This value uses the IPv6 address format. Example The following command assigns the static IPv6 address "3210:4179:0:8:0:800:200:417/128" to the EMX device.
Chapter 10: Using the Command Line Interface Setting the IPv6 Primary DNS Server After selecting the static IP configuration mode, you can use this command syntax to specify the primary DNS server. It is required to enable overriding the auto-assigned DNS server before you can specify the DNS servers manually. See Overriding the IPv6 DHCP-Assigned DNS Server (on page 250). config:# network ipv6 primaryDNSServer Variables: is the IP address of the primary DNS server.
Chapter 10: Using the Command Line Interface Overriding the IPv6 DHCP-Assigned DNS Server After specifying the primary/secondary DNS server, you can use this command to override the DHCP-assigned DNS server with the one you specified. config:# network ipv6 overrideDNS
Chapter 10: Using the Command Line Interface Option Description 10Mbps The LAN speed is always 10 Mbps. 100Mbps The LAN speed is always 100 Mbps. Example The following command lets the EMX determine the optimal LAN interface speed through auto-negotiation. config:# network interface LANInterfaceSpeed auto Changing the LAN Duplex Mode This command syntax determines the LAN interface duplex mode.
Chapter 10: Using the Command Line Interface Changing the HTTP Port This command syntax changes the HTTP port. config:# network services http port Variables: is a TCP port number between 1 and 65535. The default HTTP port is 80. Example The following command sets the HTTP port to 81. config:# network services http port 81 Changing the HTTPS Port This command syntax changes the HTTPS port.
Chapter 10: Using the Command Line Interface Enabling or Disabling Telnet This command syntax enables or disables the Telnet service. config:# network services telnet enabled
Chapter 10: Using the Command Line Interface Enabling or Disabling SSH This command syntax enables or disables the SSH service. config:# network services ssh enabled
Chapter 10: Using the Command Line Interface Determining the SSH Authentication Method This command syntax determines the SSH authentication method. config:# network services ssh authentication Variables:
Chapter 10: Using the Command Line Interface Option Description disable The SNMP v1/v2c protocol is disabled. Example The following command enables the SNMP v1/v2c protocol. config:# network services snmp v1/v2c enable Enabling or Disabling SNMP v3 This command syntax enables or disables the SNMP v3 protocol. config:# network services snmp v3
Chapter 10: Using the Command Line Interface Example This command syntax sets the SNMP read-only community string to "public." config:# network services snmp readCommunity public Setting the SNMP Write Community This command syntax sets the SNMP read/write community string. config:# network services snmp writeCommunity Variables: is a string comprising 4 to 64 ASCII printable characters. The string CANNOT include spaces.
Chapter 10: Using the Command Line Interface Setting the sysName Value This command syntax sets the SNMP MIB-II sysName value. config:# network services snmp sysName Variables: is a string comprising 0 to 255 alphanumeric characters. Example The following command sets the SNMP MIB-II sysName to "Win7_system" config:# network services snmp sysName Win7_system Setting the sysLocation Value This command syntax sets the SNMP MIB-II sysLocation value.
Chapter 10: Using the Command Line Interface Firewall Control You can manage firewall control features through the CLI. The firewall control lets you set up rules that permit or disallow access to the EMX device from a specific or a range of IP addresses. An IPv4 firewall configuration command begins with security ipAccessControl ipv4. An IPv6 firewall configuration command begins with security ipAccessControl ipv6.
Chapter 10: Using the Command Line Interface Modifying the Firewall Control Parameters There are different commands for modifying firewall control parameters.
Chapter 10: Using the Command Line Interface Option Description reject Discards traffic from all IP addresses, and an ICMP message is sent to the source host for failure notification. Tip: You can combine both commands to modify all firewall control parameters at a time. See Multi-Command Syntax (on page 320). Example The following command sets up two parameters of the IPv4 access control feature.
Chapter 10: Using the Command Line Interface config:# security ipAccessControl ipv4 rule add -- OR -- config:# security ipAccessControl ipv4 rule add IPv6 commands To add a new rule to the bottom of the IPv6 rules list, use this command syntax: config:# security ipAccessControl ipv6 rule add To add a new IPv6 rule by inserting it above or below a specific rule, use this command syntax: config:#
Chapter 10: Using the Command Line Interface 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 number. Then: new rule's number = the specified rule number + 1 is the number of the existing rule which you want to insert the new rule above or below.
Chapter 10: Using the Command Line Interface config:# security ipAccessControl ipv4 rule modify policy The command syntax to modify all contents of an existing IPv4 rule: config:# security ipAccessControl ipv4 rule modify ipMask policy IPv6 commands The command syntax to modify an IPv6 rule's IP address and/or subnet mask: config:# security ipAccessControl ipv6 rule modify ipMask The command syntax to modify an IPv6 r
Chapter 10: Using the Command Line Interface Option Description drop Discards traffic from the specified IP address(es), without sending any failure notification to the source host. reject Discards traffic from the specified IP address(es), and an ICMP message is sent to the source host for failure notification. Example The following command modifies all contents of the 5th IPv4 rule. config:# security ipAccessControl ipv4 rule modify 5 ipMask 192.168.84.
Chapter 10: Using the Command Line Interface Example The following command removes the 5th rule from the IPv6 access control list. config:# security ipAccessControl ipv6 rule delete 5 HTTPS Access This command determines whether the HTTPS access to the EMX web interface is forced. If yes, all HTTP access attempts are automatically directed to HTTPS. config:# security enforceHttpsForWebAccess
Chapter 10: Using the Command Line Interface Single Login Limitation This command syntax enables or disables the single login feature, which controls whether multiple logins using the same login name simultaneously is permitted. config:# security loginLimits singleLogin
Chapter 10: Using the Command Line Interface Password Aging Interval This command syntax determines how often the password should be changed. config:# security loginLimits passwordAgingInterval Variables: is a numeric value in days set for the password aging interval. The interval ranges from 7 to 365 days. Example The following command sets the password again interval to 90 days.
Chapter 10: Using the Command Line Interface config:# security userBlocking maximumNumberOfFailedLogins To determine how long a user's login is blocked, use this command syntax: config:# security userBlocking blockTime Variables: is an integer between 3 and 10, or unlimited, which sets no limit on the maximum number of failed logins and thus disables the user blocking function. is a numeric value in minutes.
Chapter 10: Using the Command Line Interface Enabling or Disabling Strong Passwords This command syntax enables or disables the strong password feature. config:# security strongPasswords enabled
Chapter 10: Using the Command Line Interface Maximum Password Length This command syntax determines the maximum length of the password. config:# security strongPasswords maximumLength Variables: is an integer between 16 and 64. Example This command syntax determines that a password must NOT comprise more than 20 characters.
Chapter 10: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneUpperCaseCharacter
Chapter 10: Using the Command Line Interface config:# security strongPasswords enforceAtLeastOneSpecialCharacter
Chapter 10: Using the Command Line Interface Role-Bassed Access Control In addition to firewall access control based on IP addresses, you can configure other access control rules that are based on both IP addresses and users' roles. An IPv4 role-based access control command begins with security roleBasedAccessControl ipv4. An IPv6 role-based access control command begins with security roleBasedAccessControl ipv6.
Chapter 10: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 defaultPolicy Variables:
Chapter 10: Using the Command Line Interface Adding a Role-Based Access Control Rule Depending on where you want to add a new rule in the list, the command syntax for adding a rule varies.
Chapter 10: Using the Command Line Interface Policy Description deny Drops traffic from the specified IP address range when the user is a member of the specified role 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 number.
Chapter 10: Using the Command Line Interface config:# security roleBasedAccessControl ipv4 rule modify startIpAddress endIpAddress To modify an IPv4 rule's role, use this command syntax: config:# security roleBasedAccessControl ipv4 rule modify role To modify an IPv4 rule's policy, use this command syntax: config:# security roleBasedAccessControl ipv4 rule modify policy To modify all contents of an existing IPv4 rule, use t
Chapter 10: Using the Command Line Interface config:# security roleBasedAccessControl ipv6 rule modify policy To modify all contents of an existing IPv6 rule, use this command syntax: 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.
Chapter 10: Using the Command Line Interface Deleting a Role-Based Access Control Rule This command removes a specific rule from the list. config:# security roleBasedAccessControl ipv4 rule delete config:# IPv4 commands IPv6 commands security roleBasedAccessControl ipv6 rule delete Variables: is the number of the existing rule that you want to remove. Example The following command removes the 7th IPv6 rule.
Chapter 10: Using the Command Line Interface Example The following command assigns the name "Cabinet humidity" to the environmental sensor with the ID number 4. config:# externalsensor 4 name "Cabinet humidity" Specifying the Sensor Type Raritan's contact closure sensor (DPX-CC2-TR) supports the connection of diverse third-party or Raritan's detectors/switches. You must specify the type of connected detector/switch for proper operation. Use this command syntax when you need to specify the sensor type.
Chapter 10: Using the Command Line Interface Setting the X Coordinate This command syntax specifies the X coordinate of an environmental sensor. config:# externalsensor xlabel "" Variables: is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the EMX web interface. It is an integer between 1 and 16. is a string comprising up to 24 ASCII printable characters, and it must be enclosed in quotes.
Chapter 10: Using the Command Line Interface Setting the Z Coordinate This command syntax 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 assigned and shown in the EMX web interface. It is an integer between 1 and 16.
Chapter 10: Using the Command Line Interface Changing the Sensor Description This command syntax provides a description for a specific environmental sensor. config:# externalsensor description "" Variables: is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the EMX web interface. It is an integer between 1 and 16.
Chapter 10: Using the Command Line Interface config:# sensor externalsensor upperCritical
Chapter 10: Using the Command Line Interface config:# sensor externalsensor upperWarning
Chapter 10: Using the Command Line Interface config:# sensor externalsensor lowerCritical
Chapter 10: Using the Command Line Interface config:# sensor externalsensor lowerWarning
Chapter 10: Using the Command Line Interface config:# sensor externalsensor hysteresis Variables: is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the EMX web interface. It is an integer between 1 and 16. is one of these sensor types: temperature, humidity, airPressure or air Flow.
Chapter 10: Using the Command Line Interface config:# sensor externalsensor assertionTimeout Variables: is the ID number of the environmental sensor that you want to configure. The ID number is assigned and shown in the EMX web interface. It is an integer between 1 and 16. is one of these sensor types: temperature, humidity, airPressure or air Flow.
Chapter 10: Using the Command Line Interface 2. Re-type the same password for confirmation and press Enter. Variables: is a string comprising up to 32 ASCII printable characters. The variable CANNOT contain spaces.
Chapter 10: Using the Command Line Interface Changing a User's Password This command syntax allows you to change an existing user's password if you have the Administrator Privileges. config:# user modify password After performing the above command, EMX prompts you to enter a new password. Then: 1. Type a new password and press Enter. 2. Re-type the new password for confirmation and press Enter. Variables: is the name of the user whose settings you want to change.
Chapter 10: Using the Command Line Interface Modifying a User's Personal Data You can change a user's personal data, including the user's full name, telephone number, and email address.
Chapter 10: Using the Command Line Interface config:# user modify May fullName "May Turner" telephoneNumber 123-4567 Results: May's full name is specified as May Turner. May's telephone number is set to 123-4567. Enabling or Disabling a User Profile This command syntax enables or disables a user profile. A user can log in to the EMX device only after that user's user profile is enabled.
Chapter 10: Using the Command Line Interface config:# user modify forcePasswordChangeOnNextLogin
Chapter 10: Using the Command Line Interface To determine the security level: config:# user modify securityLevel Variables: is the name of the user whose settings you want to change. is one of the options: noAuthNoPriv, authNoPriv or authPriv. Option Description noAuthNoPriv No authentication and no privacy. authNoPriv Authentication and no privacy. authPriv Authentication and privacy.
Chapter 10: Using the Command Line Interface config:# user modify authenticationPassPhrase Variables: is the name of the user whose settings you want to change. is a string used as an authentication passphrase, comprising up to 32 ASCII printable characters.
Chapter 10: Using the Command Line Interface 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 up to 32 ASCII printable characters. To determine the authentication protocol: config:# user modify authenticationProtocol Variables: is the name of the user whose settings you want to change.
Chapter 10: Using the Command Line Interface config:# user modify May snmpV3Access enable securityLevel authNoPriv userPasswordAsAuthenticationPassPhrase true Results: The user's SNMPv3 access permission is enabled. The SNMPv3 security level is authentication only, no privacy. The authentication passphrase is identical to the user's password. Changing the Role(s) This command syntax changes the role(s) of a specific user.
Chapter 10: Using the Command Line Interface Tip: To set the default measurement units applied to the EMX user interfaces for all users via CLI, see Setting Default Measurement Units. To set the preferred temperature unit: config:# user modify preferredTemperatureUnit Variables: is the name of the user whose settings you want to change. is one of the options: C or F. Option Description C This option displays the temperature in Celsius.
Chapter 10: Using the Command Line Interface Option Description psi This option displays the pressure value in psi. Example The following command sets all measurement unit preferences for the user "May." config:# user modify May preferredTemperatureUnit F preferredLengthUnit feet preferredPressureUnit psi Results: The preferred temperature unit is set to Fahrenheit. The preferred length unit is set to feet. The preferred pressure unit is set to psi.
Chapter 10: Using the Command Line Interface a. Open your SSH public key with a text editor. b. Copy all contents in the text editor. c. Paste the contents into the terminal. d. Press Enter. Tip: To remove an existing SSH public key, simply press Enter without typing or pasting anything when the system prompts you to input the contents. Example This section illustrates how to specify an SSH public key for an existing user "May" if the SSH public key-based authentication is enabled.
Chapter 10: Using the Command Line Interface Deleting a User Profile This command syntax deletes an existing user profile. config:# user delete Example The following command deletes the user profile "May." config:# user delete May Changing Your Own Password Every user can change their own password via this command syntax if they have the Change Own Password privilege. Note that this command does not begin with user.
Chapter 10: Using the Command Line Interface Re-type new password: Setting Up User Preferences (Units of Measure) Welcome to EMX CLI! Last login: 2012-08-06 02:58:14 EDT [CLI (Serial) from ] # show user admin details [...] Preferred temperature unit: Preferred length unit: Preferred pressure unit: deg C Meter Pascal [...
Chapter 10: Using the Command Line Interface Determining the Time Setup Method This command syntax 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 customized. ntp The date and time settings synchronize with a specified NTP server. Example The following command sets the date and time settings by using the NTP servers.
Chapter 10: Using the Command Line Interface Example The following command sets the primary time server to 192.168.80.66. config:# time ntp firstServer 192.168.80.66 Specifying the Secondary NTP Server This command syntax specifies the primary time server if synchronization with the NTP server is enabled. config:# time ntp secondServer Variables: The is the IP address or host name of the secondary NTP server.
Chapter 10: Using the Command Line Interface Example The following command overrides the DHCP-specified NTP servers with the customized NTP servers, including the primary and secondary NTP servers. config:# time ntp overrideDHCPProvidedServer true Role Configuration Commands A role configuration command begins with role. Creating a Role This command syntax creates a new role, with a list of semicolon-separated privileges assigned to the role.
Chapter 10: Using the Command Line Interface 308 Privilege Description changeAssetStripConfiguration Change Asset Strip Configuration changeAuthSettings Change Authentication Settings changeDataTimeSettings Change Date/Time Settings changeEmdConfiguration Change EMD Configuration changeEventSetup Change Event Settings changeExternalSensorsConfiguratio n Change External Sensors Configuration changeLhxConfiguration Change LHX Configuration changeNetworkSettings Change Network Settings chan
Chapter 10: Using the Command Line Interface Example The following command creates a new role and assigns privileges to the role. config:# role create tester firmwareUpdate;viewEventSetup Results: A new role "tester" is created. Two privileges are assigned to the role: firmwareUpdate (Firmware Update) and viewEventSetup (View Event Settings). Modifying a Role You can modify diverse parameters of an existing role, including its privileges.
Chapter 10: Using the Command Line Interface 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 Privileges (on page 307).
Chapter 10: Using the Command Line Interface config:# role modify removePrivileges :,...; :,...; :,...; ... Note: When removing privileges from a role, make sure the specified privileges and arguments (if any) exactly match those assigned to the role. Otherwise, the command fails to remove specified privileges that are not available.
Chapter 10: Using the Command Line Interface Example The following command deletes an existing role. config:# role delete tester Asset Management Commands You can use the CLI commands to change the settings of the connected asset sensor (if any) or the settings of LEDs on the asset sensor. Serial Port Configuration Commands A serial port configuration command begins with serial.
Chapter 10: Using the Command Line Interface Asset Sensor Management An asset sensor management configuration command begins with assetStrip. Naming an Asset Sensor This command syntax names or changes the name of an asset sensor connected to the EMX device. config:# assetStrip name "" Variables: is the number of the FEATURE port where the selected asset sensor is physically connected. For the EMX device with only one FEATURE port, the number is always 1.
Chapter 10: Using the Command Line Interface Example The following command specifies the total number of rack units on the asset sensor #1 to 48 rack units. config:# assetStrip 1 numberOfRackUnits 48 Specifying the Rack Unit Numbering Mode This command syntax specifies the numbering mode of rack units on the asset sensors connected to the EMX device. The numbering mode changes the rack unit numbers.
Chapter 10: Using the Command Line Interface Specifying the Rack Unit Numbering Offset This command syntax specifies the starting number of rack units on the asset sensors connected to the EMX device. config:# assetStrip rackUnitNumberingOffset Variables: is the number of the FEATURE port where the selected asset sensor is physically connected. For the EMX device with only one FEATURE port, the number is always 1.
Chapter 10: Using the Command Line Interface Orientation Description bottomConnector This option indicates that the asset sensor is mounted with the RJ-45 connector located at the bottom. Example The following command specifies the orientation of the RJ-45 connector on the asset sensor #1 to be on the top. config:# assetStrip 1 assetStripOrientation topConnector Rack Unit Configuration For the Raritan asset sensor, a rack unit refers to a tag port.
Chapter 10: Using the Command Line Interface Example The following command assigns the name "Linux server" to the rack unit whose index number is 25 on the asset sensor#1. config:# rackUnit 1 25 name "Linux server" Setting the LED Operation Mode This command syntax determines whether a specific rack unit on the specified asset sensor follows the global LED color settings.
Chapter 10: Using the Command Line Interface Setting the LED Disconnect Color This command syntax sets the LED color for all rack units on the connected asset sensor(s) to indicate the absence of a connected asset tag. config:# assetStrip LEDColorForDisconnectedTags Setting an LED Color for a Rack Unit This command syntax sets the LED color for a specific rack unit on the specified asset sensor.
Chapter 10: Using the Command Line Interface Setting an LED Mode for a Rack Unit This command syntax sets the LED mode for a specific rack unit on the specified asset sensor. You need to set a rack unit's LED mode only when the LED operation mode of this rack unit has been set to "manual." config:# rackUnit LEDMode Variables: is the number of the FEATURE port where the selected asset sensor is physically connected.
Chapter 10: Using the Command Line Interface Setting the History Buffer Length This command syntax changes the history buffer length. The default length is 25. config:# history length Variables: is an integer number between 1 and 250. If you leave the variable blank when using the command, the history buffer is set to 25 by default. Multi-Command Syntax To shorten the configuration time, you can combine various configuration commands in one command and perform all of them at a time.
Chapter 10: Using the Command Line Interface Example 2 - Combination of SSID and PSK Parameters This multi-command syntax configures both of SSID and PSK parameters simultaneously for the wireless feature. config:# network wireless SSID myssid PSK encryp_key Results: The SSID value is set to myssid. The PSK value is set to encryp_key. Quitting the Configuration Mode Both of "apply" and "cancel" commands let you quit the configuration mode.
Chapter 10: Using the Command Line Interface 3. When the "Username to unblock" prompt appears, type the login name of the user to be unblocked and press Enter. 4. A message appears, indicating that the specified user was unblocked successfully. Resetting the EMX You can reset the EMX device to factory defaults or simply restart it using the CLI commands. Restarting the Device This command restarts the EMX device. It is not a factory default reset. To restart the EMX device: 1.
Chapter 10: Using the Command Line Interface Network Troubleshooting The EMX provides 4 diagnostic commands for troubleshooting network problems: nslookup, netstat, ping, and traceroute. The diagnostic commands function as corresponding Linux commands and can get corresponding Linux outputs. Entering the Diagnostic Mode Diagnostic commands function in the diagnostic mode only. To enter the diagnostic mode: 1. Ensure you have entered the administrator mode and the # prompt is displayed. 2.
Chapter 10: Using the Command Line Interface Showing the Network Connections This command syntax displays network connections and/or status of ports. diag> netstat
Chapter 10: Using the Command Line Interface Testing the Network Connectivity This command syntax sends the ICMP ECHO_REQUEST message to a network host for checking its network connectivity. If the output shows the host is responding properly, the network connectivity is good, or the host is shut down or not being connected to the network. diag> ping Variables: is the host name or IP address whose networking connectivity you want to check.
Chapter 10: Using the Command Line Interface Tracing the Route This command syntax traces the network route between your EMX device and a network host. diag> traceroute Variables: is the name or IP address of the host you want to trace. Example The following command displays the existing network routing for the host 192.168.84.222. diag> traceroute 192.168.84.
Chapter 10: Using the Command Line Interface # show help To query available network configuration parameters, the syntax is: config:# network ? OR config:# network help To query available role configuration parameters, the syntax is: config:# role ? OR config:# role help Retrieving Previous Commands If you would like to retrieve any command that was previously typed in the same connection session, press the Up arrow ( ) on the keyboard until the desired command is displayed.
Chapter 10: Using the Command Line Interface Logging out of CLI After completing your tasks using the CLI, always log out of the CLI to prevent others from accessing the CLI. To log out of the CLI: 1. Ensure you have entered the administrator mode and the # prompt is displayed. 2. Type exit and press Enter. Resetting to Factory Defaults (CLI) The Command Line Interface (CLI) provides a reset command for restoring the EMX to factory defaults.
Appendix A Using Raritan Asset Management Sensors with the EMX In This Chapter Asset Sensors and Tags .......................................................................329 Asset Sensors and Tags Asset management tags (AMTs) are electronic IDs that are adhered to data center items such as servers and then plugged in to asset management sensors (AMS) mounted on the rack.
Appendix A: Using Raritan Asset Management Sensors with the EMX Configuring the Asset Sensor The EMX cannot detect how many rack units (tag ports) a connected asset sensor supports, so you must provide this information manually. You can name the asset sensor or determine the numbering way for all rack units in the web interface. Additionally, you can provide a description to identify each asset sensor. The customized name is followed by the label in parentheses.
Appendix A: Using Raritan Asset Management Sensors with the EMX For the latest version of asset sensors with a built-in tilt sensor, it is NOT necessary to configure the orientation setting manually. The EMX device can detect the orientation of the asset sensors and automatically configure it. Top Connector: This option indicates that the asset sensor is mounted with the RJ-45 connector located on the top.
Appendix A: Using Raritan Asset Management Sensors with the EMX Changing a Specific LED's Color Settings In the EMX web interface, a rack unit refers to a tag port on the asset sensor. You can name a specific rack unit, or change its LED color settings so that this LED behaves differently from others on the same asset sensor. To change an LED's settings: 1. Connect the asset sensor to the EMX if it is not already. 2. Click on the Feature Ports folder in the navigation tree to expand it. 3.
Appendix A: Using Raritan Asset Management Sensors with the EMX Connecting AMS-M2-Z Asset Sensors (Optional) The AMS-M2-Z is a special type of asset sensor that functions the same as regular MASTER asset sensors with the following differences: It provides two RJ-45 connectors Multiple AMS-M2-Z asset sensors can be daisy chained Only two tag ports are available on each AMS-M2-Z so only two asset tags can be connected This product is especially useful for tracking large devices such as SAN boxes
Appendix A: Using Raritan Asset Management Sensors with the EMX c. Connect the other end of the cable to the RJ-45 connector labeled "Input" on another AMS-M2-Z. d. Repeat the above steps to daisy chain additional AMS-M2-Z. See AMS-M2-Z Daisy-Chain Limitations (on page 334) for the maximum number of AMS-M2-Z asset sensors supported in the chain. e. It is highly recommended using the cable ties to help hold the weight of all connecting cables. 4.
Appendix A: Using Raritan Asset Management Sensors with the EMX Models Daisy-chain limitations EMX2-888 Up to 6 AMS-M2-Z can be daisy chained. The maximum cable length between each AMS-M2-Z in the chain is 3 meters. Expanding a Blade Extension Strip A blade extension strip, like an asset sensor, has multiple tag ports. After connecting it to a specific asset sensor, it is displayed as a folder on that asset sensor's page.
Appendix A: Using Raritan Asset Management Sensors with the EMX 3. Double-click that rack unit or click the white arrow prior to the folder icon. The arrow then turns into a black, gradient arrow , and all tag ports appear below the folder. To collapse a blade extension strip: Double-click the blade extension strip folder, or click the black, gradient arrow prior to the folder icon. All tag ports under the folder are hidden.
Appendix A: Using Raritan Asset Management Sensors with the EMX Item Description A Barcode (ID number) for the tag connector cable B Tag connector C Cable connector for connecting the blade extension strip Note: A tag connector cable has a unique barcode, which is displayed in the EMX's web interface for identifying each blade extension strip where it is connected.
Appendix A: Using Raritan Asset Management Sensors with the EMX 2. Move the blade extension strip toward the bottom of the blade chassis until its mylar section is fully under the chassis, and verify that the blade extension strip does not fall off easily. If necessary, you may use the adhesive tape in the back of the mylar section to help fix the strip in place. 3. Connect one end of an asset tag to a blade server and connect the other end to the blade extension strip. a.
Appendix A: Using Raritan Asset Management Sensors with the EMX 5. Plug the tag connector of the blade extension strip into the closest tag port of the asset sensor assembly or the AMS-M2-Z asset sensor on the rack. Note: If you need to temporarily disconnect the tag connector of the blade extension strip, wait at least 1 second before connecting it back, or the EMX may not detect it.
Appendix B Integrating EMX and Asset Management Sensors with dcTrack In This Chapter Overview ................................................................................................341 EMX Asset Sensor Management ..........................................................
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack Overview dcTrack™, Raritan's data center management solution, integrates with Raritan's EMX, asset management sensors and asset management tags. This integration allows you to monitor your devices and provide location information on each asset at the rack level using asset management sensors. Asset management tags (AMTs) are adhered to data center items such as servers so you can remotely track the item's location.
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack Diagram key Asset management tag (AMT) Asset management sensor (AMS) EMX EMX/Power IQ To connect each component: 1. Affix the adhesive end of the asset management tag (AMT) to the data center item you want to track, and plug the other end of the AMT into the asset management sensor (AMS). See diagram. in the 2. Use a Cat 5e/6 cable to connect the asset management sensors RJ-45 connector to the EMX. See in the diagram. 3.
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack EMX Asset Sensor Management Before asset sensors can be managed in dcTrack ™, they must be configured in EMX, the EMX needs to be added to dcTrack as a probe item, and the data center item the asset management tag is adhered to must exist in dcTrack. dcTrack supports the EMX2-111 and EMX2-888 models. If you have a large number of EMXs to add, consider using the Import Wizard. See Import Wizard.
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack 5. Click Setup in the Settings section. The Setup of Asset Strip dialog appears. 6. Enter a name of the asset sensor. 7. Type the total number of rack units the selected asset sensor has in the "Number of Rack Units" field. This field shows 48 by default. 8. Determine how to number all rack units on the asset sensor by selecting an option in the Numbering Mode.
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack 12. In the Numbering Offset field, select the starting number. For example, if you select 3, the first rack unit is numbered 3, the second is numbered 4, the third is numbered 5, and so on until the final number. 13. Indicate how the asset sensor is mounted in the rack in the Orientation field. The rack unit that is most close to the RJ-45 connector of the asset sensor will be marked with the index number 1 in the web interface.
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack 6. Click Configure Rack Unit or double-click the selected rack unit. The setup dialog for the selected rack unit appears. 7. In the Name field, type a name for identifying this rack unit. 8. Select either Auto or Manual Override as this rack unit's LED mode. Auto (based on Tag): This is the default setting. With this option selected, the LED follows the global LED color settings.
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack 4. Select Add a New Item from the Actions drop-down in the toolbar. At a minimum, complete all of the required fields on the Detail 1 page. Complete additional fields as needed. 5. Enter the probe name. Required 6. Select the make and model. Required 7. Select the cabinet and rail position of the probe. Required 8.
Appendix B: Integrating EMX and Asset Management Sensors with dcTrack To assign an IP address, select a subnet. This automatically assigns the first available address from the selected subnet. You can change the address by manually typing another address in the subnet, or using the drop-down to view all the available addresses in that subnet. a. If needed, enter comments pertinent to the port. b. Enter the SNMP community name the port is associated with.
Appendix C Raritan PX Asset Management In This Chapter Overview ................................................................................................349 Overview Raritan's PX2 power distribution unit (PDU) also supports asset sensors so that you can remotely track IT devices through the PDU's web interface while monitoring the PDU's power status. Only PDUs with model names that begin with 'PX2' support the asset management function.
Appendix C: Raritan PX Asset Management To set up an asset management system: Affix the adhesive end of an asset tag to each IT device through the tag's tape. Plug the connector on the other end of each asset tag into the corresponding tag port on the asset sensor. Connect the asset sensor assembly on the rack to the Dominion PX device. a. Connect one end of the Category 5e/6 UTP cable to the RJ-45 connector on the asset sensor. b.
Appendix D Specifications In This Chapter Altitude Correction Factors (EMX) .........................................................351 Maximum Ambient Operating Temperature (EMX) ...............................351 Serial RS-232 Port Pinouts....................................................................352 Sensor RJ-12 Port Pinouts ....................................................................352 RS-485 Port Pinouts ..............................................................................
Appendix D: Specifications Serial RS-232 Port Pinouts RS-232 Pin/signal definition Pin No. Signal Direction Description 1 DCD Input Data 2 RxD Input Receive data (data in) 3 TxD Output Transmit data 4 DTR Output Data terminal ready 5 GND ― Signal ground 6 DSR Input Data set ready 7 RTS Output Request to send 8 CTS Input Clear to send 9 RI Input Ring indicator Sensor RJ-12 Port Pinouts RJ-12 Pin/signal definition Pin No.
Appendix D: Specifications RS-485 Pin/signal definition 3 D+ bidirectional Data + 4 ― ― ― 5 ― ― ― 6 D- bidirectional Data - 7 ― ― ― 8 ― ― ― 353
Appendix E LDAP Configuration Illustration This section provides an LDAP example for illustrating the configuration procedure using Microsoft Active Directory® (AD). To configure LDAP authentication, four main steps are required: a. Determine user accounts and groups intended for the EMX b. Create user groups for the EMX on the AD server c. Configure LDAP authentication on the EMX device d. Configure roles on the EMX device In This Chapter Step A. Determine User Accounts and Groups ......................
Appendix E: LDAP Configuration Illustration Step B. Configure User Groups on the AD Server You must create the groups for the EMX on the AD server, and then make appropriate users members of these groups. In this illustration, we assume: The groups for the EMX are named EMX_Admin and EMX_User. User accounts emxuser, emxuser2, usera and userb already exist on the AD server. To configure the user groups on the AD server: 1. On the AD server, create new groups -- EMX_Admin and EMX_User.
Appendix E: LDAP Configuration Illustration Step C. Configure LDAP Authentication on the EMX Device You must enable and set up LDAP authentication properly on the EMX device to use external authentication. In the illustration, we assume: The DNS server settings have been configured properly. See Modifying the Network Settings (on page 80) and Role of a DNS Server (on page 84). The AD server's domain name is techadssl.com, and its IP address is 192.168.56.3.
Appendix E: LDAP Configuration Illustration Base DN for Search - Type dc=techadssl,dc=com as the starting point where your search begins on the AD server. Login Name Attribute - Ensure the field is set to sAMAccountName because the LDAP server is Microsoft Active Directory. User Entry Object Class - Ensure the field is set to user because the LDAP server is Microsoft Active Directory. User Search Subfilter - The field is optional.
Appendix E: LDAP Configuration Illustration Note: For more information on LDAP configuration, see Setting Up LDAP Authentication (on page 123). 5. Click OK to save the changes. The LDAP server is saved. 6. Click OK to save the changes. The LDAP authentication is activated. Note: If the EMX clock and the LDAP server clock are out of sync, the certificates are considered expired and users are unable to authenticate using LDAP.
Appendix E: LDAP Configuration Illustration c. Click Add. d. Repeat Steps a to c to add all permissions beginning with "View." 6. Click OK to save the changes. The EMX_User role is created. 7. Keep the Manage Roles dialog opened to create the EMX_Admin role. To create the EMX_Admin role with full permissions assigned: 1. Click New. The Create New Role dialog appears.
Appendix E: LDAP Configuration Illustration 2. Type EMX_Admin in the Role Name field. 3. Type a description for the EMX_Admin role in the Description field. In this example, we type "The role includes all privileges" to describe the role. 4. Click the Privileges tab to select the Administrator permission. The Administrator permission allows users to configure or change all EMX settings. a. Click Add. The "Add Privileges to new Role" dialog appears. b.
Appendix E: LDAP Configuration Illustration 5. Click OK to save the changes. The EMX_Admin role is created. 6. Click Close to quit the dialog.
Index A A Note about Untriggered Rules • 158 About Contact Closure Sensors • 35 About the Interface • 212 Access Security Control • 104 Add Page Icon • 56 Adding a Firewall Rule • 261 Adding a Role-Based Access Control Rule • 276 Adding an EMX to dcTrack • 342, 346 Adding IT Devices for Ping Monitoring • 165 Adding the LDAP Server Settings • 124 Alert States and LHX Event Log • 196 All Privileges • 307, 310, 311 Altitude Correction Factors (EMX) • 74, 351 AMS-M2-Z Daisy-Chain Limitations • 29, 329, 333, 334
Index Connecting a Logitech Webcam (Optional) • 41, 184, 185 Connecting a Schroff LHX Heat Exchanger (Optional) • 41, 192 Connecting AMS-M2-Z Asset Sensors (Optional) • iii, 28, 333 Connecting an Asset Sensor to the EMX-111 • 25 Connecting an Asset Sensor to the EMX-888 • 27 Connecting Asset Sensors to the EMX • 24, 29, 333, 343 Connecting Blade Extension Strips • 30, 336 Connecting Detectors/Switches to DPX-CC2TR • 36 Connecting Differential Air Pressure Sensors • 40 Connecting Environmental Sensors (Opti
Index Enabling Login Limitations • 111 Enabling or Disabling a User Profile • 294 Enabling or Disabling Data Logging • 233 Enabling or Disabling SNMP v1/v2c • 255 Enabling or Disabling SNMP v3 • 256 Enabling or Disabling SSH • 254 Enabling or Disabling Strong Passwords • 270 Enabling or Disabling Telnet • 253 Enabling Password Aging • 113 Enabling Service Advertisement • 92 Enabling SNMP • 176, 202 Enabling Strong Passwords • 112 Enabling the Feature • 113 Enabling the Firewall • 105 Enabling User Blocking
Index Logging in to CLI • 213 Logging out of CLI • 328 Login Limitation • 266 Logout • 52 Lowercase Character Requirement • 271 M MAC Address • 50 Managing Environmental Sensors • 170, 171 Managing External Devices • 161 Managing Firewall Rules • 261 Managing Role-Based Access Control Rules • 275 Managing Roles • 69 Managing Users • 62 Maximum Ambient Operating Temperature (EMX) • 351 Maximum Password History • 273 Maximum Password Length • 271 Menus • 55 Minimum Password Length • 270 Modifying a Firewall
Index Record Snapshots to Webcam Storage • 143 Reset Button • 50 Resetting the EMX • 322 Resetting the PM710 Minimum and Maximum Values • 199 Resetting to Factory Defaults • 50, 102, 322 Resetting to Factory Defaults (CLI) • 328 Restarting the Device • 322 Restricted Service Agreement • 216 Retrieving Previous Commands • 327 Role Configuration Commands • 307 Role of a DNS Server • 84, 356 Role-Bassed Access Control • 274 RS-485 Port Pinouts • 352 S Sample Asset-Management-Level Event Rule • 154 Sample Eve
Index Setting Up an EMX Using Bulk Configuration • iii, 72, 94 Setting Up an SSL Certificate • iii, 104, 118 Setting Up Asset Sensors in EMX • 343 Setting Up Default User Preferences (Units of Measure) • iii, 65, 67, 75 Setting Up LDAP Authentication • 84, 104, 123, 358 Setting Up Role-Based Access Control Rules • 113 Setting Up Roles • 53, 62, 65, 69, 176 Setting Up User Login Controls • 110 Setting Up User Preferences (Units of Measure) • iii, 65, 67, 75, 301, 304 Setup Button • 55 Show Serial • 224 Show
Index Wired Network Settings • 78 Wireless Configuration • 220 Wireless Network Settings • 79 With HyperTerminal • 213, 321 With SSH or Telnet • 214 369
U.S./Canada/Latin America Monday - Friday 8 a.m. - 6 p.m. ET Phone: 800-724-8090 or 732-764-8886 For CommandCenter NOC: Press 6, then Press 1 For CommandCenter Secure Gateway: Press 6, then Press 2 Fax: 732-764-8887 Email for CommandCenter NOC: tech-ccnoc@raritan.com Email for all other products: tech@raritan.com China Europe Europe Monday - Friday 8:30 a.m. - 5 p.m. GMT+1 CET Phone: +31-10-2844040 Email: tech.europe@raritan.com United Kingdom Monday - Friday 8:30 a.m. to 5 p.m.
